Fix check for images which are too small to scale

Images with width == min_width are not too small.
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

@Shreeshrii, this also affects the results of the UNLV tests. The results now look more consistent, but the recognition rates are slightly worse. This is caused by images with vertical lines. Tesseract fails to remove them, so they are often "detected" as a | character. With this pull requests some more are detected like that.
Example:
--- unlvtests/old/doe3.3B/5373_008.3B.unlv       2019-02-14 17:25:52.783598953 +0100
+++ unlvtests/new/doe3.3B/5373_008.3B.unlv       2019-02-15 10:52:56.196964557 +0100
@@ -4,9 +4,9 @@
 Year| Date | Time i Locali Given| N. : Ww. 5 ,ghrea | Hlaximum | Ded i
 | te | pst. cality Mag. | Lat. Long. | oar | fensity wie D. Db:
 | |S -_ | ro
-1906 | 04-18 | 05: 12.0 NW of San Francisco 8.3 138 | 123 ~; 375,000 | XT. 17.8 | 0.8 | 0.25
+1906 | 04-18 | 05: 12.0 | NW of San Francisco 8.3 138 | 123 ~; 375,000 | XT. 17.8 | 0.8 | 0.25
 1915 10-02 | 22:52.8 Pleasant Valley, Nev. 7.6 40.5 | 117.85 500,000 | XN. | 7.5 OL | OOL
-1927 | 09-17 | 18:07:07 | Near Bishop 6.0 | 37.5 | 118.75 | 75,000 | VII. P.$ 10.4 | 0.16
+1927 | 09-17 | 18:07:07 | Near Bishop | 6.0 | 37.5 | 118.75 | 75,000 | VII. P.$ 10.4 | 0.16
 1930 | 01-15 | 16:24 | Fawnskin and Summit 5.2 | 34.2 | 116.9 50,000 | VII. 6.1 i-0.9: 0.81
 1930 | 02-25 | 18:30 | Imperial Valley | 5.0 | 33 | 115.5 | 20,000 | VIII. | 5.6 |~0.6 | 0.36
 1930 | 03-01 | 15:44 | Imperial Valley 4.5 | 33 115.5 | 11,000 | VIII. | 5.2 1-0.7 | 0.49

Could you attach the image?

5373_008.3B.zip

@stweil What's the difference between .unlv output and .txt output from tesseract?


[SPARK-19721][SS] Good error message for version mismatch in log files

Problem
There are several places where we write out version identifiers in various logs for structured streaming (usually v1). However, in the places where we check for this, we throw a confusing error message.
What changes were proposed in this pull request?
This patch made two major changes:

added a parseVersion(...) method, and based on this method, fixed the following places the way they did version checking (no other place needed to do this checking):

HDFSMetadataLog
  - CompactibleFileStreamLog  ------------> fixed with this patch
    - FileStreamSourceLog  ---------------> inherited the fix of `CompactibleFileStreamLog`
    - FileStreamSinkLog  -----------------> inherited the fix of `CompactibleFileStreamLog`
  - OffsetSeqLog  ------------------------> fixed with this patch
  - anonymous subclass in KafkaSource  ---> fixed with this patch

changed the type of FileStreamSinkLog.VERSION, FileStreamSourceLog.VERSION etc. from String to Int, so that we can identify newer versions via version > 1 instead of version != "v1"

note this didn't break any backwards compatibility -- we are still writing out "v1" and reading back "v1"

Exception message with this patch
java.lang.IllegalStateException: Failed to read log file /private/var/folders/nn/82rmvkk568sd8p3p8tb33trw0000gn/T/spark-86867b65-0069-4ef1-b0eb-d8bd258ff5b8/0. UnsupportedLogVersion: maximum supported log version is v1, but encountered v99. The log file was produced by a newer version of Spark and cannot be read by this version. Please upgrade.
	at org.apache.spark.sql.execution.streaming.HDFSMetadataLog.get(HDFSMetadataLog.scala:202)
	at org.apache.spark.sql.execution.streaming.OffsetSeqLogSuite$$anonfun$3$$anonfun$apply$mcV$sp$2.apply(OffsetSeqLogSuite.scala:78)
	at org.apache.spark.sql.execution.streaming.OffsetSeqLogSuite$$anonfun$3$$anonfun$apply$mcV$sp$2.apply(OffsetSeqLogSuite.scala:75)
	at org.apache.spark.sql.test.SQLTestUtils$class.withTempDir(SQLTestUtils.scala:133)
	at org.apache.spark.sql.execution.streaming.OffsetSeqLogSuite.withTempDir(OffsetSeqLogSuite.scala:26)
	at org.apache.spark.sql.execution.streaming.OffsetSeqLogSuite$$anonfun$3.apply$mcV$sp(OffsetSeqLogSuite.scala:75)
	at org.apache.spark.sql.execution.streaming.OffsetSeqLogSuite$$anonfun$3.apply(OffsetSeqLogSuite.scala:75)
	at org.apache.spark.sql.execution.streaming.OffsetSeqLogSuite$$anonfun$3.apply(OffsetSeqLogSuite.scala:75)
	at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22)
	at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85)

How was this patch tested?
unit tests

Test build #73476 has started for PR 17070 at commit dcae69b.

Test build #73476 has finished for PR 17070 at commit dcae69b.

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

Merged build finished. Test PASSed.

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

This is changing a lot of stuff to barely improve an error, and the PR has problems. I don't think this is worthwhile

Test build #73487 has started for PR 17070 at commit 18f77b0.

@srowen thank you for the comments! I was trying to tackle SPARK-19721, sorry the summary just said "WIP" without a JIRA number; adding JIRA number back.

Test build #73487 has finished for PR 17070 at commit 18f77b0.

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

Merged build finished. Test PASSed.

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

/cc @zsxwing

@zsxwing would you take a look when you've got a minute? Thanks!

Jenkins retest this please

Test build #74063 has started for PR 17070 at commit 18f77b0.

Test build #74063 has finished for PR 17070 at commit 18f77b0.

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

Merged build finished. Test PASSed.

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

@zsxwing would you take a look when you've got a minute? Thanks!

Test build #74648 has started for PR 17070 at commit 32c0017.

Test build #74648 has finished for PR 17070 at commit 32c0017.

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

Merged build finished. Test PASSed.

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

LGTM. Merging to master and 2.1. Thanks!

@lw-lin there are conflicts with 2.1. Could you submit a new PR for branch-2.1?

@zsxwing sure, please see https://github.com/apache/spark/pull/17327


[main] Upgrade to latest dependencies

