Read article content using goose retrieving nothing

I am trying to goose to read from .html files(specified url here for sake convenience in examples)[1]. But at times it's doesn't show any text. Please help me out here with the issue.
Goose version used:https://github.com/agolo/python-goose/ Present version gives some errors.
from goose import Goose
from requests import get
response = get('http://www.highbeam.com/doc/1P3-979471971.html')
extractor = Goose()
article = extractor.extract(raw_html=response.content)
text = article.cleaned_text
print text
Link to same question asked at stackoverflow:
http://stackoverflow.com/questions/30381944/read-article-content-using-goose-retrieving-nothing

from goose import Goose
g = Goose()
url = 'http://www.highbeam.com/doc/1P3-979471971.html'
article = g.extract(url=url)
article.title
u'Tamil Nadu appoints Commission to look into Chennai stampede deaths - Hindustan Times (New Delhi, India)'

@JoshYuJump the OP was talking about the cleaned_text field which is the body of the article, not title.
I posted an answer on SOF, it's not a bulletproof solution but indeed Goose uses it as a part of the algorithm.


[HUDI-5029] Enable incremental timeline sync by default

Change Logs
Enable incremental timeline sync by default.
Impact
The file system view is incrementally updated as new actions are performed on the timeline.
Risk level: medium
Could have a performance impact but first, we want to check that is functionally correct.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure


Use approveAndCall pattern for requestRedemption

approveAndCall reduces our UX from two transactions to one (see https://github.com/keep-network/tbtc/issues/273). This implements approveAndCall for the requestRedemption step in the dApp.
Currently still blocked by vending machine updates in https://github.com/keep-network/tbtc/pull/390.
Blockers: https://github.com/keep-network/tbtc/pull/390
Epic: https://github.com/keep-network/tbtc/issues/273

Closing this for now in favor of #201.

Omg did I say I was closing this and forget to hit the “close” button? 😂😂😂


Fix/readme v2

Description
Improves  README inline with this document.
Fixes # (issue)
https://github.com/appsmithorg/appsmith/issues/1166

@pric-appsmith Minor: Can we bring back the emojis? 😄

Leaving my global comments here:

We need to reduce the number of files that show up before the user can read a single line of the readme. Today the readme is an entire scroll away.
Please remove the logo(nobody cares about our logo except for us :)) and reduce the empty space below it which doesn't say much.
Does the line of GitHub badges really need to be the first thing someone reads after our name? They say nothing of value and only increase scroll length
Why does Appsmith exist should be the very first line of the read me.
So the first thing a user should read is some variation of this: Appsmith was created to build custom internal tools really quickly. Our visual MVC Framework gives you UI widgets, DB integrations, API connectors, and user management features that reduce repetitive work. The current line says things that you don't have to do and then the next line explains what Appsmith is.

@areyabhishek

We need to reduce the number of files that show up before the user can read a single line of the readme. Today the readme is an entire scroll away.

Agreed.

Please remove the logo(nobody cares about our logo except for us :)) and reduce the empty space below it which doesn't say much.

It's true that readers don't care about the logo. However, IMO -

The logo sets the stage for the details. It's a good starter.
To compare the options - logo+Appsmith-text against Appsmith-text written on an image. The former, IMO, is better simply because picture+text looks better than just text - when both of them are images. Picture is easier to remember. Also both the options are currently taking roughly the same amount of screen-space, so we aren't saving users from an extra scroll.
The proposal of having no image at all - an only a Heading-text saying Appsmith, is IMO, going overboard because GitHub users are used to seeing a logo, a byline, and then the details; and hence used to scrolling away quickly from there on.
To summarize - I think we should have the logo, may be smaller in size.

Does the line of GitHub badges really need to be the first thing someone reads after our name? They say nothing of value and only increase scroll length

I agree. I refrained from proposing a rethinking of them earlier because I am not entirely sure of how GitHub users judge repositories since I've not been an open-source contributor. I'll take the liberty to share my opinion on them now.

From my experience of being a user of open-source products, I can say that I'd want to first know whether the repository is useful for me, and second the legalities around forking it to build something on top of it.
Badges should exist only when they convey something of value, and when those badges are the best way to give that value. Going by this principle, maybe all current badges can be gotten rid of.
I feel the same about emojis :)

Why does Appsmith exist should be the very first line of the read me.
So the first thing a user should read is some variation of this: Appsmith was created to build custom internal tools really quickly. Our visual MVC Framework gives you UI widgets, DB integrations, API connectors, and user management features that reduce repetitive work. The current line says things that you don't have to do and then the next line explains what Appsmith is.

Agreed. I'll come up with the changes.

Also, we use MVC in the first line, but then don't expand on it. It feels like it was just used for the sake of it.

I absolutely agree. @Nikhil-Nandagopal and I had had a quick conversation on the same lines - that since the MVC bit about it is not clear, IMO, it is rather confusing as the introductory line. If you can may be help me understand briefly the discussions the Appsmith team has had regarding this phrase - how and why they came up with it, etc., it'll help me come up with the changes, and also give an opinion on whether we should use the phrase at all. As of today, I think we shouldn't.

@areyabhishek

We need to reduce the number of files that show up before the user can read a single line of the readme. Today the readme is an entire scroll away.

Agreed.

Please remove the logo(nobody cares about our logo except for us :)) and reduce the empty space below it which doesn't say much.

It's true that readers don't care about the logo. However, IMO -

The logo sets the stage for the details. It's a good starter.
To compare the options - logo+Appsmith-text against Appsmith-text written on an image. The former, IMO, is better simply because picture+text looks better than just text - when both of them are images. Picture is easier to remember. Also both the options are currently taking roughly the same amount of screen-space, so we aren't saving users from an extra scroll.
The proposal of having no image at all - an only a Heading-text saying Appsmith, is IMO, going overboard because GitHub users are used to seeing a logo, a byline, and then the details; and hence used to scrolling away quickly from there on.
To summarize - I think we should have the logo, may be smaller in size.
Make sense.

Does the line of GitHub badges really need to be the first thing someone reads after our name? They say nothing of value and only increase scroll length

I agree. I refrained from proposing a rethinking of them earlier because I am not entirely sure of how GitHub users judge repositories since I've not been an open-source contributor. I'll take the liberty to share my opinion on them now.

From my experience of being a user of open-source products, I can say that I'd want to first know whether the repository is useful for me, and second the legalities around forking it to build something on top of it.
Badges should exist only when they convey something of value, and when those badges are the best way to give that value. Going by this principle, maybe all current badges can be gotten rid of.
We'll need a way to point users towards Discord so that badge can probably be pushed down. But these badges aren't very readable. An actual button with Discord icon would have more impact.

There's no clear call to action on the page and our main objective is to get the user to try Appsmith cloud. So what about a single CTA button that says "Try Appsmith" and links to the sign up page?

I feel the same about emojis :)
Today they serve as guides for the users that are scanning and scrolling. Websites use icons to organize and guide a reader who is scanning. Without these visual breaks, the page just looks monotonous. Our choice icons could be better for sure.

Why does Appsmith exist should be the very first line of the read me.
So the first thing a user should read is some variation of this: Appsmith was created to build custom internal tools really quickly. Our visual MVC Framework gives you UI widgets, DB integrations, API connectors, and user management features that reduce repetitive work. The current line says things that you don't have to do and then the next line explains what Appsmith is.

