Read image author from label 'maintainer' if author is null

Coverage decreased (-0.02%) to 56.181% when pulling 745d83e393028517c28961037feddedf33ccc39a on ywk253100:171214_author into 0abd30f9f4dd9f8f98e61dc6d658a9289a12f504 on vmware:master.

Checked the code, I think we can split a func and add UT?

Coverage increased (+1.3%) to 57.497% when pulling d9b0f54c5ead1cb80e0867629b0472428cf98a83 on ywk253100:171214_author into 0abd30f9f4dd9f8f98e61dc6d658a9289a12f504 on vmware:master.


wrong polyfill with IE11 ?

Configuration:

Web browser and its version: IE11
Operating system and its version: Windows 7
PDF.js version: not sure, but probably >= 2.0.0
Is a browser extension: no

Steps to reproduce the problem:

open https://mozilla.github.io/pdf.js/web/viewer.html
try to use Array.prototype.includes()

What is the expected behavior? (add screenshot)
[1,2].includes(1) should return true, not false

fwiw, the polyfill comes from core-js library

@yurydelendik unless I completely misunderstood something, according to the core-js author the fault is not in his polyfill:
https://github.com/babel/babel/issues/7419
(please look the last comment on that issue)


Version check in DownloadAllFiles will fail past 3.9

The version check in DownloadWindow::DownloadAllFiles uses _stricmp and will sort 3.10 as lower than 3.9

Never mind


Adding some additional programs

@yesnet0 - thanks for the approval, how do I actually merge them in?


Untracable design decision in System Context

In 3.1 System Context - Bridge Corrosion Responsibilities:

Build a database storing the chloride exposure data for every 25 km over time.

Where is the 25 km coming from? It is not mentioned anywhere else in the document. Is it because of the source dataset or is it a requirement made by someone (the research team? MTO?), or system limitations?. Please provide some justification so that it does not sound like an arbitrary design decision.

Add scope decision to explain the 25km is from the limit of the climate data model.


Jaclu unused files cleanup

Cleanup of some long since commented out or otherwise disabled stuff

Looks good, merging.  Thank you!


Create eventbrite for Oct 10 HQ Workshop

https://www.eventbrite.com/e/technology-customer-value-workshop-tickets-38549530684


Fix progress messages in Calva

The helper to generate progress messages was incorrectly using the :title key in :report messages. That key should only be used with :begin messages. This changes the helper to generate valid progress messages.
After lsp4clj is bumped in clojure-lsp, Calva will show progress messages during startup. Emacs was showing progress messages before this fix, so it must observe the non-standard :title key.
I've also noticed that Calva doesn't show percentages in its UI. So, as a future enhancement to clojure-lsp, we may want to embed percentages in the messages themselves "36%", or perhaps add something like "file 26/235".

Oh, that's awesome, I will test that.
I thought that calva issue was because of this and this, didn't know we could fix only via that way

Works great! thanks

About the percentage, I'd like to avoid changing the message since will affect other clients (unless we add a flag just for calva wichi is kind of meh), maybe we could debug calva vscode-language-server-node to understand why the percentage is not showing

maybe we could debug calva vscode-language-server-node to understand why the percentage is not showing

Did some research... users have to choose to see the percentage. VS Code omits the percentage from the "window" progress area (the lower left), as part of a feature it calls "silent" notifications. It will show the progress message with the percentage in the "notification center", if it's open. There are several ways to open the notification center, by clicking on the progress messages, by clicking on the bell icon in the lower right, or by executing Notifications: Show Notifications.

Got it, thanks @mainej maybe worth mentioning that in calva docs or tell to calva maintainers? It seems something that some users may like


Update limits basing on Tezos updates [TE-422, TE-405]

Limits are updated according to Tezos code
Encoded data generator is added to test limits
Now there is the PeerMessageResponse.message that contains exactly one specific message

@bkontur Please take a look at the HISTORY_MAX_SIZE. It is 200 despite that CURRENT_BRANCH_HISTORY_MAX_LENGTH is now 1000. Should that also be updated?
This addresses following Jiras:
TE-422, TE-405, TE-407

@akoptelov last change looks good, but something happened with the drone run and it failed.

Looks good to me.
@bkontur @akoptelov I'm thinking that I may be worth it to have a small OCaml program that just prints the values of all limits to easily detect when something changes. Probably as part of the idea I mentioned some time ago about using OCaml's PPX to produce parseable definitions of the encodings. I'm still dealing with storage integration related stuff, but it is something I can look into doing once I'm free from other things.


Rename handler API ExtractClaims to ExtractClaimsAndReferenceIDs

In order for clarity and consistency, API to extract claims and reference ID should renamed fromL ExtractClaims() to:
ExtractClaimsAndReferenceIDs()
Originally posted by @yogeshbdeshpande in https://github.com/veraison/services/pull/211#discussion_r1526631802

This issue is no longer applicable, as it is addressed using https://github.com/veraison/services/pull/216


Minor: examples/Async_ESP32_FSWebServer/ wrongly uses FileFS.begin(true)

(please also see https://github.com/lorol/LITTLEFS/issues/27 for more context)
I'm using your library and your examples as a starting point for my project. Thanks for sharing this!
I noticed that the following code
// Format SPIFFS if not yet
  if (!FileFS.begin(true))
  {
    Serial.print(FS_Name);
    Serial.println(F(" failed! AutoFormatting."));
  }

seems to assume that FileFS.begin(true) returns false if the SPIFFS was un-initialized and needed to be formatted. In reality that call returns true if the mount has been successful, even if that required an auto-format, false only when the mount fails for whatever reason.
If the debug output is enabled, the LittleFS library debug messages overwrite any debug print from the Arduino thread, causing additional comprehension problems
If the call FileFS.begin(true) fails, that means that there is no SPIFFS, and your example should abort
The above applies to all your examples using SPIFFS for ESP32

Thanks for identifying the misleading message in the examples. It happened because time spent in them were so small, and not considered so serious.
I have been aware of this minor issue and knew it's better to have something like the following code, such as in BlynkSimpleEsp32_WM.h#L1510-L1520 or BlynkSimpleEsp8266_WM.h#L1467-L1480
I won't let it slipping this time and will fix it in next release.

For ESP32

     // Format SPIFFS if not yet
      if (!FileFS.begin(true))
      {
        Serial.println(F("SPIFFS/LittleFS failed! Already tried formatting."));

        if (!FileFS.begin())
        {
          Serial.println(F("SPIFFS/LittleFS failed! Pls use EEPROM."));
          return false;
        }
      }

For ESP8266

      if (!FileFS.begin())
      {
        FileFS.format();

        if (!FileFS.begin())
        {
#if USE_LITTLEFS
          Serial.println(F("LittleFS failed!. Please use SPIFFS or EEPROM."));
#else
          Serial.println(F("SPIFFS failed!. Please use LittleFS or EEPROM."));
#endif
          return false;
        }
      }

Combined, to be in new release

  // Format FileFS if not yet
#ifdef ESP32
  if (!FileFS.begin(true))
#else
  if (!FileFS.begin())
#endif
  {
#ifdef ESP8266
    FileFS.format();
#endif

    Serial.println(F("SPIFFS/LittleFS failed! Already tried formatting."));

    if (!FileFS.begin())
    {
#if USE_LITTLEFS
      Serial.println(F("LittleFS failed!. Please use SPIFFS or EEPROM. Stay forever"));
#else
      Serial.println(F("SPIFFS failed!. Please use LittleFS or EEPROM. Stay forever"));
#endif

      while (true)
      {
        delay(1);
      }
    }
  }

I know it's not really a meaningful contribution, but I'm glad to have been of help :)
Your new code looks great to me. I cannot thank you enough for contributing this library and the examples. It really helped me a lot, and I learned a lot just following the examples
Just keep in mind that, if using LittleFS at least, the debug messages from LittleFS will preempt your Serial.print() and the user won't see a debug message, just the code hanging. If you do something like the code below, on the other hand, the error message will be correctly displayed. Truly minor, but it took me a bit to figure out what was happening, and remembering that all ESP32 code is dual thread, unlike other Arduino platforms
  // Format FileFS if not yet
#ifdef ESP32
  if (!FileFS.begin(true))
#else
  if (!FileFS.begin())
#endif
  {
#ifdef ESP8266
    FileFS.format();
#endif

    Serial.println(F("SPIFFS/LittleFS failed! Already tried formatting."));

    if (!FileFS.begin())
    {
       delay(100); // prevents debug info from the library to hide err message. The code stops anyway, so a delay is not an issue
#if USE_LITTLEFS
      Serial.println(F("LittleFS failed!. Please use SPIFFS or EEPROM. Stay forever"));
#else
      Serial.println(F("SPIFFS failed!. Please use LittleFS or EEPROM. Stay forever"));
#endif

      while (true)
      {
        delay(1);
      }
    }
  }

That's great. I'll certainly use it and have some not about your contribution.
Regards,

The new ESPAsync_WiFiManager Release v1.6.2 has been published, with a note to thank you at Contributions and Thanks

Releases v1.6.2

Fix example misleading messages. Check Minor: examples/Async_ESP32_FSWebServer/ wrongly uses FileFS.begin(true) #47


[WIP] remote_billing: Implement confirmation flow for legacy servers.

Still WIP

[ ] For the last form (with Full Name and ToS consent field), this pretty
shamelessly re-uses and directly renders the
corporate/remote_realm_billing_finalize_login_confirmation.html
template. That's probably good in terms of re-use, but calls for a
clean-up commit that will generalize the name of this template and the
classes/ids in the HTML.
[ ] Tests for the flow are broken of course and still need to be refactored and updated for this much longer flow.
[ ] The new pages aren't styled at all, though I imagine we may do this like in the previous cases, a follow-up PR

Here's a screencast, showing that also the next_page mechanism work. I try to access /sponsorship unauthed, and get redirected to complete full auth flow before being granted access:
Screencast from 2023-12-08 20-29-02.webm

This look great; I posted a handful of minor comments but I think if we had a version of this with completed tests, it'd otherwise be ready to merge and proceed with the RemoteRealm variant changes.

