sys/android: several ion ioctl commands failed

Hi, I just want to test the ion.txt in sys/android. https://github.com/google/syzkaller/blob/master/sys/android/ion.txt
However, when syz-manager running, I found that several ion ioctls commands not run because resource "ion_handle" is not created.
2019/05/07 10:00:08 transitively unsupported: ioctl$ION_IOC_IMPORT: no syscalls can create resource ion_handle, enable some syscalls that can create it [ioctl$ION_IOC_ALLOC ioctl$ION_IOC_IMPORT ioctl$ION_IOC_MAP ioctl$ION_IOC_SHARE ioctl$ION_IOC_SYNC]
2019/05/07 10:00:08 transitively unsupported: ioctl$ION_IOC_MAP: no syscalls can create resource ion_handle, enable some syscalls that can create it [ioctl$ION_IOC_ALLOC ioctl$ION_IOC_IMPORT ioctl$ION_IOC_MAP ioctl$ION_IOC_SHARE ioctl$ION_IOC_SYNC]
2019/05/07 10:00:08 transitively unsupported: ioctl$ION_IOC_ALLOC: no syscalls can create resource ion_handle, enable some syscalls that can create it [ioctl$ION_IOC_ALLOC ioctl$ION_IOC_IMPORT ioctl$ION_IOC_MAP ioctl$ION_IOC_SHARE ioctl$ION_IOC_SYNC]
2019/05/07 10:00:08 transitively unsupported: ioctl$ION_IOC_FREE: no syscalls can create resource ion_handle, enable some syscalls that can create it [ioctl$ION_IOC_ALLOC ioctl$ION_IOC_IMPORT ioctl$ION_IOC_MAP ioctl$ION_IOC_SHARE ioctl$ION_IOC_SYNC]
Do you know why? Whether "resource" supports dependency between parameter of two ioctls, like "ion_handle"?

Do you know why?

What the error message says. Or what do you mean?
The descriptions in sys/android are unused and probably broke, use the ones in sys/linux/dev_ion.txt.

Whether "resource" supports dependency between parameter of two ioctls, like "ion_handle"?

If something accepts a resource as an input, then something else must produce this resource as an output. Otherwise there is no way to create a resource to pass it into the first syscall.


how do I pass a string for the relationship in a query?

Neography::SyntaxException: Parameter maps cannot be used in MATCH patterns (use a literal map instead, eg. "{id: {param}.id}") (line 1, column 21 (offset: 20))
"MATCH   (fromNode)-[{relationship}]->(toNode) "

My match statement has an error, even though I pass the value to the relationship string:

query_response = @neo.execute_query("MATCH   (fromNode)-[{relationship}]->(toNode)
WHERE   fromNode.bot_client_id = {bot_client_id} AND toNode.epoch_utc_i > {fromTime} AND toNode.epoch_utc_i < {toTime}
                                        RETURN  toNode.value
                                        LIMIT   {limit}",
                                        {
                                            :fromTime => fromTime, :toTime => toTime, :bot_client_id => @bot_client_id,
                                            :limit => limit, :relationship => relationship.to_sym
                                        }
                                    )

