sshd fails to start

I have OpenSSH.Server installed, but sshd fails to start.
-Powershell is running as administrator.
Repro steps
PS D:\Software> Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'

Name  : OpenSSH.Client~~~~<IP_ADDRESS>
State : Installed

Name  : OpenSSH.Server~~~~<IP_ADDRESS>
State : Installed

PS D:\Software> Start-service sshd
Start-service : Failed to start service 'OpenSSH SSH Server (sshd)'.
At line:1 char:1
+ Start-service sshd
+ ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
   ServiceCommandException
    + FullyQualifiedErrorId : StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand

System Event Log:
The OpenSSH SSH Server service terminated unexpectedly.
Firewall Settings look odd:

As a test I disabled all rules except for 1 of the private sshd rules.  Still failed.
Any help?

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

ID: 18a5a4e5-2604-23c2-1374-68a6974170bc
Version Independent ID: f93809cc-eb5e-6b9b-ed58-c8811a8ee21f
Content: Installation of OpenSSH For Windows Server
Content Source: WindowsServerDocs/administration/OpenSSH/OpenSSH_Install_FirstUse.md
Product: windows-server
Technology: administration
GitHub Login: @maertendMSFT
Microsoft Alias: damaerte

@konstruktoid : Do you have any ideas about this? Or should we refer to some support instance?

I have no idea, I guess I need support.  thanks!

Without any error logs I can't really assist. Anything in EventViewer?

yes, from my original comment:

The OpenSSH SSH Server service terminated unexpectedly.

Can I turn on other logging?

PS C:\WINDOWS\system32> Get-Service sshd

Status   Name               DisplayName
------   ----               -----------
Stopped  sshd               OpenSSH SSH Server

PS C:\WINDOWS\system32> sshd --help
unknown option -- -

OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
usage: sshd [-46DdeiqTt] [-C connection_spec] [-c host_cert_file]
            [-E log_file] [-f config_file] [-g login_grace_time]
            [-h host_key_file] [-o option] [-p port] [-u len]

PS C:\WINDOWS\system32>_

The OpenSSH SSH Server service terminated unexpectedly. won't tell us about the root cause, and I don't know enough about logging on Windows on how to turn that into a useful message.

Hi,
Thanks for your comments!
I think I found the relevant event logs with more useful information.
Under Applications and Services Logs -> OpenSSH -> Admin.
I get the following errors sequentially:

sshd: error: Bind to port 22 on :: failed: Permission denied.
sshd: error: Bind to port 22 on <IP_ADDRESS> failed: Permission denied.
sshd: fatal: Cannot bind any address.

Note: I run my powershell window as administrator.
This is my hosts file  at C:\Windows\System32\drivers\etc\hosts (dunno if it helps):
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      <IP_ADDRESS>     rhino.acme.com          # source server
#       <IP_ADDRESS>     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#       <IP_ADDRESS>       localhost
#       ::1             localhost
<IP_ADDRESS> blocked-your-system-61.gq
<IP_ADDRESS> MEDIA mpc
<IP_ADDRESS> vm.lcl
<IP_ADDRESS> mac
<IP_ADDRESS> devpc.ip

Thanks @brucejo75, can you verify you user with whoami before starting sshd?
If you are a system user, could you please step through https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps?

Could this have anything to do with the multitude of inbound rules I have for sshd & OpenSSH?

Configured the sshd_config file, added:

SyslogFacility LOCAL0
LogLevel DEBUG

Here is the result of running the commands:
PS C:\ProgramData\ssh> whoami
devpc\admin
PS C:\ProgramData\ssh> Stop-Service sshd
PS C:\ProgramData\ssh> psexec -s sshd.exe -d

PsExec v2.2 - Execute processes remotely
Copyright (C) 2001-2016 Mark Russinovich
Sysinternals - www.sysinternals.com

debug1: sshd version OpenSSH_for_Windows_7.7, LibreSSL 2.6.5
debug1: private host key #0: ssh-rsa SHA256:hXx1JyZ5YwFXwYkMLJ1R0CT2mBF4jACpu82Ime81bOg
debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:oSfbiqRznCHFPCdW+g5uSY3Jxd9V8EgqOgNtU0hxM9E
debug1: private host key #2: ssh-ed25519 SHA256:b3xydKOH5a8eZ+dnpWL5uK2c41BLb859snWDv+PTDNE
debug1: rexec_argv[0]='sshd.exe'
debug1: rexec_argv[1]='-d'
debug1: Bind to port 22 on ::.
Bind to port 22 on :: failed: Permission denied.
debug1: Bind to port 22 on <IP_ADDRESS>.
Bind to port 22 on <IP_ADDRESS> failed: Permission denied.
Cannot bind any address.
sshd.exe exited on DEVPC with error code 255.

No log files are output.
Should I move my issue over here: https://github.com/powershell/Win32-OpenSSH/issues?

Could this have anything to do with the multitude of inbound rules I have for sshd & OpenSSH?

Possibly. Maybe there are some recommended ways to set specific rules for its use. Myself, I don't have the required experience to know the answer.
(part of the log omitted)

debug1: Bind to port 22 on ::.
Bind to port 22 on :: failed: Permission denied.
debug1: Bind to port 22 on <IP_ADDRESS>.
Bind to port 22 on <IP_ADDRESS> failed: Permission denied.
Cannot bind any address.
sshd.exe exited on DEVPC with error code 255.

No log files are output.
Should I move my issue over here: powershell/Win32-OpenSSH/issues?

Looks like a good idea to me. I am hopeful that they may have more experience with proper usage and setup of OpenSSH in a Windows environment.

Closing...


DlGrid > improvements and restructuring

Today we have 2 main components for widget handling with dl-grid and dl-grid-row
We want to merge these two components into one with specific API
<dl-grid
 layout=”[2,3]”
/>

Props:
Layout -> null | array of numbers
If layout is null the grid is a flex style container that just displays grid where it allows multiple items in the container by size and by min size and restructure
otherwise the format of layout is an array of numbers where the length of the array is the amount of rows and each row contains layout[rowIndex] columns.

@VictorOpenTech FYI

@VictorOpenTech  this task has been done in https://github.com/dataloop-ai/components/pull/93 PR


Support multiple projects with different vocabulary and corpus

Right now some parts of Annif are hardwired for YSO and Finna.
Instead there should be a configuration file (projects.ini) specifying what projects exist. Each one could have a different subject vocabulary, corpus, language and corresponding Elasticsearch index.
The current model where there is a single YSO index with data in three languages could be split up to become three projects. The configuration could look something like this:
[yso-finna-fi]
name=YSO+Finna Finnish
language=fi
analyzer=finnish
corpusdir=corpus/yso-finna/fi/

[yso-finna-sv]
name=YSO+Finna Swedish
language=sv
analyzer=swedish
corpusdir=corpus/yso-finna/sv/

[yso-finna-en]
name=YSO+Finna English
language=en
analyzer=english
corpusdir=corpus/yso-finna/en/

The section tags yso-finna-fi etc. would be the project id's and used as the Elasticsearch index names.
Command line tools would take the project id as parameter, e.g. autoindex.py yso-finna-fi <document.txt, instead of the current language parameter.

Also need to restructure the REST API after this.
Probably the current autoindex method, with a lang parameter, could be changed to /projects/{projectid}/autoindex and the lang parameter could be dropped since the language is part of the project configuration.


Changes jQuery alias 'expr[":"]' to 'expr.pseudos'

Uses newer alias as per jQuery Migrate documentation
https://github.com/jquery/jquery-migrate/blob/master/warnings.md#jqmigra
te-jqueryexpr-is-jqueryexprpseudos
I want to resolve #1813

In which version of jquery was $.expr.pseudos added?

If I read the commit [1] correctly, this feature $.expr.pseudos was added with jquery 3.0.
this means merging this PR would drop support for jquery 2.x ?
[1] https://github.com/jquery/jquery/commit/0402963845be8d71c4e8ddf65e7c055014739b60

@staabm
AFAIK, .pseudos is a Sizzle thing and was there from the version 1.8.0 of Sizzle.
Also, $.expr[ ":" ] is an alias of $.expr.pseudos. So it's backward compatible with older versions of jQuery (1.8.0+).

It looks like the jQuery Foundation does not want to encourage the use of custom pseudos, so public documentation is extraordinarily sparse. As far as I can tell from the discussions linked below, $.expr.pseudos (or jQuery.expr.pseudos) works back to 1.8.0.

https://github.com/jquery/jquery/issues/2073
https://stackoverflow.com/questions/11624345/getting-the-match-object-in-a-custom-filter-selector-in-jquery-1-8
https://github.com/jquery/sizzle/wiki#back-compat
https://bugs.jquery.com/ticket/12409

Thx for the patch, looks good as is.
Since we support jquery 1.7.2+ we need to wait for a while before merging (or a 1.7.2+ compatible patch).

... (or a 1.7.2+ compatible patch)

Something like this ?
$.extend( $.expr.pseudos || $.expr[ ":" ], { ... } );

Yeah, imagined something like that

Thank you, @Arkni! I added your backwards compatibility fix and did some quick testing. It seems to be working with both jQuery 3.0 and 1.7.2.

My pleasure :)
Just a note, something wrong happened when you rebased your PR (there are 10 unrelated commits included). You can fix that by rebasing a second time on top of upstream/master.

PR is fixed now
Ah ha! I thought that was weird to see so many commits in the PR, but I wasn't sure how to fix it. Thanks again!

squashed and merged, thx!


Make smaller docker image using multistage build

Make docker image smaller
docker build -t petrjurasek/docker-hub-rate-limit-exporter .
Sending build context to Docker daemon  1.632MB
Step 1/11 : FROM python:3-alpine as build
 ---> bcab265f7997
Step 2/11 : WORKDIR /install
 ---> Using cache
 ---> 89841d543429
Step 3/11 : COPY ./requirements.txt /requirements.txt
 ---> Using cache
 ---> f11e405f8b7f
Step 4/11 : RUN pip install --prefix=/install -r /requirements.txt
 ---> Using cache
 ---> 969a9e782b6b
Step 5/11 : FROM python:3-alpine
 ---> bcab265f7997
Step 6/11 : WORKDIR /src
 ---> Using cache
 ---> 3beb98e81b4b
Step 7/11 : ENV PYTHONPATH '/src/'
 ---> Using cache
 ---> 14a599d0a5a7
Step 8/11 : COPY --from=build /install /usr/local
 ---> Using cache
 ---> 06518f027d2e
Step 9/11 : COPY ./collector.py /src
 ---> Using cache
 ---> 642997fc642e
Step 10/11 : EXPOSE 80/TCP
 ---> Using cache
 ---> 42b51bc779d4
Step 11/11 : ENTRYPOINT python /src/collector.py
 ---> Using cache
 ---> 46aaa0825397