I resolved what I could and responded to a couple of things. Tests have been added for the important stuff. So possibly we can merge?
I'd propose leaving cleaning up that "shamelessly re-used" template to be done in my next PR adding the confirmation flow to the RemoteRealm flow - since it'll deal and modify that template directly, so it'll be easier for me to know how exactly to generalize it when I'm doing that.

This seems like a great checkpoint to merge, thanks for all the work on this @mateuszmandera!
I made the one change noted in https://github.com/zulip/zulip/pull/28100#discussion_r1421301060.


Security Suggestion: storing API Key not in clear text has it is in data.json

Your plugin is simply wonderful and very useful to daily
While; it would be remarkable to not have the API key in clear text stored in the data.json
Would you be able to fix that, please?
https://forum.obsidian.md/t/store-secrets-like-api-key-outside-of-data-json/56035

Hey,
Thanks for your nice words about our Text Generator plugin!
It's great to hear that you find it helpful.
I totally get where you're coming from with your worry about the API key being stored in clear text in the data.json file. I'll definitely take a look at this and see if there's a way we can improve the security of the API key.
If you have any other ideas or concerns, please don't hesitate to let us know!

Hey, I believe this could be helpful https://www.electronjs.org/docs/latest/api/safe-storage, however the main drawback is this cannot be used for mobile. And because many people sync their obsidian vaults to access them from whenever I think enforcing this would be a mistake but adding as an option might be good.

i think we already added this feature in the v0.4.0+
it will try to encrypt keys, and if it cant, then it wont. that should keep the mobile compatibility

what do you think the default should be,
encryption or no encryption.
or should it look if it had mobile access before, if that then it will default to no encryption, otherwise do encryption?. what do you think

Hey, I believe this could be helpful https://www.electronjs.org/docs/latest/api/safe-storage, however the main drawback is this cannot be used for mobile. And because many people sync their obsidian vaults to access them from whenever I think enforcing this would be a mistake but adding as an option might be good.


[BEAM-646] Remove Unneccessary DataflowRunner Overrides

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

The removed overrides are indistinguishable from the transform that they
are overriding.
This is separated mainly to make sure the surgery-based implementation
doesn't mysteriously remove overrides when it's easier to handle as 1-to-1.

R: @peihe @dhalperi @davorbonaci @ssisk @kennknowles (or anyone else, really)

Coverage decreased (-0.5%) to 68.79% when pulling 43ea18b7abfd171250031b898a5e3ee98002a49f on tgroh:remove_redundant_overrides into cd4e6e402c5841aef24b279309354422bcfa5e4c on apache:master.

Coverage decreased (-0.04%) to 69.241% when pulling 43ea18b7abfd171250031b898a5e3ee98002a49f on tgroh:remove_redundant_overrides into cd4e6e402c5841aef24b279309354422bcfa5e4c on apache:master.

Run Dataflow RunableOnService

LGTM if postcommit is happy.


cancel Bug Bash participation

Signed-off-by: Daniel Holbach<EMAIL_ADDRESS>

https://deploy-preview-914--fluxcd.netlify.app/blog/2022/05/april-2022-update/
https://deploy-preview-914--fluxcd.netlify.app/blog/2022/04/contributing-to-flux/
https://deploy-preview-914--fluxcd.netlify.app/blog/2022/04/march-update/

all these posts had to be updated...


Time Format without AM and PM

using moment().format('LT') , I can get result like 6:02 PM
I would like to get th result as 18:02 without setting am/pm

It seems that you should use moment().format('H:mm'). (https://momentjs.com/docs/#/displaying/format/)
const date = moment();
console.log(date.format('LT')); // 9:47 PM
console.log(date.format('H:mm')); // 21:47
console.log(date.format('HH:mm')); // 21:47. Just in case you need to precede a '0' when is one digit hour: 04:21

hmm, then . @antarilos  , could you please add that precede 0 there when is one digit hour? Most of time , that's used more than not including

That is just what is done using date.format('HH:mm').


Enable HSTS on OCP route

This change adds the required annotation to the OCP route to enable HSTS headers as per:
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/networking/configuring-routes\#nw-enabling-hsts_route-configuration

Implemented in:
https://github.com/openstack-k8s-operators/openstack-operator/pull/819


VxWorksSymTab_Finder : add vxworks 5.0 format

struct SYMBOL is slightly shorter.
Source : disassembly of a vx 5.0.2-based ROM (TDS 744A firmware v1.1e, available at ko4bb.com
This closes #4507

Closed by accident, sorry. Still good.

Also works on vxWorks ROMs for TDS640 series also.  +1 for merge.

I went to merge it, but the remote branch fenugrec:vxworks_5.0 is missing.

I went to merge it, but the remote branch fenugrec:vxworks_5.0 is missing.

Sorry, not sure what happened there. Pushed it again, should be there now.
If it still fails and you don't mind doing it via the fairly trivial patch, that's fine.


RaZberry2: Failed to initialize the driver on arm64 (bullseye)

I moved my Raspberry from "stretch" to "bullseye". After new setup, zwabve-js-ui won't work anymore.
Reason: failed to initialze the driver.
2022-11-02T09:54:22.373Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                                  ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                                    ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                                   ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                                  ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                                  ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2022-11-02T09:54:22.373Z DRIVER   version 10.3.0
2022-11-02T09:54:22.374Z DRIVER
2022-11-02T09:54:22.374Z DRIVER   starting driver...
2022-11-02T09:54:22.381Z DRIVER   opening serial port /dev/zwave
2022-11-02T09:54:22.392Z DRIVER   serial port opened
2022-11-02T09:54:22.393Z SERIAL » [NAK]                                                                   (0x15)
2022-11-02T09:54:22.395Z DRIVER   loading configuration...
2022-11-02T09:54:22.400Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2022-11-02T09:54:22.401Z CONFIG   version 10.3.0
2022-11-02T09:54:24.696Z DRIVER   beginning interview...
2022-11-02T09:54:24.696Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2022-11-02T09:54:24.697Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2022-11-02T09:54:24.697Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2022-11-02T09:54:24.698Z CNTRLR   querying controller IDs...
2022-11-02T09:54:24.713Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-02T09:54:24.714Z DRIVER » [REQ] [GetControllerId]
2022-11-02T09:54:25.720Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-11-02T09:54:25.823Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-02T09:54:25.825Z DRIVER » [REQ] [GetControllerId]
2022-11-02T09:54:26.831Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2022-11-02T09:54:27.936Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-02T09:54:27.938Z DRIVER » [REQ] [GetControllerId]
2022-11-02T09:54:28.956Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D
                                  river.ts:3990:23)
                                      at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/co
                                  ntroller/Controller.ts:713:33)
                                      at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                                  /src/lib/driver/Driver.ts:1208:26)
                                      at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive
                                  r/Driver.ts:1015:16)
2022-11-02T09:54:28.971Z DRIVER   destroying driver instance...
2022-11-02T09:54:28.978Z DRIVER   driver instance destroyed

my docker-compose config is still same as on "stretch":
version: "3.7"
services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:8.2.2
    restart: unless-stopped
    tty: true
    stop_signal: SIGINT
    environment:
      - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
    networks:
      - zwave-js-ui
    devices:
      - '/dev/ttyAMA0:/dev/zwave'
    volumes:
      - zwave_data:/usr/src/app/store
    ports:
      - "8091:8091" # port for web interface

networks:
  zwave-js-ui:
    name: zwave-js-ui

volumes:
  zwave_data:
    name: zwave_data

raspi config should be ok. Device /dev/ttyAMA0 is availabe.
Any idea to solve this?

Try to disable soft reset using env var: ZWAVEJS_DISABLE_SOFT_RESET=true

Still same. Disable soft reset didn't change anything.

Try replacing /dev/ttyACM0 with the one you find by following this: https://github.com/zwave-js/zwave-js-ui/discussions/2483

@Qaldak Is there any fixed id path for that serial device? the problem is that using ttyACM0 could fail as zwave-js does a soft reset on startup and that could cause that id to change (for ex. ttyACM0 becomes ttyACM1). That's why we suggest to use that path instead, try to check in /dev/serial/by-path/

Have you checked the config.txt and cmdline.txt files and verified the required changes there, and know that the board is working as expected?

No, there is any fixed id path.
config.txt: uart, i2c and spi are enabled.
cmdline.txt: root=PARTUUID=8d0105b5-02 rootfstype=ext4 rootwait fsck.repair=yes net.ifnames=0 logo.nologo console=tty1 cgroup_enable=memory console=ttyAMA0,115200
What other way can I check if the device is working?

I'm using the following:
# Enable the serial pins
enable_uart=1
dtoverlay=miniuart-bt
core_freq=250

But I'm also using Ubuntu Core and the snap version, so I only have to connect the serial-port and it's automatically identified by ZUI. So I can't help you any futher.. I know @AlCalzone uses these boards too, and I guess under Debian based system (e.g rapsbian).

console=ttyAMA0,115200

Delete that. You have a serial console on the GPIO, preventing communication with the zwave controller.

Many thanks for all your inputs, guys.
I solved the problem!
Problem was: additionaly to enable_uart=1 (ttyS0 (mini UART device)), I had explicity ttyAMA0 console activated.
So I did following:
/boot/cmdline.txt removed
console=ttyAMA0,115200
/boot/config.txt set
enable_uart=1
dtoverlay=pi3-miniuart-bt

Now it works fine.


Text too big on plots

Just wondering why the text is always too big:
julia> using Gadfly
julia> plot(x=rand(10), y=rand(10))

For what it's worth, this can occur in Firefox as well (I'm using version 38.0.5 on OS X 10.10.3) with effectively the same workaround (Preferences / Content / Fonts & Colors / Advanced / Minimum Font Size = None). I don't know if they're using the same SVG backend or if it's an independent issue.
I'm also including the phrase "large text" in this comment to make this page easier to find for other people with the same issue (I didn't find it until I searched for "big text").

Today I've tested both in Firefox (46.0) and Inkscape (SVG editor). Both display with too big font size.
Yet on Chromium (Blink), Apache Batik and on gThumb displays OK.
It appears Firefox and Inkscape use different SVG rasterizer software components.


