Fix spelling in main README

Just dropped in to find out what the project is about -- and the first thing that caught my eye were these spelling errors... :)
Signed-off-by: Les Matheson<EMAIL_ADDRESS>

@Stabledog Thanks! Could you sign your commit (i.e. add "Signed-off-by:" ... line in the commit message)? :pray:.

Signed-off-by: Les Matheson<EMAIL_ADDRESS>

Hi -- sorry, but I don't understand. The commit message isn't editable, how would I sign it after-the-fact?

@Stabledog Please take a look at https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message


added note app

I added the note app under the Node.js section as mentioned eaerlier. The app is bootstraped using Reactjs, Nodejs and Tailwind CSS.

I have tested this app and is working .

Thanks

Actual sent the previous comment by mistake

I have tested this app and is not working as expected
Here are the errors you need to resolve before getting this merged


Disable selecting more than one hierarchy from the same dimension.

After our meeting with @hermosillajelmy we know that it shouldn't be possible to select more that one hierarchy of the same dimension. Now we allow the user to do it, the request fails and we show an error message.
This is not very common but we should handle this in the frontend.  The previous did not provide a feature for this.
Example Data Saudi.
https://data-explorer.datawheel.us/?cube=households_electricity&drilldowns[0]=Category.Electricity+sources.Electricity+sources&locale=en&measures[]
There is another scenario where we can not select more than one level of the same hierarchy. Example: Continent, Country.
This works but it could lead to not trusted data as @hermosillajelmy informed.
Maybe the way to do it should be use the new version of &parents=A.B.
We are waiting on @hermosillajelmy debug about this one because could be something that the server may handle.

@walbuc regarding the levels within the same hierarchy, I checked with different queries and they are showing me the correct result so it should not be a problem in pytesseract. If in the future we want to make it compatible with tesseract rust this would be a limitation.


fix(IDN): use INTL_IDNA_VARIANT_UTS46 for idn_* functions

This PR:

adds PHP 7.2 to test matrix
as INTL_IDNA_VARIANT_2003 is deprecated in PHP 7.2,  we use INTL_IDNA_VARIANT_UTS46 for idn_* functions if it's defined

Codecov Report

Merging #20 into master will decrease coverage by 1.11%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #20      +/-   ##
============================================
- Coverage       100%   98.88%   -1.12%
- Complexity       70       72       +2
============================================
  Files             4        4
  Lines           175      179       +4
============================================
+ Hits            175      177       +2
- Misses            0        2       +2

Impacted Files
Coverage Δ
Complexity Δ

src/IDN.php
87.5% <100%> (-12.5%)
8 <0> (+2)

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 c27974a...235c213. Read the comment docs.


Fix 0.9.0 breaking YARD change

= 0.9.0 in YARD version changes the DOM structure of the templates
which broke the nokogiri finder. This results in the docset being
empty, changing the nokogiri the finder fixes the problem. This change
also should be backwards compatible because the tag is still present in
older versions.

https://github.com/lsegal/yard/commit/be17c0fec5022d20dce9f239b06d3055b588be0d

I have tried this PR, and it works in Yard 0.9.9 version

So sorry that it's been years.  I am terrible at Github :.
Thank you for your contribution, and thank you for testing!

Done! :-) Thanks for the reminder, @oniofchaos!


Run for module generation in parallel

Currently dpl-docs on dlang.org run a single-thread. That makes them the bottleneck in time consumption.

Unfortunately this change causes multiple race conditions. I think when we make an attempt to parallelize document generation, we should also use pure and shared/immutable within the affected call tree to let the compiler make reasonably sure that the approach is correct. Frankly, I don't feel comfortable to do multi-threading these days without either that or guaranteed memory isolation, unless it is a small and isolated piece of code. Too many bad memories from C++ times ;-)


Newline

Is there anyway to get a newline into a tooltip?
I'm really loving the speed of css3 tooltips over the likes of tippyjs that I would normally use (Though I still need to use something like tippy or bootstraps tooltips if I want HTML in a tooltip), but for a lot of the basic stuff, this library works perfectly.
However, for some reason, I can't get
 to work.
In a regular 'title' attribute, I can do something like
title="test
test2"
and the tooltip when it shows will have 'test2' on the line below 'test'.

Hi @ray73864, thanks for raising this bug. It seems the reason why it is not showing is because Cooltipz.css sets the property white-space: nowrap; on the tooltip. In devtools, if you set this to white-space: pre; or white-space: pre-wrap;, it should work.
As a quick fix, you create an overriding class, in the meantime I'm going to look at the best way to resolve this in this package.

This will be released in the next version release.
You can add data-cooltipz-size="custom" or class="cooltipz--custom" and use
 in the aria-label to add custom newlines.

This is now released in v2.2.0
Please see https://cooltipz.jackdomleo.dev/#size


Added support for upgrading<EMAIL_ADDRESS>projects solving #482

Added support for upgrading<EMAIL_ADDRESS>projects solving #482

Coverage remained the same at 100.0% when pulling d6079af76771aedce5070c51784299092377a7f0 on waldekmastykarz:spfx-upgrade-131 into 4b0e372b3716362981ed1a890f1db2907c6c6248 on SharePoint:dev.

Merged manually


Fixes related to fb1468: Proof of Concept

Apparently, some of the formatting in ModelTester got corrupted after I had commented and then un-commented certain tests.

No you are correct, make no change, disregard my comment.
On Thu., May 9, 2019, 2:18 p.m. andrei-sa<EMAIL_ADDRESS>wrote:

@andrei-sa commented on this pull request.
In Tests/Source/ModelTester.cpp
https://github.com/eidolonsystems/rover/pull/30#discussion_r282606464:

   m_max_values = m_data[0].m_arguments;

   for(auto i = std::size_t(0); i < m_data[0].m_arguments.size(); ++i) {

     auto [min_it, max_it] = std::minmax_element(m_data.begin(),

         m_data.end(), [&](const auto& lhs, const auto& rhs) {

       return lhs.m_arguments[i] < rhs.m_arguments[i];

     });

     m_min_values[i] = min_it->m_arguments[i];

     m_max_values[i] = max_it->m_arguments[i];

   }

