AttributeError: 'NoneType' object has no attribute 'T' while trying synthesis.py

Trained the model. while doing evaluation getting below error
AttributeError: 'NoneType' object has no attribute 'T'

The audio is not being generated here. That is why it is throwing a NoneType error. Check demo.iypnb, or try printing the audio shape before .T or transpose.


refactor: look up default values on struct tag

Which problem is this PR solving?

resolves part of #970

Short description of the changes

add a struct tag lookup to getter funcs for fields that default to boolean true

@VinozzZ Yeah I just spoke with @kentquirk and he agreed that its maybe not the best idea to lookup struct tags for every getter func call. There is an option to cache the struct tag values to maybe make this better. But I think the consensus here is that using a defaultTrue type would be the best solution. I'll open a separate PR for that work.


OpenTargets dataset update in the S3 buckets

Hi Guys,
I'm form OpenTargets. One of our users reported that OT data fetched from S3 has some problem: the data seems to have unexplainable duplication.  We believe the problem might due to how the data is synced from EBI ftp. The datasets our pipelines generated via spark are partitioned into smaller chunks with filenames containing a release specific hash. As the hash is different from release to release, the line below probably will not overwrite the content of the S3 buckets, instead, these chunks keep accumulating.
https://github.com/aws-samples/data-lake-as-code/blob/50f57f5b4b81773dfd0a67ab393fe10285899277/scripts/ssmdoc.import.opentargets.latest.json#L30
For more details, please see the issue in our tracker.

@DSuveges ,
Apologies for never responding to this. I missed it! We just fixed an issue with our OpenTargets/Latest dataset where the source data was exceeding the way-to-small 50GB we had allocated for the FTP copy. We've updated that. Is this duplication issue still happening?

Hi @paulu-aws , thanks for getting back to me! So my colleague has opened a PR that supposedly resolved the problem. As the PR got merged and we had no complaints from our users, we considered the issue resolved.


Support for corner-smoothing property via percentage tokens

I'd like to document iOS corner smoothing (anti-alias bezier smoothing) to a border-radius token value.
I'm not sure if there are any alternatives at the moment since the math to accomplish this is quite complex.
Here is a reference to a Figma article that lays out the math involved:
https://www.figma.com/blog/desperately-seeking-squircles/

I think we could introduce percentage tokens which would allow users to set

opacity
corner smoothing

Adding the docs for corner-smoothing here: https://www.figma.com/plugin-docs/api/properties/nodes-cornersmoothing/ in case it will be relevant for development

Awesome and thank you Jan!

This request has been moved to our new feedback tool. Go check out https://tokensstudio.featurebase.app/ to create a free account. You can upvote and comment on existing posts, make a new request, and subscribe to be notified when requests move into our roadmap.

Added to Featurebase Roadmap : 🪙 Expand token types


HTML

#HTML
##User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
##Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the website in my browser
THEN I see four boxes titled HTML, CSS, GIt and Javascript with associated notes listed

The HTML code is ready!


Issue-Moves price formatter into utils

Automated Review Comments
Issues in src/components/coins/CoinListItem.tsx:

(1, 'Hardcoded string found')
(13, 'TODO found')
(15, 'Hardcoded string found')
(23, 'TODO found')
Issues in src/components/coins/utils.ts:
(6, 'Line exceeds 80 characters')
(8, 'Line exceeds 80 characters')
(9, 'Hardcoded string found')

I got it.


Revert "koji_promote: name value should include namespace"

This reverts commit 404836e23ab16c20d2d9e0d2cb08665f4fa6f1dd and fixes up the tests.
We should not be including the namespace in this field (spotted by @pbabinca).

LGTM, merging


Add "resolve() won't return Promise instance"

resolve() won't return Promise instance
const theObject = {
  "a": 7,
};
const thePromise = new Promise((resolve, reject) => {
  resolve(theObject);
}); // -> Promise instance object

thePromise.then(value => {
  console.log(value === theObject); // -> true
  console.log(value); // -> { a: 7 }
})

The value which is resolved from thePromise is exactly theObject.
How about input another Promise into the resolve function?
const theObject = new Promise((resolve, reject) => {
  resolve(7);
}); // -> Promise instance object
const thePromise = new Promise((resolve, reject) => {
  resolve(theObject);
}); // -> Promise instance object

thePromise.then(value => {
  console.log(value === theObject); // -> false
  console.log(value); // -> 7
})

💡 Explanation:

If the value (which is inputted into resolve function) is a thenable (i.e. has a "then" method), the returned promise will "follow" that thenable, adopting its eventual state; otherwise the returned promise will be fulfilled with the value.

– Promise.resolve() on MDN
The specification is ECMAScript <IP_ADDRESS>.2 Promise Resolve Functions. But it is not quite human-friendly.

@denysdovhan
Finally.
Conflicts are resolved. Please review.

Also updated information from MDN.

Thank you!


feat: switch to use @kinde/jwt-decoder package

Explain your changes
Switches to use the shared kinde package for decoding token
Checklist

[x] I have read the “Pull requests” section in the contributing guidelines.
[x] I agree to the terms within the code of conduct.

🛟 If you need help, consider asking for advice over in the Kinde community.

@coderabbitai review


Snippets never load

I'm using Ulauncher 5.11 with the snippets extension, and using some test snippets from this GitHub repository, the snippets don't load. All I get after typing "snip " is "Loading", but the snippets never load.
And one more thing. By default, the snippets directory is set to ~/snippets. But it appears the Snippets extension doesn't convert ~ to /home/$USER because placing the snippets in ~/snippets, typing "snip " in Ulauncher returns "No snippet". After entering the full path to the snippets folder (e.g. /home/logix/snippets) in the extension settings, the "No snippet" message was gone, but now I'm stuck at the but I mentioned above.

I was having this exact problem, but then I re-ran the pip3 command (pip3 install --user dateparser jinja2 python-frontmatter), rebooted ulauncher, and that fixed it. I would guess that one of the dependencies didn't get installed correctly the first time, so it the plugin failed silently. Just FYI.

Thanks for giving the right instructions. I really hope Ulauncher implements a way to automatically install dependencies. https://github.com/Ulauncher/Ulauncher/issues/273

Thanks jlimas and WebInspectInc your suggestions worked for me.


Add support for third party concurrency libraries

Problem

Not all python frameworks use the standard library asyncio module for running coroutines, we should add first class support for such frameworks
Suggested solution

Not clear, don't have enough experience using other concurrency frameworks.
Additional context

trio
gevent
curio

Probably just use anyio. This gives you support for asyncio and trio w/ almost no code changes.
IMO it's not worth supporting gevent and curio.

I will look into that, thank you.
I don't have any experience using third part concurrency frameworks, why would it not be worth supporting gevent anc curio?

I will look into that, thank you.

Cool! I can probably help with the implementation if we end up aligning on the vision.

I don't have any experience using third part concurrency frameworks, why would it not be worth supporting gevent and curio?

Firstly, from a technical perspective, supporting trio and asyncio via AnyIO is very easy. And you have to support asyncio anyway. There's nothing to "do" to support gevent: it monkey patches IO in the standard library. So users of gevent would just use the sync version and apply the gevent monkey patches. Finally, I think (could be wrong) that you can't / it's hard to support curio and asyncio at the same time.
On the practical side, the momentum in the Python ecosystem is towards asyncio + trio + whatever mix of them comes in the future (today that's anyio, tomorrow that may be changes to asyncio to support structured concurrency). I don't think anyone is using gevent or curio in new development, which is what async users of this library would probably be doing.
So TLDR, gevent should just work, curio is not worth supporting and asyncio+trio can easily be supported via AnyIO.
Again, if we aligning on the vision, I'm happy to make the (what I'm guessing is a simple PR) to add trio support via AnyIO.

Ah I see, thank you for clarifying that.
I am averse to adding dependencies and would rather work around issues if they are simple enough, however I will go against that if the work around is too complicated / increases maintainability burden too much.
I haven't used trio before so I don't know how much work would be required to support it, I will look into that before deciding whether or not to use AnyIO, thank you for your informative comment.

I am averse to adding dependencies and would rather work around issues if they are simple enough

Is this in reference to httpx or the concurrency backends?

@adriangb concurrency backends, I will happily add as many optional dependencies as required.

I hadn't actually considered making this feature optional, I will happily merge a PR that adds optional support for trio with AnyIO

Makes sense, sorry my question was nonsensical, I got mixed up with our two threads 🤦♂

@adriangb No worries!


feat: support type args

Status
READY
Breaking Changes
Possible tests that were positive before can be flagged as negative now.
Description
Add support for type args. More on this: #66
Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[x] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Thanks so much for taking the time to open a PR! I'll review as soon as I can. 🙏

Updated formatting but it looks like tests are failing now. I'll try to take a look tomorrow.

Updated formatting but it looks like tests are failing now. I'll try to take a look tomorrow.

That was a weird break, something related to the local package dir. Maybe a re-run?

@renancaraujo tests are failing with the current implementation. You can run them locally for more information. I'll try to take a closer look soon but haven't had time recently.


🐾 Providing a link to the Openstack console of remote cluster.

Ref: https://github.com/kubev2v/forklift-console-plugin/issues/1106
Providing a link to remote cluster UI (Openstack):
Improve integration with the Openstack UI by providing a link to the Openstack UI of remote cluster.
Issue:
In providers details page, we show a information about the provider, in the case the provider is the a remote Openshift cluster we can add a link to the clusters console URL.

addressed by https://github.com/kubev2v/forklift-console-plugin/pull/1158


Media Hotlinking: Show "Preview unavailable" placeholder if loading fails

Feature Description

Taking this out of #8667.
Sometimes a video or image cannot be displayed in the editor due to CORS, but it will still work fine on the frontend.
For this case, we need some sort of placeholder in the editor that says "Preview unavailable" or something like that.
For example, the image https://pascalbirchler.com/wp-content/uploads/2021/08/juliana-malta-Km_14xo_PIo-unsplash-scaled-e1628006213150-1536x768.jpg would be totally fine to embed, but the editor says it's invalid because of those missing headers.
To give an example, in Gutenberg, embeds which cannot be previewed are displayed like this:

Alternatives Considered

Additional Context

FYI @aaskedall