fix wrong version on main (https://cloud-native.slack.com/archives/C04LY4Y3EHF/p1729776009449449?thread_ts=1729763678.995479&cid=C04LY4Y3EHF) -ReToCode
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads
Produced by: knative-extensions/knobots/actions/update-deps

/lgtm
/approve


Using dll in the Unity but can't subscribe

Hello. I met a situation with SubscribeCharacteristic()  when I try it in the Unity in PC. I had got the deviceId, serviceId and characteristicId， and try to subcribe it. But it return false when I used BleApi.SubscribeCharacteristic(selectedDeviceId, selectedServiceId, selectedCharacteristicId, false);
And in the while loop:BleApi.PollData(out res, false) never gets true.
I used the dll in the form C# program, which is good running.
is there some important things I lost?

Now I am updating this question: when the code is running in the unity if you have the same questions like can't subscribe the characteristic, the while loop can't break, don't be worried and try to use write()  something then you may see a good result.
This project is so excellent!
Thanks a lot!


how to sample the sub-network while training?

how to sample the sub-network while training?  I random sample the sub-network every batch, but always get loss NAN

It needs to be implemented in train.py and mmcv for sampling, and we will post the search code for details.

@tingtingliangvs any plans?

Thank you for your attention, and a more concise search code version 2.0 will be released in a month.


Version conflict with latest MTK (9.19.0).

There is a version conflict with latest MTK (9.19.0).
julia version 1.10.4
how to reporduce:

create a new project
add ModelingToolkit
pin ModelingToolkit
add EasyModelAnalysis

(@v1.10) pkg> add EasyModelAnalysis
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Turing [fce5fe82]:
 Turing [fce5fe82] log:
 ├─possible versions are: 0.5.0-0.33.0 or uninstalled
 ├─restricted by compatibility requirements with EasyModelAnalysis [ef4b24a4] to versions: [0.22.0-0.24.4, 0.30.0-0.30.9]
 │ └─EasyModelAnalysis [ef4b24a4] log:
 │   ├─possible versions are: 0.0.1-1.0.0 or uninstalled
 │   ├─restricted to versions * by an explicit requirement, leaving only versions: 0.0.1-1.0.0
 │   └─restricted by compatibility requirements with ModelingToolkit [961ee093] to versions: 1.0.0 or uninstalled, leaving only versions: 1.0.0
 │     └─ModelingToolkit [961ee093] log:
 │       ├─possible versions are: 0.0.1-9.19.0 or uninstalled
 │       └─restricted to versions 9.19.0 by an explicit requirement, leaving only versions: 9.19.0
 ├─restricted by compatibility requirements with SciMLBase [0bca4576] to versions: [0.5.0-0.18.0, 0.29.2-0.33.0] or uninstalled, leaving only versions: 0.30.0-0.30.9
 │ └─SciMLBase [0bca4576] log:
 │   ├─possible versions are: 1.0.0-2.41.3 or uninstalled
 │   ├─restricted by compatibility requirements with ModelingToolkit [961ee093] to versions: 2.28.0-2.41.3
 │   │ └─ModelingToolkit [961ee093] log: see above
 │   └─restricted by compatibility requirements with ADTypes [47edcb42] to versions: [1.0.0-1.92.0, 2.34.0-2.41.3] or uninstalled, leaving only versions: 2.34.0-2.41.3
 │     └─ADTypes [47edcb42] log:
 │       ├─possible versions are: 0.1.0-1.3.0 or uninstalled
 │       ├─restricted by compatibility requirements with SciMLBase [0bca4576] to versions: 0.2.5-1.3.0
 │       │ └─SciMLBase [0bca4576] log: see above
 │       └─restricted by compatibility requirements with Symbolics [0c5d862f] to versions: 1.0.0-1.3.0
 │         └─Symbolics [0c5d862f] log:
 │           ├─possible versions are: 0.1.0-5.30.3 or uninstalled
 │           └─restricted by compatibility requirements with ModelingToolkit [961ee093] to versions: 5.30.1-5.30.3
 │             └─ModelingToolkit [961ee093] log: see above
 └─restricted by compatibility requirements with ADTypes [47edcb42] to versions: [0.5.0-0.29.3, 0.31.3-0.33.0] or uninstalled — no versions left
   └─ADTypes [47edcb42] log: see above

@jClugstor this is due to the Turing version. Can you make sure that gets updated to Turing latest?

https://github.com/SciML/EasyModelAnalysis.jl/pull/259
This should fix it. Only problem seems to be codecov, tests all pass locally.


Update xGroup to have a different key

At the moment the "GroupName" is the key of xgroup.
We have the problem of i can't use xGroup twice in my config because i'm trying to add 2
use case:
We use composite resources, we have a basic config anything that has to be applied to ALL Servers goes in here.
in here we have resource
xGroup AddLocalAdminToAdministrators
{
GroupName = 'Administrators'
Ensure='Present'
MembersToInclude='CompanyAdmin'
}
One of our application servers requires a different user account be in part of the admin group. so in the config for that server it would firstly call the Server composite resource and then we would have ANOTHER resource as below
xGroup AddAppAccounttoAdministrators
{
GroupName = 'Administrators'
Ensure = 'Present'
MembersToInclude = 'ApplicationAdminAccount'
}
This will not compile because there are 2 resources with the same key.
I don't know what the solution to this would be and whether there are other people using DSC the same way or not to have this problem. I have a workaround (pass extra admin accounts through to the composite resource) but it's not as clean

@DamianBis GroupName is the logical key for a Group so it will not be changed.
This is a limitation of all DSC resources, not just xGroup specifically.
The DSC LCM (engine) doesn't know how to deal with resource conflicts.
Imagine if we allowed you to specify to same Group twice, both with the Members property rather than MembersToInclude.
They would conflict because you were trying to specify two different states the group should be in at the same time.
Of if you specified two resources with the same group name and one had a member in MembersToExclude and the other had the same member in MembersToInclude.
The DSC LCM wouldn't know what to do.
I've asked the DSC team if there is any workaround for what you are trying to do, but these two resources cannot be defined in the same configuration.
Sorry 😞


Inlcude geofence name in MQTT

It would be nice to be able to access the current geofence (if any) via MQTT topic. If the vehicle is currently not in a geofence, the value would be empty.
As teslamate is already determining if the vehicle is in a geofence, this keeps the list of geofences and the calculation logic in one location when integrating with other systems, like HomeAssistant.
My use case is in home automation (HomeSeer), where I would like to be notified if the car is at home, has a low state of charge and is not plugged in. I currently have access to all the necessary values from teslamate except for the named location.

Check this out: teslamate/cars/$car_id/geofence. Is this what you're looking for?

Ah, yes, that will do. When I was looking for something related to geofence, the car wasn't inside the fence, so it wasn't showing up. Thanks for the quick reply!

You should actually receive such a message. But it could depend on the client how messages with an empty payload are handled. MQTT.fx, for example, shows said messages.

Thanks for the explanation. For some reason my client isn't picking that up, but I did see it in MQTT.fx.


[AutoPR compute/resource-manager] Modify Gallery Swagger According To Feedback

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3175

(message created by the CI based on PR content)

Codecov Report

Merging #2685 into restapi_auto_compute/resource-manager will decrease coverage by 1.24%.
The diff coverage is 44.66%.

@@                            Coverage Diff                            @@
##           restapi_auto_compute/resource-manager    #2685      +/-   ##
=========================================================================
- Coverage                                  55.47%   54.22%   -1.25%
=========================================================================
  Files                                       7572     5821    -1751
  Lines                                     169132   134351   -34781
=========================================================================
- Hits                                       93827    72855   -20972
+ Misses                                     75305    61496   -13809

Impacted Files
Coverage Δ

..._01/operations/virtual_machine_sizes_operations.py
26.47% <ø> (ø)

...18_04_01/operations/virtual_machines_operations.py
12.86% <ø> (ø)

...perations/virtual_machine_scale_sets_operations.py
11.76% <ø> (ø)

...te/azure/mgmt/compute/compute_management_client.py
47.69% <0%> (-5.23%)
:arrow_down:

...18_04_01/models/compute_management_client_enums.py
100% <100%> (ø)
:arrow_up:

...re/mgmt/compute/v2018_04_01/operations/__init__.py
100% <100%> (ø)
:arrow_up:

.../azure/mgmt/compute/v2018_04_01/models/__init__.py
100% <100%> (ø)
:arrow_up:

...ations/virtual_machine_scale_set_vms_operations.py
14.1% <14.1%> (ø)

...ompute/v2018_04_01/operations/images_operations.py
14.45% <14.45%> (ø)

...8_04_01/operations/availability_sets_operations.py
14.61% <14.61%> (ø)

... and 3308 more

Continue to review full report at Codecov.

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

@AutorestCI rebase

Rebase done and pushed to the branch


Adding a BitmapFont as a Custom Font in Project Settings causes errors

Godot version
3.4
System information
Windows 10, NVIDIA GeForce RTX 2080, GLES3
Issue description
In Godot 3.4, adding a BitmapFont as a Custom Font in the Project Setting's gui/theme/custom_font section causes errors when reopening the project. The same happens if a BitmapFont is added to a Theme which is then used in the gui/theme/custom section. This works in Godot 3.3.4

Steps to reproduce
Open the provided project and see the errors in the console.
Minimal reproduction project
BitmapFontBug.zip

Related to https://github.com/godotengine/godot/issues/36614. See https://github.com/godotengine/godot/issues/36614#issuecomment-592177855 for a workaround.

Thanks, I've added the theme to a root Control node as a workaround.

This is actually the same issue as https://github.com/godotengine/godot/issues/54752, which will be fixed by https://github.com/godotengine/godot/pull/55483. The problem is not with fonts, it's with loading images.


Updated to v1.0.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

The token here is expired. Please see the "Near term" plan on how to fix this.

Thanks, I will do this and close this PR for now

Sorry if I gave you the impression this should be closed. It can certainly be open. Just encouraging you to resubmit the recipe in master to staged-recipes so that the token can be updated in the feedstock.

I merge this now because the failed tests on appveyor only came from CondaHTTPError (see
appveyor build 1.0.8


Update README.md

@danielreed Can you also review this PR? As a native speaker, your feedback is very important.

@danielreed
I've made all the changes you suggested. Can you check again?

@marikrg The changes look good, I'll merge the PR.


[Public Doc Update request] - Enable SSH in custom containers - Handshake Error: no matching host key format

Hello Azure Docs team,
I'm getting this error when my custom Alpine container is deployed to Azure App Service and then try to SSH into it:

It appears the current script for ssh_setup.sh does not meet the host key format required by KUDU SSH.
#!/bin/sh

if [ ! -f "/etc/ssh/ssh_host_rsa_key" ]; then
    # generate fresh rsa key
    ssh-keygen -f /etc/ssh/ssh_host_rsa_key -N '' -t rsa
fi

if [ ! -f "/etc/ssh/ssh_host_dsa_key" ]; then
    # generate fresh dsa key
    ssh-keygen -f /etc/ssh/ssh_host_dsa_key -N '' -t dsa
fi

if [ ! -f "/etc/ssh/ssh_host_ecdsa_key" ]; then
    # generate fresh ecdsa key
    ssh-keygen -f /etc/ssh/ssh_host_ecdsa_key -N '' -t dsa
fi

if [ ! -f "/etc/ssh/ssh_host_ed25519_key" ]; then
    # generate fresh ecdsa key
    ssh-keygen -f /etc/ssh/ssh_host_ed25519_key -N '' -t dsa
fi

#prepare run dir
    if [ ! -d "/var/run/sshd" ]; then
    mkdir -p /var/run/sshd
fi

That issue can be resolved replacing the whole script for ssh-keygen -A. For some reason, the default keys generated by -A are accepted by KUDU SSH.
Currently running the image FROM node:alpine in my container, Alpine version 3.15.0. Here is the project I'm using to test this out: juniorj-webappexample-sshd.
I discussed this situation with my technical advisor and looks like enable SSH section is a bit outdated. For the reasons above, I would like to suggest the following:
Update request:
Is it possible to change the current ssh_setup.sh script in the official doc for ssh-keygen -A? since this line does not cause the handshake error not matching the host key format when the web app is deployed to Azure, and lets you SSH the container with no issues from KUDU.
Thanks.

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

ID: 1d385179-7730-3b99-aff6-75491deb070a
Version Independent ID: 7da429ea-5421-9d99-3e7c-af1b3fee5ca8
Content: Configure a custom container - Azure App Service
Content Source: articles/app-service/configure-custom-container.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Thanks for the feedback! We are currently investigating and will update you shortly.


Command for deleting members one by one

Question about:

[x] Specific command: Please specify command [ member delete ]
[ ] Instruction / document
[ ] Other

Additional context
Is there any way to delete members in Dropbox Business one-by-one (comparable to suspend / unsuspend member commands) in order to set individual destination members?
Unfortunately, our login names for Dropbox Business differ from the normal e-mail-addresses.
Therefore many of our users register for a second business account in our team.
We would like to remove those duplicates and transfer the data to the 'correct' account.
Looking forward to your reply, kind regards
Robert
P.S.: Sorry, if this issue may be in the wrong category - perhaps ist should be tagged as feature request?

Hi. Thank you for the question.
Here is the manual for member delete. But currently, the command only accepts CSV file to delete the member. And the CSV file does not support individual destination member.
https://toolbox.watermint.org/commands/member-delete.html
If you want to delete a member one-by-one, you can pass CSV data through standard input by passing - to the -file argument.
echo<EMAIL_ADDRESS>| tbx member delete -file - -transfer-dest-member<EMAIL_ADDRESS>

Hi, thank you very much for your fast reply.
So when I as an admin want to delete member<EMAIL_ADDRESS>and transfer his files to his account<EMAIL_ADDRESS>on a Windows client, the command line is
echo<EMAIL_ADDRESS>| .\tbx.exe member delete -file - -transfer-dest-member<EMAIL_ADDRESS>-transfer-notify-admin-email-on-error<EMAIL_ADDRESS>Is this correct? Or are there other specifications for Windows clients?
Looking forward to yor reply, kind regards,
Robert
P.S.: Are there any changes concerning this command planned in the upcoming versions of watermint?

@watermint - sorry for any inconvenience but did I get your last comment right?
Is this the correct command in toolbox to delete a single user and to transfer his files to another account?
echo<EMAIL_ADDRESS>| .\tbx.exe member delete -file - -transfer-dest-member<EMAIL_ADDRESS>-transfer-notify-admin-email-on-error<EMAIL_ADDRESS>Looking forward to your reply, kind regards,
Robert

Hi. I believe that should work. There is no immediate plan to changing command related this. Please reopen the issue if you got unexpected result. Thanks

Hi,
thank you very much - I just tested it with an account and it seems to work.
If we meet some unexpected results with further users, I will contact you again.
Just one additional info on the command line mentioned above:
echo<EMAIL_ADDRESS>.\tbx.exe member delete -file - -transfer-dest-member<EMAIL_ADDRESS>-transfer-notify-admin-email-on-error<EMAIL_ADDRESS>At least on my Windows client, there must be no space between the echo command and the pipe, otherwise the command results in a failure stating
Error: Error in call to API function "team/members/get_info": request body: members<EMAIL_ADDRESS>' did not match pattern '^['#&A-Za-z0-9._%+-]+@[A-Za-z0-9-][A-Za-z0-9.-]*.[A-Za-z]{2,15}$'


Don't run empty commands (including comments)

This PR makes sure the REPL ignores empty commands, including comment-only commands.
This is useful if you want to give yourself some visual space by typing Enter several times.
It's also useful if you want to write some comments for educational purposes.
Before
»                [I just typed Enter here]

Enter an expression to evaluate, or a definition (like x = 1) to use later.

  - ctrl-v + ctrl-j makes a newline
  - :q quits
  - :help shows this text again

» # You can do plenty of things in the Roc REPL,
… # including arithmetic:

Enter an expression to evaluate, or a definition (like x = 1) to use later.

  - ctrl-v + ctrl-j makes a newline
  - :q quits
  - :help shows this text again

» 2 * 3

6 : Num *
»

After
»

» # You can do plenty of things in the Roc REPL,
… # including arithmetic:

» 2 * 3

6 : Num *

I also replaced line.trim() with line.trim_end(), because the spaces don't hurt, and sometimes you want to keep those spaces for visual purposes, for example:
»         ############
… 2 * 3   # AMAZING! #
…         ############

6 : Num *

I'm not sure why this PR is failing, it looks like the failure is due to some other change, unrelated to this PR. Wdyt?


Width of slides isn't set if the slide is React component

If I do a regular slide, per docs, everything works fine:
    <Swiper>

Awesome slide

Awesome slide

Awesome slide

    </Swiper>

However, if I try to encapsulate the slide in a component, like so:
        function MyComponent(props) {
          return
Awesome slide

        }

        <Swiper>
          <MyComponent/>
          <MyComponent/>
          <MyComponent/>
        </Swiper>

Then the whole Swiper gets broken - I see all slides at once. It seems to be happening because Swiper doesn't set the width of the div inside the components in this case.
The only solution I found is something like that:
    <Swiper>

<MyComponent/>

<MyComponent/>

<MyComponent/>

    </Swiper>

I thought that perhaps MyComponent would be getting the width as a prop and I could propagate to its children. However, there is no such prop.
Since I assume the issue stems from the original, non-react, library, how about a fix that does the following:

Goes over every provided child
Wraps it in a div

Source
https://github.com/vitalybe/react-test/tree/react-id-swiper-component-width-broken
Screenshot of the issue

Hi @vitalybe ,
I also faced this problem before. Still finding the way to solve. If u have any idea, pls let me know

Personally, I think the fix is to wrap your children in a  like you've done @vitalybe.
Digging deeper would be to investigate why [https://github.com/kidjp85/react-id-swiper/blob/fda12d3ccc0fd7f781a84d35bb1c917b03067d0a/src/index.js#L466](this line) doesn't just pass through any child component.

Yeah, I did it in a more generic way though eventually:
class FixedSwiper extends Component {
  render() {
    return (
      <Swiper>
        {this.props.children.map(child => {
          return
{child}
;
        })}
      </Swiper>
    );
  }
}

So I can use it like so:
    <FixedSwiper>
      <MyComponent />
      <MyComponent />
      <MyComponent />
    </FixedSwiper>

Source:
https://github.com/vitalybe/react-test/blob/2b0c45d08fa5579fdb0b6312fcfa7b518608b2b5/src/App.js

I tried this before too. But I didn't put in lib file, because I don't wanna to wrap children component in a specific wrapper like div

Yeah, wrapping could cause more issues than it solve. Like making SEO issues worse and I'm trying to fix current SEO issues in this PR: https://github.com/kidjp85/react-id-swiper/pull/120
I do it like @vitalybe and it's working just fine. I'm rendering div in my component and wrapping them with lis when rendering Swiper children.


How do you remove "have I been pwned" from all entries?

How do you remove "have I been pwned" from all entries?
I no longer wish to use the plugin, I removed the plugin but there's leftover string field for have I been pwned.
How can I remove the string field from all entries?

This plugin doesn't modify your existing entries in any way. Did you maybe use this plugin https://github.com/mihaifm/HIBPOfflineCheck as that does appear to add a new field to your entries?

Perhaps I have, sorry. I think I looked at this one, but I'm worried about anything calling out from a password manager so looked for an offline version.


put version and run.py in the same folder

I do not really understand the error, I will try to put the files version and run.py in the root folder...


Parser Bug

The following command fails to parse correctly
echo "teswt" fdsafd"
It is a runtime error.
The parser should not allow a string which doesn't have equal " in it.

Will keep this open, but as of now it is not reproducible.


ImageDecoder

Assigned to @vinayakdsci

Is there a plan for this one? https://onnx.ai/onnx/operators/onnx__ImageDecoder.html looks out of scope for compiler codegen to me...

Loads and decodes and image from a file. If it can’t decode for any reason (e.g. corrupted encoded stream, invalid format, it will return an empty matrix). The following image formats are supported:

BMP
JPEG (note: Lossless JPEG support is optional)
JPEG2000
TIFF
PNG
WebP

@ScottTodd can't we simply treat the image as a (H,W,C) shaped tensor of uint8 values?. We would then only need to check for the pixel format.

The op loads from encoded image files in any of those formats. Those formats are incredibly complicated and working with them is nearly always delegated to external libraries, platform APIs, or hardware decoders. This is the sort of thing that inference frameworks usually leave to higher level APIs, or include via plugins - not something that the compiler would generate code for directly.
ImageDecoder isn't even implemented in onnxruntime yet: https://github.com/microsoft/onnxruntime/issues/17593. When the op was added to ONNX in https://github.com/onnx/onnx/pull/5294, the author said "I was hoping that the ORT team will handle the implementation. It should be simple using a library such as OpenCV.". Simple... yeah, right, just take a dep on another framework that doesn't even exist on many platforms :P

The op loads from encoded image files in any of those formats. Those formats are incredibly complicated and working with them is nearly always delegated to external libraries, platform APIs, or hardware decoders. This is the sort of thing that inference frameworks usually leave to higher level APIs, or include via plugins - not something that the compiler would generate code for directly.
ImageDecoder isn't even implemented in onnxruntime yet: microsoft/onnxruntime#17593. When the op was added to ONNX in onnx/onnx#5294, the author said "I was hoping that the ORT team will handle the implementation. It should be simple using a library such as OpenCV.". Simple... yeah, right, just take a dep on another framework that doesn't even exist on many platforms :P

Ah, my first thought regarding the implementation was that it would recieve the tensor after loading the image, and not make loading that a part of the implementation at all. The user would call into the op after they had loaded the image, maybe by the use of a library like PIL. But you seem to be right here, it appears to be difficult to work with without delegating to an external library.
So what do you suggest? Is it worth a stab or not?

If the goal is just to claim support for the op, I wouldn't bother with this one.
If the goal is to solve a specific customer request, I'd look deeper at how the op is used and find other ways to solve their problem.

HI @vivekkhandelwal1,  This op is almost impossible to implement without the use of external libraries to read in the supported image formats, owing to their complexity.
The following is a rough sketch of the implementation:

The op takes in a 1-D tensor of bytes(uint8 values) that represent the image(in one of the formats that are supported).
Then it loads the image(the reference implementation uses PIL in python for this), which converts it to a tensor of shape [height, width, num_channels] and dimension 3.
Once this has been done, an output decoded image of the same shape as the converted tensor is built based on what pixel_format was passed in.

The step (2) is unfeasible to implement without the use of an external library like OpenCV. My initial thought was that we could bypass the process of loading the image into a tensor, and leave that for the user to do, so that we would then expect a 3-D tensor as input.
However, this would make it impossible to write e2e tests, for which the onnx back end due to its shape inference would not allow a 3-D input, and a 1-D image array in one of the supported formats is expected.
What do you think is the way forward? Should we skip the e2e tests and make do with the lit tests then? Or drop support for this op altogether?

My initial thought was that we could bypass the process of loading the image into a tensor, and leave that for the user to do, so that we would then expect a 3-D tensor as input.

That would be changing the semantics of the op to the point that there is very little left of the original definition. If a user needs to change their program to use this toolchain, have them change their model. Don't change the semantics of an op just to claim support for it.

Should we skip the e2e tests and make do with the lit tests then?

IDK. You can do a surface level import of the onnx op into torch-mlir and test that translation, but if no backend will be able to run the op then I don't see the point. Are there backends for torch-mlir (other than IREE) that could support this op?

That would be changing the semantics of the op to the point that there is very little left of the original definition.

Yes, that is the primary point of concern, aside from the difficulties with e2e tests.

Are there backends for torch-mlir (other than IREE) that could support this op?

No, none that I am aware of at the moment that would allow for an easier implementation.
The thing is, even the lit tests are reduced to just checking against the pixel_format and performing basic array operations independent of the file format, so much so that the op feels too much bare of useful functionality.
Still, let us also wait to hear what @vivekkhandelwal1's opinion on the matter is.
Thanks!

HI @vivekkhandelwal1, This op is almost impossible to implement without the use of external libraries to read in the supported image formats, owing to their complexity.
The following is a rough sketch of the implementation:

The op takes in a 1-D tensor of bytes(uint8 values) that represent the image(in one of the formats that are supported).
Then it loads the image(the reference implementation uses PIL in python for this), which converts it to a tensor of shape [height, width, num_channels] and dimension 3.
Once this has been done, an output decoded image of the same shape as the converted tensor is built based on what pixel_format was passed in.

The step (2) is unfeasible to implement without the use of an external library like OpenCV. My initial thought was that we could bypass the process of loading the image into a tensor, and leave that for the user to do, so that we would then expect a 3-D tensor as input. However, this would make it impossible to write e2e tests, for which the onnx back end due to its shape inference would not allow a 3-D input, and a 1-D image array in one of the supported formats is expected.
What do you think is the way forward? Should we skip the e2e tests and make do with the lit tests then? Or drop support for this op altogether?

I'm not very sure, if we would ever need this op. But to claim the ONNX op support right now we can just go ahead with a lit test and skip the e2e test for now. (If required, we will revisit this op later)

Resolved by https://github.com/llvm/torch-mlir/pull/3478.

Hi @vinayakdsci, since we've dropped the plan for supporting this op for now, so I'm closing the issue and the corresponding PR. If needed, we can revisit this later.


Emojis do not appear in the chat

Emojis are not displayed in the application window or in the chat. Instead it shows the name of the icon of the type :face_with_tongue:
I am using version 1.4.1-beta.
Greetings and thanks for the work!

Yeah, we'll probably be fixing that issue on the next update.
The problem is, these emojis aren't what we call "Unicode" emojis. So the emoji 🙄 for example is a Unicode emoji and it will display on Twidget. But youtube has emojis that are very specific to youtube and they're not technically emojis, they're actually rendered as images. And each channel can upload its own custom youtube emojis so this issue just gets quite complicated.
Ideally, though, we should add some code to the app that detects the ": :" symbols and then match it with a list of youtube emojis.


Allow an array instead of a single value

Description
Currently, each function returns a single value. We should give the option to return an array of values.
Proposed solution
Create a proxy function and use it in each one of the function generators:
export function cat(options?: FakeOptions) {
  return fake(catsData, options)
}

// core.ts
export interface FakeOptions {
  size: number
}

export function fake(options?: { size: 10 } ) {
  return ...
}

Alternatives considered
No response
Do you want to create a pull request?
No

As of API. I would consider to have a plural method for this
e.g.
import { randomNumber, randomNumbers } from 'falso'

randomNumber() // single number
randomNumbers({ size: 10 }) // array with 10 random numbers


inspec should be a meta role

each role should be responsible for its own inspecs, this enabled that by
setting inspec as a meta role, and demonstrates is use via keystone

retest

retest


[Feature Request] adding an Outpainting option to Lama Cleaner

Lama Cleaner serves me wonderfully.
I would like to suggest adding an Outpainting option to it. This way it will also be possible to expand images and not only work within their framework.
Is this on the to-do list?

And one more thing I wanted to say, if you can improve the model menu, using this model is kind of time consuming and I wanted to say that you should add the Lora model as well, for making this beautiful program, thank you.

This would be extremely helpful. Currently I have to switch to auto1111 just to outpaint, which is disappointing as lama-cleaner's inferface is much better overall for this type of task.


Add 0003-cmake-config-fix-library-suffix-and-prefix.patch to CppInterOp

@vgvassilev Here is the patch to CppInterOp so it picks the right suffix when finding the library.
@anutosh491 @JohanMabille can you review this PR for me please?

@DerThorsten are you able to merge this PR please?


[ffmpeg] add CMake targets to FindFFMPEG.cmake module

Describe the pull request

What does your PR fix?

missing CMake targets for ffmpeg. I ran into issues using ${FFMPEG_LIBRARIES} in a generator expression like $<$<BOOL:${USE_FFMPEG}>:${FFMPEG_LIBRARIES}> because ${FFMPEG_LIBRARIES} is a list. Using a target resolves that and also makes it easier to add the include directories.

Which triplets are supported/not supported?
I am still working on this PR and asking for help.

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/
At the end of the build, this is printed:
The package ffmpeg:x64-linux provides CMake targets:

    find_package(ffmpeg CONFIG REQUIRED)
    target_link_libraries(main PRIVATE FFMPEG::FFMPEG)

I am getting an error I don't understand when doing find_package(FFMPEG CONFIG REQUIRED) in the application's CMakeLists.txt:
CMake Error at /home/be/sw/vcpkg/installed/x64-linux/share/ffmpeg/vcpkg-cmake-wrapper.cmake:6 (_find_package):
  Could not find a package configuration file provided by "FFMPEG" with any
  of the following names:

    FFMPEGConfig.cmake
    ffmpeg-config.cmake

  Add the installation prefix of "FFMPEG" to CMAKE_PREFIX_PATH or set
  "FFMPEG_DIR" to a directory containing one of the above files.  If "FFMPEG"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /home/be/sw/vcpkg/scripts/buildsystems/vcpkg.cmake:736 (include)
  CMakeLists.txt:559 (find_package)

-- Configuring incomplete, errors occurred!

If I change it to find_package(ffmpeg CONFIG REQURIED) that does not work either:
CMake Error at /home/be/sw/vcpkg/installed/x64-linux/share/ffmpeg/vcpkg-cmake-wrapper.cmake:6 (_find_package):
  Could not find a package configuration file provided by "ffmpeg" with any
  of the following names:

    ffmpegConfig.cmake
    ffmpeg-config.cmake

  Add the installation prefix of "ffmpeg" to CMAKE_PREFIX_PATH or set
  "ffmpeg_DIR" to a directory containing one of the above files.  If "ffmpeg"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /home/be/sw/vcpkg/scripts/buildsystems/vcpkg.cmake:736 (include)
  CMakeLists.txt:559 (find_package)

-- Configuring incomplete, errors occurred!

CI failures seem to be unrelated?

Working on another port, it seems vcpkg has issues if the target exported by a CMake config file from a library's build system does not exactly match the port's name, including the case I guess.

I think it's a great idea to provide a target.

I am getting an error I don't understand when doing find_package(FFMPEG CONFIG REQUIRED) in the application's CMakeLists.txt:

There's a simple explanation for this. CMake has two methods for finding packages: via FindXXX.cmake, or via XXXConfig.cmake. Currently FFmpeg uses the FindXXX method for historical reasons, although it probably should switch to a XXXConfig.cmake system (at least in my opinion). Using the "CONFIG" option forces cmake to look only for the XXXConfig.cmake script which obviously fails since it does not exist.
Not related to the suggested changes but related to the topic of the PR, note that, if you want to get targets, you can also import ffmpeg using pkgconfig. This has the added flexibility that you can directly specify which components of ffmpeg you want to link to (and even their individual versions). For example:
find_package(PkgConfig REQUIRED)
pkg_check_modules(AVFORMAT REQUIRED IMPORTED_TARGET libavformat libswresample)
add_executable(main main.cpp)
target_link_libraries(main PRIVATE PkgConfig::AVFORMAT)

For this to work on windows, you need to manually point cmake to recognize pkgconf on windows; for instance:
vcpkg install pkgconf:x64-windows
set PKG_CONFIG=c:\vcpkg\installed\x64-windows\tools\pkgconf\pkgconf.exe

Currently FFmpeg uses the FindXXX method for historical reasons, although it probably should switch to a XXXConfig.cmake system (at least in my opinion). Using the "CONFIG" option forces cmake to look only for the XXXConfig.cmake script which obviously fails since it does not exist.

Ah, that makes sense. I don't think I have seen FindXXXX.cmake modules in other vcpkg ports.
The motivation that lead to opening this PR is that I was having trouble linking FFmpeg in a generator expression:
$<$<BOOL:${USE_FFMPEG}>:${FFMPEG_LIBRARIES}>

That gave some strange errors that I don't recall. I think they were because ${FFMPEG_LIBRARIES} is a list. I couldn't figure out how to get that to work in a generator expression. So I modified the FindFFMPEG.cmake module in the application to create targets and changed it to:
$<$<BOOL:${USE_FFMPEG}>:FFMPEG::FFMPEG>

then it worked.

That gave some strange errors that I don't recall. I think they were because ${FFMPEG_LIBRARIES} is a list.

Sounds like a syntax issue. Have you tried putting quotes around the expression, e.g. "$<$<BOOL:${USE_FFMPEG}>:${FFMPEG_LIBRARIES}>"? I'm not sure if that will fix the problem, but might be worth a shot.

This would be nice to have but I'm not particularly motivated to continue working on this myself, so I'm closing this. I would appreciate if someone else picked this up though.


Fix minification issue with FilterString

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Fix blog post without description in blog posts list

Add description to Sprint 23 & disable excerpts for blog posts without introduction :bowtie:

Deploy preview for openbuildservice ready!
Built with commit 40a6bb875d743b9f2058dcb47eefc21f0d58478d
https://deploy-preview-171--openbuildservice.netlify.com


AlmaLinux support added

added support for AlmaLinux.
Without this changes, it uses 'centos' but check for version 7 fails.
yum has been replaced by dnf.

Thanks!


[ISSUE #4690]Supports gzip compression in response to HTTP requests.

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4691 (f9383f8) into master (23af5ff) will increase coverage by 0.14%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4691      +/-   ##
============================================
+ Coverage     66.43%   66.57%   +0.14%
- Complexity     8015     8023       +8
============================================
  Files          1109     1109
  Lines         32041    32029      -12
  Branches       2896     2892       -4
============================================
+ Hits          21285    21324      +39
+ Misses         9065     9011      -54
- Partials       1691     1694       +3

see 20 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[REEF-395] Implement ClassHierarchySerializer using Avro on the Java side

This addressed the issue by

Defining the avro schema for class hierarchy
Implementing the AvroClassHierarchy
Define ClassHierarchySerializer interface and implement an Avro version
Replace the class hierarchy serializer for the round trip tests
Leave TODO comments for the future issues to resolve when we revisit REEF-148
Mark the ProtocolBufferClassHierarchy class as deprecated

p.s.
There was an additional change for the types in Avro. By default, Avro uses CharSequence for the string field: In the Java code, we should convert the types between String and CharSequence all the time. I could change the configuration to use String for the string field in the pom.xml. There was only one class (org/apache/reef/io/network/naming/serialization/NamingLookupRequestCodec.java) that is affected by this change and the conflict was resolved by changing only one type.

I did a pass. One additional comment: There are many added //TODO comments linking this to ongoing work to remove protobuf support. For those: Please file the JIRAs that should resolve the TODO comments and add the JIRA id to the comment.

@jwang98052 can you also have a look? Does this look like it can be replicated in Tang.NET?

Schema looks looks good. .Net Tang can make the similar change with the shared schema. I can work on .Net side as we have .Net environment handy and it might be better to verify it by second person from .Net side. But if Yunseong likes to work on .Net, that is totally fine as well :)

@markusweimer @jwang Thanks for the kind reviews! I’ve addressed your comments except some issues which I left questions on a line note.

@jwang98052 Could I ask you a great favor to work on the .Net side? We lack of the .Net environment for development and testing at this moment. :(

@yunseong Sure, I can work on .Net side. That way, we would have more to discuss. Thanks!

There are some bugs in .Net Avro library. I am discussing it with Avro team now. So we need to separate proto buffer and Avro and keep them in parallel for a while.

I've made all the tests in the ClassHierarchyDeserializationTest to have the Avro version separately so that we can test both versions in parallel.

@markusweimer @jwang98052 Would we have more issues to tackle on this PR?

The code looks good.
The only problem is Hadoop.Avro has multiple issues. Even I have implemented .Net class hierarchy serializer, the conversion between AvroNode and ClassHierarchy works but serialization for file, byte[], etc still have issues. That would prevent us from integration testing and really use it in REEF.
For now, we have to keep using protobuffer for Class Hierarchy.
I would think we should merge the code for both java and C#. Once Hadoop.Avro resolve the issue, we can come back to test it and replace protobuffer with Avro implementation.
@markusweimer, what do you think?

We can merge this if it looks good. We only need to gate the removal of protobuf support on having all issues with Avro resolved on both sides. Otherwise, this runs the risk of becoming outdated with new pull requests being merged.

I will test and merge it.

Opps, committed abut forgot to push. Will do it with your latest comments.


Implement password salts

When an account is created a random salt should be generated and stored with the password. When the password hash is generated, the salt should first be concatenated to the actual password.

Marked "Actually-Playable" instead of "Actually-Better" because I'll like to implement this before I get a new round of testers.

Fixed on dev branch


Parameter to set overall maximum questions

I don't use this plugin much anymore because I never have time to get to the questions towards the end of the list.
Since I have a lot of sections, there's a lot of overhead to make this box make any sense. So I end up with a ton of questions.

I would like to set a global maximum of, say, 5 questions across all sections if possible. Although maybe the dice plugin would be better suited for this?

@fedderw Hi! Thank you for feedback.
Your suggestion sounds nice. I think, it can looks like "switch option" between custom template and global picking.
I think, that random picking should be default option and custom template should be advanced feature, which can be enabled by switcher.

Nice, that’s exactly the kind of thing I had in mind!
On Wed, May 18, 2022 at 5:32 AM Timur Sidoriuk @.***>
wrote:

@fedderw https://github.com/fedderw Hi! Thank you for feedback.
Your suggestion sounds nice. I think, it can looks like "switch option"
between custom template and global picking.
I think, that random picking should be default option and custom template
should be advanced feature, which can be enabled by switcher.
[image: image]
https://user-images.githubusercontent.com/20852534/169007591-31c84365-b161-4caf-8564-f06e25a792f8.png
—
Reply to this email directly, view it on GitHub
https://github.com/ShockThunder/RandomStructuralDiary/issues/3#issuecomment-1129787188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5C7FFFRW6E3HUGEMKEJMTVKS2KHANCNFSM5WFYC2IA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Will Fedder
Research Analyst, UBI Center
Email: @.***
Phone:<PHONE_NUMBER>

Implemented in version 1.1.0
Major launch bug fixed in 1.1.1
Please update the plugin version and try new functionality =)


List of Categories, Severity Levels, Urgency Levels

Would it be possible for to post a list of the possible NOAA categories, severity levels, and urgency levels in the wiki if you have this info available (or can get it) so these values can be used in scripts/automations?  I have searched high and low and can't seem to locate this information on the NOAA website.
This information would be very helpful to determine if an alert should be waking me up at 4am. The availability of this data what sets this sensor apart from the other  NWS web based sensor.  It would be nice to be able to take advantage of it.

Decided to do some more googlin.  Information I was asking about starts on about page 15 in this PDF.
https://www.weather.gov/media/alert/CAP_v12_guide_03-07-2017.pdf
Additional info that may be of use.
https://www.weather.gov/otx/Watch_Warning_Advisory_Definitions
https://www.weather.gov/unr/hwd
https://www.weather.gov/phi/RiskDefinitions
https://w2.weather.gov/dtx/wwa_defs
https://www.nws.noaa.gov/nwr/info/eventcodes.html


Does Vuforia support ZED camera?

Hi,
I am using AR camera in my Unity project (I have Vuforia package), I want to set the camera as ZED camera, does Vuforia support ZED?
And how can I disable one of the lans for ZED camera?
Thanks,
Karni

Unfortunately, Vuforia does not support the ZED SDK.
It technically supports the ZED, but only by using it as a basic video device, and connecting directly to it. The images are unrectified, with both left and right images together (SBS) and there is no depth information. And as you can only have one active connection to the ZED at a time, it is not possible to have Vuforia and the ZED SDK connected to the camera at once as a workaround.
That said, Vuforia recently responded to a post of mine asking about this on their forums in the context of their Unity plugin. They said there is now an External Camera feature that may work, as you can pass custom camera frames to the SDK. We haven't tested this ourselves, and they say it may not be ideal as it was developed for mobile and UWP, but worth investigating.


kts

how can i include flutter groovy in setting.gradle.kts like :
setBinding(new Binding([gradle: this]))
evaluate(new File(settingsDir.parentFile, './xx_flutter_module/.android/include_flutter.groovy'))

This is not the place for questions. Please try stackoverflow.


Make Submit Locally, Run Globally block standalone.

Note this keeps the old news article at the prior link - we don't want to break things we already shared - but doesn't advertise it on the homepage anymore.
Screenshot:

Making Submit Locallly a stand alone page


Fast wrap to the end of the line doesn't put end pair to the very end

Description
When trying to use the fast wrap feature I'm getting unexpected behaviors.
Steps to reproduce

On the first line when I fast wrap to the end, the ) is immediately put before the end instead of the very end.
On the second line, when I fast wrap to the end (after the existing brace), I get to choose where to put the new ).
I think the first case should put the end pair at the very end.
Although I'm not found of the difference of behavior between the 2 lines.
:point_right: I want that when I wrap to the end of line with $ hint, it always put the end pair at the very end, without asking to put it before/after the last char.
To that end, I think the $ hint should be after the last char to show it'll always put end pair at the very end.
Minimal config
-- example line
-- example line (with braces already)
vim.opt.rtp:append("/home/bew/.local/state/nvim-wip/managed-plugins/start/nvim-autopairs")

require"nvim-autopairs".setup {
  fast_wrap = {
    map = "<C-M-l>",
    highlight = "Search",
  },
}

I'm facing similar issues. I am using lazy.nvim.
my configuration:
-- File: lua/custom/plugins/autopairs.lua

return {
  "windwp/nvim-autopairs",
  -- Optional dependency
  dependencies = { 'hrsh7th/nvim-cmp' },
  config = function()
    require("nvim-autopairs").setup {}
    -- If you want to automatically add `(` after selecting a function or method
    local cmp_autopairs = require('nvim-autopairs.completion.cmp')
    local cmp = require('cmp')
    cmp.event:on(
      'confirm_done',
      cmp_autopairs.on_confirm_done()
    )

    local npairs = require("nvim-autopairs")
    local Rule = require('nvim-autopairs.rule')
    -- put this to setup function and press <a-e> to use fast_wrap
    npairs.setup({
      fast_wrap = {},
    })
    -- change default fast_wrap
    npairs.setup({
      fast_wrap = {
        map = '<M-e>',
        chars = { '{', '[', '(', '"', "'" },
        pattern = [=[[%'%"%>%]%)%}%,]]=],
        end_key = '$',
        before_key = 'h',
        after_key = 'l',
        cursor_pos_before = true,
        keys = 'qwertyuiopzxcvbnmasdfghjkl',
        manual_position = true,
        highlight = 'Search',
        highlight_grey = 'Comment'
      },
    })
  end,
}

I think this is happening because of the manual_position was changed to true in commit 1be91cc0289cbfc485b593260dedfcf7feb01580

Thanks @windwp, looks like the end pair is put at the very end correctly now 👍

Although I'm not fond of the difference of behavior between the 2 lines.
👉 I want that when I wrap to the end of line with $ hint, it always put the end pair at the very end, without asking to put it before/after the last char.
To that end, I think the $ hint should be after the last char to show it'll always put end pair at the very end.
If the line ends with a char matching the pattern there would be another hint for it, that allows to put the end pair before/after.

What do you think about this behavior change suggestion for $ hint?


"Configure HTTPS On a custom domain": Every Azure CDN instance has access to every configure certificate

If I'm following correctly for configuring HTTPS on a custom domain, should there be a note that every Azure CDN instance in this tenant has access to every configured custom certificate in keyvault?
I'm assuming this based on the fact that the keyvault policy is created using the Azure CDN app id: 205478c0-bd83-4e1b-a9d6-db63a3e1e1c8.  Therefore, if 10 teams have their own CDN in one tenant - nothing would be preventing one team to select the certificate of another team.  Is this correct?

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

ID: beac0740-af6e-61ce-bcfa-e783ca181b7d
Version Independent ID: d97885ea-b051-5fde-bd14-ec977e34760e
Content: Tutorial - Configure HTTPS on an Azure CDN custom domain
Content Source: articles/cdn/cdn-custom-ssl.md
Service: cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

@tiny-dancer Thanks for the feedback. We are actively investigating and will get back to you soon.

We only allow key vault certs from the same subscription as the cdn resource to be selected. Any user who doesn't have access to that subscription cannot use the cert in their own cdn resource.

@tiny-dancer If you are concerned about teams having access to other teams certificates, you will need each team to have their own subscription with their own Key Vault and CDN.

@TravisCragg-MSFT @mdgattuso thanks for the quick response. As a user of the docs I believe adding a note on this would be helpful as it appears to be a hidden implementation choice of Azure CDN to scope to subscription (as opposed to more visibly set in say, Azure RBAC). If not hidden, a link to those docs would be nice  :).
Thanks again, always fast response times in this feedback model and it's greatly appreciated :+1:

@tiny-dancer I have assigned the issue to the content author to evaluate and update as appropriate.

Assigning to PM for review
#reassign:@sohamnchatterjee

Updated wording in document
#please-close


HDDS-1738. Add nullable annotation for OMResponse classes.

Modify classes under
hadoop/hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/
NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
1383
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
39
hadoop-hdds in trunk failed.

-1
mvninstall
30
hadoop-ozone in trunk failed.

-1
compile
20
hadoop-hdds in trunk failed.

-1
compile
15
hadoop-ozone in trunk failed.

+1
checkstyle
60
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
854
branch has no errors when building and testing our client artifacts.

-1
javadoc
22
hadoop-hdds in trunk failed.

-1
javadoc
19
hadoop-ozone in trunk failed.

0
spotbugs
951
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
31
hadoop-hdds in trunk failed.

-1
findbugs
20
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

-1
mvninstall
33
hadoop-hdds in the patch failed.

-1
mvninstall
30
hadoop-ozone in the patch failed.

-1
compile
24
hadoop-hdds in the patch failed.

-1
compile
19
hadoop-ozone in the patch failed.

-1
javac
24
hadoop-hdds in the patch failed.

-1
javac
19
hadoop-ozone in the patch failed.

-0
checkstyle
29
hadoop-ozone: The patch generated 5 new + 0 unchanged - 0 fixed = 5 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
686
patch has no errors when building and testing our client artifacts.

-1
javadoc
22
hadoop-hdds in the patch failed.

-1
javadoc
19
hadoop-ozone in the patch failed.

-1
findbugs
31
hadoop-hdds in the patch failed.

-1
findbugs
20
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
28
hadoop-hdds in the patch failed.

-1
unit
23
hadoop-ozone in the patch failed.

+1
asflicense
32
The patch does not generate ASF License warnings.

3649

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1499

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux be6736efcdd1 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 659c888

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-compile-hadoop-ozone.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/diff-checkstyle-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/testReport/

Max. process+thread count
413 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/1/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
47
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
35
hadoop-hdds in trunk failed.

-1
mvninstall
29
hadoop-ozone in trunk failed.

-1
compile
22
hadoop-hdds in trunk failed.

-1
compile
15
hadoop-ozone in trunk failed.

+1
checkstyle
62
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
850
branch has no errors when building and testing our client artifacts.

-1
javadoc
22
hadoop-hdds in trunk failed.

-1
javadoc
17
hadoop-ozone in trunk failed.

0
spotbugs
944
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
30
hadoop-hdds in trunk failed.

-1
findbugs
19
hadoop-ozone in trunk failed.

-0
patch
979
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

-1
mvninstall
34
hadoop-hdds in the patch failed.

-1
mvninstall
29
hadoop-ozone in the patch failed.

-1
compile
23
hadoop-hdds in the patch failed.

-1
compile
19
hadoop-ozone in the patch failed.

-1
javac
23
hadoop-hdds in the patch failed.

-1
javac
19
hadoop-ozone in the patch failed.

-0
checkstyle
29
hadoop-ozone: The patch generated 6 new + 0 unchanged - 0 fixed = 6 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
789
patch has no errors when building and testing our client artifacts.

-1
javadoc
22
hadoop-hdds in the patch failed.

-1
javadoc
20
hadoop-ozone in the patch failed.

-1
findbugs
30
hadoop-hdds in the patch failed.

-1
findbugs
21
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
29
hadoop-hdds in the patch failed.

-1
unit
23
hadoop-ozone in the patch failed.

+1
asflicense
33
The patch does not generate ASF License warnings.

2410

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1499

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux e46c74a77441 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 51c64b3

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-compile-hadoop-ozone.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/diff-checkstyle-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/testReport/

Max. process+thread count
418 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1499/2/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


feat!: Implement the description property on Unix

Blocked on #382

Closing because it's not needed afterall.


Add Open Data Hub 0.9.0 release

Update the Open Data Hub operator to the newest 0.9.0 release
Signed-off-by: Landon LaSmith<EMAIL_ADDRESS>Updates to existing Operators

[X] Is your new CSV pointing to the previous version with the replaces property?
[X] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[X] Have you tested an update to your Operator when deployed via OLM?
[X] Is your submission signed?

Your submission should not

[X] Modify more than one operator
[ ] Modify an Operator you don't own
[X] Rename an operator - please remove and add with a different name instead
[X] Submit operators to both upstream-community-operators and community-operators at once
[X] Modify any files outside the above mentioned folders
[X] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[X] Description about the managed Application and where to find more information
[X] Features and capabilities of your Operator and how to use it
[X] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[X] Human readable name and 1-liner description about your Operator
[X] Valid category name1
[X] One of the pre-defined capability levels2
[X] Links to the maintainer, source code and documentation
[X] Example templates for all Custom Resource Definitions intended to be used
[X] A quadratic logo

/ok-to-test

/test all

/test all

contacted DPTP team, look like issue with ci-operator.

/retest

/test all


Add example notebook about Generative adversarial network

We could try this MNIST example.

This issue was addressed in #7 . It can be closed now.


Update to libp2p 0.10

Updates libp2p to version 0.10.0.

I assume this fixes: https://github.com/paritytech/substrate/issues/2940 ?

I assume this fixes: #2940 ?

Yes, but I also published libp2p v0.9.2 which fixes it as well.


chore: use "!" in license to avoid minification

Using /*! for starting license blocks seems to be a typical approach to tell minifiers not to remove them.
For example, terser-webpack-plugin docs:
https://github.com/webpack-contrib/terser-webpack-plugin/#extractcomments

The other option is to use @license inside the comment block.


Why not to use the "monadic" approach

I think the whole point of the futures is the capability of composing the previous result with the next one and if some computation in the middle of the chain fails, the whole chain fails. This is the monadic approach and allow much more composability. With the current interface of futures Future<T,Error> this cannot be achieved, because Error cannot be modified by the map method on the result (I actually think this cannot be achieved without hacks).
In Scala, this can be achieved through the for comprehension syntactic sugar. Only at the end of the chain you use onSucces/onComplete.
I know that this is a huge amount of work, but i think it must be pointed out.

BrightFutures uses typesafe error handling, which has some advantages including exhaustive error handling. The downside however is that it is not directly compatible with Swift's error handling. But I do not concur with your conclusion that this prevents BF from being 'monadic'. The Future type has map for transforming values and mapError for transforming errors. Future inherits these operations from the Result type (Future is basically an async wrapper around Result).
Knowing this, and using Results' materialize and BF's flatMap you can compose Futures the way you want. An example:
enum MyError {
    case .httpError(HTTPResponse, NSError)
    case .fluxCapacitorFailure
}

func synchronouslyCalculateFluxCapacitor() throws -> Int {
    // ...
}

func fetch(_ url: String) -> Future<Data, MyError> {
    // ...
}

fetch("http://www.example.org").flatMap {
    materialize(synchronousFailiableOperation()).mapError { .fluxCapacitorFailure }
}

It involves an explicit error type transformation, but enables typesafe error handling. In this case, I would have synchronouslyCalculateFluxCapacitor probably return a Result<Int, MyError>, but even using Swift's error handling it works pretty well.
Hope this helps!


[#2494] feat(spark-connector): support UpdateColumnPosition in AlterTable for spark connector

What changes were proposed in this pull request?
Support UpdateColumnPosition in AlterTableCommand.
Why are the changes needed?
Implement UpdateColumnPosition ops for Spark AlterTableCommand.
Fix: #2494
Does this PR introduce any user-facing change?
Yes, users can run the following commands to modify the table column position using spark sql.
ALTER TABLE StudentInfo CHANGE COLUMN col1 col1 string FIRST
How was this patch tested?
New UTs.

cc @FANNG1

Hi @hiirrxnn, if you would like to keep working on it. i will close this pr.

Hi @hiirrxnn, if you would like to keep working on it. i will close this pr.

have communicated with @hiirrxnn , and i will continue on it.

CI failed, please note that hive has some constraints about altering column positions.
    java.lang.IllegalArgumentException: Failed to alter Hive table [TEST_COLUMN_POSITION] in Hive metastore, since Hive metastore will check the compatibility of column type between the old and new column positions, please ensure that the type of the new column position is compatible with the old one, otherwise the alter operation will fail in Hive metastore.

CI failed, please note that hive has some constraints about altering column positions. may be we could create a table with same column type to bypass this.
    java.lang.IllegalArgumentException: Failed to alter Hive table [TEST_COLUMN_POSITION] in Hive metastore, since Hive metastore will check the compatibility of column type between the old and new column positions, please ensure that the type of the new column position is compatible with the old one, otherwise the alter operation will fail in Hive metastore.

ALTER COLUMN ... FIRST | ALTER is only supported with v2 tables. But I wonder why not throw operationOnlySupportedWithV2TableError exception. cc @FANNG1

operationOnlySupportedWithV2TableError

The current spark connector is implemented based on V2 table. For hive catalog, we use Kyubbi spark-connector.

operationOnlySupportedWithV2TableError

The current spark connector is implemented based on V2 table. For hive catalog, we use Kyubbi spark-connector. you can refer the design #1287

i got it. thanks @FANNG1

@caican00 , merge to main, thanks for your work

@caican00 , merge to main, thanks for your work

Thanks for review and merge.


ci/cd: added github actions for agenta-web

Closes #471

Hi @lazyfuhrer thanks for the PR. I added some comments. Btw have you tried to test it ?

nope, will do shortly!

@all-contributors please add @lazyfuhrer for implementing https://github.com/Agenta-AI/agenta/issues/471

https://github.com/all-contributors please add @lazyfuhrer for [code]

@all-contributors please add @username for code

@all-contributors please add @lazyfuhrer  for code


Network Policies

In the code example, a dash "-" is missing before the ports fields bellow the egress and ingress fields.

egress:

ports:

/language en

Egress rules are defined with the following fields.
ports: an array of NetworkPolicyPort (port, endport, protocol)
to: an array of NetworkPolicyPeer (ipBlock, namespaceSelector, podSelector)
so the Egress yaml structure would be
egress:
- to:
ports:

if you understood, please close the issue

/priority awaiting-more-evidence

/retitle Bug in example NetworkPolicy manifest

I would like to work on this! but can you show more evidence for this issue!!

According to kubectl explain:
~ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-14T09:47:38Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.7+k3s2", GitCommit:"575bce7689f4be112bd0099362fb8d5f2e39398e", GitTreeState:"clean", BuildDate:"2023-11-08T01:59:21Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/arm64"}
~ kubectl explain netpol.spec.ingress
GROUP:      networking.k8s.io
KIND:       NetworkPolicy
VERSION:    v1
FIELD: ingress <[]NetworkPolicyIngressRule>
DESCRIPTION:
ingress is a list of ingress rules to be applied to the selected pods.
Traffic is allowed to a pod if there are no NetworkPolicies selecting the
pod (and cluster policy otherwise allows the traffic), OR if the traffic
source is the pod's local node, OR if the traffic matches at least one
ingress rule across all of the NetworkPolicy objects whose podSelector
matches the pod. If this field is empty then this NetworkPolicy does not
allow any traffic (and serves solely to ensure that the pods it selects are
isolated by default)
NetworkPolicyIngressRule describes a particular set of traffic that is
allowed to the pods matched by a NetworkPolicySpec's podSelector. The
traffic must match both ports and from.
FIELDS:
from	<[]NetworkPolicyPeer>
from is a list of sources which should be able to access the pods selected
for this rule. Items in this list are combined using a logical OR operation.
If this field is empty or missing, this rule matches all sources (traffic
not restricted by source). If this field is present and contains at least
one item, this rule allows traffic only if the traffic matches at least one
item in the from list.
ports	<[]NetworkPolicyPort>
ports is a list of ports which should be made accessible on the pods
selected for this rule. Each item in this list is combined using a logical
OR. If this field is empty or missing, this rule matches all ports (traffic
not restricted by port). If this field is present and contains at least one
item, then this rule allows traffic only if the traffic matches at least one
port in the list.
According to my understanding, all of ingress, ports and from are lists so their items must start with a dash.
So the example should be:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: test-network-policy
namespace: default
spec:
podSelector:
matchLabels:
role: db
policyTypes:
- Ingress
- Egress
ingress:
- from:
- ipBlock:
cidr: <IP_ADDRESS>/16
except:
- <IP_ADDRESS>/24
- namespaceSelector:
matchLabels:
project: myproject
- podSelector:
matchLabels:
role: frontend
- ports:
- protocol: TCP
port: 6379
egress:
- to:
- ipBlock:
cidr: <IP_ADDRESS>/24
- ports:
- protocol: TCP
port: 5978
I had a question about a netpol in the simulator of the CKAD certification (egress netpol only) and I copied and pasted this example.
The solution was wrong and I needed to add a "-" before ports in order to make it work.

We're confident that the documentation doesn't need a correction.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: test-network-policy
  namespace: default
spec:
  podSelector:
    matchLabels:
      role: db
  policyTypes:
    - Ingress
    - Egress
  ingress:
    - from:
        - ipBlock:
            cidr: <IP_ADDRESS>/16
            except:
              - <IP_ADDRESS>/24
        - namespaceSelector:
            matchLabels:
              project: myproject
        - podSelector:
            matchLabels:
              role: frontend
    - ports:
        - protocol: TCP
          port: 6379
  egress:
    - to:
        - ipBlock:
            cidr: <IP_ADDRESS>/24
    - ports:
        - protocol: TCP
          port: 5978

has two ingress rules and two egress rules.

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: test-network-policy
  namespace: default
spec:
  podSelector:
    matchLabels:
      role: db
  policyTypes:
    - Ingress
    - Egress
  ingress:
    - from:
        - ipBlock:
            cidr: <IP_ADDRESS>/16
            except:
              - <IP_ADDRESS>/24
        - namespaceSelector:
            matchLabels:
              project: myproject
        - podSelector:
            matchLabels:
              role: frontend
      ports:
        - protocol: TCP
          port: 6379
  egress:
    - to:
        - ipBlock:
            cidr: <IP_ADDRESS>/24
      ports:
        - protocol: TCP
          port: 5978

has one ingress rule where the source IP address range and port specification must both match.
It also has one egress rule where the destination IP address range and port specification must both match.
You could read other web pages about NetworkPolicy to make sure that you have understood your confusion @gacunto. There's nowt to fix.

Ok.
I see.
Thank you for the clarification.


Add "The Consciousness Prior" link

Waiting till October before merging so that this could count towards Hacktoberfest.


Add Regkeys for BeyondCompare Context Menus

This adds registry keys to enable Beyond Compare in the context menus in Windows (things like "Select as Left File for Comare"), which is one of the key features of BComp.
Note, I have the paths set to my fork, they need to be changed to your tree before merge, should I do that on my branch?
Also, one other note. When you remove the context option with the regkey, you need to restart explorer to remove the app folder. This is unfortunate, but I feel this downside far outweighs the upside (could capture this in notes if they are available during uninstall).

Hello! I am curious to know if this is still work in progress. Thank you!

not stale

The remote repository for this PR is deleted. @f0ff886f please open a new PR after resolving conflicts.