private:
void compute_norm() {

 m_min_values = m_data[0].m_arguments;

 m_max_values = m_data[0].m_arguments;

 for(auto i = std::size_t(0); i < m_data[0].m_arguments.size(); ++i) {

   auto[min_it, max_it] = std::minmax_element(m_data.begin(),

     m_data.end(), [&](const auto& lhs, const auto& rhs) {

Do you mean I should capture i by copy instead of using reference
all-capture? You mentioned limited captures should only be used when mixing
capture types (copy vs reference).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/eidolonsystems/rover/pull/30#discussion_r282606464,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6MKGJDURYOFWKILED6K53PURTI7ANCNFSM4HL3JUYQ
.


Test Rsa oaep in fips mode

Checklist

[x] documentation is added or updated
[x] tests are added or updated

Dependent on #11927 for memory leak fix.
Also depends on #11884 which documents the openssl application changes.
test/recipes/15-test_rsaoaep.t &
apps/pkeyutil.c are the only files that should be in this PR.

Updated docs.

On a per-command basis, I'm not sure I like the whole library context fiddling, at all.  It seems...  unnecessary.
Note, though, that I don't think that a library context per se is unnecessary, but it should be made on a global level.  Think of the interactive mode, where we currently have each command affecting the rest regarding libcrypto global data.  If each command was executed within its own library context, the problem of one command affecting the next should ultimately go away.
Remains electively loading the null provider into the default provider...  I assume that's an interim thing, to purposefully make things break if they rely on the default library context when they shouldn't.  I'm not sure I'd make that subject of a per-command option, but rather of an environment variable (mostly because we don't have global options).  OPENSSL_NO_DEFAULT_CONTEXT maybe?
I've had a global app library context in the back of my mind for a while, so I have ideas (but for once, not a branch yet).  Do you want to tackle that or shall I?

I would like to see less environment variables, not more of them :)
Putting the null provider into the default context and using the fips provider in a created library context is a fundamental requirement. The library context was introduced to solve a particular problem. Using the fips provider in the default library context is avoiding the issue that the library context was added for.

As I just discovered with pkeyutl a library context is going to break certain operations that are not currently compatible (such as SM2). Which is why I gone with the per command -use_libctx option.

I would like to see less environment variables, not more of them :)

Yes, me too, but I would like even less to see interim / unnecessary options

Putting the null provider into the default context and using the fips provider in a created library context is a fundamental requirement.

Er, what???  Why?

The library context was introduced to solve a particular problem. Using the fips provider in the default library context is avoiding the issue that the library context was added for.

Yes, almost everything that's currently global in libcrypto should move to be stored in a library context, and we're currently not there.  That's the reason I'm calling all these new options "interim", because as soon as we've finished that move, they will not be necessary any more.  That's also why I seriously question the "fundamental requirement" that the FIPS provider must be loaded in a non-default provider...  it sounds much more like a band-aid than a "fundamental requirement".

I assume that's an interim thing, to purposefully make things break if they rely on the default library context when they shouldn't.

I am concerned if we dont always test it this way-  then it will get broken every time new code is added that doesnt handle the library context. (which would be easy to miss).

The testing to catch errors is compelling IMO.
I also think that loading the FIPS provider into a non-default context is a requirement.  Imagine an application with supports FIPS and not simultaneously using a library context and the default context.  Insisting that FIPS is in the default context would work but it kind of obtuse.
Also consider the application linked with two different libraries (say A & B) each using OpenSSL -- how does a library A guarantee it is FIPS and that the default context isn't contaminated by B?

Insisting that FIPS is in the default context would work but it kind of obtuse.

Insisting that it must be loaded in a non-default context is just as obtuse.

Insisting that it must be loaded in a non-default context is just as obtuse.

Which nobody is suggesting.  Both must be available.

Also consider the application linked with two different libraries (say A & B) each using OpenSSL -- how does a library A guarantee it is FIPS and that the default context isn't contaminated by B?

It doesn't, so an application that does this would be wise to create library contexts for them.  However, this is also one specific scenario, and I agree that with that scenario, the application should do so.  our application isn't one of those, as far as I know.

Insisting that it must be loaded in a non-default context is just as obtuse.

Which nobody is suggesting.  Both must be available.

In that case, we understand "fundamental requirement" differently.  For me, those are strong words, basically saying "everyone must do this, there's no alternative".

Ummm, how does an application control the library contexts in third party libraries?  This was the primary driver behind library contexts.
Sure, in time we'd hope that each third party library would create its own library context.

Ummm, how does an application control the library contexts in third party libraries? This was the primary driver behind library contexts.

Uhmmm, it doen't.  The idea was that those libraries would create their own library contexts, to insulate themselves from the application.

how does an application control the library contexts in third party libraries?

I get seriously worried by this question.  What third party libraries do is out of our control, let's not try and pretend otherwise.

We need to provide the capability for third parties to do the right thing.  We can't force them to of course.

We need to provide the capability for third parties to do the right thing. We can't force them to of course.

I haven't said anything else.  Of course we should.  What I'm currently concerned with is adding on options to the application (!) that are quite obviously going to be interim (like I said, the interactive mode will need to create a new library context for each command).

Just to make sure that this point doesn't get lost.  We want the default context to be "normal" OpenSSL, with all the non-FIPS algorithms. For some connections, we want to use the FIPS context and we are going to exlicitly specify the context for those.
I am sure there are applications who are doing the exact opposite.
Both are still possible, right?

Both are still possible, right?

Yes. The dispute is mainly about the app's ui at this point.

@levitte. I have updated the code.
I need the 'use_libctx' option to test this as well as any other fips tests (see CMS). So even though it is 'just for testing'. It needs to always be there in order to do the tests. So this is not really a temporary config option.
I have reused -config instead of using provider_config (but this also now loads any modules).

The size of PR #11884 is getting quite large - so I have tried to separate out some bits into smaller PR's to make it easier to review.

ping @levitte

ping @levitte

ping @levitte

ping @levitte

Changed apps to use an environment variable 'OPENSSL_TEST_LIBCTX'
instead of the -use_libctx option.
@levitte or @mattcaswell  - can someone review please.

Needed to rebase and remove the default options for tests call to fipsinstall.

you could have left the redundant default flags, as a test.  When I added the defaults, I deliberately did that in one test.

Either way.. having hexkey:00 was not good though :)

Wow the tests ran without a timeout...

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Thanks.. Merged to master.


Chain Polymorphism

Summary of feature
Using the Silk.NET.Vulkan.Chain class and its subtypes is occasionally unwieldy when dealing with chains that have conditional elements - in my case I have a function that takes in a SwapchainCreateInfoKHR and returns an ImageCreateInfo and I'd like to forward a ImageFormatListCreateInfo chain element if present, and as it stands I have to return Chain and cast the indexer to get the head value out for passing to vulkan apis. To make this easier, I propose the following APIs:
public interface IChain<T0> : IDisposable ... {
    T0 Head { get; }
}
public interface IChain<T0, T1> : IChain<T1> {
    T1 Item1 { get; }
}
...
public class Chain<TChain, T1, T2> : ... IChain<TChain, T1, T2> ...

so that I can use a return value in my case of IChain<ImageCreateInfo> and always have a typed Head property to access while maintaining the usefulness of the Chain type.
Note this API would also possibly allows a version of Chain.Load that is typed without discarding extra chain items, though I am uncertain how to best implement such a method and this is not particularly necessary for my use-case

This definitely feels like a good idea, but would need a bit more thought to make sure we're all on the same page when implementing it.
Would it be possible for you to put together a proposal (like the original Vulkan Structure Chaining proposals as found here) so we can review this further?
Thanks for the great suggestion :)

ill see about creating a proposal for it

This proposal has now been approved and is ready for implementation. This should actually be super easy, as it's implemented as a T4 template: https://github.com/dotnet/Silk.NET/blob/main/src/Vulkan/Silk.NET.Vulkan/Chain.g.tt


chore: remove unused Bootstrap theme

Motivation
The Bootstrap theme/preset has never been production-ready and is not used by anyone.
It is totally broken today because we don't have yet the infra to share enough code across themes.
After internal discussions, we decided to remove it from the repo.
Due to significant traction, it's likely that the 2nd production-ready Docusaurus theme will be the Tailwind one: https://github.com/facebook/docusaurus/issues/2961
It's also likely that we'll only provide 2 official themes to reduce maintenance, and delegate the implementation of an eventual Bootstrap theme to the community

Not even BC? 😄

Added Breaking Change but IMHO it won't affect anyone anyway 🤪

docusaurus-community sounds great as org name, and later (after they officially approved) you would transfer/share the ownership org with FB.

According to our recent discussions, Facebook is more likely create a "docusaurus-core" org for support packages we have in the scope of Docusaurus (the existing forks, slorber/docusaurus-starter and other deps like admonition that we use internally).
I doubt that a docusaurus-community org will be created, or at least it would have to be self-organized, and FB doesn't necessarily want ownership of the packages


Update CNY to have a subunit_to_unit of 100

Co-authored-by: Dario Mercado<EMAIL_ADDRESS>https://www.pivotaltracker.com/n/projects/407849/stories/178712868
Prior to this update
Money.parse("84905.6", "CNY").cents.to_i would return 84,911.00 instead of 84,905.60

Ended up being too hard to test just for a single bug. Decided to do a change in the money file itself. Closed this PR


Updating 2018 and newer Maya versions to use the newer evaluate method

If you try to access the input geometry through the datablock, including the world space matrix, any upstream deformers are computed on the CPU inorder to get a valid data handle. This negates the potential gains from GPU deformers upstream as they will run on both GPU and CPU. Autodesk realized this and beginning in 2018, they created a new "evaluate" member function that has additional world space matrix and inverse matrix in a GPU buffer to go along with the local space points buffer. Using this method no longer requires accessing the inputGeom from the datablock, removing that performance hit. Unfortunately they did not back port it to any earlier Maya versions so it will only benefit 2018 and newer. Also unfortunately they kept the matrices in row major order so you have to transpose them before doing the dot product of a point.
This also requires a slight modification to the kernel and separate out some code depending on which Maya you are compiling.

Thanks, Scott!


Optimize generate_projects.sh

This is taking longer than it needs to :)
Consider pre-merging build yaml files and running plugins, and then emitting the pickled result.
This would allow each template to quickly load it's input data, and turn one of the bulkier operations we do nearly 40 times into a once-off.

@nicolasnoble @jtattermusch @adelez heads up

Was the issue fixed with 560c9017c4ce73322cc541eef421e607bd1856a0 or still waiting for the help? :)


sickbay new reshuffle test on runners that do not support it

Mitigates #29973 but I will leave the issue open because the tests are just being disabled because the runners do not preserve reshuffle metadata

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Green - after LGTM I will remove the commit with the trigger files.

Removed trigger files. Will merge after confirming that default tests remain green.


Updating Broken to privileged-access-strategy.md

line 77: miscellaneous "/" in front of intermediaries link.
Previously site error 404 - "page not found"

#please-close


Remove the "Sample Usage" links from the Web site

Usability studies have shown they are black holes of doom.

Specifically, which page(s) ?

The basic widget list, at a minimum, but i think we link to github Search results in other places too.


Error

Hello, can you help me please with one error?

uhhh couldn't you just change uint8* prime to uintptr_t prime?

Not working

think before ask, everyone likes free pasta. closed


Helps on the build issue on Mac OS X

I searched in the issue list, and it was suggested to be autoconf linking problem and that issue was closed. Tried to follow the suggestion there (https://github.com/servo/servo/issues/9504), did not succeed. Don't know if it is the same problem or not. Helps are appreciated.

cd<EMAIL_ADDRESS>&& make -j8
/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-recursive
Making all in src
/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-recursive
Making all in hb-ucdn
CC       libhb_ucdn_la-ucdn.lo
CCLD     libhb-ucdn.la
CXX      libharfbuzz_la-hb-blob.lo
CXX      libharfbuzz_la-hb-buffer-serialize.lo
CXX      libharfbuzz_la-hb-buffer.lo
CXX      libharfbuzz_la-hb-common.lo
CXX      libharfbuzz_la-hb-face.lo
CXX      libharfbuzz_la-hb-font.lo
CXX      libharfbuzz_la-hb-ot-tag.lo
CXX      libharfbuzz_la-hb-set.lo
CXX      libharfbuzz_la-hb-shape.lo
CXX      libharfbuzz_la-hb-shape-plan.lo
CXX      libharfbuzz_la-hb-shaper.lo
CXX      libharfbuzz_la-hb-unicode.lo
CXX      libharfbuzz_la-hb-warning.lo
CXX      libharfbuzz_la-hb-ot-font.lo
CXX      libharfbuzz_la-hb-ot-layout.lo
CXX      libharfbuzz_la-hb-ot-map.lo
CXX      libharfbuzz_la-hb-ot-shape.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-arabic.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-default.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-hangul.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-hebrew.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-indic.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-indic-table.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-myanmar.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-thai.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-tibetan.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-use.lo
CXX      libharfbuzz_la-hb-ot-shape-complex-use-table.lo
CXX      libharfbuzz_la-hb-ot-shape-normalize.lo
CXX      libharfbuzz_la-hb-ot-shape-fallback.lo
CXX      libharfbuzz_la-hb-fallback-shape.lo
CXX      libharfbuzz_la-hb-ucdn.lo
CXX      main-main.o
CXX      test-test.o
CXX      test_buffer_serialize-test-buffer-serialize.o
CXX      test_size_params-test-size-params.o
CXX      test_would_substitute-test-would-substitute.o
GEN      harfbuzz.pc
--- stderr
configure: WARNING:
You will not be able to create source packages with 'make dist'
because gtk-doc >= 1.15 is not found.
make[1]: warning: -jN forced in submake: disabling jobserver mode.
sed: 1: "s@%prefix%@/Users/xli/G ...": bad flag in substitute command: 'm'
/bin/sh: harfbuzz.pc: command not found
make[5]: *** [harfbuzz.pc] Error 1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [all-recursive] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [all] Error 2
thread '' panicked at 'assertion failed: Command::new("make").args(&["-R", "-f", "makefile.cargo",
&format!("-j{}" , env:: var ( "NUM_JOBS" ) .
unwrap (
))]).status().unwrap().success()', /Users/xli/GoogleDrive/xiaofeng.li@gmail.com/temp/git/servo/.cargo/registry/src/github.com-88ac128001ac3a9a/harfbuzz-sys-0.1.2/build.rs:14
note: Run with RUST_BACKTRACE=1 for a backtrace.
[Warning] Could not generate notification! Optional Python module 'pyobjc' is not installed.
Build completed in 122.83s

