install error

composer require felixfbecker/language-server
I got following output error:
composer require felixfbecker/language-server
Using version ^5.4 for felixfbecker/language-server
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - felixfbecker/language-server v5.4.6 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - felixfbecker/language-server v5.4.5 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - felixfbecker/language-server v5.4.4 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - felixfbecker/language-server v5.4.3 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - felixfbecker/language-server v5.4.2 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - felixfbecker/language-server v5.4.1 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - felixfbecker/language-server v5.4.0 requires jetbrains/phpstorm-stubs dev-master -> satisfiable by jetbrains/phpstorm-stubs[dev-master] but these conflict with your requirements or minimum-stability.
    - Installation request for felixfbecker/language-server ^5.4 -> satisfiable by felixfbecker/language-server[v5.4.0, v5.4.1, v5.4.2, v5.4.3, v5.4.4, v5.4.5, v5.4.6].

Installation failed, reverting ./composer.json to its original content.

My system: Arch Linux Linux dark 4.19.2-arch1-1-ARCH
php -version
PHP 7.2.12 (cli) (built: Nov  6 2018 15:07:37) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies

I ran in the same issue, trying to have the server installed somewhere out of any project.
You need to have a basic composer.json file with the following :
{     "minimum-stability": "dev",     "require": {     } }

Thanks, this fixed my problem.


remove ArrayBuffer.transfer

The proposal has been withdrawn, so we can remove it.
https://github.com/tc39/proposals/blob/ee9b3204622e5d488dbf26eda87e51a117a4529a/inactive-proposals.md

:shipit:

Superseded by #3621


refactor cluster::rnd_idx to avoid overflow

The current impl for the LoadBalancerStrategy::Random has risk of overflow (and does so often) This reworks it to avoid the multiplication.

@rrichardson good catch and elegant solution! Thank you.
Could you please take a look on code formatting? We have a step in CI which checks code formatting. What it complains now is following
Diff in /home/travis/build/AlexPikalov/cdrs/src/cluster.rs at line 152:
             assert_eq!(&nodes_c[i % 3], load_balancer.next().unwrap());⏎
         }⏎
     }⏎