@neo.execute_query("MATCH (fromNode)-[:" +relationship + "]->(toNode)
WHERE fromNode.bot_client_id = {bot_client_id} AND toNode.epoch_utc_i > {fromTime} AND toNode.epoch_utc_i < {toTime}"

You can't use a parameter for a relationship type.


how does it works?

hello i have installed yor tool... then tried to clone certificate, so i havee download kmp player and so open sourse tool from github...
./mangle -C KMP.exe -I Captura.exe -O 1.exe -S 3
it just broke new file it does not work... why what i did wrong?

I need more information on what the broke file looks like. Does it not run, does it look like a different file type?


run mapreduce tests

Related: https://github.com/pouchdb/express-pouchdb/pull/424

fixed in the monorepo merge


Microsoft Graph v1.0: teams user app list

The teams user app list command uses a beta endpoint that is now in v1.0.
https://github.com/pnp/cli-microsoft365/blob/266fd8d68e2a71a9c3d8d58d5c133916193f99b9/src/m365/teams/commands/user/user-app-list.ts#L42
List apps installed for user: https://docs.microsoft.com/en-us/graph/api/userteamwork-list-installedapps?view=graph-rest-1.0&tabs=http#example-1-list-apps-installed-for-the-specified-user

I would like to take this.
Could you please assign to me?

Appreciate your help @dips365 👏


Monitor was always enabled causing performance degradation

The Boolean expression for the monitor to be enabled was incorrect, as instead of using the enabled field, it used the comet configuration object, making the expression always True.
This caused performance degradation (we've observed ~10% drop) as it erroneously invoked the events logging flow along with the expensive calculation of loss.mean().item().

http connection issue caused cpu-torch-latest to fail

@deepcharm
Hi! It's Alex from Comet. Thanks for noticing and fixing the bug, we appreciate it.


Powershell Module Should Support Scope Parameter

Description of the new feature / enhancement
Currently the winget-cli module supports a --scope parameter which can be set to user or machine.
https://learn.microsoft.com/en-us/windows/package-manager/winget/install#options
The current powershell implementation (Microsoft.Winget.Client) does not appear to support the scope parameter.  Looking through the README doesn't speak to this one way or another, but looking at https://github.com/microsoft/winget-cli/blob/master/src/PowerShell/Microsoft.WinGet.Client.Engine/Commands/FinderPackageCommand.cs it appears the parameter is not currently supported.
Adding a scope parameter to the Powershell implementation would provide a powershell native way to manage machine level packages.  This would be particularly useful when working with Intune, which currently only executes Powershell remotely and has no good way to execute winget as an administrator at the user scope.
Proposed technical implementation details
Implement a new scope parameter that supports the "Machine" and "User" values to bring parity with the current winget cli tool.
EX: Get-WinGetPackage -Scope "Machine"

[Policy] PowerShell

Seems like it's included
See
https://github.com/microsoft/winget-cli/issues/4798#issuecomment-2438598369


add ability to extend sortable params

This PR allows user to add personal options at Sortable library such scrollSpeed, scrollSensitivity, scroll and other. All params you may find here https://github.com/RubaXa/Sortable . I added example. Also this PR close this issue https://github.com/angular-dashboard-framework/angular-dashboard-framework/issues/54

Because of scrollSensitivity and sroll we had to modify the dist file of adf. So, would be great to see this pull request get merged.


deep routing server rendering

with the following configuration (referenced by the docs):
<Route path="/" component={App}>
    <IndexRoute component={Home}/>
        <Route path="/login" component={Welcome}>
            <IndexRoute component={Login}/>
            <Route path="/forgot" component={ForgotPassword} />
        </Route>
    <Route path="about" component={About} />
</Route>

and with the following server router matching (also from the docs):
match({ routes, location: req.url }, (error, redirectLocation, renderProps) => {
    if (error) {
        res.status(500).send(error.message)
    } else if (redirectLocation) {
        res.redirect(302, redirectLocation.pathname + redirectLocation.search)
    } else if (renderProps) {
        res.status(200).send(renderToString(<RoutingContext {...renderProps} />))
    } else {
        res.status(404).send('Not found')
    }
})

renderProps is undefined when navigating to:
localhost:3000/login/forgot

navigating to 2nd level works just fine (localhost:3000, localhost:3000/login and localhost:3000/about are accessible)
desperate for help with this, thanks!

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router.
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.


denoflare serve: WorkerD support?

Now that workerd is working reasonably well:
https://github.com/cloudflare/workerd
Should we add support to be able to start/watch it in the same way wrangler dev --experimental-local does? Since the APIs are emulated the same, it shouldn't matter if its deno or node style post-bundling using this worker.

👍 I would love to have workerd as a local option for serve - good long-term goal.
First step would be to find/make a Deno package to manage workerd.  It does not have implementations for any Cloudflare service APIs like KV, so we'd need a way to pass our implementations down for it to use.
Denoflare's default isolation mode already rpc-ifies these service APIs, so they can be threaded out through the permissionless isolate, and in preparation for a process-based isolation mode, once https://github.com/denoland/deno/issues/10750 is implemented.  This work might make remoting down to a separate workerd process a bit easier than starting from scratch.
Some of the missing features and sandbox warnings in the current workerd readme are also an indication to me that this might be a longer-term vision rather than a shorter-term viable project.


Xnero: Watch eduhelphub.com

Xnero requests the watch of the watch_keyword eduhelphub\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

eduhelphub\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Remove possiblity of duplicating sequence ids when reading latest id

These changes resolve an issue I was seeing whereby sequence ids for messages going from a state partition to a parallel computation would grow by 2. This meant that the messages were not routed to all the parallel workers, leaving some workers completely idle forever.
This change makes sure that reading the current_seq_id from the generator cannot produce the side effect of incrementing the id.
cc: @jtfmumm

@pzel is this something we would want to do a hotfix release for related to your blog post? or do we just want to mention this fix in the blog post or is it not important for the blog post?

@pzel What is the other way that these changes break sequence numbering?  Why was this closed instead of addressed?

Re-opened as https://github.com/WallarooLabs/wallaroo/pull/2524, with tests.

Regarding your question about the fix allegedly breaking sequence numbering in another way: it was confusion on my part, coupled with weird behavior of ponyc with debug enabled.


run error in replay_actions

Hi, I'm using win10 and python3.6. I have installed this package and can use the command " python pysc2.bin.play ..." to play as human or play replay. But, when I want to dumpped the actions from replay, I got the errors as follows:
python -m pysc2.bin.replay_actions --replays "D:\Blizzard App\StarCraft II\Replays\test"
Getting replay list: D:\Blizzard App\StarCraft II\Replays\test
1 replays found.
[0] Starting up a new SC2 instance.
C:\Users\chensy\Desktop\pysc2 source\pysc2\lib\protocol.py:103: RuntimeWarning: Trying to access flag sc2_verbose before flags were parsed. This will raise an exception in the fut
ure.
if FLAGS.sc2_verbose:
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
C:\Users\chensy\Desktop\pysc2 source\pysc2\lib\protocol.py:81: RuntimeWarning: Trying to access flag sc2_verbose before flags were parsed. This will raise an exception in the futu
re.
if FLAGS.sc2_verbose:
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
C:\Users\chensy\Desktop\pysc2 source\pysc2\lib\protocol.py:85: RuntimeWarning: Trying to access flag sc2_verbose before flags were parsed. This will raise an exception in the futu
re.
if FLAGS.sc2_verbose:
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
[0] SC2 Started successfully.
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
[0] Got replay: D:\Blizzard App\StarCraft II\Replays\test\0000e057beefc9b1e9da959ed921b24b9f0a31c63fedb8d94a1db78b58cf92c5.SC2Replay
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
ERROR:root:Trying to access flag sc2_verbose before flags were parsed.
Traceback (most recent call last):
File "D:\Software\Anaconda\lib\site-packages\gflags\flagvalues.py", line 535, in getattr
raise exceptions.UnparsedFlagAccessError(error_message)
gflags.exceptions.UnparsedFlagAccessError: Trying to access flag sc2_verbose before flags were parsed.
============================================= Summary 10 secs =============================================
Replays: 0, Steps total: 0
Camera move: 0, Select pt: 0, Select rect: 0, Control group: 0
Maps: 0
{}
Races: 0
{}
Unit ids: 0
{}
Valid abilities: 0
{}
Made abilities: 0
{}
Valid actions: 0
{}
Made actions: 0
{}
Crashing replays: 0
[]
Invalid replays: 0
[]
---------------------------------------------- Process stats ----------------------------------------------
[ 0] replay: 0000e057be, replays:     0, steps:       0, game loops:       0, last:  replay_info,   0 s ago
Hope for your help, thanks~
By the way, your api really do a great job!

add this line "FLAGS(sys.argv)" after defining flags to parse the flags explicit. it works.

I can't seem to replicate this problem. I just switched to a newer version of the flags and app library, so hopefully this is now fixed. Can you verify?

Hi, sorry that I'm late to reply.  @Tangent-Wei , your way fix it well. Just add " FLAGS(sys.argv)" in the replay_action.py  file.  Also, I have fixed it in a tricky way:
(in protocol.py):
class FLAGS(object):
sc2_verbose = 0
By the way, there may be a "bug" in the replay_action.py, in about 117 line:
" replay_name = os.path.basename(replay_path)[:10] "
it means that the name is just 10 characters?  @tewalds

Ah, yeah, that may not be optimal in all cases. It was useful when running over blizzard's replay packs where the name is just a giant hash. Overall that script needs a bunch of love, but is something I'm unlikely to do given we do it rather differently internally.

@pangzhenjia  Where is the replay_action.py file? Did you mean replay_actions.py? I can't find where the sc2_verbose flag is but it is throwing up the flag parsing error.

Solved this by upgrading to pysc2 1.2


SlurmGCP. Refactor reservation fetching logic

Preparatory step to allow for more functionality.

For CentOS File tools/cloud-build/daily-tests/builds/slurm-gcp-v6-centos7.yaml not found


Adding one-time RPC to find unaliased / true dataset ID.

@tseaver I just peeled off the part of #528 that determines the ID without using it anywhere.
I pinged
https://github.com/GoogleCloudPlatform/google-cloud-datastore/issues/59
to determine the necessity of this.
The real "bug" here is having to use _prepare_key_for_request.

Changes Unknown when pulling ff5b2a7d3092006f34f9e96ad4b63ccb65fb6df2 on dhermes:non-fuzzy-app-id-isolated into ** on GoogleCloudPlatform:master**.

@tseaver I rewrote the commit to make _find_true_dataset_id public.

Coverage remained the same at 100.0% when pulling 01d0354f4d8b3a34af0967f06ec29cf9552813bb on dhermes:non-fuzzy-app-id-isolated into 3af46b17a8c1655274e188cd124097ac5dfa2dd0 on GoogleCloudPlatform:master.

LGTM


Create a description for the concept of static transformer

This task was derived from the committee workshop on 19.02.2018.
There are two transformer scenarios:

A static transformer with a predefined mapping
A dynamic transformer (Will be described by Igor)

In order to be able to clearly distinguish between both concept we first need to describe them:

[ ] The connectors workgroup needs to describe the concept of static transformers

Initial version of a transformer description is currently pending: Transformers


Eloquent support

Porting project forward to Eloquent.
Fortunately no code changes to the core of ros2_dotnet were required; only some updates to repos, an update to the repos files, and updated build instructions.
This PR depends on the completion of #41 which should be merged first. I will rebase this PR once that happens.

Great!!!!
Thanks for your work ;)

Unfortunately it appears the foonathan/memory project (a new dependency of Fast-RTPS introduced in Eloquent) is currently unable to cross compile for ARM at the moment.
I've decided to disable ARM support for the near term as ARM on UWP is not very common -- I'll create a new issue to track finding an ARM-compatible DDS implementation (especially on ARM64 for HoloLens2) but in the meantime this will let work on the core ros2_dotnet project continue.

Experiencing quite a bit of trouble outside of Win32 builds -- closing PR until this is fully tested and ready on all platforms.

Hi @theseankelly
I have been building and testing this morning this branch in Linux, including rclcpp (I will need it for tf2).

I had to disable tests in dotnet because of an error similar to this.
At Fast-RTPS/src/cpp/transport/UDPv4Transport.cpp:313 I had to change interface() to interface_name(). I will prepare a PR with this.

I will try this afternoon to compile it in Win Desktop.

Oh, thanks for looking at this @fmrico -- I'll re-open the PR since you're working with it also.
Sounds good -- the bulk of my problems are with some new dependencies added by Fast-RTPS that are not UWP compatible. That, and I think the GitHub Actions environment is different in some ways as I don't have the same problems building locally.

Turns out the issues were due to known problems with the Fast-RTPS release for Eloquent -- updated the ros2-dotnet fork of Fast-RTPS.

@theseankelly the Fast-RTPS folks don't test their releases for all the platforms they claim to support, so this will be a recurring problem. I've opened https://github.com/ros2-dotnet/ros2_dotnet/issues/52 to investigate if we could get rid of Fast-RTPS and use CycloneDDS instead.


feat: Add tapped skip event

The type of this PR is: Feature

This PR resolves CX-2415
Description

PR Checklist (tick all before merging)

[x] If I've added a new file to the tree I've exported it from the common index.ts
[x] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

:rocket: PR was released in v4.38.0 :rocket:


lots of updates

updates:

filter out Hidden Power in movepools.
teambuilder and the challenge code button immediately reflect changes made in popup (used to require a reload of showdown).
show metagame date in a corner if there's empty space (eye candy).
updated firefox readme instructions.
replaced some outdated code (massive xhr function, callbacks when promises are available).
fixes:
replaced alert() in popup because it was broken af.
fix movepool headers (Moves, Usually useless moves) getting removed in some cases.
fix mobile view behavior getting applied to desktop users as well.

we should introduce a service worker for 1.4 and move a lot of code there. for now, i avoided doing this, because doing so would require a new branch for kiwi browser or dropping support for it until it updates (neither option is very user friendly)

Please don't publish to the store yet, I found a cleaner way to handle date updates than using the messaging api.


Add Marco Petersen to students

Hey, just saw your post on /r/programming, love the idea!

@ocrampete16 I'm glad that you liked it! And thank you for enrolling! :smile:

@ocrampete16
I updated the manner to enrolling in our course to be more scalable.
Can you create your profile here again?
Sorry for that, but in that way will be much more easy for all of us :smile:


Refactor Autoscaling tests

Moves all tests that touch ELB to a dedicated file
Use setUp-methods to remove duplicate code from ELB and ELBv2 tests

Codecov Report

Merging #5426 (cdf3873) into master (b6929b7) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #5426   +/-   ##
=======================================
  Coverage   96.08%   96.08%
=======================================
  Files         717      717
  Lines       71366    71366
=======================================
  Hits        68571    68571
  Misses       2795     2795

Flag
Coverage Δ

servertests
35.77% <100.00%> (ø)

unittests
96.02% <100.00%> (ø)

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

Impacted Files
Coverage Δ

moto/__init__.py
98.56% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix for Passing require('<SomeLocalURI>') to .source, results in “E…

#61 …rror while updating property ‘source’ of a view managed by RCTWebViewBridge”. #61

@agenthunt merged, thank you.

Np. Thanks :)


gp.sh not working for private repos

Running gp.sh for a non-public repository fails with the following error:
bower my-element#master       not-cached git://github.com/my-org/my-element.git#master
bower my-element#master          resolve git://github.com/my-org/my-element.git#master
bower my-element#master          ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/my-org/my-element.git", exit code of #128 fatal: remote error:    Repository not found.

The problem here seems to be the repository url git://github.com/my-org/my-element.git#master which should probably be something like git@github.com:my-org/my-element.git.

Outdated, from a previous use of this repo.


Loading twice

I am using this inside my calendar component to run external js files. Its working if your component will only be used once but if you use the component twice or more loadjs will error out

Oops nvm I read the other thread I need to turn off async false


Spacing issues in search results view

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
Some of the spacing looks weird in the search screen, "the header with the filename" should have some more margin since its is covering the buffer below.

Environment
Zed: v0.119.5 (Zed Preview)
OS: macOS 14.2.1
Memory: 64 GiB
Architecture: aarch64
MacBook Pro M1, built in screen, "Berkeley Mono" as ui font (not sure it matters).
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

This was fixed in 0.119.10: https://zed.dev/releases/preview/0.119.10

Fixed headers in multi-buffers overlapping over content of the buffer.


Add lint CI

Create a CI pipeline to lint code on each push.

https://github.com/astral-sh/ruff looks awesome for python


Optimize the scenario of adding/deleting a large number of tables

Fix #2358
in this scenario, drop a large number of tables will move to CatalogRecycleBin.
then when he actually deletes the table, he will record a log
this log will take 10ms per table and hold lock for a long time
this PR optimize write log once to reduce the time consumed by this operation.

The scenario of adding/deleting a large number of databases or partitions also need to be optimized?

The scenario of adding/deleting a large number of databases or partitions also need to be optimized?

this will optimize it later near future if encounter this.


Feature Add Reactive, ObservableAsProperty and ReactiveCommand Source Generators