Agreed. I'll come up with the changes.

Also, we use MVC in the first line, but then don't expand on it. It feels like it was just used for the sake of it.

I absolutely agree. @Nikhil-Nandagopal and I had had a quick conversation on the same lines - that since the MVC bit about it is not clear, IMO, it is rather confusing as the introductory line. If you can may be help me understand briefly the discussions the Appsmith team has had regarding this phrase - how and why they came up with it, etc., it'll help me come up with the changes, and also give an opinion on whether we should use the phrase at all. As of today, I think we shouldn't.

This is why we've been discussing MVC:

Users need to understand the architecture of how things are built in Appsmith so that they can understand how things interact with each other. Some devs described Appsmith to be similar in architecture like Angular or RoR. We thought describing Appsmith as MVC is a potential shortcut
In Appsmith world, model=data sources, view=widgets, controller=JS logic(we are building a dedicated section for JS logic)
So the idea was if a developer understands these concepts, they'll be able to build quicker and debug faster. They'll never have to think, 'So where do I go fix this problem?'. This architecture will also help us design features in a way that doesn't break their mental models

@Nikhil-Nandagopal Resolved comments. Please see if it can be approved.


[PLUGIN-1780]changes done for GCS multisink issue.

PLUGIN-1780 changes done for GCS multisink issue.
GCS MultiSink plugin is failing while having Flexible schema set as true.
io.cdap.plugin.gcp.gcs.sink.DelegatingGCSRecordWriter.close() method has a problem. It commits the job in a single partition close to the executor and not in the driver. This has the logical problem of commiting partially and too early, but also when a lot of partitions are committed at once (as it happens with datacacher).
This PR is copy of https://github.com/data-integrations/google-cloud/pull/1406
as it was containing merge commit.

Bigtable e2e are failing due to some other reason, PR raised for that fix separately. https://github.com/data-integrations/google-cloud/pull/1413


[IOS] Test Crash when add package mobile_scanner in pubspec.yaml

Steps to reproduce

App test with patrol work normally
just add new dependency call mobile_scanner: ^5.1.1 into pubspec.yaml
Start app is working normally
Start execute test with patrol got crashed.

Actual results
Sorry, I don't know this problem come from package mobile_scanner or from patrol but app is run normally with mobile_scanner. It's only crash on test.
Logs

Logs
• Building app with entrypoint test_bundle.dart for iOS simulator (debug)...
✓ Completed building app with entrypoint test_bundle.dart for iOS simulator (27.0s)
• Running app with entrypoint test_bundle.dart for iOS simulator on simulator iPhone 15 Pro...
        --- xcodebuild: WARNING: Using the first of multiple matching destinations:
        { platform:iOS Simulator, id:F4165E75-5981-42F6-9DD2-2DBC29E920DE, OS:17.5, name:iPhone 15 Pro }
        { platform:iOS Simulator, id:F4165E75-5981-42F6-9DD2-2DBC29E920DE, OS:17.5, name:iPhone 15 Pro }
        2024-07-22 16:05:09.060 xcodebuild[33294:2051983] [MT] IDETestOperationsObserverDebug: 39.028 elapsed -- Testing started completed.
        2024-07-22 16:05:09.060 xcodebuild[33294:2051983] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
        2024-07-22 16:05:09.060 xcodebuild[33294:2051983] [MT] IDETestOperationsObserverDebug: 39.028 sec, +39.028 sec -- end
        Testing failed:
                RunnerUITests-Runner (33302) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal abrt before starting test execution.))

        ** TEST EXECUTE FAILED **

✗ Failed to execute tests of app with entrypoint test_bundle.dart for iOS simulator on simulator iPhone 15 Pro (xcodebuild exited with code 65) (42.3s)
Error: xcodebuild exited with code 65
See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.

Patrol version
patrol: ^3.9.0
Patrol Doctor output

Patrol Doctor output
Patrol doctor:
Patrol CLI version: 3.0.1
Flutter command: flutter
  Flutter 3.22.3 • channel stable
Android:
• Program adb found in /Users/mrrhak/Library/Android/sdk/platform-tools/adb
• Env var $ANDROID_HOME set to /Users/mrrhak/Library/Android/sdk
iOS / macOS:
• Program xcodebuild found in /usr/bin/xcodebuild
• Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output
[✓] Flutter (Channel stable, 3.22.3, on macOS 14.5 23F79 darwin-arm64, locale en-US)
    • Flutter version 3.22.3 on channel stable at /Users/mrrhak/Documents/Developments/SDK/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0850beeb2 (5 days ago), 2024-07-16 21:43:41 -0700
    • Engine revision 235db911ba
    • Dart version 3.4.4
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/mrrhak/Library/Android/sdk
    • Platform android-35, build-tools 35.0.0
    • ANDROID_HOME = /Users/mrrhak/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] VS Code (version 1.91.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.92.0

[✓] Connected device (4 available)
    • iPhone 15 Pro (mobile)          • F4165E75-5981-42F6-9DD2-2DBC29E920DE • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-17-5 (simulator)
    • macOS (desktop)                 • macos                                • darwin-arm64   • macOS 14.5 23F79
      darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad                • darwin         • macOS 14.5 23F79
      darwin-arm64
    • Chrome (web)                    • chrome                               • web-javascript • Google Chrome
      126.0.6478.183
[✓] Network resources
    • All expected network resources are available.

• No issues found!

Hi, I am not able to reproduce that behavior, could you set up some example repo so I can invesitgate it deeper?

Thank @fylyppo, Here is an example repo: https://github.com/mrrhak/myapp

Hi @mrrhak. Thanks for the reproducible sample. I checked the issue and in the logs it says that:

This copy of libswiftCore.dylib requires an OS version prior to 12.2.0.
2024-07-25 19:32:38.803238+0200 RunnerUITests-Runner[30802:12703449] This copy of libswiftCore.dylib requires an OS version prior to 12.2.0

After changing deployment target to 12.2 for RunnerUITests the test was executed successfully.

Closing this issue. If the same solution won't work for you, feel free to reopen it and provide more info.

Yes, after change to 12.2 it's working. Thanks for your support.


Development v1.1

Branch v.1.1 / Master
Same thing as #1 (who will be v.1.0)
Difference is a version bump and removal of cart_decorator.js and override (which was added before the fork between my branch so not in this fork) who added missing params for automated translations of cart_link

@dangerdogz as I merged #1 could you please rebase your branch with master, fix merge conflicts and force push your branch again, thanks.
PS: Please do not raise the version. That's what we do. Thank you :smile:

Here you go,
Sorry about the version :smile:

Thanks. No worries :tulip:
PS: We need to harden the tests. Maybe I'll find some time to fix 'em /c @alepore @jhawthorn

From me :+1: @alepore ?


Fix aggregation mode visitor for containments

In one of the rewrites of the aggregations mode visitor we / I missed updating how we handle containment nodes.
This PR resolves same.

LGTM :+1:  :shipit:


Event listing on nixos.org

Note that there's also a pretty big event listing on https://nixos.org/community/, though it's not very nice (ideally I'd like to see a world map with all the meeting points!). Are you maybe interested in working on improving this on the homepage directly? https://github.com/NixOS/nixos-homepage

The events listed there are mostly dead, I scraped the ones that were not dead by hand. It seems that nobody is maintaining that list, only 2 or 3 are still alive. They are now listed on nix.ug. I think a world map would be nice, but I  also think it could be over-engineering. it just adds more JavaScript to maintain, I like simple, queryable directory listings.
The nix.ug page is generated with Homer. If you think you could add a new type to https://github.com/bastienwirtz/homer that allows a user to specify co-ordinates and attach links to those datapoints, I think that would be an awesome way of making it simple to specify and re-use.
I think this would be useful for Homer users, to do something like specify a list of IP addresses and where they're located on the planet. So if anybody implemented this in Homer,  it would kill two birds with one stone by implementing a feature that is more generic and re-usable by more people.
If you have some JavaScript that just lets me specify datapoints in JSON/TOML and generates the map you want, then we can work on embedding that on nix.ug. Similarly, I can also imagine nix.ug being embedded on the nixos-homepage as it is also a static site that can go inside of an iframe.


[SPARK-43861][CORE] Do not delete inprogress log

What changes were proposed in this pull request?

After https://github.com/apache/spark/pull/38983 PR is merged, Spark History Server deletes inprogress logs created before expiration date even if it's still running.
So I add condition for check log's completed flag.
Why are the changes needed?

Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test
Was this patch authored or co-authored using generative AI tooling?

Thank you for making a PR, @bluzy . Could you elaborate about the problem, specifically, in progress logs created before expiration date? What is your configuration for spark.history.fs.cleaner.maxAge?

Spark History Server deletes inprogress logs created before expiration date even if it's still running.

@dongjoon-hyun
spark.history.fs.cleaner.maxAge is 14d, and my spark streaming application is started 14 days ago.
Spark history server deleted the spark streaming app's log file by it's modification date, and then error occurs like:
java.io.FileNotFoundException: File does not exist: /user/pdd-dev/log/spark/application_1711009858797_276181.inprogress (inode 230295719) Holder DFSClient_NONMAPREDUCE_-582659247_1 does not have any open files.
	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkLease(FSNamesystem.java:2890)
	at org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.analyzeFileState(FSDirWriteFileOp.java:605)
	at org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.validateAddBlock(FSDirWriteFileOp.java:172)
	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2769)
	at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:875)
	at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:561)
	at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
	at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
	at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
	at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
	at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1729)
	at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)

