DDEV fails to start : failed to solve: rpc error: code = Unknown desc = no build stage in current context

Is there an existing issue for this?

[X] I have searched the existing issues

Output of ddev debug test
Expand `ddev debug test` diagnostic information
➜  stacy-frontend git:(develop) ✗ ddev debug test
Running bash [-c /tmp/test_ddev.sh]
OS Information: Linux manset 6.2.0-37-generic #38~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov  2 18:01:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
User information: uid=1000(chub) gid=1000(chub) groups=1000(chub),4(adm),24(cdrom),27(sudo),30(dip),33(www-data),46(plugdev),50(staff),120(lpadmin),132(lxd),133(sambashare),998(docker)
DDEV version:  ITEM             VALUE
 DDEV version     v1.19.0
 architecture     amd64
 db               drud/ddev-dbserver-mariadb-10.3:v1.19.0
 dba              phpmyadmin:5
 ddev-ssh-agent   drud/ddev-ssh-agent:v1.19.0
 docker           24.0.7
 docker-compose   v2.2.3
 docker-platform  manset
 mutagen          0.12.0
 os               linux
 router           drud/ddev-router:v1.19.0
 web              drud/ddev-webserver:v1.19.0-1
======= DDEV global info =========
Global configuration:
instrumentation-opt-in=true
omit-containers=[]
mutagen-enabled=false
nfs-mount-enabled=false
router-bind-all-interfaces=false
internet-detection-timeout-ms=750
disable-http2=false
use-letsencrypt=false
letsencrypt-email=
table-style=default
simple-formatting=false
auto-restart-containers=false
use-hardened-images=false
fail-on-hook-fail=false
required-docker-compose-version=
use-docker-compose-from-path=false
no-bind-mounts=false

======= DOCKER info =========
docker location: -rwxr-xr-x 1 root root 35939040 oct.  26 11:07 /usr/bin/docker
======= Mutagen Info =========
======= Docker Info =========
Docker platform: manset
Using docker context: default (unix:///var/run/docker.sock)
docker-compose: v2.2.3
Using DOCKER_HOST=unix:///var/run/docker.sock
Docker version: 24.0.7
Able to run simple container that mounts a volume.
Able to use internet inside container.
Docker disk space:
Filesystem                Size      Used Available Use% Mounted on
overlay                 467.9G     68.0G    376.1G  15% /

unable to create project at project root '/home/var/www/etnic/MFWB': project root /home/var/www/etnic/MFWB does not exist
unable to create project at project root '/home/var/www/etnic/intranetmfwbv3': project root /home/var/www/etnic/intranetmfwbv3 does not exist
The ddev-ssh-agent container has been removed. When you start it again you will have to use 'ddev auth ssh' to provide key authentication again.
Existing docker containers:
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
Creating a new ddev project config in the current directory (/home/chub/tmp/tryddevproject-26515)
Once completed, your configuration will be written to /home/chub/tmp/tryddevproject-26515/.ddev/config.yaml

Found a php codebase at /home/chub/tmp/tryddevproject-26515
Project type has no settings paths configured, so not creating settings file.
Configuration complete. You may now run 'ddev start'.
Network ddev_default created
Starting tryddevproject-26515...
Container ddev-ssh-agent  Started
ssh-agent container is running: If you want to add authentication to the ssh-agent container, run 'ddev auth ssh' to enable your keys.

Project type has no settings paths configured, so not creating settings file.
Successfully started tryddevproject-26515
Project can be reached at https://tryddevproject-26515.ddev.site https://<IP_ADDRESS>:32769
+ curl --fail -I tryddevproject-26515.ddev.site
HTTP/1.1 200 OK
Server: nginx/1.20.1
Date: Thu, 30 Nov 2023 16:47:05 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

+ '[' 0 -ne 0 ']'
+ set +x
Thanks for running the diagnostic. It was successful.
Please provide the output of this script in a new gist at gist.github.com
Running ddev launch in 5 seconds

Expected Behavior
DDEV to start
Actual Behavior
➜  stacy-frontend git:(develop) ✗ ddev start
Starting stacy-frontend...
Using nginx snippets: [/home/var/www/etnic/stacy-frontend/.ddev/nginx/grafana-cors-allow-all.conf]
Using custom PHP configuration: [/home/var/www/etnic/stacy-frontend/.ddev/php/20-bcmath.ini /home/var/www/etnic/stacy-frontend/.ddev/php/20-gd.ini /home/var/www/etnic/stacy-frontend/.ddev/php/99.ddev.php.ini /home/var/www/etnic/stacy-frontend/.ddev/php/xdebug.ini]
Custom configuration takes effect when container is created,
usually on start, use 'ddev restart' if you're not seeing it take effect.
failed to solve: rpc error: code = Unknown desc = no build stage in current context
Failed to start stacy-frontend: ComposeCmd failed to run 'COMPOSE_PROJECT_NAME=ddev-stacy-frontend docker-compose -f /home/var/www/etnic/stacy-frontend/.ddev/.ddev-docker-compose-full.yaml up --build -d', action='[up --build -d]', err='exit status 17', stdout='#4 [ddev-stacy-frontend_adminer internal] load build definition from Dockerfile
#4 sha256:4374d94361c23ad531cc6e3da16921d656aa6d067930cc7b5d4e75661e1b7a08
#4 transferring dockerfile: 127B done
#4 DONE 0.0s
#1 [drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built internal] load .dockerignore
#1 sha256:62c7bad96a4358a3aec3972efca94f4614ff5cb047447a45e91b2e19122e35d2
#1 transferring context: 2B done
#1 DONE 0.0s
#5 [ddev-stacy-frontend_adminer internal] load .dockerignore
#5 sha256:15fb679801e1e1df4ef57d3543fc7ea86adbaf2cb4545b44eec0c376e321e695
#5 transferring context: 2B done
#5 DONE 0.0s
#3 [drud/ddev-webserver:v1.19.0-1-stacy-frontend-built internal] load .dockerignore
#3 sha256:d5cd217187d2e0f692f74993fabafe55a8cebe064a09df53c1ce57cb8676ecc4
#3 transferring context: 2B done
#3 DONE 0.0s
#6 [drud/ddev-webserver:v1.19.0-1-stacy-frontend-built internal] load build definition from Dockerfile
#6 sha256:d3bf757e987e86a12338d6c24d327296b52379ef1b4279ea1e908eaf6bf5dad9
#6 transferring dockerfile: 1.55kB done
#6 DONE 0.0s
#2 [drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built internal] load build definition from Dockerfile
#2 sha256:617d371ad53dc529a43b3c461a34dd09828a1840998f6c49d608665cd3481f6e
#2 transferring dockerfile: 408B done
#2 DONE 0.0s
#8 [drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built internal] load metadata for docker.io/drud/ddev-dbserver-mysql-8.0:v1.19.0
#8 sha256:7ce8e6478d634be85244a37276f16ba8bae563fb2198f789590bc85a4191e016
#8 DONE 0.0s
#10 [drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built 1/2] FROM docker.io/drud/ddev-dbserver-mysql-8.0:v1.19.0
#10 sha256:9ab9443ce04901811378c5efc9f2ab63f4abdd2002bc16d3889d892e576fdfd9
#10 DONE 0.0s
#9 [drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built 2/2] RUN (groupadd --gid 1000 "chub" || groupadd "chub" || true) && (useradd  -l -m -s "/bin/bash" --gid "chub" --comment '' --uid 1000 "chub" || useradd  -l -m -s "/bin/bash" --gid "chub" --comment '' "chub" || useradd  -l -m -s "/bin/bash" --gid "1000" --comment '' "chub")
#9 sha256:6731f953d640fd74f2d17d13cb8af3fa167bb22d8db3be595b9779e97bd1d575
#9 CACHED
#11 [drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built] exporting to image
#11 sha256:0c89d9364218a8a7970e4c5f836c38be60a1ef0ea5abf313fe11316919c3aa25
#11 exporting layers done
#11 writing image sha256:51cf9c6017f0714791006f29f6811fc51fa430d7c2eb7a7e8dbb50b7fa4981a1 done
#11 naming to docker.io/drud/ddev-dbserver-mysql-8.0:v1.19.0-stacy-frontend-built done
#11 DONE 0.0s
#7 [ddev-stacy-frontend_adminer internal] load metadata for docker.io/library/adminer:standalone
#7 sha256:37da4b35930cd637e8b8828c0ee49d8474d624abead3d707a50335cdacc55d8c
#7 CANCELED
', stderr='failed to solve: rpc error: code = Unknown desc = no build stage in current context'
.ddev.zip
Steps To Reproduce
No response
Anything else?
To be sure, I pruned all containers and docker images before.
Many thanks for your help

Hi @christophe-hubert - You seem to be having trouble with adminer. I assume you're using the ddev-adminer add-on?
Could you please remove it for now and see if that solves your problem? ddev get --remove adminer? Then add it back in and see what you have? ddev get ddev/ddev-adminer ?
And of course, Colima has been having a difficult few weeks,  so please mention what colima version you're using, and do a ddev snapshot -a before upgrading it.

Thank you rfay,
After removing adminer, ddev start has  built the dockers,
But I have another error :
Building project images...
Project images built in 0s.
Container ddev-stacy-frontend-memcached  Running
Container ddev-stacy-frontend-zoo  Running
Container ddev-stacy-frontend-db  Created
Container ddev-stacy-frontend-solr1  Running
Container ddev-stacy-frontend-web  Running
Container ddev-stacy-frontend-solr2  Running
Container ddev-stacy-frontend-solr3  Running
Container ddev-stacy-frontend-db  Started
Waiting for web/db containers to become ready: [web db]
Failed waiting for web/db containers to become ready: db container failed: log=, err=container exited, please use 'ddev logs -s db' to find out why it failed
Starting ddev-router if necessary...
Container ddev-router  Running
Waiting for additional project containers to become ready...
Failed to start stacy-frontend: container(s) failed to become healthy before their configured timeout or in 120 seconds. This might be a problem with the healthcheck and not a functional problem. (container 'db' exited, please use 'ddev logs -s db' to find out why it failed)
➜  stacy-frontend git:(develop) ✗ ddev logs -s db
MySQL init process done. Ready for start up.
Starting mysqld.

exec mysqld --server-id=0
tail -f /var/log/mysqld.log
2023-11-30T17:37:34.709845Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2023-11-30T17:37:34.709858Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2023-11-30T17:37:34.709871Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2023-11-30T17:37:34.710703Z 0 [Warning] [MY-010101] [Server] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2023-11-30T17:37:34.710760Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu<IP_ADDRESS>) starting as process 1
2023-11-30T17:37:34.716169Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=100663296. Please use innodb_redo_log_capacity instead.
2023-11-30T17:37:34.717336Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-11-30T17:37:34.870372Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 8.0.26, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
2023-11-30T17:37:34.870386Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2023-11-30T17:37:35.303198Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2023-11-30T17:37:35.303325Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-11-30T17:37:35.303342Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-11-30T17:37:35.304023Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33-0ubuntu<IP_ADDRESS>)  (Ubuntu).