@nhirata suggested in #9612 that brew install gtk-doc will solve this.

@nhirata suggested in servo/servo#9612 that brew install gtk-doc will solve this.

That's surprising.
Maybe it's the missing autoheader issue.
@2015xli any error about autoconf and/or autoheader?

Thanks for the helps. I am continuing to check the problem, and will update the progress here.
@jdm  gtk-doc does not help my case.
@paulrouget It may be related to autoconf/autoheader. I have not identified the root cause yet.

FYI, I was able to compile in my case.  I had the same error :
"You will not be able to create source packages with 'make dist' because gtk-doc >= 1.15 is not found."
see: https://github.com/servo/servo/issues/9612

Oh.  I did want to mention after installing both, I did have to fix my autoconf link.  I had to relink my autoconf doing a little search for autoconf and the link it was looking for and relinking it with brew.

@2015xli Are you still having this problem? The saltfs issue queue is generally for problems with the build infrastructure that Servo runs, whereas the servo/servo repo's issues include user support. You might be able to follow out buildslave installation steps and use Salt to configure a Mac to look the same as the environments where we test Servo, but that doesn't seem to be the question at hand.

Actually, the better way to do this is to close this bug and ask you nicely to re-open it with clarification if it is still a problem. So, if this is still a problem, could you please reopen this bug and clarify what you would like us to do to help you? Thanks!

