feat: add config.operation

Description

This is solving a long standing problem: there isn't a reliable way to distinguish between dev and preview (since config.command === 'serve' for both $ vite dev and $ vite preview).
There are workarounds but none of them are reliable. (E.g. checking whether configureServer()/configurePreviewServer() is called doesn't work in certain situations.)
What is the purpose of this pull request?

[x] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] ~Ideally, include relevant tests that fail without this PR but pass with it.~ N/A.

It's really a shame we can't call this command as it's quite confusing to have command be 'build'|'serve' and they feel a bit swapped. I wonder if we should name this new one cmd and deprecate the old command?

It's really a shame we can't call this command as it's quite confusing to have command be 'build'|'serve' and they feel a bit swapped.

Yes, I couldn't agree more.

I wonder if we should name this new one cmd

👍 Done.

and deprecate the old command?

I think so too. How about we already start showing a warning in the next patch release?

I noticed that this change is a breaking change as it requires users to pass an additional argument to resolveConfig/loadConfigFromFile. We can avoid that by making the argument optional, but I fear that would lead to a same situation with configEnv.ssrBuild (https://github.com/vitejs/vite/discussions/13809#:~:text=An issue with,is no usage).

We discussed about this in the meeting today. To minimize the changes, and since the main usecase is to only differentiate dev and preview, we think passing a isPreview property to ConfigEnv (the second param of the config hook) should be enough for now. resolveConfig can accept a new parameter to pass in the isPreview value.
This would make it work similar to the ssrBuild value today. ssrBuild is used to differentiate what kind of build is running, and isPreview would be used to differentiate what kind of server is running.

Neat, good idea. I'll try to update the PR later today.

@brillout I've already opened a PR 😬 https://github.com/vitejs/vite/pull/14855
I forgot to credit you as a co-author for kicking this off though. Let me send a comment there so we do so before merging.

Neat. No need for credits.


Feature/add campaign suppression list history var

Pull Request
Are you a current Fivetran customer?

Internal
What change(s) does this PR introduce?

Add a variable iterable__using_campaign_suppression_list_history to disable stg_iterable__campaign_suppression_list_history if source table is not being used
Did you update the CHANGELOG?

[x] Yes

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[x] No  (please provide an explanation as to how the change is non-breaking below.)
Adding a variable for disabling a model
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

[x] Yes

Is this PR in response to a previously created Bug or Feature Request

[x] Yes, Issue/Feature (https://github.com/fivetran/dbt_iterable/issues/19)
[ ] No

How did you test the PR changes?

[x] CircleCi
[ ] Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

[x] BigQuery
[x] Redshift
[x] Snowflake
[x] Postgres
[ ] Databricks
[ ] Other (provide details below)

Provide an emoji that best describes your current mood

:dancer:
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

LGTM!


My library uses your library!

First off, thanks for the backport and simplification of Nicks amazing work.
Secondly, I'll make another PR to update the icon, but for now it's just the sample one.
Link to my lib: https://github.com/Vexigon/Material-Onboarding

Thank you! Great work! Don't forget to update the icon.


Disable smp on esp32c6

These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

I believe all issues on this PR have been resolved and this should be mergeable

Feedback goes beyond this PR, but I wonder if further code changes are need for c6 support.
code search for the (similar?) esp32c3 yields:
sys.c get_model?


Make serde serialize enum variants as snake_case

What problem does this solve or what need does it fill?
This is not a huge issue, but when making a TOML or JSON file that use KeyCodes as values, it's annoying to see CamelCase.
Compare TOML:
[[profile.action]]
event = "run"
digital = "LShift"

to
[[profile.action]]
event = "run"
digital = "l_shift"

And JSON:
{
  "profile": {
    "action": [
      {
        "event": "run",
        "digital": "LShift"
      }
    ]
  }
}

to
{
  "profile": {
    "action": [
      {
        "event": "run",
        "digital": "l_shift"
      }
    ]
  }
}

It just looks more consistent with the rest of the data.
What solution would you like?
Just change #[cfg_attr(feature = "serialize", derive(serde::Serialize, serde::Deserialize))] to #[cfg_attr(feature = "serialize", derive(serde::Serialize, serde::Deserialize), serde(rename_all = "snake_case"))] and serde will do it automatically.
What alternative(s) have you considered?
I could try to use a huge match statement with another enum that does convert fields to snake_case, but that would stupid way of doing it compared to just putting this in.
Additional context
I can make a pull request; I just wanted to make sure that people approve of this change.

I also wouldn't just be updating KeyCode. I think all serializable types with CamelCase fields should get this treatment, so all enums.

Did you mean kebab-case (as in your code), or should the code actually read l_shift?
To be honest, especially in this case I am happy about the uppercase L, because it makes it easier to read (I easily confuse l and I, but when it's L and I then it's clear)
Also, according to the official Rust naming conventions enums should be CamelCase, and when serializing an enum value, keeping the enum notion keeps the consistency with the guide and the code, so for me the CamelCase looks good...

Fixed that, sorry for the confusion, I was using kebab-case first, but changed it to snake_case. Guess I missed that with the example I copied at 3;30 AM...
I think the Rust naming conventions are great for Rust, but for a data format, you don't see the names of structs, so fields often act like them, and field names are in snake_case. To make it look consistent, enum variants, which we do see, should be snake_case as well.
Here is a better example to compare (can't do it in TOML, since externally tagged enum variant structs don't work):
{
  "Hello":
    {
      "x" : 5
    }
}

to
{
  "hello":
    {
      "x" : 5
    }
}

If the enum variant (Something::Hello in this case) wasn't unit-like, it would be the key for some value, and that would be inconsistent with the rest of the document. I rest my case. ;)

CamelCase doesn't bother me personally and it has a number of benefits:

1-1 parity with the rust types, making it easier for users to mentally map between configured values and the rust types
Default: we are consistent by default for all of our types, no need to override defaults for very serde derive
Provides a visual distinction between "field names" and "value / type names"
I agree that L is clearer than l

Alright, I'll close this then. 👍


How to start?

I have cloned your project but I am unable to start it. Can you please provide proper guideline step by step on how to run your project on Windows based computer using XAMPP?
Thank you.
-Saeed

Hi @zaisahil, the project is still in a WIP state right now, the main missing part being the UI (we proxy the call to our legacy WMS to provide the UI).
I'll do my best to provide you with some guideline to help you have it running, but be aware that it is not entirely user friendly yet.

Thanks for the reply @dav-m85.
Well, I hope UI will be completed soon.
I will wait for your guidelines.
-Saeed


Promote OME2021 meeting event

As discussed this morning this makes the community event page more accessible via a new entry in the events page as well as a top-level banner

I kind of like the banner which was put up for the OME 2020 https://user-images.githubusercontent.com/1644105/78772246-6201ff80-7989-11ea-841b-5c9fc9eb3761.png - it attracts much better the attention. It was established in the PR https://github.com/ome/www.openmicroscopy.org/pull/352
At first look, when I built the present PR, https://snoopycrimecop.github.io/www.openmicroscopy.org/ I thought the red line on the top is the old SV announcement (it always used to be SV).
Maybe we could consider to rewrite the https://github.com/ome/www.openmicroscopy.org/pull/352 commits so that we have a better banner such as last year ?
Present state

Last commits deployed at https://snoopycrimecop.github.io/www.openmicroscopy.org/

@sbesson thank you. LGTM.

Thanks @pwalczysko. Tagging and deploying to start linking to the programme and we will start filling speakers in the upcoming days.


Make tests support Windows

Running the tests on Windows 10 fail, since there are some hard-coded values (eg. the path of ffmpeg).

Might as well add an .npmignore as well


Make independent of OpenCV

I decided to freeze this repository, but leaving issues is uncomfortable.
So I bury this.


Box not working anymore

Greetings from your former working colleagues of HTB.
Hope you are doing fine.
We would have a request about the Kudos-Box you once created for the Team Code-Black.
Looks like it is not working anymore for a few weeks. Would you do us the favor to check why the box is not working anymore?
We love to use it and it would be nice to have it back again :)
Thanks

Hi Michael, sorry for the inconveniences! I made some security improvements for a while and as you already noticed, also introduced a bug. But I have fixed it here and you should be able to use your box again.
Greets to the HTB colleagues!

Thanks for the quick fix, we are happy to have the kudos box back :)
Wish you all the best


Iframe is showing as code not rendering the video

File: get-started/index.md
https://docs.docker.com/get-started/#what-is-a-container
This Iframe is showed as code but I think it should display a video on page.

Thanks for reporting; this is fixed in https://github.com/docker/docker.github.io/pull/11984