It looks like you previously had MySQL 8.0.26, perhaps quite some time ago? You'll need to ddev delete -Oy and ddev restart and re-import it.


Add genomic source class to variant observations

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed

Expected Behavior
Consider allowing for inclusion of genomic source class (e.g. somatic vs. germline) via a new optional parameter. If specified, we would include an additional component in the variant observation. This component would have LOINC code 48002-0 'Genomic source class [Type]', with component values drawn from here.
Current Behavior
We do not currently include genomic source class.

Hi Bob, I am a beginner looking for some good first issues. Can you please assign it to me?

Ok @VamakshiMagotra. Let me know if you need some guidance.

@VamakshiMagotra Apologies for the change in thinking, but I'm now thinking we should hold off on this one. We don't have a reliable way of knowing if a VCF is containing germline and/or somatic variants. This issue will need some more thought, so we should defer it for now.

This is being folded in to vcf2fhir for SV enhancements


How to sort nested object?

Hi, I'm trying to sort a nested object but always got this following error:
elastic: Error 400 (Bad Request): all shards failed [type=search_phase_execution_exception]
This is my sort statement:
searchSvc = searchSvc.Sort("student.first_name", true)
When I remove it, or change it to:
searchSvc = searchSvc.Sort("created_at", true)
It works without problem.
So is it because of I'm trying to sort by a property of a nested object?
my object is something like this:

{
"created_at": "2018-01-01",
"student":{
"first_name": "john"
}
}

And I don't have any mapping for the index

I'm so sorry! I shouldn't make an issue request here! It's a beginner mistake and you're right! I'm using text instead of keyword. I fixed it by using student.first_name.keyword. I'm closing this.


Not supporting Multi Input keras layers

Ideally in the single input
model.layers[0].input_shape should give (None,X) where X is the input
However in multi input
model.layers[0].input_shape gives [(None,X)] which is causing "ValueError: invalid literal for int() with base 10:" because of extra ']' element.
Though I tried correcting this line finally its throwing a Exception

Have the same issue. Multi input layer works fine with keras.utils.plot_model though.

Hi, I apologize for the delay in replying.
This issue is same as #5. The bug has been fixed in the new version.
Thanks for your feedback.


Crossplat MSBuild and path representation

This is a part of #781 but focused on path separators and how path values flow through msbuild.
Path values get introduced in MSBuild's data flow from:

user input (command line properties, properties, items, metadata, task arguments, imports, using tasks, conditions)
glob expansions (discussed in #1026 )
task outputs
well known item metadata pertaining to paths (FullPath, RootDir, etc)

Paths values are consumed in:

Conditions (path comparisons, etc)
Tasks
Exec task

Path consumers can access paths via:

direct property / item reference (@(Compile), $(MyFile))
item file metadata (FullPath, Identity, etc)

Observations:

There is no distinction between strings and paths
Path value consumers can interpret the values either as plain strings (and MSBuild should not massage the value thinking it's a path), or as actual paths and thus do IO operations on them (when MSBuild is OK to normalize paths, etc)

Problems:

crossplatform MSBuild may break if path producers do not agree with path consumers. For example if producers and consumers use different slashes, trailing slashes, absolute vs relative paths, etc

Potential solutions:

msbuild could normalize all or some path producers in regards to separators to:

only use forward or backward slashes
use the file system specific path separator

use the file system specific path separator

That can't work as your typical .NET Core OSS project should be buildable on any system.
What's the objection against making them interchangeable? I get that it could break some existing tasks, but do we know exactly how bad that would be?

Currently Mono's xbuild normalizes paths to work on the current platform. Will msbuild do the same or will there be an agreed standard for the path separator in the xml files?

My two cents: MSBuild should follow idealized xbuild behavior, by which I mean:

Strings and paths are interchangeable. There is no difference.

Whenever strings are compared, \ and / compare as the same value, and thus "Foo\Bar" == "Foo/Bar" is True.

When reading from/writing to a file, MSBuild will replace \ and / with the correct OS-native directory separator character.
 <ItemGroup>
   <Foo Include="Something\File1.txt" />
   <Foo Include="Something\File2.txt" />
 </ItemGroup>
 <WriteLinesToFile File="Some\Path.txt" Lines="@(Foo)" />

On Unix, the <WriteLinesToFile/> task should write to the file Some/Path.txt, and the Lines property should likewise contain Something/File1.txt and Something/File2.txt.

In the (hopefully rare) instances in which a \ is actually required, e.g. to use the <Exec/> with the grep(1) Unix command utility, which uses \ as an escape character, \ should be escaped and instead entered as %5c.

Rationale
Most existing MSBuild projects use \ within filesystem paths, e.g.:
  <Import Project="$(MSBuildExtensionsPath)\Xamarin\Android\Xamarin.Android.CSharp.targets" />

Thus, on Unix platforms, \ must be treated as / most of the time, or the above import won't work. That's Bad™.
(2) is the natural fallout of this: if most project files will be written originally on Windows, if they have any use of Condition which may compare a filesystem path against anything else, then \ and / need to be normalized so that they're treated the same. For example:
<Import
  Condition="'$(Language)' != 'F#' And Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\Microsoft.FSharp.Targets')"
  Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\Microsoft.FSharp.Targets" />

We could argue that only Exists() within a Conditional needs escaping, but I believe that the mental model is easier to reason about if we say that all strings are treated the same, not just "substrings" within certain contexts.
(3) Shows why this needs to be done consistently everywhere. Filesystem paths can be stored in anything, e.g. %(Reference.HintPath), and that "anything" can in turn be passed on to other tasks which will read or write those values. Since any string may potentially contain a path value, all strings need to be similarly munged so that \ or / will contain the OS-native directory separator character.
(4) is the escape hatch: sometimes you need an actual \ or an actual /, for  any number of reasons. In such situations, we should require using the existing %xx literal syntax to enter the desired character.

Note that I said that this is the idealized xbuild behavior. I have observed scenarios where I would write Item Metadata which contains a \, then invoke the <Copy/> task, the \ would be used as part of the copy output. This...is maddening.
<?xml version="1.0" encoding="utf-8"?>
<!-- b.targets -->
<Project DefaultTargets="Default" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <Dir>Foo</Dir>
  </PropertyGroup>
  <ItemGroup>
    <F Include="b.targets">
      <MD>Foo\Example</MD>
    </F>
  </ItemGroup>
  <Target Name="Default">
    <Message Text="foo\bar" />
    <MakeDir Directories="$(Dir)" />
    <Copy SourceFiles="@(F)" DestinationFiles="%(F.MD)" />
  </Target>
</Project>

When running on xbuild:
$ xbuild b.targest
...
	Target Default:
		foo/bar
		Copying file from '/Users/jon/tmp/b.targets' to '/Users/jon/tmp/Foo\Example'

Just...wat.
MSBuild actually behaves reasonably here.

My two cents about xBuild: xBuild just replace char '' to Path.DirectorySeparatorChar in all sub items: https://github.com/mono/mono/blob/master/mcs/class/Microsoft.Build.Engine/Microsoft.Build.BuildEngine/Expression.cs#L103

Addendum/elaboration: the original comment wrote:

Paths values are consumed in:

Exec task

A related concern is that path values aren't just "consumed" in the <Exec/> task. They are also generated in the <Exec/> task. Consider the xamarin-android repo, which contains <Exec/>s such as:
<Exec Command="%(_LlvmRuntime.ConfigureEnvironment) $(LlvmSourceFullPath)\configure %(_LlvmRuntime.ConfigureFlags)" />
<Exec Command=""%(_MonoRuntime.Strip)" %(_MonoRuntime.StripFlags) "$(OutputPath)\lib\xbuild\Xamarin\Android\lib\%(_MonoRuntime.Identity)\%(_MonoRuntime.OutputRuntimeFilename).%(_MonoRuntime.NativeLibraryExtens
ion)"" />
<Exec Command="$(ManagedRuntime) ..\..\bin\Build$(Configuration)\jnienv-gen.exe -o Android.Runtime\JNIEnv.g.cs --use-java-interop" />
<Exec Command=""$(AndroidNdkDirectory)\ndk-build"" /
<Exec Command="$(AndroidToolchainDirectory)\ndk\ndk-build $(_NdkBuildArgs) NDK_LIBS_OUT=./libs/Debug NDK_OUT=./obj/Debug V=1" />
<Exec Command=""$(JavaSdkDirectory)\bin\javac" -source 1.5 -target 1.6 -d "Jars\classes" @(InputJarSource -> '%(Identity)', ' ')" />
...

My (incorrect?) understanding is that, at present, MSBuild/master will replace \ with / when accessed from Item metadata and properties. This is insufficient. Many of the above commands should work in a cross-platform manner, but if \ replacement only happens for properties and item groups, none of the above will be "fixed" to execute properly on Unix.
All of those execute on Unix, today, using xbuild and the msbuild included with Mono 4.8.

Any update on this? I'm in favor of treating \ equal to /, for example when using Include="%2A%2A" with Exclude=a/b/c at the same time, should I use forward or backslashes in exclude?

We have chosen to keep the current behavior. At this point, changing this would be a big breaking change for what does not look like a fantastic improvement.


Sets are incompatible with Safari 11.0

It seems like Safari 11.0 blocks multiple new windows, only the first window.open gets executed.
Have to refactor sets.

This solved itself in Safari 11.1 by disabling "Security > Block pop-up windows" in the settings.


Allow proc for static_navigation url parameter

Handle a Proc vs. String as a navigation_static_link url

:+1:

Merging to #2345.


pull request for e2e test at 01/09/2017 12:15:06

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


Allow Fill,Type Text to resolve variables too

Likewise to
    Fill Secret                 input#pass      $password

allow also
    Type Text                   input#user      $username

to be resolvable.
I thought it should've been RF's job to provide you the "conversion", but it seems that's not the case.
(I could try to code it myself; I am more-or-less looking for approval that this is indeed accepted)
(See: https://robotframework.slack.com/archives/C015KB1QSDN/p1621453094010200)

Why can’t you do ${username} ?

It's not that "I cannot do it"; I think the interfaces should be the same.
i.e. I don't understand / it doesn't make sense to me to force one "Fill" function to use ${x} and another to use $x.

I believe secret keywords should accept ${password} .. I think the shorthand without brackets there was just another way to define those.

It does accept it, but it cries out deprecation.
In my books, this is as good as removed (or "the next thing to remove")

Ok. So the bug is that the variable use generates the warning.

That is still a bit different issue. Warnings are generated because of the common failure pattern of writing secrets to logs.

Yes. And since this is a very loud warning, IMHO it will lead people writing
    Fill Secret                 input#pass      $password

which will then (again IMHO) make them feel puzzled when
    Type Text                   input#user      $username

won't work.
I understand the rationale behind "the issue that lead to #893".
I think that similar methods should be able to do things similarly (to some extent).

This is the issue where warnings starts https://github.com/MarketSquare/robotframework-browser/issues/421

As @aaltat wrote "Also for us, in the library level, it's not possible to influence RF running context in that level.".
@stdedos: If you want to help with this issue, I would first suggest at looking in making secret keyword not giving the warning when using variables.
It is in my opinion a non-optimal solution to force users to use $variable so that library can do the parsing instead of Robot Framework. It would be better to use standard variables ${variable}.

As @aaltat wrote "Also for us, in the library level, it's not possible to influence RF running context in that level.".

I think @aaltat is correct, and therefore $secret suggestion cannot be reverted.
I also think that the warning is well warranted; if the library tries to protect me against secret spillage, I want any of it. Library cannot enforce RF workings; but it can dictate itself. (I don't know why Input Password https://robotframework.org/SeleniumLibrary/SeleniumLibrary.html#Input Password is not enough - I "may be" okay secrets spilling in TRACE logging).
Therefore, the solution forward I think is making Fill/Type variables accept $variables.

SeleniumLibrary Input Password will leak the secret in many ways. In SeleniumLibrary if one wants to debug issues, one needs to raise logging level so that Selenium logging is visible and that will leak the secrets. SeleniumLibrary is not good role model here. In Browser context, our secret hiding is not bullet proof either, we will leak secrets if Playwright debug logs is enabled.
I am not favor of enabling $ or % prefix resolving in all Fill/Type because the lack of third party support. The $secret or %secret is seen as string in RF data syntax. So if you make a typo, IDE and other tool will not complain, because tools will think it is string. Only in run time, keyword will complain, which is annoying.
There is work to make the feature and maintain the syntax in our side. Also it opens a door for this implementation to leak in other keywords, where it is not needed in my mind. I understand your need for symmetry, but in this case, I think that symmetry is not the best solution.
Therefore I am not in favor to have this in the Type/Fill keywords.

Just to make it more clear for me an others?!
This is NOT a matter of Fill vs Type!
It is about Fill Text & Type Text vs. Fill Secret & Type Secret
And if we would implement both keyword groups to do the same, there would not be a need for these two different kinds.
I think as Mikko said, there is one error. That we write in the warning that "variables" are allowed.
That is not really the case. The ... Secret keywords are only silent, when you use the "python variable syntax"
I would recommend to close that issue. Sorry

@mkorpela I think the warning is correct, with current "bug" in Robot Framework that the unresolved variables do not work correctly.
So the warning text should be changed.
As you can see in the following screenshot, trace spoils variables.

But it does not spoil the "python variable syntax"

@Snooz82 I do not see how the warning message should be changed?

@aaltat because it says "use variables or env variables instead"
But that does not help!
You have to use special variable syntax to work. $var instead of ${var}
That should be in the warning.

Closing due #1070


Questions: hiding error overlay, hiding loading indicator, container size inquiry

I started integrating the Mux React Player and I am using it as a looping background video. In some cases (e.g. when my macbook goes to sleep) I get an error that says the media might be corrupt, but the player somehow recovers from this error and continues playing. However, I can't find a way to hide the error overlay, because it makes the text unreadable above the background video and it defeats the purpose. I would rather see a black background without the video playing if errors occurred during playback. Is it possible to hide the error overlay programmatically when an error occurs? Or have a callback/event when an error occurs so I can decide whether to wether hide it or not.
Can the loading indicator be hidden? Even though I have a poster image set and all the controls hidden, I do see a loading spinner while the video loads.
I have a container that has a specific width & height and the video player inside it should stretch it. However, until the video player loads, it has a different size and that is undesirable. Once the player initialized, it takes up the width & height of the container. Can I force the player to stretch the container initially, even while loading? (screen recording removed for privacy)

once the user lands on the page, the player didn't stretch the container
the poster image is not loaded until the player is not initialized
once the player is initialized, the player gets resized to the size it was set (with classname)
once the poster image loaded, the video starts loading and a spinner appears (that I would like to hide)

Why does the poster image has to wait for the player to initialize? It defeats the purpose. Should I use a regular image on top of the player, until the video loads?
Can the player use the style/classname I set before being initialized? I set the size already so I don't expect that it should resize after initialized.
Can I hide the loading indicator?

I would like to add the following point:
Style the loading screen / hide it
I am using the mux player in a vue/nuxt environment. My client wants to have some background videos on his website on a white body. With the black loading screen, it created unpleasant black boxes at the beginning. Found nothing in the docs about styling the loading screen.

@dKaipfKMS okay, a couple things here:

I started integrating the Mux React Player and I am using it as a looping background video

For background looping videos since you don't need the controls, you would probably be better off with <MuxVideo /> which is more like the HTML5 video element, instead of Mux Player. The main value of using Mux Player is the controls, so if you don't need controls at all then <MuxVideo /> has everything you need (and just like the HTML5 video element it doesn't have an error screen, so you don't need to worry about hiding it).

Can the loading indicator be hidden? Even though I have a poster image set and all the controls hidden, I do see a loading spinner while the video loads.

I don't think the loading indicator can be hidden right now. If you hide it, what would you expect to see while the video loads?

I have a container that has a specific width & height and the video player inside it should stretch it. However, until the video player loads, it has a different size and that is undesirable. Once the player initialized, it takes up the width & height of the container. Can I force the player to stretch the container initially, even while loading?

Yes, you can style <mux-player> with CSS to achieve this. See Style with CSS section.
mux-player {
  width: 100%;
  aspect-ratio: 16 / 9 // use the aspect-ratio of your video
}

The exact CSS you need will depend on the containing page. If you spin up a CodeSandbox or similar for us to look at we can provide some guidance.

Why does the poster image has to wait for the player to initialize? It defeats the purpose. Should I use a regular image on top of the player, until the video loads?
Why does the poster image has to wait for the player to initialize? It defeats the purpose. Should I use a regular image on top of the player, until the video loads?

What do you mean here "by the player initializing". A code sample here would be helpful. The poster image should show when the page loads. For example here

Moving this to discussion because they are grouped general questions.
They should be split up in distinct bugs / issues for the issue tracker.


[Bug] Update from 1.20.4 to 1.20.6/1.21 loose items

Describe the bug
I have updated to 1.21 and all my of my chest has been "reseted" all stack inside has been set to 1 item
To Reproduce
1 Minecraft 1.20.4 world with Reinforced Chest
Screenshots
1.21

1.20.4

Environment

Minecraft: 1.21/1.20.4
Fabric Loader: 0.16.2 / 0.15.11
Fabric API: 0.102.0+1.21 / 0.97.1+1.20.4

Additional context
Its a world on Multiplayer

I have tried with the 1.20.6 version and i have the same issue.

In my test, Reinforced Barrels and Reinforced Shulker Boxes have the same issue
I guess the problem comes from the conversion from NBT to Component

I think it's the same thing.
Describe the bug
1.20 updated to 1.21 and 1.21.1
In every slot in the Reinforced Chest only one item remained (i.e. from 64/30/15 items to 1)
 - if this item was enchanted (tools, weapons, elytra) it was disenchanted in 1.21.
 - i.e. "Enchanted Book: Mending" -> In 1.21 was just an "Enchanted Book" (it was still glowing but it was without specific enchantment).
 - if the item was renamed, it's back to its default name in 1.21.
 - Every Shulker Box (Reinforced or not) in the chest was emptied and renamed ones were back to a default name.
The same bug with the Reinforced Barrels and stand alone Shulker Boxes. If the Reinforced Shulker Box was in a chest (Reinforced or not) it was emptied and renamed to its default name.
Environment
Minecraft: 1.21 nad 1.21.1/1.20
Fabric Loader: 0.16.5 0.16.2 / 0.15.11
Fabric API:0.105.0+1.21.1   0.102.0+1.21 / 0.83.0+1.20
Additional context
Its a Single Player World.

I'd like to bump this. Big issue here.. I can't see a part of this mod's code that handles converting stored item data from 1.20.4 to 1.20.5 data components. Tons of our players would have lost their items if we didn't make a backup.

It's getting late. This issue has been resolved in reinforced chests v3.0.1+1.20/v3.1.1+1.12.1, reinforced shulker boxes v3.0.1+1.20/v3.2.1+1.12.1, and reinforced barrels v2.5.1+1.20/v2.6.1+1.12.1. If there are any further issues, please re-open this issue.


Add a 'telemetry/logging guide' section to the docs

Many WOPI implementors don't realize they should log some things on each request to make it easier to diagnose issues. We should add a dedicated section to the docs with details on this.

Related to #137 and #236.


Teku validator client requires fee recipient before Bellatrix upgrade

Description

Teku validator client requires fee recipient before Bellatrix upgrade, prysm validator client does not.  This miss in config caused many of our validators to miss attestations

Steps to Reproduce (Bug)
[Please be as specific as possible]

teku beacon upgraded to 22.8.1 and configured with default fee recipient
teku validator client running at 22.6.1 (not upgraded as we did not want to restart yet)

Expected behavior: [What you expect to happen]

Consistent behavior as prysm
Backwards compatibility between beacon and validator client
Make it clear in release notes at what point exactly the config is needed

Actual behavior: [What actually happens]

Failed with:

[eth-validator-teku-eth-wallet-0222-0] Invalid configuration. --validators-proposer-default-fee-recipient or --validators-proposer-config must be specified when Bellatrix milestone is active

Frequency: [How regularly does it occur?]
Versions (Add all that apply)

Software version: [teku --version or look for log lines starting with Teku version:] teku beacon: 22.8.1; teku validator client: 22.6.1
Java version: [java -version]
OS Name & Version: [cat /etc/*release]
Docker Version: [docker version]
Cloud VM, type, size: [Amazon Web Services I3-large]

Thanks for raising this, can you confirm your validator-client was either not specifying --network or was using --network=auto?
This setting would fetch network settings from the beacon-node when it connects, and that would result in the VC getting informed of the pending bellatrix network upgrade, and it would behave as you are describing...
A workaround would be to specify --validators-proposer-default-fee-recipient, and you'll be able to continue to use the old VC with the new network configuration, and be compliant with the minimal requirements for the merge. If we were to default the setting, it'd be to 0x00, and that'd cause the flow on effect of burning any earnt eth silently if you don't give an appropriate value.

yes, validator client was using --network=auto, and we fixed it by specifying --validators-proposer-config and upgrading validator client to 22.8.1.  But we had to do it more as a firedrill, rather than the intended planned rollout to beacons first and then validator clients.
Not sure, there is much to fix here, other than docs and consistent workflow as prysm for next time.

Ok, going to close this one. We expect that fee recipient is required for any network where bellatrix is scheduled. I can see why this is a bit surprising given the VC didn't update, but it was still a configuration change applied to the validator client which caused it. This is a one off transition where we had to make a choice between refusing to startup when required config is missing or running with the invalid config and then failing when the merge actually happened (or burning the fees).  We went with refusing to start because it's much more visible, ensuring the configuration problem gets fixed rather than missing block proposals (which is also then bad for overall network health).


Update to latest version of TS / Immer

Would be nice to have immer 3.x.x and TS 3.4

Yup. Will happen soonish. There are some non-trivial type errors with Immer 3.x so I can't just release it. Need to figure those out first. (PR welcome thou if you're in hurry)


Question for podcast.

1). Beginners guide to research paper. Should we start writing research papers in college. how beginners can start with writing research paper. Guide to conferences and publications.
2). How to build a strong online presence.(i write a blog :- https://tushirnitin.wordpress.com/) .what different strategies can be used for better reach.
3). Guide to stackoverflow.
4). shifting from non-technical to technical.
5). what about training institute (they charges 30,000 for 3 months training) . does it bring any value ?

6). Work-Life balance in IT industry: A guide to freshers.

Put questions as separate issues.


Added getContext/setContext effects, where context is acting like dyn…

…amic scoping between parent/child tasks (resolves #713)
Just a quick draft of this proposed API. I've put several TODO:s in the code, they act as thought-placeholders and I would appreciate commenting each one of them.
Also there I've spotted a difference between standard middleware API and runSaga.

middleware - options are passed once, so encapsulated by the factory) and each subsequent middleware.run(saga) will receive them (also context now)
runSaga - each call expects the options all over again, so subsequent calls do not share context and it cannot be shared among 'top sagas' (at least not without creating a topContext within runSaga module)

cc @aikoven

also I think like some way for removing the context should be available as for now it wouldnt be possible to 'uncover' higher scope
function* saga() {
	yield setContext({ a: 1 })
	yield fork({
	  yield setContext({ a: 2 })
	  yield setContext({ a: undefined })
	  yield getContext('a') // undefined, no way to reach { a: 1 } at this point
	})
}

hating to put 3 effects for this rather simple feature - getContext, setContext and unsetContext (?)

also I think like some way for removing the context should be available as for now it wouldnt be possible to 'uncover' higher scope
function* saga() {
	yield setContext({ a: 1 })
	yield fork({
	  yield setContext({ a: 2 })
	  yield setContext({ a: undefined })
	  yield getContext('a') // undefined, no way to reach { a: 1 } at this point
	})
}

hating to put 3 effects for this rather simple feature - getContext, setContext and unsetContext (?)

Should generator have access to context properties set by itself? IMO it shouldn't, because you can just use variables for this. So maybe setContext should only have effect on children? Maybe even rename setContext with setChildContext (I don't really like the verbosity though)?

I dont think it will be a problem as this context feature is less convenient to use, so people will always prefer accessing variables than this within task which uses setContext

For removing context we can make setContext replace all own properties instead of assigning. This way we can keep API surface smaller.

I think that could lead to unexpected bugs and also updating the context would be quite unwieldy

Should c be able to uncover context set in its grandparent a? I think not, because it will break encapsulation.

Nah, didnt think about uncovering like this, just 1 step into the upper context like in the example posted here

Should generator have access to context properties set by itself? IMO it shouldn't, because you can just use variables for this. So maybe setContext should only have effect on children? Maybe even rename setContext with setChildContext (I don't really like the verbosity though)?

I dont think it will be a problem as this context feature is less convenient to use, so people will always prefer accessing variables than this within task which uses setContext

For removing context we can make setContext replace all own properties instead of assigning. This way we can keep API surface smaller.

I think that could lead to unexpected bugs and also updating the context would be quite unwieldy

Should c be able to uncover context set in its grandparent a? I think not, because it will break encapsulation.

Nah, didnt think about uncovering like this, just 1 step into the upper context like in the example posted here

For removing context we can make setContext replace all own properties instead of assigning. This way we can keep API surface smaller.

I think that could lead to unexpected bugs and also updating the context would be quite unwieldy

Another way to avoid unsetContext is to use symbols for context keys on the library user's side.

Context property could be anything, not just plain object, so we can't safely copy it.

ofc it would be checked beforehand if it is a plain object to see if we should make a shallow copy

Is this really a library responsibility? We don't shallow copy selected state and actions returned from take.

Here's a counterexample:
const obj = {
  foo: null,
  setFoo(foo) {this.foo = foo},
  getFoo() {return this.foo}
};

yield setContext({obj});
// ...
const obj1 = yield getContext('obj');
yield call([obj1, obj1.setFoo], 1);
// ...
const obj2 = yield getContext('obj');
const foo = yield call([obj2, obj2.getFoo]);  // null

Here, the value of obj.foo is lost due to shallow copying. In real world, this could happen when you store observable objects in context and later add callbacks to them.

Hm, interesting. Its really a scary situation and compelling one at the same time to drop shallow copying. Wondering only which usage would be more often and therefore which approach would give us less footguns in the end.
In theory we could make 2 versions of this effect getContext and getContext.impure
In general im in favor of immutability and this-less programming, aint saying though that everyone should. This feature would be experimental anyway and rather an escape hatch which should noy be used in trivial cases anyway, so... i dont know which is better now as a default

In general im in favor of immutability and this-less programming

I absolutely agree with you, but my reasoning is this: for pure things we already have Redux store and actions which we can access in sagas at any level using appropriate effects. We would use Context to access non-pure third-party library objects.
Another use case is to share Channels between sagas, however I guess shallow-copying a Channel would be safe.

@aikoven
Last comments made I think (ofc still waiting for your input, if you disagree - or agree :trollface: - somewhere) and I think im gonna update the PR soon so it can get finally merged in

I think the code is final now, so you can have last look on it - whats missing before merging is some tests + docs, ill get them done in this week and merge whole thing to the master.

Guys, do you think this branch is going to get merged eventually?

@AriaMinaei yes, it sure will! I just need to get some time to merge it and some other branches, so I can release new version, sorry about the delay

Is there anything I can do to help out with this PR?

@neurosnap, i think its basically done. Will review it again in the weekend and gonna publish

Released, not docs yet - but if you know about the feature and want to use it - go ahead. Let me know if everything works as expected.


Disabling debugInfo results in inability to re-order nodes.

When I disable Angular's debug info using the steps in this Egghead tutorial in order to gain a performance boost, I lose the ability to drag and drop items. No information is logged in the console.
The following configuration option is what breaks the re-ordering:
module.config([ '$compileProvider', ($compileProvider) {
 $compileProvider.debugInfoEnabled(false);
}]);

Is ui-tree relying on attributes added by angular's debug info?

@joshuabc that Egghead link is behind a paywall for me. Is the technique the same as the one documented here? https://docs.angularjs.org/guide/production

Hi @StefanCodes. Yes, I believe the technique is the same. I edited my comment with the exact code which results in the issue.

Yup. I can reproduce this in my app, too.
Drag drop breaks using the snippet @joshuabc pasted above.
Running
angular.reloadWithDebugInfo();

in the browser debugger makes drag drop start working again. I'll take a quick look, but this is outside my area of familiarity so I may not get anywhere.

I think I see what's going on.
When you enable debugging, as per Angular docs:

Where the compiler has created a new scope, the scope and either ng-scope or ng-isolated-scope CSS class are attached to the corresponding element. These scope references can then be accessed via element.scope() and element.isolateScope().

What this looks like in the rendered HTML is that the node objects (in my case, a div with the ui-tree-handle directive on it) are rendered with the ng-scope and ng-binding CSS classes, which I suspect is what Angular uses to get an object's scope using IAugmentedJQuery.scope() and .isolateScope(). As the Angular docs say, those scope functions are only available with debugging hints. And scope() is called twice in ui-tree - in the dragMove and the dragStart events!
I think the correct fix is to replace the calls to .scope() in both event handlers to a production-capable equivalent. Unfortunately I don't know Angular well enough to see a simple way to get a scope from an arbitrary DOM element (which is what the handlers are currently doing). Hopefully someone more experienced can suggest a solution.
The only workaround I'm aware of is "don't disable debug information on the compile provider". :(

Thanks for looking into it @StefanCodes!

+1 - just ran into this with my app. :(

+1 http://embed.plnkr.co/Tw51pOGImzlni6obV63X/preview

Related issue #425. I'll start working on this soon.

Please review: #596

Closing, let's have further discussion in the PR containing a fix (work in progress for now). See #648.

This issue has been fixed in v2.15.0.


Incorrect destination URL is picked for tenants during destination validation for tenants.

Describe the issue:
When trying a login scenario for a SAML SP in a newly created tenant, the following error can be seen.
Destination validation for Authentication Request failed. Received: [https://localhost:9443/samlsso?tenantDomain=t2.com]. Expected one in the list: [https://localhost:9443/samlsso]

This is not observed when the OOTB destination URL is readded again.
How to reproduce:

Configure SAML SP for a tenant as in [1]. NOTE: enable signature validation and single logout (front channel logout - HTTP Post binding).
Try loging in to the app.

[1] - https://piraveenaparalogarajah.medium.com/trying-out-saml2-pick-up-dispatch-app-with-wso2-identity-server-in-a-tenant-20626ac4865a
Expected behavior:
The by default destination URL should be picked by the server.

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: 5.11.0 and above
OS: [e.g., Windows, Linux, Mac]

By default, in the server it is configured as https://localhost:9443/samlsso?tenantDomain=t2.com. But in the server startup, this value is not read properly. At the server startup, from here https://github.com/wso2-extensions/identity-inbound-auth-saml/blob/v5.9.2/components/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/util/SAMLSSOUtil.java#L661 destination URL is coming as null. Since it is null, it takes the default value https://localhost:9443/samlsso. But once we update the Resident IdP config again to https://localhost:9443/samlsso?tenantDomain=t2.com, it will work.


Reduce index overhead

Index is currently a size_t. Most of the time we can get away with an ubyte.

Fixed by 2d37a51569414393f1ce2002e141affe76848ee7 / v1.0.1


Enable WebUSB

This PR enables the WebUSB interface, allowing integration with the @ledgerhq/hw-transport-webusb package. WebUSB is crucial for Ledger device support on Android web applications, simplifying communication and improving security. (Chrome on android supports only webusb - not HID)
Related to https://github.com/LedgerHQ/ledgerjs/issues/423

Replaced by #67


[SoftDeleteable] not working on bidirectional oneToOne

<?php
/** @Entity */
class Customer
{
	// ...

	/**
	 * @OneToOne(targetEntity="Cart", mappedBy="customer")
	 */
	private $cart;

	// ...
}

/** @Entity */
class Cart
{
	// ...

	/**
	 * @OneToOne(targetEntity="Customer", inversedBy="cart")
	 * @JoinColumn(name="customer_id", referencedColumnName="id")
	 */
	private $customer;

	// ...
}

there is **SoftDeleteable **on **Customer **and on Cart
when I want to select Customer, there is automatic left join ... and it's selecting even deleted cart ...
so, SoftDeleteable is not working on oneToOne

This is a doctrine issue. In some cases, docrine is forced to hydrate. This is one of those cases.
Customer has a one-to-one relation, but the owner of said relation is the cart object (that has the customer_id). The hydrator is forced to fetch and hydrate the cart. There is nothing that can be done about that by this library I think.
There are a couple of things that can possibly help you:

Flip the owning side of the relationship
Refactor your code to have a one-to-many relationship ordered by the deleted at timestamp
Simply remove the cart reference from customer, and have it fetched by the repository.

You could report this issue to doctrine, but there is nothing that could be done about it ATM, and I'm not sure that they would even think about it, considering the amount of work that has to be done to change this.

I don't think its problem of DOCTRINE ...
when I look at SoftDeleteableFilter, there is NOTHING about what else is in SQL query left join on another table)
SoftDeleteableFilter is solving deleteable only for "actual table/root entity" .. it's not solving, if there is oneToOne, oneToMany, manyToOne or manyToMany
I'm talking about SELECT-ing entites.. not about removing entities

I understand that. Remove the softdeleteable, and check the queryes. The cart will still be fetched. Its done internally by doctrine.

yes, cart is still fetched ... there is no problem with that
it's problem of selecting entities in sql filter
maybe someone else should write something

The sql filter currently does not work on joins, this has always been the way this extension works, you would have to add the condition manually. In your case, doctrine is making the join automatically, you can't add an extra condition without the query builder.
Either you do a quick refactor on your code, or do a PR that makes the sql filter handle joins, which would be a great new feature in 3.0 :)

https://github.com/Atlantic18/DoctrineExtensions/issues/1427#issuecomment-155686889

so, with actual version of DOCTRINE there is no way to do this automatically with SoftDeleteable ..
I must refactor entities

@poolerMF this has always been the case with Doctrine. Inversed one-to-one relationships are always fetched eagerly when hydrating the document. Proxies can't be used because they rely on the identifier of the entity being known, which isn't the case for inversed references.
One common use case is, as @Padam87 already mentioned, to use a one-to-many relationship (which won't be loaded eagerly) and then have a getCart() method which proxies to the collection and returns the last (or first depending on how you want your logic to be) element from the cart collection.


KBC_RUNID is not propagated to storage client

https://github.com/keboola/app-project-backup/blob/2bfc6db1a941b826734c71bd10756e51f0f762a9/src/Component.php#L38
https://developers.keboola.com/extend/common-interface/environment/#environment-variables

fixed


Bug/fix mock

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add boundLog to enable log-uniform sampling

Using bound to generate random inputs is heavily skewed towards the upper end of the range [see below]. To explore a more balanced distribution of values, users should have the option to sample in log space instead.
This PR adds boundLog(uint256 x, uint8 min, uint8 max), which generates a random number between [2**min, 2**(max+1)-1] that is uniformly distributed in log space (ie. data generated follows a log-uniform distribution)
Note: contrarily to bound, boundLog WILL NOT return x when the input x is within the provided [2**min, 2**(max+1)-1] bounds.

bound vs boundLog sampling between 1 and 2^32, N=10**6

cc @grandizzy @klkvr for thoughts

@mds1 I think it makes sense to have such directly in foundry and have strategies generate values in bounded range. What I can see here as a potential issue is that we will need config to specify limits per fuzzed param so could lead to more complex config, e.g. for a fuzzed test like testFuzz(uint256 a, uint256 b) we need to specify a min/max for a and  another one (or none) for b
Since we already have such per named param config for fixtures we could extend it to include bounds too (ref https://book.getfoundry.sh/forge/fuzz-testing#fuzz-test-fixtures)

Yea the UX for this was always the trickiest, in the past we also considered just using the inline config which could be a good approach:
/// forge-config: default.fuzz.range.x = [5, type(uint256).max];
/// forge-config: default.fuzz.distribution.x = logarithmic;
/// forge-config: default.fuzz.range.y = [1, 10];
/// forge-config: default.fuzz.distribution.x = uniform;
function testFoo(uint256 x, uint256 y) public {
  // --- snip ---
}

How would you specify distribution type with fixtures? Though, I am hesitant to expose distribution
type at all because it adds more complexity to fuzz config. I would prefer to add some logic to forge to detect when this is needed and just accordingly. For example if fuzzing over a really large space like uint256, logarithmic uniformity is preferable and should be the default. If fuzzing a uint8 standard uniform sampling is preferable.

How would you specify distribution type with fixtures?

Yeah, wasn't thinking to use fixtures for distribution but maybe having a similar way to current fixtures for all configuration of named parameter in Solidity
struct Uint256ParamConfig {
    uint256 min;
    uint256 max;
    uint256[] fixtures;
    uint256[] excluded;
}

Uint256ParamConfig public configAmount;

(basically including fixtures in same config and also superseeding assume and bound cheatcodes per named param). Though probably inline config is better UX here considering that we need specific struct per type...

I would prefer to add some logic to forge to detect when this is needed and just accordingly. For example if fuzzing over a really large space like uint256, logarithmic uniformity is preferable and should be the default. If fuzzing a uint8 standard uniform sampling is preferable.

Yep, agree, maybe we should start an issue in foundry to track / implement these?

Yep, agree, maybe we should start an issue in foundry to track / implement these?

That sounds good to me, would you mind creating that? :)

How would you specify distribution type with fixtures?

Yeah, wasn't thinking to use fixtures for distribution but maybe having a similar way to current fixtures for all configuration of named parameter in Solidity
struct Uint256ParamConfig {
    uint256 min;
    uint256 max;
    uint256[] fixtures;
    uint256[] excluded;
}

Uint256ParamConfig public configAmount;

(basically including fixtures in same config and also superseeding assume and bound cheatcodes per named param). Though probably inline config is better UX here considering that we need specific struct per type...

I would prefer to add some logic to forge to detect when this is needed and just accordingly. For example if fuzzing over a really large space like uint256, logarithmic uniformity is preferable and should be the default. If fuzzing a uint8 standard uniform sampling is preferable.

Yep, agree, maybe we should start an issue in foundry to track / implement these?

Hey I am working on this issue and trying to solve it using the struct
struct ParamConfig {
        uint256 min;
        uint256 max;
        DistributionType distributionType;
        uint256[] fixtures;
        uint256[] excluded;
    }

and I am fetching the from another function that is checking the unit type of the value. Is it important to keep the exact same struct to solve the issue?

Closing in favor of https://github.com/foundry-rs/foundry/pull/9154


Menu item title text should be align center

Describe the bug
Menu item title are aligned start of the div. It should be center to provide batter UX.
To Reproduce

Go to https://www.covid19india.org/
Click on Menu
Menu title text

Expected behavior
Text should be center for better UX.
Screenshots

I would like to resolve this issue please assign this issue to me if it is available.

That was a design choice. Thanks :)


Add missing disabledMarkerStyle

Prop disabledMarkerStyle exists in code, yet missing in definitions.

Thank you for the contribution!


Add a wiki: The Binding of Isaac: Rebirth Wiki

Link to origin wiki: https://bindingofisaacrebirth.fandom.com/wiki/Binding_of_Isaac:_Rebirth_Wiki
Link to destination (independent) wiki: https://bindingofisaacrebirth.wiki.gg/wiki/Binding_of_Isaac:_Rebirth_Wiki

Hi @Britanniann! Thanks for the submission. This wiki was already added in v3.11.0, released in mid-October.


Are events 4802 and 4803 missing from Windows 11?

Are events 4802 and 4803 missing from Windows 11?  There are many posts in Google that ask this question but no apparent response or communication from Microsoft on this issue.  On the official page, this page there is nothing suggesting these events are removed from Windows 11, or where Windows 10 and older specific.  Please provide reference or explanation of why Windows 11 no longer generates event ids 4802 and 4803.  Even if other logon events GPO policy is enabled, such that 4800 and 4801 events are generated, correctly, events 4802 and 4803 are not generated on Windows 11 at all.

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

ID: 326b1f74-f183-d9c4-7802-51a85743ef2f
Version Independent ID: bacf84a4-13b9-ae0b-c0e7-aa9b91b0340e
Content: 4802(S) The screen saver was invoked. (Windows 10) - Windows security
Content Source: windows/security/threat-protection/auditing/event-4802.md
Product: m365-security
Technology: windows-sec
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@vinaypamnani-msft Please help us in resolving this issue. Thanks


Ansible role pinning

Pin Ansible role by default to the latest known stable version, and also allow specifying the st2-ansible role version by the user in GH Actions.

@LeoDiazL could you explain the first part of this a bit. What do you mean by:

pin the ansible role by default to the latest known stable version

The latest known stable version of ansible-st2 is v3.2.0: https://github.com/StackStorm/ansible-st2/releases
and it's ideal to pin that somewhere, additionally exposing the ansible-st2 version via GH Actions inputs.

https://github.com/bitovi/github-actions-deploy-stackstorm/blob/main/operations/deployment/ansible/bitops.before-deploy.d/clone-ansible-st2.sh#L13


Improve special CC handling in Node Functions

I am not happy with my original method of translating certain parameters into the z-wave js equivalent classes - i.e. Duration.
I will change this logic, to work on CC level, instead of specific parameters

@hufftheweevil,
I am ready to publish 2.0 - But I call on a favour.
I have improved the way certain params are converted to classes (required by ZWJS).
At the same time - I have bridged Meter for Managed Usage.
Do you have a meter you can test? - to ensure you can get its data using Managed?.
its detail is in the readme for Managed.

Version 2.0.0 is out.
Awesome work on the UI. 👍

Thanks, just glad I could help out.


CollectionName not prepended to branch names in Editorial Workflow mode

- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
I have two collections which contain pages with the same names with different content. With the Editorial Workflow enabled changing any of these pages effects the other collections equivalent page.
I think I've worked out what is happening, it looks like the generated branch names do not contain the collectionName- as it suggests it should in the documentation.
At first I thought this was the same issue as https://github.com/netlify/netlify-cms/issues/1164 but I actually think its different.
Looking at the code I think the problem is here: https://github.com/netlify/netlify-cms/blob/55a24a75c14fcef97b19f9c1fe6cc1579e0b59c2/src/backends/github/API.js#L325
It seem as just the slug is passed to the generateBranchName function and not options.collectionName as well. I might be wrong though.
So in my case instead of cms/pages-consumer/color, I get cms/color.
- If the current behavior is a bug, please provide the steps to reproduce.

Create two collections with pages/files of the same name
Make a change to a file in one collection and see the branch/PR created with the name cms/[name of file]
Try changing the corresponding file in the other collection and you should see the changes you made in the previous step.

- What is the expected behavior?
Branches should be created with the collectionName prepended to the branch name allowing them to be different.

- Please mention your versions where applicable.

Netlify CMS version: 1.8.4
Browser version: Chrome 66

Node.JS version: 9.8.0
Operating System: OS X
- Please link or paste your config.yml below if applicable.

Looks like a long standing regression from #145.

a simple fix i made to my branch (in our case we had index.md for most collections), so i simply check if the slug is index and add to it the collectionName.
here is a ref which you can base your fix on:
in file API.js after line 281
      if (file.slug === "index") {
        file.slug = "index-" + file.path.match(/\/([\w-]+)\/index\.md$/)[1];
      }

the line  file.path.match(/\/([\w-]+)\/index\.md$/)[1]; takes the collection name from the path, you will need to modify the code to work in your case for either to pass the collection name to this function somehow to to parse it out of the url

We'd definitely take a PR for this.

I will work on that by the weekend..
it needs some changes, anyways happy to help


IDE plugin to generate the project template.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Loading tokenizer trained with Huggingface implementation

Hey,
I you mentioned this implementation was heavily inspired by the Huggingface one. I was wondering if it's possible to load a tokenizer trained with huggingface with this implementation ?
If it is, is there any gotchas to be aware of ?
I thought this information was lacking from the doc.
Thank you

Hey, I was just experimenting idk if this works for all models, I downloaded the file from https://huggingface.co/ibm-granite/granite-8b-code-instruct-4k/tree/main tokenizer.json file and then called pretrained.FromFile(path) it worked.

@keerthivasansa ,
Thanks for your report.


Clang tidy action failing to post comments.

The clang-tidy-pr-comments action is failing to post comment with the following assert
Processing 'cppcoreguidelines-pro-type-member-init' at lines 340-340 of libbinlogevents/include/compression/payload_event_buffer_istream.h...
    sys.exit(main())
             ^^^^^^
  File "/home/runner/work/_actions/platisd/clang-tidy-pr-comments/v1/run_action.py", line 623, in main
    post_review_comments(
  File "/home/runner/work/_actions/platisd/clang-tidy-pr-comments/v1/run_action.py", line 433, in post_review_comments
    assert result.status_code in (
           ^^^^^^^^^^^^^^^^^^^^^^^

The workflow file can be found at https://github.com/percona/percona-server/blob/testing/.github/workflows/main.yml.
The workflow is configured with the following permissions.
permissions:
      issues: write
      pull-requests: write

Also, pull request ID is being passed through properly
Run ${GITHUB_ACTION_PATH}/action_launcher.bash
  ${GITHUB_ACTION_PATH}/action_launcher.bash
  shell: /usr/bin/bash -l {0}
  env:
    UBUNTU_CODE_NAME: jammy
    COMPILER_VERSION: 17
    BOOST_VERSION: 1_77_0
    BOOST_DIR: /home/runner/my_boost
    INPUT_GITHUB_TOKEN: ***
    INPUT_CLANG_TIDY_FIXES: clang-tidy-result/fixes.yml
    INPUT_PULL_REQUEST_ID: 5241
    INPUT_REQUEST_CHANGES: true
    INPUT_SUGGESTIONS_PER_COMMENT: 10
    INPUT_REPO_PATH_PREFIX: /home/runner/work

For more info, check out https://github.com/percona/percona-server/pull/5241

Hi @VarunNagaraju your workflow will not work with PRs from forks, and https://github.com/percona/percona-server/pull/5241 is a cross-fork PR. This workflow is executed with credentials that do not allow to modify the pull requests in the base repo.

@oleg-derevenetz Thanks for the quick response. I'll try with the artifact method for forks.

Hi @oleg-derevenetz , I see that in order to use on : workflow_run trigger, the workflow files should be on the master/default branch. If that's the case, how would one test if the workflows are working correctly without modifying the default branch?
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run
https://github.com/percona/percona-server/pull/5242

Hi @VarunNagaraju yes, it requires the workflow(s) to be on the default branch. In order to test this, you'll need two forks. You should make PR from one fork to another (which should already have corresponding workflows in its default branch).

Thanks for the assistance @oleg-derevenetz !


Fix Some Typos on Restart

Fix Some Typos on Restart Section of Command-Line Chapter on Docs

Close with b4919f9fcf46363c47c3170d2d859e51f72fe2f6


Fix Android build errors

We've just updated our Android build. Have a look and see if it works for you. thanks for your contribution and feel free to reopen if you still have issues.


OpenMP update module vars

Analog to OpenACC
!$acc update device(<module vars>)

do OpenMP
!$omp target update to(<module vars>)

The failing test is present also on develop andd seems unrelated to this PR. Will be investigated separately.


[Conformance] Virtual-Kubelet limits number of log lines

Kubelet's behavior is to display > 1000 log lines when getting logs with no options.  Virtual Kubelet, however, asks for 10 lines by default.  This ends up truncating log lines when running conformance tests and tests fail.
I believe the following tests are affected by this issue:

[k8s.io] Pods should contain environment variables for services [NodeConformance] [Conformance]
[k8s.io] Variable Expansion should allow composing env vars into new env vars [NodeConformance] [Conformance]
[sig-api-machinery] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]
[sig-api-machinery] Secrets should be consumable via the environment [NodeConformance] [Conformance]
[sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]
[sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]

We should (1) investigate exactly how the kubelet limits log lines it returns and (2) make an issue, followed by a PR to Virtual Kubelet to bring the behavior of logs into alignment with kubelet.

Looks like there are already 2 PRs that fix this in different ways:

https://github.com/virtual-kubelet/virtual-kubelet/pull/806
https://github.com/virtual-kubelet/virtual-kubelet/pull/821

https://github.com/virtual-kubelet/virtual-kubelet/pull/806 has been merged, so this should be fixed.


rust-project check TARGET

Context: relies on the as-yet unmerged https://github.com/rust-lang/rust-analyzer/pull/18043, which adds {label} interpolation in rust-analyzer flycheck commands and allows rust-project develop-json to supply the flycheck commands.
Previously rust-project worked with the $saved_file interpolation in rust-analyzer. This PR makes it work with a target label, substituted as {label} instead. So it's not really backwards compatible, but we could make it so. Submitting this now to get feedback.
We also now emit flycheck runnables that configure rust-analyzer to do flychecks using rust-project check.
Also:

rust-project develop-json --use-clippy false
Don't just exit silently if check.bxl fails, show us what went wrong
Errors out if your rustc sysroot does not have the rust-src component. This was an undocumented requirement and rust-analyzer just doesn't work without it, so we should fail as early as possible.
#[cfg(fbcode_build)]s the existing buck2 test runnables, the new ones work with the rustc_test harness and OSS buck2.

Attn @davidbarsky

Previously rust-project worked with the $saved_file interpolation in rust-analyzer. This PR makes it work with a target label, substituted as {label} instead. So it's not really backwards compatible, but we could make it so. Submitting this now to get feedback.

My feeling is that we should move over to {label} can be done in a month or so after this PR lands and we can simply get rid of $saved_file in rust-project. I think we'll need to keep $saved_file in rust-analyzer for a little while longer, as I know the Fuchsia folks use it.

Only problem is there are other buck users that are adopting rust-project and using saved file. Maybe it's still few enough people that we can break the CLI.

Only problem is there are other buck users that are adopting rust-project and using saved file. Maybe it's still few enough people that we can break the CLI.

Gotcha! I think we should keep the $saved_file stuff around for a month or so, but remove it then. I think while a few folks might be using it, but I think a ping on the buck2 fans Discord + some time should be enough should be enough to migrate to the {label} approach.
For what it's worth, I always viewed the $saved_file stuff as temporary workaround and my goal with rust-project was to always make the integration as Cargo-like as possible to ensure that I'd be imposing the smallest possible support burden on rust-analyzer, and {label} feels more conceptually minimal than $saved_file—the former, at least, can be reused with Cargo, but $saved_file can't.


Fixes warp type-cast issue in #189

PR #189 introduced fixing of the field variable to that of the torch's default type.
If it should have been casted at all, it should be casted to that of the image's input type, to circumvent the type-similarity issue not being thrown.
I have decided to remove this cast introduced in #189 altogether, making it the developers responsibility to cast and use correct and matching types.
I have also added a few lines of tests in test_warp.lua to make sure this issue does not re-occur:
out = image.warp(im:float(), mtx:float(), 'bilinear') -- both float
out = image.warp(im:double(), mtx:double(), 'bilinear') --both double

And do note mixing will throw a proper error
out = image.warp(im:float(), mtx:double(), 'bilinear') -- fails with crystal clear type error
out = image.warp(im:double(), mtx:float(), 'bilinear') -- fails with crystal clear type error

Closes https://github.com/NVIDIA/DIGITS/issues/1134

Thank you!


error was: ValueError: 'virtual_networks' is not available in API version 2021-03-01

Package Name:
Package Version:
ansible [core 2.15.5]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/salam/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
ansible collection location = /home/salam/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] (/usr/bin/python3)
jinja version = 3.0.3
libyaml = True
Operating System: WSL Ubuntu 22.04
Python Version:  3.10.12

Describe the bug
I am trying to create a Vnet, subnet and VM in Azure with Ansible, very basic stuff. I get the following error:
TASK [Create virtual network] **********************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ValueError: 'virtual_networks' is not available in API version 2021-03-01. All valid API version are 2015-06-15, 2017-10-01, 2018-04-01, 2018-11-01, 2018-12-01, 2019-02-01, 2019-04-01, 2019-06-01, 2019-07-01, 2019-08-01, 2019-09-01, 2019-11-01, 2019-12-01, 2020-03-01, 2020-04-01, 2020-05-01, 2020-06-01, 2020-07-01, 2020-08-01, 2020-11-01, 2021-02-01, 2023-02-01, 2023-04-01, 2023-05-01.
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n  File \"/home/salam/.ansible/tmp/ansible-tmp-1699285220.0876105-15441-13683065176970/AnsiballZ_azure_rm_virtualnetwork.py\", line 107, in <module>\n    _ansiballz_main()\n  File \"/home/salam/.ansible/tmp/ansible-tmp-1699285220.0876105-15441-13683065176970/AnsiballZ_azure_rm_virtualnetwork.py\", line 99, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/home/salam/.ansible/tmp/ansible-tmp-1699285220.0876105-15441-13683065176970/AnsiballZ_azure_rm_virtualnetwork.py\", line 47, in invoke_module\n    runpy.run_module(mod_name='ansible_collections.azure.azcollection.plugins.modules.azure_rm_virtualnetwork', init_globals=dict(_module_fqn='ansible_collections.azure.azcollection.plugins.modules.azure_rm_virtualnetwork', _modlib_path=modlib_path),\n  File \"/usr/lib/python3.10/runpy.py\", line 224, in run_module\n    return _run_module_code(code, init_globals, run_name, mod_spec)\n  File \"/usr/lib/python3.10/runpy.py\", line 96, in _run_module_code\n    _run_code(code, mod_globals, init_globals,\n  File \"/usr/lib/python3.10/runpy.py\", line 86, in _run_code\n    exec(code, run_globals)\n  File \"/tmp/ansible_azure_rm_virtualnetwork_payload_q1bgk12k/ansible_azure_rm_virtualnetwork_payload.zip/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py\", line 413, in <module>\n  File \"/tmp/ansible_azure_rm_virtualnetwork_payload_q1bgk12k/ansible_azure_rm_virtualnetwork_payload.zip/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py\", line 409, in main\n  File \"/tmp/ansible_azure_rm_virtualnetwork_payload_q1bgk12k/ansible_azure_rm_virtualnetwork_payload.zip/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py\", line 254, in __init__\n  File \"/tmp/ansible_azure_rm_virtualnetwork_payload_q1bgk12k/ansible_azure_rm_virtualnetwork_payload.zip/ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common.py\", line 461, in __init__\n  File \"/tmp/ansible_azure_rm_virtualnetwork_payload_q1bgk12k/ansible_azure_rm_virtualnetwork_payload.zip/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py\", line 281, in exec_module\n  File \"/home/salam/.local/lib/python3.10/site-packages/azure/mgmt/network/_validation.py\", line 25, in wrapper\n    raise ValueError(\nValueError: 'virtual_networks' is not available in API version 2021-03-01. All valid API version are 2015-06-15, 2017-10-01, 2018-04-01, 2018-11-01, 2018-12-01, 2019-02-01, 2019-04-01, 2019-06-01, 2019-07-01, 2019-08-01, 2019-09-01, 2019-11-01, 2019-12-01, 2020-03-01, 2020-04-01, 2020-05-01, 2020-06-01, 2020-07-01, 2020-08-01, 2020-11-01, 2021-02-01, 2023-02-01, 2023-04-01, 2023-05-01.\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

PLAY RECAP *******************************************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Here is the ansible yml file
---
- name: Create Azure VM
  hosts: localhost
  connection: local

  collections:
    - azure.azcollection

  vars_prompt:
    - name: password
      prompt: "Enter local administrator password"

  vars:
    resource_group_name: manageazureansible
    vm_name: awesomevm1
    vnet_name: awesomevnet
    subnet_name: awesomesubnet1
    public_ip_name: awesomepublicip1
    security_group_name: awesomesecgroup1
    network_interface_name: awesomenic1

  tasks:
    - name: Create virtual network
      azure_rm_virtualnetwork:
        resource_group: "{{ resource_group_name }}"
        name: "{{ vnet_name }}"
        address_prefixes: "<IP_ADDRESS>/16"

    - name: Add subnet
      azure_rm_subnet:
        resource_group: "{{ resource_group_name }}"
        name: "{{ subnet_name }}"
        address_prefix: "<IP_ADDRESS>/24"
        virtual_network: "{{ vnet_name }}"

    - name: Create public ip
      azure_rm_publicipaddress:
        resource_group: "{{ resource_group_name }}"
        allocation_method: Static
        name: "{{ public_ip_name }}"

    - name: Create security group that allows RDP
      azure_rm_securitygroup:
        resource_group: "{{ resource_group_name }}"
        name: "{{ security_group_name }}"
        rules:
          - name: 'allow_rdp'
            protocol: Tcp
            destination_port_range: 3389
            access: Allow
            priority: 1001
            direction: Inbound
          - name: 'allow_web_traffic'
            protocol: Tcp
            destination_port_range:
              - 80
              - 443
            access: Allow
            priority: 1002
            direction: Inbound
          - name: 'allow_powershell_remoting'
            protocol: Tcp
            destination_port_range:
              - 5985
              - 5986
            access: Allow
            priority: 1003
            direction: Inbound

    - name: Create NIC
      azure_rm_networkinterface:
        resource_group: "{{ resource_group_name }}"
        name: "{{ network_interface_name }}"
        virtual_network: "{{ vnet_name }}"
        subnet: "{{ subnet_name }}"
        public_ip_name: "{{ public_ip_name }}"
        security_group: "{{ security_group_name }}"

    - name: Create virtual machine
      azure_rm_virtualmachine:
        resource_group: "{{ resource_group_name }}"
        name: "{{ vm_name }}"
        vm_size: Standard_DS1_v2
        managed_disk_type: Standard_LRS
        admin_username: awesomeadmin
        admin_password: "{{ password }}"
        network_interfaces: "{{ network_interface_name }}"
        os_type: Windows
        image:
            offer: WindowsServer
            publisher: MicrosoftWindowsServer
            sku: 2019-Datacenter
            version: latest
      no_log: true

How this can be fixed? Thanks

I was googling and found a thread indicating to drop to v19.1.0. My azure-mgmt-network  is  25.1.0, is there a way to tell it to work with nanother version of the API for instance one of the ones indicated in the error messages like 2023-05-01

@eliassal I suggest you open this issue over at https://github.com/ansible-collections/azure
I'm not familiar with the ansible library and whether it can target a different library version or API version for azure-mgmt-network. Tagging @msyyc and @iscai-msft just in case this feature is expected in this version, but I do suspect this is by design.

So how can I fix and make ansible work in this case?

@eliassal I took a quick look at their docs and it appears that these are the requirements they want you to install to use the Azure collection: https://github.com/ansible-collections/azure/blob/dev/requirements-azure.txt#L25
I suggest you open this issue with https://github.com/ansible-collections/azure/issues if they are specifying the wrong version of azure-mgmt-network to use with their library.
Closing this as the issue is unrelated to the Python SDK.


Show previous analysis id+name on input form field for an analysis

All "input" fields in the analyses forms currently only display the id (e.g. "a0"), it should display the input with more visual cues, like this:

Should be implemented in such a way that's it's reusable for all the different kind of forms that have a source.
In the case it's a secondary source it should not be disabled and slightly different styling too:

yep, important on UX


Schedule for the next release

Hi,
Thank you for providing this package to the community.
I am getting an issue related to the commit https://github.com/getsentry/sentry-laravel/commit/bb8efcbb1c0a5c6510e7afb3c8a82a2f0603896a that conflicts with a package I developed, which replaces the event dispatcher (but respects the contract).
Is there any release date for the new version that includes fixes like this?

Hey @fntneves I see we never released an version containing that fix since we need to split out Laravel 4 support first for that to happen (since v4 does not have those contracts, see #107). Let me get on that. I have no fixed date though, soon-ish 😉

Hi @stayallive, thank you for your reply!
I understand, let me know if you need help to make this happen 😉
Thank you !

Hey, any ETA on this? :) Master branch contains some useful fixes and a PR for Laravel 5.6 log channels we are currently using (through the fork).

@sebastiaanluca Yes, planning is this week.
The "wait" is for sentry-php which needs a few looks on some fixes, we're getting there!


Create dark mode for button component

[x] Add dark mode to Adobe XD library/file
[x] Update guidelines with new images/token definitions
[ ] Implement dark mode in React library

Updated the button component page for dark mode:

New specifications and states images
Updated color table definitions

Branch:
https://github.com/rconcepcion3/halstack-react/tree/rconcepcion-1060-darkmode-button-design
Source XD file Updated (not yet published to Halstack Style Guide)


static factory seemed off

http://designpatternsphp.readthedocs.io/en/latest/Creational/StaticFactory/README.html
most of static factory implementation I see does not seem to require another class, as the factory method itself is implemented statically on the same type. examples are like :
php datetime Carbon library, like Carbon::now()
http://carbon.nesbot.com/docs/
guzzlehttp ServerRequest::fromGlobals()
https://github.com/guzzle/psr7/blob/master/src/ServerRequest.php
and even php DateTime::createFromFormat() itself
or please correct me if my understanding is wrong. I think it's one of the most used pattern out there. or is this documentation isn't meant to be for static factory method?

I think that both approaches are OK.
I mentioned examples you have one static factory per class which is returning objects for class that is attached to. And this is OK. The example that is present in this repository assumes that you have multiple classes sharing same interface and you want to create those objects from one static factory. You could split this and setup static factory separately for FormatNumber and FormatString but in this particular example it would be a code duplication.
It makes any sense for you?

Okay, I think I can say that static factory and static factory method is totally two different things.
As in my opinion, the pattern introduced here (static factory) is so unheard of, and going to be confused with the famous static factory method pattern..

@eimihar - true.
On the other hand there is Factory Method described. Not static of course but gives a general idea.
Please feel more thank welcome to contribute Static Factory Method pattern to the repo :)


Remove superfluous shader_format_glsl feature

Objective
naga_oil now includes glsl support unconditionally, so this feature isn't doing anything.
Fixes #8505 (see recent discussion there and in #8657)
Solution
Remove the feature
Changelog

Removed the shader_material_glsl feature. glsl support is now included by default.

Migration Guide
The shader_material_glsl feature was removed. glsl support is now included by default. If you were previously using this feature, you can remove it from your Cargo.toml.

I would be more in favour to make it optional in naga_oil

Cool, me too. I was under the false impression that wasn't going to happen in time for 0.11.


timeout error

Hi,
I was able to download couple of ebooks but after that getting timeout error as below.
"
Initialize file
URL Template: https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/UX200_EN_Col21/xml/topic$$$.svg
File path: C:\Test/UX200_EN_Col21.pdf
r: waiting for selector "#progressIndicator" failed: timeout 30000ms exceeded
at new d (C:\saplearninghub-pdf-downloader-1.1.0\dist\index.js:1:1075704)
at DOMWorld._waitForSelectorOrXPath
"
Could you please help me on it?
Thanks

My bad..I have entered wrong URL.
Its working all good.


CFE or VM: Execution of unbound external should throw

The test outcome expectations in tests/language/external_abstract_fields/external_fields_test.dart have been corrected to match the specified behavior: Throwing a NoSuchMethodError when an external function with no binding is called.
This makes the configurations dartk-strong-linux-debug-x64, dartk-strong-linux-release-x64, dartk-weak-asserts-linux-debug-x64, dartk-weak-asserts-linux-release-x64 fail, because they don't throw.
@johnniwinther, @mkustermann: I'm not sure about the label on this issue, is it up to the CFE to generate code that makes this happen, or is this handled in the backend?

Labeling as area-vm for now since we do not have a way for backends to tell which external members are allowed and which are not.

Right. The behavior is actually specified in a way that allows many things:

An external function is connected to its body by an implementation specific
mechanism. Attempting to invoke an external function that has not been
connected to its body will throw a NoSuchMethodError or some subclass thereof.

I made the tests expect a NoSuchMethodError because it seems reasonable that the implementation specific mechanism would bind external declarations to callable entities for a specific reason (e.g., FFI would use metadata and a marker supertype to request a binding from an external getter to a compiler-generated native function reading some non-Dart memory).
With no specific reason to perform a binding of any kind (which is the situation we have in the test), I'd assume that we are in the case where the external declaration "has not been connected to its body", so invocations should throw a NoSuchMethodError.
That's outside the language, however, because an 'implementation specific mechanism' could have a way to bind these particular external declarations to a body (FFI uses metadata, but it could also be based on extra command line arguments, etc). An external declaration could also be bound to different callable entities at different times during an execution. So it seems impossible for the front end, but natural for the back end, to determine whether each individual external function is unbound and should throw.


spike(robot-server): evaluate performance of async SQLAlchemy

Overview
As currently implemented, our SQLite access for persistence in the the /runs and /protocols endpoints uses SQLAlchemy's default, synchronous API. The robot-server application uses a single-process, cooperative-multitasking architecture via Python's async/await.
Our synchronous database access may be causing significant performance issues by blocking the application's thread(s) from processing other important tasks, like hardware interaction or executing protocol logic.
Acceptance criteria
Expected output of this spike :

[ ] A write-up about why or why not SQLAlchemy's async interface would improve
[ ] If we expect performance to improve, a prototype swapping our usage of SQLAlchemy's Engine with its available async interface: AsyncEngine

Cross-reference: #10025


Release Candidate 0.10.0-rc3

This patch marks release candidate 0.10.0-rc3.

Codecov Report

Merging #1014 into master will increase coverage by 0.31%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1014      +/-   ##
==========================================
+ Coverage   34.16%   34.47%   +0.31%
==========================================
  Files          36       36
  Lines        2901     2901
==========================================
+ Hits          991     1000       +9
+ Misses       1807     1797      -10
- Partials      103      104       +1

Impacted Files
Coverage Δ

...storage/drivers/storage/vfs/storage/vfs_storage.go
40.28% <0%> (+2.15%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 32ca198...c76d159. Read the comment docs.


x/tools/internal/lsp: we should respect the contentFormat capabilities

At the moment things like hover always send back markdown content, even if the client cannot support them.
This came up when implementing the gopls query definition command line, which wants the hover in plain text and has to strip off the markdown formatting by hand.

Duplicate of #31078


      cannot call method 'isandroid' of undefined

tried to run my app on a bluestack emulator got this error cant say am happy after it took me almost a day to migrate to this package from d old ionic push am getting token though but thats where it end help me please

Sorry, we need more information to investigate the Problem.
Can you please paste the complete Error-Stack?
Please also add some version-numbers (cordova, node, npm)
On which system are you? mac/windows?
Thanks


2nd level import requires extra closing bracket in 1st level import

Affected versions: 1.8.1, 1.8.2, <IP_ADDRESS>
When there is a import in a file, that on itself was imported, then an extra closing curly bracket } at the end of the intermediate file is needed. Otherwise the following error is thrown:
[error] line[x] column[y], MenuType expected "intermediate.nss"

So in an import tree, any intermediate file is affected:
shell.nss
|
├── a.nss
├── b.nss                     <= affected!
│   └── b.i.nss               <= affected!
│       ├── b.i.1.nss
│       └── b.i.2.nss
├── c.nss
└── d.nss                     <= affected!
    ├── d.i.nss
    ├── d.ii.nss
    └── d.iii.nss             <= affected!
        └── d.iii.1.nss       <= affected!
            ├── d.ii.1.A.nss
            └── d.ii.1.B.nss

As an example:
shell.nss
|
└── metaworx/convert.nss             <= affected!
    ├── metaworx/convertSubmenu.nss
    └── metaworx/convertSubmenu.nss

shell.nss (not affected)
shell
{
	var
	{
		mwxConvertMedia =<EMAIL_ADDRESS>	}

	// ..

	dynamic
	{
		import 'metaworx/convert.nss'  //   <== 1st level import. All is good in this file.
	}

	// ..
}
//  <== Since this is the top-level file, there is no need for an extra closing curly bracket.

metaworx/convert.nss (affected)
// show this menu on the desktop and taskbar
menu(
	title     = 'Convert'
	type      = 'desktop|taskbar'
	separator = 'both'
	image     = \uE0DA
)
{
	import "convertSubmenu.nss"  //  <== 2st level import.
                                     //      This import raises an error, if the file
                                     //      does not have an additional closing
                                     //      curly bracket } at the end
}

// show this menu also in the explorer on all directories ending with "abc"
menu(
	title     = 'Convert'
	type      = 'directory'
	find      = '*abc'
	separator = 'both'
	image     = \uE0DA
)
{
	import "convertSubmenu.nss"  //  <== 2st level import.
                                     //      This import makes no difference,
                                     //      since there is already another import

}
}  //  <== Note this extra closing curly bracket.
   //        Without this, I would get the following error:
   //       [error] line[x] column[y], MenuType expected "convert.nss"

metaworx/convertSubmenu.nss (not affected)
item(
	title  = 'Some info'
	vis    = label
	col    = 0
)

separator

item(
	title     = 'Default'
	image     = \uE259
	cmd       = @mwxConvertMedia
	args      = '--default "" @sel.path.quote'
)

item(
	title     = 'Medium'
	image     = \uE257
	cmd       = @mwxConvertMedia
	args      = '--medium "" @sel.path.quote'
)
//  <== Since there is no import in this file, there is no need for an extra closing curly bracket.
//      If there was another import also in this file, then the bracket would be required.

The debug version mentioned in https://github.com/moudey/Shell/issues/185#issuecomment-1460374034 seems to fix this issue.
However, the issue is now that if there is an extra closing bracket, the explorer.exe seems to get into an endless loop until it crashes .... :-)

