DataMatrix DMDetetor: traceGap() assertion may fail in noisy area

If the image is noisy after binarization, traceGap() assertion may fail on this line.
https://github.com/nu-book/zxing-cpp/blob/b93fdeef39342a4af66c5c62a6b28d05379c9772/core/src/datamatrix/DMDetector.cpp#L554
Because there are actually two operations in the main while loop that moves EdgeTracer's current point p, and it may stay unmoved. Project back + centered() and traceStep() happens to move the point in exactly the opposite direction. https://github.com/nu-book/zxing-cpp/blob/b93fdeef39342a4af66c5c62a6b28d05379c9772/core/src/datamatrix/DMDetector.cpp#L576 and https://github.com/nu-book/zxing-cpp/blob/b93fdeef39342a4af66c5c62a6b28d05379c9772/core/src/datamatrix/DMDetector.cpp#L607

Could you provide a sample image that triggers this issue?

I found one assertion failure in one image in my large dataset. However, I have modified the binarizer and use image pyramid. So the image may or may not trigger failure in the original code. I could provide the binarized BitMatrix image and the tracer state.

I need something to reproduce the error on my machine. You should be able to dump your BitMatrix as a b/w image so that I can use that with the code as.
Am I right to assume you are employing an image pyramid to improve the decoding of high resolution images?

That's right, pyramid is to improve decoding of high-res image. I am trying to reproduce on your master branch. Also, the image contains private info, so I have to remove them. But you can see these lines may have some problem.

Fortunately I have reproduced it on the binarized image. Here is the image that cause assertion failure. Manually set try_harder = true in DMDetector.

First set tryHarder = true in DMDetector.cpp Line 779, to enable multi-line scan to detect off-center symbols.
Entry arguments:
ZXing:BitMatrixCursorF = {
img = {
object_ = 0x0000000101291bf0
}
p = (x = 283.5, y = 92.5)
d = (x = -1, y = 0.02175528874599993)
…
}
maxStepSize = 15
Line 340:
CHECK(tlTracer.traceGaps(tlTracer.right(), lineT, maxStepSize));
in traceGaps()
do…while loop
line.points().back() equals to p at the 14th iteration
(lldb) p line
(ZXing::DataMatrix::RegressionLine) $5 = {
_points = size=14 {
[0] = (x = 283.5, y = 92.5)
[1] = (x = 282.5, y = 92.5)
[2] = (x = 281.5, y = 91.5)
[3] = (x = 280.5, y = 91.5)
[4] = (x = 279.5, y = 91.5)
[5] = (x = 279.5, y = 93.5)
[6] = (x = 278.5, y = 95.5)
[7] = (x = 277.5, y = 95.5)
[8] = (x = 274.5, y = 95.5)
[9] = (x = 276.5, y = 100.5)
[10] = (x = 275.5, y = 99.5)
[11] = (x = 275.5, y = 101.5)
[12] = (x = 274.5, y = 100.5)
[13] = (x = 273.5, y = 99.5)
}
_directionInward = (x = -0.021750142264310393, y = -0.99976343767487418)
a = -0.82308011556249749
b = -0.56792527973812335
c = -283.34570390971504
}
(lldb) p *this
(ZXing::DataMatrix::EdgeTracer) $4 = {
ZXing::BitMatrixCursorF = {
img = {
object_ = 0x0000000101291bf0
}
p = (x = 273.5, y = 99.5)
d = (x = -1, y = 0.39311942704135705)
}
history = {
object_ = 0x0000000101291e90
}
}
(lldb) p gaps
(int) $6 = 1

#171

I can not reproduce the failed assertion with your sample image with current master (including the tryHarder = true change). Could you please double check that this actually shows the issue. Which parameters to you pass ZXingReader?
Your removal of the assertion will fix your immediate issue but the assertion is there to let me know if there still is a problem with endless loops in the code. I'd rather reproduce the problem first and maybe fix it at a more appropriate place. Thanks for the effort, though!

Question: what compiler flags related to optimization/floating point math are you using? It could be that we get different results because you are using some relaxed floating point math, like -ffast-math?

Question: what compiler flags related to optimization/floating point math are you using? It could be that we get different results because you are using some relaxed floating point math, like -ffast-math?

No, I checked by default this flag if off.

Have your tracer traced to p = (x = 273.5, y = 99.5)?

I can not reproduce the failed assertion with your sample image with current master (including the tryHarder = true change). Could you please double check that this actually shows the issue. Which parameters to you pass ZXingReader?
Your removal of the assertion will fix your immediate issue but the assertion is there to let me know if there still is a problem with endless loops in the code. I'd rather reproduce the problem first and maybe fix it at a more appropriate place. Thanks for the effort, though!

The parameters are -format DataMatrix **.png.

My trace passes through p = (x = 273.5, y = 99.5) as well but the contents of line is different at that point in time. I still suspect the differences in behavior come from differences in what your and my compiler actually put out. I was not referring only to the specific -ffast-math flag. Could you please provide the full command line of your compilation of DMDetector.cpp? (see e.g. make VERBOSE=1).

CompileC /Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/Objects-normal/x86_64/DMDetector.o /Users/nullptr/Downloads/zxing-cpp/core/src/datamatrix/DMDetector.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'ZXing' from project 'ZXing')
cd /Users/nullptr/Downloads/zxing-cpp
export LANG=en_US.US-ASCII
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -target x86_64-apple-macos11.0 -fmessage-length\=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit\=0 -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wno-float-conversion -Wno-non-literal-null-conversion -Wno-objc-literal-conversion -Wno-shorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DCMAKE_INTDIR\=\"Debug\" -DZXing_EXPORTS -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.0.sdk -fasm-blocks -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -g -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -Wno-comma -Wno-block-capture-autoreleasing -Wno-strict-prototypes -Wno-range-loop-analysis -Wno-semicolon-before-method-body -index-store-path /Users/nullptr/Library/Developer/Xcode/DerivedData/ZXing-firwcmslrqjcthfaxwldpyjelthc/Index/DataStore -I/Users/nullptr/Downloads/zxing-cpp/Xcode/core/Debug/include -I/Users/nullptr/Downloads/zxing-cpp/core/src -I/Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/DerivedSources-normal/x86_64 -I/Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/DerivedSources/x86_64 -I/Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/DerivedSources -F/Users/nullptr/Downloads/zxing-cpp/Xcode/core/Debug -fPIC -Wall -Wextra -Wno-missing-braces -Werror\=undef -std\=c++17 -MMD -MT dependencies -MF /Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/Objects-normal/x86_64/DMDetector.d --serialize-diagnostics /Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/Objects-normal/x86_64/DMDetector.dia -c /Users/nullptr/Downloads/zxing-cpp/core/src/datamatrix/DMDetector.cpp -o /Users/nullptr/Downloads/zxing-cpp/Xcode/core/ZXing.build/Debug/ZXing.build/Objects-normal/x86_64/DMDetector.o

I noticed there is no -ffloat-store, is this flag causing the problem?

I noticed there is no -ffloat-store, is this flag causing the problem?

That seemed like a very good guess, but it turns out, my linux clang-11 setup is not using that compiler flag either. I'm running out of ideas. It seems the only difference left is macOS + clang12 vs linux + clang11. My gut feeling says it is unlikely that this really is the root cause.
Could you please double check that the input you are working with is exactly what you posted above?

I noticed there is no -ffloat-store, is this flag causing the problem?

That seemed like a very good guess, but it turns out, my linux clang-11 setup is not using that compiler flag either. I'm running out of ideas. It seems the only difference left is macOS + clang12 vs linux + clang11. My gut feeling says it is unlikely that this really is the root cause.
Could you please double check that the input you are working with is exactly what you posted above?

I checked the input is exactly what I posted above. Have you set tryHarder = true in DMDetector.cpp on your linux + chang11 setup?

Good question but, yes, I did. At this point I give up. I assume you don't mind if the assert stays (debug build only)? The release build will contain your fix.

Good question but, yes, I did. At this point I give up. I assume you don't mind if the assert stays (debug build only)? The release build will contain your fix.

Thanks, I don't mind the asserts. Btw, there is also another assert in TraceStep(), which may fail in rare cases. I will keep filling more DataMatrix test cases and try to trigger it. I will notify you once I found another case.


docs(matrix): add system requirements doc DOC-350

Resolves Jira: DOC-350

I addressed all of @aimeeu 's comments  @dogonthehorizon , so you can merge when you're ready


🐞 - Input style bug when autofill class is added

