Trouble mapping Backspace

I'm new to your great interface, but keeps crashing when inputting backspace
NotFoundError

The object can not be found here.

  [native code]:undefined:undefined
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:94704
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:95949
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96409
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97769
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97555
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96347
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:97527
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96099
  https://nickcoutsos.github.io/keymap-editor/react.5a014ff6c3bc1104749a.js:2:96212

Could you be more specific about what you mean by "inputting backspace"?

Sorry, I’m new to ZMK and now realised that it was not just the backspace
that was the issue. What I meant was that when using the Keymap Editor to
change the left Thumb key from the default one (which was space) on the
Corne setup, the screen would sometimes freeze with the message that I
attached. Have since encountered the same issue intermittently with other
keys eg adding the Bluetooth Select Profile 2 to another key. Not
consistently though.
Seem to have gotten through by frequent saves, and have installed the new
keymap onto my Corne.
Thanks again for creating this interface - really helpful. I hope my
message was helpful.
Kind Regards,
Peter
On 24 July 2023 at 12:22:07 am, Nick Coutsos @.***)
wrote:
Could you be more specific about what you mean by "inputting backspace"?
—
Reply to this email directly, view it on GitHub
https://github.com/nickcoutsos/keymap-editor/issues/124#issuecomment-1646852487,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWAB37YM74NQYXGLL45NXHTXRUXQ7ANCNFSM6AAAAAA2UKFBKE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm glad that you're having at least some success using the app, but if this is a persistent problem (I think there were ~40 such errors logged yesterday, possibly from your session) I'd really like to solve it. There have been sporadic errors before that seem like they could be related to this but you're the first person to step forward so if you're able to help me better understand what's happening it would mean a lot.
From your description it doesn't sound like the specifics of what you're doing (which key is being bound with what value) matter, and from the call stack in the error message it looks like the problem is coming up while React is doing its processing rather than in the application logic.
Can you tell me a little about your browser setup? I'm wondering if there are any extensions or even built-in functionality (to do translation, maybe) that would manipulate the DOM and leave it in an unexpected state when React attempts to re-render.
Something like this during keybind actions could mean the DOM tree changing unexpectedly at the moment that a modal dialog is being opened/closed.

Going ahead with the idea of browser translation corrupting the DOM tree, I was able to reliably reproduce the same kind of error in my dev environment using the following steps:

Open Keymap Editor in Chrome (demo keyboard is fine)
Right-click to open the context menu and chose the translate option (I went with English to Japanese)
Click on the binding for Space to open the binding dialog
Click on the Space key code parameter to open the key code picker dialog
Click on the Backspace option (should be the second in the list)

I've pushed a fix for this instance. It's possible there are others and I'll have a look for similar areas of the codebase that could be affected.
I've also updated my error logging so that if another exception is thrown during React rendering I should also get an indication of which component to look at. Please let me know if you're encountering the failure and I can look at other potential causes.

Hi Nick,
Thanks for doing this - I’ll let you know if anything comes up; I’m an
incessant tinkerer, so will be using the editor intermittently for a while
to find that “perfect” setup!
Cheers,
Peter

I see that a few more errors have popped up in another location, I'll be away for a few days and may not be able to address everything right away but the new instances follow the same pattern which should make it easier for me to start tracking them down proactively. I'll update here when I can!

The error rate has been reduced since I started applying fixes to DOM manipulations such as those by translators so it looks like that strategy of testing and exception tracing is a good one.
I'm sure this isn't the end of it yet, but I'm going to go ahead and close the issue now -- if another one crops up and I'm not getting to it quickly enough feel free to make another issue to grab my attention.

Hi Nick,
Thanks for letting me know. I have used it a few more times and no issues
since the last email. I’ll let you know if anything comes up. Again thanks
on behalf of all of us who benefit from the ease that your app allows!
Cheers,
Peter
On 4 August 2023 at 10:25:59 am, Nick Coutsos @.***)
wrote:
The error rate has been reduced since I started applying fixes to DOM
manipulations such as those by translators so it looks like that strategy
of testing and exception tracing is a good one.
I'm sure this isn't the end of it yet, but I'm going to go ahead and close
the issue now -- if another one crops up and I'm not getting to it quickly
enough feel free to make another issue to grab my attention.
—
Reply to this email directly, view it on GitHub
https://github.com/nickcoutsos/keymap-editor/issues/124#issuecomment-1664795984,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWAB372ROFHZTUTTPDNSHCTXTQ6RPANCNFSM6AAAAAA2UKFBKE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add port field on "Quick Connection" toolbar

Hi!
It's possible to add a "Port" field on "Quick Connection" toolbar?
Many people must connect to servers using not default ports.
Thanks!

Wasn't immediately obvious to me either but in the host field you can use specify $HOSTNAME:$PORT

Ok, thanks, but this trick isn't explained anywhere.
Please, can you add a port field (numeric or char, due serial connections like COM1, COM2, ...)?


Apps can not be installed or updated anymore after 3.33.80 update

Describe the bug
Apps cannot be installed or updated. When clicking either action, the "Please wait" bar pops up and nothing else happens. When starting the Appimage (Linux), there is no error indicated on the console either, just the following output (no timeout seems to occur) -
./web-os-dev-manager_1.11.18_amd64.AppImage
[2023-10-27T19:49:57Z INFO  app::conn_pool::connection] DeviceConnection { id=737e42e5-cea3-4819-8462-3f5f0b72f146, device.name=lgtv } created
[2023-10-27T19:49:57Z INFO  app::conn_pool::connection] DeviceConnection { id=8ba26232-1aa8-430d-af79-f790de828295, device.name=lgtv } created
[2023-10-27T19:49:57Z INFO  app::conn_pool::connection] Dropping DeviceConnection { id=737e42e5-cea3-4819-8462-3f5f0b72f146, device.name=lgtv }, last_ok=true
[2023-10-27T19:49:57Z INFO  app::conn_pool::connection] DeviceConnection { id=9189e1d6-7149-4827-a55a-db72c78bf3b4, device.name=lgtv } created
[2023-10-27T19:49:57Z INFO  app::conn_pool::connection] DeviceConnection { id=00f2a1f9-e12d-4d8c-9133-824adce2cd6c, device.name=lgtv } created

To Reproduce
Steps to reproduce the behavior:

Go to 'Apps'
Click on 'any app that should be updated or installed''
Scroll down to ''
See error

Expected behavior
The selected action either updates or installs an app.
Screenshots
Currently installed apps. I removed Moonlight for testing ...

App update / installation indicator indefinitely indicating ...

System specs according to dev-manager-desktop ...

Additional context

OS: Debian 12 (x64)
TV: see screenshot above; developer mode, not rooted

IPK files (e.g. Kodi) also cannot be installed / updated manually anymore. The behavior happened sporadically previously (a restart of the app usually fixed it), but doesn't go away after updating the TV to firmware 3.33.80 and 3.33.85. The same is the case for the "webos-homebrew-channel" app, which doesn't allow to install or update applications anymore (greyed out).
This may or may not be a bug in dev-manager-desktop, but I would appreciate some feedback on what to do next. Disable developer mode, re-enable and start over or can this perhaps be fixed another way? Did anybody experience the same behavior with the latest update or is dev mode screwed up on my end? I'll gladly provice any logs and screenshots you might need.

Hi. Other than installing via this app, you could try install with ares-install and see the logs. https://github.com/webosbrew/ares-cli-rs

When you say "installed / updated manually", do you mean running luna-send(-pub) luna://com.webos.appInstallService/dev/install (or equivalent) on the TV?

I'll give ares-cli-rs a try soon and report back and as for your question, @throwaway96 , I (imprecisely - sorry for that) meant the "Install" button to the right hand side where you select a separately downloaded IPK.

@mariotaku I didn't get around to it right away, but using the ares-install you linked, I could install new apps (e.g. Moonlight) as well as updates to already existing ones (e.g. Kodi) without any problems.

Might be fixed in recent updates. Feel free to reopen if you're still seeing this issue.

@mariotaku thank you very much, but could it be that the assets under the 1.12.2 tag are still v1.12.1? The file name and at least AppImage state the older version.


Replace trollop with optimist

gauntlt outputs the following deprecation message related to the trollop dependency:
[DEPRECATION] This gem has been renamed to optimist and will no longer be supported. Please switch to optimist as soon as possible.

I also encountered the same issue. Any workaround for the issue?


Feedback on Using Llama 2 to Answer Questions About Local Documents

Regarding https://swharden.com/blog/2023-07-30-ai-document-qa/
Feedback goes here...
I loved your article! Just what I needed!
I’m creating a school-friendly AI for my school which can be fed audio (transcript by OpenAI’s whisper which is free) and txt docs. Any advice? I plan to have Python scripts that can be triggered via an Electron framework application.

Hi @Oscar123456780, I'm happy you found the article useful!
I haven't explored this topic much more beyond what I discovered and wrote on that page, so I'm afraid I don't have tons of advice there. I see HuggingFace has a Discord https://discord.com/invite/hugging-face-879548962464493619 maybe the group there can offer better suggestions based on them having more personal experience working with these models and document ingestion.
Hope it helps! Good luck! 🚀


Struct property is not selected in Presto

Expected behavior
A struct property in a class should be retrieved in Presto when the topic is queried. Preferably as a nested object or otherwise as flattened properties.
Actual behavior
The property isn't selected at all.
Steps to reproduce
Create a class with a property of type LocalDate.
Add messages to a topic with JSON schema.
Select the topic in Presto.
It is expected that the property classified as LocalDate is returned (as a nested object).
When reading the message with Pulsar the message does contain the LocalDate property as an object.
Message id: 2535:2:-1:0
Message key: 1
Message value: {"orderNbr":1,"customerNbr":1,"orderStatus":"O","totalPrice":173665.47,"orderDate":{"year":1996,"month":"JANUARY","chronology":{"calendarType":"iso8601","id":"ISO"},"era":"CE","dayOfYear":2,"dayOfWeek":"TUESDAY","leapYear":true,"monthValue":1,"dayOfMonth":2},"orderPriority":"5-LOW","clerkNbr":"Clerk#000000951","shipPriority":0,"comment":"nstructions sleep furiously among "}
Message publish time:<PHONE_NUMBER>827
Message event time:<PHONE_NUMBER>773

