Having this same issue in macOS as of today. Per @meganrogge recommendation on #156668, I set terminal.integrated.enablePersistentSessions: false, but am still having this issue. It's persisted through a complete wipe of settings and a fresh install.

Having this same issue in macOS as of today. Per @meganrogge recommendation on #156668, I set terminal.integrated.enablePersistentSessions: false, but am still having this issue. It's persisted through a complete wipe of settings and a fresh install.
Originally posted by @drenze-athene in https://github.com/microsoft/vscode/issues/130320#issuecomment-1199733729

Hi there -- sorry, I can't quite understand what your bug report is. This repository only contains software for Windows :smile:

Hi there -- sorry, I can't quite understand what your bug report is. This repository only contains software for Windows 😄

I'm not certain how this got opened here. I initially submitted a VSCode bug report for macOS, got referred to another open issue for the same thing that was initially opened by a Windows user, and then this got opened. I'm not certain how this got opened here.

Huh! No problem. If it turns out this was an important thing to end up on our repo, I'll reopen it. Thanks!


can't connect to remote server

Same issue as #3335, a workaround is to revert to version 1.2.5.

Same issue as #3335, a workaround is to revert to version 1.2.5.


Out of date

Any plans to update this document so that it represents the screens and choices you will be presented with at present? I'm trying to write a function but am not seeing the shown screen that says "custom function"

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

ID: b4e5181c-002d-33bb-5e9d-02fad30a5d3c
Version Independent ID: b771d6b5-00c9-4d0a-260e-c79cb3100d8b
Content: Create a function that runs on a schedule in Azure
Content Source: articles/azure-functions/functions-create-scheduled-function.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@clintoj Thanks for the feedback! We have assigned this issue to the content author to review and update accordingly.

