Container name is not in the correct format.

Hi all,
I'm trying to find the correct ProtecteditemName format for a sql in azure vm instance with the "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}" api endpoint.
Can you help me with it ?
I would have the same question with a fileshare protecteditem.
The documentation doesn't details the format : https://learn.microsoft.com/en-us/rest/api/backup/protected-items/get?view=rest-backup-2023-02-01&tabs=HTTP
The only example is for a virtual machine
Regards

Alright, I figured out how it works for a Storage Account
The name has to be of 4 parts.
"StorageContainer;Storage;<rg-name-of-storageaccount>;<nameofstorageaccount>"

For the FileShare protectedItem I figured out the following. Once you have connected the StorageAccount to the Recovery Service Vault (do this by creating a ProtectionContainer), you can list the protectableItems via this command:
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupProtectableItems?api-version=2023-02-01&$filter=backupManagementType eq 'AzureStorage' and workloadType eq 'AzureFileShare' and containerName eq 'StorageContainer;Storage;<rg-name-of-storageaccount>;<nameofstorageaccount>'

in the results, you get the name of the items. They look something like this:
"azurefileshare;41b049bea713aa9912ac12334c7aef7ba14afad1212ba051b2914fbae4adb387"


:construction: NEW: formatDate

DRAFT - DO NOT MERGE
Link to: https://github.com/techniq/svelte-ux/issues/136

Usefull to speak over the code

Using the PR preview, or did you need me to run the server on my machine?

Reading https://github.com/techniq/svelte-ux/issues/150 and with my current progress, I think that we have to do some choices now :).
For yesterday, 3 days ago, ... this is working well:
https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/Intl/RelativeTimeFormat
For date format, ... this is working well:
https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat
I started to add a dico, for things that I can't find in intl in a robust way.
https://github.com/techniq/svelte-ux/blob/feat/formatDate/packages/svelte-ux/src/lib/utils/date.ts#L97-L105

I think that we will not get rid of date-fns as there are so many good utilities and intl is only about formatting.
But, I think that formatting should be done in 1 single way either intl either date-fns, but not both (my current state!)
intl

It's cool as it's native js support (less to ship in the browser)
It's cool as it's similar to number that we did before
It's cool, with 1 string, it's supports so many locales!
It's not cool as it will be a breaking change for the lib (https://svelte-ux.techniq.dev/docs/components/DateField format will have to be done another way)

date-fns for formatting

people will be forced to add locales of date-fns
keeping the way it's done
less work as it's spread in a lot of places

Check out: https://svelte-ux-git-feat-formatdate-techniq.vercel.app/docs/utils/format#playground

Reading #150 and with my current progress, I think that we have to do some choices now :).
For yesterday, 3 days ago, ... this is working well: https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/Intl/RelativeTimeFormat
For date format, ... this is working well: https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat
I started to add a dico, for things that I can't find in intl in a robust way. https://github.com/techniq/svelte-ux/blob/feat/formatDate/packages/svelte-ux/src/lib/utils/date.ts#L97-L105
I think that we will not get rid of date-fns as there are so many good utilities and intl is only about formatting. But, I think that formatting should be done in 1 single way either intl either date-fns, but not both (my current state!)
intl

It's cool as it's native js support (less to ship in the browser)
It's cool as it's similar to number that we did before
It's cool, with 1 string, it's supports so many locales!
It's not cool as it will be a breaking change for the lib (https://svelte-ux.techniq.dev/docs/components/DateField format will have to be done another way)

date-fns for formatting

people will be forced to add locales of date-fns
keeping the way it's done
less work as it's spread in a lot of places
convenient for DateField format

I really like the idea of using Intl for all the reasons you mentioned, especially not having to manage/download locales (i.e. date-fns/locale) and the simplicity/consistency.  With that said, when I took a look at the PR preview playground, I was initial surprised by the DateField format until I realized that what one of the things you mentioned :).

I also think date-fns provides a lot of additional utility beyond formatting so I'm good with keeping it.
For DateField format default, I wonder if we just keep our own locale/format lookup for this use case.
const defaultFormat = {
  en: 'MM/dd/yyyy`,
  fr: 'dd/MM/yyyy',
  ...
}

if we overlook one, we could have it just default to 'MM/dd/yyyy' and if a user complains, we'll know which one we missed :).
We could also take a date like 2023-11-21, format it using toLocaleDateString(locale), then parse where the values ended up, but this might be overkill.
I think the simple map might be the best, as for a default, just getting MDY or DMY or YMD right is good enough.  I think always using / as a divider is probably fine too, although I know some locales (or even personal preference) might want to use - or ..
Looking at https://en.wikipedia.org/wiki/Date_format_by_country and https://docs.oracle.com/cd/E19455-01/806-0169/overview-7/index.html, I think we could build up this list fairly easily.  Maybe even make it a case statement to simplify the impl (including handling the fallback default).
Lastly, I think we should expose this format on settings() for when a dev/user wants to override the format.
How does that sound?  We can try to sync up in a few days and chat about it further if you want too.

Oups, I just read your message after spending my all afternoon on it 🤣🤞
But, I think we are thinking the same way, hahaha
Check out the update ✅
I love all tests, I'm ssssoooo confident moving things around. And if something is not tracked, it's easy to add it 👍
I tried to clean as much as possible.
I think that I would like to remove dateDisplay! to really cut format from date-fns, but it might break some people code... So I don't know....
I'll do a break now to party a bit 🎉
Speak to you soon

Happy New Year (not quite here yet)!  You've been busy 😅.
I love the idea of removing dateDisplay / consolidating into a single date format function for all use cases (or requiring dateFns format() directly when needed).  I know there is a little usage of dateDisplay within LayerChart.  There was even a commit that switched from dateFns's format() to dateDisplay(..., { format: ... }) to better handle null so it's not a 100% drop in if we require dateFns for this kind of formatting, but I'm not against it.  If you're planning to support custom format strings in formatDate() that would be awesome too (it could still use dateFns, but then I guess we're back with dealing with locales in this case).  We might just need to support more PeriodTypes for example time-only (h:mm:ss).  Full disclosure: PeriodType has/had a tight coupling with a backend aggregation solution in one of my projects.  I no longer work on that project, so I'm not as concerned anymore :).
Regarding the variants, currently we have short, and long.  I've considered switching this to sm, lg and supporting md, xxs, xl, 2xl, etc (similar to Tailwind breakpoints) as needed.  If we do switch to this variant naming, we should do the same for duration / Duration.

breakpoint
I'm not a big big fan of short & long, I added default & custom, and now I think that it's "ok".
But I like even less sm, lg, md, ...
I think that it's hard to find 6 different levels of display of a year for example! (And then, at what breakpoint you go from yy to yyyy?) => I always forget levels & breakpoints... Ok you could customize... But then, it's too much of flexibility as of today. (My 2 cents)
d, dd, eee... All this is Day, what breakpoint is what?
I think that breakpoints don't fit, maybe I'm missing something?

That's why I was thinking:

Default => Ok, by default what do we want?
Short => Let's have a good short version
Long => Let's have a good long version
Custom => to escape and do what you want

Often, Default is or short or long... (but not always the same).
I'm almost thinking: "do we even need short & long"?
dateDisplay

. If you're planning to support custom format strings in formatDate() that would be awesome too (it could still use dateFns, but then I guess we're back with dealing with locales in this case)

The custom, is already doing "a lot", and we can handle more and more cases if we have feedback.
I'll look into your commit and add different flags to help doing the same.
side node
The fns format "MM d, yyyy" is equivalent to intl format "d MM yyyy", because my "transform" takes care only about tokens, and locales + intl will do the right thing for US => "MM d, yyyy" 😉
I'm pretty happy about this cool trick. (You can also keep "MM d, yyyy")
Just not sure how to document this.

breakpoint
I'm not a big big fan of short & long, I added default & custom, and now I think that it's "ok".
But I like even less sm, lg, md, ...
I think that it's hard to find 6 different levels of display of a year for example! (And then, at what breakpoint you go from yy to yyyy?) => I always forget levels & breakpoints... Ok you could customize... But then, it's too much of flexibility as of today. (My 2 cents)
d, dd, eee... All this is Day, what breakpoint is what?
I think that breakpoints don't fit, maybe I'm missing something?

That's why I was thinking:

Default => Ok, by default what do we want?
Short => Let's have a good short version
Long => Let's have a good long version
Custom => to escape and do what you want

Often, Default is or short or long... (but not always the same).
I'm almost thinking: "do we even need short & long"?
dateDisplay

. If you're planning to support custom format strings in formatDate() that would be awesome too (it could still use dateFns, but then I guess we're back with dealing with locales in this case)

The custom, is already doing "a lot", and we can handle more and more cases if we have feedback.
I'll look into your commit and add different flags to help doing the same.
side node
The fns format "MM d, yyyy" is equivalent to intl format "d MM yyyy", because my "transform" takes care only about tokens, and locales + intl will do the right thing for US => "MM d, yyyy" 😉
I'm pretty happy about this cool trick. (You can also keep "MM d, yyyy")
Just not sure how to document this.

Breakpoint
Good points, I think it would be too much customization (especially to support).  FWIW, it's not based on viewport/breakpoints, mostly usage based on available real estate / context.  For example, LayerChart axis labels typically use short for dates since a simple MM/YY is enough context (and space constrained), and you typically use a tooltip to get more details on the date (get year, day of week, etc).  This screenshot isn't the best example, but does show the concept a little.