When we select in Presto this is the result:
select * from pulsar."public/default"."order-json-key-date" where ordernbr=1;
 ordernbr | customernbr | orderstatus | totalprice | orderpriority |    clerknbr     | shippriority |              comment               | __partition__ |     __event_time__      |    __publish_time__     | __message_id__ | __seque
----------+-------------+-------------+------------+---------------+-----------------+--------------+------------------------------------+---------------+-------------------------+-------------------------+----------------+--------
        1 |           1 | O           |  173665.47 | 5-LOW         | Clerk#000000951 |            0 | nstructions sleep furiously among  |            -1 | 2020-07-24 10:50:35.773 | 2020-07-24 10:50:35.827 | (2535,2,0)     |
(1 row)

The property "orderDate" is missing.
System configuration
Pulsar version: 2.6.0

Archive.zip


netopeer2 ssh authentication using ssh-keys

Hello team,
I am trying to authenticate netopeer2-cli user with help of public keys. To achieve this i performed following steps:

generated ssh public and private keys with ssh-keygen command
update sysrepoctl with ietf-system.yang (it already exist)

root@embedded-PC:/home/abhishek_s# sysrepoctl -i /root/ietf-system.yang -v 4
[INF]: Applying scheduled changes.
[INF]: No scheduled changes.
[ERR]: Module "ietf-system" not scheduled for deletion.
[ERR]: Module "ietf-system" is already in sysrepo.

connected to server and tried to write xml data with help of following commands:

connect --login root
edit-config --target running --config=/root/ssh_auth.xml

But edit-config command failed to write to server. I got following error:

edit-config --target running --config=/root/ssh_auth.xml
ERROR
type:     application
tag:      operation-failed
severity: error
path:     /ietf-system:system/authentication
message:  Unknown element "authentication".

At first it seems like authentication element failed to locate in ietf-system yang but I do see authentication container here

ssh_auth.xml file

ssh_auth.txt
Please suggest how can I connect server using ssh public/private keys.

Just installing a YANG module is not enough to "get this working"; you would need something which installs these SSH keys into the system for your changes to take effect. Today, Netopeer2 authenticates the users via their ~/.ssh/authorized_keys files, so just put the pubkeys in there. If you would like to manage these keys themselves via NETCONF, then you need to write that piece of software (but also see #811).

Just installing a YANG module is not enough to "get this working"; you would need something which installs these SSH keys into the system for your changes to take effect. Today, Netopeer2 authenticates the users via their ~/.ssh/authorized_keys files, so just put the pubkeys in there. If you would like to manage these keys themselves via NETCONF, then you need to write that piece of software (but also see #811).


[stability] Cleanup designed tests

Remove all test files for designed cases from master branch,
maintain them in "designed" branch:
https://github.com/crosswalk-project/crosswalk-test-suite/tree/designed/stability
Update Crosswalk Fuzz Testing to approved

https://crosswalk-project.org/jira/browse/XWALK-4606

@wanghongjuan  Lei add comment in https://crosswalk-project.org/jira/browse/XWALK-3575 said that the app can test pass, but i test it failed in 14.42.335.0 and 15.44.376.0.
In Nexus4 and Memo Pad, it fail to launch
In ZTE, it start with a black page.
Please help to confirm the app result.

merge this PR.
since the fuzz app works fine on crosswalk 12, 13, 14 in Xwalk-3575 comments.
So if meet issue on Crosswalk 15, let's report bug for it :0


[INLONG-6073][Kubernetes] Add audit.config.store.mode Configurable to k8s

Prepare a Pull Request
Add audit.config.store.mode Configurable to k8s

Fixes #6073

Motivation
Add audit.config.store.mode Configurable to k8s
Modifications
Add audit.config.store.mode Configurable to k8s

how to configure the address for different store types?

how to configure the address for different store types?

New commit has add some basic configuration for ck and es.


Add GuardDuty service

Looks like some wires got crossed and there are changes in here from https://github.com/rusoto/rusoto/pull/979 . Those need to be pulled out before merging this.

Ready for review @adimarco 😄

Appveyor is being fussy, don't think it's our fault:
cargo update
    Updating registry `https://github.com/rust-lang/crates.io-index`
cargo test --all --lib -v
 Downloading serde v1.0.74
error: unable to get packages from source
Caused by:
  [35] SSL connect error (schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.)
Command exited with code 101

Needs rebasing now.


stat /var/lib/calico/nodename: no such file or directory problem,please help.

Hi, here is a problem in my kubernetes cluster, in the node wx3, I want to create a static pod named jenkins, but kubelet make error log over and over.
E0322 15:59:06.016063    1239 kuberuntime_gc.go:152] Failed to stop sandbox "420698bd9963f65496a5fd0c127f2b23497d678ddcf58362aa35615d8739d372" before removing: rpc error: code = Unknown desc = NetworkPlugin cni failed to teardown pod "jenkins-wx3_default" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ W0322 15:59:14.922384    1239 helpers.go:847] eviction manager: no observation found for eviction signal allocatableNodeFs.available I0322 15:59:17.649057    1239 kuberuntime_manager.go:389] No ready sandbox for pod "jenkins-wx3_default(1d947eff714cafbfcc78ef0291db3291)" can be found. Need to start a new one W0322 15:59:17.651466    1239 cni.go:265] CNI failed to retrieve network namespace path: Cannot find network namespace for the terminated container "aaf3954dc74a610b5da9cfbbcf67d413b64ee49f00d5df0835fb7f340449181b" E0322 15:59:17.756783    1239 cni.go:319] Error deleting network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ E0322 15:59:17.757482    1239 remote_runtime.go:115] StopPodSandbox "aaf3954dc74a610b5da9cfbbcf67d413b64ee49f00d5df0835fb7f340449181b" from runtime service failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to teardown pod "jenkins-wx3_default" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ E0322 15:59:17.757520    1239 kuberuntime_manager.go:781] Failed to stop sandbox {"docker" "aaf3954dc74a610b5da9cfbbcf67d413b64ee49f00d5df0835fb7f340449181b"} E0322 15:59:17.757568    1239 kuberuntime_manager.go:581] killPodWithSyncResult failed: failed to "KillPodSandbox" for "1d947eff714cafbfcc78ef0291db3291" with KillPodSandboxError: "rpc error: code = Unknown desc = NetworkPlugin cni failed to teardown pod \"jenkins-wx3_default\" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/" E0322 15:59:17.757597    1239 pod_workers.go:182] Error syncing pod 1d947eff714cafbfcc78ef0291db3291 ("jenkins-wx3_default(1d947eff714cafbfcc78ef0291db3291)"), skipping: failed to "KillPodSandbox" for "1d947eff714cafbfcc78ef0291db3291" with KillPodSandboxError: "rpc error: code = Unknown desc = NetworkPlugin cni failed to teardown pod \"jenkins-wx3_default\" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/"
when I put the jenkins.yml to wx1, everything ok.
how can I fix it ?
 Specifically I'm wondering if you are using an release candidate of the CNI plugin but have not updated calico-node.
What version of the calico/node are your running and what version of calico/cni are you using?

How did you install your calico components?
With the new v3.1.0-rc1 components it is necessary to mount /var/lib/calico to the calico-node container so that it can write the file /var/lib/calico/nodename that is being referenced in the logs you reported.  If you installed from one of the master docs manifests from the docs site please let us know so we can update it.

Hi, tmjd,this is my calico.yaml, a DaemonSet of k8s, image is quay.io/calico/node:master
`ubuntu@ubuntu1:~$ sudo kubectl get ds -o yaml -n kube-system
apiVersion: v1
items:

apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
creationTimestamp: 2017-12-12T06:44:39Z
generation: 3
labels:
k8s-app: calico-node
name: calico-node
namespace: kube-system
resourceVersion: "11801514"
selfLink: /apis/extensions/v1beta1/namespaces/kube-system/daemonsets/calico-node
uid: ecf5370f-df07-11e7-9cdd-00e066414888
spec:
revisionHistoryLimit: 10
selector:
matchLabels:
k8s-app: calico-node
template:
metadata:
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ""
scheduler.alpha.kubernetes.io/tolerations: |
[{"key": "dedicated", "value": "master", "effect": "NoSchedule" },
{"key":"CriticalAddonsOnly", "operator":"Exists"}]
creationTimestamp: null
labels:
k8s-app: calico-node
spec:
containers:
- env:
- name: ETCD_ENDPOINTS
valueFrom:
configMapKeyRef:
key: etcd_endpoints
name: calico-config
- name: CALICO_NETWORKING_BACKEND
valueFrom:
configMapKeyRef:
key: calico_backend
name: calico-config
- name: CLUSTER_TYPE
value: k8s,bgp
- name: CALICO_DISABLE_FILE_LOGGING
value: "true"
- name: CALICO_K8S_NODE_REF
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: spec.nodeName
- name: FELIX_DEFAULTENDPOINTTOHOSTACTION
value: ACCEPT
- name: CALICO_IPV4POOL_CIDR
value: <IP_ADDRESS>/16
- name: CALICO_IPV4POOL_IPIP
value: cross-subnet
- name: FELIX_IPV6SUPPORT
value: "false"
- name: FELIX_LOGSEVERITYSCREEN
value: info
- name: FELIX_IPINIPMTU
value: "1440"
- name: ETCD_CA_CERT_FILE
valueFrom:
configMapKeyRef:
key: etcd_ca
name: calico-config
- name: ETCD_KEY_FILE
valueFrom:
configMapKeyRef:
key: etcd_key
name: calico-config
- name: ETCD_CERT_FILE
valueFrom:
configMapKeyRef:
key: etcd_cert
name: calico-config
- name: IP
- name: FELIX_HEALTHENABLED
value: "true"
image: quay.io/calico/node:master
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 6
httpGet:
path: /liveness
port: 9099
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: calico-node
readinessProbe:
failureThreshold: 3
httpGet:
path: /readiness
port: 9099
scheme: HTTP
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
resources:
requests:
cpu: 250m
securityContext:
privileged: true
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /lib/modules
name: lib-modules
readOnly: true
- mountPath: /var/run/calico
name: var-run-calico
- mountPath: /calico-secrets
name: etcd-certs
- command:
- /install-cni.sh
env:
- name: CNI_CONF_NAME
value: 10-calico.conflist
- name: ETCD_ENDPOINTS
valueFrom:
configMapKeyRef:
key: etcd_endpoints
name: calico-config
- name: CNI_NETWORK_CONFIG
valueFrom:
configMapKeyRef:
key: cni_network_config
name: calico-config
image: quay.io/calico/cni:master
imagePullPolicy: IfNotPresent
name: install-cni
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /host/opt/cni/bin
name: cni-bin-dir
- mountPath: /host/etc/cni/net.d
name: cni-net-dir
- mountPath: /calico-secrets
name: etcd-certs
dnsPolicy: ClusterFirst
hostNetwork: true
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: calico-node
serviceAccountName: calico-node
terminationGracePeriodSeconds: 0
volumes:
- hostPath:
path: /lib/modules
type: ""
name: lib-modules
- hostPath:
path: /var/run/calico
type: ""
name: var-run-calico
- hostPath:
path: /opt/cni/bin
type: ""
name: cni-bin-dir
- hostPath:
path: /etc/cni/net.d
type: ""
name: cni-net-dir
- name: etcd-certs
secret:
defaultMode: 420
secretName: calico-etcd-secrets
templateGeneration: 3
updateStrategy:
type: OnDelete
status:
currentNumberScheduled: 3
desiredNumberScheduled: 3
numberAvailable: 3
numberMisscheduled: 0
numberReady: 3
observedGeneration: 3
updatedNumberScheduled: 3
kind: List
metadata:
resourceVersion: ""
selfLink: ""`