Re: CORS, can we distinguish between the cases:

The placeholder preview fails but will render fine in the FE
Both preview and FE will fail to render the image

Wondering if we should prompt the user to verify visibility of the image in the story preview.

I don‘t think (2) ever happens.
Only (1), and only if video optimization (and thus cross-origin isolation) is enabled.
There are also some ideas to show a preview in the editor using a simple CORS proxy, but that‘s prone to abuse and raises security questions.
Also worth noting that without a preview in the editor we don‘t know an image‘s correct aspect ratio / dimensions.

@swissspidy Would this be an ok place to start?

@aaskedall What would the "View in browser" link do, would it open just the media URL in a new tab? Perhaps "View Image" or "View Video" or something similar would be more informative (with an external link icon), then the user would see right away as well if the element is video or image without having to select the element. Thoughts?

I updated it to say view preview since it should work in the preview window. I think that is the info a user would care the most about. How does this look in my story?
https://www.figma.com/file/1YM3jA9h4QGc4xLdyaXIJS/Stories-Sprint-1.7?node-id=9776%3A384592

Aside: I wonder how creators will grapple with authoring a story page with an image/video that can't be previewed and whose aspect ratio is unknown. E.g. I think it'll probably be difficult to layer elements on top, resize accurately, and jumping between the preview mode and the editor is unwieldy.
Some thoughts:

Should we force the user to manually input the aspect ratio to make sure that it won't be distorted?
Should the placeholder have a different visual treatment to make a little easier to work with? E.g. low-contrast checkerboard pattern, or some stock photo with a watermark that tells the user to preview the story.
I wonder if a "View in browser" button directly on the image might feel weird -- currently, there are no such call-to-actions/links on elements in the canvas

Updated figma here. https://www.figma.com/file/1YM3jA9h4QGc4xLdyaXIJS/Stories-Sprint-1.7?node-id=9776%3A384592
I think the way images are scaled currently crops the image vs it being proportionally wrong so perhaps this is not a problem.
In regards to the view in browser preview, A user inserting an image will immediately be confused by this state, if the CTA is right there to show the image in the preview it should then be more understandable that "oh, it only doesn't show up in the editor"

Alternative: require thumbnail/poster upload to WP for display in the editor, and add a new optional "hotlink URL" field to image elements. When specified, causes the image element to render the hotlink URL in the output STAMP. Higher friction UX, but still may satisfy the user intent to avoid bandwidth costs on creator origin.
Other notables:

We discussed COEP workarounds some time ago in #6776.
Interesting possible long-term solution: https://developer.chrome.com/blog/coep-credentialless-origin-trial/

The more I think about it, the more I think we should explore using a CORS proxy so that image requests in the editor are proxied through WordPress. Despite concerns around performance/abuse/security.
That would be the option with least UX friction.

Closing this as the CORS proxy approach seems to be working well.


Add example result in README

I'd love to see an example with 2-3 images as input and the expected output.
Overall the README could use some love but this could be a very good TL;DR;

https://admin.cloud.coveo.com/208/images/sprites.png


Upgrade from grafonnet-lib to grafonnet

It's mostly a mechanical translation. I'll do it one at a time, and eventually it'll be done.

Custom layout code in our deployer is no longer required, as grafonnet supports automatic grid
layout! But it doesn't support mixed widths (boo)

It will also get rid of this ugly notice:

Remove the google cloud specific bits in our labeling, and make them work with at EKS provisioned with eksctl and AKS on Azure

 Here we see that on AWS too we will get info split out per-nodegroup, rather than all aggregated together!

Everything that displays just node names will now also have the nodepool it is a part of displayed alongside. Makes identification much easier, especially on AWS with its just-ip nodenames

Would've been practically impossible to see that there was an OOM kill in a core node here.

TODO
Files to migrate

[x] cluster.jsonnet
[x] jupyterhub.jsonnet
[x] jupyterhub.libsonnet
[x] support.jsonnet
[x] usage-report.jsonnet
[x] user.jsonnet
[x] global-usage-stats.jsonnet

Remaining work

[ ] Fix remaining commented out things like sort, thresholds, etc.
[ ] Review visual changes

[ ] cluster.jsonnet
[ ] jupyterhub.jsonnet
[ ] jupyterhub.libsonnet
[ ] support.jsonnet
[ ] usage-report.jsonnet
[ ] user.jsonnet
[x] global-usage-stats.jsonnet

Things to catch

