pilot agent not exit when coredump is enabled

To solve https://github.com/istio/istio/issues/19411, so that when coredump is enabled, pilot agent would not exit when envoy exit. The alternative way is to wait sometime before quit for the core dump to finish and then transfer them into some other storage.

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

Test name
Commit
Details
Rerun command

gencheck_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test gencheck_istio

lint_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test gencheck_istio

lint_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test lint_istio

unit-tests_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
d0ea80ce3b18acff77036e822a45ff6c597ee854
link
/test unit-tests_istio

lint_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test lint_istio

unit-tests_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test lint_istio

unit-tests_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test lint_istio

unit-tests_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test pilot-multicluster-e2e_istio

integ-security-k8s-tests_istio
707e5aed5507f8f94abbced8cc9242deadc9590a
link
/test integ-security-k8s-tests_istio

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

Then the expected  application replicas will be broken, this is violent. Would suggest injecting a prestop hook, so that we can allow users define their behavior.

Yes this seems like it will make coredump enabled completely broken for anything outside of actively debugging. If envoy crashes your application will never recover

Yep I was thinking of a prestop hook as well, but I am not sure how much flexibility we should give the user to define their behavior and how much we should provide. Based on that in which way they should define this hook.
One way I can think of is use gcs and user need to specify the projectid and bucket path, but then it is limited to gcs.
Any suggestions? @hzxuzhonghu @howardjohn @lambdai

How do other applications handle this?
On Thu, Dec 12, 2019, 7:35 PM Xinnan Wen<EMAIL_ADDRESS>wrote:

Yep I was thinking of a prestop hook as well, but I am not sure how much
flexibility we should give the user to define their behavior and how much
we should provide. Based on that in which way they should define this hook.
One way I can think of is use gcs and user need to specify the projectid
and bucket path, but then it is limited to gcs.
Any suggestions? @hzxuzhonghu https://github.com/hzxuzhonghu @howardjohn
https://github.com/howardjohn @lambdai https://github.com/lambdai
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/19533?email_source=notifications&email_token=AAEYGXKI5GX4W22S2WDQA33QYL7JPA5CNFSM4JZXCMC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGYZOHQ#issuecomment-565286686,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXM5RWKSKCSY6QQXLTDQYL7JPANCNFSM4JZXCMCQ
.

from what I have seen, just different ways of persistent storage, some mount it locally and some upload to cloud storage or combine them

I didn't know how we handled it before. I didn't recall whether we mount host storage and maintain retention
I would be happy if pilot agent suicide after 10 second. The proxy memory usage is expected to be around 100 MB?
The coredump should have completed in 10 seconds.

I think we can reserve the flexibility to users, what we can do is let users config the istio-proxy with a prestop hook.  User can run a cmd/script to send the core to obs/gcs or any customized server.

Yes I think someone added a lifecycle values so people can set the
prestop hook themselves
On Thu, Dec 12, 2019 at 11:57 PM Zhonghu Xu<EMAIL_ADDRESS>wrote:

I think we can reserve the flexibility to users, what we can do is let
users config the istio-proxy with a prestop hook. User can run a
cmd/script to send the core to obs/gcs or any customized server.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/19533?email_source=notifications&email_token=AAEYGXOQERMY55YPZ3VVMLLQYM57PA5CNFSM4JZXCMC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGZGV5I#issuecomment-565340917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXOL4UW7EWPWBWZQL6DQYM57PANCNFSM4JZXCMCQ
.

ok that's reasonable, then we don't need to do code changes here. Lifycycle was just added in the injection template charts, so user can define their prestop hook directly there.

Lifecycle does not work, it is enforced by kubelet before it send term signal. Pilot agent dies itself and this does not tell the container to continue...
We need a proper solution.

I actually tried it and it worked. maybe I misconfigured something. I will verify again.


Hi @roleoroleo!
I have the possibility to buy a Yi Outdoor 1080p, DID RFUSY595GH0XXN220620 from 2023.02. It hasn't been unpacked yet so the guy can't tell about the firmware.
On paper, it looks compatible, but I'd like your opinion. What do you think?
Thanks!

Oh and I just noticed that it says ha30ga v1.4  on the label

Without a fw version I can't be sure but probably it's a h30ga.
So it's probably supported.

Camera received and I confirm the h30ga. Came with firmware 9.0.26 so it should be good.
Thanks for your response @roleoroleo !


autotiling stoped working

Hi,
my sway had a large update yesterday, and now autotiling isn't working.
Has anyone an idea how i can fix it
autotiling -h
Traceback (most recent call last):
File "/usr/bin/autotiling", line 33, in
sys.exit(load_entry_point('autotiling==1.6', 'console_scripts', 'autotiling')())
File "/usr/bin/autotiling", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
File "/usr/lib/python3.10/importlib/metadata/init.py", line 919, in distribution
return Distribution.from_name(distribution_name)
File "/usr/lib/python3.10/importlib/metadata/init.py", line 518, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for autotiling

This might be due to a recent python 3.9 -> 3.10 update. Try to rebuild with yay or pacman, or, for your convenience, follow the instructions given by the most recent Manjaro (stable) forum post.

I guess we could just rebuild it, as it should use python3.10 now by default. Let's give that a try.

as with all python updates since the beginning of time, this seems to be a nightmare. So for some reason it is on python 3.9 in the container and fails because it didn't find wheel: https://github.com/Manjaro-Sway/autotiling/runs/4706436868?check_suite_focus=true

soo, after updating the underlying builder image, this should ™  work now. let me know if it doesn't after an update in ~5minutes.

