Merge geo.location.lon and geo.location.lat

Changes
https://github.com/open-telemetry/semantic-conventions/pull/1116 added geo fields. We started implementing support for this, and we noticed that for backends that have a dedicated geo point data type, having 2 distinct attributes (geo.location.lon and geo.location.lat) is very inconvenient. These two fields clearly belong together.
Backends that have a specialized geo point type could still merge those with some tricks, but that does not feel right. On the other hand, if a backend does not have specific support for such a field, still can store it as double[].
Therefore, this PR proposes to merge those 2 attributes into a double[].
cc @felixbarny @carsonip
Alternatives

Keep as is
Introduce a specific type for this. That one feels an overkill to me. It'd also be hard to implement for some backends.

Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[x] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[ ] schema-next.yaml updated with changes to existing conventions.

Violation: Attribute 'geo.location' name is used as a namespace in the following attributes '["geo.location.lat", "geo.location.lon"]'.
  - Category         : naming_collision
  - Type             : semconv_attribute
  - SemConv group    :
  - SemConv attribute: geo.location
  - Provenance: /home/weaver/source

This seems like a blocker for such PRs :(  Is this maybe just an unwanted side-effect of this policy?
geo.location.lat and geo.location.lon are now deprecated, so we'd not use 'geo.location' as a namespace in those. These 3 would not exist at the same time.

Introduce a specific type for this. That one feels an overkill to me. It'd also be hard to implement for some backends.

An option that doesn't require a new type in OTLP (which would introduce compatibility issues) is that we add an optional type hint for attributes in KeyValue. That enables backends with support for geo points to handle these attributes in a special way. It adds semantics to the attribute, for example, for attributes with the type hint geo_point the expectation is that attributes are an array of double values where the first element represents lon, and the second lat. The benefit of the type hit would be that backends don't need explicit and up-to-date knowledge of which attributes are defined as geo points in semantic conventions and that custom attributes can also be mapped to geo points.
Example:
{
  "attributes": [
    {
      "key": "geo.location",
      "typeHint": "geo_point",
      "value": {
        "arrayValue": {
          "values": [
            {
              "doubleValue": -71.34
            },
            {
              "doubleValue": 41.12
            }
          ]
        }
      }
    }
  ]
}

Type hints could be useful for other types as well, for example, IP addresses that are currently represented in string-typed attributes.
Type hints make attributes more self-describing, while still preserving compatibility with backends that don't have native support for these more specialized types.

Violation: Attribute 'geo.location' name is used as a namespace in the following attributes '["geo.location.lat", "geo.location.lon"]'.
  - Category         : naming_collision
  - Type             : semconv_attribute
  - SemConv group    :
  - SemConv attribute: geo.location
  - Provenance: /home/weaver/source

This seems like a blocker for such PRs :( Is this maybe just an unwanted side-effect of this policy?
geo.location.lat and geo.location.lon are now deprecated, so we'd not use 'geo.location' as a namespace in those. These 3 would not exist at the same time.

This was discussed in today's SIG - there was agreement that something like this is acceptable. The idea to completely drop the policy came up as well, that may not happen, but there was no push back to allow this situation when the collision only happens between new and deprecated fields.

@gregkalapos this policy have been relaxed for deprecated attributes with https://github.com/open-telemetry/semantic-conventions/pull/1642, which has already been merged, so updating this PR from main should allow to unblock it.

This PR is effectively the reason/rationale I want to see a new "type" concept in Semantic conventions (see discussion around embed here: https://github.com/open-telemetry/semantic-conventions/issues/1264).
Specifically, there can be different Geo location coordinate reference systems.  If we limit to lat/lon AND erase the names, I think this is just a foot-gun.  particular the discussion around whether it's [lon,lat] or [lat,lon].
I think we should hold off on this PR and think about how we, generically, want to handle the issue of "grouped" attributes.  While we could do something quick for lat/lon, we're not in a hurry here, and I think we could preserve geo.location.{lat|lon} while also providing a "uniform consumption" experience as motivated this PR.
cc @open-telemetry/specs-semconv-maintainers @trisch-me

There are similar problems with other types/namespaces (e.g. user/identity, address+port) and we can't solve them all with arrays.
Arrays would be hard to use in custom queries, dashboards, etc.
I'm really curious about

having 2 distinct attributes (geo.location.lon and geo.location.lat) is very inconvenient.

and would like to understand more - what was inconvenient? In which scenarios? Inconvenient for the end users or backend implementation? How is it different from client.address + client.port that are presumably consumed together all the time.

The difference between user/identity, address+port compared to geo is that backends may have a dedicated type for geo.

what was inconvenient? In which scenarios?

This is the specific PR in the exporter: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36594 So we could not just take the 2 fields and store them as is, but needed to check if both are present (and e.g. not only one) and then turned those two into a format that is accepted by the backend as the dedicated geo type. That's basically all scenarios for geo fields.

Inconvenient for the end users or backend implementation?

Prior to that PR it was inconvenient for users because geo fields were not stored with the native geopoint type. One feature is e.g. that users can visualize these on a map - things like that were not possible. With the PR we fixed that, but with that, we start treating these 2 fields differently than other fields.

How is it different from client.address + client.port that are presumably consumed together all the time.

Ultimately, in my view, the difference  is that we have a dedicated type for geo, but not for the other examples. Of course not all backends will have a dedicated geo type, but in this example we do have, and I'd not be surprised if there would be more such backends.
Now, having said all that, I think the solution in PR https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36594 is not that bad - it's far from unacceptable and it does the job. So we kind of went with that and accepted this inconvenience already. And I also share the other concerns regarding double[].
Yet, I still think this situation is different compared to the other examples here and the connection between these 2 fields is much stronger, given the fact that backends may store them together is a dedicated type.

thanks for the context @gregkalapos, should we close this one? We can continue the discussion in https://github.com/open-telemetry/semantic-conventions/issues/1669 which should address this concern.


Setup sphinx autodoc

We should generate proper documentation from doc strings in the code.
(And also add a lot more structured documentation in the code itself).

Giving the efforts on http://osim-rl.stanford.edu/ let's skip this one for now.


GoSublime:HTML wrong autocomplete

<input>  autocompleted as <input></input>, with </input> wrongly written there
also happening with other tags with only one tag

GoSublime doesn't provide HTML auto-completion.


feat: next version

Next version of vue-prism-editor
New features
Fixes
9kb to ~3kb gz

Codecov Report

Merging #77 into master will increase coverage by 57.01%.
The diff coverage is 95.21%.

@@             Coverage Diff             @@
##           master      #77       +/-   ##
===========================================
+ Coverage   38.19%   95.21%   +57.01%
===========================================
  Files           7        2        -5
  Lines         233      230        -3
  Branches       52       62       +10
===========================================
+ Hits           89      219      +130
+ Misses        132       11      -121
+ Partials       12        0       -12

Impacted Files
Coverage Δ

src/components/Editor.js
95.19% <95.19%> (ø)

src/components/styles.css
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Fixes:
#71 custom higlight fn
#49 fixed
#73 fixed
#72 fixed
#43 fixed
#70 fixed
#62 #65 fixed
#67 custom higlight fn
#41 fixed
#28 fixed

fixes #79

Nice! Let's get er done :) This is one of the last things I'm waiting on to take https://classroom.qvault.io out of the sandbox

@koca is there an ETA for when this will be merged/released?

Hey @MattIPv4! Tomorrow i'll try to release a new version.
cc @lane-c-wagner

Hi guys! Released a beta version of v1 🎉
Try now<EMAIL_ADDRESS>There are breaking changes so please read the readme in https://github.com/koca/vue-prism-editor/tree/feature/next
cc @MattIPv4 @lane-c-wagner @elevatebart
If you need help or have ideas just let me know 😊
btw next version is just 2.7kb gzip 🚀 (previously ~7-9kb gzip)

example codesandbox using the next version: https://codesandbox.io/s/vue-prism-editor-next-gzi7k

Hey @koca,
I'm having a lot of selector power issues (existing styling framework is overriding your textarea styles).
Could I suggest writing the styling in scss, so that you can more easily nest the selectors to give them more power (and so I can import the styles directly in our scss at the right point to give them even more power)?

Looks great @koca ! Thanks for working on this. If you want to see what we are building with your library check it out: https://classroom.qvault.io
Or the playground:
https://classroom.qvault.io/playground/go

Hey @koca,
I'm having a lot of selector power issues (existing styling framework is overriding your textarea styles).

So you are having a css spesificity issue on textarea, interesting 🤔. Thanks for the info!

Could I suggest writing the styling in scss, so that you can more easily nest the selectors to give them more power (and so I can import the styles directly in our scss at the right point to give them even more power)?
Something like: https://gist.github.com/MattIPv4/3939e6c7079866260181d88864fa5561

I'm not sure about supporting scss but we can do nesting with postcss to fix the spesificity. You can still import css in scss so that would work. Thank you! 😊

Looks great @koca ! Thanks for working on this. If you want to see what we are building with your library check it out: https://classroom.qvault.io
Or the playground:
https://classroom.qvault.io/playground/go

Love it! Just checked the js course looks promising ✌ Where do you run the code client/backend?

@koca The Go code runs using web assembly, and the JavaScript is executed right in the browser

@koca The Go code runs using web assembly, and the JavaScript is executed right in the browser

Running go code on browser using web assembly? 🚀 Cool! Is it open source?

Yeah here is a tutorial: https://qvault.io/2020/07/01/running-go-in-the-browser-with-web-assembly-wasm/
You can also hop in our discord if you want to stay in the loop https://qvault.io

@koca What are we waiting for on this version?

@koca I love this library, but I'm really needing that spacing change! Is there anything I can do to help get this next release out?

@lane-c-wagner been busy sorry 🙏. Actually i was waiting for feedbacks but seems like other guys are busy as well :D anyway just released official v1 release 🎉.  Enjoy and thanks for the love mate ♥ 👍
Please let me know if you need any help.

Thank you, I will update my CMS to use the latest version! Keep up the great work! I'll let you know how it works, when I get around to do this.

@koca Thanks so much! New "Practical Cryptography" and "Go Mastery" courses are going to be some much better now :) https://classroom.qvault.io/dashboard/courses

classroom.qvault.io so good 🚀 cant try the courses(need to pay) but tried the free one and love the clean design! 🚀
btw vue-prism-editor code and version is correct on NPM, seems like i just need to update the readme. Maybe i can't see, can you tell me what is missing?

I got it working, I was just confused about NPM. My bad!
If you want to check out another course or two use this code to get some free gems: 3CORBL @koca Thanks for the awesome library

@koca, you rock my socks... In other words, it works and vue-live is now awesome ! Thank you ;)

haha thanks @elevatebart! We use vue-live in @chakra-ui it works great 👍
cheers @lane-c-wagner! and thank you for the coupon 😇


ExposureTimeRatio

I noticed, if I increase the ExposureTime the camera has more insight. But the MaxAllowedFrameRate is affected by this. So what does the EposureTimeRatio exactly doing? Will this affect anything of the view of the camera if I change it?

@Semih67 the ExposureTime is the amount of time the camera illuminates the scene. So for dark objects and objects which are far away from the camera this will enhance the visibility of those objects. For the O3X there is a trade-off, the more light is exposed the lower the frame rate can be. This is due to the fact that otherwise the VCSEL used in the camera is not eye safety any more.


fix read last msg err

Codecov Report

Merging #52 (1547708) into main (932d713) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
- Coverage   59.65%   59.59%   -0.06%
==========================================
  Files          12       12
  Lines        1088     1089       +1
==========================================
  Hits          649      649
- Misses        350      351       +1
  Partials       89       89

Impacted Files
Coverage Δ

pkg/utils/pulsar_util.go
60.52% <0.00%> (-0.81%)
:arrow_down:

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 932d713...1547708. Read the comment docs.


feat: masonry flashlist support

Description
Adds masonry flashlist support to the library.
Bonus: updates @shopify/flash-list to latest
Unfortunately though the issue https://github.com/PedroBern/react-native-collapsible-tab-view/issues/335 is the same with MasonryFlashList.
Example demo Video:
https://github.com/PedroBern/react-native-collapsible-tab-view/assets/21178754/a0c4c8f3-ac3a-4cfb-a555-e0493861dd79

Thanks! Released as 6.2.0


Create kubectl plugin as additional tool for configuring and troubleshooting Rook

Is this a bug report or feature request?

Feature Request

What should the feature do:
Create a Krew plugin to extend kubectl commands for Rook.
What is use case behind this feature:
kubectl plugins provide additional conveniences for running kubectl commands. This can be a very helpful tool for troubleshooting or automating steps that today are manual or not obvious to collect. This is another tool that can help supplement our documentation around advanced configuration or disaster recovery, besides some common commands to simplify the life of Rook users.
Here are some commands we might consider:

kubectl rook get-mon-endpoints
kubectl rook set-mon-endpoints: For disaster recovery, update the rook-ceph-mon-endpoints configmap and restart the operator
kubectl rook force-mon-quorum <mon>: Automate the disaster recovery guide for forcing the mon quorum to a single mon
kubectl rook get-volumes [rwx|rwo|cephfs|rbd]
kubectl rook ceph <args>: Run any ceph command in the toolbox
kubectl rook operator restart: Restart the operator
kubectl rook operator set <property> <value>: Set the property in the rook-ceph-operator-config configmap, for example to enable debug logging or configure the CSI driver
kubectl rook health: Shortcut to “ceph status” command, or else pretty print the status on the CephCluster CR
kubectl rook version: Print the version of Rook and the version of Ceph daemons from the CephCluster CR status
kubectl rook status: Print the phase and/or conditions of every Ceph CR
kubectl rook purge-osd <id>: Replace the purge-osd.yaml example job
kubectl rook set-pool-failure-domain <pool> <domain>: Replace the advanced topic for updating a pool's failure domain

All commands would default to the rook-ceph namespace. For other namespaces pass -n <namespace>, or pick up the environment variable ROOK_NAMESPACE.
Likely we should create a new repo for this tool, no need to version it with the main Rook releases.

Projects usually try to follow below format for the commands:
<Top Level Command> <Command> <Resource> <Arguments> <Flags>
For example:
Kubectl get pods -n rook-ceph
So
kubectl rook-ceph operator config get could be something like:
kubectl rook-ceph get operator-config


Estimate gas for non offline transactions

I looked into why we have to specify a hardcoded gas_limit of 8M in both gp-v1 and gp-v2 services (this supposedly negatively affects the time our txs stay in the mempool as some nodes might only consider a tx if there is still enough "remaining gas" in the block according to the tx's gas limit).
The issue seemed to mostly affect the e2e tests (in fact on mainnet not using a hardcoded gas limit works fine and on xdai it works when connecting to a good node that supports proper gas estimates - e.g. https://dai.poa.network)
I found that we are estimating gas only for offline signed transactions (which is what we use on mainnet/xdai). Furthermore, if None is specified as a gas limit some nodes (e.g. ganache) set the gas limit to a hardcoded 90k, which is not enough for most of our transactions. This explains why our txs fail in the e2e tests where we are using local signing.
This PR suggests to run an estimate gas call also for local signing and locked account transactions. Alternatively we could do an explicit estimate_gas call inside our services and set the value appropriately. However this would have to happen on all callers.

GitHub App like Mergify are not allowed to merge pull request where .github/workflows is changed.


libtensorflow-core.a contains duplicate symbol CreateGPUTracerEv

Running build_all_ios.sh produces a libtensorflow-core.a that contains a symbol twice. When linking on iOS the error is
duplicate symbol __ZN10tensorflow15CreateGPUTracerEv in:
    <PROJDIR>/.../libtensorflow-core.a(gpu_tracer.o)
ld: 1 duplicate symbol for architecture x86_64

I checked with nm just to be sure
$ nm libtensorflow-core.a | grep CreateGPUTracerEv
---------------- T __ZN10tensorflow15CreateGPUTracerEv
---------------- T __ZN10tensorflow15CreateGPUTracerEv

Branch master
MacOS Sierra 10.12.6 (16G29)
Xcode Version 8.3.3 (8E3004b)

Removing line 513 from Makefile
TF_CC_SRCS += tensorflow/core/platform/default/gpu_tracer.cc

resolves this issue.

@petewarden It seems duplicate symbols are being linked into a static library, when using build_all_ios.sh.

Can you assign @petewarden ?

Same problem on android, the object file gpu_tracer.o contains the dummy function returning nullptr:
int __fastcall tensorflow::CreateGPUTracer(int result)
{
  *(_DWORD *)result = 0;
  return result;
}

and a "global":
int GLOBAL__sub_I__ZN10tensorflow15CreateGPUTracerEv()
{
  std::ios_base::Init::Init((std::ios_base::Init *)&std::__ioinit);
  return _aeabi_atexit(&std::__ioinit, std::ios_base::Init::~Init, &_dso_handle);
}

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


⬆ Update dev dependencies

resolves #3551

Everything is up to date except styled-dictionary and eslint which has gotten their own tickets as these are larger undertakings. SVGO update expectedly caused icon paths to slightly change so this is why all the icons appear to be updated (there are no visual changes)


API gateway removal does not remove client certificates

While the API gateway is nuked it remove the API, but the Client Certificates attached to the API are not removed.
Unfortunately the client certificates keep accumulating if the same API is redeployed.
I am using cloud nuke v0.20.0

hello team, is there any update on this? We are part of MicroFocus (Paid client), and we wanted to know the status so that we can decide if we want to do it at our end or contribute directly to Cloud Nuke or use the different version which addresses this already. thank you.

@denmanveer thanks for reaching out.  We don't have a fix scheduled for this right now, but I will add it to our backlog. We'd welcome a PR if you have the time.

@denmanveer thanks for reaching out. We don't have a fix scheduled for this right now, but I will add it to our backlog. We'd welcome a PR if you have the time.

thank you so much @ellisonc for the reply, this helps, to understand this is a bug, not a version issue.
Definitely will try to contribute directly if time persists.


How to find a girlfriend at McMaster

@Yunfei-Ma-McMaster Can you teach us more about this

Hey there! Thanks for opening this critical issue my friend. 😄 Let's debug this together.

Initialize your repository: Make sure you've got a good README. In real life, this means being genuine, understanding, and having a good sense of humor.
Commit to personal growth: Just like in coding, continuous integration and continuous development apply to personal life. Keep learning and improving.
Pull Requests: Don't be afraid to make a move. Sometimes, you need to open a pull request to see if it gets merged. Remember, it's okay if it gets closed; there are many repos in the GitHub universe.
Frequent Commits: Engage in activities, join clubs, and attend events at McMaster. The more commits (interactions) you make, the higher the chances of a successful merge.
Handle Merge Conflicts: Relationships can have conflicts. It's essential to address them, understand the differences, and find a middle ground.
Fork and Branch: Explore different social circles (branches). Sometimes you might need to fork from your usual group to meet new people.
Code Reviews: Sometimes, it's good to get feedback. Talk to friends, get their opinions, but remember, the final merge decision is yours.
Stay Updated: Just as you would git pull to stay updated, keep yourself informed about events, trends, and happenings around McMaster.

Lastly, remember that finding the right partner is a bit like finding the right open-source project to contribute to. It might take time, there might be issues, but with patience and persistence, you'll find the right match.

Follow up: are you single?


Welcome to Elemental System Designs

This is a project born out of interest and for learning! All contributions are welcome, even if it's just raising an issue to describe a bug fix, a request to design a system that you are interested in, and improvements to the existing designs.
We can use this issue to add new contributors using all-contributors bot.

@all-contributors please add @GummyBearr for ideas

@all-contributors please add @dawoudt for ideas


Share-manager HA - lease renewal

Which issue(s) this PR fixes:
This is part of issue https://github.com/longhorn/longhorn/issues/6205, Share Manager HA.  This code will look for a lease associated to the share manager's volume and run a goroutine to renew it regularly if it exists.
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context
I am marking it as draft because the related code in longhorn-manager is still in development, although it should have no effect if there is no Lease object.

Is it ready for review?

Thanks @james-munson and @PhanLe1010 for your effort. All issues are addressed, so we can merge the PR.

@mergify backport v1.7.x


ROX-24475: Change "Label" in Policy Scope to "Deployment label"

Wizard step 4:

Policy detail:

While we're at it, let's maybe also fix the text?

                        Use Restrict by scope to enable this policy only for a specific cluster,
                       namespace, or label. You can add multiple scope and also use regular
                       expressions (RE2 syntax) for namespaces and labels.

s/multiple scope/multiple scopes
s/label/deployment label
s/labels/deployment labels

                       Use Exclude by scope to exclude entities from your policy. This function
                       is only available for Deploy and Runtime lifecycle stages. You can add
                       multiple scopes and also use regular expressions (RE2 syntax) for
                       namespaces and labels.

s/labels/deployment labels

/retest


gpxsee: 7.15 -> 7.16

Motivation for this change
Changelog:

Added support for Garmin GPI files.
Hyperlink + copy&paste enabled tool tips.
Various minor bug fixes in data loading.

Things done

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

[x] NixOS
[ ] macOS
[x] 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 nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)

$ nix path-info -Sh /nix/store/9ycbnk607va99iyq47h7c55f0hsf39zd-gpxsee-7.15
/nix/store/9ycbnk607va99iyq47h7c55f0hsf39zd-gpxsee-7.15	 263.7M
$ nix path-info -Sh /nix/store/bpcsax7j0dsx82bbkqw65gfi3fjzwflp-gpxsee-7.16
/nix/store/bpcsax7j0dsx82bbkqw65gfi3fjzwflp-gpxsee-7.16	 263.7M

[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @womfoo

@GrahamcOfBorg build gpxsee


increase the allowed maximum size of a report

The maximum size of a report is limited by nginx to be around 1MB by default.  This should be increased as logs can be rather large.  Discuss what is a good limit (2MB, 5MB?) and change the default configuration.
The file to change is /etc/nginx/conf.d/slipstream-extra/limit-reports.block:
location ~ ^/reports/ {
    include conf.d/slipstream-proxy.params;

    limit_conn reportslimit 10;
    client_max_body_size 5M;
}

4 people, 4 different answers for the maximum size.  We'll use 5MB for now.


Update theme to use newest Sphinx Book Theme

The newest version of Sphinx Book Theme (v0.2+) are all backwards incompatible.  We will need to make changes to the Sphinx Pythia Theme to use these new updates.  For now, the dependency on the Sphinx Book Theme is limited to versions < 0.2.

Noting here that the very cool latest tools in the MyST / Executable Books ecosystem are moving away from Sphinx entirely, e.g. https://mystmd.org/guide
Our infrastructure team should take a look at whether we want to continue to invest in Sphinx for our websites, our Cookbooks, both, or neither.

Hey @agoose77, just wanted to let you know here, this is the issue we have been talking about Sphinx updates.

Thanks @erogluorhan — is there any existing work on upgrading this theme? Just so I know where to start.

@dcamron was looking into it!

Hey @agoose77 , the actual work should be on @dcamron 's end, but just FWIW: I was playing with the things yesterday in my local and pushed them into a branch, creating a draft PR just for the sake of showing where actions currently fail.
You two, please feel free to take what can be helpful from that PR into your own work, take over the whole branch, or just ignore it as you see fit.

Hey @agoose77 , the actual work should be on @dcamron 's end, but just FWIW: I was playing with the things yesterday in my local and pushed them into a branch, creating a draft PR just for the sake of showing where actions currently fail.
You two, please feel free to take what can be helpful from that PR into your own work, take over the whole branch and/or PR, or just ignore it as you see fit. Let me know if I can be of any help with this work.

Update: Actually, I went ahead and got the same PR to work now as this issue is one of the highest priority infrastructure things for us currently. However, I might be missing things as this topic is not something that I have a lot of experience. I asked reviews, please give it a thorough review if you have time.

@erogluorhan fast work! I was just unblocking the Jupyter book release, I'll now have time to get to this on Monday :)


how to animate multiple uiview objects

is there a way to animate multiple attributes of multiple uview objects using same motion duration delay etc.??? or in other words equivalent to UIView.animate
or
Motion.animate(duration: 0.3, animations: {                 view.translate(x: 0, y: 100)                 view2.rotate(50)             })

You can do this:
v1.animate(.duration(1), .fadeOut)
v2.animate(.duration(3), .translate(x: 10))

The animation cycle will take the both of these in consideration and will also stack the animation if needed.
For UIView.animate ... all that actually does is allow the underlying layers to be animated. By default CALayers are animated when transitioning between property values. When using a UIView it disables that. So the UIView.animate function enables that once again. Give it a try and if you have any issues, please let me know :)

no there is no issue doing it this way.. i was just looking for way so that when i animate many ui components they start and end at exact same time

Yeah, set the duration to the same value and all should work :) Also, you can stack animations during an already animating view. So if you did this:
v1.animate(.duration(3), .spin(3))
v1.animate(.delay(1), .duration(1), .fadeOut)

That would work :)