[ ] Functionality to not show series with nulls or 0s only has been moved around a bit (https://github.com/grafana/grafana/discussions/38299). We should systematically enable it
[ ] To stack or not to stack? We previously had a haphazard approach where the answer was 'lolmaybe'. Be consistent.

Fixes https://github.com/jupyterhub/grafana-dashboards/issues/89

I am tempted to reorganize some of the panels while at it, but in order to make review and merging easier, I'll hold off and do that separately!

I've migrated all dashboards and panels so they render now, with some commented out options still.
I've not done any visual testing yet of how dashboards look before after change, and instead relied on ensuring jsonnet files render at all, and that jsonnetfmt and jsonnet-lint are happy (which now makes pre-commit pass).
Considering how I should best review changes visually, thinking about for example:

use deploy.py against a 2i2c cluster
port-forward a 2i2c clusters prometheus server and run grafana locally in a docker container

I figure I'll go for the slow but known-to-work strategy of using deploy.py.

I'm currently testing this at https://grafana.pilot.2i2c.cloud and can conclude there are things to fix still, but now its easy to compare side by side with the main branch's changes as I've deployed these to a dedicated folder.
 export GRAFANA_TOKEN=<...>
./deploy.py --folder-name "dev dashboards" --folder-uid "70E5EE84-1217-4021-A89E-1E3DE0566D94" https://grafana.pilot.2i2c.cloud && ./deploy.py --folder-name "dev dashboards" --folder-uid "70E5EE84-1217-4021-A89E-1E3DE0566D94" --dashboards-dir global-dashboards https://grafana.pilot.2i2c.cloud

Observations
Stacking could misbehave previously if one value went from something to null or similar, but that issue seems to go away after the upgrade.

I worked this to completion, this is ready for review!
About changes
I've worked to be as similar as before as possible, but there are some detail differences that I think are fine. I've visually inspected all dashboards and their panels and compared before/after this PR. This can be done at https://grafana.pilot.2i2c.cloud/ where the updated dashboards are found under the dev dashboards folder, and the old under the JupyterHub Default Dashboards folder. If you want to review this and don't have access, ping me and I'll provide you with access to review.
user-dashboard gif comparison

usage-report-dashboard gif comparison

support-dashboard gif comparison

jupyterhub-dashboard gif comparison

cluster-dashboard gif comparison

global-dashboard gif comparison
Numbers differ, but I think the new numbers are correct. It related to "Resolution 1/2" being set on the old, getting it to Resolution 1/1 makes the values become the same.

Test failures
Unrelated - tests were recently added in a failing state to trial their usefulness.

Thank you for reviewing this @GeorgianaElena!!!!

I started by checking out the code in the jsonnet files, but felt overwhelmed, so I ended up doing a side-by-side visual inspection of the panels. I feel confident that we should merge this though, as the panels either rendered the same, or were fixed by this PR.
If you also feel confident in the changes here @consideRatio, I believe you should feel empowered to go for a merge 🚀

Thank you for going for the review anyhow - I think the visual review is the key thing here as its the actual result. I think this is in a mergable state, and I opened #116 and #117 to track related work discussed in comments.
Thank you @yuvipanda for starting this work!


1.JiBnMqyl6S.gif Failed to load resource: the server responded with a status of 404 (Not Found)

I got this issue after activated filters on my nginx :(
Im using prestashop with url friendly :/

Is that the full error?  Could you "view source" on the page, find the reference to 1.JiBnMqyl6S.gif, and paste the surrounding html here?
When you say prestashop with url friendly you mean this, right? http://doc.prestashop.com/display/PS15/System+Administrator+Guide#SystemAdministratorGuide-NginxfriendlyURLs  This looks like it might interact badly with ngx_pagespeed; I'm not sure yet.

Hey Jeff :)
Thanks for you reply !
yes, thats this url rewriting ! In fact, it s this one : http://pastie.org/10036442
the full error :
Failed to load resource: the server responded with a status of 404 (Not Found)
https://example.com/pagespeed_static/1.JiBnMqyl6S.gif
And an example where it is called :

but I haven't got /pagespeed_static/ on my server...
thanks

That's a tiny (1x1) gif that PageSpeed uses as a placeholder when lazyloading images.  PageSpeed should handle serving it; here's an example: http://ngxpagespeed.com/pagespeed_static/1.JiBnMqyl6S.gif
Do you have this line in your config?
 location ~ "^/pagespeed_static/" { }

(From https://developers.google.com/speed/pagespeed/module/configuration)

Yes I got it !
My nginx config : http://pastie.org/10036535

I think this is probably a bad interaction with your rewrite rules.  Probably the simplest fix would be to disable lazyload_images by removing it from the list on line 105.

(Or you could try to see what rewrite rule might be catching this file under /pagespeed_static/.

Yes thanks you Jeff :)

For anyone having this issue (404 on the GIF file from /pagespeed_static/), i fixed it adding:
pagespeed LazyloadImagesBlankUrl "https://www.gstatic.com/psa/static/1.gif";
to my config.


Status bar  not transparent

Great API!
After following your instructions I created viewpager but the color of my status bar is still colorPrimaryDark. I have copied your theme. I have tried setting flags also but nothing can turn it transparent. What am I missing?
Thanks.

Me too having this issue. Anybody have any thoughts? Thanks.

Please copy the following code into your mainactivity. From this link: https://learnpainless.com/android/material/make-fully-android-transparent-status-bar
@Override
protected void onCreate(Bundle savedInstanceState) {
	...

	//make translucent statusBar on kitkat devices
	if (Build.VERSION.SDK_INT >= 19 && Build.VERSION.SDK_INT < 21) {
		setWindowFlag(this, WindowManager.LayoutParams.FLAG_TRANSLUCENT_STATUS, true);
	}
	if (Build.VERSION.SDK_INT >= 19) {
		getWindow().getDecorView().setSystemUiVisibility(View.SYSTEM_UI_FLAG_LAYOUT_STABLE | View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN);
	}
	//make fully Android Transparent Status bar
	if (Build.VERSION.SDK_INT >= 21) {
		setWindowFlag(this, WindowManager.LayoutParams.FLAG_TRANSLUCENT_STATUS, false);
		getWindow().setStatusBarColor(Color.TRANSPARENT);
	}
}

public static void setWindowFlag(Activity activity, final int bits, boolean on) {
	Window win = activity.getWindow();
	WindowManager.LayoutParams winParams = win.getAttributes();
	if (on) {
		winParams.flags |= bits;
	} else {
		winParams.flags &= ~bits;
	}
	win.setAttributes(winParams);
}


Require the namespace for the webhook secret

Please provide a description for what this PR is for: https://github.com/istio/istio/issues/18897

@lei-tang: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
0aea2bf932271c409cd3242c6c97c80c93ac1284
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible it has been revised based on your comment.

@lei-tang: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
4ff26e54a2d7a85f049fa10761b74a4a682ade78
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lei-tang: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
4ff26e54a2d7a85f049fa10761b74a4a682ade78
link
/test unit-tests_istio

lint_istio
203eccdd9453194ba055dbdff0c5cd4445f773c7
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test lint_istio

@lei-tang: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
203eccdd9453194ba055dbdff0c5cd4445f773c7
link
/test lint_istio

unit-tests_istio
203eccdd9453194ba055dbdff0c5cd4445f773c7
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lei-tang: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
203eccdd9453194ba055dbdff0c5cd4445f773c7
link
/test unit-tests_istio

e2e-dashboard_istio
f849b9ca802088f06f929ac12d918d9b5f716e18
link
/test e2e-dashboard_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/cherrypick release-1.4

@lei-tang: new pull request created: #18910

In response to this:

/cherrypick release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Lung Cancer Detection:

Detection of Lung cancer  using  strategically designed convolutional layers, max pooling layers ,dense Layer and fully connected layers in Deep Learning.
I agree to follow this project's Code of Conduct
I'm a GSSoC'24 contributor
I want to work on this issue

Hey @akshitagupta15june  Please assign this issue to me under SSOC'24, I really want to work on this.

I am interested in this issue. Please assign me this

its not related to face


Unable to run a pod successfully when Subnet IP resources are sufficient

describe the bug
When there are not enough resources in the subnet, the creation of a new Pod fails, and then some resources are released in the expectation that the Pod will run successfully, but in the end the Pod fails to run successfully.
Screenshots and log
{"level":"ERROR","ts":"2022-10-31T20:59:31.368Z","logger":"spiderpool","caller":"cmd/command_add.go:122","msg":"[POST /ipam/ip][500] postIpamIpFailure  failed to allocate IP addresses in standard mode: no IPPool available, all IPv4 IPPools [auto-deployment-ns5922-896537270-deploy-1-5924-35535620-v4-1667249964] of eth0 filtered out: all IP addresses used

{"level":"ERROR","ts":"2022-10-31T20:59:24.610Z","logger":"SpiderIPPool-Informer","caller":"ippoolmanager/ippool_informer.go:367","msg":"error syncing 'auto-deployment-ns5922-896537270-deploy-1-5924-35535620-v4-1667249964': failed to expand IPPool 'auto-deployment-ns5922-896537270-deploy-1-5924-35535620-v4-1667249964' with IPs '[<IP_ADDRESS>]', error: failed to update IPPool 'auto-deployment-ns5922-896537270-deploy-1-5924-35535620-v4-1667249964', error: Operation cannot be fulfilled on spiderippools.spiderpool.spidernet.io \"auto-deployment-ns5922-896537270-deploy-1-5924-35535620-v4-1667249964\": the object has been modified; please apply your changes to the latest version and try again, requeuing"}

{"level":"ERROR","ts":"2022-10-31T20:59:28.773Z","logger":"SpiderIPPool-Informer","caller":"ippoolmanager/ippool_informer.go:367","msg":"error syncing 'auto-deployment-ns5922-896537270-deploy-1-5924-35535620-v4-1667249964': failed to generate IPs from subnet 'v4-ss-5923-936159157', error: insufficient subnet FreeIPs, required '1' but only left '0', requeuing"}

Additional context
Add any other context about the problem here.
https://github.com/spidernet-io/spiderpool/actions/runs/3364501818/jobs/5579018466
Upload the zip file generated from that test failure.
ipv4Only-debuglog.txt (2).zip

https://github.com/spidernet-io/spiderpool/actions/runs/3367529754/jobs/5585152242


Closes #95: Add attachment support

Summary of changes
Add functions for attachments retrieval from posts
Checklist

[ ] Changes represent a discrete update
[x] Commit messages are meaningful and descriptive
[ ] Changeset does not include any extraneous changes unrelated to the discrete change

I'm open to critics regarding code standards and if you have some posts with attachments in the test discourse please share id and slug so that I can add tests

Also please add a "Closes #95" to your commit message

Can I confirm the behaviour topic_attachments? (sorry to bounce this to you as a question).

takes a topic, eg https://meta.discourse.org/t/understanding-uploads-images-and-attachments/275735
uses the other methods to extract attachment urls, eg https://d11a6trkgmumsb.cloudfront.net/original/4X/b/5/d/b5d483135cb1405290f07bfe4a9f5bd6dd9b6a1b.png
Checks the extension is in the permitted list

Have I got that right?
Thanks for the contribution - most of my feedback is questions or requests for short non functional changes but they'd be nice to have.
thanks,
kk

Can I confirm the behaviour topic_attachments? (sorry to bounce this to you as a question).
* takes a topic, eg https://meta.discourse.org/t/understanding-uploads-images-and-attachments/275735

* uses the other methods to extract attachment urls, eg https://d11a6trkgmumsb.cloudfront.net/original/4X/b/5/d/b5d483135cb1405290f07bfe4a9f5bd6dd9b6a1b.png

* Checks the extension is in the permitted list

Have I got that right?
Thanks for the contribution - most of my feedback is questions or requests for short non functional changes but they'd be nice to have.
thanks, kk

Hi sorry for the big delay, I've been very busy. Yes that would be the intended behaviour. I also addressed your comments, let me know if they make more sense to you know

Hi, any news on this?

Hi, any news on this?

Hi Frank,
Import logging looks like its the only extraneous move now (https://github.com/pydiscourse/pydiscourse/pull/96/files#diff-6cd9d84a11416e5456653817c28de5b33224ec63dfc5776b3e1b567454df0c75) so I'm hitting the button run the testsuite and we'll check our status after that runs.

@Frank995 it looks like the linter has a few complaints about whitespace issues
https://github.com/pydiscourse/pydiscourse/actions/runs/7030837244/job/20000450106?pr=96
Could you please resolve them?
thanks,
Karl.

@Frank995 it looks like the linter has a few complaints about whitespace issues
https://github.com/pydiscourse/pydiscourse/actions/runs/7030837244/job/20000450106?pr=96
Could you please resolve them?
thanks, Karl.

Hi, I should have fixed the above mentioned problems. Let me know

@Frank995 it looks like the linter has a few complaints about whitespace issues
https://github.com/pydiscourse/pydiscourse/actions/runs/7030837244/job/20000450106?pr=96
Could you please resolve them?
thanks, Karl.

Hi, I should have fixed the above mentioned problems. Let me know

Sorry about the long turn arounds on this.
I can't merge yet because coverage is in client.py < 46% while the current coverage is 45% (yes really, 1% :/).
I will look at pushing that up a bit in the coming days.
thanks,
Karl.

I had forgotten about this for a while. Any chance it gets merged?


Server Side rendering not working

Component inside QueueAnim is not being rendered on server side. Is there any setting for this or it doesn't support the server side rending ?
My code is like:

Any help deeply appreciated. Thanks in advance

Can you provide error messages?

Although I am getting one warning, I am not getting any error message.

When I do view source, I am not seeing the data into the html.

I tested it with no problem and no warning.
Can you provide your code?

https://github.com/ant-motion/nextjs-queue-anim

Thank you Jiang for the example. I tried the example but it is giving below
error message:
[image: Inline image 1]
In the mean time I am also setting up the project and will share with you
soon. Here my concern is Server Side Rendering as on client side it is
working perfectly.
On Tue, Jun 13, 2017 at 10:18 AM, jiang<EMAIL_ADDRESS>wrote:

https://github.com/ant-motion/nextjs-queue-anim
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/react-component/queue-anim/issues/40#issuecomment-308018021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG9Bkfmq5U8Gm5b-c5-wknsU8aO_T-Acks5sDimZgaJpZM4N3hQE
.

--
Warm Regards,
MANOJ KUMAR
Delivery Head - Software
[image: Flora Creek Deluxe Hotel Apartments]
HOTELS & HOTEL APARTMENTS
Near Deira City Centre, Port Saeed | 119062 Dubai, UAE
T +971 4 230 9000 | D +971 4 230 9750 | M +971 56 179 7748
florahospitality.com https://www.florahospitality.com/
A Division of Pearl Investment LLC
[image: facebook] https://www.facebook.com/florahospitality/

Dear Jiang,
Without queueAmin, Server Side rendering is working perfectly.
Code
[image: Inline image 1]
Server Side Rendering
[image: Inline image 2]
With QueueAnim
[image: Inline image 3]
Server Side Not Rendering
[image: Inline image 4]
Link to the github repository:
https://github.com/hotelx/react-starter-kit
https://github.com/hotelx/react-starter-kit
On Tue, Jun 13, 2017 at 10:50 AM, Manoj Kumar <
<EMAIL_ADDRESS>wrote:

Thank you Jiang for the example. I tried the example but it is giving
below error message:
[image: Inline image 1]
In the mean time I am also setting up the project and will share with you
soon. Here my concern is Server Side Rendering as on client side it is
working perfectly.
On Tue, Jun 13, 2017 at 10:18 AM, jiang<EMAIL_ADDRESS>wrote:

https://github.com/ant-motion/nextjs-queue-anim
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/react-component/queue-anim/issues/40#issuecomment-308018021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG9Bkfmq5U8Gm5b-c5-wknsU8aO_T-Acks5sDimZgaJpZM4N3hQE
.

--
Warm Regards,
MANOJ KUMAR
Delivery Head - Software
[image: Flora Creek Deluxe Hotel Apartments]
HOTELS & HOTEL APARTMENTS
Near Deira City Centre, Port Saeed | 119062 Dubai, UAE
T +971 4 230 9000 | D +971 4 230 9750 | M +971 56 179 7748
florahospitality.com https://www.florahospitality.com/
A Division of Pearl Investment LLC
[image: facebook] https://www.facebook.com/florahospitality/

--
Warm Regards,
MANOJ KUMAR
Delivery Head - Software
[image: Flora Creek Deluxe Hotel Apartments]
HOTELS & HOTEL APARTMENTS
Near Deira City Centre, Port Saeed | 119062 Dubai, UAE
T +971 4 230 9000 | D +971 4 230 9750 | M +971 56 179 7748
florahospitality.com https://www.florahospitality.com/
A Division of Pearl Investment LLC
[image: facebook] https://www.facebook.com/florahospitality/

I clone it, no problem

Dear Jiang,
Once again thank you for your support and time.
I understand there is no problem while rendering it client side or browser.
But when you do *view souce *of the page, you will not see the
content/html/DOM in case you are using QueueAmin. But if you render the
page without QueueAmin and do view source, you can see the content being
rendered.
Without QueueAmin
[image: Inline image 2]
With QueueAmin
[image: Inline image 1]
I hope now you understand my issue.
On Tue, Jun 13, 2017 at 2:05 PM, jiang<EMAIL_ADDRESS>wrote:

I clone it, no problem
[image: 222]
https://user-images.githubusercontent.com/6802825/27077526-ed40e83e-5062-11e7-9057-8f71d6607bac.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/react-component/queue-anim/issues/40#issuecomment-308069413,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG9BkVXlGVQZuR0UmA1Mv9HfXRTdSRzGks5sDl8BgaJpZM4N3hQE
.

--
Warm Regards,
MANOJ KUMAR
Delivery Head - Software
[image: Flora Creek Deluxe Hotel Apartments]
HOTELS & HOTEL APARTMENTS
Near Deira City Centre, Port Saeed | 119062 Dubai, UAE
T +971 4 230 9000 | D +971 4 230 9750 | M +971 56 179 7748
florahospitality.com https://www.florahospitality.com/
A Division of Pearl Investment LLC
[image: facebook] https://www.facebook.com/florahospitality/

Sorry, I didn't catch your meaning at first.
queue-anim It depends on rendering to finish the animation, so it must be empty at first.

appear is false will render.

https://github.com/react-component/queue-anim/blob/master/src/QueueAnim.jsx#L342  =>
const childrenToRender = typeof document !== 'undefined' && typeof window !== 'undefined' ?
      toArrayChildren(this.state.children).map(this.getChildrenToRender) : this.props.children;

this case, element will appear first, then animation appear, which is conflicting.
If you have a good solution, welcome PR.


[docs] Add Khmer (kh-KH) locale support

[x] I have followed (at least) the PR section of the contributing guide.

can you help explain a bit more?

can you help explain a bit more?

You're claiming that kh-KH is supported, but it is not. Are you asking for support or would you like to add support for it?

so sorry about the mistake, I'm trying to add support for the language. I fix the mistake and pull another request. so sorry

so sorry about the mistake, I'm trying to add support for the language. I fix the mistake and pull another request. so sorry

Everything is fine now. You can just push to the same branch and the pull request is updated automatically.

newbie to this, I'm sorry for any inconvenience.

newbie to this, I'm sorry for any inconvenience.

Don't worry. We've all gone through this. This is a safe environment for experimentation. The only thing that's required is communication and it was perfect from your side.

@eps1lon, is there anything I need to do after the checks have passed?

@teachhay It's a great first pull request on Material-UI. Thank you for working on it!


Update data-loss-prevention-policies.md

Added a line stating that Compliance and security admin need no extra permissions to create or modify a policy as they have the access by default.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@msbemba

@chrfox Please merge this PR. Thanks


Uninstall restores now the original shell

Hi there,
after having uninstalled oh-my-zsh I've noticed that the environment was not restored correctly.
The aim of this PR is to:
1 - Store the current shell into ~/.shell.pre-oh-my-zsh, when running install.sh
2 - Restore the default shell (previous to oh-my-zsh), when running the uninstall script.

See also pull request #2626.

Looks similar ... shall we merge the other then?

Hi @tonyqui I pulled the fix in #5169 which introduces other fixes and is now ready for testing.
If you want to help speed up the testing and merge (which should happen early next week), you can wget or curl it from the URL https://raw.githubusercontent.com/mcornella/oh-my-zsh/refactor-installer/tools/install.sh. Read the comments at the top of the script to know how to call it.
Thanks!

Closed by #5169.


Specify table schemas before creating models for extra validation

Feature
Feature description
In dbt, tests and schema.yml files are a powerful way to validate assumptions about models. However, tests can be limiting:

You can only run tests after a model has been built (see https://github.com/fishtown-analytics/dbt/issues/1054).
Tests do not contain information about the expected types of columns. For example, I could expect integer, but a floating point operation coerces that column to float.
Specifying an extra column in schema.yml doesn't seem to throw an error when building a model or its docs. For example, if my model produces a column foo and I have a column with - name: foo123 in schema.yml, then the model and documentation generate fine without noticing the error.

I propose allowing dbt to use schema.yml schemas to run CREATE TABLE foo(<columns>) plus INSERT INTO foo SELECT instead of CREATE TABLE AS SELECT ... (I'm experienced with postgres, Redshift, and Snowflake. Apologies if other backends work differently.)
This provides the following benefits:

Users can provide column constraints that are easily checked like NOT NULL. The database will cheaply validate them for us, and fail to create a model if validation fails. In particular, postgres can also check UNIQUE easily (it creates an index for you under the hood, but you just have to say something is UNIQUE).
Users can specify column types, which again will get checked as the model is populated.
Users can assert the list of columns in the table schema matches what the model is producing. No extra or missing columns.
Some backends like Redshift allow specifying constraints that aren't checked, like foreign keys. These constraints do help Redshift optimize queryies though.

A user could decide to use CREATE TABLE/INSERT instead of CREATE TABLE AS via a boolean flag somewhere for a model. Maybe this flag could be set in schema.yml, since a schema is required for this to work? I'm still a dbt novice, so I do not have much of an informed opinion here :smile:
Who will this benefit?
Anyone who uses dbt and wants extra validation in their table schemas would benefit. This feature gives more immediate validation of model schemas and leverages the features in our databases to do this cheaply.

Hey @jdreaver - cool idea! We had an issue to generate table definitions from schema.yml specs back in the day -- check it out over here: https://github.com/fishtown-analytics/dbt/issues/1016
There's also a discussion over here about database-level constraints that I think might be relevant.
Ultimately, this is something that I think this would solve some real problems for people, but it would be super involved to build and support. Here's the way that I could see a workflow like this being supported in dbt:

Augment schema.yml to accept arbitrary configs, then provide these configs in the materialization context
Create new materializations that build empty tables, then insert into them

So, you might have a schema.yml file like:
version: 2

models:
  - name: my_model
    columns:
      - name: id
         config:
           type: int
           encode: zstd # Redshift only
           primary_key: true

Then in a materialization, you could loop over the list of provided columns and build a table from DDL, then insert into it from your model SQL. If dbt were to support a workflow like this, I imagine that this is how we'd do it!
So, there is a tractable approach here, but there's still a question in my mind around whether or not we should even support workflows like this in dbt. It's pretty antithetical to the everything is a select design decision at the core of dbt, and I dislike how it fragments logic across model SQL and schema.yml specs.
I can tell you up front, I'm not super interested in supporting column constraints from dbt. If they come naturally as a part of some grander feature, then I'm ok with them, but I remain unconvinced of their utility in analytical settings. In particular, I dislike that they 1) are typically unenforced (or unsupported) on many analytical databases and 2) move constraint checking from test-time to build-time.
With dbt's schema test, we're adding functionality to set a "severity" level (either WARN or ERROR) for test failures. In the future, we might also add a minimum threshold before which tests will warn, and not fail. This is useful in relationships tests where one source table might be loaded before another by some ETL job. If 10 rows out of 10 million are missing a corresponding parent record for 10 minutes, I don't think that should (usually) prevent your models from building!
 Moreover, Redshift in particular can return incorrect results if a column constraint is applied but invalid!
I do however find merit in enumerating and validating all of the columns in a schema.yml file. I think that in 90% of models, this process is probably unnecessary: the benefit of keeping all of your model logic in a single .sql file outweighs the downside of synchronizing the schema and logic in two different files. If you're really keen to specify a column type in a model, you can always do:
select
  id::bigint as id
from {{ ref('my_model') }}

I think that enumerating column names and types would be most useful when there's some external constraint, like when in-app reporting is happening on top of a given table, for instance. This is distinct from internal analytics use cases, wherein the cost of having an extra column documented for your model is pretty low (and doesn't justify enumerating every column and type in every model). The last thing to say here is that this problem may be better suited for something like a linter than a fundamental redesign in how dbt models IMO.
Ok, finally, dbt supports custom schema tests, and you can very well assert type information for tables if you desire! You can check out the docs on custom schema tests for more information about making one of these yourself.
So, this is a sort of brain dump of all the things in my head regarding this topic. I think it's something we may tackle in the future, but i think the utility is still a little nebulous, at least to me. If you have opinions on any of these things, I'd love to hear them! Thanks for writing in with a thoughtful and thought-provoking feature request :)

Hey @drewbanin! Thanks for the thorough response!
Everything you've said makes total sense. I'm glad you have a guiding principle in the design of dbt (everything is a SELECT), and I totally wouldn't want that to break that for a small use case like this.
I agree that simply validating the list of columns in schema.sql against what is actually produced is probably good enough. My goal here is to avoid documentation drifting from models. That is, if we say a model has columns x, y, and z, but we add a column w or we remove column y, I'd love if something yelled loudly at me before I ran dbt.
I'm going to take a look at custom schema tests to see if I can get those to do what I want. If I come up with something valuable I'll post back to this issue so others can see my solution.
Thanks again for writing all of this up! I'm glad you broke this down by use case instead of by a single potential solution like I did. It gives me a lot to work with.

Cool! I'm going to close this issue in favor of something more actionable if/when we decide to prioritize some version of this. Definitely don't hesitate to follow up here if you have any questions or want to share further thoughts on this topic :)
Thanks again!


[bug]: Uploaded images lose metadata

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
No response
What happened?
When you create an image with Invoke, it adds metadata to the file.  This metadata can be seen by clicking the Info button in the WebUI.  If you drag the created image into the Uploads area, then click the Info button, it will say that No Metadata is available.  However if you take the same image and drop it into Automatic1111, it will read the metadata.  Invoke is somehow failing to read the metadata on uploaded images, or even images that have been dragged from the Generation window to the Uploads window.
Screenshots

Additional context
No response
Contact Details
<EMAIL_ADDRESS>Steve Warner#1284 on Discord

@psychedelicious This is actually an enhancement request, but is something that I have bumped into on several occasions myself and wish there were a fix for. I have a whole bunch of images on my external disk from earlier versions of invokeai, and I wish I could upload them and easily retrieve their metadata.

@realstevewarner @lstein
I'm pretty sure that the metadata is readable, but you have to refresh the page. The server doesn't read the metadata correctly when first uploading an image.
Going to file this under no-fix because this will be a non-issue on the new server/API.

That's weird.  Okay.  So I checked and yes, it does show the metadata once I refresh the page.  Strange that we'd have to do that.  But you're saying the next version of Invoke this won't be required?  I'm not sure what the new server/api is.

@realstevewarner
We have v2.3.0 pending release. It will not be fixed in that.
The bug is in the current web server - we are really trying to not making any more changes to it because any work there will be lost once we move to a new server. I can't give a solid ETA on the release that will fix this, sorry. If it turns out to take longer than expected, maybe we can address this sooner.

Okay.  Thanks for the update.  Happy to hear there's a workaround at least.  One last question.  If I refresh my browser, it resets all my prompt settings, size, sampler, etc.  Any way to avoid that if I'm just trying to get metadata on an imported image?

@realstevewarner You shouldn't lose anything on refresh - that's a different bug.
Please try Reset Web UI from Settings (gear icon @ top right) then refresh the page (this will definitely clear out all the your settings). Then try entering a prompt, wait a second for it to save, and refresh the page. Does it remember it now?

Nope.  It wipes out all my settings.  Keeps the model, fortunately.  But my prompt, seed, sampler, CFG, etc. all go away.  I know I can get those back by right clicking on the last generated image and pressing "use all."  So it's not a crisis.  Just an annoyance.

@realstevewarner Hmm. Please refresh browser while on InvokeAI and see if there is any output in the javascript console. [Here's how to open the javascript console on most browsers].

Do you see any output? Please copy and paste everything there if so.

After double-checking that you are on the InvokeAI UI page, paste localStorage.clear() in the console and press Enter to fully reset the InvokeAI UI. Then try changing some settings and see if they persist. Any luck?

I opened the Javascript console for the Invoke web UI page while Invoke was running and refreshed the page.  Here's what I got.

I then did a full UI reset (from the Gear icon) and refreshed the page.  The Javascript panel showed:

Once on the Invoke UI page, I tried the localStorage.clear() command into the command line console but it would not allow user input.  I tried typing the command directly but it would not accept it.  It seems that I can't type into the command line interface while in WebUI mode.  So I tried to force the command by putting it into the prompt field of the webUI.  I figured it might pass the command down to the console.  Nope.  It generated the following image.  LOL.

The issue isn't Invoke, though.  It's my browser.  I'm using Brave (with all protective shields turned off).  On a whim, I tried running the WebUI in Firefox and it was able to save all the settings even after a refresh.  Moreover, I didn't get the error loading in thumbnails that I normally get in Brave.  At least not to the same prevelance.  It's definitely a browser issue.  I'll look into the Brave settings a bit more and see if there's anything else I can do to get it to work better.
Many thanks for the ongoing support!

Thanks for the troubleshooting, and great find re: brave. I'll download that browser and see if I can recreate the issue.
To clarify I meant the browser JavaScript console not the command line where you start the server. If you couldn't type into the JavaScript console... well, that's really weird!

Ah!  Okay.  I'm dumb.  LOL.  I typed that into the Javascript console and it said "undefined"

But once I refreshed the page, it kept all the settings!  I can't explain that at all.  But it worked!

Yes, that's the expected output. Something in the browser's storage of your settings had gone sideways. localStorage.clear() is the nuke-everything-button.
Glad it's working! Just to confirm, does this fix the issue for Brave?

With regards to the issue of it losing the settings once I refresh, absolutely.  And as noted earlier, refreshing seems to fix the metadata issue of uploaded images.  The only outstanding issue I see is the occasional missing thumbnail.  The UI throws out an error and I get a "broken" icon.  The images are still there, however.  I just can't get a preview of them.

Thanks, I'll need to look into that. Do the thumbnails for those specific images never ever display, or only sometimes display?

It's random.  If I refresh the page, some will display.  Others will not.  It's usually about 3 to 5 that just don't show up, but refreshing will make them show up and others not.
Thanks again for your help with this!

I just tested with RC7 and the only way I can get the metadata in an uploaded image to display is by resetting the WebGUI and then reloading. Just a reload doesn't seem to do it. I don't consider this a blocking issue, but something to keep in mind.

That really shouldn't be needed. The gallery data isn't persisted to the browser. I have a feeling something is funky in localStorage and sometimes the UI Reset isn't clearing everything out properly. I need to dedicate a chunk of time to this class of problem, but it's really hard to reproduce.


Killing router container disrupts IPSEC traffic

Rancher Versions:
Server: 1.5.8
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker Version:
OS and where are the hosts located? (cloud, bare metal, etc):
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node server, 2 hosts.
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Setup Rancher with 2 hosts.
Create an instance of the shengliang/apache-php container on each host
Run this command in one of the apache-php containers:while true; do curl -sSf http://10.42.c.d -o /dev/null; echo `date` $?; done

10.42.c.d is the IP of the other apache-php container.
On the host running the first apache-php container, do docker kill the IPSEC router container
Results:
HTTP traffic is disrupted. Killing the router should not disrupt IPSEC traffic.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


🐛 [firebase storage] PlatformException(object-not-found, No object exists at the desired reference.

Bug report
I uploaded videos on firebase storage, and try to retrieve it with flutter as below.
var videounitList = await FirebaseStorage.instance
          .ref()
          .child('videos/MC_100i_EVO/サイドウェッジプレート取外し手順.MOV')
          .getData(1024 * 1024 * 1000);

However, firebase returns following error.
Unhandled Exception: PlatformException(object-not-found, No object exists at the desired reference., {code: object-not-found, message: No object exists at the desired reference., nativeErrorMessage: Object videos/MC_100i_EVO/サイドウェッジプレート取外し手順.MOV does not exist., nativeErrorCode: -13010}, null)
Steps to reproduce
Upload a video named サイドウェッジプレート取外し手順.MOV to videos/MC_100i_EVO folder on firebase storage.
Call getData to get the file.
Expected behavior
Should be able to download the video.

Additional context
When I uploaded the same file to videos/サイドウェッジプレート取外し手順.MOV, it was working fine.
Does the folder name 'MC_100i_EVO' invade any firebase storage rule or something??
You can see the file exist here.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[!] Flutter (Channel stable, 3.10.6, on macOS 13.4.1 22F770820d darwin-arm64, locale ja-JP)
    ! Warning: `flutter` on your path resolves to /Users/tenna/デベロッパー/flutter/bin/flutter, which is not
      inside your current Flutter SDK checkout at /Users/tenna/デベロッパー/flutter. Consider adding
      /Users/tenna/デベロッパー/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/tenna/デベロッパー/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/tenna/デベロッパー/flutter. Consider adding
      /Users/tenna/デベロッパー/flutter/bin to the front of your path.
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.82.2)
[✓] Connected device (6 available)
    ! Error: tenna (2) is busy: Fetching debug symbols for tenna (2). Xcode will continue when tenna (2) is
      finished. (code -10)
[✓] Network resources

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.0.6
Flutter SDK 3.10.6
juki_manuals 1.0.0+1

dependencies:
- app_tracking_transparency 2.0.4 [flutter]
- cached_network_image 3.3.0 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- camera 0.10.5+4 [camera_android camera_avfoundation camera_platform_interface camera_web flutter flutter_plugin_android_lifecycle quiver]
- chewie 1.7.1 [cupertino_icons flutter provider video_player wakelock_plus]
- cloud_firestore 4.9.2 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- crypto 3.0.3 [typed_data]
- csv 5.0.2
- cupertino_icons 1.0.6
- fcm_config 3.5.2 [flutter firebase_core firebase_messaging flutter_local_notifications http path_provider]
- file_picker 5.5.0 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface ffi path win32]
- firebase_auth 4.10.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.16.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_core_platform_interface 4.8.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_messaging 14.6.8 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_storage 11.2.7 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]
- flutter_app_badger 1.5.0 [flutter]
- flutter_launcher_icons 0.13.1 [args checked_yaml cli_util image json_annotation path yaml]
- flutter_localization 0.1.14 [flutter flutter_web_plugins flutter_localizations plugin_platform_interface shared_preferences]
- flutter_localizations 0.0.0 [flutter intl characters clock collection js material_color_utilities meta path vector_math]
- font_awesome_flutter 10.5.0 [flutter]
- google_fonts 6.1.0 [flutter http path_provider crypto]
- google_sign_in 6.1.5 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- html 0.15.4 [csslib source_span]
- http 1.1.0 [async http_parser meta]
- image_picker 1.0.4 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- in_app_review 2.0.6 [flutter in_app_review_platform_interface]
- intl 0.18.0 [clock meta path]
- keyboard_actions 4.2.0 [flutter]
- loading_animation_widget 1.2.0+4 [flutter]
- package_info_plus 4.1.0 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface win32]
- page_transition 2.1.0 [flutter]
- path_provider 2.1.1 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- pdf 3.10.4 [archive barcode bidi crypto image meta path_parsing vector_math xml]
- permission_handler 11.0.0 [flutter meta permission_handler_android permission_handler_apple permission_handler_windows permission_handler_platform_interface]
- printing 5.11.0 [ffi flutter flutter_web_plugins http image js meta pdf plugin_platform_interface]
- share_plus 7.1.0 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- shared_preferences 2.2.1 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- sign_in_with_apple 5.0.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- universal_io 2.2.2 [collection meta typed_data]
- url_launcher 6.1.14 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- video_player 2.7.2 [flutter html video_player_android video_player_avfoundation video_player_platform_interface video_player_web]
- video_thumbnail 0.5.3 [flutter]