Everything works, thanks for the quick support!!!
And a huge thank you to everyone for this great distro (the best Linux system I've ever used)

Ah, so that is what this was, I got it working with the exec_always autotiling, as I thought I had broken something. Commented the line now and autotiling still works.
Fully agree with @durito28's comment!


not working again

egde dev just updated, ver.0.33 is not working again

egde dev just updated, ver.0.33 is not working again
And ver.0.34  not working either

my ver.0.34 is still working now,maybe the problem is'nt about edge version?

my ver.0.34 is still working now,maybe the problem is'nt about edge version?

Solved, The main issues is the VPS problem. When I replacing the VPS everything is ok


Linking errors

Including Xsc.h and linking with xsc_core.lib gives the following errors:
error LNK2019: unresolved external symbol "public: __cdecl Xsc::IndentHandler::IndentHandler(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0IndentHandler@Xsc@@QEAA@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) referenced in function "protected: __cdecl Xsc::Log::Log(void)" (??0Log@Xsc@@IEAA@XZ)
error LNK2001: unresolved external symbol "public: virtual void __cdecl Xsc::StdLog::SubmitReport(class Xsc::Report const &)" (?SubmitReport@StdLog@Xsc@@UEAAXAEBVReport@2@@Z)
error LNK2019: unresolved external symbol "bool __cdecl Xsc::CompileShader(struct Xsc::ShaderInput const &,struct Xsc::ShaderOutput const &,class Xsc::Log *,struct Xsc::Reflection::ReflectionData *)" (?CompileShader@Xsc@@YA_NAEBUShaderInput@1@AEBUShaderOutput@1@PEAVLog@1@PEAUReflectionData@Reflection@1@@Z) referenced in function "public: static bool __cdecl Renderer::RCompileShader(struct RShaderCompilerInput const &,struct RShaderCompilerOutput &)" (?RCompileShader@Renderer@@SA_NAEBURShaderCompilerInput@@AEAURShaderCompilerOutput@@@Z)

Are you compiling with VisualC++ 2015? On 64-bit or 32-bit? And which branch have you checked out?

I'm compiling with Visual C++ 2017. I use the built in CMake functionality of VS2017.
64 bit
the master branch
I tried switching XSC_BUILD_SHELL off and XSC_SHARED_LIB on but it didn't change much.
so the main settings are:
option(XSC_BUILD_SHELL "Build XShaderCompiler shell 'xsc'" OFF)
option(XSC_BUILD_DEBUGGER "Build XShaderCompiler debugger 'xsc_debugger' (requires wxWidgets library)" OFF)
option(XSC_BUILD_TESTS "Build all test applications" OFF)
option(XSC_SHARED_LIB "Build XShaderCompiler as a shared library instead of a static library" ON)

The application where I'm trying to use the resulting library is not a cmake project. I'm including xsc.h from inc\Xsc and linking with the library that is the result of the compilation with the setup above.

Hmm, it looks like something is wrong with the linking itself, let me dig into this more.

If I force the linking using #pragma comment then it links but having xsc_core in the additional dependencies doesn't work. This is really weird.
Now I get a crash in the logger when I construct the StdLog
KernelBase.dll!00007ff96f8ea388()	Unknown
vcruntime140.dll!00007ff961364722()	Unknown
xsc_core.dll!__scrt_throw_std_bad_alloc() Line 35	C++
xsc_core.dll!operator new(unsigned __int64 size) Line 48	C++
[Inline Frame] xsc_core.dll!std::_Default_allocate_traits::_Allocate(const unsigned __int64) Line 52	C++
[Inline Frame] xsc_core.dll!std::_Allocate_manually_vector_aligned(const unsigned __int64) Line 102	C++
[Inline Frame] xsc_core.dll!std::_Allocate(const unsigned __int64) Line 195	C++
[Inline Frame] xsc_core.dll!std::allocator<char>::allocate(const unsigned __int64 _Count) Line 1036	C++
[Inline Frame] xsc_core.dll!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::_Construct_lv_contents(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &) Line 2394	C++
xsc_core.dll!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::basic_string<char,std::char_traits<char>,std::allocator<char> >(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & _Right) Line 2114	C++
xsc_core.dll!Xsc::IndentHandler::IndentHandler(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & initialIndent) Line 16	C++

I can proceed helping you tomorrow. I‘m not at home right now.

I implemented the PIMPL idiom to avoid exporting STL containers. So far, I never had a problem with this and always ignored the respective warnings.
However, maybe this causes the linking errors and crashes on your platform.
Please checkout the STL-export-fix branch and let me know if this changes anything about your situation.

This branch solves the issue, thanks!


caravel_openframe master branch vs openframe_development branch

There have been a couple of PRs adding caravel_openframe to master and then there is also openframe_development which is different from master. What are the differences between the already merged openframe and the development branch. Will the development branch be merged to master?

@RTimothyEdwards We have been using the master branch. Switching to openframe_development (as requested by you over the weekend) is not a possibility now. It is behind master and there are conflicts between the two branches.
@jeffdi Given the above, I don't think the open frame example tape-out is a possibility today.

Some additional changes were made to the openframe_development branch between March 14 and March 30.  I'm not exactly sure why they would conflict, but they do need to be folded back into the main branch carefully.


Variable not initialized error even when initialized in every normally completing match clause

Following program doesn't compile but it should.
import ballerina/io;

type S record {|
    string str;
|};

type B record {|
    boolean bool;
|};

type R S|B;

function f(R r) {
    int i;
    match r {
        var { str } => {
            i = 1;
        }
        var { bool } => {
            i = 2;
        }
        _ => {
            panic error("impossible");
        }
    }
    io:println(i);
}

This should compile even without panic error("impossible");, I put that to show this is not a SemType issue, but simply a flow control issue.

Related to https://github.com/ballerina-platform/ballerina-lang/issues/25857.


Polite client does not see stream from peer using Safari 15

The polite client does not display the peer's video if the peer uses Safari 15.
Tested with Firefox 94 and Chromium 96.

It seems to be related to this iOS 15.1 bug: https://github.com/twilio/twilio-video.js/issues/1611

Fixed in iOS 15.2: https://github.com/twilio/twilio-video.js/issues/1611#issuecomment-1011300762


How can I hidden the titlebar on 0.2.18 ?

How can I hidden the titlebar on 0.2.18 ?

Hi @duanjun , thanks for the issue! Can you please clarify what the behavior you expect is? For example, do you not want the filename in the title?

yes， I want a fullscreen just likes terminal does  ，so i think title should be configurable

Have you tried setting editor.fullScreenOnStart to true?
You can also set oni.hideMenu to true to hide the File/Edit/Split bars.

Also, maximizeScreeOnStart is a good option.

Ah I think that in OSX, where we now show a titlebar with #68 , we don't hide it on fullscreen - so maybe we don't need a new setting, but just need to hide it in the case where we are fullscreen (which I believe is consistent with how other OSX apps behave).

This should be fixed now in the latest release with #1064 - once we're full screen, we hide the titlebar on OSX (like other apps).


[UX] Wrap "Set Headers" modal into form tag

Is your feature request related to a problem? Please describe.
Wrapping "Set Headers" modal into html form tag will allow to submit modal via press Enter key.

Hey @fantua,
Thanks for reporting this! I'd look into it as soon as I can.


gbp buildpackage errors (E) do not result in failure exit code in bin/deb-build-binary

As seen in https://github.com/linz/postgresql-dbpatch/pull/67/checks?check_run_id=692974606#step:4:641 an E line doesn't seem to result in a failure exit from package building script. I think it should...

To be reported upstream, if really worth it


Merging Hygiene

How do we feel about git hygiene when merging?  I personally tend to squash-and-merge PRs, except if git history is particularly clean (this happens very rarely for me).  Any thoughts?
When people maintain larger projects it's usually nice to be able to assume a few things about git history

It is entirely linear, without branching
All tests pass on all commits

These conditions are very rarely held during normal active development of any feature branch, but are typically held when a branch is merged.  We can use github's squash-and-merge feature to automatically squash all commits in a PR to one.  This loses some history though, so there is a balance here if the git history of that branch is particularly valuable.
Most pydata projects that I know of use squash-and-merge by default.

squash-and-merge works for me. I personally am often guilty of committing breaking code usually as a way to keep track of where I'm at in the middle of a refactor or so I can have other people look at the code, so I'm usually less strict about it, but I could try to be cleaner about that.  I guess with squash-and-merge we are guaranteed that all tests pass so long as travis passes on the last commit so I am ok with that.

Committing breaking or WIP code makes lots of sense.  I do it all the time. Squash-and-merge allows this kind of workflow during a PR without having it bleed into the final history.

Do we want a .github/contributing.md to go along with this? (Can we just lift one off of another pydata project?)

I see that as separate.  That is information that a newcomer should be
aware of like write tests, check style, document functions, etc..  This
issue is about how people with commit access should manage things.
On Tue, Sep 5, 2017 at 1:04 PM, Christopher J. Wright <
<EMAIL_ADDRESS>wrote:

Do we want a .github/contributing.md to go along with this? (Can we just
lift one off of another pydata project?)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrocklin/streamz/issues/61#issuecomment-327240959,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszLzJWrddXU0Zim1mEqQ5Iq5w7-0Zks5sfX87gaJpZM4PNN9X
.

That's fair (maybe github should have an advanced contributing guide). Do you want to enshrine this information somewhere? If so, where?

In dask I tend to just informally tell individuals when they get commit
rights.  Happy with whatever
On Tue, Sep 5, 2017 at 1:12 PM, Christopher J. Wright <
<EMAIL_ADDRESS>wrote:

That's fair (maybe github should have an advanced contributing guide). Do
you want to enshrine this information somewhere? If so, where?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrocklin/streamz/issues/61#issuecomment-327243147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszCk_oUYrImEj9A0GF22vgPqqPJEwks5sfYDzgaJpZM4PNN9X
.

I am fine with whichever. Personally, I do like micro commits as they could be useful for code forensics. But the PR's can also serve this (assuming that we can still see comments on outdated diffs after the history has been modified?).

Perhaps we should have a suggestion message on the commits, with rebase instructions, such as:
To squash your commits, please type:
git rebase -i HEAD~N
where N is the number of commits you want to squash. You will be shown a list of commits. Please replace pick with squash with each commit except the latest. When finished, you will be prompted for a commit message. Please write as detailed (but terse) of a commit as you can. Remember to keep the first line short, and add the longer details two lines below.
When finished, you will have to force push to your branch:
git push origin mybranch -f
where origin is the alias to your remove and mybranch is your branch.

I don't think we need to impose this on contributors.  Instead, when
merging, we can select the "Squash and Merge" option for the green button.
This will do the squashing automatically.
On Thu, Sep 28, 2017 at 11:36 AM, Julien Lhermitte<EMAIL_ADDRESS>
wrote:

Perhaps we should have a suggestion message on the commits, with rebase
instructions, such as:
To squash your commits, please type:
git rebase -i HEAD~N
where N is the number of commits you want to squash. You will be shown a
list of commits. Please replace pick with squash with each commit except
the latest. When finished, you will be prompted for a commit message.
Please write as detailed (but terse) of a commit as you can. Remember to
keep the first line short, and add the longer details two lines below.
When finished, you will have to force push to your branch:
git push origin mybranch -f
where origin is the alias to your remove and mybranch is your branch.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrocklin/streamz/issues/61#issuecomment-332875569,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszG9-rO4CGztzfxWl23mQmo3tptLiks5sm7zqgaJpZM4PNN9X
.

thanks, I was not aware of this!

@jrmlhermitte - that level of git experience is so far above most analysts that you'd be excluding a lot of people and introducing a huge barrier to contribution. As @mrocklin says the GitHub UI can do that for you and that can even be enforced by the repo settings.

I think this issue was really aimed at all those who have merging privileges, since we can do the squash via github and its our responsibility to make sure that the history is as we expect it.

so we've been squashing and merging. Should we write up some developer documentation to close this?


Update JPG regex

This PR contains a:

[ ] bugfix
[ ] new feature
[ ] code refactor
[ ] test update
[x] typo fix
[ ] metadata update

Motivation / Use-Case
JPG and JPEG both stand for the Joint Photographic Experts Group image format, have the same meaning and are interchangeable.

Thanks for PR

Thank you as well 👍


PP-3676 Fixed attribute value Swagger error

WHAT

When we have space in the name we receive $ref values must be RFC3986-compliant percent-encoded URIs error

with @georgeracu

@alexbishop1 yes, we could add %20, but we actually decided to go with default behaviour (the name of the class) as described in io.swagger.annotations.ApiModel#value  :
    /**
     * Provide an alternative name for the model.
     * <p>
     * By default, the class name is used.
     */


Invalid buildNumber NaN   on IOs

Build/Submit details page URL
https://expo.dev/accounts/drleos/projects/test_app/submissions/b48721a5-4795-4406-bae2-a0e55c1177d7
Summary
When trying to build for "eas build --platform ios"
I get this error :
"
Invalid buildNumber NaN
Error: build command failed."
However, I cannot get this to work, whatever I try
Managed or bare?
bare
Environment
expo-env-info:
expo-env-info 1.2.1 environment info:
System:
OS: macOS 15.1.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.20.4 - /opt/homebrew/opt/node@18/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.7.0 - /opt/homebrew/opt/node@18/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.0, iOS 18.0, macOS 15.0, tvOS 18.0, visionOS 2.0, watchOS 11.0
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12483815
Xcode: 16.0/16A242d - /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config: ~19.0.1 => 19.0.1
expo: ^50.0.20 => 50.0.21
expo-router: ~3.4.10 => 3.4.10
react: 18.2.0 => 18.2.0
react-native: 0.73.6 => 0.73.6
react-native-web: ~0.19.6 => 0.19.13
npmGlobalPackages:
eas-cli: 13.4.1
Expo Workflow: bare
npx expo-doctor

✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for issues with Metro config
✔ Check npm/ yarn versions
✔ Check if the project meets version requirements for submission to app stores
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check native tooling versions
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✖ Check that native modules use compatible support package versions for installed Expo SDK
Error output
When trying to build for "eas build --platform ios"
I get this error :
"
Invalid buildNumber NaN
Error: build command failed."
Reproducible demo or steps to reproduce from a blank project
When trying to build for "eas build --platform ios"
I get this error :
"
Invalid buildNumber NaN
Error: build command failed."
However this is my app.json:
{
"expo": {
"name": "lamine",
"scheme": "index",
"slug": "test_app",
"version": "1.0.8",
"orientation": "portrait",
"icon": "./assets/icon.png",
"userInterfaceStyle": "light",
"splash": {
"image": "./assets/splash.png",
"contentFit": "contain",
"backgroundColor": "#5e17eb"
},
"assetBundlePatterns": [
"**/*"
],
"ios": {
"supportsTablet": true,
"bundleIdentifier": "ios.lamine.test",
"buildNumber": "4.0.0"
And this is my eas.json
{
"cli": {
"version": ">= 4.1.2",
"appVersionSource": "remote"
},
"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"android": {
"buildType": "app-bundle",
"gradleCommand": ":app:assembleRelease"
}
},
"preview": {
"distribution": "internal"
},
"production": {
"autoIncrement": true
Thanks in advance,

Seems like a bug on our end 🤔
What's the output of eas build:version:get if you run it locally? Would you mind running the eas build command with EXPO_DEBUG=1 so I can see a whole stack trace?


List: Add example in Storybook with list of links with icons

https://storybook.designsystemet.no/?path=/docs/felles-list--docs
Add example in Storybook with list of links with icons

This has to be done in CSS by the users, we dont need example in storybook.


List component "simple expansion" styling issue

Notice in the design overview for list, the content container for the expanded list item has a border and dropshadow to distinguish it from the other page elements.
But then in the pf-ng component, there is no border or dropshadow around the expanded content container (you'll need to select the "Simple Expansion" checkbox in the Basic/Compound Expansion list demos to see it in action.
Finally, here's an example implementation that showcases the proper html/css used to achieve this. On the surface it looks like the issue is misalignment of the html/css.

Not certain if the drop shadow is a more recent addition, but it's an easy fix. We simply need to apply the 'active' style when the row is expanded, like so:
<div class="list-pf-item active"...

Fixed with:
https://github.com/patternfly/patternfly-ng/pull/370
https://github.com/patternfly/patternfly/pull/1070


v0.4.0 - opacity in widget extension got key as positioned parameter

Opacity method in widget extension got key as positioned parameter in 0.4.0 leading to compile errors for existing code.

fixed in hotfix


Unable to build flutter app with flutter 3.19 new Gradle structure

Describe the bug
Now building the apk of a brand new created, flutter apps try to write in read only nix folders.
Steps To Reproduce
Steps to reproduce the behavior:

Set up a flake like this :  ( this one is pretty complete because my app has a lot of deps

{
  inputs = {
    nixpkgs.url = "nixpkgs/nixpkgs-unstable";

    flake-parts = {
      url = "github:hercules-ci/flake-parts";
      inputs.nixpkgs-lib.follows = "nixpkgs";
    };
  };

  outputs = {
    self,
    nixpkgs,
    flake-parts,
    ...
  } @ inputs:
    flake-parts.lib.mkFlake {inherit inputs;} {
      systems = ["x86_64-linux" "aarch64-linux" "x86_64-darwin" "aarch64-darwin"];
      perSystem = {
        pkgs,
        system,
        lib,
        ...
      }: {
        devShells.default = let
          pkgs = import nixpkgs {
            inherit system;
            config = {
              allowUnfree = true;
              android_sdk.accept_license = true;
            };
          };
          melos = pkgs.callPackage ./nix/melos { };
          buildToolsVersionForAapt2 = "34.0.0-rc4";
          androidComposition = pkgs.androidenv.composeAndroidPackages {
            # Installing both version for aapt2 and version that flutter wants
            buildToolsVersions = [buildToolsVersionForAapt2 "30.0.3"];
            platformVersions = ["34" "33" "31" "30"];
            abiVersions = ["armeabi-v7a" "arm64-v8a" "x86" "x86_64"];
            includeEmulator = true;
            emulatorVersion = "34.1.9";
            toolsVersion = "26.1.1";
            platformToolsVersion = "33.0.3";
            includeSources = false;
            includeSystemImages = false;
            systemImageTypes = ["google_apis_playstore"];
            # cmakeVersions = [ "3.10.2" ];
            includeNDK = true;
            # ndkVersions = [ "22.0.7026061" ];
            useGoogleAPIs = false;
            useGoogleTVAddOns = false;
            extraLicenses = [
              "android-googletv-license"
              "android-sdk-arm-dbt-license"
              "android-sdk-license"
              "android-sdk-preview-license"
              "google-gdk-license"
              "intel-android-extra-license"
              "intel-android-sysimage-license"
              "mips-android-sysimage-license"
            ];
          };
          androidSdk = androidComposition.androidsdk;
          PWD = builtins.getEnv "PWD";
        in
          pkgs.mkShell {
            CHROME_EXECUTABLE = lib.getExe pkgs.chromium;
            ANDROID_SDK_ROOT = "${androidSdk}/libexec/android-sdk";
            ANDROID_NDK_ROOT = "${androidSdk}/libexec/android-sdk/ndk-bundle";
            ANDROID_AVD_HOME = "${PWD}/.android/avd";
            ANDROID_HOME = "${androidSdk}/libexec/android-sdk";
            FLUTTER_SDK = "${pkgs.flutter}";
            GRADLE_OPTS = "-Dorg.gradle.project.android.aapt2FromMavenOverride=${androidSdk}/libexec/android-sdk/build-tools/${buildToolsVersionForAapt2}/aapt2";
            LD_LIBRARY_PATH = "${PWD}/apps/onyx/build/linux/x64/debug/bundle/lib/:${PWD}/apps/onyx/build/linux/x64/release/bundle/lib/:${PWD}/apps/onyx/build/linux/x64/profile/bundle/lib/";
            buildInputs = with pkgs; [
              chromium
              flutter
              melos
              jdk17
              androidSdk
              at-spi2-core
              clang
              dart
              dbus
              util-linux
              cmake
              ninja
              libsecret
              android-tools
              pkg-config
              gtk3
              glib
              pcre2
              pcre
              libselinux
              libsepol
              libthai
              libdatrie
              xorg.libXdmcp
              libxkbcommon
              xorg.libXtst
              libepoxy
              libgcrypt
              libgpg-error
              apksigner
              gnome.zenity
              ];
          };
        formatter = pkgs.alejandra;
      };
    };
}

run flutter create {name of project}
run flutter build apk

Expected behavior
The build failed because flutter does not have the right to write in some folders
[user@system:~]$ flutter build apk

FAILURE: Build failed with an exception.

* Where:
Settings file '/home/eymeric/code_bidouille/projet/oloid/onyx/apps/test/android/settings.gradle' line: 21

* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> A problem occurred configuring project ':gradle'.
   > Could not create service of type OutputFilesRepository using ExecutionGradleServices.createOutputFilesRepository().
      > Failed to create parent directory '/nix/store/83gcq64ghi2wvgrhlw8frafk23a8ndzc-flutter-wrapped-3.19.0-sdk-links/packages/flutter_tools/gradle/.gradle' when creating directory '/nix/store/83gcq64ghi2wvgrhlw8frafk23a8ndzc-flutter-wrapped-3.19.0-sdk-links/packages/flutter_tools/gradle/.gradle/buildOutputCleanup'

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s
Running Gradle task 'assembleRelease'...                            3,2s
Gradle task assembleRelease failed with exit code 1

Additional context
There were a previous similar issue fixable by modifying the build.gradle but because it changed, the previous modification from here is not applicable. (https://discourse.nixos.org/t/problem-building-flutter-app-for-android/35593/2)
Notify maintainers

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
 - host os: `Linux 6.1.77, NixOS, 24.05 (Uakari), 24.05.20240216.5863c27`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/problem-building-flutter-app-for-android/35593/3

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/flutter-development-in-nixos/39181/5

@FlafyDev no idea on how to fix this? (because you made the pr #289534 )

Ah sorry I didn't know about this issue("notify maintainers" is empty)
I'll try to figure out how it works and hopefully find a fix..

@FlafyDev For reference, this issue i believe is a duplicate of  #260278 and I've been experiencing this issue too.

@jtojnar @hedning @amaxine @bobby285271 @dasj19
This issue is also in NixOS 23.11 Stable. Should the flutter package version be reverted to an older one until this is fixed?

@FlafyDev Did you find anything to fix the problem?

Any updates on this?

I managed to build with flutter 3.19.0 the default flutter project.
I had to use the following flake: https://gist.github.com/FlafyDev/ef5e4f745f924f9980c931da588dbf9d (this is just what I used to make it work. there are probably other ways as well)
And also, since gradle has this line in <proj>/android/settings.gradle:
includeBuild("${settings.ext.flutterSdkPath}/packages/flutter_tools/gradle")

it tries to create a .gradle directory in Flutter's sdk, which on NixOS would be readonly.
To get around this I copied the contents of the directory to a new writable directory and changed the path.
This is ofc not an ideal solution and I'm currently looking to how(or if) I can change the .gradle path from Flutter's SDK. I don't know gradle very well...

After a lot of trial and error with gradle, I managed to find a solution.
Can anybody test this patch to nixpkgs? @hatch01
diff --git a/pkgs/development/compilers/flutter/versions/3_19/patches/gradle-tools-wrapper.patch b/pkgs/development/compilers/flutter/versions/3_19/patches/gradle-tools-wrapper.patch
new file mode 100644
index<PHONE_NUMBER>00..e3943fb394df
--- /dev/null
+++ b/pkgs/development/compilers/flutter/versions/3_19/patches/gradle-tools-wrapper.patch
@@ -0,0 +1,28 @@
+Adds an intermediate gradle build to change flutter_tools' gradle project from
+creating `build` and `.gradle` directories in the nix store.
+This patch moves them to "$HOME/.cache/flutter/nix-flutter-tools-gradle/$engineShortRev"
+diff --git a/packages/flutter_tools/gradle/settings.gradle b/packages/flutter_tools/gradle/settings.gradle
+new file mode 100644
+index<PHONE_NUMBER>..b2485c94b4
+--- /dev/null
++++ b/packages/flutter_tools/gradle/settings.gradle
+@@ -0,0 +1,19 @@
++rootProject.buildFileName = "/dev/null"
++
++def engineShortRev = (new File("$settingsDir/../../../bin/internal/engine.version")).text.take(10)
++def dir = new File("$System.env.HOME/.cache/flutter/nix-flutter-tools-gradle/$engineShortRev")
++dir.mkdirs()
++def file = new File(dir, "settings.gradle")
++
++file.text = """
++rootProject.projectDir = new File("$settingsDir")
++apply from: new File("$settingsDir/settings.gradle.kts")
++
++gradle.allprojects { project ->
++  project.beforeEvaluate {
++    project.layout.buildDirectory = new File("$dir/build")
++  }
++}
++"""
++
++includeBuild(dir)

For me, it does not work.
I believe I am running the patched version. I applied the patches and changed inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; to nputs.nixpkgs.url = "path:/home/miki/prg/nixpkgs";.
AAPT2 aapt2-7.3.0-8691043-linux Daemon #0: Unexpected error output: cannot execute /home/miki/.gradle/caches/transforms-3/155b5be4d4da86b2b755912971e8643d/transformed/aapt2-7.3.0-8691043-linux/aapt2: You are trying to run an unpatched binary on nixos, but you have not configured NIX_LD or NIX_LD_x86_64-linux. See https://github.com/Mic92/nix-ld for more details
AAPT2 aapt2-7.3.0-8691043-linux Daemon #2: Unexpected error output: cannot execute /home/miki/.gradle/caches/transforms-3/155b5be4d4da86b2b755912971e8643d/transformed/aapt2-7.3.0-8691043-linux/aapt2: You are trying to run an unpatched binary on nixos, but you have not configured NIX_LD or NIX_LD_x86_64-linux. See https://github.com/Mic92/nix-ld for more details
AAPT2 aapt2-7.3.0-8691043-linux Daemon #1: Unexpected error output: cannot execute /home/miki/.gradle/caches/transforms-3/155b5be4d4da86b2b755912971e8643d/transformed/aapt2-7.3.0-8691043-linux/aapt2: You are trying to run an unpatched binary on nixos, but you have not configured NIX_LD or NIX_LD_x86_64-linux. See https://github.com/Mic92/nix-ld for more details

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
> Multiple task action failures occurred:
   > A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
      > AAPT2 aapt2-7.3.0-8691043-linux Daemon #2: Daemon startup failed
        This should not happen under normal circumstances, please file an issue if it does.
   > A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
      > AAPT2 aapt2-7.3.0-8691043-linux Daemon #1: Daemon startup failed
        This should not happen under normal circumstances, please file an issue if it does.
   > A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
      > AAPT2 aapt2-7.3.0-8691043-linux Daemon #0: Daemon startup failed
        This should not happen under normal circumstances, please file an issue if it does.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 22s

This is quite amazing. When can I expect to see this in master, and when `nixpkgs?

After a lot of trial and error with gradle, I managed to find a solution. Can anybody test this patch to nixpkgs? @hatch01
diff --git a/pkgs/development/compilers/flutter/flutter.nix b/pkgs/development/compilers/flutter/flutter.nix
index 03c2968f4ab9..627a40dcb1db 100644
--- a/pkgs/development/compilers/flutter/flutter.nix
+++ b/pkgs/development/compilers/flutter/flutter.nix
@@ -82,6 +82,9 @@ let
           "dartSdkVersion": "${dart.version}"
         }
         EOF
+
+        # Suppress error now that `.gradle` location changed from our patch.
+        mkdir -p "$out/packages/flutter_tools/gradle/.gradle"
       '';

       installPhase = ''
diff --git a/pkgs/development/compilers/flutter/versions/3_19/patches/gradle-tools-wrapper.patch b/pkgs/development/compilers/flutter/versions/3_19/patches/gradle-tools-wrapper.patch
new file mode 100644
index<PHONE_NUMBER>00..e3943fb394df
--- /dev/null
+++ b/pkgs/development/compilers/flutter/versions/3_19/patches/gradle-tools-wrapper.patch
@@ -0,0 +1,28 @@
+Adds an intermediate gradle build to change flutter_tools' gradle project from
+creating `build` and `.gradle` directories in the nix store.
+This patch moves them to "$HOME/.cache/flutter/nix-flutter-tools-gradle/$engineShortRev"
+diff --git a/packages/flutter_tools/gradle/settings.gradle b/packages/flutter_tools/gradle/settings.gradle
+new file mode 100644
+index<PHONE_NUMBER>..b2485c94b4
+--- /dev/null
++++ b/packages/flutter_tools/gradle/settings.gradle
+@@ -0,0 +1,19 @@
++rootProject.buildFileName = "/dev/null"
++
++def engineShortRev = (new File("$settingsDir/../../../bin/internal/engine.version")).text.take(10)
++def dir = new File("$System.env.HOME/.cache/flutter/nix-flutter-tools-gradle/$engineShortRev")
++dir.mkdirs()
++def file = new File(dir, "settings.gradle")
++
++file.text = """
++rootProject.projectDir = new File("$settingsDir")
++apply from: new File("$settingsDir/settings.gradle.kts")
++
++gradle.allprojects { project ->
++  project.beforeEvaluate {
++    project.layout.buildDirectory = new File("$dir/build")
++  }
++}
++"""
++
++includeBuild(dir)

This works perfectly using my personal flake!
Thank you very much!

Good to hear it works! I'll make a PR..

When can I expect to see this in master, and when `nixpkgs?

After I make a PR and it gets merged it will be on master. Probably a few days after merging it will be on unstable

Thank you @FlafyDev. I am interested in contributing to the nixpkgs. Would it be sensible for me to create a test which creates a new Flutter app and attempts to build it in the several available modes? It sees this test would prevent breaking changes such as the one that led to this issue.

Thank you @FlafyDev. I am interested in contributing to the nixpkgs. Would it be sensible for me to create a test which creates a new Flutter app and attempts to build it in the several available modes (aar apk appbundle bundle linux web )? It sees this test would prevent breaking changes such as the one that led to this issue.

Creating tests would definitely be helpful! There is an issue about it https://github.com/NixOS/nixpkgs/issues/262507.
Though currently there isn't a way to build a Flutter apk in a pure Nix derivation, so the tests would most likely need to be impure and I don't know if you can do it in Nixpkgs.

Hi, with a recent nixpkgs update, the exact same issue came back
The issue appeared between :
        'github:NixOS/nixpkgs/4877ea239f4d02410c3516101faf35a81af0c30e' (2024-08-13)
      → 'github:NixOS/nixpkgs/b833ff01a0d694b910daca6e2ff4a3f26dee478c' (2024-09-01)

Is it because of 3.24?
Can you check if you're getting the error on 3.22 or 3.24 (or both)

@FlafyDev
only on flutter 3.24 github:NixOS/nixpkgs/b833ff01a0d694b910daca6e2ff4a3f26dee478c I got the error about the flutter plugin
Running Gradle task 'assembleRelease'...

FAILURE: Build failed with an exception.

* Where:
Settings file '/home/<project path>/android/settings.gradle' line: 25

* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> A problem occurred configuring project ':gradle'.
   > Could not create service of type OutputFilesRepository using ExecutionGradleServices.createOutputFilesRepository().
      > Failed to create directory '/nix/store/wp7165dbyc8w8ng10qaxkfsrrr9rc5hs-flutter-wrapped-3.24.1-sdk-links/packages/flutter_tools/gradle/.gradle/buildOutputCleanup'

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3s
Running Gradle task 'assembleRelease'...                            4.0s
Gradle task assembleRelease failed with exit code 1

Settings file '/home//android/settings.gradle' line: 25 contains
plugins {
    id "dev.flutter.flutter-plugin-loader" version "1.0.0" << 25th line
    id "com.android.application" version "7.3.0" apply false
}

on flutter 3.22 github:NixOS/nixpkgs/4877ea239f4d02410c3516101faf35a81af0c30e I have successfully built the project

initial commit after which the error started is github:NixOS/nixpkgs/c1ce56e9c606b4cd31f0950768911b1171b8db51 when the 3.24 version update was made

will be fixed whit #341133

I am still getting this error on flutter v3.24.1. I can see the redirect settings.gradle in the nix store under flutter-tools, as well as the created directories under $HOME/.cache/flutter/nix-flutter-tools-gradle/ but I'm still getting Failed to create directory '/nix/store/cpgyn3rn3a117nv4s1g7j5ajgbdkplby-flutter-wrapped-3.24.1-sdk-links/packages/flutter_tools/gradle/.gradle/buildOutputCleanup' when trying to do a gradle sync in a flutter project in Android Studio.

Is there a local cache, like .direnv or .devenv etc, that wll causes the flutter in the working folder to be not fresh

I am still getting this error on flutter v3.24.1. I can see the redirect settings.gradle in the nix store under flutter-tools, as well as the created directories under $HOME/.cache/flutter/nix-flutter-tools-gradle/ but I'm still getting Failed to create directory '/nix/store/cpgyn3rn3a117nv4s1g7j5ajgbdkplby-flutter-wrapped-3.24.1-sdk-links/packages/flutter_tools/gradle/.gradle/buildOutputCleanup' when trying to do a gradle sync in a flutter project in Android Studio.

There is a .direnv cache, but I've removed it, both by doing nix-direnv-reload and by simply deleting the .direnv directory, but neither seem to have solved the problem.

Hm, what is interesting is that if I look in the ~/.cache/flutter/nix-flutter-tools-gradle/ directory, it is clear that Android Studio is actually using that directory to build in. It just looks like its ALSO trying to use the nix store directory for something.

So I'm still dealing with this issue, and one thing I've noticed is that it only happens in Android Studio when gradle tries to sync. Running flutter from the command line works fine, which is interesting.

Was there a fix for this?

On my, side, I was now able to build with the flutter 3.19 .
(https://github.com/onyx-lyon1/onyx if you want to look at my flake and flutter config)


Research with sites that have signed up for SR but have not started reporting

There's a significant delta between sites that have signed up for SimpleReport and sites that have started reporting. We want to understand why sites are signing up and not following through to identify whether there are obstacles in the process we can help clear.

[x] Talk to Sparkle about: why sites drop out + why sites sign up and don't report Notes from Sparkle meeting
[x] Run analysis in Metabase to identify target participants Metabase analysis doc
[x] Reach out to target participants Outreach doc
[x] Meet w/ participants
[ ] Synthesize & deliver findings

Schedule 30 minutes (prioritize attendance from Alicia, Sparkle, Leslie) on Monday or Tuesday.


Can't run kafl fuzz after deployment

No errors while installing.
I tried already the 5... kernel and the 6.0.0 kernel on my own Systems, now I installed an Ubuntu 22.04.4 LTS and ran
make deploy
reboot
make deploy (to see if support_test will pass, it does!)
make env
kafl fuzz

To me it seems nyx can't run on the 13th Gen CPU? Maybe there are new mitigations?
Reduced output of cat /proc/cpuinfo
processor	: 19
vendor_id	: GenuineIntel
cpu family	: 6
model		: 183
model name	: 13th Gen Intel(R) Core(TM) i5-13600K
stepping	: 1
microcode	: 0x11d
cpu MHz		: 1100.005
cache size	: 24576 KB
physical id	: 0
siblings	: 20
core id		: 31
cpu cores	: 14
apicid		: 62
initial apicid	: 62
fpu		: yes
fpu_exception	: yes
cpuid level	: 32
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities
vmx flags	: vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs ept_mode_based_exec tsc_scaling usr_wait_pause
bugs		: spectre_v1 spectre_v2 spec_store_bypass swapgs eibrs_pbrsb
bogomips	: 6988.80
clflush size	: 64
cache_alignment	: 64
address sizes	: 46 bits physical, 48 bits virtual
power management:

After disabling cpu mitigations via grub (mitigations=off) , it seems to fail at another part:

Okey, I think it is working now because of mitigations=off
Maybe I will try to disable e-cores if more problems arise (like @schumilo suggested)

Hi @GanbaruTobi,
thank you for this detailed issue, and your investigation regarding mitigations=off !
I've opened an issue to track this, and we are working on providing an upgraded kAFL compatible kernel that might solve this problem.

Hi @GanbaruTobi,
I've just released kAFL v0.9, with a Nyx kernel upgraded to 6.8.
I believe this should solve your issue without having to put the mitigations=off workaround.
If you could test this kernel and give me a feedback, I would very much appreciate !


HDFS-16485. [SPS]: allow re-satisfy path after restarting sps process

When SPSPathIdProcessor thread call getNextSPSPath(), it get the pathId from namenode and namenode will also remove this pathId from pathsToBeTraveresed queue.
public Long getNextPathId() {
  synchronized (pathsToBeTraveresed) {
    return pathsToBeTraveresed.poll();
  }
}

If SPS process restart, this path will not continue the move operation until namenode restart.
So we want to provide a way for the SPS to continue performing the move operation after SPS restart.
First solution:

When SPSPathIdProcessor thread call getNextSPSPath(), namenode return pathId and then move this pathId to a pathsBeingTraveresed queue;

After SPS finish a path movement operation, it call a rpc to namenode to remove this pathId from pathsBeingTraveresed queue;

If SPS restart, SPSPathIdProcessor thread should call a rpc to namenode to get all pathId from pathsBeingTraveresed queue;

Second solution:
We added timeout detection in the application layer, if a path does not complete the movement within the specified time, we can re-satisfy this path even though it has "hdfs.sps" xattr already.
We choose the second solution because the first solution will add more rpc operation and may affect namenode performance.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 10s

trunk passed

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
1m 23s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 30s

trunk passed

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 50s

trunk passed

+1 :green_heart:
shadedclient
29m  2s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 44s

the patch passed

+1 :green_heart:
compile
1m 50s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
1m 50s

the patch passed

+1 :green_heart:
compile
1m 37s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  8s

the patch passed

+1 :green_heart:
mvnsite
1m 43s

the patch passed

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 48s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 39s

the patch passed

-1 :x:
shadedclient
29m  2s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m  3s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

116m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4033/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4033

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux da0b58da701f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0c5d41c3b57d7821508c932df0327cf2ac782076

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4033/1/testReport/

Max. process+thread count
545 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4033/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 11s

trunk passed

+1 :green_heart:
compile
1m 29s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 29s

trunk passed

+1 :green_heart:
javadoc
1m  2s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 33s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 15s

trunk passed

+1 :green_heart:
shadedclient
22m 41s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 20s

the patch passed

+1 :green_heart:
compile
1m 21s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
1m 21s

the patch passed

+1 :green_heart:
compile
1m 15s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 50s

the patch passed

+1 :green_heart:
mvnsite
1m 22s

the patch passed

+1 :green_heart:
javadoc
0m 52s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 26s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 17s

the patch passed

+1 :green_heart:
shadedclient
22m 25s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
234m 31s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

334m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4033/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4033

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux f6f62864d09b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e6516551f23ca856bfa0f35561d0f6f2ca4ffc28

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4033/2/testReport/

Max. process+thread count
3256 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4033/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Training progress stopped

I am training on a custom dataset of ~22,000 images and everything was going very well until model stopped converging. The results are quite good most of the time so I reduced my training data to the 5000 highest loss images and ran 10 epochs on them. The loss has not reduced in that time in any significant way (pink is ssim loss, blue is psnr loss, and yellow is the train loss)

I am wondering if it would be best to
a) reduce LR
b) change optimizer to SGD
c) modify the scheduler
or some combination of those things.
Thank you for any advice you can share.

I recommend exploring the following avenues:
Hyperparameter Tuning: The configurations you mentioned such as LR, optimizer, etc.
In-depth Data Analysis: Dive deeper into your dataset to understand the specific characteristics of the shadows. Analyzing their distribution, intensity, and contextual relationships within the images may reveal patterns that could inform model adjustments.
Advanced Data Augmentation: Introducing innovative data augmentation techniques can greatly enhance the model's understanding of shadow variability. Techniques such as random shadow insertion, varying shadow angles and sizes, or even synthesizing new shadow examples could enrich the training set and improve the model's ability to generalize to unseen shadows.

The pattern that I can see is that the model struggles most when the color of the paper is different from standard. I will try adding more varied images of this sort.


[Bug]: bad contrast color for button 🪲

Description

The color used for the button has a very much bad contrast and affects the accessibility, we need to fix this by adding good contrast colors like white to the button to resolve this bug

Expected Behavior

Button must want to have a good contrast color for the caption inside it.

Show us the trouble with screenshots

Which browsers are affected?
Firefox
Which OS are affected?
linux
Enter the version of your web browser
114.54
Device?
Desktop
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hey there @Vaishnavi-Patil2211, @akshathar-navada 👋🏻,
Please make sure to assign this issue to me as soon as possible so that i can proceed my progress regarding fixing this issue.
Thank you!


bloodborne-wiki.com eligible?

Uncertain how well this would gel with the goals of Indie Wiki Buddy but I figure it's worth pitching.
The main wiki that pops up when you google "Bloodborne Wiki" is the Fextralife wiki (https://bloodborne.wiki.fextralife.com/Bloodborne+Wiki). It's not great; the information quality is lacking, the site UI is clunky, and Fextralife is essentially a wikifarm. They run a network of wikis which seem to exist chiefly for the sake of inflating the viewcount of the operators' Twitch stream, which is embedded on every page.
The site that I would suggest to replace it, https://www.bloodborne-wiki.com, is not technically a wiki; the site's administrator, Meph, maintains the site alone and does all edits personally. However, Meph is pretty plugged into the community, and routinely adds new information on request, with lots of parts of the site being guides, charts, etc. written by attributed community members. The site is vastly more popular within the community than the Fextralife one; it has much more information than the Fextralife one, including a large repository of TCRF style pre-release information and material from supplements like the artbook, and the information is very accurate, mostly being collated from reliable sources like datamining, in-game testing, and official published material. Meph's site is also fully independent, being paid for by donations and out of Meph's own pocket.
I totally understand if the lack of direct user edits disqualifies bloodborne-wiki.com from Indie Wiki Buddy inclusion, but I think it's at least worth considering. Compared to the Fextralife wiki, it certainly feels more like a community wiki, and it's a vastly superior informational site.

Thanks for the submission and details!
This is a tough one, because it definitely looks like a great site that I'd love to point people towards. That being said, I'm wary of expanding the extension's scope to non-wikis, as it can cause difficulties down the line with inclusion criteria, competing fan sites, and users having unclear expectations of where they'll end up.
On the technical side, another challenge is that bloodborne-wiki.com doesn't have consistent paths for content pages (e.g. /2015/04/executioners.html vs /2015/03/saw-spear.html vs. /p/covenants.html). So I believe we could only point people to the homepage, or perhaps the search page -- which isn't terrible, just not an ideal or consistent experience.
So at the moment I'm inclined to say no, but I'll keep this in the back of my mind for how we could potentially support quality "almost-wikis" in the future, once the extension is more developed and stable.
I'll leave this open for now in case anyone has ideas to share.


Likes page doesn't show restaurants

Hi,
For some reason the likes page doesn't show the list with liked restaurants.
Does anyone have any idea how i can fix this?

Try removing the route to /likes in routers.js. Probably something is going wrong because there is now .get('/likes) in 2 files.

this worked for me

Yess that works, thanks!!


luci-app-upnp: Add Expires to port map listing

Status/overview UI:

Screenshot 23.05 release
The Port Control Protocol (PCP) is the successor to NAT-PMP, has similar protocol concepts and packet formats, but adds support for IPv6 port maps and options/extensions. For more information, see:
Port Mapping Protocols Overview and Comparison 2024: About UPnP IGD & PCP/NAT-PMP
https://github.com/Self-Hosting-Group/wiki/wiki/Port-Mapping-Protocols-Overview
Maintainer: @jow-
Previous improvement: #7407

OK, did you re-run i18n-sync after the js changes?

Above?

Sure. Test the CSS for that column. But it might be a bit over-engineered to do so. Maybe Expiry would be better?

Add the equivalent style to that column.

Merged. Thanks @Self-Hosting-Group


ATV-1 | Add content input for Document creation

Description :sparkles:
The Document create endpoint does not support submitting the content, which is the main reason of the service, so without it the whole Document is useless. This fix adds the content to the serializers to allow saving it.
Issues :bug:
Closes :no_good_woman:
ATV-1: As an anonymous user, I want to submit a public RFI, to obtain a public document
Related :handshake:
#10
Testing :alembic:
Automated tests :gear:
$ pytest documents/tests/test_api_create_document.py

Manual testing :construction_worker_man:
curl --location --request POST 'http://localhost:8000/v1/documents/' \
--header 'X-Api-Key: YOUR-API-KEY' \
--form 'business_id="1234567-8"' \
--form 'transaction_id="34b9f4b4c9774ff8b2fa0827b2ace014"' \
--form 'tos_function_id="c1f23d3a9eea4b43829cba5a68401799"' \
--form 'tos_record_id="ba3cb4fabe9b45f48d04db0a4422bf41"' \
--form 'metadata="{\"created_by\": \"alex\"}"' \
--form 'type="contract"' \
--form 'content="{\"value\": \"secret_stuff\"}"' \
--form 'status="yes"'

Response:
{
    "id": "ef5402b8-500c-4f97-bf77-f92bf9abea20",
    "created_at": "2021-08-31T11:22:07.403313+03:00",
    "updated_at": "2021-08-31T11:22:07.403335+03:00",
    "status": "yes",
    "type": "contract",
    "transaction_id": "34b9f4b4c9774ff8b2fa0827b2ace014",
    "user_id": null,
    "business_id": "1234567-8",
    "tos_function_id": "c1f23d3a9eea4b43829cba5a68401799",
    "tos_record_id": "ba3cb4fabe9b45f48d04db0a4422bf41",
    "metadata": {
        "created_by": "alex"
    },
    "content": {
        "value": "secret_stuff"
    },
    "draft": false,
    "locked_after": null,
    "attachments": []
}

Codecov Report

Merging #16 (d144743) into main (ad91cab) will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   85.18%   85.27%   +0.08%
==========================================
  Files          27       27
  Lines         513      516       +3
  Branches       39       39
==========================================
+ Hits          437      440       +3
  Misses         57       57
  Partials       19       19

Impacted Files
Coverage Δ

documents/serializers/document.py
97.29% <100.00%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


Sessions disappear on Vercel

Environment

Operating System: Darwin
Node Version:     v16.13.1
Nuxt Version:     3.2.0
Nitro Version:    2.2.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      css, build, modules, imports, app, runtimeConfig, session, nuxtTypedRouter, proxy
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Deploy the playground to Vercel
Describe the bug
Sessions can be retrieved for a number of seconds before the next refresh/request receives a blank session with a different id
Additional context
No response
Logs
No response

Vercel uses Cloud Functions which isn't ideal for Session.
I recommend using a real node Server like fly.io or Heroku.


How to render remote markdown using content layer API

📚 Subject area/topic
markdown, content layer api
📋 Suggested page
https://docs.astro.build/en/reference/configuration-reference/#experimentalcontentlayer
📋 General description or bullet points (if proposing new content)
I think that with the new content layer API, rendering remote markdown (from a server or api) is going to be a common use case.
The Astro docs currently says "Astro does not include built-in support for remote Markdown outside of experimental content collections!"
However I was unable to find any further information or examples about rendering remote (server) markdown.
So firstly, I was wondering if there already is an good example that I have missed?
If not, I have got some rough code (shown below) that renders markdown using Astros built in functions that seems to work and might help someone. But I would really like someone to review it and let me know things that can be improved.
Example Loader that renders remote markdown:
import { defineCollection, z } from 'astro:content';
import type { Loader } from "astro/loaders";

function markdownTestLoader({}):Loader {
  return {
    name: "markdown-test-loader",
    load: async ({ config, store, parseData, generateDigest, entryTypes }) => {

      store.clear();

      // Would normally load this JSON data from API.
      // The "content" field has the markdown I want to render
      const dummyAPIData = {
        id: "home",
        title: "Test Markdown Data",
        content: "## Markdown to Render \nTesting markdown rendering.\n- List item 1\n- List item 2"
      }

      const id = dummyAPIData.id;
      const data = await parseData({ id, data:dummyAPIData });
      const body = dummyAPIData.content; // markdown to render next
      const digest = generateDigest(data);

      // Render markdown to HTML using built in Astro markdown render function
      let rendered;
      const markdownEntryType = entryTypes.get(".md");
      if( markdownEntryType?.getRenderFunction ) {
        const render = await markdownEntryType.getRenderFunction(config);
        rendered = await render?.({
          id,
          data,
          body,
          digest
        });
      }

      store.set({ id, data, rendered, digest });
    }
  }
}

// Define collection with loader

const markdownTestCollection = defineCollection({
  loader: markdownTestLoader({}),
  schema: z.object({
    id: z.string(),
    title: z.string(),
    content: z.string()
  })
});

export const collections = {
  'markdownTestCollection': markdownTestCollection
};

The markdown HTML can be displayed on the page using the "render" function and built in "Content" component:
---
import { getCollection, render } from 'astro:content';

export async function getStaticPaths() {
  const pages = await getCollection("markdownTestCollection");
  return pages.map((page) => ({
    params: {
      slug: page.id },
    props: {
      page
    },
  }));
}

const { page } = Astro.props;
const { Content, headings } = await render(page);
---
<h1>{page.data.title}</h1>
<Content />

As I said, I'm sure there are things above that could be done better.
🖥 Reproduction of code samples in StackBlitz
No response

We don't add guides and recipes for experimental APIs, only the refence and examples in the description there. So it won't be added on the docs for v4.
The feature is stabilized on v5, so we can document it there. The docs for the LoaderContext is missing the entryTypes property which enables rendering the different content types. We can add documentation for that.

Thanks for this @johnmw ! Just showing off working code is already very helpful to others, and I appreciate your care in wanting to further make sure that the code is something recommended for others to copy.
Fryuni is right that any docs for this would have to go on our v5 beta docs. I will also ask @ascorbic to take a look to ensure that we end up with something that we'd recommend as a "happy path" as a general model!
If so, then I also agree this is for the Loader API page, in one of two ways:

an example of a loader that fetches remote Markdown (the first code snippet only. I think the other code examples are pretty standard usage once you have the loader configured properly? There's nothing there that seems unique to having built that particular loader?)

or

a link from this page to a full recipe set of instructions that includes everything above, but uses a real data fetch from a real API. This should be something that someone can follow along and have something working in their project at the end.

I agree! Adding it to the Loader API page would work best.

I just want to add that there is a single sentence in the docs that — other than the "outside of experimental content collections" bit — made me go on an hours-long wild goose chase, that being

Once queried, you can render Markdown and MDX entries to HTML using the render() function property. Calling this function gives you access to rendered HTML content, including both a <Content /> component and a list of all rendered headings.

at https://5-0-0-beta.docs.astro.build/en/guides/content-collections/#rendering-body-content
The docs need to specify that the user needs to build that functionality themselves. I'd make a PR but I don't think I know enough about Astro to cover all the bases.
Also, this would be a nice built-in function to have anyway, since, like @johnmw said, rendering markdown is probably one of the common use cases.

Just pinging for freshness here now that the new v5 documentation with stable Content Layer is out! If someone feels there is still an addition to make to the new documentation, please suggest so!

I just want to drop this here, there is a way to fetch remote markdown (probably not officially supported) with the @astrojs/markdown-remark package with frontmatter and headings. My only worry is that it could break anytime, because the @astrojs/markdown-remark is not documented anywhere because it is probably intended only for internal use.
import { defineCollection, reference, z } from "astro:content";
import { locales } from "@i18n-config";
import { glob } from "astro/loaders";
import type { Loader, LoaderContext } from "astro/loaders";
import { createMarkdownProcessor, parseFrontmatter } from "@astrojs/markdown-remark";

const postSchema = z.object({
	translationKey: z.string(),
	title: z.string(),
	pubDate: z.coerce.date(),
	modDate: z.coerce.date().or(z.string()).optional(),
	hidden: z.boolean().optional(),
	description: z.string(),
	featured: z.boolean().default(false).optional(),
	language: z.enum(locales as [string, ...string[]], {
		errorMap: () => ({
			message: "Please select the correct locale!",
		}),
	}),
	image: z
		.object({
			src: z.string(),
			alt: z.string(),
		})
		.or(z.string())
		.optional(),
	tags: z.array(reference("tags")),
	canonicalURL: z.string().optional(),
});

function markdownTestLoader({}): Loader {
	return {
		name: "markdown-test-loader",
		load: async ({ config, store, parseData, generateDigest, logger }: LoaderContext) => {
			store.clear();

			const res = await fetch("https://raw.githubusercontent.com/dallyh/daliborhon.dev/refs/heads/main/src/content/dev/posts/cs/2023-01-01-typography-example.md");
			const text = await res.text();

			const processor = await createMarkdownProcessor(config.markdown);
			const parsedFrontmatter = parseFrontmatter(text);
			const frontmatter = parsedFrontmatter.frontmatter;
			const rendered = await processor.render(parsedFrontmatter.content ?? "");

			const id = `${frontmatter.language}/${frontmatter.translationKey}`;
			logger.info("Loaded post: " + id);
			const data = await parseData({ id, data: frontmatter });
			const digest = generateDigest(data);

			store.set({
				id,
				data,
				digest,
				rendered: {
					html: rendered.code,
					metadata: {
						headings: rendered.metadata.headings,
						frontmatter: frontmatter
					}
				},
			});
		},
	};
}

const posts = defineCollection({
	loader: markdownTestLoader({}),
	schema: postSchema,
});

Just pinging for freshness here now that the new v5 documentation with stable Content Layer is out! If someone feels there is still an addition to make to the new documentation, please suggest so!

Thanks for your work on the new docs @sarah11918 .
It would be nice if there was an officially sanctioned recipe in the docs for rendering remote markdown so we know our own methods won't suddenly break (apologies if this documentation does exist and I missed it).
There are a number of working examples above.
For example with my original 'attempt', it looks like "entryTypes" is still being passed as a parameter to the 'load' function but is still undocumented. Does that mean I shouldn't be using it? Or iscreateMarkdownProcessor(config.markdown) safe to use?
Thanks!

My only worry is that it could break anytime, because the @astrojs/markdown-remark is not documented anywhere because it is probably intended only for internal use.

Yes, I believe it is intended for internal use, and although we have precedence for informing you when even internal things change, it's not guaranteed that we will and we typically don't consider keeping internal API consistent as a priority in development.
Both of the recent examples above do appear to make use of @astrojs/markdown-remark so maybe the first thing we should determine is whether people should be accessing this directly. There is a similar issue open now re: rendering remote Markdown/MDX for RSS feed content that relies instead on using the Container API and accessing those renderers rather than our internal markdown processing. I will have to check with the platform devs and see whether perhaps something more like that is the direction to take here.
I'll ask @delucis to have a look here for similarities/differences with the other issue and what he thinks about these examples!

I think it would make sense to make @astrojs/markdown-remark a public API, but we'd need to discuss it.


build: update gmp to 6.3.0

Additional Information
After bls-signatures#92, GMP is re-enabled for Apple Silicon macOS targets so long as GMP 6.3.0 or higher is used. GMP significantly contributes to performance improvements in bls-signatures, generally to the tune of ~50% (source).
The URL has been changed based on guidance from the Homebrew recipe for gmp (source).
Breaking Changes
None expected.


Maya: Improve error feedback when no renderable cameras exist for ASS family.

Ensure no cameras are renderable.
Publish and validate collection error message.

The collector run smoothly with the renderable camera but once it has been removed, the collector "strangely" errors out with IndexError.

The line which causes this issue is the list with renderable cameras.
renderable = [c for c in cameras if cmds.getAttr("%s.renderable" % c)]

maybe you are right, I find out that the code is built with the AppData folder. And it seems that the script doesn't sync with the script I built along with the system. Let me rebuild it to see how it looks.

Do you always rebuild for testing?

maybe you are right, I find out that the code is built with the AppData folder. And it seems that the script doesn't sync with the script I built along with the system. Let me rebuild it to see how it looks.

Do you always rebuild for testing?

If you said run build.ps1, yes. But if you are talking about env and fetch library.ps, I dont do it always and I dont do it with your fork as often as I did for the main repo.
And I find out that it is actually env and fetch library.ps1. Maybe I need to add your fork remotely into my cloned of main repos and it would be easier to work together.
It works after rebuilt.

Not sure whether you know, but you can run directly from source with run_tray.ps1. Then you dont need to rebuild and question the build.


Uncentered letterbox issue, Unity 2019.3.0f6

Hi,
So I watched your video at this link: https://www.youtube.com/watch?v=ZSQWrH96bew, and was able to get the asset imported and set up; however, I am running into an issue where the black strips are not centered properly on the screen, causing parts of the scene to still be cut out, like in this image:

The game was built for  4:3 aspect ratio, so I set up the letterBox component like this on my main camera:

And these are my camera settings:

Any idea on what I might be doing wrong here?
Thanks!

mmm, It may well be that your camera/layout isn't centered ? To check, in the Unity editor:

Switch to the "Game" tab and in the Resolution drop down, add a new one with a resolution of 2048 by 1536 if you don't already have one

Make sure this is the selected resolution and then switch to the Scene tab

In the scene tab select your main camera. It will show a white gizmo box in the scene. Check that it is centered and encompass your level layout correctly.

I found what is causing the problem, but I still have not been able to find the solution to that problem. So, the letterboxing script works perfectly when I do not have post processing toggled on my scene camera, but as soon as I toggle it, the letter boxing gets uncentered and ruined, like in this video:
https://www.youtube.com/watch?v=xUIIJhi1ggs

Huh, that is odd. Could you tell me post-processing you have set up? I'll go and experiment.

Yes. So the post processing I am using is called Post Processing Stack v2, with the Universal Render Pipeline (URP), inside of a Unity 2d project. I am in Unity version 2019.3.0f6. To set this post processing up, import Post processing from the Package manager, along with Universal RP. Once those are installed, you just right click in assets, Create -> Rendering -> Pipeline Asset. You then click on the pipeline asset made, called WRP I think, and in the inspector, under general, there is a render list, make sure to right click on assets again, go to Create -> Rendering -> 2DRenderer. Go back to the WRP asset inspector, and drag this 2d renderer into the RendererList, then, on this same WRP asset, go to the Post-processing section and switch the drop down to Post Processing V2. You then go to edit, project settings, Graphics. Under graphics, drag the WRP asset into the Scriptable Render Pipeline settings. You should then be able to go back to your test scene, and on the main camera, turn on post processing on its inspector, located under the Rendering section like in the video I shared, and on this same camera, add a component called PostProcessLayer. You should be able to just leave that component default, because I just determined also that having no PostProcessVolume on this still causes the letter box to mess up, but if I toggle this component on and off, the letter box goes from being correct (when Post process layer is toggled on) and incorrect (when Post Process layer is toggled off). Here is a link to the Post Processing documentation on Unity<EMAIL_ADDRESS>And this is the video I used to first install URP: https://www.youtube.com/watch?v=5dzGj9k8Qy8&t=0s, by Brackeys. Its main purpose in our game is for 2d lighting, in addition to the post processing effects.

Cool. Also can you list out which post processing items you have in your stack. In case it is one of them causing the issue. Unless it happens with an "empty stack" ?

Ok, on my post process volume, I had the following post process effects: Vignette, Bloom, and a custom one I wrote that creates flame distortion, but that one is disabled and the issue still occurs. Matter of fact, I was able to delete Post Process volumes in the PostProcessLayer on my camera, inside of the Trigger area, and the problem still occurs, but disabling this Post process layer component causes the letter boxer to work again.


Pointer not refreshing according to current time

The Dial represents the hours of the day and the Pointer points to the current Time block. I had the HA Dashboard open and the Network Tariff Number, located in the center, was updating accordingly. The Time block pointer was not moving and was not in sync with the current Time. I had to refresh/reopen the Dashboard for the Pointer to synchronize and point towards the actual Time block.
Example from yesterday evening:

We were in the 2. Network Tariff and the Network Tariff Number and Time Block Pointer were in sync and showing accurate Values.
We moved from the 2. Network Tariff to the 3. Network Tariff. Network Tariff Number was updated immediately, Time Block Pointer was still pointing to the previous Time Block and wasn't updating.

I hope I explained the issue and you will be able to recreate it.

The fix was merged yesterday  https://github.com/frlequ/network-tariff-card/pull/8. Please update the card.
Please report any issue.

I will do it right away and observe the behaviour. I was just setting up the card yesterday evening and I see now that a new version of the component is available. Thanks for the effort!


[ttx_diff] Make generated fonts easier to find

Previously the fontc output would live in build/{compare}/font.ttf, and the fontmake output would live in build/{compare}/{source}, which was unintuitive.
Now fontc write build/{compare}/fontc.ttf and fontmake writes build/{compare}/fontmake.ttf.

this requires #737

Not sure if this breaks any testing scripts that may live out of repo but the change makes sense to me.

it shouldn't, this change only changes the behaviour of ttx_diff.py, not the compiler itself.


NullabilityFix with no edge info on an inserted bang

Steps to reproduce:

Check out path package at 1.6.2 (git checkout 1.6.2).
Migrate to NNBD (e.g. dart ~/code/dart-sdk/sdk/pkg/dartfix/bin/dartfix.dart --fix=non-nullable --overwrite --outputDir nnbd-i13n .).
Open the migration output for lib/src/context.dart. Hover over the inserted ! in if (this.isRelative(path) && this.isAbsolute(from!)) {

The only reason text is:

node with no info (type(6773))

Two more on the line: !style!.pathsEqual(fromParsed.root!, pathParsed.root!))) {

If we spot this in a new package, we can report and fix it, but the path package has been migrated, so this instance is obsolete.


Vulnerability assessment notes

https://jira.atl.workiva.net/browse/RED-3228
Security +1, HEAD matches the original
Original: https://github.com/github/gh-ost/commit/79ddcecb1fba7f1105d3153edcd69524ccad6451
Workiva: https://github.com/Workiva/gh-ost/commit/79ddcecb1fba7f1105d3153edcd69524ccad6451
The original is a pre-approved tool because it is written by GitHub and looks really popular.

[x] Aviary

https://github.com/Workiva/gh-ost/pull/3
Not needed actually

I finished the assessment and marked it as complete in the RM Console.
https://w-rmconsole.appspot.com/rosie/Workiva/gh-ost/

I finished the assessment and marked it as complete in the RM Console.
https://w-rmconsole.appspot.com/rosie/Workiva/gh-ost/


[AnimeWasAMistake] graphic update and new tab

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

Hide radio button on dice scores and replace with highlighting.
Change spare tab to XP, to track XP expanses.
Change spare tab to notes.

Character Sheet Info Roll20 Internal Use only.


Setting language/locale for generated javadoc comments

I could not find a way to specify the language used to generate javadoc comments in the generated classes and I think this would be a great feature to have. E.g. via a parameter 'locale' accepting java.util.Locale.

The plugin delegates to wsdl2java. The tool itself does not provide any option in relation to the language or locale as far as I can see, so this plugin does not either.

couldn't it be done like here?
https://github.com/yupzip/wsdl2java/blob/0eef05c057fd799aeec59c9cf057793ad4c73743/src/main/groovy/com/yupzip/wsdl2java/Wsdl2JavaTask.groovy#L64

Oh, I see. That plugin programmatically invokes the wsdl2java tool directly. This plugin does not do that and instead delegates the invocation to Gradle via JavaExec:

https://github.com/ciscoo/cxf-codegen-gradle/blob/v1.0.0-rc.3/cxf-codegen-gradle/src/main/java/io/mateo/cxf/codegen/CxfCodegenPlugin.java#L98...L105

As mentioned in the documentation, Wsdl2JavaTask is a subclass of JavaExec, so whatever you can do to JavaExec tasks you can do to Wsdl2JavaTask
From Googling, there are two ways to set the locale.

Programmatically as that plugin you linked does.
JVM arguments.

You should be able to do (2) with something like following:
import io.mateo.cxf.codegen.wsdl2java.Wsdl2JavaTask

plugins {
    id("java")
    id("io.mateo.cxf-codegen") version "1.0.0-rc.3"
}

repositories {
    mavenCentral()
}

cxfCodegen {
    wsdl2java {
        register("calculator") {
            wsdl.set(file("calculator.wsdl"))
        }
    }
}

tasks.named("wsdl2javaCalculator", Wsdl2JavaTask::class) {
    allJvmArgs = listOf("-Duser.language=fr", "-Duser.country=CA")
}

References:

https://www.oracle.com/technical-resources/articles/javase/locale.html#using
https://docs.gradle.org/current/dsl/org.gradle.api.tasks.JavaExec.html

will try that right away, thank you for your support and work!


Tests for REST translations

I need to test to ensure that google.api.http annotations work properly. This is mostly about testing the behavior of vanguard to make sure I actually understand how it's working.

Yep, this works!


404 on empty page

Pages that return an empty string is 404 (index.html). Only happens if layout doesn't exist or is empty.

Fixed in furu.


update README to use assert.strictEqual

Description
What changed?

Updated README
assert.equal is deprecated since v9.9.0. Switched to assert.strictEqual

Looks like someone's already got these changes posted in #2798 so I'll defer to that one. Regardless, thank you for contributing!


LiteLLM.Info: If you need to debug this error, use `litellm.set_verbose=True'.

root@DESKTOP-1TC1K9D:/home/timuc/OpenDevin# make run
Running the app...
make[1]: Entering directory '/home/timuc/OpenDevin'
Starting backend...
make[1]: Entering directory '/home/timuc/OpenDevin'
Starting frontend...

<EMAIL_ADDRESS>start
vite

VITE v5.2.7  ready in 658 ms
➜  Local:   http://localhost:3001/
➜  Network: use --host to expose
INFO:     Started server process [12950]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:3000 (Press CTRL+C to quit)
INFO:     <IP_ADDRESS>:47280 - "GET /litellm-models HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:47296 - "GET /litellm-agents HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:47306 - "GET /litellm-models HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:47318 - "GET /litellm-agents HTTP/1.1" 200 OK
INFO:     ('<IP_ADDRESS>', 47328) - "WebSocket /ws" [accepted]
INFO:     connection open
Workspace directory ./workspace does not exist. Creating it...
==============
STEP 0
PLAN:
bana mali danışmanlık firması için web sitesi tasarla ve çalıştır. Detaylı ve kapsamlı bir çalışma olsun.
INFO:
HINT:
You're not currently working on any tasks. Your next action MUST be to mark a task as in_progress.
Give Feedback / Get Help: https://github.com/BerriAI/litellm/issues/new
LiteLLM.Info: If you need to debug this error, use `litellm.set_verbose=True'.
what is the reason of this  ?

LLM_MODEL="gemini/gemini-pro"
LLM_API_KEY="A...."
WORKSPACE_DIR="./workspace"

I am working through this one as well. It looked to me like litellm might be using the vertex api instead of the developer api for gemini. I think the API keys may be different (https://cloud.google.com/vertex-ai/generative-ai/docs/migrate/migrate-google-ai#google-ai).
Actively trying to figure out what is going on now.
I also am wondering what the right value in LLM_MODEL is and whether it should match 1:1 with the value in the UI settings or whether there is a different convention in play.

Here is a bit more that leads me to this conclusion.
OBSERVATION:
VertexAIException - 403 Vertex AI API has not been used in project <<PROJECT ID>> before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/aiplatform.googleapis.com/overview?project= <<PROJECT ID>>  then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry. [links {
  description: "Google developers console API activation"
  url: "https://console.developers.google.com/apis/api/aiplatform.googleapis.com/overview?project=<<PROJECT ID>> "
}
, reason: "SERVICE_DISABLED"
domain: "googleapis.com"
metadata {
  key: "service"
  value: "aiplatform.googleapis.com"
}
metadata {
  key: "consumer"
  value: "projects/<<PROJECT ID>>"
}
]

I was also prompted to use the google cloud client to set up credentials. This shouldn't be necessary with an API key using the developer APIs. I've coded against the before without having to do so.
OpenDevin/.env/lib/python3.12/site-packages/litellm/main.py", line 1677, in completion
    model_response = vertex_ai.completion(
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/Volumes/boxy-01/code-archive/viewing/OpenDevin/.env/lib/python3.12/site-packages/litellm/llms/vertex_ai.py", line 676, in completion
    raise VertexAIError(status_code=500, message=str(e))
litellm.llms.vertex_ai.VertexAIError: Your default credentials were not found. To set up Application Default Credentials, see https://cloud.google.com/docs/authentication/external/set-up-adc for more information.

So somewhere litellm thinks we should be using vertex APIs and I am not sure why. I was just using litellm for another project yesterday in which it was correctly authenticating with an API token against the developer apis.

I have now verified but not pinpointed the issue.
Config.toml correctly has:
LLM_MODEL="gemini/gemini-pro"

Which matches the correct value for developer the api (gemini/gemini-pro)in the (llmlite docs)[https://docs.litellm.ai/docs/providers/gemini]. Notice that llmlite also supports Vertex with the key:  gemini-pro
AI Studio Params

Vertex Params

Despite having the correct values set in the configuration file and UI cycling servers, even rebuilding, I still see the errors referring to Vertex.

@timucindusunur

Give Feedback / Get Help: https://github.com/BerriAI/litellm/issues/new
LiteLLM.Info: If you need to debug this error, use `litellm.set_verbose=True'.

what is the reason of this ?

This is only the start of an error, the next lines should say what error it is.

@jpshackelford Weird, and I think you're right, today/yesterday I've seen other issues in various places with some subset of LLMs via LiteLLM, but I can't find now the references.
Gemini via LiteLLM should work - and has worked - with google generativeai IIRC.

I guess the issue was related to some dependencies currently, everything works well with Gemini without the need for vertex here's my config.toml file:
LLM_MODEL="gemini/gemini-pro"
LLM_API_KEY="<YOUR-API-KEY>"
LLM_EMBEDDING_MODEL=""
WORKSPACE_DIR="./workspace"