Thanks for reporting; this is fixed in https://github.com/docker/docker.github.io/pull/11984


Python commands to launch tensorboard is still showing up even when the Tensorboard extension is installed

With the new update the Tensorboard extension is installed as expected! The weird thing is that now both commands are showing up:

Running the one from the Python extension fails:

After it's run, it seems to disappear and only the Tensorboard one shows up:

Originally posted by @luabud in https://github.com/microsoft/vscode-jupyter/issues/14557#issuecomment-1783252926

Unfortunately not much we can do here, as both extensions contribute this.
Once Python extension removes this command this should not be an issue.
Closing as not planned


Updating plugin from jenkins

Problem:
Recently you added server jar updater with jenkins support, but plugins can only be updated from bukkit and spigot.
Solution:
You could add very similar updater to server jenkins updater but for plugins by adding similar configuration to each plugin, useful for plugin beta build etc.

Oh if I would implement that a single plugins config in the plugins-config.yml would look like this:
  WorldBorder:
    exclude: false
    version: 1.9.10 (beta)
    latest-version:
    author: Brettflan
    spigot-id: 60905
    bukkit-id: 0
    custom-author:
    custom-check-url:
    custom-download-url:
    jenkins-projekt-url: https://some url
    jenkins-artifact-name: the artifact name
    jenkins-artifact-name-similarity: 70
    jenkins-build-id: 0

As you can see its getting pretty long and I don't think that It would affect and be useful for many plugins, because if they got a jenkins server they usually also update their plugins on spigot?
What do you say?