dev dependencies:
- flutter_lints 2.0.3 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection js matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]

transitive dependencies:
- _fe_analyzer_shared 61.0.0 [meta]
- _flutterfire_internals 1.3.6 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.13.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.4.3 [crypto path pointycastle]
- args 2.4.2
- async 2.11.0 [collection meta]
- barcode 2.2.4 [meta qr]
- bidi 2.0.10
- boolean_selector 2.1.1 [source_span string_scanner]
- cached_network_image_platform_interface 3.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.0 [cached_network_image_platform_interface flutter flutter_cache_manager]
- camera_android 0.10.8+12 [camera_platform_interface flutter flutter_plugin_android_lifecycle stream_transform]
- camera_avfoundation 0.9.13+5 [camera_platform_interface flutter stream_transform]
- camera_platform_interface 2.5.2 [cross_file flutter plugin_platform_interface stream_transform]
- camera_web 0.3.2+2 [camera_platform_interface flutter flutter_web_plugins stream_transform]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- cli_util 0.4.0 [meta path]
- clock 1.1.1
- cloud_firestore_platform_interface 5.16.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.7.1 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.17.1
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+5 [js meta]
- csslib 1.0.0 [source_span]
- dbus 0.7.8 [args ffi meta xml]
- fake_async 1.3.1 [clock collection]
- ffi 2.1.0
- file 6.1.4 [meta path]
- file_selector_linux 0.9.2+1 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3+3 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.1 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3+1 [cross_file file_selector_platform_interface flutter]
- firebase_auth_platform_interface 6.19.0 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.8.1 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core_web 2.8.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_messaging_platform_interface 4.5.7 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.5.7 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_storage_platform_interface 4.4.6 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.6.7 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_local_notifications 14.1.3+1 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_local_notifications_linux 4.0.0+1 [dbus ffi flutter flutter_local_notifications_platform_interface path xdg_directories]
- flutter_local_notifications_platform_interface 7.0.0+1 [flutter plugin_platform_interface]
- flutter_plugin_android_lifecycle 2.0.16 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- glob 2.1.2 [async collection file path string_scanner]
- google_identity_services_web 0.2.1+1 [js meta]
- google_sign_in_android 6.1.20 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.6.4 [flutter google_sign_in_platform_interface pigeon]
- google_sign_in_platform_interface 2.4.2 [flutter plugin_platform_interface quiver]
- google_sign_in_web 0.12.0+4 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http js]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 4.1.3 [archive meta xml]
- image_picker_android 0.8.8+1 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 3.0.1 [flutter flutter_web_plugins image_picker_platform_interface mime]
- image_picker_ios 0.8.8+2 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1+1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1+1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.9.1 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1+1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- in_app_review_platform_interface 2.0.4 [flutter url_launcher plugin_platform_interface platform]
- js 0.6.7 [meta]
- json_annotation 4.8.1 [meta]
- lints 2.1.1
- matcher 0.12.15 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.2.0
- meta 1.9.1
- mime 1.0.4
- nested 1.0.0 [flutter]
- octo_image 2.0.0 [flutter]
- package_config 2.1.0 [path]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path 1.8.3
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.2.0 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.1 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.1 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- permission_handler_android 11.0.5 [flutter permission_handler_platform_interface]
- permission_handler_apple 9.1.4 [flutter permission_handler_platform_interface]
- permission_handler_platform_interface 3.11.5 [flutter meta plugin_platform_interface]
- permission_handler_windows 0.1.3 [flutter permission_handler_platform_interface]
- petitparser 5.4.0 [meta]
- pigeon 11.0.1 [analyzer args collection meta path yaml]
- platform 3.1.2
- plugin_platform_interface 2.1.6 [meta]
- pointycastle 3.7.3 [collection convert js]
- provider 6.0.5 [collection flutter nested]
- pub_semver 2.1.4 [collection meta]
- qr 3.0.1 [meta]
- quiver 3.2.1 [matcher]
- rxdart 0.27.7
- share_plus_platform_interface 3.3.0 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences_android 2.2.1 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.3.4 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.1 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.1 [flutter plugin_platform_interface]
- shared_preferences_web 2.2.1 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.3.1 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- sky_engine 0.0.99
- source_span 1.9.1 [collection path term_glyph]
- sqflite 2.3.0 [flutter sqflite_common path]
- sqflite_common 2.5.0 [synchronized path meta]
- stack_trace 1.11.0 [path]
- stream_channel 2.1.1 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- synchronized 3.1.0
- term_glyph 1.2.1
- test_api 0.5.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.9.2 [path]
- typed_data 1.3.2 [collection]
- url_launcher_android 6.1.0 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.5 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.6 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.7 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.5 [flutter plugin_platform_interface]
- url_launcher_web 2.0.19 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.8 [flutter url_launcher_platform_interface]
- uuid 3.0.7 [crypto]
- vector_math 2.1.4
- video_player_android 2.4.10 [flutter video_player_platform_interface]
- video_player_avfoundation 2.4.11 [flutter video_player_platform_interface]
- video_player_platform_interface 6.2.1 [flutter plugin_platform_interface]
- video_player_web 2.0.17 [flutter flutter_web_plugins video_player_platform_interface]
- wakelock_plus 1.1.1 [flutter flutter_web_plugins meta wakelock_plus_platform_interface win32 dbus package_info_plus js]
- wakelock_plus_platform_interface 1.1.0 [flutter plugin_platform_interface meta]
- watcher 1.1.0 [async path]
- win32 5.0.9 [ffi]
- xdg_directories 1.0.3 [meta path]
- xml 6.3.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]