Successfully built 46aaa0825397
Successfully tagged petrjurasek/docker-hub-rate-limit-exporter:latest

docker images | grep docker-hub-rate-limit-exporter
petrjurasek/docker-hub-rate-limit-exporter   latest              46aaa0825397        4 minutes ago       49MB
viadee/docker-hub-rate-limit-exporter        version-1.1         4f3514c373e1        28 hours ago        895MB

Thanks for contributing!
I'll look at it over the weekend. We also would need to create a new release/tag for the changes to take effect.

Looks good and is merged now!
Thanks!

@mstein11  thanks for processing.
I see that 1.2.  tag was also created (thanks for that), however the image tagged in docker hub has same digest as version 1.1

@petrjurasek thanks for check on that.
There was a slight mistake with tagging the right commit. I fixed it and now the correct Dockerfile is used for building the image. See attached screenshot


Synchronized with community and upgrade to latest release

Had to add community io.thorntail:arquillian, as it isn't productized

@Ladicek pushed changes


NGINX 1.13 unknown directive "rtmp" in /etc/nginx/nginx.conf

Congratulations for your work.
I could make it run on a teste server but on a production server I am getting this error...

My conf is like this ...

Please I really need your help, i already take me days to make it work

Hi,
Did you recompile nginx with rtmp module on your production server ?
/etc/nginx path is generally the path when you install nginx with packager system.
Regards

OMG, I just realize I have 2 nginx installed, I have no idea how the remove one in /etc/nginx (could you please help me?)
I have 2 more questions ...
1 - when i use the on_publish it renames my live stream name. on the version I have on the test side keeps the same but on the production side changes it to the on_publish url. there is a way to keep the live stream name, not the url?
2 - another thing... looks like i can stream with no problem, but it is not outputting any stream, like does on test side. I onli get a black screen in any player i have tried to retrieve the stream.
please take a look on my stats...

Hello
I would like to congratulate you for the fantastic work, I will use this project as an official streaming server.
The project I'm working on is YouPHPTube, a YouTube clone and I'm implementing Live Streaming functionality, as it is on youtube.
If you have the time take a look and tell me what you think.
Website: https://www.youphptube.com/
Demo site: https://demo.youphptube.com/
Git: https://github.com/DanielnetoDotCom/YouPHPTube
I finally managed to solve these two problems ...
1- on_publish renames live stream issue, that's why on_publish does not accept http, and my server was redirecting all http requests to https. I created a virtual host that does not do this redirect and everything worked normally
2- The other problem with the black screen I noticed was a problem in the connection, because at another time I tested the same features and everything worked normally.
Now I just need to resolve how to have only one Ngnix installed
Thanks one more time and I wish hear your opinion about the project


Incorrect payload of mutation due to parallel database queries

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Not really a bug but more an issue of which I don't know how to fix it or create a workaround.
The problem is that the result of our mutation sometimes contains inconsistent data.
We use MySQL for storing our data, and use the DefaultTransactionScopeHandler to wrap all mutations inside a single transaction.
Currently, the mutation which gives the problem looks something like this:
public async Task<IEnumerable<MyResult>> MyMutation(MyInput input, [Service] IMyRepository repository) {

    await repository.PerformSomeChange(<arguments from input>);

    var ids = new[] { <id 1 from input>, <id 2 from input> };
    return await repository.LoadItems(ids);
}

The PerformSomeChange method performs an UPDATE query.
The node type MyResult has a one-to-many relationship with MyOtherNode. It therefore has a field others
which is defined using a method on the MyResult class and is loaded using a DataLoader like this:
public async Task<IEnumerable<MyOtherNode>> GetOthers(MyOthersForMyResultDataLoader dataloader)
    => await dataLoader.LoadAsync(Id, CancellationToken.None);

The problem occurs when, occasionally, HotChocolate decides to use two separate dataloader instances for loading
the others field on the two result items.
In this case, the two different dataloaders use two different repository instances which in turn use two different MySQL connections.
This means that at least one of these MySQL connection instances will use a different underlying database connection than the one which was used
to perform the update query in the PerformSomeChange method with (the other underlying connection may be the reused one from the UPDATE query).
Since the mutation has not finished yet, the transaction has not been committed yet and this connection will therefore not see the changes in the database made by PerformSomeChange, which will in turn lead to an inconsistent/wrong result of the mutation.
When HotChocolate decides to use a single dataloader for loading the others field of both MyResult items the underlying database connection which was also used for PerformSomeChange is reused, which does see the updated data in the database and therefore the issue does not occur in that case.
I would ideally want to solve this problem by loading the result of the mutations after all mutations have finished
and the database transaction has been committed, but I have no idea how to do that in HotChocolate.
Is there any way to achieve that, or another way to make sure that I the mutation always returns a result that is consistent with the previously performed changes?
Steps to reproduce
(I can create a small POC project if that is requested).
Relevant log output
No response
Additional Context?
No response
Product
Hot Chocolate
Version
12.14.0

Did someone already look at this issue?

You need to have a service scope for this. This is not a bug of Hot Chocolate its a bug in your DL implementation.


How to catch an exception

Hi all.
I got this code snippet and when it is successful it returns $test == 1. I expected $test to be 0 when it fails, but it isnt. It throws an exception. How can i prevent that?
$test = $driver->wait(10)->until(
WebDriverExpectedCondition::textToBePresentInElement(
WebDriverBy::id('id_of_div'),'successful'
)
);

What's the exception? May be just to wrap this snippet with a corresponding try-catch?
As we can see at https://github.com/facebook/php-webdriver/blob/community/lib/WebDriverWait.php , it's an expected behavior, and i uess you can set $test = 0 when wait throws NoSuchElementException exception.

Fatal error: Uncaught exception 'Facebook\WebDriver\Exception\TimeOutException' in /var/www/html/selenium/vendor/facebook/webdriver/lib/WebDriverWait.php:78 Stack trace: #0 /var/www/html/selenium/vendor/facebook/webdriver/fleck.php(71): Facebook\WebDriver\WebDriverWait->until(Object(Facebook\WebDriver\WebDriverExpectedCondition)) #1 {main} thrown in /var/www/html/selenium/vendor/facebook/webdriver/lib/WebDriverWait.php on line 78
Thats the exception.
Tried this now which doesn't work...
try{
$test = $driver->wait(10)->until(
WebDriverExpectedCondition::textToBePresentInElement(
WebDriverBy::id('id_of_div'),'successful'
)
);
}
catch(NoSuchElementException $e) {
$last_exception = $e;
$test = 0;
}

... got it. Thanks for your suggestion. It was a timeoutexception in my case so the catch had to look like that:
catch(TimeOutException $e) {
$last_exception = $e;
$test = 0;
}

All of these custom exceptions are all extended off WebDriverException, which in turn extends off of Exception. You can just do a catch on Exception if you want to catch any and all forms of failures thrown by PHP WebDriver.


Add maintainers

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge/core can you merge this to add us as maintainers?


Changes in /etc/dhcp/dhclient.conf does not take effect

adding for example prepend domain-name-servers <IP_ADDRESS>; does not add anything in /etc/resolv.conf after closing bash and reopening it again

Today, we recreate /etc/resolv.conf on instance creation and we don't run dhclient in our startup path. Could you share the auto created resolv.conf file with me?

I have the same issue and I can share my /etc/resolv.conf
search Dlink Dlink
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver fec0:0:0:ffff::1
nameserver fec0:0:0:ffff::2
nameserver fec0:0:0:ffff::3

And ipconfig from win cmd if it is necessary
Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  .  We investigated this issue and found that for machines where the first entry on the DNS list was an IPv6 DNS entry that lacked a route DNS lookup fails. Apparently glibc cycles through the first three entries in the resolv.conf file but this is only true when the nameserver returns success but zero records (doesn’t know how to resolve the name). We will work towards a more graceful solution here and post an update when we have a build with the fix released.

We believe that this networking issue has been fixed, please reopen if you continue to have issues.


Fix Analyzer Crash

Issue #96 is a crash in the dynamic analyzer. Each trace has its own analysis thread, but analyse_calls loops over all the traces while using the flow from a specific trace. To fix this, I simply removed the loop so we only analyze the calls for the provided trace. Also, instead of taking flow as an argument, we get it from the provided trace to avoid mixing this up again.
Specifically, the crash was a result of looking up a clnum from an instruction flow in the depth map of a shorter trace, leading to a list index OOB error.

Ugh, why is Travis failing? Its internet just dies?

yea, i don't know

I ran Travis online and it seemed to pass.
@tim-becker Code review this please?

@nedwill Looks right to me; nice fix

Thanks, I'll go ahead and merge it.

This doesn't fix the problem for me (using a8e2247...)
Exception in thread Thread-4:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/qnix/src/qira/middleware/qira_program.py", line 510, in analysis_thread
    qira_analysis.analyse_calls(self)
  File "/home/qnix/src/qira/middleware/qira_analysis.py", line 337, in analyse_calls
    endclnum = get_last_instr(trace.dmap,clnum)
  File "/home/qnix/src/qira/middleware/qira_analysis.py", line 291, in get_last_instr
    myd = dmap[clnum]+1
IndexError: list index out of range

(Pdb) print len(dmap), clnum
172 282


Cannot Add QoS Queue to Mininet Switch Port with TCLink

When I tried to Add Queues to A mininet switch port with link options such as 'bw', it doesn't work at all.
I can find them in 'ovs-vsctl list port', shows that each port has a qos uuid bonded. And, 'ovs-vsctl list qos' or 'ovs-vsctl list queue' can show these qoses and queues.
But in 'ovs-ofctl queue-stats ' command, there's nothing to show.
I thought it seems to be the implementation of the mininet leads to this problem. Does it implemented the bw in a queue as well, so that I couldn't add qos queue to these ports which linked witch a TCLink?

Hi @hu6360567 ,
Have you solved this problem? I face the same problem, and I add the code presented by dferguson, but I can not add options such as bw for link. How about you?
Thanks!
Bo Liu

Hi @lbo52230,
I've solved this problem by adding a default queue that indicates the link bandwidth.

Hi hu6360567
How to add default queue? can you please tell?

@sandhyarathee You may check the following code to create a default queue.
hu6360567/ryu-qos


Rename files to remove numbers

