nextest has issues running tests that use serial_test

First off, good work on nextext, it is a really nice idea and implementation.
I have some tests in the test suite for rust_xlsxwriter that use the crate serial_test to serialise test cases that contain multiple tests that write an Excel output file with the same name. Without this I would get periodic failures as 2 tests tried to create the same output file.
This is more of an fyi than a bug report and I don't expect you to fix this. I could work around it by dropping test_serial and having different output names for each test case or by adding --retries to nextest.
Anyway, here is a simple example to reproduce:

/tmp$ git clone git@github.com:jmcnamara/rust_xlsxwriter.git
Cloning into 'rust_xlsxwriter'...
...

/tmp$ cd rust_xlsxwriter

/tmp/rust_xlsxwriter (main)$ cargo nextest run
    Updating crates.io index
   Compiling libc v0.2.134
   ...
   Compiling rust_xlsxwriter v0.3.1 (/Users/John/Development/xlsx/tmp/rust_xlsxwriter)
   Compiling serial_test_derive v0.9.0
   Compiling serial_test v0.9.0
    Finished test [unoptimized + debuginfo] target(s) in 1m 13s
    Starting 111 tests across 56 binaries
        PASS [   0.266s] rust_xlsxwriter::array_formula01 test_array_formula01
        PASS [   0.277s] rust_xlsxwriter::array_formula03 test_array_formula03
        PASS [   0.285s] rust_xlsxwriter::array_formula02 test_array_formula02
        PASS [   0.285s]     rust_xlsxwriter::bootstrap01 bootstrap01_single_worksheet
        PASS [   0.294s] rust_xlsxwriter::array_formula04 test_array_formula04
        PASS [   0.302s]     rust_xlsxwriter::bootstrap01 bootstrap01_add_default_worksheet
        PASS [   0.301s]     rust_xlsxwriter::bootstrap02 bootstrap02_multiple_worksheets
        PASS [   0.304s]     rust_xlsxwriter::bootstrap03 bootstrap03_multiple_worksheets_with_names
        PASS [   0.243s]     rust_xlsxwriter::bootstrap04 bootstrap04_write_numbers
        PASS [   0.281s]     rust_xlsxwriter::bootstrap05 bootstrap05_test_spans
        PASS [   0.300s]     rust_xlsxwriter::bootstrap06 bootstrap06_write_string
        PASS [   0.296s]     rust_xlsxwriter::bootstrap07 bootstrap07_write_repeated_strings
        PASS [   0.282s]     rust_xlsxwriter::bootstrap09 bootstrap09_write_a_formatted_string
        PASS [   0.281s]     rust_xlsxwriter::bootstrap11 bootstrap11_bold_and_italic_text
        PASS [   0.291s]     rust_xlsxwriter::bootstrap10 bootstrap10_bold_text_on_two_sheets
        PASS [   0.305s]     rust_xlsxwriter::bootstrap08 bootstrap08_write_repeated_strings_on_different_worksheets
        PASS [   0.173s]     rust_xlsxwriter::bootstrap12 bootstrap12_bold_and_italic_text_mixed
        PASS [   0.193s]     rust_xlsxwriter::bootstrap13 bootstrap13_number_format
        PASS [   0.278s]     rust_xlsxwriter::bootstrap15 bootstrap14_number_format_via_legacy_index
        PASS [   0.290s]     rust_xlsxwriter::bootstrap14 bootstrap13_repeated_number_format
        PASS [   0.279s]     rust_xlsxwriter::bootstrap16 bootstrap16_test_nan
        PASS [   0.303s]     rust_xlsxwriter::bootstrap17 bootstrap17_color_font
        PASS [   0.309s]     rust_xlsxwriter::bootstrap18 bootstrap18_duplicate_formats_in_different_order
        PASS [   0.311s]     rust_xlsxwriter::bootstrap19 bootstrap19_font_name_and_size
        PASS [   0.276s]     rust_xlsxwriter::bootstrap20 bootstrap20_font_underlines
        PASS [   0.246s]     rust_xlsxwriter::bootstrap21 bootstrap21_strikethrough_text
        PASS [   0.238s]     rust_xlsxwriter::bootstrap22 bootstrap22_super_sub_script
        PASS [   0.269s]     rust_xlsxwriter::bootstrap23 bootstrap23_set_row
        FAIL [   0.281s]     rust_xlsxwriter::bootstrap23 bootstrap23_set_row_pixels

--- STDOUT:                  rust_xlsxwriter::bootstrap23 bootstrap23_set_row_pixels ---

running 1 test
test bootstrap23_set_row_pixels ... FAILED

failures:

failures:
    bootstrap23_set_row_pixels

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.13s