Ignore cookies with invalid values

When calling getCookies(), all cookies for the provided url are serialised. There is a possibility that a cookie's value could contain invalid characters. If this is the case, a FormatException is thrown during the creation of the Cookie object, resulting in no cookies being serialised. This is particularly annoying if the desired result of calling getCookies() is to fetch information about a particular cookie.
This commit handles serialisation of cookies with invalid values by catching any cookies with invalid values and removing them from the returned list of cookies.

Hi @fryette. Have you had the time to take a look at this yet?


Add support for ED25519 signature verification

There is a need for handling data-access authorization at the smart contract / blockchain level.
The first step is providing a way to verify a message for the ED25519 signature algorithm.

PR here: https://github.com/aionnetwork/aion/pull/589


Avoid creating a new HTTP client and transport for each Splunk request

Description
Currently, each request sent to a Splunk endpoint results in its own transport being created, with no timeout settings. That means the connection, once used, will sit around idle until the server decides to close it; if a new request goes out before that happens, the idle connection is not reused. I am not sure if we have ever seen any issues that might have been due to this, but it seems bad enough to fix it proactively anyway.
Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~
[x] ~Evaluated and added CHANGELOG entry if required~
[x] ~Determined and documented upgrade steps~

If any of these don't apply, please comment below.
Testing Performed

CI

This is a worthwhile change. Not sure why I never merged this, will do so now.


[VAGRANT] Deploying the Percona Galera Cluster with OpenEBS PVC is not getting created

BUG REPORT
While Deploying Percona Galera Cluster with OpenEBS the PVC  not getting created. Status of pvc is CrashLoopBackOff and shows some of the error as follows :
ubuntu@kubemaster-01:~/openebs/k8s/demo/galera-xtradb-cluster/deployments$ kubectl get pods
NAME                                                            READY     STATUS                                                                                RESTARTS   AGE
maya-apiserver-2288016177-nc86f                                 1/1       Running                                                                                0          2h
openebs-provisioner-2835097941-mlpqj                            1/1       Running                                                                                0          2h
pvc-4697b841-de62-11e7-bd38-021c6f7dbe9d-ctrl-597337590-xvsxs   2/2       Running                                                                                0          1h
pvc-4697b841-de62-11e7-bd38-021c6f7dbe9d-rep-3805322143-lstbl   1/1       Running                                                                                0          1h
pvc-7cc355a3-de5e-11e7-bd38-021c6f7dbe9d-ctrl-125976036-0dl7l   2/2         Running                                                                                0          2h
pvc-7cc355a3-de5e-11e7-bd38-021c6f7dbe9d-rep-3309872094-dfm22   1/1    Running                                                                                0          2h
pvc-84756e10-de65-11e7-bd38-021c6f7dbe9d-ctrl-851353941-0nn2w   0/2       rpc error: code = 2 desc = failed to start container "9926be22f069751c4a12d15d2a8c1f2e5054c9e6577eb15a0363d8d934f1a560": Error response from daemon: cannot join network of a non running container: 24bfd0c314d27a6252c437383fa5ce7e1256e9289d5e3468de4a7b1f4bbb102a   0          1h
pvc-84756e10-de65-11e7-bd38-021c6f7dbe9d-rep-1874766616-b2ndm   1/1       Running                                                                                0          1h
pxc-node1-2984138107-8dpd2                                      1/1       Running                                                                                0          2h
pxc-node2-1007987438-7g5xv                                      0/1       CrashLoopBackOff                                                                                14         1h
pxc-node3-82203929-qg18h                                        0/1         Pending                                                                                0          1h

@nsathyaseelan , can you point to the vagrantfile where this issue was seen? This seems to be an issue with the pod network.
Refer:

https://github.com/kubernetes/kubernetes/issues/50356
https://github.com/kubernetes/kubernetes/issues/44298

We are no longer supporting the Vagrant based setup after minikube has become popular. The last supported version was with K8s 1.8.


react-router-global typescript definition needed

The current typescript definition does not play well with react-global.d.ts.
There should be a separate react-router-global.d.ts file that uses react-global.d.ts

I believe this issue should be somewhere else. We don't maintain anything like this.


5.99 nightly PCB outline error

Following the comment in issue 190, I updated to the current KiCAD nightly (5.99.0-6862-g9454f9df92) as well as the current IBOM git.  Unfortunately, hitting "Generate BOM" gives:
"Please draw pcb outline on the edges layer on sheet or any module before generating BOM."
I do have a PCB outline, and prior to updating KiCAD the files worked correctly.  Did I do something wrong or did KiCAD break again?

I just compiled kicad from master branch and can't reproduce the issue but I test on a board with simple square outline.
Maybe yours has outline consisting only of arcs or something? Could you attach your board for me to test? Feel free to remove everything from it aside from the outline and maybe one footprint.

My board is circular...
Here is a different open source board with the same issue:  https://github.com/mgiacomelli/sipm/tree/master/Improved Design/KiCAD

I was able to generate bom with the board you linked just fine.
Can you confirm that your ibom version is on df2f0dd ?

I'm sorry, there was actually an older copy also on the kicad plugins search path, and that was being found before the current git version of the plugin.  Deleting the old one fixes the problem.


Some more options: local builder and CI type

Hello, I have added my own special recipe to the tool.

Thanks!


[libra framework] First cut at specifying DesignatedDealer

Motivation
This PR adds specifications for DesignatedDealer module.  The verification is currently turned off due to performance problems in Move Prover.  I will revisit the verification in a bit.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Existing tests and pending Move Prover verification
Related PRs

FYI https://github.com/libra/libra/pull/4978

@moeziniaf and I discussed offline.  I was not aware that the feature of unbounded minting is now deprecated.  I have removed this feature from the PR and updated the spec I wrote.

@bors-libra r=moeziniaf

:pushpin: Commit 154bef2 has been approved by moeziniaf

:hourglass: Testing commit 154bef22d3e4186729de8321694d0cff1737eb0a with merge d8dbbd1fb54980314d3dd25b6cdb021045bd7bc2...

[move-prover] Move Prover test (language/move-prover/cargo test) on commit 154bef2 did fail. See details.

Can you please be sure that MIRAI bot passes before you merge so we add not any additional failures to the already failing things? Libra.move fails at head because yesterday some changes were submitted which break it. You can add verify = false to the module to disable it for now.

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: moeziniaf
Pushing d8dbbd1fb54980314d3dd25b6cdb021045bd7bc2 to master...


New version: Zettlr.Zettlr version 2.2.5

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run
https://github.com/microsoft/winget-pkgs/issues/42616


FINERACT-842 Made TRY-IT swagger button work

This PR can only be merged after: #1163

After #1163 is merged we only need to add the following code to fineract-input.yaml ( can be converted from json to yaml automatically)
servers:
- url: /fineract-provider/api/v1
components:
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic

And the try it button would work, I have tested this :D

@ptuomola do you want to review and locally test this one? I'm happy to just merge it if it has your LGTM... (or even let this be one of the PRs that you can merge yourself, soon).

BTW I don't suppose there's an easy better way for that SecurityRequirement annotation to be specified only once (perhaps programmatically?), instead of having to be specified everywhere? It's not a huge deal, and I don't mind merging it as is, but was just thinking that people may forget to add that in new *Resource classes for new APIs in the future. Or perhaps they won't, because they'll just copy/paste anyway..  ;-)

With my basic knowledge on this( and a lot of research :P ) I could find the only this way to work.
I will search for a better option for this once more :D

https://www.loom.com/share/8eb964074579491090db5bacbe5eff99
@vorburger @ptuomola  I have a small demo video on how this works :)
The only problem I see is to give a proper error msg if the user try to access the API without authorizing.

For the problem that if the user does not authorize, I think a better approach will be to have a the authorization parameters set by default to:
username: mifos
password: password
Since this would probably be used most (if not all) of the time for that username.
This, however, is not part of this PR and I would raise a separate PR for that purpose.

Just noticed, Some API routes are not covered yet, converting to draft to avoid accidental merge.

@vorburger there was an easier (and probably the correct way) to do this. I have updated this.
I have also added tenantid as an authorization param so that user can enter it if he wants.
By default, the user gets them set, and he can directly test the API :)

Ready for your review @ptuomola

@thesmallstar wait but can the end-user actually CHANGE the uid/pwd (and - tenant) in the Swagg UI? That wasn't clear from the screenshot, to me.

@vorburger yes, the initial values are only added for convenience since 90percent if the times we will probably need default id-pass and tenant.

@ptuomola  WDYT?

@thesmallstar Looks great to me! Tried it out locally and it works fine

@vorburger this is ready to be merged  😄

LGTM
Awesome work @thesmallstar


crypto/x509: failed to parse ECDSA256 PEM generated by Apple Developer Website

What version of Go are you using (go version)?

1.12.7

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
GOOS="darwin"
GOARCH="amd64"

What did you do?
I'm trying to build a Apple Push Notification Service server with github.com/dgrijalva/jwt-go, which can generate token to communicate with Apple's server.
I downloaded the ECDSA256 private key(.pem file) from Apple Developer Website and tried to form the token using built-in parser.
I've regenerated the private key more than two times and it always occur.

This key is already revoked so I think it's safe to attach here
-----BEGIN PRIVATE KEY-----
MIGTAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBHkwdwIBAQQgK4vwsbmI8Zv5L3Vi
3A6jLxpPhT1foluxAzVrF8HUz0+gCgYIKoZIzj0DAQehRANCAASiiOmidKO8QG/1
uxIzl8g8yqYDCmImljypqZxutYg1YaMJuBpgfFCJdtp+SdYhq8J8avOMwDwep8KC
lfN6cID4
-----END PRIVATE KEY-----

What did you expect to see?
No error should be presented.
What did you see instead?
It presented such error messages.
2019/08/09 14:56:14 x509: failed to parse EC private key: asn1: structure error: tags don't match (4 vs {class:0 tag:16 length:19 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false}  @5

Thank you for reporting this issue @Frozen-Tofu and welcome to the Go project!
I have made for you a runnable playground link https://play.golang.org/p/KYMQBqBqlz0
or inlined below
package main