`ubuntu@ubuntu1:~$ sudo kubectl get po calico-node-vb6gj -o yaml -n kube-system
apiVersion: v1
kind: Pod
metadata:
annotations:
kubernetes.io/created-by: |
{"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"DaemonSet","namespace":"kube-system","name":"calico-node","uid":"ecf5370f-df07-11e7-9cdd-00e066414888","apiVersion":"extensions","resourceVersion":"11793622"}}
scheduler.alpha.kubernetes.io/critical-pod: ""
scheduler.alpha.kubernetes.io/tolerations: |
[{"key": "dedicated", "value": "master", "effect": "NoSchedule" },
{"key":"CriticalAddonsOnly", "operator":"Exists"}]
creationTimestamp: 2018-03-22T02:29:06Z
generateName: calico-node-
labels:
controller-revision-hash: "3331114009"
k8s-app: calico-node
pod-template-generation: "3"
name: calico-node-vb6gj
namespace: kube-system
ownerReferences:

apiVersion: extensions/v1beta1
blockOwnerDeletion: true
controller: true
kind: DaemonSet
name: calico-node
uid: ecf5370f-df07-11e7-9cdd-00e066414888
resourceVersion: "11801513"
selfLink: /api/v1/namespaces/kube-system/pods/calico-node-vb6gj
uid: cb0cce48-2d78-11e8-ad73-00e066414888
spec:
containers:
env:

name: ETCD_ENDPOINTS
valueFrom:
configMapKeyRef:
key: etcd_endpoints
name: calico-config
name: CALICO_NETWORKING_BACKEND
valueFrom:
configMapKeyRef:
key: calico_backend
name: calico-config
name: CLUSTER_TYPE
value: k8s,bgp
name: CALICO_DISABLE_FILE_LOGGING
value: "true"
name: CALICO_K8S_NODE_REF
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: spec.nodeName
name: FELIX_DEFAULTENDPOINTTOHOSTACTION
value: ACCEPT
name: CALICO_IPV4POOL_CIDR
value: <IP_ADDRESS>/16
name: CALICO_IPV4POOL_IPIP
value: cross-subnet
name: FELIX_IPV6SUPPORT
value: "false"
name: FELIX_LOGSEVERITYSCREEN
value: info
name: FELIX_IPINIPMTU
value: "1440"
name: ETCD_CA_CERT_FILE
valueFrom:
configMapKeyRef:
key: etcd_ca
name: calico-config
name: ETCD_KEY_FILE
valueFrom:
configMapKeyRef:
key: etcd_key
name: calico-config
name: ETCD_CERT_FILE
valueFrom:
configMapKeyRef:
key: etcd_cert
name: calico-config
name: IP
name: FELIX_HEALTHENABLED
value: "true"
image: quay.io/calico/node:master
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 6
httpGet:
path: /liveness
port: 9099
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: calico-node
readinessProbe:
failureThreshold: 3
httpGet:
path: /readiness
port: 9099
scheme: HTTP
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
resources:
requests:
cpu: 250m
securityContext:
privileged: true
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /lib/modules
name: lib-modules
readOnly: true
mountPath: /var/run/calico
name: var-run-calico
mountPath: /calico-secrets
name: etcd-certs
mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: calico-node-token-wncgc
readOnly: true

command:

/install-cni.sh
env:
name: CNI_CONF_NAME
value: 10-calico.conflist
name: ETCD_ENDPOINTS
valueFrom:
configMapKeyRef:
key: etcd_endpoints
name: calico-config
name: CNI_NETWORK_CONFIG
valueFrom:
configMapKeyRef:
key: cni_network_config
name: calico-config
image: quay.io/calico/cni:master
imagePullPolicy: IfNotPresent
name: install-cni
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /host/opt/cni/bin
name: cni-bin-dir
mountPath: /host/etc/cni/net.d
name: cni-net-dir
mountPath: /calico-secrets
name: etcd-certs
mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: calico-node-token-wncgc
readOnly: true
dnsPolicy: ClusterFirst
hostNetwork: true
nodeName: wx3
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: calico-node
serviceAccountName: calico-node
terminationGracePeriodSeconds: 0
tolerations:

effect: NoExecute
key: node.alpha.kubernetes.io/notReady
operator: Exists
effect: NoExecute
key: node.alpha.kubernetes.io/unreachable
operator: Exists
effect: NoSchedule
key: node.kubernetes.io/disk-pressure
operator: Exists
effect: NoSchedule
key: node.kubernetes.io/memory-pressure
operator: Exists
volumes:
hostPath:
path: /lib/modules
type: ""
name: lib-modules
hostPath:
path: /var/run/calico
type: ""
name: var-run-calico
hostPath:
path: /opt/cni/bin
type: ""
name: cni-bin-dir
hostPath:
path: /etc/cni/net.d
type: ""
name: cni-net-dir
name: etcd-certs
secret:
defaultMode: 420
secretName: calico-etcd-secrets
name: calico-node-token-wncgc
secret:
defaultMode: 420
secretName: calico-node-token-wncgc
status:
conditions:
lastProbeTime: null
lastTransitionTime: 2018-03-22T02:29:11Z
status: "True"
type: Initialized
lastProbeTime: null
lastTransitionTime: 2018-03-22T03:54:27Z
status: "True"
type: Ready
lastProbeTime: null
lastTransitionTime: 2018-03-22T02:30:03Z
status: "True"
type: PodScheduled
containerStatuses:
containerID: docker://241393942aa6815f708798d9c76fd476ad542f767eccc6294bcde612ca1c2301
image: quay.io/calico/node:master
imageID: docker-pullable://quay.io/calico/node@sha256:742875b3e0d16ddcff5eee80011dc43db4016d76cf2d4c9c4a9bacd72e87d012
lastState: {}
name: calico-node
ready: true
restartCount: 0
state:
running:
startedAt: 2018-03-22T03:53:45Z
containerID: docker://e3ea81d980f1eb1c00a4e868f177e263c995334938e7315ce74ba34a8afe7456
image: quay.io/calico/cni:master
imageID: docker-pullable://quay.io/calico/cni@sha256:9f30f6e2f81bd5757ee48ed64f1e7212fbc5c9098c112833932c4e15e9372d6f
lastState: {}
name: install-cni
ready: true
restartCount: 0
state:
running:
startedAt: 2018-03-22T03:54:23Z
hostIP: <IP_ADDRESS>
phase: Running
podIP: <IP_ADDRESS>
qosClass: Burstable
startTime: 2018-03-22T02:29:11Z`

If you take a look at the latest manifest https://docs.projectcalico.org/master/getting-started/kubernetes/installation/hosted/calico.yaml you'll see that there is a volume mount of /var/lib/calico.  You need to either add that mount to your manifest or switch to using the latest manifest.

Thanks @tmjd ,what 's the difference between master and laster?
in the DaemonSet, should i change master to a specific  version like v3.0.1 ?
i don't want to change the version when i add a new node even pass a long time

Sorry by latest I meant master.  The one I linked to https://docs.projectcalico.org/master/getting-started/kubernetes/installation/hosted/calico.yaml.  (You can look at the master docs by selecting 'nightly' in the Version drop down on the docs site.)
I would suggest you use one of the released manifests, it will have specific versions of the Calico components that have been tested together, if you are looking for a good and consistent experience with Calico.  The master versions are updated regularly and, as you have ran in to, the manifests could be mis-matched with the master container image versions.

what 's the difference between master and latest?

Just to clarify this - master is the latest build of the code from the master branch, and isn't guaranteed to be stable.
latest points to the latest stable release.
I'd still recommend pinning to a specific release to avoid pulling in unexpected changes.