Numbers are no longer needed to set the sort order of the table of contents (there's a separate config file). It was getting problematic to insert numbers anyway (see https://github.com/pelias/pelias-doc/pull/21).
Renamed them to remove numbers
Renamed the -ing files to use imperative verbs (getting-started to get-started)

:fireworks: please merge!


Setting value of a field with sub-classed type outside constructor gets highlighted by mypy

Checks

[X] I added a descriptive title to this issue
[X] I have searched (google, github) for similar issues and couldn't find anything
[X] I have read and followed the docs and still think this is a bug

Bug
According to pydantic docs:

Pydantic works well with mypy right out of the box.

However, constr() (and other similar) cannot be used without mypy nagging about them (see https://github.com/samuelcolvin/pydantic/issues/156#issuecomment-832982432). Workaround is to sub-class instead, like:
class MyStr(pydantic.StrictStr):
    pass

However, while above passes mypy validation, setting fields for an already instantiated class does not:
from pydantic import StrictStr, BaseModel

class MyStr(StrictStr):
    pass

class Model(BaseModel):
    field: MyStr

m = Model(field='jaja')  # works
m.field = 'override'  # gets highlighted

$ mypy file.py
file.py:10: error: Incompatible types in assignment (expression has type "str", variable has type "MyStr")
Found 1 error in 1 file (checked 1 source file)

From mypy perspective, above probably makes sense (although MyStr inherits from str, it may... be different?). Not sure.
You can avoid the error at least two ways:

By actually using the sub-class:
m.field = MyStr('override')  # works

By mimicing pydantic code:
if TYPE_CHECKING:
    MyStr = str
else:
    class MyStr(StrictStr):
        pass

However, both are very inconvenient. Surely not the solution intended here?
I believe docs should mention these oddities/shortcomings, and/or code should be fixed.
Potentially related: https://github.com/samuelcolvin/pydantic/issues/2329
Env
             pydantic version: 1.8.2
            pydantic compiled: True
                 install path: /home/musttu/.pyenv/versions/3.7.10/envs/famp/lib/python3.7/site-packages/pydantic
               python version: 3.7.10 (default, Mar 19 2021, 13:17:32)  [GCC 9.3.0]
                     platform: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid
     optional deps. installed: ['typing-extensions']

In V2, the solution is to use Annotated[StrictStr, annotated_types.Len(min_length, max_length)] or similar. You can also use Annotated[str, Field(strict=True, min_length=10)], etc.
You can see more details in the implementation of constr in v2, and using this Annotated approach (rather than the calls to the constr function) should play nice with type checkers.
In general, I would advise against using the constr etc. functions in v2, precisely because they don't play nice with type checkers and the Annotated approach exists.
If you have more issues and aren't able to achieve what you want in v2, please let us know.

I recognize this may be frustrating, but at this point I don't think we will be releasing a fix for this in v1; if you need this pattern to work in v1, I would unfortunately recommend using one of the "very inconvenient" approaches described in the original issue.

Thanks for taking time to respond 👍🏻
I've seen the advertised typing improvements in other tickets, happy to switch to Annotated and V2 ... once it's out 🥳


Add the planName value to the query

Description
Add the planName value to the query
Field will be sent to Hubspot
As per the design.
Motivation and Context
Unlimited Plan epic
How Has This Been Tested?
Ran query locally.
Release Plan:

As the Submitter, upon requesting review of this pull request, I confirm that the Release Checklist has been completed.
As the Reviewer, upon approving the changes in this PR, I confirm I have reviewed and I agree that the Release Checklist has been completed

Release Checklist Items Skipped?
No

@ezequielc please review. Thanks!


Support for wl-clipboard.

https://github.com/bugaevc/wl-clipboard has the wl-copy and wl-paste utilities which interact with the active Wayland compositor (I believe).
This would be an alternative to the hardcoded xclip.

Currently working on implementing this.

xclip is only a temporary solution and there has already been work put into removing this dependency.
There is no intention to add another dependency for clipboard handling either, so wl-clipboard will not be intergrated into Alacritty.
There has been some great work done by @trimental to add native Wayland clipboard support, though at this moment it's not obvious yet if this will be integrated into Alacritty, Winit or a separate library.

An absolute wontfix? I've already got something working for Wayland clipboard support - it's no larger than 100 lines total diff. Calling another binary is admittedly a bit hacky, but I see no reason this can't be put in place in the meantime, especially given it's not obvious yet if this will be integrated into Alacritty.

An absolute wontfix?

Yes, this is not going to land in Alacritty, though you're free to maintain your own fork.

I see no reason this can't be put in place in the meantime

There's nothing more permanent than a temporary solution. If this is a pain point, the effort should be put into figuring out the remaining issues in connection with winit, rather than putting effort into including this, reviewing this, maintaining this and all the other work that goes beyond just writing the code itself.
Helping out is always incredibly appreciated, however the focus should always be on what makes most sense for Alacritty in the short and long term.

I was hoping it could serve as a solution until #1583 is merged. Anyway, I respect your decision.
For anybody looking for wl-clipboard support, I'll be doing my best to keep my WaylandClipboard branch rebased with master until a proper implementation is merged.

An alternative workaround would be wl-clipboard-x11, a wrapper for wl-clipboard that impersonates xclip: https://aur.archlinux.org/packages/wl-clipboard-x11/.
Good enough for alacritty.

I really like this solution. I'm going to delete my branch and use it instead. Thanks for telling me about it.

Why cant we just set a variable which will specify the clipboard application?

@nifker AFAIK this isn't necessary anymore because Alacritty now supports the standard Wayland clipboard protocol (through the use of a library).

@nifker What is the advantage of using an external clipboard? In case you are just annoyed with #2574, please keep your annoyance with you. However you can implement wl-clipboard support and keep it in your fork, no one stops you from doing this.
@chrisduerr already made a very solid point here. Just my 2 cents here: It's better fixing our current bugs rather then adding "work around"s for them and maintaining them.

Is it really supported oob ? I just built alacritty on my Debian Buster and I cannot copy paste using select / middle click, did I miss something ?

@eLvErDe Have you built the latest master? What's you compositor?

Make sure you're running the latest master (db63c31554c01667b0b8b100dea0fa35e3094e07). It really depends on which compositor you're running though, since not all support primary selection clipboards.
I think Sway and Gnome have been confirmed to work so far.

Now I built 0.3.3. can't really confirm my compositor but I'm running gnome on an old AMD card with free drivers, so I guess I'm on wayland

Now I built 0.3.3.

Do you mean the latest master here? Primary clipboard shouldn't work on GNOME wayland on plain 0.3.3.

FYI you can check that you're on Wayland with echo $WAYLAND_DISPLAY

Fixed the typo. I built the 0.3.3 tag so I now have an answer. A bit late here for today, I'll build master tomorrow. Thanks for your support


Add Provider-Model to psai

This PR adds Provider-Model List to PSAI. This addition enables several different providers to be used with the module and opens up for end users to add their own Providers and Models to the module.

Sweet, just in time for Xmas!
Thank you - I will kick the tires and we'll see where this goes.

@Agazoth
🙏 Thank you very much for creating this PR.
I think it will be very useful for many PSAI users.
Is there an example of use available?
If you have used the functionality it introduces, could you please comment on your experience of using it?
@dfinke
🙏 As always, thanks again for your important contributions to the PowerShell community.
Kind regards,
Claudio Salvio

Thanks @claudio-salvio
This PR is in review, may take a minute to work things thru. @Agazoth  and I have been chatting about it for a while.
What sort of use examples are you looking for. The base PSAI lets you switch btwn OpenAI and Azure OAI.
This is along those lines, and will support a plugin approach so you can plug in the models you need.

Where did we end up on the Invoke-OAIChatCompletion? Resolve the provider from the model?

@Agazoth in https://github.com/dfinke/PSAI/pull/48/commits/07c1fd3118a9774b6d51425ff693bce267598db4
Added xAI. I thought I ran it, set the default to xAI and then did q 'capital if france' and it threw. It looked like I needed to add more to the provider. I can't repro.
Figuring you could see what piece I am missing. I don't see it in Get-AIProvider -All
Feels like too many places the new provider name needs to be added to. I think the validate sets need to be dynamic.

@Agazoth in 07c1fd3 Added xAI. I thought I ran it, set the default to xAI and then did q 'capital if france' and it threw. It looked like I needed to add more to the provider. I can't repro.
Figuring you could see what piece I am missing. I don't see it in Get-AIProvider -All
Feels like too many places the new provider name needs to be added to. I think the validate sets need to be dynamic.

https://github.com/dfinke/PSAI/pull/48/commits/ca7b697b07e8361d4442886d2b77f899a6169c0b should take care of the issue you have here.
I agree on there being too many places (2) new providers need to be updated. Would be cool to just get the Providers in the Providers folders and import the once that dont require anuthing else then an API key. I think we need to add a marker for that on the providers.


Update main

Bring main into line with develop. merge-conflicts branch contains develop + a commit to handle the conflicts. I think we have been updating main and not develop

Is this the other way around?

I think we have been updating main and not develop

Looking at the version history, develop has "real" content up to Jan 2.
Main stops in 2022.


Shopping club c++ project

Describe the project you want to add with tech stack
The Shopping Club Management System is a C++ project that aims to create a system for managing a shopping club or a membership-based retail store. The project provides functionalities to handle the operations related to products, customers, and purchases within the shopping club.
The system allows users to log in and authenticate themselves with their credentials. Different access levels can be assigned to users, such as administrators and regular staff members.
The system provides features to manage customer information. This includes adding new customers, updating their details, and removing customer records. Customer information may include their name, contact information, membership status, and purchase history.

@MohitGupta121 please assign me this


How do I remove x-served-by header?

What version of Hono are you using?
3.5.1
What runtime/platform is your app running on?
Nodejs
What steps can reproduce the bug?
Just simple hono server setup with node.js and then use secureHeader() middleware.
What is the expected behavior?
x-served-by header should not come
What do you see instead?
"x-served-by" header is coming with my domain name.
Additional information
No response

@geekyayush
Maybe this is not Hono matter. Hono does not add the header x-served-by. Perhaps, you can remove it with this code:
app.use('*', async (c, next) => {
  await next()
  c.res.headers.delete('x-served-by')
})

Maybe this is not Hono matter. Hono does not add the header x-served-by. Perhaps, you can remove it with this code:

Thanks for the reply. I had the same exact setup but with Cloudflare worker (using Hono only). There, I didn't have this x-served-by header. But recently, I changed it to node.js using hono node.js adapter and started getting that header.
I will try the fix. Thanks a lot!

Okay. I'll close this. Thanks!


[Epic] Plugin Framework

Insomnia should support the ability to build full-featured plugins on top of. Due to the low performance requirements that Insomnia plugins will have, HTTP would be an ideal protocol for plugin communication. HTTP-based plugins are not as easy to write or run, but maybe that's not a problem.
How it would work:

write a web server with certain endpoints to respond to hooks

/plugin-info to define plugin behavior
/pre-render to set up env and stuff
/pre-request to do things like auth and stuff
/post-request to handle the response (set env vars, etc)

app would contact plugins when hooks are triggered
plugins would respond with certain commands for the app

set-env-var
add-cookie
etc...

Random List of Use Cases

Custom authentication
Storing and refreshing authentication tokens
Computing environment variables

How would be plugin associated with Insomnia app?

@Andreyco If plugins are HTTP-based like the description states, I don't see any clear elegant solutions. If plugins were run as JS child processes it would be much easier.
Here are a few ideas I had so far:

plugin contains manifest file which describes how to interact with it
plugin adds itself by pinging the Insomnia app through a protocol request: insomnia://plugins/add?...

Any other ideas?

Is it possible to associate schema/file extension to Electron application? If so, plugin could be packed as archive of target type. When opened, it could be copied to Insomnia sandbox (or whatever Electron offers) and run after restart.
We should copy Chrome/Firefox behaviour here.
Also, there should be mechanism to run Insomnia without running plugins in case something breaks ;)

@Andreyco I think it's an awesome idea to model this system after the way browsers do it.
Like Chrome's .crx extension files, Insomnia could have a .insomnia extension. The package format could be a simple zip file with the extension renamed.
There are ways to set an Electron app to open certain file extensions (I'm pretty sure), but they could also be added via an open dialog, drag-n-drop handler, or command line interface.

I believe it can be a good idea to mimic not chrome by atom's plug-ins system http://flight-manual.atom.io/using-atom/sections/atom-packages/
It looks completely possible to store plug-ins remotely, besides that there are some extra pros:

plug-in can have it own dependencies
no need to implement a new file type and methods to work with it

I'll leave the link to atom package manager here for you to take a look https://github.com/atom/apm

@ValeriaVG there is also https://hyper.is/ which piggy-backs on npm for plugins. That might be a good thing to start with.
After taking a peek, it looks like apm is just a small wrapper around npm.

@gschier Yes, it's just a wrapper. And hyper looks promising at first sight. But how it will work with http - based plug-ins?

Closing this one, as a basic plugin system is underway, and future work will be done as smaller, separate tasks.


Programmatical migrate() won't work

When you use require('sql-migrations').migrate(configuration) instead of run() it does not attach adapter. So it breaks with an error:
..../node_modules/sql-migrations/commands/run-migrations-command.js:4
return adapter.appliedMigrations()
^
TypeError: Cannot read property 'appliedMigrations' of undefined
migrate() command requires adapter instance as a 2nd argument
as well as rollback()

migrate() command requires adapter instance as a 2nd argument

as well as rollback()

same issue here

try this:
const { postgresql: config } = require('config')
const path = require('path')

const dbConfig = {
  host: config.host, // Database host
  port: config.port, // Database port
  db: config.database, // Database name
  user: config.username, // Database username
  password: config.password, // Database password
}
const migrationConfig = {
  migrationsDir: path.resolve(__dirname, 'schema_migrations'),
  ...dbConfig,
  adapter: 'pg', // Database adapter: pg, mysql
  minMigrationTime: new Date('2018-01-01').getTime(),
}

require('sql-migrations').run(migrationConfig)

npx node ./migrate create xxx
npx node ./migrate migrate
npx node ./migrate rollback


Correctly anchor regex silences

Silence regex rules are not anchored, be explicit

Isn't this the default behavior already? https://github.com/prometheus/alertmanager/issues/99

No, there is PR open https://github.com/prometheus/alertmanager/pull/748, that ticket you mention is likely for something else.


Change language to language.sdk

#92  👈
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @costinsin and the rest of your teammates on  Graphite


What are the names and versions of the libraries, etc. that you need?

What are the names and versions of the libraries, etc. that you need?
It would also be helpful if you could tell us the version of your runtime environment if possible.
I'm trying to run it on carla0.9.6 or 0.9.8.

When I ran it on CARLA, I use 0.8.4 as the default CARLA8 environment (also the main experiment environment) and 0.9.5 for CARLA9.
You don't need any additional environment settings except for what is needed to run 0.9.6. Because this repo is basically the client side implementation in python and the environment dependency for different carla versions should be handled when you build the simulator side.
Note:

One main reason I used 0.9.5 was that pip only supports version no later than 0.9.5 then. If you'd like to run it on later version, you have to compile the python library yourself.
You should set the "--env" flag to be "carla9" to run on CARLA9.
You could check the implementation for CARLA9 support in carla9.py for implementation details.
If I were right, carla9.py supports 0.9.6 and 0.9.5 already. But if you need to use 0.9.8, you may have to make some changes because from 0.9.6 to 0.9.8, some APIs are changed.

Thanks for the reply.
I changed the version to carla0.9.5.
I'll ask again because there's something I don't understand.
Currently I have built carla0.9.5 from source (reference) and put pretrained weights in spc2/pretrain/ folder.
Then I changed --env carla8 to carla9 in the following files in scripts (auto_client.sh debug_carla.sh test_carla.sh train_carla.sh).
Then start carla SDL_VIDEODRIVER=offscreen SDL_HINT_CUDA_DEVICE=0 . /CarlaUE4.sh -carla-settings=Example.CarlaSettings.ini -windowed -ResX=256 -ResY=256 -carla-server -carla-no-hud
I tried to run bash train_carla.sh from a different terminal, but it wouldn't run with errors like "ImportError: No module named numpy".
I'm sure it's already installed with pip, and it's listed in the pip list.
Please let me know if there is anything I can do.
Thanks in advance.

Hi Atusi,
I tried the same pipeline as you did, I believe you can simply fix that by just installing numpy in the docker container. Some potential issues causing the problem:

tricky library sourcing problem, which sometimes happens when you use pip and conda at the same time, you could fix this by simply reinstalling it by conda/pip as the new conda version woks well with built-in pip environment.
Reinstall the whole pytorch pipeline to avoid some potential numpy-torch dependency problem, which I heard might cause the false "ImportError" problem.

I'm closing this issue because it's not directly related to the main content of this repo but please feel free to put any follow-ups.


Make commit history page size be a setting

Commit history always 51 row per page, can i customize the pagesize in setting or in the get query params like page=5&pagesize=25
https://github.com/gogits/git-module/blob/master/repo_commit.go
line 203
var CommitsRangeSize = 50
https://github.com/gogits/gogs/blob/master/routers/repo/commit.go
line  59
ctx.Data["Page"] = paginater.New(int(commitsCount), git.CommitsRangeSize, page, 5)
...

Related: https://github.com/gogits/gogs/issues/3830

Patch has pushed to fix this issue, please test on develop branch or https://try.gogs.io.
See details: https://github.com/gogits/gogs/commit/c69900325d3b2d5eb7584512547fdc567bf6df91.


koodo-reader: fix darwin build

Description of changes
This PR adds support for building the koodo-reader package on Darwin systems.
The PR also contains some small cleanup:

use ELECTRON_IS_DEV instead of patching
use lib.getExe with electron

The cpu_features optional dependency of the ssh2 node package fails to build on x86_64-darwin, but that's expected.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.


Error in v6.1.1

Hello,
I updated to v6.1.1. Getting this error. I managed to track down to the ConfigMergeCommand not resolving extend path /home/mohan/vc-portal/client/webpack.config.[env].js'
/home/mohan/project/vc-portal/node_modules/webpack-config/dist/Config.js:101
        throw _iteratorError;
        ^

ReferenceError: name is not defined
    at eval (lodash.templateSources[5]:9:10)
    at ConfigPatternCache._eval (/home/mohan/project/vc-portal/node_modules/webpack-config/dist/ConfigPatternCache.js:125:20)
    at ConfigNameResolver.resolve (/home/mohan/project/vc-portal/node_modules/webpack-config/dist/ConfigNameResolver.js:98:32)
    at ConfigOptionsResolver.resolve (/home/mohan/project/vc-portal/node_modules/webpack-config/dist/ConfigOptionsResolver.js:94:45)
    at ConfigMergeCommand.execute (/home/mohan/project/vc-portal/node_modules/webpack-config/dist/ConfigMergeCommand.js:59:46)
    at executeCommand (/home/mohan/project/vc-portal/node_modules/webpack-config/dist/Config.js:89:15)
    at Config.merge (/home/mohan/project/vc-portal/node_modules/webpack-config/dist/Config.js:198:29)
    at Object.<anonymous> (webpack.config.base.js:119:29)
    at Module._compile (module.js:541:32)
    at loader (/home/mohan/project/vc-portal/node_modules/babel-register/lib/node.js:148:5)
    at Object.require.extensions.(anonymous function) [as .js] (/home/mohan/project/vc-portal/node_modules/babel-register/lib/node.js:158:7)

@vanthiyathevan Please look at changelog.

@vanthiyathevan I'm sorry, but you need to do some migration steps.

@vanthiyathevan Could you please share your config if it is possible?

@mdreizin Thanks for the quick response.
I've already made the migration step changes. This works in v6.0.0.
node -v v6.3.0

here are the config files

@vanthiyathevan Thanks a lot. I have just commented gist.

@vanthiyathevan I have reproduced locally. Working on fix.

@vanthiyathevan Thanks again for reporting. Please update to 6.1.2.

@vanthiyathevan https://travis-ci.org/mdreizin/webpack-config/builds/150677104

Thank you for the fast response and fix.

@vanthiyathevan Welcome. 6.1.2 version has been published to npm.
Let me know if it works for you. If everything is ok, please close this issue.

Installed 6.1.2 and its working.


Add Replace_Dots option to fluent-bit elasticsearch output

This addresses https://github.com/fluent/fluent-bit/issues/854.
Make 'Replace_Dots' settable for fluent-bit elasticsearch
output, and default to 'On'.
Signed-off-by: Don Bowman<EMAIL_ADDRESS>
What this PR does / why we need it:
Elasticsearch does not allow a leaf to be both 'text' and 'object'. In Kubernetes, labels + annotations can be of the format 'app' or 'app.kubernetes.io/foo', which confuses it. Fluent-bit has an option 'Replace_Dots' which should be settable (and default on).
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

https://github.com/fluent/fluent-bit/issues/854
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x ] DCO signed
[ x] Chart Version bumped
[x ] Variables are documented in the README.md

/lgtm

/ok-to-test

please bump chart version to 0.13.2

/lgtm

/assign @foxish

/assign @davidkarlsen

is there anything more I need to do here? This is the 2nd time now i'll have to update the version to avoid conflict on merge

is there anything more I need to do here?

@rimusz i need the /lgtm etc again since after bumping the chart version to match master it shows as a change.

coming back to this, @rimusz @davidkarlsen @foxish I'm not sure what more is needed from me.
The workflow removed the /lgtm when I rebased to get the Chart version bump.

ping? hello?
What more is needed from me?

lgtm

I believe https://github.com/helm/charts/pull/9008 incorporates this, closing.


Cannot Import name 'render_stacktrace' from 'debug_toolbar.utils'

from debug_toolbar.utils import render_stacktrace

ImportError: cannot import name 'render_stacktrace' from 'debug_toolbar.utils' (/Users/venv/lib/python3.9/site-packages/debug_toolbar/utils.py)
Having the following issue:
ORM: tortoise
DB: postgresql
python version: 3.9
fastapi  0.104.0

Hey @Anihouvi , there is no render_stacktrace import here, maybe you installed a Django debug toolbar version.
I close the issue, if you have any questions please let me know.


Unnecessary trailing separator in contextual menu

The contextual menu of the main editor view on Linux/Ubuntu contains an unnecessary separator at the end of the list items as outlined by the following red arrow:

This bar is not present in others menu so it would be better to remove it here for consistency.
On the implementation side, I imagine the drawer could merge two consecutive separators and remove a separator on the first or the last position, ie removing separators that define empty sections.

This is a duplicate of #5390 - feel free to subscribe there for updates.


[Feature Request] Allow same icon for all folders and files of those without an icon

Please allow to change all icons with the same icon.
Allow all remaining files without an icon to have same icon change.
allow files to have all same icon feature separate from folders.

This would be a great update !

Issue is implemented with release 1.0.4


[🐛 Bug]:  favicon.ico.func were not configured to run with the Edge Runtime

next-on-pages environment related information
⚡ @cloudflare/next-on-pages CLI
⚡ Preparing project for 'npx vercel build'...
⚡ Project ready for 'npx vercel build'...
⚡
⚡ Building project with 'npx vercel build'...
▲ Vercel CLI 28.20.0
▲ WARNING: You should not upload the .next directory.
▲ Installing dependencies...
▲ up to date in 2s
▲
▲ 10 packages are looking for funding
▲ run npm fund for details
▲ Detected Next.js version: 13.4.2
▲ Detected package-lock.json generated by npm 7+...
▲ Running "npm run build"
▲ ><EMAIL_ADDRESS>build
▲ > next build
▲ - info Loaded env from /home/zizifn/github/myTrash/.env.local
▲ - warn You have enabled experimental feature (serverActions) in next.config.js.
▲ - warn Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
▲ - info Creating an optimized production build...
▲ - info Compiled successfully
▲ - info Linting and checking validity of types...
▲ ./src/app/nav-bar.tsx
▲ 21:19  Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲ 26:19  Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲ 69:23  Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲ 178:19  Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲
▲ ./src/components/client-redirect.tsx
▲ 14:6  Warning: React Hook useEffect has a missing dependency: 'push'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
▲
▲ info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
▲ - info Collecting page data...
▲ - info Generating static pages (0/3)
▲ - info Generating static pages (3/3)
▲ - info Finalizing page optimization...
▲
▲ Route (app)                                Size     First Load JS
▲ ┌ ℇ /                                      4.85 kB        84.3 kB
▲ ├ ℇ /actions                               144 B          79.5 kB
▲ ├ ℇ /api/hello                             0 B                0 B
▲ ├ ℇ /api/login                             0 B                0 B
▲ ├ ℇ /api/mock/d1                           0 B                0 B
▲ ├ ℇ /api/mock/kv                           0 B                0 B
▲ ├ ℇ /api/vpn/[type]/[uuid]                 0 B                0 B
▲ ├ ℇ /api/ws                                0 B                0 B
▲ ├ ○ /favicon.ico                           0 B                0 B
▲ ├ ℇ /pg-nextjs/clientsearch                903 B          80.3 kB
▲ ├ ℇ /pg-nextjs/serversearch                905 B          80.3 kB
▲ ├ ℇ /playground                            1.29 kB        91.2 kB
▲ └ ℇ /vpn                                   144 B          79.5 kB
▲ + First Load JS shared by all              79.4 kB
▲ ├ chunks/474-43d4723ec0a94de2.js         24.8 kB
▲ ├ chunks/b7dfe19b-f50f98df0e92e975.js    52.7 kB
▲ ├ chunks/main-app-43de51b9b51a236b.js    210 B
▲ └ chunks/webpack-8c83a44ea16bce0b.js     1.71 kB
▲
▲ Route (pages)                              Size     First Load JS
▲ ─ ○ /404                                   179 B          88.4 kB
▲ + First Load JS shared by all              88.2 kB
▲ ├ chunks/main-6da9f4eb766771ef.js        86.3 kB
▲ ├ chunks/pages/_app-c717e47bb95cec4a.js  192 B
▲ └ chunks/webpack-8c83a44ea16bce0b.js     1.71 kB
▲ ℇ  (Streaming)  server-side renders with streaming (uses React 18 SSR streaming or Server Components)
▲ ○  (Static)     automatically rendered as static HTML (uses no initial props)
▲ Traced Next.js server files in: 2.722s
▲ Created all serverless functions in: 3.489s
▲ Collected static files (public/, static/, .next/static): 5.92ms
▲ Build Completed in .vercel/output [26s]
⚡ Completed npx vercel build.
⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡
⚡ The following functions were not configured to run with the Edge Runtime:
⚡  - favicon.ico.func
⚡
⚡ If this is a Next.js project:
⚡
⚡ - you can read more about configuring Edge API Routes here: https://nextjs.org/docs/api-routes/edge-api-route
⚡
⚡ - you can try enabling the Edge Runtime for a specific page by exporting the following from your page:
⚡
⚡         export const config = { runtime: 'edge' };
⚡
⚡ - or you can try enabling the Edge Runtime for all pages in your project by adding the following to your 'next.config.js' file:
⚡
⚡         const nextConfig = { experimental: { runtime: 'edge'} };
⚡
⚡ You can read more about the Edge Runtime here: https://nextjs.org/docs/advanced-features/react-18/switchable-runtime
Description
I think something wrong with the new prerelease build(0.0.0-c70151d) with nextjs 13.4 for favicon.ico.func? There is no way to setup export const runtime = "edge"; for favicon..
Reproduction
I think any project with a prerelease build with nextjs 13.4 can reproduction this. If not, you can use my repo https://github.com/zizifn/myTrash
Pages Deployment Method
Pages CI (GitHub/GitLab integration)
Pages Deployment ID
da22e8f7-04f8-4568-9924-e48f213d7d2b
Additional Information
No response
Would you like to help?

[ ] Would you like to help fixing this bug?

Hi @zizifn thank you very much for the issue :slightly_smiling_face:
This is a known issue and we do have this function that should address it :confused:
https://github.com/cloudflare/next-on-pages/blob/c70151dcbfa4bb7886884364fc98e4d696285278/src/buildApplication/generateFunctionsMap.ts#L432
Something might have changed and caused the function not to get run anymore or not fix the issue :sweat:
I'll have a look :+1:

Hi @zizifn thank you very much for the issue 🙂
This is a known issue and we do have this function that should address it 😕
https://github.com/cloudflare/next-on-pages/blob/c70151dcbfa4bb7886884364fc98e4d696285278/src/buildApplication/generateFunctionsMap.ts#L432
Something might have changed and caused the function not to get run anymore or not fix the issue 😓 I'll have a look 👍

Thanks!! If I remove the app/favicon.ico, the "node:buffer" error is showing up..
⚡ @cloudflare/next-on-pages CLI
⚡ Preparing project for 'npx vercel build'...
⚡ Project ready for 'npx vercel build'...
⚡
⚡ Building project with 'npx vercel build'...
▲ Vercel CLI 28.20.0
▲ WARNING: You should not upload the `.next` directory.
▲ Installing dependencies...
▲ up to date in 1s
▲
▲ 10 packages are looking for funding
▲ run `npm fund` for details
▲ Detected Next.js version: 13.4.2
▲ Detected `package-lock.json` generated by npm 7+...
▲ Running "npm run build"
▲ ><EMAIL_ADDRESS>build
▲ > next build
▲ - info Loaded env from /home/zizifn/github/myTrash/.env.local
▲ - warn You have enabled experimental feature (serverActions) in next.config.js.
▲ - warn Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
▲ - info Creating an optimized production build...
▲ - info Compiled successfully
▲ - info Linting and checking validity of types...
▲ ./src/app/nav-bar.tsx
▲ 21:19  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲ 26:19  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲ 69:23  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲ 178:19  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
▲
▲ ./src/components/client-redirect.tsx
▲ 14:6  Warning: React Hook useEffect has a missing dependency: 'push'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
▲
▲ info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
▲ - info Collecting page data...
▲ - info Generating static pages (0/2)
▲ - info Generating static pages (2/2)
▲ - info Finalizing page optimization...
▲
▲ Route (app)                                Size     First Load JS
▲ ┌ ℇ /                                      4.85 kB        84.3 kB
▲ ├ ℇ /actions                               144 B          79.5 kB
▲ ├ ℇ /api/hello                             0 B                0 B
▲ ├ ℇ /api/login                             0 B                0 B
▲ ├ ℇ /api/mock/d1                           0 B                0 B
▲ ├ ℇ /api/mock/kv                           0 B                0 B
▲ ├ ℇ /api/vpn/[type]/[uuid]                 0 B                0 B
▲ ├ ℇ /api/ws                                0 B                0 B
▲ ├ ℇ /pg-nextjs/clientsearch                903 B          80.3 kB
▲ ├ ℇ /pg-nextjs/serversearch                905 B          80.3 kB
▲ ├ ℇ /playground                            1.29 kB        91.2 kB
▲ └ ℇ /vpn                                   144 B          79.5 kB
▲ + First Load JS shared by all              79.4 kB
▲ ├ chunks/474-43d4723ec0a94de2.js         24.8 kB
▲ ├ chunks/b7dfe19b-f50f98df0e92e975.js    52.7 kB
▲ ├ chunks/main-app-43de51b9b51a236b.js    210 B
▲ └ chunks/webpack-8c83a44ea16bce0b.js     1.71 kB
▲
▲ Route (pages)                              Size     First Load JS
▲ ─ ○ /404                                   179 B          88.4 kB
▲ + First Load JS shared by all              88.2 kB
▲ ├ chunks/main-37314a856a39015a.js        86.3 kB
▲ ├ chunks/pages/_app-c717e47bb95cec4a.js  192 B
▲ └ chunks/webpack-8c83a44ea16bce0b.js     1.71 kB
▲ ℇ  (Streaming)  server-side renders with streaming (uses React 18 SSR streaming or Server Components)
▲ ○  (Static)     automatically rendered as static HTML (uses no initial props)
▲ Traced Next.js server files in: 2.956s
▲ Created all serverless functions in: 3.079s
▲ Collected static files (public/, static/, .next/static): 8.473ms
▲ Build Completed in .vercel/output [21s]
⚡ Completed `npx vercel build`.
✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/api/mock/kv.func.js:188:108:
      188 │ ...{6195:e=>{"use strict";e.exports=require("node:buffer")},75:(e,t,r)=>{"use strict";r.r(t),r.d(...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/api/mock/d1.func.js:188:108:
      188 │ ...{6195:e=>{"use strict";e.exports=require("node:buffer")},6944:(e,t,r)=>{"use strict";r.r(t),r....
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/api/hello.func.js:188:108:
      188 │ ...{6195:e=>{"use strict";e.exports=require("node:buffer")},1881:(e,t,r)=>{"use strict";r.r(t),r....
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/api/ws.func.js:188:108:
      188 │ ...{6195:e=>{"use strict";e.exports=require("node:buffer")},1615:(e,t,r)=>{"use strict";r.r(t),r....
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/api/login.func.js:188:108:
      188 │ ...{6195:e=>{"use strict";e.exports=require("node:buffer")},8103:(e,t,r)=>{"use strict";r.r(t),r....
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/api/vpn/[type]/[uuid].func.js:188:108:
      188 │ ...{6195:e=>{"use strict";e.exports=require("node:buffer")},9248:(e,t,r)=>{"use strict";r.r(t),r....
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/vpn.func.js:191:143:
      191 │ ...,6195:e=>{"use strict";e.exports=require("node:buffer")},6501:(e,t,r)=>{let n=r(9089);function...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/actions.func.js:191:144:
      191 │ ...,6195:e=>{"use strict";e.exports=require("node:buffer")},6501:(e,t,r)=>{let n=r(9089);function...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/pg-nextjs/serversearch.func.js:191:144:
      191 │ ...,6195:e=>{"use strict";e.exports=require("node:buffer")},6501:(e,t,r)=>{let n=r(9089);function...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/index.func.js:191:144:
      191 │ ...,6195:e=>{"use strict";e.exports=require("node:buffer")},6501:(e,t,r)=>{let n=r(9089);function...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/pg-nextjs/clientsearch.func.js:191:144:
      191 │ ...,6195:e=>{"use strict";e.exports=require("node:buffer")},6501:(e,t,r)=>{let n=r(9089);function...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "node:buffer"

    ../../../../tmp/r5bvbfbpgos/playground.func.js:191:144:
      191 │ ...,6195:e=>{"use strict";e.exports=require("node:buffer")},724:(e,t,r)=>{let n=r(9089);function ...
          ╵                                             ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

/home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:1575
  let error = new Error(`${text}${summary}`);
              ^

Error: Build failed with 12 errors:
../../../../tmp/r5bvbfbpgos/actions.func.js:191:144: ERROR: Could not resolve "node:buffer"
../../../../tmp/r5bvbfbpgos/api/hello.func.js:188:108: ERROR: Could not resolve "node:buffer"
../../../../tmp/r5bvbfbpgos/api/login.func.js:188:108: ERROR: Could not resolve "node:buffer"
../../../../tmp/r5bvbfbpgos/api/mock/d1.func.js:188:108: ERROR: Could not resolve "node:buffer"
../../../../tmp/r5bvbfbpgos/api/mock/kv.func.js:188:108: ERROR: Could not resolve "node:buffer"
...
    at failureErrorWithLog (/home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:1575:15)
    at /home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:1033:28
    at /home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:978:67
    at buildResponseToResult (/home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:1031:7)
    at /home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:1143:14
    at responseCallbacks.<computed> (/home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:680:9)
    at handleIncomingPacket (/home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:735:9)
    at Socket.readFromStdout (/home/zizifn/github/myTrash/node_modules/esbuild/lib/main.js:656:7)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12) {
  errors: [
    {
      detail: undefined,
      id: '',
      location: {
        column: 144,
        file: '../../../../tmp/r5bvbfbpgos/actions.func.js',

that's strange, that should have been fixed very recently :sweat:
sorry about it, I'll have a look at it as well :sweat:

that's strange, that should have been fixed very recently 😓
sorry about it, I'll have a look at it as well 😓

yeah! I thought "node:buffer" issue should fixed before. But anyway if you want to reproduce, you can use my repo https://github.com/zizifn/myTrash, I removed node_modules and install it again, this issue still can reproduce in my repo.. Maybe I did something wrong, as I upgrade to nextjs 13.4 never success in my local..

Anyway I need to go to sleep, sorry for the report issue on Friday....

Ah no don't worry about the issue on Friday, I'm sorry for the issues you're facing, it seems like this whole last week's been pretty unlucky for next-on-pages 😓

Hey there @zizifn, we just merged a change to how we handle the favicon route that should fix your issue 🙂
I wasn't able to reproduce the node:buffer problem that you were encountering, though. Please can you try out the new beta release?
If the problem is still occurring, I'd appreciate it if you could provide some more information about your environment - does it work when you try building locally?

Hey there @zizifn, we just merged a change to how we handle the favicon route that should fix your issue 🙂
I wasn't able to reproduce the node:buffer problem that you were encountering, though. Please can you try out the new beta release?
If the problem is still occurring, I'd appreciate it if you could provide some more information about your environment - does it work when you try building locally?

building success in my local but deployment failed...
13:28:09.122 | Error: Failed to publish your Function. Got error: Uncaught Error: No such module "opt/buildhome/repo/.vercel/output/static/_worker.js/index.js".   imported from "bundledWorker-0.9571207632339629.mjs"

My Deployment is: ea914075-f432-42db-8ca1-b9b3afe727a8.. BTW, local  wrangler pages dev also have an issue, maybe need wait for wrangler fix https://github.com/cloudflare/workers-sdk/pull/3175

Thanks! Build success in my local, however CI deployment failed...
13:28:09.122 | Error: Failed to publish your Function. Got error: Uncaught Error: No such module "opt/buildhome/repo/.vercel/output/static/_worker.js/index.js".   imported from "bundledWorker-0.9571207632339629.mjs"

Apologies for the late response @zizifn  :(
I have just tried deploying your project using wrangler (npx wrangler pages publish .vercel/output/static/) and had success 😄 - https://ea051d80.nop-issue-237-repro.pages.dev/
Can you try changing the wrangler used in your workflow to the latest version?

Thanks! Build success in my local, however CI deployment failed...
13:28:09.122 | Error: Failed to publish your Function. Got error: Uncaught Error: No such module "opt/buildhome/repo/.vercel/output/static/_worker.js/index.js".   imported from "bundledWorker-0.9571207632339629.mjs"

Apologies for the late response @zizifn :(
I have just tried deploying your project using wrangler (npx wrangler pages publish .vercel/output/static/) and had success 😄 - https://ea051d80.nop-issue-237-repro.pages.dev/
Can you try changing the wrangler used in your workflow to the latest version?

Thanks for check on this. But which wrangler  version you are using, I used "wrangler": "^2.20.0" &  "@cloudflare/next-on-pages": "^0.0.0-8a46b36", and both CI and my local npx wrangler pages publish have the same error.

Thanks for checking this!! I deleted my page project and create a new one... CI deployment is success... No idea why.. But my nextjs on pages is running, will play around...

That's strange... I'm glad to hear your deployment is working now though!

Thanks for checking this!! I deleted my page project and create a new one... CI deployment is success... No idea why.. But my nextjs on pages is running, will play around...

That's strange... I'm glad to hear your deployment is working now though!

I found if I added D1 binding, CI deployment will have below error...
Error: Failed to publish your Function. Got error: Uncaught Error: No such module "opt/buildhome/repo/.vercel/output/static/_worker.js/index.js".
  imported from "bundledWorker-0.9648751693905782.mjs"

@zizifn could you provide more details on how to reproduce the issue? 🙏
Can you reproduce the failure locally? (using this wrangler prerelease https://github.com/cloudflare/workers-sdk/pull/3175#issuecomment-1542910766)

by uncommenting and testing your api/mock/d1 route it looks like d1 is working fine locally? 🤔

(it does error but it's an SQLite error so anyways I believe it shows that d1 is working)

@zizifn could you provide more details on how to reproduce the issue? 🙏
Can you reproduce the failure locally? (using this wrangler prerelease cloudflare/workers-sdk#3175 (comment))

I would say, add D1 binding to any project, this error show in CI deployment. If not, try my project https://github.com/zizifn/myTrash.. In the meanwhile, I will try wrangler prerelease..

@zizifn never mind I got it :+1:

@zizifn never mind, I got it 👍

BTW, deleted D1 binding in the dashboard and changing any file in the repo,  CI deployment will be back to normal.. I tried many times.

It is quite bad that this prevents you from using D1... 😓
However I am pretty sure that this is something that needs to be fixed in wrangler and not next-on-pages (I believe it's caused by a bug in the newly introduced _wrangler.js dir implementation which we use)
It does really limit the use of next-on-pages, I'll try to push for a fix, thanks a lot for reporting this! 🙏

PS: I think we should have a new issue here to keep track of this, please let me know if you want to open it or if you prefer that I do that 🙂

It is quite bad that this prevents you from using D1... 😓
However I am pretty sure that this is something that needs to be fixed in wrangler and not next-on-pages (I believe it's caused by a bug in the newly introduced _wrangler.js dir implementation which we use)
It does really limit the use of next-on-pages, I'll try to push for a fix, thanks a lot for reporting this! 🙏
PS: I think we should have a new issue here to keep track of this, please let me know if you want to open it or if you prefer that I do that 🙂

please do what you think is best, I'm fine.. Just ping me the issue ID, I will watch it.. :)

I'm facing a very similar issue to the favicon error :( , any help is appreciated :D
Build Logs
2024-07-09T17:54:31.726906Z	Cloning repository...
2024-07-09T17:54:32.752713Z	From https://github.com/kofferX/hesperdium
2024-07-09T17:54:32.753265Z	 * branch            b8e6e34a8b192d5e9a3e873ed426838806afe097 -> FETCH_HEAD
2024-07-09T17:54:32.753388Z
2024-07-09T17:54:32.807395Z	HEAD is now at b8e6e34 fix: minor ui scroll bugs
2024-07-09T17:54:32.807883Z
2024-07-09T17:54:32.889942Z
2024-07-09T17:54:32.890433Z	Using v2 root directory strategy
2024-07-09T17:54:32.915195Z	Success: Finished cloning repository files
2024-07-09T17:54:34.529486Z	Checking for configuration in a wrangler.toml configuration file (BETA)
2024-07-09T17:54:34.53021Z
2024-07-09T17:54:34.635822Z	No wrangler.toml file found. Continuing.
2024-07-09T17:54:34.7844Z	Detected the following tools from environment<EMAIL_ADDRESS><EMAIL_ADDRESS>2024-07-09T17:54:35.564829Z	Installing project dependencies: pnpm install
2024-07-09T17:54:36.265844Z	 WARN  Ignoring not compatible lockfile at /opt/buildhome/repo/pnpm-lock.yaml
2024-07-09T17:54:36.444126Z	Progress: resolved 1, reused 0, downloaded 0, added 0
2024-07-09T17:54:37.446894Z	Progress: resolved 30, reused 0, downloaded 26, added 0
2024-07-09T17:54:38.606467Z	Progress: resolved 38, reused 0, downloaded 35, added 0
2024-07-09T17:54:39.129143Z	 WARN  deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
2024-07-09T17:54:39.612893Z	Progress: resolved 107, reused 0, downloaded 93, added 0
2024-07-09T17:54:40.612807Z	Progress: resolved 155, reused 0, downloaded 135, added 0
2024-07-09T17:54:41.621882Z	Progress: resolved 209, reused 0, downloaded 146, added 0
2024-07-09T17:54:42.400445Z	 WARN  deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
2024-07-09T17:54:42.621835Z	Progress: resolved 286, reused 0, downloaded 217, added 0
2024-07-09T17:54:43.399564Z	 WARN  deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
2024-07-09T17:54:43.674294Z	Progress: resolved 408, reused 0, downloaded 336, added 0
2024-07-09T17:54:43.9993Z	 WARN  deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
2024-07-09T17:54:44.365055Z	 WARN  deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
2024-07-09T17:54:44.635045Z	Packages: +487
2024-07-09T17:54:44.635274Z	++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2024-07-09T17:54:44.673697Z	Progress: resolved 532, reused 0, downloaded 468, added 0
2024-07-09T17:54:45.674124Z	Progress: resolved 532, reused 0, downloaded 468, added 458
2024-07-09T17:54:46.471845Z	Progress: resolved 532, reused 0, downloaded 487, added 487, done
2024-07-09T17:54:46.61968Z<EMAIL_ADDRESS>postinstall$ node install.js
2024-07-09T17:54:46.827913Z<EMAIL_ADDRESS>postinstall: Done
2024-07-09T17:54:46.895252Z<EMAIL_ADDRESS>install$ node install/check
2024-07-09T17:54:47.030849Z<EMAIL_ADDRESS>install: Done
2024-07-09T17:54:47.549679Z
2024-07-09T17:54:47.54991Z	dependencies:
2024-07-09T17:54:47.550042Z	+ @figma/eslint-plugin-figma-plugins 0.15.0
2024-07-09T17:54:47.550224Z	+ @figma/plugin-typings 1.97.0
2024-07-09T17:54:47.550301Z	+ @hookform/resolvers 3.9.0
2024-07-09T17:54:47.550803Z	+ @icons-pack/react-simple-icons 9.6.0
2024-07-09T17:54:47.551034Z	+ @next/bundle-analyzer 14.2.4
2024-07-09T17:54:47.551117Z	+ @radix-ui/react-avatar 1.1.0
2024-07-09T17:54:47.551266Z	+ @radix-ui/react-checkbox 1.1.1
2024-07-09T17:54:47.551342Z	+ @radix-ui/react-dialog 1.1.1
2024-07-09T17:54:47.551443Z	+ @radix-ui/react-icons 1.3.0
2024-07-09T17:54:47.551552Z	+ @radix-ui/react-label 2.1.0
2024-07-09T17:54:47.551649Z	+ @radix-ui/react-popover 1.1.1
2024-07-09T17:54:47.551734Z	+ @radix-ui/react-select 2.1.1
2024-07-09T17:54:47.551841Z	+ @radix-ui/react-slot 1.1.0
2024-07-09T17:54:47.551957Z	+ @typescript-eslint/parser 7.16.0
2024-07-09T17:54:47.552059Z	+ class-variance-authority 0.7.0
2024-07-09T17:54:47.55216Z	+ clsx 2.1.1
2024-07-09T17:54:47.552266Z	+ cmdk 1.0.0
2024-07-09T17:54:47.552366Z	+ esbuild 0.21.5 (0.23.0 is available)
2024-07-09T17:54:47.552483Z	+ framer-motion 11.2.14
2024-07-09T17:54:47.552615Z	+ lucide-react 0.396.0 (0.406.0 is available)
2024-07-09T17:54:47.552731Z	+ next 14.2.4
2024-07-09T17:54:47.552849Z	+ react 18.3.1
2024-07-09T17:54:47.552947Z	+ react-dom 18.3.1
2024-07-09T17:54:47.553136Z	+ react-hook-form 7.52.1
2024-07-09T17:54:47.553244Z	+ sharp 0.33.4
2024-07-09T17:54:47.553411Z	+ tailwind-merge 2.4.0
2024-07-09T17:54:47.553524Z	+ tailwindcss-animate 1.0.7
2024-07-09T17:54:47.553604Z	+ vaul 0.9.1
2024-07-09T17:54:47.553721Z	+ zod 3.23.8
2024-07-09T17:54:47.553857Z
2024-07-09T17:54:47.55396Z	devDependencies:
2024-07-09T17:54:47.554093Z	+ @types/node 20.4.2 (20.14.10 is available)
2024-07-09T17:54:47.554223Z	+ @types/react 18.3.3
2024-07-09T17:54:47.554365Z	+ @types/react-dom 18.3.0
2024-07-09T17:54:47.554482Z	+ concurrently 8.2.2
2024-07-09T17:54:47.554607Z	+ eslint 8.57.0 (9.6.0 is available)
2024-07-09T17:54:47.554751Z	+ eslint-config-next 14.2.4
2024-07-09T17:54:47.554879Z	+ postcss 8.4.39
2024-07-09T17:54:47.555049Z	+ tailwindcss 3.4.4
2024-07-09T17:54:47.555154Z	+ typescript 5.5.3
2024-07-09T17:54:47.555241Z
2024-07-09T17:54:47.555345Z	Done in 11.6s
2024-07-09T17:54:47.732999Z	Executing user command: npx @cloudflare/next-on-pages@1
2024-07-09T17:54:50.455438Z	npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>2024-07-09T17:54:56.259151Z	npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
2024-07-09T17:54:56.387199Z	npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
2024-07-09T17:54:56.784693Z	npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
2024-07-09T17:54:56.832277Z	npm WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
2024-07-09T17:54:56.96782Z	npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
2024-07-09T17:54:57.023639Z	npm WARN deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
2024-07-09T17:54:57.041589Z	npm WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
2024-07-09T17:54:57.073774Z	npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
2024-07-09T17:54:57.427426Z	npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2024-07-09T17:54:57.726545Z	npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
2024-07-09T17:55:01.763416Z	⚡ @cloudflare/next-on-pages CLI v.1.12.0
2024-07-09T17:55:02.143712Z	⚡ Detected Package Manager: npm (9.6.7)
2024-07-09T17:55:02.144178Z	⚡ Preparing project...
2024-07-09T17:55:02.144386Z
2024-07-09T17:55:02.144514Z	⚡ The project is set up for pnpm but it is currently being run via npm this might lead to build errors, please be sure to use the same package manager your project uses when running @cloudflare/next-on-pages
2024-07-09T17:55:02.144671Z
2024-07-09T17:55:02.1474Z	⚡ Project is ready
2024-07-09T17:55:02.147666Z	⚡ Building project...
2024-07-09T17:55:04.234195Z	▲  npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>2024-07-09T17:55:08.40193Z	▲  npm
2024-07-09T17:55:08.402224Z	▲  WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
2024-07-09T17:55:08.443094Z	▲  npm
2024-07-09T17:55:08.443301Z	▲  WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
2024-07-09T17:55:08.476805Z	▲  npm
2024-07-09T17:55:08.477146Z	▲  WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
2024-07-09T17:55:08.648247Z	▲  npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
2024-07-09T17:55:08.659454Z	▲  npm WARN deprecated
2024-07-09T17:55:08.659689Z	▲<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
2024-07-09T17:55:08.706251Z	▲  npm WARN deprecated
2024-07-09T17:55:08.706511Z	▲<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
2024-07-09T17:55:08.727214Z	▲  npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
2024-07-09T17:55:08.74896Z	▲  npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2024-07-09T17:55:09.895516Z	▲  Vercel CLI 34.3.1
2024-07-09T17:55:10.232059Z	▲  Detected `pnpm-lock.yaml` version 6 generated by pnpm 8
2024-07-09T17:55:10.247432Z	▲  Installing dependencies...
2024-07-09T17:55:10.759445Z	▲  Lockfile is up to date, resolution step is skipped
2024-07-09T17:55:10.840221Z	▲  Already up to date
2024-07-09T17:55:11.183717Z	▲
2024-07-09T17:55:11.293025Z	▲  Done in 920ms
2024-07-09T17:55:11.319759Z	▲  Detected Next.js version: 14.2.4
2024-07-09T17:55:11.331144Z	▲  Running "pnpm run vercel-build"
2024-07-09T17:55:11.784558Z	▲  ><EMAIL_ADDRESS>vercel-build /opt/buildhome/repo
2024-07-09T17:55:11.784852Z	▲  > concurrently -n plugin,next 'npm run build:plugin -- --define:SITE_URL=\"https://splugin.kofferx.com\"' 'next build'
2024-07-09T17:55:12.506134Z	▲  [plugin]
2024-07-09T17:55:12.506964Z	▲  [plugin] ><EMAIL_ADDRESS>build:plugin
2024-07-09T17:55:12.507129Z	▲  [plugin] > esbuild plugin/code.ts --bundle --target=es6 --loader:.svg=text --outfile=plugin/dist/code.js --define:SITE_URL="https://splugin.kofferx.com"
2024-07-09T17:55:12.507697Z	▲  [plugin]
2024-07-09T17:55:12.557103Z	▲  [plugin]
2024-07-09T17:55:12.557872Z	▲  [plugin]   plugin/dist/code.js  3.0kb
2024-07-09T17:55:12.558037Z	▲  [plugin]
2024-07-09T17:55:12.558159Z	▲  [plugin] ⚡ Done in 3ms
2024-07-09T17:55:12.568496Z	▲  [plugin] npm run build:plugin -- --define:SITE_URL=\"https://splugin.kofferx.com\" exited with code 0
2024-07-09T17:55:12.853472Z	▲  [next] Attention: Next.js now collects completely anonymous telemetry regarding usage.
2024-07-09T17:55:12.853776Z	▲  [next]
2024-07-09T17:55:12.854099Z	▲  This information is used to shape Next.js' roadmap and prioritize features.
2024-07-09T17:55:12.854228Z	▲  [next] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2024-07-09T17:55:12.854797Z	▲  [next] https://nextjs.org/telemetry
2024-07-09T17:55:12.85499Z	▲  [next]
2024-07-09T17:55:12.924347Z	▲  [next]   ▲ Next.js 14.2.4
2024-07-09T17:55:12.924741Z	▲  [next]
2024-07-09T17:55:12.983365Z	▲  [next]    Creating an optimized production build ...
2024-07-09T17:55:40.915387Z	▲  [next]
2024-07-09T17:55:40.915705Z	▲  ✓ Compiled successfully
2024-07-09T17:55:40.916988Z	▲  [next]    Linting and checking validity of types ...
2024-07-09T17:55:48.113619Z	▲  [next]
2024-07-09T17:55:48.113882Z	▲  [next] ./src/app/dashboard/page.tsx
2024-07-09T17:55:48.114228Z	▲  [next] 65:6  Warning: React Hook useEffect has missing dependencies: 'fetchLibrary' and 'storeLocalStorage'. Either include them or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.114595Z	▲  [next] 192:6  Warning: React Hook useEffect has missing dependencies: 'backendApi', 'router', 'searchParams', 'subscriber', and 'workspaceChangeCallback'. Either include them or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.11489Z	▲  [next]
2024-07-09T17:55:48.114974Z	▲  [next] ./src/app/onboarding/page.tsx
2024-07-09T17:55:48.115034Z	▲  [next] 91:6  Warning: React Hook useEffect has a missing dependency: 'backendApi'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.115159Z	▲  [next] 193:6  Warning: React Hook useEffect has missing dependencies: 'createProjectRequest' and 'selectProjectAndContinue'. Either include them or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.115231Z	▲  [next]
2024-07-09T17:55:48.115287Z	▲  [next] ./src/app/page.tsx
2024-07-09T17:55:48.115347Z	▲  [next] 50:6  Warning: React Hook useEffect has a missing dependency: 'router'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.115459Z	▲  [next]
2024-07-09T17:55:48.115575Z	▲  [next] ./src/components/uploadAsset.tsx
2024-07-09T17:55:48.11567Z	▲  [next] 120:6  Warning: React Hook React.useEffect has a missing dependency: 'form'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.115771Z	▲  [next] 320:6  Warning: React Hook React.useEffect has a missing dependency: 'onChange'. Either include it or remove the dependency array. If 'onChange' changes too often, find the parent component that defines it and wrap that definition in useCallback.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.115868Z	▲  [next] 673:6  Warning: React Hook React.useEffect has missing dependencies: 'backendApi' and 'projectId'. Either include them or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.115969Z	▲  [next] 677:6  Warning: React Hook React.useEffect has a missing dependency: 'nodeProperties'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
2024-07-09T17:55:48.116157Z	▲  [next]
2024-07-09T17:55:48.116254Z	▲  [next] info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
2024-07-09T17:55:48.643819Z	▲  [next]    Collecting page data ...
2024-07-09T17:55:50.606019Z	▲  [next]    Generating static pages (0/8) ...
2024-07-09T17:55:50.927662Z	▲  [next]    Generating static pages (2/8)
2024-07-09T17:55:50.92791Z	▲  [next]    Generating static pages (4/8)
2024-07-09T17:55:51.278673Z	▲  [next]    Generating static pages (6/8)
2024-07-09T17:55:51.313598Z	▲  [next]  ✓ Generating static pages (8/8)
2024-07-09T17:55:51.746121Z	▲  [next]    Finalizing page optimization ...
2024-07-09T17:55:51.746407Z	▲  [next]    Collecting build traces ...
2024-07-09T17:55:56.425032Z	▲  [next]
2024-07-09T17:55:56.434661Z	▲  [next] Route (app)                              Size     First Load JS
2024-07-09T17:55:56.434876Z	▲  [next] ┌ ○ /                                    2.32 kB         130 kB
2024-07-09T17:55:56.435001Z	▲  [next] ├ ○ /_not-found                          873 B          87.9 kB
2024-07-09T17:55:56.435119Z	▲  [next] ├ ○ /auth                                2.83 kB         103 kB
2024-07-09T17:55:56.435248Z	▲  [next] ├ ○ /dashboard                           65.2 kB         223 kB
2024-07-09T17:55:56.43534Z	▲  [next] └ ○ /onboarding                          3.69 kB         162 kB
2024-07-09T17:55:56.435449Z	▲  [next] + First Load JS shared by all            87.1 kB
2024-07-09T17:55:56.435529Z	▲  [next]   ├ chunks/733-2a4bbb32379d005d.js       31.5 kB
2024-07-09T17:55:56.435624Z	▲  [next]   ├ chunks/c7bb1776-523895ddb7a4b478.js  53.7 kB
2024-07-09T17:55:56.435753Z	▲  [next]   └ other shared chunks (total)          1.89 kB
2024-07-09T17:55:56.435858Z	▲  [next]
2024-07-09T17:55:56.435967Z	▲  [next]
2024-07-09T17:55:56.436091Z	▲  [next] ○  (Static)  prerendered as static content
2024-07-09T17:55:56.43618Z	▲  [next]
2024-07-09T17:55:56.453608Z	▲  [next] next build exited with code 0
2024-07-09T17:55:56.840372Z	▲  Traced Next.js server files in: 334.144ms
2024-07-09T17:55:56.931394Z	▲  Created all serverless functions in: 90.732ms
2024-07-09T17:55:56.942113Z	▲  Collected static files (public/, static/, .next/static): 6.716ms
2024-07-09T17:55:56.989686Z	▲  Build Completed in .vercel/output [47s]
2024-07-09T17:55:57.074731Z	⚡ Completed `npx vercel build`.
2024-07-09T17:55:59.254273Z
2024-07-09T17:55:59.254578Z	⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
2024-07-09T17:55:59.254716Z	⚡
2024-07-09T17:55:59.255219Z	⚡ 	The following routes were not configured to run with the Edge Runtime:
2024-07-09T17:55:59.255357Z	⚡ 	  - /favicon.ico
2024-07-09T17:55:59.255479Z	⚡
2024-07-09T17:55:59.255558Z	⚡ 	Please make sure that all your non-static routes export the following edge runtime route segment config:
2024-07-09T17:55:59.255636Z	⚡ 	  export const runtime = 'edge';
2024-07-09T17:55:59.255713Z	⚡
2024-07-09T17:55:59.255786Z	⚡ 	You can read more about the Edge Runtime on the Next.js documentation:
2024-07-09T17:55:59.25587Z	⚡ 	  https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
2024-07-09T17:55:59.255933Z
2024-07-09T17:55:59.289276Z	Failed: Error while executing user command. Exited with error code: 1
2024-07-09T17:55:59.326519Z	Failed: build command exited with code: 1
2024-07-09T17:56:00.310839Z	Failed: error occurred while running build command

Pages Deployment Method
Pages CI (GitHub/GitLab integration)
Pages Deployment ID
2edf7588-7077-4078-b9b6-a103cbe20d2a

I have the same issue as @DarthBenro008 and it only started happening a few hours ago. It wasn't happening before. This is especially strange since there's no new versions of @cloudflare/next-on-pages: https://www.npmjs.com/package/@cloudflare/next-on-pages?activeTab=versions.

@DarthBenro008 there's another issue for this already: https://github.com/cloudflare/next-on-pages/issues/825. Looks like it's related to a vercel CLI package release.


[Bug]: AppSmith consumes {{}} when it should not

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
AppSmith is consuming {{value}} when it should not. I expect AppSmith to not consume {{value}} when it is an input value for an input field.
Steps To Reproduce

Create an input
Input example: SubjectInput Text: HL7 Result: CODE 5 - CRITICAL VALUE - {{institution}} {{accessionNumber}}
Create backend API that accepts JSON
Create an API query that sends JSON data to the backend API.
Example  - The subject and body are Handlebars templates and should have {{values}}{
  name: "{{NameInput.text}}",
  description: "{{DescriptionInput.text}}",
  from: "{{FromInput.text}}",
  to: "{{ToInput.text}}",
  cc: "{{CCInput.text}}",
  bcc: "{{BCCInput.text}}",
  subject: "{{SubjectInput.text}}",
  body: "{{BodyInput.text}}",
  templateMessageExample: {{JSON.parse(SampleMessageInput.text)}},
  rule: {{JSON.parse(RuleInput.text)}},
}

The AppSmith API Query Evaluated Value will correctly show the {{value}} but when the server receives the post request the {{values}} are replaced with null

As a work around I am doing the following body: "{{BodyInput.text.replace(/{/g, '@').replace(/}/g, '#')}}",
Environment
Production
Version
Self-Hosted

Also related to #7346. I'm closing those in favor of this


Update docs version

The v0.1.0  was missing on the table. This follows the approach used by the Tekton folks, see https://github.com/tektoncd/pipeline/tree/v0.16.2#read-the-docs

/lgtm
/approve


Throw SparkDateTimeException for InvalidInput while casting in ANSI mode [databricks]

This fixes https://github.com/NVIDIA/spark-rapids/issues/5719 .
Spark updated the error message to throw SparkDateTimeException in this PR: https://github.com/apache/spark/pull/36591 .
Since SparkDateTimeException is a private class in org.apache.spark, I have included TrampolineUtil to call that Exception.
Current integration test passes now. No new test required.

build

build

what does the full error message look like now from us?

With the latest commit, the error message looks like this:
Input: Nan
 org.apache.spark.SparkDateTimeException: The value NaN of the type DOUBLE cannot be cast to TIMESTAMP because it is malformed. Correct the value as per the syntax, or change its target type. To return NULL instead, use `try_cast`. If necessary set spark.sql.ansi.enabled to "false" to bypass this error.
Spark's error message:
org.apache.spark.SparkDateTimeException: The value NaN of the type "DOUBLE" cannot be cast to "TIMESTAMP" because it is malformed. Correct the value as per the syntax, or change its target type. To return NULL instead, use `try_cast`. If necessary set "spark.sql.ansi.enabled" to "false" to bypass this erro
Input: +Infinity/ -Infinity.
We are throwing same error message for both positive and negative infinity where as Spark differentiates between those.
org.apache.spark.SparkDateTimeException: The value Infinity of the type DOUBLE cannot be cast to TIMESTAMP because it is malformed. Correct the value as per the syntax, or change its target type. To return NULL instead, use `try_cast`. If necessary set spark.sql.ansi.enabled to "false" to bypass this error.

build

Build failure is due to #5744

build


Missing parameters for Scripted installation

Hi
it seems that the documentation explaining how to script the isntallation of ConfigMgr (here) is missing some sections .
I generated an Ini file based on a Graphical step by step installation process, and found the following sections from which I cannot seem to find the help sections related:
[SystemCenterOptions]
SysCenterId=
[SABranchOptions]
SAActive=1
CurrentBranch=1
If theses are documented somewhere else, it would either make sense to move them in here, or at least provide a link to their actual location to have a centralized entry point when it comes to scripting the installation of ConfigMgr.
Can someone add a short explanation on these different options and effects they have on the installation.
Thanks in advance!

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

ID: 5a393419-2d34-ebba-9482-7c988797f5c9
Version Independent ID: 95f509c1-5494-7f40-6392-6f7f8988dd2e
Content: Setup command-line options - Configuration Manager
Content Source: sccm/core/servers/deploy/install/command-line-options-for-setup.md
Service: unspecified
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @Stephanevg for reporting this. I filed doc bug 509715 to investigate with the feature team. I know there were changes to setup in the past year or so to prompt for Software Assurance and other licensing aspects, so suspect these are related.

Great!
I am happy to see this is getting forward. (Even though it really feels a bit long).

I made changes to this article to address this issue, it will publish live later today.