Support resolving links in @DeprecationSummary content

Bug/issue #, if applicable: rdar://120374614
Summary
This adds support for resolving links in a symbol's @DeprecationSummary content.
Previously the ReferenceResolver didn't visit a symbol's deprecatedSummaryVariants so any link in that content didn't resolve but also didn't warn about the links being unresolved.
Dependencies
None
Testing
In a documentation catalog with any symbol, add documentation extension file with a @DeprecationSummary directive that has a link in its content.
Build and preview the documentation. The deprecation summary should link to the other page.
Replace the link with something that won't resolve—for example ``NotFound``—and rebuild the documentation. There should be a warning about the unresolved link.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
~[ ] Updated documentation if necessary~

@swift-ci please test

@swift-ci please test

@d-ronnqvist do you know if there's any reason why @DeprecationSummary is not listed as a directive in the DocC docs? https://www.swift.org/documentation/docc

@d-ronnqvist do you know if there's any reason why @DeprecationSummary is not listed as a directive in the DocC docs? https://www.swift.org/documentation/docc

I don't think there's a reason. Why probably my just forgot to list it.

can we add it as part of this pr?

@d-ronnqvist do you know if there's any reason why @DeprecationSummary is not listed as a directive in the DocC docs? https://www.swift.org/documentation/docc

I don't think there's a reason. Why probably my just forgot to list it.

can we add it as part of this pr?

I found that we do intentionally hide it from the documentation but I don't know why.


luci-mod-admin-full: ralink support wpa/wpa2 encryption

current luci code is not well compatible with ralink wifi driver, so device based on ralink chip such like vocore2 will not able to setting up its wireless encryption mode to wpa/wpa2, this patch is used to fix such problem.
IMHO, WPA/WPA2 should not special for "broadcom", but it should for the all drivers without mac80211 support, currently almost every wireless router already supported wpa and wpa2, but wep is already abandoned.

You must comprised the OpenWRT source with Ralink Specific Drivers to build your project, that's not the case where OpenWRT should officially fit.

Does not apply to OpenWrt.


re-write temporary bindings (let_ifvalid and let_mutable) for new drefing paradigm

Pursuant to a conversation with ACM, i should replace the let_ifValid and let_Mutable constructs with new constructs more focused on referencing/dereferencing. let_ifValid() becomes a dereferencing bind; the bound variable mutates the remote object when assigned to, and is drefd in free_exprs and operations let_mutable() becomes a box-bind; the bound variable mutates the pointer itself, and is preserved as a raw handle in free_exprs and operations Note: we should likely change the syntax of free_expr; no need to "dref" a handle syntactically, as that behavior is now dependant on how it was bound. Note: this should be a large re-write (if done correctly).  Will defer until after current context work and store implementations.

note: I did this.  But I did it by adding an extra layer on top of temporary references, which isn't a clean way of doing it.  So it works, but the source code isn't pretty.

note: I did this a lot better in 978f2f8989ddc6ea02a33d30576d61a99df5bd25


#10010: Menu overlay with css transforms (sections)

Description
Fixes #10010.
As comented in previous issue, when using MudMenu with css transform,
inner overlay does not covers the entire page, so clicking outside menu does not close it.
This fix adds an optional parameter (OverlaySection) to MudMenu, to allow render overlay outside mud-menu div (when necessary, for example, when a css-transforms is needed like the one mentioned in the original issue).

How Has This Been Tested?

unit
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[X] I've added relevant tests.

cc @versile2

Do we might want a more universal solution or one with less setup if this is generally an issue with MudOverlay?

I haven't used SectionOutlet before, does it have much overhead? Is there a reason we don't utilize it more if not? Seems useful, but doesn't do any good if we don't indicate how to and when to use it in the component docs page. Is there a reason we don't use the actual overlay ID instead of just overlay?

Is it possible to fix this for the overlay universally without any new properties like OverlaySection?

Is it possible to fix this for usage of the overlay universally and without any new properties like OverlaySection? Would like it to work as "out of the box" as possible because adding new properties creates new opportunities for bugs in the future.

Doesn't appear so, in addition to OverlaySection property the user must also create a SectionOutlet on their side to receive the Overlay. It's a valid solution for MudMenu but what about the other things that use MudOverlay? Though I'll defer whether we want the complexity up to you. If so we need a doc example. Everything else is good.

Is it possible to fix this for usage of the overlay universally and without any new properties like OverlaySection? Would like it to work as "out of the box" as possible because adding new properties creates new opportunities for bugs in the future.

Doesn't appear so, in addition to OverlaySection property the user must also create a SectionOutlet on their side to receive the Overlay. It's a valid solution for MudMenu but what about the other things that use MudOverlay? Though I'll defer whether we want the complexity up to you. If so we need a doc example. Everything else is good.

I really don't like the added complexity for a niche issue that doesn't solve other cases like you mentioned

Hi, closing due to inactivity and the issues mentioned in comments above.

Having the user implement a section outlet for the overlay feels a bit weird to me.


background blur doesn't work when the url bar is in focus after the new update

Affected Theme

Name
Version (e.g. x.x.x)

Affected Theme Settings

x

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots/Videos
If applicable, add screenshots or videos to help explain your problem.
Additional context
Add any other context about the problem here.

Fixed with v1.1.1


Update README.md to reflect version changes

These instructions are outdated as of the 2.0.0 release, published to npm a couple of hours before this pull request was submitted.
Without these changes, following the directions for installation alongside webpack 1 results in an "unmet peer dependency" error.

Thanks @candu - Please sign the CLA and i'll get this merged.

Just signed it, though it isn't showing up on the automatic check dashboard above.

Usually a sign of your local git config email not matching that which resides in your github account.

I tried revoking CLA access, adding the email address in question to my github account, setting it as my primary, and re-signing.  No dice; it insists on auto-filling my old email address.
Is there an easier way to remedy this?  I'm happy to sign the CLA, but it isn't making this easy for me, and I don't have loads of time in the middle of a workday to debug further.

I hear ya on the workday thing. I'll find you an actual answer as opposed to guessing at a fix.
In the mean time, we can either wait on an answer or I can just update the readme myself and close this PR, totally up to you.
Given the commit is already tied to the mismatched email, i'm betting the answer I will get is to do all of this over again ( less than optimal but realistic ) If you choose the latter, I'll close this and update the readme to reflect the doc change immediately.


Add support for pod matching based on labels

This change adds a new selector property k8s_pod_labels to the services configuration. This selector property will limit the instrumentation to the applications running in the Pods having labels with matching keys and values.
Addresses https://github.com/grafana/beyla/issues/691
Please let me know what you think and whether we can improve the implementation.

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

Codecov Report
Attention: Patch coverage is 70.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 39.81%. Comparing base (933917a) to head (0f97fa5).
Report is 2 commits behind head on main.

Files
Patch %
Lines

pkg/internal/discover/matcher.go
62.50%
4 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #694       +/-   ##
===========================================
- Coverage   76.86%   39.81%   -37.05%
===========================================
  Files          97       94        -3
  Lines        8008     7827      -181
===========================================
- Hits         6155     3116     -3039
- Misses       1512     4532     +3020
+ Partials      341      179      -162

Flag
Coverage Δ

integration-test
?

unittests
39.81% <70.00%> (+0.39%)
:arrow_up:

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

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


Add pre commit hooks

This PR adds several pre-commit hooks that enforce code quality.

black8 autoformatting
flake8 linting
general checks like detect-aws-credentials etc.

As soon as this is merged, I would follow up with a PR, making the existing code comply with the pre-commit hooks.
This would be a "major" refactor though, thoughts @MrPowers?

@robertkossendey - this looks good.  Can you add a CONTRIBUTING.md file with clear instructions on how to comply with all the pre-commit hooks?  I see you removed Black from the pyproject.toml file... wouldn't we want to keep that so we can run a command to format the code before committing?  Or will that all just be done automatically?

@MrPowers will do 👍 I removed black, because it will be download automatically by specifying it in the repo in the pre-commit.config.yml

YOLO merge!


Command_Line_Client 404

https://volumio.github.io/docs/Good_to_Knows/Command_Line_Client

This link is available from the landing page, https://volumio.github.io/docs/index.html


codec-memcache: copy metadata in binary full request response

Motivations
Calling copy(), duplicate() or replace() on FullBinaryMemcacheResponse
or FullBinaryMemcacheRequest instances should copy status, opCode, etc.
that are defined in AbstractBinaryMemcacheMessage.
Modifications

Modified duplicate, copy and replace methods in
DefaultFullBinaryMemcacheRequest and DefaultFullBinaryMemcacheResponse
to always copy metadata from parent classes.
Unit tests verifying duplicate, copy and replace methods for
DefaultFullBinaryMemcacheRequest and DefaultFullBinaryMemcacheResponse
copy buffers and metadata as expected.

Fixes #9159
Checklist:

Signed ICLA

Note: need to add license header and fix line length
On Sun, May 19, 2019 at 16:45 netty-bot<EMAIL_ADDRESS>wrote:

Can one of the admins verify this patch?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netty/netty/pull/9160?email_source=notifications&email_token=AAXX2KLFPWIPZGYWE5P6CNTPWHRBVA5CNFSM4HN5UHLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVXNG6Y#issuecomment-493802363,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXX2KK2YLM5VLRQER3CGVTPWHRBVANCNFSM4HN5UHLA
.

--
Fabien

@netty-bot test this please

@netty-bot test this please

@netty-bot test this please

@fabienrenaud thanks a lot!


unify the schema into a single one

@ElaineMcA  This should go along with the data_pipeline refactor effort with @mkarmona @afaulconbridge


feat(text): add harper to grammar check comments and text

I've been testing a lot of English grammar/style checkers.
I liked https://github.com/elijah-potter/harper the best. It's simple to set up, and it adds very useful Code Actions to add words to your global (or file) dictionaries.
So, here's my contribution to add it to LazyVim. Not sure if you want to create this text dir but it feels to me that harper would not belong to linting, coding, or any other dir.

Is there any way to enable Harper only when set spell is enabled?

Is there any way to enable Harper only for buffers where set spell is enabled?

@smarquez1 I'm sorry, I'm afraid I don't know how.

Is there any way to enable Harper only for buffers where set spell is enabled?

