Proposel: dynamic partials

Hi all, I'm new to moustache so please correct if there is a way to do this. I've been using Mu2 and Node.js as a bit of context.
I could like to be able to create a skeleton moustache template and then tell it which partials to include. The reason for this is that using this top down approach to assembling a document means that each template only needs to be aware of the content it contains, not that which is around it. An example is this - with some help from the Mu2 developer I current need templates like this:
view
{
    heading: "MY content heading",
    content: "
Some text
"
}

Main render: content.mustache
{{> header}}
{{heading}}
{{& content}}
{{> footer}}

Partial: header.moustache

    <headers></headers>

Partial: footer.moustache

This will work for the moment, but it's rather ugly because the content has to know what goes around it. It also has problems if I need (for example) to select different partials in the headers and the content. What I would much prefer to be able to do is this:
view
{
    contentPartial: "content",
    heading: "MY content heading",
    content: "
Some text
"
}

Main render: page.moustache

    <headers></headers>

        {{> contentPartial}}

Partial: content.mustache
{{heading}}
{{& content}}

So when the rendering encounters the {{> contentPartial}} code, it detects that contentPartial is a value in the view, insert's it's value and then continues to include, thus including the content.moustache partial.
Please let me know if there is a way around this issue - lamda's perhaps?

Superseded by #54 and #134.


Add the ability to quit all terminal instances

Summary of the Pull Request
Add the ability to quit all terminal instances. Doing this separately from the window layout saving ones to lessen the number of 1k+ line monsters I make y'all review.

References
#11083

PR Checklist

[x] Closes #11081
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[x] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments

Warn the user before they do so to give a chance to cancel
Percolate a QuitAll event up to the monarch who then directs each peasant to clsoe.
Leave a window-layout-saving-sized hole to add that feature on top

Validation Steps Performed

quit with one window (from the monarch)
quit from the monarch with multiple windows
quit from a peasant
cancel the quit dialog

man ronpaul.gif is really getting a lot of milage this release

Ah! Don't forget to update the docs repo!


Output_plate names different from Input_plate names

Would it be possible to have different names for the input and output plates, i.e. input_plate = '0000078500', '0000065750' and '0000059864', to be returned as output_plate= 'final1', 'final2' and 'final3'?

Thanks for the issue, this is fixed in #96d94c7


Some GAr-related additions

Added GArSoft reconstruction to SRInteractionBranch and SRRecoParticlesBranch.
Small additions to SRGAr and other GAr-related classes. Also, created SRGArPartcile class (inherits from SRRecoParticle) to include additional low-level information in SRGAr.

Hi Jeremy! Thanks for reviewing this. I made some changes, trying to separate the detector-y and particle-y things as much as I could. Does it look better now?

Is this PR one that Francisco mentioned at the collaboration meeting (Sep. 10)?  It has been languishing in review for a long time.   Can we get this to move?

Hi @chenel! Sorry it took me so long, I've been thesis writing all summer.
Do you mean creating 3 vectors in SRRecoParticlesBranch, each one containing the particle information with one of the scores? The thing is the particles generated are the same (they are all produced with the same reconstruction), it's only they have 3 different scores that we use for their PID.
I can try to make the SRPIDScoreBranch simpler, maybe just populate it with these gar_mu, gar_proton_dedx, gar_proton_tof vectors. Does that sound ok?

Do you mean creating 3 vectors in SRRecoParticlesBranch, each one containing the particle information with one of the scores?

Yeah, that's what I had in mind.  It's fairly clunky but is the way different particle hypotheses are constructed elsewhere.  Particles are not specific to GAr after all--the only thing that's different is what sort of thing made them, but the user doesn't always care about that.


legend colors & plot data should both be controlled by the opacity slider

related to: https://github.com/VEuPathDB/web-eda/issues/1487 & https://github.com/VEuPathDB/web-eda/issues/1605
since the markers now have transparency, the legend for the overlay variable) should also have that amount of transparency so that the colors actually match up.

@aaronwlsong when qa'ing this, look at a scatter plot

Looks good, closing ticket.

@aaronwlsong Thank you for your tests 👍


Error when using carthage

After installing the last version 4.6.1 with carthage and adding the NVActivityIndicatorView and NVActivityIndicatorViewAppExtension to the project, I get the following error when running on the simulator:
Found bundle at /Users/user/Library/Developer/XCTestDevices/EDE1D09E-7C8A-4A03-B122-55BA26CA34CA/data/Library/Caches/com.apple.mobile.installd.staging/temp.7eRVwf/extracted/Payload/AppName.app/Frameworks/NVActivityIndicatorViewAppExtension.framework with the same identifier (me.vinhis.NVActivityIndicatorView) as bundle at /Users/user/Library/Developer/XCTestDevices/EDE1D09E-7C8A-4A03-B122-55BA26CA34CA/data/Library/Caches/com.apple.mobile.installd.staging/temp.7eRVwf/extracted/Payload/AppName.app/Frameworks/NVActivityIndicatorView.framework

Could you try again with a clean carthage build? There's a recent change on the product name which probably messed up carthage build.

I just removed NVActivityIndicatorView and NVActivityIndicatorViewAppExtension from my Build/iOS folder. Having github "ninjaprox/NVActivityIndicatorView" == 4.6.1 in my cartfile I run carthage update --platform ios. The build of the app finish successfully (so it is not a build error), the error shows up when installing it to simulator, and the full Xcode error says:

Title: This app could not be installed at this time.
Body: Found bundle at /Users/user/Library/Developer/XCTestDevices/EDE1D09E-7C8A-4A03-B122-55BA26CA34CA/data/Library/Caches/com.apple.mobile.installd.staging/temp.7eRVwf/extracted/Payload/AppName.app/Frameworks/NVActivityIndicatorViewAppExtension.framework with the same identifier (me.vinhis.NVActivityIndicatorView) as bundle at /Users/user/Library/Developer/XCTestDevices/EDE1D09E-7C8A-4A03-B122-55BA26CA34CA/data/Library/Caches/com.apple.mobile.installd.staging/temp.7eRVwf/extracted/Payload/AppName.app/Frameworks/NVActivityIndicatorView.framework

Oh I got it. You should either use NVActivityIndicatorView or NVActivityIndicatorViewAppExtension. In fact, NVActivityIndicatorView is inclusive of NVActivityIndicatorViewAppExtension. You only need to use NVActivityIndicatorViewAppExtension in an app extension.

Okey, got it, thanks!


FREE??

Is this tool always free or is it constrained to the free apis ???
Because it seems like it uses Google etc apis so maybe it's not free forever or anyway it is limited.

Hi @ireneb612, Yes this tool is free as stated in the docs and description. It does not use the Google API! it uses web scraping when possible, therefore decoupling the need to use an API. On the other hand, some translators like DeepL require an API therefore, this tool gives the freedom to the user to use that API (if they want).

You could ve formatted your question better


"yarn start" having error

Step 1: "git clone" this repository;
Step 2: "yarn install", install all the dependencies;
Step 3: "yarn start", will report below error:

Hi!
It looks like this is an issue with electron and your Linux/Mac distribution; searching for "electron libnss3.so" I can find several hits about this issue and electron/chromium projects, such as https://stackoverflow.com/questions/58134793/error-while-loading-shared-libraries-libnss3-so-while-running-gtlab-ci-job-to
Let me know if you find out which was the issue in your distribution.


refactor ocp for OIT

refactor refresh-images for OIT

@jupierce There was an errant } that the linter didn't seem to pick up. I think all the fully left justified multi-line strings are throwing it off.


https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe says fallback content is allowed

Request type

[ ] New documentation
[x] Correction or update

Details
The MDN documentation page says:

Permitted content: Fallback content, i.e. content that is normally not rendered, but that browsers not supporting the  element will render. (RSS readers and email clients often show the fallback content instead.)

However the W3 and whatwg standards say:

An iframe element never has fallback content, as it will always create a nested browsing context, regardless of whether the specified initial contents are successfully used.

As a result, the W3 validator sees fallback content as an error: "Text not allowed in element iframe in this context."
I didn't dare to go and edit the page myself because I'm not sure if it is intentional that fallback content is documented, even if it goes against standards.

The fallback content only applies to really old browsers or some email clients that don’t understand the <iframe> tag, which was added in HTML 4.
If you were to use the W3C validator with HTML 3.2 or older, it will tell you that the <iframe> element doesn’t exist.

Fair point. So the question is: what does MDN intend to document? HTML3.2? HTML4? HTML5? All of them?
In any case, I seems wrong to state that there is permitted content for the iframe element. If fallback content happens to work in older browsers that's a nice trick for those who need it, but should it be listed as if it were part of the standard? IMHO the paragraph about permitted content should at least mention that this goes against the standard.

The article should state that fallback content is not allowed, perhaps with a note that older browsers may have once supported it.

Well, that list would only include browsers that are older than HTML 4, and therefore don’t have an <iframe> implementation, which results in them treating it as an unknown element.

I've just updated the permitted content to "None" — I think it is confusing to state what the behavior was in an old version of HTML that browsers don't support any more.


create CONTRIBUTING.md file aligned with FINOS project blueprint

Can one of the admins verify this patch?

hi @crepache @leomcabral @vincentmg @ecarrenho-daitan can you please help with this? many thanks.


resin trap bugs

you cant examine them and they are rendered over the pointer arrow

you have to right click then examine it in the menu, i think its missing Clickable or something


Important UI things to include in test

This should check for important UI stuff such as correct title, menu, logo, ect

Permanent Things:
Title Should Always Be: Kennett High School Mini-THON (IN BIG FONT)
Underneath title: "Join us on February 26, 2016"
Underneath the underneath (above signup button): For the Fight. For The Cure. For The Kids.
Link to sing-up page
Committee Names and Email addresses
Instagram link
Twitter link
Facebook link (when we have it)
All of the links from the diamonds ("Mini-THONs" ; "Donations" ; "Raising Awareness" ; "Research") stay the same
The Donate Button link stays the same https://fourdiamonds.donordrive.com/index.cfm?fuseaction=donate.event&eventID=1179
The details and information in Issue #15 should go on the site and stay there.

We good here


fix: mainnavigation underneath 1024px viewports

Resolves https://github.com/db-ui/elements/issues/1964

any updates when this can be expected in a release?

@mriehl we'd like to both clean up as well as resolve a lot of open issues within the backlog by concentrated attention in January.