So really short / long is based on usage, but I like default and custom.  I wonder if we need custom but allow you to change short and long (similar to the number presets of decimal, currency, etc) and maybe let default allow you to specify short and long only?  Trying to find the sweet spot of simplicity but not overly restrictive is a delicate balance.  Thoughts?
dateDisplay
I need to get myself up to speed on DateTimeFormat and read through the PR closer, but it all sounds great.   It looks like you are mapping unicode date tokens (aka date-fns format string) to DateTimeFormat options (i.e. 'long', 'short', '2-digit', 'numeric', narrow, undefined, ...).  Looking on MDN, I was having trouble finding the full list of available options for each date part (year, month, day, etc).  Did you find a good reference?
side node
Kind of what I mentioned above, but really we're translating unicode format strings and mapping them to DateTimeFormat options.  Do this mean MM/dd/yyyy and MM-dd-yyyy and yyyy-MM-dd will also result in the same output string based on the locale, or can you still keep the explicit formatting?  I'm assuming no, which is probably OK (and using date-fns format() directly when needed is probably best for this).  How to document this (and if there is a better approach to make this more obvious if so).  Basically all that matters is each part's definition, and not the order or separators.
Side note: I'm really liking how this is coming together and I REALLY appreciate you digging in.  I knew it wouldn't be a small task, but this will be another huge improvement to Svelte UX.  Thanks for all the effort!

Breakpoint
Good points, I think it would be too much customization (especially to support).  FWIW, it's not based on viewport/breakpoints, mostly usage based on available real estate / context.  For example, LayerChart axis labels typically use short for dates since a simple MM/YY is enough context (and space constrained), and you typically use a tooltip to get more details on the date (get year, day of week, etc).  This screenshot isn't the best example, but does show the concept a little.

So really short / long is based on usage, but I like default and custom.  I wonder if we need custom but allow you to change short and long (similar to the number presets of decimal, currency, etc) and maybe let default allow you to specify short and long only?  Trying to find the sweet spot of simplicity but not overly restrictive is a delicate balance.  Thoughts?
dateDisplay
I need to get myself up to speed on DateTimeFormat and read through the PR closer, but it all sounds great.   It looks like you are mapping unicode date tokens (aka date-fns format string) to DateTimeFormat options (i.e. 'long', 'short', '2-digit', 'numeric', narrow, undefined, ...).  Looking on MDN, I was having trouble finding the full list of available options for each date part (year, month, day, etc).  Did you find a good reference?
side node
Kind of what I mentioned above, but really we're translating unicode format strings and mapping them to DateTimeFormat options.  Do this mean MM/dd/yyyy and MM-dd-yyyy and yyyy-MM-dd will also result in the same output string based on the locale, or can you still keep the explicit formatting?  I'm assuming no, which is probably OK (and using date-fns format() directly when needed is probably best for this).  How to document this (and if there is a better approach to make this more obvious if so).  Basically all that matters is each part's definition, and not the order or separators.
Side note: I'm really liking how this is coming together and I REALLY appreciate you digging in.  I knew it wouldn't be a small task, but this will be another huge improvement to Svelte UX.  Thanks for all the effort!

🥳🥳🥳 Youhouuu, I think I'm getting close to something I like (and hopefully you too 😉)
Trying to summarize:
You can configure presets for days, weeks, months, monthsYears, years with => short, default and long variants. These variants are either tokens either intlOptions (it's beautiful!)
Then, when you call format, you pass the PeriodType and the variant. (Or you can always pass custom and do what you want).
By default, everything is configured, but you can tweak a lot... I think that it's a quite nice balance spot.
I didn't find a great mapping with token, but did it case by case. And now that we can anyway pass all intlOption, I think that it's a sweet spot too.
I'll remove the draft more for you too have a lot a comment the code maybe?
One thing I have in my todo list is to replace the dateDisplay documentation page with a format dedicated to Date. What do you think?

Few changes I noticed (mostly just tracking, not saying they need to be changed yet).
DateRangeField
The range now shows numeric instead of month abbreviations (12/29/2023 instead of Dec 29, 2023).  It also shows leading 0s for months/days (01/01/2024 instead of 1/1/2024).  Neither are major, and I'm sure we can change/tweak the default for some of these cases.  I also need to think if it's better or worse than before :).

Before
After

Month
Days of the week now show better abbreviations (Mon/Tue vs M/T).  Thank you :)

Before
After

One thing I would love to do after this (and design token is merged) and allow you to change the locale/settings() in the docs and have everything update.  Similar to how you can change the theme via the AppBar.  I'm debating on whether this should be a modal/dialog/drawer or separate page, and whether it should be an extension of the current theme selector or separate.  Anyways, I'd rather we merge both of these PRs before we do that work since they would both be impacted.

Once this is ready, I would like to publish as @next to update LayerChart (like the design token PR).  I'll probably need to stack/merge both onto a next branch, since pushing to main will currently publish to the main docs as well.  I'm hoping to get the design PR to a near-mergable state by the weekend, although I return back to work tomorrow and have evening kid activities (basketball games, etc) so my availability will be spotty.
I can't say this enough, this is looking great, and a huge improvement!  Will need to kick it around a little to wrap my head around it fully, but really looking forward to it.

@jycouet I'll give it a final review this evening (I'm booked up this afternoon with meetings and need to get some head down work done).
We'll also need to merge this into the next branch instead of main.  I actually already created it a few days ago (but didn't end up using it (yet) for the design token PR, but I'll restack on top of it once you merge to it).  It's a few commits behind at the moment if you wouldn't care to pull/sync it up.

@jycouet I'll give it a final review this evening (I'm booked up this afternoon with meetings and need to get some head down work done).
We'll also need to merge this into the next branch instead of main. I actually already created it a few days ago (but didn't end up using it (yet) for the design token PR, but I'll restack on top of it once you merge to it). It's a few commits behind at the moment if you wouldn't care to pull/sync it up.

I let you have a look at git fun :p

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #167

PR #137   👈

This stack of pull requests is managed by Graphite.


invalid encoding: PLAIN_DICTIONARY

The Issue
When trying to read a test parquet file fetched from an s3 bucket, I get an invalid encoding: PLAIN_DICTIONARY error. This is after getting an invalid parquet version error multiple times due to corrupt files. So, I would think this is a sign that the file is being recognized as a parquet file and just not being read correctly. Is there anything I am not doing correctly?
The Code
(async () => {
  try {
    let reader = await parquet.ParquetReader.openFile('./fetched3.parquet');

    let cursor = reader.getCursor();

    let record = null;
    while (record = await cursor.next()) {
      console.log(record);
    }
  }
  catch(err) {
    console.error(err)
  }
})();

I just realized that PLAIN and PLAIN_DICTIONARY are two different forms of encoding.
Are there any plans to support PLAIN_DICTIONARY encoding in the future?

I would be interested in this too

I'm also getting this error, trying to read a parquet file created by AWS Wrangler (aka AWS SDK Pandas), no solution yet

any updates on this

For your information the lib does not support RLE_DICTIONARY as well. The workaround was to reencode the file to PLAIN

Also it does not support float8 data types

Hello everyone - I hope your last 4 years have been pleasant!
I find myself once again doing some work with Parquet file in Node.
The following package supports PLAIN_DICTIONARY 🎉
https://github.com/hyparam/hyparquet
Closing this issue!


Intentionally break stylish-haskell

Some time ago, it looked like the lib changes were not being picked up. Let's see if that's still the case, or if it was a fluke.

The original issue was that I wasn't aware non-changed files would be ignored by restyler. Everything is fine.


Add eviction thresholds parameters

This closes #42105
Deploy preview: https://deploy-preview-42702--kubernetes-io-main-staging.netlify.app/docs/tasks/administer-cluster/kubelet-config-file/#create-the-config-file

/cc @sftim @vaibhav2107

Hi @sftim, this CI failure looks interesting. Should we increase the maximum allowed runtime for deploy preview?
A similar error in: https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/64e8b65bfc1e730008026aad

/joke

/lgtm

@Affan-7 Please squash your PR into a single commit and git push -f again to trigger the gate.

@Affan-7 Please squash your PR into a single commit and git push -f again to trigger the gate.

Done!

/approve


sap.m.TableSelectDialog: multi-select crashes in Edge browser