Maybe an autocmd with OptionSet could work? https://neovim.io/doc/user/autocmd.html#OptionSet


docs: refactor AKS installation instructions

BYOCNI was initially introduced as the preferred installation method for Cilium on AKS clusters in d8259c1a806965c8e23f0b355a1ee99884796717, at the cost of doubling the number of AKS tabs in Getting Started and Helm guides.
Since then:

More tabs have been added, making it even more complex to navigate the options.
BYOCNI is now GA (Azure CLI version 2.39.0).
Azure CNI Powered by Cilium has been announced, further complexifying the Cilium on AKS landscape.

In order to reduce bloat and streamline AKS installation instructions, we refactor the AKS instructions in a single tab. We use this opportunity to strongly encourage users to use BYOCNI, and prepare for Azure IPAM legacy retirement.
Even though we could very add it into the current structure, Azure CNI Powered by Cilium has not been introduced as another installation option here, because the Cilium distribution used in this case is maintained and controlled by AKS, and not by the Cilium community. We felt this was sensible considering there is already a similar situation with GKE's Dataplane V2 and it is not listed in Cilium documentation either.

I am adding the backport label for 1.13 just in case it makes sense to have this in before release. If it does not, feel free to remove.

I am adding the backport label for 1.13 just in case it makes sense to have this in before release.

Backport Criteria for documentation changes
Changes to Cilium’s documentation should generally be subject to backports for all supported branches to which they apply (all supported branches containing the parent features to which the modified sections relate).
The motivation is that users can then simply look at the branch of the documentation related to the version they are deploying, and find the latest correct instructions for their version.