great thanks


feat: Implement annotations for a subset of data processing

Provide natural language annotations for the tasks in #14
See #12 for important comment regarding the pandas domain in LAPS

Probably not doable, but we can research further if we have time.


우분투 이용하여 딥러닝 훈련시 Killed

dmesg | grep -E -i -B100 'killed process'

swap
https://hiseon.me/linux/linux-swap-file/
https://faq.hostway.co.kr/Linux_ETC/1443


sample with AppCompatActivity

As the method onRetainNonConfigurationInstance() is final in AppCompatActivity,

Does flow work with AppCompat ?
if yes, how should one modify the MainActivity class (in the sample) to work with AppCompatActivity ?

NonConfigurationInstance nonConfig;
        if (activity instanceof FragmentActivity) {
            nonConfig = (NonConfigurationInstance) ((FragmentActivity) activity).getLastCustomNonConfigurationInstance();
        } else {
            nonConfig = (NonConfigurationInstance) activity.getLastNonConfigurationInstance();
        }

and
@Override public Object onRetainCustomNonConfigurationInstance() {
        return presenta.provideNonConfigurationInstance();
    }

Thanks for the tip. I got it to work with
@Override public Object onRetainCustomNonConfigurationInstance() {
return flowSupport.onRetainNonConfigurationInstance()
}
and your change in onCreate with
 flowSupport = FlowDelegate.onCreate(nonConfig, getIntent(), savedInstanceState, parceler, History.single(....my history ...), this)