import (
	"crypto/x509"
	"fmt"
	"log"
)

func main() {
	blob := []byte(`
-----BEGIN PRIVATE KEY-----
MIGTAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBHkwdwIBAQQgK4vwsbmI8Zv5L3Vi
3A6jLxpPhT1foluxAzVrF8HUz0+gCgYIKoZIzj0DAQehRANCAASiiOmidKO8QG/1
uxIzl8g8yqYDCmImljypqZxutYg1YaMJuBpgfFCJdtp+SdYhq8J8avOMwDwep8KC
lfN6cID4
-----END PRIVATE KEY-----
`)
	privKey, err := x509.ParseECPrivateKey(blob)
	if err != nil {
		log.Fatalf("Failed to parse private key: %v", err)
	}
	fmt.Printf("%#v\n", privKey)
}

in the future, please attach a reproducible code sample not just the private key :)
We are currently in code freeze before we release Go1.13 but I shall kindly ping some cryptography experts @agl @FiloSottile to take a look.

That private key is PEM encoded, so you need to unwrap that first. Also, it's a PKCS#8 rather than raw ECC private key, so the correct parsing function is ParsePKCS8PrivateKey. (The “PRIVATE KEY” means PKCS#8—I'm afraid the PKCS standards are just awkward like that.)
See https://play.golang.org/p/AlXERsa1Evr

Okay thank you


Support mounting .vhdx in the WSL Settings app (GUI)

Problem
WSL requires manual mounting for Linux file systems and VHD images due to the lack of automatic recognition. Hence, the wsl --mount come in handy for for these frequent chores, but the job is tedious, as usual.
It requires identifying the DeviceID and then invoking wsl --mount component:
GET-CimInstance -query "SELECT * from Win32_DiskDrive"
wsl --mount <DeviceID> --partition <Partition> --type <Filesystem>

or for VHD
wsl --mount --vhd <pathToVHD>

Solution
A built-in GUI for mounting in the WSL Settings app would be a valuable addition. I would love to see a dialog box featuring clickable options for selecting Linux disks/partitions, a custom option to enter the path to a VHD image, along with a button to mount the chosen item.

/feature


Powered by Fedora

Please, add the 'powered by Fedora logo' to ScholarSphere.

@mtribone is checking to see if University policy prohibits this.

Investigate where we can put this logo if anywhere.

Spoke with Jill Shockey about adding the Fedora logo to SS and we both are in the position that it is not a good idea to imply endorsement. However there are exceptions to linking to outside parties and if needed we can speak with Strategic Communications and Licensing about the matter if the logo is a "must-have" for us.
Policy reference:
http://guru.psu.edu/policies/AD52.html#F
http://guru.psu.edu/policies/AD52exemptions.htm

Discussed adding some  additional content to the About page in the "ScholarSphere and The Underlying Technology are Open Source" section.


removing unused vars and imports on save

Although I tried many editor settings as below:
"go.lintOnSave": "off",
"editor.codeActionsOnSave": {
"source.fixAll": false,
},
"editor.formatOnSave": false,
Still editor is removing unused imports and vars. It will remove other unreached statements too... eg. after "return" whatever is written in code. Many times we do test and it is not letting us to do that. Please disable this feature ASAP. This is sucking.
This is working for reactJS, nodeJS and golang. Not tested on other languages.

/needsMoreInfo
You forgot to fill in issue template.
Is it reproducible with all extensions disabled? Because VS Code doesn't support code operations on Go
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

/needsMoreInfo
You forgot to fill in issue template.
Is it reproducible with all extensions disabled? Because VS Code doesn't support code operations on Go out of the box
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

When I tried with reload with extensions disabled, it does not remove anything. It works fine. But extensions make it easier to work with specific language. In my case it is JavaScript(node.js, react.js) and golang. It is removing the unused and unreachable code in both of languages.
I have installed ESLint, jshint, Go, JSON tools, Debugger for Firefox and Docker extensions.

Not sure why you want jshint when ESLint should provide same kind of checks and more (if configured).
Anyway you can use https://code.visualstudio.com/updates/v1_52#_troubleshooting-extension-bisect to find extension that does this and then configure it or remove if unised.

After removing the jslint, it works correctly.
Thank you for support guys....appreciated.


Has anyone had this problem and what to do

Dear @mxy0610 ,
From your error code, it's unclear what settings you're using for your training. However, it seems you might be encountering issues due to using a single GPU or setting a very low label-to-unlabeled ratio. It's essential that each training batch contains at least one labeled sample for successful SSOD training. If your label-to-unlabeled ratio is set so low that certain batches lack labeled samples, the data loader might not perform as expected. If you could provide more details about your settings and approach, it would be easier for me to assist you further.
Best


word wrap

hello
i have a sensor tile that outputs text. now depending on the output the text can be a little longer than what fits on the tile.
how would i make the text break lines (word wrap)?
i tired using customStyles, for the tile but it had no effect...
customStyles: { 'background-color': '#e63946', 'word-wrap': 'break-word', 'width': '304px' }

Only solution i found is to write a custom tile...
for anyone interested: in scripts/app.js to the list var TYPES add:
   CUSTOM_SENSOR: 'custom_sensor',

in index.html add:

and in styles/main.css add
.item-entity-cust-sensor {
  position: absolute;
  height: 80px;
  line-height: 40px;
  white-space: normal;
  word-wrap: break-word;
  top: calc(50% - 45px);
  left: 0;
  right: 0;
  z-index: 2;
  overflow: hidden;
}

not a perfect solution, but does the trick for what i need right now...
happy to hear better proposals! :)


feat: Bernoulli's inequality for 0 < p < 1

!bench

Not bad: the file now takes about half as long as before, despite having roughly twice as many theorems! Thanks for taking on this job. I'll try to find time to proofread it for style later today, then it should be good to go.

Umm, I just spotted something I should have realised much earlier.
There is a file Mathlib.Analysis.Convex.SpecificFunctions.Pow, which contains a theorem
lemma strictConcaveOn_rpow {p : ℝ} (hp₀ : 0 < p) (hp₁ : p < 1) :
    StrictConcaveOn ℝ≥0 univ fun x : ℝ≥0 ↦ x ^ p := by

So we are just reinventing the wheel here. ☹ I apologise for not having realised this first time around.
Perhaps the best way forward is the following. The Bernoulli inequality for p < 1 is a statement of interest in its own right, so I suggest keeping the proof you've written for that. But it might be best to replace your proof of strictConcaveOn_rpow, and its non-strict version, with a (hopefully much quicker) version deducing it from the existing NNReal version. This would have to live in Convex.SpecificFunctions.Pow, so I also suggest adding a comment to Convex.SpecificFunctions.Basic explicitly pointing out that the p < 1 case is treated elsewhere.

But it might be best to replace your proof of strictConcaveOn_rpow, and its non-strict version, with a (hopefully much quicker) version deducing it from the existing NNReal version. This would have to live in Convex.SpecificFunctions.Pow, so I also suggest adding a comment to Convex.SpecificFunctions.Basic explicitly pointing out that the p < 1 case is treated elsewhere.

The proof of Real.strictConcaveOn_rpow already goes through the NNReal version:
lemma strictConcaveOn_rpow {p : ℝ} (hp₀ : 0 < p) (hp₁ : p < 1) :
    StrictConcaveOn ℝ (Set.Ici 0) fun x : ℝ ↦ x ^ p := by
  refine ⟨convex_Ici _, fun x hx y hy hxy a b ha hb hab => ?_⟩
  let x' : ℝ≥0 := ⟨x, hx⟩
  let y' : ℝ≥0 := ⟨y, hy⟩
  let a' : ℝ≥0 := ⟨a, by positivity⟩
  let b' : ℝ≥0 := ⟨b, by positivity⟩
  have hx' : (fun z => z ^ p) x = (fun z => z ^ p) x' := rfl
  have hy' : (fun z => z ^ p) y = (fun z => z ^ p) y' := rfl
  have hxy' : x' ≠ y' := Subtype.ne_of_val_ne hxy
  have hab' : a' + b' = 1 := by ext; simp [a', b', hab]
  rw [hx', hy']
  exact (NNReal.strictConcaveOn_rpow hp₀ hp₁).2 (Set.mem_univ x') (Set.mem_univ y')
    hxy' (mod_cast ha) (mod_cast hb) hab'

I think the better approach is to move the currently un-namespaced (strict)?ConvexOn_rpow to Analysis.Convex.SpecificFunctions.Pow (where (strict)?ConcaveOn_sqrt also lives), namespace it and prove it from a new NNReal version.

But it might be best to replace your proof of strictConcaveOn_rpow, and its non-strict version, with a (hopefully much quicker) version deducing it from the existing NNReal version. This would have to live in Convex.SpecificFunctions.Pow, so I also suggest adding a comment to Convex.SpecificFunctions.Basic explicitly pointing out that the p < 1 case is treated elsewhere.

The proof of Real.strictConcaveOn_rpow in Analysis.Convex.SpecificFunctions.Pow already goes through the NNReal version:

If this already exists in the other file, then there is even less for this PR to do.

I think the better approach is to move the currently un-namespaced (strict)?ConvexOn_rpow to Analysis.Convex.SpecificFunctions.Pow (where (strict)?ConcaveOn_sqrt also lives), namespace it and prove it from a new NNReal version.

The reasons for not doing that are very clearly explained in the existing code. The file Analysis.Convex.SpecificFunctions.Pow needs more imports than Analysis.Convex.SpecificFunctions.Basic does. Because strictConvexOn_rpow is foundational for a whole load of analysis / measure theory code (anything involving L^p spaces), it is important to prove it with minimal imports; but this is not true of the concavity result for p < 1 which has far fewer applications.

LGTM. Please update the title of this PR to match the content – when that's done I'll ping the maintainers.

It is done now?

I added a little more explanation to the header string. Code LGTM.
maintainer merge


Added opt arg for getting coverage from index.html (output by nosetests)