Apparently, these 2 names are different.
サイドウェッジプレート取外し手順.MOV from the file name on storage.
サイドウェッジプレート取外し手順.MOV from the file name on my local file.
These are the same when I paste to here, but when I paste to .dart file, it is not the same.


Issue 6994.  PDF version 1.3, with nested xref, signals 'bad xref entry'

The PDF in question contains confidential information...I am still trying to get a non-confidential version as a test case.
Until then, here's what I found.  File contains 2 xrefs.  The master xref (at EOF) contains:
xref
0 1
0000000000 65535 f
3 1
0000691433 00000 n          == <</Contents[2 0 R]/MediaBox[0 0 596 842]/Parent 4 0 R/Resources<</ProcSet[/PDF/ImageC/ImageB/ImageI]/XObject<</Im1 1 0 R>>>>/Rotate 90/Type/Page>>.endobj
5 3
0000691595 00000 n          == obj 5 <</Metadata 7 0 R/Pages 4 0 R/Type/Catalog>>.endobj
0000691655 00000 n          == obj 6 <</Author()/CreationDate()/CreationDate--Text()/Creator()/ModDate(D:20160209110716+05'30')/Producer()/Subject()/Title()>>.endobj
0000691792 00000 n          == obj 7 metadata stream,
trailer
The nested xref (in middle of file) contains:
xref
1 7
0000000000 65535 f
0000000009 00000 n     // start of object 1
0000690726 00000 n     // start of object 2
0000690823 00000 n     // start of object 3 <<./Type /Page./MediaBox [0 0 596 842]./Parent 4 0 R ./Rotate 0 /Resources <<./ProcSet [/PDF /ImageC /ImageB /ImageI]./XObject <<./Im1 1 0 R. >>. >>./Contents [ 2 0 R.].>>.endobj
0000691010 00000 n     // start of object 4
0000691068 00000 n     // start of object 5 <<./Type /Catalog./Pages 4 0 R  .>>.endobj.
0000691119 00000 n     // start of object 6 << /Creator ()./CreationDate ()./Author ()./Producer ()./Title ()./Subject ().>>
THe problem was that the dict created by merging these 2 looked like this (notice 2 'obj 3''s).
index 0: offset=0
index 1: offset=9           (obj 1, from 1st xref) OK
index 2: offset=691433 (obj 3, from 2nd xref) OK
index 3: offset=690823 (obj 3, from 1st xref) -- wrong!
index 4: offset=691595 (obj 5, from 2nd xref) OK
index 5: offset=691655 (obj 6, from 2nd xref) OK
index 6: offset=691792 (obj 7, from 2nd xref) OK
I traced the problem back to XRef_readXRefTable in core/obj.js, and decided that the safest fix was to treat the starting object number (tableState.firstEntryNum) of the xref subsection (1 7, above) as invalid (eg, treat it as 0 7).

@xrbd Any updates on getting the test file?

Closing as superseded by #7233, which is a more complete fix and has tests.


Invalid meta driver: $'postgres [interface.go:500]

What happened:
I deploy juicefs csi on k8s and use S3 (Minio) as object storage and  cockroachdb as metadata engine.
And I create pvc and pod that pvc created successfully but pod cannnot attach volume.
describe pod
MountVolume.SetUp failed for volume "juicefs-pv" : rpc error: code = Internal desc = Could not mount juicefs: juicefs format error: 2024/06/27 08:14:29.156229 juicefs[97] <INFO>: Meta address: $'postgres://jfs:****@urt-jfs-db1-lb1.xxxxxx.group:26257/jfs' [interface.go:497] 2024/06/27 08:14:29.156485 juicefs[97] <FATAL>: Invalid meta driver: $'postgres [interface.go:500] : exit status 1

logs juicefs-csi-node
I0627 05:15:17.460443       7 node.go:106] NodePublishVolume: volume_id is juicefs-pv
I0627 05:15:17.460475       7 node.go:117] NodePublishVolume: volume_capability is mount:<fs_type:"juicefs" > access_mode:<mode:MULTI_NODE_MULTI_WRITER >
I0627 05:15:17.460528       7 node.go:123] NodePublishVolume: creating dir /var/lib/kubelet/pods/912e9acc-a963-4d08-b65e-5735641b9a50/volumes/kubernetes.io~csi/juicefs-pv/mount
I0627 05:15:17.460735       7 node.go:138] NodePublishVolume: volume context: map[csi.storage.k8s.io/ephemeral:false csi.storage.k8s.io/pod.name:app-test-5cd58d95bc-vsj7n csi.storage.k8s.io/pod.namespace:infra csi.storage.k8s.io/pod.uid:912e9acc-a963-4d08-b65e-5735641b9a50 csi.storage.k8s.io/serviceAccount.name:default]
I0627 05:15:17.460768       7 node.go:148] NodePublishVolume: mounting juicefs with secret [metaurl name secret-key storage access-key bucket envs format-options], options []
I0627 05:15:17.461103       7 juicefs.go:1036] ceFormat cmd: [/usr/local/bin/juicefs format --storage=s3 --bucket=https://k8s-test-new.s3-jfs.xxxx.group --access-key=k8s-test-new --secret-key=${secretkey} ${metaurl} myjfs --trash-days=1 --block-size=4096]
I0627 05:15:17.575567       7 juicefs.go:1056] Format output is 2024/06/27 08:15:17.561114 juicefs[125] <INFO>: Meta address: $'postgres://jfs:****@urt-jfs-db1-lb1.xxxx.group:26257/jfs' [interface.go:497]
2024/06/27 08:15:17.561475 juicefs[125] <FATAL>: Invalid meta driver: $'postgres [interface.go:500]
I0627 05:15:17.575621       7 juicefs.go:1059] Format error: exit status 1
E0627 05:15:17.575682       7 driver.go:102] GRPC error: rpc error: code = Internal desc = Could not mount juicefs: juicefs format error: 2024/06/27 08:15:17.561114 juicefs[125] <INFO>: Meta address: $'postgres://jfs:****@urt-jfs-db1-lb1.xxxxx.group:26257/jfs' [interface.go:497]
2024/06/27 08:15:17.561475 juicefs[125] <FATAL>: Invalid meta driver: $'postgres [interface.go:500]
: exit status 1