Ditto. (adding to get notifications. Thanks.

Thanks @clintoj, we did apparently miss this article when refreshing articles for the most recent portal changes.

In this document, I can't find a section on how to run our written functions. I have a .fs or.fsx file, so how to run and how to see the result?

@taromielnaz as I mentioned, for version 2.x of the Functions runtime, F# script is no longer supported. Probably the best thing is create a new F# class library project in Visual Studio and add the package Microsoft.NET.Sdk.Functions. At this point, you should basically be able to follow the general steps for developing and publishing compiled C# apps, except using F# conventions instead of C#. If you need more help with F# Functions development, I suggest you ask your questions in the Forum or on Stack Overflow.
As for the original issue, which is now resolved...#please-close


Persistent build metadata

The buildpack cache is ephemeral, and a build should work even if the cache is not provided (or deleted to run a fresh build).
However, there are certain values that need to be persisted across builds, even if the cache is cleared. One example is the Rails secret_key_base.

Shouldn’t this just be a launch layer with a .profile.d that sets the value?

There's a couple problems with that: the launch layer won't be available to subsequent builds (right?) and even so a bash script won't be parseable. I'm talking about this on behalf of others who need it (I don't actually need it myself) so I'm not the best one to go into detail. I'll let @hone bring it up at a sync.

To me it seems like:

If it needs to be available at launch every time, persistently, then it should be set in <launch>/<layer>/profile.d
If it needs to be available at build every time, persistently, then it should be written to <launch>/<layer>.toml

Ah so I was not planning on providing the launch layers from previous builds during a build (that's what the cache is for?). We should discussion.

The launch layers are never available in subsequent builds — just the launch layer metadata TOML files.

@hone and @jkutner Can you please write up your understanding and close out if your comfortable with our discussion?

Given that the <launch>/<layer>.toml files are provided for subsequent builds (as described in Phase #2: Analysis), and assuming that a given a platform defines previous builds/OCI images as persistent, then I think <launch>/<layer>.toml satisfies the need for persistent metadata.
But is the <layer>.toml meant to be persistent? Would/should a new version of the lifecycle invalidate it? If so, that would be problematic for this use case. The spec is unclear i think, when it says "Was created using the lifecycle". (if we want to be unclear i think that's ok).
Related to this, the spec states "The lifecycle MUST NOT download any filesystem layers from the previous OCI image". I found this surprising given that I would expect to get the <launch>/<layer>.toml files from the previous image. Are we suggesting that the <launch>/<layer>.toml files are stored outside of the image?

But is the .toml meant to be persistent? Would/should a new version of the lifecycle invalidate it? If so, that would be problematic for this use case. The spec is unclear i think, when it says "Was created using the lifecycle". (if we want to be unclear i think that's ok).

The intent was for it to be guaranteed. We could clarify the spec to specify that the platform must always restore the metadata on a rebuild of the same image unless the developer or operator explicitly indicates otherwise.

Related to this, the spec states "The lifecycle MUST NOT download any filesystem layers from the previous OCI image". I found this surprising given that I would expect to get the /.toml files from the previous image. Are we suggesting that the /.toml files are stored outside of the image?

The <launch>/<layer>.toml files are stored as JSON metadata on the config blob, which is a component of the OCI image that isn't a layer.

Closing as this should be covered by #37 and #35. Feel free to re-open if I missed anything.


Update PairRDDFunctions.scala

https://issues.apache.org/jira/browse/SPARK-21882

Can one of the admins verify this patch?


issue in ios

flutter: MissingPluginException(No implementation found for method init on channel ncnn_ios)

@tomassasovsky


Add build-official-release.sh

This commit does 4 things:

Adds a script which will: (a) clone from a git tag, make release,
and give you very detailed instructions as to what to do from that
point.
Changes push-official-release.sh so we can't push "dirty"
releases anymore (which build-official-release.sh also double
checks at the end.)
Fixes #9576 by ensuring a correct umask.
Changes common.sh to gtar all the way through, to ensure that
bloody OS X tar never touches the release process, because I don't
want to have to understand two tar programs and how release
artifacts are created from both (c.f. #10615.)

Sample post-amble:
Success! You must now do the following: (you may want to cut
  and paste these instructions elsewhere, step 1 can be spammy)

  1) (cd /tmp/kubernetes-release-v0.20.2-1435866007; build/push-official-release.sh)
  2) Go to https://github.com/GoogleCloudPlatform/kubernetes/releases
     and create a new 'Release v0.20.2 Candidate' release
  3) Upload the /tmp/kubernetes-release-v0.20.2-1435866007/kubernetes.tar.gz to GitHub
  4) Use this table for the hashes:

binary | hash alg | hash
------ | -------- | ----
`kubernetes.tar.gz` | md5 | `442cc445c8897c27a480748651ef6764`
`kubernetes.tar.gz` | sha1 | `277b104bb1c0fdb11a71ae5a186d8c513d4ad33b`

  5) Ensure all the binaries are in place on GitHub and GCS before cleaning.
  6) (cd /tmp/kubernetes-release-v0.20.2-1435866007; make clean; cd -; rm -rf /tmp/kubernetes-release-v0.20.2-1435866007)

cc @alex-mohr @quinton-hoole @ixdy @brendandburns

@k8s-bot: test this

@k8s-bot test this

@k8s-bot: test this

The pull request builder and I .. Are not agreeing.

@k8s-bot test this

BTW, I'm finally trying to close out #1883, but rather than writing up the maddening steps involved in building that are currently there (and fraught with peril), I thought it was saner to just write a script.

Prefer to have @brendandburns review this please.  Reassigning.

LGTM, ok to merge on one LGTM, since this is non-impacting.

This broke Jenkins.
+ ./build/push-ci-build.sh
+++ [0706 16:15:45] Staging release artifacts to /jenkins-master-data/jobs/kubernetes-build/workspace/_output/gcs-stage
./build/../build/common.sh: line 849: TAR: unbound variable
./build/../build/common.sh: line 849: TAR: unbound variable
!!! Error in ./build/../build/common.sh:849
  '"${TAR}" x -C ${GCS_STAGE}/${dst}' exited with status 1 1
Call stack:
  1: ./build/../build/common.sh:849 kube::release::gcs::stage_and_hash(...)
  2: ./build/../build/common.sh:866 kube::release::gcs::copy_release_artifacts(...)
  3: ./build/../build/common.sh:792 kube::release::gcs::release(...)
  4: ./build/push-ci-build.sh:35 main(...)
Exiting with status 1

Sigh. Mea culpa.


feat(controller): adding glob matching in includePaths/excludePaths filters of Warehous…

…e Git Subscription

@hiddeco @krancour as this is a continuation of includePaths/excludePaths story, tagging you both to take a look at my changes for added glob matching when you have a second

@maksimstankevic thanks for this!
This looks pretty good. I've got just a few miscellaneous observations and questions.

I think the comments on IncludePaths and ExcludePaths fields need to be updated to reflect the new options (and the codegen re-run).

I'm not sure whether this really should be based only on globs. As it stands currently, I think people would be quite surprised to find that foo/bar isn't a match for the pattern foo/. @maksimstankevic and @hiddeco what are each of your thoughts about this?

I only just noticed this now and didn't notice in #1477 -- does this path filtering only work with the NewestFromBranch commit selection strategy? That appears to be the case and I'm now wondering why that is. (We can open a separate issue for this if we determine this was a mistake.)

I think the comments on IncludePaths and ExcludePaths fields need to be updated to reflect the new options (and the codegen re-run).
-----My bad, will work on it with after next point is finalised.
I'm not sure whether this really should be based only on globs. As it stands currently, I think people would be quite surprised to find that foo/bar isn't a match for the pattern foo/. @maksimstankevic and @hiddeco what are each of your thoughts about this?
-----I agree, but do we combine prefix matching and glob matching under the same unprefixed string array (that holds only globs currently)? Or we introduce new "regex/p:"-like prefix for either "prefix:" or "glob:" and leave the other one unprefixed?
I only just noticed this now and didn't notice in feat(api/controller): support filtering rules Git subscriptions #1477 -- does this path filtering only work with the NewestFromBranch commit selection strategy? That appears to be the case and I'm now wondering why that is. (We can open a separate issue for this if we determine this was a mistake.)
-----I somehow thought back then that tag filtering should not interfere with commit filtering. Now I have less confidence it was a correct approach but I agree if it's decided to add includePaths/excludePaths filtering to CommitSelectionStrategies involving tags - that needs to be done in a separate issue

Ok. So second point is the one most in need of addressing. imho, yes... prefix and glob match should go together, but I am willing to hear arguments against that. My argument in favor of it is that anyone accustomed to working in a shell environment is likely to find that to be the least surprising behavior. I contend most people would never think to do foo/* and would assume that foo/ suffices.

One argument against combining them would be that there could be potential conflicts or overlaps in certain scenarios, such as when dealing with literals versus special characters, nested patterns, or character escaping.
To solve this, one would have to start defining (and documenting) rules around precedence. Which in the end may make it easier from both a technical and user perspective to create a separation between the two.

Yeah, I agree, in my eyes that would be an overcomplication for a simple topic. I would go with "regex:/regexp:" prefix for regexps, "glob:" prefix for globs, these first 2 being the advanced options for folks wishing to use them (like me 😄 ) and strings without prefix would be for exact matches and string prefixes like "foo/" to match "foo/bar".

I'm a little confused because I feel as if we all probably use prefixes and globs on a regular basis in our shells without ever having to specify which we're using.

There are small details to take into account here:

Globbing in the shell is a two-step feature. The globbing happens before feeding the input to the command, and it's not a feature of the CLI you are working with.
.gitignore is a special format, and not 1:1 equal to glob https://git-scm.com/docs/gitignore#_pattern_format.

Globbing in the shell is a two-step feature. The globbing happens before feeding the input to the command, and it's not a feature of the CLI you are working with.

Right... but that's an implementation detail. You don't think about that when you write commands like mv foo/ bar/ or mv foo/*.go bar/ you just expect either way of doing things to work.

But that implementation detail means that globbing > prefix matches. Which means there is an order of precedence.

That may technically be so, but how often do you stop and think about this?

Not very often, but the shell also present me for different things to e.g. do literal string interpretations. Assuming I have a directory called foo?, I can do ls "foo?" to ensure it wouldn't be parsed as a glob. Using a declarative API, this would probably have to become foo\? as the input is a literal string already, and it needs to be escaped somehow.
These kind of details make me worry about edge cases for directory structures and (not so) great people do while naming things. In addition to it creating technical hurdles over simply using an identifier, as you can't e.g. say "if it contains one of these special characters, it's a glob".

Would you not find it surprising if foo/ and foo/* (for example) didn't both work with our default matching strategy?

It would depend on what the API tells me the features are, if the default is just simple prefix matching and there also is a regular expression feature with an identifier. I wouldn't, I think.

It would depend on what the API tells me the features are

This is a fair point, but I also want to default to the least surprising behavior for the benefit of those who didn't read the manual.
That is the main thing I care about.
If we think prefix matching would be the least surprising default, let's go with that and use the glob: prefix for glob-matching.

Thanks @hiddeco @krancour, I'll do it with "glob:" for globs and no prefix for prefix and exact string matching.

@maksimstankevic as always, thank you for your patience and your efforts!

@hiddeco @krancour pushed it, please review when you can

@maksimstankevic I think this looks pretty great. Thanks for the hard work.
At a later date, when documenting the changes, I may adjust the comments on the IncludePaths and ExcludePaths fields a bit, but this functionality all looks 👍 to me.
LGTM unless @hiddeco has anything more to say about it. (@hiddeco go ahead and merge if you're good.)

Also happy with how this looks, thanks @maksimstankevic! 🍒
As another potential follow up, I think we could improve the tests a bit to provide some guarantees when people mix-and-match patterns. But that's absolutely non-blocking for now.

Just filed a new issue for this: https://github.com/akuity/kargo/issues/1862, will take it and add thorough testing
thanks @hiddeco !


Remove lld requirement from thinlto test

lld is not really needed here. However, having it listed makes the test unable to run in systems without lld support.
I've tested this in an s390x platform (no lld) and the test now runs and passes.

Thanks!


Coefficient of beta 2

Right now, it seems as if beta[2] is providing the effect estimate of the the effect of A_2 given non-response rather than just the effect of A_2. If you run 1000 simulations, then the mean effect estimate of beta[2] = true beta[2]/(1 - r) where r denotes the probability of response. I can't seem to figure out why this is occurring. The other three coefficients seem to be correct.
Code:

Results:

True Betas:

I also tested N = 100, m = 1 to "remove" clustering and then compared with results using geeglm() from geepack after appropriate weighting and replicating. geeglm() provides the expected results that correspond with True Beta in the above output.
Code:

Results:

The issue is how we calculate D() for responding clusters. Since responders are currently coded as A2 = 0 within cSMART.mm(), the output from D() is an (m x 4) vector with columns 3 and 4 entirely 0. These columns should be either 1 or -1 depending on which dtr we are looping through because responding clusters are consistent with multiple dtrs.
I can push up a correction within the next day or two.

On a closer glance, this seems to be an issue with how variable names are handled. When I use cSMART.mm(Y ~ A1 + A2 + I(A1 * A2), it incorrectly calculates the coefficient on A2. When I use cSMART.mm(Y ~ a1 + a2 + I(a1 * a2), then it provides the correct coefficients. Note that cSMART.dgen() outputs variable names A1 and A2 which is why I was using them in cSMART.mm().


ci: remove EOL-ed Ruby

Because Ruby 3.0 reached EOL on 2024-04-23.
See also:
https://www.ruby-lang.org/en/news/2024/04/23/ruby-3-0-7-released/

Thanks.

Thanks for your review!


Fixed wrong formatting in README

This link is out of date as of now (in README) - summary, might want to fix it as well.


English Native Speaker wanted - review readme

Review the readme and correct to better english.

@altmann  I would like to pick this up

Great thanks. Please don't change the structure - only correct grammar etc.

A pull request has been opened for this: https://github.com/altmann/FluentResults/pull/69

Thank you very much @deepank120896 for your work. PR is already approved.


Converting zkHosts to lowercase cause problem when zkHosts contains uppercase chroot path

KafkaManager will convert cluster name and zkHosts to lowercase when constructing a ClusterConfig.
This works fine if zkHosts only contains host names and ports, however, it also may contain additional chroot path at its end.
In such cases, the chroot path means a part of a ZNode path, which is case sensitive. Converting it to lowercase will make Kafka Manager refer to a non-existed path on Zookeeper when operating the cluster.
To me, the case conversion is not quite meaningful, even cluster name is not necessarily to be in lowercase. Can we just keep the casings of names and zkHosts as they are given?

How to reproduce

Add a kafka cluster whose zookeeper hosts contains chroot path with uppercase letters. Like  zkhost1:2181,zkhost2:2181,zkhost3:2181/KafkaClusterPath
The cluster will be added successfully and listed in cluster list.
Clicking the name of the new added cluster will show you the error.

I tried get rid of the to lowercase conversion in my forked repo
https://github.com/evanmeng/kafka-manager/commit/9070032d26d72a31c8cb478defb548c0377906b8
and looks things work fine.
But I am not sure whether this will break other functions since there is no regression tests yet. Maybe some of you can have a look at it?

This has been fixed.


DC Network Adapter (missing) issue

Operating System Version: Ubuntu 18.04 (same system I've built DL on before, recent updates)
Provider (VirtualBox/VMWare): Virt Box 5.2.18
Vagrant Version: 2.2.1 (recently updated, last successful build was 2.1.8)
Packer Version: 1.0.8
Is the issue reproducible or intermittent? Youbetcha

Description of the issue:
On the DC - there are no network adapters, even though they are visible from the VBox menu, settings menus, in Device Manager, etc. Meaning that Windows dev manager identifies 2 ethernet controollers but neither of the are identified and get IP addresses (IPconfig returns no results).
When I run a "vagrant reload dc" AFTER I changed the NIC to an Intel 1000 MT nic, same problem, even though the base VM boots properly and sees the NIC, and the NIC gets addresses on the LAN.
Or to put another way - by default w/ no intervention, the DC image does not get functional network adapters. When I change the network adapters to something that works (intel 1000 mt), the vagrant reload dc command appears to reset the NIC to a non-working one, "paravirtualized nic", and the end result of that is no IP addresses are defined so the DC can't "talk" on the network.

I also went into the Vagrantfile, and set the NIC to one of the Intel types following the Vagrant article here:
https://www.vagrantup.com/docs/virtualbox/configuration.html
When the DC books, the Windows network icon has a red indicator, there is no network adapter to configure in the Network Connections dialog.
I get an error saying "the vm has entered a paused" state. Very odd, that.

I had the same problem and solved by the same steps as you did.
for example, for win10: (you should do it for every machine except logger. logger is OK without this parameter)
cfg.vm.provider "virtualbox" do |vb, override|
  vb.gui = true
  vb.name = "win10.windomain.local"
  vb.default_nic_type = "82545EM"

@mergene @vdog90 did either of you reproduce this problem with Virtualbox on Windows? I'm testing it now and seeing both adapters:

Hey folks - can anyone who is experiencing these issues chime in with:

Specific OS Version/Distro
Virtualbox Version
Vagrant Version

And possibly provide a debug log for via vagrant up dc --debug &> vagrant_up_dc_debug.log
I'm unable to repro on my CI build environment, but it sounds like multiple people are having this issue.

Can it be a result of recently discovered vulnerability of VirtualBox e1000 nic driver?
https://github.com/MorteNoir1/virtualbox_e1000_0day

Fixed in https://github.com/clong/DetectionLab/commit/52faea3e67e7cfa0eed0029fec4e760d9348b131


Fix formatting issues in GBSA section of SMIRNOFF spec

Fixes #294

Codecov Report

Merging #318 into 0.3.0-branch will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           0.3.0-branch     #318   +/-   ##
=============================================
  Coverage         75.66%   75.66%
=============================================
  Files                17       17
  Lines              5133     5133
=============================================
  Hits               3884     3884
  Misses             1249     1249

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 c663611...be45c80. Read the comment docs.


python3Packages.json5: 0.9.5 -> 0.9.6

Motivation for this change
Update to latest upstream release 0.9.6
Change log: https://github.com/dpranke/pyjson5/releases/tag/v0.9.6
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 129625 run on x86_64-linux 1

2 packages failed to build and are new build failures:

python38Packages.graphtage: plain log  |  pretty log
python39Packages.graphtage: log was empty

2 packages built:

python38Packages.json5
python39Packages.json5

Result of nixpkgs-review pr 129625 at a67a703f run on aarch64-linux 1

2 packages failed to build:

python38Packages.graphtage
python39Packages.graphtage

2 packages built successfully:

python38Packages.json5
python39Packages.json5

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

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

4 packages built:

python38Packages.graphtage
python38Packages.json5
python39Packages.graphtage
python39Packages.json5


Removed andExtension from AKAudioFile, and changed enum baseDirectory to camelCase.

This pull request is pulling against master, hence the absurd number of files changed. ;)


Enhancement: Support attrs converters

Description
Attrs has an attribute conversion feature where a function can be provided to be run whenever the attribute value is set.
https://www.attrs.org/en/stable/examples.html#conversion
This is not being run when the post request body is an attrs class. Looking for clarity on if this is by design or a fix if not. Also, is there another preferred pattern in litestar to do this type of payload attribute conversion?
URL to code causing the issue
No response
MCVE
requirements.txt
litestar[standard,attrs]==2.10.0

api.py
from __future__ import annotations

import attrs
from litestar import (
    Litestar,
    post,
)

@attrs.define
class TestRequestPayload:
    a: str = attrs.field(converter=str.lower)
    b: str = attrs.field(converter=str.lower)

@post("/test1")
async def test1(data: TestRequestPayload) -> dict:
    return attrs.asdict(data)

@post("/test2")
async def test2(data: TestRequestPayload) -> dict:
    # Naked evolve basically re-instantiates the object causing the converters to be run
    return attrs.asdict(attrs.evolve(data))

app = Litestar(
    route_handlers=[test1, test2],
)

Steps to reproduce

litestar --app api:app run
Make a request to the test1 route, note data response unchanged from input

$ curl --request POST localhost:8000/test1 --data '{"a": "Hello", "b": "World"}' ; echo
{"a":"Hello","b":"World"}

Make a request to the test2 route, note data response lowercased relative to input

$ curl --request POST localhost:8000/test2 --data '{"a": "Hello", "b": "World"}' ; echo
{"a":"hello","b":"world"}

Screenshots
No response
Logs
No response
Litestar Version
2.10.0
Platform

[X] Linux
[ ] Mac
[ ] Windows
[ ] Other (Please specify in the description above)

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

hey @jeffcarrico! This is a known limitation of msgspec, which Litestar uses to provide (part of) its attrs support.
There's an open issue over at their repo for this as well.
The partial msgspec support however means that it's hard for us to work around this, as msgspec doesn't give us a way to hook into the de/encoding process there for types it supports natively.
I think as of now, the workaround you're using in your test2 is the best solution.


Add method remove_children(free_children: bool = true) to Node class

Adding method remove_children() to Node class. It would be useful for Nodes with a large number of children that generated procedurally. Also, it looks like a small simple change in code

It reduces the amount of boilerplate code and increases performance. Right now, if you want to delete all children you should iterate over children array that you get from the get_children method and manually delete each child. If you go from first to the last child, you will fire event NOTIFICATION_MOVED_IN_PARENT for all next children. It can be omitted by method remove_children which will remove children in order from last to first

remove_child() does not delete children. They will instead become memory leaks.
What you should be asking for is queue_free_children() and free_children(), which has doubtful application. Deleting everything is not that common, so when you need it a loop tends to be fine.

I second for queue_free_children() and free_children()

@TheDuriel What for free_children()?

By the way, it can be kept as remove_children, but with an additional boolean argument free_children which is by default true. While it's true on each children node would be called queue_free(), if it's false queue_free() wouldn't be called.

By the way, it can be kept as remove_children, but with an additional boolean argument free_children which is by default true. While it's true on each children node would be called queue_free(), if it's false queue_free() wouldn't be called.

There's no use case for remove_children without freeing the nodes, it's just asking for memory leaks.

@akien-mga Yes, you're right, but it would be noticed in the documentation. Also, it provides more flexibility for Godot user, because if you have links to all children and you want to do something with them you would have the ability to do this with remove_children(false)

Yes, but that's not a real life use case, so there's no point adding a feature for it which users might use by mistake, thinking it will free children (many users won't read documentation thoroughly).
If you really want to remove children for the scene for which you already saved references to them, you can use a for loop, it's really a corner case.

@akien-mga Ok, I agree with you. Maybe add to docs dedicated section where explains about memory management. I know about this page, but it doesn't where I should call free() method and where shouldn't. Also, this page targeted for cpp devs.

Closing this in favor of proposal: https://github.com/godotengine/godot-proposals/issues/764


Return User with ObtainJSONWebToken and token_auth decorator

currently the ObtainJSONWebToken mutation, specifically the @token_auth decorator, doesnt return the user with the token so you have to send two requests to get the user data after logging in.
Because token_auth is written as a decorator (an area I'm not super comfortable with) it makes it difficult to extend this mutation to get the user data, so you currently have to rewrite the entire decorator just to add payload.user = user in the on_resolve method inside it.

Hi @nwaxiomatic !,
you can add any field in the payload, see the documentation:
https://django-graphql-jwt.domake.io/en/latest/customizing.html
https://django-graphql-jwt.domake.io/en/latest/relay.html#customizing

amazing thanks!


Bump up Gradle version to 3.3

Summary
This commit bumps up the project and application Gradle version to 3.3.
Background, Problem or Goal of the patch
N/A.
Design of the fix, or a new feature
This includes the following changes:

Upgrade gradle wrapper version in the project
Upgrade gradle wrapper version of the default Asakusa application projects
Add a test of asakusaUpgrade task about the target version

Related Issue, Pull Request or Code
N/A.
Wanted reviewer
N/A.

BUILD SUCCESS. <jenkins-prb-asakusafw-sdk-111>


Setup Dev and Main Branches

Add dev branch and setup continuous integration

CI is being done in this ticket:
https://github.com/0xBootleggers/bufficorn/issues/10


import cycle not allowed when install from Go

I haven't used Go lang before. So after installed to a custom location in Linux, and export GOROOT as well as GOPATH with my custom path, I got a import cycle not allowed error for go get github.com/ericchiang/pup, details as follow:
import cycle not allowed
package github.com/ericchiang/pup
        imports bytes
        imports errors
        imports runtime
        imports runtime/internal/atomic
        imports unsafe
        imports runtime

searched but still can't figure out what's the problem.. Anyone helps?

I believe this has to do with an incorrect GOROOT installation. This error is indicating that there's an import cycle in "runtime", a standard library package that's outside of pup.
Have you followed the Go installation guide and tested the example there?
https://golang.org/doc/install

@ericchiang Reset GOROOT to path/to/go instead of path/to/go/bin and installed pup successfully. Thanks a lot!


Refactor Containerfile

Move to multistage builds to better support downstream OSBS. This allows
us to now install gcc into its own layer and not deal with packages
missed on removal.
Signed-off-by: Paul Belanger<EMAIL_ADDRESS>

Pull-request updated, HEAD is now dfccfcc00fd9c1243be3ee8ade693b1858b0332e


Separate project classes for better modularity and scalability

@ArthurCintra01 whenever you got time to review it, it would be great!


Example using dask.array.learn on non-trivial data

We built dask.array.learn a long while ago https://github.com/blaze/dask/pull/138 .
It's a fairly trivial pairing of sklearn and dask.array (and honestly something that sklearn does just fine with a for loop).  Still, it's something that more established libraries show off, so we might as well have a clear user example on how to combine a large HDF5 file with an sklearn classifier using dask.array, probably something like the following
from sklearn import MyFavoriteEstimator
e = MyFavoriteEstimator()

import h5py
X = h5py.File(...)['/X']
y = h5py.File(...)['/X']

import dask.array as da
X = da.from_array(X, chunks=(...))
y = da.from_array(y, chunks=(...))

da.learn.fit(e, X, y)
e.predict(new_X)

The hard thing here is to find a large and meaningful dataset and the right estimator within sklearn that supports partial fitting.  Then this work should be publicized in some way, perhaps both in documentation and in some sort of blogpost / notebook.

Dictionary learning with a large stack of images would be an interesting application.

I agree.  It might be good through to have a straight vanilla problem as well that fits into the above mold.  I think I'm mostly looking for a demonstration of capability of the common case.

Once I finally add dask to hyperspy, PCA (or, more likely, incremental PCA ) will no doubt be one of the most widely used features with big datasets.
It's extremely common to perform dimensionality-reduction on electron microscopy datasets, and later on perform ICA or something of that sort.

Incremental PCA does seem like a better example -- dictionary learning can
be very slow. How is it different from the existing chunked linear algebra
routines already in dask, though?
On Tue, Nov 3, 2015 at 2:04 AM, Tomas Ostasevicius<EMAIL_ADDRESS>
wrote:

Once I finally add dask to hyperspy, PCA (or, more likely, incremental PCA
http://scikit-learn.org/stable/modules/decomposition.html#incremental-pca
) will no doubt be one of the most widely used features with big datasets.
It's extremely common to perform dimensionality-reduction on electron
microscopy datasets, and later on perform ICA or something of that sort.
—
Reply to this email directly or view it on GitHub
https://github.com/blaze/dask/issues/817#issuecomment-153304155.

It may not be - I have not had a look. In my mind (never having had to implement it myself) PCA is just an SVD with some pre- and post-processing. On the other hand, you don't have to reinvent the wheel and just plug-and-play with different decompositions (NMF, PCA, incremental PCA)

My guess is that algorithms like SGD might still be valuable to demonstrate.

How about blaze streaming from a database to sgd? That would be really cool.

This is ill-formed and stale.  Closing.
Also: http://matthewrocklin.com/blog/work/2016/04/20/dask-distributed-part-5


Augment d3.csv.format to handle an array of objects

Currently, d3.csv.format is the reverse of d3.csv.parseRows [1]. It would be useful if it could also reverse the d3.csv.parse function. In other words, if it could take as input an array of objects, each with the same keys, and return a CSV of values with the header row consisting of the key names.
[1] https://github.com/mbostock/d3/wiki/CSV

This is "unpossible", at least with a naïve implementation, due to the nondeterministic ordering of keys in objects. From MDC:

A for...in loop iterates over the properties of an object in an arbitrary order (see the delete operator for more on why one cannot depend on the seeming orderliness of iteration, at least in a cross-browser setting).

Another reason why this is dangerous is that some objects may not have every key defined.
I think you could fix this problems with a two-pass approach. First, you'd iterate over the keys of every object, creating the union of all keys. The order of the keys would likely be arbitrary, but you could at least make it match the iteration order in the case where all of the objects have all of the keys defined. Then, you'd iterate over all the objects again, and extract the values. I suppose this would also mean mapping null and undefined values to the empty string (though you could map these to "null" and "undefined", and only generate the empty string if the given property is missing via in).


can we create tag: latest instead of hardcoding version

Hi,
Is there any way you can find a way to have 'latest' tag for version instead of number.
So we don't need to worry about latest versions
anypoint = {
  source = "mulesoft-anypoint/anypoint"
  version = "latest"
}

Hi @arun-tu,
After thinking about this, I don't think we are ready to use the latest tag just yet. Using hardcoded version gives our users the ability to revert back to their original version in case of a bug or inconsistency in newer versions ...


Basic authentication remove/reset doesn't work.

I did set security as per below.
solrOptions:
security:
authenticationType: Basic
It generated bootstrap and auth secret and authentication and authorization was working fine. Somehow admin user doesn't able to access "Security" in admin UI "You do not have permission to view the security panel.". Though admin role does have permission "security-read" and "security-edit".
To reset authentication, I removed the secrets and did helm upgrade and restart all solr cloud pods and operator pod. It generated new bootstrap and auth but still new credentials doesn't work but old credentials are working and persists "Security" access issue.
Even I removed SolrOptions- security and again applied helm upgrade but it still has authentication enabled and old (first time) credentials are working.
How can I remove and/or reset authentication/authorization ?

The issue is that the security.json file lives in Zookeeper, not in any of the Solr pods.
If you don't want to delete your cluster:

You can run a kubectl exec -it <solr-pod-name> -- solr zk rm <chroot-if-exists>/security.json.  Insert one of the Solr Pod Names
Then run kubectl delete pod <solr-pod-name>.

The pod will come back online and repopulate the security.json field.
If you do want to delete you cluster.

delete the Solr cluster via helm delete <solr-release-name>
Wait for everything to go down.
run kubectl get pvc. If there are any ZK pvcs left, delete them.
Recreate your solr helm release.

We can make the docs better here.

You can use this issue still. What version of Solr are you running?

chart version - 0.6.0
Solr version - 8.11


Interrupt for Win terminal not returning prompt

Description
Trying to interrupt an embedding in a Windows terminal under an ipython interpreter acknowledges
the interrupt but does not return control to user:
In [28]: import minorminer
    ...: minorminer.find_embedding(Q.keys(), sampler.edgelist)
caught interrupt; embedding cancelled
caught interrupt; embedding cancelled
caught interrupt; embedding cancelled

To Reproduce
I'm running find_embedding(Q.keys(), sampler.edgelist) where Q is 500 nodes highly connected (about 50% of a clique) and sampler is the DW_2000Q_6. (Low expectations of success, I wanted the error message)
Expected behavior
CNTR-C should return prompt to user.
Environment:

OS: WIN 10 terminal
Python version: ipython 3.6.5

Additional context
Add any other context about the problem here.

This is fixed in the current version, will be included in the next release.
See #117 for more info:
https://github.com/dwavesystems/minorminer/pull/117/commits/41217eeda6002ca419a71c40d68824345a6e31f4

Thank you!


[Build] Bower Overwrites Files [!]

I use semantic as a bower component in my frontend source folder, thus locating it in bower_components
After upgrading to 1.0 I decided to modify a few things with the help of the site.variables file located in src/site/globals. I did this and successfully built my own semantic.css with gulp build.
Then when updating semantic to 1.0.1 with bower update it deleted my semantic.json, theme.less files along with the site folder. Not too happy with this. I can restore the files through git but for future updates of semantic I would like to know how my customization should be done so that it will not be overwritten.

So if this is closed, what is the proposed solution? I read the other thread but it only seemed to be a general discussion of best practices, not anyone offering a concrete way of solving this problem. I can change to npm instead of bower if the workflow would work there.

@vikeri The solution will launch early next week along with other changes to build tools, like importable watch and build tasks, and first party meteor integration.
NPM will be the preferred install path. It will crawl for a semantic.json and either run update or install scripts.
You can take a peek at it the underlying code here if you're interested
https://github.com/Semantic-Org/Semantic-UI/tree/meteor/tasks
I still need to do some testing to make sure the changes don't introduce any other issues. So this will probably launch next week.

Great news! So are those task folders included in the newest npm package or how would I go about exactly to install and configure it?

I'm still debugging some edge cases. My big fear is releasing new build tools that prevent people from working with SUI immediately. Beyond this testing, and rewriting some admin tasks meteor branch is just about done.
See readme here: https://github.com/Semantic-Org/Semantic-UI/tree/meteor/src#setup

Moved everything into next, i want to review a few more things before pushing

Ok! Thanks for keeping us posted :)

1.9.0 is now published. I encourage you to check it out.

Good stuff! Downloaded with npm and did the install. But I'm still not 100% sure of how the supposed install config should be, my hypothesis the following:

I put the install in eg. lib-semantic
I exclude that folder from my git-repo so that it can be updated without showing up in git.
I specify that my site folder should be outside of lib-semantic, eg. ../src/semantic since those are files that I do want to monitor with git
I add the semantic.json to git

My question is hence if this accomplishes these two objectives:

I can update the semantic core files with npm update without it showing up in git
When I update semantic my own edits to the theme are not overwritten

I now tried this setup with a fresh install and even though the installer finds my semantic.json it says it can't find the files in the lib-semantic folder (correct since that folder does not exist in the repo). Thereafter it ignores the values in semantic.json it and runs the standard installation prompts with the standard defaults.

@vikeri Make sure the base in semantic.json points to wherever you plopped in the files relative to semantic.json.
It should be able to detect the files and update them instead of triggering install.

The base points to the correct folder, the issue is that the folder does not exists since I do not want it to be tracked by git. This since I got the impression that those files will be overwritten when I update Semantic UI.  I do not want git to notice the upgrade of a package.
I had the impression that the only files I had to change to make my own theme were those in site, hence I would like to only version that specific folder. Ideally the other folders would update and install themselves when i do npm install.
{
  "base": "lib-semantic/", // In my .gitignore and thus would like the install to create it
  "paths": {
    "source": {
      "config": "src/theme.config",
      "definitions": "src/definitions/",
      "site": "../src/site/", // In git since that is where I customize my own theme
      "themes": "src/themes/"
    },
    "output": {
      "packaged": "dist/",
      "uncompressed": "dist/components/",
      "compressed": "dist/components/",
      "themes": "dist/themes/"
    },
    "clean": "dist/"
  },
  "permission": false,
  "rtl": false,
  "version": "1.9.1"
}

The new build tools no longer have issues with overwrites, there's a manual upgrade script baked in for npm.
This will only update if the installed version is different than the version in semantic.json
https://github.com/Semantic-Org/Semantic-UI/blob/master/tasks/install.js#L84


admob pro plugin unable to install in Intel xdk 2727

No matter what proyect i try to build, always error when instal

i got that problem as well (trying to build for IOS)

I already solve it, it's kind of a server problem, download the plugin from the web, and then instal it from your own directory :)

xai1985, thank you. It solved for me too.

:) nice


Java-CEF v114 is available

Chrome v114 is now available for java-cef.  Was hoping this could be updated to the latest.
https://bitbucket.org/chromiumembedded/java-cef/commits/

Yes, I am aware of that. Sadly the build for 114 is currently failing for jcefbuild, which this project depends on. I will leave this issue open and resolve it once I had the time to update to 114.

Now we have v116.


Discussion: Nuget-Parity:  Check for missing MSBuild Imports

.targets files get included conditionally, so that they don't error out if they don't exists.
<Import Project="..\packages\PepitaPackage\build\$(__paket__PepitaPackage_targets).targets" Condition="Exists('..\packages\PepitaPackage\build\$(__paket__PepitaPackage_targets).targets')" Label="Paket" />
On the other hand, this means that should for some reason the file not exist, it will just be silently ignored.
The conditional import is required so that the projects can be opened in Visual Studio before package restore, otherwise VS would pop open a message box.
For this reason, nuget creates a Task which checks on build time that the imports exist:

The nuget check looks like this:
  <Import Project="..\packages\PepitaPackage.1.21.4\build\PepitaPackage.targets" Condition="Exists('..\packages\PepitaPackage.1.21.4\build\PepitaPackage.targets')" />
  <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild">
    <PropertyGroup>
      <ErrorText>This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText>
    </PropertyGroup>
    <Error Condition="!Exists('..\packages\PepitaPackage.1.21.4\build\PepitaPackage.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\PepitaPackage.1.21.4\build\PepitaPackage.targets'))" />
  </Target>

What do you think, would it make sense to replicate this functionality in Paket?
I was hit by this and it took me a few minutes to figure out why a build didn't work.

think we should wait to see how they change MSBuild to support packages. They are currently changing a lot. Maybe this gets easier in a couple of months.

@0x53A Would be interesting what they do in the new world... Because IIRC they are just copying targets  files in the obj directory. But there you cannot check if it doesn't exist at build time :)
So yes I guess we don't have this problem in the new world. Question is: Is it worth it to fix it in the old world. Is it enough to skip the existence check? I guess it is not because we silently use that when the targets file is only for a specific framework...
This in turn means you need to handle that case as well (what NuGet doesn't need). So it's probably more complicated than you think.

The only problem with this is Fsharp.Compiler.Tools.  If the msbuild files are missing for some reason you get very weird follow up errors (like target build not defined). problem is people don't understand those error messages while they understand missing files

I think we are saying the same thing, that there should be an explicit check, and an explicit error?

Ah okey, than I'm all in ;)


Make secp256k1 optional

Add feature "crypto" and feature gate anything that touches secp256k1 behind it.
Fix: #526
Note
Does not add doc(cfg for private functions, do we want that?

Cool! Needs doc(cfg(...)) in public items though.

Doing this I learned that doc(cfg has no effect on enum variants.

Observation: The feature guarded imports are pretty ugly.

Doing this I learned that doc(cfg has no effect on enum variants.

 We will need to document it in text then.

The feature guarded imports are pretty ugly.

You can decrease the ugliness by putting guarded impls into separate modules:
pub struct Foo {
    // ...
}

impl Foo {
    // unconditional impls
}

#[cfg(feature = "secp256k1")]
#[cfg_attr(docsrs, doc(cfg = "secp256k1"))] // please check that this doc is propagated to the items inside, I'm not sure it is
mod secp256k1_impls {
    use secp256k1::PublicKey;

    // Yes, this works fine, the restriction is that it has to be the same crate
    impl Foo {
        // Something that uses Public key here
    }
}

Went to report it and when I wrote a minimal reproducer I saw it documented correctly

Face palm, no idea where I looked yesterday - it is as you say when I hacked up an example just now. My bad.

You can decrease the ugliness by putting guarded impls into separate modules:

That's a good idea.

Added docs attributes to enums. I went over the diff and didn't see any chunks of code that would be better in sub-modules.

Rebase only on other changes.

CI was red so I rebased and checked/re-did a bunch of the feature guards on import statements.

@TheBlueMatt compile time of whole secp256k1 is quite significant since it also compiles the build script with its dependencies and requires C compiler which may be annoying to get to work on unusual platforms. Further short compile times are interesting for package vendors since new versions of software are generally compiled from scratch.

I package a few Debian packages that do use rust-bitcoin and the trouble is that sometimes if something goes wrong I have to recompile everything. electrs uses LTO for instance. So decreasing the compile time is quite interesting. But if multiple people are against it I would respect that.

I have zero opinions on this, will wait for others to weigh in before rebasing or closing.

Since I do not have strong feelings and no one has weighed in with any, leaving for another day.

I don't want to push this overly strongly but I just remembered one more argument: dealing with C crap is often painful experience, especially when cross-compiling or on less common OSes. Being able to avoid it can help. We had a bunch of issues at electrs, although admittedly, they were caused by rocksdb, not secp256k1. And yes, secp256k1 is quite painless overall, but still there's some risk.

Let's revisit once the crate smashing is done. My feeling with this is "only if it's easy". I agree that secp256k1 is likely to be a particularly big pain point, but OTOH it's also responsible for the bulk of this library's functionality. For example, after crate smashing we may have a bitcoin-crypto crate that we could simply make optional and be done with it.
If we try to do this now it's just going to be another complication as we're rearranging other stuff.

OK, that makes sense.

I am trying to build a statically linked executable that has rust-bitcoin as dep with musl. It doesn't need secp256k1 and it is failing on building it so it may be one reason to have this.
The other option is understanding why the build fails with a strange error  error occurred: Failed to find tool. Isaarch64-linux-musl-gcc installed? while I am trying to target  aarch64-unknown-linux-musl

Details

error: failed to run custom build command for `secp256k1-sys v0.8.1`
Caused by:
process didn't exit successfully: /home/casatta/git/dinasty/target/release/build/secp256k1-sys-7ab9d397732e17b3/build-script-build (exit status: 1)
--- stdout
TARGET = Some("aarch64-unknown-linux-musl")
OPT_LEVEL = Some("3")
HOST = Some("x86_64-unknown-linux-gnu")
cargo:rerun-if-env-changed=CC_aarch64-unknown-linux-musl
CC_aarch64-unknown-linux-musl = None
cargo:rerun-if-env-changed=CC_aarch64_unknown_linux_musl
CC_aarch64_unknown_linux_musl = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
RUSTC_LINKER = None
cargo:rerun-if-env-changed=CROSS_COMPILE
CROSS_COMPILE = None
cargo:rerun-if-env-changed=CFLAGS_aarch64-unknown-linux-musl
CFLAGS_aarch64-unknown-linux-musl = None
cargo:rerun-if-env-changed=CFLAGS_aarch64_unknown_linux_musl
CFLAGS_aarch64_unknown_linux_musl = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("neon")
cargo:rerun-if-env-changed=CC_aarch64-unknown-linux-musl
CC_aarch64-unknown-linux-musl = None
cargo:rerun-if-env-changed=CC_aarch64_unknown_linux_musl
CC_aarch64_unknown_linux_musl = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
RUSTC_LINKER = None
cargo:rerun-if-env-changed=CROSS_COMPILE
CROSS_COMPILE = None
cargo:rerun-if-env-changed=CFLAGS_aarch64-unknown-linux-musl
CFLAGS_aarch64-unknown-linux-musl = None
cargo:rerun-if-env-changed=CFLAGS_aarch64_unknown_linux_musl
CFLAGS_aarch64_unknown_linux_musl = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("neon")
running: "aarch64-linux-musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-I" "depend/secp256k1/" "-I" "depend/secp256k1/include" "-I" "depend/secp256k1/src" "-Wall" "-Wextra" "-DSECP256K1_API=" "-DENABLE_MODULE_ECDH=1" "-DENABLE_MODULE_SCHNORRSIG=1" "-DENABLE_MODULE_EXTRAKEYS=1" "-DECMULT_GEN_PREC_BITS=4" "-DECMULT_WINDOW_SIZE=15" "-DUSE_EXTERNAL_DEFAULT_CALLBACKS=1" "-DENABLE_MODULE_RECOVERY=1" "-o" "/home/casatta/git/dinasty/target/aarch64-unknown-linux-musl/release/build/secp256k1-sys-ee85cd798ceda1c6/out/depend/secp256k1/contrib/lax_der_parsing.o" "-c" "depend/secp256k1/contrib/lax_der_parsing.c"
cargo:rerun-if-env-changed=CC_aarch64-unknown-linux-musl
CC_aarch64-unknown-linux-musl = None
cargo:rerun-if-env-changed=CC_aarch64_unknown_linux_musl
CC_aarch64_unknown_linux_musl = None
cargo:rerun-if-env-changed=TARGET_CC
TARGET_CC = None
cargo:rerun-if-env-changed=CC
CC = None
RUSTC_LINKER = None
cargo:rerun-if-env-changed=CROSS_COMPILE
CROSS_COMPILE = None
cargo:rerun-if-env-changed=CFLAGS_aarch64-unknown-linux-musl
CFLAGS_aarch64-unknown-linux-musl = None
cargo:rerun-if-env-changed=CFLAGS_aarch64_unknown_linux_musl
CFLAGS_aarch64_unknown_linux_musl = None
cargo:rerun-if-env-changed=TARGET_CFLAGS
TARGET_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("neon")
running: "aarch64-linux-musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-I" "depend/secp256k1/" "-I" "depend/secp256k1/include" "-I" "depend/secp256k1/src" "-I" "wasm/wasm-sysroot" "-Wall" "-Wextra" "-DSECP256K1_API=" "-DENABLE_MODULE_ECDH=1" "-DENABLE_MODULE_SCHNORRSIG=1" "-DENABLE_MODULE_EXTRAKEYS=1" "-DECMULT_GEN_PREC_BITS=4" "-DECMULT_WINDOW_SIZE=15" "-DUSE_EXTERNAL_DEFAULT_CALLBACKS=1" "-DENABLE_MODULE_RECOVERY=1" "-o" "/home/casatta/git/dinasty/target/aarch64-unknown-linux-musl/release/build/secp256k1-sys-ee85cd798ceda1c6/out/depend/secp256k1/contrib/lax_der_parsing.o" "-c" "depend/secp256k1/contrib/lax_der_parsing.c"
--- stderr
error occurred: Failed to find tool. Is aarch64-linux-musl-gcc installed?
warning: build failed, waiting for other jobs to finish...

@RCasatta interesting. I think the message comes from cc and that crate is most likely the one to file an issue against.


az webapp up --runtime option should either be implemented or removed

Here's the doc for az webapp up. It says there is a --runtime option
https://docs.microsoft.com/en-us/cli/azure/webapp?view=azure-cli-latest#az_webapp_up
However, if I do:
call az webapp up --plan %app_plan% --name %app_name% --subscription %subscription_id% --resource-group %resource_group_name% --runtime "abc"
I get the error:
az: error: unrecognized arguments: --runtime abc
plus, az webapp up --help doesn't show a --runtime option.
If there is no --runtime option, it needs to be removed from the documentation. Or better yet, it should be implemented.

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

ID: 2983e943-cce1-effd-57d0-cce4b0c0a7e1
Version Independent ID: 4262c40a-7140-b420-58b5-5cf40ab2316e
Content: az webapp
Content Source: latest/docs-ref-autogen/webapp.yml
Service: app-service-web
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

webapp

@calvinsID this looks like a bug since we always want to auto-detect runtime for UP scenarios. --runtime parameter should be removed
FYI @panchagnula

@roalexan the --runtime option is new. To use it you will need to update your CLI to latest release.


Inpaint stops working after one generation - " Cannot export_stableart_exported_mask.png "

Found that 8-bit images are not affected by this issue - current work around is to convert all 16-bit images to 8-bit

Txt2Img - works fine and no issues. (8bit & 16bit images)
Img2Img - works fine and no issues. (8bit & 16bit images)
!!! - Inpaint - (16bit images) Works one time and then upon the second attempt of inpaint generation it appears the Quick Export function of PS stops working causing a crash prompt;

"Cannot export_stableart_exported_mask.png. Try to reload Photoshop and check that Quick Export as PNG is working"
Quick Exports as PNG works fine without issues with multiple savings through normal PS drop down menus on 16 bit image.
Recently Updated to Win10 22H2 and Updated PS23.x/Beta versions to most recent of PS Version: 25.0.0 20230906.r.37 and is when issue began. Did a FRESH install of Windows and ALL applications on new SSD and still same issue persists for 16-bit image Inpaint generation. Prior to updates etc system was working fine for months and months (since initial install of Stable.Art)
Win10 22h2 - 3060ti - 16gb RAM

same here - the plugin is unusable - win 11 - i'd like a solution since it seems other people are using it fine


WSL2 September 2023 allows for Mirrored Networking Mode

In the recent update post from WSL:
https://devblogs.microsoft.com/commandline/windows-subsystem-for-linux-september-2023-update/
One of the new features is New Networking Mode – Mirrored
among the notes about the feature:
Here are the current benefits to enabling this mode:
-     IPv6 support
-     Connect to Windows servers from within Linux using the localhost address <IP_ADDRESS>
-     Connect to WSL directly from your local area network (LAN)
-     Improved networking compatibility for VPNs
-     Multicast support

I would ask to maybe also mention that in the README of this repo,
since this new networking mode, may have made wsl-vpnkit obsolete..
Don't get me wrong, this Repo is amazing, it allowed me and many other WSL2 enthusiasts to use VPNs within WSL,
Without it I couldn't have worked efficiently for the last 2 years, so kudos to that ! 🎉
I'm just saying this new thing might be a good working alternative, so maybe it deserves a mention in order to spread the news..

You do also have to have Windows 11, version 22H2, build 255xx and above; I'm finding this still incredibly valuable on Windows 10 with a few of the PRed fixes applied.

The new networkingMode=mirrored is not guaranteed to work with all VPN:s. I am currently using it, but still have to use wsl-vpnkit to get the connectivity working.

And networkingMode=mirrored ist still only for Windows 11.
I am still on Windows 10, so I have to use vpn-wslkit, wich still works really good.

I also had some hope to use networkingMode=mirrored, but it does not work if the IPv6 stack is disabled. (https://github.com/microsoft/WSL/issues/11002)


Update iMazing to 1.3.7

Thank you for the contribution. It was merged directly as d56f199202ba3055a9677d649b550f9a1c3bda12 to keep commit history cleaner. Your contribution is still credited to you.


Fix rrna_list variable issue

Hi,
I was updating the default --rrna_list var value because it was preventing from the ribozero option to work proparly.

Thanks Yair


docs: moving google-cloud-examples to java-docs-samples

Moving the google-cloud-examples module from google-cloud-java
repository (main_202208 branch).
https://github.com/googleapis/google-cloud-java/tree/main_202208/google-cloud-examples

First confirm with Averi about the move is ok.
Second, fix the lint issues.

Fixes #issue

It's a good idea to open an issue first for discussion.

[ ] I have followed Sample Format Guide
[ ] pom.xml parent set to latest shared-configuration
[ ] Appropriate changes to README are included in PR
[ ] API's need to be enabled to test (tell us)
[ ] Environment Variables need to be set (ask us to set them)
[ ] Tests pass:   mvn clean verify required
[ ] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[ ] Please merge this PR for me once it is approved.

To add DEE Monorepo Migration Tracker.


Cant place rails

Expected Behaviour
Rails to be placed without game crashing
Actual Behaviour
Game world saves and crashes
Reproduction Steps
Steps to reproduce the behaviour:

Use rail nodes and connectors to connect rails

Game crashes

Crash Report
[https://mclo.gs/lrVmtrl]
Screenshots
No screenshots are possible
Environment

Minecraft Version: 1.19.4
Installed Mods: MTR and Architectury

Additional Information
Is it possibly my version or PC?

This is very strange, your forge and architectury versions are fine, it doesn't seem like an issue with your laptop, I am quite confused.

Duplicate of #744


missing errors blade when calling out of api routes

I was using in laravel 5.1 ,Here's an example for my confusing:
my .env setting:
API_PREFIX=api
API_VERSION=v1

and I was register routes like:
$api = app('Dingo\Api\Routing\Router');

$api->version('v1', function ($api) {

    $api->get('test' ,function (){
        return 'testing';
    });
});

when i calling "example.com/test" I can see it return "testing"
but when i call out of routes like "example.com/missing-view" it will always return
{"message":"404 Not Found","status_code":404}
and not view errors.404.blade
how can I let it still return error view when i visit out of api routes?

can't reproduce your issue.
With your config API_PREFIX=api, can you confirm "example.com/api/test" should return "testing".
"example.com/api/(any route)" should handle by dingo/api, and return json response as expected.
"example.com/api/404" return {"message":"404 Not Found","status_code":404}
"example.com/404" throw NotFoundHttpException or view if you have errors.404.blade, handle by laravel but not dingo/api.
show your php artisan route:list and php artisan api:routes for more details if still not fix.

@Panigale Will need more information to determine what the issue may be here.

@Panigale Are you still having this issue? No response in two weeks, gonna close out soon.


Error on vGPU

I got below err when I launch vslam stack. My environment is on vGPU in VMware.
I tested nvblox and it works well in the same VM.
Any guess what's wrong?
The VM has:

8x vCPUs
64G RAM
2x A10
256G SSD
OS: Ubuntu 20.04.4 LTS
dGPU 470.129.06

admin@omn-u20-mkomuro:/workspaces/isaac_ros-dev/ros_ws$ ros2 launch isaac_ros_visual_slam isaac_ros_visual_slam_isaac_sim.launch.py
[INFO] [launch]: All log files can be found below /home/admin/.ros/log/2022-06-15-06-07-12-816997-omn-u20-mkomuro-10633
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [component_container-1]: process started with pid [10646]
[component_container-1] [INFO] [1655273233.262291079] [visual_slam_launch_container]: Load Library: /workspaces/isaac_ros-dev/ros_ws/install/isaac_ros_visual_slam/lib/libvisual_slam_node.so
[ERROR] [component_container-1]: process has died [pid 10646, exit code -4, cmd '/opt/ros/foxy/lib/rclcpp_components/component_container --ros-args -r __node:=visual_slam_launch_container -r __ns:=/'].

Code is not head branch but it works in my local workstation (RTX2080Ti with the same OS and dGPU version).
git clone -b hemalshahNV-patch-1 --recurse-submodules https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common.git
git clone -b hotfix_1 https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_image_pipeline
git clone -b release-ea3-hotfix1 https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam

It appears that the process dies with no log or error message which could indicate any number of things unfortunately.
Are you using the Isaac ROS Common base Docker container to run within the VM instance? What version of CUDA is available in this VM instance?

Are you using the Isaac ROS Common base Docker container to run within the VM instance?
Yes.

It's CUDA 11.4.
I think it meets the requirements.
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common/tree/hemalshahNV-patch-1#x86_64
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam/tree/release-ea3-hotfix1#x86_64

Ubuntu 20.04+
CUDA 11.4 supported discrete GPU
Nvidia driver version >= 470.103.01

$ nvidia-smi
Wed Jun 15 15:13:12 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.129.06   Driver Version: 470.129.06   CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A10          On   | 00000000:0B:00.0 Off |                    0 |
|  0%   59C    P0   153W / 150W |   5488MiB / 22731MiB |     50%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Could you try with the last Isaac ROS release? The abrupt process died in your log is usually indicative of running out of memory.

Sure.
But unfortunately, my VM server has a problem and our admin has been working on resuming the system.
Once he fixed the problem, I'll try new version of Isaac ROS.
If I still have an issue with the latest Isaac ROS, I'll open a new issue.
Thanks!


Nest can't resolve dependencies of the ExplorerService (?, Reflector).

Getting this error when importing like so:
import { SlackModule } from 'nestjs-slack-bolt';
@Module({
  imports: [SlackModule],
  providers: [ReportingService],
  exports: [ReportingService],
})

Error
Nest can't resolve dependencies of the ExplorerService (?, Reflector). Please make sure that the argument ModulesContainer at index [0] is available in the SlackModule context.

Potential solutions:
- Is SlackModule a valid NestJS module?
- If ModulesContainer is a provider, is it part of the current SlackModule?
- If ModulesContainer is exported from a separate @Module, is that module imported within SlackModule?
  @Module({
    imports: [ /* the Module containing ModulesContainer */ ]
  })

