Does this need to be in the ES spec?

I was always under the impression that hosts could create subclasses of AMR without needing to get TC39 consensus. That was certainly the plan for the web, e.g. for WebAssembly.
Maybe it'd be better to just work on a small one-line patch to make that explicitly allowed? Then Node could define its own "Node.js module record" which is basically Dynamic Module Record but without the awkward indirection to a host hook; you'd just inline the relevant logic instead.
Apologies if I'm misunderstanding the proposal in some way.

I was initially hoping to make a short PR, but one of the key things that isn’t currently possible is the late definition of export bindings while retaining execution order, and there’s no way to do this in v8 right now in Node.js, and I don’t see another way of going about that.
Certainly open to suggestions too, but it does seem generally important to me.

I don't quite understand. The entire contents of https://guybedford.github.io/proposal-dynamic-modules/ is a new module record type.
If we work under my assumption that you don't need to change Ecma-262 to introduce new module record types, then, what spec change would be required?
It sounds like what you're really after is for V8 to implement a new module record type, or to have a more customizable way of introducing new module record types through the V8 API. But that's not really related to the spec, and doesn't require changing Ecma-262.

@domenic the interaction between the dynamic modules and the rest of the ES spec hits a few boundaries that are quite grey in terms of whether they are valid if implementing this as a non 262 spec.

Creating let-style module bindings lazily when resolveExport is called to a dynamic module lexical scope that then link into the module instantiation process.
Late defining exported bindings on a module during execution, including adding additional named exports to namespace exotic objects after their initial creation.

There may well be other concerns implementors would have in terms of spec validity here as well that would only be discovered during that process.
Neither the above, nor the unknown implementor concerns are obvious that they are possible if approaching this as an "addon" to the JS spec.
In addition, ECMA 262 should be serving implementations in terms of supporting the engine semantics they need. Interfacing between source text modules and non source text modules does seem a pretty fundamental feature. And this is quite an important engine semantic to be clear on what is and isn't possible.

I've added an FAQ section on this in https://github.com/guybedford/proposal-dynamic-modules#could-dynamic-module-records-not-be-defined-outside-of-ecma-262.

Another thing I've just added here - there is some book-keeping required to ensure module namespace objects of star export modules include the dynamic module export names, which involves a minor spec change.

OK. But those are solely concerns of this new type of module record, which should be worked out by whoever implements that module record. They are not part of the base language.
Your point about working out implementer concerns further suggests to me this is a good discussion to have with implementers, but not for the whole committee to advance through the proposal process and make a part of the language.
At this point my understanding of this proposal leads me to oppose it as being part of the language spec, as opposed to e.g. the Node.js documentation or a V8 design doc. (I would be fine with a spec PR to add a single parameter to GetExportedNames though, as that seems to be the only impact on the existing spec infrastructure.)

@domenic that could well be a good approach, and I'd be happy to go in that direction if it is the best way forward here.
That said, it doesn't seem an obvious assessment to me... the integration is quite detailed and to repeat myself - it doesn't seem clear that the spec would support these things. We can't just have an external spec go and change lexical bindings and fields of internal objects. It's like a private interface from a spec perspective surely?
I think the TC39 process would help to inform this judgement.

Whether the spec supports certain operations or not isn't terribly relevant to your work though.* What's relevant is whether Node.js can implement something like this (i.e. with the same observable effects) in its host platforms (V8, ChakraCore). That's a great conversation to have with those implementers, but not one that impacts the language specification.

For the record, it does: you've written them down in spec language.

I think the only reason for this to be in 262 is if we want to generalize this and expose it to user-land as a reflection API, which is something that we want to do at some point. I have mentioned some of that in the Realms presentation, we definitely need folks exploring this.
If it is a reflection API for dynamic modules, node can use it, wasm, and others can use it as well. It seems relevant from that point of view.