@mriehl we'd like to both clean up as well as resolve a lot of open issues within the backlog by concentrated attention in January.

uhm okay. I would have expected this issue to be higher priority, since any page using DB elements is completely unusable on a smaller viewport (if using a menu). But I guess if there are more important things it will have to wait.
It's quite difficult to explain to users who complain about the unusable navigation that I am using an official framework and it's simply broken upstream.

@mriehl we'd like to both clean up as well as resolve a lot of open issues within the backlog by concentrated attention in January.

uhm okay. I would have expected this issue to be higher priority, since any page using DB elements is completely unusable on a smaller viewport (if using a menu). But I guess if there are more important things it will have to wait.
It's quite difficult to explain to users who complain about the unusable navigation that I am using an official framework and it's simply broken upstream.

I actually don't know what kept us away from merging this earlier. Maybe there's still some outstanding features, but this should serve quite well as fix for the moment without breaking anything, but actually fixing the problem itself.
So I'll release this in the next half an hour.

Thanks @mfranzke !

Thanks @mfranzke !

thanks for your feedback & reportings.


fix: Remove Second Arg from optional tf function

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.


perhaps the server part should use python instead of nodejs

I have investigate some python lib like langchain and gpt_index, it could create something like new bing or even more powerful function.  perhaps the server part should be implement by python and use some libs like langchain to extend chatgpt abilities.  I have found some interesting repo : https://github.com/circlestarzero/EX-chatGPT/blob/main/README.en.md

My current thinking about LangChain (and similar projects) is that if it's added to this project, it should be as part of an extension/plugin system. I'm picturing a screen in the app that shows a list of optional integrations the user can enable or disable.
However, I want the application architecture to be more stable and to have a better idea of what specific integrations are wanted before starting work on this.
For now, my goal is to keep the server lightweight and implement as much functionality as possible in the browser instead - so that we have the flexibility to make decisions like this (switching to Python) at a later date if needed.

it should be as part of an extension/plugin system. I'm picturing a screen in the app that shows a list of optional integrations the user can enable or disable.

yes, I think this is a direction for future llm.

For now, my goal is to keep the server lightweight and implement as much functionality as possible in the browser instead

I agree, this way i could put this web on a object store, without a backend. save a lot of money


documentation touchups

doc/maintainers.md is taking a while, but the rest of these changes are still valuable.

I don't think these documentation changes warrant review. Merging...


Update royal-tsx to <IP_ADDRESS>0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

brew cask style is failing as the comment above the url stanza does not match due to the interpolation, but otherwise everything else is fine.

@miccal You’re right, hadn’t noticed. Apologies, @artdevjs, mind changing it back? Since the major number changes only sporadically, it’s preferable to have the cask not break on checks.
I remember we had similar cases when introducing this cop. Did we have a better solution, @reitermarkus?

Closed by mistake.

https://github.com/caskroom/homebrew-cask/pull/28069


channeldb: node channels cache [poc]

Rough outline that shows how in-memory pathfinding could be implemented by extending the existing graph channel cache.

Superseded by #5642. Thanks for the PoC!


Add a "mirror position" option to the Board Editor

see lichesstools.reverseFen

Implemented in v.2.3.26


[IN DRAFT][WIP][CI] add code coverage to nightly

Motivation
We have code coverage working locally via grcov.  We can integrate it with nightly CI and push the coverage report to codecov.io
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan

Currently canarying as part of commit-workflow in CircleCI.

@bob-wilson I need to run a few more canaries to validate the work flow.  I am going to remove you from the reviewer list to avoid spamming you with noise.  Will add you back once the PR is out of draft mode.

Rebased due to recent change in build that changed how cargo test is run.
Currently canarying the flow on CircleCI.

Codecov Report

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

@@           Coverage Diff            @@
##             master   #1420   +/-   ##
========================================
  Coverage          ?      0%
========================================
  Files             ?     409
  Lines             ?   32289
  Branches          ?    5524
========================================
  Hits              ?       0
  Misses            ?   32289
  Partials          ?       0

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 1587530...5366f05. Read the comment docs.

Looks like the plumbing works.  Just need to figure out the 0 coverage next.  When tested locally with grcov's recipe, I saw 84% coverage.
I updated the work flow with scripts/coverage_report.sh but it generated a report with 0 coverage.  @bob-wilson do you see anything obvious that would cause it?  At the meantime, I will try to get the raw lcov.info from circle (if not, I will repro locally)

:umbrella: The latest upstream changes (presumably 38d2a1ed3fde793784b2dba978ee349099cdecfe) made this pull request unmergeable. Please resolve the merge conflicts.

I don't see anything obviously wrong. Maybe this will be fixed by https://github.com/libra/libra/pull/1523?

Somehow the log in Circle's build didn't capture the stderr.
Repro-ed the issue on my dev server with 0 coverage. Don't know yet why the checksum would be different.
test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

   Doc-tests client

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

Generating lcov report at codecov/lcov.info...
22:33:06 [ERROR] Error in computing counters: File checksums do not match:<PHONE_NUMBER> !=<PHONE_NUMBER> in debug/deps/miniz_oxide-a73c908dcf1a65db
22:33:06 [ERROR] Error in computing counters: File checksums do not match: 613053570 !=<PHONE_NUMBER> in debug/deps/prost_derive-1d9dbcd2beb2e861
22:33:06 [ERROR] Error in computing counters: File checksums do not match:<PHONE_NUMBER> != 783098701 in debug/build/failure_derive-5a59685ba3278008/build_script_build-5a59685ba3278008
22:33:06 [ERROR] Error in computing counters: File checksums do not match: 530971125 !=<PHONE_NUMBER> in debug/build/syn-7dc90910d41d0cd9/build_script_build-7dc90910d41d0cd9
22:33:06 [ERROR] Error in computing counters: File checksums do not match:<PHONE_NUMBER> !=<PHONE_NUMBER> in debug/build/bindgen-981e0319cceca5d3/build_script_build-981e0319cceca5d3
22:33:06 [ERROR] Error in computing counters: File checksums do not match:<PHONE_NUMBER> !=<PHONE_NUMBER> in debug/deps/same_file-716c7a8e8485c074
22:33:06 [ERROR] Error in computing counters: File checksums do not match:<PHONE_NUMBER> != 52740952 in debug/deps/proc_macro2-5427030bd3b277e0
22:33:06 [ERROR] Error in computing counters: File checksums do not match:<PHONE_NUMBER> != 603037411 in debug/deps/nibble_vec-cba0390f6cba99a0
...
...
Processing file language/transaction-builder/src/lib.rs
genhtml: WARNING: cannot read language/transaction-builder/src/lib.rs!
Writing directory view page.
Overall coverage rate:
  lines......: 0.0% (0 of 5463 lines)
  functions..: 0.0% (0 of 718 functions)
Done. Please view report at codecov/index.html

:umbrella: The latest upstream changes (presumably 194713b84f5ec9e34b85c1065f1062701fd963bc) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 2a6f58b20d81919823dae324ff78d75a6c003208) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=bob-wilson

:pushpin: Commit 1b2e786 has been approved by bob-wilson

:hourglass: Testing commit 1b2e786a1325f14502d6e8e50a1e19d7c16e6599 with merge ad9379516943f52fa5f033ee7cbe3e2080255fa2...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: bob-wilson
Pushing ad9379516943f52fa5f033ee7cbe3e2080255fa2 to master...


Billing > handle sessions in error

In case of if Stripe is not available during a session do not prevent the user to charge

Session with no billing data should be visible in Session In Error

Should be possible to create the invoice from session In Error

In case of if Stripe is not available during a session do not prevent the user to charge => ok
Session with no billing data should be visible in Session In Error => ok
Should be possible to create the invoice from session In Error => test not possible


WIP: Add noexcept to defaulted move-constructors and move-assignments

Add noexcept specifier to explicitly-defaulted move-constructors and
move-assignment operators.
Ensures that the compiler checks that these member functions are indeed
noexcept.