(https://docs.cilium.io/en/latest/contributing/release/backports/#backport-criteria-for-documentation-changes)
So makes sense to me to backport.

Looks good to me, although it's a bit difficult to review and understand what has moved, what has disappeared, and what has simply been reformatted with a smaller paragraph width.
The Azure IPAM instructions are now gone from k8s-install-default.rst, everything else is still here but moved around to other tabs etc., am I correct?

Sorry about that, such is the bane of indentation-based edits. I gave a high level intent in the commit description but here is a more detailed report of what happened in terms of edits, I will also add this back in the commit description:

Getting Started Guides:

We had 2 separate AKS tabs for creating AKS clusters (one for BYOCNI and one for Azure IPAM), now we have only one AKS tab and it only explains how to create a cluster for BYOCNI. This is the only set of instructions that was removed, and it was done intentionally so as to just silently encourage users that don't have a cluster yet to use BYOCNI.
We had 2 separate AKS tabs for installing Cilium in an AKS cluster (one for BYOCNI and one for Azure IPAM) but they actually contained the exact same installation instructions. This is because the Cilium CLI is responsible for automatically detecting which mode to use based on the cluster type. Now we have only one AKS tab with the installation instructions up front, and then sub-tabs for both modes with the rest of the previous info we had (requirements + limitations).
So putting the 2 together, if it happens that someone already had an AKS cluster and did not create it with BYOCNI, it'll still work, and if someone actually does want to use Azure IPAM intentionally, they can still figure it out based on the requirements.

Helm:

We had 2 separate AKS tabs for installing Cilium in an AKS cluster (one for BYOCNI and one for Azure IPAM). Now we have only one AKS tab with sub-tabs for both modes with all the previous info we had (installation instructions + requirements + limitations).

Both:

BYOCNI is made even more explicit as the preferred option for installing Cilium on AKS, since it's now GA on AKS.
Azure IPAM has been re-dubbed Legacy Azure IPAM to double down on that fact, in preparation for the fact we might want to stop maintaining it.

Sorry about that, such is the bane of indentation-based edits. I gave a high level intent in the commit description but here is a more detailed report of what happened in terms of edits, I will also add this back in the commit description:

That's where having more than one commit usually helps.

That's where having more than one commit usually helps.

In this case we would end up with a first commit where changes are done but the doc does not compile (due to indentation) and lines go over the line width, and then a second one to fix both. I personally don't like like it much :/

That's where having more than one commit usually helps.

In this case we would end up with a first commit where changes are done but the doc does not compile (due to indentation) and lines go over the line width, and then a second one to fix both. I personally don't like it much :/

I would prefer it over bad reviewing experience. I doubt we often need to bisect on docs changes so temporarily breaking the lint checks there is probably okay.

Merging given reviews and passing docs test.


Python 3 support.

This module does not supports Python version 3, (or, so it seems). This is nowhere mentioned.

+1

Hi
I added python3 support. I could not submit it to this rep, but it is upload and open to download from my fork.
https://github.com/HishamKamal/code2flow/tree/Python3.0Version

@HishamKamal why don't you open a PR?

Not sure what PR stands for ?!

@HishamKamal PR means Pull Request

Done, thanks.

I just closed the Python3 PR given that I ended up doing a rewrite of the project. I feel deeply sorry I didn't see this at the time. The rewrite does support Python3 so I think the issue is now addressed.


[python3] build failure

Host Environment

OS: Windows 10
Compiler: Visual Studio 2015 Update 3
CMake 3.17.3

To Reproduce
Steps to reproduce the behavior:
vcpkg.exe --triplet x64-windows install python3
Failure logs
Computing installation plan...
The following packages will be built and installed:
    python3[core]:x64-windows
Starting package 1/1: python3:x64-windows
Building package python3[core]:x64-windows...
-- Using cached C:/dev/vcpkg/downloads/python-cpython-v3.8.3.tar.gz
-- Extracting source C:/dev/vcpkg/downloads/python-cpython-v3.8.3.tar.gz
-- Using source at C:/dev/vcpkg/buildtrees/python3/src/v3.8.3-43b03f2bf0
-- Building C:/dev/vcpkg/buildtrees/python3/src/v3.8.3-43b03f2bf0-Lib-Win/PCBuild/pythoncore.vcxproj for Release
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: msbuild C:/dev/vcpkg/buildtrees/python3/src/v3.8.3-43b03f2bf0-Lib-Win/PCBuild/pythoncore.vcxproj /p:Configuration=Release /t:Rebuild /p:Platform=x64 /p:PlatformToolset=v140 /p:VCPkgLocalAppDataDisabled=true /p:UseIntelMKL=No /p:WindowsTargetPlatformVersion= /m
    Working Directory: C:/dev/vcpkg/buildtrees/python3/x64-windows-rel
    Error code: 1
    See logs for more information:
      C:\dev\vcpkg\buildtrees\python3\build-x64-windows-rel-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_msbuild.cmake:120 (vcpkg_execute_required_process)
  ports/python3/portfile.cmake:56 (vcpkg_build_msbuild)
  scripts/ports.cmake:76 (include)

Error: Building package python3:x64-windows failed with: BUILD_FAILED

C:\dev\vcpkg\buildtrees\python3\build-x64-windows-rel-out.log
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 6/18/2020 4:00:04 PM.
     1>Project "C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\pythoncore.vcxproj" on node 1 (Rebuild target(s)).
     1>C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\python.props(111,31): error MSB4184: The expression "[System.Version]::Parse('')" cannot be evaluated. Version string portion was too short or too long. [C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\pythoncore.vcxproj]
     1>Done Building Project "C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\pythoncore.vcxproj" (Rebuild target(s)) -- FAILED.

Build FAILED.

       "C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\pythoncore.vcxproj" (Rebuild target) (1) ->
         C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\python.props(111,31): error MSB4184: The expression "[System.Version]::Parse('')" cannot be evaluated. Version string portion was too short or too long. [C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\pythoncore.vcxproj]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.02

Additional context
I was trying to install boost when I get this failure.

open C:\dev\vcpkg\buildtrees\python3\src\v3.8.3-43b03f2bf0-Lib-Win\PCBuild\python.props
winsdk?
https://github.com/python/cpython/blob/6f8c8320e9eac9bc7a7f653b43506e75916ce8e8/PCbuild/python.props#L111
    <!-- The minimum allowed SDK version to use for building -->
    <DefaultWindowsSDKVersion>10.0.10586.0</DefaultWindowsSDKVersion>
    <DefaultWindowsSDKVersion Condition="$([System.Version]::Parse($(_RegistryVersion))) > $([System.Version]::Parse($(DefaultWindowsSDKVersion)))">$(_RegistryVersion)</DefaultWindowsSDKVersion>
  </PropertyGroup>

  <PropertyGroup Condition="$(WindowsTargetPlatformVersion) == ''">
    <WindowsTargetPlatformVersion>$(DefaultWindowsSDKVersion)</WindowsTargetPlatformVersion>
  </PropertyGroup>

https://github.com/microsoft/vcpkg/blob/ba98abdd0d1df9f8d68653f8d74c8344c73059c2/ports/python3/portfile.cmake#L56
add
/p:WindowsTargetPlatformVersion=${TARGET_PLATFORM_VERSION}

Solved. I was installed only winsdk 8.1.

Thanks @Voskrese


configration blocking error

Hi ,
I ran into this problem when i first include the library in my project ,
the keyFilename field in configuration object passed to start function ,
when its value is wrong and not found ,it throw an error and closes the application , that is maybe ok ,but the problem is that  the error is also a runtime error .
Please consider to catch the error and give a warning instead.

Hi @dlinah -- can you give us a repro case as well as the Node version/agent version you are running? When I run the following, it doesn't seem to bring the process down:
const trace = require('..').start({ keyFilename: 'non-existent', bufferSize: 1 });
trace.runInRootSpan({ name:'my-root' }, span => span.endSpan());
// keep process alive
setInterval(() => {}, 100);

Hi @dlinah -- we'll be closing this for now. Please feel free to add a comment if you would like us to re-open this issue.


Set pending for a spec to skip CI failure

we  need find clean solution for https://github.com/ManageIQ/manageiq/pull/16418
cc @agrare
@miq-bot assign @chrisarcand
@miq-bot add_label test

Thanks @lpichler

@agrare gaprindashvili/yes/no? I'd assume yes but I guess it's difficult to tell because of the other unrelated CI woes.

@chrisarcand I don't think the PR that introduced this is back to gaprindashvili https://github.com/ManageIQ/manageiq/pull/16350


[APIv2] volume create http response status code is 200, but in doc is 201

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description

volume create http response code is 200, but in doc is 201
Steps to reproduce the issue:

podman system service --timeout 0 tcp:<IP_ADDRESS>:8080

curl -v -X POST -H 'Content-type: application/json' -d '{"Name":"test0142","Label":{"helloname":"yujiang","time":"2020"}}' http://localhost:8080/v1.40/libpod/volumes/create

Check the output

Describe the results you received:
Note: Unnecessary use of -X or --request, POST is already inferred.

Trying ::1:8080...
connect to ::1 port 8080 failed: Connection refused
Trying <IP_ADDRESS>:8080...
Connected to localhost (<IP_ADDRESS>) port 8080 (#0)

POST /v1.40/libpod/volumes/create HTTP/1.1
Host: localhost:8080
User-Agent: curl/7.69.1
Accept: /
Content-type: application/json
Content-Length: 65

upload completely sent off: 65 out of 65 bytes
Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Mon, 08 Jun 2020 19:28:43 GMT
< Content-Length: 226
<
{"Name":"test0142","Driver":"local","Mountpoint":"/var/lib/containers/storage/volumes/test0142/_data","CreatedAt":"2020-06-08T15:28:43.173893297-04:00","Labels":{"helloname":"yujiang","time":"2020"},"Scope":"","Options":null}

Describe the results you expected:
http://docs.podman.io/en/latest/_static/api.html#operation/createVolume
Refer to the doc, the response status code should be 201
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.9.3
RemoteAPI Version:  1
Go Version:         go1.14.3
Git Commit:         8891b82332de4afa23f935b58263d08a3a5c6d95
Built:              Mon Jun  8 15:21:36 2020
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  gitCommit: 8891b82332de4afa23f935b58263d08a3a5c6d95
  goVersion: go1.14.3
  podmanVersion: 1.9.3
host:
  arch: amd64
  buildahVersion: 1.14.9
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.17-1.fc32.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.17, commit: bb8e273f5925c1a51737644637ef65d094a67ab1'
  cpus: 4
  distribution:
    distribution: fedora
    version: "32"
  eventLogger: file
  hostname: hp-dl360g5-01.mpc.lab.eng.bos.redhat.com
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.6.16-300.fc32.x86_64
  memFree: 573079552
  memTotal:<PHONE_NUMBER>
  ociRuntime:
    name: crun
    package: crun-0.13-2.fc32.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.13
      commit: e79e4de4ac16da0ce48777afb72c6241de870525
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree:<PHONE_NUMBER>
  swapTotal:<PHONE_NUMBER>
  uptime: 11h 21m 2.96s (Approximately 0.46 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 0
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

Additional environment details (AWS, VirtualBox, physical, etc.):
fadora32

@ryanchpowell PTAL. Feel free to reach out to me or @jwhonce if you need help getting started!

@ryanchpowell Any progress on this?

@rhatdan I have not made any progress on this issue.

I see 201 with the latest upstream master:
* Could not resolve host: POST
* Closing connection 0
curl: (6) Could not resolve host: POST
*   Trying ::1:8080...
* connect to ::1 port 8080 failed: Connection refused
*   Trying <IP_ADDRESS>:8080...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#1)
> POST /v1.40/libpod/volumes/create HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.69.1
> Accept: */*
> Content-type: application/json
> Content-Length: 65
>
* upload completely sent off: 65 out of 65 bytes
* Mark bundle as not supporting multiuse
< HTTP/1.1 201 Created
< Content-Type: application/json
< Date: Mon, 27 Jul 2020 19:17:57 GMT
< Content-Length: 275

Good to close this?

Reopen if it is still  broken.


Magnetometer setup issues

Hi
Although not implementing the library, I have used it as a reference for setting up and reading the icm20948. I appreciate your work because it is one of the most elaborated and easy to read driver software out there.
It seems the main culprit with the module is the magnetometer and how to access it. Trying to read the "who i am" variable didn't seem to work at all. Then after testing different options occasionally but by no means reliably. Adding delays before reading SLV0_DATA didn't seem to help at all.
Then I decided to do the setup and register read operations through SLV4 instead - and magic occurred. I2C_SLV4_CTRL has a trigger bit for read/write operations and will reset after completed operation that can be polled. I still use SLV0 for the sensor readings.
Now it work like a charm - every reset and power-up. This may solve your inconsistent magnetometer start-ups.
Btw, your myIMU.getMagValues() method approach may no be very commendable. It will return a pointer to memory that has been returned to the heap (free()) since it's a dynamic variable that gets out of scope with "return".  It will probably work almost 100% but I would rather see myIMU.getMagValuesmagValue(&magValue).
Keep up your good work, Chris

Hi @ChrisHul , that sounds promising. I will try another time to solve the issue using your solution. Thank you!!
Wolfgang

Hi @ChrisHul, I followed your advice to do the settings of the magnetometer by using it as SLV4. And I also still use it as SLV0 for data reading. It works! Hurray! Since it was a sporadic issue (at least on my side) I tried it very often under various conditions, e.g. different MCUs, I2C/SPI, reconnecting to power, rebooting and uploading again and again. Feels like I did this 1000 times.
I don't think you can imagine how thankful I am for your tip! I spent so many hours before.
What I don't exactly understand is why using the magnetometer as SLV0 was causing an issue. Somehow register reading and writing interfered with the data reading. But why?
The other issue with myIMU.getMagValues() is basically easy to solve. But the new version would not be compatible with programs written for the fomer versions. This might trigger a lot of questions. On the other hand, I would like to remove this unclean code. I will think about this.
Best wishes!

Hi again,
That was quicker than I thought it would be. "Another time" sounded like weeks away.
SLV4 is different from other SLVs in that the EN flag is specified to RESET upon completed transfer. The problem with the others is that you will never know when operation will occur because it is conditioned by the ODR (sampling rate) and the magnetometer readings are dependent on the Gyro and Acc ODR (as stated in the magnetometer ODR parameter). Maybe there is a delay in the start-up of the Gyro and the Magneto readings only start after a while. The datasheet is rather crappy when it comes to the timing.
About the myIMU.getMagValues() I just wanted to make you aware of the problem. I got in trouble myself for returning pointers to dynamic structures and arrays. Being a tutor you probably want to stay safe with the advice you give.
Another thing I discovered when dealing with the Gyro is that it seems to have an internal bias correction on start-up. On highest sensitivity it sometimes meant that it picked up an out of range value (2^15) and my readings on that axis stayed there until a new power-up. Disabling and enabling with a delay in between solved that problem. PWR_MGMT_2 = 0x3F, delay, PWR_MGMT_2 = 0. I saw someone else had done the same thing (other repository).
And you don't have to thank me for anything. You have done more to the community than I ever will, so I am just happy to contribute with anything I can.
Schönen Abend und auf Wiederhören, Chris

Hi @ChrisHul
I'm wondering if the current code in the version 1.1.11 has that change, because I'm facing blocking on the resetMag() function.
And the resetMag function is calling writeAK09916Register8_SLV4(AK09916_CNTL_3, 0x01);, that sometimes blocks on an eternal while
   while(readRegister8(3, ICM20948_I2C_SLV4_CTRL) & ICM20948_I2C_SLVX_EN){;}
So i'm not sure if your proposed idea is implemented or not.
Thank you

Hi @medisoft
You should be running 1.2.0 if you have the writeAK09916Register8_SLV4() in your code.
I'm not running Arduino (but rather Raspberry pi pico SDK), so I didn't propose the code myself.
I think our friend Wolfgang made the changes in a rush. I created a fork of the repository on my account () with some cleanup. I can't try it out. Maybe you can be so kind and try it before I make the pull request? That would be appreciated.

Some how the link to the fork got lost:
https://github.com/ChrisHul/ICM20948_WE/tree/main

Hi, currently I can't try myself. It looks like I've overdone it with the sport and will have to stay in hospital for a few days. Very bad timing.

No worries. We'll see if we can sort it out.
Take care. Recover soon.

I am back.
@ChrisHul, I tested you forked version and it works fine. Thank you! The only thin I would do additionally is deleting the function
void ICM20948_WE::enableMagDataRead_SLV4(uint8_t reg){}
since it is not needed anymore.
However I had also tested my former version and it also worked without any problem. So, I suggest we wait for the feedback from @medisoft.

Good to know you're back on your feet @wollewald
Sure. It shouldn't really block because the flag is stated to reset after completed operation. I think the fact that (1.2.0) set the 'reg'-register after setting the triggering flag in the write-method may have upset the module. You could also intertwine some sort of timeout in the while-statement to stop the system from hanging, but you don't seem to do a lot of error-testing anyway.
Let's hope @medisoft comes back  with a result of his testing.

@ChrisHul , I tested version 1.2.0 on an ESP32 and Arduino Nano using I2C  and SPI. Resets, power on, new uploads. Overall several hundred times. It did not hang a single time. Difficult to solve a problem which does not occur on my side.


[Fix] Fix colortoggle not displaying and Misorganized document layout

Fix certain known issues

Fixed missing theme button
The issue of missing document directories

This branch has a conflicts with the base branch. This PR is invalid, please see https://github.com/apache/incubator-streampark-website/pull/370 .


should work with Archlinux?

I just done the clone but the copied sd card doesn't boots...

I can confirm it works. I was having some disconnecting troubles of my card reader ;)


Fixed mongo connection issue

Fixed line 10 of app.js/connection issue

pull request sent to the incorrect repo. Not merging.


RAR-b initial PR

Initial PR for RAR-b: Reasoning as Retrieval Benchmark. The benchmark evaluates reasoning tasks as retrieval tasks to assess reasoning-level understanding of embedding models.
Plan to do this in multiple PRs:

[x] add 17 RAR-b datasets
[x] test without-instruction Full-dataset Retrieval
Have tested a few models including sentence-transformers/all-MiniLM-L6-v2 and sentence-transformers/all-mpnet-base-v2 and the results can match exactly with the paper with own RAR-b codebase https://arxiv.org/abs/2404.06347.

To do:

[ ] add/test with-instruction Full-dataset Retrieval
[ ] add/test Multiple-choice Retrieval

Will work on Full-dataset Retrieval with-instruction setting next. Might still go with AbsTaskRetrieval for this and make neccessary adjustments. It would be great to get this PR reviewed and some opinions on the best way to integrate the with-instruction setting! :)
Checklist

[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

Adding datasets checklist

Reason for dataset addition: ...

[x] I have run the following models on the task (adding the results to the pr). These can be run using the mteb -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).
[x] If the dataset is too big (e.g. >2048 examples), considering using self.stratified_subsampling() under dataset_transform()
[x] I have filled out the metadata object in the dataset file (find documentation on it here).
[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

@KennethEnevoldsen thanks for the suggestions! Have fixed for all 17 datasets:

n_samples; avg_character_length added
"Reasoning as Retrieval" task_subtypes added (also for allowed subtasks). Really like this!
descriptions made more descriptive.

Sounds good - anything additional to add in this PR?

@KennethEnevoldsen not really. I'll add the rest in seperate PRs. Feel free to merge this one if okay :)

Perfect, wanted to make sure that was your intention as well.

Amazing work on this 🙌🙌🙌
If you want we can add a leaderboard tab for RAR-b similar to https://huggingface.co/spaces/mteb/leaderboard?task=retrieval&language=longembed
We just need a PR with all the results like this one: https://huggingface.co/datasets/mteb/results/discussions/49 - If you have them in a different format right now, you can just reformat them into the MTEB results format with a simple script.
cc @gowitheflow-1998

@Muennighoff  🙌🙌🙌 a leaderboard tab will be great for sure! Would you like I start integrating the without-instruction results to the leaderboard while I work on integrating with instruction code to the code base? By different formats do you mean results produced from my own implementation will be fine or not?

I think it makes sense to integrate the instruction code first and then we do the leaderboard tab after.
If your implementation produces the same results as here, then that's fine but we just need the results as json files looking like this: https://github.com/embeddings-benchmark/mteb/blob/main/results/BAAI__bge-base-en-v1.5/a5beb1e3e68b9ab74eb54cfd186867f64f240e1a/BiorxivClusteringP2P.json

@Muennighoff got you. Will integrate the code first then! Wondering if you think it is a good idea to reflect both settings in the leaderboard (say as two tabs) to align with the paper? I imagine it would be great to reflect different model capabilities, i.e., some models are not (and probably won't be) trained to follow instructions for example. But I am open to both options!

Good point, maybe let's decide after the instruction setting is merged? I think it'll become clearer then 🤔

@Muennighoff no problem. Will do soon!


Clarify prerelease package documentation

Addresses https://github.com/NuGet/docs.microsoft.com-nuget/issues/1423

Docs Build status updates of commit 6dc0826:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 268a02f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d4eb4e9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/create-packages/Prerelease-Packages.md
:warning:Warning
View
Details

docs/create-packages/Prerelease-Packages.md

Line 22: [Warning] Invalid file link:(~/consume-packages/package-references-in-project-files).
Line 30: [Warning] Invalid file link:(~/reference/packages-config).
Line 30: [Warning] Invalid file link:(~/reference/nuspec).
Line 30: [Warning] Invalid file link:(~/reference/nuspec#version).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0b1dca1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@nkolev92, could you review again please? :)


Concurrency when using TestServer

Problem
I was trying to do some concurrency testing on my app and ran into this issue. The following is a simplified snippet:
#[tokio::test]
async fn test_something() {
    let app = axum::Router::new().route(
        &"/todo",
        axum::routing::get(|| async {
            tokio::time::sleep(std::time::Duration::from_secs(1)).await;
            "hello!"
        }),
    );
    let server = axum_test::TestServer::new(app).unwrap();

    let future1 = async { server.get("/todo").await };
    let future2 = async { server.get("/todo").await };
    let (r1, r2) = tokio::join!(future1, future2);

    assert_eq!(r1.text(), r2.text());
}

It seems this code does not halt, not sure if its due to some internal workings of the TestServer or if I did something wrong.
Environment
Cargo.toml:
[dependencies]
axum = { version = "0.7.5", features = ["macros"] }
axum-test = "14.10.0"
tokio = { version = "1.38.0", features = ["full"] }

Hey, I have just spent some time looking at this. I am pretty certain this is a bug. I think this is a deadlock bug.
For more context; internally there is a TransportLayer, and this is wrapped in a lock. I think it gets locked for the first request, that then waits, the second request then goes to grab the lock, is also blocked (first still holds the lock), and so everything just halts.
I will look into fixing this today.

Hey @ericywl , you should now find this fixed in the latest version 15.0.0. This version also brings a requirement for using Rust 1.75 or higher.
Please try that version, and feel free to let me know if there are any issues.

@JosephLenton Thanks for the quick response, I have confirmed that it's working as expected. Closing the issue now.


Code in NPM registry is not latest

The js that is downloaded via npm install does not match the latest in the repo... can this please be fixed? The 'equals' and the 'pattern' both have issues in the version in the registry but they work great on the demos using the most current code. Our project relies on the registry as part of the build process for 3rd party code. Thanks in advance!

Yes, please fix this. When I download your package via NPM the addMessages and setLocale functions aren't in there!

still missing latest version on NPM and jsdelivr

Here's a "fix"  "pristinejs": "git+https://github.com/sha256/Pristine.git" Use this in your package.json and rerun npm install
@sha256 you left this repo for dead?

Agreed.  Looks like the author just forgot to bump their NPM package version in package.json, which is why we are getting the old code.  The README was correctly updated though, making it reference functions in NPM on the NPM website that don't actually exist.  Must use @kevinmu17 solution until resolved.


python311Packages.experiment-utilities: 0.3.5 -> 0.3.6

Description of changes
Changelog: https://gitlab.inria.fr/creinke/exputils/-/commit/437a36a34ec3a260ce8bfc8928c0c83269aa2f0e
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] 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/)
23.11 Release Notes (or backporting 23.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.

There are two new dependencies: notebook <= 6.5.6 (the one in nixpkgs is 7.0.3) and jupyter_contrib_nbextensions >= 0.7.0 (which is broken).

There are two new dependencies: notebook <= 6.5.6 (the one in nixpkgs is 7.0.3) and jupyter_contrib_nbextensions >= 0.7.0 (which is broken).

Yes that's right. The notebook ecosystem is partly unmaintained unfortunately.
As a user of this package though, I can affirm that those dependencies are not needed for the core features of experiment-utilities.
Hence, this should not be a blocker for updating.


Bazel build failed with error  Undefined symbols:   OBJC_CLASS$_ALAssetsLibrary

OS Platform and Distribution
MacOS 13.6
Compiler version
Apple clang version 15.0.0
Programming Language and version
Swift 5
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
I pull the latest main branch (v10.7 on github version)
Bazel version
bazel 6.3.2-homebrew
XCode and Tulsi versions (if iOS)
XCode 15.0
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
Failed when I run bazel build
bazel build //mediapipe/examples/ios/posetrackinggpuswift:PoseTrackingGpuSwiftApp --ios_multi_cpus=arm64 --xcode_version=15.0
BUILD file content:
# Copyright 2020 The MediaPipe Authors.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

load(
    "@build_bazel_rules_apple//apple:ios.bzl",
    "ios_application",
)
load(
    "//mediapipe/examples/ios:bundle_id.bzl",
    "BUNDLE_ID_PREFIX",
    "example_provisioning",
)

licenses(["notice"])

MIN_IOS_VERSION = "13.0"

alias(
    name = "posetrackinggpuswift",
    actual = "PoseTrackingGpuSwiftApp",
)

load("@build_bazel_rules_swift//swift:swift.bzl", "swift_library")

load(
    "@rules_xcodeproj//xcodeproj:defs.bzl",
    "top_level_target",
    "xcodeproj",
)

# load("@rules_cc//cc:defs.bzl", "objc_library")

xcodeproj(
    name = "xcodeproj",
    build_mode = "bazel",
    project_name = "PoseTrackingGpuSwiftApp",
    tags = ["manual"],
    top_level_targets = [
        top_level_target(
            ":PoseTrackingGpuSwiftApp",
            target_environments = [
                "device",
                "simulator",
            ],
        ),
    ],
)

ios_application(
    name = "PoseTrackingGpuSwiftApp",
    app_icons = ["AppIcon"],
    bundle_id = "xxx.mediapipe.sample",
    families = [
        "iphone",
        "ipad",
    ],
    infoplists = [
        "Info.plist",
    ],
    minimum_os_version = MIN_IOS_VERSION,
    provisioning_profile = example_provisioning(),
    deps = [
        ":PoseTrackingGpuSwiftAppLibrary",
        "@ios_opencv//:OpencvFramework",
    ],
    visibility = ["//visibility:public"],
)

# objc_library(
#     name = "PoseTrackingGpuAppLibrary",
#     srcs = [
#         "PoseTrackingViewController.mm",
#     ],
#     hdrs = [
#         "PoseTrackingViewController.h",
#     ],
#     copts = ["-std=c++17"],
#     data = [
#         "//mediapipe/graphs/pose_tracking:pose_tracking_gpu.binarypb",
#         "//mediapipe/modules/pose_detection:pose_detection.tflite",
#         "//mediapipe/modules/pose_landmark:pose_landmark_full.tflite",
#     ],
#     deps = [
#         "//mediapipe/examples/ios/common:CommonMediaPipeAppLibrary",
#         "//mediapipe/framework/formats:landmark_cc_proto",
#     ] + select({
#         "//mediapipe:ios_i386": [],
#         "//mediapipe:ios_x86_64": [],
#         "//conditions:default": [
#             "//mediapipe/graphs/pose_tracking:pose_tracking_gpu_deps",
#         ],
#     }),
# )

swift_library(
    name = "PoseTrackingGpuSwiftAppLibrary",
    srcs = glob(["src/*.swift"]),
    # copts = ["-std=c++17"],
    data = [
        "Base.lproj/LaunchScreen.storyboard",
        "Base.lproj/Main.storyboard",
        "//mediapipe/graphs/pose_tracking:pose_tracking_gpu.binarypb",
        "//mediapipe/modules/pose_detection:pose_detection.tflite",
        "//mediapipe/modules/pose_landmark:pose_landmark_full.tflite",
    ],
    visibility = [
        "//mediapipe:__subpackages__",
    ],
    deps = [
        "//mediapipe/objc:mediapipe_framework_ios",
        "//mediapipe/objc:mediapipe_input_sources_ios",
        "//mediapipe/objc:mediapipe_layer_renderer",
        "//third_party/apple_frameworks:AVFoundation",
        "//third_party/apple_frameworks:CoreGraphics",
        "//third_party/apple_frameworks:CoreMedia",
        "//third_party/apple_frameworks:UIKit",
        "//mediapipe/framework/formats:landmark_cc_proto",
    ]
    + select({
        "//mediapipe:ios_i386": [],
        "//mediapipe:ios_x86_64": [],
        "//conditions:default": [
           "//mediapipe/graphs/pose_tracking:pose_tracking_gpu_deps",
        ],
    }),
)

filegroup(
    name = "AppIcon",
    srcs = glob(["Assets.xcassets/AppIcon.appiconset/*"]),
    visibility = ["//mediapipe:__subpackages__"],
)

Complete Logs
ld: Undefined symbols:
  _OBJC_CLASS_$_ALAssetsLibrary, referenced from:
       in opencv2[arm64][249](cap_ios_video_camera.o)

The Swift project is just a totally new project and I have not added any codes to it.
If I remove "//mediapipe/graphs/pose_tracking:pose_tracking_gpu_deps" and "@ios_opencv//:OpencvFramework", in deps, it will build successfully. But I need to use the pose tracking graph to implement the Pose function, so please help.
Thanks!

Hi @trunghvbk,
Could you please outline the exact steps you are following, referencing the documentation? Additionally, kindly confirm the macOS version you are using—specifying whether it is based on the Silicon chip or Intel. This information will help us reproduce and better understand the issue on our end.
Thank you

Hi @kuaashish
The steps I'm following:

Pull the latest code from mediapipe repo: https://github.com/google/mediapipe
Create new folder: mediapipe/examples/ios/posetrackinggpuswift
Create a new iOS app project, copy all the file except .xcodeproj file into the folder created above
add BUILD file (attached on description)
Run bazel build command line: bazel build //mediapipe/examples/ios/posetrackinggpuswift:PoseTrackingGpuSwiftApp --ios_multi_cpus=arm64 --xcode_version=15.0

My Macbook is Macbook pro 2020 M1.

@kuaashish  FYI this is the folder structure

Hi @schmidt-sebastian Thanks for your response
I tried using the argument as you said but it appears the ERROR
ERROR: /private/var/tmp/_bazel_admin/dd64d0bbc2d480ced47ba389824ddbde/external/rules_foreign_cc/toolchains/BUILD.bazel:192:11: in ninja_tool rule @rules_foreign_cc//toolchains:ninja_tool:
Traceback (most recent call last):
	File "/private/var/tmp/_bazel_admin/dd64d0bbc2d480ced47ba389824ddbde/external/rules_foreign_cc/foreign_cc/built_tools/ninja_build.bzl", line 16, column 30, in _ninja_tool_impl
		additional_tools = depset(
Error in depset: at index 0 of transitive, got element of type NoneType, want depset
ERROR: /private/var/tmp/_bazel_admin/dd64d0bbc2d480ced47ba389824ddbde/external/rules_foreign_cc/toolchains/BUILD.bazel:192:11: Analysis of target '@rules_foreign_cc//toolchains:ninja_tool' failed
ERROR: Analysis of target '//mediapipe/examples/ios/posetrackinggpuswift:PoseTrackingGpuSwiftApp' failed; build aborted:
INFO: Elapsed time: 58.478s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (226 packages loaded, 28508 target\
s configured)


File explorer shows error under windows

Description
Launching the web IDE on a server running on Windows (without WSL) will show an error in the File Explorer tab.
Steps to reproduce

Start DHE on a windows machine, without docker or WSL. For example, to start from python, see https://deephaven.io/core/docs/tutorials/pip-install/ or https://deephaven.io/core/docs/how-to-guides/jupyter/, etc
Launch the web IDE by navigating to http://localhost:10000/ide/ in a web browser
Switch to the File Explorer tab

Expected results
Files that are available in the notebook directory should be visible.
Actual results

Additional details and attachments
Reported slack thread https://deephavencommunity.slack.com/archives/C036HT73T43/p1705948352845709
Versions

Engine Version: 0.32.0
Web UI Version: 0.59.0
Java Version: 11
Barrage Version: 0.6.0
OS: Windows
Browser: chrome
Docker: n/a

This could also be considered an engine issue. Depends on where we want to normalize the paths. The web UI expects unix paths right now

Yea, I would like to abstract the Web UI away from the actual file system implementation. Why push this issue up to the client?


[BUG]: Polling speed is shown as km/h

Describe the bug.
The polling speed is shown as km/h instead of minutes or seconds
What version of Home Assistant Core has the issue?
2024.10.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
How did you install the stromer integration
HACS
Logging
No response
Diagnostics information
No response
Additional information
No response

Hi @los-cuentos
Not sure what you mean, the scan_interval defaults to 10 minutes (i.e. the time between retrieving data from the API) where the suggestion is to 'trigger' it more frequently by instructing HA to refresh any of the available sensors using an automation. As far as I'm aware there is no 'polling speed' (and/or not sure what you are referring to).

I’m sorry for the misunderstanding. I do have a sensor named: sensor.stromer_speed and it keeps fluctuating between 0km/h and 2,5km/h even when the bike is stalled. Though it was the polling speed as u named a similar sensor in the discription to adjust the polling frequency

I'll have a look if/why that sensor is there that way, but you should have a normal speed sensor, right?

Yes I do have another speed sensor which is the speed of the bike.


jitsu logs delay

It seems that there's a delay when requesting the logs (jitsu logs) for an app, as if there's an unknown time before they populate new logs. Is this a known bug? or si there a set time before new logs will be available to jitsu logs. It tends to get hairy trying to debug something when it breaks only to check the logs and see no sign of the error.
regards
Chris

How much of a delay?  Your log messages go from our servers to loggly for storage - likely quite a few network hops - and then your jitsu logs command has to make the same number of hops, plus the distance from you to our API, and back again - and that's not counting the amount of time it takes loggly to run a given query, or the time it takes them to store the data and make it available.
We're working on much simpler, faster, no-middleman logs - but for the moment, I think this is primarily a network topology issue.


Unused field in flyweight cpp

SBE Tool v1.7.9
Problem:
Message with only fixed fields contain an attribute in the cpp encoder/encoder called m_positionPtr that is never used. This attribute taking up 8 bytes. We suggest to remove this for optimization.
Given the following schema:
 <types>
 <enum name="EnumSBESample" encodingType="uint8" semanticType="EnumSBESample">
 <validValue name="a">0</validValue>
 <validValue name="b">1</validValue>
 </enum>
 </types>

<sbe:message name="MsgSBESample" id="1023" semanticType="MsgSBESample">
 <field name="fieldConstant" id="1" type="EnumSBESample" presence="constant" semanticType="EnumSBESample" valueRef="EnumSBESample.a" />
 </sbe:message>

Remove   std::uint64_t *m_positionPtr; that is not being read in the flyweight
class MsgSBESample
 {
 private:
 char *m_buffer;
 std::uint64_t m_bufferLength;
 std::uint64_t *m_positionPtr;
 std::uint64_t m_offset;
 std::uint64_t m_position;
 std::uint64_t m_actingBlockLength;
 std::uint64_t m_actingVersion;

inline void reset(
 char *buffer, const std::uint64_t offset, const std::uint64_t bufferLength,
 const std::uint64_t actingBlockLength, const std::uint64_t actingVersion)
{ m_buffer = buffer; m_offset = offset; m_bufferLength = bufferLength; m_actingBlockLength = actingBlockLength; m_actingVersion = actingVersion; *m_positionPtr = &m_position;* position(offset + m_actingBlockLength); }
inline void reset(const MsgSBESample& codec)
{ m_buffer = codec.m_buffer; m_offset = codec.m_offset; m_bufferLength = codec.m_bufferLength; m_actingBlockLength = codec.m_actingBlockLength; m_actingVersion = codec.m_actingVersion; m_positionPtr = &m_position; m_position = codec.m_position; }

Flyweights are by their nature used to flyweight over many other objects. This means that you typically only need one per thread per message type. If repeating groups, or var data, is used in a message then the m_positionPtr is required. This feels like an optimisation that would provide negligible benefit. Can you highlight where this optimisation would provide noticeable benefit?

The low latency app that raised this issue seeks to eliminate all non-essential fields
for message with only fixed fields

That does not count as evidence that the effort to support this would make a noticeable difference. :-)

Closing as effort to address this is not likely to produce noticeable benefit yet would introduce complexity that may cause new issues.

Having looked at this some more, if the goal is to save on space, then a bigger win would be to adjust the types so that smaller types, e.g. for acting version and block length, could be used instead of only using the largest possible type in all cases.


Delete font-mononoki.rb

Dead link.

Merged as 6bda879cf511d177e536e36faf45f27674e585ad.

Any way to add this back? The link isn't dead anymore as far as I can tell.

Any way to add this back?

Submit a PR.


[Auto-generated] Check & update dependencies (pyproject.toml)

Update dependencies (pyproject.toml)
Automatically created PR based on the 'CI - Check pyproject.toml dependencies' workflow in SINTEF/ci-cd.

Codecov Report

:exclamation: No coverage uploaded for pull request base (ci/dependency-updates@20358f7). Click here to learn what that means.
The diff coverage is n/a.

@@                   Coverage Diff                    @@
##             ci/dependency-updates     #121   +/-   ##
========================================================
  Coverage                         ?   76.19%
========================================================
  Files                            ?       15
  Lines                            ?      605
  Branches                         ?        0
========================================================
  Hits                             ?      461
  Misses                           ?      144
  Partials                         ?        0

Flag
Coverage Δ

linux
76.19% <0.00%> (?)

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


Invalid formating for conditional compilation rule

Formatter v0.8.6 prodices invalid outup for multiargument  conditional compilation rule
Resulting code doesn't compile
Expected:
/// Default path (*nix) #[cfg(all(unix, not(target_os = "macos") , not(target_os = "ios"),             not(target_os = "android")))]
Received:
/// Default path (*nix) #[cfg(all(unix, not(target_os = "macos") ), not(target_os = "ios") ),             not(target_os = "android")))]

I have got similar problems. Rustfmt is doing something weird with #[cfg()] and #[cfg_attr()].
Example with #[cfg()]:
#[cfg(target_os = "freertos")]
match port_id {
    'a' | 'A' => GpioPort { port_address: GPIO_A },
    'b' | 'B' => GpioPort { port_address: GPIO_B },
    _ => panic!(),
}

becomes
#[cfg(target_os = "freertos")]    #[cfg(target_os = "freertos")]
    #[cfg(target_os = "freertos")] match port_id {
         'a' | 'A' => GpioPort { port_address: GPIO_A },
         'b' | 'B' => GpioPort { port_address: GPIO_B },
         _ => panic!(),
    }

Example with #[cfg_attr()]:
#[cfg_attr(not(target_os = "freertos"), allow(unused_variables))]

becomes
#[cfg_attr(not(target_os = "freertos") /* ) /* ) */, allow(unused_variables))]

Thanks for raising this issue. Looks like the span from ast::NestedMetaItem does not contain the closing paren and rustfmt inserts it for recovery.

Similar problems from me as well.
#[cfg(all(not(test), target_os = "macos"))]

becomes
#[cfg(all(not(test) ), target_os = "macos"))]

@mjfeller Thanks, this is fixed via #1669.


substitute rescale to rescaledata?

Error using rescale
Too many output arguments.
Error in esfit>runFitting (line 478)
[fit,scale] = rescale(fitraw,fitdat.data,fitdat.FitOpts.Scaling);
Error in esfit (line 373)
result = runFitting();

This is now implemented for v6.0 with 3a79b9a864e8a18dd55b9ce4efaa45b3351b0195, see also #209.


reported document scores are switched

It appears that when I compare two documents the scores are switched. Here are some screenshots:

"vitrin önü" is an exact match, so it should have a score of 1.00.

The sentence that contains "lütfen", which is in the reference, should have the higher score.

Huh. Pretty sure this is not the case in general. In fact, the demo YouTube
video shows that it works fine.
However, the difference here is that you are text files for both hypotheses
files. And your target language is not English. Perhaps this causes some
problems. I'll check it out tomorrow.
On Thu, Oct 15, 2015 at 03:08 Nathan Glenn<EMAIL_ADDRESS>wrote:

It appears that when I compare two documents the scores are switched. Here
are some screenshots:
[image: 1]
https://cloud.githubusercontent.com/assets/778453/10506809/935b7fea-7356-11e5-8b98-fcca819d5544.PNG
"vitrin önü" is an exact match, so it should have a score of 1.00.
[image: 2]
https://cloud.githubusercontent.com/assets/778453/10506812/99cfcc28-7356-11e5-9bf4-382aa14add8d.PNG
The sentence that contains "lütfen", which is in the reference, should
have the higher score.
—
Reply to this email directly or view it on GitHub
https://github.com/desilinguist/ibleu/issues/4.

Hmm, I didn't have the Chinese source but when I copied and pasted the hypothesis and references that you have in your first screenshot, I don't see any problems.

Hmm, yeah, when I tried it today I couldn't get this bug to come up. There must be some steps to reproduce. I'll tell you if I figure them out.

Yeah, I was thinking about this. May be if you trigger the second file
button to open but instead put the first file there and the second file in
the first file button? Not sure.
I'll try this later.
Thanks.
On Fri, Oct 16, 2015 at 3:05 AM Nathan Glenn<EMAIL_ADDRESS>wrote:

Hmm, yeah, when I tried it today I couldn't get this bug to come up. There
must be some steps to reproduce. I'll tell you if I figure them out.
—
Reply to this email directly or view it on GitHub
https://github.com/desilinguist/ibleu/issues/4#issuecomment-148633563.

I am going to close this for now since there's been no activity.


feat: Draft Add sections framework

This PR contains a first draft on sections level.
The structure given considers the section (for now only the generic section has been implemented) object that contains a combination of geometries (e.g. surfaces, points) and materials (constitutive relation). The section calculator is the object implementing the different computation algorithms. The integrator object is the one necessary for doing the integration of stresses in the section: two integrators have been implemented, Marin (default) and Fibre integration. The results are stored as proper dataclasses.
The implementation relys on shapely package.
Some limited usecase examples are reported.

Importing the necessary functions

from structuralcodes.materials.constitutive_laws import ParabolaRectangle, ElasticPlastic
from structuralcodes.sections._generic import GenericSection
from structuralcodes.sections._geometry import add_reinforcement, add_reinforcement_line, SurfaceGeometry
from shapely import Polygon

Creating constitutive law objects (note: the section framework supports both constitutive laws or material classes from where the constitutive law is available)

matC = ParabolaRectangle(30)
matS = ElasticPlastic(210000, 410)

Create a rectangular section with some reinforcement

rect = Polygon(((-100,-250),(100,-250),(100,250),(-100,250)))
geo = SurfaceGeometry(rect, matC)
geo = add_reinforcement(geo, (-60, 210), 16, matS)
geo = add_reinforcement(geo, (60, 210), 16, matS)

The output is the following:

Different ways of adding reinforcement:
Specifying a line and a number of reinforcements (spacing is automatically computed):

add_reinforcement_line(geo, (-60,-210), (60,-210), 16, matS, n = 4)

Specifying a line and the spacing of bars (number is automatically computed):
add_reinforcement_line(geo, (-60,-210), (60,-210), 16, matS, s = 30)

The function can be also nested
geo = add_reinforcement_line(
    add_reinforcement_line(geo, (-60, -210), (60, -210), 16, matS, n = 2),
    (-60,-210),
    (60,-210),
    8,
    matS,
    s = 20,
    first = False,
    last = False
)

Also, both spacing and number can be given:
add_reinforcement_line(
    add_reinforcement_line(geo, (60, -210), (60, 210), 12, matS, n = 2, s = 100),
    (-60, -210),
    (-60, 210),
    12,
    matS,
    n = 2,
    s = 100
)

5. Translate and other editing are included
geo = geo.translate(-100,-100)

Create the section (if integrator is not specified, Marin integration is used)

sec = GenericSection(geo, 'mySection', integrator = 'Fiber')

Compute gross properties (e.g. Area)

print(sec.gross_properties.area)

Compute bending strength

res = sec.section_analyzer.calculate_bending_strength(theta = 0, n = 0)
print(res.m_x)

Compute moment Curvature

res = sec.section_analyzer.calculate_moment_curvature(theta=0, n=0)
import matplotlib.pyplot as plt
plt.plot(res.chi, -res.my)

Analyze a steel section (like I-shaped)

fyk = 355
Es = 206000
Eh = 0.0
eps_su = 10.0e-2 #plastic strength
eps_su = fyk / Es #elastic strength

# H section
h = 300
b = 150
tf = 10.7
tw = 7.1
steel = ElasticPlastic(E=Es, fy=fyk, Eh=Eh, eps_su=eps_su)
# Geometry
sec_geom = Polygon(
    (
        (-b/2, -h/2),
        (b/2, -h/2),
        (b/2, -h/2+tf),
        (tw/2, -h/2+tf),
        (tw/2, h/2 - tf),
        (b/2, h/2-tf),
        (b/2, h/2),
        (-b/2, h/2),
        (-b/2, h/2 - tf),
        (-tw/2, h/2 - tf),
        (-tw/2, -h/2 + tf),
        (-b/2, -h/2 + tf),
    )
)
# Trick: create a CompundGeometry with just one SurfaceGeometry to make algorithms work
geo = CompoundGeometry([SurfaceGeometry(sec_geom, steel)])
# Section
sec = GenericSection(geo)

res_fiber = sec.section_analyzer.calculate_bending_strength(theta=0, n=0)
print(f'Mx = {res_fiber.m_x * 1e-6:.2f} kNm')
# Expected bending strength
J = 2/12 * (b * tf**3) + 2 * (tf*b) * (h/2-tf/2)**2 + 1/12 * (tw * (h-2*tf)**3)
W = J/(h/2)
print(f'Expected Mx,el = {fyk * W * 1e-6:.2f} kNm')
Wpl = 2 * (tf * b * (h/2 - tf/2) + (h/2-tf) * tw * (h/2-tf)/2)
print(f'Expected Mx,pl = {fyk * Wpl * 1e-6:.2f} kNm')

I've commented all your comments.
Almost everything is done, except some minor things that will be done later.

[ ] Drop functools.cache for version 3.8

@mortenengen in 3.8 tests fail because of cache not being found in module functool. Can you please assist me with this?

@mortenengen in 3.8 tests fail because of cache not being found in module functool. Can you please assist me with this?

Fixed in 6d8521d 😃

@mortenengen with 9a9d2c7 I included several tests on steel structures with I section. I have a problem: with parametrize if I un-comment more than 2-3 lines for possible testing the make test freezes.. I don't know if this a memory limit for my PC. Any suggestion?

@mortenengen with 9a9d2c7 I included several tests on steel structures with I section. I have a problem: with parametrize if I un-comment more than 2-3 lines for possible testing the make test freezes.. I don't know if this a memory limit for my PC. Any suggestion?

This was a strange one. There were tests that were either failing or freezing, and it was due to polygons that were joined through unions, but were still disconnected. Taking the union of disconnected geometries produces MultiPolygon and not Polygon, and therefore, the constructor of SurfaceGeometry raised a TypeError. I used the set_precision function from shapely to set the precision of the geometries to a very low number, and this made the tests pass 😃

In 1d64e13 I added constitutive laws to the Reinforcement class and swapped the ElasticPlastic objects with ReinforcementMC2010 in relevant tests.


test title

@lydhr
It's very easy to make some words bold and other words italic with Markdown. You can even link to Google!
Emphasis
This text will be italic
This will also be italic
This text will be bold
This will also be bold
You   can  combine them
Lists
Unordered

Item 1
Item 2

Item 2a
Item 2b
Ordered

Item 1
Item 2
Item 3

Item 3a
Item 3b
Images

Format:
Links
http://github.com - automatic!
GitHub
Blockquotes
As Kanye West said:

We're living the future so
the present is our past.
Inline code

I think you should use an
<addr> element here instead.

test

?


Error when opening notebook files in tests

I have written an extension that automatically opens a notebook file.  The relevant code for that is below:
const p = path.join(__dirname, "simple-notebook.ipynb");

const u = vscode.Uri.file(p);
const nb = await vscode.workspace.openNotebookDocument(u);
await vscode.window.showNotebookDocument(nb);

When I run the extension in debug mode, this works just fine.  When I try to test this logic via the API, the following error occurs:
Error: Notebook Editor creation failure for document {"$mid":1,"external":"file:///c%3A/Users/.../simple-notebook.ipynb","path":"/c:/Users/.../simple-notebook.ipynb","scheme":"file"}

It's just an empty notebook.  I also tried adding a single import line import re, but the issue still persists


Visual Studio should not recommend the System.Data.SqlClient for dotnet 6 projects

Is your feature request related to a problem? Please describe.
While building new code I would like Visual Studio to help me resolve references. When I build a new dotnet 6 console application that references SqlConnection it suggests System.Data.SqlClient
Describe the solution you'd like
I would like Visual Studio to guide me to choosing the Microsoft.Data.SqlClient package
Describe alternatives you've considered
I can manually install the package at this time
Additional context
I was trying to use the newer managed identity connection string features in my project and received the error "Keyword not supported". It would have been nice if that package returned an error saying it didn't support the new managed identity connection strings. I'm not sure if that's a separate issue I should open but the way I resolved the error was to import the correct package.

Hi @KSchlobohm,
This query is already running under #1063 thread. You can join the discussion.
Feel free to reopen this issue if you find that unrelated.


NC_ELATEFILL is not being called for classic files. Should it be?

Currently the library allows me to write a var in a classic file, and then change the fill value.
I had thought I would get an NC_ELATEFILL, but I don't. Is this a bug or intentional?
Here's the code:
      printf("**** testing simple fill value attribute creation...");
      {
         int status;
         int schar_data = 0;
         size_t index[1] = {0};
         int dimid;

         /* Create a netcdf-4 file with one scalar var. Add fill
          * value. */
         if (nc_create(FILE_NAME2, cmode, &ncid)) ERR;
         if (nc_def_dim(ncid, VAR_NAME, TEST_VAL_42, &dimid)) ERR;
         if (nc_def_var(ncid, VAR_NAME, NC_BYTE, 1, &dimid, &varid)) ERR;
         if (nc_put_att_schar(ncid, varid, _FillValue, NC_BYTE, 1, &fill_value)) ERR;
         if (nc_enddef(ncid)) ERR;
         if (nc_put_var1(ncid, varid, index, &schar_data)) ERR;
         if (nc_redef(ncid)) ERR;
         status = nc_put_att_schar(ncid, varid, _FillValue, NC_BYTE, 1, &fill_value_2);
         if (status != NC_ELATEFILL)
             printf("Error at line %d: expecting NC_ELATEFILL but got %s\n",__LINE__,nc_strerror(status));
         if (nc_close(ncid)) ERR;

Here's the final output. Note that the fill value is shown as 2, but it was 42 when the data were written.
netcdf tst_vars2_latefill {
dimensions:
	Battle_of_Marathon = 42 ;
variables:
	byte Battle_of_Marathon(Battle_of_Marathon) ;
		Battle_of_Marathon:_FillValue = 2b ;
data:

 Battle_of_Marathon = 0, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42,
    42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42, 42,
    42, 42, 42, 42, 42, 42, 42, 42, 42, 42 ;
}

In attr.m4, I see the following code commented out:
//    if (varid != NC_GLOBAL && !strcmp(name, _FillValue)) {
//        /* Fill value must be of the same data type */
//        if (type != ncp->vars.value[varid]->type) return NC_EBADTYPE;
//
//        /* Fill value must have exactly one value */
//        if (nelems != 1) return NC_EINVAL;
//
//        /* Only allow for variables defined in initial define mode */
//        if (ncp->old != NULL && varid < ncp->old->vars.nelems)
//            return NC_ELATEFILL; /* try put attribute for an old variable */
//    }

This was done in this commit:
https://github.com/Unidata/netcdf-c/commit/faf1470887f2526e1f0db26ce46ef34f77a81c05
@WardF do you know why fill value checking was turned off?

Tagging @wkliao because he contributed the now-commented code in attr.m4.

@WardF has decided not to enforce that rule anymore (for classic files only), to avoid breaking existing workflows. See #843

OK, awesome. I will modify the test to reflect this.


Prevent VS crashes when O# fails to properly read/write to JsonRpc streams.

O# doesn't try/catch around their reading/writing flow so if our reading/writing throws it will crash VS. This is properly solved in the latest O# but for now to mitigate VS issues we're going to swallow all exceptions introduced by our stream wrapper. This may effectively corrupt the Razor scenario and leak memory but it helps mitigate the crashes until we can land the proper fix.

Fixes dotnet/aspnetcore#25116

Do the tests need to be updated (just to pass CI)?

Why would they fail?

Do the tests need to be updated (just to pass CI)?

Why would they fail?

Nevermind, yeah I don't see how these would cause it to fail.
https://github.com/dotnet/aspnetcore-tooling/blob/master/src/Razor/test/Microsoft.VisualStudio.LanguageServerClient.Razor.Test/AutoFlushingNerdbankStreamTest.cs#L14


Restore storybook-addon-links

What happened

We consolidated all packages into the monorepo
We marked all of the original package repos as deprecated
https://github.com/storybooks/storybook-addon-links did not get transitioned to the monorepo
I read a stale PR and assessed that addon-links was deprecated
I started to remove addon-links from the docs and from the code, e.g. https://github.com/storybooks/storybook/issues/1015

However, now as far as I can tell, the only problem was that addon-links was not properly ported to the monorepo.
What needs to happen

[ ] addon-links ported to monorepo and tested
[ ] documentation updated to refer to addon-links as a standalone package
[ ] "built-in" actions and linkTo API should be deprecated (with 3.0?)

Version 3.0 is a good time to remove actions and linkTo APIs from core. But let's add a warning log in when using these APIs and make sure it continues to work for now. It'll be no longer supported from v3.0 and we can remove it completely at a later version. What do you think?

I should merge https://github.com/storybooks/storybook-addon-links into the monorepo?


feat(SingleSelectExample): Gathered single select with server select

…and removed building block examples
Proposed Changes
Gathered the Single Select and the server side Single Select in the same example file.
Removed the example that are related to building blocs and are not to use directly in the admin.
As the design system matures, we eventually will make a section for the Admin UI developers with all our building blocs.
Potential Breaking Changes
Only affect the demo
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1389      +/-   ##
==========================================
+ Coverage   99.23%   99.23%   +<.01%
==========================================
  Files         476      476
  Lines        9955     9963       +8
  Branches     2278     2281       +3
==========================================
+ Hits         9879     9887       +8
  Misses         76       76

Impacted Files
Coverage Δ

...t-vapor/src/components/tables/TableDataModifier.ts
100% <0%> (ø)
:arrow_up:

packages/react-vapor/src/components/drop/Drop.tsx
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix(learn): avoid learn use DEFAULT_POOL

FLAGS_max_copy_rate_megabytes_per_disk will use sleep_for function to block THREAD_POOL_DEFAULT. It's cause replica server cannot deal remote command. This modify is same as FLAGS_max_send_rate_megabytes_per_disk, only use THREAD_POOL_BLOCK_SERVICE to sleep.
What problem does this PR solve?
relate issue:https://github.com/apache/incubator-pegasus/issues/1969
avoid learn use DEFAULT_POOL.

Manual test (add detailed scripts or steps below)

Before fix, many partitions ballot increase, and remote_command cannot get response.
0     6       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:55000]
1     7       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:50001]
2     5       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:00001]
3     9       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:00001]