add rtu to server

As the subject, rtu server is still valuable

@ivomurrell had added an according first-pass implementation in #72, but it's not being worked on presently. I could probably extract those changes into a separate PR, but would have to check if any of the code has strict dependencies on tokio v1 or any of the other added/changed dependent crates


FIX: wrong indentation

Checks before merging PR

[ ] added documentation for any new feature
[ ] added unit test
[ ] edited the what's new (if applicable)

Codecov Report

Merging #668 (04884bd) into main (16c5cb9) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main     #668   +/-   ##
=======================================
  Coverage   54.98%   54.98%
=======================================
  Files          45       45
  Lines        2919     2919
  Branches      538      538
=======================================
  Hits         1605     1605
  Misses       1189     1189
  Partials      125      125


Create CI for author-disambiguation

Currently, we don't have a CI set for the repository, so there is no way to verify if the changes are correct. We need to set it up (also linters must be configured).

We can use github actions, which would be very similar to unit test setup on inspirehep , that runs https://github.com/inspirehep/inspire-disambiguation/blob/master/run-tests.sh

Actually let's take this opportunity to merge inspire-disambugation repo into this one, under disambiguation folder.


regressions: cannot enter values into NumberInput

Fixes: #1611
The value passed to onChange callback is not the number but an event that encapsulates the value.