Thanks!
--
Xiao-Feng Li
VP of Engineering, General manager (USA),
HUAMI Inc.
2485 Old Middlefield Way, Suite 30, Mountain View, CA 94043
From: "E. Dunham"<EMAIL_ADDRESS>Reply-To: servo/saltfs<EMAIL_ADDRESS>Date: Thursday, July 6, 2017 at 6:58 AM
To: servo/saltfs<EMAIL_ADDRESS>Cc: 2015xli<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [servo/saltfs] Helps on the build issue on Mac OS X (#221)
Actually, the better way to do this is to close this bug and ask you nicely to re-open it with clarification if it is still a problem. So, if this is still a problem, could you please reopen this bug and clarify what you would like us to do to help you? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/servo/saltfs/issues/221#issuecomment-313249437, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALMBa5yo02vZaFRtqLBOvNuZZFKx7SSPks5sLBUjgaJpZM4HZjbX.


[WIP] chore: Refactor vendor dependencies in modules

What this PR does / why we need it:
chore: Refactor vendor dependencies in modules
This is initial work on refactoring of modules. Before this PR, each module had its own vendor folder.
That means this repo holds vendor dependencies, which were multiple times duplicated. Problematic was update of any package, because it had to be changed in each go.mod file.
This PR starts migration to just a single vendor folder, go.mod and go.sum files.
As an initial work I moved cmd folder to root of the repo and moved each cmd folder from packages there. Then the vendor, tests folder, go.mod, go.sum files are removed and moved to root of repository.
The pkg folders of each module are intact, because it would be too much of changes for a single PR. They will be unified in follow up PRs.
Release note:
chore: Refactor vendor dependencies in modules

/retest
@akrejcir, @jcanocan, @0xFelix can you please review this?

This is a huge effort. Many thanks @ksimon1!
/lgtm

When you move the main.go files and test module files, you remove them in one commit and then add them again in a future commit. This makes it hard to review, to see if these files are the same.
Can you do the move in a single commit?

@akrejcir I updated the commits

/hold cancel

/retest

Thanks!
/lgtm


Cannot dispatch mousedown event on nonexistent selector: xpath selector: //*[text()="Login"]

I got this error running the script. Any idea why?
--
Visiting site
CasperError: Cannot dispatch mousedown event on nonexistent selector: xpath selector: //*[text()="Login"]
/usr/local/lib/node_modules/casperjs/modules/casper.js:1355 in mouseEvent
/usr/local/lib/node_modules/casperjs/modules/casper.js:462 in click
/Users/diegopetrucci/Desktop/fedora_course_scraper-master/course_scraper.coffee:49
/usr/local/lib/node_modules/casperjs/modules/casper.js:1553 in runStep
/usr/local/lib/node_modules/casperjs/modules/casper.js:399 in checkStep

It's possible that the markup has changed, or that your initial URL is incorrect. Can you paste the course URL?

Of course! And, obviously, thanks for making this script and helping me.
URL: http://bitfountain.io/courses/complete-ios8
Title: The Bitfountain iOS 8 with Swift Immersive


feat(frontend): add types for spl tokens

Motivation
SPL Tokens are what ERC20 is in Ethereum. Ultimately the goal is to not only handle SOL native tokens, but also SPL tokens. To handle them in the application, we add typing as we did for ERC20 Tokens.
https://spl.solana.com/#:~:text=The Solana Program Library (SPL,and%20deployed%20to%20its%20mainnet.
Changes

Add types for spl and user tokens

Nevermind, I'll just convert it to draft - the feature for Usertokens will follow, until then I'll render a disabled toggle for solana without adding this logic


No support for wstring

Not sure if this was designed specifically for use with bitcoin related services only, but support for wstrings and other w* types would make it a great drop in replacement for the old json spirit many services just copied from pre-univalue sources.

@BlockMechanic Do you have a link to an example user, for test purposes?

Happy to consider and re-open this issue, if a link to an example can be provided.


923 - OASys Health section

Add section 13: Health to the selection endpoint
When requested, return question 13.1t - General health: any mental or physical health conditions?

 Implement new oasys/sections endpoint

Nice, we got there in the end! And you made it look easy...

It's the journey, not the destination :D


[Bug]: Failed to index workspace folder(s)

Current Behavior
When starting the IDL for VSCode extension, the server does not index the folders in the workspace.
Expected Behavior
The extension should index files and print information in the log.
GitHub Repo
No response
Steps to Reproduce

In a new VSCode window, create an IDL file. This starts the extension. Since no folders have been added to the workspace, the only folder to index is .vscode/extensions/idl.idl-for-vscode-4.0.1/idl/vscode/notebooks. The code reports a failure to index.

Failure Logs
idl-lsp info Server initialized, indexing code in these folders:
  {
    '/Users/pulupa/.vscode/extensions/idl.idl-for-vscode-4.0.1/idl/vscode/notebooks': true
  }
idl-lsp info Attempting to index 22 PRO file(s)
idl-lsp error Failed to index workspace folder(s)
  {
    message: [ 'Invalid array length' ],
    stack: [
      'RangeError: Invalid array length',
      '    at t.SplitFiles (/Users/pulupa/.vscode/extensions/idl.idl-for-vscode-4.0.1/dist/apps/server/main.js:7:196089)',
      '    at IDLIndex.indexWorkspaceProFiles (/Users/pulupa/.vscode/extensions/idl.idl-for-vscode-4.0.1/dist/apps/server/main.js:1:521851)',
      '    at IDLIndex.indexWorkspace (/Users/pulupa/.vscode/extensions/idl.idl-for-vscode-4.0.1/dist/apps/server/main.js:1:522837)',
      '    at async /Users/pulupa/.vscode/extensions/idl.idl-for-vscode-4.0.1/dist/apps/server/main.js:7:261223'
    ]
  }

Operating System

[ ] macOS (Intel x86_64)
[X] macOS (ARM64)
[ ] Linux
[ ] Windows

IDL Version
8.9
Additional Information
For me, this error is occurring on a new install of VSCode on an M3 MacBook Pro, and did not occur on Intel Macs.
I get similar behavior whether I open a workspace which has folders, or the minimal example above, where the only files to index are in the .vscode/extensions/idl.idl-for-vscode-4.0.1/idl/vscode/notebooks folder.
The rest of the extension (debug, compile, run, hover help for built-in routines) is working normally.
I do have node installed (tried with version 18 and version 21)

After looking at this, I think I have a fix for the problem which I think boils down to a rounding error (lack of rounding) when getting CPU count. Until the latest generation of Macs came out, I think we have always had even CPU counts, but there is an M3 Mac with 11 CPUs.
To confirm this is the problem, does your Mac have an odd number of CPUs?

Thanks for the quick response! Yes, the Mac is an M3 Pro with 11 cores.

Alright, just published a new release (4.1.0) which should properly handle odd-numbered CPU core counts.
Let us know if you have any other problems as we are happy to take a look!


[Question] - Running an async task prior to first dbcontext use.

I would like to ensure that prior to first use, my DbContext has had Migrations run.
I'd like ensure the migrations run asynchronously so they don't tie up a thread - some migrations I expect will influence potentially large volumes of data so could take a while.
The common pattern I have seen is to do this on application startup:
                using (var serviceScope = app.ApplicationServices.GetRequiredService<IServiceScopeFactory>()
                    .CreateScope())
                {
                    serviceScope.ServiceProvider.GetService<TDbContext>().Database.Migrate();
                }

I could simply wrap that in a Task.Run() so I can proceed with other things on startup and allow it to run concurrently - however I'd also like to simplify usage of my library for consumers - for example If I distribute this library on NuGet - I want consuming it to be as simple as:
services.AddMySpecialComponent(someOptions);

So I created the following service that I can register into the IServiceCollection as a singleton:
 public class EnsureMigrations<TDbContext>
        where TDbContext: DbContext
    {
        private readonly IServiceScopeFactory _serviceScopeFactory;

        public EnsureMigrations(IServiceScopeFactory serviceScopeFactory)
        {
            _serviceScopeFactory = serviceScopeFactory;
            EnsureMigrated = new Lazy<Task>(() =>
            {
                return Task.Run(()=> {

                    using (var serviceScope = _serviceScopeFactory.CreateScope())
                    {
                        serviceScope.ServiceProvider.GetService<TDbContext>().Database.Migrate();
                    }
                });
            });
        }

        public Lazy<Task> EnsureMigrated { get; }

    }

The idea for this class, is that I will register it as a singleton, and it will expose a Lazy<Task> for the migrations work. The very first time this task is awaited, the migrations will run. On subsequent times, it should just return straight away as the task has already completed.
The next question became where to await this task - as I need this to happen prior to usage of the DbContext.
Given that people can new up an instance of a DbContext (synchronous) and then start querying against it, synchronously - there is never an appropriate point for async work to be awaited. The best I could initially do was this:
 public partial class AppTenantContext : DbContext
    {
        public AppTenantContext(EnsureMigrations<AppTenantContext> ensureMigrated)
        {
            // can't await here.. but can wait (blocking)
            ensureMigrated.EnsureMigrated.Value.Wait();
        }
 ...
}

For me this is a problem in EF core, in that it doesn't allow you to configure anywhere, some async work that will run prior to first use of the DbContext, non blocking. Simply because it doesn't force consumption of a DbContext through an async factory method.
So that led me to revert my DbContext constructor idea and create the following generic service:
    public interface IDbContextAccessor<TDbContext>
         where TDbContext : DbContext
    {
        Task<DbContext> GetDbContext();

    }

    public class DbContextAccessor<TDbContext> : IDbContextAccessor<TDbContext>
        where TDbContext : DbContext
    {
        private readonly EnsureMigrations<TDbContext> _migrator;
        private readonly TDbContext _dbContext;

        public DbContextAccessor(EnsureMigrations<TDbContext> ensureMigrated, TDbContext dbContext)
        {
            _migrator = ensureMigrated;
        }

        public async Task<DbContext> GetDbContext()
        {
            await _migrator.EnsureMigrated.Value;
            return _dbContext;
        }
    }

So the idea, is that when you want to do any work with a DbContext, you are forced to obtain it via an async method so that if work is required, is can be done asynchronously - like this:
IDbContextAccessor<AppTenantContext> dbContextAccessor = SomeInjectedAccessor();
var dbContext = await dbContextAccessor.GetDbContext();

Unfortunately this now has the drawback that a consumer could still bypass the migrations by constructing the DbContext directly and bypassing the IDbContextAccessor - but I can't find a good solution to that problem..
So my question is, is there a better solution for this, or any fundamental problems inherent in this solution that you think are likely to cause me issues further on down the line? Should I be solving this differently?
Also I think this IDbContextAccessor idea has potential for something that could be implemented by you guys, to allow us to register any setup tasks (like EnsureCreated, Migrate - seeding data etc) and have them run the first time DbContext is accessed.

@dazinator In general, running migrations as part of application startup is not something we recommend because:

It requires permission to modify the schema by the running application, which may not be available and/or desirable
It has concurrency issues that need to be handled carefully--you are touching on some of these above, and depending on other aspects of the configuration there can be more: for example, two application servers accessing the same database.

We would recommend that database migration happen as part of application deployment, rather than first run. The deployment may use scripts (e.g. generated from migrations) or may run tools directly against the production database. In either case, it is done in a controlled manner and in an environment with appropriate permissions.

Thank you for your response. That makes sense, especially for things like webfarms where each site points to a shared database. I was thinking of consumers of my nuget package whom have an application that might:

Have its own isolated database.
Not have any formal deployment process in place (I.e some cowboy/girl is manually deploying the app to a single node each release)
Be distributed / downloaded and installed via an msi

Having a mechanism to allow migrations to be automatically applied at application runtime (rather than through some CD process) still seems quite valuable for the above sorts of scenarios imho, would you agree? I imagine figuring out how to get wix to apply ef migrations during an installation might be quite painful in comparison. It seems fairly natural to me to want to ensure this work happens asychronously though. Anyway, thanks for the feedback.


reenable collection reflection tests, with impl details ignored

We still want to be able to verify the reflection system doesn't crash on these types, so let's just make sure the high level details hold.
Note that this is still relying on implementation details of these types which are slated to change. Each of these types has extra size and lacks extra inhabitants due to the use of an enum at their root. The eager bridging PRs change this. That said, tracking size/align/inhabitants isn't especially burdensome, and is probably worth doing. Although it's easy for these details to slip past CI since there's 32-bit and 64-bit configurations.
On that note: any easy way to have the CI check this PR on 32 bit? Looks like some memory layout details changed since these were turned off!
CC @dabrahams and @slavapestov

@swift-ci Please test

@shahmishal might be able to answer the 32 bit CI question.

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - be04a2b017c97f783b12c6e1dd53d4afac7cd93e
Test requested by - @Gankro

looks like full test does 32-bit!

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - be04a2b017c97f783b12c6e1dd53d4afac7cd93e
Test requested by - @Gankro

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - b6912b0ead4579af40c7a4d8ebd0fd56f71d5941
Test requested by - @Gankro

@swift-ci Please test

@swift-ci Please test

@dabrahams are you ok with committing to this level of implementation detail? This biggest fallout is my eager bridging PRs, but your string work will probably break these once or twice.

@Gankro in the interest of progress, I'm going to say "yes" for now.  You've made things better.  If I end up breaking more of these tests I'll rip out more of the detail.


thrash type entity state renders Invalid data in automation

The problem
using an automation based in state change I write that dat into the calendar. Up to 2024.12.0 this has always worked fine, but now I see below error.
still figuring out if this is user error (set up the wrong format in the config flow) or something changed in the actual entity state (output of the integration?)
Version of afvalwijzer integration having the issue?
2024.12.02
Version of Home Assistant Core having the issue?
2024.12.4
Anything in the logs that might be useful for us?
Logger: homeassistant.components.automation.afvalwijzer_in_calendar
Bron: helpers/script.py:2032
integratie: Automatisering (documentatie, problemen)
Eerst voorgekomen: 01:10:27 (1 gebeurtenissen)
Laatst gelogd: 01:10:27

automation 0: Error executing script. Invalid data for call_service at pos 2: Could not parse date for dictionary value @ data['start_date']

Additional information
apparently the variable date can no longer be set based on the state, need to find out why that is.
maybe I set the wrong format (iso) as I can remember I had the simpler 2024-12-21 before

(can not reconfigure though as the config flow is borked)
automation:

  - id: afvalwijzer_in_calendar
    mode: queued
    triggers:
      trigger: state
      entity_id:
        - sensor.afvalwijzer_gft
        - sensor.afvalwijzer_papier
        - sensor.afvalwijzer_plastic
        - sensor.afvalwijzer_restafval
      not_to: geen
    conditions: []
    actions:
      - variables:
          date: >
            {{trigger.to_state.state}}
          soort: >
            {{trigger.to_state.attributes.friendly_name}}
      - action: calendar.create_event
        target:
          entity_id: calendar.afvalwijzer
        data:
          summary: >
            Ophaaldag Saver: {{soort}}
          description: >
            {{soort}}
          start_date: >
            {{date}}
          end_date: >
            {{(as_datetime(date) + timedelta(days=1))
               |as_timestamp|timestamp_custom('%Y-%m-%d')}}

yes, that was an easy fix.
I edited the iso-format to false in the entity_registry, and restarted.
states returned to their regular format:

I then changed the state in the dev tools, and indeed that made the automation fire the action correctly, and write the dates in the calendar once again (ofc I deleted the fake date after setting it back to the correct date )

closing
(thugh it would be good to stipulate the date format and consequences in automations for calendar...)


"The system cannot find the file specified"

After connecting package to dotnet core 2.2 app hosted on ASF I am getting such exception:

Unexpected error happens on stopping service profiler.
System.ComponentModel.Win32Exception (2): The system cannot find the file specified    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)    at System.Diagnostics.Process.Start()    at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)    at ServiceProfiler.EventPipe.Client.UploaderCallers.OutOfProcCaller.Execute()    at ServiceProfiler.EventPipe.Client.TraceUploader.TraceUploaderProxy.<>c__DisplayClass2_0.<DefaultCallUploadAsync>b__0()    at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
--- End of stack trace from previous location where exception was thrown ---
at ServiceProfiler.EventPipe.Client.TraceUploader.TraceUploaderProxy.UploadAsync(DateTimeOffset sessionId, String traceFilePath, String metadataFilePath, Guid dataCube)
at ServiceProfiler.EventPipe.Client.ServiceProfilerProvider.UploadTraceAsync(PostStopOptions options, Int32 processId)
at ServiceProfiler.EventPipe.Client.ServiceProfilerProvider.PostStopProcessAsync(PostStopOptions e)

@s-krawczyk Thanks for the detailed logs. It seems like the issue is the uploader can't be unzipped. Do you know does your app have permission to write to target folder highlighted below:

If there is a different folder with write permission, could you overwrite LocalCacheFolder to redirect the output? Refer to Configurations page for details.

@s-krawczyk, have you get a chance to try it?

Not yet. Will try to find time this week.
pon., 21 wrz 2020, 18:43 użytkownik Saar Shen<EMAIL_ADDRESS>napisał:

@s-krawczyk https://github.com/s-krawczyk, have you get a chance to try
it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/ApplicationInsights-Profiler-AspNetCore/issues/97#issuecomment-696234317,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHV4T3UUP6GQA7Z45PWOGLSG57B7ANCNFSM4QSUAPFA
.

Thanks for the update.

Close this issue due to no actionable on the profiler side. Feel free to file new issues if there's more problem.

Validated it on ASF. What was required to be there is dotnet runtime in PATH variable. This was the reason. Please extend information in exception details what's wrong. It took me a while to find out this.

@s-drawczyk Thanks so much for the update.


Update UG of add, addmcq, and edit command

Codecov Report

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