Abandoned this pull request (#381 Add noexcept to defaulted move-constructors and move-assignments) It appears that the effect of adding noexcept to a move constructor or assignment depends on the compiler (version). https://github.com/InsightSoftwareConsortium/ITK/pull/381#issuecomment-451966612  For example, the following is rejected by both clang 3.8.0 and clang 8.0.0:
struct Foo
{
  Foo(){}
  Foo(const Foo&){}
  Foo(Foo&&){}
};

struct Bar
{
  Foo m_foo;

  Bar() = default;
  Bar(const Bar&) = default;
  Bar(Bar&&) noexcept = default; // error: exception specification...
};

clang 3.8.0 says:

error: exception specification of explicitly defaulted move constructor does not match the calculated one

https://rextester.com/ZMTBD67946
But it is accepted by GCC  5.4.0, GCC 9.1, VS2017, and also by newer versions of clang.
Now I think it would be preferable to just follow the Rule Of Zero (do not declare any of the five special member functions for copy, move, and destruction), whenever possible.


Calicoctl container <CONTAINER> profile (append...) [<PROFILES>...] should require profiles param

This command has the exact same functionality as the calicoctl endpoint <ENDPOINT_ID> profile (append|set|remove) [<PROFILES>...] command, which should also require the profiles flag as mentioned in #557.
# This does not actually add any profiles.
$ calicoctl container workload_A profile append
Profiles  appended

$ calicoctl endpoint d79123c4784511e5bd1a080027f532f6 profile show
+------+
| Name |
+------+
| PROF |
+------+

# This doesn't remove any profiles, but still succeeds.
$ calicoctl container workload_A profile remove
Profiles  removed.

$ calicoctl endpoint d79123c4784511e5bd1a080027f532f6 profile show
+------+
| Name |
+------+
| PROF |
+------+

# This sets the profile to be an empty string (no profiles)
$ calicoctl container workload_A profile set
Profiles  set.

$ calicoctl endpoint d79123c4784511e5bd1a080027f532f6 profile show
Endpoint has no profiles associated with it.

Just update the output text is sufficient I think.

The reason the <PROFILES> param is optional is to allow the set command to use an empty list of profiles to remove all profiles.
The change should be to update the output of the commands to be more clear what is going on.

Fixed by #568


Update vg-date-select

https://github.com/doximity/doximity-client-vue/pull/394/files#r137126708

So it seems that col-day is being added where it should not exist at all: http://d.pr/i/5dd8pA
This is causing a misalignment in mobile -- for now I will hide it via some custom CSS in the Doximity Vue client.


Error if CodeableConcept.text is omitted

The API server throws an exception of CodeableConcept.text is omitted from any data element.  text element should be optional, and concept display based on coding.display value.
The following exception was listed in the app JavaScript console when a Goal was added to sandbox that omitted the text element for a status (or any other element with CodeableConcept type).
As a result, NO goals are displayed for this patient when one of the goals does not have a text value.
http://mccservices.eastus.azurecontainer.io:8081/summary/goals?subject=mcc-pat-pnoelle
There was an unexpected error (type=Internal Server Error, status=500).
Cannot invoke "String.isBlank()" because the return value of "org.hl7.fhir.r4.model.CodeableConcept.getText()" is null

Sean will set up test data. Emma will do review.

use MCC Provider (azurecontainer) on MELD to test lates


Scrolling is broken on main branch

Describe the bug
Scrolling down shows junk lines. Scrolling back up skips lines.
To Reproduce
cargo run --features="static_output" --example static
Expected behavior
The screen always shows the numbers in the correct sequence.
Screenshots
Scrolling downwards:

Scrolling back up:

Desktop:

OS: Debian 11 on WSL 1 on win11
Terminal: IntelliJ and MobaXterm
Shell: none and bash
main branch

Additional context
The cause is a dbg!() in src/core/display/mod.rs:63. I will create a PR to remove it.

Thanks for giving you time. I will be waiting for the PR.


Make ip configureable

Would be maybe a nice to make ip address configureble
https://github.com/togrupe/dlive-midi-tools/blob/7bf31db72d4b89ec9e4deb20f20b159ab2b01195/dliveConstants.py#L23

accepted, see release v1.2.0


FYI significant update to Wikibase Suite coming up

Hey @jmformenti!
Your project looks like a great adaptation and elaboration of the Wikibase Suite project ! I wanted to give you a heads-up that we at Wikimedia Deutschland on the WBS team are nearing release of a major new version of Wikibase Suite. It will go out shortly after MediaWiki 1.42 is released later this month.
So, if you or others are depending on the packaging here, you might want to keep an eye on https://github.com/wmde/wikibase-release-pipeline and the updates going in at this point.
In addition to a lot of clean-up and better docs of the configuration, we've added Traefik as a reverse proxy service and agent for ACME SSL certificate generation in our Docker Compose configuration, to make what we're providing easier to move into production.
If it feels relevant give it a look! And feel free to ping us up here if you have any questions or concerns.
Best, Loren / Wikibase Suite Team

Hi @lorenjohnson
Thanks for the heads-up! This is indeed a very important update. In fact, with the new features of Traefik and ACME SSL, a large part of this project might no longer be necessary.
I will definitely take a look at it, and thanks for your truly appreciable work on Wikibase!


🐛 [firebase_messaging] getNotificationSettings() doesn't return correct settings in iOS PWA after user changed the permission from device Settings UI

Bug report
Describe the bug
In iOS PWA, getNotificationSettings() doesn't return the correct current notification settings after the user changed the notification permission manually from the device Settings UI. But in Android PWA it returns the settings correctly.
Steps to reproduce
Steps to reproduce the behavior:

Launch the PWA from Homescreen
On app startup, when the notification permission popup is shown after calling requestPermission(), tap Deny
Call getNotificationSettings() to get current settings. This should return the settings with AuthorizationStatus.denied value
Go to Settings -> Notifications -> yourAppName
Turn On the Allow Notifications toggle
Return to the app
Call getNotificationSettings() again (some button). This still returns the settings with AuthorizationStatus.denied value

Expected behavior
It should return the settings with AuthorizationStatus.authorized value.
Sample project
reproducible_example.zip
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.10.4, on Microsoft Windows [Version 10.0.22621.1992], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[√] Chrome - develop for the web
[!] Visual Studio - develop for Windows (Visual Studio Build Tools 2017 15.9.9)
    X Visual Studio 2019 or later is required.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2022.1)
[!] Android Studio (version 4.1)
    X Unable to determine bundled Java version.
[√] VS Code (version 1.80.1)
[√] Connected device (3 available)
[√] Network resources

! Doctor found issues in 2 categories.

Hi @dioseltorre, can you share a minimal reproducible code sample in a repo that we can clone so we can verify this? I tried using the plugin example but safari can't get the permission.
Also, what version of firebase_messaging are you using?

Hi @danagbemava-nc, I've attached the reproducible example please check on the Sample project section.

Also, what version of firebase_messaging are you using?

I'm using the versions below:
  firebase_core: ^2.14.0
  firebase_messaging: ^14.6.4

Hi @dioseltorre, just for reference, what android device did you test this on? On my pixel 7 I get the same behaviour as the iOS device.

@danagbemava-nc Below are the Android device information and also the sample video of the behavior.
Device: Samsung Galaxy A31
OS: Android 12
Chrome version: 114.0.5735.196
https://github.com/firebase/flutterfire/assets/14935048/73cb5029-34ee-46c6-be4d-3ddf99514687

Thanks for the info. It seems like it might work on some devices but not work on others. This might be more a flutter issue than an actual issue with flutterfire, but for now I'll label this for further insight from the team.

iOS
Pixel 7


train with C3D model

Hi,
I am currently trying to train from scratch C3D model with my own dataset. Can you provide some hints on that? The tutorial is only about R(2+1)D with HMDB dataset. Thanks for your time!

Is it just the matter of changing the model name and using example of training from scratch? you may need to tune the hyper-parameters for your dataset though.


[Sample]  Need to use Deployment name as Labelling component for kubernetes pod

Problem Statement
I want to use  Deployment name as Labelling component for kubernetes pod .
Below is the requirment we are trying to mutate the policy
can we change the value of the label to reference the deployment resource? for example, the daemonset name datadog instead of the pod instance id datadog-ias31f
Solution Description
I need a sample policy where we can access the deployment name as Label name for a pod
Example "Good" Resource
No response
Example "Bad" Resource
No response
Other Comments
No response
Slack discussion
No response
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have verified the policy does not exist in the samples library.

Addressed on Slack
https://kubernetes.slack.com/archives/CLGR9BJU9/p1670393323427489


Fork the theme

I think it'd be better to fork the theme, just as other do...

Not :100: % whether it is relevant but this is done in 6ccd4c8

Not :100: % whether it is relevant but this is done in 6ccd4c8


The index out parameter is incorrect for C++/CX

The signature should be:
public : Platform::Boolean IndexOf(Platform::Object^ value, unsigned int* index);

...instead of:
public : Platform::Boolean IndexOf(Platform::Object value, unsigned int index);

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

ID: 7e4a65cc-0478-b715-919c-d806c9bed9c6
Version Independent ID: 6797d5d3-acb5-2ace-fc19-74e436327603
Content: IBindableVector.IndexOf(Object, UInt32) Method (Windows.UI.Xaml.Interop) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.ui.xaml.interop.ibindablevector.yml&version=GBlive&_a=contents
Product: uwp
Technology: winui
Git Login: jwmsft
Microsoft Alias: jimwalk

Thanks, @marmphco, and apologies for the very long delay in responding to this issue. It looks like the signature is correct on the live site now, so I'll go ahead and close the issue.
-Steve


Guarantees we have 3 cards to display

What's this PR do?

Our super users have signed up for all our staff picks, this provides a fallback
Makes the headers 3/4 width

How should this be reviewed?
Signup for all staff picks, do you see any campaigns on the campaign signup slide?
Any background context you want to provide?
No
Relevant tickets
Fixes #i dont think the issue exists yet?

Design is luke approved

This is one of the issues it fixes https://github.com/DoSomething/TeamRocket/issues/4


Update README.md

GitSecure Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

CA-7
Security Assessment and Authorization
Continuous Monitoring

SA-12
System and Services Acquisition
Supply Chain Protection

SI-2
System and Information Integrity
Flaw Remediation

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

GitSecure Bill of Material

Control ID
Section
Description

CM-8
Configuration Management
Information System Component Inventory

 Download Bill of Material Report: [JSON Format]

Docker CIS Community Edition 1.13

Control ID
Section
Description

CM-6
Configuration Management
Configuration Settings

CA-2
Security Assessment and Authorization
Security Assessments

GitSecure Dockerfile Linter
Checks powered by Hadolint
Haolint is a smarter Dockerfile linter that helps you build best practice Docker images.

Control ID
Section
Description

SA-11 (1)
System and Services Acquisition
Developer Security Testing and Evaluation - Static Code Analysis

✅ GitSecure Open Source License Assessment: Passed
FedRAMP Controls covered:

Control ID
Section
Description

CM-7(5)
Configuration Management
Least Functionality - Authorized Software / Whitelisting

CM-10
Configuration Management
Software Usage Restrictions

CM-11
Configuration Management
User-Installed Software

CA-6
Security Assessment and Authorization
Security Authorization

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

Download Open Source Steering Committee (OSSC) Report: [JSON Format]  [HTML Format]

GitSecure Bill of Material

Control ID
Section
Description

CM-8
Configuration Management
Information System Component Inventory

 Download Bill of Material Report: [JSON Format]

GitSecure Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

CA-7
Security Assessment and Authorization
Continuous Monitoring

SA-12
System and Services Acquisition
Supply Chain Protection

SI-2
System and Information Integrity
Flaw Remediation

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

   For Dockerfile: /Dockerfile  Stage: shri4u/myapp-base:0.1

:white_check_mark: OS Packages Safe
:x: Pip Packages Safe
Vulnerability Analysis
Vulnerable OS Packages
No vulnerable os packages found
Vulnerable Python Packages
Total of 1 vulnerable pip packages found
Package  Django   needs to  satisfy this version requirement  >= 1.8.15
Detailed Package Analysis
Contains vulnerability, license and pedigree information for each package

  OS Packages [Expand for more information]

  Python Packages [Expand for more information]

 Package Name: Django | Current Version: 1.2  (VULNERABLE)

Python Vulnerabilities:
Recommended update : >= 1.8.15

1. Affected Versions  : >=1.2,<1.2.5
 Description
Directory traversal vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 on Windows might allow remote attackers to read or execute files via a / (slash) character in a key in a session cookie, related to session replays.

2. Affected Versions  : <1.2.2
 Description