Some tests failed

LGTM


Kube Node Metrics graphs are blank on EKS

Observed that Kube Node Metrics show empty graphs for EKS - need to verify is this was an environment/config issue or if there is an underlying problem.

could be related to  https://bugzilla.suse.com/show_bug.cgi?id=1142046


Declared License was Incorrect

Type: Incorrect
Summary:
Declared License was Incorrect
Details:
These files are part of the Go language. Files identified are Google Additional Grant of Patent Rights. No SPDX identifier exist specifically for this.
Resolution:
Declaring as "OTHER".
Affected definitions:

controller-runtime 12d98582e72927b6cd0123e2b4e819f9341ce62c

@cruzerika - Thank you for this curation.  I am just seeing the Apache v2 license here: https://github.com/kubernetes-sigs/controller-runtime/blob/12d98582e72927b6cd0123e2b4e819f9341ce62c/LICENSE.  Where are you seeing a Patents file?  I am looking in the source repo.  Thank you

Hi Ariel,
You're welcome.
Following are the links to the Patents file:

https://github.com/kubernetes-sigs/controller-runtime/blob/12d98582e72927b6cd0123e2b4e819f9341ce62c/vendor/golang.org/x/text/PATENTS
https://github.com/kubernetes-sigs/controller-runtime/blob/12d98582e72927b6cd0123e2b4e819f9341ce62c/vendor/golang.org/x/crypto/PATENTS
https://github.com/kubernetes-sigs/controller-runtime/blob/12d98582e72927b6cd0123e2b4e819f9341ce62c/vendor/golang.org/x/net/PATENTS
https://github.com/kubernetes-sigs/controller-runtime/blob/12d98582e72927b6cd0123e2b4e819f9341ce62c/vendor/golang.org/x/sys/PATENTS
https://github.com/kubernetes-sigs/controller-runtime/blob/12d98582e72927b6cd0123e2b4e819f9341ce62c/vendor/golang.org/x/time/PATENTS

Hope this helps.
Regards,
Erika

@cruzerika - Thank you.  Yes, I agree with these specific files being curated as OTHER.  Thank you for curating the NOASSERTIONS.

You're welcome, @ariel11 . Thank you for approving and merging the changes. Happy Friday! :)


fix: failing test on some machines

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr-build
999e0ef4719e52b244d01d6280878934afca0cc9
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add Quality of a JSON file, closes #134

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ba29112) 97.55% compared to head (e5a90ec) 97.56%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #137      +/-   ##
============================================
+ Coverage     97.55%   97.56%   +0.01%
- Complexity      766      771       +5
============================================
  Files           195      197       +2
  Lines          1675     1684       +9
  Branches         54       54
============================================
+ Hits           1634     1643       +9
  Misses           32       32
  Partials          9        9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Return an error if a schema has repeated directives without the repeatable keyword

It was reported in https://github.com/graph-gophers/graphql-go/pull/502 that this library doesn't enforce uniqueness of non-repeatable directives. This is a bug and such a restriction needs to be enforced unless the repeatable keyword is present in the directive definition.
For example, if we are given two directives:
directive @repeatabledirective repeatable on SCALAR
directive @otherdirective on SCALAR

Then only the first one (i.e. @repeatabledirective) can be repeated multiple times on the same scalar type. If we repeat the @otherdirective more than once, then that should result in an error.
The issue is considered resolved when only directives declared as repeatable can be repeated.

Good day. I would like to work on it. As far as I understand I need to update this function to return an error in case we see non repeatable directive for a second time. Is it correct?

@ostrea go for it!


Bazel BUILD files detected as Python due to Automatic Language Detection

Does this issue occur when all extensions are disabled?: No, this is a bug originating from the interaction of a feature and the extension

Commit: e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff
Date: 2021-09-01T10:43:02.136Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.4.119-14945-gafc97d54f809
Steps to Reproduce:

Have a Bazel BUILD file.
Disable Automatic Language Detection (i.e. "workbench.editor.languageDetection": false)
Have the BazelBuild.vscode-bazel extension installed.
See that Bazel files are set as the Starlark language
Now enable Automatic Language Detection (i.e. "workbench.editor.languageDetection": true)
Note that Bazel files are being automatically detected as Python.

A confluence of issues causes this:

BUILD files don't have an extension
Automatic Language Detection doesn't know about Starlark
Starlark looks a lot like Python

My ask here is essentially that the VSCode Bazel extension previously was able to have its own detection logic, and detect these files as Starlark files. Automatic Language Detection is overriding this. Is there some way to make it so that languages set by extensions override what ALD does?
In the interim I am working around this by disabling the new ALD feature for Starlark specifically.

cc @TylerLeonhardt

@grantwwu what version of VS Code are you using?

1.60.0, sorry, I didn't realize that the big blob of info I copied didn't actually have the version number 😅

Is this fixed in https://github.com/microsoft/vscode/issues/132173 ?

The issue appears to have been fixed in 1.60.1.

Yep! You found it :)

Closing as a duplicate/already fixed


le-utils 0.0.11 broken on python 2