What kind of change does this PR introduce?

Feature
What is the current behavior?

Fody is currently available for [Reactive] and [ObservableAsProperty]
What is the new behavior?

[Reactive] [ObservableAsProperty] Field Attributes and a [ReactiveCommand] Method Attribute with Source Generators now added.
What might this PR break?
There are differences between the old Fody injector and the new Source Generator both in the Attribute location and the operation.
Documentation must be updated to coincide with a release.
Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

There is a separate repo for the source generators, probably best to separate since source-generators don't have a dependency on the rxui version.

https://github.com/reactiveui/ReactiveUI.ObjectGenerators

https://github.com/reactiveui/ReactiveUI.ObjectGenerators

 GitHub**GitHub - reactiveui/ReactiveUI.ObjectGenerators: Use source generators to generate objects.**Use source generators to generate objects. . Contribute to reactiveui/ReactiveUI.ObjectGenerators development by creating an account on GitHub.

Thank you, I will move it to this repository.
It has no direct dependency to ReactiveUI.

Moved to https://github.com/reactiveui/ReactiveUI.SourceGenerators/pull/3


perf: create zip using streams

I noticed that zipping is not done using streams which results in the zip file being accumulated in the memory of the user which massively slows down the process of zipping and for some users (me included) throws an out of heap error for big projects.
before:

after:

Released in v0.18.12


[INLONG-7908][Sort] Update cdc-base for Incremental Snapshot Framework

[INLONG-7908][Sort] Update cdc-base for Incremental Snapshot Framework

Title Example: [INLONG-7908][Component] Title of the pull request

(The following 7908 should be replaced by the actual GitHub Issue number)

Fixes #7908

Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve?
Modifications
Describe the modifications you've done.
Verifying this change
(Please pick either of the following options)

[ ] This change is a trivial rework/code cleanup without any test coverage.

[ ] This change is already covered by existing tests, such as:
(please describe tests)

[ ] This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

@kuansix, please add more details about this PR. Thanks.


CalWORKS case study QA

CalWORKS case study live site: https://innovation.ca.gov/our-work/projects/helping-more-eligible-families-enroll-in-calworks/
Image to use for social media share image and Projects page: https://drive.google.com/file/d/1yXpFt9NCak0SplKC9vCZgWW5ml7er7Jw/view?usp=drive_link

[x] content sign off
[x] design QA sign off
[ ] social media share images
[ ] Remove do-not-tag from the page.
[ ] update Project page

The page looks good on Desktop and mobile!
Social media share image is only working on LinkedIn. I tested Facebook and Twitter as well.

Confirming that content is approved!

Hey @jbum not rush, we have about a week assuming this case study gets approved in time (so possibly even more time). The social media share images for FB and Twitter are still not working for CalWORKS cae study for some reason. Can you look into it?

Sorry, this didn't make it past my gmail filters.  Fixed now!

Thanks Jim! Social media images work.
Waiting on partners for any revisions and final approvals
cc @YeseniaGtz


Add package dependency completness field

Description
Adds a field that describes the completeness of a package's direct dependencies:

complete: the package has all of its direct dependencies resolved and related to this package.
incomplete: the package does not have all of its direct dependencies resolved.
mixed: a superset of complete -- indicates that the package has all of its direct dependencies resolved as well as some or all of indirect dependencies.  What is notable about this is that direct and indirect dependencies are linked directly to this package and are not separable (you cannot distinguish between a direct and indirect dependency from the perspective of this package).
unknown: indicates when dependency resolution mechanism for this package is not well understood.

In addition to adding this new field, all catalogers were updated to raise up accurate values for this field:

Cataloger
Completeness
Comment

alpm-db-cataloger
complete

apk-db-cataloger
complete

binary-classifier-cataloger
unknown
classifiers are limited to identifying package identities, but have no information about dependencies

cargo-auditable-binary-cataloger
incomplete

cocoapods-cataloger
incomplete

conan-cataloger
conanfile.txt: incomplete, conan.lock: complete

conan-info-cataloger
complete

dart-pubspec-lock-cataloger
incomplete

dotnet-deps-cataloger
complete

dotnet-portable-executable-cataloger
incomplete

dpkg-db-cataloger
complete

elf-binary-package-cataloger
unknown
though we can look for shared libs, we cannot see static dependencies nor dynamic dependencies using dlopen. This means that, even in cases where the dep info is actually complete, we can't programmatically determine that.

elixir-mix-lock-cataloger
incomplete

erlang-otp-application-cataloger
incomplete

erlang-rebar-lock-cataloger
incomplete

github-action-workflow-usage-cataloger
complete
the only known exception to this is shared workflows

github-actions-usage-cataloger
incomplete

go-module-binary-cataloger
mixed

go-module-file-cataloger
mixed

graalvm-native-image-cataloger
unknown
or if anything is decoded from the internal SBOM, then that value is used

haskell-cataloger
incomplete

java-archive-cataloger
complete/incomplete
all packages are assumed to be incomplete unless searching for transitive dependencies configuration option has been enabled

java-gradle-lockfile-cataloger
incomplete

java-jvm-cataloger
incomplete

java-pom-cataloger
incomplete

javascript-lock-cataloger
incomplete

javascript-package-cataloger
incomplete
we find all dependency nodes but are not crafting relationships

linux-kernel-cataloger
incomplete

lua-rock-cataloger
incomplete

nix-store-cataloger
incomplete

opam-cataloger
incomplete

php-composer-installed-cataloger
incomplete

php-composer-lock-cataloger
incomplete

php-pecl-serialized-cataloger
incomplete

portage-cataloger
incomplete

python-installed-package-cataloger
incomplete

python-package-cataloger
requirements.txt: incomplete, setup.py: incomplete, poetry.lock: complete, Pipfile.lock: incomplete

r-package-cataloger
incomplete

rpm-archive-cataloger
incomplete

rpm-db-cataloger
complete

ruby-gemfile-cataloger
incomplete

ruby-gemspec-cataloger
incomplete

ruby-installed-gemspec-cataloger
incomplete

rust-cargo-lock-cataloger
complete

sbom-cataloger
unknown
this may need some discussion

swift-package-manager-cataloger
incomplete

swipl-pack-cataloger
incomplete

wordpress-plugins-cataloger
incomplete

Closes #3010

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have added unit tests that cover changed behavior
[x] I have tested my code in common scenarios and confirmed there are no regressions
[x] I have added comments to my code, particularly in hard-to-understand sections

@wagoodman I wanted to make sure I understand why the rust-cargo-lock-cataloger is labeled as "complete" not as "mixed".
It seems like as we make a set of dependency relationships more complete, it passes from complete, to mixed, and back to complete, which is surprising:

It finds all the direct dependencies and nothing else -> "complete"
It finds all the direct and some or all indirect dependencies, but you can't tell how direct the dependencies are -> "mixed"
It finds all direct and indirect dependencies, and you can tell which ones are direct -> "complete"

It seems weird to me that a cataloger can effectively get promoted from complete to mixed, and then from mixed to complete, by adding relationship data.
When I first read the descriptions above, I thought, "rust isn't complete, it's mixed, because it includes transitive dependencies."
Am I understanding correctly here?

you're correct, cargo.lock should be mixed 👍

Cross posting https://github.com/anchore/syft/issues/3010#issuecomment-2485475311 so that it gets seen here.


Performance impact on actual buffer editing after save

I've been having some minor performance issues lately (db reached 4k+ notes).

Issue: shortly after saving, I sometimes get a .5-multisecond delay as I wait for the graph to refresh. This shouldn't be the case on a machine with 16 cores, and significant free RAM.
When turning off org-roam-server, the lag disappears. Something is either locking, or there is a bottleneck I can't seem to find.
Looking at the image above, the httpd server does not run in it's own process. Would it be possible to fork this off, so it could potentially be reniced? Other ideas? Polling impact?

Can you try disabling auto updates to see if it makes any difference

I also experience lagging due to org-roam-server. How should I disable the auto updates?

I also experience lagging due to org-roam-server. How should I disable the auto updates?

(setq org-roam-server-network-poll nil)

Let me play with that and see if the lagging continues, thanks for the variable pointer.

 It does seem to be polling. Can the process be forked off, so one can enable polling but nice it, so it doesn't affect the editor?

Unfortunately, as far as I know, every process in emacs runs in a single core, so every process locks emacs. But checking database updates can be improved so I will look into that.

It should be better now. It will only create the json format if the database is modified. You can still disable the polling but org-roam only updates the database if your emacs is idling or if you run org-roam-db-build-cache, so enabling polling should not affect your usage of the emacs now.
https://github.com/org-roam/org-roam-server/commit/608fc3865ff1c69c9802d2e2bb22430e83252c3c

Thanks a lot. This sounds promising, waiting for idle.


Fix issue where pattern completion would not be triggered

Forgot to check for the cursor position when initiating pattern completion in a certain case.

Merging this before review as its a simple small fix and I need it to continue.


Module 'Alamofire' was not compiled with library evolution support; using it means binary compatibility for 'surfMadly' can't be guaranteed

when I update the Xcode to 11.3, this issue had come, from this many times alamofire not respond.

Alamofire doesn't support library evolution for Alamofire 5. We will eventually ship support for v4, as tracked by #2990.


How to integrate Users with scaffold?

php artisan infyom:scaffold User --fromTable --tableName=users --ignoreFields=email_verified_at,remember_token

Requires a lot of customization like:

Merge User.php with Models\User.php (and change all references)
Create a way to add a random password if empty and hash the provided one (editing repository)
Remove password from list

Is there a better way or Users are not intended to be managed?

@mariovalney Unfortunately I don't think so. I will add it as a feature.

Added Support to Publish User Crud with default fields.
Check its docs from here: https://labs.infyom.com/laravelgenerator/docs/6.0/generator-commands#default-users-model-crud

Awesome work, guys. Thank you!

see the demo here https://youtu.be/V7PCL6HCdXo

see demo here https://youtu.be/V7PCL6HCdXo

Is missing the generated model_schema User.json when you generate for User model.

Just in case, I had to change the route for users from:
Route::resource('users', 'UserController')->middleware('auth');
to:
Route::resource('users', App\Http\Controllers\UserController::class)->middleware('auth');