--- STDERR:                  rust_xlsxwriter::bootstrap23 bootstrap23_set_row_pixels ---
thread 'bootstrap23_set_row_pixels' panicked at 'called `Result::unwrap()` on an
    `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }',
    tests/common/mod.rs:47:31
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

   Canceling due to test failure: 7 tests still running
        PASS [   0.298s]     rust_xlsxwriter::bootstrap24 bootstrap24_set_row
        PASS [   0.316s]     rust_xlsxwriter::bootstrap25 bootstrap25_set_column_pixels
        FAIL [   0.323s]     rust_xlsxwriter::bootstrap25 bootstrap25_set_column

--- STDOUT:                  rust_xlsxwriter::bootstrap25 bootstrap25_set_column ---

running 1 test
test bootstrap25_set_column ... FAILED

failures:

failures:
    bootstrap25_set_column

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.12s

--- STDERR:                  rust_xlsxwriter::bootstrap25 bootstrap25_set_column ---
thread 'bootstrap25_set_column' panicked at 'called `Result::unwrap()`
    on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }',
    tests/common/mod.rs:47:31
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

        PASS [   0.282s]     rust_xlsxwriter::bootstrap26 bootstrap25_set_column_with_format
        PASS [   0.258s]     rust_xlsxwriter::bootstrap27 bootstrap27_set_row_2_worksheets
        PASS [   0.187s]     rust_xlsxwriter::bootstrap28 bootstrap28_set_column_contiguous_formats
        PASS [   0.178s]     rust_xlsxwriter::bootstrap29 bootstrap29_alignment
        PASS [   0.192s]     rust_xlsxwriter::bootstrap30 bootstrap30_alignment
------------
     Summary [   1.358s] 37/111 tests run: 35 passed, 2 failed, 0 skipped
        FAIL [   0.281s]     rust_xlsxwriter::bootstrap23 bootstrap23_set_row_pixels
        FAIL [   0.323s]     rust_xlsxwriter::bootstrap25 bootstrap25_set_column
error: test run failed

Thanks for the issue!
Yes, this is a known issue with nextest -- in general, the solution is isolating the tests somehow. In this case, randomizing file names or using temporary directories would resolve the issue.


Create UI kit

It would be cool if somebody wanted to put the time in to make a UI kit for Ionic, whether that be in the form of a photoshop document, I don't know... just an idea.

Hi guys,
What are the chances of a UI Kit for Sketch @bensperry @mlynch @adamdbradley ?
Thank you!

Or a UI Kit for UXPin?

Hey! What's up with the UI kit for Sketch/Photoshop? :D

@mlynch Any update for this? I am hoping to give some designers a baseline to work off of (to make my life easier of course). No response from you guys for a while on this issue.

Hey, so we have since solved this issue with Ionic Creator! Ionic creator gives you a browser based drag and drop prototyping tool to prototype your apps. Thanks!

This is looking good - https://market.ionicframework.com/themes/ionic-sketch


Compile to Java 21 bytecode

We have been running in Java 21 runtime for a couple of weeks and every
works as expected.

This change is

Will hold off for another week for Java 21 runtime to bake a bit more. Planning to merge next week.


iOS: Should only detect QRcode inside frame

Expected behaviour:
Camera should only scan when QR is within the frame
Observed behaviour:
Camera scanned QR when QR is out of the frame as well.
*Only in iOS

+1 Same issue here.


Fixed RT camera

RT Camera tool fixed by re-adding UpdateRenderTarget function that was
removed by garry in update 13

@Divran dont add global functions, even if they existed before.
Especially if they existed before.
Someone might detect the absence of that function and do stuff.
Don't add any global stuff, because it tends to break other addons.

There's a variable called RenderTargetCamera which appears to be global as well. This seems to be garry's code as well. If we make this function local, the variable would still be global, and I believe it needs to be, if other RT camera addons use it.

so how does garry's rt camera work nowadays?

I believe it was removed

Can you verify that
Was there a reason given?

Nah I just remember garry removed several tools with the gmod 13 update, and I'm pretty sure the RT cam was one of them. No idea why.


Docs fix spelling issues

Hello
I fixed several spelling issues in order to ensure a better understanding.
Br, Elias.

done

Thanks for contributing! Feel free to try your hand at coding tasks as well!


Add lenght to Connect with lines analysis result

Now its giving also the length of each line so we should add that to the explanation of the analysis.

I've changed camshaft to return length in km and also returns a new column called length_mile. PR ready, not deployed yet.

After discuss with @rochoa I removed the a new column length_mile. We are going to apply a common strategy to have both metric and imperial system.

so what did we do finally?

For now, we have a column lenght in Kilometers.

ok closing then! Thanks @dgaubert!


[Doc Improvement][Add a link in see also for meeting API][2809656]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/apps-in-teams-meetings/meeting-apps-apis.md
93
24
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit cb8020e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/meeting-apps-apis.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/apps-in-teams-meetings/meeting-apps-apis.md
90
47
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Crashes on sparrow horn

Here we create an Item for each equippable,
https://github.com/GeekyEggo/DestinyTailor/blob/a7dee9c9eb2482ed24a8658a391dc6ab3b85a4f6/client/js/services/inventoryService.js#L45
And the equippable is required to have at least one item,
https://github.com/GeekyEggo/DestinyTailor/blob/a7dee9c9eb2482ed24a8658a391dc6ab3b85a4f6/client/js/models/item.js#L20
But on my character (psn:tantalor, Hunter) I have a sparrow horn (buckethash:3796357825) that has no items, and crashes the app in item.js

Hey @tantalor, thanks for raising this! I believe it's related to classified items; I've got a hotfix incoming, should be available shortly.

Hopefully this should all be sorted now; psn/tantalor/hunter. Any problems, just let me know. 😄

THANKS 😀 😄


Sheild icon is not visible on the URL bar

Description
I'm using edge-frfox v23.12.2. I'm using dark mode on my firefox, Once I hover the cursor on the URL bar the shield icon appears.
Screencast from 2023-12-03 03-17-56.webm
Configuration

Firefox Version: Nightly 122
OS: Ubuntu

This is intended behaviour, as Microsoft Edge does not have this button and it doesn't serve much purpose other than to open the tracking protection menu, it is hidden by default. If you need to access the menu, then you can hover over the URL bar then click it.
If you want to disable this, the code for hiding the button can be found here:
https://github.com/bmFtZQ/edge-frfox/blob/59ad4dac25f2a594679751fb27bb8b61d490bc22/chrome/toolbar/urlbar.css#L139-L141


Reposition container notes

Move container notes to the bottom of the material list
Display notes with a single line preview of the notes
Handle new lines in notes
Handle multiple notes in the notes array by placing 2 new lines between each array element
Mark out residual containers so it's clear what they're there for

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove EXHIBITOR_URL environment variable

We are not using the environment variable during the tests. Let's remove
all reference to it.

:+1: we can also get rid of VBOX_IP


Sahar

👷 Deploy Preview for adoring-leavitt-e31a11 processing.

Name
Link

🔨 Latest commit
1f697e0f381b44ff6bd56a02ce7053766e279e9f

🔍 Latest deploy log
https://app.netlify.com/sites/adoring-leavitt-e31a11/deploys/62a8818450faae000940fc37


Support Array.Get

As there're some cases like #155 that Array.Get can be helpful, I implemented it.
@tgpfeiffer Can you check if making jsonPathHead optional just like jsonPath <- jsonPathHead? jsonPathNonHead* !. is fine?

I noticed that the previous PEG rules accept .field due to making the head optional. So, I replaced the rule to accept jsonPathHead or jsonArraySlices as a head.

I think with your fix in 3ed3fd4 it should be fine.

Great Job!


Support for multiple date formats in one JSON

Nice design, test code and license comment!
Looks great 👍
Thank you for your PR!


Update Stale.yml

Reverting to original configuration after a bug was resolved in Stale bot.

This change is

Reviewed 1 of 1 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


Cannot find module 'portfinder'

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Windows 10

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:

ng --version not working, node version 4.50 (LTS)

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.

No App created yet

The log given by the failure. Normally this include a stack trace and some
more information.

Error cannot find module 'portfinder'

Mention any other details that might be useful.

I installed globally via NPM as normal and when I try to either check the version or generate a new project it throws the same error.

Thanks! We'll be in touch soon.

@JoshWilliams92 -- this looks like a dup of #1782

I have resolved the issue by globally installing the portfinder module and then npm installing it in my main project directory after generating a new project. I had this problem today also with the reflect-metadata module but repeated the same process as above.

Dupe of #1782.


Updates Bulk Edit status combination/validation for Findings

Bulk Edit for findings allowed for contradictory selections (e.g. "Active" and "Mitigated" simultaneously). Added functionality similar to Bulk Edit for Endpoints to eliminate this.

@blakeaowens Just noticed after merging that view_test.html contains the same logic and should be updated as well. Could you make another PR maybe?
At some point we need to deduplicate these 2 ways of displaying a list of findings, but currently we have to maintain both pages.


Add usage examples

title

I intend to do this. For now I would recommend looking at the quick test client 4.0, specifically hud/main.lua has uses of PeekPoke for examples there.


How to add a new payment gateway

I can create the documentation. Please connect me to the developer for this part @restmount


move PRE and BQE declaration from ingress/egress to top level package

I am feeling itchy about having to write down PacketReplicationEngine pre every time I create an ingress block. I hope we can move them to the top level package definition, where they belong. Ideally, users shouldn't even need to create an instance of PRE, but I haven't figured out how to do that.

Looks reasonable to me, given that there are no methods for those objects callable from P4 code.

@cc10512 OK to merge this one in, then?

Yes, looks good to me.

Need to update all examples the make sure they still compiles?

Yes, I can do that separately, unless someone else beats me to it.


feat(cli): Tag Support

Issue #, if available:
#4607
Description of changes:
This PR implements tags into the Amplify CLI workflow. I'd love to receive as much feedback! There are definitely things I know that can be done better. Feel free to let me know if there are parts of the code you don't understand too.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sebastiancrossa Can you fix the conflicts?

Can you fix the conflicts?


[Add]

Site URL
https://colormagic.app/
Description of the above provided site
ColorMagic is an AI color palette generator. Generate colors by entering the keyword into the textbox
Category
Frontend
Sub Category
colors
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@07jhashubham Thanks Shubham :), you can now reference this issue in the PR


reserved keywords clarification

When describing restrictions on the custom names of objects, the "reserved keywords" are mentioned, in numerous places:
cameras.md#camera-names
lights.md#light-names
sources.md#source-names
styles.md#style-names
textures.md#texture-names
layers.md#layer-name
layers.md#sublayer-name
layers.md#properties
This was originally written with the understanding that there were globally-reserved keywords, and that none of them could be used as custom names in any of these circumstances. Is this true?
Or – is it that a custom name can be anything except one of the reserved keywords at that layer in the document – and if there aren't any at that layer, the name can be anything at all?
Eg a layer object can take data and filter parameters (in addition to any sublayers), so the sublayers can be named anything except "data" and "filter" – whereas the cameras object has only custom names as parameters, so those names can be anything?
cc @bcamper

Reserved words are context-sensitive. For example, a layer can have any name except for data, filter, or properties. But a camera or light can be named data, for example.

Fixed by https://github.com/tangrams/tangram-docs/commit/9853801cfb5ca5e706de637c14f694b3a0e4b574


Model unknown Manuf.: ABB - Model: -3P46-

After long time running fine, today started loggin this message of model unknown
2022-10-14 13:48:43.663 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] (opt_comm_model) Model unknown, report to @alexdelprete on the forum the following data: Manuf.: ABB - Model: -3P46- - Options: 0x03ED/0xFF69/ - OptModel: 0x03ED/0xFF69/ - OptModelInt: 3

Claudio, it's not a real error, did you read the message? :)
I put the error on purpose to ask users to provide the real model of the inverter associated with Option Model (in your case it's 3) so I can add it to the list of inverters known to the integration.
So, can you tell me the specific model of your inverter? In next update you'll find the correct model and no error in the log.
Ciao.

Thanks
The mode il UNO-DM-4.6-TL-PLUS
Thanks
Claudio

On 14 Oct 2022, at 21:42, Alessandro Del Prete @.***> wrote:
Claudio, it's not a real error, did you read the message? :)
I put the error on purpose to ask users to provide the real model of the inverter associated with Option Model (in your case it's 3) so I can add it to the list of inverters known to the integration.
So, can you tell me the specific model of your inverter? In next update you'll find the correct model and no error in the log.
Ciao.
—
Reply to this email directly, view it on GitHub https://github.com/alexdelprete/ha-abb-powerone-pvi-sunspec/issues/32#issuecomment-1279390695, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXK6MPXR7XZSMM7OZP5R6ALWDGZTNANCNFSM6AAAAAARFNXRMQ.
You are receiving this because you authored the thread.

Added your model and released new version. If you upgrade the component, you should see the model in the sensors list, instead of 0x03ED/0xFF69.
Let me know if it works.

Thank you. I’m worried to reboot due to the other issue I opened today, the one relate do pymodbus

On 14 Oct 2022, at 22:25, Alessandro Del Prete @.***> wrote:
Added your model and released new version. If you upgrade the component, you should see the model in the sensors list, instead of 0x03ED/0xFF69.
Let me know if it works.
—
Reply to this email directly, view it on GitHub https://github.com/alexdelprete/ha-abb-powerone-pvi-sunspec/issues/32#issuecomment-1279427114, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXK6MPQOSEA7SNU7JOPF3XTWDG6SXANCNFSM6AAAAAARFNXRMQ.
You are receiving this because you authored the thread.

Thank you. I’m worried to reboot due to the other issue I opened today, the one relate do pymodbus

Sorry, I didn't check that issue. I'll answer there. Closing this issue.

Just tested doing a snapshot before reboot and nothing. Had to restore the snapshot because of the issue #31 preventing from load the integration

On 14 Oct 2022, at 22:34, Alessandro Del Prete @.***> wrote:
Thank you. I’m worried to reboot due to the other issue I opened today, the one relate do pymodbus
Sorry, I didn't check that issue. I'll answer there. Closing this issue.
—
Reply to this email directly, view it on GitHub https://github.com/alexdelprete/ha-abb-powerone-pvi-sunspec/issues/32#issuecomment-1279437434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXK6MPXKIDPPD4MGIQMT7WTWDG7V3ANCNFSM6AAAAAARFNXRMQ.
You are receiving this because you authored the thread.


Reverting removal of reference to global.yml variables in ci.yml

Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
Fix cosmos custom pipeline yml which was broken by change to main pipeline yml to add CodeQL support
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

If cosmos is broken here we should fix it similar to what we did in java https://github.com/Azure/azure-sdk-for-java/pull/33501

azp /run  js - cosmosdb - ci


add SOFARPC to support list

Please answer these questions before submitting pull request

Why submit this pull request?
[ ] New feature provided

add SOFARPC to support list
see https://github.com/apache/incubator-skywalking/pull/1210#issuecomment-394156229

Coverage decreased (-0.004%) to 24.001% when pulling 568e524540c9dd533d1f786232267c51fffeb1aa on leizhiyuan:add_sofa_rpc_support_doc into c4766ecbf251613bafef55722e26bba554a4aba6 on apache:master.


Add Hackerearth Problems and Solutions

Add problems & solutions from Hackeearth in the Hackerearth folder

can you assign me this issue. Thanks

Could I also take on this Issue?

Hey, can i work on this?

This issue to open to all, you may send a Pull Request after reading the Contributing guidelines.


[FEEDBACK]: Web5 Quickstart Output

Type
Feedback - Improvement Suggestion
Feedback
From @jiyoontbd in Discord:

in web5 quickstart page step 4: https://developer.tbd.website/docs/web5/quickstart/#4-write-dwn-records
i think it could be neat for folks walking through the quickstart to see a console log that actually prints the destructured record object stored in the DWN.
the most obvious (and not the prettiest) way would be to call console.log('write result', JSON.stringify(record, null, 4)) instead of console.log('write result', record) as shown in the screenshot #1
as a side note, the collapsible code block below the "Run!" button in this step shows the whole object returned from the await web5.dwn.records.create(...) method, not just the destructured record object - see screenshot #2

Screenshots

developer.tbd.website URL
https://discord.com/channels/937858703112155166/949067751803191397/1105672024115912755
Browser
Chrome
Relevant log output
No response

@blackgirlbytes can you validate that this still needs to be done or close it if it doesn't? ty


Remove dependency on wmic.exe, use CMDCMDLINE variable

Details

https://stackoverflow.com/a/53474705/4424236
https://ss64.com/nt/syntax-variables.html

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.


IPIP broken in EL 8.3 with multiple drivers

This is just a heads up to help triage bug report, nothing to fix in calico.
With EL (RHEL/CentOS/Oracle) 8.3, I've seen 2 cases where IPIP is broken

using Mellanox network card (mlx5_core driver), 8.3 ask the NIC firmware what offload is supported, but the firmware is buggy

OLD FW / DRIVER with Feature
NO iperf traffic
# ethtool -i eth2 | grep firm ; uname -r ; ethtool -k eth2 | grep ipx
firmware-version: 14.26.1040 (MT_2420110034)
4.18.0-240.el8.x86_64
tx-ipxip4-segmentation: on
tx-ipxip6-segmentation: on

FIXED FW / DRIVER with Feature
iperf traffic works
# ethtool -i eth2 | grep firm ; uname -r ; ethtool -k eth2 | grep ipx
firmware-version: 14.29.0538 (MT_2420110034)
4.18.0-240.el8.x86_64
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]

Nothing public, internal RHEL case https://access.redhat.com/support/cases/#/case/02800279

using VMWare (vmxnet3 driver) udp tunnel segmentation is enabled since 8.3, but not working
https://github.com/kubernetes-sigs/kubespray/issues/7268#issuecomment-775929387

-tx-udp_tnl-segmentation: off [fixed]
-tx-udp_tnl-csum-segmentation: off [fixed]
+tx-udp_tnl-segmentation: on
+tx-udp_tnl-csum-segmentation: on

Possible Solution
Use VXLAN Crosssubnet or VXLAN Always
Your Environment

Operating System and version: EL 8.3

@champtar thanks for the heads up!

Found a new broken driver with IPIP, qede with CentOS 7.8
# ethtool -i ens3f6
driver: qede
version: <IP_ADDRESS>
firmware-version: mfw <IP_ADDRESS> storm <IP_ADDRESS>

https://bugzilla.redhat.com/show_bug.cgi?id=1968614
https://lkml.org/lkml/2021/1/11/849
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062

Related: https://github.com/projectcalico/calico/issues/4727


Adds the necessary models for Payouts page

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2068

PR #2071

PR #2072

PR #2073

PR #2074   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: TLpS7mRK611WyBbtlMOK

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 7mQp0aCulfn1WjwNMx70


Override of map2html5-coverImpl.xsl in HTML5 plugin

Expected Behavior
Extension point <feature extension="dita.xsl.html5.cover" file="xsl/map2html5-coverImpl.xsl"/> (in plugin.xml) permit to override templates present in map2html5-coverImpl.xsl.
Actual Behavior
Actually I try, via dita.xsl.html5.cover extension point, to override template <xsl:template match="*[contains(@class, ' map/map ')]" mode="chapterBody"> present in map2html5-coverImpl.xsl.
But I can't see modifications made in my custom stylesheet in HTML5 output,.
Possible Solution

Steps to Reproduce

Create a custom HTML5 plugin
Add dita.xsl.html5.cover extension point in plugin.xml to override xsl/map2html5-coverImpl.xsl
Make modifications on <xsl:template match="*[contains(@class, ' map/map ')]" mode="chapterBody"> in custom map2html5-coverImpl.xsl
Run HTML5 transformation

Copy of the error message, log file or stack trace

Environment

DITA-OT version: 3.0.4
Operating system and version: Windows 10
How did you run DITA-OT? : Oxygen
Transformation type: HTML5

In OT 3.4 I still have the problem. When I switched from 2.5.4 I wanted to try to implement the correct way. I can't overwrite the template <xsl:template match="*[contains(@class, ' map/map ')]" mode="chapterBody"> in xsl/map2html5-coverImpl.xsl via the dita.xsl.html5.cover extension point.


Add content encoding question in WAF

Currently, WAF aware the UTF-8 encoded content only.

@tksh164 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


example

if i want only scan for only for CVE-2022-22954
i didnt see a example

In this case, it is recommended to use nuclei directly


Custom Avatar based on Mui Avatar

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 71.372%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
1948

Relevant Lines:
2510

💛  - Coveralls


Feat/tiflash flame graph

related: #782

TiFlash flame graph support

/cc @breeswish @baurine

I will test it today.

/lgtm


Maintained ?

Issue Summary
There has been no commit for a while. @JavaCafe01 maybe it's time to call for maintainers, move this to an org maybe ? PdfViewer is deployed as part of /e/ OS, maybe they could help ?
Thanks for the great work 🙏🏿

@rgarrigue I know I've made lots of development promises but unfortunately I'm very busy with school work and other parts of life.
Changing this repo ownership to an organization is actually a great idea. I'll think about it after I'm sure I removed all the donation links.
I never knew this app was on /e/OS! That's pretty cool. They have this app mirrored in Gitlab, so I might leave a comment there.


feat: multi-region support

This pull request extends sqsmv to support moving messages across regions. This is accomplished via a naive regex match, relying on the region to be the first value in the URL (which is currently true for all SQS URL formats).

Opened by mistake, let me know if you want this change!


Add a welcome bot

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Add a welcome bot for new issue, pull request etc.
Kindly assign it to me.
[under gssoc]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Go ahead @itsIapetus


add apcu storage

for php 7 support

You're probably better off enabling apcu-bc. This is code I took from one of my Dockerfiles.
pecl install apcu
pecl install apcu_bc-beta
echo extension=apcu.so >> /usr/local/etc/php/conf.d/docker-php-ext-apcu.ini
echo extension=apc.so >> /usr/local/etc/php/conf.d/docker-php-ext-apcu.ini

Duplicate of #62.


chore: update ape core 0.5

What I did

Updated ape core to >=0.5.0,<0.6.0: fixes issue with cli where ape doesn't recognize ape notebook as a command
Updated template dependencies for current state in ApeWorX/project-template
Fixed CONTRIBUTING.md for a small typo

How I did it
Changed setup.py file.
How to verify it

Install ape-notebook plugin pointing to this branch with eth-ape>=0.5.0,<0.6.0.
Run ape notebook.
Check notebook server starts in ./notebook/ directory

Checklist

[x] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[x] PR title follows Conventional Commit standard (will be automatically included in the changelog)

alright, I'll merge this one for now. will release as v0.5.0a1

released! https://pypi.org/project/ape-notebook/0.5.0a1/

woot!


Automatically generating dependency notations

Accept related PR?
Discussed in https://github.com/jmfayard/refreshVersions/discussions/432

Originally posted by RinOrz September  6, 2021
I created a project myself to create the corresponding mapping symbols by defining or searching for remote dependencies. I think this feature will be great if it is combined with refreshVersions.
Currently, refreshVersions often needs to manually built more dependencies to follow updates, which will be very troublesome in some cases, for example:

If some groups have added new components (AndroidX).
If I need to import some other dependencies (maybe some of my local dependencies).

At this time, I need to import dependencies through by string notations, apparently destroying the elegance of dependency management.
So I have currently have the following solution:

Configuration：
dependencyMapper {
  libraries(rootClass = "Libs") {
    // Follow the internal mapping path conversion
    map("com.diffplug.spotless:spotless-plugin-gradle")
    // Full specify mapping path
    map(
      "com.tfowl.ktor:ktor-jsoup" to "Ktor.Jsoup",
      "com.github.ben-manes.caffeine:caffeine" to "Caffeine",
    )

    remote {
      defaultRepositories {
        mavenCentral()
      }
      groups(
        "org.apache.tika",
        "io.ktor",
      )
      startsWith(
        "commons-io",
        "org.jetbrains.kotlin",
        "org.jetbrains.kotlinx",
      )
      // Specifies to search in google maven for dependencies starting with 'androidx'
      startsWith(
        "androidx",
        "com.android"
      ).filter {
        // Skip deprecated dependencies
        it.startsWith("com.android.support").not()
      } from google()
    }

    // Convert the generated name node
    transformName {
      when (it) {
        "Io" -> "IO"
        "ios", "IOS" -> "iOS"
        else it
      }
    }

    transformPath {
      it.replace("org.jetbrains.kotlin", "kotlin")
        .replace("org.jetbrains.intellij", "intellij")
        .removePrefix("com.")
        .removePrefix("net.")
      ...
    }
  }
  plugins(rootClass = "Plugins") {
    map("io.gitlab.arturbosch.detekt" to "Detekt")
  }
  // Even the mapping projects to dependencies, like Projects.Sample.Android, but I am not sure if this should be more creating a new project instead of bringing into `refreshVersions` (because the name seems to limit only version of something)
}

Pseudo code generated with bytebuddy:
class Libs {
    object Caffeine : DependencyNotation("com.github.ben-manes.caffeine:caffeine")
    class Ktor {
        object Jsoup : DependencyNotation("com.tfowl.ktor:ktor-jsoup")
        class Client {
            object Core : DependencyNotation("io.ktor:ktor-client-core") {
               object Jvm....
            }
        }
    }
    class Apache {
        class Tika {
            object Core : DependencyNotation("org.apache.tika:tika-core")
        }
    }
  ...
}

class Plugins {
    object Detekt: org.gradle.plugin.use.PluginDependency(pluginId = "io.gitlab.arturbosch.detekt", version = "_")
}

Use:
buildscript {
    dependencies.classpath("deps-mapping.jar")
}

plugins {
    id(Plugins.Detekt) apply false
}

implementation(Libs.Apache.Tika.Core)

The draft code should be very easy to understand...🙂
Bringing it to refreshVersions should have a good effect for dependency management, this will no longer need to have any pre-written dependencies, users can define their any dependencies and maintain remote up-to-date!

Bonjour @chachako
I appreciate your efforts writing this nice issue.
I also want to be honest, we have lots to do and limited time and energy.
Realistically you should upate your script to generate a Gradle Versions Catalog instead
We just added support for it.
See https://github.com/jmfayard/refreshVersions/wiki/RefreshVersions-♥-Gradle-Version-Catalog


Add useDeepCompareMemoize hook for memoizing artifact in ArtifactVisu…

closes: https://issues.redhat.com/browse/RHOAIENG-11432

Description

prevents s3 endpoint from polling during running of a pipeline
How Has This Been Tested?

create a new run with markdown or html artifacts
open the markdown artifact
once it succeeds (has a uri)
it should not keep polling (check network tab)
Test Impact

none
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/approve


add responsive winget installs

Merry Christmas @ChrisTitusTech and @Carterpersall I found a way to have the GUI remain responsive and install winget in a separate process. Let me know what you think, only downside is you loose the popup at the end but gain the ability to close the GUI if you desire.

Oh this looks absolutely amazing. Thanks man!


WIP - Hist colors

This will fix the two first tasks on https://github.com/bloomberg/bqplot/issues/995

Something wrong with the signoff thing, I'll create another branch


Changes to Console and Emulator files

When you make a change to these files do.you have to re-run ice.exe each time or is saving the file all that is needed?

I think if you want to apply those changes you've made to the text files, you need to run ice.exe again

Thanks. On the flip side what if you want to clear our all of emulators and roms from steam how would you do that?


Fix missing text

Hi @yanisurbis I just merged your PR. Thank you very much for your contribution.


How to connect Robomongo

Hi,
thanks a lot for your script, it have successfully installed mongodb!
Now i'm trying to connect it with Robomongo.
I have made forward port on 27017 and 3000.
But, i'm not able to connect (i tried: <IP_ADDRESS>, <IP_ADDRESS>, localhost)... but nothing.
do you know how to solve this ?

I'm using SSH tunnel and it works without using port forwarding. I guess you can connect to MongoDB without authentication by default, but I like to set up auth anyway. To do that, connect to your mongo DB server:
mongo --port 27017
Then, select the admin database and insert new user:
use admin
db.createUser(
  {
    user: "admin",
    pwd: "admin",
    roles: [ { role: "userAdminAnyDatabase", db: "admin" } ]
  }
)

Now, open up Robomongo and make new connection, name ti whatever you want and set hostname to localhost and port to 27017. Now switch to Authentication tab and set up auth database to admin, user name and password admin (or whatever you set in previous step) and auth mechanism to SCRAM-SHA-1. Switch to SSH tab and check Use SSH tunnel. SSH address <IP_ADDRESS> (your homestead IP address), user name vagrant and use password or private key (I prefer private key). If using private key set path to /Users/USERNAME/.ssh/id_rsa (this is path for OS X) and your passphrase. Save settings and voila - it works!

Thanks @avramovic for the solution, if this helps @mistre83 i am closing this issue

@zakhttp This works. I think you should close the issue.


[layers] flatten layer consider target_shape

This patch makes a flatten layer consider target_shape and use it during exporting.
FYI, flatten layer exports to Reshape operator in tflite. That is why the flatten layer needs to know about target shape.
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Related: #1879
Signed-off-by: seongwoo<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1903. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


[BEAM-11781]: Update kafka-clients version in samza-runner

Update kafka-clients version in samza-runner.

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @xinyuiscool


docs(rss): add RSS links to release notes pages

Add RSS to social section in footer
Add RSS to each release notes page (not Halyard)
Resolves Jira: DOC-524

I added Agent plugin, Agent service, Operator, and AE RSS to my local RSS app - all feeds look correct

LGTM. When I click the RSS icons, I get dropped on what looks like valid XML. I didn't test with an actual RSS reader though. Not sure if you have @aimeeu , but I don't have one installed and don't even actually know of one after Google killed theirs :(

I have Reeder installed, linked to my ancient Inoreader account lol


All the test suites that need to pass

Very important

[ ] d3
[ ] forever
[ ] winston
[ ] nconf
[ ] director
[ ] cradle

Important

[ ] godot
[ ] prompt
[ ] quill-{cli,composer,tar,template}
[ ] forever-monitor
[ ] api-easy
[ ] cli-easy
[ ] errs

Nice to have

[ ] asana-api
[ ] http-agent
[ ] nssocket
[ ] portfinder
[ ] procfile
[ ] revalidator
[ ] roadmap
[ ] system.json
[ ] window-stream

I don't know if we're going to try to support all of these or not with 1.x. At least we should document what breaks.


Add support for Markdown Checkboxes

Currently this seems to convert Google Docs checkmarks into numbered bullets instead of markdown checkboxes. Would be great if it converted them properly!

I came here just to say this! And turns out @DarwinJS beat me to the punch.


Adding a LocalDataset Class to be able to use internal dataset

Goal is to be able to use any type of csv files as dataset input. This is required for OCHEM integration cause OCHEM generate local csv files for tasks.

So that you could use it as in the test_local.py in the PR


adding stale bot

adding stale bot integration

Codecov Report

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

@@           Coverage Diff           @@
##           master     #168   +/-   ##
=======================================
  Coverage   48.27%   48.27%
=======================================
  Files           1        1
  Lines          29       29
  Branches        5        5
=======================================
  Hits           14       14
  Misses         11       11
  Partials        4        4

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 afdda92...c09c5ec. Read the comment docs.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Enhancement to support oc login with apikey

Right now, the tool only support oc login with credential using user/password or token. It is very common to use apikey to login OCP cluster especially for ROKS clusters.
The enhancement request is to include the following oc login option while running IO perf testing on the cluster.
oc login -u apikey -p {ocp_apikey} --server={ocp_url}

Sure, will do. Thanks.

This enhancement has been implemented and delivered. Please follow the README to try it.
If you find any issue, reopen this git issue. Thanks.


Automated cherry pick of #8896: fix: oidc data may be encapuslated in data field

Cherry pick of #8896 on release/3.5.
#8896: fix: oidc data may be encapuslated in data field

Codecov Report

Merging #8897 (15f58ab) into release/3.5 (e3fe6c4) will decrease coverage by 1.82%.
The diff coverage is 0.33%.

@@              Coverage Diff               @@
##           release/3.5   #8897      +/-   ##
==============================================
- Coverage         6.03%   4.20%   -1.83%
==============================================
  Files              795     163     -632
  Lines           124282   24871   -99411
==============================================
- Hits              7503    1047    -6456
+ Misses          116114   23732   -92382
+ Partials           665      92     -573

Flag
Coverage Δ

aFlag
4.20% <0.33%> (-1.83%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/cloudcommon/db/domainresource.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/modelbase.go
4.51% <0.00%> (-0.08%)
:arrow_down:

pkg/cloudcommon/db/namevalidator.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/orderby.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/virtualresource.go
0.00% <0.00%> (ø)

pkg/cloudprovider/cloudprovider.go
0.71% <0.00%> (-0.04%)
:arrow_down:

pkg/cloudprovider/objectstore.go
2.57% <ø> (ø)

pkg/cloudprovider/securitygroup.go
0.00% <ø> (ø)

pkg/compute/regiondrivers/aliyun.go
0.34% <0.00%> (+<0.01%)
:arrow_up:

pkg/compute/regiondrivers/base.go
1.02% <0.00%> (-0.05%)
:arrow_down:

... and 558 more

Continue to review full report at Codecov.

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


Blacklisted cmake 3.18.2 because macos build failed

See commit abff69f.
Don't use cmake 3.18.2 when building wheel
Our macos build has been failing since 2020-08-21:
+ pip wheel . -w /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/cibuildwheelvcmdx5mi/built_wheel --no-deps
Processing /Users/runner/work/wildbook-ia/wildbook-ia
  Installing build dependencies: started
  Installing build dependencies: finished with status 'error'
  ERROR: Command errored out with exit status 1:
   command: /private/tmp/cibw_bin/python /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pip install --ignore-installed --no-user --prefix /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-build-env-srqflxar/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'setuptools>=42' wheel 'setuptools_scm[toml]>=3.4' scikit-build cmake ninja
       cwd: None
  Complete output (23 lines):
  Collecting setuptools>=42
    Downloading setuptools-49.6.0-py3-none-any.whl (803 kB)
  Collecting wheel
    Downloading wheel-0.35.1-py2.py3-none-any.whl (33 kB)
  Collecting setuptools_scm[toml]>=3.4
    Downloading setuptools_scm-4.1.2-py2.py3-none-any.whl (27 kB)
  Collecting scikit-build
    Downloading scikit_build-0.11.1-py2.py3-none-any.whl (72 kB)
  Collecting cmake
    Downloading cmake-3.18.2.tar.gz (28 kB)
      ERROR: Command errored out with exit status 1:
       command: /private/tmp/cibw_bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-iy6chcw0/cmake/setup.py'"'"'; __file__='"'"'/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-iy6chcw0/cmake/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-pip-egg-info-4z_omqj3
           cwd: /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-iy6chcw0/cmake/
      Complete output (5 lines):
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
        File "/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-iy6chcw0/cmake/setup.py", line 7, in <module>
          from skbuild import setup
      ModuleNotFoundError: No module named 'skbuild'
      ----------------------------------------

cmake 3.18.2 was released on 2020-08-21 and that appears to break the macos
build.
We might need to look into this so raising an issue.

This is also fixed for macOS in https://github.com/WildbookOrg/wildbook-ia/runs/1127343938?check_suite_focus=true


[Dependency: Guides] - Create "Migrating" section and move content from Guides

Dependency for #1859
Goal: As a user I would like to be able to easily find (starting from the homepage), how to upgrade to the latest version of webpack.

[ ] Create a new Section called "Migrate", it's creation should be at the same tier as "Guides"

[ ] The url to access this page should be webpack.js.org/migrate

[ ] Move existing Migrating (v1 => v2/3) Guide and place it inside of new Migrating section under

[ ] This page's url should be webpack.js.org/migrate/3

How about we add a link "Migration" section in the home page in this "It's that simple" section? Or probably something similar? Please let me know your thoughts on this. @TheLarkInn 😅

We can link to it from that page certainly, but this is just scoped to creating the section itself, and moving the existing guide to the new section location, and then with the PR that @sokra lands with #1939, then we can move that also into this section.

@montogeek can you assign this on me, will implement over this weekend

@TheLarkInn pls see PR open for any additions


Where did the dist folder go?

Context
I updated the action from @v1 to @v1.3.0 and got the following error message:
Error: File not found: '/home/runner/_work/_actions/tale/kubectl-action/v1.3.0/dist/index.js'

I observed in the main branch that the dist folder isn't mapped anymore, but is referred in the action.yaml file (dist/index.js)
How to reproduce the error
I was using the action like this and just updated it to use node 20 and remove Github Actions WARNING messages.
      - name: kubectl config
        uses<EMAIL_ADDRESS>        with:
          base64-kube-config: ${{ steps.kubeconfig.outputs.KUBE_CONFIG_CONTENT }}
          kubectl-version: v${{ inputs.kubernetes-cluster-version }}

Coming back to v1 resolved the issue, but v1.3.0 tag and main branch should be updated.

You know I'm actually not sure, v1 points to the v1.3.0 tag anyways. If you look at both the tags they are identical builds. I made it so that v1 always fast tracks to the latest tag.

If you check your tags:
v1.3.0 doesn't have the dist diretory.
v1 does have the dist diretory.
Currently, referring to uses<EMAIL_ADDRESS>returns an error.

Huh okay let me fix this.


Feature/1029 record fixed param

Submisison Checklist

[x] Run tests: ./runCmdStanTests.py src/test
[x] Declare copyright holder and open-source license: see below

Summary:
In command.hpp, before invoking service method fixed_param, add line "# fixed_param=1" to Stan CSV header.
Intended Effect:
This will make it easier for wrapper interfaces to check Stan CSV files.  see https://github.com/stan-dev/cmdstan/issues/1029
How to Verify:
Added more unit tests
Side Effects:
CSV header files will change only when method fixed_param is invoked.  Should be harmless.
Documentation:
n/a
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

I couldn't agree more.  I looked at the classes in src/cmdstan/argument - the code is a bit opaque.
are these object mutable?  not sure how to change the algorithm argument - just create a new one?

OK, will look into messing with valid_arguments.   since we've got a fix for this in CmdStanPy, not a huge priority.  just another example of why we really need to change the way that CmdStan handles command line argments and config.

The problem here isn't with the CmdStan argument parser but rather with that recently introduce feature of trying to modify the CmdStan configuration based on the given Stan program.
The entire CmdStan ecosystem was designed around the arguments being immutable.  A user specifies the configuration and CmdStan executes exactly that configuration no matter the structure of the Stan program.  The behavior of CmdStan is then entirely determined how it is called without the need to consult the associated Stan program, which is critical to reproducible analysis pipelines where different Stan programs are switched in and out.  In other words the immutability of the configuration ensures no surprises in what is executed.
Modifying the configuration based on the structure of the Stan program breaks this guarantee.  Instead of returning an error that immediately communicates a conflict between the requested configuration and the given Stan program the assumption of a misspecified configuration propagates through the entire analysis pipeline.  If that assumption is incorrect then it would not be observed until later on in the pipeline complicating debugging.
The reason why the argument parser does not have readily-accessible mutators is that it was designed for this immutability paradigm.  By breaking the immutability you've gone beyond the intended use of the code.  That said while mutators are not implemented the modification of the parsed argument is straightforward given that the argument parsing is implemented recursively.
// Grab the algorithm argument node from the argument tree and
// cast it to a `list_argument` to ensure that the proper methods are called
list_argument* algo = dynamic_cast<list_argument*>(
        parser.arg("method")->arg("sample")->arg("algorithm"));

// Create a vector of strings with the new algorithm arguments
std::vector<std::string> modified_algo_args;
modified_algo_args.push_back(“fixed_param”);

// Update the algorithm node to use the new arguments
algo.parse_args(modified_algo_args, info, err, false);

Again I don't actually think that this fix should be implemented but rather the automatic modification reverted.

I agree with @betanalpha that it seems confusing to change what users requested to something else because what they requested is incoherent.
How about just generalizing the HMC algorithms to allow zero-size parameter vectors?  If you look at the leapfrog algorithm with size zero vectors, the boundary condition is a no-op, which is just what we want.  Then users can choose any of our HMC algorithms when there is zero-size parameters and the boundary condition should do the right thing.  Then we don't need to modify any of our output.

The reason why I introduced a separate “fixed_param” sampler configuration is that while the Hamiltonian trajectories themselves are fine the local (trajectory length) and global (stepsize, inverse metric) adaptation are not.  Instead of trying to adapt each of those routines it was easier to have a separate, explicit option for the user to communicate when they don’t want to modify the parameter space at all.

On Sep 21, 2021, at 12:43 PM, Bob Carpenter @.***> wrote:
I agree with @betanalpha https://github.com/betanalpha that it seems confusing to change what users requested to something else because what they requested is incoherent.
How about just generalizing the HMC algorithms to allow zero-size parameter vectors? If you look at the leapfrog algorithm with size zero vectors, the boundary condition is a no-op, which is just what we want. Then users can choose any of our HMC algorithms when there is zero-size parameters and the boundary condition should do the right thing. Then we don't need to modify any of our output.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/stan-dev/cmdstan/pull/1030#issuecomment-924164895, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALU3FSZMSID6ELYLAGG2NTUDCY3ZANCNFSM5BXW4HEQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

it seems confusing to change what users requested to something else because what they requested is incoherent.

the user's request was vague, but then defaults were applied and the result is incoherent.  it's a problem with the defaults, not the user.  all the user wants is to run the program to generate a sample.

That's a really good point. If a user only specifies "sample", then I don't see the problem with choosing fixed_param or adaptive, diagonal, Euclidean NUTS for them depending on whether the model has 0 or 1+ parameters.

This is a misinterpretation of what “sample” means.
All of the method arguments refer how the parameter space is handled.  method=sample refers to sampling from the parameters defined in a Stan program and nowhere else.
The fixed_param algorithm runs a trivial Markov chain that leaves the initial parameter values unperturbed.  A consequence of this is that running with the fixed_param algorithm just executes the transformed parameters and generated quantities block on the initial parameters over and over again, regardless of the configuration of the parameter space or the code in those blocks.  If the generated quantities block happens to have RNG evaluations then this might look like a sampling operation but that’s irrelevant to why method=sample and algorithm=fixed_param were chosen.  And if the generated quantities block doesn’t have any RNG evaluations then nothing looks like sampling at all despite method=sample and algorithm=fixed_param still being meaningful.
More detailed warning messages to users clarifying this behavior is awesome.  Adding a new method that more directly runs generated quantities without pretending to run a Markov chain, with the additional benefit of being able to craft proper arguments, is also awesome.  Trying to change the behavior of method=sample based on overlapping terminology that might arise in some Stan programs is, in my opinion, much more confusing and much less awesome.

This is a misinterpretation of what “sample” means.

I agree that fixed-param doesn't do MCMC sampling, but it's main utility is for MC sampling using the _rng functions.  Not to go all Humpty-Dumpty here, but we can define the keyword "sample" in an interface to mean whatever we want it to mean as long as it's consistent with standard meanings of the word.
I can see two reasons to run fixed-param.

to MC sample using pseudo-RNGS, or
to evaluate a Stan function or test a data/transformed data block.

(2) feels like it should be done another way.  Are there other reasons people run fixed_param?
What I tend to do in practice is just call the defaults.  Then if I have zero size parameters, I have to fumble in the doc to figure out how to call a different function.  And if I ever want to use a single program for both, I have to write a conditional into the interface scripts.  But I agree that it's awkward to be able to supply HMC parameters if HMC isn't being run.  If we enforce that consistency by throwing errors whenever we call fixed_param with HMC parameters, I'd still have to write conditionals into the interface scripts.

I agree that fixed-param doesn't do MCMC sampling, but it's main utility is for MC sampling using the _rng functions. Not to go all Humpty-Dumpty here, but we can define the keyword "sample" in an interface to mean whatever we want it to mean as long as it's consistent with standard meanings of the word.

Sure, but we don’t want define it in ways that clash with what is actually being done or even possible.
For example there’s no general way to turn a Stan program that species a joint density over the parameters and data variables into a “procedurally generative” program that can generate example samples of all of those variables, so there’s no “sample” or “Monte Carlo” method that would ever a valid option for general Stan programs.
fixed_param describes what is done - fixed the parameters but letting everything else be evaluated -- not what one can do with the side effects of that action, such as evaluating the data or transformed data block once or running the generated quantities block over and over again.

I can see two reasons to run fixed-param.
to MC sample using pseudo-RNGS, or
to evaluate a Stan function or test a data/transformed data block.
I think it’s more to think about how a Stan program is actually processed, in other words which blocks are actually evaluated.  fixed_param evaluates everything at the same initial values of the parameters block which then allows for all kinds of useful side effects based on the structure of those blocks.  At the same time because those side effects can’t be guaranteed unless a Stan program has certain structure in certain blocks there’s no way to guarantee them and hence they’re not really appropriate naming targets.
What I tend to do in practice is just call the defaults. Then if I have zero size parameters, I have to fumble in the doc to figure out how to call a different function. And if I ever want to use a single program for both, I have to write a conditional into the interface scripts. But I agree that it's awkward to be able to supply HMC parameters if HMC isn't being run. If we enforce that consistency by throwing errors whenever we call fixed_param with HMC parameters, I'd still have to write conditionals into the interface scripts

I don’t see the problem with having to call the right method based on what you want to do.
method=sample algorithm=hmc will attempt to evolve the parameters with Markov chain Monte Carlo.  That’s it.  If your program does not provide enough information for that to be a well-defined operation then it should err our, which is used to do.
method=sample algorithm=fixed_param uses a trivial Markov chain Monte Carlo algorithm that doesn’t achieve the same behavior as the Hamiltonian Monte Carlo sampler.  There are lots of useful side effects for this, and if you want one of those side effects then you should specify that directly with the call.  You can’t rely on default behavior when there are multiple, distinct actions you want to perform.
Again I think having a full method that repeatedly evaluates the Stan program at the fixed input, and not hiding that in method=sample would be a great way to clarify the intent and possible applications.  But this issue is all about the CmdStan interface automatically switching from algorithm=hmc to algoirthm=fixed_param based on an exceptional circumstance for certain Stan programs.

@betanalpha

The problem here isn't with the CmdStan argument parser but rather with that recently introduce feature of trying to modify the CmdStan configuration based on the given Stan program.

I don't actually think that this fix should be implemented but rather the automatic modification reverted.

@bob-carpenter

How about just generalizing the HMC algorithms to allow zero-size parameter vectors? If you look at the leapfrog algorithm with size zero vectors, the boundary condition is a no-op, which is just what we want. Then users can choose any of our HMC algorithms when there is zero-size parameters and the boundary condition should do the right thing. Then we don't need to modify any of our output.

@betanalpha

while the Hamiltonian trajectories themselves are fine the local (trajectory length) and global (stepsize, inverse metric) adaptation are not.

In theory, HMC works perfectly fine in a zero-dimensional space. It's just arithmetic with size-zero vectors, trivial but well-behaved.
In practice, Stan's HMC algorithm works perfectly fine in a zero-dimensional space but there are two other bugs that interfere.
First, disabling the zero-parameter check in CmdStan and running with defaults result in
Exception initializing step size.
Posterior is improper. Please check your model.

which is obviously false: the posterior is a point mass and necessarily proper. It's just that step size is meaningless and the step size adapter misdiagnoses this.
But precisely because step size is meaningless adaptation shouldn't do anything anyway. Running with adapt engaged=0 warmup completes successfully but the program crashes when it tries to print the metric.
stan/lib/stan_math/lib/eigen_3.3.9/Eigen/src/Core/DenseCoeffsBase.h:425: Eigen::DenseCoeffsBase<type-parameter-0-0, 1>::Scalar &Eigen::DenseCoeffsBase<Eigen::Matrix<double, -1, 1, 0, -1, 1>, 1>::operator()(Eigen::Index) [Derived = Eigen::Matrix<double, -1, 1, 0, -1, 1>, Level = 1]: Assertion `index >= 0 && index < size()' failed.