Which @taiga-ui/* package(s) are the source of the bug?
kit
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/taiga-starter
Is this issue blocking you?
Non-Blocking
Description
.autofill(@mode:default) {
    &:-webkit-autofill,
    &:-webkit-autofill:hover,
    &:-webkit-autofill:focus {
        border-radius: inherit;
        color: inherit !important;
        background-color: transparent !important;
        -webkit-text-fill-color: transparent !important;

        & when (@mode = default) {
            border-color: var(--tui-autofill);
            -webkit-box-shadow: 0 0 0 100rem var(--tui-autofill) inset !important; // to overlay native background
        }

        & when (@mode = dark) {
            border-color: var(--tui-autofill-night);
            -webkit-box-shadow: 0 0 0 100rem var(--tui-autofill-night) inset !important;
        }
    }
}

The line that is causing the issue:
-webkit-text-fill-color: transparent !important;
This was added a month ago in another fix by @splincode to fix another bug with card number autofill but it is making the value of all inputs invisible when using autofill.
Here is a image of a case

Angular version
14.1.1
Taiga UI version
2.58.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

try on version 2.62, all the same?

@splincode we have update now to 3.0 and it seems to be fixed!


docs: include/spi.h removed spi_config doxygen comment for removed variable

Removed a doxygen comment for a structure variable that has been
removed from spi_config.
Signed-off-by: AJ Palmer<EMAIL_ADDRESS>

Codecov Report

Merging #12082 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12082      +/-   ##
==========================================
+ Coverage   48.05%    48.1%   +0.05%
==========================================
  Files         281      281
  Lines       43416    43416
  Branches    10406    10406
==========================================
+ Hits        20864    20886      +22
+ Misses      18403    18382      -21
+ Partials     4149     4148       -1

Impacted Files
Coverage Δ

subsys/logging/log_msg.c
88.63% <0%> (+2.27%)
:arrow_up:

subsys/logging/log_core.c
82.53% <0%> (+7.86%)
: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 523932c...f4cd81f. Read the comment docs.

Looks like it needs a recheck


Issue while the logon scripts are running inside the HCIbox

Discussed in https://github.com/microsoft/azure_arc/discussions/1795

Originally posted by ullasanand13 April 25, 2023
Hi GIT team,
"HCIBox-Client" has got deployed. However, after login to the HCIbox the logon scripts have failed due to the below error. I know this is a permissions issue. But it is trying to connect to our default subscription. How to change the subscription where the resources have to be deployed?
Message: The client<EMAIL_ADDRESS>with object id 'f0851858-ef81-48ef-b258-b865c3e268ce' does not have authorization to perform action 'Microsoft.GuestConfiguration/register/action' over scope '/subscriptions/7e62512b-1073-46d1-b75c-c507c9cc7eb2' or the scope is invalid. If access was recently granted, please refresh your credentials.
(AuthorizationFailed) The client<EMAIL_ADDRESS>with object id 'f0851858-ef81-48ef-b258-b865c3e268ce' does not have authorization to perform action 'Microsoft.Kubernetes/register/action' over scope '/subscriptions/7e62512b-1073-46d1-b75c-c507c9cc7eb2' or the scope is invalid. If access was recently granted, please refresh your credentials.
Code: AuthorizationFailed

Hello, thanks for reaching out. You would need to select the right subscription before deploying following this guidance

Thank you. I was able to overcome this issue by giving contributor role to the service principal.
Regards,
Ullas

Glad to hear its resolved. Please note you need Owner permissions to make sure to have all the functionality working in HCIBox


Unable to authenticate

Exactly the same issue as https://github.com/segmentio/aws-okta/issues/26 just started happening between Friday and today.
DEBU[0000] Parsing config file /Users/shawn/.aws/config
DEBU[0000] Using aws_saml_url from profile: <profile_name>
DEBU[0000] using okta provider
DEBU[0000] Failed to reuse session token, starting flow from start
DEBU[0000] Step: 1
DEBU[0001] Step: 2
INFO[0001] Requesting MFA. Please complete two-factor authentication with your second device
DEBU[0001] <REDACTED>
DEBU[0001] Okta Factor Provider: DUO
DEBU[0001] Okta Factor ID: <REDACTED>
DEBU[0001] Okta Factor Type: web
DEBU[0001] Host:api-beb1bbc4.duosecurity.com
Signature:<REDACTED>
StateToken:<REDACTED>

DEBU[0001] challenge u2f
INFO[0001] Sending Push Notification...
Failed Duo challenge

Unclear what happened, but this is now working properly. Sorry to bother!


consider adding a #![recursion_limit="128"] attribute to your crate

let map = HashMap::new();
        pool.prep_exec("INSERT INTO k_bill\
        (\
        user_id,owner_id,app_id,updated_time,updated_user,created_time,created_user,\
        out_trade_no,order_name,origin_amount,discount_amount,trade_amount,remark,addition_data,\
        auth_code,notify_url,jump_url,payment_method\
        ) \
        VALUES \
        (\
        :user_id,:owner_id,:app_id,:updated_time,:updated_user,:created_time,:created_user\
        :out_trade_no,:order_name,:origin_amount,:discount_amount,:trade_amount,remark,:addition_data,\
        :auth_code,:notify_url,:jump_url,:payment_method\
        )", params!(
        bill.user_id,
        bill.owner_id,
        bill.app_id,
        bill.updated_time,
        bill.updated_user,
        bill.created_time,
        bill.created_user,
        bill.out_trade_no,
        bill.order_name,
        bill.origin_amount,
        bill.discount_amount,
        bill.trade_amount,
        bill.remark,
        bill.addition_data,
        bill.auth_code,
        bill.notify_url,
        bill.jump_url,
        bill.payment_method
        )).unwrap();

Hello,When I try to insert a bill record with more than 8 parameter,but the cargo check was show me the error.
error: recursion limit reached while expanding the macro `vec`
  --> src/app/bill_service.rs:39:12
   |
39 |           )",params!(
   |  ____________^
40 | |         bill.user_id,
41 | |         bill.owner_id,
42 | |         bill.app_id,
...  |
57 | |          bill.payment_method
58 | |         )).unwrap();
   | |_________^
   |
   = help: consider adding a `#![recursion_limit="128"]` attribute to your crate
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: Could not compile `user`.

After that, when I adding a  rust #![recursion_limit="128"],the cargo check isn't compiler,and then,
I setting the number 1024,the cargo check was runing with long time.
So,How can I solve the problem?
Appreicated you answer :smiley:

Hi!
params!(bill.user_id, ...) isn't a valid syntax for params! macro and leads to recursion because of a bug in macro definision (solved in 4c60d4e). Thanks for reporting it!
To fix this you have the following options:
// 1. Use params!( expr => expr, ... ) syntax:
params!(
    "user_id" => bill.user_id,
    "owner_id" => bill.owner_id,
    // ...
)

// 2. User params!( ident, ... ) syntax
let user_id = bill.user_id;
let owner_id = bill.owner_id;
// ...
params!(
    user_id,
    owner_id,
    // ...
)

Thanks for your help.
Now, I have another question about the prepare statement logging.
When I trying to debug my prepare statement,but don't know how the statement execution.

I'm afraid i need more explanation/code to understand your question.
Anyway, since it's unrelated to this issue youl'd better to use stackoverflow fo this.


fix: support scanning font families from "font:"

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

@danielroe
Resolves #291. css-tree does the parsing work automatically for us.

Codecov Report
Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 41.98%. Comparing base (9119228) to head (7f15378).

Files with missing lines
Patch %
Lines

playground/pages/providers/google.vue
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #299   +/-   ##
=======================================
  Coverage   41.98%   41.98%
=======================================
  Files          58       58
  Lines        3561     3561
  Branches      442      442
=======================================
  Hits         1495     1495
  Misses       2028     2028
  Partials       38       38

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


 PR updates starlight to have drobes and cameras, while also giving hardsuit's built in cameras that you can view on wireless camera monitors.
Screenshots

Changelog
:cl: eclips_e

add: Hardsuit Cameras have been added, fear not fellow spessmen!
fix: Starlight has been updated

Also did some cleanup, I'd recommend moving fork-based prototypes to the OuterRim/ directory


to_param must be string

I have run the code, but it show me undefined method `empty?' for 1:Fixnum.
So I found the problem. to_param return value must be string.

Thanks!


Styles disappear when element is re appended when using constructible stylesheets

Description
When element is temporarily removed and then re appended to the dom styles from static get styles do not work. This only happens when browser supports constructible stylesheets. Manually calling this.shadowRoot!.adoptedStyleSheets = MyElement.styles.map(style => style.styleSheet) inside connectedCallback fixes the problem for that element but not for its children.
Live Demo
https://stackblitz.com/edit/typescript-vva73g?file=my-element.ts
Steps to Reproduce

Create my-element
Append my-element to document.body
Remove the same element from document.body
Re append the same element to document.body

Expected Results
Styles are still applied.
Actual Results
No styles from adoptedStyleSheets are applied.

Thanks for reporting this; it's a Chrome bug and has been filed here: https://bugs.chromium.org/p/chromium/issues/detail?id=934340.

Can't open the Chrome issue, here is a minimal repro:
Minimal repro here: https://65s7tj-jqi1d9.stackblitz.io
Code at https://stackblitz.com/edit/65s7tj-jqi1d9

It's fixed in Chrome 74 canary, but broken in Chrome 73 beta, though I think the fix will be backported to 73 before it is released.

Looks like the fix was merged into 73. We should be seeing it roll out soon.


NEXT-7754 - Fix thumbnail generation when physical file is missing

1. Why is this change necessary?
Regeneration of thumbnails requires a check of the physical file to ensure that the thumbnail was actually generated and not just having a virtual representation in the database.
The circumstances why this situation might occur are not relevant.
However, possible causes could be:

Third-party actions such as file monitoring processes and automated clean-up operations
Unintentional deletion by humans
Previously unknown Bugs in Code that can cause such a condition
...

2. What does this change do, exactly?
Adds a physical file check when updating thumbnails.
3. Describe each step to reproduce the issue or behaviour.

Make sure you have generated thumbnails.
Delete the Thumbnail folder or only a specific file from the sub-folders
Execute bin/console media:generate-thumbnails
Check that every thumbnail generation was skipped

4. Please link to the relevant issues (if any).

NEXT-7754
artikelbild-thumbnails-verschwinden-sind-kaputt-404-wieso

5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Reopens #1879 @J-Rahe

@leptoquark1 is back 🎉  Could've used that one right yesterday :D

Hey @leptoquark1, there was an discussion regarding the performance of this yesterday. I will come back to you once i have an answer on how to proceed.

What are the performance concerns here?
I would love to see this merged.

Hey @leptoquark1 and @treffner, sorry for the late response.
We decide to implement this check as an optional flag E.g. "--strict" to the media:generate-thumbnails command, due to the performance impact.
Note that adding an optional parameter to updateThumbnails is breaking

@jakob-kruse I will implement the missing flag to the command and its further behaviour in the service in the next few days.

@jakob-kruse I've updated the commit as requested.
But I was not sure about the  media:generate-thumbnails command behaviour with --async option.
It does dispatch the UpdateThumbnailsMessage, but the corresponding GenerateThumbnailsHandler calls the method generate of the ThumbnailService.
By this step I noticed that the updateThumbnails and generate method does not share any accumulation logic until the call of createThumbnailsForSizes.
This may cause a different behaviour of the thumbnails being update/generated depending on if the async option is given in with media:generate-thumbnails or not. I was not sure if this was intended.
However, I only implemented the target call of updateThumbnails, but I'd rather suggest to refactor the ThumbnailService or add an condition in the GenerateThumbnailsHandler:
class GenerateThumbnailsHandler extends AbstractMessageHandler
{
    // [...]

    public function handle($msg): void
    {
        // [...]

        if ($msg instanceof UpdateThumbnailsMessage) {
            foreach ($entities as $media) {
                $this->thumbnailService->updateThumbnails($media, $context, $msg->isStrict());
            }
        } else {
            $this->thumbnailService->generate($entities, $context);
        }
    }

    // [...]
}

class UpdateThumbnailsMessage extends GenerateThumbnailsMessage
{
    private bool $isStrict = false;

    public function isStrict(): bool
    {
        return $this->isStrict;
    }

    public function setIsStrict(bool $isStrict): void
    {
        $this->isStrict = $isStrict;
    }
}

class GenerateThumbnailsCommand extends Command
{
    // [...]

    private function generateAsynchronous(RepositoryIterator $mediaIterator, Context $context): void
    {
        // [...]
        while (($result = $mediaIterator->fetch()) !== null) {
            $msg = new UpdateThumbnailsMessage();
            // [...]
            $msg->setIsStrict($this->isStrict); // <--
            $this->messageBus->dispatch($msg);
            // [...]
        }
        // [...]
    }

    // [...]
}

Hey @leptoquark1
Thanks for adding the option. I noticed there were some changes to the theme compiling in the meantime. It would be nice if you could rebase your changes.
I will get back to you once I know more!

Hey @leptoquark1
Thanks for adding the option. I noticed there were some changes to the theme compiling in the meantime. It would be nice if you could rebase your changes.
I will get back to you once I know more!

Due to a merge conflict with current trunk, I have rebased this pull request again.

@fschmtt @keulinho @jakob-kruse Sorry for the late response!
Looks like I just dismissed the notification and forgot about it... However, I made the changes as I suggested and it works just fine.
This pull request now contains the following changes, which are split into two commits:

Fix updateThumbnails function in src/Core/Content/Media/Thumbnail/ThumbnailService.php so that the physical presence of the thumbnail file is respected

Added new parameter $strict to method Shopware\Core\Content\Media\Thumbnail\ThumbnailService::updateThumbnails

Added option --strict to command media:generate-thumbnails. Supplying it, a physical file check for existing thumbnails is performed.

Fix different behaviour or results expected when media:generate-thumbnails command is executed with or without the async flag.

The GenerateThumbnailsHandler now distinguish which method is executed in theThumbnailService based on the message type.

Added two methods isStrict and setIsStrict and it's corresponding property isStrict to class UpdateThumbnailsMessage

The GenerateThumbnailsHandler will now proceed with ThumbnailService::generate when handling GenerateThumbnailsMessage

The GenerateThumbnailsHandler will proceed with ThumbnailService::updateThumbnails when handling UpdateThumbnailsMessage

When processed by MessageBus the optional strict flag for thumbnail generation (as introduced in NEXT-7754) will be passed,
to the respective ThumbnailService::updateThumbnails method as expected. So it may considered in following generation process.

I would actually recommend combining the two methods generate and updateThumbnails to create some sort of "single source of trouth", since it should be no difference in its context and responsibility if the input is either update or a generate. But we should close this issue and have these changes solve existing issues.
Have a good day :)

Wow, many thanks for your efforts @leptoquark1! 🎉

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-18957
Please use this issue to track the state of your pull request.

Hey @leptoquark1 thanks for your contribution! :blue_heart: :tada:

#383
#1062


Evaluate WizardCoder-1B, WizardCoder-3B, WizardCoder-Python-7B, WizardCoder-Python-13B

Somehow missed these.

Python-13B does a decent job at senior


Propose how to improve testing process

Describe the problem
We've identified that we want to

reduce manual testing
reduce testing pre-release
clearly identify which test cases are most critical
Streamline code review assignment

Proposed solution
Develop a clear process for the lifecycle and infrastructure changes we need to make to increase the efficiency of testing and be confident we've covered the critical use cases.
Alternatives you've considered
No response
Additional context
No response

Timebox: 1 day

To properly cover the test plan we to have data that reproduce conditions that might make the query fail (refer to the Limit problem)
Solutions:

Improve unit tests to add the conditions

Con: We might have to artificially create a lot of data to reproduce the corner cases

Identify data in our current QA or PROD database that reproduce the problem and tailor the query for that

e.g. if we know that the limit problem happens with a certain feed, set the offset so the offending feed is included in the response
Con: The DB changes over time and we might have to readjust the tests if they start failing because of the data
Con: The DB might not contain all the data to reproduce corner cases.

Have a special integration test that uses a DB created for that purpose.

The DB would be filled with:

A reduced version of source.csv that we control
The equivalent of test_datasets.json to add missing data that can reproduce error conditions

Currently we test the API with unit tests and integration tests. Here is a list of tests that should be added. Wether they go in the unit tests or the integration tests is TBD.

For all feed and dataset endpoints:

Test for non-existent ID
Verify that the response matches the response schema
limit and offset

Currently we do test the number of items returned, but we don't test to see if the right items are returned

Test for issue #445, i.e. create the conditions that led to that bug (suspect currently is multiple datasets for a feed, or presence of redirect)
Search by subdivision_name

/v1/gtfs_feeds

Add more combination of parameters

We currently do quite a bit of testing. I would suggest adding more combination of parameters (e.g. provider and producer_url, provider and municipalty, etc.)

Test for condition that lead to issue #433, i.e. we need a latest dataset that has a null bounding box
Verify that the latest dataset is really the latest

/v1/gtfs_feeds/{id}/datasets

Verify that there is only 1 latest dataset
Verify that all returned datasets are really for the specified feed

/v1/datasets/gtfs/{id}

Verify the validation report fields (validated_at, features, etc)

/v1/metadata

Verify if the version and commit hash are accurate

/v1/search

Verify the schema of the returned data (should be a combination of gtfs and gtfs_rt feed shemas)
Verify that some fields are null depending on the type of result

e.g. latest_dataset should be null for gtfs_rt type, entity_types should be null for gtfs type.

Next step is for @jcpitre to create issues for each of the endpoints included here


Backspace not properly removing characters on both iOS and Android

Bug report

Summary
I've just added this module to my project in order to support masks.
However, I've noticed an issue when I use the backspace on both iOS and Android that the character is not properly erased.
I'm not sure the issue is due to this library or due to the RedMadRobot/input-mask library.
I do reproduce this issue on both iOS and Android.
This is a screen recording of the issue:

Environment info

react-native info output:
SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 23, 28, 29
      Build Tools: 27.0.3, 28.0.3, 29.0.0
      System Images: android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-R | Google Play Intel x86 Atom
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5

Library version: 2.0.0
Reproducible sample code
Just a regular use of the text input.
<TextInput
      placeholder="([000]) [000]-[00]-[00]"
      mask="([000]) [000]-[00]-[00]"
/>

@alexmngn : have you found the fix for the issue?

@alexmngn I've also encountered this issue. If you've found a fix could you please share it?

This issue seem to occur when the formatted text as value instead of actual text.
As specified in the documentation, the library returns two values on onChangeText function.
onChangeText={(formatted, extracted) => {
    console.log(formatted) // +1 (123) 456-78-90
    console.log(extracted) //<PHONE_NUMBER>
  }}

When using the extracted value, this issue doesnt occur for both ios and android.
Example Code
const App = (props) => {
  const [value, setValue] = React.useState()

  return <TextInputMask
    placeholder="([000]) [000]-[00]-[00]"
    mask="([000]) [000]-[00]-[00]"
    value={value}
    onChangeText={(formatted, extracted) => {
      setValue(extracted)
    }}
  />
}

What if we want to store the formatted text. If this is the case then it won't work with the current way. Is there any fix to use formatted text in both input and state?

What if we want to store the formatted text. If this is the case then it won't work with the current way. Is there any fix to use formatted text in both input and state?

import React, { Component, useContext } from 'react';
import TextInputMask from 'react-native-text-input-mask';
export default function testClass() {
const [valueE, setValueE] = React.useState("")
const [valueF, setValueF] = React.useState("")
<TextInputMask
refInput={ref => { this.input = ref }}
onChangeText={(formatted, extracted) => {
setValueE(extracted);
setValueF(formatted);
}}
value={valueE}
keyboardType={'numeric'}
mask={"([000]) [000]-[0000]"}
placeholder="Phone No"
placeholderTextColor="#525252"
keyboardType={'numeric'}
/>
//save valueF in db..

It can be done as @asfaarahmed suggested but it's a workaround and not a fix. I think fixing the backspace issue for formatted value is the best way.


Update Valhalla_docker_ubuntu.md

This replaces a link to the docker hub, which does not provide the image anymore, by a GitHub package registry link.

thanks!


Reference Error: Reveal is not defined. Initialization Error

Greetings and morning all,
I am facing this unexpected issue
I have included the dependencies as shown in README.md

But on my slides, I am getting below error

I tried to include all dependencies in script tag though it's not suggested
but then I get below error.

Any help will be appreciated.
What am I doing wrong?

I just went through a similar scenario. To resolve that, you need to expose your Reveal instance to the global Window object, as demonstrated below:
import Reveal from "reveal.js";

window.Reveal = new Reveal(deckDivRef.current, {
            transition: "slide",
            multiplex: {
                "secret": null, // fill for master execution
                "id": "35c115997a5e0645", //it must be Id here - the lib will convert to socketId
                "url": 'https://reveal-multiplex.glitch.me/' // Location of socket.io server
            },
            dependencies: [
                { src: 'https://reveal-multiplex.glitch.me/socket.io/socket.io.js', async: true },
                { src: 'https://reveal-multiplex.glitch.me/client.js', async: true } // or server
            ],
            // other config options
        });

I hope it helps.
Stay safe!

THANK YOU !! @jungleBadger
i was struggling with this issue and your solution fixed it i am using vite without a framework


Nice explanation of async and await

Just wanted to say nice job on this tutorial on async/await.  Easy to understand, and great examples.

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

ID: 17d27a0d-c072-8c9f-7e31-3de60bee9ae8
Version Independent ID: e0c09794-e712-19ff-cb9f-12648d60d4f6
Content: Asynchronous programming in C#
Content Source: docs/csharp/programming-guide/concepts/async/index.md
Product: dotnet-csharp
Technology: csharp-async
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

closing as kudos.


Crash when use ImageFileReader read jpeg

Description
If compile with release version. When I use ImageFileReader read some broke jpeg image, it's crash in Update function. I expected throw an exception.
But success in Debug.
Steps to Reproduce
Build With Release.
https://gist.github.com/Hconk/5b1bed75ebb3c62757277a1367d61edb
Expected behavior
If image broke, expect throw an exception.
Actual behavior
Crash at update.

Reproducibility
Release Version.
Versions
c4960ee19c
Environment

CMake:  3.21.1
OS: Centos 7.3 / Windows 10
ITK Version:  5.2.1 / master branch
compile: gcc10.2 / gcc 4.8 / vs2017

Additional Information
Test data.
Google Drive

I can't reproduce your error with a recent master 05ae9a5061555598bff524ff958fca66aa5b37db.
#include <itkJPEGImageIO.h>
#include <itkImageFileReader.h>

int main(int, char**) {
  constexpr unsigned int Dimension = 2;
  using PixelType = unsigned char;
  using ImageType = itk::Image<PixelType, Dimension>;
  itk::JPEGImageIO::Pointer io;
  io = itk::JPEGImageIO::New();
  itk::ImageFileReader<ImageType>::Pointer JPEGReader;
  JPEGReader = itk::ImageFileReader<ImageType>::New();
  JPEGReader->SetFileName("C:/a/211869_09365_55_55.jpg");
  JPEGReader->SetImageIO(io);
  try
  {
    JPEGReader->Update();
    std::cout << *JPEGReader->GetOutput();
  }
  catch (itk::ExceptionObject& err)
  {
    std::cerr << "ExceptionObject caught !" << std::endl;
    std::cerr << err << std::endl;
  }

  std::cout << "ITK Read Jpeg Demo.\n";
  return 0;
}

produces
Image<PHONE_NUMBER>779BF0)
  RTTI typeinfo:   class itk::Image<unsigned char,2>
  Reference Count: 1
  Modified Time: 76
  Debug: Off
  Object Name:
  Observers:
    none
  Source:<PHONE_NUMBER>7745B0)
  Source output name: Primary
  Release Data: Off
  Data Released: False
  Global Release Data: Off
  PipelineMTime: 68
  UpdateMTime: 77
  RealTimeStamp: 0 seconds
  LargestPossibleRegion:
    Dimension: 2
    Index: [0, 0]
    Size: [1200, 1400]
  BufferedRegion:
    Dimension: 2
    Index: [0, 0]
    Size: [1200, 1400]
  RequestedRegion:
    Dimension: 2
    Index: [0, 0]
    Size: [1200, 1400]
  Spacing: [1, 1]
  Origin: [0, 0]
  Direction:
1 0
0 1

  IndexToPointMatrix:
1 0
0 1

  PointToIndexMatrix:
1 0
0 1

  Inverse Direction:
1 0
0 1

  PixelContainer:
    ImportImageContainer<PHONE_NUMBER>779E20)
      RTTI typeinfo:   class itk::ImportImageContainer<unsigned __int64,unsigned char>
      Reference Count: 1
      Modified Time: 74
      Debug: Off
      Object Name:
      Observers:
        none
      Pointer:<PHONE_NUMBER>9BF070
      Container manages memory: true
      Size: 1680000
      Capacity: 1680000
ITK Read Jpeg Demo.

C:\Misc\Tester\Debug\tester.exe (process 29296) exited with code 0.

Did you test with the release version? I only reproduce in release.

I tried both Debug and RelWithDebInfo builds, and they both work.

On Debian 10 the files crashes everything related to ITK's JPEG IO: my app, Slicer (tested nightly build), that test program. In Release and RelWithDebInfo builds, Debug builds survive. Eye of Mate and Gimp doesn't crash. The file is broken. I don't hope that RelWithDebInfo can be useful, points c in my app and test app to different code, not sure. Probably Debug build and Valgrind might help. I shall try later to look closer, that crash in my paid program is worrying.

Probably i have done a temporary fixed...
The error happens in jpeg_destroy_decompress(&cinfo); I have re-written several times the Read function to find it out and tested version 4.12 with system JPEG (also crashed, BTW). So finally i looked inside Gimp code (Gimp doesn't fail on the file).
The minimal solution is to add if (setjmp (jerr.setjmp_buffer)) block at the beginning of the while loop
  // read the bulk data
  unsigned int remainingRows;
  while (cinfo.output_scanline < cinfo.output_height)
  {
    if (setjmp (jerr.setjmp_buffer))                // <------------------------
    {                                                             // <------------------------
      std::cout << "goto quit:" << std::endl;  // <------------------------
      goto quit;                                             // <------------------------
    }                                                            // <------------------------
    remainingRows = cinfo.output_height - cinfo.output_scanline;
    jpeg_read_scanlines(&cinfo, &row_pointers[cinfo.output_scanline], remainingRows);
  }

and quit: before jpeg_destroy_decompress at the end of Read function, to skip jpeg_finish_decompress call in case of an error.
quit:             // <-------------------
  // destroy the decompression object
  jpeg_destroy_decompress(&cinfo);

  delete[] row_pointers;
}

@Hconk May be you could validate?
P.S. Please don't write me that "goto" is bad. It is not the final solution, it is minimal working for now. There several possible another non-critical issues in the function, specially remainingRows in jpeg_read_scanlines, at a first look sseem that this may be a mistake and some rows are processed many times. Also  row_pointer new/delete can be easily avoided, IMHO.

@issakomi Thanks, I validate your patch code, It's work for me, This problem has bothered me for a long time.

I tried both Debug and RelWithDebInfo builds, and they both work.

Thanks for you tried, I use Github Action build this demo to reproduce this case.
Demo Project: https://github.com/Hconk/ReadJpegDemo
Test  with Debug result: https://github.com/Hconk/ReadJpegDemo/runs/4466987270?check_suite_focus=true
Test  with Release result: https://github.com/Hconk/ReadJpegDemo/runs/4466987349?check_suite_focus=true
I temporarily use @issakomi solution to fix the problem.If the final solution is updated, I would be happy to verify.

@Hconk  Thank you for testing.
If ITK wish the change, s.
https://github.com/InsightSoftwareConsortium/ITK/compare/master...issakomi:jpegio
It is exactly the same, but probably closer to ITK style.
For reference s. similar GIMP approach
P.S.

There are several possible another non-critical issues in the function, specially remainingRows in jpeg_read_scanlines

It is OK, probably no issue here, tested return values of jpeg_read_scanlines, usuall 1-2 lines are de-facto read, but passing max lines is valid.

@issakomi Great, I need process large number of images, some warnning maybe help me find broken image. Thanks for your work.

Maybe i am going to understand where the undefined behavior is from (that strange issues with Debug/Release, different Valgrind error, etc). I suspect that wrapping of setjmp may be the issue, it is extremely sensitive macro, i shall check it and probably make a PR, maybe.

Yes. Wrapping of setjump here is bug.
I have replaced wrapSetjmp(itk_jpeg_error_mgr & jerr) everywhere with (setjmp(jerr.setjmp_buffer)) without that temporary fix above and results of the test program is:
r@deb:~/Desktop/test_jpeg/build$ ./readjpeg
ExceptionObject caught !

itk::ExceptionObject (0x555e03ae2d40)
Location: "unknown"
File: /home/r/itkf/ITK/Modules/IO/JPEG/src/itkJPEGImageIO.cxx
Line: 202
Description: ITK ERROR: JPEGImageIO(0x555e03adee50): libjpeg could not read file: bug.jpg

ITK Read Jpeg Demo.

I shall look closer.

https://github.com/InsightSoftwareConsortium/ITK/compare/master...issakomi:jpeg
Only itkJPEGImageIO changed.
Works as expected, WIP.
There are also some style changes, sorry auto and reinterpret_cast hurt my eyes in extern C function, the file is primary for my own usage.

Only C-style instead auto and reinterpret_cast in extern "C" function and this possible leak here may be considered as optional, all the rest is required, IMHO.

Could a PR please be made with the "minimal" fix?

@blowekamp  it was my 1st idea to use the solution from this post and stay with 6-lines patch. But then I had tried to turn (setjmp(jerr.setjmp_buffer)) into wrapSetjmp(err) to be consistent with the style of the class and added a warning, strange issues appeared. I replaced other wraps with direct  setjumps and this changed the behavior again, s. post.

BTW, i realized that JPEG errors are supressed
METHODDEF(void) itk_jpeg_output_message(j_common_ptr) {}
With error output enabled the messages for the file are:
Corrupt JPEG data: premature end of data segment
Unsupported marker type 0x02

@dzenanz @issakomi
I found some specially constructed png image also cause crash. When I use PNGImageIO read it ,will got some libpng error infomation libpng error: PNG unsigned integer out of range then crash. I think it's need throw exception.
Although it is not generated in a real scene, may also need to be fixed. (Maybe need open a new issue.)
Example test data: https://drive.google.com/file/d/1wRMTQlz31lwccha9hdPb-uTwNXD77nZv/view?usp=sharing
image sha256: f82d996c02975eecbdf0823bad5047124d3d146a0fb8804e377c35838ed264b8
Good image:
λ Desktop itk_demo → cat ./good.png | xxd -u
00000000: 8950 4E47 0D0A 1A0A 0000 000D 4948 4452  .PNG........IHDR
00000010: 0000 0001 0000 0001 0100 0000 0037 6EF9  .............7n.
00000020: 2400 0000 1049 4441 5478 9C62 6001 0000  $....IDATx.b`...
00000030: 00FF FF03 0000 0600 0557 BFAB D400 0000  .........W......
00000040: 0049 454E 44AE 4260 82                   .IEND.B`.

Broken png image hex:
λ Desktop itk_demo → cat ./corrupted.png | xxd -u
00000000: 8950 4E47 0D0A 1A0A 0000 000D 4948 4452  .PNG........IHDR
00000010: 0000 0001 0000 0001 0100 0000 0037 6EF9  .............7n.
00000020: 24FF 0000 1049 4441 5478 9C62 6001 0000  $....IDATx.b`...
00000030: 00FF FF03 0000 0600 0557 BFAB D400 0000  .........W......
00000040: 0049 454E 44AE 4260 82                   .IEND.B`.

The difference between the two pictures is at the 0x21st byte.

Thank you!
Yes, the same, on Debian 10: my app and Slicer crash, Eye of Mate and Gimp don't:

Fixed in WIP branch
https://github.com/InsightSoftwareConsortium/ITK/compare/master...issakomi:pngio

:clap: :pray: thanks @issakomi for the patches! Can this issue now be close?

👏 🙏 thanks @issakomi for the patches! Can this issue now be close?

Yes, the problem is solved.


Question: How to temporally disable Pywal?

I'm troubleshooting some conflicts with Emacs themes and I would like to temporally disable Pywal to see how that affects Emacs, but I couldn't find an option for this in the command line arguments.
Is there an easy way to do this without editing the .bashrc file?
Thanks!

Since Pywal changes terminal colors through escape sequences it wouldn't be clean to have that kind of option. Pywal is "as out of the way as possible", so if you don't want its colors when you start a session, editing the bash configuration temporarily seems like the best option. You could possibly add a variable to control whether to use Pywal colors or not, but I think commenting and uncommenting the line temporarily is a good enough way to do it.

Yeah, sounds reasonable. Thanks @alt-romes


git test 3 md file

@ebeshero

@luh429 Nice work with Git Test part 3! have pulled in your branch to main and deleted your branch on the remote repo. You can now delete the logan-gitTest3 branch in your local version of the textAnalysis-Hub.


Update from 1.14.1 to 1.15.0-rc "This pull request is broken due to missing fork information." after updating PR

I am running gitea within a docker.

1.14.1 create PR
update gitea to 1.15.0
update branch which is already an PR
"This pull request is broken due to missing fork information."

Also branches with PRs created post gitea update have the same issue.
There were already similar problems (#11105, #11196) and I followed the suggested solution if possible but without success.

Gitea version (or commit ref): 1.15.0-rc1
Git version: 2.32.0
Operating system: Debian 10
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No

@JHenneberg we need logs gitea print out to specify the issue

Is there any easy way to sanitize the logs automatically?

There is no  ...[E]… entry so gitea did not log an issue

Does pushing an empty commit fix it?

There is no  ...[E]… entry so gitea did not log an issue

I realised this two.

Does pushing an empty commit fix it?

I did git commit --allow-empty -m "Empty commit"
Did not fix the problem

Is this docker?

Is this docker?

Yes it it.

I bet this is an alpine 3.14 seccomp related issue.

See https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0

We're hopefully about to release RC2 where we've reverted back to 3.13 because of these issues.
As alpine 3.14 percolates through the docker ecosystem users are going to be forced to update their docker installations to take account of its requirements, however, it's not our intention to force our users to do that right now.

Updated installation to 1.15.0-rc2 (it's the same as @JHenneberg ones) and it worked again, thanks!
BTW: "latest" on Docker Hub points to 1.15.0-rc2, should be 1.14.5 ?

That is a long story you can search our issues db for things relating to that and look at #16421
However, this problem is fixed therefore I'm closing and marking as a duplicate of #16428


Cannot validate IPv4-Mapped IPv6 Addresses correctly

It can identify isIPv4MappedAddress but cannot catch invalid IPv4 like ::FFFF:<IP_ADDRESS>00
ipaddr.IPv6.isValid('::FFFF:<IP_ADDRESS>00') will return true.

Good catch.

Fixed in 5c52dae107.


[bug] the webview crashes on release target

Describe the bug
I'm building an application that will be used by Skyrim Modders. The application is launched through an app called Mod Organizer 2 (this app uses something called vfs for virtual filesystem).
I built the app first with electron 3 years ago. Today, I want to migrate to tauri to reduce the bundle size and memory usage.
When starting the app exe from Windows Explorer, the Webview starts and the application is working.
When starting the app with Mod Organizer 2, the Webview starts and you can see the app menu, a blank window app and finally the app crashes with the below stack trace.
You could say

"ok, this is a problem with Mod Organizer"

but why when I built the app with electron, I did not have this problem.
I need help debugging this.uses
Reproduction
To reproduce, make sure to have all Tauri requisites.
Node 18, pnpm 8.
You will need an MO2 environment and Skyrim LE/SE/AE game.
Inside MO2, you need to have an executable, for example ↓

repository: https://github.com/Kiyozz/papyrus-compiler-app-tauri and branch main.

pnpm i
pnpm tauri:build
start MO2
start the release target PCA.exe with MO2

Expected behavior
The webview starts successfully.
Platform and versions
[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 114.0.1823.67
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.70.0 (90c541806 2023-05-31)
    ✔ Cargo: 1.70.0 (ec8a8a0ca 2023-04-25)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.16.1
    - pnpm: 8.6.7
    - yarn: 1.22.19
    - npm: 9.5.1

[-] Packages
    - tauri [RUST]: 1.4.1
    - tauri-build [RUST]: 1.2.1
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.4.0
    - @tauri-apps/cli [NPM]: 1.4.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
[0711/235617.970:ERROR:check.cc(239)] Check failed: false.
[0711/235619.250:ERROR:check.cc(239)] Check failed: false.
thread 'main' panicked at 'error while running PCA application: Runtime(CreateWebview(WebView2Error(WindowsError(Error { code: 0x8000FFFF, message: Défaillance irrémédiable }))))', src\main.rs:156:10
stack backtrace:
   0:     0x7ff756613a52 - std::backtrace_rs::backtrace::dbghelp::trace
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\..\..\backtrace\src\backtrace\dbghelp.rs:98
   1:     0x7ff756613a52 - std::backtrace_rs::backtrace::trace_unsynchronized
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\..\..\backtrace\src\backtrace\mod.rs:66
   2:     0x7ff756613a52 - std::sys_common::backtrace::_print_fmt
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\sys_common\backtrace.rs:65
   3:     0x7ff756613a52 - std::sys_common::backtrace::_print::impl$0::fmt
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\sys_common\backtrace.rs:44
   4:     0x7ff75663712b - core::fmt::write
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\core\src\fmt\mod.rs:1254
   5:     0x7ff75660e0ea - std::io::Write::write_fmt<std::sys::windows::stdio::Stderr>
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\io\mod.rs:1698
   6:     0x7ff75661379b - std::sys_common::backtrace::_print
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\sys_common\backtrace.rs:47
   7:     0x7ff75661379b - std::sys_common::backtrace::print
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\sys_common\backtrace.rs:34
   8:     0x7ff75661653a - std::panicking::default_hook::closure$1
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:269
   9:     0x7ff7566161a0 - std::panicking::default_hook
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:288
  10:     0x7ff756616c16 - std::panicking::rust_panic_with_hook
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:691
  11:     0x7ff756616b0e - std::panicking::begin_panic_handler::closure$0
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:582
  12:     0x7ff7566146f9 - std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure_env$0,never$>
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\sys_common\backtrace.rs:150
  13:     0x7ff756616820 - std::panicking::begin_panic_handler
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:578
  14:     0x7ff7566659a5 - core::panicking::panic_fmt
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\core\src\panicking.rs:67
  15:     0x7ff756665ec6 - core::result::unwrap_failed
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\core\src\result.rs:1687
  16:     0x7ff75618a15e - hashbrown::raw::RawTable<T,A>::find::{{closure}}::hbd65138ff87abba1
  17:     0x7ff75608bce6 - std::sys_common::backtrace::__rust_begin_short_backtrace::h087c7fe55efd3565
  18:     0x7ff75623fd9c - std::rt::lang_start::{{closure}}::haecab8e9fd2e039a
  19:     0x7ff75660742e - core::ops::function::impls::impl$2::call_once
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\core\src\ops\function.rs:287
  20:     0x7ff75660742e - std::panicking::try::do_call
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:485
  21:     0x7ff75660742e - std::panicking::try
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:449
  22:     0x7ff75660742e - std::panic::catch_unwind
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panic.rs:140
  23:     0x7ff75660742e - std::rt::lang_start_internal::closure$2
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\rt.rs:148
  24:     0x7ff75660742e - std::panicking::try::do_call
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:485
  25:     0x7ff75660742e - std::panicking::try
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panicking.rs:449
  26:     0x7ff75660742e - std::panic::catch_unwind
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\panic.rs:140
  27:     0x7ff75660742e - std::rt::lang_start_internal
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library\std\src\rt.rs:148
  28:     0x7ff75618b9bc - main
  29:     0x7ff75663fe24 - invoke_main
                               at D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
  30:     0x7ff75663fe24 - __scrt_common_main_seh
                               at D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
  31:     0x7ffb68c126ad - BaseThreadInitThunk
  32:     0x7ffb69e8a9f8 - RtlUserThreadStart

### Additional context

You may say that this is hard to reproduce because of the setup, but maybe someone comes across and help debug this!

Thanks you everyone that help into this!

Without looking too much into it (= without testing it myself) there are a few upstream issues with the same error code: https://github.com/MicrosoftEdge/WebView2Feedback/issues?q=0x8000FFFF+is%3Aissue - most seem to be permissions related, are you running mo as admin? The other issues don't seem related but hard to say rn 🤔
p.s. thx for the report :)

MO2 is not started as admin, as everyone should 😝
I know this is hard to test 🥲


Add possibility to request compiler's JSON output

With the JSON output it would be possible to reorder / tweak messages if needed.
E.g. my IRC bot could use it to prefer showing error messages instead of warnings.

Do you know how stable the output of the JSON format is? It might be better for the playground itself to use it, instead of scraping the stdout/stderr. Then the next thing would be to figure out how to expose it.
As a heads-up, the /meta/version/ route has no stability guarantees as it's not intended for public use. the /execute route is (unfortunately) stable because so much relies on it. So stable, in fact, that I'd be pretty hesitant to even add fields to it!

I'm not sure how stable the output format is, but the compiler let's you use it on the stable channel, so I hope it is? :crossed_fingers:
At any rate, here's what cargo/rustc outputs for the code given in the linked issue (quite verbose IMO):
{
  "message": {
    "children": [
      {
        "children": [],
        "code": null,
        "level": "note",
        "message": "#[warn(dead_code)] on by default",
        "rendered": null,
        "spans": []
      }
    ],
    "code": {
      "code": "dead_code",
      "explanation": null
    },
    "level": "warning",
    "message": "static item is never used: `X`",
    "rendered": null,
    "spans": [
      {
        "byte_end": 40,
        "byte_start": 16,
        "column_end": 29,
        "column_start": 5,
        "expansion": null,
        "file_name": "src/main.rs",
        "is_primary": true,
        "label": null,
        "line_end": 2,
        "line_start": 2,
        "suggested_replacement": null,
        "text": [
          {
            "highlight_end": 29,
            "highlight_start": 5,
            "text": "    static X: u8 = [1,2][4];"
          }
        ]
      }
    ]
  },
  "package_id": "foo 0.1.0 (path+file:///tmp/foo)",
  "reason": "compiler-message",
  "target": {
    "crate_types": [
      "bin"
    ],
    "kind": [
      "bin"
    ],
    "name": "foo",
    "src_path": "/tmp/foo/src/main.rs"
  }
}
{
  "message": {
    "children": [],
    "code": {
      "code": "E0080",
      "explanation": "\nThis error indicates that the compiler was unable to sensibly evaluate an\nconstant expression that had to be evaluated. Attempting to divide by 0\nor causing integer overflow are two ways to induce this error. For example:\n\n```compile_fail,E0080\nenum Enum {\n    X = (1 << 500),\n    Y = (1 / 0)\n}\n```\n\nEnsure that the expressions given can be evaluated as the desired integer type.\nSee the FFI section of the Reference for more information about using a custom\ninteger type:\n\nhttps://doc.rust-lang.org/reference.html#ffi-attributes\n"
    },
    "level": "error",
    "message": "constant evaluation error",
    "rendered": null,
    "spans": [
      {
        "byte_end": 39,
        "byte_start": 31,
        "column_end": 28,
        "column_start": 20,
        "expansion": null,
        "file_name": "src/main.rs",
        "is_primary": true,
        "label": "index out of bounds: the len is 2 but the index is 4",
        "line_end": 2,
        "line_start": 2,
        "suggested_replacement": null,
        "text": [
          {
            "highlight_end": 28,
            "highlight_start": 20,
            "text": "    static X: u8 = [1,2][4];"
          }
        ]
      }
    ]
  },
  "package_id": "foo 0.1.0 (path+file:///tmp/foo)",
  "reason": "compiler-message",
  "target": {
    "crate_types": [
      "bin"
    ],
    "kind": [
      "bin"
    ],
    "name": "foo",
    "src_path": "/tmp/foo/src/main.rs"
  }
}

This seems to be the definition of format https://github.com/rust-lang/rust/blob/932c736479f43dc8893a924946e4335d8e308c2e/src/libsyntax/json.rs#L94


[HW] SINI T P

Name:  Sini T P
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/sini-t-p-11846a169/
Attach the homework screenshots below:

I am sorry , couldnt take screenshot of every step. I have attached images of the final steps.
I have inserted a movie named BAHUBALI in FANTASY genre.
Excited for the badge!!

Hello,
oohhh you submitted the Netflix assignments in the tiktok repository. No worries the badge will be the netflix one.
Great Job, thank you for your work.
Here is your badge:
<EMAIL_ADDRESS>

Thank you so much to this opportunity!!!
On Tue, Jun 15, 2021, 12:46 Cedrick Lunven @.***> wrote:

Hello,
oohhh you submitted the Netflix assignments in the tiktok repository. No
worries the badge will be the netflix one.
Great Job, thank you for your work.
Here is your badge:
@.***
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/datastaxdevs/workshop-astra-tik-tok/issues/63#issuecomment-861246632,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDKVZKMWL3XV3NSXQCG3CLTS346HANCNFSM46NMDVMQ
.


[QUESTION] 404 Page

Hi, I cloned the site to test on a vps, but the 404 page I get is the default Nginx 404 page. How do you get it to show your custom 404 page?

You'll need to specify the 404 page in your nginx.conf file. More info here: https://gohugo.io/templates/404/		On Sun, 23 Jul 2023 04:47:43 GMT, @.*** wrote:Hi, I cloned the site to test on a vps, but the 404 page I get is the default Nginx 404 page. How do you get it to show your custom 404 page?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
--d71b77da6a4be2a957bb85c804215c1364cc4d11ecf3767e8cc0776ca00a
Content-Transfer-Encoding: binary
Content-Type: text/html; charset=UTF-8
You'll need to specify the 404 page in your nginx.conf file. More info here: https://gohugo.io/templates/404/On Sun, 23 Jul 2023 04:47:43 GMT, ae5960e8-a6fc-491f-b252-898ecf59af95Hi, I cloned the site to test on a vps, but the 404 page I get is the default Nginx 404 page. How do you get it to show your custom 404 page?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>--d71b77da6a4be2a957bb85c804215c1364cc4d11ecf3767e8cc0776ca00a--

You'll need to specify the 404 page in your nginx.conf file. More info here: https://gohugo.io/templates/404/


Pull up the newBuilder method from Buildable to IterableOps.

And also:

Rename newBuilder to newSpecificBuilder.
Rename Buildable to StrictOptimizedIterableOps.
Add XxxWithBuilder variants to all kinds of factories.

But the main change is that now all Iterabe have this protected method that makes it possible to create a strict builder for them. This change is supposed to make it simpler to provide default implementations for several methods (such as groupBy, see #108). It might also simplify #97.

I also just added a commit that removes builders from mutable collections. I don’t think they are useful: the main purpose of builders is to make it possible to build immutable collections in an imperative way. We don’t need that for mutable collections.

I have to say I'm not very fond of all of the formulaic boxing and indirection in the factory companions.  Isn't there some way using package private to avoid indirection by allowing "delegation" to just be returning the same object with a different type?
Regarding allowing strict builders, I like in principle the idea of having them available when needed (though not the easiest thing to use), but I'm having trouble fully grasping the consequences especially for correctness: can you get violations of expected behavior if you don't manually keep both up to date?

can you get violations of expected behavior if you don't manually keep both up to date?

keep both what?

I guess what I mean is: are there both strict and lazy builders for the same collections, or does one just defer to the other?  (Even if yes, I guess that's fine; it just should be documented clearly so if you change how something is built, you know to fix both places.)

We will have both strict and lazy builders for the same collections so yes, we should probably document better that.

Any objection to merge this one? I think we can still further discuss whether we want distinct XxxFactory and XxxFactoryWithBuilder or merge them.


[NFC] math_brute_force: reformat function list manually

clang-format has already been disabled here.  Make the function list a bit easier to read.  Make the currently commented out functions stand out better on a line of their own.

Merging immediately as this is non-controversial and brings no functional changes.


Support indirect syscall

Support indirect syscall since it is quite common nowadays. Sorry for mistakes if any!

Hey man, great work, sorry it took me so long to reply 😅 Only issue is r15 is a nonvolatile register, I don’t see it being saved or restored either. This code would probably work in an exe or DLL loader but would likely cause a crash if injected into a running process because it would clobber r15. If you can fix it so that r15 doesn’t get clobbered I will accept the pull request, thank you!

Thanks for pointing that out! Eliminated the usage of r15 and now should be using volatile registers only. Tested with generating .bin and injection and they worked for me. Thanks again!


jQuery

Can you remove jQuery dependency? No need for another library.
Very nice work though.

+1

+1

+1

How we can remove jquery for this?
Anybobdy find any solution for this?


Alerts

CATEGORY
Choose one

[ ] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Codecov Report

Merging #230 into master will decrease coverage by 6.78%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #230      +/-   ##
==========================================
- Coverage   66.20%   59.41%   -6.79%
==========================================
  Files         585      401     -184
  Lines       30744    12740   -18004
  Branches     3239     3239
==========================================
- Hits        20353     7570   -12783
+ Misses      10212     4991    -5221
  Partials      179      179

Flag
Coverage Δ

#javascript
59.41% <ø> (ø)

#python
?

Impacted Files
Coverage Δ

superset/sql_validators/base.py

superset/commands/exceptions.py

superset/db_engine_specs/exasol.py

superset/db_engine_specs/cockroachdb.py

superset/queries/filters.py

superset/viz_sip38.py

superset/connectors/sqla/models.py

superset/dashboards/commands/delete.py

superset/security/analytics_db_safety.py

superset/views/datasource.py

... and 171 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 92b843e...a5aec0a.


Use same filenames in different folders can hide results

Describe the bug
If you have same filenames along the project, this can lead to override reports inside of coverage.xml
To Reproduce
How can we reproduce the problem?  Please be specific. Don't just link to a failing CI job. Answer the questions below:

What version of Python are you using? Python 3.7.6
What version of coverage.py are you using? The output of coverage debug sys is helpful. 5.1
What versions of what packages do you have installed? The output of pip freeze is helpful.

aniso8601==8.0.0
attrs==19.3.0
click==7.1.1
coverage==5.1
Flask==1.1.2
Flask-RESTful==0.3.8
gunicorn==20.0.4
importlib-metadata==1.6.0
itsdangerous==1.1.0
Jinja2==2.11.2
MarkupSafe==1.1.1
more-itertools==8.2.0
packaging==20.3
pluggy==0.13.1
py==1.8.1
pyparsing==2.4.7
pytest==5.4.1
pytest-cov==2.8.1
pytest-html==2.1.1
pytest-metadata==1.8.0
pytz==2019.3
six==1.14.0
wcwidth==0.1.9
Werkzeug==1.0.1
zipp==3.1.0

What code are you running?  Give us a specific commit of a specific repo that we can check out.
What commands did you run?

In a project with two folders with different names, both using same filenames, just one of the files will appear in coverage.xml.
dir1
   file1.py
dir2
   file1.py

Expected behavior
Even with same filename, files would be shown with in coverage.xml
Additional context
Add any other context about the problem here.

Can you provide more details?  I tried a simple example, and didn't see the problem.
With this code layout:
├── dir1
│   ├── __init__.py
│   └── file1.py
├── dir2
│   ├── __init__.py
│   └── file1.py
└── prog.py

I get both file1.py's listed in the XML report:
<?xml version="1.0" ?>
<coverage version="6.1.3a0" timestamp="1637543489454" lines-valid="4" lines-covered="4" line-rate="1" branches-covered="0" branches-valid="0" branch-rate="0" complexity="0">
        <!-- Generated by coverage.py: https://coverage.readthedocs.io/en/6.1.3a0 -->
        <!-- Based on https://raw.githubusercontent.com/cobertura/web/master/htdocs/xml/coverage-04.dtd -->
        <sources>
                <source>/System/Volumes/Data/root/src/bugs/bug978</source>
        </sources>
        <packages>
                <package name="." line-rate="1" branch-rate="0" complexity="0">
                        <classes>
                                <class name="prog.py" filename="prog.py" complexity="0" line-rate="1" branch-rate="0">
                                        <methods/>
                                        <lines>
                                                <line number="1" hits="1"/>
                                                <line number="2" hits="1"/>
                                        </lines>
                                </class>
                        </classes>
                </package>
                <package name="dir1" line-rate="1" branch-rate="0" complexity="0">
                        <classes>
                                <class name="__init__.py" filename="dir1/__init__.py" complexity="0" line-rate="1" branch-rate="0">
                                        <methods/>
                                        <lines/>
                                </class>
                                <class name="file1.py" filename="dir1/file1.py" complexity="0" line-rate="1" branch-rate="0">
                                        <methods/>
                                        <lines>
                                                <line number="1" hits="1"/>
                                        </lines>
                                </class>
                        </classes>
                </package>
                <package name="dir2" line-rate="1" branch-rate="0" complexity="0">
                        <classes>
                                <class name="__init__.py" filename="dir2/__init__.py" complexity="0" line-rate="1" branch-rate="0">
                                        <methods/>
                                        <lines/>
                                </class>
                                <class name="file1.py" filename="dir2/file1.py" complexity="0" line-rate="1" branch-rate="0">
                                        <methods/>
                                        <lines>
                                                <line number="1" hits="1"/>
                                        </lines>
                                </class>
                        </classes>
                </package>
        </packages>
</coverage>

Feel free to re-open this if you can provide more information.


Test the lighting system

The lighting system is self contained and easily testable. There are also a lot of cases to be tested. I would write a test suite first by testing specific universes with specific editing and then by generating universes, edits and final states automatically.
Maybe the slow 16 pass propagation algorithm is simple enough to verify correctness first and use for test validation?
Otherwise, coming up with the automatic test generation would be tricky.

Added the initial test cases for torchlight propagation. Missing sunlight tests and some fuzzying.


Need to have some "monitor board" over each slide (or folder)

I attached some suggestion. It would be great if we can have a box (which shows if we click a certain button) at the top of each slide showing:

Annotation style/group stats for each slide
Checkboxes for QC (quality control), at least three boxes -- QC1, QC2, QC3
Text box for free notes

For now maybe we can just add element totals next to the styles? Something like this

@cooperlab Would those values be the number of annotations or the number of elements (e.g., the total of all polygons in all annotations)?


int.ToString(CultureInfo) hasn't been implemented.

I'm trying to port System.Windows.Forms to Bridge and came across this problem. More information about the CultureInfo here.

I guess you can use IFORMATPROVIDER version
https://github.com/bridgedotnet/Bridge/blob/master/Bridge/System/Int32.cs#L41


Add data for :read-only and :read-write selector

Add by MDN data.
@Fyrd this R is important fo next Autoprefixer release https://github.com/postcss/autoprefixer/issues/543#issuecomment-149341212

@Fyrd fixed. Sorry for quick PR :D. Not I check JSON and it is valid.

Thanks!

Awesome! Wait for release.

@Fyrd what I can do to release it quicker? :)

@ai I just tested a couple of browsers and your data seems incorrect in various places:

Firefox should have partial support because it doesn't consider disabled input & textarea fields as readonly
Opera 12.1 (and probably older ones too) appear to have partial support
Android 4.4 (and probably older) has partial support

Basically it looks like all the data needs to be reviewed. You cannot just trust MDN data and port it over to caniuse like this. If you want it released, take the time to write tests and do the browser testing yourself. I don't mind doing part of it, but since #1976 has only one vote I don't intend to make it a priority to do a full review over the higher-voted features at http://caniuse.com/issue-list/ .
I understand how just the prefixed data is all you really need for autoprefixer, but rushing partially incorrect data into caniuse is not the way to do it.

@Fyrd maybe we can hide this data from caniuse website? I think there is a field for it in JSON.

Yes, all new support data is hidden by default already.
Ah, you're waiting for it to appear in the data.json files, let me take care of that.

Okay, should be there now. I'd still recommend against using hidden data since, as in this case, it may not all be correct.

Thanks :)

See also https://github.com/w3c/csswg-drafts/issues/127


Update srdf, srdf4j, srdfjena to 0.1.105

Updates

es.weso:srdf
es.weso:srdf4j
es.weso:srdfjena

from 0.1.101 to 0.1.105.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "es.weso" } ]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #166.


Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1"

What happened:
opta apply -c flyte.yaml --auto-approve returned this error:
╷
│ Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1"
│
│   with module.helmchart.helm_release.local_chart[0],
│   on ../../../.opta/modules/helm_chart/tf_module/main.tf line 18, in resource "helm_release" "local_chart":
│   18: resource "helm_release" "local_chart" {
│
╵

How to reproduce it (as minimally and precisely as possible):
I followed this instruction with two changes:

I deleted these lines from `env.yaml':

  - type: dns
    domain: <domain>
    delegated: false # set to true once ready https://docs.opta.dev/miscellaneous/ingress/

I changed files .opta/modules/aws_s3/aws-s3.yaml, .opta/modules/aws_s3/tf_module/replication.tf, .opta/modules/aws_base/tf_module/log_bucket.tf to remove public access blocks for s3 buckets.

Environment:

Opta version (use opta version): v0.24.3
Cloud provider (or hardware configuration for local): AWS
OS (e.g: cat /etc/os-release): Ubuntu 20.04
Kernel (e.g. uname -a):
Install tools:
Others:

Hi @RustamovAzer, can you reconfirm the opta version as being v.0.24.3 (https://github.com/run-x/opta/tree/v0.24.3) released about 6 days ago?
Also, if you can post information about the Kubernetes cluster version (available in the AWS EKS console for example) that would be helpful. Thanks!

Checked opta version again: it is indeed v0.24.3
Kubernetes cluster version: 1.18

@RustamovAzer It's an issue with flyte because of this: https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/templates/common/ingress.yaml#L61
By default Opta is using K8s version 1.18 (we are updating this on our next release so this will not happen after that), which does not support this API version. For now, here is what you can do:

Destroy your existing cluster and manually update the k8s version in your opta yamls like this

.
.
.
  - type: k8s-cluster
    max_nodes: 15
    k8s_version: 1.21
.
.
.

Pin the flyte version to the not beta like so

.
.
.
  - type: helm-chart
    chart: "../../charts/flyte-core" # NOTE: relative path to chart
    namespace: flyte
    timeout: 600
    create_namespace: true
    values_file: "../../charts/flyte-core/values-eks.yaml" # NOTE: relative path to values yaml
    chart_version: "v0.19.1"
.
.
.

Let me know if you have any more questions or need help!

@juandiegopalomino please change k8s_version into string type in your comment for future users :)
(flyte-aws) ubuntu@ip-172-31-7-79:~$ opta apply -c flyte/opta/aws/env.yaml
Opta file validation failed with errors:
  : modules.1: k8s_version: '1.21' is not a str.
ERROR: flyte/opta/aws/env.yaml is not a valid Opta file.
If you need more help please reach out to the contributors in our slack channel at: https://slack.opta.dev


why can't I export tiles to local disk?

I use the Mapbox Studio on windows, But I can't export the tile data to local disk?Dose it must work on the server?

@wsf1990 any error message?

I cant find the function or the menu to export,Do you have the usage of studio?Many Thanks!

Links to tutorials are on the main page of this repository:
https://github.com/mapbox/mapbox-studio#getting-started
You can export vector tiles from a Source Project (after saving):

Thanks！I'll try it next day!Thanks

Dear BergWerkGIS：
I have tried to export,It's success,but why this mbtiles just have raster tile not vector tile?the table of grid_data is empty.Dose it need any settings?

why this mbtiles just have raster tile not vector tile?

I'm not quite sure I understand correctly, but are you saying that there are raster tiles in the exported mbtiles?
There shouldn't. It should contain vector tiles only, as you exported from the Source Project.
If you want to get raster tiles, you might want to look into @mojodna 's tl.
You can pass an Mapbox Studio Style Project to it and get raster tiles:
https://github.com/mojodna/tl#usage

Thanks!
I means when I exprot mbtiles and download to local disk,I open the mbtiles by sqlite program,But I found that the view of grid_data is empty,Is this view stored vector tiles?the view of tiles have the data of raster tiles,So I suppose that can it export vector tiles!
Thanks!


Rebuild API for Sikuli compatibility

Originally Lackey was designed to be a standalone automation library with optional Sikuli integration. As more Sikuli functionality is implemented, though, it makes more and more sense to just implement it as a drop-in Sikuli replacement.
This will eliminate the need for the sikuli.py shim and make it far easier to port existing Sikuli scripts.

The sikuli.py shim should be merged into Lackey's init.py.

Completed with release v0.4.0a1


Loan on documents: allow assigning specific item

When creating a loan on a document, the system automatically assigns an item when available.
We should be able to override the one automatically assigned and assign a specific valid item.

solved in #119


Space in aria-labelledby on Select component

When don't set id and labelId

in version 4.5.2

Could you explain how this is an issue?

I always run jest snapshot method, after update material-ui to version 4.5.2 I saw this different in snapshot between 4.5.1 and 4.5.2, it's correct?

I always run jest snapshot, after update material-ui to version 4.5.2 I saw this different in snapshot between 4.5.1 and 4.5.2, it's correct?

It's not pretty but it let's us skip a lot of logic when creating that attribute. As far as I'm aware (accname 1.1) this should not impact the accessible name since there are no id refs. Some tooling flags this though assuming these values are added manually. I would agree that manual values should be flagged (because why not remove it then?) but for automatic values whose integrity is verified at runtime I don't think those should be flagged.

@uxitten As long as it helps your team move faster, safer great!

@uxitten There is a recent thread about this topic on Twitter, the main point I think that we should be cautious with is https://twitter.com/ljharb/status/1190709332171583489. I have seen two organizations close to my circle fall into this trap. To be careful :).
We could fix your diff and the https://validator.w3.org/ warnings

With something like this, but, does it worth it?
diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
index e4496972b..fce4b5ce5 100644
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/packages/material-ui/src/Select/SelectInput.js
@@ -318,7 +318,7 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) {
         tabIndex={tabIndex}
         role="button"
         aria-expanded={open ? 'true' : undefined}
-        aria-labelledby={`${labelId || ''} ${buttonId || ''}`}
+        aria-labelledby={labelId || buttonId ? [labelId, buttonId].join(' ') : undefined}
         aria-haspopup="listbox"
         onKeyDown={handleKeyDown}
         onClick={disabled || readOnly ? null : handleClick}

We can fix it by this code:
aria-labelledby={`${labelId || ''}${` ${buttonId}` || ''}`}

@oliviertassinari I can take this

@uxitten Let's wait for @eps1lon feedback.

@oliviertassinari All right

My problem is that this is extremely unreadable and hides a legitimate issue with the Select component (it won't have an accessible name). As I understand these tools is that they are helpers for manually generated content. What we render isn't manually generated though. It's a shortcut to avoid unreadable code and nudge people to provide these ids.
Unless this is an actual issue with assistive technology which nobody touched upon.
Having a diff in a snapshot is not a valid reason to change something. The internal structure is not (and cannot) be considered the public API. Otherwise we would need to release a breaking change every other week.

hides a legitimate issue with the Select component

@eps1lon 👍


chore(website): expose examples on the website

Description
This PR exposes (nearly) all the examples we have on the modelina website.
It works by reading all the directories in the examples folder, and each example has some Modelina code which is read from the index.ts file, and then the output code is read from the jest snapshots.
The overview in /examples is created from https://github.com/asyncapi/modelina/blob/master/examples/README.md with a few modifications such as changing links etc, but otherwise it's the same.
Here is what this feature enables:

Show simple examples that contain modelina code and then the output.
Each example link is shareable through the query parameter /examples?selectedExample=adapting-input-and-output
Automatically updated on each website build (handles adding new examples, changes, etc.) with minimum maintenance as possible.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.323%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5017

Relevant Lines:
5298

💛  - Coveralls

each links on the navigation should have cursor-pointer class to have "pointer" cursor icon when someone will hover it

Makes sense 👍

it will be nice if code and output will be rendered in this same line, not like current, which has some "margin" gap

Let me try 👍

readme should be rendered at center :)

Good point 😄

@magicmatatjahu adapted everything 🙂


Using ONe.tweak to SkipDay may lead 'TimeOfDay ' fail to reset on the next day.

e

Hey, thanks for reporting. The ONe.Tweak plugin is not yet officially released but I'll see why that would be happening.
Have you tried some other features of the mod? Did you encounter some problems?

Hello!

Ghost mode is now available not only in practice mode, but also in normal play, so it's better to limit it for the sake of game balance；Also Clients with this mod installed can use this feature on hosts that do not have this mod installed.
Cards ,Clients can not view the extra cards in sync when the host cycle the cards.  Franchise cards selected in this way may not show properly in the card list.
By the way, I'm looking for a solution to remove a card from the selected card list, That can be a useful featrue.


Check the possibility of packaging OpenJDK with Ballerina distribution

We are working on this.

This is done in ballerina-distribution repository [1]. There we will include additional components such as docker, kubernetes and etc. Basically it will produce following distributions by embedding JRE. These will be used to create installers for each operating system.

ballerina-platform-linux-{version}.zip
ballerina-platform-macos-{version}.zip
ballerina-platform-windows-{version}.zip
ballerina-runtime-linux-{version}.zip
ballerina-runtime-macos-{version}.zip
ballerina-runtime-windows-{version}.zip

Additionally it will produce follow 2 distributions without JRE.

ballerina-platform-{version}.zip
ballerina-runtime-{version}.zip

[1] https://github.com/ballerina-platform/ballerina-distribution


fix(setup): remove duplicate pytest-mock

remove the duplicate pytest-mock installation from setup.py

Hey @BenHaimItay ,
thank you very much for your contribution. We need your commit to be signed-off before we can merge

Codecov Report
Base: 86.36% // Head: 28.69% // Decreases project coverage by -57.67% :warning:

Coverage data is based on head (c2a1c5c) compared to base (67209b8).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #872       +/-   ##
===========================================
- Coverage   86.36%   28.69%   -57.68%
===========================================
  Files         138      138
  Lines        7116     7116
===========================================
- Hits         6146     2042     -4104
- Misses        970     5074     +4104

Flag
Coverage Δ

docarray
28.69% <ø> (-57.68%)
:arrow_down:

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

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

You can check this to see how u can adapt it:
https://github.com/docarray/docarray/pull/872/checks?check_run_id=9767379599


Explicitly include spaces around parameter names

I needed to override the delimiters to match a templating language that does not include spaces around parameter names. I had to add these in the handlebars input explicitly to make it work.

There's a deeper issue here, will resend when it's resolved


Unexpected behaviour when using an Icon within ClientOnly fallback

Consider following code for your app:

<template>
  <ClientOnly>
    <template #fallback>

        <Icon name="svg-spinners:ring-resize" />
        Loading

    </template>

      This text should NOT be large!
      Remove the
ref="someRef"
 from the parent and it works

  </ClientOnly>
</template>

Expected behaviour when loading the page:
A big loading spinner, and, when everything is done loading, some normal text, like this:

Instead, you get this:

When you remove the ref="someRef" from the content div, it works as expected

Are you sure this is from Nuxt icon directly and not Nuxt itself?

Can't tell, but when you remove the  from the template, it works

Could you try with <IconCSS name="svg-spinners:ring-resize" />?

Already tried that, it doesn't work either

Can you create a reproduction with Stackblitz please?

https://stackblitz.com/edit/nuxt-icon-playground-ct93e9?file=app.vue


VAC still a problem?

Was running a nightly from half a year/year back and recently got a warning and got kicked from matches.
Does latest nightly run fine? Or is the offending element able to be disabled?
I assume it is the kernel driver causing it?

Does latest nightly run fine?

Yes. I last checked on the 28th of December, 2019 and it worked fine.

a nightly from half a year/year back

Please update to the latest nightly build and let me know if you're still having issues. I have direct contacts with Valve and can discuss issues with them anytime.

is the offending element able to be disabled?

No. Valve and all other Anticheat software doesn't use any generic scanning for some sort of generic feature because of there are too many false positives for other Windows software (especially security software) using the exact same API functions on Windows just like Process Hacker does.
If they've started blocking our binaries then even removing all the code won't resolve the issue.

I assume it is the kernel driver causing it?

No. Anticheat software uses the ObRegisterCallbacks function to limit our kernel driver without having to outright blacklist our driver or requiring us to make changes to our driver.
Microsoft added the ObRegisterCallbacks function back in 2006 for this exact reason allowing tools like Process Hacker to coexist peacefully with antivirus/anticheat software requirements.
If you ever have issues then please report this to us here on Github so we can follow up with Valve or other companies - sometimes they hire people without any knowledge or experience and they make stupid decisions that are unnecessary 👍

Thank you for taking the time to respond.
However I'm still not 100% convinced, as I read that there was no communication with valve at all? or this could be years ago im not sure.
Also processhacker is still listed on steam's website of programs that could cause problems. Is this because they are not stating version numbers? Why is this not communicated then? Like xxx version?
Thanks!

I read that there was no communication with valve at all? or this could be years ago im not sure.

Things have changed.

processhacker is still listed on steam's website of programs that could cause problems. Is this because they are not stating version numbers? Like xxx version? Why is this not communicated then?

They don't mention versions for the other products even things like powershell. It might be a policy to confuse cheaters by limiting the amount of information about what VAC does.
You can still get kicked for using Process Hacker but its extremely rare these days and you would have to be doing/running a few things to trigger the kick.


Output mode 'first'

I'm using cage with greetd/gtkgreet, and a drawing tablet (with screen). When I have my drawing tablet connected, I have two options for cage output. Either -m extend cuts the login fields in two between the two screens (as it is centred), or -m last puts the login screen on the tablet. In this case, a -m first option would make more sense, as I prefer the login screen on my main display.

Maybe we could have something like -m <output name>. Or a separate CLI flag for the output to use.


Looking for any event or property to flag RTSP stream lost

I have an issue / a question (pick one) about Vlc.DotNet.
Generic information

Vlc.DotNet.Core version :  3.0.0-develop306
Vlc.DotNet.Wpfversion :  3.0.0-develop306
Vlc.DotNet project used : WPF
libvlc version : v3.0.4 (nuget)
.net version : 4.0
Project language : C#
Project build architecture : AnyCPU
Operating system : (Windows ...) x64

Summary
I'm viewing an RTSP stream, and I was hoping to add some retry logic in the event of (temporarily) lost network. However, I can't seem to find any hook or property that lets me know "hey, everything was good, but I haven't seen any new frames in a while... probably this stream is dead."

Are you looking for EncounteredError?

I'm hooked to that, but no luck. I'm basically doing this:

Connect to test RTSP stream (rtsp://<IP_ADDRESS>/vod/mp4:BigBuckBunny_175k.mov)
Make sure everything is running fine, stream looks good
Disconnect wifi

The stream stops, obviously, but I never hit EncounteredError. I've let is sit in the disconnected state for ~5 minutes, and still nothing.

Please share full logs and your full code.

You need EndReached, EncounteredError as well as System.Net.NetworkInformation.NetworkChange.NetworkAddressChanged (and possibly a PInvoke call to InternetGetConnectedState if that's not reliable enough).
That's not a Vlc.DotNet issue though IMHO.

I don't think you need to hook into the system events.

I did have to do this (in my experience).

I don't think you need to hook into the system events.

I did have to do this (in my experience).

If I remember correctly, as long has your video has started, you will get EndReached or ErrorEncountered. I don't think you need to hook into the system events.
As for RTSP live streaming, the "end reached" event should be considered the same as an error IMHO, at least for the retry mechanism.

Thanks for the responses. Jeremy, I tried hooking up to EndReached, but no dice. I'm going to try to do what I'm doing in an example app real quick and send over the logs, etc. Because yeah, this feels like all of those handlers logically should be firing, but in my case they're not. Hold for logs!

In the process of building a simple example of the error, I think I found the source of the issue.
I was previously passing the following as media options when creating the player, so that when/if the stream ended, the control would automatically repeat it:
string[] mediaOptions = { "input-repeat=65535" };
vlcControl.SourceProvider.MediaPlayer.SetMedia(mediaUri, mediaOptions);
If I include the repeat option in the mediaOptions, the MediaPlayer.EndReached never fires when the network goes down. If I remove that option (and change it to string[] mediaOptions = {};) , it works great. The event fires when network goes down. (Note, the same is true for the "end" of the stream. When the video ends without the repeat option, EndReached fires, but with the repeat option, it doesn't fire, and there's no indication that the video ended and restarted. Not necessarily a bad thing, but FYI.)
So I don't know if this is a bug or a expected behavior. As a note, if I remove that option, then when the video stream ends (rtsp://<IP_ADDRESS>/vod/mp4:BigBuckBunny_175k.mov), the video doesn't restart. It does restart if I leave the repeat option in. For my current project, I don't expect the stream to ever end, so it's less relevant to me, but it could be relevant to others.
I think I'm going to take out the repeat option, then just handle an EndReached manually and attempt to restart the video, just the same as if a networking error had occurred.
Sample project here if it's useful: https://github.com/jnieman21/VLC.DotNet.IssueSample

Thanks for your analysis. it is indeed the expected behavior . if you repeat 3,the EndReached event is only triggered after the third loop. handling the EndReached manually offers you more flexibility, so I'd recommend that way.

Good to know. As an aside then, if I wanted to repeat forever, is there any way to get a call when the stream dies, like in the network failure case?

No, there's no way to differenciate. streams can fail for a wide variety of reasons, so I imagine that making an API for that would be hard.

Hi ,
i've found a solution which is perfectly working for me in unstable connections(for RTSP)
Setup a system timer which check the media state in a specific period of time.
`
private void Setup_WatchDog_Timer()
{
myTimer = new System.Timers.Timer(5000);
myTimer.Elapsed += new ElapsedEventHandler(myTimer_Elapsed);
myTimer.Enabled = true;
myTimer.AutoReset = true;
myTimer.Start();
    }

    public  void myTimer_Elapsed(object sender, ElapsedEventArgs e)
    {
        if(vlcModule.GetCurrentMedia().State != Vlc.DotNet.Core.Interops.Signatures.MediaStates.Playing &&
            vlcModule.GetCurrentMedia().State != Vlc.DotNet.Core.Interops.Signatures.MediaStates.Opening)
        {
            vlcModule.Stop();

            vlcModule.Play();
        }
    }

`