-    ⏎
+⏎
     #[test]⏎
     fn lb_random() {⏎
         let nodes = vec!["a", "b", "c", "d", "e", "f", "g"];⏎

Looks like a trailing spaces within an empty row


Fail earlier when found database schema dismatch

Coverage decreased (-37.6%) to 18.664% when pulling 659c11b00ccc8ec4280d7b5c9b36480bec528b08 on ywk253100:171102_fail_earlier into f7967e22abcf9ceb6affa1133a0238e21abb41ce on vmware:master.

Coverage increased (+0.01%) to 56.196% when pulling c6504924d82af36677498c6dd3d6e56398e4ce4a on ywk253100:171102_fail_earlier into 6a9dc8a133443daece139b953d6def82e8d4cb13 on vmware:master.

Coverage decreased (-0.04%) to 56.196% when pulling 5293a9287b0f50a6c8a300e04aa992703815b605 on ywk253100:171102_fail_earlier into 7a4a66cbd95af43a239921f165633983709d50d2 on vmware:master.


Internationalization

Note: I’ll use “i18n” instead of “internationalization”.
So let’s be honest, this issue will quite probably stand as “The Readium CSS issue” since it is roadmap-blocking, is impacting other parts of Readium 2 (streamer, navigator, API, apps developed by EDRLab), and will need a lot of documentation. In other words, it’s a project on its own, nested in the Readium CSS project.
I’ve spent the last 3 weeks documenting this issue, and you can think of it as a summary of the research that has been done. I won’t list everything there but only what is critical to provide implementers and readers with a solid baseline. I’m willing to make this baseline the best we can get (say, bulletproof although rough around the edges) but it’s worth noting we’ll need help from experts in those various and diverse languages and their typography to turn it into an excellent user experience.
Roadmap
First and foremost, I’d be in favor of updating our current roadmap. Vertical writing is indeed blocking and I’d like to move it to the beta version.
What it means is that we could ship support for horizontal-tb CJK, Right to Left and Indic languages in the alpha version relatively quickly, and then focus on vertical-writing, since our work on a11y baseline has been ahead of time since the beginning of this project.
I believe we would all probably agree that the prototype has proved a solid-enough bedrock – of course we have edge cases to deal with but it’s fine for the vast majority of contents – and pushing the small and easy wins for RTL/horizontal-tb CJK/Indic on the develop branch would allow us to release an alpha on the master branch early 2018. This would probably send a good signal too since the proto has been released 3 months ago already.
On a related note, we’ll start documenting columns handling (e.g. page progression) in January 2018 so it would make sense to prioritize LTR/RTL (horizontal-tb), especially as we’ll be able to document vertical-writing immediately after – quite frankly, this will be critical since they are conceptual changes to take into account.
Global needs outscoping Readium CSS
Obviously, Readium CSS won’t be able to fly in autopilot mode there. It needs either flags it can target or smart handling of its resources depending on the publication.
Minimal set of features
What we’ll need:

checking the page-progression-direction for the spine (streamer);
checking the language, and they can be multiple <meta> (streamer);
loading specific stylesheets based on those previous indications (API);
appending xml:lang and/or lang attribute if it’s missing in XHTML documents (API);
appending dir="rtl" attribute if it’s missing in XHTML documents (API);
loading specific fonts’ lists for user settings, based on language (Apps);
adding/removing specific user settings, based on language (Apps);
having the toc and at least some pieces of user settings (e.g. text-align) with a rtl direction for RTL languages (Apps);
page-progression from right to left (navigator).

A longer-term issue will be localization, should you want to get this need covered in the apps, as implementers might want an easy way to translate strings, etc. But it’s up to EDRLab, obviously.
Writing-mode and RTL mapping
For writing mode, those are the writing-mode we should apply based on the language and page-progression-direction:

Language
ISO code
page-progression-direction
Writing-mode

Chinese
zh
LTR / Default / None
horizontal-tb

Chinese
zh
RTL
vertical-rl

Chinese (Simplified)
zh-Hans
DNA (?)
horizontal-tb

Chinese (Traditional)
zh-Hant
DNA (?)
vertical-rl

Chinese (Taiwan)
zh-TW
LTR / Default / None
horizontal-tb

Chinese (Taiwan)
zh-TW
RTL
vertical-rl

Chinese (Hong Kong)
zh-HK
LTR / Default / None
horizontal-tb

Chinese (Hong Kong)
zh-HK
RTL
vertical-rl

Hangul
ko
LTR / Default / None
horizontal-tb

Hangul
ko
RTL
vertical-rl

Japanese
ja
LTR / Default / None
horizontal-tb

Japanese
ja
RTL
vertical-rl

Mongolian
mn
DNA
vertical-lr

I propose we simplify this model for Chinese and rely on page-progression-direction with an extra check for language (zh), and not bother with all those variants.
It’s worth noting we should not add dir="rtl" there, for the CJK languages.
In Right to left, we can simply rely on page-progression-direction, if the language is not CJK (and Mongolian) but here is a mapping of languages you might encounter, just for your information:

Language
ISO code
page-progression-direction
dir attribute

Arabic
ar
RTL
rtl

Assyrian
aii
RTL
rtl

Azeri^1
az
LTR / Default / None
ltr

Azeri^1
az
RTL
rtl

Bakhtiari
bqi
RTL
rtl

Balochi
bal
RTL
rtl

Eastern Cham
cjm
RTL
ltr

Western Cham
cja
RTL
rtl

Dhivehi/Maldivian
dv
RTL
rtl

Farsi (Persian)
fa
RTL
rtl

Gilaki
glk
RTL
rtl

Hebrew
he
RTL
rtl

Javanese^3
jv
LTR / Default / none
ltr

Javanese^3
jv
RTL
rtl

Kashmiri
ks
RTL
rtl

Kazhak^3
kk
LTR / Default / none
ltr

Kazhak^3
kk
RTL
rtl

Kurdish
ku
RTL
rtl

Malay^3
ms
LTR / Default / none
ltr

Malay^3
ms
RTL
rtl

Malayalam^3
ml
LTR / Default / none
ltr

Malayalam^3
ml
RTL
rtl

Mandekan (N’ko)
Nkoo
RTL
rtl

Pashto
ps
RTL
rtl

Punjabi
pa
RTL
rtl

Qashqai
qxq
RTL
rtl

Sindhi
sd
RTL
rtl

Somali^2
so
LTR / Default / none
ltr

Somali^2
so
RTL
rtl

Sulu (Tausug)
tsg
RTL
rtl

Syriac
syc
RTL
rtl

Takestani
tks
RTL
rtl

Tamasheq
taq
RTL
rtl

Turkmen
tk
RTL
rtl

Uyghur
ug
RTL
rtl

Urdu
ur
RTL
rtl

Yiddish
yi / ji
RTL
rtl

^1. Azeri is written in Latin, Cyrillic or Arabic scripts (therefore only Arabic will use RTL).
^2. Somali is typically written in the Latin script today (but you might want to take very old books into account).
^3. These languages were historically written in the Arabic script, but use another script in modern practice (once again you might want to take very old books into account).
Right to Left
This shouldn’t be a huge issue in Readium CSS, as we only need a few adjustments, specific base and default styles, and typefaces.
Hopefully, this doesn’t impact our views (paged and scrolled) since columns will behave as expected.

CJK (horizontal-tb)
Similar to RTL: we only need a few adjustments, specific base and default styles, and typefaces.
This should already provide support for the vast majority of contents in Chinese (vertical-writing is not used in mainland China, but only in Taiwan, Hong Kong and Macao), and Korean.
Chinese, Japanese and Hangul share a lot in terms of typography but having a few adjustments for each language would be a plus since differences are quite minor.
Other languages
For the time being, we’re only focusing on Devanagari, which should not have a huge impact. Once again, we’ll need a few adjustments, with the main focus being typefaces.
Vertical Writing
This is by very far our biggest issue in Readium CSS since we can’t necessarily manage that well, cross-platform-wise.

Note: The only alternative to solve those issues at the moment would be writing a renderer in JavaScript. It’s worth noting that if you’re only targeting iOS, there is a solution in pure CSS though.
What’s even worse is that the same typefaces can’t necessarily be used (proportional/fixed-width depending on writing-mode), and I’ll have to make adjustments for quotes and other details in the base and default stylesheets based on writing-mode…
Note: We won’t try to manage horizontal-tb documents in vertical-rl publications in a smart way for the time being. This use case is indeed not defined in the EPUB spec. Besides, we’ve got nothing at the OPF level to deal with it, and checking the writing-mode during runtime will blow performance in extreme ways i.e. 15 seconds to render some XHTML files… which would be worse than supporting this use case in terms of UX.
Longer terms issues include:

polyfilling -epub-properties for web apps;
support for alternate stylesheets (which is critical if the implementer wants to offer a horizontal/vertical-writing user setting);
support for rendition: align-x-center;
support for ibooks:respect-image-size-class (gaiji) and ibooks:scroll-axis metas (see EPUB Compat doc);
user settings (some like letter- and word-spacing might have to be removed, and not only for CJK);
rendition: flow of scrolled-doc.

Out of scope
There are some typography and layout issues which are not our responsibility but rendering engines’. Those issues include:

line-adjustment and justification (RTL and CJK);
run-in headings (display: run-in), which is popular in CJK;
ruby and its styling;
bidi;
Kashida Elongation (Arabic);
joining forms (Arabic);
single-letter styling (Arabic).

Documentation
In theory, I would only have to document the new fragmented scrolled-view model for vertical-writing, and adjustments for user settings.
In practice, I’m willing to go the extra mile and will document typographic and layout concepts, and make glossaries, so that Western implementers have everything at hand to deal with requirements and issues in CJK and languages they might not be familiar with.
This will obviously take time but will fix a huge pain point.
Overarching Issues

We don’t have any text layout requirement for hebrew, we’ll need help
Hangul, Chinese, Arabic and Indic Text Layout requirements are incomplete, we’ll have to keep track of updates and changes
We have not defined a precise baseline for i18n, it may be wise to do it
It would be useful to have data about writing-mode, RTL, typefaces used/expected, etc.

Resources

W3C Internationalization Working Group Home Page
Creating HTML Pages in Arabic, Hebrew and Other Right-to-left Scripts (tutorial)
Styling vertical Chinese, Japanese, Korean and Mongolian text
International text layout and typography index
Requirements for Japanese Text Layout
Requirements for Chinese Text Layout
Requirements for Hangul Text Layout
Requirements for the Arabic Script
Requirements for Hebrew Text Layout
Requirements for Indic Text Layout
EBPAJ File creation guide

I recommend using BCP47 language tags for language identification (per HTML standard).  That would allow you for example to refer to az-Latn vs az-Arab vs az-Cyrl above. For more info about BCP47 language tags see https://www.w3.org/International/articles/language-tags/

Javanese^3 | jv | RTL | rtl

I'd have thought that Javanese written in the Javanese script (ltr) was more likely to be encountered than written in the arabic script. (See https://r12a.github.io/scripts/javanese/ for info about the Javanese script.)

Forgive my ignorance, but are you using XHTML only?  HTML5 has a number of important additions for support of bidirectional text, introducing control for directional isolation and auto-detection of base direction for injected text. For more information see https://www.w3.org/International/articles/inline-bidi-markup/ (updated just now).  Hope these comments are helpful.

@R12a Oh yeah that’s super useful, thank you!
To answer your questions:

your first comment made me second check the EPUB specs for the language metadata of publication, and it turns out the value must be conforming to rfc5646 so I can’t even tell why I listed ISO codes in the first place. So thank you for pointing that out.

I’ve indeed had doubts about Javanese when checking multiple references. To sum things up, I took a look at the Script direction and languages doc and may have misunderstood the footnote, then I checked others docs in which LTR was mentioned so thank you for clarifying this.

In EPUB 3, documents must be HTML5 documents that conform to the XHTML syntax. Does this imply we will benefit from those additions? There indeed were talks about having HTML as a core media type but it was rejected for EPUB 3.1.

We’ll have an issue with Arabic in EPUB 2 though.
Yesterday Kevin Callahan triggered what appeared to be a bug in iBooks at first sight. Except it wasn’t.
To sum things up, the EPUB opened backwards (as if page-progression-direction="rtl" were set on the spine). Turns out the app used the last language element it found in the metadata, which was ar-SA, to render that.
Which reminded me EPUB 2 doesn’t have this page-progression-direction attribute, but supports anything else needed for Right-to-Left (including the dir attribute and the direction CSS property). I can indeed remember EPUB 2 publications in Arabic (at some point, a prospect asked if I could do that and after checking who could do that, I discovered services offering EPUB2 output).
What it means:

there are major Reading Systems supporting RTL in EPUB 2;
content providers have been probably using this version because it just works;
the only hint we get is the language then;
we don’t know what’s the main language is when multiple elements are declared;
I couldn’t find any guidance on multiple elements handling in the specs (yet);
if there are no guidance, it explains the huge interoperability issues† authors have to deal with.

How should we handle this case then?

† Footnote

Authors putting all the authors in the same meta element or else only one will be displayed in the running header.
Nobody agreeing whether you should have one element per keyword or all keywords in the same subject element (separated with commas or semi-colons).
Multiple languages, for which you don’t know how to order them since some RS may take the first one they can parse, and others will take the last one – and I’ve just discovered Kindle imposes authors to use the main one only, at least in some cases, or their KDP validator will throw an error.

After further testing, this is how iBooks and Readium handle this particular case (with 2 <dc:language> declarations):

Reading System
EPUB version
Trusted language
page-progression-direction
rendition
User Settings

iBooks
2.0.1
last value
No
language value
language value

Readium
2.0.1
none
No
LTR
DNA

iBooks
3.0.1
last value
No
language value
language value

Readium
3.0.1
none
No
LTR
DNA

iBooks
3.0.1
last value
Yes
page-progression-direction
language value

Readium
3.0.1
none
Yes
page-progression-direction
DNA

My file is EPUB3, FYI. And now I’m glad to know how iBooks decides which language + reading direction to use. Thanks.

On Dec 23, 2017, at 5:39 AM, Jiminy Panoz<EMAIL_ADDRESS>wrote:
We’ll have an issue with Arabic in EPUB 2 though.
Yesterday Kevin Callahan triggered what appeared to be a bug in iBooks at first sight https://twitter.com/BNGOBooks/status/944260033973506048. Except it wasn’t.
To sum things up, the EPUB opened backwards (as if page-progression-direction="rtl" were set on the spine). Turns out the app used the last language element it found in the metadata, which was ar-SA, to render that.
Which reminded me EPUB 2 doesn’t have this page-progression-direction attribute, but supports anything else needed for Right-to-Left (including the dir attribute and the direction CSS property). I can indeed remember EPUB 2 publications in Arabic (at some point, a prospect asked if I could do that and after checking who could do that, I discovered services offering EPUB2 output).
What it means:
there are major Reading Systems supporting RTL in EPUB 2;
content providers have been probably using this version because it just works;
the only hint we get is the language then;
we don’t know what’s the main language is when multiple elements are declared;
I couldn’t find any guidance on multiple elements handling in the specs (yet);
if there are no guidance, it explains the huge interoperability issues† authors have to deal with.
How should we handle this case then?
† Footnote
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/readium/readium-css/issues/26#issuecomment-353719271, or mute the thread https://github.com/notifications/unsubscribe-auth/APegmJTE_3R64KGjxdfLVIhTWQgSk9QJks5tDNhxgaJpZM4Q_FOY.

Ah thanks for the clarification that I should have made myself in the previous message.
So yeah, I can confirm that their strategy is trusting the last <dc:language> it can get (if there is no page-progression-direction set for the spine).

Took a quick look at the iBooks doc to check some details related to rendition and oh boy do they put the burden on authors.

Language:

it should be declared twice, in the OPF and iTunes Metadata, and values must match – I guess it helps them sanitize the OPF when several <dc:language> can be found since authoring software can output multiple values without the author even knowing;
for Chinese language books, you must specify both the language (zh) and the script (Hans or Hant) portions of the language code.

Text direction:

each content document can support a single writing-mode value. If you want both horizontal and vertical text in your book, then each text direction must be split into separate content documents;
if the Table of Contents in the iBooks menu needs to be rendered vertically as opposed to horizontally, the text direction must be specified for the TOC in the Navigation document.

Scroll:

by default, Japanese and Chinese books scroll horizontally, while all other languages scroll vertically;
to redefine the scroll direction, the book must include the following metadata in the .opf file: ibooks:scroll-axis. Possible values are vertical, horizontal, and default.

What worries me lotbits is that this is consistent with the issues we quickly discovered when starting work on vertical writing in the EPUB context (paginated, page-progression, mixed writing-modes, etc.) and they put constraints we can’t necessarily.
It also reminds me the Japanese industry is pushing for the EPUB 3.2 revision while the current spec is barely vertical-writing-friendly. I mean, I’m pretty sure lots of contents relying on the -epub-writing-mode CSS property, which hangs by an alias Webkit deigned to implement for iBooks back in the early EPUB3 days.
The constraints Apple has designed, they’re just here to fill the spec gaps – but we’ll have to design heuristics because we simply can’t do that. cc @llemeurfr

Added control captures for i18n samples. They are all available in the i18n folder.
I can’t tell whether we have any issue for text rendering or not. So any review would be greatly appreciated since I can tell for sure that only Mongolian doesn’t render as expected (we have no system font to manage that).
Tests those capture cover:

pagination;
specific font-stack for each language (base module);
direction (lrt/rtl);
writing mode (horizontal/vertical);
default for unstyled ebooks.

@JayPanoz, in the scope of the EPUB 3.2 revision, can you define what would be useful for handling vertical writing perfectly (or at lest better)?

Yeah no problem.
1/ I’ve already raised an issue about multiple metadata elements and the lack of guidance a.k.a. “which one should be considered the primary language?” on the EPUB-revision issue (<dc:language>) as it is part of this more global issue: https://github.com/w3c/publ-epub-revision/issues/992
In practice, vendors already have to deal with this, and may impose constraints to authors, e.g. only one language item, specifying the Han Traditional or Han Simplified script for Chinese, using another prefixed meta to force direction of scroll, etc.
But that’s only because there is no better way to know we should use vertical-writing from the OPF…
2/ We quickly discussed something like page-progression-direction but for vertical writing in the OPF with @HadrienGardeur during our meeting with Florian. But I’m not sure people will warmly welcome yet another rendering meta.
The thing is it’s unrealistic to use the writing-mode computed style at runtime, as it imposes a huge burden both on authors (time to rendering is abysmal, like 5–10 times more than when written horizontally) and users (UX).
3/ Then there are the mixed directions and writing-modes issues i.e. when the dir or writing-mode of a whole document/XHTML file differs from the one we can get from page-progression-direction.
A warning/note that all reading systems can’t necessarily manage those cases would be the least the spec can do, and authors must be extra cautious about that. It currently isn’t discussed at all, and the process just started for Web Publications – but impacts EPUB3 as well.

Oh and yeah, a super important one.
4/ Authors shouldn’t rely on -epub-properties and as guidance, should use all the needed prefixed properties (-ms-, -webkit-, -moz-) + the standard whenever needed. We have an increasingly corpus of files which don’t, and it builds a huge debt for everyone.

Hi Jiminy,
Just for your info, be careful with prefixed properties, as Google asked us to remove every prefixed properties except those used by them (i.e.  -webkit- ), because their programs didn't ingest correctly our files (it's new).
So we have to remove any  -ms- and  -moz-  existing in our files...
Vincent
EUB3 ISIcrunch platform for education