@@            Coverage Diff            @@
##             master      #68   +/-   ##
=========================================
  Coverage          ?   52.03%
  Complexity        ?      374
=========================================
  Files             ?       90
  Lines             ?     1643
  Branches          ?      196
=========================================
  Hits              ?      855
  Misses            ?      712
  Partials          ?       76

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 b02fe6f...5bb1788. Read the comment docs.


Add command to build podman-remote-static

CRC Team wants a static podman-remote that it can install on any linux
box.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

lgtm

@mheon @cevich @baude How do I get this to build a version of podman-remote on the github.com/containers/libpod main page, that CRC team can grab?

Automatically? Excellent question. I've been manually compiling, zipping, and generating checksums, then attaching to releases.
Also, we should make very clear that we document these are for CRC only if we're posting them here. I don't want to be fielding issues about these not working on other distros because people saw them available and assumed they were official.

@mheon Sure we can write the wording however you want.

Since it is only podman-remote, it should not as popular, you still need a full podman to use it.

LGTM assuming happy tests.

@mheon @giuseppe @baude @QiWang19 @jwhonce @vrothberg PTAL

Automatically? Excellent question. I've been manually compiling, zipping, and generating checksums, then attaching to releases.

The really really really important thing left unmentioned is: We trust @mheon isn't doing evil things.   That doesn't automatically apply to automation, though there are some built-in security measures in Github Actions, there are almost none present for Cirrus-CI.

How do I get this to build a version of podman-remote on the github.com/containers/libpod main page, that CRC team can grab?

Assuming you can tolerate the build happening through a 'docker build' command.  A compromise here is: We set up an automatic build for a new image on quay.io, but reference this file ONLY for specific branches (and/or tags).  Then you simply update the README.md file with a link to those tagged images.  They will pick up any backports automatically, but otherwise will have a static name and tag.
@rhatdan could that work for now?  What would you like the image called?

BTW I don't mind if we don't automate this, as long as we had could test somehow that after a release all of the packages are complete and in place.  Maybe have a test that runs on PRs to ensure the current release is complete.  The thing we want to solve is making sure that @mheon or whoever cuts a release, completes all of the tasks, if the tasks are not automated.

We need to ensure that there is a MAC, Windows, Linux executable in place when podman-1.9.2 is released as an example.

If you are on Ubuntu or Debian you could just do the make podman-remote-static-local, and save the container part.

Ahh, okay, so in this case you may find this Cirrus-C feature interesting/useful..  Great for testing, not so much for publishing (safely).
I would suggest adding a comment to the Makefile and Containerfile.static explaining the container image is only needed temporarily, because the static-compile feature of glibc is required from a debian-like distro.  That way future maintainers/developers won't wonder why the makefile is building a thing to build a thing :smile:

The only reason to build this is for people who want to use podman-remote on distros without compiling and packaging. Mainly doing this for CRC.

So if I understand correctly, without automation @mheon would add a 'make podman-remote-staticto his release checklist, followed by uploading the compiled/src/github.com/containers/libpod/bin/podman-remote-staticsomewhere folks can get at it.  The container image is then discarded.  The libpodREADME.md` should/will have a link to download this binary.  Have I got that all right?

Yes.

Actually checking this again, after I remove some buildtags that should not have been there, this PR works without the second container.

lgtm

/lgtm


Fixed compilation warning with clang -Wpedantic

PR fixes the following compilation warning when using clang -Wpedantic:
clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -g -O2 -Wall -Wextra -Wshadow -Wmissing-prototypes -Wpedantic -Wunreachable-code -Wunused-result -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1        -o objects/message_test.o message_test.c
message_test.c:253:37: warning: format specifies type 'void *' but the argument has type 'char *' [-Wformat-pedantic]
        n = vim_snprintf(buf, bsize, "%p", ptr);
                                      ~~   ^~~
                                      %s

Codecov Report

Merging #5958 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5958      +/-   ##
==========================================
- Coverage   86.73%   86.71%   -0.02%
==========================================
  Files         140      140
  Lines      156082   156082
==========================================
- Hits       135370   135347      -23
- Misses      20712    20735      +23

Impacted Files
Coverage Δ

src/message_test.c
100.00% <100.00%> (ø)

src/gui.c
63.30% <0.00%> (-0.56%)
:arrow_down:

src/if_xcmdsrv.c
88.38% <0.00%> (-0.53%)
:arrow_down:

src/sign.c
94.77% <0.00%> (-0.26%)
:arrow_down:

src/gui_gtk_x11.c
57.69% <0.00%> (-0.15%)
:arrow_down:

src/diff.c
85.03% <0.00%> (-0.14%)
:arrow_down:

src/message.c
88.59% <0.00%> (-0.05%)
:arrow_down:

src/terminal.c
82.92% <0.00%> (-0.04%)
:arrow_down:

src/window.c
88.89% <0.00%> (-0.04%)
:arrow_down:

src/gui_gtk.c
31.33% <0.00%> (+0.27%)
:arrow_up:

Continue to review full report at Codecov.

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


Added some pertinent Comments For DE52

https://rally1.rallydev.com/#/detail/defect/341767637800?fdp=true

Makes sense to me.


xfwm4-themes: init at 4.10.0

Motivation for this change
Additional themes for XFCE.
The package is 5 years old and has version of 4.10 (actual XFCE is 4.12), yet there is nothing to update, it is basically graphic files of classic themes like Motif, Windows95, WindowsXP, etc
Ubuntu and other distros has the same version
It is not included in default XFCE of NixOS and won't bloat any existing installation.
pkgs.xfce.xfwm4themes should be explicitly added into environment.systemPackages for  extra themes to appear in the Window Manager settings box:

Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Hi. I like this change, although we might want to be able to configure the package to only contain some of the themes - what do you think?

@matthiasbeyer: there is a nix feature for radical customisation of any package:
      yourpackage = pkgs.existingpackage.overrideDerivation (old: {
        postInstall = old.postInstall + ''
          rm -rf $out/files-you-do-not-like
        '';
      });

it could be used to add or alter files as well.


IllegalArgumentException at AndroidNetworkListener.setupNetworkCallback

Fatal Exception: java.lang.IllegalArgumentException: Too many NetworkRequests filed
       at android.os.Parcel.readException(Parcel.java:1687)
       at android.os.Parcel.readException(Parcel.java:1636)
       at android.net.IConnectivityManager$Stub$Proxy.listenForNetwork(IConnectivityManager.java:2375)
       at android.net.ConnectivityManager.sendRequestForNetwork(ConnectivityManager.java:2790)
       at android.net.ConnectivityManager.registerNetworkCallback(ConnectivityManager.java:3009)
       at com.amplitude.android.utilities.AndroidNetworkListener.setupNetworkCallback(AndroidNetworkListener.kt:59)
       at com.amplitude.android.utilities.AndroidNetworkListener.startListening(AndroidNetworkListener.kt:32)
       at com.amplitude.android.plugins.AndroidNetworkConnectivityCheckerPlugin.setup(AndroidNetworkConnectivityCheckerPlugin.kt:42)
       at com.amplitude.core.platform.Timeline.add(Timeline.kt:23)
       at com.amplitude.core.Amplitude.add(Amplitude.kt:465)
       at com.amplitude.android.Amplitude.buildInternal$suspendImpl(Amplitude.kt:61)
       at com.amplitude.android.Amplitude.buildInternal(Amplitude.kt:1)
       at com.amplitude.core.Amplitude$build$built$1.invokeSuspend(Amplitude.kt:114)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:761)

Environment

Amplitude SDK Version: 1.16.7

We are seeing a large number of crashes caused by android.net.ConnectivityManager$TooManyRequestsException in our latest releases after updating to the new Amplitude-Kotlin SDK (Version: 1.16.7), which seems related to this issue.
We will try disabling Offline mode for now to hopefully prevent these crashes.
https://amplitude.com/docs/sdks/analytics/android/android-kotlin-sdk#offline-mode

Thanks for raising this folks. Taking a look.

@yogarunner @shawn-lin-013 - do you have a way of reproducing this issue?

@yogarunner @shawn-lin-013 - do you have a way of reproducing this issue?

I tried last week but was unable to find a reliable way to reproduce the crashes we are seeing in prod.

@yogarunner @shawn-lin-013 - do you have a way of reproducing this issue?

Hi @izaaz, We can't reproduce the issue either. 😢

Thanks @yogarunner @shawn-lin-013. We've added a try catch around the network connectivity listener so it should at least not cause any crashes. Thanks for reporting the issue!


Student org-focused GitHub user manager

Description:

In my three years w/ @uclaacm I've noticed that managing GitHub teams (and subteams) within an organization is quite frustrating. In particular, I do a lot of actions that I believe should be batchable. One driving use-case is member "rotation": when a student graduates, we should move them to the appropriate team and de-list them from any current projects.
The project proposal is to create a public data store and a service that acts on said store.
The store:

keeps track of all users in a GitHub organization,
and, tags them with relevant metadata: graduation year, degree type, types of roles, etc.

Then, we create a service that:

allows users to query the data store
allows administrators to batch-apply common actions to a set of users (ex "rotate out" all 2022 grads, promote all interns)

I believe we can implement this project in a very simple manner: a data store in some public repo (or similar), a stateless Lambda that calls into the GitHub API to perform said actions, and a trivial frontend that parses relevant data and manages user auth with GitHub SSO.
(also, this goes without saying - the intention is to make this useful for CL as well. interested to scope out how this problem manifests itself at Daily Bruin, etc.)

cc: @BryanPan342

Also, looks like the table-updating action is failing?
https://github.com/UCLA-Creative-Labs/cl-rfcs/runs/3224195468?check_suite_focus=true

Also, looks like the table-updating action is failing?
https://github.com/UCLA-Creative-Labs/cl-rfcs/runs/3224195468?check_suite_focus=true

Ahh.. if the doofus (me) actually read the docs, they would know that it should be labels not label in the github action