Error: Nest can't resolve dependencies of the ExplorerService (?, Reflector). Please make sure that the argument ModulesContainer at index [0] is available in the SlackModule context.

Potential solutions:
- Is SlackModule a valid NestJS module?
- If ModulesContainer is a provider, is it part of the current SlackModule?
- If ModulesContainer is exported from a separate @Module, is that module imported within SlackModule?
  @Module({
    imports: [ /* the Module containing ModulesContainer */ ]
  })

same issue here

Hi,
I'm going to look into this problem

Hello, @simplenotezy  which version of NestJs are you using?

Hello, @simplenotezy  which version of NestJs are you using?

Hey! Version 9

The last version 0.2.0 is only compatible with Nestjs10.
You should use an old version


attention layer

h = self.sigmoid(torch.matmul(attention, x))
I found the attention alpha are multiplicated with original x instead of W * x, which is not same to the graph convolution network. Could you show me the reason? Thanks very much!

We follow the MTAD-GAT paper, in which they linearly transform the node features (multiplying with W) when calculating the attention weights, but when using attention weights to get new node representations (weighted sum), they use the original node features.
However, I see your point, and one could try to adapt the code to multiply attention weights with Wx to get new node representations.


Add "secret/data" to my "objectPath" HashiCorp Vault

Just tried to run the example with CS In Line Volume, but my secret path in HashiCorp Vault is "sandbox/k8s_infra/marketplace/account/my-new-app/db"
I spected that driver requests the path "/sandbox/data/k8s_infra/marketplace/account/my-new-app/db" instead its try to request "secret/data/sandbox/k8s_infra/marketplace/account/my-new-app/db".
Here my pod spec:
kind: Pod
apiVersion: v1
metadata:
  name: nginx-secrets-store-inline
  namespace: my-new-app