Too many time starting the application

Please share more info about the issue!

No response for 11 days.. closing now,
If you need to reopen feel free to do so with more details


microk8s inspect incorrectly claims that docker is installed

Running microk8s inspect was telling me that docker was installed. I fully removed including running apt purge it and still got the following message:
WARNING:  Docker is installed.
File "/etc/docker/daemon.json" does not exist.
You should create it and add the following lines:
{
    "insecure-registries" : ["localhost:32000"]
}
and then restart docker with: sudo systemctl restart docker

It was only after looking at the code that I figured out what was actually happening. It turns out that that just having /etc/docker is all that is needed to get this warning.
https://github.com/ubuntu/microk8s/blob/5e23ac6a001bf3fee2cbb3cd4f1781c6bc945e7e/scripts/inspect.sh#L161

On a previous server I had docker installed, then I uninstalled it. It left the directory /etc/docker behind. When I installed microk8s it complained of docker being installed. I deleted the directory and all was good after that. I think a better check would be /bin/docker.

Yeah that was pretty much the same situation for me.

The issue still exists. What's the bet this bot isn't able to reopen issues.

Thank you @neoaggelos :heart:


Add oc and kubectl download links to docs

Small docs improvements on experience on Linux.

@LalatenduMohanty Thanks for suggestion, updated the PR.


SQLfluff is looking for profiles.yml for dbt cloud connection

Hello,
I am using dbt power user in VS code with dbt cloud, Snowflake and try to get SQLfluff going.
I have the SQLfluff extension installed, and use the dbt templater as per these instructions: https://docs.sqlfluff.com/en/stable/configuration/templating/dbt.html
I tired various configurations for this part:
[sqlfluff:templater:dbt]
project_dir = <relative or absolute path to dbt_project directory>
profiles_dir = <relative or absolute path to the directory that contains the profiles.yml file>
profile = <dbt profile>
target = <dbt target>

but always end up with this error

To me it seems like SQLfluff is looking for a profiles.yml although I don't have one since I connect to dbt cloud.
I couldn't find a setting to tweak this behaviour.
This is how my .sqlfluff file looks otherwise:
[sqlfluff]
templater = dbt

[sqlfluff:templater:jinja]
apply_dbt_builtins = True

[sqlfluff:templater:jinja:macros]
# Macros provided as builtins for dbt projects
dbt_ref = {% macro ref(model_ref) %}{{model_ref}}{% endmacro %}
dbt_source = {% macro source(source_name, table) %}{{source_name}}_{{table}}{% endmacro %}
dbt_config = {% macro config() %}{% for k in kwargs %}{% endfor %}{% endmacro %}
dbt_var = {% macro var(variable, default='') %}item{% endmacro %}
dbt_is_incremental = {% macro is_incremental() %}True{% endmacro %}

I'm not sure where else I should look to try to fix this.

Running into the same error. It seems to be that dbt has a built-in version of sqlfluff which you can run by using dbt sqlfluff format. This send the invocation to the cloud. Now that's why you don't have a profiles.yml. But for some reason I'm unable to configure the extensions to use the built-in dbt command instead of the standalone sqlfluff command.


file/find confusion

This one currently says "Module contains no files to install" on the status page, but the download exists and has mod files in it. If I change file to find, it generates a valid .ckan file. And the Source directory is actually Sources.

Looks like the mod author changed the layout, thanks for catching this


Change EditPersonDescriptor parameters to be non-Optional #480

Fixes #480

@damithc prof did a quick fix for #480. So far it doesn't seem that the usage of Optional as parameters is justified, as the codebase is being littered with Optional.of(...) (see the code deleted).

v1
@Zhiyuan-Amos submitted v1 for review.

[v1 1/1] Change EditPersonDescriptor’s parameters to be non-Optional

(:books: Archive)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/482/1/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

v2
@Zhiyuan-Amos submitted v2 for review.

[v2 1/1] Change EditPersonDescriptor’s parameters to be non-Optional

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v1 and v2)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/482/2/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

v3
@Zhiyuan-Amos submitted v3 for review.

[v3 1/1] Change EditPersonDescriptor’s parameters to be non-Optional

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v2 and v3)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/482/3/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

@yamgent @limmlingg gentle reminder TO REVIEW STOP MAKING ME REMIND YOU :>

@damithc Is this use case of functional programming here appropriate, or should this be commented/simplified for student's sake since it may not come across as intuitive initially?

It is a bit obscure, but  I guess we can leave it as it is. If at all, we can add a comment at the start of the code block.

v4
@Zhiyuan-Amos submitted v4 for review.

[v4 1/1] Change EditPersonDescriptor’s parameters to be non-Optional

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v3 and v4)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/482/4/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

@yamgent @limmlingg gentle reminder FOR YOUR REVIEW RITE NOW

v5
@Zhiyuan-Amos submitted v5 for review.

[v5 1/1] Change EditPersonDescriptor’s parameters to be non-Optional

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v4 and v5)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/482/5/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

v6
@Zhiyuan-Amos submitted v6 for review.

[v6 1/1] Change EditPersonDescriptor’s parameters to be non-Optional

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v5 and v6)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/482/6/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

@chao1995 i've made the necessary changes already. @damithc for your review too prof.

@damithc gentle reminder for your review :)


BugFix of Automatically adds %.* of previous paragraph's typing.

What is this PR for?
This PR is to fix bug from https://github.com/apache/zeppelin/pull/806.
The default interpreter name that automatically adds should be interpreter group name.
What type of PR is it?
Bug Fix
Screenshots (if appropriate)

before

after

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

@astroshim Good catch indeed. LGTM 👍

LGTM

Thanks for checking this out

good fix!

@astroshim could you rebase and see if it passes selenium test CI build profile?

@Leemoonsoo I rebased.

The selenium test has passed!!

@astroshim Now there're commits not belongs to this contributions, 41a7302, fd715c8, ab5ce62
Could you remove these commits?

@Leemoonsoo Sorry for late response. I fixed.

@astroshim No worries. Thanks for the quick response.
LGTM and merge into master branch if there're no more discussions.


TextField.onTap fires before winning gesture

I use suffixIcon in TextField. When TextField is clicked, it will open PageC, but if suffixIcon is clicked, it will open pageB.
PageA
 StreamBuilder<List<ABC>>(
                stream: _bloc.listStream,
                builder: (context, snapshot) {
                  return TextField(
                    onTap: () {
                      if (snapshot.hasData) {
                        _goToPageC(snapshot.data);
                      }
                    },
                          .....
                      suffixIcon: Container(
                        padding: EdgeInsets.symmetric(vertical: 10),
                        child: FloatingActionButton(
                          heroTag: "addButton",
                          child: Icon(Icons.add),
                          onPressed: () {
                            Navigator.pushNamed(context, PageB.ROUTE);
                          },
                        ),
                            .....
                },
              ),

  void _goToPageC(List list) async {
    var results = await Navigator.of(context).push(PageRouteBuilder(
        opaque: false,
        pageBuilder: (BuildContext context, _, __) {
          return PageC(list);
        }));

    if (results != null) {
             .....
        }
      });
    }
  }

My issue is when I click the suffixIcon, it will open pageC. When I click the back device button in pageC, only pageB will show. Why would this happened?

Hi @tony123S

sample code
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) => MaterialApp(
    home: HomePage(),
  );
}

class HomePage extends StatefulWidget {
  @override
  _HomePageState createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  @override
  Widget build(BuildContext context) => Scaffold(
    body: Center(
      child: TextField(
        onTap: () =>  Navigator.push(
          context,
          MaterialPageRoute(builder: (context) => MyPage(title: 'C')),
        ),
        decoration: InputDecoration(
          suffixIcon: Container(
            padding: EdgeInsets.symmetric(vertical: 10),
            child: FloatingActionButton(
              child: Icon(Icons.add),
              onPressed: ()=> Navigator.push(
                context,
                MaterialPageRoute(builder: (context) => MyPage(title: 'B')),
        ),),),),
  ),),);
}

class MyPage extends StatelessWidget {
  final String title;
  MyPage({this.title});

  @override
  Widget build(BuildContext context) => Scaffold(
    body: Center(
      child: Text('page $title',
        textScaleFactor: 3,
    ),),
    floatingActionButton: FloatingActionButton(
      onPressed: ()=> Navigator.pop(context),
      child: Icon(Icons.arrow_back),
  ),);
}

I do see an unexpected behavior,
but not necessarily the one described in your post:
clearly the routing to "page C" when attempting to tap on the TextField decoration
happens due to the overlapping of the gesture detectors area, nevertheless
I'm surprised that 2 different routing happen at the contextually.
does the code above represent the situation you are describing?
thank you

Hi @iapicca ,
the reason I'm using  PageRouteBuilder instead of MaterialPageRoute is to prevent stack rebuild when a new page is pushed as described here https://github.com/flutter/flutter/issues/11655

Anyone can help ?

I suspect this is because the text field's gesture detector fires onTap too eagerly (doesn't wait to have won its gesture handler).

duplicate of https://github.com/flutter/flutter/issues/39376


What is the use case for the bottom menu?

ISTM that the bottom menu takes up a lot of space without adding anything useful.
Is it really needed?

Bottom menus are typically used as alternate navigational aids. They also can provide better accessibility to pages for the visually impaired via screen-readers.

FWIW, my expectation for a bottom of the page menu is that of a kind of
site map where I can go almost anywhere top-level-ish in a site. It's where
I expect to find a link to pages for thibgs like contact us, legalese, all
top level things, policies, and so on. For Apache, I would not expect a
link for each TLP, but a link to a page that lists all TLPs.
Gary
On Wed, Jul 19, 2023, 08:13 sebbASF @.***> wrote:

I see.
If it is an alternate navigational aid, then surely it should give access
to the same content as the main menu?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/www-site/issues/244#issuecomment-1641973812,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJB6NZPS55J4CNZN3V3OLLXQ7FPRANCNFSM6AAAAAA2PXPCYM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Not always. To anticipate your line of questioning: things like "privacy policy," "contact us," and other "corporate" information are usually found in the bottom (aka footer) menu. People tend to expect to find such details there, which is why historically such info is put in the footer menu.