Well, thanks for the info.
If that’s Google Play Books, they’re consequently creating an interoperability issue – and we already have an awful lot because vendors decide to do such stuff unilaterally. It also breaks yet another fundamental rule of CSS, and change the way it is working so this is bad. This should be raised at a higher level, because it impacts the whole ecosystem and, more importantly, competitors.
How are they parsing CSS in the first place?

Opened a specific issue (#32) about prefixed properties as we’d better keep this one for i18n only.

Oh joy… Kindle being Kindle all over again:

If the page propagation direction is not left-to-right, page propagation direction should be provided either in the metadata or the spine. (Example: <meta name="primary-writing-mode" content="horizontal-rl"/>)

it’s interesting they called that primary-writing-mode (emphasis on primary)
horizontal-rl doesn’t exist in the CSS spec
Why offering an alternative to <spine page-progression-direction="rtl"> in the first place? (and yeah, possible future interop issue…)

To clarify, I would not necessarily worry about that in the short term. If you ask me “do we need to support that?”, my answer would be “No, not at the moment.”
Now, [company we shouldn’t name] happens to finally care about internationalization after a decade of not caring at all. And if you had to support right to left scripts in the easiest way possible, a way that’s EPUB2-compatible and won’t raise an ePubCheck issue, a way that doesn’t require extra namespaces and doesn’t disrupt workflows, etc., guess what you’ll end up with? Yes, a <meta> in the .opf.
In other words, in the longer term, my answer could become “yes, we need to support that, because usage is significant.” But that’s relatively new, so we should probably keep in on our radar and that’s it.

see also https://github.com/readium/readium-css/wiki/Internationalization,-pagination-and-user-settings


Add IBM Clearcase version

This pull request adds "In case of fire" instruction for clearcase users

@OpenNingia Thanks!


jibs war support doesn't play well with the spring boot gradle plugin

When the war and org.springframework.boot plugins are both applied to a gradle project, the latter disables the war task and registers a bootWar task instead.
jib should therefore use the bootWar task in this case.

@larsgrefer Thanks for the contribution, v1.4.0 has been released with the fix!


Fix ensure with nonstandard versions

This increases support for DragonFly BSD as well as FreeBSD, making
them first class citizens for this module. Additionally, it creates a
new structured fact called perl, which contains the various version
numbers that can be referenced for what version of Perl is the system
default. It was mainly added to properly support the config paths for
the default @INC on DragonFly and FreeBSD. The cpan provider was
updated to fix a few bugs around how it handled version strings, and
using rubocop, some additional cleanup was done while there.

@strangelittlemonkey thanks for the PR.
It would be better to seperate the changes in this PR into multiples PRs so that it can be reviewed easily. For example support for BSD should not include rubocop fixes, etc...
By the way the tests are failing, and adding tests for the new features would be awesome too :)
Thanks for the understanding

The tests are failing on the master branch without this. I can fix them as they stand in that and break that into a separate PR to precede this.

I've separated them out into two PRs now.

Please fix the failing tests

There are insterestinf features in this PR (perl version fact, new os support).
I took ownership of this @strangelittlemonkey are you still interested to merge this ?


Creating first and basic swagger for new RP of ASI (Azure Security In…

…sight).
This RP is an extension RP of "Microsoft.operationalinsights", and it is coupled to a Log analytics workspace.
This is a first iteration in order to create a simple RP with single endpoint, after it wil work the API will be changed with the actual and full endpoints based on the learnings from this POC.
There is only one endpoint for alertRules that will be changed in the future.
I validate the swagger with autorest azure guidelines.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-go

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Hello!!
The Rest API Specs team wishes everyone a happy holiday and would like to kindly inform you that responses and review to Pull request will be delayed during the holiday period (now -> 2nds of January) to allow for Awesome reviewers to have an awesome time with their families during the holidays!
Thanks and Have a WONDERFUL HOLIDAY

Can one of the admins verify this patch?


added imgui.ini to .gitignore

Added "imgui.ini" to ".gitignore" ... Closes #202

We do want an imgui.ini file committed, we just don't update it, as cherno mensioned for example on discord:

But this can lead to several problems, like:
What if somebody who commits changes to the repository and has his ImGUI windows moved over to his 2nd screen and somebody with just one screen clones it? then the ImGUI windows will be shown outside his screen and will be "unreachable" unless he deletes the imgui.ini file :thinking:

What if somebody who commits changes to the repository and has his ImGUI windows moved over to his 2nd screen ...

We check the files before merging a PR in. Even then, it's easy to revert. We can also add our own ini files to imgui, but we're just letting imgui handle it for now.


When displaying license info to user, show Id and displayName if available

Are you going to include this one in 4.31?


Regex-based routes in site.yaml match but cause 502 error

I am experiencing almost the same error as described by another person recently on Grav Forums.
My relevant site.yaml is:
routes:
  /blog/category/(.*): '/blog?category=$1'

I see "502 Bad Gateway" from nginx and the logs show:
2018/06/30 21:08:42 [error] 1321#0: *1727 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: <IP_ADDRESS>, server: grav.dev, request: "GET /blog/category/blog HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "grav.dev", referrer: "http://grav.dev/blog/random-thoughts"
I have also tried with a slash after "/blog" before the query. Also tried the regex in single quotes.
This is exactly as documented in Regex based aliases in the docs.
I know the regex is matching because when I tweak it incorrectly I see 404s.

502 errors are usually related to Nginx -> PHP-FPM communication. Unfortunately i don't use Nginx day-to-day so am no expert at it.  Maybe this will help?
https://www.datadoghq.com/blog/nginx-502-bad-gateway-errors-php-fpm/

I tried with PHP 5.6 + Apache and PHP 7.2 +Nginx and I have the same result:
on Apache
Whoops \ Exception \ ErrorException (E_ERROR)
Maximum execution time of 90 seconds exceeded

on: Nginx "502 Bad Gateway".
Basically I wait for several seconds and then get this message.
Can you verify Regex-Based aliases on latest version of Grav please?

Can you reach the before and after URLs directly? its only the 'redirect' that causes issues?

I can reach after URL directly (/blog?category=blablabla in the above example), not the before URL (/blog/category/blablabla).

If you create a physical page in Grav with route at that URl /blog/category/blablabla can you reach it?

Yes, sure.

The TLDR of this is that I have repeatable steps. However, please try taking in the confusing detail :)
I tested the official Quark-themed blog skeleton demo, which contains a dummy route:
  /another/one/(.*): '/blog/$1'

and you can see it works: https://demo.getgrav.org/blog-skeleton/another/one/hero-classes
I also tried that locally and it works, so the regex expression seems unlikely as a culprit.
But you can also witness that the tags with URL "params" do work: https://demo.getgrav.org/blog-skeleton/tag:photography
There is no route configured in the skeleton for that path, so I surmised that a plugin I don't know like taxonomylist or simplesearch had defined it. I tried disabling these two plugins locally and still got the Nginx 502 gateway error.
For accurate comparison across environments, I downloaded and installed the blog skeleton.
/another/test/hero-classes worked unsurprisingly, as did the /tag:photography path (so whatever else is routing this works on my local env). However, when I added a query in the redirect, I got the 502 error. So this is replicatable:

download and install grav-skeleton-blog-site
add /yetanother/test/(.*): '/blog?category=$1' to the routes and load up /yetanother/test/photography
you can make the "rewrite" '/blog?foo=bar and you will get the same result
you can confirm that the rewritten URLs work when entered directly into the address bar

Doesn't clarify much for me, but I hope this helps a smarter person :)

Oh! This is just a matter of escaping the special chars in the regex with backslashes.
This string in the config is used directly as a regex so it has to be a valid regex.
Pretty sure this came up before.

Cool! Seems like we're close.
Can you help me with an example? On the right hand side, what am I escaping and for which parser? I've tried backslashing the slash, query, equals, and dollar.

Please help me how to escape this regex:
/yetanother/test/(.*): '/blog?category=$1'
I tried '/blog\?category=$1 with no results.
Thank you.

I finally tracked down the regex routing code in the source at around line 500 of Pages.php and did some logging, expecting this might be easy to figure out from there.
Just before $page = $this->dispatch($found, $all);, I inserted a line:
$this->grav['log']->info("\$pattern: $pattern; \$source_url: $source_url; \$found: $found");

I also inserted a line:
$this->grav['log']->info("dispatching: $route");

just after the first line of the method, around line 444.
My route regex is:  /blog/category/(.*): '/blog?category=$1'
and I tried accessing '/blog/category/x'.
The log showed repeated lines of:
[2018-07-08 13:43:49] grav.INFO: dispatching: /blog?category=x [] []
[2018-07-08 13:43:49] grav.INFO: $pattern: #^\/blog\/category\/(.*)#; $source_url: /blog/category/x; $found: /blog?category=x [] []

So it's almost certainly looping.
$source_url seems to "reset" on every invocation to the requested URL path around line 474, so $found is not being considered on the recursive call when it's $route. This is where I get lost as to what it's trying to do. I've edited a few of those parameters but the logic has not become apparent.
BTW in the grav logs when I enter the "target" URL '/blog?category=x' directly, I see:
[2018-07-08 14:15:20] grav.INFO: dispatching: /blog [] []
[2018-07-08 14:15:20] grav.INFO: dispatching: /blog [] []

which is not surprising.
So not as revealing as I hoped but hopefully helpful to someone who knows this code better.

Hello,
I'm pretty sure I'm having a similar issue.
Route defined in site.yaml:
/abc/123: /123

When trying to reach /abc/123/?foo=bar, Grav goes into infinite dispatch loop. Here's the dispatched routes in order:
/abc/123
/123
/abc/123/
/123/?foo=bar
/123/?foo=bar
/123/?foo=bar
/123/?foo=bar
/123/?foo=bar
// looping this until out of memory or execution time