Ok, one-line fix in stan/mcmc/hmc/hamiltonians/diag_e_point.hpp and with that it runs to completion.

You could generate the same samples a bit more efficiently with fixed_param sampler (which evaluates zero proposals for each iteration) but--and here's the problem this PR is trying to workaround--fixed_param has a different output format from all the other samplers.
Why does fixed_param have different output? As far as I can tell it's because fixed_param has no warmup and thus omits the adaptation info. On one hand that makes sense, "warming up" fixed_param would be just wasted computation; on the other hand fixed_param still supports thinning, which is equally pointless, and CmdStan accepts (but silently ignores) nonzero num_warmup argument even with algorithm=fixed_param.
In short, it's all inconsistent.

If we’re being formal then a zero-dimensional space is topologically discrete and cannot be written as a dense subset of the real numbers.
Right. R^0 has just a single element, the empty tuple and any measure has to assign it 100% of the probability mass. But it's still a proper measure and I can't see where the rest of the math won't generalize properly if we get our code right.
This also just feels like a bug in our code not handling N = 0 boundary conditions.
But isn't this moot for the issue at hand, which is just to let the sampling method deal with size zero output by allowing the flexibility to select between HMC or fixed-param depending on the problem dimensionality?

Again: a zero-dimensional space does not imply a single element set!  There are many zero-dimensional spaces and hence many different ways to extrapolate to the N = 0 boundary case of R^N.  These include the empty set, a set with a single element, and a set with a finite number of elements.
Each of these zero-dimensional spaces imply different Markov chain Monte Carlo algorithms and output configurations.  For example the empty set would correspond to no-ops everywhere with no parameter values passed to the MCMC output.  A single element set would also correspond to no-op but the value of that one element would technically get passed to the MCMC output.  A no-op sampler would definitely not be okay for a discrete set.
The zero-dimensional case is ambiguous and there is not an obvious or canonical implementation of Markov chain Monte Carlo.  We can choose one arbitrarily or we can just not define HMC for this ambiguous setting, instead erring out with an informative message as was done previously.  I strongly prefer the latter.  If a user wants a no-op sampler then they should specify a no-op sampler.