Extract StreamReference (immutable typed reference to file)

Description
Every time Var.stream() is invoked, an InputStream related to the current file value is returned. StreamReference, on the other hand, is an immutable reference to such stream, allowing to predictably obtain an InputStream pointing always to the same location. It also provides typed access to specific information related to where it originates (resource/asset/file/memory), as well as correct equals/hashCode implementations.
Thanks to this, it's now possible to properly wrap and emit Var values in "observable streams of immutable values", like in Reactive Extensions.
Proposed Changes

Add StreamReference abstract class and sealed set of subclasses (ResourceReference, AssetReference, FileReference, MemoryReference)
Split/move stream-creation logic from FileManager.stream() to FileManager.streamReference() (new) and the relative *Reference.stream()
Add Var.streamReference() and Var.streamReference(boolean fallbackToDefault) to access the stream reference

Notes

This PR does not change any existing behaviour
All new code is marked with @Nullable/@NonNull annotations
Care was taken to follow the code/documentation style as closely as possible

Can one of the admins verify this patch?


How to reset the wifi credentials?

Connected to a MiFi while on the road and set up the Badgy for the first time. Now I want to connect it to my home network and there's no clear way how to do that. Flashing the badgy.bin default file didn't reset it. Any tips on how to reset the WiFi credentials and go back into AP mode?
Thanks

Problem solved. Read through the wifimanager code. If it fails to connect via saved credentials it goes into AP mode. Not exactly the most secure but good enough so you can put it on another network.


echion-web?

I am having trouble running Austin (in a macbook pro) and echion seems to work. Is there austin-web like program for echion? If not, how can visualize the echion output files.

@hgrecco I would be interested in knowing what issues you're facing with Austin, in case this is something that we can fix. I would appreciate if you could open an issue in the Austin repository with all the details on how to reproduce the problem 🙏 .
As for the output from Echion, this is in the MOJO binary format, which is also used by Austin. This means that any tools that is good for visualising MOJO is good for Echion too. Perhaps the best one at the moment is the Austin VS Code extension. Alternatively, you could install austin-python, and use the mojo2austin to convert the MOJO file into the Austin collapsed stack format. From there you can then use the other conversion tools, such as austin2pprof or austin2speedscope to convert to other formats.
I appreciate this might not be an ideal workflow, but please note that Echion is still in an experimental stage.
Hope this helps for now!

I tried to reproduce by producing a clean, conda environment and now is working. Sorry for the noise!


Add native build make target to simplify docker-ce-packaging

Signed-off-by: Guillaume Tardif<EMAIL_ADDRESS>- What I did
Add native make target to simplify packaging and allow PLATFORM_BINARY=docker-scan make native-build
- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory)

replaced by #143


Add Managed SQL Instances

Is it possible to add SQL Managed Instances to this report as well.
Thanks!

hello @irlperu ,
sorry for delayed answer.
please, try V2 that have SQL Managed instance and sent us a feedback :)

hello @irlperu  ,
sorry for delayed answer.
please, try V2 that have SQL Managed instance and sent us a feedback :)


Add physics to TabBarView

TabBarView uses PageView internally, but ScrollPhysics can not be set.
So I added physics to TabBarView, it is applied to PageScrollPhysics and passed to PageView.

This seems reasonable (and thanks for the test!). cc @HansMuller for detailed review.

NiCE. LGTM

Thanks!


Added Python Tutor, an interactive multi-language visualizer.

Added links for Python Tutor, an interactive multi-language visualization tool. Added links for Java, JavaScript, Python, TypeScript, and  Ruby. C and C++ links not added as visualization is not yet available.

I would not necessarily count this as a tutorial...
Change the link name to "(Language) Tutor", as that's what the page says when you visit it
Remove the #edit-mode from the URLs -- leave it to the site to decide to add that or not

Thanks for the input. I've implemented your ideas and submitted another pull request.

I replaced the accidentally removed line.


Roll dialogs no longer have contextual window titles

Titles are now all "Configure Roll" instead of the contextual information they used to provide

3.2.1
4.1.2
Proposed

it seems to me the data can still even be provided, for instance in rollAbilityCheck's second arg, { options: { title: { "Title Here" }}}, but its just not used anywhere

Commenting for assignment


grpcproxy: forward PrevKv flag in Put

/cc @visheshnp

Codecov Report

Merging #8366 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8366      +/-   ##
==========================================
- Coverage   76.74%   76.71%   -0.04%
==========================================
  Files         349      349
  Lines       27366    27368       +2
==========================================
- Hits        21003    20994       -9
- Misses       4857     4868      +11
  Partials     1506     1506

Impacted Files
Coverage Δ

proxy/grpcproxy/kv.go
99.25% <100%> (+0.01%)
:arrow_up:

pkg/adt/interval_tree.go
82.58% <0%> (-8.11%)
:arrow_down:

etcdserver/api/v3rpc/watch.go
89.3% <0%> (-4.19%)
:arrow_down:

proxy/grpcproxy/watcher.go
85.71% <0%> (-4.09%)
:arrow_down:

pkg/transport/listener_tls.go
65.56% <0%> (-0.67%)
:arrow_down:

etcdserver/api/v3rpc/lease.go
96.42% <0%> (ø)
:arrow_up:

clientv3/watch.go
95.04% <0%> (ø)
:arrow_up:

lease/leasehttp/http.go
62.59% <0%> (ø)
:arrow_up:

etcdserver/server.go
80.2% <0%> (+0.23%)
:arrow_up:

etcdserver/apply.go
91.09% <0%> (+0.52%)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

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


GPG path lengths too long on RISC-V evaluation builds

Ref: https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk21u/job/jdk21u-evaluation-linux-riscv64-temurin/138/console (A re-run of the previous build to ensure it was running from the latest fixes in temurin-build):
10:31:54  GNUPGHOME=/mnt/disk-1/jenkins/workspace/build-scripts/jobs/evaluation/jobs/jdk21u/jdk21u-evaluation-linux-riscv64-temurin/workspace/.gpg-temp
10:31:54   10:31:53 up 51 days, 11:15,  0 users,  load average: 0.27, 0.08, 0.02
10:31:54  gpg: keybox '/mnt/disk-1/jenkins/workspace/build-scripts/jobs/evaluation/jobs/jdk21u/jdk21u-evaluation-linux-riscv64-temurin/workspace/.gpg-temp/pubring.kbx' created
10:32:00  gpg: connecting dirmngr at '/mnt/disk-1/jenkins/workspace/build-scripts/jobs/evaluation/jobs/jdk21u/jdk21u-evaluation-linux-riscv64-temurin/workspace/.gpg-temp/S.dirmngr' failed: File name too long
10:32:00  gpg: keyserver receive failed: No dirmngr
10:32:00  gpg recv-keys attempt has failed. Retrying after 10 second pause...
10:32:18  gpg: connecting dirmngr at '/mnt/disk-1/jenkins/workspace/build-scripts/jobs/evaluation/jobs/jdk21u/jdk21u-evaluation-linux-riscv64-temurin/workspace/.gpg-temp/S.dirmngr' failed: File name too long
10:32:18  gpg: keyserver receive failed: No dirmngr

FYI @luhenry @andrew-m-leonard since you've both been doing fixes in this area recently.
Related: https://github.com/adoptium/temurin-build/pull/3643 https://github.com/adoptium/temurin-build/pull/3630

It is https://github.com/adoptium/temurin-build/commit/88fc1e54aed1f11c205236a364fd7453b0cea412 which will override GNUPGHOME when not on alpine. @andrew-m-leonard could you please fix/revert?
I also don't understand why it's not enough to set it in build-farm/platform-specific-configurations/alpine-linux.sh given it's loaded before sbin/prepareWorkspace.sh?

prepareWorkspace

the build-farm/platform-specific-configurations/alpine-linux.sh is only called within a "build-farm" environment (Jenkins). If a user just builds locally using makejdk-any-platform.sh, then prepareWorkspace.sh(checkingAndDownloadingAlsa) will get called but the "build-farm" stuff is not.


Refactor 'guardian management' for infants

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #1533
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app


Release annotations using API keys will be retired on 31 August 2024

https://azure.microsoft.com/en-us/updates/transition-to-new-release-annotations-in-application-insights/

I don't remember what this was for as well.


go template in configmap error

Output of helm version:
Client: &version.Version{SemVer:"v2.16.0", GitCommit:"e13bc94621d4ef666270cfbe734aaabf342a49bb", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.0", GitCommit:"e13bc94621d4ef666270cfbe734aaabf342a49bb", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:50Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
DO
Hello, i'm trying to add alertmanager template (which is go template language) to configmap like
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    app: prometheus
    component: alertmanager
  name: prometheus-alertmanager
data:
  slack.tmpl: >
     .....
     {{ define "__subject" }}[{{ .Status | toUpper }}{{ if eq .Status "firing" }}:{{ .Alerts.Firing | len }}{{ end }}] {{ .GroupLabels.SortedPairs.Values | join " " }} {{ if gt (len .CommonLabels) (len .GroupLabels) }}({{ with .CommonLabels.Remove .GroupLabels.Names }}{{ .Values | join " " }}{{ end }}){{ end }}{{ end }}
    .....

and i got an error
Error: UPGRADE FAILED: parse error in "prom/templates/alertmanager-configmap.yaml": template: prom/templates/alertmanager-configmap.yaml:49: function "toUpper" not defined
UPGRADE FAILED

if i do kubectrl create configmap foo --from-file=slack.tmpl it can create configmap without any problem.
How can i do it with helm ?

The function name is upper, not toUpper. Docs can be found here: http://masterminds.github.io/sprig/strings.html

https://prometheus.io/docs/prometheus/latest/configuration/template_reference/#strings
https://golang.org/pkg/strings/#ToUpper
exactly doesn't matter which function since this configmap not for helm. helm should not handle it

Ah, I see now that you were referring to alertmanager rules. My mistake.
You may be interested in this thread: https://github.com/helm/helm/issues/2798#issuecomment-326446685

thank you


TypeError encountered with enum literal example

TypeError: Cannot convert 16 to a BigInt
    at DataView.setBigInt64 (<anonymous>)
    at DataView.<anonymous> (<anonymous>:2693:20)
    at constructor.setValue [as offset] (<anonymous>:2904:25)
    at constructor.<anonymous> (<anonymous>:2358:13)
    at constructor.initializer (<anonymous>:785:21)
    at new enum-literal-example-2.DataSection (<anonymous>:2286:23)
    at file:///home/cleong/zigar/docs/examples/enum-literal-example-2.js:3:17
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)