+CC @HeartSaVioR

Thanks, @bluzy . I understand your situation. Why don't you increase spark.history.fs.cleaner.maxAge?
Although I understand it's controversial, spark.history.fs.cleaner.maxAge is defined like the following.

https://spark.apache.org/docs/latest/monitoring.html

First, they're deleted if they're older than spark.history.fs.cleaner.maxAge.

Note that when driver crashes, the event file remains with .inprogress suffix.
Not deleting these files would result in filling up the event directory - and eventually fail all jobs (depending on the fs limits for number of files per dir).

Yes, Mridul's comment is correct. I believe the AS-IS behavior is robust and safe and intended one instead of a bug.
WDTY, @bluzy ?

@dongjoon-hyun @mridulm
I think incorrect inprogress file would be deleted on cleaner's schedule, isn't it?
I concen that many spark streaming application can lives forever until needs to be upgraded. It's difficult to set spark.history.fs.cleaner.maxAge value while running streaming job.

PTAL @dongjoon-hyun @mridulm

reader.completed is checking for the IN_PROGRESS suffix - which will be the case here @bluzy: and so with this PR, it will never clean up those files.
(Some users/deployments have out of band workflows that do the move to remove the IN_PROGRESS suffix - but they are not part of Apache Spark itself)


how to  obtain chain information from any two assemblies

I want to obtain the chain information from my assemblies,how to get it, thanks~

thanks for your reply, Can I create this file myself？ I want to use my assembled genome to liftover  ref genome

interesting. Yes, it should be possible to create a liftover chain file - for example from a VCF, but I don't have any prior experience with this. You may find this thread to be relevant https://github.com/marbl/CHM13/issues/15 - it talks about the chain file recently created for the t2t assembly.

thanks~


Clicking a change of a PR which is currently checked out should use the actual file on disk

Currently, when clicking on such a change, we still use a temp file, as mentioned in #27.

@joaomoreno you talk about the "Changes in Pull Request" files? The question here is what should happen when I have changes on top of the PR. This is somehow similar to the git extension, when you have changes staged. When you click the staged file you see the version that's staged, not the one your workspace contains.

That's a great point. We should be a bit more clear as to what the difference between the two trees actually is.

This has already been completed, the "Change in Pull Request" tree should diff with the actual file on disk and should allow opening it directly


[Android] Decouple XWalkView from the activity

Originally, XWalkView is designed to be tightly bound to the activity
that creates and holds it, and to listen the state change and activity
result, which will cause following problems:

With the change of the container activity's life cycle, XWalkView will
pause all timers and other components like videos when activity
paused, which is not suited to the usage in background.
Single XWalkView can't be shared across multiple activities.
XWalkView must be created in an activity, it can't be used for a
service.
A XWalkView object will be destroyed after its container activity
died and can't be used anymore.

To solve the problems above, we decided to decouple XWalkView from the
activity and give the developer more freedom to handle it. This patch
does following things:

XWalkView can be created and held in any context, including a service.
XWalkInitializer and XWalkUpdate don't have to be created in an
activity, they support to initialize Crosswalk environment in any context.
XWalkExternalExtensionManager doesn't handle the activity result anymore.
The implementation of the file chooser in XWalkView is separated to
a individual class called XWalkFileChooser. Because it needs to receive
an activity, it can't be integrated into internal library as default
file chooser. So move it from org.xwalk.core.internal to org.xwalk.core
as a new API, the developer has to invoke it manually in
XWalkUIClient.openFileChooser.
Use the application context instead of the activity in
XWalkPresentationHot and BuiltinXWalkExtensions to avoid memory leak.

BUG=XWALK-7002
BUG=XWALK-7188
BUG=XWALK-7189
BUG=XWALK-7190
BUG=XWALK-7191
BUG=XWALK-7192
BUG=XWALK-7193
BUG=XWALK-7197
BUG=XWALK-7198
BUG=XWALK-7199

I don't understand why this was merged so quickly and without any review if we're just going to start Crosswalk 23's life cycle. #3821 was reverted because it caused a lot of regressions, yet the pull request message is identical to the previous one and says zero about how this new version avoids breaking API and does not cause the regressions previously reported.

Given that the branch is today, this is too risky, can we merge it in master after 22 has branched? Also, please don't merge PRs without reviews, thanks!

22.52.561.0 will likely not include it anyway, but even if it does we can just revert the commit in the branch (with an explanation), so branching is still going to work.

@rakuco this pull request has been reviewed previously, but then caused some bugs and was reverted. This update is just to fix those bugs.

@rakuco this pull request has been reviewed completely previously, but then it caused some bugs and was reverted. The difference between this update and previous pull request is just bug fixing.

That's one of the things I'm complaining about: how is anyone supposed to know what changed if you send a pull request with the exact same message and merge it shortly after it has been uploaded? It's impossible to know how you fixed those bugs (which were not minor) and whether the fixes make sense and how they interact with the rest of the code. Just look at any sane open source project in the wild: whenever a patch series is sent more than once, there must be a list of changes between each version for other people to understand what's going on.