Cross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie.

3. Affected Versions  : <1.2.7
 Description
django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.

4. Affected Versions  : <1.2.7
 Description
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.

5. Affected Versions  : <1.2.7
 Description
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.

6. Affected Versions  : <1.2.7
 Description
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.

7. Affected Versions  : <1.3.2
 Description
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.

8. Affected Versions  : <1.3.2
 Description
The django.forms.ImageField class in the form system in Django before 1.3.2 and 1.4.x before 1.4.1 completely decompresses image data during image validation, which allows remote attackers to cause a denial of service (memory consumption) by uploading an image file.

9. Affected Versions  : <1.3.2
 Description
The get_image_dimensions function in the image-handling functionality in Django before 1.3.2 and 1.4.x before 1.4.1 uses a constant chunk size in all attempts to determine dimensions, which allows remote attackers to cause a denial of service (process or thread consumption) via a large TIFF image.

10. Affected Versions  : <1.3.4
 Description
The django.http.HttpRequest.get_host function in Django 1.3.x before 1.3.4 and 1.4.x before 1.4.2 allows remote attackers to generate and display arbitrary URLs via crafted username and password Host header values.

11. Affected Versions  : <1.4.18
 Description
The django.util.http.is_safe_url function in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 does not properly handle leading whitespaces, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL, related to redirect URLs, as demonstrated by a "\njavascript:" URL.

12. Affected Versions  : <1.4.18
 Description
The django.views.static.serve view in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 reads files an entire line at a time, which allows remote attackers to cause a denial of service (memory consumption) via a long line in a file.

13. Affected Versions  : <1.4.18
 Description
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.

14. Affected Versions  : <1.4.20
 Description
The utils.http.is_safe_url function in Django before 1.4.20, 1.5.x, 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x before 1.8c1 does not properly validate URLs, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a control character in a URL, as demonstrated by a \x08javascript: URL.

15. Affected Versions  : <1.7.11
 Description
The get_format function in utils/formats.py in Django before 1.7.x before 1.7.11, 1.8.x before 1.8.7, and 1.9.x before 1.9rc2 might allow remote attackers to obtain sensitive application secrets via a settings key in place of a date/time format setting, as demonstrated by SECRET_KEY.

16. Affected Versions  : <1.7.6
 Description
Cross-site scripting (XSS) vulnerability in the contents function in admin/helpers.py in Django before 1.7.6 and 1.8 before 1.8b2 allows remote attackers to inject arbitrary web script or HTML via a model attribute in ModelAdmin.readonly_fields, as demonstrated by a @property.

17. Affected Versions  : <1.8.10
 Description
The password hasher in contrib/auth/hashers.py in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to enumerate users via a timing attack involving login requests.

18. Affected Versions  : <1.8.10
 Description
The utils.http.is_safe_url function in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks or possibly conduct cross-site scripting (XSS) attacks via a URL containing basic authentication, as demonstrated by<EMAIL_ADDRESS>

19. Affected Versions  : <1.8.15
 Description
The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.

20. Affected Versions  : >=1.2,<1.2.4
 Description
The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter.

21. Affected Versions  : >=1.2,<1.2.4
 Description
The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.

22. Affected Versions  : >=1.2,<1.2.5
 Description
Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a "combination of browser plugins and redirects," a related issue to CVE-2011-0447.

Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

GitSecure Auto-remediation
  PR Created at:  https://github.com/cmadam/myapp/pull/18

GitSecure Dockerfile Linter
Checks powered by Hadolint
Haolint is a smarter Dockerfile linter that helps you build best practice Docker images.

Control ID
Section
Description

SA-11 (1)
System and Services Acquisition
Developer Security Testing and Evaluation - Static Code Analysis

Dockefile : //Dockerfile

Line #
ID
Description

2
DL3008
Pin versions in apt get install. Instead of apt-get install <package> use apt-get install <package>=<version>

2
DL3009
Delete the apt-get lists after installing something

2
DL3015
Avoid additional packages by specifying --no-install-recommends

❌ GitSecure Open Source License Assessment: Needs Review
FedRAMP Controls covered:

Control ID
Section
Description

CM-7(5)
Configuration Management
Least Functionality - Authorized Software / Whitelisting

CM-10
Configuration Management
Software Usage Restrictions

CM-11
Configuration Management
User-Installed Software

CA-6
Security Assessment and Authorization
Security Authorization

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

❌ Python PackagesSelf-Certifiable Packages
MarkupSafe version 1.1.1zipp version 0.6.0Flask_Cors version 3.0.8itsdangerous version 1.1.0pytz version 2019.3visitor version 0.1.3Mako version 1.0.7six version 1.13.0Flask_API version 1.1WTForms version 2.2.1wheel version 0.33.6Flask_Bootstrap version <IP_ADDRESS>Flask_WTF version 0.14.2more_itertools version 8.0.2importlib_metadata version 1.2.0Werkzeug version 0.16.0pyrsistent version 0.15.6aniso8601 version 8.0.0Flask version 1.1.1Flask_HTTPAuth version 3.3.0flask_nav version 0.6attrs version 19.3.0Click version 7.0Packages that Need Review
pip version 19.3.1setuptools version 41.6.0pathvalidate version 0.29.0Django version 1.2flask_restplus version 0.13.0Jinja2 version 2.10.3MarkupSafe version 1.0dominate version 2.4.0jsonschema version 3.2.0
Download Open Source Steering Committee (OSSC) Report: [JSON Format]  [HTML Format]

Docker CIS Community Edition 1.13

Control ID
Section
Description

CM-6
Configuration Management
Configuration Settings

CA-2
Security Assessment and Authorization
Security Assessments

Dockerfile: redis.yaml

ID
Rule
Compliant?

5.25
Ensure the container is restricted from acquiring additional privileges
?

5.26
Ensure container health is checked at runtime
?

5.31
Ensure the Docker socket is not mounted inside any containers
:heavy_check_mark:

5.7
Ensure privileged ports are not mapped within containers
:heavy_check_mark:

5.10
Ensure memory usage for container is limited
:x:

5.22
Ensure docker exec commands are not used with privileged option
?

5.29
Ensure Docker's default bridge docker0 is not used
?

5.14
Ensure 'on-failure' container restart policy is set to '5'
?

5.19
Ensure mount propagation mode is not set to shared
?

5.21
Ensure the default seccomp profile is not Disabled
?

5.30
Ensure the host's user namespaces is not shared
?

5.11
Ensure CPU priority is set appropriately on the container
:heavy_check_mark:

5.20
Ensure the host's UTS namespace is not shared
?

5.1
Ensure AppArmor Profile is Enabled
?

5.6
Ensure ssh is not run within containers
?

5.28
Ensure PIDs cgroup limit is used
?

5.9
Ensure the host's network namespace is not shared
:heavy_check_mark:

5.17
Ensure host devices are not directly exposed to containers
?

5.18
Ensure the default ulimit is overwritten at runtime, only if needed
?

5.24
Ensure cgroup usage is confirmed
?

5.27
Ensure docker commands always get the latest version of the image
?

5.8
Ensure only needed ports are open on the container
?

5.12
Ensure the container's root filesystem is mounted as read only
?

5.16
Ensure the host's IPC namespace is not shared
:heavy_check_mark:

5.23
Ensure docker exec commands are not used with user option
?

5.2
Ensure SELinux security options are set, if applicable
?

5.4
Ensure privileged containers are not used
:heavy_check_mark:

5.13
Ensure incoming container traffic is binded to a specific host interface
?

5.15
Ensure the host's process namespace is not shared
:heavy_check_mark:

5.3
Ensure Linux Kernel Capabilities are restricted within containers
:heavy_check_mark:

5.5
Ensure sensitive host system directories are not mounted on containers
:heavy_check_mark:

GitSecure Deployment Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

See package details below.
Report for: redis.yaml
Docker image: redis:3.0
This vulnerable image is not exposed by any services
Base OS image: debian 8.8

Package
Version
CVE
Severity
Fix

libgcrypt20
1.6.3-2+deb8u3
[CVE-2018-0495]
Unknown
1.6.3-2+deb8u5

libgcrypt20
1.6.3-2+deb8u3
[CVE-2019-13627]
Unknown
1.6.3-2+deb8u6

libgcrypt20
1.6.3-2+deb8u3
[CVE-2017-7526]
Negligible
1.6.3-2+deb8u4

bash
4.3-11+deb8u1
[CVE-2019-9924]
Low
4.3-11+deb8u2

bash
4.3-11+deb8u1
[CVE-2016-9401]
Unknown
4.3-11+deb8u2

gnupg
1.4.18-7+deb8u3
[CVE-2018-12020]
Negligible
1.4.18-7+deb8u5

gnupg
1.4.18-7+deb8u3
[CVE-2017-7526]
Negligible
1.4.18-7+deb8u4

e2fsprogs
1.42.12-2+b1
[CVE-2019-5094]
Unknown
1.42.12-2+deb8u1

tar
1.27.1-2+deb8u1
[CVE-2018-20482]
Unknown
1.27.1-2+deb8u2

procps
2:3.3.9-9
[CVE-2018-1122]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1126]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1124]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1123]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1125]
Unknown
2:3.3.9-9+deb8u1

sensible-utils
0.0.9
[CVE-2017-17512]
Unknown
0.0.9+deb8u1

systemd
215-17+deb8u7
[CVE-2018-16864]
Unknown
215-17+deb8u9

systemd
215-17+deb8u7
[CVE-2018-15686]
Unknown
215-17+deb8u8

systemd
215-17+deb8u7
[CVE-2018-16865]
Unknown
215-17+deb8u9

systemd
215-17+deb8u7
[CVE-2018-1049]
Unknown
215-17+deb8u8

systemd
215-17+deb8u7
[CVE-2017-18078]
Negligible
215-17+deb8u12

systemd
215-17+deb8u7
[CVE-2018-15688]
Negligible
215-17+deb8u8

systemd
215-17+deb8u7
[CVE-2019-3815]
Negligible
215-17+deb8u11

systemd
215-17+deb8u7
[CVE-2019-3842]
Unknown
215-17+deb8u12

systemd
215-17+deb8u7
[CVE-2019-6454]
Unknown
215-17+deb8u10

apt
<IP_ADDRESS>.4
[CVE-2019-3462]
Unknown
<IP_ADDRESS>.5