Great little package here! But it was giving me a different coverage % than what the index.html (and other files) said I had and I'd like to use that %.
I ran nosetests like this: nosetests --with-coverage --cover-package=<pkg> --cover-html
This is my first contribution to another person's work, so thanks for considering my request.

Hi, thanks for the contribution!
Is this generated HTML specific to nosetests or is it the same if you just generate a report with coverage directly?

The one that nose produced for me is identical (within reason) to the one here. I tested get_from_html() on it and it worked.

That sounds good, thanks for checking!
But still, before merging this I'd like to know the reason for the difference in the numbers (maybe I have a bug in my code). Do you have additional configuration that might affect the coverage count? The project in question isn't public, is it?

I think that coverage.py considers all modules in a package, but my tests only currently cover code imported by init.py causing nose to calculate coverage for just two .py files out of about five. Any additional code imported in init will then be covered by nose as the dev process rolls along. So in the end, I'd like the coverage badge to only reflect implemented code and ignore my work-in-progress code.
I use a .cfg file that tells nose to use --with-coverage --cover-erase --cover-package=dslw --cover-html. And yes, dslw is a public repo.
Maybe there's a better way than the one I proposed to tell your script to only cover the implemented modules of a package, but since nose does this already, I figured I'd make something that works for me/nose. If this is lying about the coverage of a project, maybe this function could add an "*" to indicate that not all code was actually covered.

Sorry for the long wait and thanks for your explanations. I'm not exactly sure about the relation between nose and coverage, but I'll merge this PR after a few small details are fixed. I'll add comments :)

I'd love to see this merged. Being a while though. @WindfallLabs are you continuing this?


Remove min execution time check