However, the issue is now that if there is an extra closing bracket, the explorer.exe seems to get into an endless loop until it crashes .... :-)

This issue has been fixed. Curly braces at the end of the imported file are ignored


feat: add minitrace-futures to support instrumentation for futures

Changes:

Add a crate minitrace-futures
Add a trait Instrumented

Provide in_span, enter_on_poll, enter_on_item instrumentation.

Checklist:

[x] Support futures 0.3.x
[ ] Support futures 0.1.x

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 78.719%

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
1709

Relevant Lines:
2171

💛  - Coveralls

How should I fill in the author field in the Cargo.toml file?

I've a question about the maker: what is the proper way to use maker? For example, Sink has 4 methods to create span on poll, and the maker has no way to know which is called. And when get called, is local parent available?

Sink has 4 methods to create span on poll, and the maker has no way to know which is called.

Perhaps replace maker in enter_on_poll() with FnMut(&str) -> Span?

And will a local parent available when get called?

Can set_local_parent be left for the user to decide?
let mut drain = sink::drain().enter_on_poll(|| {
        let span = Span::enter_with_parent("SubTask" &root);
        // Set the local parent so that `LocalSpan`
        // becomes available in the sink.
        (span.set_local_parent(), span)
});

or
let mut drain = sink::drain().enter_on_poll(||  Span::enter_with_parent("SubTask" &root));