The reason seems to be the one that @hughbris mentioned: when making the comparison of source and target uris on line 501, Grav is always using original uri instead of the one that was passed to dispatch method, and therefore there is a possibility to call the dispatch method with the same $route that was used when invoking the dispatch in the first place.
I'm not sure if the root cause of my problem is the same as yours (as this may be related to trailing slash logic), however, the end result is the same and there definitely is some sort of bug.

Hello,
I'm experiencing the same issue here. Just to keep the thread up.
As described in https://github.com/getgrav/grav/issues/2080#issuecomment-402006855 the same route is dispatched every time a query parameter is present in the replacement string.
Maybe the router needs some more logic especially for this kind of route.
My need was to plug an api client to inject custom content into some pages from the api. This content depends on the called page. I ended up by writing my own rule from a new plugin.
resources:
    "/foo/(?!(:*\?))([a-z0-9]+(?:-[a-z0-9]+)*)":
      page: '/foo/bar'
      endpoint : '/news/{uuid}'

public function onPluginsInitialized()
    {
        if ($this->isAdmin()) {
            return;
        }

        /** @var Uri $uri */
        $uri = $this->grav['uri'];
        $resources = $this->config->get('plugins.api-client.resources');

        foreach ($resources as $pattern => $config) {
            $pattern = '#^' . str_replace('/', '\/', ltrim($pattern, '^')) . '#';
            preg_match($pattern, $uri->path(), $matches);

            if (!empty($matches)) {
                $this->endpoint = str_replace('{uuid}', end($matches),$config['endpoint']);
                $this->page = $config['page'];
                $this->enable([
                    'onPageInitialized' => ['onPageInitialized', 0],
                ]);

                return;
            }
        }
    }

Then I do my own logic into onPageInitialized
I know this is very specific to my needs and certainly could be improved but for now it's working for me and I would be happy if this helps someone

These days I run Grav from a Docker image and I believe this will finally provide a simple means for @rhuk and other maintainers to reproduce this.
I've just tried the (common!) regex redirect pattern listed above for the first time since moving to Docker, and have confirmed that this bug still exists in 1.6.23.
To reproduce: install and run a container based on dsavell/grav, set up some basic pages using the regex pattern and hit them.
If you want me to craft a derivative with those routing test files set up for you, I am also happy to do that so that you can reproduce this bug.
(the uri.query bug #2090 is now safely out of the picture)


class_agnostic nms in rpn

Hi!
We train a instance segmentation network for multiple classes. For testing I found out that I need to set the nms to class_agnostic=True in order to perform nms among classes. This worked fine.
However, what about the nms during training in rpn_proposal? Here, I could also set class_agnostic=True but what does this mean in case of RPN? In my understanding the RPN only differentiates between object/no object and does not consider classes.
What would you recommend?
In our use case the Object Masks cannot overlap, however the bounding boxes could overlap partially.
Thank you!
Best regards

The rpn set fake labels according to feature map levels

you can find details at https://github.com/open-mmlab/mmdetection/blob/3b72b12fe9b14de906d1363982b9fba05e7d47c1/mmdet/models/dense_heads/rpn_head.py#L180-L183


Coverage: allow record example to pass whole directory rather than iterating it

LibFuzzer targets have the ability to consume a directory as a command-line input rather than being fed one input file at a time. Taking advantage of this has the potential to speed up coverage generation.

Codecov Report

Merging #3349 (eee86ca) into main (62c3f07) will decrease coverage by 1.36%.
Report is 7 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3349      +/-   ##
==========================================
- Coverage   31.83%   30.48%   -1.36%
==========================================
  Files         307      133     -174
  Lines       37358    14311   -23047
==========================================
- Hits        11894     4363    -7531
+ Misses      25464     9948   -15516

see 175 files with indirect coverage changes

This is also achievable by simply not using input_dir. Hmm.


TypeError with latest rev

I get this error with rev fb7c549
# adb-sync/adb-sync -s b780df65 -R /storage/emulated/0/ backup/storage/emulated/0/
INFO:root:Sync: local b'backup/storage/emulated/0/', remote b'/storage/emulated/0/'
Traceback (most recent call last):
  File "adb-sync/adb-sync", line 883, in <module>
    main()
  File "adb-sync/adb-sync", line 870, in main
    if not syncer.IsWorking():
  File "adb-sync/adb-sync", line 507, in IsWorking
    return self.adb.IsWorking()
  File "adb-sync/adb-sync", line 221, in IsWorking
    b'date +%s' % (self.QuoteArgument(test_string),)]) as stdout:
TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple'

# python3 --version
Python 3.4.2

Ah I've found out it seems my python 3.4 is too old.


update e2e tests for shared delegation

[x] update e2e tests for shared delegation

Comments

Issue Number
ADP-2602

bors r+


OAuth/ODIC - Azure AD authentication loop - Self-hosted Netbird

Describe the problem
After configuring a self-hosted netbird server with Azure AD OAuth, a login loop occurs when navigating to the netbird web interface. I get re-directed to the Azure AD login page for my Azure AD tenant as expected, authenticate, then get re-directed to Netbird, but then Netbird keeps trying to redirect me back to Azure AD. Azure AD already knows I'm authenticated then redirects me back, this causes a redirect loop over and over until Azure AD times out and throws an error that I could not be logged in.
To Reproduce
Steps to reproduce the behavior:

Navigate to your Netbird instance in a browser.
If you configured your setup.env file correctly, you should get re-directed to Azure AD SSO login to provide credentials. Login.
You should be re-directed to Netbird after login, but Netbird keeps re-directing back to Azure AD instead, Azure AD will re-direct back to Netbird because your already logged in, causing a re-direct loop until Azure AD times out and throws a login error.

Expected behavior
Navigating to the Netbird web interface on the server should redirect to Azure AD where user login occurs then the user should be re-directed back to the Netbird web console, logged in successfully.
NetBird status -d output:
If applicable, add the output of the netbird status -d command. Can't login to my VM from my current location at this time to run this command, I will need to wait until I am home from the office.

Followed this?
https://github.com/netbirdio/docs/blob/cb03373f8feb9da0204606ab055fa9825f0f9a26/docs/integrations/identity-providers/self-hosted/azure-ad.md
And make sure the to see if this was done:  "Modify the api scope within dashboard enviroment variable AUTH_SUPPORTED_SCOPES located in docker-compose.yml to api://<application_id>/api."

@Stunt0265 OMG thank you!!!

Hello @Stunt0265 we've updated the documentation and added integration to our management. Check it out here: https://docs.netbird.io/selfhosted/identity-providers#azure-ad


download client amarr places downloads in /finished

Hi there,
Finally, I got to configure the download client amarr in sonarr and radarr. But when the download finishes, sonarr doesn't import the download to the proper TV Show folder.
In the Activity tab, I can see this message

Which is also shown in the Sonarr and Radarr's health section.

You are using docker; download client amarr places downloads in /finished but this directory does not appear to exist inside the container. Review your remote path mappings and container volume settings.

I don't know where this /finished path is set, my guess is hardcoded into the amarr's docker, I've took a look into config/ directory, but there are just two files, categories.tsv and  hashes.tsv
Entering the running docker instance, I cannot see either the /finished directory.
My amule docker instance has this volumes mapped
    volumes:
      - '/data/.docker/amule/config:/home/amule/.aMule'
      - '/data/files/Downloads:/incoming'
      - '/data/files/Downloads/incomplete:/temp'

And when the file, downloaded with amule, via amarr/sonarr, is downloaded in my hosts' /data/files/Downloads or in my amule's /incoming...
As per this error, I can't even manually import the file

Any idea what could I do?

I've solved it by adding a new remote path mapping in Settings --> Download clients

Great! Another approach is to use the environment variable AMULE_FINISHED_PATH with amarr.
Example:
services:
  amarr:
    // ... omissis ...
    environment:
      - AMULE_FINISHED_PATH=/media/usb-luca/Adunanza/finished

I didn't remember that environment from the README... 🤦🏻


Fixing errors when using multiple contexts

Fixes #197
Also fixes missing cl_khr_fp64  failures on some devices.

All tests on my end passed. Thanks @pavanky and @shehzan10


Add "Manhattan distance" as an additional distance metric.

Currently, we can find cosine and l2-squared distance metrics. This PR attempts to add manhattan distance metric as well. This PR attempts to implement one of the distance metrics mentioned in this issue.

I agree with the CLA


Add pagination support

Add pagination support. This includes serverside changes on how the items are handled and a few changes to some global stylings.

LGTM


Fuchsia x86 builds on Mac fail to link.

I am pretty sure this is a Mac host specific issue as CI is fine and it may be that there is no Mac CI infra that builds Fuchsia artifacts.
ninja: Entering directory `out/fuchsia_debug_x64'
[143/3684] LINK ./fml_benchmarks
FAILED: exe.unstripped/fml_benchmarks fml_benchmarks
/Users/chinmaygarde/VersionControlled/depot_tools/.cipd_bin/gomacc  ../../buildtools/mac-x64/clang/bin/clang++ --target=x86_64-fuchsia --sysroot ../../fuchsia/sdk/mac/arch/x64/sysroot  -Wl,--fatal-warnings -m64 -Wl,-O2 -Wl,--gc-sections -Wl,--as-needed -o ./exe.unstripped/fml_benchmarks -Wl,--build-id=sha1 -Wl,--start-group @./fml_benchmarks.rsp  -Wl,--end-group ../../fuchsia/sdk/mac/arch/x64/lib/libasync-loop-default.a ../../fuchsia/sdk/mac/arch/x64/lib/libasync-default.so ../../fuchsia/sdk/mac/arch/x64/lib/libsyslog.so ../../fuchsia/sdk/mac/arch/x64/lib/libfdio.so ../../fuchsia/sdk/mac/arch/x64/lib/libtrace-engine.so && ../../buildtools/mac-x64/clang/bin/llvm-strip -o ./fml_benchmarks ./exe.unstripped/fml_benchmarks
ld.lld: error: undefined symbol: zx_clock_get_monotonic
>>> referenced by time_point.cc:21 (../../flutter/fml/time/time_point.cc:21)
>>>               obj/flutter/fml/time/fml.time_point.o:(fml::TimePoint::Now())
clang-13: error: ld.lld command failed with exit code 1 (use -v to see invocation)
[1141/3684] ACTION //third_party/dart/runtime/observatory:build_observatory(//build/toolchain/mac:clang_x64)
ninja: build stopped: subcommand failed.

Stubbing it out, it looks like a libzx is just not being linked at all.
$ ninja -C out/fuchsia_debug_x64 -j999
ninja: Entering directory `out/fuchsia_debug_x64'
[1/1] Regenerating ninja files
[129/615] LINK ./testing_unittests
FAILED: exe.unstripped/testing_unittests testing_unittests
/Users/chinmaygarde/VersionControlled/depot_tools/.cipd_bin/gomacc  ../../buildtools/mac-x64/clang/bin/clang++ --target=x86_64-fuchsia --sysroot ../../fuchsia/sdk/mac/arch/x64/sysroot  -Wl,--fatal-warnings -m64 -Wl,-O2 -Wl,--gc-sections -Wl,--as-needed -o ./exe.unstripped/testing_unittests -Wl,--build-id=sha1 -Wl,--start-group @./testing_unittests.rsp  -Wl,--end-group ../../fuchsia/sdk/mac/arch/x64/lib/libasync-loop-default.a ../../fuchsia/sdk/mac/arch/x64/lib/libasync-default.so ../../fuchsia/sdk/mac/arch/x64/lib/libsyslog.so ../../fuchsia/sdk/mac/arch/x64/lib/libfdio.so ../../fuchsia/sdk/mac/arch/x64/lib/libtrace-engine.so ../../fuchsia/sdk/mac/arch/x64/lib/libvulkan.so -ldl && ../../buildtools/mac-x64/clang/bin/llvm-strip -o ./testing_unittests ./exe.unstripped/testing_unittests
ld.lld: error: undefined symbol: zx_object_set_property
>>> referenced by object.h:63 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/object.h:63)
>>>               obj/flutter/fml/fml.thread.o:(zx::object_base::set_property(unsigned int, void const*, unsigned long) const)