Summary
Details and comments
Fixes #1064

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 4 (75.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 74.895%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/utils/qctrl.py
1
2
50.0%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/utils/qctrl.py
1
96.08%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
2497

Relevant Lines:
3334

💛  - Coveralls


Adding SSH connection to Cisco Device fails.

I assume due to xpipe trying to figure out what kind of device is on the other side of the SSH connection it connects successfully but gets confused by the Cisco environment. Can we get a checkbox to disable discovery checking to allow connections to network devices that don't have "normal" *nix shell environments?
Shell opener normalization failed:
3750#echo "Checking what shell type we are in ..."
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#echo -NoEnumerate "a"
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#
3750#echo -NoEnumerate "a"
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#

For that purpose I would try to use the Custom Command -> Custom Terminal Command connection in xpipe if your only intention is quickly booting up into a terminal. Anything more wouldn't be possible anyways if the shell is not recognized.
I will improve the descriptions in the application to highlight this.

If your SSH connection however also requires inputs like a password, then this can't be filled automatically with a custom terminal command.
I guess I can think of a solution to somehow disable shell type recognition for normal SSH connections if needed.

Most network devices will require a password it still conforms to the normal SSH protocol but its not a unix device so your checks wont be valid. Maybe having a fallback in your error handling for generic SSH would be a good option?

Sadly I don't have any cisco hardware available to test, so I have to rely on your help here a little bit.
The issue is that I need to detect that we are in a cisco environment right away somehow. If I can't do this, and the normal shell detection logic is run, it will take like 10 seconds for the timeout handling to kick in and realize that we need to fallback to an unknown shell type.
I already do something like this for opnsense shells as they also require special handling. I guess I can just check for the output The command you have entered is available in the IOS.sh. and deduce that this is a Cisco environment. Or is this warning printed only in some Cisco environments and not in some others?

I just implemented my plan of checking for a specific output for cisco devices. Can you try whether the latest version in https://github.com/xpipe-io/xpipe-ptb works?

So my recommendation would be to use sh ver short for show version which is ubiquitous across all cisco devices.
As there are 3 major different code bases IOS, IOS-XE, and NX-OS from there the output will tell you what code version is available what the underlying hardware is etc. Here is some example output from my 3750X
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.2(4)E10, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2020 by Cisco Systems, Inc.
Compiled Tue 31-Mar-20 13:22 by prod_rel_team

ROM: Bootstrap program is C3750E boot loader
BOOTLDR: C3750E Boot Loader (C3750X-HBOOT-M) Version 12.2(53r)SE2, RELEASE SOFTWARE (fc1)

3750 uptime is 26 weeks, 3 days, 7 hours, 13 minutes
System returned to ROM by power-on
System image file is "flash:/flash"
Last reload reason: power-on

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
<EMAIL_ADDRESS>
License Level: ipservices
License Type: Permanent Right-To-Use
Next reload license Level: ipservices

cisco WS-C3750X-48P (PowerPC405) processor (revision A0) with 262144K bytes of memory.
Processor board ID FDO1605P1LZ
Last reset from power-on
4 Virtual Ethernet interfaces
1 FastEthernet interface
52 Gigabit Ethernet interfaces
2 Ten Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.

512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address       : 44:2B:03:89:3C:80
Motherboard assembly number     : 73-12553-05
Motherboard serial number       : FDO1605187U
Model revision number           : A0
Motherboard revision number     : D0
Model number                    : WS-C3750X-48PF-S
Daughterboard assembly number   : 800-32727-01
Daughterboard serial number     : FDO160501H0
System serial number            : FDO1605P1LZ
Top Assembly Part Number        : 800-31324-02
Top Assembly Revision Number    : E0
Version ID                      : V02
CLEI Code Number                : COMJZ00ARB
Hardware Board Revision Number  : 0x03

Switch Ports Model                     SW Version            SW Image
------ ----- -----                     ----------            ----------
*    1 54    WS-C3750X-48P             15.2(4)E10            C3750E-UNIVERSALK9-M

Configuration register is 0xF

Well I will see what I can do with the version output. The problem is that it becomes very hard to properly read output if no normal shell commands are supported. Without echo I can't be sure where the output of one command starts and ends.
From my testing with mock output, checking for the string The command you have entered is available in the IOS.sh works for now at least. I plan to release this quick fix tomorrow with 1.7.3, maybe you find some time to quickly check whether the PTB works on real hardware until then so I can be sure.

I do want to urge caution though if someone else out there runs IOS-XE / NX-OS you won't get the same response.
So while this will likely work for me / anyone else running older 3750's which are end of life hardware your fix might not apply to everyone. I have an NX-OS device but it is not yet configured and I don't have SFPs to be able to properly test it.

Ok now we are able to add the device but get an error on starting the connection
Shell did not start up in time:
3750#echo "Checking what shell type we are in ..."
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#echo -NoEnumerate "a"
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#echo "Checking whether we are in fish"
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#echo "fish: $FISH_VERSION"
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
3750#

I think the task of supporting your cisco devices and others is going to be complicated. I had hoped that my quick fix would work, but as it does not, I would have to investigate this manually somehow to properly implement and test everything.
As I don't have any cisco hardware myself, I either have to maybe find someone near me to borrow one for a few days or purchase the cheapest used one that I can find.
I don't really like a checkbox to disable this discovery as you suggested, mainly because that would be confusing for users as you need to know what's happening in the background in order to understand why this option is necessary. However, I'm thinking about adding a special option to the error handler to mark the connection as having discovery disabled. That way, you still have the option to disable it but only if you actually need it.

So I though about the implementation and this discovery disable functionality will be added in 1.8.0 along with a more general shell type rework. Your case is not the only problematic one, fish shell also causes problems right now.
The system was not designed for these cases initially so I need to change several things there which takes some time, so stay tuned for 1.8

All right since I was not able to get my hands on a cisco device I have a couple of questions:

How does it handle connections without a tty? E.g. does it also work if you connect with ssh -T user@host?
Where are the errors written to? E.g. if you input a command that does not exist, does it write to stdout or stderr?

Alright, the shell handling has been reworked to allow for dumb shell connections in 1.8 and is currently in testing at https://github.com/xpipe-io/xpipe-ptb.
To properly make this work for your case, I would need to know whether your device will print the error
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
   'term shell'
You can also enable it for all terminals by configuring the
   'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'
``` to stdout or stderr.

Very likely yes, please do keep in mind though that the shell isn’t utilized in normal operations. Cisco has a custom CLI with three tiers of access. Zero level -> user -> privileged exec.To get from zero to user the “enable” command is utilized, and from user to priv “configure terminal” is used. There can be a separate enable password from privileged. But most of the time some form of TACACS will grant the ability to skip the enable to get straight to user. v/r Andrew CreighNetwork Engineercell:<PHONE_NUMBER>On Feb 20, 2024, at 10:24 PM, Christopher Schnick @.***> wrote:
Alright, the shell handling has been reworked to allow for dumb shell connections in 1.8 and is currently in testing at https://github.com/xpipe-io/xpipe-ptb.
To properly make this work for your case, I would need to know whether your device will print the error
The command you have entered is available in the IOS.sh.
However, the shell is currently disabled. You can enable
it on this terminal by typing
'term shell'
You can also enable it for all terminals by configuring the
'shell processing full'
command. There is additional information in the man command.
For more information, enable shell, and then enter:
'man IOS.sh'

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Yeah bad habit on my part for replying via my email instead of through github I edited my comment.
Typically there is a designator character on the shell to tell you when you are in zero vs user vs priv.
hostname> is zero
hostname# is user
hostname(config) is privileged exec
So maybe searching the returned output can help you out?

I see about the character.
If you run ssh user@host 2>/dev/null to your cisco device, does it print any error messages? E.g. if you type an invalid command, is the error then swallowed by /dev/null or not?

This is now properly fixed in XPipe 9 at https://github.com/xpipe-io/xpipe-ptb for all cases with the introduction of a new option to not attempt to identify the system.


Should disallow coercing to/from array types

Currently, there is nothing to prevent you from erroneously casting to/from array types. See this discussion on Gitter for a proposed solution.

This has been resolved in the latest release.


CI tests are failing (xvfb issue?)

Conda-based CI tests are failing, as seen in PR #755.  This this is new behavior.  I checked on my local branch and this appears to be happening on the main branch => appears that the issue is outside of this repository.  One possibility is an issue with slycot.

Doing a bit of digging.  It doesn't look like slycot is the issue, since Python 3.7 without Slycot without cvxopt also crashes.  The error messages seem to point to coveralls (?).  I'm try to isolate things here.

I don't think that it is coverage.
Looks Qt related which is the default backend for Matplotlib. My first guess is that this is a conda-forge packaging bug on the MPL or Qt side.
More things to try:

pytest-xvfb
set MPLBACKEND
try QT_QPA_PLATFORM=offscreen

Using pytest-xvfb fixes the original crash (which was happening in config_test.py, but introduces a new test failure:
def test_root_locus_zoom(self):
[102](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:103)
        """Check the zooming functionality of the Root locus plot"""
[103](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:104)
        system = TransferFunction([1000], [1, 25, 100, 0])
[104](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:105)
        plt.figure()
[105](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:106)
        root_locus(system)
[106](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:107)
        fig = plt.gcf()
[107](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:108)
        ax_rlocus = fig.axes[0]
[108](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:109)

[109](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:110)
        event = type('test', (object,), {'xdata': 14.7607954359,
[110](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:111)
                                         'ydata': -35.6171379864,
[111](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:112)
                                         'inaxes': ax_rlocus.axes})()
[112](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:113)
        ax_rlocus.set_xlim((-10.813628105112421, 14.760795435937652))
[113](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:114)
        ax_rlocus.set_ylim((-35.61713798641108, 33.879716621220311))
[114](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:115)
>       plt.get_current_fig_manager().toolbar.mode = 'zoom rect'
[115](https://github.com/murrayrm/python-control/runs/7679958935?check_suite_focus=true#step:5:116)
E       AttributeError: 'NoneType' object has no attribute 'mode'

There is a note saying that we were using xvfb-run to get the right MPL back end, so that is probably related somehow.

One thing that is odd is that the other test suites pass and they are using xvfb-run.  In particular, control-slycot-src.yml seems fine and it runs the full test suite...

There is a note saying that we were using xvfb-run to get the right MPL back end, so that is probably related somehow.

Yes, it is related. The plain Agg backend does not have the toolbar for the figure manager. We have seen this before: https://github.com/python-control/python-control/pull/504#discussion_r554623327
So this looks more and more like a qt backend issue in the MPL or Qt packages in conda-forge.
Are you able to determine package version differences in the control-slycot-src vs. the python-package-conda runs?

It looks like the error occurs when the installation uses a specialized conda environment (versus just installing things in the conda base environment).  There are quite a few differences in the various packages that are installed in each case.

Now that the conda  error is resolved, there is a new X11 error on the main branch. Something in the GHA runners must have changed between the check run for #755 and after the merge of it.

The failures with the invalid DISPLAY variable are totally random. We might just have been lucky in the builds for #755 and #757.
https://github.com/bnavigator/python-control/commits/update-CI

For the record: the random DISPLAY failure is back. (Maybe due to #796)


⚠ Turnos 24x7 has degraded performance

In 9909e4a, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 3161 ms

Resolved: Turnos 24x7 performance has improved in 797925f.


Issue with Blank Package Versions in JSON Output when Scanning composer.lock File

Description
When scanning the composer.lock file using JSON output, the package version information is returned as blank.
Attachments

composer.lock
JSON Output File

Environment

Operating System: CentOS
Scanner Version: v1.5.0

Thanks for catching this issue!
It is caused by both the package version and git repo and commit existing at the same time. I made a fix in #736 and it should be fixed in the next release.


Configuring Multi-factor Authentication Error

Practice Lab 0501: Configuring Multi-factor Authentication
Task 2: Enable MFA for a user
Step: 7. In the multi-factor authentication page, select service settings. Select Allow users to remember multi-factor authentication on devices they trust.
Description of issue:
When users are attempting to access the 'Additional cloud-based multifactor authentication settings' [P1] and then 'Service settings' [P2] they are met with a service connection error and are unable to proceed [P3].
[P1]

[P2]

[P3]

I will look into this and get back to you. Thanks for letting me know.

From: SkillableKA @.>
Sent: Thursday, September 5, 2024 6:32 AM
To: MicrosoftLearning/MD-102T00-Microsoft-365-Endpoint-Administrator @.>
Cc: Subscribed @.***>
Subject: [MicrosoftLearning/MD-102T00-Microsoft-365-Endpoint-Administrator] Configuring Multi-factor Authentication Error (Issue #90)
Practice Lab 0501: Configuring Multi-factor Authentication
Task 2: Enable MFA for a user
Step: 7. In the multi-factor authentication page, select service settings. Select Allow users to remember multi-factor authentication on devices they trust.
Description of issue:
When users are attempting to access the 'Additional cloud-based multifactor authentication settings' [P1] and then 'Service settings' [P2] they are met with a service connection error and are unable to proceed [P3].
[P1]
image.png (view on web)https://github.com/user-attachments/assets/c182a2b7-2f84-4ef1-a52b-4b98d525518a
[P2]
image.png (view on web)https://github.com/user-attachments/assets/8dca8a43-bf59-4c8b-8362-17bcd8a3962e
[P3]
image.png (view on web)https://github.com/user-attachments/assets/f52789e0-0898-4201-843c-f58622b34f7a
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftLearning/MD-102T00-Microsoft-365-Endpoint-Administrator/issues/90, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2BOXJHMJUZWZ4OW6YSM2PTZVBMP5AVCNFSM6AAAAABNWQLHUSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYDOOBSGUYDKMI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I am also facing similar issue. Please leave an update if there is any.

It's because of the 'new' interface. It does not currently affect all tenants, at least my delivery last week only affected 3 out of 12 tenants.
If you use the 'legacy' link (that is listed in the notification displayed in P2 above) to modify any setting and save, the 'new' links work like a charm.
The legacy link just takes you here : https://account.activedirectory.windowsazure.com/UserManagement/MultifactorVerification.aspx
If I had to guess I'd say the 'new' portal can't handle rehydration of custom settings, or a null set; hence the service connection error.

FYI, I just gave it another try and it worked as it is expected to.

I have faced the same issue, please let us know if it's resolved.

Hello,
Just seeing if there had been any updates to this as we are still receiving tickets with both instructors and students experiencing the issue above. The page will now load, but users are unable to actually save the MFA settings. [P1]
As Steve pointed out, the legacy link will allow you to save the required settings. You can then jump back over to the Entra GUI and the changes will be showing. [P2]
[P1]

[P2]

Yeah, I had to advise students last week to use the legacy link to set the minutes. Once saved, it's all gravy, you can then change it in the 'new' page or the 'legacy'.
It's more of a platform issue rather than a lab issue, though.
I see two choices. We either (a) advise students if it fails to use the legacy link or (b) change the lab steps to always use 'legacy' link.
I think it might be better to go for option (a), personally.

I just ran through the lab while I was making changes for a PR and it worked like a charm from the 'new' page. @SkillableKA any chance you guys wanna spin up a lab instance and check if you can also set the 30 and save?


Pass the Note to the BE and save to the DB

Description
Save the Application Note into the database.
Add an Id and name to the existing UI elements and have the Controller save it as an ApplicationEvent.
Release notes:
Program Application Notes are now saved into the database.
Checklist

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
Fixes #3020; Fixes #3264

Codecov Report

Merging #3309 (8a55cc4) into main (4f0821e) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #3309      +/-   ##
============================================
+ Coverage     79.89%   80.02%   +0.13%
- Complexity     2324     2326       +2
============================================
  Files           285      285
  Lines          9151     9166      +15
  Branches        611      612       +1
============================================
+ Hits           7311     7335      +24
+ Misses         1605     1595      -10
- Partials        235      236       +1

Impacted Files
Coverage Δ

.../controllers/admin/AdminApplicationController.java
46.30% <100.00%> (+5.79%)
:arrow_up:

...s/applications/ProgramAdminApplicationService.java
100.00% <100.00%> (ø)

.../services/application/ApplicationEventDetails.java
100.00% <0.00%> (+13.33%)
:arrow_up:

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


Add typescript definition file

Whoops I need to export declare class to make this work right.

Okay I think I fixed it.


[WIP] Close #91 | Add NusaX-MT

Please name your PR after the issue it closes. You can use the following line: "Closes #ISSUE-NUMBER" where you replace the ISSUE-NUMBER with the one corresponding to your dataset.
Checkbox

[ ] Confirm that this PR is linked to the dataset issue.
[ ] Create the dataloader script nusantara/nusa_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[ ] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _NUSANTARA_VERSION variables.
[ ] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[ ] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one NusantaraConfig for the source schema and one for a nusantara schema.
[ ] Confirm dataloader script works with datasets.load_dataset function.
[ ] Confirm that your dataloader script passes the test suite run with python -m tests.test_nusantara --path=nusantara/nusa_datasets/my_dataset/my_dataset.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

hi, any update on this PR @ilhamfp? do you need any help?

@gentaiscool Hi genta, I'm planning to work on it this weekend

Hi @gentaiscool, I have updated this PR. One question: I'm not sure what's the source schema looked like exactly for NusaX-MT. So I just make the source schema follow the nusantara_t2t schema.

@holylovenia updated to use ISO639-3 language code on text 1 and 2 name 👍


Fixed replica count not working

Rio 0.1.1-rc1
When attempting to scale a service to fixed replica count, it's not scaling.

This should already be fixed in the latest release. Closing.


feat: added support for reserved public ip address for nat gateway

closes #311

Hi @hyder,
I got a message from Carlos Santos to test this PR. I did run into this issue
https://github.com/oracle-terraform-modules/terraform-oci-oke/issues/313
However, if I comment out
modules/okenetwork/datasources.tf
...
//data "oci_waas_edge_subnets" "waf_cidr_blocks" {
//}

And replace the reference in modules/okenetwork/security.tf on row 261 to [ ] I was able to test the nat gateway id, which seems to be doing what it should.
I can see the reserved ip being used for the nat-gateway in the created vcn.

Thanks for the feedback. For the WAF issue, can you please try the following:

Create a group and add the terraform user to the group
Create a policy in root compartment with the following statement: "Allow group  to read waas-family in tenancy"

And then try again by uncommenting the datasource? Please replace the groupname in (2) as appropriate.

Thanks for the quick reply.
Unfortunately adding the policy to the group where the terraform user is part of didn't help.


[build-catkin.sh] Adds auto-detection for catkin_ws and repo paths

@pranaypratyush - Consider merging this PR, for easier builds + tests on migrating-to-catkin branch.

Make it so that it autodetects. Use some env variable and/or use find.

It already does - try running the build-catkin.sh of this PR.

I apologize for my immaturity. Merging now.


DS18B20 support

Request for support for the DS18B20;
https://github.com/flyte/pi-mqtt-gpio/issues/32#issuecomment-465640303
No, as far as I know, one wire from dht11 and one wire from ds18b20 are incompatible. So you should create a new issue for ds18b20, if you want it to be supported. Maybe you could try a library, that should be supported and mention it there. (e.g. https://github.com/timofurrer/w1thermsensor)

https://github.com/patvdleer/pi-mqtt-gpio/commit/f701a239c9a65804ce4c4358569e4a510f452c68

me too need supporto for DS18B20
+1

Me too and even multi sensor config - multiple on one line as in Tasmota sonoff firmware. I have in plan i2c bus in my house and I have few rooms to check temperature and many open/close / motion  sensors. To extend range I’ll use this:
https://www.sparkfun.com/products/14589

+1

Is this happening ?

Should be fixed with PR above


 However, Go 1.18 introduced the Go workspaces concept that is perfect for our situation.
How Has This Been Tested?

There are two ways to check if this works:

On the top directory, issue some of the workspace aware commands such as go mod graph and see how it successfully lists the dependencies of the sub-module cli.
Open the repo in GoLand or Intellij and see how it correctly recognizes the cil sub-module.

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/close


Add initial favicon to index.hbs, branding and config updates as needed

Branding on web-ui is simpler than on webadmin.  All of the branding
files need to follow the same path names.  This lets us pre-populate
the favicon with an expected path.

branding code (in `src/index.js) has been updated so it only creates
new link elements if they don't already exist.

