Today after CoreOS from 1122.0.0 to 1151.0.0 updates elasticsearch cluster nodes could not start.
I have an aci image of https://hub.docker.com/_/elasticsearch/ built using docker2aci manually because in rkt v1.11.0 docker support was broken. So the issue is not in the docker conversion.
Test image is here which is almost the same as docker://elasticsearch:2.2.
With 1.11.0 it works. With 1.13.0 it doesn't.
What did you expect to see?
The image should launch with no arguments and output something.
What did you see instead?
The image does not start and exits immediately.

I know that it might be the problem with the image, but I didn't notice any breaking changes in rkt. It worked before. Now it doesn't, and unfortunately I have no idea how to fix it.
If I attach to image using rkt enter and start the same entrypoint command - it works. If I try to do the same via --exec or without any arguments - the container does not start.
More logs
image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.13.0
image: using image from local store for url docker://elasticsearch:2.2
stage0: Preparing stage1
stage0: Writing image manifest
stage0: Loading image sha512-fec6e8615d5e7f368f6acc1c017c52aabb9b02f8b79d0cbd42d4d767a44a94f1
stage0: Writing image manifest
stage0: Writing pod manifest
stage0: Setting up stage1
stage0: Wrote filesystem to /var/lib/rkt/pods/run/81bfc048-4195-4437-9dd2-acdfac7b44d3
stage0: Pivoting to filesystem /var/lib/rkt/pods/run/81bfc048-4195-4437-9dd2-acdfac7b44d3
stage0: Execing /init
networking: loading networks from /etc/rkt/net.d
networking: loading network flannel with type flannel
networking: loading network default with type ptp
Spawning container rkt-81bfc048-4195-4437-9dd2-acdfac7b44d3 on /var/lib/rkt/pods/run/81bfc048-4195-4437-9dd2-acdfac7b44d3/stage1/rootfs.
Press ^] three times within 1s to kill container.
systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS -ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Detected virtualization rkt.
Detected architecture x86-64.

Welcome to Linux!

Set hostname to <rkt-81bfc048-4195-4437-9dd2-acdfac7b44d3>.
[/usr/lib64/systemd/system/elasticsearch.service:23] Failed to parse system call, ignoring: chown32
[/usr/lib64/systemd/system/elasticsearch.service:23] Failed to parse system call, ignoring: fadvise64_64
[/usr/lib64/systemd/system/elasticsearch.service:23] Failed to parse system call, ignoring: fchown32
[/usr/lib64/systemd/system/elasticsearch.service:23] Failed to parse system call, ignoring: fcntl64
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: fstat64
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: fstatat64
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: fstatfs64
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: ftruncate64
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: getegid32
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: geteuid32
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: getgid32
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: getgroups32
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: getresgid32
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: getresuid32
[/usr/lib64/systemd/system/elasticsearch.service:24] Failed to parse system call, ignoring: getuid32
[/usr/lib64/systemd/system/elasticsearch.service:25] Failed to parse system call, ignoring: ipc
[/usr/lib64/systemd/system/elasticsearch.service:25] Failed to parse system call, ignoring: lchown32
#!/bin/sh
[/usr/lib64/systemd/system/elasticsearch.service:25] Failed to parse system call, ignoring: _llseek
[/usr/lib64/systemd/system/elasticsearch.service:25] Failed to parse system call, ignoring: lstat64
[/usr/lib64/systemd/system/elasticsearch.service:25] Failed to parse system call, ignoring: mmap2
[/usr/lib64/systemd/system/elasticsearch.service:26] Failed to parse system call, ignoring: _newselect
[/usr/lib64/systemd/system/elasticsearch.service:26] Failed to parse system call, ignoring: recv
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: send
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: sendfile64
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setfsgid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setfsuid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setgid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setgroups32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setregid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setresgid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setresuid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setreuid32
[/usr/lib64/systemd/system/elasticsearch.service:27] Failed to parse system call, ignoring: setuid32
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: sigreturn
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: socketcall
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: stat64
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: statfs64
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: truncate64
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: ugetrlimit
[/usr/lib64/systemd/system/elasticsearch.service:28] Failed to parse system call, ignoring: waitpid
[  OK  ] Created slice system.slice.
         Starting Create /etc/passwd and /etc/group...
[  OK  ] Listening on Journal Socket.
[  OK  ] Started Pod shutdown.
[  OK  ] Started elasticsearch Reaper.
[  OK  ] Listening on Journal Socket (/dev/log).
         Starting Journal Service...
[  OK  ] Created slice system-prepare\x2dapp.slice.
[  OK  ] Started Create /etc/passwd and /etc/group.
[  OK  ] Started Journal Service.
         Starting Prepare minimum environment for chrooted applications...
[  OK  ] Started Prepare minimum environment for chrooted applications.
[  OK  ] Started Application=elasticsearch Image=registry-1.docker.io/library/elasticsearch.
[  OK  ] Reached target rkt apps target.
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Container rkt-81bfc048-4195-4437-9dd2-acdfac7b44d3 exited successfully.

Thanks for the report, and sorry for breaking your setup. We're steadily proceeding in adding more isolation layers and providing sane defaults so that they can be turned on by default, and sometime this require new tweaks in existing setups.
For your specific case:

what is the returned exit value here and what does rkt status says about the exited pod?
can you please also share the entire rkt run command-line?
can you please share journal entries from this pod run?
the failed to parse... is a benign debug warning that will soon go away, see https://github.com/coreos/rkt/issues/2843#issuecomment-234038362
the middle-air-hanging #!/bin/sh sounds suspicious, and I think it is not coming from rkt itself
docker support should be good again, can you test against the official image? (so that if it needs changes, we can report to ES directly)
just for checking if this breaks due to a security feature, can you please test with the new runtime --insecure-options flags?

Regarding the exit code... Thats another unexpected thing. Along with elasticsearch I run a sidekick. The elasticsearch app exited with status 0, but the pod remained. And its status was running in rkt list. Thats probably because the sidekick app was still running. and I could rkt enter this pod, the filesystem and other namespaces are there, just no process for the app, only the sidekick. Is that expected?
But I've never checked exit codes in previous versions of rkt so I'm not sure if thats a bug.
The full commandline is huge due to various volume mounts, but the minimal version that doesn't work:
Working gist
Not working gist
--insecure-options=image,seccomp does indeed help, and it works with the official sudo rkt run --debug --insecure-options=image,seccomp docker://elasticsearch:2.2
But what exactly wrong with the image, or is it just because the image has systemd 215 inside?

I think the issue is not a regression and could be closed if it is indeed just a security flaw of the image itself.

The problem you are seeing here is because ES wants to setup its own seccomp filter (fine), but before doing that it does a bit of magic probing (ok-ish) by calling random syscalls and passing garbage arguments (uhm). This is getting your application killed, and there is no sane way to support/encourage that behavior.
What you could do is either convince ES not to do it (maybe they have a config switch for that), or tune seccomp isolator to return an ENOSYS as expect there, via --seccomp mode=retain,errno=ENOSYS,@rkt/default-whitelist.

It should kill the application. That in turn should halt the pod. Which is not what's happening here, you are right.
From what I'm seeing, even when our seccomp filter blocks ES, it is not being abruptly killed but it cleanly exit instead. This (correctly) doesn't halt the pod, as there are other applications still running in the pod. My guess is that ES has some broad signal handler and exit cleanly (uhm) on SIGSYS.


When "enable" parameter is "false" the VS does not appear in WebUI or bigip.conf

Environment

Application Services Version: 3.31.0
BIG-IP Version: 15.1.4

Summary
I create an http virtual server with an AS3 declaration (parameter "enable" is true by default).
I want to disable the VS, so I use an AS3 declaration like this:
[{
"op": "add",
"path": "/TR1/VIP-NTRZSMU001-TR1-443001/VIP-NTRZSMU001-TR1-443001/enable",
"value": false
}]
With this declaration the VS is disabled and when I use the GET method to retrieve the VS declarations I can see it with the parameter "enable" to "false".
My problem is that when the parameter "enable" is false I don't see anymore the virtual server in WebUI or in the file bigip.conf.
I use a tool that retrieves VS informations (address, pool members, state, etc.) with snmp get requests. As the VS doesn't appear in the configuration I can't see it in my tool.
Steps To Reproduce
Steps to reproduce the behavior:

Create a VS
Submit the following declaration:

[{
 "op": "add",
 "path": "/TR1/VIP-NTRZSMU001-TR1-443001/VIP-NTRZSMU001-TR1-443001/enable",
 "value": false
}]

Expected Behavior
When I disable a VS with tmsh command "modify ltm virtual  disabled" I can see this VS in the WebUI and in the bigip.conf (with the state disabled)
When I disable a VS with AS3 I want to have the same behavior.
Actual Behavior
When I disable a VS with AS3 I don't see it in the WebUI and in the bigip.conf (with the state disabled)

This is actually working as intended based on the original design of AS3. AS3 is "disabling" the VS by removing it from the configuration. I am changing this to a feature request to allow control over the virtual server enabled/disabled property.

@cnicolorange In order to help us better understand your use case, could you elaborate on why the current behavior of removing the ltm virtual configuration does not work for you?

Created Jira task AUTOTOOL-3294 for PM tracking

Use case provided in duplicate issue #603:

The use case is to disable the VIP without removing the config from BIG-IP, so that a BIG-IP admin can quickly re-enable the VIP if needed via the GUI. Re-adding the VIP using AS3 can potentially cause significant delay and unnecessary down time.

Changing the state of an AS3 configured item via the GUI is not advised as this creates a divergence between the declared state and the existing state. If the declaration is re-applied, those manual changes will be undone.

Hello,
I answered  a few days ago but I don't see it in the issue.
I use a tool that retrieves VS informations (address, pool members, state, etc.) with snmp get requests. As the VS doesn't appear in the configuration I can't see it in my tool.

provided a pre-release build AS3 3.39.0 build 4

This issue was resolved in the 3.39.0 release.