i am getting a similar error when deploying a k8s cluster. Below are the kubelet log snippet:
E0518 09:33:50.990832   19864 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system(4c2a3a53-5a64-11e8-b577-daa39fff8710)" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ E0518 09:33:50.990858   19864 kuberuntime_manager.go:647] createPodSandbox for pod "kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system(4c2a3a53-5a64-11e8-b577-daa39fff8710)" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ E0518 09:33:50.990928   19864 pod_workers.go:186] Error syncing pod 4c2a3a53-5a64-11e8-b577-daa39fff8710 ("kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system(4c2a3a53-5a64-11e8-b577-daa39fff8710)"), skipping: failed to "CreatePodSandbox" for "kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system(4c2a3a53-5a64-11e8-b577-daa39fff8710)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system(4c2a3a53-5a64-11e8-b577-daa39fff8710)\" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod \"kube-dns-autoscaler-6966fd6fb6-29lqj_kube-system\" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/"
The daemonset calico-node has the /var/lib/calico volume and volumemount, which i can verify by exec-ing into the calico/node pod and reading the file /var/lib/calico/nodename
The images used for calico/node and calico/cni:
image: quay.io/calico/node:v3.1.0
image: quay.io/calico/cni:v3.1.0
Please let me know if I am missing anything.
Thanks.

@ggaurav10 do you see the /var/lib/calico/nodename file on the host filesystem?
Also, are you running a containerized kubelet by chance? If so, you'll also need to mount that directory into the kubelet container so that the CNI plugin can see it.

thanks for the response.
yes. i can see the file on the host, and yes, the kubelet is running in a container.
Mounting the directory in the kubelet container solved the issue. :)
Thanks again.

Doesn't this negate the point of CNI, ie should kubelet need to know about calico directories? This feels awkward, do we really need a mount to announce the node name to calico?

Whoever will be struggling with the same error and it's not always quick to upgrade kubelet config (add /var/lib/calico mount) on all clusters. There is a compatibility mode if calico nodename == hostname.
Add to configmap
"nodename_file_optional": true,

So final cni_network_config looks like that:
            cni_network_config: |-
              {
                "name": "k8s-pod-network",
                "cniVersion": "0.3.0",
                "plugins": [
                  {
                    "type": "calico",
                    "log_level": "info",
                    "etcd_endpoints": "__ETCD_ENDPOINTS__",
                    "etcd_key_file": "__ETCD_KEY_FILE__",
                    "etcd_cert_file": "__ETCD_CERT_FILE__",
                    "etcd_ca_cert_file": "__ETCD_CA_CERT_FILE__",
                    "mtu": __CNI_MTU__,
                    "nodename_file_optional": true,
                    "ipam": {
                        "type": "calico-ipam"
                    },
                    "policy": {
                        "type": "k8s"
                    },
                    "kubernetes": {
                        "kubeconfig": "__KUBECONFIG_FILEPATH__"
                    }
                  },
                  {
                    "type": "portmap",
                    "snat": true,
                    "capabilities": {"portMappings": true}
                  }
                ]
              }

@r7vme

it's not always quick to upgrade kubelet config (add /var/lib/calico mount)

Could you explain why that is needed in your case?  Is your kubelet being run with rkt or something like that (where it doesn't have full host filesystem access?  Lots of K8s deployments run the kubelet as a service I believe, and there would be no need for any kubelet config changes.

@r7vme
Facing same issue.
My calico.yml file is https://docs.projectcalico.org/v3.5/getting-started/kubernetes/installation/hosted/calico.yaml
Error
Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "b577ddbdd5fbd6cbe79e5b1bf20648e981590ecd0df545a0158ce909d9179096" network for pod "frontend-784f75ddb7-nbz7t": NetworkPlugin cni failed to set up pod "frontend-784f75ddb7-nbz7t_default" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
kubectl get pods --all-namespaces
NAMESPACE     NAME                                       READY   STATUS              RESTARTS   AGE
default       frontend-784f75ddb7-nbz7t                  0/1     ContainerCreating   0          91m
default       redis-master-97979696c-hcgdm               0/1     ContainerCreating   0          91m
default       redis-slave-6fd879d46c-klp4r               0/1     ContainerCreating   0          91m
default       ripple-app-dashboard-58d49bb867-wj44k      0/1     ContainerCreating   0          110m
kube-system   calico-etcd-b7wqf                          1/1     Running             0          143m
kube-system   calico-kube-controllers-74887d7bdf-wxhkd   1/1     Running             0          144m
kube-system   calico-node-58fqj                          1/1     Running             0          144m
kube-system   calico-node-mchcc                          0/1     CrashLoopBackOff    25         100m
kube-system   coredns-86c58d9df4-7ncdk                   1/1     Running             0          158m
kube-system   coredns-86c58d9df4-g4jcp                   1/1     Running             0          158m
kube-system   etcd-kmaster                               1/1     Running             0          157m
kube-system   kube-apiserver-kmaster                     1/1     Running             0          157m
kube-system   kube-controller-manager-kmaster            1/1     Running             0          157m
kube-system   kube-proxy-njx5c                           1/1     Running             0          137m
kube-system   kube-proxy-pkxx5                           1/1     Running             0          158m
kube-system   kube-scheduler-kmaster                     1/1     Running             0          157m
kube-system   kubernetes-dashboard-57df4db6b-zcvcc       1/1     Running             0          141m

Kubercates version
v1.13

I had a similar issue in Rancher RKE v1.17 and v1.19 clusters after provisioning more than 10 nodes to the cluster. The nodes failed with kubelete logs as below.
E0519 18:09:21.371236    5474 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
W0517 15:42:01.623240    5899 cni.go:239] Unable to update cni config: no networks found in /etc/cni/net.d

The canal CNI provisioner daemonset had resources defined for calico-node container
Containers:
   calico-node:
    Image:      rancher/calico-node:v3.13.0
    Port:       <none>
    Host Port:  <none>
    Requests:
      cpu:      250m

At a moment the pods started to fail or even failed to get scheduled on the newly launched nodes with events as below.
Events:
  Type     Reason        Age   From                  Message
  ----     ------        ----  ----                  -------
  Warning  FailedCreate  49m   daemonset-controller  Error creating: Pod "canal-vkzvr" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit
  Warning  FailedCreate  32m   daemonset-controller  Error creating: Pod "canal-m8wpv" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit
  Warning  FailedCreate  15m   daemonset-controller  Error creating: Pod "canal-zc974" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit
  Warning  FailedCreate  54s   daemonset-controller  Error creating: Pod "canal-dkc6j" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit
  Warning  FailedCreate  43s   daemonset-controller  Error creating: Pod "canal-lvb6z" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit

Where all the nodes had a minimum of 4vCPU provisioned.
This was a misleading event which was assuming vCPU limit less than the vCPU request 250m
To resolve this event, I explicitly added a vCPU limit to the same value 250m which immediately resolved the issue, canal pods got scheduled on the failing nodes, and nodes were up.


Publish actual code to NPM

Although (at least some) earlier versions published to NPM include the actual library, the latest (v1.1.2) doesn't appear to contain the library itself (no dist or src folders).  Can you please publish a new version which includes the code, so that npm i vh-check will result in a usable version being installed?

@pauln right away 😶

@pauln I've just tested it with a new install with this package.json & app.js
I've found nothing wrong.
In the node_modules folder I have:

package.json
{
  "name": "vh-test",
  "scripts": {
    "build": "webpack app.js --mode development"
  },
  "dependencies": {
    "vh-check": "^1.1.2"
  },
  "devDependencies": {
    "webpack": "^4.6.0",
    "webpack-cli": "^2.0.14"
  }
}

app.js
const vhCheck = require( 'vh-check' )

console.log( vhCheck() )

Hmm, something strange is going on here.  Initially, npm wasn't giving me the dist folder for version ^1.1.2 - but it appeared when I changed my dependency to 1.1.1 and re-ran npm i.  However, now it seems to be giving me the dist folder for ^1.1.2 as expected, even after clearing npm's cache...
Thanks for investigating, and sorry for wasting your time!


Implement Vertical Build for Android x64 Mono

This issue covers productization of the following vertical: Android x64 Mono

Build OS: Mariner
Target OS: Android
Build OS Arch: x64
Target Arch: x64
Stack Type: Short
Key Artifacts: Android x64 Mono Runtime Packs

Implementation of this vertical may depend on completion of other items within the Unified Build Space:

[ ] Link issues as necessary

When complete, the following will be true:

[ ] The vertical builds successfully and required changes are backported to individual repos.
[ ] The vertical's outputs are verified as being complete and correct as compared to the current .NET official build.
[ ] The vertical is enabled in VMR rolling CI and PR (if applicable).

T-Shirt Size: Small (default, update as necessary)

Merged.


Can i get WITH_CENTER model?

I looked at WITH_CENTER cfg, but couldn't find the model weight. Can you get the WITH_CENTER model?

Unfortunately, we do not have this model. WITH_CENTER is experimental code and we did not use it in our final model.


Error: found in requirements.yaml, but missing in charts/ directory: postgresql

WeChat User 郭晨鹏@中金云 encounter errors Error: found in requirements.yaml, but missing in charts/ directory: postgresql when using helm chart.

$ helm dependency update
$ helm init


Update phridge and is-absolute-url, and fix ESLint error.

phridge migrated off when.js promises onto native promises, so we need to wrap them in a couple places to support .spread(). This was guided by tests (basically, finding the entry points that go through getHTML), and I don't believe there should be any leakage of this change outside the UnCSS API.
is-absolute-url started treating '//somedomain.com/file.html' as not-absolute, which broke our tests. But arguably, the test was broken...if we pass a protocol-less URL in to UnCSS, there's no existing protocol that we should be accessing the protocol-relative URL against. (ie, should it be accessed over http or https? It's undefined...) So I deleted this test.

So, we just need a new test for protocol URLs?
/CC @giakki

My belief is that the existing test was flawed...we should not be supporting protocol relative URLs in the toplevel API at all, and so do not need a new test. If someone gives us a URL "//www.google.com/app.css", there is no way that we can fetch it, since we don't know through what port or protocol to request it.

@mikelambert: but things will work for protocol relative URLs, like before, or not?