After fix, return to normal.
0     0       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:55000]
1     0       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:50001]
2     0       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:00001]
3     0       3/3            <IP_ADDRESS>:00001  [<IP_ADDRESS>:55101,<IP_ADDRESS>:00001]

@ruojieranyishen Thanks for the contribution!
Please fix the CI errors.


[9.x] Discover anonymous Blade components in other folders

Do you like anonymous components? (I like them a lot) And did you ever want to also 'enable' anonymous components for directories other than resources/views/components?
For example, resources/views/admin and resources/view/frontend? And autodiscover the components like <x-admin::component.name?
This PR introduces exactly that. It allows the developer to register a directory and a prefix, which would allow to use the files in those directories as anonymous components. This would get rid of things like @include and provide developers with the ability to use the attribute bag everywhere.
Example
In your service provider, you can register the directories you want to enable discovery for:
// Folder: resources/views/admin and prefix <x-admin::your.component>
Blade::anonymousComponentNamespace('admin', 'admin');

// Folder: resources/views/frontend and prefix <x-public::your.component>
Blade::anonymousComponentNamespace('frontend', 'public');

Now you can use this in your Blade files like this:
<!-- Looks for resources/views/admin/dashboard/widget.blade.php OR resources/views/admin/dashboard/widget/index.blade.php -->
<x-admin::dashboard.widget>