Function signature helper

Hello! I just switched from coc.nvim and the experience has been pretty straightforward. Thanks for this project!
I was wondering if there's a way to achieve function signature helper on insert mode. Something similar to this but with the dependencies that lsp-zero already has.

I don't think so. The closest thing would be to call Neovim's  vim.lsp.buf.signature_help() function with a keymap in insert mode.
Something like this.
vim.keymap.set('i', '<c-k>', '<cmd>lua vim.lsp.buf.signature_help()<cr>')


VT not supported (svm enabled - hyper-v disabled)

Hey, im trying to install haxm for android studio emulator but i get vt not supported error. It was working well before but yesterday i tried to install mac os to my virtual machine from some different sources so im not sure what did i changed. This morning i tried to use android studio and then i get x86 error. i recovered my pc and deleted everything but this problem didnt fixed i cannot install haxm now. could you please help me?

AMD cpu is not supported.

are you sure? because i was using it until yesterday?

yes.

Why isn't AMD CPU supported? It uses the same instruction set as Intel CPUs that are targeted. This is a core piece of software in current Android development SDLC. Are you saying that in order to develop Android apps you need to use Intel CPU and everyone else is just out of luck?

@dantheman213 ,so far HAXM is designed and supported for CPU only.

HAXM only supports Intel CPU and leverages Intel VT-x. This project is mainly initiated by Intel. Whether it supports other CPUs depends on the development status of other manufacturers. Any diverse contributions from community or other manufacturers are also welcomed.

So what you're saying is that the Android SDK team should NOT be using Intel's technology because Intel refuses to support all common and trivially configured CPUs or computers in which it could run under?

Thanks for your comments. Android SDK recommends users to use HAXM when they are using Intel CPU on Windows. HAXM project team has rather limited resources to cover all CPUs other than Intel's. We cannot guarantee the availability for all other CPUs which use Intel technology. Any software has its usability scope, and HAXM has already clearly declared its supporting cases on the homepage. The contributions from community for the mentioned supports will always be welcomed. Thanks.

I understand this not your decision to unilaterally make. However, I'd like to clear up one thing:

Android SDK recommends users to use HAXM when they are using Intel CPU on Windows.

This is not the case. There is no viable option right now for AMD Ryzen users to run, debug, or test Android apps because AVD requires HAXM to be installed to run x86 Android Emulator. And even though I am using high-end motherboards that support VT-x and I can run software like Hyper-V, Docker, and VirtualBox, I cannot run HAXM on any AMD Ryzen machine I've tried.
Here is the only alternative that I have found:
https://stackoverflow.com/questions/27471219/can-i-run-an-emulator-without-haxm-in-android-studio
So I followed the instructions and....

OK, fine, but can I develop on it ? What kind of performance can I expect? Well, it's been about 30 mins since I booted up the ARM emulator on a 16 thread, 4GHz CPU and it just finished booting up now. I'm getting about 0.1 fps while trying to navigate. It's basically unusable.
Conclusion
The decision for Android team to use HAXM and the subsequent decision for Intel to not support AMD's popular and powerful Ryzen CPUs that use the same instruction set (x86)  is a grave combo decision that has huge impacts to the developer community. Let us hope that AMD doesn't produce some software at some point that locks out Intel users on an important development platform.
I hope in time that Intel and/or the HAXM team will reconsider this decision.


Add slides on <random>

So far we do not discuss random number generation. We use it a lot in the exercises though. We should add a few slides explaining engines and distribution. And to not use rand() anymore.

Some inspiration if you want : https://github.com/chavid/ModernScientificCpp/blob/main/5-ClassRoom/3-FloatingPointComputing/3-random-numbers.ipynb . I let you the fight with the conversion to latex ;)

This is awesome!


Search: Filters behaviour

I was aiming to fix #9060 but then realised that the behaviour we currently have for filters/no results, where we hide unavailable filters, isn't the most intuitive and doesn't work for all fields. Date, for example, is an open input and therefore is always a valid option. I thought it'd be good to document this outside of Slack and have an easier time tracking those decisions.
For some context, what gets displayed under the filters stays the same as from the old search:
No query, no selected filters:
Displays all the filters we have and the whole catalogue is listed.
No query, selected filters
Always has results to display, as only filters with results are offered to users.
Query, no selected filters:
Results are displayed, if there are none we display a no results message instead

We couldn’t find anything that matched [query]. Please try again.

Query, selected filters:
Results are displayed, if there are none we display a no results message instead

We couldn’t find anything that matched [query] with the filters you have selected. Please try again.

The difference lies in Filters and what happens to them depending on the scenarios above. For reference, the current search behaviour is not ideal either, but we could find inspiration in what worked/didn't.
Current behaviour in /works:
Three of the filters are always displayed (Format, Date, Location) and the others are contained in the More filters modal. The main three seem to be ones that always have results (I couldn't find a combination that didn't, though it might exist).
Filter options are being offered only if they have results. For example, if the "Standing order" format has been selected, only the Locations that have "standing order" format items will be displayed.
If a dropdown has no option, it is still displayed, and clicking on it displays an empty white box, which is not great UX and is something we flagged and would like to fix in the new search. In the More filters modal, if a category has no options to offer, the title displays but its section is left blank.
Search behaviour in /search/works
Currently
Filter options are being offered only if they have results. For example, if the "Standing order" format has been selected, only the Locations that have "standing order" format items will be displayed. We only display the dropdowns with options available, the others are removed.
As mentioned, this doesn't work for Date, as it always had "valid" options. Colors, in /search/images has the same problem.
This could - I think - cause issues from an a11y standpoint (change of context if all filters disappear, for example). But it also makes it unclear to a user which filters they could be using should they search for something different.
Suggestions

We could disable the dropdowns with no options to offer, so they are still visible but unusable.
In the More filters modal they imitate the current behaviour of displaying the title only - but would love another suggestion for that one.
Do we want to copy the current search in only displaying Format, Date and Location and have everything else in the More Filters modal?

@DominiqueMarshall Shall I assign this to you for now (and move it back to the backlog or Next), as we discussed you wanted to do a bit of research in

Is this the behaviour we want moving forward?
If so, how could we style the disabled buttons differently?

I'm staying super available to discuss this, it's a good puzzle.

Happy to close this one too for now and there will eventually be a review after we get to gather more feedback.


[SPARK-21117][SQL] Built-in SQL Function Support - WIDTH_BUCKET

What changes were proposed in this pull request?
Add build-in SQL function - WIDTH_BUCKET
Ref: https://docs.oracle.com/cd/B28359_01/olap.111/b28126/dml_functions_2137.htm#OLADM717
How was this patch tested?
unit tests and manual tests.
manual tests(compare spark-sql results with oracle):
select width_bucket(5.35, 0.024, 10.06, 5) from dual; -- 3 --

select width_bucket(3.14, 0, 4, 3) from dual;         -- 3 --
select width_bucket(2, 0, 4, 3) from dual;            -- 2 --
select width_bucket(-1, 0, 3.2, 4) from dual;         -- 0 --

select width_bucket(3.14, 4, 0, 3) from dual;         -- 1 --
select width_bucket(2, 4, 0, 3) from dual;            -- 2 --
select width_bucket(-1, 3.2, 0, 4) from dual;         -- 5 --

Test build #78160 has started for PR 18323 at commit 20fe567.

Test build #78161 has started for PR 18323 at commit 3a0eaf7.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78161/
Test FAILed.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78160/
Test FAILed.

Jenkins, retest this please

Test build #78181 has started for PR 18323 at commit 3a0eaf7.

Test build #78181 has finished for PR 18323 at commit 3a0eaf7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78181/
Test PASSed.

Test build #78196 has started for PR 18323 at commit 3a5d46e.

Test build #78196 has finished for PR 18323 at commit 3a5d46e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78196/
Test PASSed.

Merged build finished. Test PASSed.

cc @wzhfy

Test build #78245 has started for PR 18323 at commit 7407541.

Test build #78245 has finished for PR 18323 at commit 7407541.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78245/
Test PASSed.

Test build #78515 has started for PR 18323 at commit 5c3ecee.

Test build #78515 has finished for PR 18323 at commit 5c3ecee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78515/
Test PASSed.

Merged build finished. Test PASSed.

Test build #78611 has started for PR 18323 at commit 9e2cabb.

Test build #78611 has finished for PR 18323 at commit 9e2cabb.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78611/
Test FAILed.

retest this please.

Test build #78627 has started for PR 18323 at commit 9e2cabb.

Test build #78627 has finished for PR 18323 at commit 9e2cabb.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78627/
Test FAILed.

This error appears in a few builds. Let's wait for the fix. Currently it looks good to me.
ping @gatorsmile

retest this please

Test build #78769 has started for PR 18323 at commit 9e2cabb.

Test build #78769 has finished for PR 18323 at commit 9e2cabb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78769/
Test PASSed.

Test build #79641 has started for PR 18323 at commit 507fcfb.

Test build #79641 has finished for PR 18323 at commit 507fcfb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79641/
Test PASSed.

Test build #79794 has started for PR 18323 at commit 099db6d.

Test build #79795 has started for PR 18323 at commit 01af62b.

Test build #79795 has finished for PR 18323 at commit 01af62b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79795/
Test FAILed.

Merged build finished. Test FAILed.

Test build #79794 has finished for PR 18323 at commit 099db6d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79794/
Test FAILed.

Merged build finished. Test FAILed.

Test build #79799 has started for PR 18323 at commit 0355284.

Test build #79799 has finished for PR 18323 at commit 0355284.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79799/
Test PASSed.

Test build #80015 has started for PR 18323 at commit 0940a49.

Test build #80015 has finished for PR 18323 at commit 0940a49.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80015/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #80017 has started for PR 18323 at commit 0940a49.

Test build #80017 has finished for PR 18323 at commit 0940a49.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80017/
Test PASSed.

Merged build finished. Test PASSed.

Test build #80112 has started for PR 18323 at commit e0478f5.

Test build #80112 has finished for PR 18323 at commit e0478f5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80112/
Test PASSed.

Test build #81843 has started for PR 18323 at commit 2e2b2ca.

Test build #81843 has finished for PR 18323 at commit 2e2b2ca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81843/
Test PASSed.

Any news? What's blocking this PR to move on except the conflict to resolve since it's been 1 year?
This addition would be really great.