Something to think about is how opinionated the app should be.. Something like "interns" or "committees" might not apply to other orgs..
I'm totally okay will building something that hits a common use case between CL and ACM, but if we want this to be bigger, then we probably need to think about another solution?
As a whole though, it sounds like we could do this as a web app? Though I think it would be pretty cool to do this as a cli as well :)

Something to think about is how opinionated the app should be.. Something like "interns" or "committees" might not apply to other orgs..

Oh of course, I totally agree. I think the idea is that the tags are user-configurable, and then you can batch-apply actions to tags. The actions would be change teams, etc. - interns/committees/grad year are just names of possible fields.

but if we want this to be bigger, then we probably need to think about another solution?

Yeah for sure! I'll see if I can talk to someone @ DB on how all of this works on their end. Curious if this is something that Nova, DevX, Blueprint, etc. run into as well 👀

As a whole though, it sounds like we could do this as a web app? Though I think it would be pretty cool to do this as a cli as well :)

Yeah, I'm thinking web-app too, mostly just to minimize friction for the end user - I imagine the person doing this might be less technical within the club.


zsh: fatal error: sgtty.h: No such file or directory

I've just installed msys2-x86_64-20150202.exe and wanted to install zsh.
foo@bar MINGW64 ~/MSYS2-packages/zsh
...
gcc -c -I. -I../Src -I../Src -I../Src/Zle -I. -D_FORTIFY_SOURCE=2  -DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe  -o builtin.o builtin.c
In file included from zsh.mdh:15:0,
                 from builtin.c:33:
zsh_system.h:420:21: fatal error: sgtty.h: No such file or directory
 #  include <sgtty.h>
                     ^
compilation terminated.

FYI configure outputs (excerpt)
checking where the RLIMIT macros are located... restmp.c:1:26: fatal error: sys/resource.h: No such file or directory
 #include <sys/resource.h>
                          ^
compilation terminated.
/dev/null

zsh configuration
-----------------
zsh version               : 5.0.7
host operating system     : x86_64-pc-msys
source code location      : .
compiler                  : gcc
preprocessor flags        : -D_FORTIFY_SOURCE=2
executable compiler flags : -march=x86-64 -mtune=generic -O2 -pipe
executable linker flags   : -pipe
library flags             : -lpcre -liconv -lncursesw -lm
installation basename     : zsh
binary install path       : /usr/bin
man page install path     : /usr/share/man
info install path         : /usr/share/info
functions install path    : /usr/share/zsh/functions

Is there a package for this?

are you install msys2-runtime-devel?

I didn't, but there is still the error.
In the meantime, I found that pacman -S zsh works (see this blog). What is the difference then?

Just checking; did you update your installation?

When I got this error, it was a fresh install. Since then I haven't checked.

So you did not update? As the installer name (msys2-x86_64-20150202.exe) suggests, the installer is from February, so you need to run an update to get from "fresh" to "up-to-date". :)

At that time it was the latest version, stable I guess. After that I found that the package from pacman works, so I'm using it instead of trying to compile from this repo. I haven't understood the difference between the two, maybe you know?

The zsh package is compiled by us and then pacman -S zsh just downloads and installs it onto your computer. With makepkg, the compilation happens on your computer. Sometimes the GitHub repository contains a newer version of the package (happens regularly with -git and -svn packages).

Ok I hadn't understood that part. I'll retry compiling the package soon then.


Backport "add child to parent in completion context" to LTS

Backports #21214 to the 3.3.5.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to backport-lts-3.3-21343.
Reference


"Error: Unclosed element div" for template that worked with Handlebars