not big deal, you can make it optional so by default not set at all (you can add a comment above the file that shows you example configuration with jenkins

true, I will really welcome this feature

Now available in 5.5


Run go mod tidy to prune the old go-github version from go.mod and go.sum

We recently upgraded our go-github version, but because I forgot to run
go mod tidy, the old version was still present in go.mod
Sorry about the PR spam!

@jhrozek right, it's because nobody did it.


Parallel FaIR

See #42

[x] Verify that this method is indeed faster
[x] Description in CHANGELOG.rst added (single line such as: (`#XX <https://github.com/openscm/openscm-runner/pull/XX>`_) Added feature which does something)

A nice to have would be an option to allow the user to select the number of parallel processes. The default is set to the machine maximum minus 1 so that you can still check Facebook while this is running.

I presume the reason these tests are failing is that I don't have the MAGICC binary. All the FaIR ones are passing.

For me locally this runs 2237 configs for 8 scenarios in less than 3 minutes. If this scales it would do 1600 WG3 scenarios in 10 hours. I've spent a day to save three. I feel like a champion.

See #42

Closes #42 ?

I've spent a day to save three. I feel like a champion.

That is a big immediate return on investment!

I presume the reason these tests are failing is that I don't have the MAGICC binary. All the FaIR ones are passing.

It's failing on test coverage. I'll make a PR with a suggested way to pass in config and that should fix that too.

It's failing on test coverage. I'll make a PR with a suggested way to pass in config and that should fix that too.

Nice. Yep I couldn't figure out why - very little had changed and coverage was down to about 58%. But for me all of the MAGICC tests were failing.

Yep I couldn't figure out why - very little had changed and coverage was down to about 58%. But for me all of the MAGICC tests were failing.

FYI all the magicc code isn't included in coverage (see .coveragerc)

(if you want me to cut a release, let me know)

I'll add tests to #40 as suggested and if these two PRs can be rolled into a release then that would be grand

https://pypi.org/project/openscm-runner/


dimension separator in netcdf-zarr

found in the depths of the source...

This is a really nice hack that we should definitely document somewhere! I was just wondering about the scope of this page? Is it meant to be a general introduction to HEALPix (then the info might be a bit too niche), or is it meant to evolve into a tutorial for technical support at various nodes?

It's a bit of info for the tech support teams, so they can start playing with HEALPix.
Similar for the catalogs.
Not totally sure how far we want to take these things, though.
We could also take them to easy.gems and simply link them, as this is likely to stay a site for one hackathon...

I've also passed it on to Uwe Schulzweida.


[2.0.0-beta.1] Source map is incorrect

The source map node_modules/react-quill/lib/index.js.map references a source of ../src/index.tsx, but sources aren't included in the release. Either the source map generation needs to be configured to inline the source into the map, or the source needs to be included in the release.

Sources are now inlined in the source map. A new beta release will come soon.


Combine boolean evaluation _HT? with get _HT* and  include _HT/ transformations

State
When using _HT? the conditional expression must be written in native Go Templating syntax making it unconvenient to access fields or use includes in a short form
Feature Idea
Combine _HT? with _HT* and _HT/ so that a shorter form is sufficient to write the condition.
Alternative 1: Combine symbols like _HT?* and _HT?/
Alternative 2: Combine expressions like _HT?_HT* and _HT?_HT/
In both variants, it must be detected that the condition is a HULL transformation and not a Go templating expression. The HULL transformation must be executed and the result subjected to the boolean check.

It is now possible to combine _HT? with includes by using _HT?/ prefix. If the include returns literal true or false the result is treated as a boolean value making it suitable for checks.
For _HT?* the requirement is sufficiently satisfied with the ability to use _HT* references within _HT! and _HT? template code now. If the content of the _HT? check is only the evaluation of a reference to a boolean field this already works by directly addressing the field using _HT* since _HT* returns the correct type.


Issue with SwiftyJSON when parsing JSON with unicode characters

http://stackoverflow.com/questions/32322881/issue-with-swiftyjson-when-parsing-json-with-unicode-characters

Are you sure? This works for me using your json.
import UIKit
import SwiftyJSON
import XCPlayground

let jsonPath = NSBundle.mainBundle().pathForResource("test", ofType: "json")

if let jsonData = NSData(contentsOfFile: jsonPath!) {
  let json = JSON(data: jsonData)
  print(json["count"]) //prints 2
}

Hi Tom, thanks for your reply. So, it works fine when reading from a file, however when retrieving the same data via a REST API (in this case Spree), I get the error.
If you don’t mind please try : http://eastereggs.mysimplestore.com/api/taxonomies/1/taxons
From:  Tom Clark
Reply-To:  SwiftyJSON/SwiftyJSON
Date:  Friday, September 4, 2015 at 3:33 AM
To:  SwiftyJSON/SwiftyJSON
Cc:  dudeinthemirror
Subject:  Re: [SwiftyJSON] Issue with SwiftyJSON when parsing JSON with unicode characters (#318)
Are you sure? This works for me using your json.
import UIKit
import SwiftyJSON
import XCPlayground
let jsonPath = NSBundle.mainBundle().pathForResource("test", ofType: "json")
if let jsonData = NSData(contentsOfFile: jsonPath!) {
let json = JSON(data: jsonData)
print(json["count"]) //prints 2
}
—
Reply to this email directly or view it on GitHub.

This is what I get when I use the url. Maybe I'm missing something more specific to what your'e trying to do?

I am using Alamofire to get the data. So, it looks like there is something funky going on somewhere between getting the json back and parsing. Closing this for now, it's clear it's not a SwiftyJSON issue. Thanks for your help Tom !

No worries man. Let me know if you need any more help.


Could you test TimeChat on the EgoShema dataset?

Hello!
I have been following the development of the TimeChat model and its application in long video processing. I understand that EgoShema serves as a crucial benchmark for evaluating long video question-answering (QA) systems. Considering the significance of EgoShema in the field, I would like to inquire whether there are plans to test the TimeChat model on the EgoShema dataset.
Testing the TimeChat model on EgoShema would not only provide valuable insights into its performance but also enable a comparative analysis with other long video QA models. I believe such evaluation would be greatly beneficial to the research community and further enhance the understanding of the TimeChat model's capabilities.

Hi, thanks for your interest.
We have conducted evaluation on some benchmarks (MVBench, TempCompass, see https://github.com/RenShuhuai-Andy/TimeChat/blob/master/docs/EVAL.md). The results on EgoShema will be added recently.

The accuracy of TimeChat-7b on EgoShema is 33%, see https://github.com/RenShuhuai-Andy/TimeChat/blob/master/docs/EVAL.md#egoschema


Relative source paths in debug info

Hi,
I happens that, in some build systems/configurations, a binary can end up with relative paths to source files in the debug info in the binary.  This can happen in some cases when building a C++ program with CMake+Ninja (and currently this behavior is not easy to workaround in general).  Then, if the program is run in a different directory then backward-cpp will not be able to locate the source files and so the stack trace will not contain snippets.
I propose allowing the user to specify an optional path prefix that backward-cpp will use when searching for source files using the following algorithm in the SourceFile class:

If the source file path is absolute, just open it as-is.
If the path is relative then first try to open it as-is; if this fails, and if there is a user-specified prefix, prepend the prefix to the filename and retry opening the file.

The prefix could be specified through an environment variable BACKWARD_CPP_SRC_PREFIX, how does that sound?  If it sounds OK, then I can submit a PR for it.  Also open to other suggestions.

I would suggest maybe using the user defined prefix first? Or, better yet,
make it a list of path. "./" would simply means relative to the cwd. But
then cwd can change... therefore one would like to use the binary itself as
the reference path. But wait it could be a symlink... no nice solution here
On Tue, Dec 24, 2019, 12:18 David P. Sicilia<EMAIL_ADDRESS>wrote:

Hi,
I happens that, in some build systems/configurations, a binary can end up
with relative paths to source files in the debug info in the binary. This
can happen in some cases when building a C++ program with CMake+Ninja (and
currently this behavior is not easy to workaround in general). Then, if the
program is run in a different directory then backward-cpp will not be
able to locate the source files and so the stack trace will not contain
snippets.
I propose allowing the user to specify an optional path prefix that
backward-cpp will use when searching for source files using the following
algorithm in the SourceFile class:

If the source file path is absolute, just open it as-is.
If the path is relative then first try to open it as-is; if this
fails, and if there is a user-specified prefix, prepend the prefix to the
filename and retry opening the file.

The prefix could be specified through an environment variable
BACKWARD_CPP_SRC_PREFIX, how does that sound? If it sounds OK, then I can
submit a PR for it. Also open to other suggestions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bombela/backward-cpp/issues/153?email_source=notifications&email_token=AABUZDH7XIVYA3TYGARZTFLQ2JVAPA5CNFSM4J7ASWGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICRMC4A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUZDHPPJKOAFUMOTVX5NLQ2JVAPANCNFSM4J7ASWGA
.

Right originally I thought about using binary path (since that would work for my use case), but actually, you are correct that that would introduce complications with symlinks, and platform dependence issues.  So perhaps we should avoid using binary path.
How about this algorithm then:

If environment variable is non-empty, then assume it has a list of paths separated by colons, e.g.:

        BACKWARD_CPP_SRC_PREFIX=/a/b/c:/d/e/f

Try each path prefix until a valid file is found.
2. If no valid file is found, then fall back to current (unaltered) path.
Thanks

yeah that seems to be the best compromise. it's predictible!
On Tue, Dec 24, 2019, 12:55 David P. Sicilia<EMAIL_ADDRESS>wrote:

Right originally I thought about using binary path (since that would work
for my use case), but actually, you are correct that that would introduce
complications with symlinks, and platform dependence issues. So perhaps we
should avoid using binary path.
How about this algorithm then:

If environment variable is non-empty, then assume it has a list of
paths separated by colons, e.g.:
BACKWARD_CPP_SRC_PREFIX=/a/b/c:/d/e/f

Try each path prefix until a valid file is found.
2. If no valid file is found, then fall back to current (unaltered) path.
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bombela/backward-cpp/issues/153?email_source=notifications&email_token=AABUZDE3PWL6EB4ECCYP3H3Q2JZMRA5CNFSM4J7ASWGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTTRFY#issuecomment-568801431,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUZDHHGMSBYRDKLKAW5KLQ2JZMRANCNFSM4J7ASWGA
.

Shall I submit a PR for this then?

Yes please! I believe you should be able to handle everything in the
"snippet" thingy.
On Tue, Dec 24, 2019, 13:17 David P. Sicilia<EMAIL_ADDRESS>wrote:

Shall I submit a PR for this then?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bombela/backward-cpp/issues/153?email_source=notifications&email_token=AABUZDHQY45LBDZ4TTGH4XDQ2J37HA5CNFSM4J7ASWGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTT6NA#issuecomment-568803124,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUZDAGSXHI5FIQDBL5NBDQ2J37HANCNFSM4J7ASWGA
.

@bombela I have submitted PR #154, please take a look.  Thanks

@bombela Could you take a look at PR #154 which should fix this?  Thanks


Wallbox can not created anymore after update to 0.127.0

Describe the bug
After the Update to 0.127.0 evcc is not starting anymore.
I have two Ellipro Wallboxes that have worked fine bevor the update to 0.127.0
Steps to reproduce

Starting evcc

...
Configuration details
chargers:
- type: template
  template: ellipro
  ski: ********
  IP: ********
  name: wallbox5

Log details
Using config file: /config/evcc/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc/evcc.yaml'
[main  ] INFO 2024/06/13 21:48:26 evcc 0.127.0
[main  ] INFO 2024/06/13 21:48:26 using config file: /config/evcc/evcc.yaml
[db    ] INFO 2024/06/13 21:48:26 using sqlite database: /data/evcc.db
[main  ] INFO 2024/06/13 21:48:26 listening at :7070
[main  ] FATAL 2024/06/13 21:48:26 cannot create charger 'wallbox5': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main  ] FATAL 2024/06/13 21:48:26 will attempt restart in: 15m0s

What type of operating system are you running?
HomeAssistant Add-on
Version
0.127.0

After downgrading to 0.126.6 everything works fine again

Same issue again with 0.128.0


how to make different request code in every call of image picker

i need to implement 4 image picker with different request code for activity result can you help me

@reizamv You can specify the request code with the ImagePicker start method


Grafana 9 support

Ref #20087.
Fixes:
Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

I ended up merging https://github.com/zulip/zulip/pull/22882 for this issue; I think it's very possible that some further improvements to formatting would be worth doing, but that one is finished, and it's better to have a working integration than not.


HDDS-5808. Update commons-io to 2.11.0

What changes were proposed in this pull request?
Update commons-io to 2.11.0.
https://issues.apache.org/jira/browse/HDDS-5808
How was this patch tested?
Regular CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/1304376420
$ mvn -DskipTests -Dskip.installnpx -Dskip.npx -DskipShade clean package
$ find hadoop-ozone/dist/target/ozone* -name 'commons-io*jar'
hadoop-ozone/dist/target/ozone-1.2.0-SNAPSHOT/share/ozone/lib/commons-io-2.11.0.jar

Thanks @ayushtkn for the review.


watchOS Support

Is there any particular reason why watchOS is not currently supported?

Well, I was asking this to get a read before investing time into putting together a PR, but I ended up just starting on it anyway, and now I've got it mostly done.
One thing I'm a little unsure of is .gyb file, which looks like it's used to actually generate the swift file.  Right now I've got all my changes in the swift directly, and can try porting them out into the gyb, but

I wanted to make sure that's still how you are maintaining this project, and
I was curious if there are any docs for this workflow (I didn't see any in the repo).

I'm also curious whether you view it as a significant timesaver. Looking at the line lengths, there doesn't seem to be that much less code in the gyb, and there are now two files to maintain, so I was just wondering if you still find it to be impactful.
Thanks!

Hello! I currently require DeviceKit to support watchOS as well. Wondering if I can help in any way. I am also unsure how to effectively use the ‘gyb’ but I’m always willing to learn to be able to contribute to this amazing project!

Hi @serjooo,
That's great!
Basically, at the top of the gyb file is a large python array of all the devices we support (or one array for each "device group", i.e. iPhone, iPad, HomePod, Apple TV, etc., watch would be another one of those categories).
In these arrays we maintain all the data we support, and later, in the swifty part of the file we reference those tables.
It's basically a very powerful pre-processor.
Every line that starts with a % is python code (mostly for loops) that iterate over the stuff inside of them, e.g.
% for device in iOSDevices:
    /// ${device.comment}
    ///
    /// ![Image](${device.imageURL})
    case ${device.caseName}
% end

loops over all iOSDevices (which is one of those variables defined at the top) and generates for each of the array elements the code between the python-line-indicating % symbols. This means we don't have to list all of the devices manually (and forget images, etc.) but can conveniently use the information we collected in one central place (you guessed it: at the top :)).
Inside lines that do not start with % you can still use values of the variables you defined, this is what happens in lines 2 and 4. with ${variable} - we get the value of the comment field on the device variable (which, in this case, is our local loop variable) and gyb automatically inserts the value of that field as text in that position.
Let's assume our iOSDevices array contains Devices for iPad 2 and iPad 3. This is what would get generated:

/// Device is an [iPad 2](https://support.apple.com/kb/SP622)
///
/// ![Image](https://support.apple.com/library/APPLE/APPLECARE_ALLGEOS/SP622/SP622_01-ipad2-mul.png)
case iPad2
/// Device is an [iPad (3rd generation)](https://support.apple.com/kb/SP647)
///
/// ![Image](https://support.apple.com/library/APPLE/APPLECARE_ALLGEOS/SP662/sp662_ipad-4th-gen_color.jpg)
case iPad3

It's important to note that gyb does not at all care what it generates :) It's not restricted to Swift code or anything programming related - you can use it everywhere you want it to (g)enerate (y)our (b)oilerplate :)
This is just a very brief overview, I hope that helps a bit, if you need more help do not hesitate, I love that you all use the project and even want to contribute back, so I'm here to help! :)
Thank you!

Okay, so now i'm picking this up because I need DeviceKit in Home Assistant for watchOS :)
Here's the first issue, hopefully the last. How do we handle all the different combinations of features? Apple seems to have unique pages for each style (Apple Watch 1st generation Sport, Apple Watch 1st generation Stainless, Hermes, etc etc). The 38mm is identified as WatchX,1 and the 42mm is identified as WatchX,2 (where X is the generation number).
I can add individual devices for every combination but that seems like a bit much. I can combine some combinations together (such as representing Sport, Nike, Stainless as one) but split by size and for Series 3+, WiFi or LTE.
Actually, writing this out has made me choose to do the latter. So the devices i'm adding will look like this (formatted for easier reading on GitHub):
Device(
"appleWatchSeries0_38mm",
"Device is an [Apple Watch (1st generation)](https://support.apple.com/kb/sp736)",
"https://support.apple.com/library/content/dam/edam/applecare/images/en_US/applewatch/watch-38mm-silver-alum.png",
["Watch1,1"], 1.5, (4,5), "Apple Watch (1st generation) 38mm", 303, False, False, False, False, False, False)

Is that acceptable? So one device per screen size and connectivity type.
Let me know @dennisweissmann!

Hi Robbie, thanks for tackling this! Awesome! That said I don’t like 0_38 too much :( it doesn’t look very nice, what would you think about .appleWatch(series: Int, size: Int). WiFi and LTE could be a property (which we could also support for iPods/iPads. Since you need it, would you code at the call site be nice and easy to understand that way? Or should we stay consistent with the iPhones and put the series in the name (now that I think about it that’s probably better, so appleWatchSeriesX(size: Int). What do you think? Is that workable at the call-site or would you prefer completely different cases for each size?

I understand the annoyance about 0_38. The reason I chose that is because Apple seems to think of the 38/40mm and 42/44mm devices as standalone from one another, as evidenced by WatchX,1 and WatchX,2 and different support spec pages.
I think it would be good to keep Series in the name. We have iPhone 3, 4, 5, why not Watch 1, 2, 3. Apple calls the very first released Watch "Apple Watch (1st generation)" but many people outside of Apple call it Series 0. Is Series 0 acceptable?

@dennisweissmann I've pushed my initial work that still uses _38mm, _42mm, etc. I'm somewhat unsure of how to implement your suggested method, I thought I got it at the time but I guess not. If you could provide a bit of a larger example on how to implement it, I can get it done! In the meantime, there's a PR for everyone to poke at 😄

@dennisweissmann Another note, I set minimum SDK to 4.0 for watchOS. We could probably go lower, maybe even to 1, but wasn't sure what your policy is...

Sorry for the delay, if we could go lower that would be great, we can go with @available annotations for functions which are not available in older SDKs, does that make sense?

@dennisweissmann Yep! I'll get that taken care of within the next 24 hours

Thank you :) Take whatever time you need, I really appreciate your contribution!

@dennisweissmann Just pushed a commit to allow use on watchOS 2.0 by only exposing battery state on 4.0 and above.
There's still my outstanding comment here that I could use your help on.

That’s great, sorry for the delays ... I’ll get to a computer and take a look, regarding the function you thought you got but didn’t: I’m not sure what you mean :D which function are we talking about? 🙈

I was talking about your suggestion of instead of doing _38 and _42 instead something like appleWatchSeriesX(size: Int). I'm unsure how to implement that in the gyb.

Woohoo!!! 🎉


logs command: line break issue

hey guys, looks like there's an issue with rancher-compose logs command, as it doesn't respect line breaks (at least for Mac OS X), so all the output just goes into one line.
To reproduce:

spin up new service using rancher-compose up
run rancher-compose logs and see output

Fixed in https://github.com/rancherio/rancher-compose/pull/30

Verified fixed in Linux and Mac OS X with rancher-compose v0.1.3.
@sheng-liang Could you test in Windows?


CookieManager.set(expires_at=) default value issue

Hi, thanks for your nice Streamlit add-ons.
When I use the cookie manager component, I find an issue.
https://github.com/Mohamed-512/Extra-Streamlit-Components/blob/596d088a30806a5273a0ae97b11de08a3e26c683/extra_streamlit_components/CookieManager/__init__.py#L24
Based on the Python behavior, the default value of expires_at will always be the Steamlit app started time but not the function called time, which means one day after the Steamlit app started, I won't be able to set the cookie without giving the expires_at because the default expires_at time will be earlier than the current time.
I'm not sure it's an intentionally designed mechanism or a bug.
Thank you.

It's a bug, great catch! You can update to version 0.1.55 for the fix.


media_player/webostv component exceptions while TV is off

Make sure you run the latest version before reporting an issue. Feature requests should go in the forum: https://community.home-assistant.io/c/feature-requests
Home Assistant release (hass --version):
0.19.4
Python release (python3 --version):
3.5.1
Component/platform:
media_player/webostv
Description of problem:
Exception thrown while TV is off
Expected:
No exception
Problem-relevant configuration.yaml entries and steps to reproduce:
media_player:
  platform: webostv
  name: Living Room TV
  host: <IP_ADDRESS>

Pair WebOSTV with HA
Start HA with TV either off or on
Switch off TV via HA or TV remote

Traceback (if applicable):
ERROR:homeassistant.core:BusHandler:Exception doing job
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py", line 801, in job_handler
    func(arg)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/helpers/event.py", line 179, in pattern_time_change_listener
    action(now)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py", line 180, in _update_entity_states
    entity.update_ha_state(True)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 164, in update_ha_state
    self._attr_setter('entity_picture', str, ATTR_ENTITY_PICTURE, attr)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 191, in _attr_setter
    value = getattr(self, name)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/media_player/__init__.py", line 618, in entity_picture
    return None if self.state == STATE_OFF else self.media_image_url
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/media_player/webostv.py", line 202, in media_image_url
    return self._app_list[self._current_source_id]['icon']
TypeError: 'NoneType' object is not subscriptable

Additional info:
Not sure whether this is responsible for not being able to switch on the TV through HA. I can turn off the TV through HA but not on.

The fact that you cant turn it on is expected. There's no support implemented for turning the a webostv on.

I've written a custom compontent which extends the WebOSTV class and implements turn on. Most LG TVs have a serial port you can access using a raspi and you can use that to turn on the television when it is off (additionally exposes other actions as well)

I suggest that you open a feature request in the forum.


Schema issue template

Description
Add an issues template for schema changes. Give contributors an understanding of what we're looking for.
QA steps
No complicated QA is needed, maybe wording could be checked. Also in the Files Changed section, there's a View File button in the top right ... menu for individual files, which is useful to see what the Gİthub form will look like.

What do you think about adding a field/checked box/label (?)  to make it clear that changes an existing one? Since this could have more impact/breaking changes than adding a new one.


Implement uniq in terms of uniqWith

Removes repetition.
With equivalent benefits this could easily be done for other functions with *With equivalents as well.

i think this was a performance optimization way back when. did you bench this to see what effect this change may have?

All of the functions with *With variants are implemented in this way. Why
would that give  better performance?
On 14 Apr 2015 15:35, "Michael Hurley"<EMAIL_ADDRESS>wrote:

i think this was a performance optimization way back when. did you bench
this to see what effect this change may have?
—
Reply to this email directly or view it on GitHub
https://github.com/ramda/ramda/pull/1026#issuecomment-92840895.

https://github.com/ramda/ramda/issues/183

I truly don't understand why the performance difference is so significant. But I can't argue with the benchmarks.
Here is an updated benchmark. There's and added test that shows that R.eq is part of the reason. Also note that in Firefox R.uniqWith(function(a, b) { return a === b; }); is twice as fast as R.uniq!

:+1: from me. :)

let's do it, if it needs optimizing later we can circle back
:cow2:

I agree. uniqWith is exposed to users. If its not good enough for us then I think the issue is in uniqWith  and a stab should be taken at optimizing it instead of not using internally.

POITROAE. Should it ever arise that we need to improve perf here, we have some possible optimizations in our back pocket.

I guess I'm on board.  It would certainly be nice to have simpler code.  And we know that if we want to speed this up, it's not uniqWith that's the issue.  It would be easy enough to do this with a lambda.

problem is our eq is different than simple ===, since it handles -0 and NaN

Yes, but if we needed to change from we could inline that and save the function call and probably not take too bad a performance hit:
var uniqWith = uniq((a, b) =>   (a === 0 ? (1 / a === 1 / b) : (a === b || (a != a && b != b)));

or some such, although this is clearly not as DRY as we would like.

agreed, i was just noting that it should not be a simple a === b lambda


WIP Adds EEC diagnostic logs to support_archive package

K8S-10826
Description
Adds EEC diagnostic files to the support_archive package if Prometheus feature is enabled and files exist.
How can this be tested?
Deploy dynakube with Prometheus feature enabled and disabled.
Execute the support-archive command :
kubectl exec -n dynatrace deployment/dynatrace-operator -- dynatrace-operator support-archive --stdout > operator-support-archive.zip

Compare contents of zip packages.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 101 lines in your changes missing coverage. Please review.

Project coverage is 64.23%. Comparing base (bb0cfaf) to head (ad3337b).

Files
Patch %
Lines

cmd/support_archive/eecDiagLogs.go
0.00%
100 Missing :warning:

cmd/support_archive/builder.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3602      +/-   ##
==========================================
- Coverage   64.54%   64.23%   -0.31%
==========================================
  Files         399      400       +1
  Lines       21405    21506     +101
==========================================
  Hits        13815    13815
- Misses       6265     6366     +101
  Partials     1325     1325

Flag
Coverage Δ

unittests
64.23% <0.00%> (-0.31%)
:arrow_down:

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

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


Option to disable 'All items are selected.' text

I would like to be able to disable the 'All items are selected' text in the header, and always use the comma-separated list that is normally used.

Discovered the valueRenderer prop while reading the source code, which does the trick as well. Might be good to add this to documentation?

Hi @Jipperism,
Thanks for the suggestion, I have updated documentation for the same


Update ReadMe file with setup instructions

Once the basic React app is ready, update the ReadMe file with instructions on how to run the app locally.
Basic steps like:

Install node
clone the repo
Go inside the folder
Run "npm install" and "npm start"
Should be enough.

completed. I used some basic syntax to edit the readme file.


Variable not in scope: main when using other-modules and --test=:main

I have a cabal file that looks as follows:
test-suite my-test
  hs-source-dirs: test
  main-is: test.hs

  other-modules: SomeModuleUsedInTest

If I try to run:
ghcid -c  \"cabal new-repl my-test\" --test=:main"

The I get the following error:
<interactive>:23:53-56: error:
    • Variable not in scope: main :: IO a0
    • Perhaps you meant ‘min’ (imported from Prelude)

By removing the other-modules everything works again.
Any idea what might be causing this behaviour?

If you do cabal new-repl my-test and then type :main what happens? I'd try getting ghcid out of the picture first.

*Ledger.Delegation.Examples> :main
:1:53: error:
• Variable not in scope: main :: IO a0
• Perhaps you meant ‘min’ (imported from Prelude)
*Ledger.Delegation.Examples>

So it seems this might be a problem with cabal which doesn't bring Main into scope...

No idea I'm afraid. I stick to a .ghci in each repo as that's the simplest solution for me.


Scrollbar on table widget covers data

Screenshot of the issue below. I can fix it by dragging the table to be wider, but it would be nice to have the default width be a bit larger

@benmccann can you see if this issue still exists? In current master I get this:

@LeeTZ that scroll position could be tricky. Would have to analyse how phosphor/datagrid we are extending is handling that.
How should it look?
Horizontal scroll bar should be moved right by the width of left header.
Vertical scroll bar should be moved down by the height of top header.
How should the empty space we introduce this way look?

Ok, great. I will trust that it's fixed then
I was thinking that it could be nice to align the top of the scrollbar like the below image. I photoshopped your screenshot to demonstrate. See the top-right corner of the table

@LeeTZ close this issue please


fix($parse): allow watching object/array literals

This moves the object/array-literal watching logic from $compile to $parse so it can by used by watchers anywhere (not only bindings).
By moving this to $parse we can potentially improve it more. Maybe pushing the equals check into expressionInputDirtyCheck for literals, then we can avoid creating the object and avoid calling equals on the full object each digest?
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
bug fix
What is the current behavior? (You can also link to an open issue here)
watching object/array literals throws infdig if any inputs are non-simple values
What is the new behavior (if this is a feature change)?
watching object/array literals does what compile previously did to solve this
Does this PR introduce a breaking change?
no
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

This sounds more like a feature than a fix.

I wonder how much people would abuse this, without realizing it is inefficient :)

I think this is a fix because today $watch("{foo: bar}") works sometimes but not others. Basically if bar is a simple value it works, but as soon as bar becomes an object of any type it breaks.
That said... I think I would prefer a BC where we stop using equals for literals and instead use $watchGroup.  So $watch("{a: x, b: y}") would essentially be $watchGroup(["x", "y"]) instead of a deep watch like today.  This would improve performance when those objects are large and also stop invoking the watcher just because a child property (that we might not care about) changed.

It still feels more like a feature to me. It is ony by chance that "shallow" literals started working at some point. :smiley:
LGTM (but it would be good for someone else to take a look as well)

I think I'd actually prefer to close this in favour of only doing #15301 in 1.7.
This PR makes literals consistent by expanding the deep-equals functionality of one-way-bindings to all watched literals. Where #15301 makes literals consistent by removing the deep-equals and instead (simple) watching only the variables within the literal. So we probably shouldn't expand the use of deep-equals if we plan to land #15301 and remove it...

Works for me. Feel free to go ahead and close this in favor of #15301.

Closing then... also note that I think the first commit in #15301 could go into 1.6, but I'll comment on that there...


Runtime.tv support

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and am willing to share it if required

Region
United states
Example URLs

Single episode: https://www.runtime.tv/es/shows/jack-hunter/season/1/episode/3
Entire series: https://www.runtime.tv/es/shows/jack-hunter

Provide a description that is worded well enough to be understood
Yt-dlp cannot extract video or audio from the website in question, even with the generic extractor.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://www.runtime.tv/es/feature/tornados-de-hielo-0']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.19044-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 2022-08-13-git-c469c3c3b1-full_build-www.gyan.dev (setts), ffprobe 2022-08-13-git-c469c3c3b1-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1690 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.10.04, Current version: 2022.10.04
yt-dlp is up to date (2022.10.04)
[debug] [generic] Extracting URL: https://www.runtime.tv/es/feature/tornados-de-hielo-0
[generic] tornados-de-hielo-0: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] tornados-de-hielo-0: Extracting information
[debug] Looking for Brightcove embeds
[debug] Looking for embeds
ERROR: Unsupported URL: https://www.runtime.tv/es/feature/tornados-de-hielo-0
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1477, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1553, in __extract_info
  File "yt_dlp\extractor\common.py", line 672, in extract
  File "yt_dlp\extractor\generic.py", line 3062, in _real_extract
yt_dlp.utils.UnsupportedError: Unsupported URL: https://www.runtime.tv/es/feature/tornados-de-hielo-0

Appears to use what seems to be the same API as https://github.com/yt-dlp/yt-dlp/issues/4969 (just with different domain)

I take this open request to say that the Brazilian ( https://www.runtime.tv/pt-br/ ) and Latin America ( https://www.runtime.tv/es/ ) versions should also be added because yt-dlp cannot extract videos.


cabId parameter name

I am trying to download crash dumps from the API using the https://manage.devcenter.microsoft.com/v1.0/my/analytics/cabdownload call for a Windows Desktop application. It requires three peices of information from me:

An OAuth Bearer token in the Authorization header.
The target applicationId in the query string.
The ID for the CAB file to download.

From the documentation the name of the CAB ID parameter should be cabId. Additionally, according to the documentation I need to get the CAB ID from failuredetails API call. According to the documenatation for failuredetails the response should have cabId defined and cabDownloadable set to true. However, when I get a response from the the failuredetails API I only see a cabIdHash value in the response details and the cabDownloadable item is set to false. Additionally, the documentation's example response for that API call shows cabIdHash (and not cabId) with cabDownloadable set to false.
When I try to call the https://manage.devcenter.microsoft.com/v1.0/my/analytics/cabdownload API with the parameter named cabId I receive a 400 HTTP status code. When I call that API with the parameter named cabIdHash I receive a 401 HTTP status code.
Doing some additional spelunking, I used Chrome's dev tools to see what traffic I could see when downloading crash dumps manually from the https://partner.microsoft.com/en-us/dashboard/analytics/reports/desktop/health/details?productId=< product Id >&failureHash=< the-guid-for-a-failure > page the partner sends along the parameter as cabIdHash (to a different API, however).
Lastly, the user in partner center has a Azure AD application set up with the Role of Manager (Windows) which I understand to be of sufficent privileges to access and download the crash dumps. The line looks like

Name
Role

Microsoft Error Reporting API for < Product name > (< GUID-for-the-client-ID >)
Manager (Windows)

In summary. I believe I have sufficent privileges to download CAB files via the API, but I an getting either a 400 or 401 HTTP code from the API. Additionally, the documentation is incorrect as either the parameter name should be cabIdHash or the example response on the failuredetails needs to be updated and the API itself should return cabId in the JSON response instead of cabIdHash.
Another item of interest, the documenation for downloading crash dumps for a driver error (that is deprecated according to the documenation) lists cabIdHash as the parameter for the API call. Keep in mind that I am not trying to download crash dumps for a driver. However, I thought it was worth mentioning that it shows the parameter name to the call to be cabIdHash.

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

ID: 873524f1-46a8-b1ef-8942-c83df2308aad
Version Independent ID: a333fbe3-200f-23ed-df22-48ace485fd35
Content: Download the CAB file for an error in your app - Windows UWP applications
Content Source: windows-apps-src/monetize/download-the-cab-file-for-an-error-in-your-app.md
Product: uwp
GitHub Login: @Xansky
Microsoft Alias: mhopkins

Docs have been updated. The engineering team says it is still cabId.

Ever managed to download CAB ?
Having same issue, with valid service-to-service token created per documentation.

No. I have been unable to and I have run out of ideas on what to try next.
This fails for me reliably but MS said it isn’t broken. I assume I’m doing
something wrong, but I’ve followed the documentation.
On Sun, Mar 17, 2019 at 10:53 AM rAndom69<EMAIL_ADDRESS>wrote:

Ever managed to download CAB ?
Having same issue, with valid service-to-service token created per
documentation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-uwp/issues/1428#issuecomment-473673059,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqAXcYEusq_RjdsDtVMk-rAW2qbrt9Lks5vXlbSgaJpZM4aXCHq
.

As I'm in same boat I do blame MS. Well, I'll see what our premium support has to say about this. I'll write result here for reference. Only thing which is not according to documentation is that I'm not global administrator of AAD when I create application account, however assumption is that this is required only for partner center connection to AAD.

Repro'ed this with the following powershell
$tenantID=$env:DEV_CENTER_TENANT_ID
$clientID=$env:DEV_CENTER_CLIENT_ID
$clientSecret=$env:DEV_CENTER_CLIENT_SECRET
$appId=$env:DEV_CENTER_APP_ID
$loginString = ("grant_type=client_credentials", "client_id=$clientID", "client_secret=$clientSecret", "resource=https://manage.devcenter.microsoft.com" ) -join "&"
$accessToken = (Invoke-RestMethod -Method POST -Uri "https://login.microsoftonline.com/$tenantID/oauth2/token" -Body $loginString).access_token
$authorizationHeader = @{ "Authorization" = "Bearer $accessToken" }
$startDate = (Get-Date).AddDays(-30).ToString("yyyy-MM-dd")
$endDate = (Get-Date).ToString("yyyy-MM-dd")
$failureHitResponse =
 Invoke-RestMethod -Method Get -Uri "https://manage.devcenter.microsoft.com/v1.0/my/analytics/desktop/failurehits?applicationId=$appId&aggregationLevel=dateRange&groupby=failureName,failureHash&startDate=$startDate&endDate=$endDate&top=25&skip=1" -Headers $authorizationHeader

write-host "Failure Hit - "
$failureHitResponse.Value[0]

$failureHash = $failureHitResponse.Value[0].failureHash
$failureDetailResponse =
 Invoke-RestMethod -Method Get -Uri "https://manage.devcenter.microsoft.com/v1.0/my/analytics/desktop/failuredetails?applicationId=$appId&failureHash=$failureHash" -Headers $authorizationHeader

write-host "Failure Detail - "
$failureDetailResponse.Value[0]

# failuredetails REST API doesn't return cabId as the docs indicate, it does return a cabIdHash, so try that
$cabIdHash = $failureDetailResponse.Value[0].cabIdHash
write-host " Cab id HASH is $cabIdHash"

#  Using cabId param to cabDownload API says "Invalid or null value in cabIdHash parameter"
$cabDownloadResponse =
Invoke-RestMethod -Method Get -Uri "https://manage.devcenter.microsoft.com/v1.0/my/analytics/desktop/cabdownload?applicationId=$appId&cabId=$cabIdHash" -Headers $authorizationHeader
write-host $cabDownloadResponse

#  Using cabIdHash param to cabDownload API returns a 401
$cabDownloadResponse =
 Invoke-RestMethod -Method Get -Uri "https://manage.devcenter.microsoft.com/v1.0/my/analytics/desktop/cabdownload?applicationId=$appId&cabIdHash=$cabIdHash" -Headers $authorizationHeader
write-host $cabDownloadResponse

The output from the powershell above shows clearly that -

The failuredetails API returns cabIdHash instead of cabId.  In addition there is another field returned that is not mentioned in the docs,  filename.
The cabdownload API doesn't take a cabId parameter and if you use a cabIdHash parameter instead using the cabIdHash from the failuredetails API you will get a 401

I'm noticing that we wrote this issue up against the UWP doc pages for these APIs whereas we are seeing a problem with the desktop versions of these APIs.   The Desktop pages for these apis more accurately describe what we are seeing( with the failuredetails API returning cabIdHash ) and we are using a desktop application but we still are getting a 401 error for the cabdownload api when providing the cabIdHash.
The desktop failuredetails API documentation page
https://docs.microsoft.com/en-us/windows/uwp/monetize/get-details-for-an-error-in-your-desktop-application
The desktop cabdownload API documentation page
https://docs.microsoft.com/en-us/windows/uwp/monetize/download-the-cab-file-for-an-error-in-your-desktop-application

Via ticket opened onto backend team issue with cabDownloadable=False and inaccessible cabs was considered a bug. (although it was a perilous road...)
Holding breath for a fix

@rAndom69  Thanks for the update,  We also have had a premium support ticket open on this but you are making more headway with confirmation that this is actually considered a bug.

Update from Microsoft support. I'll post here once again when it's resolved.
"The root cause has been identified, but due to the nature of the back-end changes that will need to be made, it may be some time until a fix is available."

So, after some marathon of mailing with Microsoft, this works now and crash dumps are downloadable (verified for desktop applications)

@rAndom69 - Sorry about commenting on a really old issue. I am facing the same issue that you have outlined. Unable to download cab files, for an account with Manager privilege, as the field cabDownloadable is set to False for all the documents returned by /failuredetails API . Could you please help with any suggestions that will help fix this issue? Thank!


Ability to change file explorer indent guides color.

Current supported options related to explorer "workbench.tree":
"workbench.tree.indent": 17,
"workbench.tree.renderIndentGuides": "always",

Current Behavior: inherits color from editorIndentGuide.background
Desired Behavior: has its own settings.
Something like: workbench.tree.indentGuide.background

"workbench.colorCustomizations": {
"tree.indentGuidesStroke": "#ff0000"
}


Make clouds pop in continue

I would like to add clouds in continuous. Currently, the clouds are just at the beginning of the level, I would like to make them appear continuously on the whole level @EdwardDunn

I've already handled this one, actually. Should be solved in Pull Request #151 when that's finalized. Good work catching this, though.

Completed by @Germlord.
@painlibanais feel free to think of new issues to create, thanks for your input.


Errors should be sent to the error log channel

Possibly relevant:
https://discordpy.readthedocs.io/en/latest/logging.html

Possibly relevant:
https://discordpy.readthedocs.io/en/latest/logging.html


UI complete, merge to Develop branch

Replaced all the old code with new since the old doesn't work anymore, the old code can still be returned from old commits if needed.


cannot get timetable, but classes is working

when trying to get a timetable from /timetables/ i just get {"statusCode":404,"message":"Cannot GET /timetables/777","error":"Not Found"} but getting classes from /classes is working

Sorry, this is a documentation error, the endpoint has changed to /lessons/<class>/ics, so /lessons/777/ics.

thank you.
Might be a good idea to update the readme


ImportError: No module named examples.manual_control

Hi @fabianoboril . I used python 2.7 with its egg and scenario is getting prepared but cant run manual_control.py from scenario runner folder now
This is the error that i receive
Traceback (most recent call last):
File "manual_control.py", line 58, in
from examples.manual_control import (World, HUD, KeyboardControl, CameraManager,
ImportError: No module named examples.manual_control
My python path is as follows:
export PYTHONPATH=$PYTHONPATH:/home/schemba/carla/PythonAPI/carla/dist/carla-0.9.11-py2.7-linux-x86_64.egg:/home/schemba/carla/PythonAPI/carla/agents:/home/schemba/carla/PythonAPI/carla:/home/schemba/carla/PythonAPI:/home/schemba/carla/scenario_runner-0.9.11
Desktop (please complete the following information):

OS: [e.g. Ubuntu 18.04]
CARLA Version [e.g. CARLA 0.9.11]
Python version [e.g. 2.7]
Version [e.g. 0.9.11]

I  had to add an init.py file at ~/PythonAPI/examples folder. Can you kindly mentoin it in docs or include in script.

Hi @werewolfdev
I#M facing the same issue on Windows with scenario runner 0.9.12. Which init.py do u mean?

Hi @LucasFKobernic .I added an empty document whose name was init.py  into the examples folder as seen from another persons issue comments and it worked.


Expose SerializerToYaml

It would be beneficial to expose yaml_rust::Yaml in some way (perhaps making SerializerToYaml public?). I want to add a commenting extension on top of serde-yaml—perhaps comment-yaml—which takes serde-yaml output and adds comments on top of it. However, the YAML representation provided by serde-yaml is insufficient as it does not include comments or a means of writing to a String.
Currently, I'd have to have a full reparse

struct: Serialize + Comment
[serde-yaml]: (Serialize) -> String
[yaml-rust]: (&string) -> yaml_rust::Yaml
[comment-lib]: (Comment, yaml_rust::Yaml) -> [String or similar]

Ideally, I'd be able to have:

struct: Serialize + Comment
[serde-yaml]: (Serialize) -> yaml_rust::Yaml
[comment-lib]: (Comment, yaml_rust::Yaml) -> [String or similar]

where Comment is like Serialize but for comments.

It's intentional that yaml_rust is not exposed in the public API of this crate. I have not been happy with that library and I will be replacing it with a different yaml backend.

@dtolnay Do you have any backends in mind? If you are looking for a new backend similar in style to https://github.com/serde-rs/json/blob/master/src/de.rs, I might try implementing one. Ideally, I think the YAML lib should be able to Serialize comments without a full reparse, but I am not sure how you think this should (or even if it should) be done.


xpra: 2.1.3 -> 2.2.4

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra -h got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra --help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra --version and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra -h and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra --help and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/udev_product_version -h got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/udev_product_version --help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/udev_product_version help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra_launcher-wrapped -h got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra_launcher-wrapped --help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra_launcher-wrapped --version and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra_launcher-wrapped -h and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra_launcher-wrapped --help and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_launcher -h got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_launcher --help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_launcher --version and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_launcher -h and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_launcher --help and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/..xpra-wrapped-wrapped -h got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/..xpra-wrapped-wrapped --help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/..xpra-wrapped-wrapped --version and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/..xpra-wrapped-wrapped -h and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/..xpra-wrapped-wrapped --help and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra-wrapped -h got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra-wrapped --help got 0 exit code
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra-wrapped --version and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra-wrapped -h and found version 2.2.4
ran /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra-wrapped --help and found version 2.2.4
found 2.2.4 with grep in /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4

cc @offlinehacker for review

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘xpra-2.2.4’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/tools/X11/xpra/default.nix:80 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
patching script interpreter paths in /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4
/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_Xdummy: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/udev_product_version: interpreter directive changed from "/bin/bash" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/bash"
/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/lib/cups/backend/xpraforwarder: interpreter directive changed from "/usr/bin/env python" to "/nix/store/7b2z0vfbs9539ga4pxx5gmli47rz5y3n-python-2.7.14/bin/python"
checking for references to /tmp/nix-build-xpra-2.2.4.drv-0 in /nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4...
wrapping `/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_launcher'...
wrapping `/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/.xpra-wrapped'...
wrapping `/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_signal_listener'...
wrapping `/nix/store/sdb561gabzb04az1f9wq6190prqzv618-xpra-2.2.4/bin/xpra_browser'...
running install tests

Success on aarch64-linux (full log)
Partial log (click to expand)
/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/bin/xpra_Xdummy: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/bin/udev_product_version: interpreter directive changed from "/bin/bash" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/bash"
/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/lib/cups/backend/xpraforwarder: interpreter directive changed from "/usr/bin/env python" to "/nix/store/5crgsfgy8n7v50hrihx4mhxdqa01nrmw-python-2.7.14/bin/python"
checking for references to /build in /nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4...
wrapping `/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/bin/.xpra-wrapped'...
wrapping `/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/bin/xpra_browser'...
wrapping `/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/bin/xpra_launcher'...
wrapping `/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4/bin/xpra_signal_listener'...
running install tests
/nix/store/3imbfkr4rhbsziqdk9cr8ivd98f50hpm-xpra-2.2.4


Missing ajax loader Gif

Everytime I open a page on opencompare.org, I get the following error
"GET https://opencompare.org/assets/images/ajax-loader.gif [HTTP/1.1 404 Not Found 54ms]"
It seems the Gif file is missing from the repository. You should either add it or remove the line from the editor.css file.
https://github.com/OpenCompare/OpenCompare/blob/cb0ebb58b9ea5f6c5ba8cb130d41ea875c9059b6/org.opencompare/play-app/public/stylesheets/editor.css#L91

I removed the link to the gif.
Thanks


Pinned Blue-frame remains after qutting via "Exit" command in git Bash

Microsoft PowerToys version
0.74.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Always on Top
Steps to reproduce

Open up git Bash
Pin it
Run some commands while logging the outputs manually to Excel which is in the background but not pinned.
Exit Bash

✔ Expected Behavior
Reproduce the bug
❌ Actual Behavior
Close down successfully
Other Software
Bash version: 5.2.15(1)
Excel LTSC (idk which version)

/dup #28120


COCO Structure

Hi,
Thanks for your code, but I have a question about COCO.
When I finetune the novel weights on coco, I could not load the image.
python -m tools.train_net --num-gpus 1 \
        --config-file configs/COCO-detection/faster_rcnn_R_101_FPN_ft_novel_10shot.yaml \
        --opts MODEL.WEIGHTS checkpoints/coco/faster_rcnn/COCO_base_model/model_reset_remove.pth

The error is
FileNotFoundError: [Errno 2] No such file or directory: 'datasets/coco/trainval2014/COCO_val2014_000000482978.jpg'

The coco data structure is the same with https://github.com/ucbdrive/few-shot-object-detection/blob/master/datasets/README.md :
datasets/
    coco/
        train2014/
        val2014/
        annotations/

There is no dataset "trainval2014" ?

I fixed that by combining the two folder into one.
So it would look like this:
datasets/      coco/         train2014/         val2014/         trainval2014/         annotations/

@davesie
Yeah, it works fine. Thanks!

Glad I could help =)

Glad I could help =)

thanks for your help for meeting the same issue:)))))