Test build #94376 has started for PR 18323 at commit 2e2b2ca.

@wangyum Can we rebase it? We should add this support for compatibility.

Test build #122180 has started for PR 18323 at commit 2e2b2ca.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26852/
Test PASSed.

Test build #122180 has finished for PR 18323 at commit 2e2b2ca.

This patch fails Scala style tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122180/
Test FAILed.

Test build #122223 has started for PR 18323 at commit 31ee943.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26895/
Test PASSed.

Test build #122223 has finished for PR 18323 at commit 31ee943.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122223/
Test FAILed.

You need to run SPARK_GENERATE_GOLDEN_FILES=1 build/sbt "sql/test-only *ExpressionsSchemaSuite" to update the golden file.

Test build #122229 has started for PR 18323 at commit 44ef7df.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26901/
Test PASSed.

Test build #122229 has finished for PR 18323 at commit 44ef7df.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122229/
Test PASSed.

Could you solve the conflict?

@wangyum If you don't time to update this, I could take this over. Thought?

@maropu Please take it over. Thank you.

ok


Fails with masked depths - affects numpy 1.11 only

If the requested depths are in a masked array, even if all depths are valid, it fails if it is required to interpolate in z. This is due to a failure comparing the requested depths and the depths from the cropped depth that would be used to interpolate.
This affects only numpy 1.11.

Fixed by commit af5b8ad5ae46212e2982b367eca246ad81cdafea


Convertion of DER Encoded Certificates to PEM Encoded Certificates

Problem Statement
According to SPIFFE implementation, Workload API returns DER encoded intermediate CA's and leaf certificate also known as end entity certificate. And this certificates formed via concatenating certificates starting with leaf certificate.
Parsing these certificates and converting them is quite straightforward in Go with the help of standard crypto module.

According to SPIFFE documentation, it is possible to have multiple intermediate CA before a leaf certificate in the certificate chain.
But I was not able to find a library in Node.js which converts DER encoding to PEM encoding correctly, when this is the case.
Following libraries are investigated:

Node.js Standard Crypto Module
Problem with standard Crypto module in Node.js is, it does not parse all the buffer provided, only parses the leaf certificate and first intermediate CA. If there is more than one intermediate CA, it is lost.

Node-Forge
Has the same problem with Node.js standard crypto module, and in addition to that, node-forge does not support ECC based x509 certificates.

Why is this critical?
When Node.js applications want to make use of SPIFFE certificates, they need the certificates in PEM format because standard TLS module in Node.js supports only PEM encoded certificates. (createSecureContext function of standard module). Therefore the applications will not be able to use it
In short the problem is, SPIFFE allows having multiple Intermediate CA and leaf certificate concatenated with each other with DER encoding. But when existance of multple intermediate CA's, there is no library doing this properly. (Please
Solution Proposal
We can have a function in the client which converts DER to PEM format without parsing all certificate. Since DER encoding is a type length encoding, I was able to implement the following.
function parseDER(buffer) {
    let currentIndex = 0;
    let pemCerts = [];

    while (currentIndex < buffer.length) {
        let beginOfSequence = currentIndex;
        // Get the first byte for tag
        const tag = buffer[currentIndex++];
        // Get the second byte for length value representing bytes
        let length = buffer[currentIndex++];
        if (length === 0x80) {
            // Indefinite length encoding is not supported
            throw new Error('Indefinite length encoding not supported');
        }
        if (length & 0x80) {
            const lengthBytes = length & 0x7F;
            length = 0;
            for (let i = 0; i < lengthBytes; i++) {
                length = (length << 8) | buffer[currentIndex++];
            }
        }
        // Extract the value based on the tag and length
        pemCerts.push(`-----BEGIN CERTIFICATE-----\n${Buffer.from(buffer.slice(beginOfSequence, currentIndex + length)).toString("base64")}\n-----END CERTIFICATE-----`);

        // Move the current index to the next tag
        currentIndex += length;
    }
    return pemCerts.join("\n")
}

I am open to any other solutions, or creating a PR for this. But first I wanted to share the issue with you to check if you have experienced similar problem.

Hey, thank you for this! I've added a parseCertificateBundle helper method based on your code above and using @peculiar/x509 to parse the certificates. I've released it as v0.4.0.
I haven't had a chance to test yet, but in theory you should be able to do this:
import {parseCertificateBundle} from 'spiffe'

const data = ... // any Uint8Array
const bundle = parseCertificateBundle(data) // x509.X509Certificates, which is also an array

const pemChain = bundle.toString('pem-chain') // the PEM string

If you get a chance to try it, let me know if it works. If not, or if you have any other ideas that would make it easier to use, let me know too (and PRs are always welcome!).


Question about eu.verdelhan.ta4j.mocks and Maven

Hi there,
i have the following problem in my Netbeans project:
For a JUnit test i'd like to use eu.verdelhan.ta4j.mocks. But unfortunately eu.verdelhan.ta4j.mocks is not included in the official Maven repository "eu.verdelhan.ta4j" release 0.8 with scope "Testing".
Is it possible to add "mocks" to the repository for the testing scope?
Any other ideas?
Regards,
Elmoe

Ta4j is not intended to be a test dependency. Which one of the mock objects would you like to use? I may add it in the regular lib as basic objects.

I'd need "eu.verdelhan.ta4j.mocks.MockTimeSeries".
I just need "mocks" for the discussed conversion class https://github.com/mdeverdelhan/ta4j/issues/61.
When i pull "ta4j" from github, everything is fine and i find "mocks" in the testing package. But going this way i'd need to include the github sources for MockTimeSeries in the Maven project manually in the POM, which is also not very handsome.
Is it possible to configure Maven so that "mocks" is only included for scope "testing"?

Hi!
if you have checkout ta4j, run the maven commande mvn jar:test-jar install.
Then add to your pom the following dependency:
<dependency>
    <groupId>eu.verdelhan</groupId>
    <artifactId>ta4j</artifactId>
    <version>0.8-SNAPSHOT</version>
    <type>test-jar</type>
    <scope>test</scope>
</dependency>

Now you have access to the mock package in your project in local.

Thank you very much!


GLES 2  GL_OUT_OF_MEMORY error generated

Godot version:
3.1 399910d
OS/device including version:
Ubuntu 18.04 Nvidia 396.54
Issue description:
It was hard to get this error, because it seems to not be reproducible but I catch him when I changing scenes in FPS Demo Project. I saw this but before when I changing selected nodes in Scene Dock
 ERROR: _gl_debug_print: GL ERROR: Source: OpenGL Type: Error ID: 1285 Severity: High
Message: GL_OUT_OF_MEMORY error generated. Failed to map memory for buffer.
   At: drivers/gles2/rasterizer_gles2.cpp:111.

Steps to reproduce:
https://streamable.com/mny1t
https://streamable.com/z9sr7

Can't reproduce this anymore.


Find a secure workaround for jupyter auth key requirement

At present, when connecting to the jupyter notebook, user need to enter a shared authentication key. This authentication key changes each time the jupyter server is restarted. This is inconvenient for users and admins.
Find an alternative way to secure the jupyter server, and authenticate the users.

The jupyterlab config in local.yml has had some further attention but remains commented out.


feat: Allow specifying extension of declaration files

Fixes #267
This allows you to replace the .d.ts extension with one of your liking (e.g. .d.cts, .d.mts) by passing in the dtsExtension option.
If not set, it does nothing. If set, it changes where declarations and declaration maps get written, updates the "file" field in the declaration map, and updates the sourceMappingURL field in the declaration.
I found it was incompatible with rollupTypes: true, so it will not run if it finds this is enabled. Making that compatible would require a more extensive refactor.
This solves needing to use an afterBuild function to rename file extensions.

I'm closing this because I found a workaround using beforeWriteFile:
        beforeWriteFile: (filePath, content) => {
          filePath = filePath.replace('.d.ts', '.d.cts')
          return { filePath, content }
        },

I don't think it affects declaration maps, but it's a reasonable solution for my use case.


chaincode metadata changes added

What this PR does / why we need it:
A new feature to display the chaincode metadata information in Blockchain Explorer. Explorer will look into the channel and identifies the chaincodes installed on it and enables the feature to view the metadata.
Users can see the how the contract is structured and its associated metadata information.
Which issue(s) this PR fixes:

Fixes #352
Special notes for your reviewer:
Does this PR introduce a user-facing change?

None

Additional documentation, usage docs, etc.:

LGTM, please resolve the conflicts.


F# examples

Provide F# code examples

Thank you for your suggestion.
To test if the current code works well for F#, too some initial samples would be great.
Perhaps we need to provide some additional F# layer to make the library convenient to use from F#.
If you are interested in creating some exemplary samples feel free to create a PR.
I think optimization for F# won't be on the roadmap for the first release, except someone from the community steps up. But in the long run I think F# should be equally important to us as C#

If you are interested in creating some exemplary samples feel free to create a PR

I have just started learning F#, but I have already fallen in love with the ML family.
Yesterday I came across this question, and only now it occurred to me that in addition to haskell from functional languages for programming on GTK, F# will be available soon, and it seems to me that it is better suited for GUI since it defines OOP and FP, unlike purely functional Haskell.

I just tried to make a Window example in F#, and it worked. Now I'm super excited.
open Gtk;

[<EntryPoint>]
let main argv =
    Functions.Init();
    let mainWindow = new Window("Sas")
    mainWindow.ShowAll()
    Functions.Main();
    0

So far, I'm not sure how to bind the signal, instead of onDestroy there is add_OnDestroy, although I think it works as well.

I'm not sure how signals will work with F#. I would need to dig into it myself.
In general as C# and F# use the same IL you can currently either connect to the event (see here) or the property descriptor (see here) with the corresponding F# syntax.

Events have the nice property of being able to be used in Observable pipelines.


implement interaction request signing verification

i had previously written a small lib to do this: bsdlp/discord-interactions-go, and this is basically copypasta from there.
https://discord.com/developers/docs/interactions/slash-commands#security-and-authorization

Hi! This library hasn't traditionally featured any type of HTTP server functionality, but given the new interactions feature I think that this might be a good addition to consider! A few things I'm unsure about:

Do we really need a third-party dependency on github.com/kevinburke/nacl/sign? The check can be completed by crypto/ed25519 outright, and I'd prefer not adding additional third-party dependencies (especially crypto ones!) if it's not necessary.
Is there a particular reason that you've vendored all dependencies in this change? We haven't previously, and while I'm not inherently against it, I think that it's a bit out of the scope of this change.