I have the following template that worked with Handlebars:
{{#if disableInteraction}}

{{/if}}
  Lots of stuff here
{{#if disableInteraction}}

{{/if}}

This worked great with Handlebars for Ember CLI. However, When trying to compile this using HTMLBars for Ember CLI, I get the following error:
Unclosed element `div` (on line 2)
Error: Unclosed element `div` (on line 2).
    at HTMLProcessor.nodeHandlers.Program (/path/to/app/bower_components/ember/ember-template-compiler.js:3385:17)
    at HTMLProcessor.acceptNode (/path/to/app/bower_components/ember/ember-template-compiler.js:3579:43)
    at HTMLProcessor.nodeHandlers.BlockStatement (/path/to/app/bower_components/ember/ember-template-compiler.js:3405:44)
    at HTMLProcessor.acceptNode (/path/to/app/bower_components/ember/ember-template-compiler.js:3579:43)
    at HTMLProcessor.nodeHandlers.Program (/path/to/app/bower_components/ember/ember-template-compiler.js:3375:16)
    at HTMLProcessor.acceptNode (/path/to/app/bower_components/ember/ember-template-compiler.js:3579:43)
    at preprocess (/path/to/app/bower_components/ember/ember-template-compiler.js:3551:55)
    at compileSpec (/path/to/app/bower_components/ember/ember-template-compiler.js:741:17)
    at TemplateCompiler.__exports__.default [as precompile] (/path/to/app/bower_components/ember/ember-template-compiler.js:643:14)
    at TemplateCompiler.processString (/path/to/app/node_modules/ember-cli-htmlbars/index.js:58:38)

Is this sort of template no longer supported, or is this a bug in HTMLBars?

This worked great with HTMLBars for Ember CLI. However, When trying to compile this using HTMLBars for Ember CLI, I get the following error:

That confuses me.  Do you mean that it worked fine with Handlebars, but not HTMLBars?

Even in Handlebars, this would not have worked properly (with bindings and whatnot).  See this JSBin using 1.9.0 that shows what I mean.  When you check the isEnabled checkbox, it adds the div's, but they are not updated properly (meaning Other Stuff is not in the right place).

@Kerrick Correct, it is not supported. You can think of block helpers like the new <template> tag.

That confuses me. Do you mean that it worked fine with Handlebars, but not HTMLBars?

Sorry, I did mean that.

Even in Handlebars, this would not have worked properly (with bindings and whatnot). See this JSBin using 1.9.0 that shows what I mean. When you check the isEnabled checkbox, it adds the div's, but they are not updated properly (meaning Other Stuff is not in the right place).

Interesting, it looks like this never actually worked and was always silently failing. Thanks for clarifying!

I understand that this is a feature, but does anybody know how we can render nested divs using HTMLbars, or is there any other tempating engine compatible with Ember?

Any news on how this could work without having to duplicate code ? Great work on Ember by the way :smile:


[BUG] - Reenable roundtrip tests for cardano-ledger ledger state and extended ledger state for the next release

Internal
Summary
https://github.com/IntersectMBO/cardano-ledger/pull/4072 fixes https://github.com/IntersectMBO/cardano-ledger/issues/3740 and so the mentioned failing roundtrip tests for ledger state and extended ledger state can be reenabled once we bump the dependency to cardano-ledger-shelley-test-<IP_ADDRESS>.
Note
This change also affects any related golden tests, so their expectations would almost most likely need to be updated.

Thank you, Aniket! :raised_hands:


 Electron doesn't seem to care at all about what I do, Chrome seems to be relatively unaffected, and Firefox reacts only to Noto Color Emoji... but seems to ignore every single font in the system when Noto Color Emoji is involved. I don't know where reports have to go anymore since everything doesn't work.

I was using Ubuntu 18.10, and Ubuntu definitely doesn't support coloured emojis out of the box. I generally install Noto using Font Manager and the ZIP file. I'll see when I have the chance to reinstall if installing Noto from the package manager makes a difference.

@NatoBoram Ubuntu 18.10 does support color emoji by default.
However, web browsers and web sites have different ways of handling emoji. (Also, LibreOffice and Qt apps are different.)
The font itself works so this is not the right place to report issues. You may need to report the issue to the specific web site that doesn't work or to the developers of the app you are using.

Closing as stale and possibly not the right place to pursue the issue.


[Documentation request]: Adding more topics in the Sidebar

Brief description
We have asked a few developers to go through our documentation and find the barriers they are facing while understanding Keploy. One of them found it difficult to navigate to different pages!
Recommendation
To make the documentation easy for navigation for the developers, we can increase the number of topics that are available in the sidebar. Currently, we have to go to the navbar to check for the topics available in the documentation.
Something like this:

@nehagup as I'm facing one issue while implementing this..
When I go to SDKs section, I'm getting this screen:

Problem

As I'm adding topics in the sidebar, where should I put the SDKs section?
And as the SDKs section opens up a new screen without any sidebar, even if we add that in the sidebar, it'll break the flow of the content in the documentation

@littleironical You can show a drop down with 4 subheadings where these SDKs are options

Okay, got it 👍


Is it possible to custom the value of the line-numbers?

Issue Type (delete the irrelevant ones)

[x] Question

Hello,
I recently work on the vue-good-table, I go through the documentation, there is no way to custom the value of the line number when I set line-numbers = true. And Actually I want change it to display another value.
Is there any solution for that?

@Vbubblery this is currently not possible but I'd be happy to review a PR


[build-scripts] Check for empty array and skip-test-swift argument before printing.

Currently, build-script-impl prints the following, irrespective of the setting of the -t or --test flag on build-script.

Building the standard library for: swift-stdlib-macosx-x86_64
Running Swift tests for: check-swift-macosx-x86_64

This seems misleading and I recommend removing the second line when the -t or --test flag is omitted.
Additionally, if the flags passed to build-script-impl are set in such a way that testing should occur, yet the SWIFT_TEST_TARGETS array is empty, the output would appear as:

Building the standard library for: swift-stdlib-macosx-x86_64
Running Swift tests for:

This edit will drop the second line of output in both cases above.

Here you can see the only other instance of SKIP_TEST_SWIFT, where it causes all swift tests to be skipped:
https://github.com/apple/swift/blob/master/utils/build-script-impl#L1916
Also, I noticed that dropping the -t or --test flag causes the --skip-test-swift flag to be set, while the --skip-test-osx remains unset. Is there an omission in build_script_impl_inferred_args that needs to be fixed? Or, is it desired behavior? I would open another PR. Thanks!
https://github.com/apple/swift/blob/master/utils/build-script#L569

@djwbrown The whole *-skip-* argument setup today is a little bit of a mess, I'd like it to be redesigned to be more easily understandable if possible.
The intent here is that those two flags are disabling testing along orthogonal axes: one disables testing specific products, and another disables testing specific platforms.


Question: What's the purpose of "LangChain.Core\Chains\StackableChains"

Hi! I'm learing the Rep, and confused about "LangChain.Core\Chains\StackableChains".
StackableChains is an extension of BaseStackableChain, and normally other chains extended BaseChain. I can't find the difference of BaseStackableChain and BaseChain.
My question is:

What's the difference of BaseStackableChain and BaseChain? What's the meaning of "Stackable"?
When will I use StackableChains?

Thanks! Great job!

Hi. @TesAnti can you please answer?

Hi, @evolcano and thank you for interest in our project. As you have noticed, we have 2 base classes BaseChain and BaseStackableChain.
BaseChain is legacy class. It was there first and it is used in classes that replicating original LangChain API. But this original API was not easy to use. And, when python version developers realized this, thay came out with LCEL. Which is better, but still hard to use. They are still trying to improve.
At this moment we dicided that we will not follow python developers experiments and will take our own path. This is how we came with concept of stackable Chains. They are easy to understand, read and use. Stackable means that each chain is independent and can stack on top of other chains.
The answer to your second question is simple: Always. You can check our wiki to see different use cases and, if you dont find one you interested in, - just create an issue with request to make it.

I got it !  And I found your stack operation which similar to LangChain:
    public static StackChain operator |(BaseStackableChain a, BaseStackableChain b)
    {
        return new StackChain(a, b);
    }

Thanks!


[BUG] Page Overflow in small screeens.

Description
In mobile devices, there is a page overflow on the front page it's shown in the screenshot below.

The issue I guess is because of the container in the next section which has image animations that moves from the negative X direction to its original position.

Screenshots

Browser 🥦
Brave
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (blank for no)

Great issue, the solution would be to stop the aos animations for mobile.

Hey @IAmTamal Can you assign this issue to me?

Thank you @IAmTamal  for assign this issue to me.

Thank you @IAmTamal for assign this issue to me.

Do make a PR once done !

Hi there, it has been a while. I would love to know what changes you are making and/or are working on this. Please reply shortly.

Hey @IAmTamal Sorry for being late because in the previous 2 weeks was gone in my exam so I was not able to make these changes. But I will do this issue this weekend.

Cool !

I have one more solution to it. In the App component replace the empty angular tags with a div with class name of say "app" and then in it's CSS file add overflow - x: hidden;


Restangular doesn't accept JSON response containing empty string or number 0

If you have a Rest API (ex. http://server.com/api/data) returning the following value :
""

or
0

when calling :
Restangular.one('data').get().then(function(data){
   // data = undefined instead of "" or 0
   console.log(data)
});

If we try to get the same JSON using angularJS $http, the results are not undefined, but "" and 0. Restangular should do the same.
Here is a plunker showing the bug : http://plnkr.co/edit/yE9o3iPL0ZVa87gNuzGG
Open your console and run the plunker.
Apparently the problem is due to a if condition in the okCallback function located in the elemFunction function.
Here is the excerpt of the code :
var okCallback = function(response) {
          var resData = response.data;
          var fullParams = response.config.params;
          var elem = parseResponse(resData, operation, route, fetchUrl, response, deferred);
          if (elem) {  // <-- this test is causing the bug
             ...

To solve the problem the if(elem) test should be replaced by :
if (elem || elem === 0 || elem === '') {

or
if (elem !== undefined && elem !== null) {

I'm just curious about the use case as to why a server would return "" or 0, versus those 2 other values. Your fix makes sense, just curious about the why. :smile:

I probably didn't phrase it well, the API returned value is not switching between number and string :smile:. To rephrase it, it will be better to say : If you have a REST API returning 0 or another REST API returning "". The following problem will occur [...]


  Please redo the PR with only your changes.

please also include a title that matches what your PR is.


chore: Bump EUI to v58

Summary
Bumps EUI to the latest version.
Aside from simply upgrading EUI, this version of the library eliminates some annoying erroneous error logging that has been plaguing the recorder for months.
Implementation details
Simply updates the EUI dependency, and its associated packages.
How to validate this change
The only changes would be visual, and they are likely minute changes.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-05-20T12:50:38.185+0000

Duration: 9 min 22 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
73

Skipped
0

Total
73

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test all : Re-trigger the build for all the stages.


Expose ServiceWorker class

See https://api.dartlang.org/be/154774/dart-html/ServiceWorkerContainer/controller.html
https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorker

Why is this being added to beta 3, which is quite close?

We can bump off. Let's discuss tomorrow.

All of the other ServiceWorker interfaces are exposed this was hidden from
our 45  roll and I've removed the hidden state (removal of _).
On Mon, Mar 26, 2018 at 8:54 PM Kevin Moore<EMAIL_ADDRESS>wrote:

We can bump off. Let's discuss tomorrow.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/32675#issuecomment-376388842,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB9ewVv8v0Dssx_bUaew9lW9Xhfc9bxCks5tibgCgaJpZM4S7wDv
.

Fixed https://dart-review.googlesource.com/c/sdk/+/48381


Uniques aren't unique in the test-suite

In ghci, Uniques are indeed unique, e.g.
*Main> ( mkId "x", mkId "y" )
(Id {name = "x", unique = <1>},Id {name = "y", unique = <2>})
*Main> mkId "z"
Id {name = "z", unique = <3>}

But, in the test-suite, all the uniques have the same value, which happens to be <1>. Not sure why, so more investigation is necessary.

Looks like Data.Unique.newUnique needs to be used with Test.Tasty.withResource.


Can we haz dark mode?

Hi,
as far as I can see stringer uses an older version of Bootstrap. Can this be upgraded to a newer version where dark mode is supported and can we have a switch to enable it? 😃
Thanks for considering this.
Cheers

@duenni I'm not opposed, but I don't think I'll get to it any time soon. If you want to give it a try, I'll be happy to look over a PR. Not a prerequisite, but I'd like to remove Bootstrap at some point. I think it's a bit heavy for such a small app.


Adding Swashbuckle.AspNetCore to my ASP.NET Core MVC 3.0 project causes build failure

When I add Swashbuckle.AspNetCore 5.0.0-rc3 to my ASP.NET Core MVC 3.0 web application, I get a build failure:

MSB3073 The command "dotnet "C:\Users\jonsagara.nuget\packages\microsoft.extensions.apidescription.server\0.3.0-preview7.19365.7\build/../tools/dotnet-getdocument.dll" --assembly "C:\Dev\MyApp\src\MyApp\bin\Debug\netcoreapp3.0\MyApp.dll" --file-list "obj\MyApp.OpenApiFiles.cache" --framework ".NETCoreApp,Version=v3.0" --output "obj" --project "MyApp" --assets-file "C:\Dev\MyApp\src\MyApp\obj\project.assets.json" --platform "AnyCPU" " exited with code 7

If I copy that command and run it from PowerShell in the project directory, I get the following stack trace:
PS C:\Dev\SANDBOX\SwashbuckleAspNetCoreBuildFailure\SwashbuckleAspNetCoreBuildFailure> dotnet "C:\Users\jonsagara\.nuget\packages\microsoft.extensions.apidescription.server\0.3.0-preview7.19365.7\build\/../tools/dotnet-getdocument.dll" --assembly "C:\Dev\SANDBOX\SwashbuckleAspNetCoreBuildFailure\SwashbuckleAspNetCoreBuildFailure\bin\Debug\netcoreapp3.0\SwashbuckleAspNetCoreBuildFailure.dll" --file-list "obj\SwashbuckleAspNetCoreBuildFailure.OpenApiFiles.cache" --framework ".NETCoreApp,Version=v3.0" --output "obj" --project "SwashbuckleAspNetCoreBuildFailure" --assets-file "C:\Dev\SANDBOX\SwashbuckleAspNetCoreBuildFailure\SwashbuckleAspNetCoreBuildFailure\obj\project.assets.json" --platform "AnyCPU"
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProviderException: Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/cb7dea2a-b2a2-42c5-8f30-db24236af1ae. Exception Message: Tried the following 3 methods to get an access token, but none of them worked.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/cb7dea2a-b2a2-42c5-8f30-db24236af1ae. Exception Message: Tried to get token using Managed Service Identity. Unable to connect to the Managed Service Identity (MSI) endpoint. Please check that you are running on an Azure resource that has MSI setup.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/cb7dea2a-b2a2-42c5-8f30-db24236af1ae. Exception Message: Tried to get token using Visual Studio. Access token could not be acquired.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/cb7dea2a-b2a2-42c5-8f30-db24236af1ae. Exception Message: Tried to get token using Azure CLI. Access token could not be acquired. 'az' is not recognized as an internal or external command,
operable program or batch file.

   at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProvider.GetAuthResultAsyncImpl(String resource, String authority, CancellationToken cancellationToken)
   at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProvider.<get_KeyVaultTokenCallback>b__8_0(String authority, String resource, String scope)
   at Microsoft.Azure.KeyVault.KeyVaultCredential.PostAuthenticate(HttpResponseMessage response)
   at Microsoft.Azure.KeyVault.KeyVaultCredential.ProcessHttpRequestAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at Microsoft.Azure.KeyVault.KeyVaultClient.GetSecretsWithHttpMessagesAsync(String vaultBaseUrl, Nullable`1 maxresults, Dictionary`2 customHeaders, CancellationToken cancellationToken)
   at Microsoft.Azure.KeyVault.KeyVaultClientExtensions.GetSecretsAsync(IKeyVaultClient operations, String vaultBaseUrl, Nullable`1 maxresults, CancellationToken cancellationToken)
   at Microsoft.Extensions.Configuration.AzureKeyVault.AzureKeyVaultConfigurationProvider.LoadAsync()
   at Microsoft.Extensions.Configuration.AzureKeyVault.AzureKeyVaultConfigurationProvider.Load()
   at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList`1 providers)
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
   at Microsoft.Extensions.Hosting.HostFactoryResolver.Build(Object builder)
   at Microsoft.Extensions.Hosting.HostFactoryResolver.<>c__DisplayClass8_0.<ResolveServiceProviderFactory>b__2(String[] args)
   at Microsoft.Extensions.ApiDescription.Tool.Commands.GetDocumentCommandWorker.Process(GetDocumentCommandContext context)
PS C:\Dev\SANDBOX\SwashbuckleAspNetCoreBuildFailure\SwashbuckleAspNetCoreBuildFailure>

This looks like it's invoking my application and failing on Azure KeyVault configuration, code which is only supposed to run in non-local environments:
        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStartup<Startup>();
                })
                .ConfigureAppConfiguration(
                    (context, config) =>
                        {
                            // In Azure environments, we use Key Vault for connection strings.
                            // See: https://docs.microsoft.com/en-us/aspnet/core/security/key-vault-configuration?view=aspnetcore-3.0#use-managed-identities-for-azure-resources
                            if (context.HostingEnvironment.IsStaging() || context.HostingEnvironment.IsProduction())
                            {
                                // Grab the Key Vault name and Azure AD Application Id from App Settings stored in Portal.
                                var builtConfig = config.Build();

                                // Create an instance of the AzureServiceTokenProvider class without a connection string. When a connection string
                                //   isn't provided, the provider attempts to obtain an access token from Managed identities for Azure resources.
                                var azureServiceTokenProvider = new AzureServiceTokenProvider(connectionString: null);

                                // Create a new KeyVaultClient with the AzureServiceTokenProvider instance token callback.
                                var keyVaultClient = new KeyVaultClient(new KeyVaultClient.AuthenticationCallback(azureServiceTokenProvider.KeyVaultTokenCallback));

                                // The KeyVaultClient instance is used with a default implementation of IKeyVaultSecretManager that loads all secre
                                //   values and replaces double-dashes (--) with colons (:) in key names.
                                config.AddAzureKeyVault(
                                    vault: $"https://somevault.vault.azure.net/",
                                    client: keyVaultClient,
                                    manager: new DefaultKeyVaultSecretManager()
                                    );
                            }
                        });

Is there a way to work around this?
Sample repo with reproduction steps in the readme is located here: https://github.com/jonsagara/SwashbuckleAspNetCoreBuildFailure
Thank you.

Looks like there is a workaround: https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/1226#issuecomment-530894591
I'm not clear on how much of Swashbuckle that disables, though. Seems like there is still an underlying issue that needs fixing.

Tracking in #1266

@jonsagara - the workaround doesn't disable any part of Swashbuckle, it just disable some new .NET Core SDK features that leverage Swashbuckle at build time.


Cannot use this page to accurately determine what services are available via Private Link in Azure China

This page makes it impossible to determine which private link services are available in Azure China because it fails to define "all public regions."
For example, Azure SQL Database is available in "all public regions, all government regions and all China regions." One would think all services available for private link connection in Azure China would be listed this same way and the absence of "all China regions" would indicate unavailability.
Yet for the Azure Storage Files service, "all China regions" is not specified. However, one can, for example, create a private link to Azure Files in an Azure China storage account from a VM in Azure China.
Documentation on features on docs.microsoft.com should be authoritative and clear. This page is neither.

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

ID: 97849a4b-e79a-840e-8cfc-d43b0ea1dec3
Version Independent ID: 6d224a2c-5e53-832a-ecd4-ae30fd472b76
Content: Azure Private Link availability
Content Source: articles/private-link/availability.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

@yobyot We are checking this and will get back to you.

@asudbring Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Sending to PM for review
#reassign:@ivapplyr

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


Support services settings

Start of #20619
This expands the "configure" request to include a second set of settings. It also adds the settings as a new parameter to getCompletionsAtPosition; we'll probably want to add it to many other LanguageService methods eventually.

FYI @RyanCavanaugh

We also need this in the importfixes file, do you plan on doing this in a separate PR or in this PR?

Most services may eventually need these options -- should we just add it to all methods now instead of doing it one-by-one as we need it?

Most services may eventually need these options -- should we just add it to all methods now instead of doing it one-by-one as we need it?

GotoDef, findAllRefs, rename, sighelp, etc.. will not need it.. we just need it in things that will generate code, namelly completions, quickfixes, and refactoring. Formatting has its own thing.

I'm not sure I understand the high-level goal of this change.  It seems like we wanted to add an option to completion but wanted to avoid having to pass it on every call to completion (vs doing it once at the beginning)?

I'm not sure I understand the high-level goal of this change. It seems like we wanted to add an option to completion but wanted to avoid having to pass it on every call to completion (vs doing it once at the beginning)?

we want to add options to codeAction creation logic. that would be in completion (with imports), in quick fixes, and refactoring. the common issues are for instance which quote to use for module names.
These options are more like formatting options, they should be provided once at the beginning, or when they change.

These are exposed in VSCode settings:
Quote style:
"typescript.preferences.quoteStyle": "double"

or
"typescript.preferences.quoteStyle": "single"

module import relative vs non-relative:
"typescript.preferences.importModuleSpecifier": "relative"

or
"typescript.preferences.importModuleSpecifier": "non-relative"


Unguard xcode version check in FastlaneCore::ItunesTransporter

Quite some time ago in #4631 ("Only query for xcode version on macs") a Helper.is_mac? &&  was added as "guard" before Helper.xcode_version.start_with?('6.'), so only if run on mac, the xcode version is actually checked:
https://github.com/fastlane/fastlane/blob/c99910b79a8a22bd6423acd8ebd1a62d5e6b9e99/fastlane_core/lib/fastlane_core/itunes_transporter.rb#L307
Unfortunately I could not find out why this was done. I assume it was done to make this code not crash on system that do not have Xcode installed - which may have raised an exception if you went to check for the version.
Unfortunately it has the side effect of also making tests, that mock this xcode version check to the required 6.x version so the ShellScriptTransporterExecutor is used, not pass on non-Mac platforms.
Fortunately Helper.xcode_version got its own guard a few months ago in PR https://github.com/fastlane/fastlane/pull/9998:
https://github.com/fastlane/fastlane/blob/5019acb53fc2adf050b4227c3e3216e365ba36ec/fastlane_core/lib/fastlane_core/helper.rb#L143
With this new check, the additional check in ItunesTransporter is not necessary any more (as the version will be returned as nil on non-Mac platforms instead of raising an exception) and can be removed - which this PR does.

Huh, nice find, and extremely thorough analysis!

I want to note that I first removed that is_mac check, and only later figured out why it worked. 🤣
While posting my PR I then even found the PR responsible for it 😆


[TaskLayer] ToolTip disable

This PR closes #173 and closes #172

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question about the calculation of peak GPU memory

Hi, I would like to ask a question about the calculation of peak GPU memory.
As shown in the paper's Table 9, the peak GPU memory (224 × 224 inputs with 32 batch size & FP16) of R2-Tuning is 10.6GB.
While in the provided training log of qvhighlights, the memory is "memory: 28746" using:
# nncore
mem = torch.cuda.max_memory_allocated()
mem_mb = torch.IntTensor([int(mem / (1024 * 1024))]).cuda()
'memory: {}'.format(mem_mb.item())

How can we obtain the result in the Table 9? Thank you!

Hi @HenryHZY! The memory in the training log was calculated from bs=128. You may run the model again with bs=32 to align the results in Table 9.


Update machine-learning-apps-anomaly-detection.md

Nothing has changed in this date. Refreshed date.

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

It looks like you're working at Microsoft (luisca). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


GH-62: Feature; Added "back" button for NPC Attack Frame

Added a "back" button once you attack a NPC and also made the NPC tab update values of the lost troops.

Issue: gh-62

set the value for all IntegerOnlyInput(s) to 0

I have made the requested changes; please review again

LGTM

Tested, please merge @ItsNeil17


I.e., this fails:
$ pipenv install 'requests[socks]'
# long traceback ending with
  File "/Users/jtratner/pipenv/pipenv/vendor/pipfile/api.py", line 103, in parse
    parsed_toml = self.inject_environment_variables(toml.loads(content))
  File "/Users/jtratner/pipenv/pipenv/vendor/pipfile/api.py", line 79, in inject_environment_variables
    d[k] = self.inject_environment_variables(v)
  File "/Users/jtratner/pipenv/pipenv/vendor/pipfile/api.py", line 79, in inject_environment_variables
    d[k] = self.inject_environment_variables(v)
  File "/Users/jtratner/pipenv/pipenv/vendor/pipfile/api.py", line 81, in inject_environment_variables
    d[k] = [self.inject_environment_variables(e) for e in v]
  File "/Users/jtratner/pipenv/pipenv/vendor/pipfile/api.py", line 75, in inject_environment_variables
    for k, v in d.items():
AttributeError: 'unicode' object has no attribute 'items'

but this PR gets it to work again - woo!
I will open up an additional PR against the pipfile repo sometime later, just figured it'd be good to unbreak the build :) (I also need to fully grok how extras get converted into a dictionary format)
cc @dvf

Nice catch, thanks @jtratner


Passing data to a script as a variable

I have a struct I want to pass to a script. Atm I'm calling a get_input_data() function from the script and binding the struct to a var. This works fine, but means all scripts have to have the first line.
I would like to just set this data to a var called input. From what I can see, that is maybe possible by getting the root package (CorePackage?) and reaching into the module, where I could call set_var.
let core_package = CorePackage::new(); let core_module = core_package.get(); // core_module needs to be mutable, but it's wrapped in an Rc<> core_module.set_var("test_input", "test_string"); engine.load_package(core_module);
But I can't access the set_var function dues to mutability constraints.
So firstly, Is it possible to set a variable from Rust for use by a Rhai script?
second, if so, am I going about this the right way?
Thanks ;)

Just pass it inside a scope:
let payload = SomeThingIWantToPassToAScript::new();

let mut scope = Scope::new();

scope.push_constant(payload);

engine.eval_with_scope(&mut scope, script)?;

@schungx  excellent, works like a charm ;)