ld.lld: error: undefined symbol: zx_handle_close
>>> referenced by object.h:79 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/object.h:79)
>>>               obj/flutter/fml/fml.thread.o:(zx::object_base::close())
>>> referenced by loop.c:194 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:194)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_destroy)
>>> referenced by loop.c:195 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:195)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_destroy)

ld.lld: error: undefined symbol: zx_port_create
>>> referenced by port.cc:12 (../../fuchsia/sdk/mac/pkg/zx/port.cc:12)
>>>               obj/fuchsia/sdk/mac/pkg/zx/zx.port.o:(zx::port::create(unsigned int, zx::port*))
>>> referenced by loop.c:171 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:171)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_create)

ld.lld: error: undefined symbol: zx_socket_create
>>> referenced by socket.cc:17 (../../fuchsia/sdk/mac/pkg/zx/socket.cc:17)
>>>               obj/fuchsia/sdk/mac/pkg/zx/zx.socket.o:(zx::socket::create(unsigned int, zx::socket*, zx::socket*))

ld.lld: error: undefined symbol: zx_timer_create
>>> referenced by loop.c:173 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:173)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_create)

ld.lld: error: undefined symbol: zx_pager_detach_vmo
>>> referenced by loop.c:692 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:692)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_shutdown)
>>> referenced by loop.c:679 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:679)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_detach_paged_vmo)

ld.lld: error: undefined symbol: zx_port_queue
>>> referenced by loop.c:468 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:468)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_wake_threads)
>>> referenced by loop.c:622 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:622)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_queue_packet)

ld.lld: error: undefined symbol: zx_port_wait
>>> referenced by loop.c:282 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:282)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_run)
>>> referenced by port.h:36 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/port.h:36)
>>>               libgtest.gtest-death-test.o:(testing::internal::FuchsiaDeathTest::Wait()) in archive obj/third_party/googletest/libgtest.a

ld.lld: error: undefined symbol: zx_clock_get_monotonic
>>> referenced by loop.c:502 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:502)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_run)
>>> referenced by loop.c:502 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:502)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_now)

ld.lld: error: undefined symbol: zx_object_wait_async
>>> referenced by loop.c:515 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:515)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_begin_wait)
>>> referenced by loop.c:749 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:749)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_restart_timer_locked)
>>> referenced by object.h:143 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/object.h:143)
>>>               libgtest.gtest-death-test.o:(zx::object<zx::process>::wait_async(zx::object<zx::port> const&, unsigned long, unsigned int, unsigned int) const) in archive obj/third_party/googletest/libgtest.a
>>> referenced 2 more times

ld.lld: error: undefined symbol: zx_port_cancel
>>> referenced by loop.c:547 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:547)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_cancel_wait)
>>> referenced by loop.c:735 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:735)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_restart_timer_locked)

ld.lld: error: undefined symbol: zx_guest_set_trap
>>> referenced by loop.c:636 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:636)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_set_guest_bell_trap)

ld.lld: error: undefined symbol: zx_interrupt_bind
>>> referenced by loop.c:775 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:775)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_bind_irq)
>>> referenced by loop.c:797 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:797)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_unbind_irq)

ld.lld: error: undefined symbol: zx_pager_create_vmo
>>> referenced by loop.c:656 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:656)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_create_paged_vmo)

ld.lld: error: undefined symbol: zx_timer_set
>>> referenced by loop.c:744 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:744)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_restart_timer_locked)

ld.lld: error: undefined symbol: zx_timer_cancel
>>> referenced by loop.c:730 (../../fuchsia/sdk/mac/pkg/async-loop/loop.c:730)
>>>               obj/fuchsia/sdk/mac/pkg/async-loop/async-loop.loop.o:(async_loop_restart_timer_locked)

ld.lld: error: undefined symbol: zx_task_kill
>>> referenced by task.h:31 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/task.h:31)
>>>               libgtest.gtest-death-test.o:(zx::task<zx::process>::kill() const) in archive obj/third_party/googletest/libgtest.a

ld.lld: error: undefined symbol: zx_socket_read
>>> referenced by socket.h:37 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/socket.h:37)
>>>               libgtest.gtest-death-test.o:(zx::socket::read(unsigned int, void*, unsigned long, unsigned long*) const) in archive obj/third_party/googletest/libgtest.a

ld.lld: error: undefined symbol: zx_object_get_info
>>> referenced by object.h:55 (../../fuchsia/sdk/mac/pkg/zx/include/lib/zx/object.h:55)
>>>               libgtest.gtest-death-test.o:(zx::object_base::get_info(unsigned int, void*, unsigned long, unsigned long*, unsigned long*) const) in archive obj/third_party/googletest/libgtest.a

ld.lld: error: undefined symbol: zx_job_create
>>> referenced by gtest-death-test.cc:1038 (../../third_party/googletest/googletest/src/gtest-death-test.cc:1038)
>>>               libgtest.gtest-death-test.o:(testing::internal::FuchsiaDeathTest::AssumeRole()) in archive obj/third_party/googletest/libgtest.a

ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
clang-13: error: ld.lld command failed with exit code 1 (use -v to see invocation)
[333/615] CXX obj/flutter/shell/platform/fuchsia/flutter/flutter_runner_sources.runner.o
ninja: build stopped: subcommand failed.

This is fixed.


Forum section needs to improve and proper

Is your feature request related to a problem? Please describe.
Needs to proper work
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Can you please assign me this issue?? @aditya-bhaumik

already someone is working on it

already someone is working on it

alright....Assign me atleast please!!!!!!!!!!!!!

I cant assign this if someone is already working on this


Null Exception Error for UserManager FindBy* methods

var user = await _userManagerFindByName(username);