<!-- Looks for resources/views/frontend/auth/login/form.blade.php OR resources/views/frontend/auth/login/form/index.blade.php -->
<x-public::auth.login.form>

I added some additional inline comments to the compiler-file just for clarity, but feel free to trim this down however you want.
I took inspiration from the original PR that introduced anonymous components (#31363). I'm a slightly unsure how this should be tested, perhaps @driesvints could give me a hint?
This is a feature I wanted for a long time and I hope this will be useful to many developers! The syntax is in line with package components.

Do you have the ability to write tests for this?

@taylorotwell Yes, if you're okay with the idea.

I just added test coverage for this and applied the code style!

I think one thing that gives me pause about this how it behaves when used via a package.
I could see package maintainer's using anonymous components and wanting to use this feature, but how would they use it? It seems to always assume the "directory" is a dot path relative to the application's main view directory.

Thanks!
I decided to swap the order of directory and prefix - I felt that was a bit more consistent with the componentNamespace method which accepts "location" first and then "prefix".


Validating server cert when endpoint protected with client cert

Is your feature request related to a problem? Please describe.
The way ACME works to validate a server certificate is to access it from Let's Encrypt. In case the ingress is also protected with mutual TLS (client certificate), how could ACME validate (and hence: renew) the server certificate?
Are you aware of any workaround?
/kind feature

This is not possible - ACME requires the webserver to listen on port 80 for regular HTTP requests. If you want to protect your public facing endpoint with a client certificate, you'll need to use DNS01 validation or something similar to obtain your certificate from Let's Encrypt.


Error when trying to import sql file

After the last update, I can't import from sql files.
At the first attempt, the import gets blocked.
After aborting and retrying, the following error appear:

TypeError: Cannot destructure property 'status' of '(intermediate value)' as it is undefined. at Proxy.startImport (file:///snap/antares/500/opt/Antares/resources/app.asar/dist/renderer.js:1:2949343)

OS: Ubuntu 22.04
Antares version: 0.7.1
Client: MySql

Hi @mihaiphilip,
it happens on every import you tried?
Can you provide me an sql file that triggers this issue?
Thanks.

This problem seems to occur if you cancel the first import process and try again.

I am no longer able to replicate the error conditions after updating electron.
Are you able to tell me if you experience this problem even after the latest update?


dovecot: allow sasl_bind=yes in the LDAP driver.

Dovecot has its own SASL implementation,
but needs Cyrus SASL's headers to bind to an LDAP server using SASL.
This is useful to avoid the need to manage a dnpass= in dovecot-ldap.conf
by using the Unix socket to authenticate.
This is done with sasl_mech=EXTERNAL in dovecot-ldap.conf, and some olcAccess: with
 by dn="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" read
in the slapd's cn=config for the LDAP DN queried by dovecot/auth (which runs as root).
Motivation for this change
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
[ ] 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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

Note that I'm not sure if I'm correctly adding to the CFLAGS, it may be an overriding, I don't know.

Thank you @Mic92, I didn't know that the C wrapper was already adding the right include flag. I've tested and updated a simplified commit.


[Feature]1.2.3 Email alerts - Subscription confirmation

Trello card URL:
https://trello.com/c/naFQHYhF/659-123-email-alerts-subscription-confirmation
Changes in this PR:
Adds subcsription confirmation page

 1.2.3 Email alerts: Subscription confirmation

@lozette arg I was expecting this given the changes I had to make to the other branches. Update coming soon!


SP_PROXYSOCKETENDPOINTFILEMODE is being ignored

Describe the bug
SP_PROXYSOCKETENDPOINTFILEMODE is being ignored
To Reproduce
Steps to reproduce the behavior:

Set SP_PROXYSOCKETENDPOINTFILEMODE to anything other than 0400
Check the logs

Expected behavior
File mode is set to the defined value

Thanks for reporting the bug and fixing this issue!


Is there a plan to support chunking?

If this question is related to build, please include version of Bazel that you are running J2CL with:
Build label: 0.27.0
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Jun 17 13:03:58 2019<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

I'm wondering if J2CL plans to support JS chunking? We are very happy with J2CL so far. But, if we want to build a large application and serve it efficiently, we're worried about packaging everything up in one JS target.
Surely Gmail, Calendar, and the other examples cited, must have some wiring for chunking built in. Just curious if there is a plan or ideas to do this with J2CL.

"Bundling" is not done by J2Cl, but by the Closure Compiler (or anything else that's compatible with Closure's way of loading modules).

@tbroyer, yes, indeed. however, Closure Compiler won't "chunk" (bundling is another term) without proper invocation.
i know there is a CLI interface for defining chunk boundaries, and optimization passes specific to chunking. however, i do not think J2CL is equipped to invoke Closure this way.

@gkdn okay but do you care if users want it? i'm currently the author of a proposal to bring this to Rules Closure. it would be useful to keep this issue open to track how it might be adopted in J2CL
https://docs.google.com/document/d/1LxcJhpv5YEWAO28SiFYdKavIkSno4I4rY8UX3w_krKg
we can't really adopt J2CL without some form of chunking (it's not bundling because we're splitting code here, this is the terminology the compiler uses).

I closed the issue because it was a question.
Internally, our users didn't need anything beyond the chunking provided by the underlying closure rules. However internally, we didn't provide a j2cl_application rule as well (since most users didn't need such a bootstrap).
Anyway; if we need to update j2cl_application rule to adapt chunking, that's not a problem. We will be happy to do that.


Some little fixes for ffmpeg 4.x

Hi,
Testing your code, I had to fix some build breakages on Linux, do to the use of old ffmpeg API.
Attached, the diff. Everything is under MIT License. Feel free to use my changes ... or not.
Last, I got an important question : before to propose fixes for other issues, I'd like to know the license you are using for this project ?
Thanks in advance for sharing your code, and for your answer :-)
Eric Bachard
muxer_jerett.diff.txt

Hi,
I have updated the project using FFmpeg4.* API, and applied your patch with some modifications.
The project is under MIT License, feel free to use.
Thank you for your feedback.

Thanks a lot for your great reactivity, and for the other changes.
MIT license is perfect for me. Of course,  if I use your code (for further information, please have a look at  : https://framagit.org/ericb/miniDart ), I'll explain from where it comes + add a link pointing to this repository, and I'll inform you (e.g. adding a comment on this issue).
Regards,
Eric Bachard


GLAD dataset adapter

Part of #53.
Can be adapted from clouddrift-examples/data/glad.py into clouddrift/adapters.py.

So will we have also gdp, gdp6h, parcels etc adapters?

Yes, and anything else that we want and that our users ask for, assuming it's in scope.

The main class of the package is designed to be used with any datasets. Look at the example notebooks here, https://github.com/Cloud-Drift/clouddrift-examples/tree/main/notebooks, in particular I think the numerical data could be adapted to your needs!
Happy to help if you have any questions.

Thanks @miniufo for your interest and ideas. To clarify the RaggedArray class is an intermediate data structure used internally to go from custom data formats -> xr.Dataset. It's not intended for use in analysis, and instead we define our Lagrangian analysis functions on the ragged array xr.Dataset. You're correct that TC tracks (and intensity and other vortex properties) are essentially Lagrangian and fit here very well.
You're welcome to use clouddrift's RaggedArray as a dependency in your library to make adapters for HURDAT2 and/or IBTracs or others.
Alternatively, we can also implement these adapters directly in clouddrift; we could work on that together if you'd like.

@philippemiron Thanks for pointing me to the notebooks.  I've spent some times trying with the RaggedArray data structure.  Now I see that it is a internal thing, as mentioned by @milancurcic, and the output xr.Dataset is the key data structure users play with.
I feel a little confused why we need a internal RaggedArray?  All the lagrangian dataset are stored as a txt file could easily be handled by pandas.  I think pandas can play a similar role as RaggedArray and help rearrange the data into a xr.Dataset.  If this is the case, I may skip the dependence of RaggedArray and rely on pandas to rearrange the raw data as a xr.Dataset as you guys designed here.
Just try to understand your design.  I do like to help if I can.

@philippemiron Thanks for pointing me to the notebooks.  I've spent some times trying with the RaggedArray data structure.  Now I see that it is a internal thing, as mentioned by @milancurcic, and the output xr.Dataset is the key data structure users play with.

This is correct. Most of the analysis functions are based on xr.Dataset (some also supports pd.Series or np.array).

I feel a little confused why we need a internal RaggedArray?  All the lagrangian dataset are stored as a txt file could easily be handled by pandas.  I think pandas can play a similar role as RaggedArray and help rearrange the data into a xr.Dataset.  If this is the case, I may skip the dependence of RaggedArray and rely on pandas to rearrange the raw data as a xr.Dataset as you guys designed here.

The idea of the RaggedArray class is to simplify this conversion. You can of course generate the ragged array yourself and use clouddrift analysis function afterwards.
In your case, if I understand correctly, you can probably just reshape the data, and create a RaggedArray object in a few lines. As Milan said, we could help you generate this, it should be easy considering it's a single .txt file.
Once you have this object, there are functions to easily convert to either an xr.Dataset, an Awkward Array, or output to a NetCDF or a parquet file.

Just try to understand your design.  I do like to help if I can.

I haven't found a way to download the dataset (https://data.gulfresearchinitiative.org/data/R1.x134.073:0004) from the code. This is because there is no static dataset URL, but instead it's resolved dynamically via JavaScript (and quite likely server calls). We have a few options:

Instruct the user to download the dataset to the local file system before running the adapter;
Upload a copy of the dataset to S3 or some static source. I've used GitHub issues as file storage (you attach a file to a blank issue, close the issue, and you get a static URL to the file; however, this works for < 25MB; GLAD is 150MB)

2 would allow for a better user experience. Since the dataset is DOI'd and finalized, we could serve a copy from a place we control without worry that the upstream dataset may change. @selipot do we have an S3 bucket for the project that we could use?

We do not have a bucket but we could create one. We need to figure out the cost?

S3 Standard is $0.023 per GB, so for GLAD that would be $0.00345 per download, or 290 downloads per $1.

I now see that @philippemiron already had extracted a static URL from the backend in the GLAD example notebook. I'll check that it still works and we'll just use that if so.

It works; all good.

I think I looked at the Developer tools -> Network tabs at the time to find this direct link...! Glad to see it still works!

@philippemiron that's smart, I haven't thought of that, only looked in page source. :)


Bump tmpl from 1.0.4 to 1.0.5 in /demo/graph-tutorial

Bumps tmpl from 1.0.4 to 1.0.5.

Release notes
Commits

updated-dependencies:

dependency-name: tmpl
dependency-type: indirect
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

Closing as duplicate of #91. Thanks for your contribution!


Kafka Broker doesn't restart on reboot

Describe the issue
The confluent.kafka_broker role triggers a handler to start the kafka-broker, but it never does an "enabled: true".  I was setting it up with 5.5.0, but it looks like it's similar not enabled in default.  If there is no expectation that the broker is enabled, perhaps an "enabled: false" and/or a comment about it?  Or a configurable in the all.yml?
To Reproduce
Set up a kafka broker cluster and reboot members.
Expected behaviour
Kafka broker comes up after a power outage or reboot.
Environment (please complete the following information):

OS: ubuntu 18.04
CP-Ansible Branch: 5.5.0-post, default
Ansible Version Ansible 2.9.2 and 2.9.9

Wow that is a nice catch! There should be an enabled: true there, all the other components have it

resolved with this pr: https://github.com/confluentinc/cp-ansible/pull/322

Oops, while I was testing my PR, you got this closed.  Thanks, I'll go close the PR!


Make design responsive

Slack + Tight is currently very broken at smaller widths. It would be great if it weren't.
Thanks to Alejandro for pointing this out.

Fixed with v2