spec:
  containers:
  - image: nginx
    name: nginx
    volumeMounts:
    - name: secrets-store-inline
      mountPath: "/mnt/secrets-store"
      readOnly: true
  volumes:
    - name: secrets-store-inline
      csi:
        driver: secrets-store.csi.k8s.com
        readOnly: true
        volumeAttributes:
          providerName: "vault" # Vault ou azure
          roleName: "k8s_sre_infra_sandbox_own_namespace_role"
          vaultAddress: "https://vault.dc.infra.ifood-sandbox.com.br"
          objects:  |
            array:
              - |
                objectPath: "sandbox/k8s_infra/marketplace/account/my-new-app/db"
                objectName: "db_password"
              - |
                objectPath: "sandbox/k8s_infra/marketplace/account/my-new-app/app"
                objectName: "bla"

Hi @carnei-ro thanks for reporting this issue. I think there's probably a hard coded value somewhere in the vault provider. Adding @malnick and @anubhavmishra
By the way we have moved all the provider-specific stuff out of tree. So this issue might be better tracked if you close this here and open it in https://github.com/hashicorp/secrets-store-csi-driver-provider-vault/issues
Hope this help!

Closing in favor of https://github.com/hashicorp/secrets-store-csi-driver-provider-vault/issues/17


[5.7] Add AsPivot trait.