About the risk, this feature has been being developed from Crosswalk-21, and I think it's already stable enough after the improvement throughout Crosswalk-22. Even if it may cause new regressions, it's safe to fix it during Crosswalk-22 beta.

Every time we delay our releases it's because something is wrong with Android and it takes forever to fix and verify, be it because of bugs caused by a rebase or in the code itself. Introducing such a big change (whose impact in terms of API breaks and whatnot looks uncertain) at this stage of Crosswalk 22's life cycle (when it should only be receiving bug fixes) sounds too risky to me.

OK, I understand your concern. Let's skip Crossawlk-22 and verify it on Crossawlk-23.
For some big commits like this, just reviewing is not enough to find problems. It can help to check the code style and code logic, but can not examine potential bugs. About how other ones interact with the rest of the code, I was shareing my update at the internal sync meeting every week, so at least Crosswalk Android team in PRC is aware of the status and the difference from previous pull request, so it's not a surprise for them to see this commit was merged shortly. I know it may be a surprise to the ones outside of PRC team, but I really haven't seen anybody helped to review every of our pull request actively before.
 If previous pull reqeust hasn't been reverted, I must list all changes and related bugs in the message of this commit. But after previous pull reqest was reverted, all bugs it caused have gone from the master branch, it doesn't make sense to fix unexisted bugs. I really cann't see the point to mention how I make a feature stable in the commit message of the feature itself.
Anyway, thanks for your attention to this pull request. I'll make sure more standard development process and more communication across teams before critical changes in the future.

About how other ones interact with the rest of the code, I was shareing my update at the internal sync meeting every week, so at least Crosswalk Android team in PRC is aware of the status and the difference from previous pull request, so it's not a surprise for them to see this commit was merged shortly.

This exactly the kind of thing that has no reason to be kept behind closed doors: there are no public records of those discussions and basically everybody is kept in the dark. Updating people in private sync meetings is fine as long as the actual code review and code discussions happen where they should happen: in the pull request.

I know it may be a surprise to the ones outside of PRC team, but I really haven't seen anybody helped to review every of our pull request actively before.

The Android code is usually maintained by people in PRC, but that does not mean everybody else is oblivious to the work. This is the case here for me at least, especially since I had to revert the original pull request and was also taking part in the other ticket about API compatibility. I've just been kept in the dark here.

I really cann't see the point to mention how I make a feature stable in the commit message of the feature itself.

I'm not sure I understand what you're trying to say, so let me try to rephrase what I said before: in the end, the commit message itself does not need to contain "a description of how to make itself stable", but the pull request message (or a comment etc) needs to say "hey guys, I'm aware that the previous PR was reverted because of regressions, here's how this patch differs from the previos one". Basically, other people need to be aware somehow of the iterations on your code.

@lincsoon to put in simple word, right now from this commit and the one that was reverted (which introduces breakage which is ok and not the point of the discussion here) there is no way one can figure out what changed to make the feature works better. You need to compare manually the diff to figure out and this is the point @rakuco is making here. "Internal" sync meetings are not enough because someone may pass after you on this commit and commit message needs to be explanatory so you don't need to rely on "internal sync meetings" to figure out the changes.
And it's not because the whole team doesn't review Android PR that nobody touches the Android code in Crosswalk, keep that in mind.

Thanks all the people for the concerns for this pull request. I didn't realized that this commit will attract so much attentions and got it done quickly without giving everybody enough notice. I'm sorry for that. Please trust me that I don't want to keep any work in the dark, instead I really want to make it public to meet the challenge so that our result would be more solid. But when we are not getting attention, I'm a bit sloppy with sharing information. I'll be careful and make sure enough communication in any ways including the commit message in the future.

Is the drop down menu and date picker issue related to this? I guess it is...


Upsert NotionDatabases in connectorsDB with title and url

This PR adds lastSeenTs, parentType, perentId, title, notionUrl to the NotionDatabase connectors model.
The lastSeenTs is used to properly garbage collect Notion Databases
The other will be used to properly show Databases in the Dust Notion permissions
A few comments and bug fixes were made along the way (moving to object signature at places to avoid mixing up arguments)

Deploy involves:

deploying connectors
running the notion restart-all command from the connectors cli (so that the new workflow use the new queues)

Cool will test thoroughly. @fontanierh May I ask that you do a second-pass review really squinting for potential problems? :pray:

Things I still wanted to check:

make sure we do ignore only notion database with a skip reason to make sure creating record won't ignore everything
rethink about GC before full-resync make sure everything looks sane

Will test:

deploying and see if running as is incremental updates is OK
(ideally) running a GC but not sure I'll go that far (worst case we bad GC databases I believe)
running a full resync

incremental sync post merge tested
GC post merge tested
full-resync tested

I will go ahead and merge this and restart our workspace

Deploy is:

merge
init connector db
deploy connectors


Wrong solution for tetris puzzle

Puzzle (reported by Michel4ngel0):
Puzzle URL
Looks like a failure in checkTetrisArea.

The large area that the tetris block is in somehow doesn't exist in the solver.


[AMD-AIE] Add pipeline based e2e tests to CI

-- This commit adds pipeline based e2e tests to CI.
Signed-off-by: Abhishek Varma<EMAIL_ADDRESS>

@erieaton-amd @spaceotter we can remove the seperate pad test now? since this is handled here?
https://github.com/nod-ai/iree-amd-aie/blob/main/.github/workflows/ci.yml#L107-L110

Pushed changes. If CI is green we can re-review/merge.


Fix README

Fixed missing variable in the first example. Issue #45

Codecov Report

Merging #46 (233d677) into main (752f5d9) will increase coverage by 1.93%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main       #46      +/-   ##
===========================================
+ Coverage   98.06%   100.00%   +1.93%
===========================================
  Files          11        11
  Lines         155       149       -6
===========================================
- Hits          152       149       -3
+ Misses          3         0       -3

Impacted Files
Coverage Δ

src/nnlist.jl
100.00% <0.00%> (+5.26%)
:arrow_up:

src/types/empirical_potential.jl
100.00% <0.00%> (+5.88%)
:arrow_up:

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


Version 2.0.0

Changelog

Compatibility with Prestashop <IP_ADDRESS> and <IP_ADDRESS>
Removed standard (form) integration
Unified copyright and updated licensing
Updated documentation

@oconnort please review this one as well

Why do we need the new image - views/img/simplify_phones.png?

We had a request to change the setting page to following https://github.com/OnTap/simplify-prestashop-module/blob/master/docs/plugin_configuration.png - here is this image used.

Please re-review @oconnort


HTML images have the src and " stripped off

First of all, AWESOME addon, great work!
In my testing I found that images are broken if they are already HTML.
For example, this in my obsidian markdown file:

becomes this in both the hugo and regular markdown conversions:

Any suggestions?

@jptechnical Hi, I can't reproduce it.

Are you installed the latest pandoc?

I believe so. Here are my specifics and the entire .md file.
Mac Studio (2022)
Apple M1 Max
32 GB
Monterey 12.5
Obsidian v0.15.9
Obsidian Enhancing Export v1.1.2
no other community plugins
$  which pandoc
/opt/homebrew/bin/pandoc