generates the null exception error below
{System.NullReferenceException: Object reference not set to an instance of an object.
   at Amazon.AspNetCore.Identity.Cognito.CognitoUserManager`1.PopulateTokens(TUser user, String claimType, String claimValue)

The User Pool is set to allow sign in by username and verified email. However, everything else that I've tested seems to work. GetUsersAsync() works, CreateUser, AddToRoleAsync, getting tokens... all work.

Hi @tachyon1337, I wasn't able to reproduce this issue.  Are you still having issues with it?  Which package versions are you using?

Could you provide a more complete stack trace, too?

I wasn't able to reproduce this issue.

Probably because I'm running my tests from a console app. I looked at the source code for CognitioUserManager and it appears the PopulateTokens method has a reliance on an injected IHttpContextAccessor in order to try to construct a ClaimsPrinciple on the retrieved user.  Obviously, in a console environment, the HttpContext property will be null, hence the null exception.  It looks like you did null checking safeguards on everything but the HttpContextAccessor. There are scenarios(e.g, User Administration) where you might want to use the Identity Framework from the command line.

If you are running from a console app then the HttpContext is most likely null as you said.
I will add some safeguarding around that property

This should fix it: https://www.nuget.org/packages/Amazon.AspNetCore.Identity.Cognito/<IP_ADDRESS>


How can I customize serde in jackson-dropwizard based on api version?

I have two versions of API v1 & v2. One uses camelCase as a separator and one uses snake_case. I have a common model class which I would like to reuse across both API versions. So, how would I be able to tell dropwizard to use camel case serializer for V1 apis and snake_case for V2 apis?

@anvi265 You can override the ObjectWriter and ObjectReader configuration in your JAX-RS resources using ObjectWriterInjector (with ObjectWriterModifier) and
ObjectReaderInjector (with ObjectReaderModifier) respectively.
See WriteModificationsTestBase for an example.

Can I just change the object mapper to be used for APIs that need snake_case? (Just for that API?
    ObjectMapper newMapper = baseConfig.copy();     newMapper.setPropertyNamingStrategy(PropertyNamingStrategy.SNAKE_CASE);
But how can I configure this on resource level? For others, I would not set this property.

@anvi265 Please refer to the linked Javadoc and the example in the jackson-jaxrs-providers project.


Missing storage symlink > symlink(): No such file or directory

Laravel Version: 5.5.21
Voyager Version: 1.0
PHP Version: 7.1.10
Database Driver & Version: Mysql 14.14

Description:
After installing Voyager on a fresh Laravel installation, on the dashboard I notice the avatar icon in the top right is a broken link. Also the big warning at the top about the Missing storage symlink. So I click the fix it button and get the following error:
symlink(): No such file or directory

Sounds like you're not using a standard laravel install.... Is this a local install or hosted somewhere?

It's installed in Vagrant using Homestead. I installed it just doing:
# laravel new admin
Just a normal Laravel installation. Is it a user permission problem?

Also seeing this issue: https://github.com/laravel/internals/issues/34
Not sure what the solution is.

This was a result of me moving the project directory elsewhere. It looks like Laravel creates a symlink using an absolute path for some reason. I destroyed the symlink and created a new one using artisan storage:link. Weird I have to do that but it's a Laravel problem, not Voyager problem.

Laravel creates a symlink at public_path('storage') and points it at storage_path('app/public'), so you just need to make sure your paths are set appropriately.  But I agree, Laravel issue, not Voyager.  Glad you got it working!

try to delete existing storage symbolic link and then try php artisan storage:link command

@sujalpatel022 Thanks yes that is the obvious solution. The problem is that Laravel shouldn't be making an absolute path but rather a relative one.

@Jakobud, it's not a laravel problem. It just creates a file system symlink. Symlinks don't always work well with relative references, so absolute links work much better.  In either case, pushing those links to a remote server will not work, so they'll still need to be recreated


Move BlobAndProofV1 to alloy_eips

Describe the feature
for convenience this type BlobAndProofV1
https://github.com/paradigmxyz/reth/blob/main/crates/rpc/rpc-types/src/lib.rs#L69-L69 blocked by
should be moved to alloy_eips crate blocked by https://github.com/paradigmxyz/reth/pull/9723
for blob serialization we can use
https://github.com/alloy-rs/alloy/blob/4492c25f1a666881d18367dc47d0040fc05b17ae/crates/rpc-types-beacon/src/sidecar.rs#L104-L114
and also move to eips crate
Additional context
No response

@mattsse, shouldn't this issue be moved to the alloy repository?

yeah, but we also need to use it here once release, so doesn't really matter


Delete manifests/j/JanDeDobbeleer/OhMyPosh/7.55.2 directory

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run


feat: add ViteSsrSite construct

This PR adds the ViteSsrSite construct to help deploy Vite application with vite-plugin-ssr plugin. The construct supports multiple deployment models for the SSR Lambda and Lambda@Edge.
import type { StackContext } from 'sst/constructs';
import { ViteSsrSite } from 'sst/constructs';

export function WebStack({ stack }: StackContext) {
  const site = new ViteSsrSite(stack, 'site', {
    path: 'web',
    serverHandler: {
      path: 'server/index.ts',
    },
    edge: true,
    customDomain: {
      domainName: 'vite-ssr-demo.sst.dev',
      domainAlias: 'sst.dev,
    },
  });

  stack.addOutputs({
    SiteUrl: site.url ?? 'localhost',
  });
}

Key point
As vite-plugin-ssr's Deploy documentation says, vite-plugin-ssr is just server middleware, so we need to write our own SSR Lambda handlers. In the example I used express and @vendia/serverless-express.
This server handler needs the ssr mode build output of the Vite app when building. To keep the behavior of SsrSite as much as possible, I made the server handler build run in the validateBuildOutput function, but let me know if you need any modifications. (Adding hook functions like afterBuild, etc.)

@jayair can you consider merging this PR? I am also wanting to use sst with my react vite ssr app.

Hmm I'm not sure if we can get to this soon. I think the quickest way might be to package this as a separate construct for now.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Allow files that failed to upload to be reuploaded

When a file fails to upload, it should be possible for the user to try uploading it again. Currently, we report the second attempt as a duplicate, even if the first one failed.

CZO thread

Is there any other case in which "Cannot add the duplicate file..." error arise?

@zulipbot claim

@zulipbot claim

@kimry02 , this is a high priority issue which is aimed for the 8.0 release. Since I came up with a fix, I would be moving on with the PR.


Add spec and implement the interpreter for  SelectOp

Request description
Spec and interpreter for stablehlo.select

In October, we'll be focusing on control flow, data movement and reduction ops to frontload more difficult ops as we're working towards StableHLO v1.0. Unassigning this ticket for now.

Spec for SelectOp has been implemented in 2022, interpreter ticket the tracks this work now lives in #989.


1.0.0 release Work Items

This is being made to track things that need to be done before I would consider everything ready to go for a 1.0.0 release
Items to do:

[ ] #41

Not needed honestly since the todo items should really be issues anyways.


How to perform specific function with  flutter_foreground_task

Hi, apology for being dumb and asking this question here.
I am using Flutter Telephony plugin which works fine (listens to incoming SMS). But it only works when app is in foreground for some reason. So I decided to use this plugin to listen to incoming SMS through foreground task, but don't know where to start.
So far I have been able to get flutter_foreground_task working as in example, but which part of code in this plugin will handle Flutter Telephony events?
Please help.

Looking at the telephony plugin, it seems that background processing is already included.
backgrounMessageHandler(SmsMessage message) async {
	// Handle background message
}

telephony.listenIncomingSms(
	onNewMessage: (SmsMessage message) {
		// Handle message
	},
	onBackgroundMessage: backgroundMessageHandler
);

Would you like to go to the Telephony issues page and check it out?

Thanks for taking time and replying.
I have already tried that and not working for some reason.
Is there a way to run some task through flutter_foreground_task though? For example, showing a toast every 5 seconds.

I tested using the telephony plugin and the listenIncomingSms function doesn't seem to work properly with this plugin. But the sendSms function seems to work fine. To view a sample app, go to the address below.
https://github.com/Dev-hwang/telephony_sample

I would like to thank you so much for taking the pain for going through that plugin and created that sample app.
Duplicate of # and the listenIncomingSms function doesn't seem to work properly with this plugin
Is it it possible with flutter_foreground_task to listen to data change or new data inserted in Firestore?

I haven't tested it, but looking at the implementation of the cloud_firestore plugin, it looks like it could be used with this plugin.


[WIP][rdkafka] Add new port

#5920

I see failures on Linux and UWP.  Are those expected?

@Rastaban I haven't tested it yet. :-)
Maybe I will test it after the holiday.

Known issues:

x86-windows

1>   Creating library E:/vcpkg/buildtrees/rdkafka/src/v1.0.0-5c63a98714/examples/build/Debug/rdkafka_example_cpp.lib and object E:/vcpkg/buildtrees/rdkafka/src/v1.0.0-5c63a98714/examples/build/Debug/rdkafka_example_cpp.exp
1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static int const RdKafka::Topic::PARTITION_UA" (?PARTITION_UA@Topic@RdKafka@@2HB)
1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static __int64 const RdKafka::Topic::OFFSET_BEGINNING" (?OFFSET_BEGINNING@Topic@RdKafka@@2_JB)
1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static __int64 const RdKafka::Topic::OFFSET_END" (?OFFSET_END@Topic@RdKafka@@2_JB)
1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static __int64 const RdKafka::Topic::OFFSET_STORED" (?OFFSET_STORED@Topic@RdKafka@@2_JB)
1>E:\vcpkg\buildtrees\rdkafka\src\v1.0.0-5c63a98714\examples\build\Debug\rdkafka_example_cpp.exe : fatal error LNK1120: 4 unresolved externals

Update the latest test results from the current CI system:

x64-uwp
master
test
notes

librdkafka

Fail
New Port

arm-uwp
master
test
notes

librdkafka

Fail
New Port

Please help confirm if they are expected. Thanks.

1. LNK2001

This issue seems a bug in the upstream repo: https://github.com/edenhill/librdkafka/pull/2274

Known issues:
1. x86-windows
   > 1>   Creating library E:/vcpkg/buildtrees/rdkafka/src/v1.0.0-5c63a98714/examples/build/Debug/rdkafka_example_cpp.lib and object E:/vcpkg/buildtrees/rdkafka/src/v1.0.0-5c63a98714/examples/build/Debug/rdkafka_example_cpp.exp
   > 1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static int const RdKafka::Topic::PARTITION_UA" (?PARTITION_UA@Topic@RdKafka@@2HB)
   > 1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static __int64 const RdKafka::Topic::OFFSET_BEGINNING" (?OFFSET_BEGINNING@Topic@RdKafka@@2_JB)
   > 1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static __int64 const RdKafka::Topic::OFFSET_END" (?OFFSET_END@Topic@RdKafka@@2_JB)
   > 1>rdkafka_example.obj : error LNK2001: unresolved external symbol "public: static __int64 const RdKafka::Topic::OFFSET_STORED" (?OFFSET_STORED@Topic@RdKafka@@2_JB)
   > 1>E:\vcpkg\buildtrees\rdkafka\src\v1.0.0-5c63a98714\examples\build\Debug\rdkafka_example_cpp.exe : fatal error LNK1120: 4 unresolved externals

This issue seems a bug in the upstream repo: https://github.com/edenhill/librdkafka/pull/2274

This seems a bug in the upstream repo

It's fixed

I will give those features a test sooner or later.

https://github.com/edenhill/librdkafka/pull/2307

OK. I have tested all features with this little project https://github.com/myd7349/Ongoing-Study/tree/master/cpp/CMake/vcpkg/librdkafka_pr_2274. These triplets are tested:

x86-windows
x86-windows-static
x64-windows
x64-windows-static
x64-linux
I have removed the WIP tag and any review is welcome.

I have gave UWP support a try, but failed: https://github.com/edenhill/librdkafka/files/3152143/install-x86-uwp-dbg-out.log
Maybe we can add UWP support in the future.

Maybe we can add UWP support in the future.

Yes, go without UWP.

@myd7349, thanks for your all efforts on this port. The port only failed on arm64-windows now except for x64-uwp and arm-uwp. Have you tested on arm64-windows?
The error log on arm64-window is as follows:
arm64-windows.zip

Hi @NancyLi1013 I didn't have ARM toolchain installed on my PC, so I am not able to fix it currently.

Hi @myd7349, can you use this patch to solve the problem of building errors under ARM/ARM64?
fix-builderror-in-arm.zip
Thanks.

Hi @JackBoosY Thanks!
I will give it a try after work.

Hi! @JackBoosY I am not sure whether it will work out by defining get/put_unaligned* as get/put_unaligned_direct since I saw these commits in snappy_compact.h.
I have create an issue here: https://github.com/edenhill/librdkafka/issues/2324

Hi! Can any one tell me whether the ARM patch work or not? If it works, maybe I can create a PR in the upstream.

Hi! @JackBoosY I have fixed the patch filename. Does it work for ARM/ARM64 now? Thanks!

It seems that this port does not support uwp.
Except for uwp, other triplets are built successfully.

@JackBoosY Thanks!
BTW, it seems that I can see the CI log now:
https://github.com/microsoft/vcpkg/pull/6618
https://github.com/microsoft/vcpkg/pull/6628
https://dev.azure.com/vcpkg/public/_build?definitionId=10&view=buildsHistory

/azp run

/azp run

Thanks for the new port, @myd7349!


update instructions for remote-only MLMD Python lib

Closes #228
Description
update instructions following work finalized on soft-fork repo
How Has This Been Tested?

followed included instruction
poetry lock
poetry run pytest -v
tests are passing

Merge criteria:

[x] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

thank you for mentioning the typo on approval, fixed.


Anyway to make trigonometric functions implicit?

I have 2 questions:
1- Can I make this expression acceptable ?   6SIN(8)    instead of 6xSIN(8)   ?
2- Can I let Sin(8   be automatically evaluated when at the end of the expression ?without the need to add a closing parenthesis ?

1- This would require some changes in the tokenizer, I guess. Depending on how many cases you want to support, this could be rather simple or quite complex.
2- You could do this outside EvalEx. Count the number of parentheses in the string. Then add the missing parentheses at the end, if there is a mismatch.

See #64 and #123 for pevious discussions.

Oh, thanks @RobertZenz, I totally forgot about #123


in event loop assertion failing with multiple threads

This line is getting hit when MultiThreadedEventLoopGroup is configured with numThreads > 1 right here.
You can recreate this with the following steps:
1: clone swift-nio master
2: configure group to System.coreCount threads or just hard-code to 8
3: run NIOHTTP1Server executable
4: run curl localhost:8888
This doesn't get hit in release mode (obviously) and wrk seems to work fine, but I'm assuming that assert there is important for performance / stability reasons.

@tanner0101 we will have a look. This is definitely a bug ...

@weissi can you have a look ?

Was fixed via #63


Adding Markdown support to Legend text

Description
This addresses feature request #1233 by adding markdown support for the Legend text in the LegendItem component.
I chose to use the react-markdown library due to it's widespread usage and simple API. There are many more capabilities and customizations we can choose to adopt in the future.
This PR adds support for italics, bold, and links. There are many more elements we could add support for (i.e. an underline without link, strikethrough, headers, tables, lists, etc) — we'll just need to ensure the styling works for our needs.
Note: we're not using the latest version of react-markdown (v9) because it requires an updated version of react (v18 compared to our v16). I don't think we're missing out on much in v9 tbh.
~Note 2: by default, links generated by markdown open in the current tab. We can override to open in a new tab if preferred (I do think that's what users would expect so I plan to add this).~  Updated ✅
How to test the feature:
@wadhwamatic are there any immediate use-cases for this markdown? If so, I can update the json now so we can use real examples for QA.
Checklist - did you ...
Test your changes with

[ ] REACT_APP_COUNTRY=rbd yarn start
[ ] REACT_APP_COUNTRY=cambodia yarn start
[x] REACT_APP_COUNTRY=mozambique yarn start
[ ] Add / update necessary tests?
[ ] Add / update outdated documentation?

Screenshot/video of feature:
Example usage:

Generated html:

@gislawill can you add a temp example in one oft the mozambique legends for this PR?

@gislawill can you add a temp example in one oft the mozambique legends for this PR?

Can do! Just added an example under INAM aggregate rainfall

@wadhwamatic, added the following links. The CHIRPS update was applied in every legend text that had the hyperlink


Add --secrets for VM and VMSS

add --secrets for VM and VMSS so that it takes a file or string content in the shape of ARM vm secrets
add az keyvault certificate get-default-policy
add az vm format-secret
add tests for VM and VMSS
add transformer for x509 certificates so that base64 thumbprint is also shown as hex as it is named in the file system when provisioned for Linux VM and VMSS.

Usage of: az keyvault certificate get-default-policy
$ az keyvault certificate get-default-policy -h

Command
    az keyvault certificate get-default-policy: Get a default policy for a self-signed certificate.
        This default policy can be used in conjunction with `az keyvault create` to create a self-
        signed certificate. The policy can also be used as a base to manipulate to create other
        permutations of Key Vault certificates.

Arguments

Global Arguments
    --debug    : Increase logging verbosity to show all debug logs.
    --help -h  : Show this help message and exit.
    --output -o: Output format.  Allowed values: json, jsonc, table, tsv.  Default: json.
    --query    : JMESPath query string. See http://jmespath.org/ for more information and examples.
    --verbose  : Increase logging verbosity. Use --debug for full debug logs.

Examples
    Create a self-signed certificate with a the default policy
        az keyvault create -g group-name -n vaultname -l westus --enabled-for-deployment true \
          --enabled-for-template-deployment true

        az keyvault certificate create --vault-name vaultname -n cert1 \
          -p "$(az keyvault certificate get-default-policy)"

Usage of az keyvault secret vm-format
$ az vm format-secret -h

Command
    az vm format-secret: Format secrets to be used in `az vm create --secrets`.
        Transform secrets into a form consumed by VMs and VMSS create via --secrets.

Arguments
    --secrets -s [Required]: JSON encoded secrets as an array of secrets [], or a single secret {}.
                             Use @{file} to load from a file.
    --certificate-store    : Certificate store the secret will be applied (Windows only).

Global Arguments
    --debug                : Increase logging verbosity to show all debug logs.
    --help -h              : Show this help message and exit.
    --output -o            : Output format.  Allowed values: json, jsonc, table, tsv.  Default:
                             json.
    --query                : JMESPath query string. See http://jmespath.org/ for more information
                             and examples.
    --verbose              : Increase logging verbosity. Use --debug for full debug logs.

Examples
    Create a self-signed certificate with a the default policy and add to a virtual machine
        az keyvault certificate create --vault-name vaultname -n cert1 \
          -p "$(az keyvault certificate get-default-policy)"

        secrets=$(az keyvault secret list-versions --vault-name vaultname \
          -n cert1 --query "[?attributes.enabled]")

        vm_secrets=$(az vm format-secret -s "$secrets")

        az vm create -g group-name -n vm-name --admin-username deploy  \
          --image debian --secrets "$vm_secrets"

@tjprescott I've update the command and after Travis is back to life, I think we should be all set. Let me know if you have any concerns.

Codecov Report

Merging #2212 into master will increase coverage by 0.1%.
The diff coverage is 73.18%.

@@            Coverage Diff            @@
##           master    #2212     +/-   ##
=========================================
+ Coverage   72.95%   73.06%   +0.1%
=========================================
  Files         458      458
  Lines       19499    19617    +118
  Branches     2578     2773    +195
=========================================
+ Hits        14226    14333    +107
+ Misses       4390     4340     -50
- Partials      883      944     +61

Impacted Files
Coverage Δ

...re-cli-vm/azure/cli/command_modules/vm/commands.py
92.16% <100%> (+0.04%)
:white_check_mark:

...ure-cli-vm/azure/cli/command_modules/vm/_params.py
96.01% <100%> (+0.06%)
:white_check_mark:

...yvault/azure/cli/command_modules/keyvault/_help.py
100% <100%> (ø)
:white_check_mark:

.../azure/cli/command_modules/vm/_template_builder.py
84.43% <100%> (+0.38%)
:white_check_mark:

...azure-cli-vm/azure/cli/command_modules/vm/_help.py
100% <100%> (ø)
:white_check_mark:

...ult/azure/cli/command_modules/keyvault/commands.py
100% <100%> (ø)
:white_check_mark:

src/azure-cli-core/azure/cli/core/_util.py
66.66% <100%> (+1.14%)
:white_check_mark:

...vault/azure/cli/command_modules/keyvault/custom.py
66.97% <25%> (-2.08%)
:x:

.../azure/cli/command_modules/keyvault/_validators.py
72.54% <63.63%> (-0.61%)
:x:

...cli-vm/azure/cli/command_modules/vm/_validators.py
73.25% <72.5%> (-0.22%)
:x:

... and 43 more

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 8f264f8...17ea71f. Read the comment docs.

@tjprescott I think this pull request reflects all of our conversations and should be ready for inclusion.


Update repositories.txt

Closing as duplicate of https://github.com/arduino/library-registry/pull/1599


Migrating from 2.x to 3.x

The following breaking changes need to be migrated when upgrading to version 3.x:
Mapper Container

All <ClassName>Mapper.containers are removed

Instead use the global MapperContainer.globals container.
T decode<T>(String json) {
-  MyClassMapper.container.fromJson<T>(json);
+  MapperContainer.globals.fromJson<T>(json);
}

Initializing Mappers
Mappers can be used

explicitly trough calling e.g. MyClassMapper.fromJson(json), or
implicitly trough a generic parameter, e.g. MapperContainer.globals.fromJson<MyClass>(json).

When used implicitly, mappers must be initialized beforehand by calling their MyClassMapper.ensureInitialized() method.
void main() {
+  MyClassMapper.ensureInitialized();
+  MyOtherClassMapper.ensureInitialized();
  ...
}

Generated Initializer
Calling ensureInitialized() for every mapper in your project can be cumbersome. Therefore you can generate an initializer functions that automatically initializes all mappers in scope.
To do this set the generateInitializerForScope property on @MappableLib(), which replaces the createCombinedContainer property.
@MappableLib(
-  createCombinedContainer: true, discoveryMode: DiscoveryMode.package,
+  generateInitializerForScope: InitializerScope.package,
)
library main;

- import 'main.container.dart';
+ import 'main.init.dart';

void main() {
-  mainContainer.fromJson<...>(...);
+  initializeMappers();
+  MapperContainer.globals.fromJson<...>(...);
}

When creating a library which does not have a main method, such as one for communicating with an API, should initializeMappers() be called when the class is constructed or somewhere else? What happens if it gets called more than once? What if the library is then used in a larger project which is also using dart_mappable?

Initializing mappers is idempotent, meaning executing it more than once has no effect and is safe to do.


create a VM image definition

When creating a definition, there are a number of questions the admin won't have the answer to like publisher offer sku etc. they need help to find them.
Jim Moyle
[Enter feedback here]

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

ID: 64ef4667-696f-ec14-47cd-55130bb635ce
Version Independent ID: ecee1d4b-7827-9fe2-2a44-f503f8449ef4
Content: Use custom image templates to create custom images - Azure Virtual Desktop
Content Source: articles/virtual-desktop/create-custom-image-templates.md
Service: virtual-desktop
GitHub Login: @dknappettmsft
Microsoft Alias: daknappe

@JimMoyle
Thanks for your feedback! We will investigate and update as appropriate.

@JimMoyle
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


ENH: implement a linear varying center of mass for Hybrid motors

A method was added that allows calculating the variation of the center of mass of the hybrid motor using a linear interpolation.

Pull request type
Please check the type of change your PR introduces:

[X] Code base additions (bugfix, features)
[ ] Code maintenance (refactoring, formatting, renaming, tests)
[ ] ReadMe, Docs and GitHub maintenance
[ ] Other (please describe):

Pull request checklist
Please check if your PR fulfills the following requirements, depending on the type of PR:

ReadMe, Docs and GitHub maintenance:

[ ] Spelling has been verified
[ ] Code docs are working correctly

Code base maintenance (refactoring, formatting, renaming):

[ ] Docs have been reviewed and added / updated if needed
[ ] Lint (black rocketpy) has passed locally and any fixes were made
[ ] All tests (pytest --runslow) have passed locally

Code base additions (for bug fixes / features):

[ ] Tests for the changes have been added
[ ] Docs have been reviewed and added / updated if needed
[ ] Lint (black rocketpy) has passed locally and any fixes were made
[ ] All tests (pytest --runslow) have passed locally

What is the current behavior?

Enter text here...
What is the new behavior?

Enter text here...
Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Enter text here...
A method was added that allows calculating the variation of the center of mass of the hybrid motor using linear interpolation.

@ompro07 can you add a simple example of your feature working ?

Hey @ompro07 nice PR from your side. I've pointed 3 major comments that I think we can discuss in more details in order to improve this implementation and the next ones
1 .  I definetely suggest we include an example of hybrid motor usage, at least for facilitating our verifications on future pull requests. I am suggesting the following example:
hybrid = HybridMotor(thrustSource=2000,   # These are dummy numbers, please add what makes more sense in each field,
                    burnOut=5,
                    distanceNozzleMotorReference=1,
                    grainNumber=1,
                    grainDensity=1000,
                    grainOuterRadius=10/2000,
                    grainInitialInnerRadius=5/2000,
                    grainInitialHeight = 0.3,
                    oxidizerTankRadius = 127/2000,
                    oxidizerTankHeight= 2,
                    oxidizerInitialPressure= 60,
                    oxidizerDensity= 500,
                    oxidizerMolarMass= 44/1000,
                    oxidizerInitialVolume= 1/100,
                    distanceGrainToTank= 1/10,
                    injectorArea=1/10000,
                    grainSeparation=0,
                    nozzleRadius=0.0335,
                    throatRadius=0.0114,
                    reshapeThrustCurve=False,
                    interpolationMethod="linear")
# Btw I think it would be nice having some standard values for some of these arguments

and then the hybrid.info()method will return the following:

I also believe we need to implement a simple unit test to guarantee next PRs will be verified using github actions

Finally, the info() and allInfo() method can be improved a little bit for HybridMotor class,

Thanks @MateusStano for solving the problems with github actions


upgrade to react 17

In a year and a half since release of react 17, it's been more and more common that we hit blockers in upgrading other packages because our react version is so far behind (and unsupported by the new version of the tool we're trying to use).
This PR tries to do the bare minimum to upgrade react.  Everything is working fairly well, except one dependency framer-motion.  I bisected and determined that<EMAIL_ADDRESS>is the exact version where the break occurs.  Thankfully, the version before that also supports react 17, which means we can defer whatever the problem is with framer-motion for now.  To whoever deals with this problem with framer-motion in the future, start here.
Here's the output of npx check-peer-dependencies --npm

BEFORE
AFTER

no mismatches

cool if we delay this until after #4529 to keep the variables to a minimum?

(update, we're going to hold off on this until after a GA release with electron goes out)


Dropup doesn't work but dropdown does

Dropup doesn't work but dropdown does. You can see my specific problem in my jsfiddle
I use windows 10, google chrome as browser

Create a normal form with the selectpicker class and live search bar
Scroll until bootrap-select needs to use dropup
You can just see the live search bar but no li entries

https://jsfiddle.net/6j1kz8ee/

It's because you're including Bootstrap 3.3.7 CSS in addition to Bootstrap 4 CSS.


new Requests ui have static size

The new ui has a static size and does not change when the screen gets smaller,
You can also move inside the box and lose your position

when moving in the box:

hey @IdoPeled8 Can this issue be assigned to me

hey @IdoPeled8 Can this issue be assigned to me

you want this issuse or #347 ?

Hey @IdoPeled8
I want to work on #347 ,I thought you might be working on that already. If I'm done with that and this is still available I can jump on it.
Anyways I have a problems running the project, I get this error when running the server " if (!supabaseUrl) throw new Error('supabaseUrl is required.')"

Hey @IdoPeled8
I want to work on #347 ,I thought you might be working on that already. If I'm done with that and this is still available I can jump on it.
Anyways I have a problems running the project, I get this error when running the server " if (!supabaseUrl) throw new Error('supabaseUrl is required.')"

Your message is mostly clear. You might want to make a small correction:
Got it. I've assigned you to work on #347. The main maintainer will respond to you about error soon.
Once everything is resolved, I'll provide more information about the #347 issue to complete it.

Thanks @IdoPeled8 👌

Hey! @adetyaz
You would need env variables. Ping me on discord so I will send you.
My discord - yairharas

Thanks alot @ypotter
I'll do that now

@ypotter Could you please send me the Discord link? The current link has expired.


chore(ci): add code coverage support

Description

This PR introduces Codecov to our CI for better test coverage. I've set the minimum coverage at 60%, which is currently above our 68% coverage level. This ensures a solid starting point for enhancements.
Additionally, it integrates essential tools (flake8, black, isort, autoflake) directly into our test workflow. This helps us catch issues introduced in individual PRs, rather than relying solely on the SDK generator output.
This PR reflects changes directly from the SDK generator. Once validated here, a separate PR will update the repository and other SDKs.
References

N/A
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

Disregard the Snyk license false positive; it shouldn't be flagging MPL-2.0.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

@rhamzeh Updated based on your feedback 👍


Check for a balance parentheses using Stack

Write a DSA program in JS to check for a balance parentheses using Stack

Please assign it to me


Stop command

it's not work...

https://github.com/maa123/MIDI2PMMP/commit/8933850a6f0cfc824f69c5e76f183ac1bbb1595c


failing running Dockerfile in client directory

when building the docker directory to get the client library, it throws me the next issue :
"Step 5/10 : COPY client/requirements.txt .
COPY failed: file not found in build context or excluded by .dockerignore: stat client/requirements.txt: file does not exist"
is there maybe an older version of docker to get the library, of am i installing the library wrong?

To use the client image you do not need to build it- the commands to run it will pull the prebuilt image down from docker hub. Please follow the README's Getting Started.
The error is most likely because you are not executing the build command correctly, so the working directory you are executing docker from is incorrect so it can't find the file at the right relative path. If you are trying to build it due to customizations, you should use interop-client.sh which executes the command correctly.
Beyond this, I suggest you learn Docker so you know how to troubleshoot it yourself.


Add Minisphere benchmark run

Follow-ups for discussion inhttps://github.com/svaarala/duktape/pull/1284#issuecomment-272571951.

The idea so far is:

Build the game using Cell.  Include both a transpile and minify step.  Exercises: String manipulation (concatenation especially); regular expressions; possibly bytecode dispatch
Run an automated AI-controlled Spectacles battle using minisphere.  Exercises: A bunch of stuff :)

@svaarala If it would help, I could easily add a --benchmark command like option that would instruct the engine to skip every single frame.  This would avoid drawing code skewing the results too much.  The engine is set up so that if a frame is skipped, any rendering operations done that frame are no-ops.  If the frame isn't going to shown, there's no need to draw anything to the backbuffer.

@svaarala Just got done with releasing minisphere 4.4.0, so I should be able to look into this over the next couple of weeks.


emi:fuel is white instead of orange

Idk of this is actually an issue, but the white kind of blends into the background and usually it's using the fully-fueled furnace gui texture

The fuel icon is actually just a reuse of the simplified (recipe tree) icon for smelting. The reason it's white is... I haven't given it time to actually make a proper icon, but considering I do have a flame in my textures I might as well switch to the higher contrast version to make it more readable, I agree.

This was tweaked, the icon is now the full burning orange starting in 1.0.1


"tick" or "update" and when to use them?

I feel that tick describes a measurement rather than an action. A tick would be a bi-product of an update.

@darkhax Can you explain what you mean by byproduct? I understand the time measurement part of it. A second is usually 20 ticks and 10 redstone ticks.
Should we ever use it as a verb ("Tick a redstone repeater.")?

I dislike update, update is too generic and could be seen to mean a number of different things.
Ticking in games is pretty well known.
Although I think we should make a clear distinction between full ticks, and partial rendering lerps

I'm fine with either as long as we decide on the vocabulary we want to use and are consistent in using it.

To me, update implies there is old state that is outdated and must be updated to become current.
A tick is more specific than an update. A tick is always called at regular intervals, and checks to see if the thing needs an update or not. If it does, then it is updated.

onTick?

I'm with @mezz on this, update is for explicit state updates and tick is for things on the game loop.

For reference: https://github.com/ModCoderPack/MCPBot-Issues/issues/703

Between that and what mezz said (and the support for that), I think mezz's is a fair approach to take.

Agree on tick

There are 2 distinct detail interpretations
a) ticks refer to the game loop, they happen at 20 Hz

tick is for invocations that happen exactly once every tick+object unless there's an obvious hindrance like being unloaded or having opted out globally
update is anything else - it may advance the internal state but doesn't have to

With this you could rely on tick being a mirror of the client/server tick, blocks "update" randomly or through scheduling.
b) ticks are arbitrary quantity time increments / polling+update triggers

ticks are for any repeating time delayed invocation
updates are generally only for events that have a specific cause / explicit request

With this there are random "ticks", but scheduled "updates" are quite muddy. They sometimes meet the tick definition by consistently rescheduling.

I'd much rather go for (a). A "tick" is very clearly defined on the server side, a bit less so on the client side, but in general I prefer that to (b).

:+1: for tick

tick sounds good to me

"update" is too overloaded. I've seen it as referring to ticking something on server side, and to syncing the server-side data to the client, and to redrawing something on the client (either in response to a server sync or a local simulation effect). I'd like to never see it again.


Learning rate schedules improvement + extension

re: PR#389

refactored learning rate schedules into objects
added WarmupCosineWithHardRestartsSchedule for cosine schedule with hard restarts
added WarmupCosineWithWarmupRestartsSchedule for cosine schedule with restarts where each restart uses the same warmup slope

Sorry for the delay in reviewing this.
This is a great PR and it looks good to me.
Thanks for adding some tests also.
I agree with the (mostly cosmetic) comments from @marpaia.
Do you think you can fix them and then we can merge?

Addressed @marpaia 's comments.

Awesome @lukovnikov, I think it looks great! Thanks for making this already awesome library even more awesome 💯

Thanks @lukovnikov!