Update README.md

Added a contribution guide.

We should add a licence if we have a contribution guide

It might be useful to have dev dependencies ¯_(ツ)_/¯


Format multiple trailing closures.

When a function call has multiple trailing closures, every closure is forced to wrap.

There are two potentially surprising things about the behavior here:

Unlike an if/else statement, which can be formatted like this if it would fit entirely on one line:
if foo { bar } else { baz }

...we do not allow the same thing to occur for multiple trailing closures at this time:
// this
foo(x) { bar() } label: { baz() }
// will always become
foo(x) {
  bar()
} label: {
  baz()
}

The forced break occurs after the closure signature { arg, arg, arg in‸ if it's present; otherwise, it occurs after the open brace. This lets the closure signature stay on the same line as the open brace if it fits, but it will still wrap (via the normal break that occurs here {‸arg, arg, arg in) if it wouldn't fit.
However, because the break after in‸ is forced, that means that if the break after {‸ also fires, then even a single-statement closure will have a line break after the signature, when regular closures otherwise wouldn't. In other words,
// possible
reallyLongFunctionName(x) {
  x in bar(x)
}

// NOT possible
reallyLongFunctionName(x) {
  x in bar(x)
} secondLabelThatIsAlsoLong: {
  y in baz(y)
}

// ...it becomes this:
reallyLongFunctionName(x) {
  x in
  bar(x)
} secondLabelThatIsAlsoLong: {
  y in
  baz(y)
}

I can live with (1); I don't think it's a huge problem because I imagine the number of function calls with multiple trailing closures that would fit entirely on one line are exceedingly rare to begin with, and I think in the case of multiple trailing closures it's more readable to have them wrapped anyway so that the label isn't hidden in the middle of the line.
I'm less happy about (2), since it's a weird inconsistency, but I'm not sure our current model is flexible enough to say "given {₁arg, arg, arg in₂, force break 2 only if we didn't already break at 1". It's almost like a reset, but not quite the same because we're not conditioning it on continuation line state.
@dylansturg Any ideas here?

Going to go ahead and merge this to get it into the 5.3 branch; I'll revisit improvements to the newline behavior above later.


Home Screen: Content Widget for latest Podcast Episode

Add a widget (under the Benefits Carousel) that shows the most recent Podcast.

To save time researching how the Google API works for YT I asked chat GPT how to quickly do this. The response was mind blowing.
Can be done easily.
https://chatgpt.com/share/4d768478-dd65-4fb8-afe9-a44f0c2862f9


The leaderboard is missing in https://paperswithcode.com/sota/speech-recognition-on-interspeech-2021-asr-mr

We found the leaderboard is removed recently by the official, thus we choose to close this issue for now.


Holes in simplified mesh

I tried a number of different "aggressiveness" settings to reduce this mesh by 50%.  In every case I ended up with these holes being created.  Is there something I can do to prevent this?  The original mesh is green and the simplified one is red.

I would guess that the wing and body are not connected.

I would guess that the wing and body are not connected.

I am closing this issue. This may be related to the resolved issue 24. If you wish to re-open this issue, please provide access to a mesh which demonstrates the issue. It is hard to resolve a problem if we can not replicate the issue.


Screen should not be centered in when there is no content

I see it too now. Weirddd

Oh. lol http://static.damonzucconi.com/_capture/QAYTf3ZyYi.png


Issue #593 Override operator+(n, iterator) in the iterator class

Changes include:

Override operator+(difference_type, const iter_impl&) in the iterator class

Add const qualifier in the member operator+(difference_type) function

Add test cases of the relevant issue

Coverage decreased (-0.03%) to 99.686% when pulling ed62129f8e2d2388e4c05d8de9d34ac197d09a2c on HenryRLee:iterator_arithmetic into 52adf3fd5b0b941d4a55e982ae803d968296e5fa on nlohmann:develop.

The travis test exceeded 10 mins time limit, but it seems that the other tests also took around 10 mins. Shall we extend the time limit a little?
As for the AppVeyor fail, I think it's a result of one previous PR before mine.
I really don't know what the coveralls is about. Is there a test report I can read?

The latest several commits are trying to fix the incorrect arithmetic operations in reverse iterator.
The changes include:

Change the implementation of the arithmetic operators to using the result from the base class (std::reverse_iterator<T>) directly
Change the incorrect test cases

Coverage decreased (-0.03%) to 99.686% when pulling 3aef1a582e929dfae7c8ca4da2dc03439eb6f26e on HenryRLee:iterator_arithmetic into 52adf3fd5b0b941d4a55e982ae803d968296e5fa on nlohmann:develop.

Coverage decreased (-0.03%) to 99.686% when pulling e42db27d6d90d5ab470ad392befa595277e0dd97 on HenryRLee:iterator_arithmetic into 52adf3fd5b0b941d4a55e982ae803d968296e5fa on nlohmann:develop.

The exception message checking has been commented out. Although most compilers implements the operator[] of reverse iterator using operator+, some are still using [] from the original iterator class. That makes the exception message unpredictable.

The other commit is adding some missing test cases for the n + iter operator.
It explicitly calls the iterator constructor during the checking, otherwise the check macro doesn't understand the expression. In normal uses, the iterator constructor can be omitted.

Coverage remained the same at 99.721% when pulling 0c2ed00ebe1b1c8f289c4131cdc915979e8c5095 on HenryRLee:iterator_arithmetic into 52adf3fd5b0b941d4a55e982ae803d968296e5fa on nlohmann:develop.

Coverage decreased (-0.0003%) to 99.72% when pulling daea213b44135f63409136bbd20cfae2f63b1aa6 on HenryRLee:iterator_arithmetic into 52adf3fd5b0b941d4a55e982ae803d968296e5fa on nlohmann:develop.

@HenryRLee Could you please merge the current develop branch so the AppVeyor tests have a chance to succeed?

Coverage decreased (-0.0003%) to 99.721% when pulling c98169d0d500e2a5f209c58b9e26f6d53787b782 on HenryRLee:iterator_arithmetic into 1a9d76679a3f41a038a89742fba29d81ee24ce82 on nlohmann:develop.

Coverage decreased (-0.0003%) to 99.72% when pulling 6661ec755bb6d0f0495774148ce3dc837703a5fa on HenryRLee:iterator_arithmetic into 92ef19696a18187112512b8361b822d817d01e95 on nlohmann:develop.

Coverage decreased (-0.0003%) to 99.722% when pulling e12c2ee6a882b97928bdc2376f19e33808da4e93 on HenryRLee:iterator_arithmetic into 52f934cbbf4f99eceb59b28fe9c194e17431ca1e on nlohmann:develop.

Hi Niels, I think this PR is ready for review. This one is supposed to be bug fixing and adding missing operators. As for the improvement in #593, I can create another PR some other time if that's needed.

Thanks a lot. We shall continue the discussion in #593.

Thank you as well.


Bug/221 conn module lease times

Resolves Issue: https://github.com/google/testrun/issues/221

Convert DHCP lease times to local time zone before expiration time calculated
Add max wait time when waiting for lease expiration

@jhughesbiot We want to merge this into v1.1.1 branch but having changing the base, it seems to have brought across all of the dev commits so far. Could you see what the issue might be?

Because it's branched from dev originally as usual process.  If we want to patch just this release I'd have to branch off of that first and then manually make these changes again.


Update boost-iostreams to the same style as the other Boost ports.

Fixes #4468. I think.

I see a failure in the cartographer port on x64-windows and x86-windows.  It has a dependency on boost-iostreams.

@chrullrich, could you also update CONTROL revision in https://github.com/Microsoft/vcpkg/blob/master/ports/boost-iostreams/CONTROL?
See more information in https://github.com/Microsoft/vcpkg/blob/master/docs/maintainers/control-files.md

@ras0219-msft, you mentioned the other day that there was somthing about boost-iostreams that made it unique so you added the CMakeLists.txt.  Could you remind me what that was?  It was added for boost 1.67 and I am wondering if it still applies to 1.69 and also if it is related to the cartogropher port failures in this PR.

@chrullrich Thanks for the PR; the reason we have a separate style for this library compared to the other boost libraries is because:

The iostreams build is relatively simple (doesn't have complex assembly code or otherwise)
.. except for dependencies. We were unable to get boost build to reliably detect the dependencies, whereas it is trivial for CMake to do so. Therefore, rewriting the buildsystem in CMake is the best option available.


4-dotnet6-appservice image tag points to v4.3.2, not v4.5.2

Please can you remove 4-dotnet6-appservice tag or update it to point to the latest image?  It still currently seems to point to v4.3.2 image, not the real latest (v4.5.2 at time of writing).  We followed online documentation to use this image tag, and left us with several months of vulnerabilities in the image.

Functions Runtime 4.5.2 image that have latest dotnet SDK have been released. Above tags updated.


Keep legend visible in ID timeline view to allow event type filtering in both views.

Test notes:

The event type legend is visible in both the overall and ID views.

Confirmed that the event type legend is visible in both the overall and ID views in all browsers and that clicking on and off the various event types filters the table as expected.


lineScatter config file

https://github.com/USGS-R/smwrGraphs/blob/master/inst/doc/LineScatter.pdf
Split out from #5

#371
Will need xaxs and yaxs modified once the 's' option is included

See #358


Wrong active dots calculation

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Create a carousel with 5 items
Pass following props:

<Carousel
  ...
  dots
  slidesPerPage={2}
  slidesPerScroll={2}
>

Keep changing active slides
Notice the order of active dots (it's repeatable 1, 3, 5, 2, 4)

Expected behavior
Probably active dots should be calculated differently for this kind of situation.
Screenshots

Desktop (please complete the following information):

OS: [macOS 10.14.6]
Browser [Chrome]
Version [79.0.3945.88]

IssueHunt Summary

Backers (Total: $0.00)
Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

Note for others the infinite and arrows props are vital for the reproduction.
<Carousel
  arrows={true}
  infinite={true}
  slidesPerPage={2}
  slidesPerScroll={2}
  value={...}
  slides={...}
  onChange={...}
/>

The issue is really "How to represent dots when the carousel is infinite" 🤔
The current implementation seems correct, the "active" slide is the most lefthand and the active sequence 1, 3, 5, 2, 4 would be expected.
@pierzchalatomasz How would you expect this interaction to be represented?

Hi @jamsinclair,
In this situation we have 5 scenes (I mean slides visible at one time) in the following order (where [1, 2] meaning scene with slides 1 and 2 etc.):

[1, 2]
[3, 4]
[5, 1]
[2, 3]
[4, 5]

I would expect that dots are calculated based on the index of scene instead of the first item in a current scene i.e. dots should be activated in the following order: 1 => 2 => 3 => 4 => 5 instead of 1 => 3 => 5 => 2 => 4.

@pierzchalatomasz Thanks for the great explanation 👌 . Interesting problem 🤔.

@pierzchalatomasz
After merging https://github.com/brainhubeu/react-carousel/pull/177, the order is the following:
1: [1, 2]
2: [2, 3]
3: [3, 4]
4: [4, 5]
5: [5]

http://g.recordit.co/UIhO3LMF7w.gif
So I would change only the end to be:
5: [5, 1]

What do you think?

I think that we should divide the amount of dots by slidesPerScroll by default. We may also add props to dots to control it.

I did a research and indeed this is an important bug.
We should correct the dots' behavior. How it should work:

number of dots should be equal to the number of slides divided by slidesPerScroll property and rounded up
if we have the rest from division. On the action (e.g. clicking the arrow, drag the slide) on the last slides, we should scroll only the remaining ones.
if we have the rest from dividing and infinite mode we should behave in the same way like in point 2

So...this is a major problem, I get it (and agree).
Any update on that? This is pretty important stuff...
Any workaround that makes it work?


Way Too High Virtual Memory Usage

When I use vscode, it accumilates way to much virtual memory (pagefile). I've tested this on 3 machines (Windows 7 and 10) and the issue still persists. I know its from VSCode because the virtual memory only goes up when using it. I've made about 56 GB of virtual memory for windows and VSCode uses up the memory in hours.
Does this issue occur when all extensions are disabled?: Yes

VS Code Version: latest
OS Version: Windows 7

Steps to Reproduce:

Open a workspace
Wait a little while (30-64 minutes)

/needsPerfInfo

Thanks for creating this issue regarding performance! Please follow this guide to help us diagnose performance issues: https://github.com/microsoft/vscode/wiki/Performance-Issues
Happy Coding!

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


fast-deep-equal/react not found

I get a MODULE_NOT_FOUND error when importing it as per README. I see no react folder in node_modules. Maybe it was not published?

indeed!

Is there a reason why it's mentionned as something that can be used from this package ? I'm a little confused - Thank for the package buddy 😉

Sorry, don’t understand the questions.... What is mentioned?

Sorry there for the typo!
I presume it can be used in "react land", but I'm getting the same error, is there anything that else that needs to be done in order to get it working I did
npm install fast-deep-equal
And expected it to work  - there's probably something I'm missing
There might be something I'm missing


Liqui - LiquiAdapters.adaptTrade uses trade ID for order ID

adaptTrade passes in the String.valueOf(tradeId) when it should be using the order ID field in the provided liquiTrade parameter.

defunct exchange


rake initialize assumes postgresql database is running

Couldn't create database for {"adapter"=>"postgresql", "encoding"=>"unicode", "database"=>"xing_app_dev", "pool"=>5, "host"=>"<IP_ADDRESS>"}
could not connect to server: Connection refused
Is the server running on host "<IP_ADDRESS>" and accepting
TCP/IP connections on port 5432?
It might be more prudent to assume we'll first set up a sqlite database and transition to something like mysql or postgresql later.

Thanks for the input.   However, the primary purpose of rake initialize is to create and migrate a database, which can't happen unless your RDBMS is running.
That said, if you don't want to use postgresql, you don't need rake initialize.  Pretty much all it does is create an initial set of DB tables for users, create, and migrate your DB - just a five minute convenience for typical projects.  If you'd like to start with SQLite or any other non-PG database, you can edit backend/config/database.yml like any other rails project and use it however you like, and simply skip that particular rake task.  It doesn't do anything magical.
As for the SQLite option -- it's possible a future version of Xing will support that. Though to be honest, I
(and the other authors of Xing) have never understood that particular usage pattern. We tend to be heavy users of advanced PostgreSQL column types (HSTORE, JSONB, etc.) and since the cost of leaving a postgresql server running on a workstation is close to zero, we don't really see the advantage of developing against a different database that you'll have to change before production anyway. But YMMV, and if that works for you -- cool.  We will look at supporting it in a future revision.

I've added a note to this effect to the super-fast-start page.


MessageBird\Objects\Conversation\Message miss 'from' field

As title, it only as 'to' field, is there any reason for this?

Closing this as part of the issue cleanup.


An empty MiningSchema is a deviation from the PMML standard

First, I am a big fan of the JPMML project, and I'm excited to observe its growth during the last years.
Recently, I tried jpmml-sklearn to convert an XGB model to its PMML format. Following, I add the Python script. I noticed that some of the tree models have an empty MiningSchema. An empty MiningSchema is a deviation from the PMML standard.
Here is the format of MiningSchema specified by the standard (https://dmg.org/pmml/v4-4-1/MiningSchema.html):
<xs:element name="MiningSchema">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="Extension" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element maxOccurs="unbounded" ref="MiningField"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

Based on XML Schema guideline, the default value of minOccurs is 1 (https://www.w3.org/TR/xmlschema-0/#:~:text=The default value for both,not occur more than once.). Therefor, a MiningSchema must have at least one MiningField. We may file an issue on the Github page of JPMML.
It is correct that the tree models with empty MiningSchema have only a root node (no use of any input field), but they could still have defined MiningFields. In other words, a model can have defined inputs that are not used inside the model for prediction. To best of my understanding, a model as a black box in the PMML standard cannot be without any inputs; regardless of the fact how those inputs are utilized.
The Python script
from sklearn import datasets
import pandas as pd
import xgboost as xgb

iris = datasets.load_iris()
print(iris.target_names)
print(iris.feature_names)
print(iris.data[0:5])
print(iris.target)

data=pd.DataFrame({
    'sepal length':iris.data[:,0],
    'sepal width':iris.data[:,1],
    'petal length':iris.data[:,2],
    'petal width':iris.data[:,3],
    'species':iris.target
})
data.head()
from sklearn.model_selection import train_test_split

X=data[['sepal length', 'sepal width', 'petal length', 'petal width']]  # Features
y=data['species']  # Labels
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.3) # 70% training and 30% test
clf=xgb.XGBClassifier()
clf.fit(X_train,y_train)
y_pred=clf.predict(X_test)
from sklearn import metrics
print("Accuracy:",metrics.accuracy_score(y_test, y_pred))

from sklearn2pmml import sklearn2pmml, make_pmml_pipeline
pmml_obj = make_pmml_pipeline(clf)
sklearn2pmml(pmml_obj,"xgb_iris.xml")
print("Model exported as PMML successfully.Filename: xgb_iris.xml " )

I noticed that some of the tree models have an empty MiningSchema.

It's typically an indication of an over-fitted model. For example, when you're building a booster-style ensemble model, and specify an unreasonably large n_estimators value, then XGBoost typically resorts to "stuffing" the ensemble with empty decision trees until the n_estimators criterion is met.
An empty MiningSchema indicates a "data science problem", and shouldn't be ignored.

An empty MiningSchema is a deviation from the PMML standard.

Yes, it's a JPMML extension to the PMML standard:
https://github.com/jpmml/jpmml-model/commit/b30a7d757a95693d391a8d55eadcd61a1e743901
Getting this stuff there was hard work!
If you look at the generated org.dmg.pmml.MiningSchema class source code, then you will find that this extension is properly marked with an @org.jpmml.model.annotations.Optional(org.dmg.pmml.Version.XPMML) annotation.

Based on XML Schema guideline, the default value of minOccurs is 1

Yes, but I would argue that it's a mistake to make such a requirement (minOccurs > 1).
The JPMML relaxation does not invalidate the PMML specification in any way - all "canonical" PMML documents are 100% supported by the JPMML-Model library (and any other JPMML library along the stack).

To best of my understanding, a model as a black box in the PMML standard cannot be without any inputs; regardless of the fact how those inputs are utilized.

Then how would you implement a constant-prediction model?
What makes the following regression model illegal? Why can't it be represented in PMML?
<RegressionModel>
  <MiningSchema/>
  <RegressionTable intercept="3.14"/>
</RegressionModel>

BTW, what do you expet the JPMML-XGBoost library to do when the user passes it an XGBoost model object that contains empty decision trees? Should the SkLearn2PMML utility function throw an expection or something?
How would that situation be an improvement over the current situation?

Closing as "works as intended".

Thanks for your quick response.
First, I believe that a PMML producer should strictly follow the constraints of the standard. Otherwise, the whole purpose of the standard of being a shared medium among different producers and consumers would be compromised. IMHO, any extension should be solely made based on the guideline of the standard through the Extension element:
https://dmg.org/pmml/v4-4-1/GeneralStructure.html#xsdElement_Extension
In principal, a predictive model should identify its input field. In other words, a model that can be applied on any data is meaningless and misleading. Even a constant-prediction model must have MiningFields although they are not used by the model internally.
When the JPMML-XGBoost library receives an XGBoost model object that contains empty decision trees, I expect it to create TreeModel segments similar to what it does now, but instead of empty MiningSchema, having a MiningSchema with MiningFields from the higher level.

I believe that a PMML producer should strictly follow the constraints of the standard.

Talking about this JPMML extension specifically, then how does the empty MiningSchema element affect your application? What's the downside?
The extension is clearly labeled as such, and it only affects the JPMML library level.
If you validated the PMML document against the PMML XSD, then this extension would be easily caught and reported. Perhaps you should activate this in your application.

IMHO, any extension should be solely made based on the guideline of the standard through the Extension element

Can you give me an example about how you'd represent a constant-prediction decision tree or regression model using the Extension element.

In principal, a predictive model should identify its input field.

This predictive model does not take any input fields.

A model that can be applied on any data is meaningless and misleading.

Is your example XGBoost model "meaningless and misleading" then?
The SkLearn2PMML converter is doing its best to convert your XGBoost model into PMML representation. Garbage in, garbage out.

I expect it to create TreeModel segments similar to what it does now, but instead of an empty MiningSchema, having a MiningSchema with MiningFields comin from the higher level model, MiningModel in this case.

This decision tree model is not utilizing any of those inputs. Why should it declare them?

I believe that a PMML producer should strictly follow the constraints of the standard.

Talking about this JPMML extension specifically, then how does the empty MiningSchema element affect your application? What's the downside?

We don't really rely on JPMML for our work. We're adding support of PMML standard to Vertica database as both producer and consumer (https://www.vertica.com/docs/11.1.x/HTML/Content/Authoring/AnalyzingData/MachineLearning/UsingExternalModels/UsingPMML/UsingPMMLModels.htm).  Vertica provides a set of built-in distributed algorithms to train ML models on BigData. The trained models are archived in DB and can be used for in-DB scoring at scale. Nevertheless, Vertica users would be able to export these models to PMML to be used externally. Besides, the users would be able to import the PMML models they have trained externally into Vertica to enjoy its model management and scalable in-DB scoring.
We usually test our product against several third-party libraries, including JPMML, to make sure we have satisfied the promise of the standard of sharing models between PMML compliant applications.
We think JPMML is one of the most complete open source libraries. That's why we usually recommend it to our customers who want to bridge between their Python or R ML environment and Vertica. That said, we will feel better to know that JPMML fully complies with the standard.

The extension is clearly labeled as such, and it only affects the JPMML library level.
If you validated the PMML document against the PMML XSD, then this extension would be easily caught and reported. Perhaps you should activate this in your application.

IMHO, any extension should be solely made based on the guideline of the standard through the Extension element

Can you give me an example about how you'd represent a constant-prediction decision tree or regression model using the Extension element.

IMHO, you don't really need it. You can just add one dummy MiningField.
In contrast, I suggest you make an extension element for x-mathContext instead of making it an attribute of the TreeModel element. It is another deviation from the standard, but I think it is not as critical as an empty MiningSchema because it is not about the dataflow inside multiple models.

In principal, a predictive model should identify its input field.

This decision tree does not take any input fields.

A model that can be applied on any data is meaningless and misleading.

Is your example XGBoost model "meaningless and misleading" then?

I'm afraid that there is a misunderstanding here! A tree in which the root node is a leaf (you call it a constant-prediction decision tree) is a valid model as far as its input fields are defined; regardless of the fact that the values of the inputs have no impact on its prediction. A model without defined inputs implies that it can be applied on any data with any dimension and data types which is not compatible with the definition of an ML model in PMML.

The SkLearn2PMML converter is doing its best to convert your XGBoost model into PMML representation. Garbage in, garbage out.

I expect it to create TreeModel segments similar to what it does now, but instead of an empty MiningSchema, having a MiningSchema with MiningFields comin from the higher level model, MiningModel in this case.

This decision tree model is not utilizing any of those inputs. Why should it declare them?

Because it will comply with the PMML standard then. :)


Fix Docker command path

Docker command is not valid: cas-overlay/bin/run-cas.sh is relative to /cas-overlay and is being resolved to /cas-overlay/cas-overlay/bin/run-cas.sh file which does not exist.
This should be bin/run-cas.sh (which is resolved to /cas-overlaybin/run-cas.sh).
Steps to reproduce the issue:
docker run -p 8080:8080 apereo/cas
causes:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:296: starting container process caused "exec: \"cas-overlay/bin/run-cas.sh\": stat cas-overlay/bin/run-cas.sh: no such file or directory": unknown.
ERRO[0000] error waiting for container: context canceled

After this fix it works as expected.

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


Modify the batch and slurm scripts to support additonal per-subject parameters

A current limitation of both srun_fastsurfer and brun_fastsurfer is that it is not possible to define additional subject-specific parameters to run_fastsurfer.sh.
This PR adds the feature to add such options to both srun_fastsurfer and brun_fastsurfer.
In particular, brun_fastsurfer.sh  can have additional parameters (format =,). This also passed through to srun_fastsurfer, for example:
Example 1:
--subject_list_delim "," --subject_list_awk_code_args '\$2 ",--vox_size," \$4'
to implement from the subject_list line
subject-101,raw/T1w-101A.nii.gz,study-1,0.9
to
--sid subject-101 --t1 <data-path>/raw/T1w-101A.nii.gz --vox_size 0.9
Example 2:
--subject_list_delim "," --subject_list_awk_code '\$2' --subject_list_awk_code_args '\$4,--asegdkt_segfile,\$3'
to implement from the subject_list line
4,sub_A1,mri/asegdkt.mgz,412463-t1.nii.gz
to
--sid sub_A1 --t1 <data-path>/412463-t1.nii.gz --asegdkt_segfile mri/asegdkt.mgz

The PR is tested and can be reviewed now.

Thanks for the PR, it's working well out of the box now.
I ran into two issues while testing:

I am not sure what is supposed to happen when a job crashes. Right now it seems like if the FastSurferCNN module crashes (e.g. QC doesnt pass) the slurm jobs become zombies, because the dependency is never met. Is this expected behaviour?
It would be great if the cleanup job is executed in any case, so we don't have to hunt down the jobs and files on the slurm cluster and cancel them manually.
The HPC work directory can not be modified while the processing is running because any files placed there would be deleted. We could instead check and remove the three folder created ("cases", "script", "logs", "images"). I think this only needs modifications in the check_hpcwork and make_cleanup_job functions.

I believe I found a bug - the surface pipeline can not run, because --parralel_subjects is passed to brun_fastsrufer.sh without argument.
Putting --parallel_subjects -1 for maximum parallelism https://github.com/Deep-MI/FastSurfer/blob/0d4dbb541fafc3f1cfdad9d90ce0d65dc359d94c/srun_fastsurfer.sh#L669 allows the surface pipeline to complete

--parallel_subjects is supposed to be a valid setting and equal to max.
I'll look into it.
With regards to your earlier comments.

Initially, if a job crashed, all jobs in following jobs were supposed to fail via slurm. (The dependency is never fulfilled). But this creates unwanted side-effects for the other cases that are merged to be processed in the same batch. So I implemented a monitoring file for successful completion of different stages, the subject_success file. So from then on, the expected behavior was that failed cases are skipped for failed prior steps. But I have not checked this recently, just when I implemented this.
Users are not supposed to modify/edit the work directory, so this is not really a concern. All data should be copied back in the cleanup script to the folder specified via --sd.
Also, you do not need to specify --work if $HPCWORK is set, as would be set on most clusters.

There seems to be a not missing https://github.com/Deep-MI/FastSurfer/blob/0d4dbb541fafc3f1cfdad9d90ce0d65dc359d94c/brun_fastsurfer.sh#L148.

I am a bit surprised about the zombification of jobs though. brun_fastsurfer is supposed to always return 0 (success)
https://github.com/Deep-MI/FastSurfer/blob/0d4dbb541fafc3f1cfdad9d90ce0d65dc359d94c/brun_fastsurfer.sh#L466
I'll have to read up on the slurm docs, whether a non-zero return code for a child process supercedes a zero return code of the mailing process.

1. Initially, if a job crashed, all jobs in following jobs were supposed to fail via slurm. (The dependency is never fulfilled). But this creates unwanted side-effects for the other cases that are merged to be processed in the same batch. So I implemented a monitoring file for successful completion of different stages, the subject_success file. So from then on, the expected behavior was that failed cases are skipped for failed prior steps. But I have not checked this recently, just when I implemented this.

I think this is broken atm, I can keep an eye on this when I run some batches with failing subjects and let you know what happens currently. IIRC the jobs stayed IDLE indefinetly with "dependency not met" (zombie processes), but I didn't look into it.

2. Users are not supposed to modify/edit the work directory, so this is not really a concern. All data should be copied back in the cleanup script to the folder specified via --sd.
   Also, you do not need to specify --work if $HPCWORK is set, as would be set on most clusters.

The issue is not that files used by the script cant be modified, but that the script esentially blocks the HCP work directory, so no other scripts can use it. (e.g. what if I want to also run freesurfer on slurm at the same time as fastsrufer). Why not only check and delete the folders that are actually used?
A workaround would be to set --work manually to a subfolder of $HPCWORK (which I didn't do yet, but might need to do in the future).

For proper scheduling between Jobarrays, there needs to be a dependency between in corresponding seg and surf tasks.

In case this pops up during testing, just FYI - I ran into an issues on line
https://github.com/Deep-MI/FastSurfer/blob/0d4dbb541fafc3f1cfdad9d90ce0d65dc359d94c/brun_fastsurfer.sh#L438
where there seemed to be some issue with the formatting of the srun commend. I did a quick and dirty workaround by building the command into a string and calling eval on it.

In case this pops up during testing, just FYI - I ran into an issues on line
https://github.com/Deep-MI/FastSurfer/blob/0d4dbb541fafc3f1cfdad9d90ce0d65dc359d94c/brun_fastsurfer.sh#L438
where there seemed to be some issue with the formatting of the srun commend. I did a quick and dirty workaround by building the command into a string and calling eval on it.

I don't particularly know what you are running into, but #438 identifies an issue in exactly that line, $seg_surg_only is empty. The question is what error you were getting. In #438 it was "unrecognized option" -- the empty string.

Currently, the default option for check_hpc_work is none, i.e. there is no check, if the directory is in fact empty, which can lead to unexpected deletion of files by the cleanup job.
Also, the cleanup job should just delete cases, logs, scripts, and images, not *.

I can confirm that slurm inherits the return code from job steps, i.e. if a srun call fails, for example a surface or a segmentation command, this interrupts the whole processing pipeline.
This can be avoided by manually setting the derived return code with sjobexitmod https://slurm.schedmd.com/job_exit_code.html.
It would probably be best to have a verbose error message at the end of the script, but always return 0, so proceeding tasks are always executed.


Prevent circular references (for comment/feedback)

Submitted for comments, feedback for general usefulness.
For my app I had issues serializing resources that link to each other. This would cause infinite recursion.
This PR leverages the context to block resources have already been serialized.

Friendly ping ⛵  What steps are required to move this forward?


The second option is available via the Copy vscode.dev Link command, which is in both the command palette and also in the line number context menu:

The second option is available via the Copy vscode.dev Link command, which is in both the command palette and also in the line number context menu:

The first option is not yet available.
Originally posted by @joyceerhl in https://github.com/microsoft/vscode-remote-repositories-github/issues/359#issuecomment-1690108570

The second option is available via the Copy vscode.dev Link command, which is in both the command palette and also in the line number context menu:

The first option is not yet available.
Originally posted by @joyceerhl in https://github.com/microsoft/vscode-remote-repositories-github/issues/359#issuecomment-1690108570

jeckpot sum:170000$
28.08.2023/08:00:00


Update TTD for Sepolia

PR Description
Update to the actual TTD for sepolia.
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

Another one! We're getting there


terraform init fails due to checksum mismatch

Description
terraform init fails when using ionoscloud provider in version 6.0.3
Expected behavior
terraform init works.
Environment
Terraform version:
Terraform v1.1.3
on linux_amd64

Provider version:
6.0.3

OS:
Linux 5.16.0-arch1-1

How To Reproduce
Create a main.tf with the following content
terraform {
  required_providers {
    ionoscloud = {
      source  = "ionos-cloud/ionoscloud"
      version = "= 6.0.3"
    }
  }
}

And run terraform init.
Error and Debug Output
2022-01-13T15:40:40.429+0100 [INFO]  Terraform version: 1.1.3
2022-01-13T15:40:40.429+0100 [INFO]  Go runtime version: go1.17.6
2022-01-13T15:40:40.429+0100 [INFO]  CLI args: []string{"terraform", "init", "-no-color"}
2022-01-13T15:40:40.429+0100 [TRACE] Stdout is not a terminal
2022-01-13T15:40:40.429+0100 [TRACE] Stderr is not a terminal
2022-01-13T15:40:40.429+0100 [TRACE] Stdin is a terminal
2022-01-13T15:40:40.429+0100 [DEBUG] Attempting to open CLI config file: /home/mv/.terraformrc
2022-01-13T15:40:40.429+0100 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2022-01-13T15:40:40.429+0100 [DEBUG] ignoring non-existing provider search directory terraform.d/plugins
2022-01-13T15:40:40.429+0100 [DEBUG] ignoring non-existing provider search directory /home/mv/.terraform.d/plugins
2022-01-13T15:40:40.429+0100 [DEBUG] ignoring non-existing provider search directory /home/mv/.local/share/terraform/plugins
2022-01-13T15:40:40.429+0100 [DEBUG] ignoring non-existing provider search directory /usr/local/share/terraform/plugins
2022-01-13T15:40:40.429+0100 [DEBUG] ignoring non-existing provider search directory /usr/share/terraform/plugins
2022-01-13T15:40:40.430+0100 [INFO]  CLI command args: []string{"init", "-no-color"}

Initializing the backend...
2022-01-13T15:40:40.430+0100 [TRACE] Meta.Backend: no config given or present on disk, so returning nil config
2022-01-13T15:40:40.430+0100 [TRACE] Meta.Backend: backend has not previously been initialized in this working directory
2022-01-13T15:40:40.430+0100 [DEBUG] New state was assigned lineage "f147b222-d793-cccc-a6f2-51fd3a8446af"
2022-01-13T15:40:40.430+0100 [TRACE] Meta.Backend: using default local state only (no backend configuration, and no existing initialized backend)
2022-01-13T15:40:40.430+0100 [TRACE] Meta.Backend: instantiated backend of type <nil>
2022-01-13T15:40:40.430+0100 [DEBUG] checking for provisioner in "."
2022-01-13T15:40:40.434+0100 [DEBUG] checking for provisioner in "/usr/bin"
2022-01-13T15:40:40.434+0100 [TRACE] Meta.Backend: backend <nil> does not support operations, so wrapping it in a local backend
2022-01-13T15:40:40.434+0100 [TRACE] backend/local: state manager for workspace "default" will:
 - read initial snapshot from terraform.tfstate
 - write new snapshots to terraform.tfstate
 - create any backup at terraform.tfstate.backup
2022-01-13T15:40:40.434+0100 [TRACE] statemgr.Filesystem: reading initial snapshot from terraform.tfstate
2022-01-13T15:40:40.434+0100 [TRACE] statemgr.Filesystem: snapshot file has nil snapshot, but that's okay
2022-01-13T15:40:40.434+0100 [TRACE] statemgr.Filesystem: read nil snapshot

Initializing provider plugins...
- Finding ionos-cloud/ionoscloud versions matching "6.0.3"...
2022-01-13T15:40:40.434+0100 [DEBUG] Service discovery for registry.terraform.io at https://registry.terraform.io/.well-known/terraform.json
2022-01-13T15:40:40.434+0100 [TRACE] HTTP client GET request to https://registry.terraform.io/.well-known/terraform.json
2022-01-13T15:40:40.637+0100 [DEBUG] GET https://registry.terraform.io/v1/providers/ionos-cloud/ionoscloud/versions
2022-01-13T15:40:40.637+0100 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/ionos-cloud/ionoscloud/versions
2022-01-13T15:40:40.823+0100 [TRACE] providercache.fillMetaCache: scanning directory .terraform/providers
2022-01-13T15:40:40.823+0100 [TRACE] getproviders.SearchLocalDirectory: failed to resolve symlinks for .terraform/providers: lstat .terraform: no such file or directory
2022-01-13T15:40:40.823+0100 [TRACE] providercache.fillMetaCache: error while scanning directory .terraform/providers: cannot search .terraform/providers: lstat .terraform/providers: no such file or directory
2022-01-13T15:40:40.823+0100 [DEBUG] GET https://registry.terraform.io/v1/providers/ionos-cloud/ionoscloud/6.0.3/download/linux/amd64
2022-01-13T15:40:40.823+0100 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/ionos-cloud/ionoscloud/6.0.3/download/linux/amd64
2022-01-13T15:40:40.929+0100 [DEBUG] GET https://github.com/ionos-cloud/terraform-provider-ionoscloud/releases/download/v6.0.3/terraform-provider-ionoscloud_6.0.3_SHA256SUMS
2022-01-13T15:40:40.929+0100 [TRACE] HTTP client GET request to https://github.com/ionos-cloud/terraform-provider-ionoscloud/releases/download/v6.0.3/terraform-provider-ionoscloud_6.0.3_SHA256SUMS
2022-01-13T15:40:41.173+0100 [TRACE] HTTP client GET request to https://objects.githubusercontent.com/github-production-release-asset-2e65be/319271388/f1a8b342-abb5-451f-888f-c27baf6d4424?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220113%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220113T144041Z&X-Amz-Expires=300&X-Amz-Signature=8a93897dcbbb6c81e1ee52c330c57cf0a0c6a449098f8a439eb99fed8db83ce4&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=319271388&response-content-disposition=attachment%3B%20filename%3Dterraform-provider-ionoscloud_6.0.3_SHA256SUMS&response-content-type=application%2Foctet-stream
2022-01-13T15:40:41.369+0100 [DEBUG] GET https://github.com/ionos-cloud/terraform-provider-ionoscloud/releases/download/v6.0.3/terraform-provider-ionoscloud_6.0.3_SHA256SUMS.sig
2022-01-13T15:40:41.369+0100 [TRACE] HTTP client GET request to https://github.com/ionos-cloud/terraform-provider-ionoscloud/releases/download/v6.0.3/terraform-provider-ionoscloud_6.0.3_SHA256SUMS.sig
2022-01-13T15:40:41.549+0100 [TRACE] HTTP client GET request to https://objects.githubusercontent.com/github-production-release-asset-2e65be/319271388/04d63215-7bae-4761-add2-ef09e6a3c79e?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220113%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220113T144041Z&X-Amz-Expires=300&X-Amz-Signature=97565988899b4d9dd075ae7fb8343330cd4167e4b175cdbe1cb01fd4b7b966c0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=319271388&response-content-disposition=attachment%3B%20filename%3Dterraform-provider-ionoscloud_6.0.3_SHA256SUMS.sig&response-content-type=application%2Foctet-stream
- Installing ionos-cloud/ionoscloud v6.0.3...
2022-01-13T15:40:41.690+0100 [TRACE] providercache.Dir.InstallPackage: installing registry.terraform.io/ionos-cloud/ionoscloud v6.0.3 from https://github.com/ionos-cloud/terraform-provider-ionoscloud/releases/download/v6.0.3/terraform-provider-ionoscloud_6.0.3_linux_amd64.zip
2022-01-13T15:40:41.690+0100 [TRACE] HTTP client GET request to https://github.com/ionos-cloud/terraform-provider-ionoscloud/releases/download/v6.0.3/terraform-provider-ionoscloud_6.0.3_linux_amd64.zip
2022-01-13T15:40:41.922+0100 [TRACE] HTTP client GET request to https://objects.githubusercontent.com/github-production-release-asset-2e65be/319271388/a9e253a5-2471-4881-ba54-f99bcd0245cb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220113%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220113T144041Z&X-Amz-Expires=300&X-Amz-Signature=0bc97dd2dd916095d8421f661116b2d5c52a076b479a12ca912ac00090e81b5d&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=319271388&response-content-disposition=attachment%3B%20filename%3Dterraform-provider-ionoscloud_6.0.3_linux_amd64.zip&response-content-type=application%2Foctet-stream

Error: Failed to install provider

Error while installing ionos-cloud/ionoscloud v6.0.3: checksum list has
unexpected SHA-256 hash
e045d94df346f00ea123df6457f5ff897302be04808380cc4253b582baaf4beb (expected
97a763fea021e452c3c09bc8942a58bf1654f1ed94f4abe08cd46bad6f63fd04)

Additional Notes

References

Should be fixed in version the latest version, 6.1.2.

Yes, it's fixed. Thanks


Status of Gtk version?

I'm rewriting Images now, ImageView comes after that is done.
I do have a Gtk-based viewer that I use privately, but it's a small thing that doesn't support much of the functionality of ImageView. If people really need something now I can post it, but I will not promise to support it---it's "take it as-is", add features or fix bugs yourself.

will the Gtk version supplant this Tk version?  either way, is it worth fixing these deprecations?
julia> using ImageView
WARNING: Base.WORD_SIZE is deprecated.
  likely near /Users/arthurb/.julia/v0.5/Tk/src/tkwidget.jl:269
WARNING: `@linux_only` is deprecated, use `@static if is_linux()` instead
 in depwarn(::String, ::Symbol) at ./deprecated.jl:64
 in depwarn(::String, ::Symbol) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in @linux_only(::Any) at ./deprecated.jl:500
 in include_from_node1(::String) at ./loading.jl:488
 in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in include_from_node1(::String) at ./loading.jl:488
 in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in eval(::Module, ::Any) at ./boot.jl:234
 in eval(::Module, ::Any) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in require(::Symbol) at ./loading.jl:415
 in require(::Symbol) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in eval(::Module, ::Any) at ./boot.jl:234
 in eval(::Module, ::Any) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in eval_user_input(::Any, ::Base.REPL.REPLBackend) at ./REPL.jl:64
 in macro expansion at ./REPL.jl:95 [inlined]
 in (::Base.REPL.##3#4{Base.REPL.REPLBackend})() at ./event.jl:68
while loading /Users/arthurb/.julia/v0.5/ImageView/src/display.jl, in expression starting on line 17

julia> Pkg.installed("ImageView")
v"0.1.20+"

julia> VERSION
v"0.5.0"

Thanks for fixing the deprecations!
It's a timely question, since the Images rewrite is almost to the finish line---before merging it to master, I plan to at least start on the ImageView rewrite in case I discover more changes that need to be made to support ImageView. My intention is that the Gtk version would supplant the Tk version. Is supporting both toolkits a priority?

supporting both is not a priority for me.  i just wanted to know whether it was worth the time to fix the deprecations.  went ahead and did it anyway because they bothered me.

The Gtk version is released.


Add the option to make a radio field inline.

Thanks!

Hi Kent,
Looks like this doesn't do things quite like Bootstrap wants. For inline radio buttons, the "radio-inline" class should be on the label, not the div. Having the classless div is unnecessary for inline radio buttons, but it doesn't hurt anything.
Desired visual output:

Current visual output:

Desired HTML output (different fields/labels from the visual example above):
<input type="radio" name="optradio">Option 1
<input type="radio" name="optradio">Option 2
<input type="radio" name="optradio">Option 3

Current HTML output:
<div class="radio-inline"<input type="radio" name="optradio">Option 1

<div class="radio-inline"<input type="radio" name="optradio">Option 2

<div class="radio-inline"<input type="radio" name="optradio">Option 3

Reference: http://www.w3schools.com/bootstrap/bootstrap_forms_inputs.asp

For now, I made a custom radioInline type that extends yours and uses a different template. These Formly Bootstrap templates are making my life a lot easier - thanks!

Feel free to makeapullrequest.com :-)


Add a WsTrustChannelFactory for getting a SecurityToken using WsTrust

Now, since there is work ongoing with WsTrust message serialization/deserialization, it would be good to get a WsTrustChannelFactory for the raw communication to a WsTrust server.

@gislikonrad this would be a good feature and would help us with a wstrust client.
Not sure where it fits in.

@gislikonrad this has been moved to WCF repo and is being completed.
see: https://github.com/dotnet/wcf and there is a current pull request.


Dropdown icon

  # 8 items with icon
  - Dropdown:
      label: Example 8
      hintText: Select something
      items:
        - {'iconname' : star , value : Red}
        - {'iconname' : star , value : Green}
        - {'iconname' : star , value : Blue}

@hamxa152 can you please fix your VCS so it doesn't automatically format the code. Now your code appears to have changes everywhere just because the formatting changed. Please fix that and checkin again so we only see the real changes.

@hamxa152 can you delete this PR please


Fix UI for find and filter command

Fixes #225
Create a new setEmptyInformation() method which sets the text of all labels to empty strings in the case no employee is to be listed (when no employee satisfies the Predicate in the find and filter command)

LGTM


[auto-merge] branch-23.08 to branch-23.10 [skip ci] [bot]

auto-merge triggered by github actions on branch-23.08 to create a PR keeping branch-23.10 up-to-date. If this PR is unable to be merged due to conflicts, it will remain open until manually fix.

FAILURE - Unable to auto-merge. Manual operation is required.
{'message': 'Pull Request is not mergeable', 'documentation_url': 'https://docs.github.com/rest/pulls/pulls#merge-a-pull-request'}

Please use the following steps to fix the merge conflicts manually:
# Assume upstream is NVIDIA/spark-rapids remote
git fetch upstream branch-23.08 branch-23.10
git checkout -b fix-auto-merge-conflict-8853 upstream/branch-23.10
git merge upstream/branch-23.08
# Fix any merge conflicts caused by this merge
git commit -am "Merge branch-23.08 into branch-23.10"
git push <personal fork> fix-auto-merge-conflict-8853
# Open a PR targets NVIDIA/spark-rapids branch-23.10

IMPORTANT: Before merging this PR, be sure to change the merging strategy to Create a merge commit (repo admin only).
Once this PR is merged, the auto-merge PR should automatically be closed since it contains the same commit hashes

working on a conflict resolver


Add ability to disable automatic formatting of email addresses within markdown/message components

Hi all, I am trying to display an email address within one of my whispers and instead of just displaying the email as plain text, which is what I am hoping to have, it creates an icon to the left of the email address and converts the email address to a clickable link. See code and screenshot attached below.
Is there a way to disable this automatic formatting somehow so that I can just display it as plain text? (Note: this also happens when you use a message component as well).
import { Direction, JustifyContent } from '@oliveai/ldk/dist/whisper';
import React from 'react';

export const TestEmailMarkdown = () => {
  return (
    <oh-box direction={Direction.Vertical} justifyContent={JustifyContent.Left}>
      <oh-markdown<EMAIL_ADDRESS>/>
    </oh-box>
  );
};

@kyuhas Thanks for the feedback! There're several discussions inside OliveHelps team regarding this feature. We'll keep you updated!

We have created a ticket to better address this issue. We'll let you know once it's done! Thanks!

@kyuhas We have made a fix to remove the icon that appears, but it doesn't look like it was possible to disable auto-linking emails within Markdown components.
I'm going to close this for now, but if you feel you need a solution to the autolinking, feel free to comment and reopen this!


Allow for lazy date input in "d.m.yy" format when desired format is "dd.mm.yyyy"

I have set up datepicker with german locale so dates are expected in "dd.mm.yyyy" format. However, many users are lazy and key in dates without leading zeros. It was very annoying that datepicker doesn't accept such values. E.g., you type in "3.5.2014", which shoud be May 3rd, 2014 (and which I think is totally unambiguous), but datepicker wouldn't accept the date.
I'm not very good at JS, but I searched bootstrap-datepicker.js for what I thought was the problem and I have made a litte addition that I think might be of use to others as well. In fact, I post it here in hope for comments whether this is a good idea or why it should or should not work - it seems to work so far.
I found a part that starts with
parseDate: function(date, format, language)
After the line "if (date instanceof Date) return date;" I added this:
var my_str = date.split(".");
if (
Number(parseInt(my_str[0], 10))
&& Number(parseInt(my_str[1], 10))
&& Number(parseInt(my_str[2], 10))
) {
date = ("0" + my_str[0]).slice(-2)
+ "." + ("0" + my_str[1]).slice(-2)
+ "." + ("20" + my_str[2]).slice(-4);
}
So I check whether it is numbers divided by dots, and if so, I make sure that numbers have a leading zero and that the year is four-digit. Only after that the standard "parseDate" routine is executed.
It actually seems to work much better than I hoped. As soon as the input field has something that matches "numbers divided by dots", the datepicker panel even marks the right date in the calendar.
Note that my simple implementation only works for years 2010+, as I only prepend "20" (with 2005, I should prepend "200", I guess). It's also not a good solution if a two-digit year is ambiguous - but if all dates are in the future and "13" can only be 2013 (vs. 1913), I guess it's safe.
I'd really like comments on this as I don't feel too comfortable to just manipulate code I don't fully understand. I'm totally new to GitHub and apologise if this doesn't belong here.
(I hope that) I attached a screenshot that shows the result. Left is the demo page, with German locale, and the result when you key in "3.5.14". (Actually, I've never seen that "NaN" errors on my own page??? Datepicker just doesn't pick up the right date and replaces it by today's date, but it doesn't give "NaN".) Right is the result after my addition to the code. When the input loses focus, the date is even displayed in "dd.mm.yyyy" format. So I'm very happy with the result... but:
I hope the whole thing doesn't have any undesired side effects!

Hi, sorry for the late reply.
Is this still an issue for you ? I do believe this have been fixed in the latest release.

closing, feel free to reopen.


feat: add extra-files input

resolve #343
Add the extra-files input option.
See: https://github.com/googleapis/release-please/blob/main/docs/customizing.md#updating-arbitrary-files

@jcornaz try installing the latest version of release-please and running npm run build.

Thanks @bcoe. It does work now :-)

@jcornaz mind rebasing?

@bcoe I rebased :+1:

@jcornaz thank you 🥳

How does this work with updating xml or json files? How can I set the xpath?

How does this work with updating xml or json files? How can I set the xpath?

You cannot set a XPath. In the file you want to update, you have to comment in the file where are the part want to update. See: https://github.com/googleapis/release-please/blob/main/docs/customizing.md#updating-arbitrary-files for more details
Example:
<myxml>
  <version>1.0.0</version> <!-- x-release-please-version -->
</myxml>

Thanks @jcornaz . I've tried that with the simple strategy but it's ignoring the extra-files option. At least, I cannot see anything in the output and there's no change in the PR it creates. Are there any examples of how to use this? The docs are pretty light.

Mmh strange, it should work. I suggest you open an issue and share an example of how to reproduce.


onItemChanged filtering

Looking at:
https://github.com/geprog/use-feathers/blob/c3f8a7dc2e3e33b5f21ef72754a47ed61ecb40c0/src/useFind.ts#L32-L33
and the corresponding test:
https://github.com/geprog/use-feathers/blob/c3f8a7dc2e3e33b5f21ef72754a47ed61ecb40c0/test/useFind.test.ts#L380
This seems like a case that can not happen. When the query changes find is called and overrides data.value completely.

@anbraten Am I missing something?

@lukashass I think the query stays the same, but the object which was first matched changed and is not matching the query anymore after that update / patch.
Exp:
query: { type: "dog" }
data: { _id: "123", type: "dog", name: "Pluto" }
=> we have one item in matching data
update:  { _id: "123", type: "dog", name: "Pluto" } =>  { _id: "123", type: "cat", name: "Pluto" }
=> we have 0 items in matching data


Width is set in inline style

Hi,
since width is set in inline style, I cannot change it in my custom css class.
I think width should not be passed to options but it should be set in css so we can customize it in custom css class.

Hi,
thanks for recommendation, but width will stay an argument for multiple reasons. One of them is some velocity animations (in projects that are already in production) rely on having width.

How can we have a different width on mobile? Or at least, have the widget set it's width to min(requested_width, viewport)


Client-sided crash with supply carts.

Client-sided crash.
Mainly using supply carts.
does not crash on server-side. seems to be rendering related.

crash-2024-04-22_00.13.24-client.txt

This seems like an incompatibility with Iris. Unfortunately I don't have much time for modding at the moment. So the fix will take a while.

It also seems you are using Quilt. I do not use Quilt and I don't test with it so I cannot guarantee that this mod is compatible with Quilt.

Hey! I was able to fix it by disabling armor rendering, temporarily, solving the crash at least client-side

Upon further inspection this seems to be indeed an incompatibility with the Quilt Loader. I do not use Quilt and don't test the mod against it. Which means if no one else contributes a fix, this issue will unfortunately persist. But I will add configuration options to disable the rendering of the armor which should serve as a workaround.


Support feature creation by meter Id OM-719

Overview
Includes (per commit):

make task to run e2e tests
removes *map[string]string for feature meterGroupByFilters and replaces it with a custom type
Proposed solution for OM-719 : Create Feature with MeterID

Notes for reviewer

If the proposed solution's not accepted I'll revert as I'd still like to get the first 2 commits merged

This PR changes the API which I don't like that much, another option would be to add an extra input property meterId and then we'd document which has precedence, but I that doesn't seem the best either.
MeterID shouldn't be added to the Feature directly (IMO) as in most cases MeterID doesn't exist... the idea is to provide a convenience when creating a feature

Closing due to inactivity


docs: add warning for writing new workflow steps

This adds a small warning to the pipeline step docs regarding naming conventions in the workflow Snakefile.
Needed for https://github.com/bihealth/cubi-tk/pull/174

https://github.com/bihealth/cubi-tk/pull/174 has been merged. This should be merged too


Document limitation of the system (ALD)

Using this as a place holder first and also a tracker of the task.
We want this for both us and the auditor and our user to be easier to track our system.

[Note]

Global assumption of the design

outputId should be unique
tx bytes should be unique aside from deposit tx


tests: drivers: counter: Fix test for nrf52 platform

Fix failing tests.
Tests were failing because:

alarm_cnt was not reset before the test.
one test was failing because it was expecting that setting top_value for channel_alarm is too much but in fact top_value+1 is too much.

Fixes #13254.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

fyi @cinlyooi-intel

Codecov Report

Merging #13305 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #13305      +/-   ##
==========================================
+ Coverage   48.76%   48.76%   +<.01%
==========================================
  Files         319      319
  Lines       46864    46864
  Branches    10832    10832
==========================================
+ Hits        22853    22854       +1
  Misses      19381    19381
+ Partials     4630     4629       -1

Impacted Files
Coverage Δ

arch/posix/core/posix_core.c
91.91% <0%> (+1.01%)
:arrow_up:

Continue to review full report at Codecov.

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

@anangl splitted work into 2 commits, reworked commit message and applied your suggestions.


Print appropriate parameter name when trying to set its value again

What is the purpose of this change? What does it change?

Prints the name of the parameter whose value the user is trying to set again
Was the change discussed in an issue?

fixes #1675

error: could not run steps: step e2e-scenarios failed: could not wait for template instance to be ready: could not determine if template instance was ready: failed to create objects: object is being deleted: pods "e2e-scenarios" already exists

/retest

/retest

/retest


Missing fields for basetypes

Hi there,
I'm currently trying to upgrade to latest Marten 5.8.0 (from 3.14.X).
I found that the fields from basetypes are not persisted in postgres after upgrading. Is this a bug?
public class MyBaseClass
{
  public string Foo {get;set;}
  public int Bar {get;set;}
}

public class AnotherClass : MyBaseClass
{
  public string AnotherVal {get;set;}
}

when registering and using only AnotherClass the Fields Foo and Bar are left out.
Worked in 3.14

@srasch We do have many unit tests on for the hierarchical documents and are working as expected in the latest version. I did a test using your above example and looks to work fine. Please provide a repro for us to check further.

hm, that's crazy. I tried to setup a test for this case. Now it works... ⁉


Ctrl+click on Mac (laptop with touchpad) is not detected as right-click

I was sent here from libGDX project:
https://github.com/libgdx/libgdx/issues/6405
Via the LWJGL:
https://github.com/LWJGL/lwjgl3/issues/621
When using libGDX with LWJGL3 dependency, ctrl+click on Mac (laptop with touchpad) is not detected as right-click, instead it's a left-click. This is a recommended way of achieving right-click on Mac:
https://support.apple.com/en-gb/guide/mac-help/mh35853/mac

I think the big question is: is it a bug in GLFW that ctrl+ click is not detected as right click on macOS (which is apparently recommended by the official Apple user guide) or should it be up to the applications using GLFW to implement this behaviour themselves?

@crykn If GLFW is multi-platform, as it purports, it probably should extract a set of common functionalities, and hide those away from the library user. Many developers might not have a Mac handy to test, and their Mac end-users might be disappointed that they cannot use ctrl+click to achieve right-click functionality.

Please do not make GLFW do this emulation. It's definitely the application's job to implement this behavior. It is very easy to make your application do this emulation on top of GLFW, but it's impossible to make your application ignore this emulation in case it is forced in GLFW. Before you say that I'm crazy for wanting to break Apple's guidelines, let me explain my case.
In Minecraft, the Ctrl button is used for sprinting across all platforms - Windows, Linux, and macOS. So, if you want to sprint and left click, it works just fine on Windows and Linux, but it becomes impossible in macOS, which literally breaks the game. In LWJGL2, this emulation was included in the native library, which made it impossible to alter. In LWJGL3, this emulation was removed, so now Minecraft does it in its own Java code. It is trivial to write a mod to toggle the behavior in Minecraft code, but it is impossible to do it if it's included in LWJGL2 or GLFW. Same goes if Mojang decided to add this toggle themselves - it would be impossible to do if the emulation is forced on GLFW's level.
In my opinion, GLFW should expose hardware in a common way (in this case mouse and keyboard events), not expose a common set of functionalities, because then it becomes impossible to have the same functioning application across platforms.


Synthesis failed for scheduler

Hello! Autosynth couldn't regenerate scheduler. :broken_heart:
Here's the output from running synth.py:
nd, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e935c9e build(java): run linkage monitor as GitHub action (#933)
2021-02-03 03:10:15,236 autosynth [DEBUG] > Running: git checkout f694606e3e34d0e2a289d655864e225cab9ecb88
Note: checking out 'f694606e3e34d0e2a289d655864e225cab9ecb88'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f694606e chore(profiler): Set proto namespace to google.cloud
2021-02-03 03:10:15,253 autosynth [DEBUG] > Running: git branch -f autosynth-scheduler-43
2021-02-03 03:10:15,257 autosynth [DEBUG] > Running: git checkout autosynth-scheduler-43
Switched to branch 'autosynth-scheduler-43'
2021-02-03 03:10:15,286 autosynth [INFO] > Running synthtool
2021-02-03 03:10:15,286 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-02-03 03:10:15,286 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Scheduler/43/sponge_log.log
2021-02-03 03:10:15,289 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-02-03 03:10:15,522 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-php/Scheduler/synth.py.
On branch autosynth-scheduler-43
nothing to commit, working tree clean
2021-02-03 03:10:15,696 synthtool [DEBUG] > Ensuring dependencies.
DEBUG:synthtool:Ensuring dependencies.
2021-02-03 03:10:15,708 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
2021-02-03 03:10:15,714 synthtool [DEBUG] > Cloning googleapis.
DEBUG:synthtool:Cloning googleapis.
2021-02-03 03:10:15,714 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2021-02-03 03:10:15,718 synthtool [DEBUG] > Which version of bazel will I run?
DEBUG:synthtool:Which version of bazel will I run?
bazel 3.0.0
2021-02-03 03:10:15,722 synthtool [DEBUG] > Generating code for: //google/cloud/scheduler/v1:google-cloud-scheduler-v1-php.
DEBUG:synthtool:Generating code for: //google/cloud/scheduler/v1:google-cloud-scheduler-v1-php.
2021-02-03 03:10:15,821 synthtool [ERROR] > Failed executing bazel --max_idle_secs=240 build //google/cloud/scheduler/v1:google-cloud-scheduler-v1-php:

Loading:
Loading: 0 packages loaded
INFO: Call stack for the definition of repository 'com_google_api_codegen' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:77:1
WARNING: Download from https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'com_google_api_codegen':
   java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
ERROR: no such package '@com_google_api_codegen//': java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
INFO: Elapsed time: 0.089s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)

ERROR:synthtool:Failed executing bazel --max_idle_secs=240 build //google/cloud/scheduler/v1:google-cloud-scheduler-v1-php:

Loading:
Loading: 0 packages loaded
INFO: Call stack for the definition of repository 'com_google_api_codegen' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:77:1
WARNING: Download from https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'com_google_api_codegen':
   java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
ERROR: no such package '@com_google_api_codegen//': java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
INFO: Elapsed time: 0.089s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/google-cloud-php/Scheduler/synth.py", line 32, in <module>
    bazel_target=f'//google/cloud/scheduler/{lower_version}:google-cloud-scheduler-{lower_version}-php',
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 64, in php_library
    return self._generate_code(service, version, "php", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 197, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', '--max_idle_secs=240', 'build', '//google/cloud/scheduler/v1:google-cloud-scheduler-v1-php']' returned non-zero exit status 1.
2021-02-03 03:10:15,867 autosynth [ERROR] > Synthesis failed
2021-02-03 03:10:15,867 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at f7702e01 chore: update with latest version of protobuf (#3710)
2021-02-03 03:10:15,913 autosynth [DEBUG] > Running: git checkout autosynth-scheduler
Switched to branch 'autosynth-scheduler'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Pre-install information worksheet recommended in Documentation

@xwu0226 commented on Tue May 12 2020
Customer content
Pre-install information worksheet would be useful. Even better if the pre-install worksheet would carry across product installs.

Good suggestion! The pre-Installation worksheet identifies all the information required by the installer. Filling out the worksheet prior to installation will help the installation process run smoothly and provide a record of the settings used for ease of replication across multiple servers.Investigated and found some example installation worksheets:
Example 1
https://docs.bmc.com/docs/digitalworkplaceadvance/33/installation-worksheets-718093048.html
Example 2

@sn666239 and @vit-tomica and @uzust01.  It sounds like this would be great for us to create to shadow the z/OSMF workflow install and configure templates you created.  A few folks are very keen to see the templates in action - is this something that any/all of you would be able to do to the community ?  Perhaps at the end of a scrum or the Tuesday architecture call next week or an ad-hoc presentation where we can all see the workflows in action and understand them ?  cc:  @stevenhorsman

Close with existing checklists for installation. Thanks


FreeBSD 10.1 install problem

Hi DTVD,
this is a wonderful Twitter application you've shared - thank you very much. I'm having some problems getting it working on FreeBSD 10.1 - it installed fine on a PC-BSD 10.1 system - and I'm not sure where my problems are.
I did the following as root: # pip install rainbowstream without any errors or dependency problems.
As a regular user:
> rainbowstream
You are running latest version (1.2.7)
Hi there! We're gonna get you all set up to use Rainbow Stream.
There seems to be a connection problem.
You might want to check your proxy settings (host, port and type)!

I'm not using a proxy and I'm pretty sure that it isn't a firewall problem on my FreeBSD install, unless Rainbow Stream uses an odd port to try talking to Twitter?
I've tried uninstalling/reinstalling without any success.
Any suggestions?
Thank you for your time and trouble!

Hi @CanOfBees Thanks for report!
RS doesn't use some special port to connect to Twitter. Maybe Twitter API just got unstable during a while.
Can you try again tomorrow and if this problem still there please let me know

@CanOfBees See #180
Can you try the port/pkg (or latest rainbowstream versions) and let us know if you can still reproduce

Hi @koobs - thanks for the response. Somewhere along the way I think I reinstalled with pip and things  started working again. I just reinstalled with pkg and everything started okay there, too. I removed the pkg and built the port: it just works from there, too.
Let me know if you'd like me to test anything else: I probably didn't make as clean a slate as I could have, so I'm happy to rebuild if it would be useful.
Cheers!

@CanOfBees Lovely, thank you for testing them :)
Only thing I'd suggest is removing/deleting rainbowstream (both pip uninstall and pkg delete), then looking in /usr/local/lib/pythonX.Y/site-packages to look for leftovers (*rainbow*) that may cause issues/conflicts in the future. If/when it's clear, reinstall from ports/packages and enjoy
Also, can this issue now be closed?


CI/CD documentation not available for Microgateway

Description:
CI/CD documentation[1] provides information on how the APICTL can be used with APIM but it does not cover how APICTL can be used with Microgateway to automate Microgateway deployments.
[1] https://apim.docs.wso2.com/en/latest/learn/api-controller/ci-cd-with-wso2-api-management/#cicd-with-wso2-api-manager

@Rajith90 and @npamudika , please share your feedback. Also shouldn't this documentation be added in the MGW documentation rather than the APIM docs?

@Mariangela , I think we need the doc on both sides. Problem is MGW side doesn't have it.

We need to add the documentation. Right now what we have is sample tutorial. We need to upgrade this to use apictl
[1] - https://www.youtube.com/watch?v=8mMRy0VEknc


Revert "Migrate Flutter gallery test to null safety"

Reverts flutter/flutter#69048
This is causing failures in apps, for example in flutter/gallery:
git clone https://github.com/flutter/gallery.git
cd gallery
flutter pub get

=>
"af": 41 untranslated message(s).
"am": 41 untranslated message(s).
...
"zh_TW": 41 untranslated message(s).
"zu": 41 untranslated message(s).
To see a detailed report, use the --untranslated-messages-file
option in the tool to generate a JSON format file containing
all messages that need to be translated.
Because gallery depends on flutter_localizations any from sdk which depends on intl 0.17.0-nullsafety.2, intl 0.17.0-nullsafety.2 is required.
So, because gallery depends on intl ^0.16.1, version solving failed.
Running "flutter pub get" in gallery...
pub get failed (1; So, because gallery depends on intl ^0.16.1, version solving failed.)

I tried to resolve this in flutter/gallery by upgrading intl (intl: ^0.17.0-nullsafety), but that causes another failure:
gallery] flutter pub get
Running "flutter pub get" in gallery...

Because every version of flutter_localized_locales depends on intl ^0.16.0 and gallery depends on intl ^0.17.0-nullsafety, flutter_localized_locales is forbidden.
So, because gallery depends on flutter_localized_locales ^1.1.1, version solving failed.
pub get failed (1; So, because gallery depends on flutter_localized_locales ^1.1.1, version solving failed.)
exit code 1

So looks like a fix is needed in flutter_localized_locales to roll that to intl 0.17

TBR @blasten,  this is now passing CI, so I'm going to merge this to unblock the engine roll, which we need by monday

Looks like there were some dependencies in the migration that were still on non-null-safe versions.  e.g. I notice http http_parser were still on 0.12.2 and 3.1.4 respectively.  In those cases, the null-safe versions haven't been published, so you have to do something like the following:
dependency_overrides:
  http:
    git:
      url: https://github.com/dart-lang/http.git
      ref: 7bc620de8b416d8186f0bed75837c09293f597d4
  http_parser:
    git:
      url: https://github.com/dart-lang/http_parser.git
      ref: 763512ce970c336b3392a1a75d2ccd9508a33896

@mit-mit we should probably publish null safe versions of those packages (and any others in the Dart SDK that the gallery depends on).

@tvolkert https://pub.dev/packages/http_parser/versions/4.0.0-nullsafety is already there, and @kevmoo says http should be there later today

cc @guidezpl @rami-a for flutter/gallery dependencies.

flutter_localized_locales was just published
intl_translation also conflicts as it depends on intl, but I heard it could be dropped from the Gallery's dev dependencies.

Are you guys driving the changes to the Gallery's pubspec.yaml?

Also blocked on https://dart-review.googlesource.com/c/sdk/+/171021 – and would need to roll this into google3


HADashboard on Old Ipad Mini No longer Syncing States

I updated the AppDaemon 4 add-on to add-on version 0.3.0 today (was running a version behind this before) and now HADashboard is not syncing states on an old Ipad Mini I am using as a control panel.  It works fine on Chrome on this mini but not Safari (which is what I normally use because of full screen mode when launching from a home screen shortcut).  If I load it in Safari from the address bar and not from the home screen shortcut I get "error getting state, check Java Console for details".  If I launch it from the shortcut it loads fine but only shows states of entities at the time of loading and never updates after that.  If it is finally time for me to retire this Ipad I am fine with that, just wanted to give a heads up, and hopefully there is a fix.

Add-ons wrap existing applications. Please report this issue with the ApPDaemon project.
Thanks 👍


User Selects Criteria

User Selects Criteria
User Story
AS AN employee with access to sensitive data,
I WANT to randomly generate a password that meets certain criteria,
SO THAT I can create a strong password that provides greater security.
Acceptance Criteria
GIVEN I need a new, secure password,
WHEN prompted for password criteria,
THEN I select which criteria to include in the password.

Complete. See deployed site: https://nestibry.github.io/umn-bcc-mod03-password-generator/


ci: optimize

✔ Checklist:

[ ] Commit messages have been written in Conventional Commits format;
[ ] This PR has been added to CHANGELOG.md (at the top of the list);
[ ] Tests for the changes have been added (for bug fixes / features).

Codecov Report

Merging #38 (2c39adc) into main (30dedb3) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 2c39adc differs from pull request most recent head 14a139a. Consider uploading reports for the commit 14a139a to get more accurate results

@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   93.71%   93.71%
=======================================
  Files           9        9
  Lines         573      573
=======================================
  Hits          537      537
  Misses         36       36

Impacted Files
Coverage Δ

src/lib.rs
92.89% <0.00%> (ø)

Continue to review full report at Codecov.

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