Adding missing desc

https://github.com/MicrosoftDocs/office-docs-powershell/issues/5767

Docs Build status updates of commit b2cc43f:
:clock10: Full build: the average full build time is 18 min(s) 3 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b2cc43f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlineLisCivicAddress.md
:white_check_mark:Succeeded
View (skype-ps)

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@tseward Please review this PR. Thanks

@chrisda Please merge this PR. Thanks.

@chrisda Please merge this PR. Thanks

Docs Build status updates of commit b8724e7:
:clock10: Full build: the average full build time is 17 min(s) 57 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b8724e7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlineLisCivicAddress.md
:white_check_mark:Succeeded
View (skype-ps)

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Small fixes to the Spanish translation

Pull Request Checklist

[X] Description: Briefly describe the changes in this pull request.
[X] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.

[X] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?

Description
Small fixes to the Spanish translation

Changelog Entry
Fixed

Small fixes to the Spanish translation to give more specific meaning to the words in their actual use on the web UI

Thanks!


checkbox commented

I think that that should do also if checkbox is not use now ...

I cant test it right now, but it looks like ok 😊


Added support for haproxy scraping that implements basic auth

Hi
I needed this to work with a haproxy that had basic auth implemented.
I have updated the go build version to 1.6 because that is what we use locally, if this is not idea I can revert the change. Also welcome any other changes regarding how the code should be structured to fit into the repo going forward.
Thanks
@juliusv @brian-brazil

You can add basic auth via the existing flag for the URL.
We're not ready to upgrade to 1.6 yet.

Yeah this isn't necessary. You can just haproxy_exporter -haproxy.scrape-uri='http://foo:bar@localhost:8080/stats;csv'

… I guess this needs to be documented better though, since it keeps coming up.

Do we officially support this though? We didn't explicitly add this as a feature, it Just Worked due to go internals.

I think we should rely on this and document it. It kind of is already in the Docker example.
That gives us the support for basic auth and custom stats paths built in, I think that's better than adding a bunch of extra code to make it "explicitly supported" (while putting it in the URL would still work too, with a different mechanism!)

I'm thinking if someone wants SSL or something else that we'd have to support this all similar to how we do in Prometheus.

Yes, but we can deal with that as it comes up – if it's not supported by the scrape URI as is, it warrants adding code to support it when needed. But for this one, we'd just duplicate functionality that already exists.
We're in basically the same situation here wrt. client vs. server side options as with Prometheus, although we can probably get by with less in the client side because HAProxy is a limited target. So far, nobody has come up with a need for HTTPS, so I am not worried about that right now.
But basic auth is usable, and there is a need, so we can

add more code to break it out into separate flags
document what is already working
keep that it is working as dark lore, passed around under friends, but that still means we can't just remove it

I think 2. is the best of these options because it doesn't add any complexity to the code, and we could not break this support now anyway, because I bet someone somewhere is relying on it already.

Cool thanks for the heads up , will possibly just send through a doc update pull request so that its easier to find in future

@RC1140 please comment on #50 if that is clear enough


[storage-preview] pulish 0.2.4

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/limingu/azure-cli-extensions.git@publish#subdirectory=src/$EXT&egg=$EXT"


Add sort, stableSort, stableSortInPlace to Array

sort is the immutable version of the JS Array.sort function
stableSort, stableSortInPlace are the implementation from Belt

It seems we do not need our own stable sort implementation.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#sort_stability

Since version 10 (or ECMAScript 2019), the specification dictates that Array.prototype.sort is stable.


gh-pages branch should be created manually beforehand

This should be reflected either on the docs or automated in the code, otherwise a first run will fail, i.e:

Ideally I should be created based on ghPagesBranch config in write.ts, right before fetching for that branch specifically, otherwise it'll fail as shown above:
    if (githubToken && !skipFetchGhPages && ghRepository) {
        benchmarkBaseDir = './benchmark-data-repository';
        await git.clone(githubToken, ghRepository, benchmarkBaseDir);
        extraGitArguments = [`--work-tree=${benchmarkBaseDir}`, `--git-dir=${benchmarkBaseDir}/.git`];
        // TODO: Create gh_pages branch if not already present? <----
        await git.checkout(ghPagesBranch, extraGitArguments);
    } else if (!skipFetchGhPages && (!isPrivateRepo || githubToken)) {
        await git.pull(githubToken, ghPagesBranch);
    } else if (isPrivateRepo && !skipFetchGhPages) {
        core.warning(
            "'git pull' was skipped. If you want to ensure GitHub Pages branch is up-to-date " +
                "before generating a commit, please set 'github-token' input to pull GitHub pages branch",
        );
    } else {

Putting this as an issue first to see what main devs think?

It's already in docs.

Sure, would be nice to have it automated away though. Automation >>> Documentation


Error while adding via SPM

Tried adding SLP to a new project and I am getting an error about incompatible tools version.

because SwiftLinkPreview >=0.1.0 contains incompatible tools version and root depends on SwiftLinkPreview 3.1.0..<4.0.0, version solving failed.

Are you planning an update? or is there a way to resolve this myself?

New version with the fix coming right up.


$withCount return Illegal offset type

I get the Illegal offset type error with protected $withCount = ['replies'] or Post::withCount('replies').
Any fix soon?

Please reopen this issue the workaround by making it an accessor will not help eager loading.
withCount should be the proper way to do this.

@alexjose done.


Publish 'Docker official images' to DockerHub.

Is your feature request related to a problem? Please describe
The Docker images that are currently published on OpenSearch DockerHub organization are not Docker official images.
Describe the solution you'd like
Publish Docker official image(s) by following the guidelines to Dockerhub
Initial Scope:

OpenSearch
OpenSearch-Dashboards

Describe alternatives you've considered
No response
Additional context
Docker official image creation process

We have matches a lot of the tenets here:
Focus on [Free](https://www.debian.org/social_contract#guidelines) and [Open-Source](https://opensource.org/) Software

    Support [multiple architectures](https://github.com/docker-library/official-images#architectures-other-than-amd64)

    Exemplify [Dockerfile best practices](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/)

    [Actively rebuild](https://github.com/docker-library/official-images#library-definition-files) for updates and security fixes

    Adhere to upstream recommendations

    Add minimal quality-of-life behavior for the container environment where fit

Tho we probably need to re-evaluate the dockerfiles we have according to best practices, that would take some time to complete:
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/
I still have questions on what this supposed to mean:
    Adhere to upstream recommendations

I found these links helpful
https://github.com/docker-library/official-images
https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what

@elfisher What can we do to get this moved forward? This is really important for people to have good visibility on which images the OpenSearch project is publishing.

Some resources for creating official Docker image
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/
https://github.com/docker-library/official-images/blob/master/README.md#contributing-to-the-standard-library
https://github.com/docker-library/official-images/blob/master/NEW-IMAGE-CHECKLIST.md

created PR for opensearch and opensearch-dashboards for official image program
OS: https://github.com/docker-library/official-images/pull/13161
OSD: https://github.com/docker-library/official-images/pull/13194

For now we have decided to go ahead with Docker Verified Publisher program


Add Unit Tests

Add Unit Tests, look at how Slim and Laravel are doing it
Look into using example in https://akrabat.com/testing-slim-framework-actions/ & https://github.com/slimphp/Slim-Skeleton/tree/main/tests for writing unit tests for actions
The easiest approach is to run http GET & POST requests for all the routes that come with a vanilla installation of this project and verify that the returned Response has the right status code & that the return Body contains the expected elements

All routes are now tested as of version 5.0.1 see https://github.com/rotexsoft/slim-skeleton-mvc-app/compare/5.0.0...5.0.1


Write about Sprint 6 in the Rust Gamedev newsletter for July 2021

Deadline: before August 7.
rust-gamedev/rust-gamedev.github.io#719
Prepare to submit the newsletter before the publication deadline (BEFORE the end of our sprint, August 14).

https://github.com/rust-gamedev/rust-gamedev.github.io/pull/743


Avoid exiting the application if we fail to lookup the maker address

This is the result of an investigation where the testnet taker was was not running for significant time because the application had just exited upon startup leading the container to stop.
2022-05-23 14:48:58
{"timestamp":"2022-05-23T04:48:58.950821203Z","level":"TRACE","fields":{"message":"measuring heartbeat pulse"},"target":"wire"}

2022-05-23 14:49:01
{"timestamp":"2022-05-23T04:49:01.243552118Z","level":"INFO","fields":{"message":"Initialized logger"},"target":"shared_bin::logger"}

2022-05-23 14:49:01
{"timestamp":"2022-05-23T04:49:01.2436744Z","level":"INFO","fields":{"message":"Running version: 0.1.0"},"target":"taker"}

2022-05-23 14:49:01
{"timestamp":"2022-05-23T04:49:01.243707847Z","level":"INFO","fields":{"message":"CFDs created with this release will settle after 24 hours"},"target":"taker"}

2022-05-23 14:49:01
{"timestamp":"2022-05-23T04:49:01.355320375Z","level":"INFO","fields":{"message":"Opened database at /data/testnet/taker.sqlite"},"target":"daemon::db"}

2022-05-23 14:49:01
Error: failed to lookup address information: Name or service not known

The error comes from std::net likely from the cvt_gai call in this tryfrom impl<'a> TryFrom<(&'a str, u16)> for LookupHost - but that does not really help. I'm surprised we don't see a panic if the application crashed
This is likely triggered by:
https://github.com/itchysats/itchysats/blob/eeefe8eefa818b94551bd9e54e41da0963ed8e35/taker/src/main.rs#L329
which does a tokio::net::lookup_host :
https://github.com/itchysats/itchysats/blob/eeefe8eefa818b94551bd9e54e41da0963ed8e35/taker/src/main.rs#L417-L428
Note that I am not entirely sure if tokio::net::lookup_host actually uses the code in std::net - but I'd say this is a likely candidate (also because the last message before is the db connection message, and that fits the code execution)
I think we fail there and just exit main.
We can add a retry mechanism there, but essentially its questionable if we can start with such an error. It might be a valid solution to let the container restart.

I think it's fine to let the application terminate if it is not able to connect to the maker because of a lookup_failure.


Struktur (Vorschlag)

Looks good. I say that we should put this kind of information in the trello board though. This repo should be focused on the development. Also, before merging any pull requests in the future, we should all take a look at them and understand the changes. I'll leave this open for now as an example, so that everyone can see it and take a look at it before we close it.


Update numba from 0.56.4 to 0.59.1

Update numba from 0.56.4 to 0.59.1.
Fix #2698.

I have removed the explicit dependence on numba-0.56.4 from libcommon/pyproject.toml, as we do not use it in our code.

Note the dependence is now indirect via: datasets > librosa > numba

Before merging, I would suggest waiting for @lhoestq reply on: https://github.com/huggingface/dataset-viewer/issues/2698#issuecomment-2049108864

It seems this PR could be merged without any further impact, @huggingface/dataset-viewer.


Various Dialog close functions for windows decorations are not working

clicking the X on the window does noting. Should close it

fixed


Log ratchet keys in olm::Session::debug

Include the latest public ratchet keys in the debug output.
Fixes #125. Review commit-by-commit.
Question: does any of this need to be behind a feature flag? It's all public data so it feels like it's not a problem to retain or log it, but in theory I suppose there's a reduction in security due to keeping the parent ratchet key around.

Codecov Report
Attention: Patch coverage is 6.66667% with 14 lines in your changes are missing coverage. Please review.

Project coverage is 84.50%. Comparing base (2deb206) to head (72992e5).
Report is 2 commits behind head on main.

Files
Patch %
Lines

src/olm/session/double_ratchet.rs
6.66%
14 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #133      +/-   ##
==========================================
- Coverage   84.92%   84.50%   -0.43%
==========================================
  Files          32       32
  Lines        1758     1768      +10
==========================================
+ Hits         1493     1494       +1
- Misses        265      274       +9

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

Do you want to squash that fixup commit?

yarp, hold on

Ah, now we won't have a changelog entry, I wanted to write a merge commit containing one. :cry:

Oh, sorry!


Dbaeumer/involved-goat-bronze

More small fixed to the meta model generation.

@dbaeumer This is one heck of a branch name. I am confused... 🤔

@rcjsuen we will move to a new model where all code will come via PRs into the main branch. Since it is hard to come up with branch names in this model we have a branch name generator comparable to the docker name generator. So you will see more of these names.


Remove Silex support

http://symfony.com/blog/the-end-of-silex
To be done on next major.

Done in v4.0.0.


Alignment of captured images from Realsense viewer

Required Info

Camera Model
D400

Firmware Version

Operating System & Version
Win10

Platform
PC

SDK Version
2.11.1

Language
python

I have some images (rgb and depth raw) i captured using the snapshot button of realsense viewer
I tried to align the depth image to the rgb image using the following code:
           depth_point = d435.processing.rs2_deproject_pixel_to_point(depth_Intrinsics, depth_pixel,depth_value*d435.processing.depth_scale)
           color_point = d435.processing.rs2_transform_point_to_point(d435.processing.depth_extrinsics['848'], depth_point)
           color_pixel = d435.processing.rs2_project_point_to_pixel(d435.processing.color_Intrinsics['848'], color_point)
but the images were not aligned
I used the depth_intrsincs that i got from the depth_metadata when i captured the depth frame, which is different from the one i get when i am using the api (for the color Intrinsic and depth to color extrinsic i am using the api).
How can i align images i captured from real sense viewer snapshot button?

[Realsense Customer Engineering Team Comment]
@adarvit
the rs2_deproject_pixel_to_point function in rsutil.h accepts the parameters the order should be static void rs2_deproject_pixel_to_point(float point[3], const struct rs2_intrinsics * intrin, const float pixel[2], float depth). But from your code your parameter obviously not the same, I don't think python wrapper changes the parameter order, can you attach your whole python code? Also for the mapping, you can refer to the align.cpp function "align_z_to_other" which illustrate how to map the depth image to color.

[Realsense Customer Engineering Team Comment]
@adarvit
Any more issue?

can you share the code ?
i am working something exactly same so i need to view your code ... can i have it ?


Composer package

This looks awesome but is there any chance of making it a proper composer package?  It would make it way easier to include in deployments.
Thanks!

I have started messing around with this.
https://github.com/pxgamer/MediaInfo-Helper/tree/feature/composer

awesome thanks @pxgamer. You have been a great help so far with the UNIT3D as well. Should message me sometime on the UNIT3D discord or<EMAIL_ADDRESS>Maybe you would be interested in joining the core-dev team?

When I run the composer require, I'm getting:
  [InvalidArgumentException]
  Could not find a matching version of package hdvinnie/mediainfo-helper.  I'm happy to add it through proxy and add @HDVinnie as the official owner.
Not sure if @HDVinnie has a Packagist account.

Sorry forgot about that. I'll add the v1.0.0 tag when home in few hours


WithStore hook crashed logic of component load

If use withStore and withEventBus, "mounted" component hook run before "created" component hook.
Versions:

withStore from https://cdn.skypack.dev/ficusjs@6
createComponent and withEventBus from<EMAIL_ADDRESS>

@zavada123 thanks for letting us know of this issue. This has now been fixed in v6.3.0 - https://github.com/ficusjs/ficusjs/blob/6.3.0/CHANGELOG.md


Add attributes() method to model and interface

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues
161

Please add a test,
Thks,

Please add a test,
Thks,

Done


do not use jinja2 map filter with default param

support for the map filter with default was added in jinja2 2.11.0
https://jinja.palletsprojects.com/en/2.11.x/changelog/#version-2-11-0
But some of our supported platforms use jinja2 2.10, so we need to
rewrite the code to not use map/default.
Jinja2 gives warnings/errors like this:
TASK [linux-system-roles.certificate : Ensure provider packages are installed] ***
task path: tasks/main.yml:26
[WARNING]: Falling back to Ansible unique filter as Jinja2 one failed:
Unexpected keyword argument 'default'
...
TASK [linux-system-roles.certificate : Ensure certificate requests] ************
task path: tasks/main.yml:104
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.fedorahosted.certmonger was not provided by any .service files
failed: [image.qcow2] (item={'name': 'mycert', 'dns': 'www.example.com'....

In this case, is it possible to use Jinja 2.10 in the tests? Is this Jinja executed in the controller? If not we could probable add jinja version here in the repo.

In this case, is it possible to use Jinja 2.10 in the tests?

I'm trying to find out why some of our rhel8 tests use a jinja2 version which supports map/default and some do not.

Is this Jinja executed in the controller?

Yes.

If not we could probable add jinja version here in the repo.

For the CI tests, we use the jinja2 package provided by the OS, which is what we should be doing.


chore: add local migrate_local.go again

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


[RFC] Macro Defs - Methods in Macro land

As someone who does a good amount with macros, one thing I find lacking is the ability to be DRY.  There currently isn't a way (AFAIK) that allows encapsulating logic to be reused within different macros.  I.e. if there is some piece of logic you need to do multiple times in a macro, you would have to duplicate it.
It would be a great addition to allow defining methods that can be used within macro code; I.e. that accept one or more ASTNodes, and return an ASTNode.
For example:
macro def foo(x : StringLiteral) : StringLiteral
  "foo#{x}"
end

macro bar
  {{ foo "x" }}
end

bar # => "foox"

This would allow common/complex logic to be defined once and reused throughout an application.

This is basically extending the macro language to allow user-defined macro methods. Right now they are hardcoded in the compiler and not extensible. Right?
My idea is that they are also macros. For example, you could reopen Crystal::StringLiteral to add methods to it:
class Crystal::StringLiteral
  macro foo(x)
    "foo#{x}"
  end
end

Then call it:
macro bar
  {{ "x".foo }}
end

It only makes sense to call the macro method foo inside macro code because that returns ASTNode, not code, though maybe we can allow it outside macro code and the code is then transformed to code by calling to_s on it.
So the way I'd like to see this implemented is by just allowing to find macros when you call them inside macro code.
That said, I'd like to avoid so many macro code in Crystal, and not having this is a great way to accomplish this.

This is basically extending the macro language to allow user-defined macro methods.

Not necessarily.  I would rather just having methods within macro land.  I.e. you pass it one or more ASTNode, and it returns an ASTNode.
Like your example wouldasterite be
macro def foo(x : StringLiteral) : StringLiteral
  "foo#{x}"
end

macro bar
  {{ foo "x" }}
end

bar # => "foox"

I don't really think it's necessary to be able to reopen the ASTNodes to add your own method like you can with the stdlib types.  Using what is currently defined is usually good enough.  All I'm suggesting is being able to have some sort of way to keep things DRY.  As in this latest example, if you had to format x three times you would have to do "foo#{x}" three times as well.

As someone that's also been doing a lot with macros, especially lately, I love this idea. I actually needed something exactly like this last night and was out of luck. I also love @asterite's idea of being able to open up macro definitions and add methods to them like you could with any other class or struct. Would this all be insanely hard to do?
Additionally having initializers for ASTNode types would be nice too. Currently the only way to define a HashLiteral, ArrayLiteral, or anything else afaik is to actually use the literal notation. That means that using a macro to generate a Hash or Array can get kinda hacky.

Well, not crazy hard, I managed to implement a quick prototype in an hour.
After thinking a bit more about this, I think it would be really nice to go forward with this.
One thing I dislike about macros is how long and hard to understand they can get. That's a good way to try to avoid them. But if we can Dry them up and make them more concise and easier to understand, and more powerful, maybe it's the best solution.

100% agree. Crystal macros are powerful, but there are definitely some instances where you have to do some pretty hacky/unreadable things to do what you need to do. Documentation is also sparse, but once macros are somewhat finalized for v1 @Blacksmoke16 and I can probably work on that.
I feel like having initializers for ASTNode types would go a long way towards cleaning things up, as well as adding some methods that are missing on their standard library counterparts. Also, annotations need some work, but that's another issue.

I feel like having initializers for ASTNode types

Do you have an example of that? I don't quite understand what this means.

{% hash = HashLiteral.new %}
versus
{% hash = {} of Nil => Nil %}

Exactly. Especially if we had stuff like ArrayLiteral.build and HashLiteral.new which takes a block and allows you to build it.

You can already build hashes with "regular" crystal code:
enum SomeEnum
  Red
  Green
  Blue
end

{% begin %}
  {% h = {} of Nil => Nil %}
  {% for c in SomeEnum.constants %}
    {% h[c.stringify] = c.stringify.downcase %}
  {% end %}
  p({{ h }})
{% end %}

So you see I create a hash and add elements to it at compile-time, instead of outputting a hash literal.
And with macro methods this would be simpler because you could define a method to do that, though you'd need to have each.
I don't think we'll add build and such methods, it's just too much in my opinion. We can't keep adding built-in macro methods.

Now that 1.0.0 is release maybe we can revisit this? :slightly_smiling_face:.

Wanting to bring this RFC up again, as it seems to be something I constantly want/need. Would be open to sponsoring someone to implement this as well :pray:.
To summarize I think the primary goal of this feature is to:

Reduce the amount of duplication required in macro code by allowing reusable macro methods

For example:
macro def foo(x)
  "foo#{x}"
end

macro bar
  {{ foo "x" }}
end

bar # => "foox"

This plus being able to call the macro def recursively would be a HUGE win to how macro code could be written, ultimately making it easier to read/maintain/share.
Going further and allowing users to monkey patch methods into the stdlib's macro types could be useful, but I don't think it's a requirement, at least for a first pass, given you could just pass the node as an argument. Similarly, supporting parameter/return type restrictions could be a nice win from a documentation/readability POV, but also don't think it should be a blocker to a first pass given normal macros don't support them on parameters either.
Based on what I read in this issue and the related PRs, I think what we'd need to do is like:

(ref) Support parsing macro def macroName, storing them in their own place
(ref) Figure out how to handle @type.foo given it could clash with methods defined on TypeNode
The actual logic of being able to call the macro defs in existing macros, disallowing them to be used outside of a macro context, but still allowed to use them in different macro contexts. E.g. SomeNamespace.my_macro_def to support sharing of the macro code as a shard
Update doc generation to include a dedicated section for macro defs
(nice to have) Support next in macro contexts
(nice to have) Support type restrictions on parameters/return
(future iteration) Possibly allow monkey patching macro defs into existing macro AST types?

Of course not all of this has to be done at once, getting a solid MVP implementation going first would be fine as it would allow people to start using it, then figure out what the pain points are to improve on.

Minor: the term "macro def" already refers to defs that use @type.

Yeah, we'll have to take care of using clear terms.
We have def with macro code, macro, top-level macro expressions, and with this feature there's another kind of macro. What should it be called? I'm not sure. macro def as keyword would probably be confusing.
From a technical point of view, the macro keyword could actually work for this. The difference to normal macros is determined at call site (is it called from normal code or from a macro expression?). But of course it would be helpful to have a clear distinction at the definition.
Similarly, we need to worry about ambiguity at call site, as well. We already have macro calls. How do we call calls in macro expressions?

Or call them macro functions - macro fun? Technically they are more functions, since they are not methods called from an object instance. fun already exist for bindings. In a way the macro-land is already a bit special as there are for loops.

What should it be called?

Kind of just spitballing here so TBD on exact names of things, but some ideas I thought of:
Use an annotation to denote a macro as "callable". Would require being able to read annotations on macros, and allow displaying annotations applied to them in some way. Would probably require less? compiler work since you could reuse existing macro parsing logic, and just set a flag on it, like visibility?
@[Callable]
macro foo(x)
  "foo#{x}"
end

Make the keyword more akin to a modifier of the macro, e.g. private or protected. Probably more readable and could also just be a flag.
callable macro foo(x)
  "foo#{x}
end

Use some symbol as part of the macro name to denote it being special. Similar could be used to just set a flag, tho I'd say less readable and easier to miss.
macro $foo(x)
  "foo#{x}
end

Require type restrictions on them and use that as a means to differentiate:
macro foo(x : StringLiteral) : StringLiteral
  "foo#{x}
end

Or lastly, use some entirely new non-ambiguous name, like ast (fun|def) foo(x) or node (fun|def) foo(x) or something like that. Coming up with a clearer work than macro might be challenging.
@HertzDevil I'm assuming that logic would be specific to Call? I.e. if you tried to do {{ {{ 2 + 2 }} }}, you'd still get Error: can't nest macro expressions?

What's wrong with macro def?

@asterite The concern is mainly around https://github.com/crystal-lang/crystal/issues/8835#issuecomment-1080024082. I.e. that we already have macro def meaning something, and making it mean something else would be confusing.

Let's settle the terminology in #11945

@HertzDevil I'm assuming that logic would be specific to Call? I.e. if you tried to do {{ {{ 2 + 2 }} }}, you'd still get Error: can't nest macro expressions?

It is as shown above:

If the macro is not already within a macro evaluation context, then 2.+(2) is not a valid macro def call, because the first 2 is not a type.
If it is within a macro evaluation context, possibly yet another outer {{ ... }}, the error would be something like expected Call, got MacroExpression.

Also minor point: the following is valid syntax:
module A
  macro def
    1
  end
end

A.def # => 1

I don't understand what's the ambiguity.

Here are some additional examples involving non-printing or escaped macros:
macro def foo
  {% x = 1 %} # Error: macro def call must use {{ ... }}, not {% ... %}
end

macro foo
  {{ {% foo %} }}     # Error: macro def call must use {{ ... }}, not {% ... %}
  {% x = {{ foo }} %} # okay
end

{% ... %} cannot be nested within {{ ... }}. The opposite is allowed.
Also notice how the macro and the macro def are both called foo. This is technically fine, because the nested macro treatment implies they are always in separate namespaces, but we may want to forbid this to avoid confusion. This is notably not forbidden between defs and macros already; macros are "ordered before" defs in terms of "overload" ordering if they share the same name.
macro foo
  \{{ {{ 1 + 2 }} }}
  {% debug %}
end

foo # => {{ 3 }}

If an outer {{ ... }} is escaped, everything within is interpolated normally. This is existing behavior and will continue to be allowed. The body of a macro def is never considered to be escaped in this manner.
macro def foo
  \{{ 1 + 2 }} # Error: unknown token: '{'
end

macro bar
  {% x = \{{ 1 + 2 }} %} # Error: unknown token: '{'
end

bar

Escaped macros cannot be nested in macros, so it follows bare escaped ones are also disallowed within macro defs. At the moment the supported AST expressions within a macro def should be exactly what are currently permitted within {% ... %} (no case for example).

I don't understand what's the ambiguity.

This one, i.e. whether macro defs and AST node methods should both be callable with the same syntax.

It still clashes with the names of AST node methods:
struct Int32
  macro def ancestors
  end
end

{% Int32.ancestors %} # does this return a `Nop`?

We can either accept that these methods can be overridden (just like regular methods from stdlib can), or perhaps introduce some less aggressive way to avoid the ambiguity: adding a call macro:
struct Int32
  macro def foo(a, b)
    a + b
  end
end

{% Int32.call(:foo, 1, 2) %} # returns a `3` literal

This is easier to read and integrates better with existing syntax, IMHO. It would be defined for TypeNodes and at the top level.

It still clashes with the names of AST node methods

Right, and in that case you are overriding the method. There's still no ambiguity.

The opposite argument is we can then redefine all AST node methods as "primitive" macro defs, but that's a much larger undertaking and I'm not sure if a breaking change is avoidable there

I don't think there's a breaking change at all.
All the current macro methods are defined with macro def and they are primitives. Of course that syntax doesn't exist yet, so you can't do it, but we can imagine that's how it's done.
Now we are enabling macro def to be actually defined by users, and the existing ones can also be defined, it's just that they are @[Primitive] somehow (and eventually we could implement them like that)
So with this:
struct Int32
  macro def ancestors
  end
end

you are overriding the behavior of Int32.ancestors inside macros, but String.ancestors would still return the "correct" value.
Then we can redefine ancestors for every type like this:
class Crystal::Macros::TypeNode
  macro def ancestors
  end
end

It's a bit similar to how we can define a method for all classes by defining an instance method in Class:
class Class
  def foo
    1
  end
end

p Int32.foo # It works!

So there's a bit of "conflict" in that you can define a macro def on a type, or on TypeNode, and both kind of work, and it's exactly the same as in regular Crystal code, where you can define a class method on a type, or a method on Class, and they both kind of work.
Then you can define macro methods on Crystal::Macros::*, so for example adding a method to a StringLiteral. And all existing methods are also macro def, they are just primtiives.
Is there any conflict or ambiguity with that approach?

It seems the idea here is to establish a "metaclass" hierarchy on top of TypeNode that mirrors the real hierarchy of metaclasses. I am still not sure if that's the best approach, but it does admit an alternative syntax:
macro class TypeNode
  @[Primitive]
  def ancestors
  end
end

macro class Int32
  # the entire body deals with the `Int32` macro "metaclass", so
  # every def is implicitly a `macro def`

  def ancestors
  end
end

# not allowed for macros, but allowed for the non-macro class analog (#11764)
macro def String.ancestors
end

And we can simply call them "defs" of "macro metaclasses", avoiding the terminology conflict altogether.

Oh, I like that! I like that these things are "scoped" inside a "macro" context.
But how would you define a top-level macro method with that syntax? Is it just macro def? I'm thinking I'd still like methods inside macro class to be called macro def just because if you see def ... without the surrounding context you can't immediately know if that's a method to be used at compile-time or not.
So maybe we only need macro def in that case, and macro class isn't really needed, because the type Int32 is the same inside or outside macros.

Would macro def also be used to define them within a non stdlib namespace as well? Or is the idea you'd also be able to do like macro class MyModule? But yea, if we're okay with just allowing the end user to override macro methods like they could with stdlib methods, then that syntax would definitely be more readable/flexible I'd say. I'm all for having an implementation that is a bit future facing to make the macro language implementation simpler longer term, which sounds like this approach would.

A slightly different idea: we reserve macro class to represent the AST node types in the macro language, without the Crystal::Macros part. After all, the types we use in the macro #is_a? are in an entirely separate namespace, do not physically reside under Crystal::Macros, and never conflict with non-macro types sharing the same names. Then normal types use macro def within the usual class. Example:
macro class ArrayLiteral
  @[Primitive(...)]
  macro def each_with_index(&); end

  @[Primitive(...)]
  macro def size; end

  macro def empty?
    # note: implicit `self`
    size == 0
  end

  macro def splat(trailing_string = nil)
    str = ""
    each_with_index do |v, i|
      str = "#{str.id}, " if i > 0
      str = "#{str.id}#{v}"
    end
    if trailing_string && !empty?
      str = "#{str.id}#{trailing_string.id}"
    end
    str.id
  end
end

# okay, not the AST node macro type
class ArrayLiteral
  macro def empty?
    # same as `ArrayLiteral.ancestors.empty?` in a macro context
    ancestors.empty? # => false
  end
end

# okay, not the AST node macro type either
class Crystal::Macros::ArrayLiteral
end

I like that! In the API docs I can imagine they will also live inside a different section.

Inside a macro class you define macro defs that happen to be like instance methods on the AST node. At the same time macro defs at a regular class/module operate like a metaclass method. This is odd because the same syntax create methods that are called in different ways. I propose we use regular method syntax inside a macro class to define methods of AST nodes (as primitives), and macro def syntax at regular classes/modules to define methods that are callable from the TypeNode.
macro class ArrayLiteral
  def foo
    "foo"
  end
end

class String
  macro def bar
    ancestors.foo
  end
end

{% p String.bar %} # prints "foo"

Anyone interested in getting a PoC together? Would love to see this gain some momentum.

The other day I realized the current macro defs are named like that because methods referring to {{ @type }} used to have the macro def syntax: #2565

@HertzDevil Yea, that's why I was thinking we could reuse that syntax since nothing is using it anymore. Tho, as you and others pointed out, there are other options depending on exact path we want to take this. I.e. The more focused approach of "just allow macro code to be reused by defining reusable macro methods" or treat this feature as a way to implement the existing macro methods/modify the methods available on the macro AST nodes.


Tooling: drop flake8, configure ruff

Why: Ruff is more powerful, flexible, and faster than flake8, with better defaults and integrated formatter.
FYI I also added corresponding editorconfig settings to help ensure that editors and formatters aren't fighting each other over the style defaults, but it's technically independent (and actually ignored by ruff currently :frowning_face:).

BTW my motivation is more to get off of flake8 than to rush to get onto ruff, but I like what I've seen of ruff so far and tox config makes it fairly painless to switch dependencies.
The set of checks I enabled seemed like a pretty uncontroversial set of basic checks, but we can totally customize later if any of them are giving people grief.
Also note I didn't batch reformat files through ruff and I'm not planning to try to enforce strict formatting policies or anything, but I did peek through the diff of formatting changes ruff would want to perform if we asked it to reformat everything and adjusted some settings to try to keep that suggested formatting pretty close to the existing versions where possible.

@mdengler FYI I went ahead and submitted the .editorconfig changes separately while I was waiting for review here. Mostly just looking for a gut check that switching to ruff looks reasonable.

Gonna go ahead and merge this one too. Can easily revert it later if needed.


Fix prvd.new() shorthand throwing a TypeError

seems like a recent regression too soo... might try using typeof setmetatable for this


network shows disconnected interface instead of connected

Since @Alexays asked for testing of @tperard's recent network changes in https://github.com/Alexays/Waybar/issues/388#issuecomment-849881941, I ran a few tests with master (5444a66) and noticed an issue:
On a computer with both a wireless interface (wlp3s0) and an ethernet interface (enp0s25), when the wireless interface goes down, Waybar displays information for the disconnected wireless interface rather than the connected ethernet interface.  To reproduce, using the following config:
{
  "modules-left": [
    "network"
  ],
  "network": {
    "format": "{ifname}:{ipaddr}/{cidr}",
    "format-disconnected": "{ifname}:Disconnected"
  }
}

Start with wireless connected and ethernet disconnected.
nmcli status reports:
DEVICE   TYPE      STATE         CONNECTION
wlp3s0   wifi      connected     WifiConn
enp0s25  ethernet  unavailable   --
lo       loopback  unmanaged     --

ip -4 -br addr reports:
lo               UNKNOWN        <IP_ADDRESS>/8
wlp3s0           UP             <IP_ADDRESS>/24

Start Waybar: waybar -c config -l trace.
  (Note: 0.9.5 shows enp0s25 when both are connected, then continues showing it when wlp3s0 is disconnected.)
Capture of stdout with -l trace during the procedure described above:
[2021-05-27 16:14:46.283] [info] Resources files: config, /home/kevin/.config/waybar/style.css
[2021-05-27 16:14:46.290] [debug] Output detection done: LVDS-1 (Unknown 0x213E 0x00000000)
[2021-05-27 16:14:46.293] [debug] network: new default route via if3
[2021-05-27 16:14:46.293] [debug] network: wlp3s0, new addr <IP_ADDRESS>/24
[2021-05-27 16:14:46.331] [debug] GTK widget tree:
window#waybar.background.LVDS-1.:dir(ltr)
  decoration:dir(ltr)
  box.horizontal:dir(ltr)
    box.horizontal.modules-left:dir(ltr)
      widget:dir(ltr)
        label#network:dir(ltr)
    box.horizontal.modules-center:dir(ltr)
    box.horizontal.modules-right:dir(ltr)

[2021-05-27 16:14:46.333] [info] Bar configured (width: 1600, height: 17) for output: LVDS-1
[2021-05-27 16:17:16.810] [debug] network: wlp3s0 addr deleted <IP_ADDRESS>/24

Thanks for working on it!
Kevin

Hi, thanks for testing!
I think I've managed to reproduce the issue when using NetworkManager, so I should be able to fix the issue.
Thanks.

Thanks for investigating and implementing a fix @tperard!
Unfortunately, while testing it I noticed a similar issue now occurs when changing connections in the opposite order (disconnecting ethernet after both connected).  I opened #1129 to track that issue.  Sorry to be the bearer of bad news.


Allow Multiple Workflow Events to be Expanded

Is your feature request related to a problem? Please describe.
When debugging a workflow run, it would be nice to see more than one expanded event history item.  This would especially be useful when one wants to see an activity input and the activity output.
Describe the solution you'd like
Be able to expand any number of of event items.  That said, there should also be a collapse all feature-- though one could reload the URL to close all expanded items.
Describe alternatives you've considered
Use 2 web browser tabs to be able to see both the inputs and outputs.

Fixed with https://github.com/temporalio/ui/pull/1694


[BUG] Unsupported parameter 'max_tokens' with o1-mini and o1-preview

Describe the bug
When calling either o1-mini or o1-preview we can only set maxTokens on the ChatCompletionsOptions object however upon calling the model this error is returned
Status code 400, "{ "error": { "message": "Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead.", "type": "invalid_request_error", "param": "max_tokens", "code": "unsupported_parameter" } }"

To Reproduce
Steps to reproduce the behavior:
Set maxTokens when calling o1-mini or o1-preview
Code Snippet
            .setMaxTokens(config.maxTokens())

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

I believe this is an issue related to Azure OpenAI Java API and not Java SDK for Cosmos DB? @JackMatthewRimmer I think your issue has been tagged incorrectly - can you please help clarify with more context on how you are making this call (i.e. provide a full code snippet, reference the client library you are using, etc)?

Thanks for reporting this @JackMatthewRimmer, @mssfang and @jpalvarezl could you follow-up on this.

@JackMatthewRimmer
maxTokens is not available in o1-preview and p1-mini models. We haven't added the support for max_completion_tokens yet. But it will be in the next service API version, 2024-09-01-preview.
Will keep you posted when we release next SDK version (ETA, before end of year).


How can I open swipeout manually?

//  open swipeout manually
, _open: function(direction) {
    this.refs.swipeoutContent.measure((ox, oy, width, height) => {
      this.setState({
        btnWidth: (width/5),
        btnsLeftWidth: this.props.left ? (width/5)*this.props.left.length : 0,
        btnsRightWidth: this.props.right ? (width/5)*this.props.right.length : 0,
        contentHeight: height,
        contentWidth: width,
      });
    });
    btnsRightWidth = this.state.btnsRightWidth;
    btnsLeftWidth = this.state.btnsLeftWidth;
    if (direction == 'right') {
      // open swipeout right
      this._tweenContent('contentPos', -btnsRightWidth);
      this.setState({ contentPos: -btnsRightWidth, openedLeft: false, openedRight: true });
    } else if (direction == 'left') {
      // open swipeout left
      this._tweenContent('contentPos', btnsLeftWidth);
      this.setState({ contentPos: btnsLeftWidth, openedLeft: true, openedRight: false });
    }
  }
,

I add this function to open swipeout manually, it works only when I touched swipeout content at least once. Actually I found solution without trying to touch once, which write the direct width in btnsRightWidth and btnsLeftWidth variable but it's not universal way at all. What do you think about?

https://github.com/dancormier/react-native-swipeout/issues/118

@iicdii Check it out! https://github.com/CandyOgre/react-native-swipeout


In 3D on Android transparent textures not displaying correctly

Godot version:
3.1.1 and higher
OS/device including version:
GLES2
Android
MOTOROLA E3 Android 6.0
CUBOT X11 Android 4.4.2
Issue description:
Perhaps I'm doing something wrong here. I'm trying to display a transparent texture in a 3d Node.
In the example I have 2 Sprite3Ds and a Mesh using the builtin Quadmesh and a material, both with transparent ticked. but when I run the project on an Android device the corners of the Texture should be rounded but in fact they are square which was not what I expected.
Working on Mac

Not Working Android

Steps to reproduce:
Run attached project on an Android device. Edges of the Godot Icon should be rounded not square.
Minimal reproduction project:
3dtest.zip

After a little research it seems the issue is with using a compression Mode of Video RAM and changing this to one of the other choices such as Lossless fixes my issue.

That's normal because the ETC VRAM compression format used on GLES2 does not support transparency.
If you reimport icon.png as Lossless, Lossy or Uncompressed, it should work.
@clayjohn Maybe something to mention in https://docs.godotengine.org/en/latest/tutorials/misc/gles2_gles3_differences.html#texture-compression ?

Thanks a lot anyway.


perf setup update: add grafana, misc fixes

need git pull --tags to get latest_release tag movement for fortio on vm, use DUR variable for duration

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
Assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ldemailly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
5ac4115e2bdbe4b60e9790cf2287f74651230335
link
/test e2e-bookInfo-envoyv2-v1alpha3

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

@ldemailly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
5ac4115e2bdbe4b60e9790cf2287f74651230335
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
1fb0e08ec23bd0717abbf03897f0ac4eaa6d231f
link
/test e2e-simple

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

/test e2e-simple
/test e2e-bookInfo-envoyv2-v1alpha3

@ldemailly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
1fb0e08ec23bd0717abbf03897f0ac4eaa6d231f
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
1fb0e08ec23bd0717abbf03897f0ac4eaa6d231f
link
/test e2e-simple

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

@ldemailly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
1fb0e08ec23bd0717abbf03897f0ac4eaa6d231f
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
1fb0e08ec23bd0717abbf03897f0ac4eaa6d231f
link
/test e2e-bookInfo-envoyv2-v1alpha3

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

New changes are detected. LGTM label has been removed.

@ldemailly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
079eef3e2e4442828b26358e668989b3369661e1
link
/test e2e-bookInfo-envoyv2-v1alpha3

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


"Lucianca", "Ungureni" are listed in the drop-down menu

Description:
When user writes ”Lucianca” and "Ungureni" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Lucianca"

Expected results
The location appears in the drop-down menu as "Sat Lucianca, DÂMBOVIȚA (Butimanu)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Ungureni"

Expected results
The location appears in the drop-down menu as "Sat Ungureni, DÂMBOVIȚA (Butimanu)".


Simulation results tables exported with metadata

Enable users to add an optional argument e.g. --metadata to their existing ecl2df calls, then use fmu-dataio under the hood to create metadata on export.
Acceptance Criteria
User can add optional argument --metadata (or similar) to their existing ecl2df calls in ERT config, then metadata is produced for outgoing tables.

[x] Add ecl2df as a utility in fmu-sumo -> #197

[x] Confirm with a Snorre case

[ ] Feedback from "someone" from Castberg

[ ] Feedback from Øyvind

[ ] Feedback from Rosebank

[ ] Define missing data.content

[ ] Feedback from JS (Marie Louise/Richy)

Done with some small known issues that will be followed up in separate tasks. Closing.


DEPRECATED OPTION

Upon connecting with a new fresh OpenVPN server I am greeted by the following warning:
DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning

Duplicate #847


feature suggestion - ability to add failed test steps log to testrail report alongside screenshot

Would be great to have an option to add failed test steps log into the testrail test report together with screenshot. sometimes screenshot does not show enough info, and when test had run in a pipeline then I have to go in there to check logs

Hi @RemigijusMazulis could you expose what kind of logging you need? I believe this plugin already added the error messages of failed tests.

I am talking about these logs saved into the test result. Now I do not see them

https://github.com/PeterNgTr/codeceptjs-testrail/blob/master/index.js#L143
I saw we add the error there, is it not enough @RemigijusMazulis ?

@kobenguyent I see only screenshot and no logs


Compiler option

Getting "unsupported int type of intermediate value, must cast intermediate value to type short or byte". I am able to compile using Java Card 3 Platform Development Kit but not with ant-javacard. The problem looks like related to compiler cmd parameters.  The class files generated by Java Card 3 Platform Development Kit are different in size(applet.class is 34kb from jcde and 21kb from ant-javacard) compared to ant-javacard. Is there a document pointing to recommended JAVAC cmd parameters.

Ant appends "-g:none" by default. "-g:lines,vars,source" is a mandatory field for javac since debug information in the class file is used by the convertor


Placeholder text

Would be nice to be able to pass a placeholder text to the input element.

Would have made a patch for it myself if i could get the project to run.
I get the same error for all of the examples:
ERROR in ./examples/static-data/app.js
Module build failed: ReferenceError: [BABEL] /.../react-autocomplete/examples/static-data/app.js: Unknown option: /.../react-autocomplete/.babelrc.presets
If you have any idea of what can cause this I'll have another go. If not I'll have to way til after my exams before I try again.

Hi!
You can use props.inputProps to provide props to the <input> element:
<Autocomplete
  inputProps={{ placeholder: 'Helpful examples' }}
/>

We're aware of the build problems. A workaround is to delete .babelrc.

Ah, sorry, I was not aware of that.
Thank you for a great module!

No worries, happy to help :) Once we land the 2.0 API you'll be able to use Autocomplete just as you would an <input>, i.e. we'll pass along any top-level props that aren't custom directly to the wrapped <input>.


model 2.1

Discussed in https://github.com/JoePenna/Dreambooth-Stable-Diffusion/discussions/131

Originally posted by OoAnikioO December 25, 2022
Does the notebook work with the model 2.1 with 768 images?
I tried to upload v2-1_768-nonema-pruned.ckpt rename to model with the yaml file and run a training but I got only errors
Global seed set to 23
Running on GPUs 0,
Loading model from model.ckpt
Traceback (most recent call last):
File "/workspace/Dreambooth-Stable-Diffusion/main.py", line 683, in
model = load_model_from_config(config, opt.actual_resume)
File "/workspace/Dreambooth-Stable-Diffusion/main.py", line 33, in load_model_from_config
model = instantiate_from_config(config.model)
File "/workspace/Dreambooth-Stable-Diffusion/ldm/util.py", line 87, in instantiate_from_config
return get_obj_from_str(config["target"])(**config.get("params", dict()), **kwargs)
File "/workspace/Dreambooth-Stable-Diffusion/ldm/util.py", line 95, in get_obj_from_str
return getattr(importlib.import_module(module, package=None), cls)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/workspace/Dreambooth-Stable-Diffusion/ldm/models/diffusion/ddpm.py", line 26, in
from ldm.models.autoencoder import VQModelInterface, IdentityFirstStage, AutoencoderKL
File "/workspace/Dreambooth-Stable-Diffusion/ldm/models/autoencoder.py", line 6, in
from taming.modules.vqvae.quantize import VectorQuantizer2 as VectorQuantizer
ModuleNotFoundError: No module named 'taming'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/workspace/Dreambooth-Stable-Diffusion/main.py", line 896, in
if trainer.global_rank == 0:
NameError: name 'trainer' is not defined

I got the same error with proton model, were you able to you fix it?

no, and i have like you the error with protogen
you have tested other models ?   realisticVision, dreamlike, .....


[1.13] Bump Mesos modules

High-level description
In a typical overlay configuration, there are two overlay networks: dcos and dcos6, and each of them have the save VXLAN VTEP IP addresses. When dropping agent records from the overlay state, deletion from the replicated log succeeds, but deletion from in-memory data structures fails because the same IP address is deleted twice which leads to a Mesos crash and fail-over.
Corresponding DC/OS tickets

DCOS_OSS-5597 Delete each VTEP IP address only once when deleting agent records.

Checklist for component/package updates:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[x] Included a test which will fail if code is reverted but test is not.
[ ] Test Results: The CI is broken.
[ ] Code Coverage: NA

@mesosphere-mergebot label Ready For Review


broken netip.Addr scan support v0.25.1-0.20240516073824-99941dbd5078

Hi. trying to migrate from v0.22.1 to v0.25.1-0.20240516073824-99941dbd5078 and:

fetching from db into netip_Addr fails - unsupported Scan, storing driver.Value type string into type *netip.Addr

how to reproduce:

take postgres 16.2
create table create table n (addr inet  [);]
and just go run<EMAIL_ADDRESS>and there will be error - unsupported Scan

Scan error on column index 0, name "addr": unsupported Scan, storing driver.Value type string into type *netip.Addr

rows, err := models.N.InsertMany(ctx, t.DB, n...)

I see where this bug comes from. I somehow didn't take into account that netip.Addr does not implement the Scan interface.
I'll have to create some wrapper type for it 🤦🏾

Should be fixed in v0.26.0. Let me know if it persists

nope. it is still there.
unsupported Scan, storing driver.Value type string into type *netip.Addr

// Network is an object representing the database table.
type Network struct {
	ID                    int64                `db:"id,pk,generated" `
	NetworkAddr           null.Val[netip.Addr] `db:"network_addr,generated" `
}
...
models.Networks.InsertMany(ctx, t.DB, networks...)

and here is created incorrect target https://github.com/stephenafamo/scan/blob/main/row.go#L68
![image](https://github.com/stephenafamo/bob/assets/19396845/8d566bd5-ea7b-43ca-b743-67f5a9996364)

You have to regenerate the models. It should now use a wrapper type which can be scanned into

oh, it's my fault. I forgot to update the generator to 0.26.
but with the new one (0.26) in the same place there is another problem.
Scan error on column index 5, name "network_addr": ParseAddr("<IP_ADDRESS>/24"): unexpected character (at "/24")

the postgres inet type can also handle subnets
https://www.postgresql.org/docs/current/datatype-net-types.html#DATATYPE-INET

The inet type holds an IPv4 or IPv6 host address, and optionally its subnet, all in one field.
The input format for this type is address/y where address is an IPv4 or IPv6 address and y is the number of bits in the netmask. If the /y portion is omitted, the netmask is taken to be 32 for IPv4 or 128 for IPv6, so the value represents just a single host. On display, the /y portion is suppressed if the netmask specifies a single host.

so its better to use netip.Prefix instead of netip.Addr

so its better to use netip.Prefix instead of netip.Addr

Great suggestion 👍🏾

This should now be fixed by #217.
Try it out and let me know.

Thanks a lot. everything is working. please tell me when to expect the tagged version?

Tagged v0.26.1 now.


Bug - Litewallet iOS

Describe the bug
Note: This is a different variation of an issue I previously logged.  Yesterday I received some LTC and it showed up in my history just fine.  It went through all the steps of processing (the percentage completion etc) and then showed as complete.  Balance was correctly updated and everything was good.  This morning, I sign in and see everything is good, but then all of a sudden, yesterday's transaction said something like "processing" and then magically disappeared from the history, and the balance was reduced.  So there is some sort of persistent sync issue, that seems like when you sign in, sometimes it may not sync correctly, and just lose the transaction.  It's like it connected to my history from before when I received the transaction.  Syncing the blockchain fixes it, but the transaction should not disappear right before my eyes.   I did notice something though.  When I synced with the blockchain, all my transactions showed as "complete" but when I signed in for the first time, I don't believe any of them showed any status except the one that disappeared, as mentioned above. So, it's like Litewallet had no memory of any of the transactions ever being completed, although only the most recent one disappeared.
To Reproduce
Receive LTC and verify it shows as complete in the history.  Close out of Litewallet.  Sign in to Litewallet the following day.  Look at the history.  If the most recent receipt shows as "processing", it will disappear shortly.
Expected behavior
Once a transaction is completed, it should remain in history.
Screenshots
Did not have time to capture.  The transaction was gone before I realized what was about to happen.
Desktop (please complete the following information):
Smartphone (please complete the following information):
iOS 14.4 iphone 11
Additional context

Thanks @jeff169
This is something I have seen as well.  The  issue is Litewallet has to sync at launch and whenever the difference in the local block height and the network block height.
So, the syncing is 'showing the making of the sausage'. And it may be that we are discussing how we present to the user.  So, if the sync sample rate is reduced, the transaction view will always stale for everyone. This is less than ideal.
It may be we need a better way of letting the user knowing the some local syncing updating is being calculated?

Isn't there a way to have it sync from the last login to the present time?  It seems like it's syncing to an older time, or not syncing at all and reverting to a prior time.  It seems like a mislignment of present time and Litewallet time.

I need to dig into the loafwallet-ore lib. Its a good idea. But considering the dev time , I may have to just to fix the way it'
s updated


Copy over provider session & remove qiskit-ibm-provider

Summary
The last place we are importing qiskit-ibm-provider is in ibm_backend for backend.run() sessions functionality. Since we want to completely remove qiskit-ibm-provider as a dependency, we can copy over the imported file as an intermediary step before #1280.
I have not had chance to completely test the unification of the sessions in #1280 and would prefer not to merge that PR(yet) with so many moving parts regarding Qiskit 1.0 and the V2 primitives.
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-8 of 34 (76.47%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 69.286%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/provider_session.py
24
32
75.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
5520

Relevant Lines:
7967

💛  - Coveralls


Fixed the readthedocs.org build but the docs appear to still be outdated?

The other day I fixed the readthedocs.org build but the docs appear to still be outdated?   Just judging by the CHANGELOG being from Sept ... any help would be appreciated on this.

I am not sure if this is true or if just the CHANGELOG is not getting updated.   Definitely that part of the docs is outdated.   Requires more testing.

I fixed this tonight.


💬 [Question] Guest link to meeting is shown also to non-moderators

💬 Question

Guest link to meeting is shown also to non-moderators.
Is this intentional?

Vorschlag: Konsistenz - nur Moderatoren


Vehicle total milage not changing

I have noticed that my vehicle total milage hasn't change in many months... any one else noticed this? The rest of the data is correct and is up to date. Thanks

If you mean the entity named sensor.<my_id_3>_odometer, mine is updating normally:

(The gap in the middle is OK – the server was intentionally shut down.)
Volkswagen We Connect ID version 0.2.3
Home Assistant version 2024.7.4

How strange.. for some reason my milage stops at the end of January...

So I've installed a fresh Home assistant on a separate PC and installed the integration... still the same 31765km... which isn't the cars odometer reading! I don't get why...

[...] which isn't the cars odometer reading!

Does the official Android / iOS Volkswagen app show the same mileage as the car’s odometer, or is it also stuck at 31,765km?
In my case with an ID.3 and the Volkswagen app for Android (v3.17.0 downloaded from the Google Play Store), the initial app screen has a Vehicle Health Report link that leads to another screen that shows the same mileage shown in Home Assistant, and the car.

im using the iPhone app and it doesn't show mileage.. unfortunately

I've just loaded another app on my phone celled evvee, this links to the VW servers and its showing my milage to be 19738miles which is 31765 KM, so clearly this is an issue on VW side.

ok, its a known problem having just googled it.. synchronised it with the car and now showing correct mileage. sorry for the NON issue!


Update Timer_Obscure_Behaviour.md

Just a spelling fix. Also, how is the timer affected when writing to DIV? Is it reset too?

For all intents and purposes, rTIMA is essentially a separate counter which ticks according to a set frequency described in rTAC. This frequency is tied to rDIV and its internal bits. All writing rDIV does is reset rDIV and its internal bits; it does not reset rTIMA. But since rDIV and its internal bits are used to source the frequency of rTIMA's ticks, it will be affected by the rDIV write.

For all intents and purposes, rTIMA is essentially a separate counter which ticks according to a set frequency described in rTAC. This frequency is tied to rDIV and its internal bits. All writing rDIV does is reset rDIV and its internal bits; it does not reset rTIMA. But since rDIV and its internal bits are used to source the frequency of rTIMA's ticks, it will be affected by the rDIV write.

Well, it may be affected: TIMA is updated when a falling edge is detected on a certain bit of DIV; which bit this is is selected by TAC. Since writing to DIV resets it, it may cause the observed bit to be reset, thus incrementing TIMA.

Well, it may be affected: TIMA is updated when a falling edge is detected on a certain bit of DIV; which bit this is is selected by TAC. Since writing to DIV resets it, it may cause the observed bit to be reset, thus incrementing TIMA.

Cool! Thanks for the information! @CasualPokePlayer and @ISSOtm

Cool! Thanks for the information! @CasualPokePlayer and @ISSOtm


bug: there are 2 unique indexes in the migration file when combining IndexWhere and Unique

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

There are 2 unique indexes in the migration file when combining IndexWhere and Unique
https://github.com/ent/ent/issues/1472
https://github.com/ent/ent/pull/2944

Expected Behavior 🤔

Only one unique index is generated

Steps to Reproduce 🕹

The schema code

func (Pet) Indexes() []ent.Index {
	return []ent.Index{
		index.Fields("abc_id").Unique().
			Annotations(
				entsql.IndexWhere(`(((status)::text = 'STATUS_1'::text) OR ((status)::text = 'STATUS_99'::text))`),
			),
	}
}

The migration file is generated

-- create index "pet_abc_id" to table: "pets"
CREATE UNIQUE INDEX "pet_abc_id" ON "pets" ("abc_id") WHERE (((status)::text = 'STATUS_1'::text) OR ((status)::text = 'STATUS_99'::text));
-- create index "pets_abc_id_key" to table: "pets"
CREATE UNIQUE INDEX "pets_abc_id_key" ON "pets" ("abc_id");

Your Environment 🌎

Tech
Version

Go
1.19.1

Ent
v0.11.3-0.20220922085605-0f5cba6144c7

atlas
v0.7.1-0.20220922152615-58d4f7e4f6d3

Database
Postgres

Driver
https://github.com/lib/pq/releases/tag/v1.10.7

Hey @dodangquan, can you please provide a complete example using https://github.com/ent/bug?


Cannot request update when writing to external flash

Describe the bug
Nordic's qspi does not support writing if data comes from internal flash. The buffer must be in RAM.
https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/drivers/src/nrfx_qspi.c#L355
When the image magic is written the buffer resides in flash.
https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/dfu/boot/mcuboot.c#L100
https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/dfu/boot/mcuboot.c#L386
To Reproduce
Steps to reproduce the behavior:
Create any setup where dfu is done through the external flash.
Expected behavior
Image magic should be writable.
Impact
Showstopper
Screenshots or console output
N/A
Environment (please complete the following information):
master
Additional context
N/A

@nvlsianpu

It is enough to write to flash through the buffer in RAM. I copier the data to stack allocated array and performed write. Everything works. I think this is the best change to do so there will be no additional complexity done on the qspi driver side.
The other way to do it would be to handle it in the driver (detect that the buffer is not compatible and make a local copy in RAM). This may be more generic.

I thought that https://github.com/zephyrproject-rtos/zephyr/pull/25971/ introduced support for from flash writes.
@pabigot

AFAIK #25971 works, but if the amount of data being written is 4 or more bytes you need to set CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE=16` or whatever size buffer you want for the stack-based RAM region.  Only smaller values (which I know are used in MCUBoot) are handled without that option.

I see. CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE is not yet present downstream so I have not seen it.

It's a forward-port of an equivalent functionality that I thought made it into 1.3, but maybe it didn't.  @hakonfam

There is NORDIC_QSPI_NOR_FLASH_ALLOW_STACK_USAGE_FOR_DATA_IN_FLASH in 1.3 indeed. I overlooked it.
When enabled magic is written correctly. Thanks @pabigot


fix building on FreeBSD (dl is linux only, bsd has it with libc)

seems like not relevant for development branch

Thanks for the pull request. Normally, we only accept PRs targeting the development branch, see our contribution guidelines for the details.
The issues still is relevant for the development branch. Instead of relying on CMAKE_SYSTEM_NAME, I suggest to use a find_library call for dl and link to it only if the resulting variable is valid.

Strange but on development branch I can't see manual dl linking there
https://github.com/CppMicroServices/CppMicroServices/blob/development/CMakeLists.txt

Yes, the project structure changed. Now it is here: https://github.com/CppMicroServices/CppMicroServices/blob/development/framework/CMakeLists.txt#L23

@saschazelzer okay I'll try to elaborate it


Registration approval

This completes admin registration approval. The only remaining thing to be done regarding this is to send users an email telling them their account has been approved/deleted.
Still to be implemented for admin page:

Post approval
Account suspension
View posts
View users

LGTM!

LGTM!


Better accessibility

I've been planning on implementing built-in a11y. Based on Gatsby and Fable Tech Labs research, the recommended approach was to:

Provide a skip link that takes focus on a route change within the site, with a label that indicates what the link will do when activated: e.g. "skip to main navigation".

Include an ARIA Live Region on page load. On a route change, append text to it indicating the current page, e.g. "Portfolio page".

Implementing a common API for these can be tricky and should be discussed before moving forward. Hence feedback is appreciated!
Skip link
Something similar to @reach/skip-nav, provide utility components to handle skip navigation. Whenever $route.path is changed, focus on the global skip link.
Questions:

How about multiple nested content, how would it link to them?

ARIA live region
A utility component to render a route announcer, similar to how Gatsby does it.
Questions:

Can it be built into the <RouterView />?
How will the announcement text be localized?
How will the announcement text refer to the navigated page? e.g. "Navigated to ???"
Do we need to expose an extra name field when defining routes?

Manually move focus

Although this isn't a recommendation from the research, this might address some of skip link's shortcomings.

Dynamically prepend a focused div to the top-most changed route. So after navigation and the user "tabs", it will navigate into the new route.

It's been a busy month for me but I thought I'll give an update.
Skip link
Looking around several implementations, skip links seems to work best for pages with a single content. I can't find any information about nested content (nested routes), which leads me to believe that skip links may not be right solution for this issue.
ARIA live region
This feature would be fairly easy to implement, the only issue is the extra name field for the route records, which I find may be confusing for vue-router users who would assume that it's possible to navigate by name (which I don't plan to support). I've also looked into other possible alternatives to infer the announcement text, but all has it own tradeoffs.
Still, users can also implement this feature themselves and it's quite a simple process (I'll probably do a write-up on this). This way the live regions can be customized how ever they want and can include features like internationalization.
Auto focus
Likely the same focus management mechanism as @reach/router, but currently reach handles this by wrapping a div and focuses on it, which can potentially break styles. There's display: contents though support isn't great yet.
To conclude all this, I would prefer holding back all these features for now, except ARIA live region which I may revisit again.


Scope: Define Use Cases

In what scenario will the aforementioned personas use this?

Use Case 1

Persona: Self-Learner
Scenario: The Self-Learner is organizing a new learning resource using nlog, the learning resources requires no annotation.
Use Case: The user runs the import command (undecided via cli, browser extension, or web app) and sees after a short period of time for the new resource to appear in Notion (Media (including web clip) & Training Log).

Use Case 2

Persona: Self-Learner
Scenario: The Self-Learner is organizing a new learning resource using nlog, the learning resources will be annotated.
Use Case: The user runs the import command (undecided via cli, browser extension, or web app) and sees after a short period of time for the new resource to appear in Notion (Media (including web clip) & Training Log). The user also sees after a short period of time for the new resource to be now populated in their OneNote, ready for annotation.

Use Case 3

Persona: Self-Learner
Scenario: The Self-Learner is starting to consume a new learning resource using nlog.
Use Case: The user runs the start command (undecided via cli, browser extension, or web app) and sees after a short period of time for the time tracking for the learning resource in Notion Training Logs has started.

Use Case 4

Persona: Self-Learner
Scenario: The Self-Learner is organizing and starting to consume a new learning resource using nlog, the learning resources requires no annotation.
Use Case: Use Case 1 + Use Case 3

Use Case 5

Persona: Self-Learner
Scenario: The Self-Learner is organizing and starting to consume a new learning resource using nlog, the learning resources will be annotated.
Use Case: Use Case 2 + Use Case 3

Use Case 6
(undecided: may be automatically performed after a week of open training)

Persona: Self-Learner
Scenario: The Self-Learner is done consuming a new learning resource using nlog
Use Case: The user runs the stop command (undecided via cli, browser extension, or web app) and sees after a short period of time for the time tracking for the learning resource in Notion Training Logs has stopped.

Use Case 7

Persona: Evaluator
Scenario: The Evaluator is requesting a report between two time intervals
Use Case: The user runs the report command (undecided via cli, browser extension, or web app) and is given (undecided method (email, return, etc.) and format (pdf, html, md)) after a short period of time a report of time spent and resources used of all categories by category/alignment/path.

Use Case 8

Persona: Evaluator
Scenario: The Evaluator is requesting a report between two time intervals, filtered by the category/alignment/path
Use Case: The user runs the report command (undecided via cli, browser extension, or web app) and is given (undecided method (email, return, etc.) and format (pdf, html, md)) after a short period of time a report of time spent and resources used of the specific category/alignment/path filtered.

Added docs in wiki under https://github.com/mitchellciupak/nlog/wiki/Scope#use-cases


feat update meta

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


Image doesn't build

Summary
I'm trying to install Saleor by documentation: https://docs.saleor.io/docs/3.x/developer/installation. I cloned the repository and started docker-compose build. I can see it.
Steps to reproduce

git clone https://github.com/saleor/saleor-platform.git --recursive --jobs 3
cd saleor-platform
docker-compose build

A link to a reproduction repository
No response
What OS are you using?
Windows
Your next.config.js file

`next.config.js`
const withBundleAnalyzer = require("@next/bundle-analyzer")({
  enabled: process.env.ANALYZE === "true",
});

const apiURL = new URL(process.env.NEXT_PUBLIC_API_URI);
const allowedImageDomains = process.env.NEXT_PUBLIC_ALLOWED_IMAGE_DOMAINS
  ? process.env.NEXT_PUBLIC_ALLOWED_IMAGE_DOMAINS.split(",")
  : [];
const imageConversionFormats = process.env.NEXT_PUBLIC_IMAGE_CONVERSION_FORMATS
  ? process.env.NEXT_PUBLIC_IMAGE_CONVERSION_FORMATS.split(",")
  : [];

module.exports = withBundleAnalyzer({
  reactStrictMode: true,
  swcMinify: true,
  images: {
    domains: [apiURL.hostname, ...allowedImageDomains],
    formats: imageConversionFormats,
  },
  async headers() {
    return [
      {
        source: "/(.*)",
        headers: [
          {
            key: "x-content-type-options",
            value: "nosniff",
          },
          { key: "x-xss-protection", value: "1" },
          { key: "x-frame-options", value: "DENY" },
          {
            key: "strict-transport-security",
            value: "max-age=31536000; includeSubDomains",
          },
        ],
      },
    ];
  },
  experimental: {
    reactRoot: true,
  },
});

Builds logs (or link to your logs)

Build logs
$ docker-compose build
[+] Building 64.4s (35/52)
 => [saleor-platform_dashboard internal] load build definition from Dockerfile.dev                                                                             0.1s
 => => transferring dockerfile: 345B                                                                                0.0s
 => [saleor-platform_worker internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 2.29kB                                                                                0.0s
 => [saleor-platform_react-storefront internal] load build definition from Dockerfile.dev                                                                      0.0s
 => => transferring dockerfile: 474B                                                                                0.0s
 => [saleor-platform_api internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 2.29kB                                                                                0.0s
 => [saleor-platform_dashboard internal] load .dockerignore                                                                                0.1s
 => => transferring context: 59B                                                                                0.0s
 => [saleor-platform_worker internal] load .dockerignore                                                                                0.0s
 => => transferring context: 93B                                                                                0.0s
 => [saleor-platform_react-storefront internal] load .dockerignore                                                                                0.1s
 => => transferring context: 54B                                                                                0.0s
 => [saleor-platform_api internal] load .dockerignore                                                                                0.1s
 => => transferring context: 93B                                                                                0.0s
 => [saleor-platform_dashboard internal] load metadata for docker.io/library/node:14                                                                           2.1s
 => [saleor-platform_worker internal] load metadata for docker.io/library/python:3.9-slim                                                                      2.0s
 => [saleor-platform_worker internal] load metadata for docker.io/library/python:3.9                                                                           2.1s
 => [saleor-platform_react-storefront internal] load metadata for docker.io/library/node:16                                                                    2.2s
 => [saleor-platform_dashboard internal] load build context                                                                                3.0s
 => => transferring context: 36.17MB                                                                                3.0s
 => [saleor-platform_dashboard 1/5] FROM docker.io/library/node:14@sha256:ce156f9b2e9dbe73139cf0619a71188960e6c9eaba0ff832a5dfa0febf9eee27                     0.0s
 => [saleor-platform_api stage-1 1/9] FROM docker.io/library/python:3.9-slim@sha256:c01a2db78654c1923da84aa41b829f6162011e3a75db255c24ea16fa2ad563a0           0.0s
 => CACHED [saleor-platform_api stage-1 2/9] RUN groupadd -r saleor && useradd -r -g saleor saleor                                                             0.0s
 => CACHED [saleor-platform_api stage-1 3/9] RUN apt-get update   && apt-get install -y   libcairo2   libgdk-pixbuf2.0-0   liblcms2-2   libopenjp2-7   libpan  0.0s
 => CACHED [saleor-platform_api stage-1 4/9] RUN mkdir -p /app/media /app/static   && chown -R saleor:saleor /app/                                             0.0s
 => [saleor-platform_api build-python 1/5] FROM docker.io/library/python:3.9@sha256:51c996c8c65d826d20c61336353371961996e053cad353745661b24b60e711f5           0.0s
 => [saleor-platform_api internal] load build context                                                                                3.0s
 => => transferring context: 30.91MB                                                                                2.9s
 => [saleor-platform_worker internal] load build context                                                                                2.9s
 => => transferring context: 30.91MB                                                                                2.8s
 => [saleor-platform_react-storefront 1/9] FROM docker.io/library/node:16@sha256:a13d2d2aec7f0dae18a52ca4d38b592e45a45cc4456ffab82e5ff10d8a53d042              0.0s
 => [saleor-platform_react-storefront internal] load build context                                                                                0.9s
 => => transferring context: 4.16MB                                                                                0.8s
 => CACHED [saleor-platform_react-storefront 2/9] WORKDIR /app                                                                                0.0s
 => CACHED [saleor-platform_react-storefront 3/9] RUN npm install -g pnpm                                                                                0.0s
 => CACHED [saleor-platform_react-storefront 4/9] RUN apt-get update && apt-get install -y nginx                                                               0.0s
 => CACHED [saleor-platform_react-storefront 5/9] COPY ./nginx/dev.conf /etc/nginx/conf.d/default.conf                                                         0.0s
 => CACHED [saleor-platform_react-storefront 6/9] COPY package.json ./                                                                                0.0s
 => CACHED [saleor-platform_react-storefront 7/9] COPY pnpm-lock.yaml ./                                                                                0.0s
 => ERROR [saleor-platform_react-storefront 8/9] RUN pnpm install                                                                                57.7s
 => CACHED [saleor-platform_worker build-python 2/5] RUN apt-get -y update   && apt-get install -y gettext   && apt-get clean   && rm -rf /var/lib/apt/lists/  0.0s
 => CACHED [saleor-platform_worker build-python 3/5] COPY requirements_dev.txt /app/                                                                           0.0s
 => CACHED [saleor-platform_worker build-python 4/5] WORKDIR /app                                                                                0.0s
 => CACHED [saleor-platform_dashboard 2/5] WORKDIR /app                                                                                0.0s
 => CACHED [saleor-platform_dashboard 3/5] COPY package*.json ./                                                                                0.0s
 => [saleor-platform_dashboard 4/5] RUN npm install                                                                                58.9s
 => [saleor-platform_worker build-python 5/5] RUN pip install -r requirements_dev.txt                                                                         59.0s
 => => #      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 97.5/97.5 KB 543.8 kB/s eta 0:00:00
 => => # Collecting codecov==2.1.12
 => => #   Downloading codecov-2.1.12-py2.py3-none-any.whl (16 kB)
 => => # Collecting coverage==6.3.2
 => => #   Downloading coverage-6.3.2-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (210 kB)
 => => #      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 210.7/210.7 KB 77.7 kB/s eta 0:00:00
------
 > [saleor-platform_react-storefront 8/9] RUN pnpm install:
#0 2.583 Progress: resolved 1, reused 0, downloaded 0, added 0
#0 3.616 Progress: resolved 15, reused 0, downloaded 12, added 0
#0 4.622 Progress: resolved 24, reused 0, downloaded 21, added 0
#0 5.625 Progress: resolved 35, reused 0, downloaded 31, added 0
#0 6.644 Progress: resolved 44, reused 0, downloaded 41, added 0
#0 7.646 Progress: resolved 49, reused 0, downloaded 45, added 0
#0 8.649 Progress: resolved 52, reused 0, downloaded 51, added 0
#0 9.649 Progress: resolved 54, reused 0, downloaded 53, added 0
#0 10.65 Progress: resolved 55, reused 0, downloaded 54, added 0
#0 11.65 Progress: resolved 55, reused 0, downloaded 55, added 0
#0 12.66 Progress: resolved 95, reused 0, downloaded 64, added 0
#0 13.67 Progress: resolved 164, reused 0, downloaded 88, added 0
#0 14.68 Progress: resolved 236, reused 0, downloaded 132, added 0
#0 15.68 Progress: resolved 294, reused 0, downloaded 175, added 0
#0 16.69 Progress: resolved 333, reused 0, downloaded 202, added 0
#0 17.70 Progress: resolved 415, reused 0, downloaded 247, added 0
#0 18.70 Progress: resolved 460, reused 0, downloaded 283, added 0
#0 19.71 Progress: resolved 531, reused 0, downloaded 325, added 0
#0 20.82 Progress: resolved 633, reused 0, downloaded 368, added 0
#0 21.83 Progress: resolved 710, reused 0, downloaded 415, added 0
#0 22.83 Progress: resolved 771, reused 0, downloaded 472, added 0
#0 23.84 Progress: resolved 829, reused 0, downloaded 499, added 0
#0 24.85 Progress: resolved 876, reused 0, downloaded 523, added 0
#0 25.86 Progress: resolved 934, reused 0, downloaded 555, added 0
#0 26.87 Progress: resolved 957, reused 0, downloaded 580, added 0
#0 27.89 Progress: resolved 989, reused 0, downloaded 598, added 0
#0 28.89 Progress: resolved 1028, reused 0, downloaded 610, added 0
#0 29.91 Progress: resolved 1046, reused 0, downloaded 625, added 0
#0 30.92 Progress: resolved 1078, reused 0, downloaded 644, added 0
#0 31.92 Progress: resolved 1118, reused 0, downloaded 681, added 0
#0 32.92 Progress: resolved 1154, reused 0, downloaded 711, added 0
#0 33.98 Progress: resolved 1207, reused 0, downloaded 728, added 0
#0 34.98 Progress: resolved 1359, reused 0, downloaded 762, added 0
#0 36.56 Progress: resolved 1404, reused 0, downloaded 779, added 0
#0 37.92 Progress: resolved 1558, reused 0, downloaded 781, added 0
#0 38.98 Progress: resolved 1574, reused 0, downloaded 788, added 0
#0 40.12 Progress: resolved 1626, reused 0, downloaded 812, added 0
#0 40.17 Packages: +817
#0 40.17 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#0 41.22 Progress: resolved 1626, reused 0, downloaded 813, added 0
#0 41.52 Packages are hard linked from the content-addressable store to the virtual store.
#0 41.52   Content-addressable store is at: /root/.local/share/pnpm/store/v3
#0 41.52   Virtual store is at:             node_modules/.pnpm
#0 42.23 Progress: resolved 1626, reused 0, downloaded 813, added 98
#0 43.25 Progress: resolved 1626, reused 0, downloaded 813, added 303
#0 44.24 Progress: resolved 1626, reused 0, downloaded 813, added 513
#0 45.24 Progress: resolved 1626, reused 0, downloaded 813, added 697
#0 46.87 Progress: resolved 1626, reused 0, downloaded 813, added 787
#0 47.87 Progress: resolved 1626, reused 0, downloaded 813, added 815
#0 49.74 Progress: resolved 1626, reused 0, downloaded 814, added 815
#0 50.93 Progress: resolved 1626, reused 0, downloaded 815, added 817, done
#0 51.18 .../node_modules/core-js-pure postinstall$ node -e "try{require('./postinstall')}catch(e){}"
#0 51.35 .../node_modules/core-js-pure postinstall: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
#0 51.35 .../node_modules/core-js-pure postinstall: The project needs your help! Please consider supporting of core-js:
#0 51.35 .../node_modules/core-js-pure postinstall: > https://opencollective.com/core-js
#0 51.35 .../node_modules/core-js-pure postinstall: > https://patreon.com/zloirock
#0 51.35 .../node_modules/core-js-pure postinstall: > https://paypal.me/zloirock
#0 51.35 .../node_modules/core-js-pure postinstall: > bitcoin: bc1qlea7544qtsmj2rayg0lthvza9fau63ux0fstcz
#0 51.35 .../node_modules/core-js-pure postinstall: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
#0 51.37 .../node_modules/core-js-pure postinstall: Done
#0 53.36
#0 53.36 ><EMAIL_ADDRESS>prepare /app
#0 53.36 > husky install
#0 53.36
#0 53.44 fatal: not a git repository (or any of the parent directories): .git
#0 53.45
#0 53.45 dependencies:
#0 53.45 + @apollo/client 3.5.10
#0 53.45 + @formatjs/swc-plugin 1.4.0
#0 53.45 + @formatjs/ts-transformer 3.9.2
#0 53.45 + @graphql-codegen/typescript-apollo-client-helpers 2.1.15
#0 53.45 + @headlessui/react 1.5.0
#0 53.45 + @heroicons/react 1.0.5
#0 53.45 + @saleor/sdk 0.4.4
#0 53.45 + @stripe/react-stripe-js 1.7.0
#0 53.45 + @stripe/stripe-js 1.26.0
#0 53.45 + @tailwindcss/aspect-ratio 0.4.0
#0 53.45 + @tailwindcss/forms 0.5.0
#0 53.45 + @tailwindcss/typography 0.5.2
#0 53.45 + clsx 1.1.1
#0 53.45 + dotenv 16.0.0
#0 53.45 + dotenv-cli 5.1.0
#0 53.45 + editorjs-blocks-react-renderer 1.2.4
#0 53.45 + graphql 16.3.0
#0 53.45 + next 12.1.4
#0 53.45 + next-seo 5.3.0
#0 53.45 + next-sitemap 2.4.3
#0 53.45 + next-usequerystate 1.7.0
#0 53.45 + react 18.0.0
#0 53.45 + react-dom 18.0.0
#0 53.45 + react-intl 5.24.6
#0 53.45 + tailwind-scrollbar-hide 1.1.7
#0 53.45
#0 53.45 devDependencies:
#0 53.45 + @formatjs/cli 4.8.2
#0 53.45 + @graphql-codegen/add 3.1.1
#0 53.45 + @graphql-codegen/cli 2.6.2
#0 53.45 + @graphql-codegen/introspection 2.1.1
#0 53.45 + @graphql-codegen/typescript 2.4.8
#0 53.45 + @graphql-codegen/typescript-operations 2.3.5
#0 53.45 + @graphql-codegen/typescript-react-apollo 3.2.11
#0 53.45 + @next/bundle-analyzer 12.1.4
#0 53.45 + @types/qs 6.9.7
#0 53.45 + @types/react 17.0.43
#0 53.45 + @typescript-eslint/eslint-plugin 5.17.0
#0 53.45 + @typescript-eslint/parser 5.17.0
#0 53.45 + autoprefixer 10.4.2
#0 53.45 + eslint 8.12.0
#0 53.45 + eslint-config-airbnb 19.0.4
#0 53.45 + eslint-config-next 12.1.0
#0 53.45 + eslint-config-prettier 8.4.0
#0 53.45 + eslint-plugin-formatjs 3.0.0
#0 53.45 + eslint-plugin-import 2.25.4
#0 53.45 + eslint-plugin-jsx-a11y 6.5.1
#0 53.45 + eslint-plugin-react 7.29.4
#0 53.45 + eslint-plugin-react-hooks 4.3.0
#0 53.45 + eslint-plugin-simple-import-sort 7.0.0
#0 53.45 + husky 7.0.4
#0 53.45 + pathpida 0.18.1
#0 53.45 + postcss 8.4.12
#0 53.45 + prettier 2.6.2
#0 53.45 + react-hook-form 7.29.0
#0 53.45 + react-use 17.3.2
#0 53.45 + tailwindcss 3.0.23
#0 53.45 + typescript 4.6.3
#0 53.45
#0 53.46  ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies
#0 53.46
#0 53.46 .
#0 53.46 ├─┬ @graphql-codegen/typescript-react-apollo
#0 53.46 │ └── ✕ missing peer<EMAIL_ADDRESS>#0 53.46 ├─┬ @graphql-codegen/typescript
#0 53.46 │ └─┬ @graphql-codegen/visitor-plugin-common
#0 53.46 │   └─┬ @graphql-tools/relay-operation-optimizer
#0 53.46 │     └─┬ relay-compiler
#0 53.46 │       └── ✕ unmet peer<EMAIL_ADDRESS>found 16.3.0
#0 53.46 ├─┬ @saleor/sdk
#0 53.46 │ ├── ✕ unmet peer<EMAIL_ADDRESS>found 16.3.0
#0 53.46 │ └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.0.0
#0 53.46 ├─┬ react-use
#0 53.46 │ ├── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.0.0
#0 53.46 │ └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.0.0
#0 53.46 ├─┬ @apollo/client
#0 53.46 │ └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.0.0
#0 53.46 ├─┬ @stripe/react-stripe-js
#0 53.46 │ ├── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.0.0
#0 53.46 │ └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.0.0
#0 53.46 ├─┬ editorjs-blocks-react-renderer
#0 53.46 │ └─┬ html-react-parser
#0 53.46 │   └── ✕ unmet peer<EMAIL_ADDRESS>|| 15 || 16 || 17": found 18.0.0
#0 53.46 └─┬ react-intl
#0 53.46   └── ✕ unmet peer<EMAIL_ADDRESS>|| 17": found 18.0.0
#0 53.46 Peer dependencies that should be installed:
#0 53.46<EMAIL_ADDRESS>#0 53.46
#0 53.46 hint: If you want peer dependencies to be automatically installed, add "auto-install-peers=true" to an .npmrc file at the root of your project.
#0 53.46 hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.
#0 53.46
------
failed to solve: executor failed running [/bin/sh -c pnpm install]: exit code: 1

Function logs

Function logs
# Paste logs here

Updating these two config auto-install-peers and strict-peer-dependencies for pnpm did the trick for me,
Updated Dockerfile.dev
`FROM node:16
WORKDIR /app
Setup pnpm package manager
RUN npm install -g pnpm
Setup proxy to API used in saleor-platform
RUN apt-get update && apt-get install -y nginx
COPY ./nginx/dev.conf /etc/nginx/conf.d/default.conf
COPY package.json ./
COPY pnpm-lock.yaml ./
RUN pnpm config set auto-install-peers true
RUN pnpm config set strict-peer-dependencies false
RUN pnpm install
COPY . .
ARG API_URI
ENV API_URI ${API_URI:-http://localhost:8000/graphql/}
EXPOSE 3000
CMD pnpm dev -- --hostname <IP_ADDRESS>
`

For further problems, see this issue: https://github.com/saleor/saleor/issues/9764.
This bug makes running the first instructions you see in the documentation unsuccessful, so it can determine one's experience with Saleor for good. For that reason, I think we should try to find a permanent solution for it.

Related
https://github.com/saleor/react-storefront/issues/275

https://github.com/saleor/saleor-platform/pull/158 was merged, which means react-storefront was updated to the newest version.
It applies a fix for pnpm issue.
The issue should be solved, so I close this one.