Hi,
TL;DR:

Just moved the core of the Pivot class to a trait.
No breaking change.
All tests green.

Why:
In fact, like a lot of developers, I have my own abstract Model class which is extended by all my eloquent models. It allows me to add directly some methods that all can share.
Extending the pivot class prevent this classic way of doing.
It's why I've added this trait: to allow devs to implement the pivot methods to any of their Model.
Thanks.
Matt'

@deleugpn no problem with changing that. I like the "use as pivot" way.

I'm fine with AsPivot.

@mathieutu @idsulik any interest in adding a matching AsMorphPivot trait?
To respond to @taylorotwell's original request for justification in #34488 (see comment) you would need to use AsMorphPivot as a trait for the same reason that you would need to use AsPivot as a trait: you are extending the base Model class with a customized Model class and need the Pivot & MorphPivot models to extend your custom Model class instead of the base Laravel Model class.
You can't just extend the base MorphPivot model in that case because the base MorphPivot class extends the base Pivot class which extends the base Model class. Instead, you would need to create your own MorphPivot class that extends your own Pivot class that extends your own Model class that extends the base Laravel Model class. One such example of the need for custom base Model classes is the Winter CMS base Model class that adds our dynamic class extension system and custom events to all models within Winter CMS (see https://github.com/wintercms/storm/blob/develop/src/Database/Model.php).
Currently, we have to extend our custom Pivot model and reimplement all of the Laravel logic (see https://github.com/wintercms/storm/pull/64/files#diff-44330773d7e77b50c2bfd6a051c1ff1c0b538dd7d03caf65062649d7798bfee9), adding AsMorphPivot as a trait would make it so that we didn't have to do that.
One difference that I would suggest from the original #34488 is that the AsMorphPivot trait shouldn't itself include the AsPivot trait since I think the only valid use case for this change is the one I described above and that use case does not benefit from having the AsMorphPivot trait automatically include the AsPivot trait.


UniRx signal integration doesn't work with .net 4.6

Issue
The UniRx signal integration (ZEN_SIGNALS_ADD_UNIRX) doesn't work in Unity 2017.x with UniRx because UniRx moved to conditionally using System.IObservable
Source from UniRx IObservable
using System;

#if !(NETFX_CORE || NET_4_6)

namespace UniRx
{
    public interface IObservable<T>
    {
        IDisposable Subscribe(IObserver<T> observer);
    }
}

#endif

In the SignalX classes, zenject references IObservable directly from UniRx
Signal0, Line 30
#if ZEN_SIGNALS_ADD_UNIRX
        public UniRx.IOZbservable<Unit> AsObservable
        {
            get
            {
                return _observable;
            }
        }
#endif

Solution
Easy fix. Remove the UniRx namespace from IObservable
#if ZEN_SIGNALS_ADD_UNIRX
        public IObservable<Unit> AsObservable
        {
            get
            {
                return _observable;
            }
        }
#endif

You already reference the UniRx namespace in the signal class.
Note
This also applies to the UniRx.Tuple<TParam1, TParam2> refernces in the Signal2 onward classes.

Some observations from a very brief look I took at this today:
I noticed that the copy of IObservable.cs within UniRx that I get when I install it from the asset store is different from the copy in the source code rep here.  The defines that are used to include the UniRx version of IObservable are different.  The code you posted appears the same as what's directly in the repo instead of the version froma sset store.
Also, it doesn't seem like the fix is as simple as removing UniRx when referencing IObservable, since you get ambiguous reference errors in this case when you set scripting runtime to 4.6
I'm also unclear on how to reproduce this issue since I'm unclear on how to get UniRx to not define the IObservable class when installed from asset store

I should have mentioned that sorry.
neuecc hasn't really committed much to UniRx in a while (busy with other projects.)
He hasn't pushed a new build on the assetstore or done a release since Sep 30, 2016.
The most recent assetstore and release doesn't work with .net 4.6
However he did commit changes to UniRx to give it .net 4.6 support on July 6th 2017
https://github.com/neuecc/UniRx/commit/6ea038d114ffa1f709eeb6ebc2701de8d0248ee4
The only way to get it is to pull from repo.
So yeah I'm not really sure what a good solution is since it's not the actual release build (but again current release build doesn't work.)
I've updated it in my own project so it all works fine as I don't care about .net 3.5 support.
I just thought it should be something you were aware of for when/if the fix is pushed to assetstore.

Ah yes I understand what you mean now.  It seems like the version of UniRx that you install from asset store does compile properly and work when using .net 4.6, but it's painful because it still uses UniRx.IObservable everywhere so you have to explicitly reference that in any code that includes namespace System and namespace UniRx in the same file.
So we could change zenject to not run using UniRx when 4.6 is enabled, then change UniRx.IObservable to just IObservable.  But then that would only work with the copy of UniRx from the github repo and would break when trying to use it with the copy of UniRx that's in asset store...
So I think we should probably just wait for UniRx to update the asset store version with the NET_4_6 if statement that you pasted above before making any change on our side

Whats the current solution to this? I keep getting Observable.AsObservable<T>(IObservable<T> is not a method, which is not valid in the given context whenever I try to subscribe to it.

I believe this is fixed now that UniRx has updated the asset store version


[Bug] Dropping files

Insomnia Version: 5.9.6 (<IP_ADDRESS>3)_
Operating System: macOS 10.12.6

Details

drag any file from Finder onto the Insomnia app window opens the file in Insomnia
if the file was dropped somewhere other than the Preview pane, this renders Insomnia unusable, requiring an app restart

Expected result would be for Insomnia to either ignore the drop operation, or to respond appropriately to a limited set of file types (eg. for imports)

Hey @crispinb, thanks for reporting this. It should definitely be fixed. I think the ideal behavior for this would be to prompt the user to import the file after dropping.


KV: Add enabledForDiskEncryption and enabledForTemplateDeployment

Add enabledForDiskEncryption and enabledForTemplateDeployment to Key Vault properties

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Hi @seanbamsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@seanbamsft, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, AZPRBOT;

@azuresdkci add to whitelist


added notebook with erddappy and simple class wrap

This PR address issue #1

Please ignore the CI errors for now. We don't really have anything to test yet.

nbviewer link to facilitate the vizualitation of the notebook: https://nbviewer.jupyter.org/github/callumrollo/ohw20-proj-glide-data-fetcher/blob/master/notebooks/demo.ipynb
How do you envision the time/space query API? argopy has a .region but region does not really encompass time IMO. What would be a better name that would mean both? Maybe just .query?

.query sounds sensible. I envisage taking the arguments supplied to this and passing them to errdappy's constraints
working on it now

This commit addes a query method as discussed above. It's rough araound the edges and requires the user to supply lat, lon and time constraints all at once and in the correct order

Just now catching up! I agree, .query would be better. And we will do a something similar to argopy .float as well right? What if we name that one .id_query? Are those too similar?

@LindsayRAbrams when you have some time can you read the notebook and let us know what you think? A good API is usually ok when someone can read and understand what is going on without asking the devs about it, so you'll be our "proof reader." If you don't understand it, that means we need to work a bit more on the design.

Just now catching up! I agree, .query would be better. And we will do a something similar to argopy .float as well right? What if we name that one .id_query? Are those too similar?

Yep. But I was thinking about using the ERDDAP dataset_id instead, so we can get ERDDAP info tables and map 1-1 there.

This is my first time working with classes and it's a very rough notebook. Let me know if stuff doesn't make sense and feel free to add comments/overwrite

This is my first time working with classes and it's a very rough notebook. Let me know if stuff doesn't make sense and feel free to add comments/overwrite

Don't worry about that part now. When we port this to the library I'll guide you there. (Although I'm not an expert as well :smile:).
My main goal is to come up with an API that will be easy to use and that users will find pleasant to work with. The "raw" erddadpy are a bit involved and not really meant to be easy for a specific dataset. When we narrow the scope, like glider or argo, we can do better than erddapy.

Yes reviewing the notebook now. You both definitely have more experience than me so I can definitely see if there is anything that doesn't make sense to me

I can mostly follow along so far. I have a few questions/comments:

So glider_grab.fetcher.dataset_id = "sp022-20170209T1616" is basically the equivalent to argopy's .float right?
Are there any other glider variables we would want to include? Do any of these datasets include dissolved oxygen or chlorophyll concentration?
The only thing I was kinda confused about was the time_parse function. Is this necessary because erddapy requires the time to be in ISO 8601 format?
I really like the 'glider_grab.query' function, very easy to use like argopy's .region

Thanks for the feedback Lindsay!

So glider_grab.fetcher.dataset_id = "sp022-20170209T1616" is basically the equivalent to argopy's .float right?
Sort of, these strings identify a glider but also a time as, unlike floats, gliders are redeployed (except those donated to Neptune). The class I've just added to generate a list of available datasets could be expanded to identify multiple datasets from the same glider perhaps?

Are there any other glider variables we would want to include? Do any of these datasets include dissolved oxygen or chlorophyll concentration?
Yes! We want to expand this list but, at present, if you send a request for a variable that is not present on that server, you get an HTTP error that will halt your script. This needs to be looked into. Maybe a list of variables available on each server?

The only thing I was kinda confused about was the time_parse function. Is this necessary because erddapy requires the time to be in ISO 8601 format?
You're right that this isn't strictly necessary. With the time parser though, users can imput arbitrary datestrings like "2020-02-03" or "4th May 1970" and the parser will make the proper timestamp to pass to erddappy

I really like the 'glider_grab.query' function, very easy to use like argopy's .region
That's the plan. Imitation is the highest form of flattery :)

except those donated to Neptune

:rofl:


xSQLServerSetup: Get-TargetResource does not detect clustered SSAS instances

Details of the scenario you try and problem that is occurring:
After PR #326 is merged, Get-TargetResource will not collection information about a clustered Analysis Services instance. Currently, only clustered SQL Server instances are supported.
The DSC configuration that is using the resource (as detailed as possible):
None.
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
dev

If think this one got solve by PR #404. I can now install SSAS and Get-TargetResource successfully recognizes that analysis services is installed. Minor issues with the helper function Connect-SQLAnalysis that was submitted in issue #436 (work in progress).
Since the Get-TargetResource successfully detects SSAS instance in a cluster I will close this issue.


inshellisense: 0.0.1-rc.15 -> 0.0.1-rc.16

Description of changes
Update to latest version. No changes that effect build.
Diff: https://github.com/microsoft/inshellisense/compare/refs/tags/0.0.1-rc.15...0.0.1-rc.16
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@NixOS/nixpkgs-merge-bot merge


Improve readme

Some additionnal info in the readme, to get started.

Thanks for contribution

Thanks, I'm getting familiar with the project then will try to contribute more. Cheers


Nested groups can't have identically named routes.

I'm getting an error for identical routes when I don't believe there are identical routes.
Here is my minimum test case:
<?php

require 'vendor/autoload.php';

$app = \Slim\Factory\AppFactory::create();

$test = function(Request $request, Response $response){
	$response->getBody()->write('testing 123');
	return $response;
};

// Real pages:
$app->group('', function () use ($app,$test) {

	$app->group('/users', function () use ($app,$test) {
		$app->get('/test', $test);
	});

	$app->group('/clients', function () use ($app,$test) {
		$app->get('/test', $test);
	});
});

$app->run();

It's returning this error

PHP Fatal error:  Uncaught FastRoute\BadRouteException: Cannot register two routes matching "/test" for method "GET"

I was moving from Slim 3 to Slim 4 and renaming $this to $app to make my route groups work, but this error still shows up. Am I not doing it correctly?
My composer.json require section contains:
{
                "slim/slim": "^4.7",
                "slim/psr7": "^1.3"
 }

This worked fine previously, but now it throws an error. My understanding is that /users/test and /clients/test should be registered as routes. Only if there were two identical routes like /users/test and /users/test should it give this error.

I think I clicked on the wrong documentation on your website, your search feature searches through all versions... It fooled me...

I have the same issue.
It seems nested group routes doesn't work
<?php

require 'vendor/autoload.php';

$app = \Slim\Factory\AppFactory::create();

$test = function(Request $request, Response $response){
	$response->getBody()->write('testing 123');
	return $response;
};

// Real pages:
$app->group('', function () use ($app,$test) {

	$app->group('/users', function () use ($app,$test) {
		$app->get('/test', $test);    // this route must be registered as  '/users/test' , however is registered as '/test'
	});

	$app->group('/clients', function () use ($app,$test) {
		$app->get('/test', $test);  // this route must be registered as '/clients/test', however is registered as '/test'
	});
});

$app->run();


Display vlan ip range for specified domainid

Description
Currently if we try to list vlan ip range by passing
domainid then it lists for all domain. Make sure that
it lists only for that domain

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):
Before the changes
(local) 🐱 > list vlanipranges domainid=4aa4c-f694-45c0-8844-8d9a129
{
  "count": 14,
  "vlaniprange": [

After the changes
(local) 🐱 > list vlanipranges domainid=4560c-f694-45c0-8844-8d94129
{
  "count": 1,
  "vlaniprange": [

How Has This Been Tested?

@ravening, do you intend this for master/4.16 only or do you want this on older versions?

@ravening, do you intend this for master/4.16 only or do you want this on older versions?

@DaanHoogland 4.16 is good

ping @ravening

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

DomainVlanMapDaoImpl, i'd say.

@ravening you have a new conflict

@ravening can you move the logic to the DAO layer and fix the conflicts?

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

DomainVlanMapDaoImpl, i'd say.

@DaanHoogland Im using the same code which is used by account and pod also which are present above and below of this code. So even they needs to be moved away?
I searched in other places in the same file and they are also using the same logic. for eg: publicipaddress, loadbalancer, resourcetag, vlan, guestos

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

DomainVlanMapDaoImpl, i'd say.

@DaanHoogland Im using the same code which is used by account and pod also which are present above and below of this code. So even they needs to be moved away?
I searched in other places in the same file and they are also using the same logic. for eg: publicipaddress, loadbalancer, resourcetag, vlan, guestos

@ravening the rest of the code is not perfect and should be in DAOs as well. I'm not asking that of you now as I don't expect you to fix everything in one go, just to not add to the technical debt we have.

Ping @ravening can you address review and fix conflicts, thanks

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

DomainVlanMapDaoImpl, i'd say.

@DaanHoogland Im using the same code which is used by account and pod also which are present above and below of this code. So even they needs to be moved away?
I searched in other places in the same file and they are also using the same logic. for eg: publicipaddress, loadbalancer, resourcetag, vlan, guestos

@ravening the rest of the code is not perfect and should be in DAOs as well. I'm not asking that of you now as I don't expect you to fix everything in one go, just to not add to the technical debt we have.

@DaanHoogland
there are more than ten Dao.search() or Dao.searchAndCount() in ManagementServerImpl.java, and much more in QueryManagerImpl.java
we do not need to move everything into DAO, especially for the searches in multiple (more than 2) tables.

Ping @ravening can you address review and fix conflicts, thanks

@rhtyd done

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

DomainVlanMapDaoImpl, i'd say.

@DaanHoogland Im using the same code which is used by account and pod also which are present above and below of this code. So even they needs to be moved away?
I searched in other places in the same file and they are also using the same logic. for eg: publicipaddress, loadbalancer, resourcetag, vlan, guestos

@ravening the rest of the code is not perfect and should be in DAOs as well. I'm not asking that of you now as I don't expect you to fix everything in one go, just to not add to the technical debt we have.

@DaanHoogland
there are more than ten Dao.search() or Dao.searchAndCount() in ManagementServerImpl.java, and much more in QueryManagerImpl.java
we do not need to move everything into DAO, especially for the searches in multiple (more than 2) tables.

no, but those single table transactions that can we should.

no comment on this PR but all this DAO code really shouldn't be in the ManagementServer

@DaanHoogland any idea where else I can add this ?

DomainVlanMapDaoImpl, i'd say.

@DaanHoogland Im using the same code which is used by account and pod also which are present above and below of this code. So even they needs to be moved away?
I searched in other places in the same file and they are also using the same logic. for eg: publicipaddress, loadbalancer, resourcetag, vlan, guestos

@ravening the rest of the code is not perfect and should be in DAOs as well. I'm not asking that of you now as I don't expect you to fix everything in one go, just to not add to the technical debt we have.

@DaanHoogland
there are more than ten Dao.search() or Dao.searchAndCount() in ManagementServerImpl.java, and much more in QueryManagerImpl.java
we do not need to move everything into DAO, especially for the searches in multiple (more than 2) tables.

no, but those single table transactions that can we should.

@DaanHoogland agree .
as you can see in the code changes of this pr, the search on vlans has some join tables (DomainVlanMapDao, AccountVlanMapDao, PodVlanMapDao)

@DaanHoogland @weizhouapache let's get a consensus on this PR to try moving it forward as it seems the requested changes may not be applied. Would that be a reason for a -1 on this PR for any of you?
@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

If it's fixing a bug then +1 (sounds like you can't list Vlans for a domain?) but this would need testing

Packaging result: :heavy_multiplication_x: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1282

@blueorangutan test suse15 kvm-suse15

@davidjumani a Trillian-Jenkins test job (suse15 mgmt + kvm-suse15) has been kicked to run smoke tests

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1291

@blueorangutan test

@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Manually tested + 2xLGTM - ready for merge after tests pass

Trillian test result (tid-2098)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35205 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4634-t2098-kvm-centos7.zip
Smoke tests completed. 84 look OK, 5 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_nic
Error
135.77
test_nic.py

test_01_add_primary_storage_disabled_host
Error
0.57
test_primary_storage.py

test_01_primary_storage_nfs
Error
0.12
test_primary_storage.py

ContextSuite context=TestStorageTags>:setup
Error
0.21
test_primary_storage.py

test_02_list_snapshots_with_removed_data_store
Error
1.17
test_snapshots.py

test_01_secure_vm_migration
Error
156.38
test_vm_life_cycle.py

test_02_unsecure_vm_migration
Error
271.97
test_vm_life_cycle.py

test_03_secured_to_nonsecured_vm_migration
Error
148.02
test_vm_life_cycle.py

test_08_migrate_vm
Error
43.69
test_vm_life_cycle.py

test_hostha_enable_ha_when_host_in_maintenance
Error
305.13
test_hostha_kvm.py

@blueorangutan test

@weizhouapache a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

-0 if we allow for a mix of concerns in manager implementations we will increase the number of code conflict we will get over time. We should strive for better separation as much as possible. I'm not going to block this simple fix over this but it is an increasing concern. Calls to DAOs could have been made.

Trillian test result (tid-2107)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35409 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4634-t2107-kvm-centos7.zip
Smoke tests completed. 89 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

-0 if we allow for a mix of concerns in manager implementations we will increase the number of code conflict we will get over time. We should strive for better separation as much as possible. I'm not going to block this simple fix over this but it is an increasing concern. Calls to DAOs could have been made.

@DaanHoogland want to add this to cwiki / issues (as improvement) to track it later?

Manually tested + 2xLGTM - ready for merge after tests pass

Merging based on LGTMs, and manual / smoke tests.


Kubernetes connect cli telemetry integration

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

add to S169

Please add change log in HISTORY.rst.
Please also test locally and check the telemetry log in ~/.azure/telemetry/cache to see if the properties are expected.

Please add change log in HISTORY.rst.
Please also test locally and check the telemetry log in ~/.azure/telemetry/cache to see if the properties are expected.

I have updated the History.rst file. I have also verified in telemetry local cache that all expected properties are being stored