OpenUI5 version: latest
Browser/version (+device/version): Edge (latest
Any other tested browsers/devices(OK/FAIL): Chrome, Firefox OK
URL (minimal example if possible): https://openui5.hana.ondemand.com/#/sample/sap.m.sample.TableSelectDialog/preview
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

Open up Table Select Dialog (Multi) sample using Edge browser
Select an item in the list
Shift + select another item in the list further down
Repeat steps 2 and 3 (pressing cancel in between and bringing up dialog again) until the entire app resets.

What is the expected result? Expected no app crash/reset
What happens instead? It may take 5 times or more, but eventually the entire app will hang for a few seconds and then restart.
Any other information? (attach screenshot if possible) Even though Shift + select intentionally doesn't select all rows in between, it's an expectation of users and they may try it, and it shouldn't crash the application.

Hello @cmastrandrea ,
Thanks for your ticket!
Unfortunately however, we weren't able to reproduce this issue (even after many attempts). Take a look at the recording below:
https://ufile.io/hhywk
Can you confirm you are still facing this issue? If so, can you attach a video of the issue - maybe that will help us to reproduce it? Can you also spot any errors/warnings on the console?
Best regards,
Georgi

I am no longer able to reproduce this either, so I'd recommend this be closed. Thanks for looking into it.


Cannot mine contract deployment transaction

Hi Iuri, need your urgent help.
I have set up a private network with 2 nodes and node # 2 is the miner. I deploy a contract through embark to the node 1. It sends a transaction and i see it on the console. The miner (node #2) never mines this transaction while the network is perfectly in sync. However, if the miner is started on node #1, the contract deploys and returns the address.
While this behaviour is only while deploying contracts. If i send any other transaction on the deployed contract, everything is mined perfectly by the miner node (node #2).
Why is this behaviour? Am i missing some configuration?
Thank you

Output from node 2 the miner and it is always this output
I0916 16:09:45.810529 miner/miner.go:119] Starting mining operation (CPU=4 TOT=5)
I0916 16:09:45.810529 miner/worker.go:573] commit new work on block 924 with 0 txs & 0 uncles. Took 0
I0916 16:09:45.810529 eth/backend.go:461] checking DAG (ethash dir: C:\Users\avpatil\AppData\Ethash)
I0916 16:09:45.810529 ethash.go:259] Generating DAG for epoch 0 (size<PHONE_NUMBER>)<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000)
I0916 16:09:47.337681 ethash.go:276] Done generating DAG for epoch 0, it took 1.5271527s
I0916 16:10:00.798027 miner/worker.go:339] ??  Mined block (#924 / d137734a). Wait 5 blocks for confirmation
I0916 16:10:00.800028 miner/worker.go:573] commit new work on block 925 with 0 txs & 0 uncles. Took 0
I0916 16:10:00.855033 miner/worker.go:573] commit new work on block 925 with 0 txs & 0 uncles. Took 1.0001ms
I0916 16:10:00.859033 miner/worker.go:339] ??  Mined stale block (#924 / b628aaa7).
I0916 16:10:00.860034 miner/worker.go:573] commit new work on block 925 with 0 txs & 0 uncles. Took 1.0001ms
I0916 16:10:16.780625 miner/worker.go:339] ??  Mined block (#925 / d38870ad). Wait 5 blocks for confirmation
I0916 16:10:16.784626 miner/worker.go:573] commit new work on block 926 with 0 txs & 0 uncles. Took 0
I0916 16:10:16.901638 miner/worker.go:573] commit new work on block 926 with 0 txs & 0 uncles. Took 0
I0916 16:10:26.669614 miner/worker.go:339] ??  Mined block (#926 / ebe8b0a1). Wait 5 blocks for confirmation
I0916 16:10:26.727620 miner/worker.go:573] commit new work on block 927 with 0 txs & 0 uncles. Took 0
I0916 16:10:26.752623 miner/worker.go:573] commit new work on block 927 with 0 txs & 0 uncles. Took 0

check if they are the same configuration, you might need to specify in the config the same networkid for e.g

Configurations are correct. The moment i add the node to the network, they sync up. The other transactions on the contract are mined and all nodes sync up. The issue is only with contract deployment, where the transaction can be mined only on the node that has the account that deploys the contract.

@talktoavi could you try this in embark 2?


Elastic beanstalk logging issue

Expected behaviour
When deployed to elastic beanstalk the Django log file should be present on both instances
Actual behaviour
When deploying to elastic beanstalk one of the two instances is unable to write the Django log file due to a permission denied error and this causes the instance to become unusable.
Steps to reproduce the behaviour
Deploy the application to Elastic beanstalk
Technical information
Browser
Chrome
Operating System
Windows
Screenshot

https://forums.aws.amazon.com/message.jspa?messageID=395925


Engine prebuilt of dart segfaults on dart test --disable-dart-dev

As of https://github.com/flutter/engine/pull/54811, I am moving dart tooling tests written with a homegrown test runner to use dart test (and package:test). As part of that move, instead of enumerating test/*_test.dart files manually, and invoking them with dart {%s}, we're invoking dart test (with the current working directory temporarily changed to the package path).
Concretely:
dart_tests = glob.glob('%s/test/*_test.dart' % package_path)
if not dart_tests:
  raise Exception('No tests found for Dart package at %s' % package_path)
for dart_test_file in dart_tests:
  opts = ['--disable-dart-dev', dart_test_file] + extra_opts
  yield EngineExecutableTask(
      build_dir, os.path.join('dart-sdk', 'bin', 'dart'), None, flags=opts, cwd=package_path
  )

Becomes:
opts = ['test', '--disable-dart-dev']
yield EngineExecutableTask(
    build_dir, os.path.join('dart-sdk', 'bin', 'dart'), None, flags=opts, cwd=package_path
)

However, this command causes a segfault on both MacOS and Linux platforms.
To reproduce this easily, check out (and build) the latest version of the engine, and do the following:
# Assuming host_debug_unopt_arm64 is built, but substitute another pre-built if needed.
cd tools/header_guard_check
../../../out/host_debug_unopt_arm64/dart-sdk/bin/dart test --disable-dart-dev

===== CRASH =====
si_signo=Segmentation fault: 11(11), si_code=SEGV_ACCERR(2), si_addr=0x0
version=3.6.0-180.0.dev (dev) (Mon Aug 26 05:02:58 2024 -0700) on "macos_arm64"
pid=8421, thread=259, isolate_group=(nil)(0x0), isolate=(nil)(0x0)
os=macos, arch=arm64, comp=no, sim=no
isolate_instructions=0, vm_instructions=1029d9360
fp=16d456d10, sp=16d456cf0, pc=19c683904
  pc 0x000000019c683904 fp 0x000000016d456d10 _platform_strlen+0x4
  pc 0x0000000102e669ac fp 0x000000016d456d40 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x4be9ac
  pc 0x00000001029d627c fp 0x000000016d456de0 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x2e27c
  pc 0x00000001029d6100 fp 0x000000016d456e40 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x2e100
  pc 0x00000001029d74cc fp 0x000000016d456f20 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x2f4cc
  pc 0x00000001029d70f4 fp 0x000000016d456fd0 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x2f0f4
  pc 0x00000001029d7f08 fp 0x000000016d457140 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x2ff08
  pc 0x00000001029d7008 fp 0x000000016d457160 /Users/matanl/Developer/engine/src/out/host_debug_unopt_arm64/dart-sdk/bin/dart+0x2f008
  pc 0x000000019c2cb154 fp 0x000000016d457390 start+0x9ac
-- End of DumpStackTrace
zsh: abort      ../../../out/host_debug_unopt_arm64/dart-sdk/bin/dart test --disable-dart-dev

The SDK-shipped Dart SDK also crashes:
cd tools/header_guard_check
../../prebuilts/macos-arm64/dart-sdk/bin/dart test --disable-dart-dev

I believe we use --disable-dart-dev as its not something that adds value to CI runs, and in the past has caused minor forms of instability and/or log spam, but I can't be certain. For now I can workaround this by not using --disable-dart-dev, but I figured I should file this for posterity.

Closing in favor of https://github.com/dart-lang/sdk/issues/56592.


IE11 support

❓Question
Is Formik supported by IE11? I open my app on IE11 and form's onChange event handler don't fire at all. Anyone knows how to make it work?
Thanks!

I had a similar issue with the form not submitting when pressing enter and adding a promise polyfill fixed it for me. Maybe it will also help you? I used the promise polyfill from core-js.

Are you using react-app-polyfill

In my case it was a different issue, but yes, I had to use polyfill. I am using Nextjs to Promise polyfill is already there

In my case it was a different issue, but yes, I had to use polyfill. I am using Nextjs to Promise polyfill is already there

How did you manage to fix it? Having the same issue atm

@SchauweM It usually is caused by missing polyfills when formik is not working in IE11. As discussed here.


fix(restore): send start request if related vmi is not found

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:
When volume resources is ready for a restoring VM, we try to send a start request. However, if runStrategy is RerunOnFailure and related VMI is not existent, we do nothing.
https://github.com/harvester/harvester/blob/19bc22db86ec0c9d796ec1d9116c3ddce908082a/pkg/controller/master/backup/restore.go#L914-L938
Solution:
We should send a start request if VMI is not found.
Related Issue:
https://github.com/harvester/harvester/issues/6895
Test plan:

Create a new cluster with this PR.
Create a VM with RerunOnFailure.
Create a backup target.
Create a backup.
SSH into the VM and use command to shutdown it. (Don't click stop button on the UI, because this behavior change the runStrategy.)
Make sure the stopped VM runStrategy is RerunOnFailure.
Use the backup to restore replace the VM.
Check the VM can be restarted.

Hi @FrankYang0529
https://github.com/harvester/harvester/blob/625f14e0c4b568272763f9fd74b87577edef7809/pkg/controller/master/backup/restore.go#L551-L555
We should already set runStrategy as Halted, why this PR is still required? Thanks

We should already set runStrategy as Halted, why this PR is still required?

This PR is to avoid edge case when the cluster is upgraded from v1.3.2 with off VM. Please take a look for reproduce steps in original issue: https://github.com/harvester/harvester/issues/6895

We should already set runStrategy as Halted, why this PR is still required?

This PR is to avoid edge case when the cluster is upgraded from v1.3.2 with off VM. Please take a look for reproduce steps in original issue: #6895

IIUC, the Harvester controller should always set restoring VM's set runStrategy as Halted, then the VM will be started by https://github.com/harvester/harvester/blob/625f14e0c4b568272763f9fd74b87577edef7809/pkg/controller/master/backup/restore.go#L947-L948

We should already set runStrategy as Halted, why this PR is still required?

This PR is to avoid edge case when the cluster is upgraded from v1.3.2 with off VM. Please take a look for reproduce steps in original issue: #6895

IIUC, the Harvester controller should always set restoring VM's runStrategy as Halted, then the VM will be started by
https://github.com/harvester/harvester/blob/625f14e0c4b568272763f9fd74b87577edef7809/pkg/controller/master/backup/restore.go#L947-L948

Hi @WebberHuang1118, I noticed that the run strategy of VM from v1.3.2 is Halted at first. After VM restore replace, it will change to RerunOnFailure, because startVM sends a start request. However, its status is still stopped, so I think we still need this PR to send another start request to make VM be running.


Issue 77 - confirm delete collection

add: dialog box to confirm deletion of cookbook or menu

This works for cookbooks,
It doesn't work for menus though
Before

After Delete

After Refresh

Cookbooks working
Before

After Delete

After Refresh


Cannot install new version of vela with kubevela.net

When attempting to install KubeVela version 1.9.11 on a Kubernetes cluster running using the vela CLI tool, the installation process fails due to an issue with retrieving and loading the Helm chart. The specific error encountered indicates a problem with the Helm chart file's gzip header.
To Reproduce
Pull kubevela:
curl -fsSl https://kubevela.net/script/install.sh | bash'
Run the following command to install KubeVela:
sh
vela install --version 1.9.11
KubeVela Version
v1.9.11
Cluster information
1.24.0
Additional context
Installing KubeVela Core ...
Error: loadding the helm chart of kubeVela control plane failure, error retrieving Helm Chart at https://charts.kubevela.net/core/vela-core-1.9.11.tgz: gzip: invalid header

Can you help this? @barnettZQG

Kubevela.io is up now. Try again and see if it works

Working for me

Recovered.


Graph CLI creating webserver on each command run

Hi all,
I believe this is due to the sync-rpc dependency attempting to load a local webserver at require time, although I'll admit I've not done the full stack crawl to see where it comes in. As a result I get the following network security request from MacOS for each command run, even the simpler ones such as codegen

I can imagine legitimate uses for this library but generally feel quite antsy/nervous about any command that attempts to run a local webserver without declaring it, typically because of unexpected security concerns (is it accessible from a browser JS runtime to escape the sandbox, is it attached to localhost or <IP_ADDRESS> and available over my local network etc).
I also recieved the following error which pointed me to the source:
$ graph codegen
events.js:377
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::60748
    at Server.setupListenHandle [as _listen2] (net.js:1331:16)
    at listenInCluster (net.js:1379:12)
    at Server.listen (net.js:1465:7)
    at Object.<anonymous> (<redacted>:68:8)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1358:8)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  code: 'EADDRINUSE',
  errno: -48,
  syscall: 'listen',
  address: '::',
  port: 60748
}
<redacted>/node_modules/gluegun/build/index.js:13
    throw up;
    ^

Error: Timed out waiting for sync-rpc server to start (it should respond with "pong" when sent "ping"):

events.js:377
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED <IP_ADDRESS>:60748
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 60748
}

    at waitForAlive (<redacted>/node_modules/sync-rpc/lib/index.js:85:11)
    at start (<redacted>/node_modules/sync-rpc/lib/index.js:41:3)
    at sendMessage (<redacted>/node_modules/sync-rpc/lib/index.js:133:17)
    at createClient (<redacted>/node_modules/sync-rpc/lib/index.js:173:27)
    at Object.<anonymous> (<redacted>/node_modules/sync-request/lib/index.js:16:14)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Module.require (internal/modules/cjs/loader.js:974:19)

thanks @jackturnbull ! @evaporei do you know where this originates within graph-cli?

I think it comes form this PR https://github.com/graphprotocol/graph-cli/pull/816 and that sync-request and sync-rcp are also responsible for this Issue https://github.com/graphprotocol/graph-cli/issues/849

@saihaj do you know if this still happens

@saihaj do you know if this still happens?

yeah I think this is one of the dependency we use. Should probably work on way to refactor it out.


Program Indicator List view: Setting reporting period start and end months

Background context
See #227: Pull program start and end dates from GAIT and use them to set reporting start and end months.
UI changes to Program Indicator List view
In order to afford the interactions required in this story, we need to update the "program container" that users click to reveal and hide the program's list of indicators.
Here is how it looks today:

Here is the updated UI:

Acceptance criteria
The program container still has two rows, but I've moved some items between rows, made some adjustments to the layout, and added a new "Reporting period" link.
Top row

There are two columns. The left column is much wider than the right column, in order to give long program names more room.
Left column includes the program name that is permitted to wrap instead of being truncated as it is today.
Right column includes only the New Indicator button, which I've renamed "Add indicator". (Label change is based on Fruit Basket feedback.)
The top row no longer includes a "Grid/Print report" button.

Bottom row

The bottom row now has two columns.
In the left column, instead of a button, the "# Indicators" open/close interaction is now more like a tree behavior, with a right-facing arrow next to the number of indicators when the container is closed, and a downward-facing arrow when it is open. Like so:

(Incidentally, we will use this same type of interaction for opening and closing disaggregations in the Collected Data record.)
In the right column are two links separated by a pipe sign.
3.1. The left link says "Indicator plan" and links to what we were formerly calling "Grid/Print Report." (We had feedback that the current phrasing is not intuitive to users.)
3.2. "Reporting period" opens up our new reporting period modal, described below.

Reporting period modal
Clicking the "Reporting period" link launches a configuration modal that communicates reporting period options and permits the adjustment of program reporting start and end dates.

Here is the descriptive text under the "Reporting period" page title: The program reporting period is used in the setup of periodic targets and in Indicator Performance Tracking Tables (IPTT). TolaActivity initially sets the reporting period to include the program’s official start and end dates, as recorded in the Grant and Award Information Tracker (GAIT) system. The reporting period may be adjusted to align with the program’s indicator plan.
Here is the descriptive text under the start and end dates: While a program may begin and end any day of the month, reporting periods must begin on the first day of the month and end on the last day of the month. Please note that the reporting start month can only be adjusted before targets are set up and a program begins submitting performance results. The reporting end month can still be extended.
GAIT program dates are auto-populated directly from GAIT and may not be modified.
The reporting start date can only be modified before any targets are set up.
4.1. When the reporting start date can no longer be modified, that form field is disabled, while the end date is still editable, like so:

The reporting end date can only be moved earlier BEFORE any targets are set up. (That's because once targets are set up, moving the end month earlier will "cut off" existing target periods.)
5.1. If the user tries to move the reporting end date earlier after targets are set up, the end date field is outlined in red with an error message below: The end month can be moved later but not earlier.
The reporting end date may be moved later at any time. This has repercussions for the Program indicators list page and target setup views that will be addressed in one or two separate tickets.
Upon clicking "Save changes", our standard green confirmation bar appears with the message, "Success. Reporting period changes were saved."

Additional error conditions

User cannot enter a reporting end date that occurs prior to the start month. (Can we handle this similarly to how we handle it in the filter panel? That is, you only see the months available for the currently selected program year?)
Either or both program dates are missing in GAIT.
2.1. In the GAIT program dates section, replace the date or dates with the word "Unavailable" in our standard red error color -- #DD0000
2.2. Start month and End month fields are empty and disabled.

Note: We may need to remove the sentence "The reporting end month can still be extended." and update the prior sentence to read "start and end months". It depends on what happens with tickets #263  and #264.

@sanjuroj I no longer seem to be able to access the reporting start and end date pickers. I remember seeing it a little while ago. But now when I click into the box, the date picker does not appear -- regardless of whether there is already a date in there or it is empty.
I also notice some auto-select type behavior. If I merely tap into a field and then tap or tab out, it auto-populates the fields with what appears to be a random date, but what I'm guessing is a date from a different program. I get the same auto-populated date regardless of program. Similarly, if I don't do anything except click "RESET" in a program, it auto-populates both date field with what I assume are dates from some other program.
While you're in there, please make the calendar icon active if that's easy to do. (Please don't spend more than 5 or 10 minutes on it though -- it's low priority.)

The reporting start and end date fields should not auto-select the current month. It should behave similarly to the date picker in the Indicator Targets tab, in that I can back out of interacting with the date picker and not have it auto-populate if I do the following:
Click Esc key
Click Tab key
Click the mouse anywhere outside the date picker field.

We don't need the "Today" button. (Due to the auto-select being turned on, I can't see the date picker anymore in the Targets tab to check if the Today button is included in that instance, but I don't recall it being there.

Still having issues with the Reset button.

Everything except the Reset-related issues is validated.


Inconsistency of documentation with actual code in DeepGCNLayer

🐛 Bug
DeepGCNLayer documentation states that is does
GraphConv→Normalization→Activation→Res/Dense/Plain→Dropout
if block='res'/'dense'/'plain' . However, the tailing dropout is never applied in the forward method and is thus somewhat misleading. Sorry for if I misunderstood or missed anything.

Good spot! Fixed in master.

You are welcome :)


✨[Feature] Add a log module for logging info (console + DB)

Is your feature request related to a problem? Please describe.
Currently we log output to the console using console.log() directly. For this common functionality the same code in written repeatedly. We should have a log module that we'll can use for a centralized logging tool. This'll help with -

[x] Checking if it is production or development and logging according to it
[x] Log stuff to the DB when necessary
[x] Formatting the logged message according to different priority
[x] Easier debugging and modularity

Describe the solution you would like
Create a log module.
Additional context
I've used log as the module name here but it isn't set and stone. We could call this module a different name.

There is likely already a mature logging package somewhere on NPM