[CSL-236] Make web and wallet compilation optional

@gromak

@gromak
Now we have 2 flags: with-web and with-wallet.
Also scripts now don't run web server by default, but do it only when CARDANO_WEB environmental variable is not empty. It works only if built with web.


Add oauth2_proxy chart

Towards: https://github.com/giantswarm/giantswarm/issues/2480
Add chart for the oauth2_proxy. This is a new host cluster service that will allow authentification via an OAuth2 Provider and based on this project.
We use google directly as an identity provider, since Auth0 or Github doesn't work for us at the moment. Access restriction is to all @giantswarm.io email addresses.

Yes. Own repo with Dockerfile would work
On 19. Jun 2018, 09:37 +0200, Tobias Richter<EMAIL_ADDRESS>wrote:

@indyfree commented on this pull request.
In helm/g8s-oauth2-proxy-chart/templates/deployment.yaml:

labels:

k8s-app: oauth2-proxy
name: oauth2-proxy
namespace: kube-system
+spec:
replicas: 2
selector:
matchLabels:

 k8s-app: oauth2-proxy

template:
metadata:

 labels:

   k8s-app: oauth2-proxy

spec:

 containers:

 - image: quay.io/giantswarm/oauth2_proxy:2.2

Sure, will do. Thinking about just having a own repo with a Dockerfile, since theres no official one anyways.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or mute the thread.