Sorry, I don't really understand your question in the context of my
explanation. What is this "before" support that you want to keep working?
Is it a fear of losing functionality we theoretically once had
(functionally that I don't believe anyone in their right mind could have
actually used, but was just an artifact of an overzealous test case). Or is
there a concrete use case you believe we need to keep supporting, and if so
can you describe how someone would be using those protocol urls in html
urls without any protocol to be relative against?
2016年2月19日(金) 19:04 XhmikosR<EMAIL_ADDRESS>
@mikelambert https://github.com/mikelambert: but things will work for
protocol relative URLs, like before, or not?
—
Reply to this email directly or view it on GitHub
https://github.com/giakki/uncss/pull/218#issuecomment-186172866.

I might have misunderstood this issue. Anyway, feel free to merge.

@mikelambert: any chance that we switch to phantomjs-prebuilt?

Hmm, scratch that, it's actually phridge that references it.


Bug fix for short watchlist scraping

If a user's watchlist is 0 < n < 5, placeholder posters will be added to pad out the first 5. These placeholders break the scrape.

Small change, if a watchlist doesn't exist I'd argue the length should be 0, not None

If a user's watchlist is 0 < n < 5, placeholder posters will be added to pad out the first 5. These placeholders break the scrape.

Yes, you're right. Just changing this line is enough, edit the code then I'll merge it later.
# watchlist_items = section_watclist.find_all("li")
watchlist_items = section_watchlist.find_all("li", {"class": ["film-poster"]})

Small change, if a watchlist doesn't exist I'd argue the length should be 0, not None

Regarding defaulting to 0, it doesn't make sense to me to default to 0 for something that doesn't exist.

Yes, you're right. Just changing this line is enough, edit the code then I'll merge it later.

Good call. Fixed a typo in the above line, too. Much cleaner, thanks.

Small change, if a watchlist doesn't exist I'd argue the length should be 0, not None

Regarding defaulting to 0, it doesn't make sense to me to default to 0 for something that doesn't exist.

I'd argue the watchlist technically always exists, it's just empty. You can go to the watchlist page of a user you don't get a 404, it's a page with a header "{user} WANTS TO SEE 0 FILMS". And practically speaking, it seems more convenient for a length of a list to always be an int for comparisons.  I don't think there's a concept in letterboxd of a user with NO watchlist vs a user with 0 items in their watchlist that forces us to make the distinction by mixing types.
But I'll defer to you, I changed it back to None

I'd argue the watchlist technically always exists, it's just empty. You can go to the watchlist page of a user you don't get a 404, it's a page with a header "{user} WANTS TO SEE 0 FILMS". And practically speaking, it seems more convenient for a length of a list to always be an int for comparisons. I don't think there's a concept in letterboxd of a user with NO watchlist vs a user with 0 items in their watchlist that forces us to make the distinction by mixing types.

The section you mentioned only applies to HQ members. That's why I set it as None since HQ members don't have such a page.
For basic members, we can successfully retrieve the watchlist length. For example:
if "Watchlist" in link.text:

Here, we are searching for the text "Watchlist" in the navbar. If it's not found, the user is an HQ member; if it is found, they're a basic member. So, every member's profile must have this text.
Thank you for the changes.

Ah, that's a good point. Thanks!


remove ceph-iscsi-gw play from site.yml.sample

We ship ceph-iscsi-gw in a separate repo downstream and do not package
it with ceph-ansible. Including the play for ceph-iscsi-gw in
site.yml.sample makes the playbook fail when using the downstream
packages.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1454945
Signed-off-by: Andrew Schoen<EMAIL_ADDRESS>

Having this in the tree at all is a problem, until it is really functional :(


Validate users while role assignment and improve organization management authorization model

Purpose

$subject

Related Issues

https://github.com/wso2-extensions/identity-organization-management/issues/50
https://github.com/wso2-enterprise/identity-org-mgt-connector/issues/30


Initial API Spec Draft as OpenAPI 3 JSON

See #1
Here is a published version: https://app.swaggerhub.com/apis/prvd/Baseline/v1.0.0
A few notes:

We will ensure the default API gateway for poking around (baseline.provide.network) is functional by the time this PR is merged
The BRI-1 endpoint will be functional for local use as part of an upcoming PR against the baseline repo

Using Postman collection or Swagger isn't more user/document friendly instead of pcap?
Using DID standard would change the message data model?
Instead of UUID, can we use the hash of the object (e.g. message) itself?
What information are internal and what are external? What about the API calls? (Internal meaning my own stack where external can be seen by my partners/working group or even public)

@kthomas will review once the PR is fully ready for review

👍🏻 Soon and thank you.
On Thu, Apr 8, 2021 at 1:09 PM Andreas Freund @.***>
wrote:

@kthomas https://github.com/kthomas will review once the PR is fully
ready for review
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum-oasis/baseline-standard/pull/47#issuecomment-815992399,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABHL3L3OMHBELPGV2FVD73THXPMDANCNFSM42JIGHOQ
.

Using Postman collection or Swagger isn't more user/document friendly instead of pcap?
Using DID standard would change the message data model?
Instead of UUID, can we use the hash of the object (e.g. message) itself?
What information are internal and what are external? What about the API calls? (Internal meaning my own stack where external can be seen by my partners/working group or even public)

PCAP was just proof of life :)
Messaging model is still forthcoming, but won't change the model too much tbh... the way things are implemented looks very much like that standard already. We should consider joining the DIF to participate in the discussion. I think that could be a good bounty idea for someone... to be our rep at DIF for 3 months or something ;)
UUID is needed IMHO but perhaps you can be more specific about where you'd rather use a hash and we can consider.
Internal/external calls will be properly noted (will push again before Thursday to indicate this differentiation).
@mehranshakeri ^
cc: @Consianimis @Therecanbeonlyone1969

@kthomas regarding the UUID, if it's a unique identifier used internally (i.e. doesn't create inconsistency across different Baseline instances, e.g. not included in the message signature) then it doesn't matter for me. One can even assign an incremental uint.
But if this identifier is part of the message sent across different Baseline instances, then the hash of message content (hex string) could be the unique identifier. It will be unique since every message is unique (we can even add a random nonce) and it can be used as a consistency check on the received message. Even different Baseline instances can talk about the message hash and be pretty sure that they are talking about the same message content without having the content present (privacy, efficiency, addressable). We can use a simple hashing function like SHA3 as default.

@kthomas regarding the UUID, if it's a unique identifier used internally (i.e. doesn't create inconsistency across different Baseline instances, e.g. not included in the message signature) then it doesn't matter for me. One can even assign an incremental uint.
But if this identifier is part of the message sent across different Baseline instances, then the hash of message content (hex string) could be the unique identifier. It will be unique since every message is unique (we can even add a random nonce) and it can be used as a consistency check on the received message. Even different Baseline instances can talk about the message hash and be pretty sure that they are talking about the same message content without having the content present (privacy, efficiency, addressable). We can use a simple hashing function like SHA3 as default.

There is a UUID used externally, called the baseline_id.

API Review

POST /accounts

should return same schema as what is returned in GET /accounts?

PUT /networks/{id}

What is being updated about the network? Nothing in body?

/networks definition: peer-to-peer network? Should it specify "blockchain" network?

/connectors

Need more thorough definition of what a connector is. What functionality is it providing?
Are connectors required? If not, should we remove these from the core API spec?
credentials: should not passed as plain text in payload of request

/connectors/{id}/load_balancers

Who controls/configures the load_balancers?
Are load balancers required? If not, should we remove them from the core API spec?

What is the difference in functionality provided by the following routes?

POST /contracts/{id}/execute
POST /transactions

POST /business_objects

What is the purpose of the “type” field in the request body? Is there schema enforcement based on the “type”? Which “types” are supported?
If multiple parties are baselining the same object, does the “id” field recorded in each baseline system have to match?

/workgroups

In my opinion, workgroups should be an optional way to bundle workflows together. Workflows seem like the data object that should be required to be supported by the API spec

/oracles

This seems like an optional feature
Is this meant to support an on-chain data oracle such as Chainlink or off-chain or both?

POST /circuits

Does this allow the user to upload circuit source code? Or is a circuit automatically created based on the “identified” field in the request body? Which “identified” values are supported?
Shouldn't this respond with a circuitId so that we can check the state of any asynchronous activity initiated by this request?
Shouldn't there be a GET /circuits/{id} route so that we can poll for the state of an individual circuit?

POST /circuits/{id}/store/{index}

What is a “store value” in this context?

API Review
POST /accounts

should return same schema as what is returned in GET /accounts?

It does-- updated the docs to reflect

PUT /networks/{id}

What is being updated about the network? Nothing in body?

name, description, enabled, chain_id, config [] are all updatable in the request body

/networks definition:

peer-to-peer network? Should it specify "blockchain" network?

Blockchain is a subset of peer-to-peer networks.

/connectors

Need more thorough definition of what a connector is. What functionality is it providing?

Connects an SOR to the Baseline protocol

Are connectors required? If not, should we remove these from the core API spec?

They are required for SOR connectivity

####credentials:

should not passed as plain text in payload of request

Credentials are encrypted as a secret in a Vault

####/connectors/{id}/load_balancers

Who controls/configures the load_balancers?

implicitly configured and provisioned
-Are load balancers required? If not, should we remove them from the core API spec?
They are a suggested design pattern for production deployments but can likely be optional in the core spec

What is the difference in functionality provided by the following routes?

POST /contracts/{id}/execute
POST /transactions

The /contracts/{id}/execute method will validate input parameters against the smart contract ABI before the transaction is executed

####POST /business_objects

What is the purpose of the “type” field in the request body?

Corresponds to the domain model

Is there schema enforcement based on the “type”? Which “types” are supported?

Should be enforced by the SOR and the circuit (if using a non-generic circuit)

If multiple parties are baselining the same object, does the “id” field recorded in each baseline system have to match?

It is highly unlikely for the id field to match across SORs. See baseline_id

####/oracles

