[BUG]debugger. pops up when i change profiles in Evlui , thought I already mention this in here . sry if this is double !

🔵 Describe the bug:
A clear and concise description of what the bug is.
🔵 To reproduce: (Steps to reproduce the behavior)

Go to '...'
Click on '....'
Scroll down to '....'
See error

🔵 The error:
Paste the error message in this blockquote.

🔵 Screenshots:
If applicable, add screenshots to help explain your problem.
🔵 Expected behavior:
A clear and concise description of what you expected to happen.
🔵 GSE.lua file:
Please provide your GSE.lua file or the export string for the specific macro that is causing an issue.

To find the GSE.lua file:

First, make sure you have enabled the "File Name Extensions" checkbox in Explorer (View tab)
Browse to C:\path\to\wow\_retail_\WTF\Account\YourAccountName\SavedVariables\ or /path/to/WoW/_retail_/WTF/Account/YourAccountName/SavedVariables
Copy the GSE.lua file to your Desktop
Rename this copy to GSA.lua.txt
Then just drag it here in your message

Note: If you do not include your GSE.lua file you are wasting your time and mine. 90% of the time, the first thing I will ask for is "Can you please upload your GSE.lua file?".  This file is needed with the error to work out Why that error occured for you.

🔵 Desktop (please complete the following information):

OS: [e.g. Windows 10 64bit]
Game Version [e.g. classic/bcc/retail (9.1.0)]

🔵 GSE Version:

Version: [e.g. 3.x.y]
Downloaded From: [e.g. https://www.curseforge.com]

🔵 Additional context:
Add any other context about the problem here.

ANd i already closed it.  Its an Elv bug that only affects your config not a GSE bug

Duplicate of #1082

ok cant see where it was closed, ty

https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/issues?q=is%3Aissue+is%3Aclosed
TimothyLuke

On 16 Dec 2021, at 11:24 pm, Timf63 @.***> wrote:

ok cant see where it was closed, ty
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Add time range event exports.

Ready for review.
Depends on praekelt/vumi#1017.

I added some help text for the new events option. :+1: once vumi#1017 lands and travis is happy.

:+1: on the help text!


Exclude studies from clustering step in V2D pipeline

Email from Daniel Seaton suggests GCST005922 should not have clustering step applied to it. We should maybe have a list of studies to exclude from the clustering step.

@DSuveges please consider this when reviewing V2D. Please close if appropiate

I think this is not an issue anymore as we are changing the clustering logic, so it is no longer distance based but LD based. The cited study is quite interesting: out of the 220 associations 138 are on chromosome 19 in a very narrow region.


PAWN/SourcePawn misclassified as Pascal

PAWN/SourcePawn misclassified as Pascal (but a very small part, about 0.1%)
https://github.com/NexiusTailer/Nex-AC

Linguist detection fails on this file because it's a UTF-16 encoded:
$ bundle exec linguist ../Nex-AC/lang/nex-ac_pt_br.inc
/linguist/lib/linguist/blob_helper.rb:281:in `split': invalid byte sequence in UTF-8 (ArgumentError)
	from /linguist/lib/linguist/blob_helper.rb:281:in `lines'
	from /linguist/lib/linguist/blob_helper.rb:298:in `loc'
	from /linguist/bin/linguist:49:in `<top (required)>'
	from /.rvm/gems/ruby-2.3.0/bin/linguist:23:in `load'
	from /.rvm/gems/ruby-2.3.0/bin/linguist:23:in `<main>'
	from /.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval'
	from /.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `<main>'

This seems related to #353.

Closing in favor of #353.


typo(function)add sidebar for split_by_string function and delete split_by_char builtins code

…iltins code
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[x] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.96 seconds
load time: 471 seconds
storage size:<PHONE_NUMBER>6 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230106093443_clickbench_pr_74793.html


Failed to parse search result json

Matcher fails since recent solr upgrade
2024/02/22 07:18:57 WARN: "KAFKA_NUM_PARTITIONS" env var is not set. Using default value 8
2024/02/22 07:18:57 INFO: Using value 3 as defined in KAFKA_REPLICATION_FACTOR env var
2024/02/22 07:18:57 INFO: Using value 168 as defined in KAFKA_RETENTION_HOURS env var
2024/02/22 07:18:58 INFO: topic "kashtanka_calvin_zhirui_embeddings_output" creation reault: kashtanka_calvin_zhirui_embeddings_output (Topic 'kashtanka_calvin_zhirui_embeddings_output' already exists.)
2024/02/22 07:18:58 WARN: "KAFKA_NUM_PARTITIONS" env var is not set. Using default value 8
2024/02/22 07:18:58 INFO: Using value 3 as defined in KAFKA_REPLICATION_FACTOR env var
2024/02/22 07:18:58 INFO: Using value 168 as defined in KAFKA_RETENTION_HOURS env var
2024/02/22 07:18:58 INFO: topic "kashtanka_card_matches" creation reault: kashtanka_card_matches (Topic 'kashtanka_card_matches' already exists.)
2024/02/22 07:18:58 Initialization complete. Starting main loop
2024/02/22 07:18:58 Waiting for the next job...
2024/02/22 07:18:58 Got job key pet911ru_rl796922 (partition kashtanka_calvin_zhirui_embeddings_output[2]@16609; 2024-02-17 20:25:16.745 +0000 UTC)
2024/02/22 07:18:58 Job pet911ru_rl796922 has 1 embeddings
2024/02/22 07:18:58 Qeuring for similarities...
2024/02/22 07:19:02 Got similarity serach result: 200
2024/02/22 07:19:02 Failed to parse search result json: json: cannot unmarshal number into Go struct field SimilarImageDocsJson.response.docs.calvin_zhirui_embedding of type string;

failed_input_pet911ru_rl796922 .json

solr_image_serch_response.json


Open settings in a new tab like the old version

Now that the horizontal tab view starts from the starting, it makes sense to open settings in a new tab rather than occupying the entire window.

@Jaiganeshkumaran There is still an option to hide the tab strip, it would be better to keep the behavior how it is to keep things consistent.


sidebar spacing

The sidebar spacing is too compact, especially when items happen to wrap across lines.

Compare to the "cosmo" presentation:

There is not as much of a contrast on the TOC right-hand-side navigation:

With "cosmo":

The TOC navigation has a sufficient amount of separation between items and does not feel especially compact when entries happen to wrap.

This was a similar issue that I had filed: https://github.com/quarto-dev/quarto-cli/issues/5640
I'm not sure what is the responsibility of the theme versus Quarto itself.

There is not as much of a contrast on the TOC right-hand-side navigation:
Yeah - that is the posit blue color which doesn't quite pop as much (this was a requirement).

I have been messing around with some of this in the dark theme PR that I have to increase the font weight so there is more constrast in the TOC for light theme as well (it wasn't passing accessibility standards in dark mode): https://github.com/posit-dev/product-doc-theme/tree/dark-theme-blue-option

@aronatkins
The spacing for the two is identical (including the margins):

I think that Cosmo uses Source Sans Pro and we are using Open Sans. So there will be a lot of slight differences based on that alone.
We could increase spacing a bit if you think that will help but they are current set to the same.
Let me know what you think

If we change the letter spacing to match what the body font is, I think that improves it a bit?


add vk write for shared_ptr

Description
Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[ ] There are no circuit changes, OR a cryptographer has been assigned for review.
[ ] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[ ] The branch has been rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.
[ ] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[ ] If existing code has been modified, such documentation has been added or updated.

Why this and not just dereference the smart pointer with write(*vk)

Or if we think that's too much indecision when writing I'd rather just declare a generic shared ptr write with all the other containers


Tricaster Module no longer connecting to Tricaster after Tricater Update

Here some screenshots of the issue at hand this was working until I updated the Tricaster.  Now it just timesout and doesn't stay connected.

Which version of the Tricaster software are you using?
Are there any errors in the companion log?

TC1
Build Number: 8-1-230825C
Just updated a few days ago.
23.08.31 22:27:17 Instance/Wrapper/tricaster: Unable to connect to Tricaster. Check your device address in the module settings
23.08.31 22:27:22 Instance/Wrapper/tricaster: Unable to connect to Tricaster. Check your device address in the module settings
23.08.31 22:28:29 Instance/Wrapper/tricaster: Unable to connect to Tricaster. Check your device address in the module settings
The IP Address has not changed on the Tricaster after the update just will no longer connect.

I don't see anything obvious listed in the release notes.
I'll have to upgrade and test at some point, but don't currently have a unit running that build

Any update on this?

@kaleforge I'll try to get to it soon, but since I only have one Tricaster and it's been in production use I need to find a decent downtime to upgrade and test.

@nixaathletics @kaleforge I think if you download the latest companion beta this should be fixed. I updated my Tricaster, and it seems they changed some of the XML structure which was causing it to error.
Let me know if this doesn't fix it!

Just did it! Thank you
On Sat, Sep 16, 2023 at 3:47 PM bryce @.***> wrote:

@nixaathletics https://github.com/nixaathletics @kaleforge
https://github.com/kaleforge I think if you download the latest
companion beta this should be fixed. I updated my Tricaster, and it seems
they changed some of the XML structure which was causing it to error.
Let me know if this doesn't fix it!
—
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-newtek-tricaster/issues/41#issuecomment-1722302674,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANQHQO7R66PH3SZE336BGGDX2X665ANCNFSM6AAAAAA4GT7YII
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

@bryce-seifert I just updated my Tricaster again after rolling it back to the older verison.  It appears to be working! Thanks for the fix.


Fix segmentation fault on pam_getenv failure

pam_sys assume that pam_getenv cannot fail, thus never return NULL.
However when asking for the env vars after the authentication form pam-auth, it is failing and the code is segfaulting.
Changed the code to actually check if the the returned value is the NULL pointer and return Option::None in case.

Hey thanks for the PR!
Would you mind adding the fix to the CHANGELOG.md?

Done

Awesome thank you!


Add basic support for coreclr

There are a few left, but they'll disappear when changing CS for the entire project so don't bother. Thanks for the update :)


Updated ReadMe

Udated readme please tell me if there's anything I should add that I didn't or if I did anything wrong please guide me. Thank you!

Great work @alkatrivedi!

Thank You:)


README: Update releasing with GitHub action

Split the releasing into sections:

Release with local environment
Release with GitHub action

This helps providing more detail informaiton of releasing with "Bump version to release" action on GitHub.
Fixes: https://github.com/endlessm/kolibri-explore-plugin/issues/594

Sure!  Updated as the new commit!


Broken CI, possible dependency issue

I expect

the CI to work smoothly

Instead

tests cannot be run because of a dependency issue

Note

we need to fix up library versions. Maybe we need to  pin tox version too.

Fixed by #221 and #222.


Fix KeyError raised in Module.update.

e.g., load safetensors from black-forest-labs/FLUX.1-Depth-dev-lora.
Traceback (most recent call last):
  File "/Volumes/Develop/MLX/mlx-examples/flux/txt2image.py", line 141, in <module>
    load_adapter(flux, args.adapter, fuse=args.fuse_adapter)
  File "/Volumes/Develop/MLX/mlx-examples/flux/txt2image.py", line 106, in load_adapter
    flux.flow.load_weights(list(weights.items()), strict=False)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 195, in load_weights
    self.update(tree_unflatten(weights))
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 335, in update
    apply(self, parameters)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 323, in apply
    apply(current_value, new_value)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 331, in apply
    current_value.update(new_value)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 335, in update
    apply(self, parameters)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 321, in apply
    current_value.update(new_value)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 335, in update
    apply(self, parameters)
  File "/opt/anaconda3/envs/MLX/lib/python3.12/site-packages/mlx/nn/layers/base.py", line 326, in apply
    current_value = dst[i]
                    ~~~^^^
KeyError: 0

I'm not sure this fix makes sense. This might be an issue in the Flux code.. could you share steps to reproduce it?

I'm not sure this fix makes sense. This might be an issue in the Flux code.. could you share steps to reproduce it?

Can be reproduced in mlx-examples/flux project:
python txt2image.py --model dev --save-raw --steps 20 --n-images 1 \
    --adapter ~/.cache/huggingface/hub/models--black-forest-labs--FLUX.1-Depth-dev-lora/snapshots/3b68ab0a12fc3e2ad8a1bf46f45219721ae8c493/flux1-depth-dev-lora.safetensors \
    --fuse-adapter \
    "Any prompt..."

I found
"final_layer.adaLN_modulation.1.bias": {"dtype":"BF16","shape":[6144],"data_offsets":[12913589248,12913601536]},
"final_layer.adaLN_modulation.1.weight": {"dtype":"BF16","shape":[6144,3072],"data_offsets":[12913601536,12951350272]},

in ~/.cache/huggingface/hub/models--black-forest-labs--FLUX.1-dev/snapshots/0ef5fff789c832c5c7f4e127f94c8b54bbcced44/flux1-dev.safetensors
and
"final_layer.adaLN_modulation.1.lora_A.weight": {"dtype":"BF16","shape":[128,3072],"data_offsets":[690863104,691649536]},
"final_layer.adaLN_modulation.1.lora_B.bias": {"dtype":"BF16","shape":[6144],"data_offsets":[691649536,691661824]},
"final_layer.adaLN_modulation.1.lora_B.weight": {"dtype":"BF16","shape":[6144,128],"data_offsets":[691661824,693234688]},

in ~/.cache/huggingface/hub/models--black-forest-labs--FLUX.1-Depth-dev-lora/snapshots/3b68ab0a12fc3e2ad8a1bf46f45219721ae8c493/flux1-depth-dev-lora.safetensors
When mlx loads the above models, 'mlx.nn.layers.containers.Sequential' will be created for adaLN_modulation, which will result in "KeyError: 0"  exception when "flux.flow.load_weights(lora_weights), strict=False)".

Actually, I don't know if this commit makes sense either, although it works smoothly. Maybe this should be changed to a issue.
Looking forward to your bug fixes!

>>> import mlx.nn
>>> sequential = mlx.nn.Sequential()
>>> print(sequential.items())
dict_items([('layers', [])])

The author of mlx-examples/flux had to use a method named "sanitize" to eliminate the effect of Sequential on the addition of ".layers" to the weights' path:
mlx-examples/flux/flux/model.py
    def sanitize(self, weights):
        new_weights = {}
        for k, w in weights.items():
            if k.endswith(".scale"):
                k = k[:-6] + ".weight"
            for seq in ["img_mlp", "txt_mlp", "adaLN_modulation"]:
                if f".{seq}." in k:
                    k = k.replace(f".{seq}.", f".{seq}.layers.")
                    break
            new_weights[k] = w
        return new_weights


[Bulk] Validation-skype-docs-tableSyntax2

This PR fixes 38 issues for invalid table syntax in Skype-docs repo.

Docs Build status updates of commit 9433793:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/UCWA/groupContacts_ref.md
:warning:Warning

Details

Skype/UCWA/applicationSharer_ref.md
:white_check_mark:Succeeded

Skype/UCWA/applicationSharingRenegotiation_ref.md
:white_check_mark:Succeeded

Skype/UCWA/delegator_ref.md
:white_check_mark:Succeeded

Skype/UCWA/group2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/holdPhoneAudio_ref.md
:white_check_mark:Succeeded

Skype/UCWA/leaders_ref.md
:white_check_mark:Succeeded

Skype/UCWA/me_ref.md
:white_check_mark:Succeeded

Skype/UCWA/mediaRelay_ref.md
:white_check_mark:Succeeded

Skype/UCWA/onlineMeetingDefaultValues_ref.md
:white_check_mark:Succeeded

Skype/UCWA/phone_ref.md
:white_check_mark:Succeeded

Skype/UCWA/phones_ref.md
:white_check_mark:Succeeded

Skype/UCWA/photo_ref.md
:white_check_mark:Succeeded

Skype/UCWA/presenceSubscriptionMembership_ref.md
:white_check_mark:Succeeded

Skype/UCWA/presenceSubscriptions_ref.md
:white_check_mark:Succeeded

Skype/UCWA/resetUnansweredCallSettings_ref.md
:white_check_mark:Succeeded

Skype/UCWA/search2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/simultaneousRingToDelegates_ref.md
:white_check_mark:Succeeded

Skype/UCWA/startAudio2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/startMessaging2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/stopVideo_ref.md
:white_check_mark:Succeeded

Skype/UCWA/subscribeToGroupPresence_ref.md
:white_check_mark:Succeeded

Skype/UCWA/to_ref.md
:white_check_mark:Succeeded

Skype/UCWA/unansweredCallToContact_ref.md
:white_check_mark:Succeeded

Skype/UCWA/unansweredCallToVoicemail_ref.md
:white_check_mark:Succeeded

Skype/UCWA/groupContacts_ref.md

Line 106, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@lindalu-MSFT The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2.
This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see.
Thank you!

Docs Build status updates of commit d8439e6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCWA/applicationSharer_ref.md
:white_check_mark:Succeeded

Skype/UCWA/applicationSharingRenegotiation_ref.md
:white_check_mark:Succeeded

Skype/UCWA/delegator_ref.md
:white_check_mark:Succeeded

Skype/UCWA/group2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/groupContacts_ref.md
:white_check_mark:Succeeded

Skype/UCWA/holdPhoneAudio_ref.md
:white_check_mark:Succeeded

Skype/UCWA/leaders_ref.md
:white_check_mark:Succeeded

Skype/UCWA/me_ref.md
:white_check_mark:Succeeded

Skype/UCWA/mediaRelay_ref.md
:white_check_mark:Succeeded

Skype/UCWA/onlineMeetingDefaultValues_ref.md
:white_check_mark:Succeeded

Skype/UCWA/phone_ref.md
:white_check_mark:Succeeded

Skype/UCWA/phones_ref.md
:white_check_mark:Succeeded

Skype/UCWA/photo_ref.md
:white_check_mark:Succeeded

Skype/UCWA/presenceSubscriptionMembership_ref.md
:white_check_mark:Succeeded

Skype/UCWA/presenceSubscriptions_ref.md
:white_check_mark:Succeeded

Skype/UCWA/resetUnansweredCallSettings_ref.md
:white_check_mark:Succeeded

Skype/UCWA/search2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/simultaneousRingToDelegates_ref.md
:white_check_mark:Succeeded

Skype/UCWA/startAudio2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/startMessaging2_ref.md
:white_check_mark:Succeeded

Skype/UCWA/stopVideo_ref.md
:white_check_mark:Succeeded

Skype/UCWA/subscribeToGroupPresence_ref.md
:white_check_mark:Succeeded

Skype/UCWA/to_ref.md
:white_check_mark:Succeeded

Skype/UCWA/unansweredCallToContact_ref.md
:white_check_mark:Succeeded

Skype/UCWA/unansweredCallToVoicemail_ref.md
:white_check_mark:Succeeded

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel


Adding Employee Hierarchy

Would be great if this could be augmented with one more dimension for Sales Structure containing the employee who made the sale (some sales could also be done online, without employee).
This way, more use cases could be tackled as well that depend on a employee hierarchy.
This dimension could be a hierarchy with:
Employee Id
Employee Name
Employee Region
Employee Country
Employee Position (Vendor, Regional Manager, Country Manager, Global Head of Sales)
Employee Manager Id

There could be tens of tables to add. Why not a generic employees table for HR (not just for sales), why not a BOM (Bill of Material), why not shipments, why not... you name it!
However, this is an open-source project. As such, anyone can create a derivative product and ask for a pull request if the contribution is generic and add value to the community - we will certainly consider it!
It is out of the scope of our investment to add (and maintain!) other tables to this project. At SQLBI, we use the result of the Contoso Data Generator for our demo files, and we add tables to specific data models whenever it is required for specific demos, but adding tables to the generic database is an additional cost of one or two orders of magnitude that we cannot justify for our internal use!


typo: Retrives -> Retrieves

@drewbatgit The PR passed the acceptance checklist. Please evaluate further and approve/complete the PR if appropriate. Thanks! Note: I could not find this name space in the current spreadsheet, please coordinate with Jill


VisualScript: Fix mislabeled logic operators #49412

Fix #49412
Logic operators appeared with a wrong label.

Thanks! And congrats for your first merged Godot contribution :tada:


Indicator to show a setting or an extension is not synced

User can configure extensions and settings to be ignored while syncing. There are also some settings which are ignored by default (like machine settings).
We would need some UI indication representing that these items are not getting synced

Some mock ups from @misolori here:
And when ignore we append a badge, similar to when we disable an extension:

@misolori How does this look for settings. Is it possible to have just an icon due to the real estate constraints in extensions?

We could use just an icon right next to the gear and then have the tooltip show this info.

Should I work on this? Is this icon checked in somewhere or can you send it to me?

@roblourens @misolori I played around a bit and I felt the descriptive label is bit too much to have in the extensions view. There is already space constraints. Hence I would like to have only icon and show the text on hover. (Also same in the extension editor)

My only concern is that this is very subtle and most users might miss this if they don't do this action from the extension gear.
We should also provide for an option to re-sync from the extension list. Maybe under the disable dropdown button?

My only concern is that this is very subtle and most users might miss this if they don't do this action from the extension gear.

Not sure if I understand the point here. What does users might miss when only icon is shown?

We should also provide for an option to re-sync from the extension list. Maybe under the disable dropdown button?

True. I am planning to add gear icon in the extension editor too.

Not sure if I understand the point here. What does users might miss when only icon is shown?

If you ignore an extension from the Settings UI, you likely won't ever noticed the small icon in the extension viewlet, which is why I'm concerned that the icon alone might not be enough.

I see and agree with you. I also think the icon + label are causing UI clutter as extension view is already filled with too much data. If icon is not too expressive, is it possible to get a different icon which is prominent?


Properties for drives

Is your feature request related to a problem? Please describe.
Default file manager has a possibility to show properties a driver. It would be really good, if you added this feature.

Drive properties you could see through right click in its root.

Drive properties you could see through right click in its root.

Got it, but is it possible to add it, when you click on drive in left-side?

It will be added as soon as possible.

for sidebar: #1212


Move SqlStatementClient integration test project

Description
The SqlStatementClient integration test project was placed outside the source folder.
This PR moves it into the source folder.
References

#0000

Codecov Report

Merging #219 (26386de) into main (8fc8680) will not change coverage.
Report is 11 commits behind head on main.
The diff coverage is n/a.

:exclamation: Current head 26386de differs from pull request most recent head 0f28a41. Consider uploading reports for the commit 0f28a41 to get more accurate results

@@           Coverage Diff           @@
##             main     #219   +/-   ##
=======================================
  Coverage   70.24%   70.24%
=======================================
  Files         190      190
  Lines        3475     3475
  Branches      439      439
=======================================
  Hits         2441     2441
  Misses        891      891
  Partials      143      143

Flag
Coverage Δ

databricks
80.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add extras sub-project

Closes #74

Codecov Report

Merging #77 into master will increase coverage by 1.72%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master       #77      +/-   ##
===========================================
+ Coverage   98.27%   100.00%   +1.72%
===========================================
  Files          24        25       +1
  Lines         116       124       +8
===========================================
+ Hits          114       124      +10
+ Misses          2         0       -2

Flag
Coverage Δ

#unittests
100.00% <100.00%> (+1.72%)
:arrow_up:

Impacted Files
Coverage Δ

...s/src/main/scala/io/fmq/pattern/RequestReply.scala
100.00% <100.00%> (ø)

.../src/main/scala/io/fmq/socket/ProducerSocket.scala
100.00% <0.00%> (+11.11%)
:arrow_up:

...re/src/main/scala/io/fmq/socket/reqrep/Reply.scala
100.00% <0.00%> (+33.33%)
:arrow_up:

Continue to review full report at Codecov.

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


Apply modifications on object root

Prerequisites

[x] I have read the Contributing guidelines
[x] I have read the Code of conduct and I agree with it

Description
I can't assign values on object root like I sometimes do in vanilla:
Object.assign({}, { entities: {}, result: [] })

Only for bugs :bug:
Version : 1.0.0
Expected behavior
Be able to assign values on object root
Actual behavior
Throw TypeError: path should not be empty
How to reproduce
See runkit
Only for feature requests :sparkles:
Don't know if it's possible or a good practice, but it would be nice to be able to assign values on object root
Example
const { assign } = require('immutadot')

const current = {}
const next = assign(current, '', { entities: {}, result: [] })
// { entities: {}, result: [] }

To apply operation on root object like yours you can write it like:
const { assign } = require('immutadot')

const current = {}
const next = assign(current, '.', { entities: {}, result: [] })
// { entities: {}, result: [] }

Thanks a lot, I should tried this !

My bad it will create an empty property with { entities: {}, result: [] } in it

We won't implement operations on root object because javascript already provides tools for that. In your example Object.assign({}, { entities: {}, result: [] }) is already immutable.

No problems, thanks for your time !


Storybook: Showing source code examples

Setting up the workflow for showing source code in stories.
https://github.com/user-attachments/assets/43640579-8010-466b-b0d2-f3d3c37de5c0

@coderabbitai full review


Microdata coverage extent

@gcushen @zaazi and others,
I am curious if anyone else has an itch for more extensive microdata coverage in the academic them.
There is currently a microdata ticket #413 for JSON-LD consideration, but google seems to be the only search engine that supports JSON-LD at the moment. #413 discusses the format of the microdata but does not discuss the extent of coverage.
I used the Google Validator on the test site and had some very pleasing results. I think there was only one error for "event" and two errors for "blog posting". https://search.google.com/structured-data/testing-tool/u/0/#url=https%3A%2F%2Fthemes.gohugo.io%2Ftheme%2Facademic%2F
However when I look at the Blog page for blog articles on Academic there are three errors.
https://search.google.com/structured-data/testing-tool/u/0/#url=https%3A%2F%2Fthemes.gohugo.io%2Ftheme%2Facademic%2Fpost%2Fgetting-started%2F
I would like to hear more about the challenges in removing these errors. Is it some funky validator thing that makes it an unpractical problem to address, or is it an implementation oversight or perhaps something else?
I think that there are several types of content that we as academics are prone to use and that Academic is well situated to present. In general web development we might consider these "edge cases" but because Academic is marketed as a product towards the academic CV it makes sense (at least to me) to talk about supporting these additional elements of schema.org.
What would we benefit from?
Description of Talks as events. https://schema.org/Event
Description of Publications as Creative works. https://schema.org/CreativeWork or http://bib.schema.org/Thesis or http://schema.org/ScholarlyArticle
Description of teaching experience as courses. http://schema.org/CourseInstance
The contact section of our main page: https://schema.org/ContactPage
File Formats https://schema.org/fileFormat
For our tag and category pages https://schema.org/CollectionPage
Since Projects is a reusable widget per #274 and #421 and #429 does it make sense to have two or three "keyword" options for schema descriptions?
What I mean, is that would it be possible to use the same "widget" and then if people use the keyword "people" to describe the objects as schema.org/person whereas if they use the keyword "project" the objects being described could be described as "creative works" or "things".
Some of us in our academic careers have created instructional materials. These can be marked up with LRMI metadata - which is also in schema.org see elements like this one: http://schema.org/EducationalAudience
Or have earned professional certifications. Which i am also currently in a w3c discussion group on formalizing but these would describe things in a skills section.
With all these options it might be easy to get overwhelmed or to think: how will we make it all available?
I am wondering if we might use a key-value pairing in the header. It seems that the theme could take care of almost 90% of this additional usage.
Thoughts?

Considering web performance, it makes completely perfect sense to adopt json-ld, since it is by far more lightweight. It is also more modern and does not interfere with the general markup of a page. Beside these factors, the adoption of that protocol by such a big player as Google, will most likely cause others to follow. Schema.org already offers a json-ld generator, so it's no longer a fringe technology.
However, with that said, json-ld is more complicated and can be a bit complicated to implement, but there are also a lot of gains to be made from using it. Not to be the Google fan-boy, but their search engine is the de facto standard on the web for the general public.
When it comes to the errors and warnings that the Google microdata validator shows you, I personally hit a wall with the publisher type attribute. According to Schema.org both Author and Publisher can be of type Person or Organization, but Google has disregarded this and does not support Person (at least as far as their validation tool goes).
I would be interested on working on this, mostly to be able to clean up the html, but also to produce better search results on sites that support json-ld. I think one of the first steps would be to decide exactly how much of the standard we would like to support. There are a lot of attributes that can be provided, but which of them would make sense to add?

For me publications and courses make the most sense. Others?

There are many types under CreativeWork that in my opinion should be covered. Article, Blog, Comment, Conversation, Course, HowTo*, Software*. Under Event there are also some interesting types, such as CourseInstance and EducationEvent.

Just to note. I found this course description guide for google: https://developers.google.com/search/docs/data-types/course


Deploying and publishing to existing app on AWS Amplify no longer works

Hi! I need some help.
In our company we use Github Actions to deploy and publish our front on Amplify. It always worked perfectly. Deployment and publishing is done in a single Amplify application.
However, since yesterday we were unable to deploy and publish, an error occurs indicating that the user is not authorized to create a new app. However, a new app should not be created in Amplify, an existing app should be used, as it always has been.
Our yml is:
In our YML file we have the following command to publish to Amplify:
amplify init --amplify $AMPLIFY --frontend $FRONTEND --providers $PROVIDERS --yes
The error:

Can you help us please?

Hey @Nadine-Schneider :wave: thanks for raising this! This appears to be a duplicate of https://github.com/aws-amplify/amplify-cli/issues/11120, and as such I will close this as a duplicate bug
Please see this comment for workaround steps. In short, replace init with pull in your script

Hey @josefaidt! 👋
Yes, I just discovered that.
And I managed to solve my problem by going back to version 10.0.0 of @aws-amplify/cli.
Thanks for listening!


Notifying consecutive array changes

I'm trying to notify dom-bind on array changes, with notifySplices, but I cannot get DOM aligned to my model.
Here is live example: http://jsbin.com/burako/2/edit?html,console,output
I modify array, outside of Polymer:
model.array.push({prop:"1"});
var removedItem = model.array.shift();
// ...
// notify `dom-bind` about it
domBind.notifySplices(
    "model.array",
    [{
        object: model.array,
        index: 1,
        addedCount: 1,
        removed: 0,
        type: 'splice'
    }]
);
// ...
domBind.notifySplices(
    "model.array",
    [{
        object: model.array,
        index: 0,
        addedCount: 0,
        removed: [removedItem],
        type: 'splice'
    }]
);

Then I end up with model = {array: [{prop:1}]} and nothing in the DOM.

I've found in code doc:

   *   Note that splice records _must_ be normalized such that they are

   *   reported in index order (raw results from `Object.observe` are not
   *   ordered and must be normalized/merged before notifying).

So does it mean that not only "splice records" but also notifySplice calls need to be normalized/merged?
Could you then provide some rules what precisely this normalization  means?
For example, do I get correctly that after 2 splices and one regular change
array = [item0, item1, item2, item3, item4, item5]
array.splice(3, 2, itemD);
array[4].prop = "new";
array.splice(2, 2, itemTwo, itemThree);

I should notify about 3 different ones, and normalize also notifyPathentry
array.splice(2, 1, itemTwo);
array.splice(3, 1, itemThree);
array.splice(4, 1);
array[5].prop = "new";

?

BTW, do you really want to keep such constraint? As I could imagine the case, when someone (component inside) may listen to changes to perform some animation. There will be no way to notify about the change that should animate push then shift from a list.

Is there a chance for fixing this?

@kevinpschaaf I'm trying to document notifySplices, would be good to get clarification on this point.
Is there a reference somewhere to what we mean by "normalized/merged"?
If this is not easily achievable, maybe we need to consider a 'forced update' method as has been requested in some other issues. I was able to do that using code like this:
var tmp = model.array.slice();
domBind.set('model.array', []);
domBind.async(function() {
  domBind.set('model.array', tmp);
});

Shouldn't there be an easier way to say , "This really isn't the same array anymore. Please throw away the backing collection and start over."?

Thanks @arthurevans for support. Unfortunately, the method you proposed does not fit my case well, as it binds to a copy of an array, what breaks integration with other parts of an app.


[Feature] Storybook Web

This PR implements Storybook on the next app, adding a pnpm storybook:web script to run Storybook from the root folder.
There are two example stories included for the PasswordReset and SignUpSignIn components.

Resolve the merge conflicts and it's good to go!


Library unfinished

Whilst the lib is useful, quite a lot is unimplemented.
Specifically, transactions. I need to look again at them to see how they work

TODO make a list of missing functionality.

Track functionality
alpm_list.h

[x] I've implemented alpm_list_to_vec and vec_to_alpm_list to convert between alpm_list_t and Vec. This
should mean that I don't need to implement any functionality for alpm_list_t, and although the operation
will allocate, there will be much less redirection once in a Vec, since all data is laid out in order in
memory.

alpm.h

[x] alpm_errno and alpm_strerror These are handled in the Error enum. The std::error::Error trait requires
you to implement description(&self) -> &str, which will display the result of alpm_strerror.
[ ] alpm_logaction I need to look to make sure this is working. I'm not sure how essential this is, so it
probably won't get priority.
[ ] alpm_fetch_pkgurl I've implemented this, but I'm not sure how it's supposed to work, so don't know how to
test it.
[ ] alpm_option_get_*cb, alpm_option_set_*cb I've implemented these by storing the user supplied function, and
passing a wrapper function to the C library. Examples of these callbacks working in the /examples directory.
Not done yet for question and progress functions.
[x] alpm_option_get: root, dbpath, lockfile readonly implemented.
[ ] Everything down to alpm_option_get_arch not implemented. Need to work out how to do add and remove
functions. May require implementing some alpm_list after all.
[x] arch, deltaratio, checkspace, dbext, *_siglevel all done.
[x] get_localdb, get_syncdbs, register_syncdb done. Wraps returned handle in Db structure.
[ ] unregister_all_syncdbs not done. Not sure if this can be made safe. Not sure how often it's useful, since
Dbs are unregistered on Drop.
[x] db_unregister done, implicitally when Db is Dropped.

@guinux Do you know of any documentation for how transactions work. This is where I got stuck before. I could look at the source, but I guess that would take a long time.

Sadly no doc. I read pacman sources to understand how alps works.

Ok I'll do the same :S

The Package implementation must be changed. It's good that alpm_pkg_load is the only function that return a alpm_pkg_t which must owned but it can't be free automatically via Drop. In fact the common usage is to load a local tarball and then to install it. In the case of a successful install it must not be freed, otherwise it must be freed.
What I would do:

implement alpm_pkg_load in Transaction in a function which load a tarball and add the returned package to install, this way the package can freed manually in case of failure.
rename PackageRef as Package for name consistency.
maybe implement Package as Db with a struct keeping a reference to a alpm_pkg_t

Hopefully this conversation shows how useful rust can be - it is not possible to work out correct library usage from alpm.h, you have to look through the source. With rust, a library can guarantee that access is memory safe just using the type system.

https://code.toofishes.net/pacman/doc/modules.html Is some documentation for libalpm.
Also wondering if it would be possible to either link to this function, or reimplement it; It would be super helpful (read, I need it for a project): https://github.com/gtmanfred/pacman/blob/master/lib/libalpm/version.c#L39

Hey @MggMuggins, sorry to revive a dead thread, but I did implement this, or at least something similar. I'm experimenting with a pure rust alpm in https://github.com/derekdreery/alpm-experimental, including handling redhat-style version strings.

Just an FYI, I ended up dropping this library altogether for my project in favor of just implementing the functionality I needed. I don't even remember how the source is put together anymore (it's been a year since I looked at this code), but you're welcome to take a look and steal whatever pieces might be helpful: https://gitlab.com/MggMuggins/aurum


Not able to see License Page in Swift 5

I am using Acknowlist to show the licenses of the SPM packages that I am using. The view gives a list of the packages that I am using like as shown below

But when I tap on one of the entries, I am taken to the default landing page of the repository rather than going into the license page as shown below.
For example if I tap on "acknowlist", then the following page is shown

Is this the expected behavior?

Hello @jobinsjohn  👋
Yes, this is the expected behavior. SPM doesn’t specify licences, so AcknowList doesn’t know what to display and falls back to the repo URL (where one can usually find the licence).
If you really want to embed the licence for your SPM dependencies, you’ll have to specify them from your code, by customizing the acknowledgements property in your AcknowListViewController.

Hello @jobinsjohn,
Sorry to bring back this old issue, but it turns out that I found a solution for the problem you reported here. As you can see in #113, AcknowList will now try to fetch the missing libraries from the GitHub API. Not perfect, but a significant improvement in most cases.
I haven’t released it as a new version yet. You can try it on the main branch. Let me know if you have any feedback.

Note: Only works with UIKit so far, not with SwiftUI.


Add a button to each resource page on Medplum app to support downloading as bundle

Feature should include bundling references as well

Complete https://www.youtube.com/watch?v=cux5iBUSALQ


UI redesign Issue: more/less message interaction

Fixes:
Try to fix issue #22801. It is based on the implementation that the color of the more/less button should be the same. If there is any suggestion or correction then please let me know,I will modify the changes.
Fixes #22801

Screenshots and screen captures:
https://user-images.githubusercontent.com/102480226/228023065-03743821-08d4-4b34-86be-ca362e8a8a6a.mp4
https://user-images.githubusercontent.com/102480226/228023427-71c14c70-3b84-401d-a101-ea3f3a919d7c.mp4

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Hey @aa98-45556443355666 , it would be better to squash the commits and make sure they follow the commit guidelines for easy review. Thanks. https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html

@timabbott I have been assigned this issue since more than a month, so please review my pull request made on this issue.

@aa98-45556443355666 Thanks! Unfortunately, this PR does not follow our [guidelines]((https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html) for commit structure and PR descriptions. Closing in favor of #25119; you can help by reviewing the work in that PR and leaving any suggestions for improvement.


[#160785993] add sendgrid transport

Warnings

:warning:

Please include a description of your PR changes.

Affected stories

⚙ #160785993: Integrare transport SendGrid

New dependencies added: nodemailer-sendgrid-transport.
nodemailer-sendgrid-transport
Author: SendGrid
Description: SendGrid transport for Nodemailer
Homepage: https://github.com/sendgrid/nodemailer-sendgrid-transport#readme

Createdabout 4 years agoLast Updatedabout 3 years agoLicenseMITMaintainers7Releases4Direct DependenciessendgridKeywordsNodemailer and SendGrid

README
nodemailer-sendgrid-transport
This module is a transport plugin for Nodemailer that makes it possible to send through SendGrid's Web API!

Usage
Install via npm.
npm install nodemailer-sendgrid-transport

Require the module and initialize it with your SendGrid credentials.
var nodemailer = require('nodemailer');
var sgTransport = require('nodemailer-sendgrid-transport');

// api key https://sendgrid.com/docs/Classroom/Send/api_keys.html
var options = {
	auth: {
		api_key: 'SENDGRID_PASSWORD'
	}
}

// or

// username + password
var options = {
	auth: {
		api_user: 'SENDGRID_USERNAME',
		api_key: 'SENDGRID_PASSWORD'
	}
}

var mailer = nodemailer.createTransport(sgTransport(options));

Note: We suggest storing your SendGrid username and password as enviroment variables.
Create an email and send it off!
var email = {
	to<EMAIL_ADDRESS><EMAIL_ADDRESS>	from<EMAIL_ADDRESS>	subject: 'Hi there',
	text: 'Awesome sauce',
	html: '<b>Awesome sauce</b>'
};

mailer.sendMail(email, function(err, res) {
	if (err) {
		console.log(err)
	}
	console.log(res);
});

License
Licensed under the MIT License.

  Generated by :no_entry_sign: dangerJS


Make master index optional when master is used in other contexts

OpenShift provides a default URL at the root that shows the UI. The
provided flag makes loading the index handler optional for now.

Or, right, sorry.
/cc @nikhiljindal

I reversed it, it was only a few places.  Agree it looks better.

LGTM, but test failures look real (consistent at least)

	auth_test.go:313: case {GET /  map[200:true]}
	auth_test.go:326: Expected status one of map[200:true], but got 404

I'm going to pretend like I was just validating negative testing here...
----- Original Message -----

	auth_test.go:313: case {GET /  map[200:true]}
	auth_test.go:326: Expected status one of map[200:true], but got 404

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3997#issuecomment-72297339

Rerunning Travis.

Travis is green. Merging.


scream: 3.6 -> 3.7

Motivation for this change
Updated, also Jack support added and stuff
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128524 run on x86_64-linux 1

1 package built:

scream


regression: process doesn't resume on page refresh

Ran out of time today but I marked my place in my investigation. The regression was introduced above this red line:

Upon refresh, if a process is in progress, it should resume at the correct intermediate location and update the percent, duration, and progress bar tween at regular intervals. However, after this regression, there is no update. Once I find the first failing build, I'll hopefully identify the root cause.

Need some followup AIs to prevent this type of regression in the future. Will create issues for those later.


Unpdate installation instructions in README

Point users to install from PyPI:
pip install deep_disfluency

Seems that this issue was resolved. Closing.


LsmStorage::scan does not include level 1-6 iterators

I noticed that the reference scan function in https://github.com/skyzh/mini-lsm/blob/main/mini-lsm/src/lsm_storage.rs doesn't include l1-l6 iterators. It stops at merging the memtables and the l0_sstables. Wondering if this is a mistake or there's a reason behind doing so. I would suppose scan would return an iterator over all the data in the storage?

Up to part 4 we only have l0 SSTs. Other levels will be supported in the compaction chapter. Thanks for reporting!


[FileName("outputfile")] attribute causes the metadata to be exported to the wrong file

Description
Using the Bridge. FileName attribute seems to cause some issues with meta-data output for reflection. The metadata will be output to a different file than the attribute specifies.
Example
[FileName("outputfile")]
class Test
{
    public int Item {get;}
}

Will generate the following files:

default.js -> All other code that does not have the FileName- attribute
default.meta.js -> All other metadata, AND the metadata of the class "Test"
outputfile.js -> The code/implementatino of class "Test"
outputfile.meta.js -> Is not generated at all

Observe that the metadata for class "Test" is still in default.meta.js, while outputfile.meta.js does not exist at all.
Steps To Reproduce
Not reproducable on Deck.NET.

No matter how I look at it, it really seems off. Hitting 'defect' label.

This introduces a breaking change as the emitted file structure will be (potentially) different upon building Bridge after the proposed fix is effective in the translator.

Reviewed and merged, will make it to the next Bridge release!


New command: remove classic site

Remove classic site

command: spo site classic remove -u|--url <url> --skipRecycleBin --confirm
url - url of the site to remove, required
skipRecycleBin - set to directly remove the site without moving it to the Recycle Bin
confirm - don't prompt for confirmation before removing the site
requires connection to tenant admin site

For more information see: https://github.com/SharePoint/PnP-PowerShell/blob/59f19f26232e46b429687bfdfa10600258ef6bb7/Commands/Admin/RemoveTenantSite.cs

I'll take this!

Excellent! All yours!

Hey @rjesh-git, are you still working on this command?

Sorry got busy with work, please change the label. Will take it, once I'm freed up.

Sure thing

You can assign this one to me

Quick question(s):

deletion can take some time as well (most deletions are handled within the first request, but some larger sites take up to a few minutes), do you expect a --wait option as well?
When you delete without --skipRecycleBin the site will be moved to the recycle bin. In PnP they introduced a --fromRecycleBin to remove it from there (otherwise you would not have an option to delete it from that location as well). Would that be a requirement for this command as well?

yes and yes. Good ideas!


Not issue, need help.

Need help to config trade in gekko

my config

What exectly are you having problems with? If you want to create real orders using gekko, please see this document:
https://github.com/askmike/gekko/blob/stable/docs/Plugins.md#trader

Gekko trading, And i lose btc, have no profit. What i do wrong.

What kind of strategy are you using? Do you get different results when backtesting or paper trading? Read this very carefully:
https://github.com/askmike/gekko/issues/201


Project structure: move *Services into control-plane core module

Feature Request
Currently the *Service services are located into the data-management modules so they aren't usable from other extensions.
The idea would be to make them available.
Which Areas Would Be Affected?
data-management, core
Why Is the Feature Desired?
Giving the opportunity to implement different kind of api.
Solution Proposal
Move the Service interfaces to the control-plane spi and the implementation to the control-plane core extension.
Type of Issue
cleanup
Checklist

[x] assigned appropriate label?
[x] Do NOT select a milestone or an assignee!

Superseded by https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/1887


[JENKINS-35420] Pipeline compatibility

JENKINS-35420
Could be improved by integration with @abayer’s https://github.com/jenkinsci/junit-plugin/pull/76; currently just coalesces archival patterns from all junit steps in the last build, whereas we would rather keep distinct results for each kind of test being reported.
@reviewbybees

‘Jenkinsfile’ not found??

Ah, not from a trusted source, so I cannot test a Jenkinsfile. Will try a separate PR for that.

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@reviewbybees done (more or less; some minor changes after last reviews)
@olivergondza WDYT?

Changes made to the plugin makes sense to me. I am barely following what PipelineAttacher is doing but that is Jesse's domain and the main body of the PR so I presume it works as it should. So +1 from me.

Let me explore the suggested block-scoped step.

@reviewbybees done

Thanks, are we ready to merge?

@olivergondza yes as far as I am concerned. Also please check the downstream demo PR where you can see this in context.


Fix SSL3_ALIGN_PAYLOAD=0

"./config -DSSL3_ALIGN_PAYLOAD=0" used to work
before 1.1.1 but is now broken.
This patch fixes it again.

Checklist

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

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 92 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 123 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 154 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 185 days ago

I've approved the change for 3.x, but do note that it will give warnings with -Wundef

It is unclear to me, this is right given @mattcaswell comments on #20215

I'll remove approval label until this is clarified

I've added it back and added hold as it needs to wait for https://github.com/openssl/openssl/pull/20215 anyway.

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


[ERROR]: {"code":"7","message":"No ssrResources.json file"} when deploying a SSR Next Js App

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Next.js
Amplify APIs
Not applicable
Amplify Categories
hosting
Environment information

# Put output below this line

2021-09-29T04:42:25 [INFO]: Beginning deployment for application dh8mh8nkle4ny, branch:dev, buildId<PHONE_NUMBER>
2021-09-29T04:42:26 [INFO]: Cannot find any generated SSR resources to deploy. If you intend for your app to be SSR, please check your app Service Role permissions. Otherwise, please check out our docs on how to setup your app to be detected as SSG (https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app)
2021-09-29T04:42:26 [ERROR]: {"code":"7","message":"No ssrResources.json file"}

Describe the bug
When I try to deploy my Next JS app on Amplify I encounter this error. My build is 100% successful but I don't know why I am getting this error. I have set my app Service Role permission.
I am using Amplify website to deploy my Next JS application ( not with Amplify CLI)
Expected behavior
100% status on deploy
Reproduction steps

Connected my Github Private Repo with Amplify
Build the project (100% success)
Fails on Deploy with the error above.

EXPECTED OUTPUT

ACTUAL OUTPUT
// Put your logs below this line

Hi @abdullahmujahidali 👋 Thank you for raising this! transferring this issue over to the console repo as it seems more related to hosting than the Amplify JS library.

Any updated for this issue?

I got the same issue and spent hours trying to figure out what was wrong, finally, I realized that I was using yarn's berry version to manage my project, and when Amplify builds the app; it uses the classic version. So after installing again the dependencies with the classic version, it finally worked.
I was using NextJs version 12 and initially thought that was the problem, but I managed to deploy that version with the yarn change.
Hope this helps someone.

I realized that I was using yarn's berry version to manage my project, and when Amplify builds the app; it uses the classic version

I had the same issue and thought yarn would look into .yarnrc.yml file to look for yarn implementation.

Same error as above, No ssrResources.json file. The build procedure was stopping at the SSG phase, and was skipping the SSR build.
I've a mixed SSG and SSR nextJS 12 app and I solved the problem adding this line  "export": "next build && next export", to the package.json script.
"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "export": "next build && next export",

Hi, here is the docs for deploying SSR App (Package.json file settings) https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app
Feel free to re-open this if issue persists, thanks!

I'm having the same issue. I'm not using yarn berry (for all I know). This happens after updating to next12 version. @victorccccc I followed the instructions and even admin access to the amplify-backend-deployment role did not work. I think this should be reopened

@NotSoShaby
try running:
aws amplify update-app --app-id <APP_ID> --platform WEB --region <REGION>
if you've followed everything in this article: https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app
Also, take a look at this helpful link: https://github.com/aws-amplify/amplify-hosting/blob/main/FAQ.md#convert-an-ssr-app-to-ssg

I'm also facing this issue when using Amplify's build preview feature. I've tried everything above and nothing has worked. Interestingly enough though, sometimes a build generated from a new PR with the same code used in a different PR's build preview that failed will succeed (I have no idea why). Any help on this matter would be great, it is quite frustrating.


Vulkan: dof_blur_far_distance & near are innacurate

Godot version
4.0 custom e093cfdf0
System information
Win 10/64 NVIDIA GeForce GTX 1060/PCIe/SSE2
Issue description
The observed distances for the focus planes are way off from the measured and specified distances.
Build Version is from @Calinou 's pr #62501 so I can use separate blur plane settings.
In these examples, transition is set to 0.1 and blur to 0.2 so we get sharp, observable planes.
Near:
Here the measured distance to the pink box near corner is: 2.88, and to the far is 4.2. Placing the blur plane between those corners, it should be about 4.0, however you can see the setting is 8.01.

Far:
Here you see the blur plane cuts through the purple box when set to 21.77. However the box near face is 10.38 and far is about 11.25.

Related to #62473 and pr #62501
Steps to reproduce
Set the distance planes at a value you know and observe that they are different than what is specified.
In the sample project, the camera is at (-1.5, 3, 4.5), the blue box is at (-2, 1, -2), for a distance of 6.819 from camera to box center, and +/- 0.5 to the far or near faces. Turn on or off the near or far blur planes. They are set so that visually they cut through the middle of the blue box at 6.8. However far is set to 13.09 and near 12.87.

Minimal reproduction project
test_dof_blur.zip

Can this get added to the gd4 road map? What determines what gets added to that list?


[BEAM-7389] Add Python snippet for WithTimestamps transform

Add Python snippet for WithTimestamps transform

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

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] 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.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @aaltay Can you have a look please?

retest this please

Run Python PreCommit

Run RAT PreCommit

R: @pabloem could you review this PR when you get a chance?

Run Python PreCommit

Run Python PreCommit

Run Python PreCommit

this LGTM. Thanks David, I think it's great practice to add thorough unit tests for snippets : )


Handle publishing of packages using Yarn Classic

This was previously submitted as #17 and has been reworked.
Reopening as collectively hours are wasted trying to identify compatible combination of actions for legacy repos as they transition to automated publishing.
Yes, @metamask/action-npm-publish@1 does work for Yarn Classic use-cases but there are further changes in this action that would benefit those still actively maintained Yarn 1 repos.

Feat: Fall back to npm publish / npm pack when yarn>=v3 not available

This works regardless of if packages are using npm or yarn as packageManager.

CI: Fix skunk-monorepo test to actually test intended behavior

The test indicates that it should validate that publishing is skipped because versions are already published. Instead, it just ran yarn pack and never runs the version-checking code.
Also adds PUBLISH_NPM_TAG env var to make the test pass

Feat: Fall back to recognizing NPM_TOKEN env var if YARN_NPM_TOKEN env var not set
Fix: Move set -x to not leak npm token in debug log

Also noticed that one of the CI tests doesn't actually run the intended code at all, which is also fixed in this PR now. Reviewers: Let me know if you prefer me to split that part (and the associated NPM_TOKEN recognition) in a separate PR from this one.

Is it possible for you to test this PR on a fork of core, and also a fork of whichever library you've been working with that still uses Yarn v1? As annoying as it is that's the only real way we've been testing these actions so far.

@legobeat Oh cool. No that sounds good, thanks for confirming that.
I do see that shellcheck is failing though :/

@legobeat Lovely 😫 Well, I have approved now.


PHP 7.4.9 Update with Composer

Please see change log attached.
Change log.docx

@timothygwebb Looks go so far from what I've read... though i still have a lot to go through.
One thing you need to do is remove the config file. it contains details specific to you test installation, il update this posts if i spot anything else :)

@timothygwebb Looks good so far from what I've read... though i still have a lot to go through.
One thing you need to do is remove the config file. it contains details specific to your test installation, il update this posts if i spot anything else :)
I have deleted the bb-config.php file.
Thanks.

You need to remove bb-data/cache/ & bb-data/log/ directories too along with their contents...

You need to remove bb-data/cache/ & bb-data/log/ directories too along with their contents...
@rndevuk  I have removed bb-data directories.

I think its possible that the he did it by accident. i assume he made his changes on a version of bb that was prior to pull request #622
@timothygwebb might be worth going through your commits and pulling out all files that were not directly changes by you..
it seems you maybe be accidently overwriting various changes...

Alright then @rndevuk.

@timothygwebb I also agree to the
https://github.com/boxbilling/boxbilling/pull/628/commits/3ada75fb841746e452f25d222fd08846906cedba#diff-c58ebdc533db078bc2374f10b5582a44L123
You've also replaced this
 if($this->di['config']['debug'] === FALSE && $event['priority'] > self::INFO) {
with:

@timothygwebb
This commit 3ada75f reverses this pull request #622.
Is there a reason for the reversal?

The reason is with the following line of code in the pull #622 I am unable to login to the bb-admin administration area.
[root@webbhostingservices log]# diff /var/www/vhosts/webbhostingservices.com/httpdocs/boxbilling/bb-library/Box/Log.php /root/boxbilling/src/bb-library/Box/Log.php
45c45
<     protected $_min_priority = NULL;   //protected $_min_priority = array();

protected $_min_priority = NULL;

121,124c121,123
<
<             if($this->di('config')('debug') === FALSE && $event('priority') > self::INFO) {
<           //do not log debug level messages if debug is OFF
<           //if($this->_min_priority && $priority > self::INFO) {

    //do not log debug level messages if debug is OFF
    if($this->di['config']['debug'] === FALSE && $event['priority'] > self::INFO) {

166c165
< }

}
\ No newline at end of file

[01-Sep-2020 16:26:12 UTC] PHP Notice:  Trying to access array offset on value of type null in /var/www/vhosts/webbhostingservices.com/httpdocs/boxbilling/bb-library/Box/Log.php on line 122
Fix to array offset I implemented
       if($this->di('config')('debug') === FALSE && $event('priority') > self::INFO) {
      //do not log debug level messages if debug is OFF
      //if($this->_min_priority && $priority > self::INFO) {
        return ;
    }

Produced Bad Log Priority so I modified it to be
//if($this->_min_priority && $priority > self::INFO) {
Let me know if you all have any further questions. Remember I am upgrading this to php7.4.9 and the information in the pull #622 is not to the latest and greatest. I am fixing all errors to be compliant with the version php7.4.9. and the most updated version of composer packages.

@timothygwebb
3ada75f#diff-c58ebdc533db078bc2374f10b5582a44L123
You've also replaced this
 if($this->di['config']['debug'] === FALSE && $event['priority'] > self::INFO) {
with:
if($this->_min_priority && $priority > self::INFO)
Could you also explain why? I think it should only log debug messages if debugging is enabled.
Is there a problem with the existing behaviour?

@samapraku Explanation included with prior comment.

@timothygwebb might be worth going through your commits and pulling out all files that were not directly changed by you and also check that you are using the latest master branch for these changes...
it seems you maybe be accidentally overwriting various changes...

I did pull the master before making these changes and re-based by request of @fordnox for my prior pull request that I closed for this one to replace. Please let me know if you all have any further questions.

Appologies @timothygwebb I assumed wrongly. :)

@timothygwebb
I get your explanation. However, I was mainly focusing on the first part.
The if condition has two parts, the first part if($this->di['config']['debug'] === FALSE && ...) checks if debug is enabled in the bb-config file before logging debug messages but you left that out so it means that debug messages will be logged regardless of whether debug is set to true or false in bb-config.
Is the configuration value check not compatible with PHP 7.4?

@timothygwebb
I get your explanation. However, I was mainly focusing on the first part.
The if condition has two parts, the first part if($this->di['config']['debug'] === FALSE && ...) checks if debug is enabled in the bb-config file before logging debug messages but you left that out so it means that debug messages will be logged regardless of whether debug is set to true or false in bb-config.
Is the configuration value check not compatible with PHP 7.4?
@samapraku I have pushed change to switch variable back to 'NULL'.
It works again now with your modification.
Thanks for the catch.


Tz and lk issues

Pmos recommends this tz with a size of over 400k (https://releases.linaro.org/96boards/dragonboard410c/linaro/rescue/17.09/dragonboard410c_bootloader_emmc_android-88.zip) and I would like to know if the Switching rproc mode is available？

I would like to know if the Switching rproc mode is available？

What do you mean by this?
All versions of the bootloader will work fine.

What do you mean by this?
Lk supports reading a file called 'rproc' to turn off the modem or both wifi and modem. If you want, you can search for 'rproc' on the pmos wiki to see it.


set core.wcm.components deps as provided and do not embed them

remove embedded deps of core.wcm.components.*
set core.wcm.components.* as provided
rename language_country to languageCountry (refactoring leftover)

core.wcm.components.* deps are part of quickstart and should not get installed with project generated by the archetype, otherwise a duplicated bundles get installed with different versions resulting in a conflict that breaks model adapter

What about for AEM 6.x.x @grubyak ? Those won't have the latest AEM Core Components as part of the quickstart...

@godanny86 do you think it would be reasonable to document that with help of @bohnertchris that for some aem versions core.wcm.components deps would need to be installed manually, or you would prefer to have them embedded conditionally for specific aem target?
cc: @pfauchere

@grubyak I think there seems to be a misunderstanding:

or you would prefer to have them embedded conditionally for specific aem target?

That's exactly how this maven archetype works , see the aemVersion property:
https://github.com/adobe/aem-project-archetype#available-properties
Setting aemVersion to cloud skips the inclusion of core components dependencies, setting any of the on-prem versions includes them.


[translation\ Update Catalan translation of CLI

Please check the translation files you want to add/fix/update:

[ ] CLI banner: (apps/jreleaser/src/main/resources/org/jreleaser/cli/Banner*.properties)
[x] CLI bundle: (apps/jreleaser/src/main/resources/org/jreleaser/cli/Messages*.properties)
[ ] core bundle: (core/jreleaser-utils/src/main/resources/org/jreleaser/bundle/Messages*.properties)

A list of language codes can be found at https://sda.berkeley.edu/man41h/localelist.htm
Changes:
diff --git a/apps/jreleaser/src/main/resources/org/jreleaser/cli/Messages.properties b/apps/jreleaser/src/main/resources/org/jreleaser/cli/Messages.properties
index 25b435a9..d837359a 100644
--- a/apps/jreleaser/src/main/resources/org/jreleaser/cli/Messages.properties
+++ b/apps/jreleaser/src/main/resources/org/jreleaser/cli/Messages.properties
@@ -31,6 +31,9 @@ usage.footerHeading      = %nDocumentation found at https://jreleaser.org%n
 helpCommand.command      = COMMAND
 help                     = Show this help message and exit.
 version                  = Print version information and exit.
+filter.header            = %nFilter:%n
+include.filter.header    = %nInclude Filter:%n
+exclude.filter.header    = %nExclude Filter:%n
 # options
 debug             = Set log level to debug.
 info              = Set log level to info.
@@ -40,9 +43,18 @@ basedir           = Base directory.
 output-directory  = Output directory.
 overwrite         = Overwrite existing files.
 dryrun            = Skip remote operations.
-announcer-name    = The name of the announcer.
-distribution-name = The name of the distribution.
-tool-name         = The name of the tool.
+announcer-name        = Include an announcer. Repeatable.
+exclude-announcer     = Exclude an announcer. Repeatable.
+assembler-name        = Include an assembler. Repeatable.
+exclude-assembler     = Exclude an assembler. Repeatable.
+packager-name         = Include a packager. Repeatable.
+exclude-packager      = Exclude a packager. Repeatable.
+distribution-name     = Include a distribution. Repeatable.
+exclude-distribution  = Exclude a distribution. Repeatable.
+uploader-type         = Include an uploader by type. Repeatable.
+exclude-uploader      = Exclude an uploader by type. Repeatable.
+uploader-name         = Include an uploader by name. Repeatable.
+exclude-uploader-name = Exclude an uploader by name. Repeatable.
 # errors
 ERROR_trace_file_init  = Could not initialize trace file
 ERROR_unexpected_error = Unexpected error
@@ -84,7 +96,6 @@ jreleaser.announce.usage.header        = Announce a release.
 # header
 jreleaser.assemble.usage.headerHeading =
 jreleaser.assemble.usage.header        = Assemble distributions.
-jreleaser.assemble.assembler-name      = The name of the assembler.

 ###############################################################################
 # Changelog
@@ -203,11 +214,14 @@ jreleaser.sign.usage.header        = Sign release artifacts.
 ###############################################################################
 # header
 jreleaser.template.usage.headerHeading =
-jreleaser.template.usage.header        = Generate a tool/announcer template.
+jreleaser.template.usage.header        = Generate a packager/announcer template.
 jreleaser.template.announcer.header    = %nAnnouncer templates%n
-jreleaser.template.tool.header         = %nTool templates%n
+jreleaser.template.packager.header     = %nPackager templates%n
 # options
 jreleaser.template.distribution-type   = The type of the distribution.%nDefaults to JAVA_BINARY.
+jreleaser.template.distribution-name   = The name of the distribution.
+jreleaser.template.packager-name       = The name of the packager.
+jreleaser.template.announcer-name      = The name of the announcer.
 jreleaser.template.snapshot            = Use snapshot templates.
 # text
 jreleaser.template.TEXT_success        = Template generated at {}
@@ -217,7 +231,4 @@ jreleaser.template.TEXT_success        = Template generated at {}
 ###############################################################################
 # header
 jreleaser.upload.usage.headerHeading =
-jreleaser.upload.usage.header        = Upload all artifacts.
-# options
-jreleaser.upload.uploader-type       = The type of the uploader.
-jreleaser.upload.uploader-name       = The name of the uploader.
\ No newline at end of file
+jreleaser.upload.usage.header        = Upload all artifacts.
\ No newline at end of file

@anyulled perhaps you can help with this translation once more?

sure, assign it to me

Hi @anyulled, do you think you could get the CLI translation before Saturday? Would like to release v0.9.0 with this translation if possible 😁

sure, give me this weekend for it
Le jeu. 25 nov. 2021 à 22:29, Andres Almiray @.***> a
écrit :

Hi @anyulled https://github.com/anyulled, do you think you could get
the CLI translation before Saturday? Would like to release v0.9.0 with this
translation if possible 😁
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jreleaser/jreleaser/issues/505#issuecomment-979476238,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAYTBOHWTYREWDI3UQWEB3UN2TD3ANCNFSM5H3I5SUQ
.

--
*
https://about.me/anyulled?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb
Anyul Rivas about.me/anyulled
https://about.me/anyulled?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb
*


Would it be possible to do this?

How would I make it so it would check for the latest image from an account every half an hour and download if there's a new one?
I'd understand -latest would do that but I don't know how to schedule it.
I suppose a cron job would do it but I'm kinda unsure about this.
10 * * * * instagram-scraper instagramname --latest --destination /home/lewis/
This should be working right? Not seeing any updated images. ;/

This worked for me under macOS. Should be virtually the same on UNIX.
PATH=/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/bin:/usr/sbin:/sbin
MAILTO=""
*/30 * * * * instagram-scraper stradivariuz_  --latest --destination /tmp/instagramname >> /tmp/instagramname.log 2>&1


Define 'TextScaler'

the BullBitcoinWalletApp class is trying to access a getter called TextScaler which hasn't been defined or properly imported.

the textScaler is currently fixed.
We planning a design sprint for accessibilities in the near future.


feat(DefinePlugin): Support array as value in DefinePlugin

What kind of change does this PR introduce?
Currently, DefinePlugin doesn't support array as value. Let's see this example:
new DefinePlugin({ ITEMS: [1, 2, 3] })

We get:
{ '0': 1, '1': 2, '2': 3 }

With these changes, we get:
[1, 2, 3]

Did you add tests for your changes?
Yes
Does this PR introduce a breaking change?
Potentially, yes. Because before, an array was handled as an object
What needs to be documented once your changes are merged?
We can add information about using array in DefinePlugin, here

Please accept CLA, thanks for PR

Hi @sokra, may you have a look at the PR? I applied your review's suggestions 🙂

@evilebottnawi Will this PR be merged? 😕

Thanks


Fix running commands on NixOS.

Resolves #22
As mentioned in the issue, nohup does not exist at the path /usr/bin/nohup on NixOS, but like any Linux distro I can think of, it is a core utility that is available on the default PATH.

Hey @The-Jonsey, as it's been a couple of months since I submitted this PR, I thought I'd best check in to see if there is anything I can do to help get this merged?
I'd really like to be able to use streamdeckd/streamdeckui on NixOS, including packing it up, but I'm kinda stumped without this little change.
If there's any way I can help, please let me know.


Get kubeprod latest release programatically in quickstart guides

This will default to the latest release available of kubeprod. By the moment it will be set to:
~/projects/kube-prod-runtime$ echo $BKPR_VERSION
v0.3.1

Let me know what you think :)

done, thanks for the feedback 👍


Update sdelete url

The sdelete download has 404'd on me a few times now and failed builds, so I hunted down a working url.

Closing this in favor of #201. Your approach downloads the exe and not the zip. As discussed in #201 we plan to move to a pure PowerShell version. But for now master branch should work again.

Sounds good - didn't see that other PR.


verify the compatibility with Istio

A link to the original Istio design doc, may be useful.
Some aspects to investigate:

Authorization polices allow for connectivity between pods in the mesh.  What connections are to be allowed?  e.g. function pod to broker.
Remember that function pods must not use the broker's Kubernetes service account or secrets.
All pods need to have a label service.istio.io/canonical-name with the name of the Function object or FunctionMesh object.  This service name will become the 'source' traffic label in the Istio graph explorer.  e.g. "function mesh X is sending traffic to Pulsar cluster Y".
if the function mesh has a Service, rename the ports to use the Istio naming convention.
Istio doesn't allow for init containers that perform network calls.  Will this cause a problem?
Is there any pod to pod communication?   Are requests made to a headless service or to a pod ip?  (mTLS issues)


vue-cli can`t be run with ip adrees

A Vue project  create by vue-cli can be run with 'localhot:8080' but can not be run with ip adrees, why?

what kind of IP address?

such as "http://<IP_ADDRESS>:8080"

localhost doesn't allow external access from our network. That'S why it's the default setting, it's secure.
Set the host to <IP_ADDRESS>, then other computers in the network can access it via your local IP.

https://github.com/webpack/webpack-dev-server/issues/147

Firewalls can be trouble too. I had to disable the Firewall of Windows to use that feature.


Battery status not reported on devices

Hi Again,
Another thing I have noticed has been "lost" after the switch: all batteries powered devices reports as "0%" on battery level. On the old plugin the battery status showed correctly.
Not a big hassle, just to pinpoint the issue

Hi,
I have the same effect. Is it possible to have an estimate date of resolution?
Thanks à lot for the job.

@redeemer666, @naspinec I have several battery powered devices that report correctly the battery level on HC3. Which devices do you have? Are all presenting the problem?

@redeemer666, can you test the beta version?
With: npm install -g homebridge-fibaro-home-center@beta

Hi Again,
With your latest version (1.2.2) issue has been solved. Beta not needed, so thanks a lot for your kindness

ok.

Hi ilcato.
Same for me, I use an hc2 and with the old plugin the battery level was correctly reported.
Regards.

Le 7 déc. 2021 à 17:01, Andrea T. @.***> a écrit :

Hi ilcato,
I have a Fibaro home center 2 and home center lite and all battery-powered devices report the status at "0%". This was not happening on the old plug-in
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Update pysaml2 to fix known vulnerability

https://github.com/ayr-ton/kamu/network/alerts
Currently, there's no updated version that fixes this issue, I'm one of the maintainers of this plugin.
As this plugin is not an authentication backend for Django we may or update the plugin for supporting this or migrate to a new one that supports this.
Also, there's always the possibility of just fixing the initialization vector across encryptions and release a new plugin version with this.

pysaml2 was already updated.


[Experimental] Implemented a CloudProvider extension mechanism using runtime.RawExtensions

Issue, if available:
https://github.com/awslabs/karpenter/issues/642
Description of changes:

Uses runtime.RawExtensions as an arbitrary cloud provider extension mechanism
Strongly typed AWS fields are not currently implemented (Well Known Labels continue to work)
Collapsed validation logic since validation can be done on extensions (restricted labels must be registered)

apiVersion: karpenter.sh/v1alpha3
kind: Provisioner
metadata:
  name: default
spec:
  # Provisioned nodes connect to this cluster
  cluster:
    name: "${CLUSTER_NAME}"
    caBundle: "${CLUSTER_CA_BUNDLE}"
    endpoint: "${CLUSTER_ENDPOINT}"

  # If nil, the feature is disabled, nodes will never expire
  ttlSecondsUntilExpired: 2592000 # 30 Days = 60 * 60 * 24 * 30 Seconds;

  # If nil, the feature is disabled, nodes will never scale down due to low utilization
  ttlSecondsAfterEmpty: 30

  # Provisioned nodes will have these taints
  taints:
    - key: example.com/special-taint
      effect: NoSchedule

  # Provisioned nodes will have these labels
  labels:
    ##### AWS Specific #####
    # Constrain node launch template, default="bottlerocket"
    node.k8s.aws/launch-template-id: "bottlerocket-qwertyuiop"
    # Constrain node launch template, default="$LATEST"
    node.k8s.aws/launch-template-version: "my-special-version"
    # Constrain node capacity type, default="on-demand"
    node.k8s.aws/capacity-type: "spot"

Changes to
apiVersion: karpenter.sh/v1alpha3
kind: Provisioner
metadata:
  name: default
spec:
  # Provisioned nodes connect to this cluster
  cluster:
    name: "${CLUSTER_NAME}"
    caBundle: "${CLUSTER_CA_BUNDLE}"
    endpoint: "${CLUSTER_ENDPOINT}"

  # If nil, the feature is disabled, nodes will never expire
  ttlSecondsUntilExpired: 2592000 # 30 Days = 60 * 60 * 24 * 30 Seconds;

  # If nil, the feature is disabled, nodes will never scale down due to low utilization
  ttlSecondsAfterEmpty: 30

  # Provisioned nodes will have these labels
  labels:
    foo bar
  # Provisioned nodes will have these taints
  taints:
    - key: example.com/special-taint
      effect: NoSchedule

  launchTemplate: "bottlerocket-qwertyuiop"
  subnets: ["abcd", "efgh"]
  securityGroups: ["ijkl", "mnop"]
  capacityType: "spot"

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@rustrial FYI

@ellistarn I am not yet sure whether I fully understand your design decisions. Talking about provider specific extensions, I was (naively) always thinking about something like the example below, in which all provider specific extensions are captured in a single YAML sub-tree called (something like) provider:
apiVersion: karpenter.sh/v1alpha3
kind: Provisioner
metadata:
  name: default
spec:
  # Common part, well typed and common to all providers
  cluster:
    name: "${CLUSTER_NAME}"
    caBundle: "${CLUSTER_CA_BUNDLE}"
    endpoint: "${CLUSTER_ENDPOINT}"
  # Make constraints a dedicated subtree to avoid mixing constraints and non-constraints properties
  constraints:
    ttlSecondsUntilExpired: 2592000 # 30 Days = 60 * 60 * 24 * 30 Seconds;
    ttlSecondsAfterEmpty: 30
    taints: {}
    labels: {}
  ...
  # Provider specific extensions (of type runtime.RawExtensions)
  provider: {}

With such a design:

As much as possible (the parts common to all providers) is still we-typed (structured) with all the benefits of typing (compiler support, ...) and reducing code size (as we can use go's Marshall/Unmarshall infrastructure as it is for most parts).
Only provider is untyped (runtime.RawExtension) to minimise the unstructured surface (risk for bugs)
No matter which common and provider-specific extension properties we add in future there will never be a name conflict (clash) as all extensions are nested below provider.
We clearly separate constraints from non-constraints properties by nesting the below constraints instead of inlining them on top-level (in .spec).
Of course, there might be additional provider-specific constraints, which are part of provider (and not constraints) such as subnet selection (etc.), but those constraints are provider-specific-contstrains and will need anyway provider specific logic.

Please, let me know what you think about this and how it compares to your ideas.

Thoughts

Please, let me know what you think about this and how it compares to your ideas.

I think the only difference is whether or not these fields are inlined in YAML or under a field called provider. I toyed with this idea a lot. I'm not too concerned about code bugs -- they can be fixed, while the customer experience with the interface cannot.
I'm most compelled by:

No matter which common and provider-specific extension properties we add in future there will never be a name conflict (clash) as all extensions are nested below provider

I am a bit wary about versioning challenges and making sure that there's a path to promote fields from the provider spec to the top level spec.
I'm not a huge fan of:

Make constraints a dedicated subtree to avoid mixing constraints and non-constraints properties

Even in your example, ttlSecondsUntilExpired are behaviors and not constraints, as I see them. I don't like promoting the concept of constraints be part of the API, since ideally users don't need to think in these terms, and they're only used to simplify the implementation.

Thinking further, I feel somewhat torn on nesting provider or inlining.

provider will help us avoid collisions. Aren't collisions bad in any situation? If both spec.myfield and spec.provider.myfield are valid, that seems massively confusing. Is it possible that collision prevention is a good thing?
provider makes it more clear to customers which fields are cloud provider specific -- how valuable is this?
provider means that zones and provider.securityGroups are no longer siblings. This seems like a big bummer.

Maybe we should define some guiding tenets, which will help use make a decision for such cases.
For example (this is just a starting proposal ...):

Make common things uniform, simple and intuitive:

Things common among all providers (even if a minority of providers does not support all of them) should not go into the provider extension and instead have a well structured (typed) representation. Such properties might still have (extended) provider specific validation logic, but syntactically they are represented in an uniform way. According to my understanding this would include cluster, ttl*, taints, labels, zones, tags.
Make it hard for users to do common things wrong. The easier the mental model of those things is, the less tickets and support requests we will have to deal with. Support, if avoidable,  is always a waste of time. If you catch yourself and others in your community repeatedly explaining the same things (in tickets, PRs, chats, ...) or resolving the same problem than there is likely something wrong with your design.

Make provider specific things possible:

If it is provider specific or otherwise hard to abstract among all providers, put it into the provider extension. For AWS provider this might include things like subnets, launchTemplate, securityGroups, capacityType, ...
Whenever possible provide a sane default (behaviour) for provider specific things (making them optional)

Avoid inconsistency by design and not by convention:

If you can prevent errors/problems/bugs by design you save yourself and your community endless hours of debugging, bug fixing and maybe emotional discussions (which might burn-out contributors). Separating provider specific extension into the provider sub-tree is an example for this tenet as it will avoid several kind of potential future name conflicts, which might only show-up at runtime (e.g. in which order are things deserialised, the slightest change in go's unmarshalling logic might break your system).

...

Are you interested in syncing up on slack? You kind find me on the kubernetes slack under "Ellis Tarn". https://kubernetes.slack.com/archives/D015J88KGPL

Closing in favor of https://github.com/awslabs/karpenter/pull/681


[Perf] Introducing static bundle

This is a performance specific configuration which gives us two major performance benefits:
1. Reduce webpack's dev re-build time by 2x (or more)
Webpack's rebuild time usually depend on the amount of code it needs to handle. Basically, most of those code is from NPM modules but not from your app's source code. With static modules, we are moving those NPM modules out of the webpack builder and serves directly.
With that change, webpack only handles your app's code. So, that's where we could gain the re-build performance.
2. Explicitly define common modules
Our code splitting logic moves any common modules into a common bundle. But in order to do that, that module needs to be used in every page in our app. Practically, that's something hard to do.
Because of that, some of the most used modules won't move into the common bundle and keep a copy of that module in each and every page in your app. That increases the overall size of the app.
In that case, we could mark that module as a "static module" and then it'll move into the static bundle.
Usage
Add following content into your next.config.js.
module.exports = {
  staticModules: function(options) {
    // use options.dev flag to add modules to the bundle based on the env.
    return [
      'material-ui',
      'material-ui/svg-icons'
    ]
  }
}

You could use this app to benchmark this PR.
(Thanks @tgoldenberg for the sample repo)

This is amazing @arunoda 😮 checking now.

The Idea seems great 👍  I wonder if we can use DLL plugin of webpack for this purpose 🤔
https://github.com/webpack/docs/wiki/list-of-plugins#dllplugin
I'm not fully understand how it works yet though.

@nkzawa DDL plugin uses something similar. (It complicated things a bit)
Anyway even if we do that, we need to do a webpack build for that.
We don't need that and this is something we've already done with our CDN bundle and
we know it's working pretty well.

Thanks @timneutkens pick your changes.

@arunoda What I expect is cache of webpack works and don't rebuild dll files at all when the plugin is enabled. Then basically it would be the same with what this PR does ?
Anyway I wonder if this can be a webpack plugin since this is a workaround for webpack. I feel t's a bit weird to have settings on next.js.

It seems DLL plugin works a bit differently than what I expected, but using the plugin is a recommended way anyway ?

It seems DLL plugin works a bit differently than what I expected, but using the plugin is a recommended way anyway ?

I don't think so. Anyway, it complicate stuff.
A nice option is I provide a list modules like this and webpack create this static bundle itself.
I'm not sure we can do it with a plugin or not.

This implementation makes it one step closer to slimmer apps, but how would you recommend to handle the use-case when there are groups of pages having heavy dependencies? Here is an example:
I have an app, which uses UI framework (e.g. React-MD), so it makes sense to bundle it into static. Then, I have a submodule with a few pages, which heavily use charts, so I use a charting library and I want it to be a common dependency for the submodule. And just for the sake of example, there is another submodule with a few pages, which makes heavy map interactions. Thus, charts are only relevant to the first submodule, and maps are only relevant to the second. Putting those into the static ruins the whole point of code-splitting...

@frol yes. Basically you've to balance between moving to static bundle or keeping them in each page. And we'll have dynamic imports(#728)  soon. That'll also helps on this matter.

It is unfortunate that this is marked as 2.1 feature because 2.0 hasn't even released yet, so it sounds like a "far future". However, for the "far future" I would love to see a more flexible implementation, e.g. it would be nice if you can specify "sub-static" bundles in addition to static bundles, which would be shared with just a few of the pages (dynamic imports are still nice, but the out of the box solution for intelligent bundling is nicer).


Add new initial fields to v20240812preview

Which issue this PR addresses:

Fixes https://issues.redhat.com/browse/ARO-4381 && https://issues.redhat.com/browse/ARO-4377, unblocks https://issues.redhat.com/browse/ARO-3979
What this PR does / why we need it:
This is the first of 3-ish PRs to add new fields to the preview API + converter. There will be additional fields added to support OCP upgrades as well as Cluster MSI.

Test plan for issue:

Is there any documentation that needs to be updated for this PR?

How do you know this will function as expected in production?

/azp run ci,e2e

/azp run ci,e2e

/azp run ci, e2e

@s-amann should be good now, thanks for pointing that out!

/azp run ci,e2e


M3-1344 In the mutation drawer, bold the new GB offering

Coverage remained the same at 26.248% when pulling 82cdd87de81ae6d5d03c622be5de37673b5f4e62 on WilkinsKa1:M3-1344-boldGB into 8f7aba6790214958419b6ce0e145838e0abbe42e on linode:develop.

@martinmckenna I reverted back to the original values!


feat: allow to customize the namespace

add a new -namespace flag to set a custom namespace - no impact for existing users, because we keep the same default value

Hey @vbehar! Thanks for the PR. I would like to wait until we land #120 before adding the namespace flag as it'll significantly change the way we're handling flags and the config.
Cc @rakshitgondwal

ok sure.

 Are you ok to rework this PR a bit to fit the new model? If you need any help or have questions feel free to reach out to @rakshitgondwal or I on slack, or in the #hydrophone channel.

 Are you ok to rework this PR a bit to fit the new model? If you need any help or have questions feel free to reach out to @rakshitgondwal or I on slack, or in the #hydrophone channel.

yes, I'll do it today or tomorrow

I'm closing this one, see https://github.com/kubernetes-sigs/hydrophone/pull/139 instead (rebased against main)