Webpack configs for HtmlWebpackPlugin no contain the "public path"
of the app.  The template prefixes this path on the favicon path
so it works on both the dev server and in a production deploy.

Fixes: https://github.com/oVirt/ovirt-web-ui/issues/1206

ci test

LGTM


get rid of github

IMO using github makes the bot painful to test.
How about installing a light git daemon so the bot is self contained on the server and the bot is turned into an irc bot to accept votes on pull requests?

only problem is most people haven't used IRC since the 90's :)

But IRC will be around long after github, number of users on freenode is still growing :)
I guess using something like ansible would make the project a lot easier to maintain since constributors are in control of the server and probably will want to also install external tool.

I have mixed feelings with this, as it will, for sure, draw people out of this idea. On the other hand, it could enhance democracy in the server. :D
Github provides a nice way of reviewing changes before voting too.

I think GitHub is essential to get the most contributions possible. Most developers should have a GitHub account.
This way it is also a tool to learn GitHub workflows and maybe leads to more contributions to open source projects (on github) in general.
I could live with another, more open system, that is also easy to use like GitLab or Gogs.

i think the point is to keep the project accessible. So far nothing is happening -let's make it interesting first


Print dim text with dim color without concrete color

This aims to fix #2945. The control code 2 means dim and it will be printed with suitable color on various color schemes, including Solarized Dark.

Coverage increased (+0.04%) to 89.062% when pulling 53d0266e7269edb53e0c197a6bcc1961fbc9a8e2 on piroor:fix-invisible-dim-text into 075bd51906b828812b320f33cd1c7fa60d1702f1 on mochajs:master.


Windows: Update go-winio to 0.3.5

Signed-off-by: John Howard<EMAIL_ADDRESS>Updates go-winio to v0.3.5. This contains a critical bug fix for the 10B release.
@jstarks @friism @dmp42 @mavenugo

LGTM

LGTM


Shows wrong information about line of code where exception occurred

When a mgem has 2 files to load:

mrblib/00.rb

module PocMod
  def add_foo
    self + "foo"
  end
end

String.send :include, PocMod # L6

mrblib/01.rb

module PocMod2
  def add_bar
    self + "foo"
  end
end

class String
  include PocMod2
end

The mgem initializer process loads files in order 00.rb -> 01.rb.
This time L6 @ mrblib/00.rb makes NoMethodError (because mruby-metaprog is splitted). But with conf.enable_debug, exception info shows that L1 @ mrblib/01.rb has an error.
$ ./mruby/bin/mruby -e '1 + 1'
trace (most recent call last):
        [0] /usr/local/ghq/github.com/udzura/mruby-pocs/mruby-poc-2/mrblib/01.rb:1
/usr/local/ghq/github.com/udzura/mruby-pocs/mruby-poc-2/mrblib/01.rb:1: undefined method 'send' (NoMethodError)

If you add extra 7th line to 00.rb, mruby shows that error is occurred in L7 @ mrblib/00.rb. This looks that unnecessary 1 line is added to exception info than the line where real exception occurred.
This is undesirable to developers.
mruby revision
a690aef8d3219e3123822e741e2bb7c97220425c
Build environment

macOS 10.13.6(17G65) using Apple LLVM version 10.0.0 (clang-1<IP_ADDRESS>)
Ubuntu Bionic, using gcc version 4:7.3.0-3ubuntu2.1

$ uname -a
Linux foo.jp 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

PoC code:
https://github.com/udzura/mruby-pocs/tree/master/mruby-poc-2

Thanks!!


feat!: Add support for Outposts, remove node security group, add support for addon preserve and most_recent configurations

Description
List of backwards incompatible changes

Minimum supported version of Terraform AWS provider updated to v4.32 to support latest features provided via the resources utilized.
Minimum supported version of Terraform updated to v1.0
Individual security group created per EKS managed node group or self managed node group has been removed. This configuration went mostly un-used and would often cause confusion ("Why is there an empty security group attached to my nodes?"). This functionality can easily be replicated by user's providing one or more externally created security groups to attach to nodes launched from the node group.
Previously, var.iam_role_additional_policies (one for each of the following: cluster IAM role, EKS managed node group IAM role, self-managed node group IAM role, and Fargate Profile IAM role) accepted a list of strings. This worked well for policies that already existed but failed for policies being created at the same time as the cluster due to the well known issue of unkown values used in a for_each loop. To rectify this issue in v19.x, two changes were made:

var.iam_role_additional_policies was changed from type list(string) to type map(string) -> this is a breaking change. More information on managing this change can be found below, under Terraform State Moves
The logic used in the root module for this variable was changed to replace the use of try() with lookup(). More details on why can be found here

Added

Support for setting preserve as well as most_recent on addons.

preserve indicates if you want to preserve the created resources when deleting the EKS add-on
most_recent indicates if you want to use the most recent revision of the add-on or the default version (default)

Modified

cluster_security_group_additional_rules and node_security_group_additional_rules have been modified to use lookup() instead of try() to avoid the well known issue of unkown values within a for_each loop
block_device_mappings previously required a map of maps but has since changed to an array of maps. Users can remove the outer key for each block device mapping and replace the outermost map {} with an array []. There are no state changes required for this change.
node_security_group_ntp_ipv4_cidr_block previously defaulted to ["<IP_ADDRESS>/0"] and now defaults to ["<IP_ADDRESS>/32"] (Referenc: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html)
node_security_group_ntp_ipv6_cidr_block previously defaulted to ["::/0"] and now defaults to ["fd00:ec2::123/128"] (Referenc: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html)
create_kms_key previously defaulted to false and now defaults to true. Clusters created with this module now default to enabling secret encryption by default with a customer managed KMS key created by this module
cluster_encryption_config previously used a type of list(any) and now uses a type of any -> users can simply remove the outer [...] brackets on v19.x

cluster_encryption_config previously defaulted to [] and now defaults to {resources = ["secrets"]} to encrypt secrets by default

cluster_endpoint_public_access previously defaulted to true and now defaults to false. Clusters created with this module now default to private only access to the cluster endpoint

cluster_endpoint_private_access previously defaulted to false and now defaults to true

The addon configuration now sets "OVERWRITE" as the default value for resolve_conflicts to ease addon upgrade management. Users can opt out of this by instead setting "NONE" as the value for resolve_conflicts
The kms module used has been updated from v1.0.2 to v1.1.0 - no material changes other than updated to latest

⚠ See UPGRADE-19.0.md for full list of changes and upgrade guidance
Motivation and Context

Add support for latest EKS features provided by the AWS provider such as Outposts support and addition addon configuration settings
Add support for Terraform AWS provider v4.x feature releases
Resolves #1800
Resolves #1908
Resolves #2053
Resolves #2054
Resolves #2261
Resolves #2264
Resolves #2273
Resolves #2281

Breaking Changes

Yes, see UPGRADE-19.0.md for full list of changes and upgrade guidance

How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

FYI - we are validating deployment of EKS on Outposts in local mode and further changes may be added

bug found in provider, converting to draft until fixed and supported https://github.com/hashicorp/terraform-provider-aws/issues/27560

This PR is included in version 19.0.0 :tada:


Fix documentation typo

Hey!
The docs refer to Rollbax.Reported.Standard, but that doesn't exist. I think you meant Rollbax.Reporter.Standard

Yes we did :) Great catch @capablemonkey, thanks! 💟


Warn users when navigating away with the terminal window open

https://bugzilla.redhat.com/show_bug.cgi?id=1325761

Browser support for onbeforeunload: https://developer.mozilla.org/en-US/docs/Web/API/WindowEventHandlers/onbeforeunload
@jwforres PTAL

The message doesn't appear when navigating back to another page in the app (but we delete the pod automatically in that case).

OK so won't be prompted on mobile it sounds like, but I think that's OK, this is just a best effort to try to get you to clean it up.

Updated message.


Support advanced ND scatter/reduce operations

Proposal
Support operations that scatter updates into a tensor with the following requirements:

Support a reduction with overlapping values (e.g. min, max, sum)
Supports default value tensor to also consider in the reduction
Supports ND updates & indices

Essentially, support tensorflow's tensor_scatter_nd_* operations, like:

tf.tensor_scatter_nd_update
tf.tensor_scatter_nd_max
tf.tensor_scatter_nd_min

Design discussion
API design
Currently, there is already a keras.ops.scatter_update function. This only supports a default value of 0 for the tensor, and doesn't support reductions.
Option 1: Upgrade keras.ops.scatter_update to take in optional tensor and reduction arguments.
Option 2: Create a dedicated tensor_scatter_nd api for these new functions.
Technical implementation
Overall the technical implementation is straightfoward, just flatten indices to the 1D case and invoke the segmentation functions of each backend (e.g. segment_max for TF and scatter_reduce for torch).
Implementation plan
I have already implemented a tensor_scatter_nd function for Nuro's internal use and it works well for all our cases (and is XLA compatible for all backends). Once we settle on a design, I can upstream the implementation.

cc @haohuanw

@fchollet let us know which option you prefer on these ops. i think scatter_update is closer to what jax and torch has


No files found

Since a while ago I have been facing this problem when I try to create a barrel:

Hi @roadieroundup ,
The information you present is very minimal and may lead you to think that the extension is not working.
If I had to guess, you are using NextJS (or fork) and the issue only appears in folders that contain the characters '[' or ']' in their name.
This is a known bug that I have been fighting with for months but have not been able to come up with a solution and it is actually part of a function within the VSCode Core itself.
I am sorry for the inconvenience and if it is the case I invite you to try to create the files manually in this type of folders or try with another extension since what you are looking for is the comfort as a development experience.

Hi @ManuelGil
Which additional information do you need?
I'm using vite with react and the error appears in any folder with .jsx files

In order to recreate your issue, I would like to know first the configuration you have of the extension for this project. For example:
{
  "autoBarrel.language.defaultLanguage": "JavaScript",
  "autoBarrel.files.disableRecursiveBarrelling": false,
  "autoBarrel.files.includeExtensionOnExport": ["js", "jsx"],
  "autoBarrel.files.ignoreFilePathPatternOnExport": ["**/*.spec.*", "**/*.test.*"],
  "autoBarrel.files.keepExtensionOnExport": false,
  "autoBarrel.files.detectExportsInFiles": false,
  "autoBarrel.files.exportDefaultFilename": "filename",
  "autoBarrel.formatting.excludeSemiColonAtEndOfLine": true,
  "autoBarrel.formatting.useSingleQuotes": true,
  "autoBarrel.formatting.endOfLine": "crlf",
  "autoBarrel.formatting.insertFinalNewline": false,
}

I'm also getting this error. Is there a better way to get debug info.
The only additional information I have is this worked once, and then stopped. I've tried all the settings, and nothing works.
I set the following in settings.json
    "autoBarrel.language.defaultLanguage": "JavaScript",
    "autoBarrel.files.disableRecursiveBarrelling": false,
    "autoBarrel.files.includeExtensionOnExport": ["js", "vue"],
    "autoBarrel.files.ignoreFilePathPatternOnExport": ["**/*.spec.*", "**/*.test.*"],
    "autoBarrel.files.keepExtensionOnExport": false,
    "autoBarrel.files.detectExportsInFiles": false,
    "autoBarrel.files.exportDefaultFilename": "filename",
    "autoBarrel.formatting.excludeSemiColonAtEndOfLine": false,
    "autoBarrel.formatting.useSingleQuotes": true,
    "autoBarrel.formatting.endOfLine": "lf",
    "autoBarrel.formatting.insertFinalNewline": true,

I removed this line:
    "autoBarrel.files.ignoreFilePathPatternOnExport": ["**/*.spec.*", "**/*.test.*"],

It flashed a 'dont forget to update the file' message, but nothing happened.
vscode:
Version: 1.94.1 (user setup)
Commit: e10f2369d0d9614a452462f2e01cdc4aa9486296
Date: 2024-10-05T05:44:32.189Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

Is it possible you're not sanitizing folders on windows?

So it looks like you may want to update "findFiles" @ManuelGil/vscode-auto-barrel/blob/main/src/app/controllers/files.controller.ts
https://github.com/microsoft/vscode/blob/f287d2d847b29c4887f913f404c8ec4e84f4d61a/src/vs/workbench/api/common/extHost.api.impl.ts#L960
			findFiles: (include, exclude, maxResults?, token?) => {
				// Note, undefined/null have different meanings on "exclude"
				return extHostWorkspace.findFiles(include, exclude, maxResults, extension.identifier, token);
			},
			findFiles2: (filePattern: vscode.GlobPattern, options?: vscode.FindFiles2Options, token?: vscode.CancellationToken): Thenable<vscode.Uri[]> => {
				checkProposedApiEnabled(extension, 'findFiles2');
				return extHostWorkspace.findFiles2(filePattern, options, extension.identifier, token);
			},
			findFiles2New: (filePattern: vscode.GlobPattern[], options?: vscode.FindFiles2OptionsNew, token?: vscode.CancellationToken): Thenable<vscode.Uri[]> => {
				checkProposedApiEnabled(extension, 'findFiles2New');
				return extHostWorkspace.findFiles2New(filePattern, options, extension.identifier, token);
			},

This is probably more helpful:
https://github.com/microsoft/vscode/blob/f287d2d847b29c4887f913f404c8ec4e84f4d61a/src/vs/workbench/api/common/extHostWorkspace.ts#L455 for findFiles
Is it possible exclude or maxResults are truncating results? The error suggests maxResults 0 is being passed. Otherwise, i get a different seemingly correct report when exclude is removed, but it still doesn't act.
The first time it worked was perfect, so it's odd it stops working. That would suggest some kind of cache is being hit, but I've restarted multiple times; uninstalled, reinstaleld. testing other plugins, etc.

unrelated issue? You set the default in constants:
export const EXPORT_FILENAME: string = 'index';

then in config:
this.exportDefaultFilename =
      config.get<string>('files.exportDefaultFilename') ?? EXPORT_FILENAME;

When I try to change it to index, it's an error, listing:

looks like this is set under schema/config.schema.json
		"autoBarrel.files.exportDefaultFilename": {
			"type": "string",
			"default": "filename",
			"enum": [
				"filename",
				"camelCase",
				"pascalCase",
				"kebabCase",
				"snakeCase"
			],
			"enumDescriptions": [
				"Use the filename as the default export.",
				"Use camelCase as the default export.",
				"Use PascalCase as the default export.",
				"Use kebab-case as the default export.",
				"Use snake_case as the default export."
			],
			"scope": "resource",
			"description": "Filename to use when exporting the default export."
		},

Doesn't appear related or how it might be to this issue, but curious.

Just tried uninstalling almost everything, and no change with default install.

Hi @disarticulate ,
Thank you so much for your comments. I made the changes you proposed and did some tests with a React project and a Vue project with the settings you suggested in the comments. In both cases the files were generated without problems.

This change is already published, please perform the relevant tests and share your results.
I look forward to hearing from you

bizarrely, the same error message after update:

The repo shows you're using the same findFiles, and I don't see how your code if it returns a list of promises is wrong.
As I noted above, there's two other findFiles functions on workspace that could be tried. It looks like they have a typed outputs and findFiles does not.
So, seems like it's an upstream issue. If you tried findFiles2 it'd look something like:
findFiles2(include,
        {
          exclude,
          options?.maxResults ?? Number.MAX_SAFE_INTEGER,
          followSymlinks: true,
          [...]
       }
)

Other than that, I dont see how it's failing to return files. they're all using _findFilesImpl method, so even the above still might return an empty array.
the private method is documented as:
	private async _findFilesImpl(
		// the old `findFiles` used `include` to query, but the new `findFiles2` uses `filePattern` to query.
		// `filePattern` is the proper way to handle this, since it takes less precedence than the ignore files.

So they suggest you move to the findFiles2 function, so I'd guess even if we reported this, they'd want you to try the findFiles2.

Sorry, I didn't pay attention to the functions, it was my mistake.
Actually that is the internal API of VSCode. To develop the extensions you install the @types/vscode npm package. The only function available is findFiles as it is in the official VSCode extensions API documentation.
I have performed the test on several computers, I suggest you try it on a different computer and share your results with me.
You can also clone this repository and test on your own how the extension works.

this seems to work! Great! I had to restart when updating the settings, but otherwise it's fine.
To get it to work with vue:

detect the exports
Keep extension on export

Thanks again!

...unfortunately, this appears to be a heisenbug. It's reverted to not finding files. It's definitely an upstream issue with how ever vscode handles files. I'm using the ssh plugin.

I'm going to have to spend a little more time checking what else might be affecting the performance of the extension.
I'll be reporting back if I find anything

So basically, I'm operating on 2-3 project workspaces. It works immediately upon installing. But after ignoring it for hours or whatever, and I need to create a new set of barrel files, it suddenly stops working.
It has become more reliable, but there must be some kind of cache inbetween invokes.


docs : screenshots exercise 30/10

There is 6 screenshot :
-namedroppers
-whois
-whoisology
-CRTF with CLI
-Cloudflair with CLI
-Cachedview.com
Checks

[ ] Your YAML file has required fields as listed in Specs
[ ] All checks have passed yaml-lint passed
[ ] You agree to contribute your work under MIT license

I also worked on the project


Can not find setup_ld_path.sh

I clone this project to my local. I can not find the setup_ld_path.sh according the ReadMe.md. Therefore, How can I build the project. Could you give more details about how to build  this project. Thanks.

Hi, thanks for raising this issue.
It seems the script got lost when moving repositories. I'm on mobile, but I'll add it when i have the time.
The lines you want are
export LD_LIBRARY_PATH="${ENNCLAVE_HOME}/lib:$LD_LIBRARY_PATH"
export PYTHONPATH="${ENNCLAVE_HOME}/lib:$PYTHONPATH"

Where ENNCLAVE_HOME is the path to your cloned repo.
Hope this helps :)

Ok，I know what's your means. I have anther questions. I get pull this repo, but I do not know how to build this project. Could you give me more details steps about how to build eNNclaves and how to use it. Thanks.

It's probably best if you look at our experiments repository. There you can download the pretrained models and the heading "performance evaluation" will tell you how to compile and use the code :)