$ pandoc -v
pandoc 2.19
Compiled with pandoc-types 1.22.2, texmath <IP_ADDRESS>, skylighting 0.13,
citeproc <IP_ADDRESS>, ipynb 0.2, hslua 2.2.1
Scripting engine: Lua 5.4
User data directory: /Users/jp/.local/share/pandoc
Copyright (C) 2006-2022 John MacFarlane. Web:  https://pandoc.org
This is free software; see the source for copying conditions. There is no
warranty, not even for merchantability or fitness for a particular purpose.

How to Set File Permissions on Windows.md

Note that it is also adding \ to the [ characters.
So the string # [[How to Set File Permissions on Windows]]
is exported as # \[\[How to Set File Permissions on Windows\]\]
Attached is the file after exporting on my system.
How to Set File Permissions on Windows.md

Thanks for your feedback, I have reproduce it, I'ill fix it this weekend.

@jptechnical I have fix it in version 1.1.4.

Looks good, thanks, good work!


Port 137 to V3

Direct Mode improvements PR needs to be ported to V3: https://github.com/Azure/azure-cosmosdb-java/pull/137

nvm, this is already done


Horrible grammar

The grammar in this article needs serious improvements

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

ID: e80fe2fd-cbdb-699e-0dbb-a0a310bd372c
Version Independent ID: 266d08ae-344a-683b-11e2-143b704e21a8
Content: Open-source .NET library guidance
Content Source: docs/standard/library-guidance/index.md
Product: dotnet
GitHub Login: @JamesNK
Microsoft Alias: mairaw

Closing due to the lack of response. We'd need more info on which parts of the article if you find horrible as well.


Can`t catch error in AsyncStorage.mergeItem.

I`m trying to catch error in mergeItem method of AsyncStorage. In your documentation you wrote what third params must be callback for catching error. But it is not working.
export const setToken = (token) => { 	return AsyncStorage.mergeItem(constant.permissionSettings, null, () => { 		console.log("ERROR") 	}); };
For example in this situation I don`t see in console my message, but application is down with a normal message:

ExceptionsManager.js:82 JSON value '' of type NSNull cannot be converted to NSString

I tried catch it with try catch but result is the same.

The second arg of mergeItem is supposed to be a string, but you are passing null. I think you should just pass a string there. See the examples at https://facebook.github.io/react-native/docs/asyncstorage.html .
In general, I think you should expect error callbacks to be for cases where there's some unpreventable underlying error, like there's a disk failure or some other sort of IO failure. Rather than passing the wrong datatype.


Improve DOMWorld initialization

closes #1670

Check this out @Androbin. By initializing the properties we don't need to call SetContext in the constructor, and there wouldn't be any chance of a null TaskCompletionSource.

I would like to think this is equivalent to the current version.

World world = null

Thread 1:
world = new DOMWorld(...);

DOMWorld is allocated
TaskCompletionSource<ExecutionContext> is allocated
_contextResolveTaskWrapper is assigned
world is assigned

Thread 2:
world?.SetContext(new ExecutionContext(...));

Thread 2 simply cannot observe world != null before _contextResolveTaskWrapper is assigned

@Androbin true.


Do people want a feather mailing list?

We can make technical decisions about Feather on here, or on a mailing list. What would folks prefer?

I would say that the least time consuming would be to open a google group:
https://groups.google.com/

Or Gitter for extra shiny new thing cool:
https://gitter.im/

And here you have it: https://groups.google.com/forum/#!forum/feather-format


BUILD: Prepare monorepo structure for Zerox

Description
This PR drafts a monorepo structure for Zerox.
Changes Made

Poetry Integration: Added Poetry for managing Python dependencies.
Dependency Separation: Organized dependencies into separate groups for test, development, and vanilla builds
Setuptools Integration: Integrated Setuptools for building the package.
Post Install Hooks: Added mock post-install hooks for setting up system dependencies. These hooks are placeholders and can be replaced with actual implementation later.
Makefile: Created a Makefile to simplify the setup of the development environment and the final build process.
Code Quality Checks: Integrated Ruff for linting. Added Black for code formatting. Configured pre-commit hooks and .editorconfig for consistent code.
.gitignore Update: Updated .gitignore to accommodate changes in the directory structure of the monorepo.

Tests

Verified functionality of the Makefile to ensure it sets up the development environment and builds the package correctly.

Documentation

No new documentation has been added at this time.

Additional Notes

The changes are intended to validate the proposed monorepo structure.
Current implementations are placeholders. The actual implementation details will be added once the proposed structure is reviewed and approved.

Hey @wizenheimer, did a brief code review and this repo structure looks good!
I'll spend some time this afternoon doing a full end to end test, and hopefully we can merge today.


Wider menu items?

The display of the menu items is a bit narrow on the iPad. Is it possible to widen it?

Hi @llorenzo
As far as i know, pull-down menus in iOS and iPadOS have equal width of 250px (i'll double-check it tomorrow 'cause i can't quite remeber if iPadOS even uses pull-down menus or something different).
But i'll look into adding possibility to change menu's width (probably somewhere in the end of this week).

Quick follow up to my yesterdays comment and indeed both iOS and iPadOS are using the same 250px width pull-down menu.
I also checked if there is any width difference between native and my flutter version - they're also same.
Since they're equal, i'd say that it should stay that way.

Yes, your propably right. The thing is, I would like to strech the iOS design in my particular case...

The thing is, I would like to strech the iOS design in my particular case...

I think there is no problem in that really, i'll try to get update with this out in a few hours.

@llorenzo
I have just published update that adds menu width customization.
Example:
PullDownButtonTheme(
  widthConfiguration: PullDownMenuWidthConfiguration(400),
)

or
PullDownButton(
  itemBuilder: ...,
  buttonBuilder: ...,
  widthConfiguration: PullDownMenuWidthConfiguration(400),
)

Works perfect! Thank you very much.


jsuite CSS rgb function change to rgba

4 argument passed into rgb function instead of 3. Typescript expects exact number of arguments to be passed(works in pure JS). Project build failing due to this. Request to please change the function to rgba.
ERROR in ./node_modules/jsuites/dist/jsuites.css (./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./node_modules/jsuites/dist/jsuites.css)
Module build failed:
background: rgb(255,255,255,0.95);

This has been fixed and It will be deployed soon. Thanks for spotting that.

Sir,
The issue still persists.


SW-5856 Include variables injected into section text values when getting variables for a document's manifest

SW-5856 Include variables injected into section text values when getting variables for a document's manifest
Put functionality into VariableService, add test

#2309  👈
main

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

Join @nickgraz and the rest of your teammates on  Graphite


Assemble new chassis - Andrew's robot

Waiting on task #1 (make new thigh parts) which in turn are waiting on the Haimer to be repaired.

Was not getting any motor movement at first. Once I changed the I2C address of the left motor controller to 0x41 and connected it to the I2C bus on physical pins 17 & 18 of the ESP32 then the motors started to move when I issued the command stp,0,0,300. This command will centre the robot's right front hip servo. Using this command across each motor will allow me to put the horns on each servo in their home position.

Legs are now assembled using new thigh part and 3/8” long screws. Now waiting on mounting brackets and posts to be machined.

My robot is fully assembled for now. Extra upright post and brackets created but likely will not be used due to lack of space.


macOS codesigning failures

Error logs:
Error: HTTP status code: 403. A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. Ensure your team has signed the necessary legal agreements and that they are not expired.

Failing jobs:

CI: https://github.com/artichoke/nightly/actions/runs/5317096428/jobs/9627259251
Nightly: https://github.com/artichoke/nightly/actions/runs/5317152377/jobs/9627383470
Nightly: https://github.com/artichoke/nightly/actions/runs/5317152377/jobs/9627383555

Upon logging into the Artichoke Apple Code Signing account on the Apple Developer portal https://developer.apple.com/account:

Note: The program license agreement has been updated.
Accept the latest Apple Developer Program License Agreement to continue integrating new technologies, submitting content to App Review, accessing Certificates, Identifiers, and Profiles, and more.

Apple Developer Program License Agreement
Apple_Developer_Program_License_Agreement_QMSS25KHJ3.pdf

I just agreed to the updated agreement. Kicking CI and nightly jobs now to verify this is resolved.

jobs passed


Metal Support for binding with Unity

Hi,
Is there a chance for supporting Metal as rendering option for iOS in binding Unity projects since OpenGL becomes deprecated in iOS and soon will be not available to use?
Best Regards,
Bartosz

Duplicate https://github.com/f111fei/react-native-unity-view/issues/29


PICT-1552 : Add button to trigger Crime Portal Gateway

Worth noting that we raised a second ticket for tidying up unused code and testing PIC-1744


SF Symbols support

Description
Is there a way to use SF Symbols in ConfettiSwiftUI?  I tried embedding in Text but that did not work.  Thanks.
Tasks

[ ] ...

Context
...mention related issues and/or user stories...

Yes this was merged recently. Check related PR: https://github.com/simibac/ConfettiSwiftUI/pull/14

Excellent.  Works.  Thanks!


2022051301

Closes #4944
Closes #4945
Closes #4872

Can you please look at these hotspots?
https://github.com/helium/denylist/issues/2715
There are blocked but ther are real deployments.


Typo "Microsoft Teams Room"→"Microsoft Teams Rooms"

https://learn.microsoft.com/en-us/microsoftteams/rooms/room-planning-guidance?source=recommendations&tabs=emtr
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/rooms/room-planning-guidance.md
#PingMSFTDocs

@dstrome
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Dialog for read-only files does not go away on Esc

There seems to be some focus issue -- RET or Esc doesn't act on the dialog.

cc @zcbenz


test(kafka): Add test for partial cluster failure

For INC-599, in followup SNS-2603, add a test that ensures that the
consumer reliably crashes when a broker dies. I will work a bit more on
the CI setup, but basically you need to run docker-compose up, run
that one test using pytest  tests/backends/test_kafka.py -k died -s,
and observe that it passes.
This is a problem though because it means we cannot reproduce the
failure we have seen in that incident, where the consumer hangs after
broker failure.

this didn't end up going anywhere, closing.


Updated metal-go client for sub-commands gateways

Breakout from https://github.com/equinix/metal-cli/pull/270
What this PR does / why we need it:
This PR replaces packngo with metal-go for all interactions with the Equinix Metal API specifically for gateways sub commands
DISCUSSION POINTS:

Needs update for new pagination and rebase.

@vasubabu Please decline this PR in the favour of https://github.com/equinix/metal-cli/pull/376


Next.js Deployment Issues on AWS Amplify:  Import Errors and useContext Null Property Errors

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature
Deployments
Is your feature request related to a problem? Please describe:
We are experiencing several issues during the build phase of our Next.js application deployment on AWS Amplify. These issues include:

 import outside of pages/_document: We are encountering errors where  components are being imported outside of the pages/_document file. According to Next.js documentation (https://nextjs.org/docs/messages/no-document-import-in-page),  should only be used within _document.js and not within regular pages.

I am using app directory and don't have pages/_document and have touch anything that much in the code of create-next-app with next-auth

import type { Metadata } from "next";

import { Inter } from "next/font/google";
import { Toaster } from "react-hot-toast";

import { SessionProvider } from "next-auth/react";
import { Providers } from "./providers";

import "./globals.css";

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

export const metadata: Metadata = {
  title: process.env.NEXT_PUBLIC_SITE_NAME || "Create Next App",
  description: "Generated by create next app",
};

export default function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode;
}>) {
  return (
    // <html lang="en" className='dark'>
    <html lang="en">
      <body>
        <Providers>
          <SessionProvider>
            {children}
          </SessionProvider>
          <Toaster />
        </Providers>
      </body>
    </html>
  );
}

TypeError: Cannot read properties of null (reading 'useContext'): This error is occurring intermittently, particularly on pages that involve useContext. It's unclear why this error is happening, as our codebase adheres to React's useContext guidelines and works correctly in local development environments.

Also don't know why it's throwing TypeError

Other static page generation errors: Additionally, we are seeing errors related to static page generation, particularly on paths like /404, /500, and custom pages such as /dashboard, /login, /register, and others.

For /404 and /500 We don't have this page and for the /dashboard, /login, /register, and others, I have tried building it and haven't found the same issue as amplify throwing in the log.

Build Log:
024-06-27T10:03:09.774Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
                                 # Executing command: yarn run build
2024-06-27T10:03:09.931Z [INFO]: yarn run v1.22.19
2024-06-27T10:03:09.954Z [INFO]: $ next build
2024-06-27T10:03:10.026Z [WARNING]: ⚠ You are using a non-standard "NODE_ENV" value in your environment. This creates inconsistencies in the project and is strongly advised against. Read more: https://nextjs.org/docs/messages/non-standard-node-env
2024-06-27T10:03:10.693Z [INFO]: ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2024-06-27T10:03:10.707Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2024-06-27T10:03:10.708Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
                                 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
                                 https://nextjs.org/telemetry
2024-06-27T10:03:10.775Z [INFO]: ▲ Next.js 14.2.4
2024-06-27T10:03:10.775Z [INFO]:
2024-06-27T10:03:10.854Z [INFO]: Creating an optimized production build ...
2024-06-27T10:03:13.077Z [WARNING]: Warning: You're using `next/head` inside the `app` directory, please migrate to the Metadata API. See https://nextjs.org/docs/app/building-your-application/upgrading/app-router-migration#step-3-migrating-nexthead for more details.
2024-06-27T10:03:26.585Z [WARNING]: ⚠ Compiled with warnings
2024-06-27T10:03:26.591Z [WARNING]: ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (process.nextTick at line: 351) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (setImmediate at line: 352) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (setImmediate at line: 352) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (process.nextTick at line: 352) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
2024-06-27T10:03:40.637Z [INFO]: ✓ Compiled successfully
2024-06-27T10:03:40.642Z [INFO]: Linting and checking validity of types ...
2024-06-27T10:03:45.893Z [INFO]: Collecting page data ...
2024-06-27T10:03:47.701Z [INFO]: Generating static pages (0/15) ...
2024-06-27T10:03:48.067Z [WARNING]: Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
                                    Error occurred prerendering page "/500". Read more: https://nextjs.org/docs/messages/prerender-error
                                    Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
2024-06-27T10:03:48.068Z [INFO]: Generating static pages (3/15)
2024-06-27T10:03:48.188Z [WARNING]: Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
                                    Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
                                    Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
2024-06-27T10:03:48.214Z [WARNING]: TypeError: Cannot read properties of null (reading 'useContext')
                                    at t.useContext (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:109363)
                                    at d (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:21495)
                                    at h (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:13448)
                                    at au (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    at a_ (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
                                    at ab (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908) {
                                    digest: '3984810264'
                                    }
                                    TypeError: Cannot read properties of null (reading 'useContext')
                                    at t.useContext (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:109363)
                                    at d (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:21495)
                                    at h (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:13448)
                                    at au (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    at a_ (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
                                    at ab (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error
                                    TypeError: Cannot read properties of null (reading 'useContext')
                                    at t.useContext (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:109363)
                                    at d (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:21495)
                                    at h (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:13448)
                                    at au (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    at a_ (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
                                    at ab (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
.
.
.
.
.
.
.
2024-06-27T10:03:48.432Z [INFO]: ✓ Generating static pages (15/15)
2024-06-27T10:03:48.437Z [WARNING]:
2024-06-27T10:03:48.437Z [WARNING]: > Export encountered errors on following paths:
                                    /_error: /404
                                    /_error: /500
                                    /_not-found/page: /_not-found
                                    /client-side/page: /client-side
                                    /dashboard/page: /dashboard
                                    /example/page: /example
                                    /login/page: /login
                                    /page: /
                                    /profile/page: /profile
                                    /register/page: /register
2024-06-27T10:03:48.470Z [WARNING]: error Command failed with exit code 1.
2024-06-27T10:03:48.470Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-06-27T10:03:48.483Z [ERROR]: !!! Build failed
2024-06-27T10:03:48.483Z [INFO]: Please read more about Amplify Hosting's support for SSR frameworks to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/amplify-ssr-framework-support.html. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html
2024-06-27T10:03:48.483Z [ERROR]: !!! Error: Command failed with exit code 1
2024-06-27T10:03:48.483Z [INFO]: # Starting environment caching...
2024-06-27T10:03:48.483Z [INFO]: # Environment caching completed
``````bat
024-06-27T10:03:09.774Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
                                 # Executing command: yarn run build
2024-06-27T10:03:09.931Z [INFO]: yarn run v1.22.19
2024-06-27T10:03:09.954Z [INFO]: $ next build
2024-06-27T10:03:10.026Z [WARNING]: ⚠ You are using a non-standard "NODE_ENV" value in your environment. This creates inconsistencies in the project and is strongly advised against. Read more: https://nextjs.org/docs/messages/non-standard-node-env
2024-06-27T10:03:10.693Z [INFO]: ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2024-06-27T10:03:10.707Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2024-06-27T10:03:10.708Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
                                 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
                                 https://nextjs.org/telemetry
2024-06-27T10:03:10.775Z [INFO]: ▲ Next.js 14.2.4
2024-06-27T10:03:10.775Z [INFO]:
2024-06-27T10:03:10.854Z [INFO]: Creating an optimized production build ...
2024-06-27T10:03:13.077Z [WARNING]: Warning: You're using `next/head` inside the `app` directory, please migrate to the Metadata API. See https://nextjs.org/docs/app/building-your-application/upgrading/app-router-migration#step-3-migrating-nexthead for more details.
2024-06-27T10:03:26.585Z [WARNING]: ⚠ Compiled with warnings
2024-06-27T10:03:26.591Z [WARNING]: ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (process.nextTick at line: 351) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (setImmediate at line: 352) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (setImmediate at line: 352) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    A Node.js API is used (process.nextTick at line: 352) which is not supported in the Edge Runtime.
                                    Learn more: https://nextjs.org/docs/api-reference/edge-runtime
                                    Import trace for requested module:
                                    ./node_modules/bcryptjs/dist/bcrypt.js
                                    ./auth.ts
2024-06-27T10:03:40.637Z [INFO]: ✓ Compiled successfully
2024-06-27T10:03:40.642Z [INFO]: Linting and checking validity of types ...
2024-06-27T10:03:45.893Z [INFO]: Collecting page data ...
2024-06-27T10:03:47.701Z [INFO]: Generating static pages (0/15) ...
2024-06-27T10:03:48.067Z [WARNING]: Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
                                    Error occurred prerendering page "/500". Read more: https://nextjs.org/docs/messages/prerender-error
                                    Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
2024-06-27T10:03:48.068Z [INFO]: Generating static pages (3/15)
2024-06-27T10:03:48.188Z [WARNING]: Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
                                    Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
                                    Error: <Html> should not be imported outside of pages/_document.
                                    Read more: https://nextjs.org/docs/messages/no-document-import-in-page
                                    at Z (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5430)
                                    at I (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/682.js:6:1263)
                                    at renderWithHooks (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
                                    at renderIndeterminateComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5732:15)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5957:7)
                                    at renderNodeDestructiveImpl (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6115:11)
                                    at renderNodeDestructive (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6087:14)
                                    at finishClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5688:3)
                                    at renderClassComponent (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5696:3)
                                    at renderElement (/codebuild/output/src3157314800/src/Prod-App/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5954:7)
2024-06-27T10:03:48.214Z [WARNING]: TypeError: Cannot read properties of null (reading 'useContext')
                                    at t.useContext (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:109363)
                                    at d (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:21495)
                                    at h (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:13448)
                                    at au (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    at a_ (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
                                    at ab (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908) {
                                    digest: '3984810264'
                                    }
                                    TypeError: Cannot read properties of null (reading 'useContext')
                                    at t.useContext (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:109363)
                                    at d (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:21495)
                                    at h (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:13448)
                                    at au (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    at a_ (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
                                    at ab (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error
                                    TypeError: Cannot read properties of null (reading 'useContext')
                                    at t.useContext (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:109363)
                                    at d (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:21495)
                                    at h (/codebuild/output/src3157314800/src/Prod-App/.next/server/chunks/317.js:1:13448)
                                    at au (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
                                    at a_ (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
                                    at ab (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
                                    at /codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
                                    at aw (/codebuild/output/src3157314800/src/Prod-App/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
.
.
.
.
.
.
.
2024-06-27T10:03:48.432Z [INFO]: ✓ Generating static pages (15/15)
2024-06-27T10:03:48.437Z [WARNING]:
2024-06-27T10:03:48.437Z [WARNING]: > Export encountered errors on following paths:
                                    /_error: /404
                                    /_error: /500
                                    /_not-found/page: /_not-found
                                    /client-side/page: /client-side
                                    /dashboard/page: /dashboard
                                    /example/page: /example
                                    /login/page: /login
                                    /page: /
                                    /profile/page: /profile
                                    /register/page: /register
2024-06-27T10:03:48.470Z [WARNING]: error Command failed with exit code 1.
2024-06-27T10:03:48.470Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-06-27T10:03:48.483Z [ERROR]: !!! Build failed
2024-06-27T10:03:48.483Z [INFO]: Please read more about Amplify Hosting's support for SSR frameworks to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/amplify-ssr-framework-support.html. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html
2024-06-27T10:03:48.483Z [ERROR]: !!! Error: Command failed with exit code 1
2024-06-27T10:03:48.483Z [INFO]: # Starting environment caching...
2024-06-27T10:03:48.483Z [INFO]: # Environment caching completed

Describe how you'd like this feature to work
N/A

Hello - thanks for reaching out! Are you able to create a support case with AWS?

Hello - thanks for reaching out! Are you able to create a support case with AWS?

Hi, I haven't created a support case yet as I find the dashboard console somewhat overwhelming.
I used to host react apps at vercel but vercel is expensive.

Sorry to hear that! Let me ask you -- what is your current issue with Amplify Hosting? Can you try to deploy your app again?

It gives me errors to the pages that dont exist in the files /404 and /500
Also give an error that exist only in Page directory Error: <Html> should not be imported outside of pages/_document. I am using App directory btw. I already raised the issue to next.js and they check the code is fine.
Building in local, vercel and Netlify have no issues except for Amplify the log is attached above

Sorry to hear that! Let me ask you -- what is your current issue with Amplify Hosting? Can you try to deploy your app again?

It gives me errors to the pages that dont exist in the files /404 and /500
Also give an error that exist only in Page directory Error: <Html> should not be imported outside of pages/_document. I am using App directory btw. I already raised the issue to next.js and they check the code is fine.
Building in local, vercel and Netlify have no issues except for Amplify the log is attached above

What is your appID?

What is your appID?

d3uewcwndluxob

@mauerbac not sure why it worked, i didnt change anything at the code but yea could be cache issue or something


bluetooth: host: Bug fix in bt_uuid_create

Endianness bug fix in bt_uuid_create function.
Signed-off-by: Akshatha.H<EMAIL_ADDRESS>

bt_uuid_create may not be only used with data coming over the air so conversion should be done before the call, we could perhaps have a _le alternative that can be used directly when parsing data received over the air.

@Vudentz There is already a function bt_uuid_create_le just before this function call to handle the above mentioned scenario

bt_uuid_create_le is meant to handle packets on air.
bt_uuid_create was meant to create a bt_uuid type from internal represententation (like from the read callback). Since it is from internal representation i don't think it needs to handle unaligned access.

Yes, that is my understanding also.

The fix doesn't look right to me (considering the existence of bt_uuid_create_le()), but at the same time the current implementation of bt_uuid_create() looks buggy in that it seems to have unaligned access issues if given unaligned data. @kimsekkelund any comments? It looks like you're behind this code?

I assume sys_get_le16() and sys_get_le32() functions assures aligned memory even though the input data is unaligned.

I assume sys_get_le16() and sys_get_le32() functions assures aligned memory even though the input data is unaligned.

Yes, they are safe to use, however considering that that bt_uuid_create() takes the "internal representation" doesn't that imply native byte order, meaning no conversion should be needed? If  alignment is not guaranteed then UNALIGNED_GET() is what should be used when no byte order conversion is needed.

I assume sys_get_le16() and sys_get_le32() functions assures aligned memory even though the input data is unaligned.

Yes, they are safe to use, however considering that that bt_uuid_create() takes the "internal representation" doesn't that imply native byte order, meaning no conversion should be needed? If alignment is not guaranteed then UNALIGNED_GET() is what should be used when no byte order conversion is needed.

In function find_type_cb, attr->read (line 603) always returns uuid in little endian , so we need to do this conversion for big endian targets

In function find_type_cb, attr->read (line 603) always returns uuid in little endian , so we need to do this conversion for big endian targets

There's something wrong with the naming of these APIs then. If both take little-endian data it's confusing that only one has an _le suffix. Can we come up with better names for them?

In function find_type_cb, attr->read (line 603) always returns uuid in little endian , so we need to do this conversion for big endian targets

There's something wrong with the naming of these APIs then. If both take little-endian data it's confusing that only one has an _le suffix. Can we come up with better names for them?

I think the problem is that someone expected local database reads to return native endian UUIDs, and client related reads to return little endian UUIDs (in this case 2 different create functions are needed), whereas someone else expected both types of reads to be handled by the same function (in this case only one create function is needed). So now we have a mix: both types of read are handled by the same function which returns little-endian UUIDs, and we have two create functions which both process little-endian UUIDs.
At this point it is probably easier to merge the 2 create functions into one.
By the way, the database read function currently lacks support for 32-bit UUIDs, so we should add that.

In function find_type_cb, attr->read (line 603) always returns uuid in little endian , so we need to do this conversion for big endian targets

There's something wrong with the naming of these APIs then. If both take little-endian data it's confusing that only one has an _le suffix. Can we come up with better names for them?

I think the problem is that someone expected local database reads to return native endian UUIDs, and client related reads to return little endian UUIDs (in this case 2 different create functions are needed), whereas someone else expected both types of reads to be handled by the same function (in this case only one create function is needed). So now we have a mix: both types of read are handled by the same function which returns little-endian UUIDs, and we have two create functions which both process little-endian UUIDs.
At this point it is probably easier to merge the 2 create functions into one.
By the way, the database read function currently lacks support for 32-bit UUIDs, so we should add that.

It looks like you are correct, if the attr->read function in find_type_cb in att.c is bt_gatt_attr_read_service in gatt.c then it seems that data is not in native CPU endianness, but always little endian, so then bt_uuid_create in find_type_cb should actually be bt_uuid_create_le.
It seems that we should get rid of one of the functions then. It would seems this PRs version of bt_uuid_create is the correct one.  I suggest we use this one, and get rid of bt_uuid_create_le.
The changes to these uuid create functions was here: https://github.com/zephyrproject-rtos/zephyr/pull/17765

In function find_type_cb, attr->read (line 603) always returns uuid in little endian , so we need to do this conversion for big endian targets

There's something wrong with the naming of these APIs then. If both take little-endian data it's confusing that only one has an _le suffix. Can we come up with better names for them?

I think the problem is that someone expected local database reads to return native endian UUIDs, and client related reads to return little endian UUIDs (in this case 2 different create functions are needed), whereas someone else expected both types of reads to be handled by the same function (in this case only one create function is needed). So now we have a mix: both types of read are handled by the same function which returns little-endian UUIDs, and we have two create functions which both process little-endian UUIDs.
At this point it is probably easier to merge the 2 create functions into one.
By the way, the database read function currently lacks support for 32-bit UUIDs, so we should add that.

It looks like you are correct, if the attr->read function in find_type_cb in att.c is bt_gatt_attr_read_service in gatt.c then it seems that data is not in native CPU endianness, but always little endian, so then bt_uuid_create in find_type_cb should actually be bt_uuid_create_le.
It seems that we should get rid of one of the functions then. It would seems this PRs version of bt_uuid_create is the correct one. I suggest we use this one, and get rid of bt_uuid_create_le.
The changes to these uuid create functions was here: #17765

@joerchan I have modified the code accordingly, hope this should be fine.

@akshhr Thank you. Did you run the files through an automated style tool?
There are some #endif /*CONFIG_NAME */ That are weirdly aligned with the code line above them. Can you fix them?

@akshhr Thank you. Did you run the files through an automated style tool?
There are some #endif /*CONFIG_NAME */ That are weirdly aligned with the code line above them. Can you fix them?
I ran the uncrustify tool as specified in contribution guidelines. I will check once again and confirm. Thank you


[Bug][Config-UI] Refdiff parameter setting error in transformation

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
tagsLimit in refdiff is wrongly set to tagsOrder.
What do you expect to happen
Set wrong tagsOrder back to tagsLimit.
How to reproduce

Create a transformation for GitHub.
Create a blueprint including the above GitHub transformation.

Anything else
No response
Version
main
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey @mintsweet @likyh did we cherry pick this fix?

@JoshuaPoddoku Yes, it's been cherry picked to https://github.com/apache/incubator-devlake/releases/tag/v0.16.0-beta13