When the output Stan configuration specifies that HMC was run but the output doesn’t contain the assumed HMC output then there are problems.
That feels like a bug to me in the brittle way we pack things into and read things out of .csv format.

It’s not bug in that it’s technically working as intended.  Every well-defined HMC output has a guaranteed structure and the reader assumes that structure.
I agree that the CmdStan csv reader is brittle and should be updated or redesigned, but I don’t think this is the reason why.

There are many zero-dimensional spaces and hence many different ways to extrapolate to the N = 0 boundary case of R^N.

There are indeed many zero dimensional spaces (although, no, the empty set is not one of them) but R^N does not mean some random N-dimensional space. R^N means the N-dimensional real vector space. That is unique for every N; zero is not special.
The issue isn't about generalizing HMC to arbitrary zero dimensional spaces. The only space of interest is the one Stan chooses when a model has no parameters at all. And that particular space is quite well-behaved.

There are indeed many zero dimensional spaces (although, no, the empty set is not one of them) but R^N does not mean some random N-dimensional space. R^N means the N-dimensional real vector space. That is unique for every N; zero is not special.

By empty set I was referring to the model theoretic use of the empty set itself as the canonical element of a set with cardinality one, but that’s irrelevant.
R^N does not uniquely define an N-dimensional real vector space.  In order to identify R^N with a Euclidean vector space one has to fix a parameterization/coordinate-system; in particular non-linear transformations/reparameterizations/changes or coordinate systems change the identification of R^N with the Euclidean vector space.  One can interpret this as an infinite number of different R^N, each identified with a canonical Euclidean vector space, or a single R^N that requires a choice of parameterization before it can be identified with a Euclidean vector space, but either way R^N doesn’t refer to unique, full-specified system.
The identification ambiguity carries over to the zero-dimensional case as well.  For example let’s say that we define a vector space containing only the zero vector as a zero-dimensional space.  There are an infinite number of ways to associate the zero vector with a single point, each corresponding to a different choice of origin in R^1 with the different choices related by translations.
Taking any choice arbitrarily yields has a non-empty state space, which formally means that we need a name for a variable that takes values in the state space so that we can print the constant output.  This does not correspond to the no-op, no-output behavior of the fixed_param sampler.

