Retrive group name

[Enter feedback here]
When we are trying to retrieve the group attributes, we are only getting group ids......... Is there any way we can retrieve group name ?

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

ID: c5a6779a-58f1-73fa-2b24-5f85deeea52b
Version Independent ID: 481c093b-6db3-c4e5-6644-b1a3a4497a30
Content: Configure group claims for applications with Azure Active Directory
Content Source: articles/active-directory/hybrid/how-to-connect-fed-group-claims.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@thadathiljacob Thank you for your query . We will investigate and update the thread.

@thadathiljacob , If you are expecting group names in the claims of ID/Access/SAML token, unfortunately currently that is not supported due to some limitations. You would only have the object ids (guid) of the groups in the claim for AAD managed groups.
If you absolutely need group names for your purpose, consider a separate Graph API call to list group memberships of a user.
Also feel free to upvote on the feature request of group names in claims here.

We will now proceed to close this issue here since this repo is for Azure docs. Please feel free to follow up if you have any question.

Is there any upgrade or newly information for this feature ?

I have the same issue


Changed the Quotes API to a newer better API. Fixed issue #17

Used a better API for better quotes.
As mentioned in issue #17 , the previously used API was quotable.io .
Tried different APIs, most of them were rate limiting, a possible replacement was zenquotes.io , but it was rate limited to 5 quotes per 30 secs.
Finally, went with https://api.api-ninjas.com/v1/quotes , which is an active API without limits.

Hey @devAyushDubey Thanks for Contributing, After testing the API I'll merging it.


Added delegate method didMoveTo to capture the final position, be it …

…from manual gesture or by calling move() programatically.

Thanks for this PR, @victorwon!
We discuss about this feature at https://github.com/SCENEE/FloatingPanel/issues/46#issuecomment-440478635!
I'd like to merge your idea, but I think floatingPanelDidChangePosition  proposed at https://github.com/SCENEE/FloatingPanel/issues/46#issuecomment-438569902 is better than floatingPanelDidMoveTo because the latter is confusing a bit.
Could you please have a look at https://github.com/SCENEE/FloatingPanel/commit/c0647017b5dafb1cfec0fbcb52a490a92dc042c8 whether it achieves what you want?

It looks great, please release asap. Thanks a lot!
On Tue, Nov 20, 2018 at 7:51 PM Shin Yamamoto<EMAIL_ADDRESS>wrote:

Thanks for this PR, @victorwon https://github.com/victorwon!
We discuss about this feature at #46 (comment)
https://github.com/SCENEE/FloatingPanel/issues/46#issuecomment-440478635
!
I'd like to merge your idea, but I think floatingPanelDidChangePosition
proposed at #46 (comment)
https://github.com/SCENEE/FloatingPanel/issues/46#issuecomment-438569902
is better than floatingPanelDidMoveTo because the latter is confusing a
bit.
Could you please have a look at c064701
https://github.com/SCENEE/FloatingPanel/commit/c0647017b5dafb1cfec0fbcb52a490a92dc042c8
whether it achieves what you want?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SCENEE/FloatingPanel/pull/49#issuecomment-440486300,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbj0QmnQw1jJxX0D81bdGRGtV5is69oks5uxKOigaJpZM4YdFFs
.

Thanks, @victorwon! I appreciate it. I will merge the commit and release v1.2.1.


Docs(v2): update snippets/examples to use manifest v2

Note: I'm also seeing manifest snippets in content/cloud which doesn't have a v2 delineation.  What is our strategy/timing for updating these @tpmccallum @itowlson?
(Will continue under content/spin/v2 in the meantime...)

Great question @vdice
@mikkelhegn is going to tackle this in two stages.
Stage 1 is to update manifest examples in /spin/v2/ pages in a separate PR that we can merge now (asap); non-breaking because the v2 files have future publish in frontmatter.
Re: https://www.notion.so/fermyon/Update-Manifests-examples-and-spin-new-examples-in-v2-pages-not-v1-legacy-folder-a1bb35329b9d4863b4f2ec434b71ea9f?pvs=4
Stage 2 is to update manifest examples in /cloud/ pages in a separate PR that we can merge as part of the flip-switch at announcement time < https://www.notion.so/fermyon/Update-Manifests-examples-and-spin-new-examples-in-Cloud-pages-not-v1-legacy-folder-d1e098f24cfe45768aa156b1deb6bbe3?pvs=4 >
The examples in v1 will just remain as is for correctness relative to Spin 1.x


avoid fireing ionChange event twice and fire ionSelect event to be consistant with the remaining select interfaces

Short description of what this resolves:
#11480
Changes proposed in this pull request:

avoid fireing ionChage as it is already fired by button value setter
add handler to SelectPopoverOption
fire input.ionSelect.emit(input.value) instead of  this.ionChange.emit(value) to be consistent with alert and action-sheet

Ionic Version: 3.x
Fixes: #11480

Looks like a good fix! Good job! I will review it today.
BTW, next time, please follow the commit style!
https://github.com/driftyco/ionic/blob/master/.github/CONTRIBUTING.md#commit-message-format
Don't worry with this PR, I can rename it :)

DONE! thanks a lot!


Support parsing the text format in wasmtime crate

This commit adds support to the wasmtime::Module type to parse the
text format. This is often quite convenient to support in testing or
tinkering with the runtime. Additionally the wat parser is pretty
lightweight and easy to add to builds, so it's relatively easy for us to
support as well!
The exact manner that this is now supported comes with a few updates to
the existing API:

A new optional feature of the wasmtime crate, wat, has been added.
This is enabled by default.
The Module::new API now takes impl AsRef<[u8]> instead of just
&[u8], and when the wat feature is enabled it will attempt to
interpret it either as a wasm binary or as the text format. Note that
this check is quite cheap since you just check the first byte.
A Module::from_file API was added as a convenience to parse a file
from disk, allowing error messages for *.wat files on disk to be a
bit nicer.
APIs like Module::new_unchecked and Module::validate remain
unchanged, they require the binary format to be called.

The intention here is to make this as convenient as possible for new
developers of the wasmtime crate. By changing the default behavior
though this has ramifications such as, for example, supporting the text
format implicitly through the C API now.
I'm curious to get others' feedback here on this change, there's naturally a number of variations this could take beyond the one I'm proposing here:

We could not add support at all, the wat crate is "just one Cargo.toml line away" anyway
We could make wat an off-by-default feature
We could add explicit functions to parse *.wat files

I would personally advocate that this proposal, as-is, is the best of all worlds though. @sunfishcode's suggestion of a wat::parse_bytes function which takes either *.wasm or *.wat is perhaps the single-most convenient thing I've seen in a long time, so I think we can get a lot of mileage from enabling this by default in all the typical APIs. If an environment doesn't want the wat parser to be supported, then it's always optional and can be easily disabled without affecting clients too much, since *.wat parsing is likely only used as a convenience.

I like this idea. I'm concerned about enabling functionality in the C API which isn't provided by wasm-c-api.
I'm also concerned about contexts which specifically want to reject the text format -- for example, Web browsers only accept the binary format, and not the text format. The cargo feature helps, but if I understand correctly, cargo features apply globally, so if a program were to pull in say some dependency which used wasmtime for internal sandboxing or so, that could cause the feature to get enabled globally.
How about leaving Module::new as-is, and adding a separate Module::parse or so to provide the text-or-binary interface?

Yeah that was one of the alternatives that I was wondering about, although I think that from an API/ergonomics perspective it'd be best for Module::new to support this. I suspect that a huge majority of users won't care about supporting the text format and/or will want to support it, and it'd be sort of odd if we recomended something other than Module::new to everyone.
I think it'd be best to skew the design towards those users and require those who explicitly want to reject the text format to jump through an extra hoop or two (since I suspect they'll be few and far between). In that sense those users, I believe, can always call validate and new_unchecked themselves. Does that sound like an ok middle ground? I can be sure to at least disable the wat feature for the C API as well.

What about adding this to Module::new as you suggest, and adding a Module::from_binary function, which would be the same except just supporting the binary format?
Then we can make wasm-c-api use Module::from_binary to ensure that it always does that, rather than relying on the cargo feature being left unset by all dependencies in a program.

That sounds good to me yeah, but I'd want to double-check, are we sure we don't want the C API to support this? It seems like a pretty nice feature for extension (like the .NET one) built on the C API to support the text format as well?
It's sort of a question of how far are we ok diverging from the "official" C API (I say "official" because it seems like it was proposed and hasn't really changed since, so I don't get the impression that it's got wide consensus that it's the right API to adopt). Or also do we want to start providing extensions to the C API?


Concatenated cert + CA cert results in key mismatch error.

Error report via jon on #pto:oob.systems:

So I'm trying to set up PTO on one of my servers, and I concatenated my cert and intermediate CA cert together as I would for a web server... but PTO complains of cert/key mismatch. I might have slipped up somewhere, but you should be able to use an intermediate cert like that, right?

Probably needs a call to this somewhere:
http://sfackler.github.io/rust-openssl/doc/v0.7.6/openssl/ssl/struct.SslContext.html#method.set_certificate_chain_file

No worries, was my own mistake... they did in fact not match. XD


Share Extension - [PFUser currentUser] is nil