you're 100% right. i've removed the external lib dependency. thanks!

build is failing due to crypto/ed25519 not existing in go stdlib before 1.13. imo those versions can be dropped, go release policy says the currently supported releases are 1.14 and 1.15.

Why do you touch the request body? Seems unnecessary

Why do you touch the request body? Seems unnecessary

Why do you touch the request body? Seems unnecessary

Looks like we need to read the request body to validate the signature, so a copy of the original io.Reader body is created to replace the request body
after it's read from for the signature check before we return. Other functions later that use the same request can then read the body in normally.

Why do you touch the request body? Seems unnecessary

Looks like we need to read the request body to validate the signature, so a copy of the original io.Reader body is created to replace the request body
after it's read from for the signature check before we return. Other functions later that use the same request can then read the body in normally.

Thank you for the addition! This should definitely be useful for the adoption of webhook interactions 😃

Thank you for the addition! This should definitely be useful for the adoption of webhook interactions 😃

thanks for your work on this lib!

thanks for your work on this lib!


No module named 'util'

I have an error in 'Setup Imports' step - ModuleNotFoundError: No module named 'util'
Please validate and / or add comments how to import util module properly

never mind, the issue was on my side


Assistance Requested for Fine-Tuning on Visual Question Answering Task

First of all, thank you for this excellent work.
I would like to fine-tune the model from https://huggingface.co/THUDM/cogagent-vqa-hf on a visual question answering task. I would like to input a pair consisting of an image and a prompt (a question string), and I expect the output to be the answer (a string) and one or more bounding boxes with grounding to support the answer.
Unfortunately, I am unable to understand how the examples for training should be passed in the script
https://github.com/THUDM/CogVLM/blob/main/finetune_demo/finetune_cogagent_lora.sh
Could you kindly help me?
Thank you very much,
Danilo

bbox 也需要按照 字符的输入和输出格式进行匹配，格式为 [x,y,w,h](如果您是为了微调），可以直接放在文字中输出，bbox并不需要单独的处理，直接放在常规文字的后方就行
这是一个例子：
图像中有两只猫，分别是[[x1,y,1,w1.h1],[x2,y2,w2,h2]]这种格式

@zRzRzRzRzRzRzR
OK!
First of all, thank you very much for the prompt response.
One last question: from the script example with the dataset from https://www.kaggle.com/datasets/aadhavvignesh/captcha-images, only an image is used as input, without any additional text (in my case, the question), and the output is expected to be a string.
While the output is clear to me, I am now unclear on how to pass the image/text input pair.
Can you help me?
Thank you again!

Dear @zRzRzRzRzRzRzR and other authors, I am interested too in fine-tuning your model on a Visual Question Answering task.
Looking through the repository and the scripts, I can't find any mention of how to format my bounding boxes in the labels. As an example, if I want the model to generate in output something like
"The girl [[000,111,222,333]] is standing tall and the boy [[000,111,222,333]] is sitting on a chair [[000,111,222,333]]"
given a prompt and an image, how should I format these labels? Should I pass them as plain text? Don't I need to transform the bounding boxes into patches first?
Thank you in advance!


simcells.v: Generate the fine FF cell types by a python script.

This makes adding more FF types in the future much more manageable.
Fixes #1824.

@mwkmwkmwk -- I have a spreadsheet documenting flip flops.
I also had scripts which generate models at flipflop-download-csv.py, flipflop-generate.py and flipflop.py. The goal was to generate Yosys techmaps, good looking documentation (truth tables, schematic diagrams, etc).

Perhaps; the question is whether the "in-place" generator is even a good idea in this case — for a proper makefile flow, I suppose we should have the non-generated cells in a separate file (simcells_src.v)?

Perhaps; the question is whether the "in-place" generator is even a good idea in this case — for a proper makefile flow, I suppose we should have the non-generated cells in a separate file (simcells_src.v)?

I'd be fine either way, especially as the way you've built it means that nothing changes if the script is run when it doesn't need to be.


Warnings when compiling .stan file

Summary:
I was trying to compile a .stan file in cmdstan and got these warnings
/home/juandiaz/covid19_epi/Mexico/code/stan-models/base_reduce_sum3.hpp:1555:49: warning: ISO C++ says that these are ambiguous, even though the worst conversion for the first is better than the worst conversion for the second:                  (((1 - pow(weekly_rho, 2)) - pow(weekly_rho1, 2)) -                                                  ^ In file included from /cvmfs/soft.computecanada.ca/nix/store/59wpzavgpf1syqd6zzgc385qkm0qrd35-glibc-2.24-dev/include/features.h:368:0,                  from /cvmfs/soft.computecanada.ca/nix/store/m64vdgyzr1d29j8372iibl2m3ixg2f0d-gfortran-5.4.0/include/c++/5.4.0/x86_64-unknown-linux-gnu/bits/os_defines.h:39,                  from /cvmfs/soft.computecanada.ca/nix/store/m64vdgyzr1d29j8372iibl2m3ixg2f0d-gfortran-5.4.0/include/c++/5.4.0/x86_64-unknown-linux-gnu/bits/c++config.h:482,                  from /cvmfs/soft.computecanada.ca/nix/store/m64vdgyzr1d29j8372iibl2m3ixg2f0d-gfortran-5.4.0/include/c++/5.4.0/new:39,                  from stan/lib/stan_math/lib/eigen_3.3.9/Eigen/Core:82,                  from stan/lib/stan_math/lib/eigen_3.3.9/Eigen/Dense:1,                  from stan/lib/stan_math/stan/math/prim/fun/Eigen.hpp:22,                  from stan/lib/stan_math/stan/math/rev.hpp:4,                  from stan/lib/stan_math/stan/math.hpp:19,                  from stan/src/stan/model/model_header.hpp:4,                  from /home/juandiaz/covid19_epi/Mexico/code/stan-models/base_reduce_sum3.hpp:3: /cvmfs/soft.computecanada.ca/nix/store/59wpzavgpf1syqd6zzgc385qkm0qrd35-glibc-2.24-dev/include/bits/mathcalls.h:153:1: note: candidate 1: double pow(double, double)  __MATHCALL_VEC (pow,, (_Mdouble_ __x, _Mdouble_ __y));  ^ In file included from stan/lib/stan_math/stan/math/rev/fun/inc_beta.hpp:6:0,                  from stan/lib/stan_math/stan/math/rev/fun/grad_inc_beta.hpp:11,                  from stan/lib/stan_math/stan/math/rev/fun.hpp:74,                  from stan/lib/stan_math/stan/math/rev.hpp:10,                  from stan/lib/stan_math/stan/math.hpp:19,                  from stan/src/stan/model/model_header.hpp:4,                  from /home/juandiaz/covid19_epi/Mexico/code/stan-models/base_reduce_sum3.hpp:3: stan/lib/stan_math/stan/math/rev/fun/pow.hpp:242:26: note: candidate 2: std::complex<stan::math::var_value<double> > stan::math::pow(const std::complex<stan::math::var_value<double> >&, T) [with T = int; <template-parameter-1-2> = void]  inline std::complex<var> pow(const std::complex<var>& x, T y) {
The file was successfully compiled but I am not sure if I should be worried about these warnings
Current Version:
v2.25.0

If the model successfully compiled you have no reason to worry and I am going to close the issue.
Could you provide a bit more detail so we can look at ways to remove the warning?
Primarily the OS version and the output of g++ --version.


mod: update go-ipa

Update go-ipa to include the changes in this merged PR which brings a ~1.3x speedup in our replay benchmark regarding doing MSM in CommitToPoly(...).
Client should be aware of deleting previously generated precomp file and allow the code to regenerate it again automatically.

@gballet, just a comment about this failure in CI. That's because we merged this first than the go-verkle PR it's using.
[Prob you might already figured that out, but just in case if it was confusing]

Also note that means go-ethereum isn't pointing to go-verkle@master with this PR changes, since it's pointing to that other PR that doesn't have these changes.
I'd say whenever we merge the batch serialization , we can move again go-ethereum to go-verkle@master and be "clean" again.

@gballet, OK, to simplify stuff, I created a draft PR to have an easy reference of our replay benchmark using the fastest version of go-verkle and go-ipa.
Isn't expected to be merged or similar; we can clean up go-ethereum after.


Multi-dimensional coordinate mixup when writing to netCDF

Problem description
Under certain conditions, the netCDF files  produced by Dataset.to_netcdf() have the wrong coordinates attributed to the variables.  This seems to happen if there are multiple multi-dimensional coordinates, which share some (but not all) dimensions.
Test Dataset
Some sample code to generate a problematic Dataset:
import xarray as xr
import numpy as np

zeros1 = np.zeros((5,3))
zeros2 = np.zeros((6,3))
zeros3 = np.zeros((5,4))
d = xr.Dataset({
    'lon1': (['x1','y1'], zeros1, {}),
    'lon2': (['x2','y1'], zeros2, {}),
    'lon3': (['x1','y2'], zeros3, {}),
    'lat1': (['x1','y1'], zeros1, {}),
    'lat2': (['x2','y1'], zeros2, {}),
    'lat3': (['x1','y2'], zeros3, {}),
    'foo1': (['x1','y1'], zeros1, {'coordinates': 'lon1 lat1'}),
    'foo2': (['x2','y1'], zeros2, {'coordinates': 'lon2 lat2'}),
    'foo3': (['x1','y2'], zeros3, {'coordinates': 'lon3 lat3'}),
})
d = xr.conventions.decode_cf(d)

Here, the coordinates lat1,lat2,lat3 (and lon1,lon2,lon3) share one dimension with each other.  The Dataset itself gets created properly:
>>> print(d)

<xarray.Dataset>
Dimensions:  (x1: 5, x2: 6, y1: 3, y2: 4)
Coordinates:
    lat1     (x1, y1) float64 ...
    lat3     (x1, y2) float64 ...
    lat2     (x2, y1) float64 ...
    lon1     (x1, y1) float64 ...
    lon3     (x1, y2) float64 ...
    lon2     (x2, y1) float64 ...
Dimensions without coordinates: x1, x2, y1, y2
Data variables:
    foo1     (x1, y1) float64 ...
    foo2     (x2, y1) float64 ...
    foo3     (x1, y2) float64 ...

and each DataArray does have the right coordinates associated with them:
>>> print (d.foo1)

<xarray.DataArray 'foo1' (x1: 5, y1: 3)>
array([[ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.]])
Coordinates:
    lat1     (x1, y1) float64 ...
    lon1     (x1, y1) float64 ...
Dimensions without coordinates: x1, y1

>>> print (d.foo2)

<xarray.DataArray 'foo2' (x2: 6, y1: 3)>
array([[ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.],
       [ 0.,  0.,  0.]])
Coordinates:
    lat2     (x2, y1) float64 ...
    lon2     (x2, y1) float64 ...
Dimensions without coordinates: x2, y1

>>> print (d.foo3)

<xarray.DataArray 'foo3' (x1: 5, y2: 4)>
array([[ 0.,  0.,  0.,  0.],
       [ 0.,  0.,  0.,  0.],
       [ 0.,  0.,  0.,  0.],
       [ 0.,  0.,  0.,  0.],
       [ 0.,  0.,  0.,  0.]])
Coordinates:
    lat3     (x1, y2) float64 ...
    lon3     (x1, y2) float64 ...
Dimensions without coordinates: x1, y2

The problem
The problem happens when I try to write this to netCDF (using either the netCDF4 or scipy engines):
d.to_netcdf("test.nc")

The resulting file has extra coordinates on the variables:
~$ ncdump -h test.nc
netcdf test {
dimensions:
	x1 = 5 ;
	y1 = 3 ;
	y2 = 4 ;
	x2 = 6 ;
variables:
	double lat1(x1, y1) ;
		lat1:_FillValue = NaN ;
	double lat3(x1, y2) ;
		lat3:_FillValue = NaN ;
	double lat2(x2, y1) ;
		lat2:_FillValue = NaN ;
	double lon1(x1, y1) ;
		lon1:_FillValue = NaN ;
	double lon3(x1, y2) ;
		lon3:_FillValue = NaN ;
	double lon2(x2, y1) ;
		lon2:_FillValue = NaN ;
	double foo1(x1, y1) ;
		foo1:_FillValue = NaN ;
		foo1:coordinates = "lat1 lat3 lat2 lon1 lon3 lon2" ;
	double foo2(x2, y1) ;
		foo2:_FillValue = NaN ;
		foo2:coordinates = "lon1 lon2 lat1 lat2" ;
	double foo3(x1, y2) ;
		foo3:_FillValue = NaN ;
		foo3:coordinates = "lon1 lon3 lat1 lat3" ;

// global attributes:
		:_NCProperties = "version=1|netcdflibversion=<IP_ADDRESS>|hdf5libversion=1.8.18" ;
}

Here, foo1, foo2, and foo3 have extra coordinates associated with them.  Interestingly, if I re-open this netCDF file with xarray.open_dataset, I get the correct coordinates back for each DataArray.  However, other netCDF utilities may not be so forgiving.
Expected Output
I would expect the netCDF file to have a single pair of lat/lon for each variable:
        ...
	double foo1(x1, y1) ;
		foo1:_FillValue = NaN ;
		foo1:coordinates = "lat1 lon1" ;
	double foo2(x2, y1) ;
		foo2:_FillValue = NaN ;
		foo2:coordinates = "lon2 lat2" ;
	double foo3(x1, y2) ;
		foo3:_FillValue = NaN ;
		foo3:coordinates = "lon3 lat3" ;
        ...
}

Output of xr.show_versions()

INSTALLED VERSIONS
commit: c2b205f29467a4431baa80b5c07fe31bda67fbef
python: 2.7.12.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.0-101-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: None.None
xarray: 0.10.0-5-gc2b205f
pandas: 0.21.0
numpy: 1.13.3
scipy: None
netCDF4: 1.3.1
h5netcdf: None
Nio: None
bottleneck: None
cyordereddict: None
dask: None
matplotlib: None
cartopy: None
seaborn: None
setuptools: 38.2.4
pip: 9.0.1
conda: None
pytest: 3.3.1
IPython: None
sphinx: None

It looks like currently write coordinates in data variable attributes if the share any dimensions in common. This should probably be updated to require that all dimensions match:
https://github.com/pydata/xarray/blob/c2b205f29467a4431baa80b5c07fe31bda67fbef/xarray/conventions.py#L1217-L1220
Any interest in putting together a pull request? :)

I can try putting together a pull request, hopefully without breaking any existing use cases.  I just tested switching the any condition to all in the above code, and it does fix my one test case...
...However, it breaks other cases, such as if there's another axis in the data (such as a time axis).  I think the all condition would require "time" to be one of the dimensions of the coordinates.
Here's an updated test case:
import xarray as xr
import numpy as np

zeros1 = np.zeros((1,5,3))
zeros2 = np.zeros((1,6,3))
zeros3 = np.zeros((1,5,4))
d = xr.Dataset({
    'lon1': (['x1','y1'], zeros1.squeeze(0), {}),
    'lon2': (['x2','y1'], zeros2.squeeze(0), {}),
    'lon3': (['x1','y2'], zeros3.squeeze(0), {}),
    'lat1': (['x1','y1'], zeros1.squeeze(0), {}),
    'lat2': (['x2','y1'], zeros2.squeeze(0), {}),
    'lat3': (['x1','y2'], zeros3.squeeze(0), {}),
    'foo1': (['time','x1','y1'], zeros1, {'coordinates': 'lon1 lat1'}),
    'foo2': (['time','x2','y1'], zeros2, {'coordinates': 'lon2 lat2'}),
    'foo3': (['time','x1','y2'], zeros3, {'coordinates': 'lon3 lat3'}),
    'time': ('time', [0.], {'units': 'hours since 2017-01-01'}),
})
d = xr.conventions.decode_cf(d)

The resulting Dataset:
<xarray.Dataset>
Dimensions:  (time: 1, x1: 5, x2: 6, y1: 3, y2: 4)
Coordinates:
    lat1     (x1, y1) float64 ...
  * time     (time) datetime64[ns] 2017-01-01
    lat3     (x1, y2) float64 ...
    lat2     (x2, y1) float64 ...
    lon1     (x1, y1) float64 ...
    lon3     (x1, y2) float64 ...
    lon2     (x2, y1) float64 ...
Dimensions without coordinates: x1, x2, y1, y2
Data variables:
    foo1     (time, x1, y1) float64 ...
    foo2     (time, x2, y1) float64 ...
    foo3     (time, x1, y2) float64 ...

saved to netCDF using
d.to_netcdf("test.nc")

With the any condition, I have too many coordinates:
~$ ncdump -h test.nc
netcdf test {
dimensions:
	x1 = 5 ;
	y1 = 3 ;
	time = 1 ;
	y2 = 4 ;
	x2 = 6 ;
variables:
        ...
	double foo1(time, x1, y1) ;
		foo1:_FillValue = NaN ;
		foo1:coordinates = "lat1 lat3 lat2 lon1 lon3 lon2" ;
	double foo2(time, x2, y1) ;
		foo2:_FillValue = NaN ;
		foo2:coordinates = "lon1 lon2 lat1 lat2" ;
	double foo3(time, x1, y2) ;
		foo3:_FillValue = NaN ;
		foo3:coordinates = "lon1 lon3 lat1 lat3" ;
        ...
}

With the all condition, I don't get any variable coordinates (they're dumped into the global attributes):
~$ ncdump -h test.nc
netcdf test {
dimensions:
	x1 = 5 ;
	y1 = 3 ;
	time = 1 ;
	y2 = 4 ;
	x2 = 6 ;
variables:
        ...
	double foo1(time, x1, y1) ;
		foo1:_FillValue = NaN ;
	double foo2(time, x2, y1) ;
		foo2:_FillValue = NaN ;
	double foo3(time, x1, y2) ;
		foo3:_FillValue = NaN ;

// global attributes:
		:_NCProperties = "version=1|netcdflibversion=<IP_ADDRESS>|hdf5libversion=1.8.18" ;
		:coordinates = "lat1 lat3 lat2 lon1 lon3 lon2" ;
}