Own Dockerfile added. Going with this.


Add selection here a bit odd

User :right clicked a folder and "add selection" here
Problem : says "do you want to move undefined to xxx"
Solution : should allow that selection
User : click a folder XXX -> "add selection here"
Problem : says "do you want to add XXX to XXX"
Solution: should not be allowed to add XXX to XXX  (although does give an error if you try)

"Undefined" suggests no current selection, in which case the menu option should be disabled.
Cursory check whether item is being added to itself should be possible.  Subsequent error is to ensure this does not happen down a  number of levels of nesting (i.e adding a selection to a great great grandchild of itself)


Multiple paginator params don't work

Hi,
I think I found an issue when adding multiple where params to the paginator. It seems something like:
    *      wheres = {
    *          {"x", "code", "=", "GER"},
    *          {"x", "dial", "=", "49"},
    *      }

doesn't work, it only loads the value of the last param and the query executed is like this:
`WHERE c0_.code = '49' AND c0_.dial = '49' ORDER BY c0_.code ASC) dctrn_result) dctrn_table
I've looking into the code and I think I found the problem: in the evaluate method of the PaginatorWheresEvaluator you initialize interation:
        $iteration = 0;

but I think the $iterations++; is missing in the foreach loop.
I tried by adding it and it works perfectly now, here's the method:
public function evaluate(
        QueryBuilder $queryBuilder,
        AnnotationPaginator $annotation
    )
    {
        $iteration = 0;

        if (is_array($annotation->getWheres())) {

            foreach ($annotation->getWheres() as $where) {

                $whereValue = $this
                    ->requestParameterProvider
                    ->getParameterValue($where[3]);

                $optionalFilter = (boolean) isset($where[4])
                    ? $where[4]
                    : false;

                if ($optionalFilter && ($where[3] === $whereValue)) {

                    continue;
                }

                $queryBuilder
                    ->andWhere(trim($where[0]) . '.' . trim($where[1]) . " " . $where[2] . " ?0" . $iteration)
                    ->setParameter("0" . $iteration, $whereValue);
                # The missing iteration
                $iteration++;
            }
        }

        return $this;
    }

This line is already in the code...
https://github.com/mmoreram/ControllerExtraBundle/blob/master/Resolver/Paginator/PaginatorWheresEvaluator.php#L81
I've tagged the repository. Now you should get the fixed version :)
Thanks!

Great! thanks!


Feature Request: Moving and rotating bars/Change edges of screen

It would be good to be able to move the bars freely on the screen and rotate them by 90/180 degrees.
Or at least chose the edge of the screen.
For menu bar and taskbar essentially (desktop bar already draggable).

I do plan to support taskbar on top as part of M3. I also think menu bar on bottom could be an interesting thing to add as well.
However, the existing interface wouldn't work very well in a vertical layout. If someone is willing to spend the time to create a usable and sustainable implementation of it, I would gladly accept the pull request 😄

Taskbar-on-top is available in the latest Milestone 3 release. Please check for updates and re-open the issue if it is not resolved.

Menu bar on bottom has not been implemented yet.
I think I cannot reopen this by myself, isn't it ?

I do not plan on implementing menu bar on bottom at this time.


PL: bossowie → bossy

PL: bossowie → bossy

Description 🗒
Change wrong form of "bosses" in Polish.

Examples 📸

Related Issues 🔗

 Expand for Help

Have questions about the review or deployment process? View our contributing docs
Need additional help and want to chat in real time? Join our community Discord

By submitting this pull request, you agree to our code of conduct

Can you commit the changes of the other PR #376  on this?

.deploy


Remove 'static mut' usage in features::os::kernel_version.

Resolves #2028
Note that this is (AFAICT) the first use of Atomic* types in nix (other than tests). However, this shouldn't be a portability issue, since nix is not #![no_std], and (IIUC) std requires at least loads and stores of pointer-sized atomics (i.e. AtomicUsize), which is all this PR uses.

(see https://github.com/bytecodealliance/rustix/pull/645 about CI failures)


NO-JIRA: controller:annotation: introduce pause annotation

Allowing the operator to pause reconciliation of specific CR.
This is useful for experiment,debug and development process.
For example when a contributor would like to test some changes
done to the owned object, without having those
object overwritten by the operator.

/retest
infra issue

/cherry-pick release-4.16

/reteat

/retest

/retest
Infra issue


Sync eng/common directory with azure-sdk-tools for PR 9381

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/9381  See eng/common workflow

/check-enforcer override
We don't support macos-12 anymore. Need to bump that in repo + update tooling references.


[mountvol] listing "mounts by volume" vs. "volumes by mount"

The /l switch lists the volumes by mount point, but apparently there is no switch to do the opposite, list mount points by volume. The information is, however, provided by typing mountvol without any parameters. As far as I can tell, this is the only way to get mount points by volume using mountvol.
Unfortunately, doing it this way also displays the help info as a header, and there is no way to narrow the request down to only the mount for a particular specified volume.
C:\> mountvol
Creates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
MOUNTVOL [drive:]path /P
MOUNTVOL /R
MOUNTVOL /N
MOUNTVOL /E

    path        Specifies the existing NTFS directory where the mount
                point will reside.
    VolumeName  Specifies the volume name that is the target of the mount
                point.
    /D          Removes the volume mount point from the specified directory.
    /L          Lists the mounted volume name for the specified directory.
    /P          Removes the volume mount point from the specified directory,
                dismounts the volume, and makes the volume not mountable.
                You can make the volume mountable again by creating a volume
                mount point.
    /R          Removes volume mount point directories and registry settings
                for volumes that are no longer in the system.
    /N          Disables automatic mounting of new volumes.
    /E          Re-enables automatic mounting of new volumes.

Possible values for VolumeName along with current mount points are:

    \\?\Volume{650fa92e-96e5-4f91-8d1a-2102a05ec50f}\
        E:\

    \\?\Volume{fa86ef6d-0000-0000-0000-402400000000}\
        C:\

    \\?\Volume{eafac607-2463-46ff-9772-d1d0f169fc41}\
        X:\
        E:\test-mount\
C:\>

@glenn-slayden : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@glenn-slayden : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[2370] Hook up back links for new course flow

Context
When going through the new course flow, the user should be able to see and use a back link to go to their previous steps, with the following circumstances:

Going through the flow normally
Going back to the confirmation page
Going back past locations if there is only a single location
Going back to different pages depending on the user being an accredited body

Changes proposed in this pull request

Add in correct back links
Add in view helper for doing back links with confirmation

Guidance to review
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

https://trello.com/c/M6J2ViCg/2370-s-hook-up-back-links-for-new-course-flow

Feels like a good candidate to have a quick gif demonstrating how this works. @TobyRet what were you using to do that, again?

now with added gif @misaka (OBS -> ffmpeg to gif is a way to do it on linux, apparently)

now with added gif @misaka (OBS -> ffmpeg to gif is a way to do it on linux, apparently)

How much work is it?

OBS is straightforward enough, ffmpeg might be a bit fiddly though https://engineering.giphy.com/how-to-make-gifs-with-ffmpeg/

Ran into a small problem: accredited bodies aren't re-selected when I go back to them from a later page.
Steps:

navigate to provider 2HN's course page
create a new course (by append /new to the URL)
when on the accredited bodies select an existing provider as the accredited provider
click "Continue"
use the "Back" link to go back to the previous page
:boom: the previously-selected accredited body is no longer selected

Notably, when using the browser back-button this persists.
Unless this is trivial to fix, we should probably just deploy this ticket as-is and create a new bug ticket for this.


[release-4.14] OCPBUGS-23202: Don't build InstanceSpec during delete operations

This is a manual cherry-pick of #90

/unassign EmilienM
/assign @mandre

/uncc @EmilienM
/assign @pierreprinetti

/hold
Please include https://github.com/openshift/machine-api-provider-openstack/pull/98 in whatever form the fix will end up being merged

Updated to include a cherry-pick of https://github.com/openshift/machine-api-provider-openstack/pull/98 also.
/cc @pierreprinetti

/hold cancel
:ok_hand:

/jira refresh

/jira refresh

/jira refresh


Wrong documentation for Iterable.iterator

Iterable.iterator documentation reads
https://github.com/dart-lang/sdk/blob/05003ab60d4f015b4eee30e29940201fad87f99c/sdk/lib/core/iterable.dart#L139-L140
This is not true if iterator instance is created by Iterator.empty(). In this case instance of EmptyIterable is returned which doesn't create a new object each time
https://github.com/dart-lang/sdk/blob/05003ab60d4f015b4eee30e29940201fad87f99c/sdk/lib/internal/iterable.dart#L692

The important part is that each returned iterator will start a new iteration from the start if the elements.
It's technically true that it's not a new instance here, and the documentation could probably be tweaked to not say that.
If we do that, we should be very careful to not make the documentation harder to understand for all the other cases.