Hi,
I've tested the previously working Share Extension (using Parse platform) after I migrated to Parse-server. The main/container app is working fine with queries and is still configured as follows:
[Parse enableDataSharingWithApplicationGroupIdentifier:AppGroupId];
[Parse initializeWithConfiguration:[ParseClientConfiguration configurationWithBlock..
So on my share extension I'm still using the same initialization as well except [Parse setApplicationId.. which is changed to Parse initializeWithConfiguration,
[Parse enableDataSharingWithApplicationGroupIdentifier:AppGroupId                                      containingApplication:AppGroupId];     [Parse enableLocalDatastore];
before I set the Parse initializeWithConfiguration...
On the share extension, the [PFUser currentUser] is always nil..
Kindly advise if there are some tweaks need to be done.. Thanks in advance..

Hey @seecahkhing, initializeWithConfiguration: changes everything :stuck_out_tongue:
Now to enable data sharing - you would need to do something like this:
[Parse initializeWithConfiguration:[ParseClientConfiguration configurationWithBlock:^(id<ParseMutableClientConfiguration> configuration) {
  configuration.applicationId = ...;
  configuration.clientKey = ...;
  configuration.localDatastoreEnabled = YES;
  configuration.applicationGroupIdentifier = AppGroupId;
  configuration.containingApplicationBundleIdentifier = AppGroupId; // This goes only in extension
 }];

Which means that any configuration applied directly via Parse class if you use initializeWithConfiguration: is ignored and is superseded by the configuration provided in an object.
Hope this helps, feel free to reopen this issue if it doesn't.

@nlutsenko
Can you please explain how to import parse library to share extension?


fix popup design #159

Thanks for contributing. Your contribution might help someone understand the concepts better.
However, to make sure things are working properly, here's a checklist. Just make sure you check them.

[x] I am reading these checkboxes.
[x] Read contribution guidelines
[x] Screenshots

:+1: LGTM


Update sdx-common version

What? and Why?

What does this pull request change/fix? Why was it necessary?

Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #98 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #98   +/-   ##
=======================================
  Coverage   87.25%   87.25%
=======================================
  Files          17       17
  Lines        1342     1342
=======================================
  Hits         1171     1171
  Misses        171      171

Impacted Files
Coverage Δ

transform/transformers/PDFTransformer.py
77.57% <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 d1e9af7...5db2b8d. Read the comment docs.


Details about ConnectException

What kind of issue is this?

[X] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

I've got a few users that logs ConnectException from okhttp , but the underlying detail is hidden by okhttp implementation.
https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/internal/connection/RealConnection.java#L189
Is there a way to get more details like returning underlying error ?
Most of the time I get proper IOException with details like timeout / refused that help to give clue to the user.
But with this one I have no idea what the root cause can be.

Send a pull request to set the cause?

@swankjesse #2882


Enable etcd-snapshot to use config.yaml flags.

Is your feature request related to a problem? Please describe.

etcd-snapshot is not able to use config.yaml values to store s3 credentials.
Describe the solution you'd like

Enable etcd-snapshot to use config.yaml values.
Describe alternatives you've considered

Additional context

Backporting

[X] Needs backporting to older releases

Validated using commit id d85b2468ea9df3187cb230f503bd41c4cfa0f842
k3s version v1.22.3+k3s-d85b2468


voxelands: 1512.00 -> 1704.00

Motivation for this change
Version update, Repo change URL change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

It fails on aarch64 https://logs.nix.ci/?key=nixos/nixpkgs.104705&attempt_id=ce623944-0fb0-4184-8afb-3211576e4a57
Perhaps it should be marked as broken for this system?

Perhaps it should be marked as broken for this system?

This seems more like a issue with Irrlicht engine on aarch64 - see https://sourceforge.net/p/irrlicht/bugs/443/
So more like anything maybe we should mark irrlicht broken on aarch64 until this is resolved

This seems more like a issue with Irrlicht engine on aarch64 - see sourceforge.net/p/irrlicht/bugs/443 (irrlich thinks the system libpng was compiled with NEON instructions support, but it seems it's not)

Is irrlicht a bundled dependency built within the build of voxeland? Because from the log it seems it's voxeland's build that fails: https://logs.nix.ci/?key=nixos/nixpkgs.104705&attempt_id=ce623944-0fb0-4184-8afb-3211576e4a57

Is irrlicht a bundled dependency built within the build of voxeland?

No. If I see it correctly voxeland uses system irrlicht.

Is irrlicht a bundled dependency built within the build of voxeland?

No. If I see it correctly voxeland uses system irrlicht.

Then if irrlicht was the failing build, the build log wouldn't have looked like this:
[ 99%] Linking CXX executable ../../bin/voxelands-server
[ 99%] Built target voxelands-server
[100%] Linking CXX executable ../../bin/voxelands
/nix/store/liq5wrz3yprc9623bb9lc90qv610gsd8-binutils-2.31.1/bin/ld: /nix/store/ci25cir0pkj8h2dmsaxppdcyqif2m0cb-irrlicht-1.8.4/lib/libIrrlicht.so: undefined reference to `png_init_filter_functions_neon'
collect2: error: ld returned 1 exit status
make[2]: *** [src/CMakeFiles/voxelands.dir/build.make:1370: ../bin/voxelands] Error 1
make[1]: *** [CMakeFiles/Makefile2:186: src/CMakeFiles/voxelands.dir/all] Error 2
make: *** [Makefile:171: all] Error 2
error: --- Error --- nix-build
error: --- Error --- nix-daemon
builder for '/nix/store/9lzw62zdgkzq8jb25xs9yq22ar793q81-voxelands-1704.00.drv' failed with exit code 2; last 10 log lines:
    414 |   for (u8 i = 0; i < 8; i++) {
        |   ^~~
  [ 99%] Linking CXX executable ../../bin/voxelands-server
  [ 99%] Built target voxelands-server
  [100%] Linking CXX executable ../../bin/voxelands
  /nix/store/liq5wrz3yprc9623bb9lc90qv610gsd8-binutils-2.31.1/bin/ld: /nix/store/ci25cir0pkj8h2dmsaxppdcyqif2m0cb-irrlicht-1.8.4/lib/libIrrlicht.so: undefined reference to `png_init_filter_functions_neon'
  collect2: error: ld returned 1 exit status

As you can see, it's voxelands' binaries that fail to link, not irrlicht's. Whatever the reason is, we should mark it as broken for aarch64, ideally with a comment saying the build expects neon symbols or something like that.

we should mark it as broken for aarch64

Addressed in 1ed49e3ea9201a6f932bcbe79e3cc1c32a5f9fc6


multi-GPU Training

Hi, Thank you for sharing the code.
I noticed that there is no code for multi-gpu training in the training code, but evaluation can support multiple gpus. Is there any special reason for this?

no special reason, I just didn't test it out with multiple gpus. if you look at the code there is already some logic to handle distributed training (ie: there's a DistributedSampler being generated), but I haven't really tried it out myself (PRs for any potential fixes needed are welcome!)


Add support for strict DI

This fixes https://github.com/aleross/angular-segment-analytics/issues/16
I have used the same logic as angular to validate the strict DI validation. https://github.com/angular/angular.js/blob/master/src/auto/injector.js#L122-L126

Coverage remained the same at 96.269% when pulling daa7fef86e60ea38d76ef9a5e64fa8f1e3c6b533 on stwiname:master into 2ba0baf2e7c9d9e33e736e68330e9dc18c46ce67 on aleross:master.

Great, thanks @stwiname! I'll review this over the weekend and merge it if everything looks good.


PIA-1443: Split CI workflows [WIP]

This PR splits the CI workflows that run on every pull request into 3 workflows:

1 workflow to build and run the unit tests on iOS and tvOS
1 workflow to build and run the e2e tests on iOS
1 workflow to build and run the e2e tests on tvOS

We have decided to use the following strategy:
https://github.com/pia-foss/mobile-ios/pull/111


Regarding LFattNet_sub

Hello,
I notice that an algorithm called LFattNet_sub was currently submitted to the HCI 4D LF benchmark and achieved top performance. I wonder how the method is modified to achieve such a significant improvement?

Hi,
Thank you for your information!
This is very interesting.......
That is not submitted by our team.
So I do not know why the person who submit that great results using our paper title.........


fix: model name should be set

Interesting, I'm not sure that the string being used as the model name will make sense to the chat completion API - and the endpoint afaik would only be hosting one model anyway 🤔  I'm curious what will happen when this is set though
im also wondering if we could remove that argument entirely instead

/gcbrun


Update dependency

The new version of carbon commons only contains the fix https://github.com/wso2/carbon-commons/pull/423/files

PR builder passed with https://github.com/wso2/product-is/actions/runs/359030865


Provide context for callbacks

An idea from @mkadunc initially posted in https://github.com/Open-EO/openeo-api/issues/160#issuecomment-461024660:

Currently, it is not possible to pass custom values to code inside a callback — right now we pass only those arguments that the outer function (e.g. reduce) declares in the signature of its callback (e.g. dim_data and dimension). If I wanted to use some other variable in the callback (such as a result of a previous computation), I would somehow need to embed its values inside the array.
The following is possible in Javascript, but not in openEO:
const foo = [1,2,3];
const bar = 7;
const fifu = map(a, params =>params.dim_data + bar);

[...]
If we were to solve this problem, I'd consider doing this explicitly, e.g. with a parameter on definition of > custom-callback that one could populate manually in order to provide the "context" into the callback.
E.g. like this:
const fifu = apply_dimensions(cube: a, dimensions: ALL, callback :
   {
      // explicitly specify which local data will be 'injected' into callback
      context: {boo: bar},
      // use only params and context in the callback expression (no access to data outside)
      expression: (params, context) =>params.dim_data + context.boo
   }
);

It is an interesting idea, but it is not clear yet whether this is a feature needed by the community. So I'd leave it out for now and wait for feedback? What do others think?

On the other hand, we have process graph variables anyway (for now only useful for stored process graphs) and could add a set_variable process. It could allow to fill these variables and no context would be needed. But this approach doesn't feel as clean as the contexts. For the context we would need a new process, too. One that composes the context "object" somehow.

Is there anybody who needs this for the use cases? Otherwise I'd vote to move this to 0.5 or later.

We may not need this if the do the change the scoping of parameters as discussed in https://github.com/Open-EO/openeo-api/issues/161#issuecomment-554502184


ClickHouse Grafana plugin leaks credentials to client

Is this still up to date? where did it leak the creds?

Fixed with https://github.com/monogon-dev/NetMeta/commit/2e6ab3ad2bb32fdc128ba6678221d26d4eff399d


Content is missing from the Teams section.  Specifically  Notifications in Teams.   Who do we report this too?

You would report it here, in general but... there is no Notifications in Teams asset in the "Intro to Microsoft Teams" playlist that I see.  Can you please provide the version of the learning pathways solution you're using?

Julie
I apologize.  How can I find out what version of Learning Pathways we are using?
Gerry
From: Julie Turner<EMAIL_ADDRESS>Sent: Tuesday, September 15, 2020 1:54 PM
To: pnp/custom-learning-office-365<EMAIL_ADDRESS>Cc: Hornaday, Gerry<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [pnp/custom-learning-office-365] Content is missing from the Teams section. Specifically Notifications in Teams. Who do we report this too? (#361)
You would report it here, in general but... there is no Notifications in Teams asset in the "Intro to Microsoft Teams" playlist that I see. Can you please provide the version of the learning pathways solution you're using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/pnp/custom-learning-office-365/issues/361#issuecomment-692876998, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQCB6UQYZ3ZOP3UVSVMFEI3SF6S4DANCNFSM4RNOUFAQ.

We are on version <IP_ADDRESS>.   We are currently updating it.  However the assets were there previously.  Did it get removed?
From: Julie Turner<EMAIL_ADDRESS>Sent: Tuesday, September 15, 2020 1:54 PM
To: pnp/custom-learning-office-365<EMAIL_ADDRESS>Cc: Hornaday, Gerry<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [pnp/custom-learning-office-365] Content is missing from the Teams section. Specifically Notifications in Teams. Who do we report this too? (#361)
You would report it here, in general but... there is no Notifications in Teams asset in the "Intro to Microsoft Teams" playlist that I see. Can you please provide the version of the learning pathways solution you're using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/pnp/custom-learning-office-365/issues/361#issuecomment-692876998, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQCB6UQYZ3ZOP3UVSVMFEI3SF6S4DANCNFSM4RNOUFAQ.

FYI, you may want to be careful about responding to email to post your response in GitHub as your personally identifiable information does end up in the body of the issue.

As far as the asset being removed, based on what you showed me it would be more of a matter of the page on support.office.com or docs.microsoft.com as having been removed. That said I did just a quick search and can find no reference to us ever having an asset called "Notification in Teams"... is it possible it was a custom asset?

I'm going to close this due to lack of activity.  If you're still having issues, please feel free to open a new issue and reference this one providing more details.


Add Email copy settings-menu

There's a couple emails that get sent automatically. We should add an Emails settings page as a sub-menu of the RSVP menu item.
It should have Editor screens for each of the emails so SDRT Leadership can change/update the text as they want.

This would be very useful!

@dreazee -- this is already implemented on the site actually. It's a sub-menu of the RSVP menu. See here:


docs: explain optional boolean args in from_native

closes #1420
What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #<issue number>
Closes #<issue number>

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below

Is there a reason to have Nones in the first place? From a user point of view, I think it would be more clear to have boolean defaults 🤔

thanks for your review, and thanks @emilykl for helping us improve the docs, really appreciate this and the other suggestions you made!


Head elements are not wrapped in a Head tag

Subject of the issue
If this utility is run with a Hast-formatted HTML document containing a DocumentType, Head, and Body, the converted HTML is printed with the DocumentType, then the Body, and finally the contents of the Head are spit-out just before the closing Body tag without being wrapped in a Head tag. As a result, the generated HTML is invalid.
Your environment

OS: MacOS Mojave 10.14.6
Packages<EMAIL_ADDRESS>Env: Node v12.4.0, NPM 6.11.3

Steps to reproduce
Provided with a minimal Hast object containing the HTML DocType, Head, and Body elements:
{          type: 'element',          tagName: 'html',          children: [             {                  type: 'element',                  tagName: 'head',                  children: [headContent]             },              {                  type: 'element',                  tagName: 'body',                  children: [bodyContent]             },          ] }
🎉 BONUS POINTS for creating a minimal reproduction and uploading it to GitHub.  This will get you the fastest support.  🎉
Expected behaviour

headContent
bodyContent

Actual behaviour

bodyContent
headContent

What happens instead?
The contents of the Head are not wrapped in a Head tag, and are spit-out just before the closing body tag.

@nwehner can you clarify how the actual behavior is invalid?
Looking at the HTML spec
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/head
https://html.spec.whatwg.org/multipage/semantics.html#the-head-element
It looks like

headContent
bodyContent

would be invalid output.
Only <title>, <link>, <base>,


New "Soundboard" button pushes buttons into 2 rows

The new "Soundboard" button pushes the buttons into 2 rows.

Fixed in 82a59abbde24c52f3b34c5fcbeb27ba7217a37ff


Koji fix to not provide deleted builds

Retest this please

I apparently introduced a regression by this causing that only the root GAs of every build are available in maven-metadat.xmls. Fixing that now.


Add scroll anchor for Block

This patch teaches block how to anchor its scrolling to the end rather than the
start.
Fixes #136

@Hixie

lgtm


What if i need to run using docker-compose

Is there a way to run it without specify -i and so run varnish in foreground?
This is a problem if you're using docker-compose i suppose.
I think that something like that (in start.sh)
exec bash -c "exec varnishd -F -f /etc/varnish/default.vcl -s malloc,100M -a <IP_ADDRESS>:${VARNISH_PORT}"

could work.

Old issue/question, but here's an answer:
You don't need to change the command if running from Compose. Just have compose start the container:
data:
  image: busybox
  volumes:
    - /opt/docker/varnish/var:/var/lib/varnish
    - /opt/docker/varnish/etc:/etc/varnish
varnish:
  image: yourname/varnish
  volumes_from:
    - data
  ports:
    - "8000:80"
  environment:
    VARNISH_PORT: 80
    VARNISH_IP: <IP_ADDRESS>

The included start.sh runs varnish (which goes into the background) and then runs varnishlog as the foreground process. This allows you to get logs from varnish by using docker logs or docker-compose logs (though the latter lacks options for tail and follow and will blast your screen with more data than you can process).
This is not an issue and should be closed.


Wakelock doesn't work with Huawei + android 8.1

Your Environment

Uploader Version Number: 0.7.1
Your Android Phone Model Name (e.g. Samsung J1 Ace): Huawei Honor 7s
Android Version Number (e.g. use 4.4 for 4.4.4):  8.1
Network Connection at the time the issue occurred (Wi-Fi, Mobile):Wi-Fi
(if relevant) Nightscout website version (e.g. 0.8.4 Funnel cake, master / dev branch):

Brief Explanation of Issue
Huawei's ash process hibernates uploader, i.e. its ignores acquired wakelocks
Uploader Error Code
CNL gives E86 and then USB connection is lost
Steps to Reproduce (for bugs)
The issue is permanent, and is visible after 5-10 mins  from the start when CNL is connected to USB bus
The attached patch to AndroidManifest.xml seems to fix the issue
huawei.patch.gz
Don't know if it is a valid workaround/fix
Severity Score
5

Thanks. Hopefully this is of use to some with this issue.
I had a look at the changes for possible inclusion but due to potential issues with security and variability across android versions and even products from the same manufacture and no real way to do broad tests, I think it will be up to the user to apply and build this patch for their device.

This doesn't explain why the same issue can be seen on a 7-year old tablet, running Android 4.4.4, constantly connected to wall power (it's got a separate charger socket - which was the main reason it's got a new job despite its age) and in devel settings there's "screen always on when on power". E86, nevertheless.
Some random message sent by the CNL seems to get in the way of normal query-read handshakes, and I suspect that ignoring that message (that doesn't start with the expected byte) and reading again might also address the issue.
There's python code that shows the same behaviour, and perhaps could more easily be tweaked to present the extra data - and get an idea of how to handle or ignore them. @ondrej1024 got closer to it - I'm out right now because I don't have access to the whole setup (which was given to a friend).

@steve8x8 fyi the patch here addresses a particular device brand and their android customizations with manifest permissions.
Android 4.4.4 is really old and has it's own set of issues. While it's supported I would recommend using android versions from 6 on for solid reliability. Android OS will regularly kill apps without notification and when this happens while a CNL read is in progress it will E86. The android uploader has mitigations for this but with the older os it is much less reliable.

I was happy too early.
Next issue occured:
12-11 21:23:07.871   949  1181 I UsbAlsaManager: USB Audio Device Removed: null
12-11 21:23:07.878   949  1036 I UsbDeviceManager: HOST_STATE connected:false
12-11 21:23:07.880  1523  1761 I ash     : android send broadcast:android.hardware.usb.action.USB_DEVICE_DETACHED notify package: info.nightscout.android, pid: 2983
12-11 21:23:07.880  1523  1761 I ash     : info.nightscout.android { hibernation duration=204713 UptimeDuration=204714 } transition to: doze reason:bc_notify_android.hardware.usb.action.USB_DEVICE_DETACHED
12-11 21:23:07.932  2983  2983 D MasterService: receiver: android.hardware.usb.action.USB_DEVICE_DETACHED
12-11 21:23:07.944  1523  1761 I ash     : android send broadcast:android.hardware.usb.action.USB_DEVICE_DETACHED notify package: com.android.gallery3d, pid: 5206
12-11 21:23:07.945  1523  1761 I ash     : com.android.gallery3d { hibernation duration=730855 UptimeDuration=730856 } transition to: doze reason:bc_notify_android.hardware.usb.action.USB_DEVICE_DETACHED
12-11 21:23:07.989 12838 13637 E MedtronicCnlService: java.io.IOException: Error writing to usb endpoint
12-11 21:23:07.989 12838 13637 E MedtronicCnlService:   at info.nightscout.android.USB.UsbHidDriver.write(UsbHidDriver.java:90)
12-11 21:23:08.011  1193  1193 D StatusBar: onNotificationPosted: StatusBarNotification(pkg=info.nightscout.android user=UserHandle{0} id=1 tag=null key=0|info.nightscout.android|1|null|10107: Notification(channel=error pri=2 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x0 color=0x00000000 vis=PRIVATE))
12-11 21:23:08.011  1193  1193 D StatusBar: addNotification key=0|info.nightscout.android|1|null|10107
12-11 21:23:08.038  1193  1193 D StatusBar: No peeking: not in use: 0|info.nightscout.android|1|null|10107
12-11 21:23:08.052 12838 13637 D UsbHidDriver: Releasing HID interface.
12-11 21:23:08.053 12838 13637 W UsbHidDriver: releaseInterface returned false
12-11 21:23:08.053 12838 13637 D UsbDeviceConnectionJNI: close
Any hints available to share :)

it seems that USB connection fails randomly, now-and-then. But it still works at next poll. So you can forget the previous message. Normal behaviour, perhaps?

The usb device should never be issuing a detached broadcast unless it has actually become detached or the CNL self cuts the usb due to a E86 / E81 error (at around 10 mins after). Errors while in MedtronicCnlService would indicate this has happened during a poll. Are you absolutely sure the wired connection is solid?

It should be solid. CNL was "stationary" all the time on the table, and no one touched it. And USB connectors are tight ones.. Maybe I should try an another OTG cable?

Sounds like it should be good if it's just sitting there. Keep tracking the logs for a while and maybe there is some underlying trend that will give a clue.

My daughter's CNL is several years old, so I don't know what kind of hits it got in those years :)
So it may CNL issue as well, bad connector or even connector is in loose from PCB side.
I'm planning to buy an another CNL for nightscout usage only.
I'll keep tracking it from the logs.. And I'll use IPA to clean-up the connectors etc..

Looks nice now.
after using IPA the connection is much more stable now.
But I'll follow it.

Just a thought... maybe get a phone that is known to work well for this and be done with it. I've been running for nearly 4 years with Sony Xperia Z3 Compact going 24/7 and it has a separate charge connector to the usb. Also use a stripped down CNL taped to back of phone and with this low profile it runs very solid for months on end.

Nice idea to strip it down.
Thanks for the tip. Sony sounds quite reliable HW, perhaps I bomb my Huawei and switch to Sony.
It would be nice, if we could collect a list from working HW + SW envs with Medtronic.

This seem to be Huawei specific issue.
I set display to sleep after 30min of inactivity. And it started to work smoothly without any E86 or USB disconnection.
Next I changed display  to sleep after 30s of inactivity.
So lessons learned: Never buy anything from Huawei :(
Perhaps it is time to switch Huawei to Galaxy J5. But first I have to fix its broken display to able to try it.
Similar kind of fights is ongoing in here:
https://github.com/AltBeacon/android-beacon-library/issues/778

Yesterday I got a new display to J5, and the uploader was on overnight without any issues. So my problem is now solved.
Perhaps you should mentioned somewhere:
"Not recommended for use with vanilla Huawei devices, because of aggressive battery strategy" or similar..

@akumpu first I was wondering why you'd want to soak the stick in India Pale Ale - then became aware of yet another (also alcoholic!) meaning of that "IPA" abbreviation ;) Will try thoroughly cleaning the connector, although after so many reconnects, it should be shiny as hell...
Also I'll check whether I can find any images of the CNL inside (FCC site?) - and possibly how to reversibly disassemble it. The image by @Pogman doesn't show anything connected to the internal antenna socket, does it?

@akumpu to open the cnl use a thin edged tool to work the shell open starting at the usb end.

Hello,
Device: Huawei Mate 20 lite
Android: 8.1
from my experience in the last 3 days:

used the patch from akumpu on latest Version of the Uploader 0.7.1
set Power Saving in Settings to "disabled"
set screen/Display of to highest value which is not "never" (15 Minutes)
charged CNL

After three days of usage i had no "E86"- Error.

HI Akumpu & aendes,
Am facing the same CNL E86 errors on a Huawei 20 lite.
Newbie question, how do I go about applying said patch to the Uploader?
Thanks all for your great work!

@aendes:
About your comment:"set "screen/Display off" to highest value which is not "never" (15 Minutes)"
Does it leave screen on "forever".. Then this is no option for me, because then I'll lose mobility. I.e the battery will drain quite fast

@blad974 :
You need to install Android Studio, and download the source, change the file and compile the app. After that you can sideload the app.
@pazaan: Maybe you could release a version with these power settings?
@akumpu: I did not set it to never, my settings now are down to 5 Minutes and i have no issues over days.
With these settings i had no E86- Error since days

Thanks ever so much. Shall do and test. Cheers.

FYI. setting doesnt work with Honor7s.

@pazaan: Maybe you could release a version with these power settings?
@aendes - see https://github.com/pazaan/600SeriesAndroidUploader/issues/262#issuecomment-564552417.
We're very unlikely to make bespoke builds for vendor customisations to Android.


Adjust AM-Fix Gain Table

Adjusted the gain table in AM-Fix.c to prioritise reducing the LNA gain over reducing the PGA gain.
Helps to prevent Mixer overload and Cross modulation from adjacent strong signals.
Tested on a communications test set and it still receives all signal levels well.  Cross Modulation is definitely also reduced.

tested ok.

Perfect, greatly appreciated.


[FEATURE] Optionally provide openapi spec as YAML

Is your feature request related to a problem
FastAPI can generate the OpenAPI spec as JSON. It would be nice if that could (optionally) be converted to YAML by FastAPI, because the spec is usually read by humans and sometimes, dev policies might require that the spec is made available in YAML format.
The solution you would like
You can already specifiy the openapi_url when creating a FastAPI instance. When the provided url ens with .yaml, a yaml should be generated instead of a JSON:
app = FastAPI(openapi_url='/openapi.yaml')

The method FastAPI.setup() would need to be patched to something like this:
    def setup(self) -> None:
        if self.openapi_url:
            if self.openapi_url.endswith('.yaml'):
                async def openapi(req: Request) -> Response:
                    yaml_str = StringIO()
                    yaml = YAML()
                    yaml.indent(mapping=2, sequence=4, offset=2)
                    yaml.dump(self.openapi(), yaml_str)
                    return Response(yaml_str.getvalue(), media_type='text/yaml')
            else:
                async def openapi(req: Request) -> JSONResponse:
                    return JSONResponse(self.openapi())

            self.add_route(self.openapi_url, openapi, include_in_schema=False)
            ...

This would add the dependency ruamel.yaml, but that could be made optional.
Describe alternatives you've considered
Manually converting the JSON file to YAML evertime the API changes.
Additional context

I’d glady provide a PR for this if you are interested in this feature.

Is this the wrong time to point out that json is valid yaml? 😄
Just kidding, I think this would be a nice feature too!

Thanks for the conversation here! :cake:
But adding YAML support by default would mean requiring another dependency just to change the format :slightly_frowning_face:
The good news is that you can do it in your app, for your use case.
You could remove the default OpenAPI URL: https://fastapi.tiangolo.com/tutorial/metadata/#openapi-url
And then you could use the tools described at https://fastapi.tiangolo.com/advanced/extending-openapi/ but instead of changing the default OpenAPI, using those same utils to generate the OpenAPI dict.
And then use those utility functions to generate the OpenAPI dict that would be returned as JSON, and instead create a new path operation with your custom YAML response returning your serialized OpenAPI.

Thanks for your reaply. I can understand that you don’t want to add another dependency. I will see if your idea works for us.  If so, I could integrated the necessary changes into a cookiecutter template.

@tiangolo Thanks again for your suggestions.  Since we needed to some other modifications to FastAPI, too, I created a subclass that implements the desired behavior:
from io import StringIO

from fastapi import FastAPI
from fastapi.openapi.utils import get_openapi
from fastapi.routing import APIRoute
from ruamel.yaml import YAML
from starlette.responses import Response

class UnicornAPI(FastAPI):
    def __init__(
        self,
        *,
        contact_name: str = "",
        contact_email: str = "",
        audience: str = "",
        **kwargs,
    ) -> None:
        super().__init__(**kwargs)
        self.contact = {
            'name': contact_name,
            'email': contact_email,
        }
        self.audience = audience
        self.openapi_yaml_str = ''

    def use_route_names_as_op_ids(self):  # pylint: disable=redefined-outer-name
        """Simplify operation IDs so that generated API clients have simpler function
        names.

        """
        for route in self.routes:
            if isinstance(route, APIRoute):
                route.operation_id = route.name  # in this case, 'read_items'

    def openapi(self) -> dict:
        # Change original method to include extra info fields and to generate YAML
        # from the openapi schema.
        if not self.openapi_schema:
            self.use_route_names_as_op_ids()
            self.openapi_schema = get_openapi(
                title=self.title,
                version=self.version,
                openapi_version=self.openapi_version,
                description=self.description,
                routes=self.routes,
                openapi_prefix=self.openapi_prefix,
            )
            self.openapi_schema['info']['contact'] = self.contact
            self.openapi_schema['info']['x-audience'] = self.audience

            yaml_str = StringIO()
            yaml = YAML()
            yaml.indent(mapping=2, sequence=4, offset=2)
            yaml.dump(self.openapi(), yaml_str)
            self.openapi_yaml_str = yaml_str.getvalue()

        return self.openapi_schema

    def openapi_yaml(self) -> str:
        # This is just a wrapper for the opanapi path operation
        self.openapi()
        return self.openapi_yaml_str

    def setup(self) -> None:
        # Override the openapi path operation to return YAML
        super().setup()
        if self.openapi_url:
            async def openapi() -> Response:
                return Response(self.openapi_yaml(), media_type='text/yaml')

            self.add_route(self.openapi_url, openapi, include_in_schema=False)

All API apps then use UnicornAPI instead of FastAPI :smile_cat: :unicorn:

Ah, nice! Thanks for sharing your solution and closing the issue @sscherfke ! :rocket:

Thanks for making this nice piece of software <3

Thanks a lot for sharing @sscherfke.
@tiangolo: Does it still hold true that an unwanted additional dependency would be needed for this? As per https://fastapi.tiangolo.com/#optional-dependencies fastapi has an (optional) dependency on pyyaml anyway, so this could also be done with pyaml, not needing ruamel.
So maybe this could indeed be provided out-of-the-box conditionally, if pyyaml is installed, and automagically get linked in the /doc and /redoc pages...
In case anyone stumbles upon this (like myself) here's a simple variant without inheritance:

from fastapi import FastAPI
from fastapi.responses import Response
import functools
import io
from pydantic import BaseModel
import yaml

# data model
class HelloResponse(BaseModel):
    message: str

app = FastAPI()

# add endpoints
# additional yaml version of openapi.json
@app.get('/openapi.yaml', include_in_schema=False)
@functools.lru_cache()
def read_openapi_yaml() -> Response:
    openapi_json= app.openapi()
    yaml_s = io.StringIO()
    yaml.dump(openapi_json, yaml_s)
    return Response(yaml_s.getvalue(), media_type='text/yaml')

@app.get("/hello", response_model=HelloResponse)
def read_hello():
    return {"message": "Hello, world!"}

@app.get("/hello/{name}", response_model=HelloResponse)
def read_hello_name(name: str):
    return {"message": f"Hello, {name}!"}

The lru_cache mimicks app.openapi() once-only schema generation for the json-to-yaml conversion.  I don't know if this would work if there's any real async going on here (doesn't look like it from what I can see in app.openapi(), but I'm basically an async noob :-)).
Here's a gist that additionally hooks the .yaml OAS schema into the fastapi redoc page, instead of the normal .json: https://gist.github.com/hjoukl/790f95128e431396bcabf5ed39a5610b

Thanks @hjoukl for your code! I ran into trouble when using a list of servers (see https://fastapi.tiangolo.com/advanced/behind-a-proxy/#additional-servers), which requires additional fixes to make yaml.dump work.
For instance if you define the app as follows:
app = FastAPI(servers=[{"url": "https://example.com", "description": "Staging environment"}])

Then the yaml.dump call will fail because the url is converted to the type pydantic.networking.AnyUrl, which will be serialized as an unsafe python object and the Swagger UI doesn't like this.
In my case the following helped:
from pydantic.networks import AnyUrl, url_regex

def _any_url_representer(dumper, data):
    return dumper.represent_scalar("!anyurl", str(data))

yaml.add_representer(AnyUrl, _any_url_representer)
# omitted the constructor for AnyUrl since it is not required here
yaml.add_implicit_resolver("!anyurl", url_regex())

Where is this at?


Fix tokenization

Some fixes regarding whitespace issues in the network output.

whats fixed here exactly?

fixed some formatting
use the proper way for the removal of special tokens (end of sequence, padding, ...)
add all notes (e.g. c''1) to the tokenizer vocabulary. This solves some issues where the notes are split into subtokens. This results in unessesary many tokens (and autoregressive steps during the prediction), longer sequences during training and issues where the tokenizer inserts space tokens between subtokens of the note (e.g. c''1 is c 1`). I do not fully understand the reason for the last one but my fix works.


Add Swift workflow

Create GitHub action workflow for building and testing SchafKit on macOS.
Issues
~Currently these tests are failing because the Swift distribution used in the workflow doesn't recognize new features of SwiftUI, which cause it to break. I'm looking into whether this can be fixed.~
After updating the workflow, we're getting another error.
The issue is being tracked at: https://github.com/fwal/setup-swift/issues/133
Generally, another issue is that this only tests the macOS-specific code.
Not sure if there's any way to actually test the iOS-specific code in an automated fashion.

@JannThomas please check the build error.

Is this a valid error?

There was a valid error in the iOS target (fixed with 63bf898). But for the macOS target afaics

The target SDK version seems to be 10.15.6. That is wrong. It should be 10.16 or 11.0, depending upon which is available. Can you do that? Doesn't make sense still that it does not compile, as it is marked with @available(macOS 10.16, *).

The target SDK version seems to be 10.15.6. That is wrong. It should be 10.16 or 11.0, depending upon which is available. Can you do that?

I'm actually pretty sure that it's not possible to compile with 11.0 at the moment.

So I guess we'll either have to somehow make this work with macOS 10.15 or wait for release.

Doesn't make sense still that it does not compile, as the line in question is marked with @available(macOS 10.16, *)

With your annotation that should work though..

I guess we'll just have to wait 🤷🏻♂


Annotation Values

Annotations
Resolves: #685
What's Changed:
Allows both lists and dictionaries to be used within annotations

Type of Change:

[ ] Bug fix
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Housekeeping:

[x] Tests have been updated to reflect the changes done within this PR (if applicable).
[x] Documentation has been updated to reflect the changes done within this PR (if applicable).

Screenshots (If Applicable):

Hahaha I like it! Thanks for checking it as well


WHATWG now uses issue templates

This ensures we link directly to the options we're offering as per https://github.com/whatwg/spec-factory/pull/53.

As choose redirects this seemed safe to merge given that we're going ahead with this.


[REDIS] az redis create has too many required params

We should be able to default everything but name and group.
I had to jump to the portal to understand what C, P and Standard actually mean. There needs to be some documentation here to describe C and P. Please don't make me go to the portal.
Why not just create an enum of all of the family / capacity values and then fill the correct combination of sku name, family and capacity based on something like, Premium1, Basic0, Standard2, etc? These combinations are error prone and confusing.
$ az redis create -h

Command
    az redis create: Create new Redis Cache instance.

Arguments
    --location -l       [Required]: Location. You can configure the default location using 'az
                                    configure --defaults location=<location>'.
    --name -n           [Required]: The primary resource name.
    --resource-group -g [Required]: Name of resource group. You can configure the default group
                                    using 'az configure --defaults group=<name>'.
    --sku-capacity      [Required]: What size of redis cache to deploy. Valid values for C family
                                    (0, 1, 2, 3, 4, 5, 6), for P family (1, 2, 3, 4).  Allowed
                                    values: 0, 1, 2, 3, 4, 5, 6.
    --sku-family        [Required]: Which family to use. Valid values: (C, P).  Allowed values: C,
                                    P.
    --sku-name          [Required]: What type of redis cache to deploy. Valid values: (Basic,
                                    Standard, Premium).  Allowed values: Basic, Premium, Standard.
...

Required parameters got changed and doesn't match what is posted in this issue. Below are the required parameters from latest version of azure-cli 2.0.75:
Command
    az redis create : Create new Redis Cache instance.

Arguments
    --location -l       [Required] : Location. Values from: `az account list-locations`. You can
                                     configure the default location using `az configure --defaults
                                     location=<location>`.
    --name -n           [Required] : Name of the Redis cache.
    --resource-group -g [Required] : Name of resource group. You can configure the default group
                                     using `az configure --defaults group=<name>`.
    --sku               [Required] : Type of Redis cache.  Allowed values: Basic, Premium, Standard.
    --vm-size           [Required] : Size of Redis cache to deploy. Basic and Standard Cache sizes
                                     start with C. Premium Cache sizes start with P.  Allowed
                                     values: c0, c1, c2, c3, c4, c5, c6, p1, p2, p3, p4, p5.

@haroldrandom Can this issue be closed?

I think this SKU capacity option should be clear right now as features delivered.
If don't, please feel free to open another issue to describe. Sorry for the late reply.


String pool

Existing implementation abuses BoundedArray everywhere. This has the major disadvantage of requiring multiple copies as the data ferries through the layers.
I propose a string pool to help resolve the problem:
const PoolString = struct {
    next: ?*PoolString,
    len: usize,
    data: [0x1000]u8,

    var available: ?*PoolString = null;

    pub fn init() !*PoolString {
        if (available) |result| {
            available = result.next;
            result.next = null;
            return result;
        }
        return error.OutOfMemory;
    }

    pub fn deinit(self: *PoolString) void {
        self.next = available;
        available = self;
    }
};

Fixed via https://github.com/fengb/zigbot9001/commit/7e208312503096a18b90927f38377c1606462597


Penetration occurs in mujoco simulation

Hi,
I'm a student and I'm trying to use MuJoCo for  peg-in-hole task
When I started simulating, I found that the block would get stuck in the board, and it seemed to be constantly shaking.
The following are the XML files for my block and peg-board
minimal XML
block XML
<mujocoinclude model="block">
        <body name="peg_block_link" pos="0 -0.3 -0.27" euler="1.5707963 1.5707963 0">
            <joint name="block_joint" type="free" damping="0.0001"></joint>>
            <geom type="mesh" contype="0" conaffinity="0" group="1" mass="0.001" friction="10" rgba="0.078431 0.494117 0.984313 1" mesh="peg_block" />
            <geom type="mesh" rgba="0.078431 0.494117 0.984313 1" mesh="peg_block" />
        </body>>
</mujocoinclude>
--------------------------------
peg-board XML
<mujoco model="peg_board">
        <body name="board_link" pos="0 -0.3 -0.295">
            <geom type="box" size="0.08 0.05 0.005" mass="1000" material="board_mat" />
        </body>>
</mujoco>

Here is a  video, illustrating my question:
https://github.com/google-deepmind/mujoco/assets/69098659/0aa6936e-3da4-4113-a397-a3e8a535ffbe

https://mujoco.readthedocs.io/en/latest/XMLreference.html#option-flag-multiccd


Error: Login error, VPN ?

Hi,
I try to use rdcli (version 1..3.2 et 1.3.3) and i always have an error : Error: Login error, VPN ?
I don't know what to do. I am not behind a VPN.
My OS is Archlinux which is on a dedicated server.
Regards,
Jérémy

Hello @jeremyj29,
Actually, real-debrid.com don't allow dedicated servers... You can try to ask them to allow your specific server on their website : https://real-debrid.com/support
I have no solutions to bypass this rule. Maybe soon !

Ok !
Thanks for the answer.
Regards,
Jeremy


use rev returned by List in Watch. Closes #22

Coverage decreased (-0.01%) to 84.124% when pulling ca9e2db9a89071966aed635f0c06b84fea27a9f3 on mthenw:fix-watch-list into 82cb888d811cbc8031b0f0e4e9d11a63ba354b56 on abronan:master.

Coverage decreased (-0.01%) to 84.124% when pulling ca9e2db9a89071966aed635f0c06b84fea27a9f3 on mthenw:fix-watch-list into 82cb888d811cbc8031b0f0e4e9d11a63ba354b56 on abronan:master.

I'm nitpicking a little bit but it would be awesome if the commit description could include a little bit more informations about the bug and how the commit fixed it (without the -m flag). So that this is well documented! I'm planning to add more tests for these cases so that'll remind myself of what was the issue looking at the commit history. Thanks!

Sure thing. I will update the commit message.

Done :)

Coverage decreased (-0.01%) to 84.124% when pulling 7a8d4c590558f37131cf5af20b1ae0be9bf89595 on mthenw:fix-watch-list into 4f0a102dbcf29f873dd68238444c4b67d419c069 on abronan:master.


Activate Jupyter extension on interactive window open

This impacts whether the Jupyter extension activates on VS Code reload with an existing interactive window restored from backup.

Codecov Report

Merging #6422 (e0b8275) into main (731f1ba) will decrease coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #6422    +/-   ##
======================================
- Coverage     69%     69%    -1%
======================================
  Files        407     410     +3
  Lines      27918   28248   +330
  Branches    4138    4184    +46
======================================
+ Hits       19491   19616   +125
- Misses      6770    6963   +193
- Partials    1657    1669    +12

Impacted Files
Coverage Δ

...science/jupyter/kernels/kernelDependencyService.ts
86% <0%> (-3%)
:arrow_down:

...t/common/application/webviewPanels/webviewPanel.ts
59% <0%> (-3%)
:arrow_down:

...datascience/editor-integration/codelensprovider.ts
82% <0%> (-2%)
:arrow_down:

src/client/datascience/baseJupyterSession.ts
70% <0%> (-2%)
:arrow_down:

...t/datascience/notebook/vscodeNotebookController.ts
79% <0%> (-1%)
:arrow_down:

...ient/datascience/editor-integration/codewatcher.ts
68% <0%> (-1%)
:arrow_down:

src/client/common/types.ts
100% <0%> (ø)

src/client/datascience/types.ts
100% <0%> (ø)

src/client/debugger/jupyter/debuggingCellMap.ts
100% <0%> (ø)

src/client/debugger/jupyter/kernelDebugAdapter.ts
5% <0%> (ø)

... and 11 more


Publish to topic cmd_val

Is there a good example how to control two motors for differential drive robot ? I would like to publish Twist message to cmd_val topic to control velocity of two motors.

Hi, there's a good example provied by @kallaspriit. Please refer to issue #1.

Yeah my robot uses this library for physical and simulated differential drive robot, works nicely :)
https://github.com/kallaspriit/rosbot
https://www.youtube.com/watch?v=t-1GAfGHRLs

@kallaspriit I have checked your library, but I don't understand which part do I need to create a node that creates cmd_vel topic and sends the correct data to odrive. I'm new at this. Can you help me ? I have seen that you use joystick to send a Twist message, but I dont know where is that twist message being read and then converted to values that odrive driver understands.

For manual testing /cmd_vel is published by teleop_twist_joy package (which uses  joy package to get joystick input).
See this for reference
https://github.com/kallaspriit/rosbot/blob/main/ros/src/teleop_twist_joy/launch/teleop.launch.py
To run in, you can run . launch_teleop.bash in ros or
. install/local_setup.bash
ros2 launch teleop_twist_joy teleop.launch.py

Which does the same thing.

Ok, but who is subscribing to /cmd_vel topic ? And how is the Twist message being converted to input so that odrive can understand it ? Thats the part that I don't understand.

Before using this package, you need to be familiar with ros2_control framework.
http://control.ros.org/ros2_controllers/diff_drive_controller/doc/userdoc.html

Ok. Some example of how to use an implement diff_drive_controller with odrive package would be nice. @kallaspriit coould you help me with this ?

Well the rosbot repo IS an example of how to implement diff drive controller with odrive, not sure what else you need. Familiarize yourself with ROS2, ros2_control, URDF's and read the repo. It's all configuration, no actual code is needed but it takes time to understand what does what, no way around it.
Main configuration is in robot URDF (Universal Robot Descriptor File), take a look at
https://github.com/kallaspriit/rosbot/blob/main/ros/src/rosbot_description/urdf/rosbot.urdf.xacro
https://github.com/kallaspriit/rosbot/blob/main/ros/src/rosbot_description/ros2_control/rosbot_system.ros2_control.xacro
https://github.com/kallaspriit/rosbot/blob/main/ros/src/rosbot_description/urdf/rosbot_links.urdf.xacro
https://github.com/kallaspriit/rosbot/blob/main/ros/src/rosbot_description/config/diff_drive_controller.yaml

Ok, thank you @kallaspriit and @borongyuan four your help.


Development team recordings

Description:

Add links to the development team recording.
Add the title for each recording
Add resources, references etc links if any
Check our out here  on how to submit a PR

@peculiaruc Please I would like to be assigned to this issue


remove install script and use json

Bash Install Script Removal for RPM/DEB (Ansible changes)

[x] Eliminate bash install script for deb
[ ] Eliminate bash install script for rpm
[ ] Ensure there is a var to pass in the location of the install files as either a path or a hyperlink
[ ] Split permissions for data directory from creation of data directory
[x] Switch templates from YAML to JSON for ease of future modification

related to https://github.com/redpanda-data/deployment-automation/issues/176

@hcoyote re: https://github.com/redpanda-data/redpanda-ansible-collection/pull/14#discussion_r1200911361
this was a derp on my part. I forgot to put in the deb repo config stuff I had been working. It's all in now and that config pull is removed 🤦♀


Resolving async data in router with async props

What problem does this feature solve?
Idea it to handle all async data in the router stage, so the component already get's the data without a need for v-if checking. vue-router already has beforeRouteEnter and beforeRouteEnter, but I think it's too complicated because I need to reimplement both methods to be able to reuse component, the code overhead is to large and it also doesn't enable me to reuse component (same component, different data source).
What does the proposed API look like?
API proposes to add additional logic into router beforeEach (this is always called). Changes to router are
router.beforeEach((to, from, next) => {
    to.matched.forEach((match) => {
        Object.keys(match.props).forEach(propKey => {
            let props = match.props[propKey];
            if (typeof props === "boolean") {
                next();
            } else {
                if (!match._cache_props) {
                    match._cache_props = props;
                }

                match._cache_props(to).then((data) => {
                    match.props[propKey] = () => data;
                    next();
                });
            }
        });

    });
});

and then we simply make our props async
route = {
    path: '/products/:id',
    name: 'products.product',
    component: Product,
    props: async (route) => ({
        product: await http.get(`products/${route.params.id}`).then(r => r.data)
    })
}

This will first resolve the data, then render the component. All data will be passed to component through standard props.
Of course, there is additional works to handle all types of props and to have dependency resolves (I resolve something based on previous resolve).

At first, I was quite skeptical because it's adding another way of doing something
But as you said, it does make things more declarative and easy to test.
Regards implementation, I'm wondering if we shouldn't abstract some of the behaviour in components and leverage existing async components in Vue

Any news regarding this? I would also like to resolve data before passing it to the view (angular had this with resolve, it would be quite handy to have something like it without depending on the store)

I'm also struggling with this, @FrEaKmAn's first pass is good but as he detailed it is also incomplete.
This is the only thing preventing us from a full move away from Angular1.

To be clear, async data is already feasible in the current state of vue-router and it is documented. This feature would make things more declarative and easier to test

https://router.vuejs.org/guide/advanced/data-fetching.html

Here are my 2 cents:
# Todolist.vue
<template>

            {{ todo.text }}

</template>

# router.js

import VueRouter from "vue-router";

const hydrateProps = (route, props) => {
    Object.assign(route.meta, {props});
}

return new VueRouter({
    routes: [
        {
            path: '/todos',
            name: 'todolist',
            async beforeEnter(to, from, next) {
                const todos = await someService.retrieve('/todos');
                hydrateProps(to, {todos});
                next();
            },
            props: (route) => ({
                todos: route.meta.props.todos
            }),
            component: () => import('Todolist'),
        }
    ],
});

WDYT?

After further consideration and after revisiting the architecture of navigation guards, props cannot be async because they are a mere way to provide data to components and must be synchronous. They are not part of the navigation flow.
It's however easy to recreate a similar behavior in Vue Router 4 by storing data in to.meta in a navigation guard like beforeResolve() and then using it in props props: to => ({ data: to.meta.data }).
In Vue router 3, changes to to.meta should be avoided. One could

@posva [In Vue router 3, changes to to.meta should be avoided. One could ...], you never finished this sentence, and I am using Vue router 3


Repair sfvmss avjai

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @avjai you are introducing a new api-version for the RP compute, but your account did not join the Azure organization. Please be sure to do that before you open a PR.
In the meantime, I know that CRP has a dev branch here: https://github.com/Azure/azure-rest-api-specs/tree/feature/cplat-2021-11-01, since you are introduce the same api-version in this PR, I would like to close this one in favor of the dev branch


Dynamic typing of activity map parameter values (or dynamic dropdown choices in UI)

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
When the legal values for an entry in an activity map parameter depend on the key of the entry, I have to provide values for all keys and have to guess the right values when editing in the UI.
For example (and show below), I would like a parameter to list a subset of devices and the corresponding states to which I want to set the devices.  The devices and their states come from a PEL (power equipment list).

Each device has a different set of legal states, but I can't change the possible values based on the key, so I list all of them together.  In the screenshot above, ON_UHF_BITSTREAM is a not legal value for the ALTIMETER_ALT_STATE component.  This mission model only includes a small set of devices for testing.  But, we expect to have 100+ devices that together will have a 1000+ values, so I'll need an enum in the Java with these 1000+ states.  Users will need to know the possible states to find in the dropdown of 1000+ choices.
Describe the feature request
I would like to somehow be able to change or restrict the possible choices in the UI dropdown for a value of an entr in an activity map parameter based on the chosen key of the entry.
There are multiple possible designs for this.

Matt Dailis mentioned, "Expanding the value schema to support tagged unions is something we've wanted for a while, but never got around to. I think that would address this particular use case."

Can you give more information on the code you have written/restrictions you have?
In my experience from Clipper, these PEL states were represented as a enum made of the permitted compound states. For example, rather than one mega enum for all possible PEL states across instruments, there'd be one enum per instrument (ie ALTIMETER_ON, ALTIMETER_OFF). Additionally, rather than having one generic activity type that could change any state arbitrarily, there was one activity type per subsystem, ie SetAltimeterState (or whatever the subsystem for the Altimeter is). Together, these can limit the need for a mega enum.

We don't want a separate parameter for each device because the activity type, by default, may only be relevant to a few devices, and we don't want to limit which the devices are affected to give the user flexibility.

#1526 is a possible solution


doc: add Baidu Waimai

/cc @ohlinux

lgtm

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0c38f1f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #7473   +/-   ##
=========================================
  Coverage          ?   70.79%
=========================================
  Files             ?      244
  Lines             ?    21518
  Branches          ?        0
=========================================
  Hits              ?    15233
  Misses            ?     5151
  Partials          ?     1134

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 0c38f1f...911ae60. Read the comment docs.


Resolve hosted zones regardless of domain name

Goes through and incrementally looks for a hostedZone based on the
domain
Resolves #62

@bigkraig This solution works elegantly. I'm working through a small caching issue, which i'm attempting to resolve tonight.
Caching issue will cause minimal code changes, feel free to review when you have a free moment.

Ready for validation and merge.


Remove savings from Footer links 💸

only to be exposed after bank launch 🙇🏻♂

:tada: This PR is included in version 3.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


crash on logging out then in

InsanityPie
Not sure if it's something stupid with my game but im having this issue where I start a world and enter just fine. Play a while, then after exiting the world then going to play it later I always get these:
"The state engine was in incorrect state ERRORED and forced into state SERVER_STOPPED. Errors may have been discarded.
and
"The state engine was in incorrect state ERRORED and forced into state AVAILABLE. Errors may have been discarded." and just kicks me back to the title screen.
The log says the problem is something to do with the game being unable to unregister dimension 256 since no provider was registered. If you need the part of my log that shows the full error just let me know. And yes, I tried with only advance rocketry and 1 RF powered mod to see if it was a mod conflict and got the exact same error and the inability to enter a played on world.
Im using the most recent version, 0.8.0

I'm experiencing a similar issue involving dimensions but since I removed
Compact Machines the game no longer includes a dimension ID in the crash
report, just that it's something at unregister.
On Thu, Sep 15, 2016, 2:20 PM zmaster587<EMAIL_ADDRESS>wrote:

#145 https://github.com/zmaster587/AdvancedRocketry/issues/145
InsanityPie
View User Profile
Send Message
Follow User
Ignore User
Posted 2 days ago
Not sure if it's something stupid with my game but im having this issue
where I start a world and enter just fine. Play a while, then after exiting
the world then going to play it later I always get these:
"The state engine was in incorrect state ERRORED and forced into state
SERVER_STOPPED. Errors may have been discarded.
and
"The state engine was in incorrect state ERRORED and forced into state
AVAILABLE. Errors may have been discarded." and just kicks me back to the
title screen.
The log says the problem is something to do with the game being unable to
unregister dimension 256 since no provider was registered. If you need the
part of my log that shows the full error just let me know. And yes, I tried
with only advance rocketry and 1 RF powered mod to see if it was a mod
conflict and got the exact same error and the inability to enter a played
on world.
Im using the most recent version, 0.8.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zmaster587/AdvancedRocketry/issues/200, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJzt6ksD9-LL4NsWVU61rwLwC7mk6n39ks5qqZqagaJpZM4J-Pw0
.


Make reference to libsqlite3.tbd non-version specific on macOS

The filesystem reference to libsqlite3.tbd for the macOS platform had been hardcoded to the macOS 10.11 SDK. This PR updates the path of this file to the non-version-specific MacOSX.sdk (and hopefully fixes some downstream issues in the process!).

Closed in 4b4dc65997c1fce4735178c7563285b988133c6a


Incorrect string comparison

Observed while building package for 4.3.0.
17:33PM kory@kdd-ws:~/dev/prog/cpp/build_storage_tiering $ ninja package
[2/7] Building CXX object CMakeFiles/irods_rule_engine_plugin-unified_storage_tiering.dir/storage_tiering_utilities.cpp.o
/home/kory/dev/prog/cpp/irods_capability_storage_tiering/storage_tiering_utilities.cpp:15:26: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
            if(msp->type == STR_MS_T) {
                         ^  ~~~~~~~~
1 warning generated.
[6/7] Run CPack packaging tool...
CPack: Create package using DEB
CPack: Install projects
CPack: - Install project: irods_capability-storage_tiering []
CPack: Create package
CPack: - package: /home/kory/dev/prog/cpp/build_storage_tiering/irods-rule-engine-plugin-unified-storage-tiering_<IP_ADDRESS>-1~bionic_amd64.deb generated.

We should cherry pick the fix for this to 4-2-stable if it has the same problem.
We verify.

Same issue is in 4-2-stable.


[BUG] - AttributeError: module 'bcrypt' has no attribute 'about'

when run app locally
(trapped) error reading bcrypt version
Traceback (most recent call last):
  File "C:\project\.venv\Lib\site-packages\passlib\handlers\bcrypt.py", line 620, in _load_backend_mixin
    version = _bcrypt.__about__.__version__
              ^^^^^^^^^^^^^^^^^
AttributeError: module 'bcrypt' has no attribute '__about__'

app runs normally on localhost
app deployed, runs ok


Update to 1.1.0

Checklist

[X] Used a personal fork of the feedstock to propose changes
[] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@brianv0 looks like this is ready to merge


Actions: add rateLimitScope

Post actions can have a rateLimit argument that specifies how often identical events from the same hook and thread are generated. There is a use case to rate limit per process or generally.
This commit introduces the rateLimitScope argument, to be used with rateLimit, to specify whether the rate limiting should be limited to the same thread, the same process, or globally, using values "thread" (default), "process", or "global".
Add rateLimitScope to control what rateLimit applies to.

LGTM after I guess updating this
https://github.com/cilium/tetragon/blob/78262f08662cf23cf1045bdb79e4c6a5165778f6/pkg/k8s/apis/cilium.io/v1alpha1/version.go#L10
?
Really nice feature was planning to add it. Also we may want to add: rateLimitBy="function (default) | policy_name"

Yeah I forgot the version! I'll do that now.


Some outdated code in the tutorial.

Chapter 3 Propositions and Proofs uses Or.intro_left, Or.intro_right, and Or.elim pretty heavily, but I believe they are no longer supported in Lean4.

It is your Lean 4 version that is outdated, not the tutorial :) https://github.com/leanprover/lean4/blob/075ba63a8b4653a5152917cef028b0695f2b471d/src/Init/Prelude.lean#L145-L154. Try updating to the latest nightly.

Ah thanks, I apologize for not doing my research. Still, while trying to install the nightly build I've run into the following error: dyld: Library not loaded: /Users/runner/work/lean4/lean4/build/stage1/lib/lean/libleanshared.dylib. Not sure if this has anything to do with the artifact mentioned at https://github.com/leanprover/lean4/pull/148.

That sounds like a bug. Could you check and see if you can run the bin/lean executable in https://github.com/leanprover/lean4/suites/3726227515/artifacts/91212300?

Thanks, that's now working for me.
The version that did not work is the nightly build on 9/8.


allow to specify a proxy when calling openai api

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
None
Problem Description
servers that are not on the internet need to refer to a proxy when calling the openai api,
like curl --proxy [proxy] openapi_request_url
Solution Description
allow to specify a proxy url
Benefits
servers that are not on the internet need to refer to a proxy when calling the openai api,
Potential Drawbacks
none
Additional Information
this is actually a change in go-openai

this is actually a change in go-openai


Sample for Integration Registry

Hi Team,
Can you also add sample resource file for creating Integration Registry for Azure Container Registry (ACR) via Tokens from Azure Keyvault to the examples location?
Thanks

Hi, @ParthibanSG  we are planning to do some refactoring around this resource, In the meanwhile you can try the following:
resource "aquasec_integration_registry" "integration_registry" {
  name = "azure_integration_registry"
  type = "ACR"
  author = "<AUTHOR>"
  auto_cleanup = true
  auto_pull = false
  auto_pull_interval = 1
  auto_pull_max = 100
  auto_pull_rescan = false
  auto_pull_time = "08:45"
  description = "Automatically discovered registry"
  image_creation_date_condition = "none"
  prefixes = []
  pull_image_age = "0D"
  pull_image_count = 5
  scanner_name = []
  scanner_type = "any"
  url = "<REGISTRY_URL>"
  username = "<USERNAME>"
  password = "<TOKEN>"
  options {
    option = "ACRConnectionType"
    value ="Token"
  }
}

@yossig-aquasec Thanks for the sample and is there any ETA when the refactoring for this resource will be completed so that it can be put to use ?


train_y.bin

Thank you for your contribution!
python DEC.py --dataset mnist
This runs fine.
However,
python run_exp.py
yields this:
Reached tolerance threshold. Stopping training.
('saving model to:', './results/exp1/reuters10k/trial9/DEC_model_final.h5')
Traceback (most recent call last):
File "run_exp.py", line 26, in
x, y = load_data(db)
File "./datasets.py", line 324, in load_data
return load_stl()
File "./datasets.py", line 283, in load_stl
y1 = np.fromfile(data_path + '/train_y.bin', dtype=np.uint8) - 1
IOError: [Errno 2] No such file or directory: './data/stl/train_y.bin'
Any ideas on what the problem is?
Much appreciated.
Thanks.

Thank you for your response. I have re-performed that step, just to make sure I have done it, and still, I get the same " IOError: [Errno 2] No such file or directory: './data/stl/train_y.bin' " error.
Any other ideas? I appreciate your help.
Thanks.

Whoops, did not unpack the data enough before. I've unpacked it, will try it again now. Thanks.

"No data! Use %s/get_data.sh to get data ready, then come back" % data_path

AssertionError: No data! Use ./data/stl/get_data.sh to get data ready, then come back
I have run:
cd data/stl
bash get_data.sh
cd ../..
And unpacked the data, revealing train_y.bin and other files. Now, instead of getting the train_y.bin error, I am getting the error above.
Am I doing something wrong?
Thanks!

@dnnguifever After unpacking, there should be at least four files existing in 'data/stl': train_X.bin, test_X.bin, train_y.bin, test_y.bin. Please make sure that satisfied. See details on http://ai.stanford.edu/~acoates/stl10/

-rw-r--r-- 1   221184000 Sep 21 10:43 test_X.bin
-rw-r--r-- 1             8000 Sep 21 10:43 test_y.bin
-rw-r--r-- 1   138240000 Sep 21 10:43 train_X.bin
-rw-r--r-- 1             5000 Sep 21 10:42 train_y.bin
Those are four files in my data/stl folder. I am still getting that error.
Thank you for your help!

@dnnguifever Maybe you can implement load_stl() by yourself according to http://ai.stanford.edu/~acoates/stl10/. It is very easy.


Support command to get filePath through fileId

What changes are proposed in this pull request?
Please outline the changes and how this PR fixes the issue.
Why are the changes needed?
Please clarify why the changes are needed. For instance,

If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

change in user-facing APIs
addition or removal of property keys
webui

@dbw9580 I just update this PR under the discussion between us, PTAL.

@maobaolong this should be superseded by #15565, can we close this PR?

@dbw9580 Thanks for remind me, close this PR


Standardize nb examples and briefly describing its content in the nb title

In the documentation website the examples title are not standardized. Some of the examples are in capital letters and some are not, as we can see in this picture:

The titles must follow the pattern seen in this example:
Example 5.9.4 (Cross-Coupled Bearings)

PR #174  closes this issue.


Ansible installation fails, registering the API server

Describe the bug
The Ansible installation fails:
TASK [api_server_cluster_admin : Register API Server with API Aggregator] *************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "cat <<EOF | oc apply -f -\napiVersion: apiregistration.k8s.io/v1beta1\nkind: APIService\nmetadata:\n  name: v1alpha1.enmasse.io\nspec:\n  group: enmasse.io\n  groupPriorityMinimum: 1000\n  caBundle: \"XXXXX=\"\n  version: v1alpha1\n  versionPriority: 10\n  service:\n    name: api-server\n    namespace: \"enmasse\"\nEOF\n", "delta": "0:00:00.383646", "end": "2018-09-24 13:15:47.307682", "msg": "non-zero return code", "rc": 1, "start": "2018-09-24 13:15:46.924036", "stderr": "Warning: oc apply should be used on resource created by either oc create --save-config or oc apply\nThe APIService \"v1alpha1.enmasse.io\" is invalid: spec.insecureSkipTLSVerify: Invalid value: true: may not be true if caBundle is present", "stderr_lines": ["Warning: oc apply should be used on resource created by either oc create --save-config or oc apply", "The APIService \"v1alpha1.enmasse.io\" is invalid: spec.insecureSkipTLSVerify: Invalid value: true: may not be true if caBundle is present"], "stdout": "", "stdout_lines": []}
	to retry, use: --limit @/home/jreimann/Development/workspace-hono/hono/deploy/src/main/deploy/openshift_s2i/enmasse-0.22.0/ansible/playbooks/openshift/deploy_cluster_admin.retry

To Reproduce
Steps to reproduce the behavior:
Run:
ansible-playbook -i enmasse.inventory enmasse-0.22.0/ansible/playbooks/openshift/deploy_project_admin.yml
oc login -u admin
ansible-playbook -i enmasse.inventory enmasse-0.22.0/ansible/playbooks/openshift/deploy_cluster_admin.yml

Expected behavior
Not to fail.
Additional context
EnMasse: 0.22.0
oc v3.10.0+dd10d17
kubernetes v1.10.0+b81c8f8
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://cluster00.amazing.iot-playground.org:8443
openshift v3.10.0+e3465d0-44
kubernetes v1.10.0+b81c8f8

Inventory file:
[enmasse]
localhost ansible_connection=local

[enmasse:vars]
namespace=enmasse
multitenant=true
enable_rbac=true
api_server=true
service_catalog=true
register_api_server=true
keycloak_admin_password=admin
authentication_services=["standard"]

I had to add insecureSkipTLSVerify: false to the API registration call to make it work.

This seems to be working fine with systemtests on 3.10, which registers the API server. This will be changed a bit for 0.23.0, so might be worth retrying with that.

@ctron were you able to retest with a newer release?

I don't have the ansible installation anymore. As I switched to the plain YAML files. So I would need to start from scratch testing this.

Api-server is gone.


Integrate JS parser module better with JRT

The fact that the JS parser had been developed as a separate
component for a while is still visible from some macros that mirror
things from JRT. This patch removes those duplicates and makes the
JS parser rely on jrt.h. (The removed macros are: PARSER_DEBUG,
PARSER_INLINE, PARSER_NOINLINE.)
JerryScript-DCO-1.0-Signed-off-by: Akos Kiss<EMAIL_ADDRESS>

LGTM

LGTM


ci: switch CentOS Stream 8 to use vault.centos.org

CentOS Stream 8 has now been archived to vault.centos.org.
Refs: https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/

This fixes the following Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist error:
#5 [common 2/2] RUN dnf install -y dnf-plugins-core rpm-build libicu-devel &&   dnf config-manager -y --set-enabled powertools &&   dnf install -y epel-release epel-next-release &&   dnf clean -y all
#5 0.392 CentOS Stream 8 - AppStream                     760  B/s |  38  B     00:00
#5 0.398 Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
#5 ERROR: process "/bin/sh -c dnf install -y dnf-plugins-core rpm-build libicu-devel &&   dnf config-manager -y --set-enabled powertools &&   dnf install -y epel-release epel-next-release &&   dnf clean -y all" did not complete successfully: exit code: 1
------
 > [common 2/2] RUN dnf install -y dnf-plugins-core rpm-build libicu-devel &&   dnf config-manager -y --set-enabled powertools &&   dnf install -y epel-release epel-next-release &&   dnf clean -y all:
0.392 CentOS Stream 8 - AppStream                     760  B/s |  38  B     00:00
0.398 Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
------
Dockerfile:5
--------------------
   4 |     FROM quay.io/centos/centos:stream8 as common
   5 | >>> RUN dnf install -y dnf-plugins-core rpm-build libicu-devel && \
   6 | >>>   dnf config-manager -y --set-enabled powertools && \
   7 | >>>   dnf install -y epel-release epel-next-release && \
   8 | >>>   dnf clean -y all
   9 |
--------------------
ERROR: failed to solve: process "/bin/sh -c dnf install -y dnf-plugins-core rpm-build libicu-devel &&   dnf config-manager -y --set-enabled powertools &&   dnf install -y epel-release epel-next-release &&   dnf clean -y all" did not complete successfully: exit code: 1
Error: Process completed with exit code 1.


A simple speed test to measure conversion time

Information

Generic improvement.

Changes proposed in this PR:

Just a simple speed test that averages results.

Checklist

[x] All JUnit tests pass (mvn clean verify).
[x] Added and updated JavaDocs for non-test classes and methods.
[x] No local design debt. Do you feel that something is "ugly" after your changes?

No more love for this PR.  😢
If I am to understand @omnivion, he doesn't like the idea of having this as part of our official code in the repository.  I'm cool with closing this PR without merging, but does anyone else have a thought on this PR, @clydet or @sfradkin?

Meh, I'm closing this.


JsonSerializerSettings not honored for Field Expressions

NEST/Elasticsearch.Net version:
7.0.1
NEST.JsonNetSerializer version:
7.0.1
Elasticsearch version:
7.2.0
Description of the problem including expected versus actual behavior:
Expected: be able to query on a field using an Expression lambda which should honor the [JsonProperty] attributes when configured using JsonSerializerSettings just like in NEST 6.8.0.
Actual: No query results are returned.
Steps to reproduce:

DELETE my-index
Index a document and query it using a date range filter:

var pool = new SingleNodeConnectionPool(new Uri("https://localhost.fiddler:9200"));
var settings = new ConnectionSettings(pool, (serializer, connectionSettings)
        => new JsonNetSerializer(serializer, connectionSettings))
    .BasicAuthentication("elastic", "elastic");
var client = new ElasticClient(settings);
var doc = new DocumentModel { Timestamp = DateTime.UtcNow, DocumentName = "Doc 1" };

await client.IndexAsync(doc, descriptor => descriptor
    .Index("my-index")
    .Refresh(Refresh.True)
);

var countResponse = await client.CountAsync<DocumentModel>(descriptor => descriptor
    .Index("my-index")
);
long totalDocs = countResponse.Count; // totalDocs = 1

var searchResponse = await client.SearchAsync<DocumentModel>(descriptor => descriptor
    .Index("my-index")
    .Query(q => q
        .DateRange(range => range
            .Field(model => model.Timestamp)
            .GreaterThan("1970-01-01"))
    )
);
int count = searchResponse.Documents.Count; // count = 0

The poco model:
public class DocumentModel
{
    [JsonProperty("@timestamp")]
    public DateTime Timestamp { get; set; }

    [JsonProperty("document_name")]
    public string DocumentName { get; set; }
}

Notice that the date range filter uses the lowercased Timestamp property name, not @timestamp from the [JsonProperty] attribute:

POST https://localhost:9200/my-index/_search?typed_keys=true HTTP/1.1
Accept: application/json
Content-Type: application/json
User-Agent: elasticsearch-net/7.0.1 (Microsoft Windows 10.0.17134; .NET Framework 4.7.3416.0; Nest)
Authorization: Basic ZWxhc3RpYzplbGFzdGlj
Host: localhost:9200
Content-Length: 53

{"query":{"range":{"timestamp":{"gt":"1970-01-01"}}}}

Also the documentation for 7.x seems not updated yet?
It still mentions Newtonsoft Json which is removed completely now?

@kpstolk You are correct, this needs to be updated

Opened https://github.com/elastic/elasticsearch-net/pull/3942 to address


Show invalid login error

When login fails (such as an invalid password) it currently takes the user to the failure callback of the application. I think it would be a much better user experience if mistyping a password allowed the user to stay on the login form with a nice error message saying it's invalid. Isn't this how most providers behave?

+1

+1

Perhaps this was a problem in 2011 but it's difficult to do with >= v1.1.0.
I suspect it would be good idea to start a wiki to document how to handle common use-cases.

Latest release has this feature.


yq is a hard requirement for make

Running make on a fresh build requires yq to even pull down devbase. There is an asdf plugin for yq, but it installs the Go yq and not the Python yq (and I believe that the Python yq is expected).
In the short term, this hard dependency should be documented. For the long term, should this be an be an asdf plugin of its own, or should the project move to the Go yq which is much more portable and doesn't require Python.

Agreed, we actually have a wrapper to support both but it's used only in limited cases. This one definitely belongs in devbase though, so I'm going to move it there.
My one issue with the go yq is that it decided to make it's own interface instead of keeping what jq had. Very sad about that.


Params name style convertion

dataclass_factory does converion of dataclass fields between naming styles: e.g. snake_Case to CamelCase.
We need this feature also for query params.


Update type hint readme for return any cases

What is the context of this PR?
Adds changes to readme content about type ignores of returning Any as requested on the card, some minor style fixes added to make it more readable which can be reverted
How to review
Read the new text and add your opinions if anything needs changing.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Update type hint documentation for return any cases (1 SP)


actually making it work

The current module does not work with the latest AVP in-sync hub or AVPlayback V2

Clips must be referenced like 01 or 02, not 1 or 2... Updated labels to reflect as such, defaults and switched to regex_string
Many commands that were added did not even exist in the AVP docs or were missing Pgm/Prv
CMD must have space appended (not sure why it is the only way it seems to work)
Added the rest of the commands from the AVP protocol documentation

I had not tried those. In the end I am not sure if it matters which we use if it works since it is not causing causing problems in future content and commands or how the command operated.
I will get the rest of the requests fixed up tonight. My apologies for jumping around accounts too.
My only worries are that he will update the software to actually reflect the documentation and not require a space or whatever is causing the need for it.
At the very least we want the additional commands and the few other commands that did not even exist updated (start and pause vs PgmStart/PrvStart and PgmStart/PrvStart) and added.

Update the to resolve your requested changes. Thanks


libxkbcommon: 1.2.1 -> 1.3.0

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121499 at 42df1f8b run on x86_64-linux 1

536 packages marked as broken and skipped:

adoptopenjdk-hotspot-bin-13
adoptopenjdk-hotspot-bin-14
adoptopenjdk-jre-hotspot-bin-13
adoptopenjdk-jre-hotspot-bin-14
adoptopenjdk-jre-openj9-bin-13
adoptopenjdk-jre-openj9-bin-14
adoptopenjdk-openj9-bin-13
adoptopenjdk-openj9-bin-14
agdaPackages.iowa-stdlib
aldor
...

4145 packages skipped due to time constraints:

AusweisApp2
DisnixWebService
MIDIVisualizer
OSCAR
R
SDL2_gfx
SDL2_mixer
SDL2_net
SDL_gpu
Sylk
...

21 packages built successfully:

SDL2
SDL2_image
SDL2_ttf
adoptopenjdk-bin (adoptopenjdk-hotspot-bin-11 ,openjdk11-bootstrap)
openjdk16-bootstrap (adoptopenjdk-hotspot-bin-15)
openjdk8-bootstrap (adoptopenjdk-hotspot-bin-8)
chromaprint
clickclack
ffmpeg (ffmpeg_4)
gtk3 (gnome3.gtk ,gtk3-x11)
gssdp
gst_all_1.gst-libav
gupnp
gupnp-igd
libdbusmenu-gtk3
libxkbcommon (libxkbcommon_8)
openconnect (openconnect_gnutls)
sdlpop
stoken
usbview
yapesdl