So the update may be a bit more tricky to get right.  I know the DataArray objects (foo1,foo2,foo3) already have the right coordinates associated with them before writing to netCDF, so maybe the logic in _encode_coordinates could be changed to utilize v.coords somehow?  I'll see if I can get something working for my test cases...

I know the DataArray objects (foo1,foo2,foo3) already have the right coordinates associated with them before writing to netCDF, so maybe the logic in _encode_coordinates could be changed to utilize v.coords somehow?

DataArray objects get appropriate coordinates when indexed from a Dataset by using the following logic:
https://github.com/pydata/xarray/blob/3a28b611e40f2a09c05f982242f638cc3f7d94bf/xarray/core/dataset.py#L785-L789
We could should duplicate the same logic for encoding coordinates on particular variables.

I think I've duplicated the logic from _construct_dataarray into _encode_coordinates.  Test cases are passing, and my actual files are writing out properly.  Hopefully nothing else got broken along the way.


Fixes #7 - Fix exit codes in extract command

According to the Django docs, CommandError will return an exit code of 1 and also print the error to stderr. Seems like what we want.

BEE-YOO-TIFUL!


"Segmentation fault" error

Hi @lukasalexanderweber
Thank you for the great work!
I'm having some troubles with the algorithm since yesterday and though you might provide some information.
While using stitching pipeline I'm getting error: "Segmentation fault" without any further explanation. It is not "Stitching error" and happening sometime during cropping by my tests, although I can't get precise place or understand what could cause the error. I haven't done any changes to my code since yesterday.
Will appreciate any ideas!
Best,
Mariia

I read some other errors with cropping. Should add that I'm running code on remote Linux server

What do you mean with " I read some other errors with cropping. "

@lukasalexanderweber I mean other issues like https://github.com/OpenStitching/stitching/issues/119

Quite sure this isn't related to the stitching package: https://stackoverflow.com/questions/2346806/what-is-a-segmentation-fault

Hi @lukasalexanderweber you are right - I've solved segmentation error but still getting errors: free(): invalid size or munmap_chunk(): invalid pointer. Have no idea how to solve them. Can't make even one stitching.

This is also really C++ specific: https://stackoverflow.com/questions/32118545/munmap-chunk-invalid-pointer.
Don't you have a way to test it locally and make sure your installation on the remote server is correct

Closing as the problem was solved!