Linux version in  juicefs-csi-node : Oracle Linux Server 8.7   and kernel: 5.4.17-2136.315.5.el8uek.x86_64
Install JuiceFS helm (this repo) and set in values.yaml
mountMode: process
and changes
node:
  enabled: true
  debug: false
  hostNetwork: true

this my StrorageClass
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    meta.helm.sh/release-name: jucefs
    meta.helm.sh/release-namespace: infra
  creationTimestamp: "2024-06-27T05:50:47Z"
  labels:
    app.kubernetes.io/instance: jucefs
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: juicefs-csi-driver
    app.kubernetes.io/version: 0.24.1
    helm.sh/chart: juicefs-csi-driver-0.20.3
  name: juicefs-sc
  resourceVersion: "2672155149"
  uid: f149a442-3db1-416d-9450-a7728a9f8def
mountOptions:
- writeback
- upload-delay=1m
parameters:
  csi.storage.k8s.io/controller-expand-secret-name: juicefs-sc-secret
  csi.storage.k8s.io/controller-expand-secret-namespace: infra
  csi.storage.k8s.io/node-publish-secret-name: juicefs-sc-secret
  csi.storage.k8s.io/node-publish-secret-namespace: infra
  csi.storage.k8s.io/provisioner-secret-name: juicefs-sc-secret
  csi.storage.k8s.io/provisioner-secret-namespace: infra
  juicefs/mount-annotations: '{"prometheus.io/port":"9567","prometheus.io/scrape":"true"}'
  juicefs/mount-cpu-limit: 4000m
  juicefs/mount-cpu-request: 100m
  juicefs/mount-memory-limit: 5Gi
  juicefs/mount-memory-request: 100Mi
  pathPattern: ${.PVC.annotations.csi.juicefs.com/subdir}