This seems like an optional feature
Is this meant to support an on-chain data oracle such as Chainlink or off-chain or both?

Both, but this could be optional in the core spec

####POST /circuits

Does this allow the user to upload circuit source code? Or is a circuit automatically created based on the “identified” field in the request body?

Arbitrary source code should be supported; the identifier field should support a growing library of general consistency circuits.

Which “identified” values are supported?

List of identifiers is up for discussion

Shouldn't this respond with a circuitId so that we can check the state of any asynchronous activity initiated by this request?

It responds with an id

Shouldn't there be a GET /circuits/{id} route so that we can poll for the state of an individual circuit?

There is one. Update docs to reflect.

####POST /circuits/{id}/store/{index}

What is a “store value” in this context?

The hash of the baseline proof at index leaf of the merkle tree.

@Therecanbeonlyone1969 lol this is epic.
@djones0 @zacparker41 👀

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: kthomas:x: djones0You have signed the CLA already but the status is still pending? Let us recheck it.


inputs onInvalid handler not working

Hey guys,
when using styled.input and then passing an onInvalid handler to the component this handler is never actually called.
Tried the same with onBlur, onKeyDown and these work.
Environment
System:

OS: macOS High Sierra 10.13.4
CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Free Memory: 263.92 MB
Total Memory: 16.00 GB
Shell: /bin/bash - 3.2.57

Binaries:

Node: 9.7.1
Yarn: 1.5.1
npm: 5.6.0
Watchman: Not Found

npmPackages:
styled-components:

wanted: ~3.2.1
installed: 3.2.3

Reproduction
Steps to reproduce

create styled input component like:

import styled from 'styled-components';

export const TextInput = styled.input`
  color: green;
`;

add onInvalid handler to component

<TextInput
     {...props}
      onInvalid={() => console.log('foo')}
      onBlur={() => console.log('bar')}
/>

render component to DOM
type in input field

Expected Behavior

foo and bar should be logged

Actual Behavior

see that only bar is logged

We don't do anything to your props and will almost always just pass them through (className & innerRef are exceptions) so this is 100% not a bug with styled-components. You could try to create a reproduction and submit it here, but it's more likely that you'll receive help on Stackoverflow or Spectrum, since this is not specific to styled-components.
I suspect that this is not an event on inputs with any type, so I'd suggest that you should check the input type and what the invalid event shape maybe.

@kitten are you sure? just had a look at
https://github.com/styled-components/styled-components/blob/master/src/utils/validAttr.js
and the regex is missing onInvalid.. but it has onBlur and onKeyDown

(Edit: wrong image ugh, was missing the second command)
Seems that you're right. Sorry, I made the assumption that the comment above matches the actual content there. Mind fixing this up for us please? Otherwise I'll try to fix it asap

@kitten great! I'll open a PR!
Glad we found it so fast!!
Thank you :)

https://github.com/styled-components/styled-components/pull/1668


Cannot connect to Azure Analysis Services with 2.16.7

Describe the bug
I cannot connect to an Azure Analysis Services Server when using 2.16.7 but I can for 2.16.6 / .5 / .4 ...
To Reproduce
Steps to reproduce the behavior:

download and do a fresh install of 2.16.6
use the servername from your resource to connect to database file->open-from db [asazure://centralus.asazure.windows.net/[myinstance]
select your azure authentication user in the OATH prompt
select databaase and life goes on as usual
download and do a fresh install of 2.16.7
repeat 2
spins forever (never gets to azure authentication)

Expected behavior
ability to connect to azure analysis services database
Observed behavior
Cannot connect to azure analysis service database
Application specifics

Tabular Editor 2.16.7
Semantic Engine used: Azure Analysis Services
Model Compatibility Level: 1500

Duplicate of #1002

Confirmed!!


Issue with connecting models of same class

Essentially trying to connect two nodes of the same type, as the first step in recommending users to follow through users currently followed. I'm running into this problem: isinstance() arg 2 must be a class, type, or tuple of classes and types.
Any advice for how I can build this functionality in neomodel or why i'm hitting this error would be great.
This is what the class looks like so far:
class NeoConnectProfile(StructuredNode):
user_id = IntegerProperty(required=False, unique_index=True)
company= StringProperty(required=False, index=True)
following = RelationshipTo('NeoConnectProfile', 'FOLLOW')
followers = RelationshipFrom('NeoConnectProfile', 'FOLLOW')
def follow_person(self, user_id):
    followed_user = self.index.get(user_id=user_id)
    self.follow.connect(followed_user)

def unfollow_person(self, user_id):
    followed_user = self.index.get(user_id=user_id)
    self.follow.disconnect(followed_user)

Hi @ahrennsiva, is there a reason why you don't want to just use:
ncp1.following.connect(ncp2)
and/or
ncp1.followers.connect(ncp2)
where ncp1 and ncp2 are two nodes of the NeoConnectProfile? This would achieve the same end state as your custom methods without needing to extend the Class.

You are also using index which is deprecated and has now been removed in master. If @the4thv doesn't solve your problem please re-open the ticket


[Analytics] Make app backgrounding trigger the end of a session

Analytics sessions should be closer to as expected

Fixes https://github.com/artsy/eigen/issues/1239

1 Warning

:warning:
Found unstubbbed networking requests

ARFairFavoritesNetworkModelSpec in test_ignores_artworks_without_a_partner
ARFairFavoritesNetworkModelSpec in test_ignores_artworks_without_a_partner
ARFairFavoritesNetworkModelSpec in test_ignores_artworks_without_a_partner

  Generated by :no_entry_sign: danger

Rocking :moyai:


Pshazz SSH agent does not work

I followed the steps in https://github.com/lukesampson/scoop/wiki/SSH-on-Windows but it doesn't work for me. I have the following apps installed (I also tried with openssh instead of git-with-openssh).
PS C:\Users\marcoent\Documents> scoop list
Installed apps:

  7zip 18.06
  coreutils 5.97.3 {32bit}
  curl 7.63.0
  dd 0.6beta3
  gcc 8.1.0 {32bit}
  git 2.20.1.windows.1
  git-with-openssh 2.20.1.windows.1
  grep 2.5.4
  mc 4.8.19 [extras]
  neovim 0.3.3
  openssh 7.6p1
  pshazz 0.2019.02.04
  sed 4.2.1

When I SSH into a server with ssh<EMAIL_ADDRESS>I am asked for the password of my private key and after entering it, I'm logged into the server. Excellent! However, once I log out and want to log back in, I have to enter the password of my private key again.
PS C:\Users\marcoent\Documents> ssh-add -l
Could not open a connection to your authentication agent.

So I expect the tutorial is missing some crucial bits between installing pshazz and everything magically working.

My $profile contained: try { $null = gcm pshazz -ea stop; pshazz init 'default' } catch { }. After changing the theme to something and back to the default, I got asked to enter my private key password. After entering it once, I was able to SSH into my server multiple times without entering the password.

The same problem in the latest pshazz installed by scoop in win11

Although following these steps, it remain fail to work.

My $profile contained: try { $null = gcm pshazz -ea stop; pshazz init 'default' } catch { }. After changing the theme to something and back to the default, I got asked to enter my private key password. After entering it once, I was able to SSH into my server multiple times without entering the password.

My $profile contained: try { $null = gcm pshazz -ea stop; pshazz init 'default' } catch { }. After changing the theme to something and back to the default, I got asked to enter my private key password. After entering it once, I was able to SSH into my server multiple times without entering the password.

@tommarcoen, could you clarify what you mean by "changing the theme"?

I changed jobs since three years ago and I haven't been using this software since so I am not sure what I meant or what I did in detail. I will try to install the software again and go through the steps once more to provide more details, should the issue manifest itself again.


Removed docker bridge configuration for agent overlay module on Master

Description:
Removed the configuration of the docker bridge on the agent overlay module on the Master. This reduces the dependency on the docker daemon for the Master. The docker bridge being configured was redundant, since there were no docker containers on the overlay on the Master.
Issues
DCOS-539
...
Checklist

[x] Included a test which will fail if code is reverted but test is not
[x] Followed relevant code rules Rules for Packages and Systemd

If this is a component/package update, include

[ ] Change Log from last:
[ ] Test Results:
[ ] Code Coverage:

@sargun can you review this?

:+1:

@cmaloney this should be ready to merge

@cmaloney

If the pr isn't WIP, please remove WIP from the PR title
My bad. Sorry about that.
Is it possible to test actually accessing something which is supposed to be running on the overlay actually works? That seems to be the bug being fixed here, but we don't test that directly.
This PR only changes the configuration for the overlay on the Master, hence the tests are checking configuration being reflected on the overlay-master and overlay-agent endpoints on the Master. I believe we have separate tests for checking the functional behavior of the overlay. These come to mind:
https://github.com/dcos/dcos/blob/master/packages/dcos-integration-test/extra/test_networking.py#L48
and
https://github.com/dcos/dcos/blob/master/packages/dcos-integration-test/extra/test_networking.py#L66

I get we're changing the config. I'm saying it would be nice to check that the functional result of changing that config (If I lock a docker on the master I should be able to access a container on the overlay network) actually works.

I agree, need a test to see if we if we launch docker container on the master it is able to access the overlay. But that test is not exactly going to test this configuration change. The configuration change removes the d-dcos bridge on the Master, which was never being used to start with.
We can add the test case in a separate patch.

@cmaloney can you this another look.

Wasn't aware that you could do dictionary comparisons by excluding keys.
Atleast without iterating through the keys. Is that what you were
suggesting?
On Thu, Dec 1, 2016 at 2:19 PM, Cody Maloney<EMAIL_ADDRESS>wrote:

@cmaloney commented on this pull request.
In packages/dcos-integration-test/extra/test_endpoints.py
https://github.com/dcos/dcos/pull/983:

assert json['network'] == dcos_overlay_network

+def test_if_overlay_master_agent_is_up(cluster):

r = cluster.get('/mesos/overlay-agent/overlay')
assert r.ok, "status_code: {}, content: {}".format(r.status_code, r.content)

Make sure the dcos overlay has been configured.

json = r.json()
dcos_overlay = {

   'name': 'dcos',

   'subnet': '<IP_ADDRESS>/8',

   'prefix': 24

}

assert 'overlays' in json

how is it non-deterministic? Shouldn't we still be able to do something
like pull out that one chunk, then check it has the right structure, as
well as then just do the big dictionary comparison for the rest excluding
that one key?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dcos/dcos/pull/983, or mute the thread
https://github.com/notifications/unsubscribe-auth/AC-9mlgR4i43Lfxx-vpVeHcs_JZOU5OSks5rD0fugaJpZM4K5xdV
.

--
Avinash Sridharan, Mesosphere
+1<PHONE_NUMBER>

@cmaloney made the changes you had suggested. Can you give another pass? Thanks !!

@asridharan / @sargun
I see that upgrade Integration tests have been failing since this PR was introduced.

Teamcity first failure link

>       assert json['overlays'] == dcos_overlay_network
E       assert [{'docker_bri...'STATUS_OK'}}] == [{'info': {'na...'STATUS_OK'}}]
E         At index 0 diff: {'state': {'status': 'STATUS_OK'}, 'docker_bridge': {'ip': '<IP_ADDRESS>/25', 'name': 'd-dcos'}, 'info': {'subnet': '<IP_ADDRESS>/8', 'name': 'dcos', 'prefix': 24}} != {'state': {'status': 'STATUS_OK'}, 'info': {'subnet': '<IP_ADDRESS>/8', 'name': 'dcos', 'prefix': 24}}
E         Full diff:
E         - [{'docker_bridge': {'ip': '<IP_ADDRESS>/25', 'name': 'd-dcos'},
E         -   'info': {'name': 'dcos', 'prefix': 24, 'subnet': '<IP_ADDRESS>/8'},
E         ? ^^
E         + [{'info': {'name': 'dcos', 'prefix': 24, 'subnet': '<IP_ADDRESS>/8'},
E         ? ^^
E         'state': {'status': 'STATUS_OK'}}]

Note that the output has docker_bridge information from agent.
The gen-config.yaml for the agent.json has the docker-bridge mode to true.
  - path: /etc/overlay/config/agent.json
    content: |
      {
        "cni_dir":"/opt/mesosphere/etc/dcos/network/cni",
        "network_config":
        {
          "allocate_subnet": true,
          "mesos_bridge": true,
          "docker_bridge": true,
          "overlay_mtu": {{ dcos_overlay_mtu }}
        },
        "max_configuration_attempts": {{ dcos_overlay_config_attempts }}
       }

Either the test needs to fix or the overlay/config needs to change (if that was unexpected).


C++: IR translation for binary conditional operator

IR generation was not handling the special two-operand flavor of the ?: operator that GCC supports as an extension. The extractor doesn't quite give us enough information to do this correctly (see github/codeql-c-extractor-team#67), but we can get pretty close.
About half of the code could be shared between the two-operand and three-operand flavors. The main differences for the two-operand flavor are:

The "then" operand isn't a child of the ConditionalExpr. Instead, we just reuse the original value of the "condition" operand, skipping any implicit cast to bool (see comment for rationale).
For the three-operand flavor, we generate the condition as control flow rather than the computation of a bool value, to avoid creating unnecessarily complicated branching. For the two-operand version, we just compute the value, since we have to reuse that value in the "then" branch anyway.

I've added IR tests for these new cases. I've also updated the expectations for SignAnalysis.ql based on the fix. @rdmarsh2, can you please double-check that these diffs look correct? I believe they do, but you're the range/sign analysis expert.

The sign analysis results are either improvements or cases where it was previously right for the wrong reasons. We don't run the range analysis on the same set of tests, so I'm not sure if there's regressions there. I'll check that and then do a proper code review.


sample size in mafCompare

Hello,
Thanks for your contribution to this package. I have been thinking about a problem when using mafCompare. MafCompare is to calculate the number of mutated genes in two MAFs, and then identify the differentially mutated genes based on Fisher's exact test, whether the sample size of two groups will have an impact on the results. Recently, when comparing the differentially mutated genes in the high and low immune groups, the sample size ratio of the two groups was 3:1, and some problems were found in the results.
Therefore, is there a regulation on the sample size? For example, the sample size of the two groups is not significantly different.
Looking forward to your reply. Thank you.

Hi,
AFAIK, it should not affect much.
You could also try the chi-square test (if your sample size is large enough).

Hi,
AFAIK, it should not affect much.
You could also try the chi-square test (if your sample size is large enough).

Hi,
AFAIK, it should not affect much.
You could also try the chi-square test (if your sample size is large enough).

OK! thank you very much

Hi,
AFAIK, it should not affect much.
You could also try the chi-square test (if your sample size is large enough).


Clear cell output for empty cell in Notebook Editor

Steps to cause the bug to occur

Enter anything inside cell, like constant 123, and run cell - it will show "123" in output
Clear all text in cell input, so it is empty now, and again run cell - it will NOT clear old "123" output

Expected behavior

as in JupyterLab, expected behavior is that output will empty if you run empty input cell
above bug prevent clearing old output from cells - only workaround currently is 'delete cell', and insert again new cell

@gmnenad I am able to repro this

Thanks for the feedback! However, we don't have plans on fixing this at this time. @gmnenad, if this is more problematic for you than we're thinking, please reopen.


Inspecting the interface (3)

Open devtools and set it up for modding.
Should this guide contain any code or not?
Should there be a CSS version and a JS version?
Do you want to help make this guide?
File: creating-mods/devtools.md

Open devtools

That could be separate, depending on how long it would get.

Should this guide contain any code or not?

Just what’s needed to show the important features.

Should there be a CSS version and a JS version?

Those could be naturally separated under headings.

This is now the big one that needs to be done, so that we can start working on FIrst CSS mod and First JS mod.
Maybe we could merge in a "draft version"?

Or maybe we should just add this link for now - is that alright?
https://forum.vivaldi.net/topic/16684/inspecting-the-vivaldi-ui-with-devtools?page=1

I don’t think we should skip such important guides & put in links instead of them.

Ok.

I don’t think we should skip such important guides & put in links instead of them.

I do question how much value we can provide by essentially saying the same things. I think the value in this guide is going to come in when we write the next guides that will go beyond the pinned topics on the forum. What about asking luetage if we can copy some or all of that post (giving credit to him as the author of course), and then working from there?

Ehh, why not. Would you mind, @luetage?

I can make a pull request for it myself when the time comes.

@luetage Thanks! The time has come, like, now. But if you’re busy, that’s fine.

I'm on mobile right now and have to do VFM stuff anyway. I don't think that's too pressing atm, since its available to the community.
30 May 2021 12:53:56 code3z @.***>:

@luetage[https://github.com/luetage] Thanks! The time has come, like, now. But if you’re busy, that’s fine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub[https://github.com/tiosgz/modding-vivaldi/issues/9#issuecomment-850979839], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ADKXC6KI6YX2EJCUEYKCZY3TQIKMDANCNFSM45FLTUGA].
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEgAAABICAYAAABV7bNHAAAABHNCSVQICAgIfAhkiAAAACtJREFUeJztwQENAAAAwqD3T20ON6AAAAAAAAAAAAAAAAAAAAAAAAAAAD4MUUgAARy2AfAAAAAASUVORK5CYII=###24x24:true###][Tracking image][https://github.com/notifications/beacon/ADKXC6JEJX3CW2TEEKFPNB3TQIKMDA5CNFSM45FLTUGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGK4OX7Y.gif]

Yeah, no worries.
Since it’s available we can make the next guides assuming that the user knows everything in the post, but no more.

Sorry for accidentally closing this.
Assign luetage?


[FLOC-2576] Skip conch tests in Flocker 1.0.1

Back-porting fix to 1.0.1 to allow tests for other patches to pass.

Approved, pending passing tests.


Spec.Timeout Behaviour

As per v1beta2, the Spec.Timeout documentation states:

.spec.timeout is an optional field to specify a timeout for Git operations like cloning.

With the introduction of GitOptimizedClones, Git clones are a lot faster when a no-op clone is identified. However, the process is split into two: the first part attempts an optimised clone, and in specific types of failures it goes on to try a full non-optimised clone.
In the worse case scenario (slow network or blocking Git server) a reconciliation that requires both operations, may now take twice as long to timeout during clones, given that the timeout is being reset before each operation.
Potential ways we could approach this:

Update documentation to highlight scenarios where timeout may not be honoured, exposing to the users the implementation details of the new no-op process.
Enforce the Timeout considering the entire source fetching process, abstracting away to the user that two operations may take place. In total the reconciling process won't spend more than X time trying to clone the repository - as per before GitOptimizedClones.
Agree that this is a non-issue and requires no changes.

Also keen to hear other ideas.
cc: @stefanprodan @hiddeco.

Ideally the timeout context should flow from one operation to another, so that a reconciliation would exit after the specified timeout no matter the number of internal operations.

Ideally the timeout context should flow from one operation to another, so that a reconciliation would exit after the specified timeout no matter the number of internal operations.

Can you elaborate on what makes you think this? Because I can only see this being extremely painful to a user, due to a variety of things:

It is hard to know the precise steps the reconciler process is going to take, and thus hard to get a stable median.
If we add steps to the process in the future, any old timeouts have to be updated to allow more room for the overall operation.
What if the timeout expires between e.g. a Git operation and the production of the Artifact? I would now expect this to cancel the whole reconcile operation, which is an expensive and intrusive action post-clone.

Great points @hiddeco. Thanks for putting thought into this. The main benefit I as a consumer would see in treating the field value as an aggregated timeout is that you most likely want to tweak it from an end-to-end perspective, from creation of the resource until it gets ready. This is also the semantics that HelmRelease and Kustomization ship, right?
However, I understand that this makes our implementation kind of hard to change in the sense that you raised: adding a remote operation might force users into tweaking their timeouts again.
🤔

If you look at e.g. a HelmRelease, it has a global .spec.timeout configuration which is used as a per-action base. Which can then be further fine-tuned for individual Helm actions (e.g. install or upgrade) using .spec.<action>.timeout. This provides the user with specific control over actions they can measure themselves (using e.g. helm from within a cluster container).

What if the timeout expires between e.g. a Git operation and the production of the Artifact? I would now expect this to cancel the whole reconcile operation, which is an expensive and intrusive action post-clone.

Fair point, Ok let's leave it as it is with the timeout per-operation basis.

The maintainers voted on this issue with the following outcome:
.spec.timeout in GitRepositorys is interpreted on a per-operation basis, i.e. each operation conducted during reconciliation of a resource (such as a Git clone) has that amount of time to finish.


Update vendored version of github.com/digitalocean/godo

This pulls in the fix from https://github.com/digitalocean/godo/pull/157
That resolves an issue where DigitalOcean volumes were not being
properly filtered by region. I noticed this when using the
the rexray/dobs Docker plugin.

@akutz - this looks like all issues were addressed. merging!


Upgrade of User Profile Service Application is missing

The overview page (https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/overview-of-the-services-upgrade-process-2019) seems to indicate that this page should include the User Profile Service app upgrade steps. There are 2 mentions of User Profile on this page but seem to be mistakes in the Performance Point section.

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

ID: 97493854-efe6-3451-d96b-a04b6ac32075
Version Independent ID: 46b84a4a-fbe2-5afc-f442-13d8411e395e
Content: Upgrade service applications to SharePoint Server 2019
Content Source: SharePoint/SharePointServer/upgrade-and-update/upgrade-service-applications-to-sharepoint-server-2019.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: kirks

@DennisGoss Thank you for submitting this feedback.
From our understanding the issue has been resolved. If you feel it hasn't been resolved please re-open this issue.

@officedocsbot close


Expose XOnlyPublicKey in crate root

It was previously exposed in 0.29.0 and we removed it in 0.30

IIRC @tcharding had some reason not to? I didn't think much about this one...

I'm easy. We can go ahead and put it back, along with these sighash types. I think we just thought it was too obscure.

IME public keys are way less obscure than sighash types.

I was working under the idea that we decided on before, and documented in the release blog post, that "types exported at the crate root should be in the Bitcoin vernacular". Amusingly the XOnlyPublicKey was the exact type I used in the example in the blog post :)
I.e. "bitcoin pubkey" is in the vernacular but "bitcoin x-only pubkey" is not, or so I claimed, am I wrong?
One counter-argument is that having to
use bitcoin::key::XOnlyPulbliKey;
use bitcoin::PublicKey

Is un-ergonamic.
Counter-argument to the counter-argument, one still has to go into the key module to get all the other taproot key types so why is only the XOnlyPublicKey exported?

bitcoin::PublicKey should really be called LegacyPublicKey. And, as the name suggests, it probably shouldn't be used much anymore, so if we're not re-exporting XOnlyPublicKey I'd prefer to not export legacy stuff either.
It also looks a bit odd that bitcoin::PublicKey isn't the same as secp256k1::PublicKey but bitcoin::XOnlyPublicKey is the same as secp256k1::XOnlyPublicKey. I know exactly why and it's not wrong, just odd. I was trying to find if there's any reason to newtype it but couldn't. So if anyone knows of any that'd be helpful.

So, the reason bitcoin::PublicKey is exported under that name is exactly that it needs to be distinguishable from secp256k1::PublicKey. If we remove the re-export (which I agree with the logic of; we shouldn't be treating it as preferable to XOnlyPublicKey) then we should rename the type to BitcoinPublicKey.
As for newtyping secp256k1::XOnlyPublicKey ... I don't think we should do that. It's extremely annoying having distinct types in rust-bitcoin and rust-secp for legacy pubkeys, because as soon as you need a compressedness flag you have to virally change all your secp pubkeys to bitcoin ones, and then stick .key onto basically every access where you actually just want the pubkey. It is a big benefit of xonly public keys that the keys are just keys.

I'm acking this but FTR I'm not exactly sure what we are exporting at the crate root and what we are not. Also reading the discussion above about bitcoin::PublicKey I can't figure out if there is anything actionable in it?

I'm acking this but FTR I'm not exactly sure what we are exporting at the crate root and what we are not. Also reading the discussion above about bitcoin::PublicKey I can't figure out if there is anything actionable in it?

Adding verify method to it which simply forwards to secp256k1.

There are two main ways for organizing types in root. 1) Ergomics, 2) Bitcoin vernacular.
I think we can do both. We should definitely have all the bitcoin vernacular types exported, but also many of common types according to (1) Ergonomics.

I don't feel strongly enough about this. So, I am also okay with the way it is being done currently. But still would mildly prefer an export.

I think there is a bunch of work still to be done on the crate level re-exports so we have time to discuss this. I'm pretty sure we aren't going to get it right first time but surely in the next couple of releases we can get this locked.

Needs rebase please.

Rebased

Needs cargo +nightly fmt bro


Add kickoff, complete and describe_collect on StandardDetector

This requires moving the existing logic of kickoff/complete and describe_collect from the flyer to the StandardDetector.
This is part of a general work to disassemble the flyer object to purely hold logic triggers for underlying detectors, such that the stream resource/datum documents produced from a fly scan do not eject data about the flyer itself. See the project page readme for more details.

Closed with #116


Support for on-premise instance for edit link

Edit link only supports SaaS instance (gitlab.com, github.com, bitbucket.org). github and gitlab (I don't know for bitbucket) allow on-premise instance, with custom urls.
Can we add a source_provider optional setting, with allowed values github|gitlab|bitbucket that override edit link building behavior and allow to use edit link with on-premise instance. If source_provider is missing, we can use startswith check to automatically handle gitlab.com/github.com/bitbucket.org cases.
I step into this issue as I use furo theme, and configuring edit link feature triggers Could not understand "source_repository" provided messages, and edit link is generated with an empty href.

Merged that one, I'll cut a release and enable this in Furo sometime later in the week.


[DiagnosticVerifier] Add a -verify-tag frontend option to the verifier

If -verify-tag=TAG is passed when the diagnostic verifier is enabled,
it will only look for expected diagnostics of the form
expected{error|warning|note|remark}(TAG). This is similar to -check-prefix
in FileCheck, and makes it easier to invoke the verifier multiple times
per test.
I updated a couple of tests which benefited from this, but haven't come up with a systematic way to find them. I have a few use cases in mind for the future though as diagnostics get more configurable.

closing in favor of https://github.com/apple/swift/pull/6980, I prefer that approach


Fix issue where cell columns can't be read

Codecov Report

Merging #142 (bdd46a3) into dev (1a2e78c) will increase coverage by 1.19%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #142      +/-   ##
==========================================
+ Coverage   83.26%   84.46%   +1.19%
==========================================
  Files          46       45       -1
  Lines        2833     2793      -40
  Branches      487      487
==========================================
  Hits         2359     2359
+ Misses        370      334      -36
+ Partials      104      100       -4

Flag
Coverage Δ

unittests
84.46% <100.00%> (+1.19%)
:arrow_up:

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

Impacted Files
Coverage Δ

meerkat/mixins/io.py
100.00% <ø> (+22.41%)
:arrow_up:

meerkat/cells/abstract.py
77.77% <100.00%> (-1.54%)
:arrow_down:

meerkat/columns/abstract.py
84.81% <0.00%> (+1.04%)
:arrow_up:

meerkat/columns/numpy_column.py
89.52% <0.00%> (+1.90%)
:arrow_up:

meerkat/columns/cell_column.py
93.47% <0.00%> (+23.91%)
:arrow_up:

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 1a2e78c...bdd46a3. Read the comment docs.


Make it better to type into Tweak Milestones date fields

cruise tn406 -> lowering   1438 -> replay
system admin-> lowerings -> 1438 -> edit -> milestones and stats -> tweak milestones (they don't like the arrows)
ALSO everytime you edit the milestones it gets duplicated

Resolved May 30, 2023 at 1:11 PM by @figuernd


404 for search notebook

Got a error box when I clicked on the left side link labeled "search"

https://github.com/AllenDowney/DSIRP/blob/main/notebooks/search2.ipynb returns 404

I had to do some renaming, so it is now searching.ipynb.
Links to it should be updated now, but might take time to get cleared from caches.
Thanks for letting me know!


chore: adds the log file to IOStream configuration for Out and ErrOut

This change ensures logs from oc library calls make it
into the logfile as well as standard out.
Signed-off-by: Jennifer Power<EMAIL_ADDRESS>Description
This PR adds the oc-mirror log file as an output destination when calling oc libraries.
Fixes #22
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

[x] Manually tested

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

/lgtm


ModuleNotFoundError: No module named 'sed_vis.util'

Hi! After successful installation in a python 3.6 environment on Ubuntu 20.04 LTS, visualizers/sed_visualizer.py returns:
Traceback (most recent call last):   File "visualizers/sed_visualizer.py", line 10, in <module>     import sed_vis   File "<frozen zipimport>", line 259, in load_module   File "/home/galvo/.virtualenvs/py36/lib/python3.8/site-packages/sed_vis-0.1.2-py3.8.egg/sed_vis/__init__.py", line 5, in <module>   File "<frozen zipimport>", line 259, in load_module   File "/home/galvo/.virtualenvs/py36/lib/python3.8/site-packages/sed_vis-0.1.2-py3.8.egg/sed_vis/visualization.py", line 21, in <module> ModuleNotFoundError: No module named 'sed_vis.util'
Any hints? Thanks.

Did you get an answer for this?

Fixed it pretty easily you need to add the following lines to sed_vis/sed_vis.egg-info/SOURCES.txt
sed_vis/util/__init__.py
sed_vis/util/audio_player.py

Hi. I'm getting this same error. Can you provide the solution?

How did you install the sed_vis? Did you use the command pip install -e sed_vis?