Sure. But that would be a separate proposal, which would have its own gauntlet to pass through (e.g. it's in conflict with the current plans of the WebAssembly Community Group).

This now lives as a Node spec at https://github.com/nodejs/dynamic-modules.


Module build failed: TypeError: unknown: Duplicate declaration "_JSXStyle"

Looks like we no longer need to add the plugin to the babel configuration?
I noticed when this is added to the babel configuration
{
  "plugins": [
    "styled-jsx/babel"
  ]
}

we get the following error:
.
Perhaps we should update the docs to reflect this change?
Example repo demonstrating the issue.

Never been the case, Next.js comes with styled-jsx already

There is no need to use Babel and install style-jsx in next


Class 02

Feature Checklist
[x] Function that returns nth value of fibonacci sequence
[x] Function that returns nth value of lucas sequence
[  ] Function that returns nth value of sum_series sequence
[x] Testing for fibionacci sequence
[x] Testing for lucas sequence
[  ] Testing for sum_series sequence


Align bridge with kubetron

This PR addresses issue #33 . But, actually did not align with kubetron implementation....
(1) I prefer the channel approach to get the pod over polling the k8s file - seems cleaner
(2) I prefer a programmatic approach for managing the interfaces over a scripted approach

 [epic-network-resource] Learn about device plugins and Kubetron


ubuntu 15.04, error on display the menu

I run the pre-build  released  0.19.0 version malmo on ubuntu 15.04.
The released file I download is "Malmo-0.19.0-Linux-Ubuntu-14.04-64bit_withBoost.zip"
The result is as below:

Any suggestion on how can I find the root cause or how can I solve this?

Hi @redliu312, sorry you are having problems. Is this still an issue?
A few questions:
Have you installed any other Minecraft mods, texture packs etc?
What version of java are you using?
How much memory do you have?
Are you running on a 64bit machine or 32bit?
What do you see if you type
glxinfo | grep version

into a terminal?
(If you don't have glxinfo, try typing sudo apt-get install mesa-utils first.)

@redliu312 I'm closing this because we haven't heard anything for a while, but if it's still an issue, please go ahead and re-open.

Hi @DaveyBiggers ,
Apologies for the delay.
This ubuntu run on a virtualbox as a guest machine.
I made some tests and I confirmed that this issue is caused by the virtualbox 3D acceleration option
which will cause the openGL fail. I  uncheck this option and the Malmo work greatly.


HEAD failed with exit status 128

I'm getting this error on a lot of parsers.
In this particular example, I have this for yaml in the parsers.toml file:
yaml = { ref="7b03feefd36b5f155465ca736c6304aca983b267", from = "https://github.com/tree-sitter-grammars/tree-sitter-yaml"}

Command line output:
Error:   × yaml: Could not clone to /Users/username/Development/tree-sitter/tmp/yaml
  ╰─▶ [tmp/yaml] git rev-parse HEAD failed with exit status 128.
      StdOut:
      HEAD
      StdErr:
      fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
      Use '--' to separate paths from revisions, like this:
      'git <command> [<revision>...] -- [<file>...]'

Many parsers work correctly, but there's a handful that I can't get to run as they all fail with that status 128 error.

Hi, sorry for the late reply, I was on vacations.
I will take a look asap, but it looks like the cloning part went wrong. Did you try again ever since? In a clean dir? Or maybe just delete the --build-dir (normally tmp under cwd)?

Also, could you please give me your config file so I could replicate + see which parsers are not working?

@Shpigford I tested it locally and it worked.
I am now more convinced it was a problem in cloning that put the repo in a weird state.
Could you please confirm ? Or at least send me the full parsers.toml file, give me more information on your machine, the # of CPUs (because tsdl downloads in parallel), etc. any info on how to reproduce is appreciated.

What you can do is either pass the --fresh arg, to force a delete of the out dir … may not be suitable for all cases, but it's there.

@Shpigford are you still facing problems? Can I close this issue?

This usually happens when adding a parser with non-existent ref to parsers.toml, building, then correcting ref and/or from and building again. The first build seems to create a tempdir for the parser repo, which is empty. The second build maybe skips cloning, because the tempdir already exists?
Using fresh = true or --fresh or manually deleting the tempdir work around the problem.
Suggestions for a fix:

check if tempdir for parser is empty before the clone and delete it if true
improve error message, because Could not clone to ... is misleading, but maybe this is obsoleted by the first point?

Thanks @bugabinga for the feedback.
I made a https://github.com/stackmystack/tsdl/pull/12 to specifically address this issue.
I hope it covers it. I would have preferred not to hope, but to actually cover and fix it, but I am not able to reporduce manually and add it to the test case.
If you got a specific set of instructions I can follow, it would be great.
I will let you know when I make a new release (which should be today).

I release v1.3.0 which contains these fixes. Please let me know if it addresses the issues you raised here.

Issue is fixed for me. Good job!


Code fixes for return, break statements

Hi Please review the updates. The comment is added in each commits.

Being picky, but we expect commits to be GPG-signed :)

The return statements eliminated might be needed for testing. I know that the one in Console is, and cannot be simply removed.

No response from OP for 4 months. Don't get any errors locally or on Travis. Closing.


Overwrite maxSizeOfInstructions in maxp with computed value.

In issue #7507 the value is less than the actuall max size
of the glyph instructions causing OTS to fail the font.
Fixes #7507

/botio test

Forgot the pdf file :(
/botio test

/botio test

/botio makeref


Update profiles

Learn Build status updates of commit 56c4228:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

rd/media/profiles/rotem-rozmarin.jpg
:white_check_mark:Succeeded
View

rd/media/profiles/stale-hansen.jpg
:white_check_mark:Succeeded
View

rd/stale-hansen.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Add bevy_lint

Per https://github.com/bevyengine/bevy/pull/2582

Reserved. Sorry for the massive delay!


Merge master to live

No changes beyond just merging master into live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/authoring-cards/card-schema.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/host-config.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/renderer-status.md
:white_check_mark:Succeeded

AdaptiveCards/resources/partners.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/net-wpf/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/uwp/actions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/authoring-cards/card-schema.md
:white_check_mark:Succeeded

AdaptiveCards/getting-started/windows.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/host-config.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/renderer-status.md
:white_check_mark:Succeeded

AdaptiveCards/resources/partners.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/net-wpf/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/uwp/actions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/authoring-cards/card-schema.md
:white_check_mark:Succeeded

AdaptiveCards/getting-started/windows.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/host-config.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/renderer-status.md
:white_check_mark:Succeeded

AdaptiveCards/resources/partners.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/net-wpf/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/uwp/actions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/authoring-cards/card-schema.md
:white_check_mark:Succeeded

AdaptiveCards/getting-started/windows.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/host-config.md
:white_check_mark:Succeeded

AdaptiveCards/rendering-cards/renderer-status.md
:white_check_mark:Succeeded

AdaptiveCards/resources/partners.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/net-wpf/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/uwp/actions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Overnight events listed first

Can there be an option where overnight events show at the top of the list on the day that it ends or at least in chronological order? If an event ends at 0730 the next day, it should show on the ending day between an event that starts at 0630 and another that starts at 0830.

Are you implying that the current order is not correct or is that a new feature?


ludwig fails to work with uppercase extension names such as CSV and JSON

On my Mac I'm trying to use a file with a .CSV extension such as input.CSV. Unfortunately, ludwig fails to load such files in preprocessing since string.replace in python is case sensitive.
Steps to reproduce (provided you already have a trained model):

Create your prediction data csv file and name it prediction.CSV
Execute command ludwig predict --data_csv prediction.CSV --model_path results/experiment_run_0/model

Expected behavior:
ludwig can read the file
Actual:
An exception is thrown:
| |_  _ __| |_ __ _(_)__ _
| | || / _` \ V  V / / _` |
|_|\_,_\__,_|\_/\_/|_\__, |
                     |___/
ludwig v0.1.0 - Predict

Dataset type: generic
Dataset path: prediction.CSV
Model path: results/experiment_run_0/model
Output path: results_0

Found hdf5 with the same filename of the csv, using it instead
Loading metadata from: results/experiment_run_0/model/train_set_metadata.json
Loading data from: prediction.CSV
Traceback (most recent call last):
  File "/Users/vood/.pyenv/versions/3.6.3/bin/ludwig", line 11, in <module>
    sys.exit(main())
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/cli.py", line 86, in main
    CLI()
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/cli.py", line 64, in __init__
    getattr(self, args.command)()
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/cli.py", line 73, in predict
    predict.cli(sys.argv[2:])
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/predict.py", line 379, in cli
    full_predict(**vars(args))
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/predict.py", line 86, in full_predict
    only_predictions
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/data/preprocessing.py", line 660, in preprocess_for_prediction
    shuffle_training=False
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/ludwig/data/preprocessing.py", line 239, in load_data
    hdf5_data = h5py.File(hdf5_file_path, 'r')
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/h5py/_hl/files.py", line 394, in __init__
    swmr=swmr)
  File "/Users/vood/.pyenv/versions/3.6.3/lib/python3.6/site-packages/h5py/_hl/files.py", line 170, in make_fid
    fid = h5f.open(name, flags, fapl=fapl)
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5f.pyx", line 85, in h5py.h5f.open
OSError: Unable to open file (file signature not found)```

Thanks for sending this!
This is a small fix, will do it tomorrow.


Keeping, Expanding, and Dumping of inc/dec/quant concepts not in causal events

this was done from master, so fyi when it comes to merge ordering (I can fix conflicts too)
there is likely another way to do this, but this is what I came up with, please tweak as desired
to activate this "flag" set EidosSystem.keepStatefulConcepts = true in the config

See what you get when making a variable name that is too long!  Thanks for putting  up with my left indenting.

haha -- I was wondering if you'd notice my sloppy handling of it :) that
one line is a weeee bit close to the left edge..... :)
On Mon, Apr 1, 2019 at 11:31 AM Keith Alcock<EMAIL_ADDRESS>wrote:

See what you get when making a variable name that is too long! Thanks for
putting up with my left indenting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/570#issuecomment-478692744, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFIniVmQxJEqN1pjw3iPFcAqg1j_z4ncks5vclB5gaJpZM4cViBJ
.

Something is strange with Travis.  Where is it?

It seems to be back.  Just talking to myself...

@BeckySharp that was a really good catch a couple of minutes ago.  In JLDSerializer there is
object JLDRelation {
  val typeString = "relation"

  def newJLDRelation(serializer: JLDSerializer, mention: EidosEventMention): JLDRelation = {
    // This could be looked up in the taxonomy somehow, but the taxonomy doesn't include
    // information about the name of the arguments anyway, so may as well do all decoding here.
    // This could be pushed down to JLDRelation given EidosEventMention => JLDRelation.
    // If the JSON-LD specification doesn't change, then it is possible for the argument
    // names to be specified in master.yml file and then be taken over verbatim by querying the
    // arguments dictionary.
    if (JLDRelationCorrelation.taxonomy == mention.odinMention.label)
      new JLDRelationCorrelation(serializer, mention)
    else if (JLDRelationCausation.taxonomy == mention.odinMention.label)
      new JLDRelationCausation(serializer, mention)
    else
      throw new IllegalArgumentException("Unknown Mention: " + mention)
  }

that is not going to be happy with the new label when such a labeled Mention is used in a relation.  I just ran on the 52 documents and it didn't crash, so these new ones were never used or they might be used but the label gets pushed down by another one put in front of it.  (I see no instance of that.)  They are dangling there in the JSON_LD but nothing refers to them.  See below.  If something tried to in a relation, it would crash.  I think it is OK if this kind of output is expected:
    "@type" : "Extraction",
    "@id" : "_:Extraction_56",
    "type" : "concept",
    "subtype" : "entity",
    "labels" : [ "Concept-Expanded", "Concept", "Entity" ],
    "text" : "a significant depreciation of the local currency",
    "rule" : "simple-np++Decrease_ported_syntax_1_noun",
    "canonicalName" : "currency",
    "provenance" : [ {
      "@type" : "Provenance",
      "document" : {
        "@id" : "_:Document_1"
      },
      "documentCharInterval" : [ {
        "@type" : "Interval",
        "start" : 4833,
        "end" : 4880
      } ],
      "sentence" : {
        "@id" : "_:Sentence_20"
      },
      "positions" : [ {
        "@type" : "Interval",
        "start" : 37,
        "end" : 43
      } ]
    } ],
    "states" : [ {
      "@type" : "State",
      "type" : "DEC",
      "text" : "depreciation",
      "provenance" : {
        "@type" : "Provenance",
        "document" : {
          "@id" : "_:Document_1"
        },
        "documentCharInterval" : [ {
          "@type" : "Interval",
          "start" : 4847,
          "end" : 4858
        } ],
        "sentence" : {
          "@id" : "_:Sentence_20"
        },
        "positions" : [ {
          "@type" : "Interval",
          "start" : 39,
          "end" : 39
        } ]
      },
      "modifiers" : [ {
        "@type" : "Modifier",
        "text" : "significant",
        "provenance" : {
          "@type" : "Provenance",
          "document" : {
            "@id" : "_:Document_1"
          },
          "documentCharInterval" : [ {
            "@type" : "Interval",
            "start" : 4835,
            "end" : 4845
          } ],
          "sentence" : {
            "@id" : "_:Sentence_20"
          },
          "positions" : [ {
            "@type" : "Interval",
            "start" : 38,
            "end" : 38
          } ]
        },
        "intercept" : 0.6154,
        "mu" : 1.034E-5,
        "sigma" : -0.001123
      } ]
    } ]
  }, {

@kwalcock any news on why travis hates this PR?

actually @kwalcock -- the checks say they passed if you click on them, but here they don't... can we reset it?  I'd like to merge this soon bc I have another PR waiting in the wings (putting on some final touches...)

Sorry for the delay.  I noticed that they had passed.  I'm doing a regression test with all 3 PRs now.  The JSONLD reading is likewise in the wings.

At Tuesday's meeting I was asked to verify that there are TimeExpressions and GeoLocations in the new Extractions with the first label "Concept-Expanded".  I can confirm that.  I will send the output of the 52 document to Ben so that he can adjust INDRA and then plan to run the 500 overnight when we think everything is all lined up.

👍

There was similar instruction to double check on these new Extractions being involved in a relation.  I don't see evidence of that yet.  Is that a good thing or a bad one?


chore(deps): update semantic-release-base-image to v4.1.8

This PR contains the following updates:

Package
Update
Change

tubenhirn/semantic-release-azdo
patch
v4.1.6 -> v4.1.8

tubenhirn/semantic-release-git
patch
v4.1.6 -> v4.1.8

tubenhirn/semantic-release-github
patch
v4.1.6 -> v4.1.8

tubenhirn/semantic-release-gitlab
patch
v4.1.6 -> v4.1.8

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.3.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Recent RCs?

Are there plans on creating another release candidate? It's been several months since the last one and it seems like the dev branch is hundreds of commits ahead of master. It would be great to test out these changes/improvements through a RC.

Next week there'll be an RC


Add settings to ignore first click on unfocused window

Implements https://github.com/jwilm/alacritty/issues/1291

Was there a reason to leave out the platform checks? AFAIK this only matters for macOS.

Why is this optional? Are there ever a reason to accept a click on an unfocused window?

@NickeZ I'd say there is, at least for tiling window managers I can see this being useful.

Thanks for the feedback! I will implement t today and submit to you guys. Should I go ahead and make it an OSX only feature?

@NickeZ With focus following mouse this PR should be completely irrelevant. However I know about quite a few people that have focus on click in i3 just because they don't want random mouse movements to change the focused window. In this case it might be desired to still start a selection without having to click on the window to focus first and then start the selection.
However I completely agree with you when it comes to the additional complexity of the configuration file and codebase. I personally don't need to be able to turn this option off since I also use the option of focus following the mouse without any clicks required. However this still would be a breaking change from the current behavior without the possibility to recover the original behavior without the configuration option.
Unless there is anyone complaining in this PR already, there certainly is an option to kinda satisfy both groups though. We can remove the configuration option from this PR, merge it and just see if anyone will complain about the regression. If there is nobody speaking up I'd just go ahead and assume the target audience I'm talking about either doesn't exist or doesn't care that much.
@felippemr Unless you have a different idea I'd recommend following through with removing the configuration option and making this always take place. I have created a branch on my personal repo with the current state of this PR so no work is getting lost.
@NickeZ Thanks for chiming in, I'd say it's very likely that a large part of users will not care about being able to configure this. I haven't used WMs that use clicks to change mouse in quite a while so any other perspective is always welcome.

Thanks @chrisduerr, I will make it later today.

@chrisduerr just pushed

Thanks for looking into this! LGTM!


[DO NOT MERGE][Windows] Fix Split DLL Win with fix cyclic dep

Only use for windows build, linux part will be added later

https://github.com/intel/torch-xpu-ops/pull/838


Pygamer Qspi

This seems to be working for pygamer.
Also I'm pretty sure my change to your comment  @twitchyliquid64  is correct, but would be happy to be called out on that. I cant test that high a clock speed with my non pro salae logic analyser :(
Its possibly my comments arent perfect for your chip, but im pretty sure they hold for the family? Though we should probably document somewhere that this works for the w25 family only currently.
Beyond that Im dying, I cant get the GD25Q16C on the edgebadge to set the QE bit to save my life.

RE edgebadge, it should be same as your code I think because it doesnt have the writestatus2 register and should write past it
    flash
        .write_command(Command::WriteStatus, &[0x00, 0x02])
        .unwrap();

Adafruit hits this path I think
https://github.com/adafruit/Adafruit_SPIFlash/blob/12a69700ecaeed03d23ce5a64b4354495dae992a/src/Adafruit_SPIFlashBase.cpp#L166
Because of the definition
https://github.com/adafruit/Adafruit_SPIFlash/blob/3a7a0665ac1a52c7209cc4ff0fd047057c2f1109/src/flash_devices.h#L90-L100
I cant think of what to try to check..

Should we be rustfmt nightly?

Its possibly my comments arent perfect for your chip, but im pretty sure they hold for the family?

Maybe move these more specific comments into the example code rather than the qspi crate? Given qspi can be used for anything and not just flash operating with standard commands.

Beyond that Im dying, I cant get the GD25Q16C on the edgebadge to set the QE bit to save my life.

I cant see the command code for WriteStatus2 in the datasheet - are you sure youre not meant to use WriteStatus? Aside from that, your implementation looks fine.
Did you also play around with 7.5: 7.5. Write Enable for Volatile Status Register (50H) ?

Also I'm pretty sure my change to your comment @twitchyliquid64 is correct, but would be happy to be called out on that.

Nope, youre spot on xD

Maybe move these more specific comments into the example code rather than the qspi crate? Given qspi can be used for anything and not just flash operating with standard commands.

Yeah. I think this impl is odd in that way. Its clearly hardcoded to a certain style of chip. Dummy cycles are hardcoded for instance. The impl should probably be more or less expressive in the future.
 Both of the datasheets for the gigadevice chips say 06bh read take 1 dummy cycle, but adafruit uses 8 and 8 works for my GD25Q64, and 1 doesnt.. so Just version 1 million of the datasheet is just blatantly wrong i guess... sigh

I cant see the command code for WriteStatus2 in the datasheet - are you sure youre not meant to use WriteStatus? Aside from that, your implementation looks fine.

No I'm only using WriteStatus2 for the GD25Q64. Note it did seem like WriteStatus worked fine on the 64 as well but adafruit uses writestatus2 directly. I suppose its always better to not wipe out those lower level status bits if you dont need to.
Im using WriteStatus for the GD25Q16C same as your implementation and thats what's not working.
    flash
        .write_command(Command::WriteStatus, &[0x00, 0x02])
        .unwrap();

Did you also play around with 7.5: 7.5. Write Enable for Volatile Status Register (50H) ?

No I hadnt, Adafruit doesnt use it.. Didnt seem to help sadly.
Either way I think ive proven out the second implementation so.. whatever. Ready for merge whenever

Yeah. I think this impl is odd in that way.

Note that we are using this peripheral in memory mode, it also has a direct SPI mode.

Either way I think ive proven out the second implementation so.. whatever. Ready for merge whenever

Awesome,thanks! Should be ready to go after a re-base to master.


update tsconfig and fix errors

What changes were proposed in this pull request?

How was this pull request tested?

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@bourdakos1 Have you tried the pipeline editor after applying these changes? Just want to make sure that removing some of the files from its tsconfig file does not cause other side effects.

@lresende it seems that at least the basic functionality is working for me, but this touches a lot of code so we might want more extensive manual tests to be done by others

I just pushed some updates to the PRs with:

Fixed bug where new vars weren't saved on close
Added (back) support for env var detection on node add
Updated callback function to be more generic so it can be extended with more properties in the future

The last point was to partially address @bourdakos1 and @lresende discussion above. I believe for now leaving the refresh button inline where it actual applies makes sense, but I updated the code so that when we make it more generic in the future we only have the move the button, the actual callback function is already ready to support a full refresh.
With these changes I'm also moving this out of WIP for review

Code changes LGTM, but haven't tested locally

Code looks good.
I tested this locally and it works well for code snippets and script editors.
Although I'm seeing this alert element at the bottom of pipeline editor

Clicking the x does nothing, it just stays there. Wondering if it's my env or anybody else can reproduce this?

I'm able to reproduce what Karla commented. I think it's due to this change: https://github.com/elyra-ai/elyra/pull/1670/files#diff-c3ebbc30bb0c07233b81530f86ee864bf04a6eaa2542f1b7f1601ebf595bc513R130
because the alert shows if the alert variable is not equal to null, but the default is now an empty string.


Remove dotenv, use node-config only

In recent pull request, we added dotenv to manage the config params, but we should use only node-config to simplify the deployment

Pull request #89


Unable to create new play

I am not able to create new play..the following error pop up all the time(in the image)...do other facing same issue too? Or just me

Try to restart the server or Try to Sync your fork in your Account Your Repo


Loop error

As of a few days I cant generate images on Colab Pro, and get the following error while trying to switch model:
"The future belongs to a different loop than the one specified as the loop argument"

make sure your installed extensions are up to date

I get the same error just checking for extension updates actually


fix: order warning messages

Related issues 🔗
Closes #997 & #950 & #968
Description ℹ
Revisit the warning message because persistent limit orders are accepted, including GFA, GTT, GTC as well as liquidity commitments.
If the market is suspended, any orders placed now will not trade until the auction ends.
Demo 📺 & Technical 👨🔧

Tested each = Looks good


Add mentioning of unary minus to LRM

https://github.com/DavidWatkins/Dice/commit/218cdd226af54fc7a12aa54174686808b9c0c080#diff-4d2b42b627eff6deab20a53051f6bd3fR26


Remove different timeframe for Masternode Polls

For simplicity, all proposal types should stay on the same 30 day timeframe. Generally the advantage of quicker decisions is outweighed by the disadvantage of a more complex governance system overall, with multiple timeframes, both in code and socially.
For example, many MNO only pay attention once a month, if governance polls were on a separate timeframe they would be settled before many MNO even saw them.
Also the advantage of quicker decisions applies equally to funding proposals as it does to decision polls, but 30 days is what we have and are used to. Unless it’s a problem, it should not be changed.
There is nothing special about decision polls that justify the increased complexity of implementing a separate governance timeframe for them.

We want the result of these polls to be as authoritative as possible. That will be determined by how many masternodes participate. Having a poll with an end date other than the standard governance cycle will get less participants and therefore be less authoritative.
The result of any poll with a voting deadline other than the standard governance cycle will be undermined as being "snuck through undercover with only x% of masternodes knowing about it".
Also one of the points critics will make against this proposal is that governance polls may as well be off the blockchain. Platforms like the dash forum, dash central and dash nexuses could easily run polls that can only be voted on by cryptographically verified masternode owners (or their delegates).
That argument against these proposed on chain polls is made stronger by having them on a different time frame because it would make the polls more different and separate then the existing governance system anyway and it would make less masternodes participate.

between Dash Nexus, delegated voting, and this - it's my expectation that the active voting body will be more involved going forwards

That's conjecture, all of those things don't exist and we don't know if they ever do exist how much use, if any, they will get.

I ran into a scenario where this would be useful...

Everyone who ever made a tresury proposal would have found it useful to get a faster decision. That applies to everything, polls are not different and separate, we want them to be as less different and separate as possible because different and separate increases code and social complexity.

Just yesterday I ran into a scenario where this would be useful. Having to wait 30 days every time you need to make a decision in the world of crypto where things move as fast as they do is a problem. Even a 14 day voting period is still pretty slow for some things.

By putting these polls on the same timeframe as the rest of the governance system one would not have to wait 30 days, one would have to wait for a voting deadline that occurs once every 30 days. If one creates a poll in the 21st day of a voting cycle one would have to wait 9 days. Just like current governance (tresury) proposals.
So is your proposal to have a poll voting deadline cycles every 14 days so multiple polls created in that period have the same voting deadline? Or is your proposal for polls have a voting deadline 14 days after they are created so there is no regular poll deadline cycle?

@bitedgecom I've thought about what you said a lot over the past 10 days and I'm still not sure if I agree with you.
Another proposed change to governance that I've seen floated by two devs at this point is a rolling treasury that continually gets filled up and can be spent whenever a proposal receives enough votes to pass.
With that as context, what I'm proposing seems much less crazy.
That being said, I don't think it's asking too much of MNO to check in twice a month. To clarify, my two week long voting period for this polls is just about having a cycle that's 16616 / 2 blocks long.

If we had off-chain polling, it would also never get the level of credibility that an on-chain poll would.


Demographics blocks modal issue

Describe the bug
It's an amazing feature though, When we click on any patient ID, the whole website getting stretched, Seems small, But it will better if we fix it :)
To Reproduce
Steps to reproduce the behavior:

Go to 'Demographics.'
Click on 'Click on Patient ID'
Scroll down to 'Observe Blocks and Modal Background'
See error

Screenshots
Check the below presentation

Desktop (please complete the following information):

OS: [Windows 10]
Browser [All Major Browsers]

Additional context
Hope you can sort this out and i suggest you to add feature to close popup by clicking anywhere outside of the modal :) That way we can check them fastly.
Thanks & Regards,
Vamsi

Thanks for filing the issue :)
@Binu42 saw your PR a couple of days regarding the modal fix, can you help me fix that? I'll have it assigned to you!

#606 This is the PR :) Can you please help it @binu42

Thanks for filing the issue :)
@Binu42 saw your PR a couple of days regarding the modal fix, can you help me fix that? I'll have it assigned to you!

ya sure, assign it to me.


It already HTML-escapes characteres

Context
We are using the latest flutie gem in our Rails 6.1.5 app with the following code:
app/views/pages/show.html.erb
<% content_for :page_title, @page.title %>

app/views/layouts/application.html.erb
<title><%= page_title %></title>

Issue
For titles that contain characters that need to be HTML-escaped, we've noticed them being double-HTML-escaped.
For example, for the title Page & "Title" we get
<title>App : Page &amp; &quot;Title&quot;</title>

which causes the browser to display it as

Instead, we expected to get
<title>App : Page & "Title"</title>

which displays as expected

Here is a spec that asserts it already HTML-escapes characters:
https://github.com/elias19r/flutie/commit/2165815f9cc08e6d26ce575c1eaadb445c8a0243


Queryable status of worker and currently running/last running plan

There should be REST endpoints and methods on the worker class that give access to:

The current WorkerState
The status of the last plan to be run/currently running plan

Sounds good.
I think 1 is a long-term task, I would like to make a mechanism that allows us to encode progress information inside a plan. For 2 we also have the same problem, so if you have a nicer idea it might be worth a look. For 3 I think there may be a third concern as "how well did artemis work?" is different to "how well did my plan work?".

Based on Dom's comments and to be compliant with API guidelines, the endpoint for this should probably be of the form:
GET /tasks//status
where  could be 'current', 'last' or the task id generated and returned by the service when the task was created. This would also allow for requesting a longer history of task statuses if that were deemed useful/supported.

Further to my comment above, in the latest version of the API submitted in #231, tasks which are running or have been run on the worker are going to have URLs of the form {baseurl}/worker/tasks/{identifier} so we probably want the URL form for this to be:
GET {baseurl}/worker/tasks/{identifier}/status
with {identifier} being as specified before

Closing this as I think blueapi now supports the desired functionality.


can't add any other models like stable diffusion and inpainting

Please if you can add an easy way for people to add custom models that would be very helpful
Thanks!

Try forking it ,..!! It could work...!! I dont know , I havent tried it ,..!!

https://github.com/peaashmeter/invoke-ai-gui-colab/issues/2#issuecomment-1368143941


replace url in an alert

https://github.com/gragland/chatgpt-everywhere can be replaced with https://github.com/gragland/chatgpt-chrome-extension as i thought there is another repo while reading the code:
https://github.com/gragland/chatgpt-chrome-extension/blob/b1edc8659758aa582e5154de873a992e5d4104df/extension/content.js#L91

Ah yes forgot to change that when I renamed the repo. Fixed!


Unable to create a backup in openstack - temporary URL/volume in-use issue

Describe the bug
I'm deploying Velcro using helm chart, and I'm not able to successfully create a backup. They are always in the PartiallyFailed state.
Steps to reproduce the behavior

Deploy using helm chart
Create a backup using :

velero backup create test4  --include-namespaces=default --default-volumes-to-fs-backup --snapshot-volumes --ttl 30m

Expected behavior
A successful backup is created and uploaded to openstack Shared Object Storage.
Used versions

Velero version(velero version): velero/velero:v1.13.0
Plugin version(kubectl describe pod velero-...): lirt/velero-plugin-for-openstack:v0.6.0, velero/velero-plugin-for-csi:v0.7.0
Kubernetes version(kubectl version):  1.27.8
Openstack version:

Link to velero or backup log
time="2024-02-18T03:28:42Z" level=info msg="Authentication will be done for cloud main" cmd=/plugins/velero-plugin-for-openstack controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/utils/auth.go:33" pluginName=velero-plugin-for-openstack
time="2024-02-18T03:28:42Z" level=info msg="Trying to authenticate against OpenStack using environment variables (including application credentials) or using files ~/.config/openstack/clouds.yaml, /etc/openstack/clouds.yaml and ./clouds.yaml" cmd=/plugins/velero-plugin-for-openstack controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/utils/auth.go:68" pluginName=velero-plugin-for-openstack
time="2024-02-18T03:28:42Z" level=info msg="Authentication against identity endpoint https://identity-3.eu-nl-1.cloud.sap/v3/ was successful" cmd=/plugins/velero-plugin-for-openstack controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/utils/auth.go:113" pluginName=velero-plugin-for-openstack
time="2024-02-18T03:28:42Z" level=info msg="Successfully created object storage service client" cmd=/plugins/velero-plugin-for-openstack controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/swift/object_store.go:66" pluginName=velero-plugin-for-openstack region=eu-nl-1
time="2024-02-18T03:28:42Z" level=info msg="ObjectStore.CreateSignedURL called" cmd=/plugins/velero-plugin-for-openstack container=velero-backups-can controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/swift/object_store.go:252" object=backups/test4/test4-results.gz pluginName=velero-plugin-for-openstack ttl=6e+11
time="2024-02-18T03:28:42Z" level=warning msg="fail to get Backup metadata file's download URL {BackupResults test4}, retry later: rpc error: code = Unknown desc = failed to create temporary URL for \"backups/test4/test4-results.gz\" object in \"velero-backups-can\" container: Unable to obtain the Temp URL key." controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="pkg/controller/download_request_controller.go:206"
time="2024-02-18T03:28:43Z" level=error msg="Reconciler error" controller=downloadrequest controllerGroup=velero.io controllerKind=DownloadRequest downloadRequest="{\"name\":\"test4-4036bc95-faac-472e-ac17-f16b167c98cc\",\"namespace\":\"velero\"}" error="rpc error: code = Unknown desc = failed to create temporary URL for \"backups/test4/test4-results.gz\" object in \"velero-backups-can\" container: Unable to obtain the Temp URL key." error.file="/go/src/github.com/vmware-tanzu/velero/pkg/controller/download_request_controller.go:207" error.function="github.com/vmware-tanzu/velero/pkg/controller.(*downloadRequestReconciler).Reconcile" logSource="/go/pkg/mod/github.com/bombsimon/logrusr/v3@v3.0.0/logrusr.go:123" name=test4-4036bc95-faac-472e-ac17-f16b167c98cc namespace=velero reconcileID="\"1041cd96-1e2c-4ad0-823d-2d0c1438b387\""
time="2024-02-18T03:28:43Z" level=info msg="ObjectStore.Init called" cmd=/plugins/velero-plugin-for-openstack config="map[bucket:velero-backups-can cloud:main prefix: region:eu-nl-1]" controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/swift/object_store.go:38" pluginName=velero-plugin-for-openstack
time="2024-02-18T03:28:43Z" level=info msg="Authentication will be done for cloud main" cmd=/plugins/velero-plugin-for-openstack controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/utils/auth.go:33" pluginName=velero-plugin-for-openstack
time="2024-02-18T03:28:43Z" level=info msg="Trying to authenticate against OpenStack using environment variables (including application credentials) or using files ~/.config/openstack/clouds.yaml, /etc/openstack/clouds.yaml and ./clouds.yaml" cmd=/plugins/velero-plugin-for-openstack controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="/go/src/github.com/Lirt/velero-plugin-for-openstack/src/utils/auth.go:68" pluginName=velero-plugin-for-openstack

My guess is that it's related to that step but I'm not able to exec into the container to run those command

Ended up founding other way to do backup and now I'm unable to create a successfull backup du to volume in-use :
command : velero backup create test5  --include-namespaces=default
time="2024-02-18T05:02:15Z" level=info msg="Waiting for volumesnapshotcontents snapcontent-70c18c78-6e80-443d-a967-ab24bc97c370 to have snapshot handle. Retrying in 5s" backup=velero/test5 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:259" pluginName=velero-plugin-for-csi
time="2024-02-18T05:02:15Z" level=warning msg="Volumesnapshotcontent snapcontent-70c18c78-6e80-443d-a967-ab24bc97c370 has error: Failed to check and update snapshot content: failed to take snapshot of the volume c91638ec-6362-4e15-b3cd-e2f957e3e6b5: \"rpc error: code = Internal desc = CreateSnapshot failed with error Bad request with: [POST https://volume-3.eu-nl-1.cloud.sap:443/v3/ddcde3b2cae24ea0a85ad5b608b7ac97/snapshots], error message: {\\\"badRequest\\\": {\\\"code\\\": 400, \\\"message\\\": \\\"Invalid volume: Volume c91638ec-6362-4e15-b3cd-e2f957e3e6b5 status must be available, but current status is: in-use.\\\"}}\"" backup=velero/test5 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:261" pluginName=velero-plugin-for-csi
time="2024-02-18T05:02:20Z" level=info msg="Waiting for volumesnapshotcontents snapcontent-70c18c78-6e80-443d-a967-ab24bc97c370 to have snapshot handle. Retrying in 5s" backup=velero/test5 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:259" pluginName=velero-plugin-for-csi
time="2024-02-18T05:02:20Z" level=warning msg="Volumesnapshotcontent snapcontent-70c18c78-6e80-443d-a967-ab24bc97c370 has error: Failed to check and update snapshot content: failed to take snapshot of the volume c91638ec-6362-4e15-b3cd-e2f957e3e6b5: \"rpc error: code = Internal desc = CreateSnapshot failed with error Bad request with: [POST https://volume-3.eu-nl-1.cloud.sap:443/v3/ddcde3b2cae24ea0a85ad5b608b7ac97/snapshots], error message: {\\\"badRequest\\\": {\\\"code\\\": 400, \\\"message\\\": \\\"Invalid volume: Volume c91638ec-6362-4e15-b3cd-e2f957e3e6b5 status must be available, but current status is: in-use.\\\"}}\"" backup=velero/test5 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:261" pluginName=velero-plugin-for-csi

Hi,
Thank you for opening issue.
Regarding the first error, you need to follow documentation for swift container setup to make plugin to successfully create temporary URL:
time="2024-02-18T03:28:42Z" level=warning msg="fail to get Backup metadata file's download URL {BackupResults test4}, retry later: rpc error: code = Unknown desc = failed to create temporary URL for \"backups/test4/test4-results.gz\" object in \"velero-backups-can\" container: Unable to obtain the Temp URL key." controller=download-request downloadRequest=velero/test4-4036bc95-faac-472e-ac17-f16b167c98cc logSource="pkg/controller/download_request_controller.go:206"

Those swift commands don't need to be executed from inside a container. You can run them locally, but you need to download your Openstack/Swift credentials, source them and then run the commands. Of course you need to install python-swiftclient using pip to run the swift command.
For volume in-use the snapshot should work, because it's doing --force as mentioned in docs:

The snapshots are done using flag --force. The reason is that volumes in state in-use cannot be snapshotted without it (they would need to be detached in advance). In some cases this can make snapshot contents inconsistent!

Can you write me definition of your BackupStorageLocation? From log message you pasted it seems like you are doing snapshot using CSI driver, not this plugin.
backup=velero/test5 cmd=/plugins/velero-plugin-for-csi
logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:261"
pluginName=velero-plugin-for-csi

here's my full value.yaml file that I applied :
##
## Configuration settings related to Velero installation namespace
##

# Labels settings in namespace
namespace:
  labels: {}
    # Enforce Pod Security Standards with Namespace Labels
    # https://kubernetes.io/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/
    # - key: pod-security.kubernetes.io/enforce
    #   value: privileged
    # - key: pod-security.kubernetes.io/enforce-version
    #   value: latest
    # - key: pod-security.kubernetes.io/audit
    #   value: privileged
    # - key: pod-security.kubernetes.io/audit-version
    #   value: latest
    # - key: pod-security.kubernetes.io/warn
    #   value: privileged
    # - key: pod-security.kubernetes.io/warn-version
    #   value: latest

##
## End of namespace-related settings.
##

##
## Configuration settings that directly affect the Velero deployment YAML.
##

# Details of the container image to use in the Velero deployment & daemonset (if
# enabling node-agent). Required.
image:
  repository: velero/velero
  tag: v1.13.0
  # Digest value example: sha256:d238835e151cec91c6a811fe3a89a66d3231d9f64d09e5f3c49552672d271f38.
  # If used, it will take precedence over the image.tag.
  # digest:
  pullPolicy: IfNotPresent
  # One or more secrets to be used when pulling images
  imagePullSecrets: []
  # - registrySecretName

nameOverride: ""
fullnameOverride: ""

# Annotations to add to the Velero deployment's. Optional.
#
# If you are using reloader use the following annotation with your VELERO_SECRET_NAME
annotations: {}
# secret.reloader.stakater.com/reload: "<VELERO_SECRET_NAME>"

# Annotations to add to secret
secretAnnotations: {}

# Labels to add to the Velero deployment's. Optional.
labels: {}

# Annotations to add to the Velero deployment's pod template. Optional.
#
# If using kube2iam or kiam, use the following annotation with your AWS_ACCOUNT_ID
# and VELERO_ROLE_NAME filled in:
podAnnotations: {}
  #  iam.amazonaws.com/role: "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<VELERO_ROLE_NAME>"

# Additional pod labels for Velero deployment's template. Optional
# ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
podLabels: {}

# Number of old history to retain to allow rollback (If not set, default Kubernetes value is set to 10)
# revisionHistoryLimit: 1

# Resource requests/limits to specify for the Velero deployment.
# https://velero.io/docs/v1.6/customize-installation/#customize-resource-requests-and-limits
resources:
  requests:
    cpu: 500m
    memory: 128Mi
  limits:
    cpu: 1000m
    memory: 512Mi

# Resource requests/limits to specify for the upgradeCRDs job pod. Need to be adjusted by user accordingly.
upgradeJobResources: {}
# requests:
#     cpu: 50m
#     memory: 128Mi
#   limits:
#     cpu: 100m
#     memory: 256Mi
upgradeCRDsJob:
  # Extra volumes for the Upgrade CRDs Job. Optional.
  extraVolumes: []
  # Extra volumeMounts for the Upgrade CRDs Job. Optional.
  extraVolumeMounts: []
  # Extra key/value pairs to be used as environment variables. Optional.
  extraEnvVars: {}

# Configure the dnsPolicy of the Velero deployment
# See: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy
dnsPolicy: ClusterFirst

# Init containers to add to the Velero deployment's pod spec. At least one plugin provider image is required.
# If the value is a string then it is evaluated as a template.
initContainers:
  - name: velero-plugin-for-csi
    image: velero/velero-plugin-for-csi:v0.7.0
    imagePullPolicy: IfNotPresent
    volumeMounts:
      - mountPath: /target
        name: plugins
  - name: velero-plugin-for-openstack
    image: lirt/velero-plugin-for-openstack:v0.6.0
    imagePullPolicy: IfNotPresent
    volumeMounts:
      - mountPath: /target
        name: plugins

# SecurityContext to use for the Velero deployment. Optional.
# Set fsGroup for `AWS IAM Roles for Service Accounts`
# see more informations at: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
podSecurityContext: {}
  # fsGroup: 1337

# Container Level Security Context for the 'velero' container of the Velero deployment. Optional.
# See: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
containerSecurityContext: {}
  # allowPrivilegeEscalation: false
  # capabilities:
  #   drop: ["ALL"]
  #   add: []
  # readOnlyRootFilesystem: true

# Container Lifecycle Hooks to use for the Velero deployment. Optional.
lifecycle: {}

# Pod priority class name to use for the Velero deployment. Optional.
priorityClassName: ""

# The number of seconds to allow for graceful termination of the pod. Optional.
terminationGracePeriodSeconds: 3600

# Liveness probe of the pod
livenessProbe:
  httpGet:
    path: /metrics
    port: http-monitoring
    scheme: HTTP
  initialDelaySeconds: 10
  periodSeconds: 30
  timeoutSeconds: 5
  successThreshold: 1
  failureThreshold: 5

# Readiness probe of the pod
readinessProbe:
  httpGet:
    path: /metrics
    port: http-monitoring
    scheme: HTTP
  initialDelaySeconds: 10
  periodSeconds: 30
  timeoutSeconds: 5
  successThreshold: 1
  failureThreshold: 5

# Tolerations to use for the Velero deployment. Optional.
tolerations: []

# Affinity to use for the Velero deployment. Optional.
affinity: {}

# Node selector to use for the Velero deployment. Optional.
nodeSelector: {}

# DNS configuration to use for the Velero deployment. Optional.
dnsConfig: {}

# Extra volumes for the Velero deployment. Optional.
extraVolumes:
- name: cloud-config-velero
  secret:
    secretName: velero-credentials
    items:
    - key: clouds.yaml
      path: clouds.yaml

# Extra volumeMounts for the Velero deployment. Optional.
extraVolumeMounts:
- name: cloud-config-velero
  mountPath: /etc/openstack/clouds.yaml
  readOnly: true
  subPath: clouds.yaml

# Extra K8s manifests to deploy
extraObjects: []
  # - apiVersion: secrets-store.csi.x-k8s.io/v1
  #   kind: SecretProviderClass
  #   metadata:
  #     name: velero-secrets-store
  #   spec:
  #     provider: aws
  #     parameters:
  #       objects: |
  #         - objectName: "velero"
  #           objectType: "secretsmanager"
  #           jmesPath:
  #               - path: "access_key"
  #                 objectAlias: "access_key"
  #               - path: "secret_key"
  #                 objectAlias: "secret_key"
  #               - path: "region"
  #                 objectAlias: "region"
  #     secretObjects:
  #       - data:
  #         - key: access_key
  #           objectName: client-id
  #         - key: client-secret
  #           objectName: client-secret
  #         - key: region
  #           objectName: client-secret
  #         secretName: velero-secrets-store
  #         type: Opaque

# Settings for Velero's prometheus metrics. Enabled by default.
metrics:
  enabled: true
  scrapeInterval: 30s
  scrapeTimeout: 10s

  # service metdata if metrics are enabled
  service:
    annotations: {}
    labels: {}

  # Pod annotations for Prometheus
  podAnnotations:
    prometheus.io/scrape: "true"
    prometheus.io/port: "8085"
    prometheus.io/path: "/metrics"

  serviceMonitor:
    autodetect: true
    enabled: false
    annotations: {}
    additionalLabels: {}

    # metrics.serviceMonitor.metricRelabelings Specify Metric Relabelings to add to the scrape endpoint
    # ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#relabelconfig
    # metricRelabelings: []
    # metrics.serviceMonitor.relabelings [array] Prometheus relabeling rules
    # relabelings: []
    # ServiceMonitor namespace. Default to Velero namespace.
    # namespace:
    # ServiceMonitor connection scheme. Defaults to HTTP.
    # scheme: ""
    # ServiceMonitor connection tlsConfig. Defaults to {}.
    # tlsConfig: {}
  nodeAgentPodMonitor:
    autodetect: true
    enabled: false
    annotations: {}
    additionalLabels: {}
    # ServiceMonitor namespace. Default to Velero namespace.
    # namespace:
    # ServiceMonitor connection scheme. Defaults to HTTP.
    # scheme: ""
    # ServiceMonitor connection tlsConfig. Defaults to {}.
    # tlsConfig: {}

  prometheusRule:
    autodetect: true
    enabled: false
    # Additional labels to add to deployed PrometheusRule
    additionalLabels: {}
    # PrometheusRule namespace. Defaults to Velero namespace.
    # namespace: ""
    # Rules to be deployed
    spec: []
    # - alert: VeleroBackupPartialFailures
    #   annotations:
    #     message: Velero backup {{ $labels.schedule }} has {{ $value | humanizePercentage }} partialy failed backups.
    #   expr: |-
    #     velero_backup_partial_failure_total{schedule!=""} / velero_backup_attempt_total{schedule!=""} > 0.25
    #   for: 15m
    #   labels:
    #     severity: warning
    # - alert: VeleroBackupFailures
    #   annotations:
    #     message: Velero backup {{ $labels.schedule }} has {{ $value | humanizePercentage }} failed backups.
    #   expr: |-
    #     velero_backup_failure_total{schedule!=""} / velero_backup_attempt_total{schedule!=""} > 0.25
    #   for: 15m
    #   labels:
    #     severity: warning

kubectl:
  image:
    repository: docker.io/bitnami/kubectl
    # Digest value example: sha256:d238835e151cec91c6a811fe3a89a66d3231d9f64d09e5f3c49552672d271f38.
    # If used, it will take precedence over the kubectl.image.tag.
    # digest:
    # kubectl image tag. If used, it will take precedence over the cluster Kubernetes version.
    # tag: 1.16.15
  # Container Level Security Context for the 'kubectl' container of the crd jobs. Optional.
  # See: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
  containerSecurityContext: {}
  # Resource requests/limits to specify for the upgrade/cleanup job. Optional
  resources: {}
  # Annotations to set for the upgrade/cleanup job. Optional.
  annotations: {}
  # Labels to set for the upgrade/cleanup job. Optional.
  labels: {}

# This job upgrades the CRDs.
upgradeCRDs: true

# This job is meant primarily for cleaning up CRDs on CI systems.
# Using this on production systems, especially those that have multiple releases of Velero, will be destructive.
cleanUpCRDs: false

##
## End of deployment-related settings.
##

##
## Parameters for the `default` BackupStorageLocation and VolumeSnapshotLocation,
## and additional server settings.
##
configuration:
  # Parameters for the BackupStorageLocation(s). Configure multiple by adding other element(s) to the backupStorageLocation slice.
  # See https://velero.io/docs/v1.6/api-types/backupstoragelocation/
  backupStorageLocation:
    # name is the name of the backup storage location where backups should be stored. If a name is not provided,
    # a backup storage location will be created with the name "default". Optional.
    # provider is the name for the backup storage location provider.
  - name:
    provider: community.openstack.org/openstack
    # bucket is the name of the bucket to store backups in. Required.
    bucket: velero-backups-can
    # caCert defines a base64 encoded CA bundle to use when verifying TLS connections to the provider. Optional.
    caCert:
    # prefix is the directory under which all Velero data should be stored within the bucket. Optional.
    prefix:
    # default indicates this location is the default backup storage location. Optional.
    default: true
    # validationFrequency defines how frequently Velero should validate the object storage. Optional.
    validationFrequency:
    # accessMode determines if velero can write to this backup storage location. Optional.
    # default to ReadWrite, ReadOnly is used during migrations and restores.
    accessMode: ReadWrite
    credential:
      # name of the secret used by this backupStorageLocation.
      # name: velero-credentials
      # name of key that contains the secret data to be used.
      # key: clouds
      # auth_url: "https://identity.com/v3"
    # Additional provider-specific configuration. See link above
    # for details of required/optional fields for your provider.
    config:
     cloud: main
     auth_url: "https://identity.com/v3"
     region: "eu-nl-1"
    #  resticRepoPrefix: swift:containers:/restic
    #  domain-name: "cp"
    #  tenant-name: "gardener-canary-team"
    #  s3ForcePathStyle:
    #  s3Url:
    #  kmsKeyId:
    #  resourceGroup:
    #  The ID of the subscription containing the storage account, if different from the cluster’s subscription. (Azure only)
    #  subscriptionId:
    #  storageAccount:
    #  publicUrl:
    #  Name of the GCP service account to use for this backup storage location. Specify the
    #  service account here if you want to use workload identity instead of providing the key file.(GCP only)
    #  serviceAccount:
    #  Option to skip certificate validation or not if insecureSkipTLSVerify is set to be true, the client side should set the
    #  flag. For Velero client Command like velero backup describe, velero backup logs needs to add the flag --insecure-skip-tls-verify
    #  insecureSkipTLSVerify:

  # Parameters for the VolumeSnapshotLocation(s). Configure multiple by adding other element(s) to the volumeSnapshotLocation slice.
  # See https://velero.io/docs/v1.6/api-types/volumesnapshotlocation/
  volumeSnapshotLocation:
    # name is the name of the volume snapshot location where snapshots are being taken. Required.
  - name: cinder
    # optional snapshot method:
    # * "snapshot" is a default cinder snapshot method
    # * "clone" is for a full volume clone instead of a snapshot allowing the
    # source volume to be deleted
    # * "backup" is for a full volume backup uploaded to a Cinder backup
    # allowing the source volume to be deleted (EXPERIMENTAL)
    # * "image" is for a full volume backup uploaded to a Glance image
    # allowing the source volume to be deleted (EXPERIMENTAL)
    # requires the "enable_force_upload" Cinder option to be enabled on the server
    method: snapshot
    volumeTimeout: 5m
    snapshotTimeout: 5m
    cloneTimeout: 5m
    backupTimeout: 5m
    imageTimeout: 5m
    # provider is the name for the volume snapshot provider.
    provider: community.openstack.org/openstack-cinder
    credential:
      # name of the secret used by this volumeSnapshotLocation.
      name: velero-credentials2
      # name of key that contains the secret data to be used.
      key: clouds
    # Additional provider-specific configuration. See link above
    # for details of required/optional fields for your provider.
    config:
     auth_url: "https://identity.com/v3"
     region: eu-nl-1
     domain-name: "cp"
     tenant-name: "gardener-canary-team"
  #    apiTimeout:
  #    resourceGroup:
  #    The ID of the subscription where volume snapshots should be stored, if different from the cluster’s subscription. If specified, also requires `configuration.volumeSnapshotLocation.config.resourceGroup`to be set. (Azure only)
  #    subscriptionId:
  #    incremental:
  #    snapshotLocation:
  #    project:
  - name: manila
    provider: community.openstack.org/openstack-manila
    credential:
      # name of the secret used by this volumeSnapshotLocation.
      name: velero-credentials2
      # name of key that contains the secret data to be used.
      key: clouds
    # Additional provider-specific configuration. See link above
    # for details of required/optional fields for your provider.
    config:
      # optional snapshot method:
      # * "snapshot" is a default manila snapshot method
      # * "clone" is for a full share clone instead of a snapshot allowing the
      # source share to be deleted
      method: snapshot
      region: eu-nl-1
      auth_url: "https://identity.com/v3"
      domain-name: "cp"
      tenant-name: "gardener-canary-team"
      # optional Manila CSI driver name (default: nfs.manila.csi.openstack.org)
      driver: ceph.manila.csi.openstack.org
      # optional resource readiness timeouts in Golang time format: https://pkg.go.dev/time#ParseDuration
      # (default: 5m)
      shareTimeout: 5m
      snapshotTimeout: 5m
      cloneTimeout: 5m
      replicaTimeout: 5m
      # ensures that the Manila share/snapshot/replica is removed
      # this is a workaround to the https://bugs.launchpad.net/manila/+bug/2025641 and
      # https://bugs.launchpad.net/manila/+bug/1960239 bugs
      # if the share/snapshot/replica is in "error_deleting" status, the plugin will try
      # to reset its status (usually extra admin permissions are required) and delete it
      # again within the defined "cloneTimeout", "snapshotTimeout" or "replicaTimeout"
      ensureDeleted: "true"
      # a delay to wait between delete/reset actions when "ensureDeleted" is enabled
      ensureDeletedDelay: 10s
      # deletes all dependent share resources (i.e. snapshots, replicas) before deleting
      # the clone share (works only, when a snapshot method is set to clone)
      cascadeDelete: "true"
      # enforces availability zone checks when the availability zone of a
      # snapshot/share differs from the Velero metadata
      enforceAZ: "true"
  # These are server-level settings passed as CLI flags to the `velero server` command. Velero
  # uses default values if they're not passed in, so they only need to be explicitly specified
  # here if using a non-default value. The `velero server` default values are shown in the
  # comments below.
  # --------------------
  # `velero server` default: restic
  uploaderType:
  # `velero server` default: 1m
  backupSyncPeriod:
  # `velero server` default: 4h
  fsBackupTimeout:
  # `velero server` default: 30
  clientBurst:
  # `velero server` default: 500
  clientPageSize:
  # `velero server` default: 20.0
  clientQPS:
  # Name of the default backup storage location. Default: default
  defaultBackupStorageLocation:
  # How long to wait by default before backups can be garbage collected. Default: 72h
  defaultBackupTTL:
  # Name of the default volume snapshot location.
  defaultVolumeSnapshotLocations:
  # `velero server` default: empty
  disableControllers:
  # `velero server` default: 1h
  garbageCollectionFrequency:
  # Set log-format for Velero pod. Default: text. Other option: json.
  logFormat:
  # Set log-level for Velero pod. Default: info. Other options: debug, warning, error, fatal, panic.
  logLevel:
  # The address to expose prometheus metrics. Default: :8085
  metricsAddress:
  # Directory containing Velero plugins. Default: /plugins
  pluginDir:
  # The address to expose the pprof profiler. Default: localhost:6060
  profilerAddress:
  # `velero server` default: false
  restoreOnlyMode:
  # `velero server` default: customresourcedefinitions,namespaces,storageclasses,volumesnapshotclass.snapshot.storage.k8s.io,volumesnapshotcontents.snapshot.storage.k8s.io,volumesnapshots.snapshot.storage.k8s.io,persistentvolumes,persistentvolumeclaims,secrets,configmaps,serviceaccounts,limitranges,pods,replicasets.apps,clusterclasses.cluster.x-k8s.io,clusters.cluster.x-k8s.io,clusterresourcesets.addons.cluster.x-k8s.io
  restoreResourcePriorities:
  # `velero server` default: 1m
  storeValidationFrequency:
  # How long to wait on persistent volumes and namespaces to terminate during a restore before timing out. Default: 10m
  terminatingResourceTimeout:
  # Bool flag to configure Velero server to move data by default for all snapshots supporting data movement. Default: false
  defaultSnapshotMoveData:
  # Comma separated list of velero feature flags. default: empty
  # features: EnableCSI
  features: EnableCSI
  # `velero server` default: velero
  namespace:

  # additional key/value pairs to be used as environment variables such as "AWS_CLUSTER_NAME: 'yourcluster.domain.tld'"
  extraEnvVars: {}

  # Set true for backup all pod volumes without having to apply annotation on the pod when used file system backup Default: false.
  defaultVolumesToFsBackup:

  # How often repository maintain is run for repositories by default.
  defaultRepoMaintainFrequency:

##
## End of backup/snapshot location settings.
##

##
## Settings for additional Velero resources.
##

rbac:
  # Whether to create the Velero role and role binding to give all permissions to the namespace to Velero.
  create: true
  # Whether to create the cluster role binding to give administrator permissions to Velero
  clusterAdministrator: true
  # Name of the ClusterRole.
  clusterAdministratorName: cluster-admin

# Information about the Kubernetes service account Velero uses.
serviceAccount:
  server:
    create: true
    name:
    annotations:
    labels:

# Info about the secret to be used by the Velero deployment, which
# should contain credentials for the cloud provider IAM account you've
# set up for Velero.
credentials:
  # Whether a secret should be used. Set to false if, for examples:
  # - using kube2iam or kiam to provide AWS IAM credentials instead of providing the key file. (AWS only)
  # - using workload identity instead of providing the key file. (Azure/GCP only)
  useSecret: true
  # Name of the secret to create if `useSecret` is true and `existingSecret` is empty
  name:
  # Name of a pre-existing secret (if any) in the Velero namespace
  # that should be used to get IAM account credentials. Optional.
  existingSecret: velero-credentials
  # Data to be stored in the Velero secret, if `useSecret` is true and `existingSecret` is empty.
  # As of the current Velero release, Velero only uses one secret key/value at a time.
  # The key must be named `cloud`, and the value corresponds to the entire content of your IAM credentials file.
  # Note that the format will be different for different providers, please check their documentation.
  # Here is a list of documentation for plugins maintained by the Velero team:
  # [AWS] https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/README.md
  # [GCP] https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/README.md
  # [Azure] https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/README.md
  secretContents:
  # additional key/value pairs to be used as environment variables such as "DIGITALOCEAN_TOKEN: <your-key>". Values will be stored in the secret.
  extraEnvVars: {}
  # Name of a pre-existing secret (if any) in the Velero namespace
  # that will be used to load environment variables into velero and node-agent.
  # Secret should be in format - https://kubernetes.io/docs/concepts/configuration/secret/#use-case-as-container-environment-variables
  extraSecretRef: ""

# Whether to create backupstoragelocation crd, if false => do not create a default backup location
backupsEnabled: true
# Whether to create volumesnapshotlocation crd, if false => disable snapshot feature
snapshotsEnabled: true

# Whether to deploy the node-agent daemonset.
deployNodeAgent: true

nodeAgent:
  podVolumePath: /var/lib/kubelet/pods
  privileged: false
  # Pod priority class name to use for the node-agent daemonset. Optional.
  priorityClassName: ""
  # Resource requests/limits to specify for the node-agent daemonset deployment. Optional.
  # https://velero.io/docs/v1.6/customize-installation/#customize-resource-requests-and-limits
  resources:
    requests:
      cpu: 500m
      memory: 512Mi
    limits:
      cpu: 1000m
      memory: 1024Mi

  # Tolerations to use for the node-agent daemonset. Optional.
  tolerations: []

  # Annotations to set for the node-agent daemonset. Optional.
  annotations: {}

  # labels to set for the node-agent daemonset. Optional.
  labels: {}

  # will map /scratch to emptyDir. Set to false and specify your own volume
  # via extraVolumes and extraVolumeMounts that maps to /scratch
  # if you don't want to use emptyDir.
  useScratchEmptyDir: true

  # Extra volumes for the node-agent daemonset. Optional.
  extraVolumes: []

  # Extra volumeMounts for the node-agent daemonset. Optional.
  extraVolumeMounts: []

  # Key/value pairs to be used as environment variables for the node-agent daemonset. Optional.
  extraEnvVars: {}

  # Configure the dnsPolicy of the node-agent daemonset
  # See: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy
  dnsPolicy: ClusterFirst

  # SecurityContext to use for the Velero deployment. Optional.
  # Set fsGroup for `AWS IAM Roles for Service Accounts`
  # see more informations at: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
  podSecurityContext:
    runAsUser: 0
    # fsGroup: 1337

  # Container Level Security Context for the 'node-agent' container of the node-agent daemonset. Optional.
  # See: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
  containerSecurityContext: {}

  # Container Lifecycle Hooks to use for the node-agent daemonset. Optional.
  lifecycle: {}

  # Node selector to use for the node-agent daemonset. Optional.
  nodeSelector: {}

  # Affinity to use with node-agent daemonset. Optional.
  affinity: {}

  # DNS configuration to use for the node-agent daemonset. Optional.
  dnsConfig: {}

# Backup schedules to create.
# Eg:
# schedules:
#   mybackup:
#     disabled: false
#     labels:
#       myenv: foo
#     annotations:
#       myenv: foo
#     schedule: "0 0 * * *"
#     useOwnerReferencesInBackup: false
#     template:
#       ttl: "240h"
#       storageLocation: default
#       includedNamespaces:
#       - foo
schedules: {}

# Velero ConfigMaps.
# Eg:
# configMaps:
    # See: https://velero.io/docs/v1.11/file-system-backup/
#   fs-restore-action-config:
#     labels:
#       velero.io/plugin-config: ""
#       velero.io/pod-volume-restore: RestoreItemAction
#     data:
#       image: velero/velero-restore-helper:v1.10.2
#       cpuRequest: 200m
#       memRequest: 128Mi
#       cpuLimit: 200m
#       memLimit: 128Mi
#       secCtx: |
#         capabilities:
#           drop:
#           - ALL
#           add: []
#         allowPrivilegeEscalation: false
#         readOnlyRootFilesystem: true
#         runAsUser: 1001
#         runAsGroup: 999
configMaps: {}

##
## End of additional Velero resource settings.
##

install command
helm install velero vmware-tanzu/velero  -f values.yaml

Extra information:

Hello,
The config looks correct. You need to first apply the TMP URL configuration. Please reach back to me after you do it to check if the issue is solved.

Secondary the Backup or Schedule has to reference storageLocation: default (or your name of BackupStorageLocation).

You might need to upgrade your swift command:
This one is returning an error on MacOS
SWIFT_TMP_URL_KEY=$(dd if=/dev/urandom | tr -dc A-Za-z0-9 | head -c 40)
tr: Illegal byte sequence

An alternative that I found was
SWIFT_TMP_URL_KEY=$(dd if=/dev/urandom | LC_ALL=C tr -dc A-Za-z0-9 | head -c 40)

I ran the command to do the Swift Container Setup and it went well.
I setup the BackupStorageLocation like you mentionned, but now it seems like the error that I'm getting comes from the backuprepositories.velero.io

logs from Velero pod
time="2024-02-19T15:18:45Z" level=info msg="pod default/my-pod has volumes to backup: [my-volume]" backup=velero/test223 logSource="pkg/podvolume/backupper.go:172" name=my-pod namespace=default resource=pods
time="2024-02-19T15:18:45Z" level=info msg="No repository found, creating one" backupLocation=default logSource="pkg/repository/ensurer.go:89" repositoryType=restic volumeNamespace=default
time="2024-02-19T15:18:45Z" level=info msg="Initializing backup repository" backupRepo=velero/default-default-restic-wlv7b logSource="pkg/controller/backup_repository_controller.go:216"
time="2024-02-19T15:18:45Z" level=info msg="Set matainenance according to repository suggestion" frequency=168h0m0s logSource="pkg/controller/backup_repository_controller.go:263"
time="2024-02-19T15:18:45Z" level=error msg="Restic command fail with ExitCode: 1. Process ID is 297, Exit error is: exit status 1" logSource="pkg/util/exec/exec.go:66"
time="2024-02-19T15:18:45Z" level=error msg="Error checking repository for stale locks" backupRepo=velero/default-default-restic-wlv7b error="error running command=restic unlock --repo= --password-file=/tmp/credentials/velero/velero-repo-credentials-repository-password --cache-dir=/scratch/.cache/restic, stdout=, stderr=Fatal: Please specify repository location (-r or --repository-file)\n: exit status 1" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/repository/restic/repository.go:123" error.function="github.com/vmware-tanzu/velero/pkg/repository/restic.(*RepositoryService).exec" logSource="pkg/controller/backup_repository_controller.go:184"
time="2024-02-19T15:18:45Z" level=info msg="Checking backup repository for readiness" backupRepo=velero/default-default-restic-wlv7b logSource="pkg/controller/backup_repository_controller.go:307"
time="2024-02-19T15:18:46Z" level=info msg="1 errors encountered backup up item" backup=velero/test223 logSource="pkg/backup/backup.go:457" name=my-pod
time="2024-02-19T15:18:46Z" level=error msg="Error backing up item" backup=velero/test223 error="failed to wait BackupRepository: backup repository is not ready: error to get identifier for repo default-default-restic-wlv7b: invalid backend type community.openstack.org/openstack, provider community.openstack.org/openstack" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/repository/backup_repo_op.go:83" error.function=github.com/vmware-tanzu/velero/pkg/repository.GetBackupRepository logSource="pkg/backup/backup.go:461" name=my-pod

Thank you again for your help

Regarding this error it looks like Velero code only allows certain providers to do filesystem backup. It's configured here in the code. For this I have to redirect you to Velero FSB documentation as restic or other file-system-backup providers are not a topic of this plugin.
time="2024-02-19T15:18:46Z"
level=error
msg="Error backing up item" backup=velero/test223
error="failed to wait BackupRepository: backup repository is not ready:
             error to get identifier for repo default-default-restic-wlv7b:
             invalid backend type community.openstack.org/openstack,
             provider community.openstack.org/openstack"
error.file="/go/src/github.com/vmware-tanzu/velero/pkg/repository/backup_repo_op.go:83"
error.function=github.com/vmware-tanzu/velero/pkg/repository.GetBackupRepository
logSource="pkg/backup/backup.go:461" name=my-pod

Besides that there is a restic error that you need to solve but I'm not sure if solving this can fix the error above.
time="2024-02-19T15:18:45Z"
level=error
msg="Error checking repository for stale locks"
backupRepo=velero/default-default-restic-wlv7b
error="error running
             command=restic unlock \
                     --repo= \
                     --password-file=/tmp/credentials/velero/velero-repo-credentials-repository-password \
                     --cache-dir=/scratch/.cache/restic,
stdout=,
stderr=Fatal: Please specify repository location (-r or --repository-file)\n:
             exit status 1"
             error.file="/go/src/github.com/vmware-tanzu/velero/pkg/repository/restic/repository.go:123"
             error.function="github.com/vmware-tanzu/velero/pkg/repository/restic.(*RepositoryService).exec" logSource="pkg/controller/backup_repository_controller.go:184"

If you don't want to do file-system-backup, you can disable restic and snapshots will work fine.

looks like Velero code only allows certain providers to do filesystem backup

Nice catch.
Unfortunately, even when I disable restic and run a normal velero backup create test3 --include-namespaces=default I'm getting the issues that I had previously mentioning that the volume is in use.
time="2024-02-19T17:22:39Z" level=info msg="Waiting for volumesnapshotcontents snapcontent-c9c3c980-d38b-46c5-91ea-be3976aa035b to have snapshot handle. Retrying in 5s" backup=velero/test3 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:259" pluginName=velero-plugin-for-csi
time="2024-02-19T17:22:39Z" level=warning msg="Volumesnapshotcontent snapcontent-c9c3c980-d38b-46c5-91ea-be3976aa035b has error: Failed to check and update snapshot content: failed to take snapshot of the volume c91638ec-6362-4e15-b3cd-e2f957e3e6b5: \"rpc error: code = Internal desc = CreateSnapshot failed with error Bad request with: [POST https://volume-3.eu-nl-1.cloud.sap:443/v3/ddcde3b2cae24ea0a85ad5b608b7ac97/snapshots], error message: {\\\"badRequest\\\": {\\\"code\\\": 400, \\\"message\\\": \\\"Invalid volume: Volume c91638ec-6362-4e15-b3cd-e2f957e3e6b5 status must be available, but current status is: in-use.\\\"}}\"" backup=velero/test3 cmd=/plugins/velero-plugin-for-csi logSource="/go/src/velero-plugin-for-csi/internal/util/util.go:261" pluginName=velero-plugin-for-csi

Having previously achieved success backing up everything in AWS S3, I think returning to that option would provide ample support for various backup requirements.
Thank you for your assistance. If no other solutions address the ongoing "in use" issue, I suggest closing the ticket.

:smile: This is still not a log of this plugin - you can see this in log pluginName=velero-plugin-for-csi. Please read error logs carefully or you will be deceiving yourself!
In a simple standard setup you should have 1 BSL and 1 VSL.
---
apiVersion: velero.io/v1
kind: BackupStorageLocation
metadata:
  name: my-awesome-bsl
  namespace: <NAMESPACE>
spec:
  objectStorage:
    bucket: <CONTAINER_NAME>
  provider: community.openstack.org/openstack

---
apiVersion: velero.io/v1
kind: VolumeSnapshotLocation
metadata:
  name: my-awesome-vsl
  namespace: <NAMESPACE>
spec:
  provider: community.openstack.org/openstack-cinder
  config:
    volumeTimeout: 5m
    snapshotTimeout: 5m
    cloneTimeout: 5m
    backupTimeout: 5m
    imageTimeout: 5m
    ensureDeleted: "true"
    ensureDeletedDelay: 10s
    cascadeDelete: "true"

Then run velero backup with explicitly defined storage location and volume snapshot location. This will ensure that you don't backup using a different configuration (or provider):
velero backup create \
            --namespace velero \
            --include-namespaces default \
            --snapshot-volumes true \
            --storage-location my-awesome-bsl \
            --volume-snapshot-locations my-awesome-vsl \
            --wait

Can you try it this way?
(This example might miss something, I was writing it from my memory)

Ok great I was able to create a few successful backup by :

Being more precise with the command that I use like you mention in your previous command (both are working)

velero backup create test2345678 --include-namespaces=default --snapshot-volumes=true --storage-location=default --volume-snapshot-locations=manila --wait

velero backup create test2345678 --include-namespaces=default --snapshot-volumes=true --storage-location=default --volume-snapshot-locations=cinder --wait

Disabling the initContainers velero-plugin-for-csi and only keep the velero-plugin-for-openstack

initContainers:
  # - name: velero-plugin-for-csi
  #   image: velero/velero-plugin-for-csi:v0.7.0
  #   imagePullPolicy: IfNotPresent
  #   volumeMounts:
  #     - mountPath: /target
  #       name: plugins
  - name: velero-plugin-for-openstack
    image: lirt/velero-plugin-for-openstack:v0.6.0
    imagePullPolicy: IfNotPresent
    volumeMounts:
      - mountPath: /target
        name: plugins

Thanks a lot for your help ! Hopefully it will be able to help other people as well.

Great to hear that.


Query parameter parser fails to parse array parameters correctly

The query parameter parser fails to parse query parameters in array CSV form (e.g. q=1,2,3).
With the following OpenAPI 3.0 parameter definition:
      parameters:
        - name: id
          in: query
          description: ID of the customer to fetch
          required: true
          style: form
          explode: false
          schema:
            type: array
            items:
              type: integer

and with the request ?id=1,2,3
It generates then following error:
SyntaxError: Unexpected token , in JSON at position 1
    at JSON.parse (<anonymous>)
    at parseObject (C:\Users\P772381\Work\cm-ods-api\node_modules\swagger-express-middleware\lib\helpers\json-schema.js:501:24)
    at JsonSchema.parse (C:\Users\P772381\Work\cm-ods-api\node_modules\swagger-express-middleware\lib\helpers\json-schema.js:92:14)
    at parseParameter (C:\Users\P772381\Work\cm-ods-api\node_modules\swagger-express-middleware\lib\param-parser.js:143:35)
    at C:\Users\P772381\Work\cm-ods-api\node_modules\swagger-express-middleware\lib\param-parser.js:35:35
    at Array.forEach (<anonymous>)
    at parseSimpleParams (C:\Users\P772381\Work\cm-ods-api\node_modules\swagger-express-middleware\lib\param-parser.js:30:12)
    at Layer.handle [as handle_request] (C:\Users\P772381\Work\cm-ods-api\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (C:\Users\P772381\Work\cm-ods-api\node_modules\express\lib\router\index.js:317:13)
    at C:\Users\P772381\Work\cm-ods-api\node_modules\express\lib\router\index.js:284:7 status: undefined, toJSON: [Function: errorToJSON] }

The error is a result of the following line: https://github.com/BigstickCarpet/swagger-express-middleware/blob/master/lib/param-parser.js#L35
        req.query[param.name] = parseParameter(param, req.query[param.name], param);

needs to be
        req.query[param.name] = parseParameter(param, req.query[param.name], param.schema);

Is there a plan to fix this? This is a problem not just for the array but any type of path parameter validation. I am trying to parse a simple string id and it is always validating it as an integer ID. the fix above mentioned above works.
Thanks.

Swagger Express Middleware does not support OpenAPI 3.0 yet.  The code that you pointed out above is for OpenAPI 2.0 (fka "Swagger")

Thanks for quick reply. I was trying this out with OpenApi 3 branch.

From: James Messinger<EMAIL_ADDRESS>Sent: Thursday, February 14, 2019 9:11 PM
To: APIDevTools/swagger-express-middleware
Cc: Arvind Agarwal; Comment
Subject: Re: [APIDevTools/swagger-express-middleware] Query parameter parser fails to parse array parameters correctly (#116)
Swagger Express Middleware does not support OpenAPI 3.0 yet. The code that you pointed out above is for OpenAPI 2.0 (fka "Swagger")
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/APIDevTools/swagger-express-middleware/issues/116#issuecomment-463674780, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIDgW-DLvX6005VUw3fzT8F-C-IMbPtuks5vNYOogaJpZM4V08uD.

The OpenAPI 3 branch is not yet working and is in a state of active development. We will notify once it is ready for use.

Thanks for your quick responses. I will look forward to the release.

From: Randall Krauskopf<EMAIL_ADDRESS>Sent: Thursday, February 14, 2019 10:52 PM
To: APIDevTools/swagger-express-middleware
Cc: Arvind Agarwal; Comment
Subject: Re: [APIDevTools/swagger-express-middleware] Query parameter parser fails to parse array parameters correctly (#116)
The OpenAPI 3 branch is not yet working and is in a state of active development. We will notify once it is ready for use.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/APIDevTools/swagger-express-middleware/issues/116#issuecomment-463714087, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIDgW1g10iJQVyA0uQ7VORJ5DbkDIkO4ks5vNZthgaJpZM4V08uD.