After upgrading to the latest Kolibri develop branch (which uses le-utils 0.0.11) can no longer run on python 2. Running on python 3 works fine.
(le)~/P/l/r/kolibri (develop) $ yarn
yarn install v0.19.1
$ node ./frontend_build/src/npm_deprecation_warning.js
[1/4] 🔍  Resolving packages...
success Already up-to-date.
$ node ./frontend_build/src/install_dependencies.js
Traceback (most recent call last):
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/Users/d/Projects/learning_equality/repos/kolibri/kolibri/__main__.py", line 8, in <module>
    main(args=sys.argv[1:])
  File "kolibri/utils/cli.py", line 540, in main
    initialize(debug=debug)
  File "kolibri/utils/cli.py", line 141, in initialize
    django.setup()
  File "/Users/d/PythonEnvs/le/lib/python2.7/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/d/PythonEnvs/le/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models(all_models)
  File "/Users/d/PythonEnvs/le/lib/python2.7/site-packages/django/apps/config.py", line 202, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "kolibri/content/models.py", line 19, in <module>
    from le_utils.constants.languages import LANGUAGE_DIRECTIONS
ImportError: No module named languages
child_process.js:533
    throw err;
    ^

Error: Command failed: python -m kolibri manage webpack_json -- --outputfile /var/folders/n9/k997qvqs3f7_m_310crwsxyc0000gp/T/11773-1471-1572598.wft27ta9k9.json
Traceback (most recent call last):
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/Users/d/Projects/learning_equality/repos/kolibri/kolibri/__main__.py", line 8, in <module>
    main(args=sys.argv[1:])
  File "kolibri/utils/cli.py", line 540, in main
    initialize(debug=debug)
  File "kolibri/utils/cli.py", line 141, in initialize
    django.setup()
  File "/Users/d/PythonEnvs/le/lib/python2.7/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/d/PythonEnvs/le/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models(all_models)
  File "/Users/d/PythonEnvs/le/lib/python2.7/site-packages/django/apps/config.py", line 202, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "kolibri/content/models.py", line 19, in <module>
    from le_utils.constants.languages import LANGUAGE_DIRECTIONS
ImportError: No module named languages

    at checkExecSyncError (child_process.js:490:13)
    at execSync (child_process.js:530:13)
    at module.exports (/Users/d/Projects/learning_equality/repos/kolibri/frontend_build/src/read_webpack_json.js:10:3)
    at Object.<anonymous> (/Users/d/Projects/learning_equality/repos/kolibri/frontend_build/src/install_dependencies.js:6:15)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

invalid - I had previously installed le-utils for local dev and this required manual modification of my virtual environment's site packages to remove: https://stackoverflow.com/a/18818891


[Package Request]: Direct Folders

How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://www.codesector.com/downloads
Publisher: Code Sector
Package Name: Direct Folders
Description: Quick access to your favorite folders
Package Version: 4.2
Installer URL: https://codesector.nyc3.cdn.digitaloceanspaces.com/directfolders.exe

Universal Silent Switch Finder failed to inspect the file type of the installer wizard.
By adding /? switch to the installer wizard, following dialog shows up. It might be created by Advanced Installer?

Btw, this issue has already been resolved by PR #160815

By adding /? switch to the installer wizard, following dialog shows up. It might be created by Advanced Installer?

It was using exact same installer as teracopy one, most likely Advanced Installer.

By adding /? switch to the installer wizard, following dialog shows up. It might be created by Advanced Installer?

It was using exact same installer as teracopy one, most likely Advanced Installer.


Use PhotonOS for template VM

Current template VM is Ubuntu 16.04 based. We need to see what it will take to start using PhotonOS based template VM instead.

k we have a base image already :)

I have an photonOS image WIP.
To use it as the template for kops, it needs two extra disks attached and mounted ahead for etcd and etcd-events.
Prashima has the script for ubuntu and I modified it for PhotonOS.
Maybe @maplain can sync up with me so we can avoid duplicated work :)

This issue was moved to kubernetes/kops#2735


feat: derive from Clone on PrivateKeyDer enum

I think we specifically want to avoid making private key material types Clone, so it is possible to minimise the number of places they exist in memory. What problem are you trying to solve?

And also, thanks for the quick response! :smile:

These objects are immutable, so having multiple copies is not really useful. Have you considered wrapping them in Rc/Arc? This gives you (~free/cheap) clone without any underlying copies happening.

It makes sense @ctz! I'm quite new to the Rust ecosystem, so I didn't knew about this "workaround". Thanks for the hand!

Hey guys, update on my use case: early evaluate the Item worked to move it around the application, but it did not work to load the file, as TlsAcceptor::builder().with_single_cert needs ownership of the key, which can't be given since it can't be cloned and is inside an Arc.
What I'm planning to do to avoid such issue is hold the plain file on the application and late evaluate it to an Item right before the creation of TlsAcceptor. Anyway, thanks for your kindness and velocity on giving me feedback around this issue.

It worked @djc, thanks 🙌🏽 was able to achieve a clone-like behavior by using Arc + clone_key.
I apologize for my ignorance, but what's the difference between deriving explicitly from Clone and clone_key, and why clone_key is safe to use?

The idea was that clone_key() forces an explicit usage, whereas it would be trivial to oversee deriving Clone of some type that includes a PrivateKeyDer, leading to the key potentially leaking into places it shouldn't go.
It's admittedly a nuanced topic -- this is the line we've ended up at for now.


Component Side panel 2 in same screen

Scenario
Actually Side panel allow use only one time. Imagine screen 'dashboard' where left I have a side panel of configurations and right I have a side panel of options about info results of query (like a filter).
Expected
Way to use 2 side panels at same screen.
Problem
At this moment if has 2 side panels  they crash screen, see this image

Fix commit here : https://github.com/kserin/Phonon-Framework/commit/7506d0c8cf56ea8142acd13dcdbd3be1916c625f


I am not able to access payload

Dialog flow , I am not able to access payload.
How to get payload json object?

@rajscet Did you solve this?

@rajscet @CabuxaMapache. Did you solve this?
@google-admin

@rajscet @CabuxaMapache @google-admin  did anyone solved this to get basicdard from JSON object ??


sharing fixtures across tests

Goal
Allow sharing pytest fixtures across tests suites, even when each suite runs in different install environments.
What I changed
Many Frizzle flows follow similar patterns, and therefore use the same pytest fixtures in their test suites.  This PR builds a library of "sharable" fixtures that all suites can avail themselves.  A *_test.py file can make this library available by including the line
pytest_plugins = ["f.frizzle.tests.conftest"]

See https://docs.pytest.org/en/stable/how-to/writing_plugins.html
Notes for reviewers
This PR may be ill-advised, for up to a few reasons:

This is my first use of "pytest plugins" so not sure if I have the mental model correct.
It introduces some indirection that I don't love.  gc-scripts-hub is already unconventional in that tox.ini builds separate environments different test suites, since their dependencies can diverge so much.  Under this PR, one test suite may use the plugin that introduces its own package dependencies but those dependencies are not declared at the shared library (plugin) scope.  Rather the test suite needs to be aware of which shared fixture(s) it uses -- and that fixture's package dependencies -- and declare them in its own requirements-test.txt.
Probably long term I will have wanted to define these shared fixtures at even a lower scope: e.g. one file per fixture.  And then a specific test file would do something more along the lines of

pytest_plugins = ["f.frizzle.tests.plugins.postgresql", "f.frizzle.tests.plugins.mocked_responses"]

Throwing this idea out into the world for discussion.  Happy to receive criticism or rejection on it if warranted.