provisioner: csi.juicefs.com
reclaimPolicy: Retain
volumeBindingMode: Immediate

this my secrets
apiVersion: v1
kind: Secret
metadata:
  name: juicefs-sc-secret
  namespace: infra
type: Opaque
stringData:
  name: myjfs
  access-key: k8s-test-new
  secret-key: xxxxxxxxxxxxxxxxxxxxxxxxxxx
  metaurl: postgres://jfs:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@urt-jfs-db1-lb1.xxxxxxxxxxxx.group:26257/jfs
  storage: s3
  bucket: https://k8s-test-new.s3-jfs.xxxxxxxx.group
  format-options: trash-days=1,block-size=4096

this my test  app:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: juicefs-pv
  labels:
    juicefs-name: ten-pb-fs
spec:
  # For now, JuiceFS CSI Driver doesn't support setting storage capacity for static PV. Fill in any valid string is fine.
  capacity:
    storage: 10Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  csi:
    # A CSIDriver named csi.juicefs.com is created during installation
    driver: csi.juicefs.com
    # volumeHandle needs to be unique within the cluster, simply using the PV name is recommended
    volumeHandle: juicefs-pv
    fsType: juicefs
    # Reference the volume credentials (Secret) created in previous step
    # If you need to use different credentials, or even use different JuiceFS volumes, you'll need to create different volume credentials
    nodePublishSecretRef:
      name: juicefs-sc-secret
      namespace: infra
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: juicefs-pvc
  namespace: infra
  annotations:
    csi.juicefs.com/additional-mount-options: "writeback,upload-delay=1m" # Add JuiceFS settings if necessary.
    juicefs/mount-cpu-limit: 4000m
    juicefs/mount-cpu-request: 100m
    juicefs/mount-memory-limit: 5Gi
    juicefs/mount-memory-request: 100Mi
spec:
  accessModes:
    - ReadWriteMany
  volumeMode: Filesystem
  # Must use an empty string as storageClassName
  # Meaning that this PV will not use any StorageClass, instead will use the PV specified by selector
  storageClassName: ""
  # For now, JuiceFS CSI Driver doesn't support setting storage capacity for static PV. Fill in any valid string that's lower than the PV capacity.
  resources:
    requests:
      storage: 10Gi
  selector:
    matchLabels:
      juicefs-name: ten-pb-fs
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: app-test
  name: app-test
  namespace: infra
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app-test
  template:
    metadata:
      labels:
        app: app-test
      annotations:
        app: app-test
    spec:
      containers:
        - args:
          - -c
          - while true; do echo $(date -u) >> /data/out.txt; sleep 5; done
          command:
          - /bin/sh
          image: busybox
          name: app
          volumeMounts:
          - mountPath: /data
            name: data
          resources:
            limits:
              cpu: 400m
              memory: 1Gi
            requests:
              cpu: 100m
              memory: 100Mi
      volumes:
      - name: data
        persistentVolumeClaim:
          claimName: juicefs-pvc

But if I change in values.yaml from process on mountpod
mountMode: mountpod
then everything is ok.  PV and PVC are being created and mounted pods
can you help solve this case? Why mode "mountMode: process" don't mount.

@KKulishov We recently fixed a bug https://github.com/juicedata/juicefs/pull/4731/ with postgres not sure if it's related.
You can download the juicefs v1.2 binary and try it with the same metaurl format.
The postgresql format doc: https://juicefs.com/docs/community/databases_for_metadata/#postgresql

@zhijian-pro thanks for the advice
But version

I use this helm
image
image:
  repository: juicedata/juicefs-csi-driver
  tag: "v0.24.1"
  pullPolicy: ""

dashboardImage:
  repository: juicedata/csi-dashboard
  tag: "v0.24.1"
  pullPolicy: ""

sidecars:
  livenessProbeImage:
    repository: registry.k8s.io/sig-storage/livenessprobe
    tag: "v2.12.0"
    pullPolicy: ""
  nodeDriverRegistrarImage:
    repository: registry.k8s.io/sig-storage/csi-node-driver-registrar
    tag: "v2.9.0"
    pullPolicy: ""
  csiProvisionerImage:
    repository: registry.k8s.io/sig-storage/csi-provisioner
    tag: "v2.2.2"
    pullPolicy: ""
  csiResizerImage:
    repository: registry.k8s.io/sig-storage/csi-resizer
    tag: "v1.9.0"
    pullPolicy: ""

Can you suggest which image should be used for
mountMode: process

I repeat , if I set the mode
mountMode: mountpod

everything is working . PV and PVS are created and mounted in pods.
When user (mountMode: mountpod)
image use  pods juicefs-urt-k8s-test-w8-pvc-b4a40f88-a9e2-4573-9233-b85434fc8a6d-wwjuaf
juicedata/mount:ce-v1.1.2

version jucefsversion

The problem only occurs when I use
mountMode: process

there may be a problem in the operating logic in https://github.com/juicedata/charts/blob/main/charts/juicefs-csi-driver/templates/daemonset.yaml

Can you desensitize the meta-url and post it, I need to determine if his formatting is correct.

@zhijian-pro  Sorry, I can't post url. It my corp network. I can share logs only
but I changed cocroachdb on redis
use
mountMode: process

and with redis everything worked
rather the problem is on the side controller

@zhijian-pro @zxh326 I suppose it's been escaped by this function?

Does your pg password contain the $?


Updated to 2021.3 using a workaround resolve #18

I tried to update to 1.3.2 and then I used a workaround describe in https://github.com/Kotlin/kotlinx.serialization/issues/993#issuecomment-984742051.
I'm not sure how to verify that it work, I just ran gradlew buildPlugin and it succeeded.

There are a bunch of other issues I want to fix before releasing it for 2021.3, I will try fixing them when I get to it

Ok, I tested the plugin, what I did is not working anyway, I'm don't understand why
Java.lang.NoClassDefFoundError: io/ktor/client/HttpClientJvmKt
	at me.schlaubi.intellij_gradle_version_checker.GradleVersionKt.<clinit>(GradleVersion.kt:50)
	at me.schlaubi.intellij_gradle_version_checker.gradle_inspector.GradleVersionResolvingActivity$runActivity$1.invokeSuspend(GradleVersionResolvingActivity.kt:39)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

java.lang.NoClassDefFoundError: io/sentry/SentryOptions
	at me.schlaubi.intellij_gradle_version_checker.error_handling.InitializeSentryActivity.runActivity(InitializeSentryActivity.kt)


Make the behaviour clear when providing a Service URI