no longer relevant.


Add more information to cli output

why
Kubernetes APIs supports a Table format to be requested when retrieving resources using oc or kubectl. This is triggered by the CLI setting the header Accept: application/json;as=Table;v=v1beta1;g=meta.k8s.io, application/json
The API servers then respond with both a schema for the table and the data within it.
See https://kubernetes.io/docs/reference/using-api/api-concepts/#receiving-resources-as-tables for more information
Proposal
Add support for the Table format in the API server so that cli can provide better information about addressspaces, addresses and messagingusers.
Testing
What is the test plan for the feature/change?
Documentation
Examples must be updated with the actual output.
Tasklist

[ ] Decide on what columns to display
[ ] Add support for parsing Accept header and detect requested table format
[ ] Add types and responses for Table type.

I think being able to easily see the status of address and addressspans from the command line would be valuable.   For addresses that are queue like, being able to see a recent queue depth would be really useful too.
Would there be benefit to expose connections too?
Would we want to

I think we should not expose information there that are not persisted in the configmap. Also it doesn't feel right to have the api server query brokers for stats. Lastly something like queue depths would need to be updated regularly, requiring a lot of writing to the configmap compared to today where we only write it in rare cases. I think metrics etc. maybe long elsewhere.

@k-wall A couple of ideas that came up discussing this with @rgodfrey and @robshelly :
a) provide a command line tool to manage all of enmasse from an ops side (enmassectl :))
b) provide a read-only addressstatus resource that can be queried for stats of an address and that will cause api-server to query broker, router etc. for information
We should also consider service admin vs. tenant here... I think an enmassectl would be useful for an admin to manage an EnMasse instance, whereas oc get addressstatus is perhaps mostly interesting for a messaging tenant.
I think alternative 'a' has a lot of potential to be used for installing, upgrading etc. as well and as a way to inspect routers, brokers etc. in more detail. This is also a well-established approach used by the Istio project for instance.
Alternative 'b' will meet the requirements of getting more stats about addresses without requiring to write stats to the configmap and is perhaps a more realistic short-term task.