Interesting proposal. On one hand, it reduces some redundancy in common Frizzle fixtures, but there's something to be said for having everything I need to know about a script be contained within its Frizzle subdirectory. That is to say, if I only care about f/frizzle/kobo, then I don't need to look at anything else.
Maybe one way of thinking about that is if this proposal is poised to raise the barrier of contribution for a new contributor in a slight way. I don't think so if we provide good documentation about why these fixtures (e.g. connect to a postgres db) are being shared. If anything, it's a good opportunity for us to describe what "frizzle" is, and why these scripts are grouped together to begin with. (I've got a forthcoming PR adding a README with some still-relevant copy from past repos).

Interesting proposal. On one hand, it reduces some redundancy in common Frizzle fixtures, but there's something to be said for having everything I need to know about a script be contained within its Frizzle subdirectory. That is to say, if I only care about f/frizzle/kobo, then I don't need to look at anything else.

I think this is a good aim, and this PR goes against it.
The only way I can imagine to do something like this PR in-line with your guidance is to package this up as its own pytest plugin, distributed to a test environment through means other than local path search.  Yet in fact there's not very much that's cohesive about the code that this PR groups together in the first place, so I struggle to justify doing that.
I am going to close this without merge.
The greater question that this PR attempted to address is "how to deal with shared code between scripts?"  This PR only dealt with test code but we do have the same problem in script code, for example see #25

Maybe one way of thinking about that is if this proposal is poised to raise the barrier of contribution for a new contributor in a slight way. I don't think so if we provide good documentation about why these fixtures (e.g. connect to a postgres db) are being shared. If anything, it's a good opportunity for us to describe what "frizzle" is, and why these scripts are grouped together to begin with. (I've got a forthcoming PR adding a README with some still-relevant copy from past repos).

I agree that the documentation propose will be nice.  I am not convinced that it actually resolves the problems with this PR, though.


Only two little changes (button, spacing).

-Changed the buttons on fileStatus to primary.
-Changed spacing on the confirmation page.

I can only see the change to the confirmation page (which looks fine :slightly_smiling_face:). Is there another commit with the button change?


If Prefer native menu is enabled after displaying a popupmenu at least once, it displays in odd location

Tested versions

Reproducible in v4.3.beta2.official [b75f0485b]
Feature "Prefer Native Menu" on PopupMenu is not available on the latest version of 4.2.2

System information
Windows 10 - v4.3.beta2.official [b75f0485b]
Issue description
After displaying a PopupMenu at least once, if the option "Prefer Native Menu" in it's property list is enabled, displaying the popup menu again will reveal it in an odd location

Steps to reproduce

Create PopupMenu node
Add an item or two to the item list
trigger the PopupMenu
Enable the "Prefer Native Menu" property in the node's property list
Retrigger the PopupMenu

Minimal reproduction project (MRP)
bug-report.zip
I've included this project in two other bug reports I've posted recently - If you're coming from/going to one of the other two this is a part of, rest assured you don't need to redownload the project for each report. They are the exact same file.

CC @bruvzg

Not sure what's the issue here, you are using .popup() method without position, so it will be shown at the last set position (position is in embedding viewport coordinates, so it's relative to window for non-native and relative to virtual desktop for native).

I'll be honest I had no idea that was intentional- It just seemed like such behavior I thought it was a bug. If there isn't anything already, maybe adding something somewhere that explains this behavior would be nice instead?


Set default tensor type to double-float

I think you mean (complex double-float)
This can be set with magicl::*default-tensor-type*


[web] how to support search text from browser

I guess it's a feature request ?
Or I miss some widget to do this ?
Steps to Reproduce

Include a list of Text('some text') in a widget.
After run with flutter run -d chrome, it will display in chrome.
I try to search the text by chrome's search tool, but not work.

Target Platform:  Chrome
Target OS version/browser:  Chrome 79.0.3945.88 (Official Build) (64-bit)
Devices: Chrome

[✓] Flutter (Channel beta, v1.12.13+hotfix.6, on Mac OS X 10.15.2 19C57, locale en-CN)
    • Flutter version 1.12.13+hotfix.6 at /Users/jerryzhou/Documents/code/flutter/sdk/flutter
    • Framework revision 18cd7a3601 (4 weeks ago), 2019-12-11 06:35:39 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.41.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.7.1

[✓] Connected device (2 available)
    • Chrome     • chrome     • web-javascript • Google Chrome 79.0.3945.117
    • Web Server • web-server • web-javascript • Flutter Tools

Hi @jerryzhoujw ,
Hardly it's related to the fact I'm doing it on Windows instead of Mac, but I cannot reproduce your case.
Could you post a code sample?
Thank you

hi，there’s the example project https://github.com/jerryzhoujw/flutter_web_app_example

Still with the same version of Chrome and Flutter SDK I can't reproduce it on Windows

I can't repoduct it on my Mac.
@jerryzhoujw If you try upgrading chrome and using master does it work like mine?
Chrome Version 79.0.3945.117 (Official Build) (64-bit)
[✓] Flutter (Channel master, v1.13.9-pre.70, on Mac OS X 10.15.2 19C57, locale en-US)
    • Flutter version 1.13.9-pre.70 at /Users/kent/Developer/flutter
    • Framework revision ef62092b9b (8 hours ago), 2020-01-13 14:30:37 -0800
    • Engine revision 73d2fb374c
    • Dart version 2.8.0 (build 2.8.0-dev.0.0 32ce9c7872)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/kent/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.4

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 38.2.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.41.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.7.1

[✓] Connected device (3 available)
    • macOS      • macOS      • darwin-x64     • Mac OS X 10.15.2 19C57
    • Chrome     • chrome     • web-javascript • Google Chrome 79.0.3945.117
    • Web Server • web-server • web-javascript • Flutter Tools

• No issues found!

Strange, I can't reproduce it now. @kenthinson.

this issue is happening for me right now with flutter web on chrome
flutter doctor -v output

[✓] Flutter (Channel beta, v1.15.17, on Mac OS X 10.14.6 18G87, locale en-US)
    • Flutter version 1.15.17 at /Users/ryan/Downloads/flutter
    • Framework revision 2294d75bfa (3 weeks ago), 2020-03-07 00:28:38 +0900
    • Engine revision 5aff311948
    • Dart version 2.8.0 (build 2.8.0-dev.12.0 9983424a3c)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/ryan/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio 3.6.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.3.1, Build version 11C505
• CocoaPods version 1.9.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio 3.6.app/Contents
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[✓] Android Studio
• Android Studio at /Applications/Android Studio 4.0 Preview.app/Contents
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] Connected device (2 available)
• Chrome     • chrome     • web-javascript • Google Chrome 80.0.3987.149
• Web Server • web-server • web-javascript • Flutter Tools
• No issues found!