There is likely already a mature logging package somewhere on NPM

@snowteamer I haven't looked for any NPM package tbh. Can you suggest any?

Unfortunately I am not familiar with any :(


Pylint shows a lot of warnings (and only warnings)

When I run Pylint on my project, everything is shown as a warning, while some problems are obviously errors (e.g. missing parameter) and others are unimportant formatting issues (e.g. trailing spaces). Now important problems disappear in the noise.
According to pylint's man page there are 5 different classes of errors:

(C) convention, for programming standard violation
(R) refactor, for bad code smell
(W) warning, for python specific problems
(E) error, for probable bugs in the code
(F) fatal, if an error occurred which prevented pylint from doing further processing.

It would be nice if you could see the difference between the different classes of problems found by Pylint. Even better if you could also filter on it.

Unfortunately, we are constrained by the design of VS Error List window here (and specifically, the columns and the preset categories that it has). Note that the Pylint  error category is in fact reported as part of the error text, in square brackets, e.g.: "function docstring [C:missing-docstring]". C is the category, and the identifier after it is the one that you would use to suppress that particular warning with #pylint: disable, or in your pylintrc.

Actually you can configure the way pylint provides the output.
See http://docs.pylint.org/output.html for more information.
This means that you can provide the error category as output. The visual studio format would therefore be:
{path}({line}): {category} {msg_id}: {obj} {msg}
Note: This will not handle all categories (generally visual studio supports error and warning so fatal, refactor and convention would appear as regular messages). There is also some example in https://github.com/mike-ward/VSColorOutput of coloring build output which may be of use simply by color coding.


chore(main): release haproxy 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-04-20)
Features