Add vision purpose to files

OpenAI has added the possibility to create a message with an image attached to the content: https://platform.openai.com/docs/assistants/how-it-works/creating-image-input-content
You can now upload a file with a vision purpose set. This PR adds the “vision” purpose to enable that functionality.
All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Thanks, @willywg !

Released in v7.1

How do you use this, is there an example where the image is uploaded and a question is asked?  Sorry not able to figure out from the API.
Thanks


Publish clarification questions and answers on briefs

#112340959
Depends on https://github.com/alphagov/digitalmarketplace-apiclient/pull/15
This allows clarification questions and answers to be published on a live brief.
I've done validation on the model rather than with a JSON schema as we are not using a JSON data column.

:+1: :+1: :+1:


Minecraft deployment template has incorrect case for FORCE_GAMEMODE

Is this a request for help?:
No

Bug Report
Version of Helm and Kubernetes:
N/A
Which chart:
stable/minecraft
What happened:
Setting values.yaml variable forcegameMode: true has no effect, because the case in the template file is different to the variable in the Docker image
What you expected to happen:
File server.properties to be updated to match values.yaml
How to reproduce it (as minimally and precisely as possible):
helm install stable/minecraft --set forcegameMode=true
Anything else we need to know:
PR incoming shortly

.

What is the point of this repository, exactly?