Problem with the example passing number to i64. Issue is moot in any event due to implementation of #283.


[🐛 Bug]: Not-found page doesn't work with last vercel version v31.2.0 in edge runtime

next-on-pages environment related information
System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:41 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8103
CPU: (8) arm64 Apple M1
Memory: 16 GB
Shell: /bin/zsh
Binaries:
Node: 18.15.0
Yarn: 1.22.17
npm: 9.5.0
pnpm: 8.6.5
Package Manager Used: yarn (classic)
Relevant Packages:
@cloudflare/next-on-pages: 1.4.0
vercel: N/A
next: N/A
Description
Hi guys.
I tried to run npx @cloudflare/next-on-pages on Friday and got this error. (Everything was fine a day before).

Vercel version had been up to 31.2.0 this day so maybe that was the problem.
When I tried to add export const runtime = "edge";  to not-found.tsx page I've got this error:

not-found.tsx
export const runtime = "edge";

export default async function NotFoundPage() {
  return (

test

  );
}

Reproduction
No response
Pages Deployment Method
None
Pages Deployment ID
No response
Additional Information
No response
Would you like to help?

[ ] Would you like to help fixing this bug?

Yes. I have the same problem.

Hi @AlexandrNetsvetov thank you very much for the issue 🙂
The second part of the issue is a duplicate of #288
The first could be a very similar issue, it's interesting that it worked on an older Vercel CLI but not on a new one, I'll investigate it
if you could share your code that'd be very helpful 🙏 , if that's not possible, anyways I'd just like to double-check, am I correct in thinking that you're using app directory? (as in pages you'd have 404.tsx/jsx instead I think?)

PS: @BlackBerry009, you as well, if you can share your code that could be very helpful 🙂 🙏  (if you experienced the first part of the issue this is the right place, if you experienced the second part please share info in #288)

@dario-piotrowicz Thanks for your answer.
Yes, I'm using app directory.
I can't share my code but I'm ready to provide you all details that you need.
PS: I've added export const runtime = "edge"; field only because my build had been fallen with first error message. My not-found page used to worked without edge runtime for vercel 31.1.1.

Thanks a lot for the info @AlexandrNetsvetov 😄
I'll investigate and if more info is needed I'll let you know 🙂 🙏

Minimal Reproduction: https://github.com/dario-piotrowicz/next-on-pages-app-not-found-vercel-31-issue-reproduction

My app throw the same error.
Next v13.4.13
cloudflare/next-on-pages v1.5.0

I've just merged #418 which introduces a temporary workaround for this issue, it allows the use of a not-found page as long as it doesn't contain runtime logic
It is not ideal but the best we can do for now, I've marked this issue as blocked by external as we'll have to investigate if maybe Vercel/Next can the generation of serverless functions for such routes on their end

I've tried that solution, but the issue still occurs @dario-piotrowicz.
{
  "devDependencies": {
    "@cloudflare/next-on-pages": "https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/5786546906/npm-package-next-on-pages-418",
  }
}

Build logs in no edge runtime:
22:21:28.531 | ⚡The following routes were not configured to run with the Edge Runtime:
22:21:28.531 | ⚡ - /_not-found
22:21:28.531 | ⚡
22:21:28.532 | ⚡Please make sure that all your non-static routes export the following edge runtime route segment config:
22:21:28.532 | ⚡ export const runtime = 'edge';

Build logs in edge runtime:
22:24:11.400 | ⚡The following routes were not configured to run with the Edge Runtime:
22:24:11.401 | ⚡  - /_error
22:24:11.401 | ⚡
22:24:11.401 | ⚡Please make sure that all your non-static routes export the following edge runtime route segment config:
22:24:11.401 | ⚡ export const runtime = 'edge';

@emrecoban are you sure the prerelease got installed correctly? 😓
can you double check and make sure that next-on-pages tells you that it's using the prerelease version?
(like this)
I just used the prerelease to deploy this application which is getting built correctly and working as expected:
https://ed46310b.next-apps-for-testing.pages.dev/
(If you confirm that you're indeed using the prerelease, can you spot something different between your application and mine that could make yours not work?)

Finally I'm here. Okay, I updated next-on-pages, and then it worked. But I had to add<EMAIL_ADDRESS>package, or something (I'm not sure). Because I couldn't update the package for a while as follow (The message I gave up to send).
_

It seems that the reason I got the error is cloudflare/next-on-pages not updated.
I'm investigating how to update the package to pre-version, but  pnpm throws that error: No matching version found for<EMAIL_ADDRESS>I didn't get why pnpm throws this one.
I've checked the versions of cloudflare/next-on-pages, and have not found  the commit d1839d6.

_
The next issue: I get that error sometimes while I refresh the not-found.js:

Sometimes not-found, sometimes that error.
My guess is that Next.js doesn't catch not-found.js (sometimes, IDK why sometimes) and try to run the server component (fetching data).

@emrecoban awesome! no problem! thanks so much for confirming that's all good now (or at least as good as it can be given our limitations 😅) ❤

same error, so annoying. remix just worked out of the box. I will side with joe armstrong the creator of erlang here RIP, when he said NPM and the node ecosystem is simply wack, taking something that should be smoothly and easily and adding a layer of 3 PhDs required just to deploy a project.

20:37:52.323 | ➤ YN0000: │ /tmp/xfs-76265625 STDOUT Some issues need review, and may require choosing
-- | --
20:37:52.323 | ➤ YN0000: │ /tmp/xfs-76265625 STDOUT a different dependency.
20:37:52.323 | ➤ YN0000: │ /tmp/xfs-76265625 STDOUT
20:37:52.324 | ➤ YN0000: │ /tmp/xfs-76265625 STDOUT Run `npm audit` for details.
20:37:52.869 | ➤ YN0058: │ next-on-pages@https://github.com/cloudflare/next-on-pages.git#commit=5bfbbe15ce14369016992a7cca9f93847851be67: Packing the package failed (exit code 1, logs can be found here: /tmp/xfs-bf62a741/pack.log)
20:37:52.870 | ➤ YN0000: └ Completed in 1m 46s
20:37:52.870 | ➤ YN0000: Failed with errors in 1m 46s
20:37:53.996 | Error: Exit with error code: 1
20:37:53.997 | at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
20:37:53.997 | at Object.onceWrapper (node:events:652:26)
20:37:53.997 | at ChildProcess.emit (node:events:537:28)
20:37:53.998 | at ChildProcess._handle.onexit (node:internal/child_process:291:12)
20:37:54.007 | Failed: build command exited with code: 1
20:37:55.100 | Failed: error occurred while running build command

added like so
    "next-on-pages": "git+https://github.com/cloudflare/next-on-pages.git#5bfbbe15ce14369016992a7cca9f93847851be67",

Does anyone know how to force next-on-pages to be commit or branch bound?

20:58:32.965 | Executing user command: npx @cloudflare/next-on-pages@1
-- | --
20:58:35.048 | npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>
even with this line in package.json it still pulls wrong version
 "next-on-pages": "git+https://github.com/cloudflare/next-on-pages.git#5bfbbe15ce14369016992a7cca9f93847851be67",

@vans163 is there a reason why you can't use the PR's prerelase?
Also since the change made it into main it's also been published in the latest beta

@vans163 is there a reason why you can't use the PR's prerelase?
Also since the change made it into main it's also been published in the latest beta

I did npm i<EMAIL_ADDRESS>  "dependencies": {
    "@cloudflare/next-on-pages": "^0.0.0-705a95b",

I dont get why this keeps happening in the cloudflare pipeline
09:54:20.388 | Executing user command: npx @cloudflare/next-on-pages@1
-- | --
09:54:22.876 | npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>

@vans163 I've checked my app's build logs, and then seen the same warn. You can ignore it.
Just check the devDependencies list:
01:35:41.009 | devDependencies:
01:35:41.009 | + @cloudflare/next-on-pages 0.0.0-54d6325
01:35:41.010 | + @tailwindcss/forms 0.5.4
01:35:41.010 | + vercel 30.0.0
01:35:41.010 |
01:35:41.010 | Done in 29.2s
01:35:41.050 | Executing user command: npx @cloudflare/next-on-pages@1
01:35:47.290 | npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>
Everything is okay in the app now.

@vans163 I've checked my app's build logs, and then seen the same warn. You can ignore it.
Just check the devDependencies list:
01:35:41.009 | devDependencies:
01:35:41.009 | + @cloudflare/next-on-pages 0.0.0-54d6325
01:35:41.010 | + @tailwindcss/forms 0.5.4
01:35:41.010 | + vercel 30.0.0
01:35:41.010 |
01:35:41.010 | Done in 29.2s
01:35:41.050 | Executing user command: npx @cloudflare/next-on-pages@1
01:35:47.290 | npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>
Everything is okay in the app now.
You can install the 54d6325 in your project with:
npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/5786546906/npm-package-next-on-pages-418

Yea same error

10:11:38.298 | ⚡ Completed `npx vercel build`.
-- | --
10:11:40.688 |
10:11:40.689 | ⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
10:11:40.689 | ⚡
10:11:40.689 | ⚡ 	The following routes were not configured to run with the Edge Runtime:
10:11:40.689 | ⚡ 	  - /_error
10:11:40.689 | ⚡
10:11:40.690 | ⚡ 	Please make sure that all your non-static routes export the following edge runtime route segment config:
10:11:40.690 | ⚡ 	  export const runtime = 'edge';
10:11:40.690 | ⚡
10:11:40.690 | ⚡ 	You can read more about the Edge Runtime on the Next.js documentation:
10:11:40.690 | ⚡ 	  https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
10:11:40.690 |
10:11:40.732 | Failed: Error while executing user command. Exited with error code: 1
10:11:40.743 | Failed: build command exited with code: 1
10:11:44.924 | Failed: error occurred while running build command

This is the repo, maybe if you have a chance to look I would really appreciate it. I have no idea whats wrong. It is using the app/ instead of pages/ feature of NEXTJS.  Its a charity project to help out a not-for-profit.
https://github.com/vans163/link

@vans163 I've tried several ways, but couldn't be successful. I am not sure what causes this error. Although I added different versions of next-on-pages (included beta), it threw the same error. I should say that your packages are not working together. Maybe it is related to that.
 WARN  Issues with peer dependencies found
.
└─┬ pliny 0.1.1
  └─┬ kbar 0.1.0-beta.41
    └─┬ react-virtual 2.10.4
      └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.2.0

@vans163 I've tried several ways, but couldn't be successful. I am not sure what causes this error. Although I added different versions of next-on-pages (included beta), it threw the same error. I should say that your packages are not working together. Maybe it is related to that.
 WARN  Issues with peer dependencies found
.
└─┬ pliny 0.1.1
  └─┬ kbar 0.1.0-beta.41
    └─┬ react-virtual 2.10.4
      └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.2.0

So moving the project out was gonna be a pain, I read carefully your PR #418 and hit a eureka. Deleting not-found from the app/ root made it automagically-gandalf-wizardry stop producing the _error artifact after compile. It compiled!

Now its giving
      "message": [
        "EvalError: Code generation from strings disallowed for this context"
      ],

visiting any page on the router lol..

adding a not-found.tsx still gives me the same error. I'm using @cloudflare/next-on-pages CLI v.1.5.1 but also tried the newest beta without a difference.
Is there any specific setting i have to set to get this working, as above is mentioned someone got a successful build.
⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡
⚡      The following routes were not configured to run with the Edge Runtime:
⚡        - /_error
⚡
⚡      Please make sure that all your non-static routes export the following edge runtime route segment config:
⚡        export const runtime = 'edge';
⚡
⚡      You can read more about the Edge Runtime on the Next.js documentation:
⚡        https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes

@emrecoban i found my problem. i used the generateMetadata in the layout. seams like the layout also have to be static if using a not found.

i would have a question about this static rendered 404 page:
I'm using CSP nonce for security reasons and it works fine in the whole app, but not for the 404, as the nonce isn't injected to the code of the 404 pages (as they are static), but the middleware is running and adding the header which results in CSP errors.
I implemented CSP like in this example https://github.com/cloudflare/next-on-pages/discussions/442

Now its giving
      "message": [
        "EvalError: Code generation from strings disallowed for this context"
      ],

visiting any page on the router lol..
EDIT: This is most likely due to the mdx templating engine to turn markdown into html code. Dead end it seems.

Were you able to fix this? I also got the same issue when doing pdx templating engine with contentlayer

@dario-piotrowicz is this fixed under certain branch/pre-release? I tried with your branch but still happening

I was able to get the app to build. I just added the not-found.tsx file to the app folder to resolve the /_not-found bug.
// app/not-found.tsx
export default function NotFound() {
  return (

Not Found

Could not find requested resource

      Return Home

  )
}

Then to overcome the _error issue, I couldn't fix it with the app router custom errors but I just added custom errors to the pages folder.
pages
├── 404.js
└── 500.js

These files are just very simple for now:
// pages/404.js
export default function Custom404() {
  return
404 - Page Not Found

}

// pages/500.js
export default function Custom500() {
  return
500 - Server Error

}

Now the app builds with npx @cloudflare/next-on-pages@1.

the fix @tao mentioned worked for me, in the sense that it got @cloudflare/next-on-pages to build. BUT the only problem is that when the user goes to a not found route (ie /asdf), the /pages/404.js is rendering instead of /app/not-found.tsx. I can work around this by just importing the same component used in /app/not-found.tsx but this seems hacky especially since I'm trying to use only the app router.
I guess this proves further that @cloudflare/next-on-pages has issues with error and not found pages in the app router when they use the edge runtime, but not for the pages router.
@dario-piotrowicz appreciate anything you can do for this 💪

@emrecoban i found my problem. i used the generateMetadata in the layout. seams like the layout also have to be static if using a not found.
But this doesn't show the warning for the dynamic not-found page

This is the case for me as well.
When I added export const runtime = 'edge'; to app/layout.jsx, @ cloudflare/next-on-pages would fail to build. When I removed the runtime export, builds started working again.

@brianfryer my workaround currently by creating export const runtime edge on the layout, and force the not-found tsx use nodejs runtime, somehow its working

@brianfryer my workaround currently by creating export const runtime edge on the layout, and force the not-found tsx use nodejs runtime, somehow its working

🙃. I’m gonna give that a shot today.

Basically to recap, I implemented the fix in https://github.com/cloudflare/next-on-pages/pull/418 and it ""fixes"" the not-found issue in the sense that:

if you have a static app/not-found.tsx it uses it with no problems
if you have an app/not-found.tsx with server logic then it still breaks, but the eslint-plugin at least warns you about that

(as described here)
I just checked and the above works as intended (I just tested it with the minimal reproduction I created, with the latest package versions).
Now the issue that people are experiencing is that it you have a static app/not-found.tsx AND an app/layout.tsx with server side logic, then the build fails because of the _error issue again 😕 (I checked it here and it does break the build unfortunately) , so that's the problem right? that the solution implemented above breaks when you add such an app/layout.tsx, am I correct? is there anything else I'm missing or does this sums it up?

If the above is correct I am afraid that the only solution will be to say that we can't do anything about that and say that if you've got an app/not-found.tsx then also app/layout.tsx can't contain server side logic 😓 (and unfortunately I don't know if we'll be able to add an eslint plugin that help such case 😓)
But regardless before throwing in the towel I'll try to explore this and see if anything better can be done 😢

It seems like not found and error pages/routes are auto generated on build when you don't define app/not-found.tsx.
I don't have app/not-found.tsx and I had to remove server side logic from app/layout.tsx to make the build work again.
I'm on Next.js version 13.5.4, using only App Router, and building with npx @cloudflare/next-on-pages@1

It seems like not found and error pages/routes are auto generated on build when you don't define app/not-found.tsx.
I don't have app/not-found.tsx and I had to remove server side logic from app/layout.tsx to make the build work again.
I'm on Next.js version 13.5.4, using only App Router, and building with npx @cloudflare/next-on-pages@1

could you write example app/layout.tsx?

@microooji Sure. Example app/layout.tsx:
import './globals.css'
import { Inter } from 'next/font/google'
import { cookies } from 'next/headers';

const inter = Inter({ subsets: ['latin'] })

export const runtime = "edge"; // <--  Specifying edge runtime.

export const metadata = {
  title: 'Create Next App',
  description: 'Generated by create next app',
}

export default function RootLayout({
  children,
}: {
  children: React.ReactNode
}) {
  console.log(cookies().get('some-cookie')); // <-- reading cookies turning route into dynamic rendering.

  return (

      {children}

  )
}

Without app/not-found.tsx, this is the error I see:

Been having the same issue as you folks mentioned.
What ended up working for me now (PS: I'm using src/app folder):

Have a src/app/error.tsx with "use client" directive
Have a src/app/not-found.tsx with "use client" directive
Have a src/pages/404.js (No directive)
Have a src/pages/404.js (No directive)
Specify the edge runtime in my src/app/layout.tsx.

Aside from that, the usuals. :)
If it helps. This is a permalink to the commit that worked in our project 😄
https://github.com/JSConfCL/turuleca/tree/c9b2060aab57f7d0c0bb5b56ff56f6ffa231c10a

Though now we are getting some client-side errors. https://ad924d6e.turuleca.pages.dev/
Error: NextRouter was not mounted
Application error: a client-side exception has occurred (see the browser console for more information).

After trying several things the only solution that worked for me was to remove export const runtime = "edge" from both my not-found.tsx and app/layout.tsx.

Been having the same issue as you folks mentioned.
What ended up working for us. Which fixes the deploy, but still fails a runtime
* Have a `src/app/error.tsx` with `"use client"` directive

* Have a `src/app/not-found.tsx` with `"use client"` directive

* Have a `src/pages/404.js` (No directive)

* Have a `src/pages/404.js` (No directive)

* Specify the edge runtime in my `src/app/layout.tsx`.

(PS: I'm using src/app folder):

Aside from that, the usuals. :)
If it helps. This is a permalink to the commit that worked in our project 😄 https://github.com/JSConfCL/turuleca/tree/c9b2060aab57f7d0c0bb5b56ff56f6ffa231c10a

Though as mentioned, now we are getting some client-side errors. ad924d6e.turuleca.pages.dev
Console
Error: NextRouter was not mounted

FYI this worked for us. Thanks!

Realized that my issue is most likely due to middleware.ts and the clerk provider. WIll ideally work on it and see if it solved. Glad i helped @YoranBrondsema

Guys I have this error with Page Router, too. not sure if it's the same error.

⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
--
23:52:13.699 | ⚡
23:52:13.699 | ⚡ 	The following routes were not configured to run with the Edge Runtime:
23:52:13.699 | ⚡ 	  - /_next/data/T2unbIx1RCCAyFtaJjxro/brands/[...id].json
23:52:13.699 | ⚡ 	  - /_next/data/T2unbIx1RCCAyFtaJjxro/designers/[...id].json
23:52:13.699 | ⚡ 	  - /_next/data/T2unbIx1RCCAyFtaJjxro/news/[...id].json
23:52:13.699 | ⚡ 	  - /_next/data/T2unbIx1RCCAyFtaJjxro/products/[...id].json
23:52:13.699 | ⚡ 	  - /_next/data/T2unbIx1RCCAyFtaJjxro/products/category/[...category].json
23:52:13.699 | ⚡ 	  - /_next/data/T2unbIx1RCCAyFtaJjxro/products/sub-category/[...sub-category].json
23:52:13.700 | ⚡ 	  - /brands/[...id]
23:52:13.700 | ⚡ 	  - /designers/[...id]
23:52:13.700 | ⚡ 	  - /products/[...id]
23:52:13.700 | ⚡ 	  - /products/category/[...category]
23:52:13.700 | ⚡ 	  - /products/sub-category/[...sub-category]
23:52:13.700 | ⚡
23:52:13.701 | ⚡ 	Please make sure that all your non-static routes export the following edge runtime route segment config:
23:52:13.701 | ⚡ 	  export const runtime = 'edge';

All these paths have getStaticPaths function.

I tried to add export const runtime = 'edge' to these pages, it will complain Error: Page /news/[...id] provided runtime 'edge', the edge runtime for rendering is currently experimental. Use runtime 'experimental-edge' instead.
IF I swith to experimental-edge, it will complain > webpack config.resolve.alias was incorrectly overridden. https://nextjs.org/docs/messages/invalid-resolve-alias
Tried to add the export const runtime = 'edge' to layout, it build OK but failed on deployment.

@vader1359 I'm pretty sure you're experiencing something different, would it be possible for you to create a minimal reproduction of it to share and open a new issue for it?

What ended up working for me was:

Removing export const runtime = 'edge' from the app/layout.tsx file
Adding export const runtime = 'edge' to each page/routes and to app/not-found.tsx

I get the error message about the missing edge runtime on the _not-found and _error route (both files do not exist in this project) when I try to work with next/headers in the layout.tsx file.
Once I remove this everything is fine.

@dario-piotrowicz Any updates? do you think this is going to be fixed soon?

@anonymouscatcher this issue seems caused by how Vercel builds functions and it is a bit of our control to fix, one possible solution I thought of was allowing users to ask next-on-pages to ignore invalid routes as sometimes those are actually ok to ignore (like in the layout/not-found case mentioned in this thread and reproduced in this application).
I implemented that here: https://github.com/cloudflare/next-on-pages/pull/497, the PR hasn't made much progress since I was trying to get the team's feedback on this since it's really not a super elegant solution.
if you could, could you just the prerelease a try and let me know what you think? I would surely appreciate external feedback on this.
If the solution above works reasonably well for people I think I can push for it with the team and merge it soon, so again I'd be very thankful if people could give it a go and let me know if it works for them :slightly_smiling_face:

Hey @dario-piotrowicz I tried installing your prelease and making it build, but unfortunately still get the
The following routes were not configured to run with the Edge Runtime:
⚡        - /_error

Error :(

@maghfoor-dev but you also should get there a message saying that you can ignore that route right?
Did you try then to add -g=_error?

@dario-piotrowicz
I didn't try to do that sorry, do you mean adding that in the build command?
I fixed this by trying to find out what actually was causing the issue. For me it was the layout.tsx page being an async component because I wanted to pass the auth SessionProvider to my app. I removed that and my project built. Weird behaviour but yeah

My personal take:
if _error gets falsely interpreted/generated as route, the solution should not the to ignore that entry, but to not generate it in the first place.
Wouldn't that be a bug/responsibility within vercel? Didn't see any issues there mentioning this. (my 4th day of next - don't know)

The above solution did not solve my problem. There is still an _error problem. I have temporarily given up deploying to cloudflare.

Hi all, this popped into my head just earlier, but you can probably do something like the following for your build command as a temporary workaround. The real fix would be Vercel resolving this.
npx vercel build; rm -rf .vercel/output/functions/_not-found*; rm -rf .vercel/output/functions/_error*; npx @cloudflare/next-on-pages --skip-build

removing app/not-found.tsx fixed it temporarily
https://github.com/always-maap/NIT-Academy

Hi all, I've opened #585 to fix this issue, the changes make it so that invalid _error functions generated when you have a layout that uses the edge runtime and also a static not-found route get ignored.
You still however cannot have a not-found route using the edge runtime.
Please give the prerelease a try and let me know if it works for you 🙏

PR https://github.com/cloudflare/next-on-pages/pull/585 has closed this issue, although the situation is still not perfect I would keep this issue closed so not to keep the conversation going, making it too diluted/unfocused
What things should work like right now in applications using the App router (in the latest beta release and from the next stable release):

not-found routes need to be static and not have server side logic (as per https://github.com/cloudflare/next-on-pages/pull/418), if they do the build process is expected to fail

assuming that the app has a static not-found route, the app can have a root layout that does have server side (edge) logic (as per https://github.com/cloudflare/next-on-pages/pull/585)

If you see that any of the two points above doesn't work as expected please comment here and we can reopen this issue, if you spot anything else please let's open a new issue focused on that specific problem 🙏
Sorry for the trouble here, this one is a bit of a painful issue, hopefully the latest changes help the situation 😅

@dario-piotrowicz after adding middleware.ts to the bootstrapped default nextjs project (npx create-next-app@latest) as per their docs (literally copy-paste), I've got the following error:

And after adding missing pages and marking all as export const runtime = "edge";,

I still get this:

(latest available)
Does it mean no way to run it on Cloudflare?

@xanderim thanks for confirming that the latest beta release does work 🙂
I've just cut a standard release so using the latest stable release should work fine now 🤞
@nikitaeverywhere please give it a try and let me know if it works for you 🙂

@xanderim @dario-piotrowicz thanks for the feedback. I changed the build command in CloudFlare page settings, and both "latest" npx @cloudflare/next-on-pages@1 and npx<EMAIL_ADDRESS>work as of now.
nextjs 14 is however totally incapable of handling CSP but that's unrelated :D
Thanks.

@nikitaeverywhere I'm glad things work for you now 😄 🚀
Regarding Next.js 14 and CSP, sorry I am not aware of the incompatibility you're mentioning, is that something totally on Next.js? or is it something caused by our adapter? (if it's the latter please open a new gh issue for that, so that we can look into it 🙏)

Regarding Next.js 14 and CSP

@dario-piotrowicz it's on the NextJS side completely. I personally think NextJS is just not designed to support CSP. You can find a lot of lengthy threads with other people suffering.
So, as for Cloudflare, no worries at all :D

I see @nikitaeverywhere I'm glad that it's not something we're causing 😄 (but of course I'm sad that Next.js seem to present this many issues around CSP 🥲)
Anyways thanks a ton for sharing the Next.js issue, I gave it a quick scan through and it does feel like something something that could definitely come in handy to be aware of and keep in mind! so again thanks a bunch! ❤

I still have this issue locally, I have only one not-found.js in top level

seeing this same issue myself, has anyone found a solution? (generally wouldn't bump but its 2.5 months old)

Hey all, I've built on top of morphic but everytime the search results post, the app re routes to the home page ?

For others experiencing this issue, upgrading from "vercel": "^31.1.0" to "vercel": "^32.4.1" (latest) in the Next.js project I was trying to build for pages fixed this for me.

Upgrading the vercel dependency did not fix the error in my project, however I've seen successful builds by entirely removing the _error directory before running Next on Pages.
npm run build; rm -rf .vercel/output/functions/_error*; npx @cloudflare/next-on-pages --skip-build
This command was written by @james-elicx in the Cloudflare Developers Discord.

Sorry for the late reply (I don't really notice much comments on closed issues 😓)
@anonymouscatcher and @DeJayDev if you experience the _error problem, please feel free to open a new issue for it with a minimal reproduction 🙏 (emphasis on the minimal reproduction, since, without one I feel like it's going to be very difficult to get to the bottom of things 😓).
PS: @DeJayDev, please note that the command you shared (from @james-elicx) is (at least in my opinion) not really safe as that completely removes the problematic file without any guarantee that the application will run correctly in production (if you want you can indeed use it, but in that case you'd probably also want to very very thoroughly test that the built application works as intended before deploying it (with wrangler pages dev))


Just can find this? Customize the Group Buttons

Summary of problem or feature request
Hi, I have spent the better part of 2 days customizing the table look and feel -- the last area I just cant seem to find where or how to is the Group Buttons from Select All to Delete Selection

 I want to add padding far left and in-between, and group position them center  and finally  color to each?

IMAGE of challenge:

System details
Composer version 2.3.5
node -v17.5.0
Laravel Installer 4.2.10
PHP 8.0.17

Operating System: Windows 11
PHP Version: "php": "^8.0",
Laravel Version: "laravel/framework": "^8.0",
Laravel-Datatables Version: "yajra/laravel-datatables-oracle": "^9.9"
Bootstrap CSS

Quick answer, make sure you have the dataTables buttons css loaded on your site.
Also, better check datatables.net forum to get better results as this is already a js/css issue. Thanks!

as you can see I have the necessary Button CDN (which i converted to a file to allow me to try and customize this.)
Yet sadly a still am not able to?
Your advice would be appreciated
I see in the datatables.net docs the following:
#section
https://datatables.net/extensions/buttons/#Displaying-the-buttons
Any change someone has an example for me (i am still VERY young in JS) yet if you can show me how to I will could learn by this - Please?
<as you can see in the image in 1st comment above my exact need and reference>

I assume something like this:
var table = $('#example').DataTable( {
    buttons: [
        'copy', 'excel', 'pdf'
    ]
} );

table.buttons().container()
    .appendTo( $('.col-sm-6:eq(0)', table.table().container() ) );

This is an example from Datatables.net -- yet i am unsure on how to proceed

Please sir - I would love to know how to place these buttons correctly?

I assume something like this:
var table = $('#example').DataTable( {
    buttons: [
        'copy', 'excel', 'pdf'
    ]
} );

table.buttons().container()
    .appendTo( $('.col-sm-6:eq(0)', table.table().container() ) );

This is an example from Datatables.net -- yet i am unsure on how to proceed

This only makes them disappear - I am sure i am not understanding properly

The screenshot you posted is almost correct and just missing a piece of css in the library. Make sure buttons css files are loaded correctly.
You can also achieve the layout you want by using the dom option


Fixes type annotations and adds mypy

Hello @ribeiro-rodrigo I just saw your're the maintainer of this project. First of all, I really appreciate you've adopted type annotations here ❤
But to ensure we put the correct types we need to check them with mypy.
So I've added mypy as a development dependency and fixed all errors showed by tests, in addition I did a little code refactor just to complain with some Python styles (import order, empty lines e etc.).
I also created a GitHub test workflow to run mypy tests on pushs or PRs!
If you need some help to understand anything, keep me in touch.

Hello @thepabloaguilar. Thank you for the excellent contribution. I'm adding your changes to the master.
Thank you!!