haproxy: add a collection that installs haproxy (#4) (bbeb1cb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mateusz-uminski/ansible-collections/releases/tag/haproxy-v0.1.0 :sunflower:


jmavsim: update submodule

enable baro noise
add lat/lon to ground truth

Reviewed, seems to be correct.

CI mixer failure unrelated


Make executor report facts to the scheduler

On get fact, the executor reportsthe facts to the server, we want to move this to the scheduler, such that the scheduler write it to the DB.
this is similar to #8189 and make have a synergy with #8183

Hey team! Please add your planning poker estimate with Zenhub @arnaudsjs @hlloreda @Hugo-Inmanta @jptrindade


Doesn't work with "multiple files" import

Describe the bug
This code causes the "handle-import" babel plugin to break:
import(
  /* webpackInclude: /\.docs\.js$/, webpackChunkName: "whatever-[request]" */
  `__cwd/${path}`,
)

To Reproduce

Include the snippet above in a code.
Receive Module build failed: TypeError: Cannot read property '0' of undefined error from node_modules\next\dist\server\build\babel\plugins\handle-import.js:35:30

Expected behavior
I'd expect Next.js to be able to handle this kind of import usage, as it's supported by webpack. The old way to do the same, namely require.context, is not breaking like this (though it's breaking in other ways, as I'll bescribe in "additional context").
System information

OS: Windows 10
Version of Next.js: 6.0.3

Additional context
Related issue: https://github.com/zeit/next.js/issues/2690
This problem is directly caused by the "handle-import" plugin expecting the first argument to be a string literal (which has the value property). Since in my case it's a template literal, it doesn't have a value, only expressions and quasis.

For a while now I've been trying to create a wrapper around Next.js that's able to work with dynamically imported files (a tool for documentation which includes all *.docs.js files in the project).
First of all, I can't use pages/ - I want documentation files to be close to the scripts they document. I want the original structure of the source to be reflected by the structure of documentation, so replicating the directory structure in two places (original and pages) seems like an unmaintainable idea.
That's how I arrived at a solution that uses import-all.macro. The problem with that is, it's powered by babel. So when, as a user, I'm adding a new documentation file, I'll need to stop the tool, purge the cache (since all imports are inlined in a file), and restart the tool. I'm losing the file-listening capabilities of webpack-dev-server, and I need to go around the limitations of babel caching.
That's how I arrived at a solution that uses require.context. It almost works! I can't get the SSR story correctly though - while the server renders the appropriate script, the chunk doesn't seem to be ready when dynamic is rendering the component. Actually, the chunk doesn't seem to be generated at all! That's why I switched to import, to try and see if I could get the chunk-creating machine going at least with the other way of importing. As it is now, I've spent several days on this, I'm spinning in place, and I'm determined to fix the problem.

I managed to make everything work. I'm very excited, because for so many days I was hoping that "the next solution will finally work" and there was always something lacking. But to get to the final solution, I had to change Next.js in a few ways - I'd like to get those changes into the package, as I think they'll benefit not only me, but also Next.js in the long run.
TL;DR:

Fixing the condition in handle-import to ignore template literals is very important (the current behavior of just crashing with an unhelpful error message is very undesirable)
Fixing getAvailableChunks to remove only the last hyphen and what follows it is also very important (it's because of how Webpack constructs chunk names - I can't do much here)
Upgrading to Webpack 4 would help a tiny bit

Below is a comprehensive description of whats and whys.
The handle-import plugin
As far as I know, the only way to set chunk names for "context" imports is to use this construct:
import(
	/* "webpackChunkName": "chunks/[request]" */
	`__cwd/${path}.docs.js`,
)

__cwd is resolved to process.cwd(), which is not the same directory where Next.js is running from
This is quite inconvenient because of three things:

It's impossible to get a map of all paths from this, as I described here: https://github.com/webpack/webpack/issues/7283
Because of that I have to retrieve the map of paths using require.context('__cwd', true, /\.docs\.js/, 'weak');, which forces me to use a hack (I'll describe it below)
Webpack docs describe syntax that's only available in v. 4, so I wasted some time on discovering that webpackChunkName has to be put in quotes in v. 3 (otherwise this just breaks and the error message is not helpful)

What I'd benefit here from (a bit) is to have Webpack upgraded to v. 4, but that's a small issue.
As an extra thing, I have to actually use something like this:
const marker = '|';
import(
	/* "webpackChunkName": "chunks/[request]" */
	`__cwd/${marker}${path}${marker}.docs.js`,
)

Here I'm using the fact that Webpack doesn't know what marker is at the build time, so it just looks up the same paths as before. Afterwards though, I can easily get the actual path by getting the one between the markers (the ${path} argument comes from require.context, which returns full paths, so the result might look something like this: ././path/to/file.docs.js.docs.js, and after marking it's ./|./path/to/file.docs.js|.docs.js).
Ok, but at this point everything's still failing, because of the bug in server/build/babel/plugins/handle-import.js. What I did to fix the situation was to change the first condition inside CallExpression visitor to:
if (path.node.callee.type === TYPE_IMPORT && path.node.arguments[0].type !== 'TemplateLiteral') {
  ...
}

This just makes the plugin ignore template literals. I'd like it very much to see this change added to Next.js soon - if Next.js is not doing anything meaningful with import(`foo${bar}`), then it could at least not explode.
The getAvailableChunks utility function
So at this point I've added a few things here and there to be able to import files dynamicly like a civilised human. I got to know a bit about Webpack internals, and I've added an extension that not only allows me to get the chunk name for any file in import(`foo${bar}`), but also sets the proper value of module.__webpackChunkName so that Next.js knows such and such chunk was used when rendering a page. I don't really need this to be added to Next.js, but I'm leaving this here; maybe it will be useful someday when context imports come to Next.js:

The big hack that solves all my chunk-mapping-related problems
const marker = JSON.stringify('|');
const getExtraLazy = chunkNameMap => `
var chunkNameMap = ${JSON.stringify(chunkNameMap, null, '\t')};

function webpackContextResolveChunk(req) {
  if (!map.hasOwnProperty(req)) {
    throw new Error("Cannot find module '" + req + "'.");
  }
  return chunkNameMap[map[req][1]];
};

function extraWebpackAsyncContext(req) {
  if (req.indexOf(${marker}) === -1) {
    throw new Error("Cannot handle unmarked module request '" + req + "'.");
  }

  var unmarkedReq = req.slice(req.indexOf(${marker}) + 1, req.lastIndexOf(${marker}));

  return webpackAsyncContext(unmarkedReq).then(function(module) {
    var chunkId = webpackContextResolveChunk(unmarkedReq);
    module.__webpackChunkName = chunkId;
    return module;
  })
};

module.exports = extraWebpackAsyncContext;
`;

function getChunkNameMap(module) {
  return fromPairs(flatten(
    module.blocks
      .filter(block => block.dependencies[0].module)
      .map(block => (block.chunks || []).map(chunk => [chunk.id, chunk.name.slice('chunks/'.length)])),
  ));
}

class ExtraLazyTemplatePlugin {
  apply(moduleTemplate) {
    moduleTemplate.plugin('module', (source, module) => {
      if (module.async !== 'lazy') {
        return source;
      }
      const chunkNameMap = getChunkNameMap(module);
      return new ConcatSource(source, getExtraLazy(chunkNameMap));
    });
  }
}

class ExtraLazyPlugin {
  apply(compiler) {
    compiler.plugin('compilation', compilation => {
      compilation.moduleTemplate.apply(new ExtraLazyTemplatePlugin());
    });
  }
}

I'm almost completely set, but I still see a flash of "Loading..." after opening the page (proper markup is sent because of SSR, then "Loading..." appears, then the page is rendered again). And the reason for that is that my chunks are still being ignored by Next.js. I tracked it down to the following line in getAvailableChunks:
const chunkName = filename.replace(/-.*/, '')

If I understand correctly, the goal of this line is to strip the hash preceeded by a hyphen. Unfortunately with my chunks named chunks/[request], I get a lot of hyphens in the name - Webpack changes all slashes to hyphens. But because we're interested only in the last hyphen and what comes after it, my suggested change is this:
const chunkName = filename.replace(/-[^-]*$/, '');

It correctly strips the file name of the last hyphen and the remaining part.

Sorry if the write up is too long. It was a long ride for me after all, and I needed to get this off my chest. My biggest hope right now is that maintainers will agree with two small fixes I suggested. I'm here to help and I'd gladly prepare the needed PRs.

@timneutkens I hope I'm not overstepping my bounds if I ask you to give me any feedback on this? Right now I could prepare PRs for changes that I suggested - I just want to make sure that the problems I highlighted are something that you'd also like to see fixed.

@fatfisz let me read up on this soon it's quite a lot of research 😄, I've been thinking about making some changes to next/dynamic anyway 👍

Hi, could I just create said PRs? They'll be very small and easy to merge - I promise 🙂
I'd like to move forward with my project and while I can patch webpack to do what I need, Next.js is much harder to adjust (I'd need to release my own version, monkey patching is impossible).

Sure go ahead with creating a PR, I can review them and we have extensive tests for the feature anyway, so if you break something you'll know 😄

Just a heads up that both branches seem to be passing. I just updated them with the latest canary.

Looks like some of the changes that @fatfisz suggested have been merged. But dynamic imports (using dynamic paths) still don't work with NextJS v6.1.1

Will be fixed with #4639

This sounds awesome - so you'll be dropping handle-import and using react-loadable instead?

@fatfisz yep that's what I'm working on, works great so far 👍


Fix packUnit not displayed on product detail

1. Why is this change necessary?
The packUnit is not displayed on the product detail page. The variable is access by product.packUnit but this does not work, as it's in the translation table.
2. What does this change do, exactly?
product.packUnit -> product.translated.packUnit
3. Describe each step to reproduce the issue or behaviour.
Enter a package unit in the administration for a product. It's not display on the product's page.
4. Please link to the relevant issues (if any).

5. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[ ] 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.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

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-10042
Please use this issue to track the state of your pull request.

Hey @simkli,
thank you very much for your pull request! 💙
We've just merged your changes! :-)


[BUG] - New Year needs Update - No Popups

Like always mercury trade needs a new year update. No popups for incoming trades.

wonder what makes this break in the code

wonder what makes this break in the code

wonder what makes this break in the code

afaik some certificate needs to be renewed

wonder what makes this break in the code

afaik some certificate needs to be renewed

wonder what makes this break in the code

afaik some certificate needs to be renewed

In case it doesnt get fixed, i just tried Poe Trades Companion, works just like mercury, its really good

wonder what makes this break in the code

afaik some certificate needs to be renewed

In case it doesnt get fixed, i just tried Poe Trades Companion, works just like mercury, its really good

Poe Trades Companion is AutoHotKey, isnt it?
if its realy a certificate, what takes so long to refresh it? ^^
so i guess the app is not supported anymore?! that would be realy sad...

It's not a problem with any certificate since this app does not have any certificate at all. The problem is that I can't replicate that error when I try so it's hard to fix it

When you press test message button do the popups show or not?

Test shows up.
It was the same issue like 1. Jan 2019 in the original version.
https://github.com/Exslims/MercuryTrade/issues/335
If you change your system Date back to 2021 it is working for incoming messages.

i can use all "tests" and they popup/work...

and same here 1. jan 2020
https://github.com/Exslims/MercuryTrade/issues/404

its very interesting how such a "new year bug" can still happen ^^
is the year a static number or what happend?
whats the background of this error? im realy curious...
im using poe-overlay-community-fork and it still works without a new-year-update.

I'm just looking at code, and yes, there is some static value for year checked for messages, I will fix it in a sec and try to deploy today

sounds awesome. thank u in advance..

I'm just looking at code, and yes, there is some static value for year checked for messages, I will fix it in a sec and try to deploy today

Sounds very good. The exact new year date got me to the assumption that it could be a certificate. so i think the issue is who it reads the date of the client.txt?
Thanks for your work.

closed with release 1.1.8

Is this now fixxed for other years to come?

It's fixed up to 2099 so I think we are all covered :D


New version: MilosParipovic.OneCommander Version 3.65.2

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @dkr91,

This PR's version number <IP_ADDRESS> has 4 parameters (sets of numbers between dots - major, minor, etc), which is greater than the current manifest's version 3.44.1, which has 3 parameters.

Is this intentional?
(Automated response - build 629)

Yes, Milos changed his Versioning.
see [Current Release](https://www.onecommander.com/#:~:text=<IP_ADDRESS> (2024-01-22)


Add support dash border in BorderDesignable

That could be useful, but how handle the inspectable part? Using a a border type  (solid, dash...)?
The code is quite simple (didn't try it, paste from SO):
 let shapeLayer:CAShapeLayer = CAShapeLayer()
    let frameSize = self.frame.size
    let shapeRect = CGRect(x: 0, y: 0, width: frameSize.width, height: frameSize.height)

    shapeLayer.bounds = shapeRect
    shapeLayer.position = CGPoint(x: frameSize.width/2, y: frameSize.height/2)
    shapeLayer.fillColor = UIColor.clear.cgColor
    shapeLayer.strokeColor = color
    shapeLayer.lineWidth = 2
    shapeLayer.lineJoin = kCALineJoinRound
    shapeLayer.lineDashPattern = [6,3]
    shapeLayer.path = UIBezierPath(roundedRect: shapeRect, cornerRadius: 5).cgPath

    self.layer.addSublayer(shapeLayer)

@tbaranes will it be a var borderType: BorderType property. and BorderType is an enum?

Yeah something like that, I'm gonna give it a try, will see if it looks good :)


Canonicalize and ensure uniqueness of indices

Prior to this commit, adding a entryUUID or entryCSN
index conflicted with those being added by default
when the syncprov overlay is enabled.
This avoids that behavior by canonicalizing and uniquing
the indices before adding them into OpenLDAP.

I'm trying to understand this change.

Do you have a test case or example for this? What other indices do you need for entryUUID/entryCSN?
Your new function appears to be something supported by Puppet 4 only. I don't want to drop Puppet 3 support; writing this in terms of a parser function would work on both.

There will also need to be tests written for this.

Hi Matt,
Thanks for responding so quickly - I'm happy to clarify. I've cc'd Jesse
Hathaway, who I'm working with.

The idea is to make the behavior more lenient in the case where someone
specifies indices that are already included when syncprov is set to true.
The example would be a user who sets syncprov => true and also adds indices
for entryUUID and entryCSN up front. These indices are added again in
config.pp, which causes LDAP to reject the duplicate indices and the puppet
apply to fail. It seems more user-friendly to just reformat and unique the
index entries before adding them to LDAP, rather than completely fail in
the case that someone accidentally adds duplicate indices.

Good point - I've rewritten it as a parser function.

We had some trouble getting the tests to run yesterday, but got them
working today. I added several test cases for the new function, and had to
modify a few existing test cases to account for the different format for
the olcDbIndex attributes. I've amended the pull request to include these
changes.
Best,
Tom Christiansen-Salameh
On Wed, Jul 20, 2016 at 4:49 PM, Matt Dainty<EMAIL_ADDRESS>wrote:

I'm trying to understand this change.

Do you have a test case or example for this? What other indices do
you need for entryUUID/entryCSN?
Your new function appears to be something supported by Puppet 4
only. I don't want to drop Puppet 3 support; writing this in terms of a
parser function would work on both.

There will also need to be tests written for this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bodgit/puppet-openldap/pull/28#issuecomment-234094361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIXiUN-V1gUa0UfGWWI_w-qHKsVdkqm7ks5qXpfigaJpZM4JQ3Sm
.

Coverage decreased (-0.1%) to 52.743% when pulling 9a7bddd424dcb0d17fa431c06040f63446c71665 on tcsalameh:unique-indices into 9a14f51f94e28ea7fe49d7838691dfc62d06c7d9 on bodgit:master.

Coverage decreased (-0.1%) to 52.743% when pulling 91f7c71effc445b0307a1ad5bf249c71a524e960 on tcsalameh:unique-indices into 9a14f51f94e28ea7fe49d7838691dfc62d06c7d9 on bodgit:master.

Ok, the change looks good to me. Tests all pass. 👍
Thanks for your contribution!

Thank you! We're using this module as part of an OpenLDAP implementation project, so I may be submitting a couple more pull requests in the next few weeks.

Thank you! We're using this module as part of an OpenLDAP implementation project, so I may be submitting a couple more pull requests in the next few weeks.

No problem. I've pushed v1.1.4 to the forge.


Add deploy service modal

This PR does include the following functionality:

Create Modal
JSON editor
Parsing data back and forth between those two.
The JSON editor is submitting the JSON you supply which means any app definition can be POSTed to the server
The form only does supply the given fields.
Switching to the form will cut the definition to the fields which are provided.
Some validation.
Refactoring of the SchemaForm

Remove the Header from the component and moving it to the modal
Clearing the timeout if component does unmount

This PR does not include:

A final design
A full fledged form
Complete Validation
Dependent fields
Multiple rows
Right error Handling

IMAGES:

This PR has a couple of dependencies:
#208 (not merged yet)
#209 (not merged yet)
#210 (not merged yet)
#211 (not merged yet)

Reviewer: @jfurrow

I've force-pushed some changes to fix rebase issues against current master.

This is starting to look great!

wow, just tried this. this is pretty fucking awesome

one thing that happens: if you're on the json mode and close it and then reopen it, the animation is broken and also you lose the model completely.

after my last round of nits and the closing when in json mode issue, i think this looks good. sorry for the waterfall review

I adressed those nits but I couldn't address the animation issue. Losing the date by canceling the dialog is intentional.

but that's not the custom data. that's the default data that comes from the schema. should it be there like it is for the form mode?

You are right @kennyt, the reset was causing this problem. I fixed the reset so that upon opening the modal the user will see the form pre-filled with the default data.

I took the liberty to force-push after rebasing on master

I don't see the json toggle ... ?

I still see some open comments – can you please address them so we can merge? Thx!

It seems like you force pushed a very old state. I'll fix it with my state.

Oh jeez! That's really weird, I'm absolutely sure I pulled the latest from the branch... ! 😱 Hope it's not too bad!!! Sorry! 😢

No problem I rebased and force pushed now everything should be there 👍

Sorry for crashing the party but I've noticed a few things I'd like to see discussed before hitting Merge! Thanks

Solid work @Poltergeist


resolve warnings about Dockerfile casing

Reviewing #706, I noticed the following on the Files tab (https://github.com/rapidsai/docker/pull/706/files):

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

This resolves those warnings. They don't change anything functionally, but I do slightly agree with the style suggestion, and it'd be nice to remove the visual noise of all those warnings in PR reviews.

/merge


URSACHE: 9002 - Failed to connect to svc90.main.px.t-online.de/:::443

Describe the bug
I setup the app without any problem, and did use it for one day. Today, it tells me
"URSACHE: 9002 - Failed to connect to svc90.main.px.t-online.de/:::443"
Can't screenshot you the stacktrace, because for whatever reason, I am not allowed to make screenshots inside the app.
Expected behaviour
The problem not to popup 😄
Steps to reproduce the issue
Opening the app is enough. Clearing the cache might help, but this will (I think), get rid of my data collected, which is contraproductive.
Technical details
Android 10 (Buildnumber QQ3A.200605.001)
Google Pixel 4 XL
Possible Fix
Never seen the port annotation /:::443
Additional context
Why are screenshots not allowed? There should be either the possibility to make screenshot on Android (on iOS its allowed) or at least have a stacktrace export in case of an error.
From my Java experience, here are some files and lines with the problems (not gonna type every last line):
java.net.ConnectionException: Failed to connect to svc90.main.px.t-online.de/:::443
RealConnection.kt:23
ExchangeFinder.kt:143
ExchangeFinder.kt:1
ConnectInterceptor.kt:16
RealInterceptorChain.kt:14
CacheInterceptor.kt:197
RealInterceptorChain.kt:14
BridgeInterceptor.kt:36
RealInterceptorCHain.kt:14
RetryAndFollowUpInterceptor.kt:31

Thanks for your issue report! Can you kindly give us some more details or tell us if the issue still persists? Especially the first few lines of the details of the error dialog would help a lot in this case!

Just as an aside: Clearing the cache or even all data should not be a problem in my view; the received rolling proximity identifiers, and the daily tracing keys used to calculate the sent rolling proximity identifiers are not stored by the app, but by the API.
Would be good if someone could confirm.
The only disadvantage might be that the app would then incorrectly state that it has only been active for a day, but that's just a minor inconvenience (I had the Latvian app installed for two weeks or so, so in principle the CWA should show "14 of 14 days active" for me, but as the app does not have this information, it only shows "1 of 14 days active").

Hey @MikeJayDee ! For us, it would greatly help our efforts in maintaining our issues if you could open up a separate issue with this exact question in mind. This helps us keep topics separated.

@jakobmoellersap clearing the cache didn't help. Clearing the memory content actually did help. Sorry I tried that before talking an actual photo of the error. If the error reappears, I will take a photo of the stacktrace. For now I can only provide the photo attached. I will keep you posted.

The error suggests an error during the buildup of the TLS Handshake and should be very uncommon as this would indicate an error before the real Handshake even happens (which would be caught by a different Error in the Transport Layer of OkHTTP).
Could you please ensure that you can replicate somehow? Otherwise, the error is extremely hard to reproduce.

I know that feel. Give me a day or two, and I will let you know if I was able to reproduce it.

Hm maybe  there is a bug in the manifest? The app doesn't request any network access permissions.
Way down in the details it says:
.....
java.net.Socket.connect(Socket.java:621) at m0.p0.h.e (Platform.kt:1) at m0.p0.g.i.e(RealConnection.kt:16)
... 23 more
Caused by: android.systemErrnoException: connect faileed: EACCES (Permission denied) at libcore.io.Linux.connect(Native Method)
.....

@trololo9000 Regarding your suggestion:
<uses-permission         android:name="android.permission.INTERNET"         android:required="true" />
Snippet from the Manifest would suggest otherwise.

I can confirm the suggestion, must be another cause. :-/

@jakobmoellersap can not reproduce it. It just appears. But i managed to make a screenshot of the stacktrace. I will not clear my cache, let me know if you need anything else.

You have a connection refused error. Do you tamper with the connection by any chance?

I messed around with my private DNS. t-online was blocked there. Disableing it was the solution. Sorry for the confusing and timeconsumption.

No worries, thanks for updating us about this issue! It will hopefully also help out other community members in the future!


can I install it locally instead of docker?

I know it's not the proper channel to ask but can I install it on the local machine(ubuntu) instead of docker due to some strange requirements. Thanks

Is this for the CLI or service assembly? It is possible to install it locally, but it will require a bit of manual work to prepare the environment. I recommend looking at the Dockerfile to see what is required. You just need to mimic it.

Let me know if you have any additional questions.

@MrSaints can you please point me to the Dockerfile(there are two in the repo) so that I'll start it. Thanks

@arbabnazar https://github.com/arachnys/athenapdf/blob/master/cli/Dockerfile


Null safe package:vm_service has lost support for variable inspection in debugging

See https://github.com/dart-lang/sdk/issues/44800
There may be other breakages too. Still need to find the exact version # this was introduced in.

/cc @dnfield Can we roll back?

/cc @dnfield Can we roll back?

From offline discussion: We're going to roll back for the 1.26 branch.
For master, I'd like to know more about how long a fix forward would take. A roll back of this would require doing a new update packages roll into flutter with the constraint pushed back,and reverting some null safe migrations that depend on the new vm_service. It's doable but somewhat involved.

From offline discussion: We're going to roll back for the 1.26 branch.
For master, I'd like to know more about how long a fix forward would take. A roll back of this would require doing a new update packages roll into flutter with the constraint pushed back,and reverting some null safe migrations that depend on the new vm_service. It's doable but somewhat involved.

It would also require reverting some BUILD file changes in google3

It would also require reverting some BUILD file changes in google3

Update: the revert has rolled into cp1.26, and a fix forward has rolled into master.
Leaving this open with a lower priority to track adding a test covering this functionality.

Update: the revert has rolled into cp1.26, and a fix forward has rolled into master.
Leaving this open with a lower priority to track adding a test covering this functionality.


NIFI-6341: Addressed bug that can result in a deadlock if Thread 1 ad…

…ds a Controller Service to a Process Group (which obtains group's write lock and AbstractComponent's Lock) while at the same time Thread 2 attempts to peform validation on the service (which obtains Controller Service's write lock, then AbstractComponent's Lock)
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...


Update main.js

Good morning sir ,
Okay sir i will see through and rectify my mistake.
Sorry for the inconvenience.
Thank you


Coinbase Bank Integration with API through IOS App?

Hi,
I'm trying to integrate Bank with coinbase through IOS app with getting user bank details like Account number, Bank name, Branch code, etc. Please, anyone, tell me how to integrate bank with coinbase using API or any other method which can help me?
Thanks :)

@StanislavKrishu please help me if you know this?

Hey @abrarEpazz, hope you were able to sort this out.
This might be a good question for Stack Overflow if you are still having troubles.
As we're deprecating the package, we'll be closing out this issue.
Thanks for your interest!

Hey @abrarEpazz, hope you were able to sort this out.
This might be a good question for Stack Overflow if you are still having troubles.
As we're deprecating the package, we'll be closing out this issue.
Thanks for your interest!


Script runs fine in Terminal. But when invoked via service: No module named 'dropbox'

I had initially installed pip3 install dropbox (the module) as your README.md instructed.

In the shell get_dropbox_link.py executes just fine.

In my setup placed in ~/bin/bin/ which is in my PATH.
All the dropbox API key + permissions work fine.
I get URLs for ~/Dropbox/* filepaths just fine.

But when pressing the shortcut, which invokes the service (aka Quick Action built with Automator), in this environment the dropbox python module seems to be no accessible, because I get this error:
 The action “Run Shell Script” encountered an error: “Traceback (most recent call last):
 File "/Users/•••/bin/bin/get_dropbox_link.py", line 37, in <module>
 import dropbox
 ModuleNotFoundError: No module named 'dropbox'

Remarks:

I don't know Python at all, but I remember there is this important distinction whether to install a module only into a project or globally.
And there is also pipx to ease some things with this, which I had installed (I think with brew AFAIR).
But all this is fading memory to me meanwhile.
I guess the bug lies in how the module got installed and is available in the python environment to other scripts.

It looks like there are two /bin directories in the error message. Can you check that the path is right in the Automator action?

I would create an Automator script which runs echo PYTHONPATH and then also run the same in the terminal and look for differences. Then compare that to the location of the module on disk.

I ran python3 -m site in Automator and got this result:
sys.path = [
    '/Users/nick',
    '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/lib/python39.zip',
    '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9',
    '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/lib-dynload',
    '/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/site-packages',
]
USER_BASE: '/Users/nick/Library/Python/3.9' (doesn't exist)
USER_SITE: '/Users/nick/Library/Python/3.9/lib/python/site-packages' (doesn't exist)
ENABLE_USER_SITE: True

This is the same Python environment used by the system python3 binary at /usr/bin/python3, and it's different from my personal python3 environment (since I use asdf to manage Python versions).
So all that to say that the right solution is to install dropbox like this:
/usr/bin/python3 -m pip install dropbox

I've updated the script and README as well, so this should be resolved any future users too.
Thank you for pointing this out, and let me know if this has resolved your problem.

Hi,
I installed your newest python script with the renewed instructions in README.md. (not with pipx like the first time)
It fails, but not early on, already later this time luckily. The dropbox package seems to be available to python this time.
The action “Run Shell Script” encountered an error: “Traceback (most recent call last):
File "/Users/me/bin/bin/get_dropbox_link.py", line 257, in <module>
main()
File "/Users/me/bin/bin/get_dropbox_link.py", line 77, in main
fetcher.fetch(args.paths)
File "/Users/me/bin/bin/get_dropbox_link.py", line 92, in fetch
with dropbox.Dropbox(
File "/Users/me/Library/Python/3.8/lib/python/site-packages/dropbox/dropbox_client.py", line 197, in __init__
raise BadInputException("app_key is required to refresh tokens")
dropbox.dropbox_client.BadInputException: app_key is required to refresh tokens”

On first glance this sounds to me as if it cannot get the API keys.
The previous version left them at: ~/.get_dropbox_link_conf.json with the content:
{
	"refresh_token": "XXX",
	"access_token": "YYY",
	"access_token_expiration": "2023-05-ZZZ"
}

Did the file location or JSON format change maybe?

Can I fix this by renaming/editing the file?
Do I need to repeat the whole API key registration procedure?

I already got to the cause. No deep to reply for now. Will update here later.

✅ I re-ran the entire procedure (including a new app key). Now works.
👉 In order that updating the script and/or resuming with earlier credential files gets more user friendly I created proposal:

#8

This issue is resolved from my side.

But I wanted to leave closing to you, if there may be anything left.

Thanks for this cool script!

An integration/efficiency improvement that Dropbox themselves refused to make themselves,
Now made possible with a FLOSS script solution. Thanks!


MINOR: remove unused import

Remove unused import that's slipping past checkstyle somehow

@cpettitt-confluent @guozhangwang @bbejeck @mjsax

Both Java 11 builds passed, Java 8 failed but results already cleaned up
retest this please

Merged #7345 into trunk.


fix(#350): RepeatComponent use fields as getter

What kind of change does this PR introduce? Bug fix

Current coverage is 91.98% (diff: 100%)

Merging #353 into master will not change coverage

@@             master       #353   diff @@
==========================================
  Files            16         16
  Lines           749        749
  Methods         141        141
  Messages          0          0
  Branches        197        197
==========================================
  Hits            689        689
  Misses           60         60
  Partials          0          0

Powered by Codecov. Last update 0015a97...6a71e40


Missing Context-Aware Configuration After Deploy

We installed the context-aware configuration on an AEM cloud service instance.
But after deployment, we missed the configuration.
According to the guide, we have already enabled the persistence strategy: AEM page, but this solution doesn't work.

hmm, that's difficult to tell the root cause from that description.
if i understand correctly, existing context-aware configurations that you stored before deploying io.wcm.caconfig.extensions are not longer found = could no longer be resolved after deploying it? io.wcm.caconfig.extensions adds additional persistence strategies without disabling the default ones, so normally this should not happen and existing configurations should be resolvable as well.
to see whats going on internally, you can enabled DEBUG or even TRACE logging in AEM for these two log categories:

org.apache.sling.caconfig
io.wcm.caconfig


Add integration tests

Integration test cases:

JobSet with pod DNS hostnames disabled - success scenario: create JobSet with pod DNS hostnames disabled. Ensure all jobs are created, and ensure JobSet status is JobSetCompleted after all jobs have completed.
JobSet with pod DNS hostnames disabled - failure scenario: create JobSet with pod DNS hostnames disabled. Ensure all jobs are created, and ensure JobSet status is JobSetFailed after 1 job fails.
JobSet with pod DNS hostnames enabled - success scenario: create JobSet with pod DNS hostnames enabled. Ensure all jobs are created, ensure all headless services are created, then ensure JobSet status is JobSetCompleted after all jobs have completed.

Notes:

I designed the test cases to each run in their own namespace, in order to avoid weird race conditions I was running into where resources from a previous test case were somehow interfering with the subsequent test case, despite successfully deleting the resources in the AfterEach() block.

@ahg-g Thanks for the review, I finished addressing your comments and this is ready for another look.

/label tide/merge-method-squash

/lgtm


Incorrect network data in daily site reports

e.g. "Usgamer.net daily statsdash for Sun 16 Oct 2016" shows 'Change vs month to date last year' under 'Network Month To Date' as alarmingly low.  This is not the case when looking at the whole network statsdash.

I think we got to the bottom of this off-list, it's all cool.


[BUG] Weird rendering bug occurred using ForgeCIT

Minecraft version
1.20.1
Describe the bug
Forge CIT breaks textures / CIT Resewn doesn't do anything
Steps to reproduce

Install Forge CIT in any mod pack with connect and it will break texture when there are more than 240 Mods installed.
Install Resewn CIT in the same mod pack and disable ForgeCIT, now the texture is normal but CIT doesn't work
...

Logs
No response
Additional context
Very weird issue, I have 2 modpacks that I tested with this.
1st modpack, 240 mods, with Forge CIT, ANYTHING after 240 mods will break the textures.
-> This is to test the limitation of numbers of mods before the texture breaks

2st modpack, 305 mods, with CIT Resewn, works perfectly but CIT Resewn will not render item as it supposed to be. And the moment I swapped CIT Resewn for Forge CIT resewn it will break the texture like the images. Using nongko-3d-weapons
-> Main modpack that I want to use

What are the exact mods required to reproduce this?

Include a crash log

What are the exact mods required to reproduce this?

Here is mod list: https://mclo.gs/elbyUlx
If you want a mod pack I can send the curseforge zipfile

Include a crash log

It's not crashing, it loads fine.
It's just the texture is broken when used Forge CIT and CIT Resewn (Fabric) doesn't do anything.

Then you can send the latest Log

Then you can send the latest Log
Sure
This log is for when everything works fine (240 Mods)
with forge cit 240 mods.log

This log is for when the texture broke after installing 1 extra mod
with forge cit 241 mods.log

Yup, also facing the same issue.
I'm pretty sure that CIT worked before, perfectly, with a previous Connector release.

Yup, also facing the same issue. I'm pretty sure that CIT worked before, perfectly, with a previous Connector release.

From what i do to fix it is that certain resources pack is incompatible (For my case it's Ghoulcraft and Mizunos). If you have modernfix then turn on Dynamic Resources and remove Better Archeology if you have that

From what i do to fix it is that certain resources pack is incompatible (For my case it's Ghoulcraft and Mizunos). If you have modernfix then turn on Dynamic Resources and remove Better Archeology if you have that

I don't think it fixes CIT Resewn, though🤔.

From what i do to fix it is that certain resources pack is incompatible (For my case it's Ghoulcraft and Mizunos). If you have modernfix then turn on Dynamic Resources and remove Better Archeology if you have that

I don't think it fixes CIT Resewn, though🤔.
EDIT: Hmm.. Works only with ForgeCIT... Thanks, though💖!

yeah nah CIT Resewn just doesn't work at all in general for me

As our LTS support target, 1.20.1 now only receives critical fixes related to Connector bugs. Please upgrade to the latest version for mod compatibility support.


File paths (inclusion/exclusion) for acr task triggers

Is there a way to specify inclusion/exclusion of file paths in ACR tasks triggers?
I have a monorepo with many different Dockerfiles and - as there are different jobs that have both source code and base image update triggers - some jobs are build too often when a commit is made in the repository. Once for the commit and once triggered by the base-image update.
Someting as this: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml#paths) perhaps?

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

ID: bd0e3f3c-5aed-28b6-1e28-22ff32a8521d
Version Independent ID: 128e5bc6-e518-bd5a-f511-48e0ed185739
Content: az acr task
Content Source: src/azure-cli/azure/cli/command_modules/acr/_help.py
Service: container-registry
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@BenjaminHerbert thanks for the question. Unfortunately tasks doesn't support path filter. Can you raise your feature request in https://aka.ms/acr/uservoice.
One workaround is disable Tasks built-in commit trigger and instead using Azure Pipeline to subscribe to the filtered commit events and call az acr build -t image . from Azure Pipeline CLI task.

@northtyphoon I am currently using base image update triggers. (See https://docs.microsoft.com/bs-latn-ba/azure/container-registry/container-registry-tasks-overview#automate-os-and-framework-patching).
Do you have a pointer how/if this (read: a base-image update triggers all dependent builds) is is possible with Azure (DevOps) Pipeline?

DevOps hasn't supported  base-image update trigger yet. It's under development. Stay tuned.

@northtyphoon That's good to hear. Is there a way where I can track the progress for this feature? :yum:

This was more of a feature request than documentation question. Closing now.
#please-close

#please-close