JustSaying allows you to provide a SerivceURI through the fluent API and DefaultAwsClientFactory which is then passed down to the underlying AWS SNS / SQS clients.
This is great for testing as it allows you to use libraries like LocalStack, however, there is a subtle behaviour change in that any region provided will be ignored by the AWS clients if a ServiceURI is provided and visa versa (see AWS client config).
To avoid consumers of JustSaying falling into this trap, we should look to surface this information in the public API somewhere so that it is clear what the behaviour is.

This was a really tricky and time consuming thing to be trapped by. Would be nice if it is better documented (or a sample has a comment to highlight this)


Added support for Swift 4.2

Hey @roberthein could you approve this pr?

There is a Swift 4.2 brach now. 👌
pod 'TinyConstraints', :git => 'https://github.com/roberthein/TinyConstraints.git', :branch => 'release/Swift-4.2'

@roberthein thank you so much! One question, do you plan to merge it in master branch?

Oh yeah sure, do you use Carthage @alexanderkhitev?

@roberthein no, I use pods


Improved the tests

The test cases had minor problems in coding style.
Improved them by going through link
This is the pr for #750 .

thanks a lot for working on this @vipulchhabra99!  Can you please rebase branch update-actionsnpm-reference. I added a fix for the actions/npm errors observed there.

ok sure @ivotron.

@ivotron can you please check this why its still failing?

@vipulchhabra99, as pointed out in shellcheck's documentation before the fix you introduced to the test scripts, we were basically ignoring all ! cmd tests. So it is likely that what we observe in travis is an actual error (i.e. an expectation not being met).

Oh, I misunderstood it oppositely, Sorry for the inconvenience caused I am updating it again.

thanks a lot @vipulchhabra99 . I added your commits to PR #754, as there were other couple of things that needed to be fixed.


docs: remove unnecessary TRG 2.02 - repo permissions

Description
This PR removes TRG 2.02 - Repo permissions without replacement. The description is contained in multiple other sources also available on our website. Examples are "OSS - Getting started", "OSS - How to contribute" and the EF Project handbook mentioned at several places
Closes eclipse-tractusx/sig-infra#364

Maybe instead of deleting it completely, replace it by a disclaimer that it was superseded by / merged into ...
Main reason is to prevent dead links as the TRGs have been linked to very often.

I added a redirect from the deleted TRG to the intro page: cfd7e9f
So any link that we had in our release check issues for example will at least not end up in a 404.
Is this a valid solution? I would rather delete the content to properly clean up instead of deprecating them


Post upgrade PR: Pipfile.lock & pre-commit

Codecov Report

Merging #797 (edffa82) into main (5b7bb4c) will decrease coverage by 0.04%.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #797      +/-   ##
==========================================
- Coverage   91.90%   91.86%   -0.04%
==========================================
  Files         155      155
  Lines        6494     6494
==========================================
- Hits         5968     5966       -2
- Misses        526      528       +2

Flag
Coverage Δ

unittests
91.86% <ø> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes


Adjust the Fallback logic for obtaining the hashes from private indexes

The else Fallback here is not working right, for example if my source url is: url = "https://download.pytorch.org/whl/cu117" and the page contains url's like: /whl/cu117/torch-2.0.1%2Bcu117-cp310-cp310-linux_x86_64.whl So the url that gets generated is: https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp310-cp310-linux_x86_64.whl which is wrong because it repeats /whl/cu117/
The issue
Fixes #5864
Fixes #5860
Maybe Fixes #5848
The fix
Use urllib.parse urljoin which will intelligently handle this case:
Downloading file torch-2.0.1+cu117-cp310-cp310-linux_x86_64.whl to obtain
hash...
Downloading file torch-2.0.1+cu117-cp310-cp310-win_amd64.whl to obtain hash...
Downloading file torch-2.0.1+cu117-cp311-cp311-linux_x86_64.whl to obtain
hash...
Downloading file torch-2.0.1+cu117-cp311-cp311-win_amd64.whl to obtain hash...
Downloading file torch-2.0.1+cu117-cp38-cp38-linux_x86_64.whl to obtain hash...
Downloading file torch-2.0.1+cu117-cp38-cp38-win_amd64.whl to obtain hash...
Downloading file torch-2.0.1+cu117-cp39-cp39-linux_x86_64.whl to obtain hash...
Downloading file torch-2.0.1+cu117-cp39-cp39-win_amd64.whl to obtain hash...

Install:
Writing supplied requirement line to temporary file: 'torch==2.0.1+cu117 --hash=sha256:0a56cf5d99f1c7fa29c328a6737c5e5108fa71d8f021c074f4ff0de9e8969302
--hash=sha256:245d04e1541350dba11c7b76e343ca0071bbcb10f956a09b6bede3d68db9e759 --hash=sha256:60b21e8db98f7365758a5c218f5dc533d84f046ed0876b4540ba5ba7ef6797d4
--hash=sha256:a77ba4f4b13c8b6c2c863b84a98dde2ddf1feaad5f25700d41cf3236e11d2ee8 --hash=sha256:bb54b705185bea820e6ec6485a25761bc03f689e1a09a37d814d6ea8e276b5bd
--hash=sha256:bec39e6fe7232f399c6a5cda5785517fec759fc0852e0c31d71a39f7bf6b23b3 --hash=sha256:deed82674691238ff9471fb7dd13a6eafc0c394cb6cdb249b483b4855c00276f
--hash=sha256:e06deb28938e7468bdd79ad5a4cfda36e95113507a9144a367039b35ac73986c'
Install Phase: Standard Requirements
Preparing Installation of 'torch==2.0.1+cu117 --hash=sha256:0a56cf5d99f1c7fa29c328a6737c5e5108fa71d8f021c074f4ff0de9e8969302 --hash=sha256:245d04e1541350dba11c7b76e343ca0071bbcb10f956a09b6bede3d68db9e759
--hash=sha256:60b21e8db98f7365758a5c218f5dc533d84f046ed0876b4540ba5ba7ef6797d4 --hash=sha256:a77ba4f4b13c8b6c2c863b84a98dde2ddf1feaad5f25700d41cf3236e11d2ee8
--hash=sha256:bb54b705185bea820e6ec6485a25761bc03f689e1a09a37d814d6ea8e276b5bd --hash=sha256:bec39e6fe7232f399c6a5cda5785517fec759fc0852e0c31d71a39f7bf6b23b3
--hash=sha256:deed82674691238ff9471fb7dd13a6eafc0c394cb6cdb249b483b4855c00276f --hash=sha256:e06deb28938e7468bdd79ad5a4cfda36e95113507a9144a367039b35ac73986c'
$ C:/c/Users/matte/.virtualenvs/pytorch_new-7A-x71qg/Scripts/python.exe 'C:\Users\matte\Projects\pipenv\pipenv\patched\pip\__pip-runner__.py' install -i https://download.pytorch.org/whl/cu117 --no-input
--upgrade --no-deps -r 'c:\users\matte\appdata\local\temp\pipenv-6a7209oi-requirements\pipenv-8x7x43h8-hashed-reqs.txt'
Using source directory: 'C:\\c\\Users\\matte\\.virtualenvs\\pytorch_new-7A-x71qg\\src'
Looking in indexes: https://download.pytorch.org/whl/cu117

Collecting torch==2.0.1+cu117 (from -r c:\users\matte\appdata\local\temp\pipenv-6a7209oi-requirements\pipenv-8x7x43h8-hashed-reqs.txt (line 1))

  Using cached https://download.pytorch.org/whl/cu117/torch-2.0.1%2Bcu117-cp311-cp311-win_amd64.whl (2343.6 MB)

Installing collected packages: torch

Successfully installed torch-2.0.1+cu117

I've also added better error handling for this case to avoid capturing a hash if the response is not 200.   When I undo the fix, that looks like:
[  ==] Locking...Downloading file torch-2.0.1+cu117-cp310-cp310-linux_x86_64.whl to obtain hash...
[   =] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp310-cp310-linux_x86_64.whl
Downloading file torch-2.0.1+cu117-cp310-cp310-win_amd64.whl to obtain hash...
[  ==] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp310-cp310-win_amd64.whl
Downloading file torch-2.0.1+cu117-cp311-cp311-linux_x86_64.whl to obtain hash...
[==  ] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp311-cp311-linux_x86_64.whl
Downloading file torch-2.0.1+cu117-cp311-cp311-win_amd64.whl to obtain hash...
[=   ] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp311-cp311-win_amd64.whl
Downloading file torch-2.0.1+cu117-cp38-cp38-linux_x86_64.whl to obtain hash...
[ ===] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp38-cp38-linux_x86_64.whl
Downloading file torch-2.0.1+cu117-cp38-cp38-win_amd64.whl to obtain hash...
[   =] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp38-cp38-win_amd64.whl
Downloading file torch-2.0.1+cu117-cp39-cp39-linux_x86_64.whl to obtain hash...
[  ==] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp39-cp39-linux_x86_64.whl
Downloading file torch-2.0.1+cu117-cp39-cp39-win_amd64.whl to obtain hash...
[====] Locking...HTTP error 403 while getting https://download.pytorch.org/whl/cu117/whl/cu117/torch-2.0.1%2Bcu117-cp39-cp39-win_amd64.whl
[==  ] Locking...Downloading file torch-2.0.1+cu117-cp311-cp311-win_amd64.whl to obtain hash...

Latest Update is I got caching to work -- so if you download the expensive pytorch wheels in one lock phase, the subsequent lock phase is much faster!  🎉

The checklist

[X] Associated issue
[X] A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

Nice job with the caching improvement as well!

so...what's the final solution? I'm using the latest version of pipenv. when I run
pipenv install torch==2.0.1+cu117 --index https://download.pytorch.org/whl/cu117

It's still keep locking and downloading something I don't know...
Installing torch==2.0.1+cu117...
Resolving torch==2.0.1+cu117...
Added torch to Pipfile's [packages] ...
Installation Succeeded
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
[====] Locking...

@BetterWorld-Liuser The first time you lock its going to download 16 GB of wheel files from the torch index.

@matteius so there is no way to install just like pip install ? like just download the target whl...

@BetterWorld-Liuser Once you have a valid lock file, which needs the hashes of all matching wheel files for that version, which is why it has to download approximately 16 GB, then the subsequent install just downloads the one matching wheel for your system, which should be cached by the prior lock.

@matteius OK, I understand, thanks!