This seems too complicated. Maybe we could break it down. Perhaps a use_root field to indicate EnterOnItem to create a root span for each item? Perhaps in_span and enter_on_poll can be removed since meaningless.

This seems too complicated, and maybe we could break it down

OK, let's confirm the approximate API first.

Perhaps a use_root field to indicate EnterOnItem to create a root span for each item?

It can be done with:
let s = stream! {
        for i in 0..2 {
            yield i;
        }
}
.enter_on_item(|| Span::root("Root", SpanContext::random()));

In my scenario, I want to create a span for the user from the end of the last request to the receipt of the next request data. I hope this span can also collect some log events from the codec layer (the span needs to be the local parent), and it is best to report them as early as possible (the span is a root span). And I found that the duration of this span can be used to calculate a user's request frequency.

However, in fact, what I would prefer to do is to calculate the time consumed by the codec layer. It seems difficult to achieve without modifying the Item types of Stream and Sink.
If I want to fully customize the lifetime of the span, then need to change the type of Stream and Sink Item to the following:
enum Item<T> {
    StartSpan,
    EndSpan,
    Item(T),
}

The instrumentation layer opens a span upon receiving StartSpan and ends the span upon receiving EndSpan.
For some simple stream or sink,

Perhaps in_span and enter_on_poll can be removed since meaningless.

For some simple streams or sinks, such as a snapshot stream that closes after complete reception, we can use in_span to handle it. The enter_on_poll is designed to provide an API similar to FutureExt and it could be removed.

It can be done with:

let s = stream! {
        for i in 0..2 {
            yield i;
        }
}
.enter_on_item(|| Span::root("Root", SpanContext::random()));

I mean, instead of a flexible but error-prone maker, a specialized use_root is better, if the only thing we want is to switch between Span and root span.

However, in fact, what I would prefer to do is to calculate the time consumed by the codec layer. It seems difficult to achieve without modifying the Item types of Stream and Sink.

Maybe you can do it by implementing https://docs.rs/tokio-util/latest/tokio_util/codec/trait.Decoder.html?

tracing-futures will not create new span for items but only enter a span, which will last the entire lifetime of the steam/sink. It seems like in_span in minitrace.

There is another question: is enter_on_item still needed? If so, I will submit a new PR to try to constrain the maker solution.

is enter_on_item still needed?

I believe it will prove valuable if we can precisely define the semantics of enter_on_item (specifically, determining the precise moment that is considered as enter_on_item) and also develop a concrete example or use case to illustrate its application.

@iGxnon Thank you!