return ListView.builder(

                  padding: EdgeInsets.all(8.0),
                  itemCount: snapshot.data.documents.length,
                  itemBuilder: (BuildContext context, int index) {
                    DocumentSnapshot document = snapshot.data.documents[index];
                    Map<String, dynamic> task = document.data;
                    return Card(
                      child: ListTile(
                        title: Text(task['name']),
                        subtitle: Text(task['details']),
                        isThreeLine: false,
                        leading: Column(
                          mainAxisAlignment: MainAxisAlignment.center,
                          children: <Widget>[
                            Container(
                              width: 60.0,
                              height: 24.0,
                              decoration: BoxDecoration(
                                color: appColor.colorSecondary,
                                shape: BoxShape.rectangle,
                                borderRadius: BorderRadius.circular(12),
                              ),
                              child: Center(
                                child: Text(
                                    DateFormat.jm().format(DateTime.parse(task['utc'].toDate().toString())),
                                  style: TextStyle(color: Colors.white),
                                ),
                              ),
                            ),
                            SizedBox(height: 4.0),
                            SizedBox(height: 15, width: 80,
                              child:
                                  Text(
                                    task['geo'],
                                    textAlign: TextAlign.center,
                                    overflow: TextOverflow.ellipsis,
                                    style: TextStyle(fontSize: 12.0),
                                  ),
                            )
                          ],
                        ),

Thank you @maceip
I was trying to make your code sample as minimal as possible to leave reproducing of this search bug and I came to interesting conclusion and opened new issue about it https://github.com/flutter/flutter/issues/53585

Thank you @maceip
I was trying to make your code sample as minimal as possible to leave reproducing of this search bug and I came to interesting conclusion and opened new issue about it #53585

wow great catch, thanks


== "" @echo off

https://github.com/gladed/gradle-android-git-version/blob/4fb0593fb70c2eb1badf4bcc236f166d06da7511/gradlew.bat#L1-L1

?


[AIRFLOW-410] Add 2 Q/A to the FAQ in the docs

Also changed the markup of Questions as sections to be directly linkable.
I made sure the rst rendered nicely here:

@r39132  @aoen @plypaul

Current coverage is 64.52% (diff: 100%)

Merging #1720 into master will not change coverage

@@             master      #1720   diff @@
==========================================
  Files           127        127
  Lines          9443       9443
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           6093       6093
  Misses         3350       3350
  Partials          0          0

Powered by Codecov. Last update 197c905...a9c6ba6

Fix and LGTM.

LGTM


Bug in the script optimize_scale.py

On executing the script optimize_scale.py, I encountered the following error:

The call to minimize_scalar in the optimize_scale function seems to be causing the issue. I have tried running the optimize_scale function on various different input values and the same error is thrown on all of them. Please look into it.

Suppressing the warning using np.seterr(divide='ignore') worked!

Thanks for reporting. Good that suppressing works for now, but I'll still try to look into it asap.


Bump vitest dependencies

Consume 2.1.4 for vitest related dependencies
All vitest deps follow the same version number, to avoid dependency mismatch warnings when running tests.

Why didn't rush catch this?

The mismatched dependencies were in the pnpm lockfile. Some were '2.1.1', while others were '2.1.0'. I guess rush doesn't catch mismatched deps that are in lockfiles

setting back to draft for now, circling back to fix regression for vitest/browser at a later point

Marked as active again - I had to update the setup file for core frontend to import the barrel file. Vitest now inlines setup files into test files , messing up dependency resolution in test files and reintroducing circular imports otherwise


fix: default secure to True if samesite is not set

Browsers will soon start to discard cookies that do not have "Secure" if SameSite is not set/set to None
This pull request sets Secure by default whenever SameSite isn't passed as a param to dump_cookie(). Also updated are all the tests to reflect changes made to the code.

I think this would be better if it raised a ValueError if a cookie was secure False and samesite None. This is as it is more informative to the user and doesn't result in a potentially surprising set of the secure parameter.

I can certainly make those changes. But then I also do think that this would be a better path to head towards, since eventually werkzeug would end up having to do this anyways. A ValueError sounds good as of today, but I suppose a warning stating that the browser might reject the cookie would be better? (along with adding the Secure param to the cookie by default).
Let me know what you think of it, and I'll make whatever changes that are required.

Thanks for bringing this up. I understand the issues around cookie security, but it's hard to change the behavior of the utility functions that Werkzeug provides.
We can't default to secure because not all sites are HTTPS, and the local dev server almost always isn't. While it's a best practice, it's not something we can mandate and a change would break a lot of existing deployed apps and development environments in a way that would be hard to detect.
We can't raise an error either, because the default is secure=False and samesite=None, so the default behavior would be to raise a ValueError. Flask has Flask-Talisman, which takes care of this, as well as a document on security issues surrounding cookies.
I think a warning could make sense here. dump_cookie already raises a warning when the browser might ignore a cookie due to its size. I would like to avoid raising warnings everywhere though. For example, I don't want to have warnings for "secure isn't set", "samesite isn't strict", etc.

It looks like browsers themselves are raising these warnings already: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#Fixing_common_warnings
I don't think browsers were raising an error for cookies that were too large, just silently dropping them, so the warning there made sense, but if the browsers are already warning about this I don't think Werkzeug needs to. I'm going to close this for now.


Passing FreeBayes frequency test when no normal information available

At this line:
https://github.com/chapmanb/bcbio-nextgen/blob/af4701be303bd64ccb47b107d9be36cd606d278d/bcbio/variation/freebayes.py#L255
Frequency is set to zero when there is no normal information available (either "." in FreeBayes normal sample or sum(AO) + RO == 0, or invalid field content). This then passes the frequency filter due to being under the normal threshold.
The error cases don't seem equivalent to the case that sum(AO) == 0 with RO > 0. Our experience suggests that these are very often false positives - there is simply not enough information to say the tumor call is good.

Sam;
Thanks for starting the discussion. This implementation is on purpose to try and avoid filtering out calls which have no evidence in the normal. These definitely could contribute to false positives, because, as you say, there is not enough evidence to rule out the call being germline. On the other side, which is the stance we're taking here, there is also not enough evidence to be sure the call should be removed. We also use similar logic in checking LOD scores.
In cases of incomplete information like this we try to error on the side of passing too much rather than risk removing real variants. This is a case where having to make a yes/no decision like this is painful since the right answer would really be to report "maybe" and that we need more information.
Hope this helps in terms of the implementation logic. I'm happy to discuss better implementations that help improve how this gets conveyed in the final VCF.

I think this is skewed heavily towards false positives in practice, just wanted to alert you to that. We are seeing thousands and thousands of cases where there is a "tumor call" which is passed because the normal has poor coverage, FreeBayes says ".", but the deeper-sequenced tumor location passes this filter.
I would say the evidence is already there that no call can be made - FreeBayes outputs something because it is basically looking at the samples independently as I understand it. If you were looking at both samples together you would not make a call at a location with no information in one of them.
We aren't using this repo, so feel free to close the issue if you like the current method.

Sam -- sorry for dropping this discussion thread earlier. FreeBayes calls tumor and normal together so should have information to attempt to make a reference call if there is enough evidence there. A call in tumor and no-call in normal says you have coverage (and a variant) in the tumor and insufficient coverage in the normal. I guess this is a difference of an opinion about whether it's useful to know there is a tumor call even if you don't have normal evidence. I worry that you could throw away known variants by removing anything without normal coverage, especially in cases where you have uneven tumor and normal sequencing coverage. Thanks again for this discussion.

In what sense are the normal and tumor called together if there is no normal coverage at a given position? Can you really call it a known (tumor) variant given that fact?

Sam;
They're called together since FreeBayes has reads from both tumor and normal when making calls, so will try to distinguish homozygous reference versus no call at that position. In this case there is evidence for a call in the tumor sample, but no read evidence in the normal to help us determine whether it is somatic or germline. In a sense, it's similar to calling with tumor but no normal at this position. You're right that the majority of these will be germline. This is the same as if you sequenced a tumor without the normal; a majority of those calls are germline. However, throwing them all out also throws out the minority which are somatic variants.
You're right that you don't know if it's somatic or germline, and that the majority are germline.  In the lack of normal evidence, we typically rely on prioritization schemes (http://bcb.io/2015/03/05/cancerval/) for these tumor only cases as the best way to try and reduce the background. Hope that helps explain the thinking.

Sounds like it would make sense to discard these in your matched normal path but keep them in the without-normal path?

Sam;
I was only trying to draw a parallel between this case: matched tumor/normal with no normal coverage at a region, and tumor-only calling. You'd interpret both the same way, as a variant in the tumor without any sample specific knowledge about whether it's somatic or germline.

Hi Sam,
I will close this guessing you all the information you needed. Let us know if you find more issues.
Thanks!


feat: Support configurable root location for creating notes

#38
My apologize in advance -- I'm not fluent in TS. Please just let me know if I'm making any dumb mistake.
Thanks.

Thanks for the contribution! 💙I'll have a look next week.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@62dda4d). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #331   +/-   ##
=========================================
  Coverage          ?   91.85%
=========================================
  Files             ?       21
  Lines             ?      921
  Branches          ?      211
=========================================
  Hits              ?      846
  Misses            ?       74
  Partials          ?        1

Impacted Files
Coverage Δ

src/utils/utils.ts
100.00% <ø> (ø)

src/commands/openDocumentByReference.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Sorry I was busy lately.
I don't have a windows as well. Sorry.

It was busy time for me as well, thanks for considering all comments!


Added @modifiers annotation

Added the @modifiers annotation tag. This can be used to list out class modifiers in the documentation.

Screenshot of modifiers in the wild:

Any chance of taking a look at this, @michaelseibt :champagne:

Anyone looking into this? I'm basically waiting until it's entering master before I start using Nucleus fully :)

@michaelseibt Cheers, man. Can you do a NPM version bump please? 🎉 🎉 🍾

Merged, bumped and published!

@michaelseibt Yay! I think I may do some work on the mobile styling next year, maybe a button that emulates sizes.

Nice, great feature :+1:

maybe a button that emulates sizes.

Great idea! http://demo.patternlab.io/?p=viewall-organisms-comments has this kind of feature and i also fancy the "random viewport size" button.


fix typo in tests

Coverage remained the same at 100.0% when pulling 0806ebfd33338304a59236a01a90de5317a659d0 on adam-golab:test-fix into dc6ed4a56c5b51f4a0b525a3d14c38616fd8757b on stefanjudis:master.

👍🏻


Update font

See http://localhost:8080/travels/north-america/caribbean/dominican-republic/samana/

Done


Revert "make adapter.js the result of browserification"

Reverts webrtc/adapter#146 due to merge conflict. Will reland later.

@fippo FYI

yep, will make a new PR. I wish there was blocking/blockedon here :-)

Build is failing due to travis-multirunner no longer can fetch firefox versions, seems like mozilla changed something on their download server.


[Bug] Figure out why Outlook body hash verification doesn’t work

For some reason, only email bodies downloaded from gmail clients work. There is probably some dumb string parsing issue when downloading the email body, but detecting this and fixing it would make it a lot more general of a system. Easy for yush to generate an email that can be read on the outlook and gmail clients, so just ask him for an email if you need a copy to get started on this issue!

kindly assign the issue to me


Move to pytest

Move from nose to pytest
nose is no longer maintained, thus we have to move to another
testing system in the long run. This commit updates the make
setup to use pytest instead of nose. However all tests needs
to be migrated to pytest now and no longer use nose/tools

Well, I think Travis already approved this commit. Thanks for taking care of that!


fix(services): change silence to false to see error log

fixes #41

Hello,
I use your project and first thing i notice is that there is no output in console if something wrong.
For local development i fixed that in global node_modules, by just changing silent argument to false.
I don't know, maybe there is exists more elegant solution to this. What do you think?
Best regards,
Aleh

We recently reworked a lot of the tool to cut down on verbosity of the internal actions. I've been meaning to address this; my preferred approach would be to collect the output of failed services and output only that. Simply outputting the proc.run for the services will also output the id's of all the service containers which is what I'd specifically like to avoid.

So for now I suggest to have a flag like --debug, using which user able to see full output. I like your idea, but do not understand how to implement it. Will review code and think tomorrow.

Also may be wise to consider using https://www.npmjs.com/package/debug.

This PR would really only help if the service container doesn't exist. If you start a service that fails it will still just show the sha for that container, the container will just exit immediately.
What would be more beneficial would be a --debug option that would run a tail on the logs so you could see why a container failed (internal to that service).
The issue I see with that though is if you're tailing all logs through a spawned process they wouldn't have any context, i.e. all the logs would just be outputting simultaneously for the multiple services.

After thinking about this, I'd like to propose a different approach. We're about to merge #55 which includes output of any services that failed to stop successfully. I'd like to add this to the service start process as well.
The output from docker is limited in detail (like I mentioned before, that's what logs give you). So my thought is to be more verbose about what service(s) failed to start by returning the id's in the error output. Then you at least have visibility on what failed and can investigate why.
Closing this PR. Tracking the fix for this in #41


Flex "direction" props crash on bare react native

Description
Flex "direction" props crash on bare react native
CodeSandbox/Snack link
https://snack.expo.dev/@giaptran/nativebase-template
Steps to reproduce

NativeBase Version
3.3.7
Platform

[X] Android
[ ] CRA
[ ] Expo
[X] iOS
[ ] Next

Other Platform
No response
Additional Information
No response

Hi @TVGSoft, Thanks for reporting the issue. We'll fix it soon.

Hi @TVGSoft, You can use flexDirection="row" as well. Let us know if it works.

Hi @TVGSoft, You can use flexDirection="row" as well. Let us know if it works.

same issues，it worked for me

Hi @TVGSoft @youniaogu, Closing this issue for now as flexDirection can be used instead of direction.


Go wasm not supported ?

Summary
I compiled a simple wasm instance with go, but it has exceptions.
Fatal error: Uncaught RuntimeException: An error happened while compiling or instantiating the module `/Users/mac-mini/go/src/demo/9/go_main.wasm`:
    8 link errors: (1 of 8) Import not found, namespace: go, name: debug (2 of 8) Import not found, namespace: go, name: runtime.wasmExit (3 of 8) Import not found, namespace: go, name: runtime.wasmWrite (4 of 8) Import not found, namespace: go, name: runtime.nanotime (5 of 8) Import not found, namespace: go, name: runtime.walltime (6 of 8) Import not found, namespace: go, name: runtime.scheduleCallback (7 of 8) Import not found, namespace: go, name: runtime.clearScheduledCallback (8 of 8) Import not found, namespace: go, name: runtime.getRandomData in /private/tmp/php-ext-wasm/lib/Instance.php:84
Stack trace:
#0 /private/tmp/php-ext-wasm/examples/test.php(7): Wasm\Instance->__construct('/Users/mac-mini...')
#1 {main}
  thrown in /private/tmp/php-ext-wasm/lib/Instance.php on line 84

Additional details
Go source code :
package main

func main() {

}

func test() {

}

Compile command : GOOS=js GOARCH=wasm go build -o go_main.wasm 8.go

Duplicate of https://github.com/wasmerio/wasmer/issues/924.
You've to declare the host functions (imported functions, aka imports) required by Go. Go WebAssembly toolchain is essentially targetting the Web for the moment, and a little jugglery is required to glue everything. Their approach (which is a valid one) is to required a set of imported functions.
Since this is more and more requested, I'm likely to implement this set of imported functions for all platforms (Go for PHP, Python, Ruby, C, C++, Rust etc.)…
Check this documentation to learn more about the PHP host function API: https://github.com/wasmerio/php-ext-wasm/tree/master/lib#function-wasm_new_instance, or https://github.com/wasmerio/php-ext-wasm/tree/master/lib#function-wasm_module_new_instance, or jump directly on this example: https://github.com/wasmerio/php-ext-wasm/blob/master/examples/imported_function.php.


Unable to create symlinks

Ahoi!
Since 2.6.2 we are unable to create symlinks in the charts anymore -- any idea?
If we add a symlink on the root of the chart (ie. ln -s /tmp env) and try to install the chart I'll get an error:
Error: error reading env: read /path/to/chart/env: is a directory

The same chart would work alright with 1.6.1.
PS. I have a test chart to reproduce the issue if you want to have a look, but you can literally just ln -s in an existing chart to reproduce.
EDIT: I assume we stopped supporting symlinks with this :)

Yes, going to be interesting how that feature can be reimplemented without looking "too similar" to the  implementation which facebook had.

Yes, I mentioned the reasoning behind this in the v2.6.2 release notes. The previous ticket has been re-opened.
Let’s keep the discussion rolling along in #1639. Thanks!

Release notes: https://github.com/kubernetes/helm/releases/tag/v2.6.2


Add Analytics

Google or App Insights...

Google Analytics is notorious in EU and GDPR regulations. Perhaps an alternative can be used...


hierarchical select field : order and hierarchy in select entries

I have a product table that has n to 1 relation ship (extract from product model below) to a category that's reorderable : I use the select field and it works fine for the  edit operation, but is it possible to display the category by order and displaying the hierarchy  ? in my case I jsut get a simple select ordered by default ? thanks
public function category()
{
    return $this->belongsTo('App\Category', 'category_id', 'id');
}

in categry crud controller :
$this->crud->enableReorder('name', 10);
// NOTE: you also need to do allow access to the right users:
$this->crud->allowAccess('reorder');

And here's the answer : thanks to @samsebastian (issue 502) for raising the issue somewhere around 2 years ago, I'm suprised I could not find any other mention of that one : here's a piece of code that will display hierarchical structure in the select2 field , sample code for newscrud article controller :
https://gist.github.com/breizhwave/512adcda4354d6a63d6b1596ea360cae

Thank you for sharing your solution @breizhwave ! Hmm... maybe we should consider including your select2_grouped as a default field, in Backpack? Anybody else - what do you think?
In the meantime, I would love it if you wrote a short article on your blog (or backpack's about this), providing the example too. Would love to mention it in our monthly newsletter too - sounds like a solution many would enjoy, even if we don't include it as a default field. What do you think?

Well @tabacitu this is great news, glad you consider it useful because for me I could not do without hierarchical structures. I'll write that blog entry for sure , when is your newsletter due ? you'd mind if I include a quick word about nova and how backpack still competes so well  (mainly -in my opinion- because of the answer you just made ... finally :) first one wins, I sent the same question to our friend Otwell :)

OK @tabacitu here's my post if you want to have a look at this wonderful piece of analysis
http://www.webmasterbulletin.net/2018/10/backpack-nested-field/2446

Hi @breizhwave ,
Great article - I’ll be sure to promote it in November's newsletter. Of course it’s ok to mention Nova :-)
I did not end up sending one in October, because there wasn’t anything BIG to say. I like to send as few newsletters as possible - I personally hate when projects bombard me with news about them, I wouldn’t want Backpack to become the same.
Thanks again.
Cheers!

@breizhwave , on second thought, I think this would be a great addition to Backpack. I think it would be very useful for working with things like Categories and other models that use the same ‘lft’, ‘rgt’, ‘depth’ nested set.
I’ve polished and improved the field since it had a few issues (did not work multiple times per form, etc) and will merge it into master as select2_nested - I think it’s a better name, since this isn’t actually to group options (as the original), but to show a nested model.
Deviation from select2:

Screenshot:

PR here: https://github.com/Laravel-Backpack/CRUD/pull/1687
Thanks again - very useful, I think!