Having trouble opening locally

I just doubled clicked the html file and it didnt work, can you do that?

thanks, were do i find the disable web security flag?

terminal seems to be block on my school pc

Also i seemed to have unblocked the playstore, is there something i can download from there?

If only someone would help me with my question...


User flow for setting/unsetting 'MFA required' tag

Maybe we can use the existing tag-setting/unsetting GUI for this, then we don't have to do anything for this.

We are creating one new app for Nextcloud to do two things:

[ ] Add another tab to file and folder details that inside it user can set/unset check for enabling or disabling Mfa verified zone. (User must be admin or owner of the file)
[ ] Add a new section inside the security section of the administration panel so that the Admin can select the specified tag to be used for creating the Mfa zone in the background.

Here is the repository for the new app, and This is a pull request that shows the development progress.

@mrvahedi68 what is the status of this issue?

Done with this PR:
https://github.com/pondersource/mfaverifiedzone/pull/1


cobalt: 0.17.0 -> 0.17.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cobalt-org/cobalt.rs/releases.
meta.description for cobalt is: "Static site generator written in Rust"
meta.homepage for cobalt is: "https://github.com/cobalt-org/cobalt.rs/"
meta.changelog for cobalt is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/d7zv8w8cim1jj7ywj83dkci9hqbrg73b-cobalt-0.17.4/bin/cobalt passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 0.17.4 with grep in /nix/store/d7zv8w8cim1jj7ywj83dkci9hqbrg73b-cobalt-0.17.4

found 0.17.4 in filename of file in /nix/store/d7zv8w8cim1jj7ywj83dkci9hqbrg73b-cobalt-0.17.4

directory tree listing: https://gist.github.com/f510e707abd84fb7ca34ab51d54b732f

du listing: https://gist.github.com/0d7a86bbaf8857c147a14df0e4058430

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cobalt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d7zv8w8cim1jj7ywj83dkci9hqbrg73b-cobalt-0.17.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cobalt https://github.com/r-ryantm/nixpkgs/archive/473c90014fbbe65dab653260d648084276219301.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d7zv8w8cim1jj7ywj83dkci9hqbrg73b-cobalt-0.17.4
ls -la /nix/store/d7zv8w8cim1jj7ywj83dkci9hqbrg73b-cobalt-0.17.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cobalt

Maintainer pings
cc @ethancedwards8 for testing.

LGTM.


Small fixes

Description

Changed a whole bunch of small things.
Motivation and Context

Small Issues thread #199
How Has This Been Tested?

Screenshots (if appropriate):
Some things

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] I updated the version.
[X] I updated the changelog with the new functionality.


ZipFile.TestArchive seems to always return false for AES encrypted zips

Steps to reproduce
call
var zipFile = new<EMAIL_ADDRESS>{
    Password = password
};

Assert.That(zipFile.TestArchive(false), Is.True, "Zip file should be valid");

On an AES encrypted zip file (happens with files generated with both SharpZipLib and 7-Zip).
Expected behavior
I assume that the test should pass for a valid AES archive?
Actual behavior
TestArchive returns false.
Looks like it fails @ https://github.com/icsharpcode/SharpZipLib/blob/master/src/ICSharpCode.SharpZipLib/Zip/ZipFile.cs#L1207 because the flags are different (localFlags just has the encrypted bit set, whereas entry.Flags has the StrongEncryption bit set I think).
If it gets past that, it will also fail on the compression method comparison, as entry.CompressionMethod is the compression format (Deflate), but compressionMethod is 99 (WinZipAES).
Version of SharpZipLib
1.1.0
Obtained from (only keep the relevant lines)

Compiled from source, commit: 25ee644

Actually, looking at the encryption bits of the spec, is it correct to set the strong encryption flag @
https://github.com/icsharpcode/SharpZipLib/blob/25ee6440f444aa326ee8f0b98e6223296f35fa6d/src/ICSharpCode.SharpZipLib/Zip/ZipEntry.cs#L1137
?
(Seems that is supposed to be for a different encryption approach that the Winzip one)

Yes, the only thing that the AE-1/2 mentions are that the encrypted flag should be set to 1 (bit zero). Strong encryption is what pkzip generally uses to refer to it's (stronger) encryption, so this seems to imply that it should not be set. The APPNOTE only specifies that

Strong encryption.  If this bit is set, you MUST set the version needed to extract value to at least 50 and you MUST also set bit 0.  If AES encryption is used, the version needed to extract value MUST be at least 51

The logic in CreateAndInitDecryptionStream in Zipfile is currently checking for StrongEncryption being set to decide which crypto approach should be used, which seems wrong if StrongEncryption != AE-X, and only the latter is supported?
The check @
https://github.com/icsharpcode/SharpZipLib/blob/25ee6440f444aa326ee8f0b98e6223296f35fa6d/src/ICSharpCode.SharpZipLib/Zip/ZipFile.cs#L3561
is also checking if the version is equal to 51, when the line you quote above says 'at least 51' and the linked Winzip spec doesn't specify any explicit version - not sure if that is correct?
Possibly the logic should be keyed off the AE-x flags in the entry rather than the other bits?

Indeed, it fails with Central header/local header compression method mismatch. I am taking a look at this.

It should just be a case of changing the check to compare entry.CompressionMethodForHeader instead of entry.CompressionHeader at src/ICSharpCode.SharpZipLib/Zip/ZipFile.cs#L1207

#353 does that

Yeah, not sure how I missed that.

Something I noticed while looking at something else (partly related to this issue, partly related to #460):
Is the check at:
https://github.com/icsharpcode/SharpZipLib/blob/b6ab9f5da988dbcc87b54def87e7340c19358844/src/ICSharpCode.SharpZipLib/Zip/ZipFile.cs#L1292
correct when considering AES encrypted directory entries (whose size might be larger than ZipCrypto encrypted directories)? (I'm not sure what the +2 in the calculation is for)

Should that comparison in my previous comment perhaps be using the EncryptionOverheadSize property added in #460 rather than CryptoHeaderSize?


Backport PEP 585 + PEP 604 to Python 3.8 and 3.9

Hey FastUI project maintainers, could you please share your opinion on https://github.com/python/typing_extensions/issues/315 ?
I think introducing it in typing_extensions would make working with built-in generics slightly more convenient and easier to document for the new Python programmers that would be interested in trying out FastUI. Not even mentioning the simplification in defining pydantic models with the newest-fashion type annotations.
I need your opinion on the issue so that there is a good rationale behind officially backporting or NOT backporting PEP 585 and PEP 604 in Python <3.10. I, alone, probably won't convince anyone about it...
Thanks!

Pinging @samuelcolvin as an authority here.

Closing due to https://github.com/pydantic/pydantic/pull/8209.


Go BR :)

Before submitting a pull request, please make sure the following is done:

Fork the repository and create your branch from master.

Run the build.py and test.py scripts.

If you are fixing something, add tests that fail in the current version and pass in yours.

If you're developing a new feature open an issue first to discuss it. Some features may be useful to you but harmful to others be it because of performance, new dependencies or different perspectives.

One more time: Don't forget to add tests.

Ensure the entire test suite is passing and overral performance is not degraded.

Since Víbora means the same thing in any Portuguese (I hope so) I think we fine letting it this way. (btw: my intention was Brazillian Portuguese at the beginning and you're correct haha)


fix issue with prometheus agent and operator

Description

Since upgrading to kube-prometheus-stack 45.30.0 there is an issue with the chart which causes empty labels to always be printed in prometheus.rules, for example here
this will be rendered as follows:

adding new values fixes the issue and renders the rules correcly.
I couldn't find a valid reason for this to happen so had to use this workaround.
In addition removed non required values from prometheus-agent which caused it crash
 Fixes #
How Has This Been Tested?
deployed locally

Checklist:

[x] I have updated the relevant Helm chart(s) version(s)
[x] I have updated the relevant component changelog(s)
[x] This change does not affect any particular component (e.g. it's CI or docs change)

@oded-dd merge please :)


adopt Roslyn's way of associating tokens with trees

To quote https://github.com/dotnet/roslyn/wiki/Roslyn Overview#syntax-trivia:

When source text is parsed, sequences of trivia are associated with tokens. In general, a token owns any trivia after it on the same line up to the next token. Any trivia after that line is associated with the following token. The first token in the source file gets all the initial trivia, and the last sequence of trivia in the file is tacked onto the end-of-file token, which otherwise has zero width.

I was actually wondering why it's done this way until we stumbled upon a problem with reinferring tokens after tree rewritings.
Say, we have /* comment */ class C. If we parse this code as Source, then we'll get something like Source(Seq(Defn.Class(...))) with a token collection that includes the comments. So far so good.
However, if we do something like source.copy(stats = newStats), where newStats is just the very same class, but with some members added, then the comment is going to disappear, because inferTokens for sources just concatenates the tokens for their stats. Since the comment token isn't attached to Defn.Class, it's going to vanish.
In reality, inferTokens has a special case for sources, which takes the current source as well as the original source (that was a prototype for the current one), and then tries to guess which tokens to retain. However, this is a very special case, and it's still not precise enough.
In Roslyn's model, however, the comment right before the class (along with all the whitespace and blah) is going to be associated with Defn.Class, which means that it'll be retained without any special processing. This exposes the merit that their heuristics has, and I think could motivate us to adopt similar rules.

Superseded by #379. See that issue for a detailed discussion of related work and alternative approaches.


New features : Normalisation functions and enhanced criteria.

I think this should be a light review. There are no modifications to the existing functionalities. I just added some functions to the main API, to perform the log normalisation of raw counts. I also added the extra columns needed to sample from the inferred distributions.
@pauleve I am asking you to review this PR because I think this could be a new release v0.1.3 ? So that you can use your workflow to publish to PyPI and colomoto.
Let me know what do you think.

:+1:
There is no hurry for the release, we can do it later.


Feature Request: Include and import

Hello, nice work with Hush.
I would like to suggest a new feature, I think it would interesting to add to Hush the possibility to include and to import external Hush files to a given script.
To include files one folder above, perhaps, it could be done like this include "../folder2/my_secondscript.hsh", and to include one file at the same directory like:  include "./my_secondscript.hsh". The include functionality would only copy and paste all the contents of a given file.
In the case of import, it would verify the file and include functions and other needed functionality like this, ie :   import {my_function1 as fn1 , my_function1 as fn2 } from "./folder2/my_secondscript.hsh", similarly to Typescript.
Another way around, could be done by creating to the std functions like std.include(filename), or std.import(functionName).
What do you think about this idea ? Is something like this possible, or even, can you consider  an interesting proposition.
Thank you.

You can do that using the std.import function from the standard library.
Check out the iterator example at https://github.com/hush-shell/hush/blob/master/examples/hush/iterator.hsh.

You can do that using the std.import function from the standard library. Check out the iterator example at https://github.com/hush-shell/hush/blob/master/examples/hush/iterator.hsh.

Hello. Thanks for answering. I've noticed that(std.import) before your message, that's the why I overlined part of the text above.
I made a slight mistake, what I mean is the addition of the keywords import, include, as and from, as part of the Rush programming language rather than being part of the standard library (std).
Thanks again.

Hello! I designed std.import as a built-in function on purpose, for the sake of simplicity. Implementing those custom keywords would require special syntax, and thus changes to the lexer, parser and interpreter.


Daily workflow "npm publish"

Is there a reason why the workflow https://github.com/devicons/react-devicons/blob/main/.github/workflows/publish.yaml is running on a daily base publishing the package over and over again?

Right now it runs every day and checks if there is a new version. I had to to it like this because there was no way to trigger a publish when another repo creates a release. But I will rework the whole file to only run when the main repo creates a release in a few days.


Update UG description

Codecov Report

Merging #38 (d45c6d8) into master (f8eada5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #38   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 f8eada5...d45c6d8. Read the comment docs.


[backport-1.1] [FLINK-5934] Set the Scheduler in the ExecutionGraph via its constructor

This is a backport of #3437 onto release-1.1.
Before the scheduler was set when calling ExecutionGraph.scheduleForExecution(). This
has the disadvantage that the ExecutionGraph has not scheduler set if something else
went wrong before the scheduleForExecution call. Consequently, the job will be stuck
in a restart loop because the recovery will fail if there is no Scheduler set. In
order to solve the problem, the Scheduler is not passed to the ExecutionGraph when
it is created.

+1

Thanks for the review @StephanEwen. Merging this PR.


how to make API call

A screenshot of users studio dashboard.

Hello
All you need to do is talk to your Bot in a hosted channel. Console conversations with your bot do not count against your API usage. but running any script from slack, et al will.
PS: I deleted your image because it was showing a partial API token, be careful posting that!.

I have created this bot for facebook messenger.

i can,t talk with my bot in fb Messenger?
On Tue, Aug 15, 2017 at 7:10 PM, Peter Swimm<EMAIL_ADDRESS>wrote:

If you are talking to your bot and it is not triggering Studio scripts,
the first thing to do is check your provisioning settings:
https://github.com/howdyai/botkit/blob/master/docs/provisioning/facebook_
messenger.md
And then check your bot has all the correct tokens setup as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/956#issuecomment-322468461, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdWRR7aSIJAzKrH6-p-oamDTqj6VwhfPks5sYZ-6gaJpZM4O2fgx
.

It sounds like your bot is not properly setup, did you recheck your settings in the link I provided above?

Yes sir i have checked everything. M correct with all token settings.
On Tue, Aug 15, 2017 at 8:07 PM, Peter Swimm<EMAIL_ADDRESS>wrote:

It sounds like your bot is not properly setup, did you recheck your
settings in the link I provided above?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/956#issuecomment-322486762, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdWRR5tMuF8iGq0jjLzcIDOJvkyl615-ks5sYa0ggaJpZM4O2fgx
.

When setting up the webhooks, did your urls pass validation? It is difficult to provide troubleshooting via github, you should consider asking for help on our public slack:
http://community.botkit.ai/


Local variable names in inner class methods aren't fixed when they conflict with outer names

This is due to https://github.com/MinecraftForge/ForgeFlower/blob/master/FernFlower-Patches/0037-Do-not-rebuild-variable-names-in-lambdas.patch
For background on what that code is doing (re: the patch message):
That allows the decompiler to fix variable names in a nested class or lambda expression which clashes with the name of an outer variable.
What's happening is it's checking the names for the current method against the variable names defined in the outer scope. That's why setNewOuterNames is passed to VarNamesCollector, then checked for in VarNamesCollector.getFreeName() - the outer names are compared against the names for the nested method.
What FernFlower's code originally did was append x to local variable names when conflicts came up - but now it doesn't do that because of that patch. Considering that's the only thing that method is actually doing I don't know what the patch is actually trying to fix. The commit which added the patch said it fixes #88, but there is no issue 88 yet.
This comes up relatively infrequently, and I guess never in MCP due to how LVT is handled, but it causes an issue with my usage. This quick and dirty fix is because of this issue - previous versions of FernFlower would rename the inner i variable to ix. https://github.com/PaperMC/Paper/blob/mappings/mojang/Spigot-Server-Patches/0266-Optimize-BlockPosition-helper-methods.patch#L113-L134

See the comment on the commit, he meant to reference #80

Ah, so this is easy to fix just by excluding this and keeping the method call. I'll PR that tomorrow.

Okay patch 9 totally changes how variables are named and so it actually makes patch 37 a little odd considering it's not doing anything. But I cannot follow the new system, and can't figure out how to backport this feature onto it. I'll just leave this issue here and hope someone smarter than me can figure it out.


Request to a new feature (Sets)

I heard about sets a feature to organize the difference windows from different applications in tabs, what would be nice.
This is an amazing project love u all who make this possible.

Duplicate of #10

Check out https://thewincentral.com/microsoft-planning-to-bring-windows-10-sets-feature-back-from-grave/, maybe that'll help?


Docker empty response error

Hi
I pulled & started an instance of instagraph in docker but when I try to access the web on 8080 port I face with a ERR_EMPTY_RESPONSE

Hi
You have to wait until program start listening on 8080. It might take long.
Please send instagraph's log.

I double checked that and same result.
But made a little work around & found if in main.go you change "localhost:8080" to "<IP_ADDRESS>:8080" that makes sense
Anyway thank you

You're right.
Can you make a PR for it ?
It's better to get listening address from CLI.

Yes, sure I can and I will.


Can't compile with latest xcode commandline tools

Xmake Version
xmake v2.7.8+20230406
Operating System Version and Architecture
Macos Ventura 13.3
Describe Bug
In an empty directory, run xmake new project.  This will generate a template main.cpp file with corresponding xmake.lua file.
Run Xmake Build.  The build fails due to a problem with xcode command line tools that I have not encountered before.  Other projects (a lot more code, but still just one file) build with xmake perfectly.
Here is the output:
xmake f -p macosx -a undefined -m debug

 *  Executing task: xmake -w

[ 25%]: cache compiling.debug src/main.cpp
error: /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/wchar.h:123:15: fatal error: 'wchar.h' file not found
#include_next <wchar.h>
              ^~~~~~~~~
1 error generated.
  > in src/main.cpp

 *  The terminal process "/bin/zsh '-c', 'xmake -w'" terminated with exit code: 255.

Here is the xmake.lua:
-- add_rules("mode.debug", "mode.release")

target("one")
    set_kind("binary")
    add_files("src/*.cpp")

Xcode version:
Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)
Target: arm64-apple-darwin22.4.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
This is probably not Xmake's problem.  There is something strange with commandlinetools going on.  In another project, a single cpp file of 1300 lines builds and runs perfectly.  So, looking for a hint...
Expected Behavior
clang++ should do its job without messing up over a header file that's not even being requested in the project.  Could be that visual studio code natively uses utf-8, so string constants could look like there made of wchar's.  But, that doesn't make sense in c++ where we need to explicitly encode as utf-8 as in:  cout << u8"\033[2J";  So, it can't be the compiler mis-interpreting string constants.  Something with commandlinetools.
Project Configuration
No response
Additional Information and Error Logs
No response

xmake f -p macosx -a undefined -m debug

try
xmake f -cvD
xmake -rvD

Good diagnostic tools.
The library access is a mess, see below.  I am going to cleanup my paths from some bad “Google advice” and try again.

one xmake f -cvD

checking for platform ... macosx

checking for architecture ... arm64

checking for Xcode directory ... /Applications/Xcode.app

checking for Codesign Identity of Xcode ... no

checking for SDK version of Xcode for macosx (arm64) ... 13.3

checking for Minimal target version of Xcode for macosx (arm64) ... 13.3

checkinfo: cannot runv(zig version), No such file or directory

checking for zig ... no

checkinfo: cannot runv(zig version), No such file or directory

checking for zig ... no

configure

{

    arch = arm64

    clean = true

    ndk_stdcxx = true

    mode = release

    xcode = /Applications/Xcode.app

    plat = macosx

    ccache = true

    kind = static

    buildir = build

    host = macosx

}

➜  one xmake -rvD

checking for /Library/Developer/CommandLineTools/usr/bin/clang ... ok

checking for the c++ compiler (cxx) ... clang

checking for /Library/Developer/CommandLineTools/usr/bin/clang ... ok

checking for flags (-fPIC) ... ok

> clang "-fPIC" "-Qunused-arguments" "-target" "arm64-apple-macos13.3" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk"

[ 25%]: cache compiling.release src/main.cpp

/Library/Developer/CommandLineTools/usr/bin/clang -c -Qunused-arguments -target arm64-apple-macos13.3 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk -o build/.objs/one/macosx/arm64/release/src/main.cpp.o src/main.cpp

checking for flags (-MMD -MF) ... ok

> clang "-MMD" "-MF" "/dev/null" "-Qunused-arguments" "-target" "arm64-apple-macos13.3" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk"

checking for flags (-fdiagnostics-color=always) ... ok

> clang "-fdiagnostics-color=always" "-Qunused-arguments" "-target" "arm64-apple-macos13.3" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk"

error: @programdir/modules/private/async/runjobs.lua:256: @programdir/modules/private/action/build/object.lua:91: @programdir/modules/core/tools/gcc.lua:721: In file included from src/main.cpp:1:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/iostream:41:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/ios:221:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__locale:18:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/memory:841:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__algorithm/copy.h:12:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__algorithm/unwrap_iter.h:13:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__iterator/iterator_traits.h:14:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__iterator/incrementable_traits.h:15:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/concepts:133:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__concepts/arithmetic.h:15:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/type_traits:421:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__functional/invoke.h:15:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__type_traits/apply_cv.h:16:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__type_traits/remove_reference.h:13:

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/cstddef:50:9: error: no member named 'nullptr_t' in the global namespace

using ::nullptr_t;

      ~~^

In file included from src/main.cpp:1:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/iostream:41:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/ios:221:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__locale:18:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/memory:841:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__algorithm/copy.h:12:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__algorithm/unwrap_iter.h:13:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__iterator/iterator_traits.h:14:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__iterator/incrementable_traits.h:15:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/concepts:133:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__concepts/arithmetic.h:15:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/type_traits:452:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__type_traits/is_compound.h:14:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__type_traits/is_fundamental.h:14:

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__type_traits/is_null_pointer.h:24:49: error: use of undeclared identifier 'nullptr_t'

template <>          struct __is_nullptr_t_impl<nullptr_t> : public true_type {};

                                                ^

In file included from src/main.cpp:1:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/iostream:41:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/ios:221:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__locale:18:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/memory:841:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__algorithm/copy.h:13:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__algorithm/unwrap_range.h:16:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__iterator/next.h:15:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__iterator/advance.h:19:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/__utility/unreachable.h:13:

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/cstdlib:86:

In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/stdlib.h:66:

In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/wait.h:110:

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:203:2: error: unknown type name 'uint8_t'

        uint8_t  ri_uuid[16];

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:204:2: error: unknown type name 'uint64_t'

        uint64_t ri_user_time;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:205:2: error: unknown type name 'uint64_t'

        uint64_t ri_system_time;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:206:2: error: unknown type name 'uint64_t'

        uint64_t ri_pkg_idle_wkups;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:207:2: error: unknown type name 'uint64_t'

        uint64_t ri_interrupt_wkups;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:208:2: error: unknown type name 'uint64_t'

        uint64_t ri_pageins;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:209:2: error: unknown type name 'uint64_t'

        uint64_t ri_wired_size;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:210:2: error: unknown type name 'uint64_t'

        uint64_t ri_resident_size;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:211:2: error: unknown type name 'uint64_t'

        uint64_t ri_phys_footprint;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:212:2: error: unknown type name 'uint64_t'

        uint64_t ri_proc_start_abstime;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:213:2: error: unknown type name 'uint64_t'

        uint64_t ri_proc_exit_abstime;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:217:2: error: unknown type name 'uint8_t'

        uint8_t  ri_uuid[16];

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:218:2: error: unknown type name 'uint64_t'

        uint64_t ri_user_time;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:219:2: error: unknown type name 'uint64_t'

        uint64_t ri_system_time;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:220:2: error: unknown type name 'uint64_t'

        uint64_t ri_pkg_idle_wkups;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:221:2: error: unknown type name 'uint64_t'

        uint64_t ri_interrupt_wkups;

        ^

/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/include/sys/resource.h:222:2: error: unknown type name 'uint64_t'

        uint64_t ri_pageins;

        ^

fatal error: too many errors emitted, stopping now [-ferror-limit=]

20 errors generated.

stack traceback:

    [C]: in function 'error'

    ***@***.***/core/base/os.lua:913]:

    ***@***.***/modules/core/tools/gcc.lua:721]: in function 'catch'

    ***@***.***/core/sandbox/modules/try.lua:123]: in function 'try'

    ***@***.***/modules/core/tools/gcc.lua:662]:

    [C]: in function 'xpcall'

    ***@***.***/core/base/utils.lua:280]:

    ***@***.***/core/tool/compiler.lua:274]: in function 'compile'

    ***@***.***/modules/private/action/build/object.lua:91]: in function 'script'

    ***@***.***/modules/private/action/build/object.lua:104]: in function 'build_object'

    ***@***.***/modules/private/action/build/object.lua:129]: in function 'jobfunc'

    ***@***.***/modules/private/async/runjobs.lua:232]:

    [C]: in function 'xpcall'

    ***@***.***/core/base/utils.lua:280]: in function 'trycall'

    ***@***.***/core/sandbox/modules/try.lua:117]: in function 'try'

    ***@***.***/modules/private/async/runjobs.lua:218]: in function 'cotask'

    ***@***.***/core/base/scheduler.lua:404]:

stack traceback:

      [C]: in function 'error'

      @programdir/core/base/os.lua:913: in function 'os.raiselevel'

      (...tail calls...)

      @programdir/modules/private/async/runjobs.lua:256: in field 'catch'

      @programdir/core/sandbox/modules/try.lua:123: in global 'try'

      @programdir/modules/private/async/runjobs.lua:218: in upvalue 'cotask'

      @programdir/core/base/scheduler.lua:404: in function ***@***.***/core/base/scheduler.lua:397>

➜  one

From: ruki @.>
Reply-To: xmake-io/xmake @.>
Date: Friday, April 7, 2023 at 2:33 AM
To: xmake-io/xmake @.>
Cc: Lewis Levin @.>, Author @.***>
Subject: Re: [xmake-io/xmake] Can't compile with latest xcode commandline tools (Issue #3605)
xmake f -p macosx -a undefined -m debug
try
xmake f -cvD
xmake -rvD
—
Reply to this email directly, view it on GitHubhttps://github.com/xmake-io/xmake/issues/3605#issuecomment-1500118679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAIYWLK7K6XEREG3GZDHH43W77NNHANCNFSM6AAAAAAWWIVHIM.
You are receiving this because you authored the thread.Message ID: @.***>

You can close this.
Build and Run are successful.
I like this tool a lot. I am about to break apart an overly large .cpp file into .h or .cpp suitable as includes--now that I can use Xmake: so much more sensible than Cmake or Make.  Not a standard, but my team of one gets to choose whatever tools it likes best.
From: ruki @.>
Reply-To: xmake-io/xmake @.>
Date: Friday, April 7, 2023 at 2:33 AM
To: xmake-io/xmake @.>
Cc: Lewis Levin @.>, Author @.***>
Subject: Re: [xmake-io/xmake] Can't compile with latest xcode commandline tools (Issue #3605)
xmake f -p macosx -a undefined -m debug
try
xmake f -cvD
xmake -rvD
—
Reply to this email directly, view it on GitHubhttps://github.com/xmake-io/xmake/issues/3605#issuecomment-1500118679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAIYWLK7K6XEREG3GZDHH43W77NNHANCNFSM6AAAAAAWWIVHIM.
You are receiving this because you authored the thread.Message ID: @.***>

This is more like it:

xmake -rvD

[ 25%]: cache compiling.release src/main.cpp

/Library/Developer/CommandLineTools/usr/bin/clang -c -Qunused-arguments -target arm64-apple-macos13.3 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk -o build/.objs/one/macosx/arm64/release/src/main.cpp.o src/main.cpp

checking for /Library/Developer/CommandLineTools/usr/bin/clang++ ... ok

checking for the linker (ld) ... clang++

checking for /Library/Developer/CommandLineTools/usr/bin/clang++ ... ok

checking for flags (-fPIC) ... ok

> clang++ "-fPIC" "-target" "arm64-apple-macos13.3" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk" "-stdlib=libc++" "-target" "arm64-apple-macos13.3" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk" "-stdlib=libc++"

[ 50%]: linking.release one

/Library/Developer/CommandLineTools/usr/bin/clang++ -o build/macosx/arm64/release/one build/.objs/one/macosx/arm64/release/src/main.cpp.o -target arm64-apple-macos13.3 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk -stdlib=libc++ -lz

From: ruki @.>
Reply-To: xmake-io/xmake @.>
Date: Friday, April 7, 2023 at 2:33 AM
To: xmake-io/xmake @.>
Cc: Lewis Levin @.>, Author @.***>
Subject: Re: [xmake-io/xmake] Can't compile with latest xcode commandline tools (Issue #3605)
xmake f -p macosx -a undefined -m debug
try
xmake f -cvD
xmake -rvD
—
Reply to this email directly, view it on GitHubhttps://github.com/xmake-io/xmake/issues/3605#issuecomment-1500118679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAIYWLK7K6XEREG3GZDHH43W77NNHANCNFSM6AAAAAAWWIVHIM.
You are receiving this because you authored the thread.Message ID: @.***>

So does it work now?

Perfectly.
Mark this closed.
From: ruki @.>
Reply-To: xmake-io/xmake @.>
Date: Saturday, April 8, 2023 at 4:43 AM
To: xmake-io/xmake @.>
Cc: Lewis Levin @.>, Author @.***>
Subject: Re: [xmake-io/xmake] Can't compile with latest xcode commandline tools (Issue #3605)
So does it work now?
—
Reply to this email directly, view it on GitHubhttps://github.com/xmake-io/xmake/issues/3605#issuecomment-1500873636, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAIYWLOAJIYCNZMXOLUFALLXAFFOJANCNFSM6AAAAAAWWIVHIM.
You are receiving this because you authored the thread.Message ID: @.***>

相同问题在尝试以下命令后依然存在问题，辛苦帮忙看下：
xmake f -cvD，结果为：
checking for platform ... macosx
checking for architecture ... arm64
checking for Xcode directory ... %s
checking for Codesign Identity of Xcode ... no
checkinfo: cannot runv(zig version), No such file or directory
checking for zig ... no
checkinfo: cannot runv(zig version), No such file or directory
checking for zig ... no
configure
{
    arch = arm64
    buildir = build
    plat = macosx
    ccache = true
    ndk_stdcxx = true
    mode = release
    clean = true
    kind = static
    host = macosx
}

xmake -rvD，结果为：
checking for /Library/Developer/CommandLineTools/usr/bin/clang ... ok
checking for the c++ compiler (cxx) ... clang
checking for /Library/Developer/CommandLineTools/usr/bin/clang ... ok
checking for flags (-fPIC) ... ok
> clang "-fPIC" "-Qunused-arguments"
checking for flags (-fvisibility-inlines-hidden) ... ok
> clang "-fvisibility-inlines-hidden" "-Qunused-arguments"
checking for flags (-O3) ... ok
> clang "-O3" "-Qunused-arguments"
checking for flags (-DNDEBUG) ... ok
> clang "-DNDEBUG" "-Qunused-arguments"
[ 25%]: cache compiling.release src/main.cpp
/Library/Developer/CommandLineTools/usr/bin/clang -c -Qunused-arguments -fvisibility=hidden -fvisibility-inlines-hidden -O3 -DNDEBUG -o build/.objs/test/macosx/arm64/release/src/main.cpp.o src/main.cpp
checking for flags (-MMD -MF) ... ok
> clang "-MMD" "-MF" "/dev/null" "-Qunused-arguments"
checking for flags (-fdiagnostics-color=always) ... ok
> clang "-fdiagnostics-color=always" "-Qunused-arguments"
error: @programdir/modules/private/async/runjobs.lua:256: @programdir/modules/private/action/build/object.lua:91: @programdir/modules/core/tools/gcc.lua:721: In file included from src/main.cpp:1:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/iostream:37:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/ios:214:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/__locale:15:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/string:519:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/__debug:14:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/iosfwd:98:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/__mbstate_t.h:29:
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/wchar.h:123:15: fatal error: 'wchar.h' file not found

目前没有查询到Codesign Identity of Xcode是什么含义..

得用 dev 版本。。https://github.com/xmake-io/xmake/issues/3686


Per action middleware options after/before

If I get this feature correctly based on the title...
Validation being already baked in, the first real-world use-case I can think of for this feature is authentication and/or ACL on sets of routes.
Since several dolman.router instances can coexist within the same app you could think of creating different routers acting as a logical group of routes based on the access level (e.g. public, private, or other special access level: app.use('/admin', authAdminMiddleware, adminRouter)) right?
There might be other obvious use-cases for after/before filters in routes but my brain is so slow I can't find any right no.
So as of now, is it really a sine qua none feature? Or maybe you have an example right out of your head.

Yes, for the time being I have dropped the feature as the example you show (as the one displayed in the docs) works quite right for now. I propose that we reopen the subject when we have a real-life issue to solve.

But having the possibility to register middleware for some routes (before validation, I guess) could become handy.

But it would probably be the product of a bad project organization, so I am still pondering it.

All other real-life use cases that come up in my head right now for before/after filters have to do with e.g. models or stuff that are not dealt with at the API layer...


Rename the extern class NativeString to CString

NativeString used to be mainly implemented by the engines, but in the last few years it became gradually a normal extern class. As such, its instances are now C strings (char *). Most of its methods are extern and implemented in the library instead of the engines. It is also widely used by extern methods implemented in C as char *, the type appears 300+ times in the general lib and 67 times in lib/core/text.
This PR renames NativeString to CString. This change makes it clear to beginner programmers that its instances are pointers to C strings and how they are passed to C code. Plus, it fits better next to CppString, JavaString and NSString.
The only remaining engine not using it as a C string is the Java compiler, which implements it as a Java string. This still works and as long as it behaves like a C string there is no problem.
This PR also updates the related doc and attempts to update all indirect references to the new CString.
As discussed with @privat and @R4PaSs.

Is this something more that a big sed?

Aside from 2abd9b25, yeah, it's a few big sed.


docs: delete unnecessary import in remix template

📝 Description
There is a description to import dotenv in the entry.server.tsx template, but this is not necessary.

This does not affect the rendering of chakra-ui.
For chakra-ui beginners, it may be a useless guess that some implicit environment variable definitions are necessary.

Yes, I had an evil guess.

If the runtime is cloudflare, it cannot be built because it is not Node and process cannot be referenced.

💣 Is this a breaking change (Yes/No): NO

Makes total sense, @aiji42! Thank you for opening this PR.
@allcontributors please add @aiji42 for docs.


Reduce Docker image size by switching to miniconda base image

Closes #29.
Bring the image size down from ~3.12GB to ~1.83GB.
Explicitly install the gcc supplied by conda and ensure it is available to the shell when building Python package dependencies. (If this looks too messy, I'm happy to switch to the python:3 image instead, which gives us a ~1.96GB image without the need to tweak the environment to get gcc.)
Based on #32 to avoid conflicts. Only the last two commits are new. This should be merged only after that PR.

Can we just have a flat /platform instead of .platform and .platform/docker?

Good idea. I see #32 has implemented this suggestion, when that PR is merged I'll rebase this one.

@adityasharad just merged, update away!

@cliffckerr done!
Re your comment about size, let's start with this change, and if we can identify other places to reduce the image size I'm happy to try those later.

@adityasharad This looks great. Is it OK if I change my mind? :see_no_evil: I think docker would be useful for a decent fraction of users, but platform probably not. Could we move the docker folder to be top-level, instead of inside .platform?

@adityasharad Also the commands listed don't seem to work, if I'm running them correctly
finzi:~/idm/covasim/.platform/docker> make pull-run
docker-compose pull covasim
Pulling covasim (covasim:latest)...
ERROR: pull access denied for covasim, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
make: *** [Makefile:13: pull] Error 1
finzi:~/idm/covasim/.platform/docker> docker-compose pull covasim
Pulling covasim (covasim:latest)...
ERROR: pull access denied for covasim, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

So this sequence worked & has it up and running on Ubuntu:
docker-compose build
docker-compose up -d

Maybe we can just list that one way of doing things? cc @devclinton

@adityasharad Also the commands listed don't seem to work, if I'm running them correctly
finzi:~/idm/covasim/.platform/docker> make pull-run
docker-compose pull covasim
Pulling covasim (covasim:latest)...
ERROR: pull access denied for covasim, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
make: *** [Makefile:13: pull] Error 1
finzi:~/idm/covasim/.platform/docker> docker-compose pull covasim
Pulling covasim (covasim:latest)...
ERROR: pull access denied for covasim, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

I think I did the wrong thing in changing the image name - if you try to pull the image then it needs to get it from @jules2689's package registry.

Reverted the change to the image name: this should fix make pull, docker-compose pull covasim, and make pull-run. Sorry about that.
make build / docker-compose build and make run / docker-compose up -d should continue to work.

Thanks @adityasharad , and last thing, can we have docker be a top-level folder instead of inside platform?

Moved .platform/docker to docker in latest commit , also updated various readme links.

Thanks @adityasharad !


Oss compliance updates

@SebastianWolf-SAP
I believe these changes should fix the issues...

@SebastianWolf-SAP I have updated the repo per your comments

Hi @SebastianWolf-SAP - I've update the repo to use the dep5 file for the .md files, and addressed your other comments.  Please review.

Any updates from your end, do you need additional support?


SPIKE: Review Service Control Policy (SCP) to ensure permission required by CloudCSPM is not denied

Describe the issue
There is a warning that we see every time we log in to use Check Point CSPM (Cloud Security Posture Management).
We think it impacts functionality but we don't understand if this is to blame for things not working in the Canadian CSPM instance we're using.  Some things aren't working right now, this could be one of many potential sources of error.  It could just be a visual bug.
We see bugs in the container workload environment.  Missing ECR list repository permission for example.
We don't know if the bug is on our side or theirs.
In our ECF environment, we have created the Role CloudGuardConnect with attached "SecurityAudit" and Custom Policy "CloudGuardRead", CloudGuard CSPM still encountered missing permission.  We want to review  the SCP to ensure, the required permission is not blocked.  We are not sure if this will solve the problem, but if we check it, then we can go back to Check Point and look at the next potential source of the problem.
Additional context

We have no logs from CheckPoint so very hard to debug.
Anyone on the team with Admin role can look at the management account for browsing the SCP
The SCPs don't exist in the workload accounts
The SCPs are additive so several apply.  We can look at the config.json file (tech team member) for the ECF to see which apply where.  https://github.com/aws-samples/aws-secure-environment-accelerator/tree/main/reference-artifacts/SCPs
Meet with Warren to get started

Review SCP requires Org Master Account

Hovering column status in Environments Splash Screen shows 'This Account has missing permissions'
Click the the any environment, the error message 'Missing Permission for CloudGuardConnect'
Click on show more, the list of related resource, permission group, action that CloudGuardConnect needs permission is displayed.
CheckPoint would like to have Screen Share once we have reviewed the SCP is the root cause.

Related CheckPoint TAC Support Ticke is 6-0003369490.
Definition of done

Cap to a 2 effort (reason: we can't solve this, we need info)
Get logs from CheckPoint because we need more info to find the SCP on our side.
Meet with someone on the tech team who can show you where the source code that defines the SCP lives and which settings apply
Identify problematic SCP and bring back to team to discuss (recall this likely may be a non-issue on our side, likely a bug on their side.  Possible one of the CloudGuardConnect permissions we're giving is blocked by the SCP)
Screen Share with CheckPoint TAC Support if needed
Make well-formed tickets if the fix is one our side.

Bonus if easy to fix (but not required):

CloudGuard CSPM does not hit 'Unauthorized Operation' Error when clicked the listed Environment.

Need to have OU Management Account Access to be able to browse SCP.   In spite of that, based on error shown in CloudGuard CSPM, the unauthorized operation error might not be related to SCP disallow.

Found ecsCluster, EcsTaskDefinition on rescource: * with an explicit deny in SCP (not region related).  Warren U. please take a look in CSPM.   Thanks

Verified that out of regions are being blocked by SEA while CSPM is trying to scan all regions.  Therefore this makes sense. Messages tell us can't see ECS clusters but we see the right clusters.  We are just getting an error message about the other regions.  Closing the ticket.


Fixed changed image size (#1437)

Images without a specified resolution (@2x, @3x etc) shouldn't be resized when loaded from the cache. Instead, the original size and (1x) resolution should be maintained.

Looks like this reopens #576 and broke our code base sadly. 😞

@ikesyo i think this was reverted here

I know because the merge commit is coming from just this PR. Could you reconsider this? #576 should be reopened for now to track the issue.

@ikesyo do you name your scaled images with @2x or @3x? If I read the code correctly, then the scale should be restored correctly. Since SDWebImage doesn't store the scale specifically in the cache, it can only deduce it from the file name.
For images without a scale specifier in the file name, a scale of 1 is the best choice imo.


Flutter 3.0 compatibility issue

Looks like there's a compatibility issue with Flutter 3.0.
I get the following error while trying to build a previously working (and built using Flutter 2.x) app:
flutter_native_view-0.0.1+1/lib/src/widgets.dart:87:20: Warning: Operand of null-aware operation '!' has type 'WidgetsBinding' which excludes null.
This seems to be a known Flutter 3.0 upgrade issue (which would require some code migration changes) explained in the Flutter 3.0 release notes here:
https://docs.flutter.dev/development/tools/sdk/release-notes/release-notes-3.0.0

Oh. The error message was actually (confusingly enough) prefixed with ERROR:, but I now see that it wasn't the actual cause of the issue I experience (it's related to something else). Thanks for taking a look!

+1 Just remove that "!"

Addressed. Along with few other issues & minor API change. Released: v0.0.2.
Also, project is now under MIT licensing.


Barneshut physics theta option throws error

The Barneshut solver options throw an error when theta option is put there, even though it accepts it (though only on initialization, thetaInversed in nodesSolver doesn't get updated on change).
Theta is an important option for improving performance, especially since Barneshut algorithm tends to perform worse than a naive force simulation for small (few thousand nodes) with little difference to post stabilization result, as shown here: https://jheer.github.io/barnes-hut/.
In practice, for visualization purpose, values higher than 0.5 do cause visual jitter, so what I do is set theta high during hidden stabilization (1.2) and lower it back to 0.5 after. In the case of our network, this resulted in ~6 times lower stabilization times for networks with >1000 nodes, which is critical as our we don't want our users to be waiting forever to visualize their network. If I could set these with the options instead of forcefully changing thetaInversed in the nodesSolver, it would probably be better. An adaptive theta could perhaps be interesting to look at.

Hi @Owlman145,
I tried changing the theta. It thrown no errors and reacted just fine. Could you provide an MWE, please?
Thanks.

For testing this issue, I'm on latest commit of master branch.
Chrome: Version 79.0.3945.130 (Official Build) (64-bit)
Added the following below line 46 of examples/network/physics/physicsConfiguration.html:
          barnesHut: {             theta: 1           },
Causes the following error:
Validator.js:218 Unknown option detected: "theta" in
options = {
physics: {
barnesHut: {
theta
}
}
}
Perhaps it was misplaced? Matching option found at:
options = {
edges: {
font
}
}
Network.js:163 Errors have been found in the supplied options object.

I believe theta needs to be added here to prevent this: https://github.com/visjs/vis-network/blob/master/lib/network/options.js#L409
Should also be added to docs for clarity, to reduce issues like #248
Strangely, these are not missing in the compiled version found here: https://visjs.github.io/vis-network/standalone/umd/vis-network.js


dma: add system calls for dma_start/dma_stop

As per current policy of requiring supervisor mode to register
callbacks, dma_config() is omitted.
A note added about checking the channel ID for start/stop, current
implementations already do this but best make it explicitly
documented.
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

Codecov Report

Merging #6088 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6088   +/-   ##
=======================================
  Coverage   52.76%   52.76%
=======================================
  Files         414      414
  Lines       40210    40210
  Branches     7791     7791
=======================================
  Hits        21217    21217
  Misses      15782    15782
  Partials     3211     3211

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 6bb98cc...5c6f307. Read the comment docs.


[room-client-js] Added RPC request on stream unpublish method

I've added RPC request on stream unpublish method. That change enables to unpublish stream by ending MediaStream and notify server (and other participants) that stream was unpublished. It also keep participant connected to the room.
That change was made to be consistent with Java Android Kurento library.
Please verify.

Merged: https://github.com/Kurento/kurento-room/commit/b653073e154fad5dd4a85563aa823ce703700a9d
Thanks for your submission.


Help please - removing security.csm in gke

This is not actually an issue with nixery but I'm hoping that someone here might know the answer to this, since you seem to have run on GKE...  I apologize for the off topic question, please forgive me!
I am trying to use nixos/nix on gke as follows:
I set up a pod with container nixos/nix, and command "nix-env --show-trace -p curl --command 'curl google.com'".
I get the following error:
error: removing extended attribute 'security.csm' from '/nix/store/9krlzvny65gdc8s7kpb6lkx8cd02c25b-default-builder.sh': Operation not permitted
   … while evaluating the attribute 'args' of the derivation 'shell'

   at /nix/store/nixnj684ymc0vdkh7h9qcbn9mpnd22nk-spaqrzbdjrssahhbi4808rqsg1sg0xbm-source/pkgs/stdenv/generic/make-derivation.nix:201:11:

      200|         // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
      201|           name =
         |           ^
      202|             let

Have you come across this error before, and do you know how to fix it?
  Well, I'm hoping to add the nix package manager into my development environment hosted on GKE, as a small step towards a principled environment.  Perhaps after this first step I will move to fully nix-built and -controlled environments, but I can't quite land there yet.  Please bear with me on so many levels.)
THank you for reading, and hopefully for responding :)

As always, less than 24 hours after asking for help, I found the simple workaround - https://github.com/NixOS/nix/pull/4765
Sorry for the noise!


Cannot submit with "submit JS script"

I am trying to submit the form and am having a couple of challenges:

The submit button is active even when you do NOT use the captcha - form tries to submit via JS (below)
If you click submit one it fails.  If you click submit any number of times after that it just sits and does nothing!

function submitContactUs() {
    if (!$("#frmContactUs").valid()) {
        return;
    }

    $("#btnSubmit").prop("disabled", true);

    let data = {
        ContactType: $("input[name='ContactType']:checked")[0].value,
        FirstName: $("#FirstName").val(),
        LastName: $("#LastName").val(),
        Message: $("#Message").val(),
        AgreeToTerms: $("#AgreeToTerms")[0].checked,
        Email: $("#Email").val(),
        PhoneNumber: $("#PhoneNumber").val(),
        PhoneNumberExt: $("#PhoneNumberExt").val(),
        Product: $("#Product").val(),
        ContactReason: $("#ContactReason").val(),
        Rating: 1 // Set default to pass range validator
    };
    let area = $("#Area").val();

    $.ajax({
        url: 'ContactUs/SubmitContactUs',
        method: 'POST',
        data: data,
        beforeSend: function (request) {
            $("div.ajax_loader").show();
        },
        complete: function () {
            $("div.ajax_loader").hide();
        },
        success: function (data) {
            if (data) {
                if (data === "error") {
                    showMessage(area, "error", "ContactUs");
                }
                else {
                    window.location = data;
                }
            }
            else {
                $("#btnSubmit").prop("disabled", false);
                showMessage(area, "error", "ContactUs");
            }
        },
        error: function () {
            showMessage(area, "error", "ContactUs", null, null, true);
        }
    });
}

What is the best approach to include the postback info required to make the Controller Action work properly.  Please note: with this JS code we are not even getting to the Action, we just get a 500 error happening in the Validator with no real message surfaced.

Removed the nuget, downloaded the repo, added the project to my solution, can trace to a generic error:  There was an error validating the google recaptcha response. Please try again, or contact the site owner.  This is in the attribute validator.


Fix multi email submits

@kauffj - I actually work with ShawnK/Sean to resolve this issue. We use the Promise.all to be able to execute multiple api calls and check if one of them failed. It works great from my testing.

Jeremy gave verbal approval for merger at all hands.


project.plot_bayes_stats()

Hi Dr. Audet,
I am using PlatFlex to estimate the effective elastic thickness over southern Africa and I have this error during the Plot stats for estimate
TypeError                                 Traceback (most recent call last)
~/anaconda3/envs/pflex/lib/python3.7/site-packages/pandas/core/indexes/base.py in get_value(self, series, key)
4410             try:
-> 4411                 return libindex.get_value_at(s, key)
4412             except IndexError:
pandas/_libs/index.pyx in pandas._libs.index.get_value_at()
pandas/_libs/index.pyx in pandas._libs.index.get_value_at()
pandas/_libs/util.pxd in pandas._libs.util.get_value_at()
pandas/_libs/util.pxd in pandas._libs.util.validate_indexer()
TypeError: 'str' object cannot be interpreted as an integer
During handling of the above exception, another exception occurred:
KeyError                                  Traceback (most recent call last)
~/anaconda3/envs/pflex/lib/python3.7/site-packages/plateflex/classes.py in plot_bayes_stats(self, title, save)
1350                 self.map_estimate, title=title,
-> 1351                 save=save)
1352         except:
~/anaconda3/envs/pflex/lib/python3.7/site-packages/plateflex/plotting.py in plot_bayes_stats(trace, summary, map_estimate, title, save)
128     # Extract results from summary and map_estimate
--> 129     results = estimate.get_bayes_estimates(summary, map_estimate)
130
~/anaconda3/envs/pflex/lib/python3.7/site-packages/plateflex/estimate.py in get_bayes_estimates(summary, map_estimate)
201             std_te = row['sd']
--> 202             C2_5_te = row['hpd_2.5']
203             C97_5_te = row['hpd_97.5']
~/anaconda3/envs/pflex/lib/python3.7/site-packages/pandas/core/series.py in getitem(self, key)
870         try:
--> 871             result = self.index.get_value(self, key)
872
~/anaconda3/envs/pflex/lib/python3.7/site-packages/pandas/core/indexes/base.py in get_value(self, series, key)
4418                 else:
-> 4419                     raise e1
4420             except Exception:
~/anaconda3/envs/pflex/lib/python3.7/site-packages/pandas/core/indexes/base.py in get_value(self, series, key)
4404         try:
-> 4405             return self._engine.get_value(s, k, tz=getattr(series.dtype, "tz", None))
4406         except KeyError as e1:
pandas/_libs/index.pyx in pandas._libs.index.IndexEngine.get_value()
pandas/_libs/index.pyx in pandas._libs.index.IndexEngine.get_value()
pandas/_libs/index.pyx in pandas._libs.index.IndexEngine.get_loc()
pandas/_libs/hashtable_class_helper.pxi in pandas._libs.hashtable.PyObjectHashTable.get_item()
pandas/_libs/hashtable_class_helper.pxi in pandas._libs.hashtable.PyObjectHashTable.get_item()
KeyError: 'hpd_2.5'
During handling of the above exception, another exception occurred:
Exception                                 Traceback (most recent call last)
 in
12
13 # Plot stats for estimate
---> 14 project.plot_bayes_stats()
~/anaconda3/envs/pflex/lib/python3.7/site-packages/plateflex/classes.py in plot_bayes_stats(self, title, save)
1351                 save=save)
1352         except:
-> 1353             raise(Exception("No 'cell' estimate available"))
1354
1355     def plot_functions(self, est='mean', title=None, save=None):
Exception: No 'cell' estimate available

Hi @mohamedsobh53
Thank you for posting this. The issue is related to an update of PyMC3 that had not been implemented in PlateFlex yet. I just fixed the code and it should work now. You will have to pull the changes, and re-install PlateFlex using pip install .. Unless you installed initially with pip install -e ., in which case the code will update automatically without the need to re-install.

Thank you so much for your reply. I re-install it again, but another error appears:

AttributeError                            Traceback (most recent call last)
 in
3
4 # Perform estimation
----> 5 project.estimate_cell(cell)
6
7 # Print summary
~/anaconda3/envs/pflex/lib/python3.8/site-packages/plateflex/classes.py in estimate_cell(self, cell, alph, atype, returned)
1107
1108         elif self.inverse == 'bayes':
-> 1109             trace, summary, map_estimate = estimate.bayes_estimate_cell(
1110                 self.k, adm, eadm, coh, ecoh, alph, atype)
1111
~/anaconda3/envs/pflex/lib/python3.8/site-packages/plateflex/estimate.py in bayes_estimate_cell(k, adm, eadm, coh, ecoh, alph, atype)
159
160         # Get Summary
--> 161         summary = pm.summary(trace)
162
163     return trace, summary, map_estimate
AttributeError: module 'pymc3' has no attribute 'summary'

I am not sure what is going on here, since the method summary does exist with pymc3: https://docs.pymc.io/api/stats.html
I can see that your python versions have changed between your first and second post (~/anaconda3/envs/pflex/lib/python3.7 vs ~/anaconda3/envs/pflex/lib/python3.8 in your TraceBack messages). It's possible the versions got mixed up with pymc3. I would recommend doing a clean install of PlateFlex with all dependencies, which involves deleting the conda pflex environment and re-creating it.

Dear Dr. Audet,
I followed what you recommend and the same error paper. Kindly find an attached a screenshot from my machine.

Ok, I figured out what the problem was. It's again related to PyMC3. The new version of PyMC3 is 3.11, which has gotten rid of all the stats methods (see here: https://github.com/pymc-devs/pymc3/blob/master/RELEASE-NOTES.md) including the summary method. To fix PlateFlex, please do the following steps:

remove your pflex environment (conda env remove --name pflex)
re-create the pflex environment by specifying pymc3=3.10 (conda create -n pflex python=3.8 fortran-compiler numpy pymc3=3.10 matplotlib seaborn scikit-image -c conda-forge)
activate pflex and re-install jypyter (conda activate pflex; conda install jupyter)
re-install PlateFlex (pip install .)

It should work now. I added a note in the documentation to use pymc3=3.10 until I can figure out how to update PlateFlex to use pymc3=3.11.

Dear Dr. Audet,
Thank you so much!. It works fine now. I appreciate your help
Best,
Mohamed Sobh


added missing vault enterprise namespace to csi kms config map

fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2181446
as the data are filled, it is reflected in the config map -

content of the secret is the same as that entered

All the content of the secrets are same as those entered

/assign @SanjalKatiyar
/assign @bipuladh

/retitle added missing vault enterprise namespace to csi kms config map

/approve
/lgtm

/cherrypick release-4.13

/cherrypick release-4.13-compatibility

/retest

/retest


isExpanded

it would have been very helpfull if we get any variable somethjing like isExpanded to keep it open when we need it to initially open like how normal dropdown works

Hey @darshan-cn-5
For this purpose, you can pass the OverlayPortalController to dropdown and use the method overlayController.show(). If you want to open the dropdown on your screen widget initialization, you have to use the WidgetsBinding.instance.addPostFrameCallback and call the .show() method inside otherwise you'll get rendering issues.
But yeah, good suggestion. I'll add the isExpanded property in the future release!


Solving compilation error for angular lib

Solving compilation error for angular lib

hi @z687wang thank you for this PR, the changes look good :) if you can just change the const to let and push ill merge it in

Thanks, jason. @jasonaibrahim


It should be possible to register and sideload the office add-in without dev server

I don't upload the dist files from webpack to localhost, but to some other URL, thus it should be possible to only register and sideload the office add-in without starting the dev server at localhost. How to do that with office-addin-debugging?

I mean, I simply wanted to automatically sideload an addin without all the attached dev server initialization

If you change the dev-server script in package.json, it can run whatever you want, or if not present, it won't run the dev-server. The office-addin-debugging start command also has a --dev-server parameter if you want to provide a different command line to run when debugging is started. If falls back to the package.json script if a parameter isn't provided.


custom awake sound not working

First of all, great project that works really nicely - thanks!
I wanted to customise the awake sound that is played, and while the included awake.wav works nicely, trying to replace it with another .wav file with --awake-sound sound/otherfile.wav results in the following error after wakeword detection:
ERROR:__main__:Unexpected error
Traceback (most recent call last):
  File "/home/pi/homeassistant-satellite/homeassistant_satellite/__main__.py", line 214, in main
    play(media=args.awake_sound)
  File "/home/pi/homeassistant-satellite/homeassistant_satellite/snd.py", line 90, in play_subprocess
    with wave.open(ffmpeg_proc.stdout, "rb") as wav_file:
  File "/usr/lib/python3.9/wave.py", line 509, in open
    return Wave_read(f)
  File "/usr/lib/python3.9/wave.py", line 163, in __init__
    self.initfp(f)
  File "/usr/lib/python3.9/wave.py", line 128, in initfp
    self._file = Chunk(file, bigendian = 0)
  File "/usr/lib/python3.9/chunk.py", line 63, in __init__
    raise EOFError
EOFError

The pipeline is also interrupted and the script has to be restarted.
I have checked that the file is playable with aplay without issues.
Any ideas?
System info:
Raspberry Pi 3A+ running Raspbian bullseye

You're welcome!
The WAV file may have an incorrect length in the header. "Converting" it to a WAV through sox or ffmpeg should fix this.

That worked like a charm!
(For future reference, the command is: ffmpeg -i <input_file> <output_file>.wav)
Thanks for the lightning fast response, now I can enjoy my Star Trek computer beep :)


Chose image from camera

Hi,
this is not an issue but a need I think at least for me. I m using  file from camera and with new update its removed so I cant upgrade to latest version. its possible add it again. I dont want to additional package for this purpose. thanks.

Hi. I’m sorry , this was actually a feature request and removed intentionally because when you are publishing your app doesn’t make sense to have camera permissions enabled when you don’t need them.
If you want to stick with the camera and file picker, just either use both file_picker and image_picker or use an older version such as 1.2.0 (file_picker: 1.2.0).
Thank you for your compreenhsion.


Changed random name for stars input to be more random

This should fix the problem of the reviews with 10+ stars

@n00b2pr0 will you code review this, please?

@ericsaupe Looks dandy :dancers:


Remove kubeUtil references from logs agent launchers

What does this PR do?
We're trying to clean up some old code from the kubeUtil, so anything
that fetches pod information needs to be migrated to workloadmeta. This
commit removes all references to it from the docker and kubernetes
launchers, and removes a lot of retrying logic that's now redundant
since pods and containers are guaranteed to be present in the store by
the time the logs agent gets to know about them.
Motivation
Cleaning up unnecessary calls to the kubelet now that workloadmeta is a viable (and better!) replacement.
Describe how to test/QA your changes
Log collection still works. In kubernetes, both with container collect all enabled and disabled. In docker, with both container labels and pod annotations.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Is dockerutil going away too?

kubeutil and dockerutil aren't going away per se, but ideally just getting some data about a container should go to workloadmeta instead. I think the refactoring you'll be working on will take care of it naturally for dockerutil in the logs agent, but if not I'll do another pass when it's all done to get rid of it too.


Add configuration to enable legacy authorization runtime

Purpose
The default behavior of product IS used legacy authorization runtime which is no longer used with the introduction of API resources based authorization.
To revert this behavior, use the following deployment.toml configuration.
[legacy_authz_runtime]
enable = false

This PR is a part of the fix

https://github.com/wso2/product-is/issues/16363

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6586292885

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6586292885
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6588962931

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6588962931
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6592229788

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6592229788
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6593815170

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6593815170
Status: cancelled

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6594851448

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6594851448
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6595890874

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6595890874
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6597953962

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6597953962
Status: success


Taking too long to load.

Describe the bug
The website takes too long to load so github doesn't display it.
Expected behavior
They site should load fast so github won't time it out.
Desktop (please complete the following information):

OS: Windows (11)
Browser: Chrome (Version 116.0.5845.190 (Official Build) (64-bit))

Ok fixed. Closing...


rst docs on pypi

PyPi is not rendering the long_description in setup.py (which is equal to the README.rst)
the :math: directive seems to be the culprit.  will figure it out later.

You can do this to cerify your long_description locally:
$ pip install readme
$ python setup.py check -r -s

hmmm ... I get,
python setup.py check -r -s
running check
warning: Check: This command has been deprecated. Use `twine check` instead: https://packaging.python.org/guides/making-a-pypi-friendly-readme#validating-restructuredtext-markup

warning: Check: The project's long_description has invalid markup which will not be rendered on PyPI. The following syntax errors were detected:
line : Warning: No MathJax URL specified, using local fallback (see config.html)

error: Please correct your package.

this seems relevant ... https://github.com/pypa/readme_renderer/issues/115

fixed by removing math directive from readme.rst


[IOTDB-2955] Design and implement ClientManager for thrift client's pooling management

see jira2955
see doc for detail

Coverage decreased (-0.1%) to 53.94% when pulling 0953f6a72ad54349fd3aced1b4e492c18d31743d on client_manager into ac51b0802ac5d016f028fbfe829f8b8ab530740e on master.

LGTM

LGTM

LGTM


docs: Add missing /root/zulip creation on upgrading

scripts/zulip-puppet-apply requires /root/zulip/puppet to find modules.

Automated message from Dropbox CLA bot
@kou, it looks like you've already signed the Dropbox CLA. Thanks!

@kou the Zulip install process creates /root/zulip as a symlink to /home/zulip/deployments/next, which is in turn a symlink to wherever we unpack the to-be-installed tarball at under /home/zulip/deployments.  So I don't think this change should be needed, but I am interested in trying to figure out why that symlink wasn't present, since clearly you ran into an actual issue here.  Is what /root/zulip was on your system; did it just not exist?
I think another approach worth investigating is modifying /root/zulip-puppet-apply to just use the deployment it was run from as the source of puppet config, basically replacing --modulepath=/root/zulip/puppet with something based on __file__.  That would eliminate our dependency on /root/zulip being anything at all entirely, and I think is likely to be the right way to improve this system.

Thanks for your explanation.

Is what /root/zulip was on your system; did it just not exist?

It just doesn't exist. I may removed it by hand but I didn't remember... Sorry. I close this pull request.

I think another approach worth investigating is modifying /root/zulip-puppet-apply to just use the deployment it was run from as the source of puppet config, basically replacing --modulepath=/root/zulip/puppet with something based on __file__. That would eliminate our dependency on /root/zulip being anything at all entirely, and I think is likely to be the right way to improve this system.

It souds good to me.

Cool, opened https://github.com/zulip/zulip/issues/3608 for that issue.  Thanks @kou!


Using a separate config file or path to save ColorSchemes.json

Description of the new feature/enhancement
Many users like to change their preference of terminal, and the current way of setting and store ColorSchemes.json is a litte bit unconverience.
Now, if I wanna to try a NewStyle, I only need to copy content and paste it into the section of schemes in settings.json.
However, when I downloading a collection of shcemes, the way above is unconfortable, cause I don't wanna to repeat it like 100 times.
Whats more, iTerm2 have a quicker way to get the preview of scheme.

Proposed technical implementation details (optional)
My suggestion is using a specific dir like ~/.WindowsTeriminal/colors/ to save all ColorSchemes.json, which will more easier to download, to add.
When launching WindowsTerminal, reading all *.json in the above dir automaticlly.
which will also be easier to find or udpate content in each *.json

Thanks for filing! A few notes:

Saving settings to a different location is something we've talked about in the past. I can't find an open issue on it though, so I'll just use this to track it for now.
Fragments are a solution to this problem, actually! You can introduce new color schemes via JSON fragment extensions. Read more about it here: https://learn.microsoft.com/en-us/windows/terminal/json-fragment-extensions
Overall, we want to invest in the Settings UI to make this a non-issue. We're tracking all our major investments in the Settings UI here: #10000

Saving settings to a different location is something we've talked about in the past. I can't find an open issue on it though

Ah, we're tracking this in #2933 actually. At least, that's the place I've duped this all to in the past - for both layering beyond just fragments, but also roaming the settings. We can consolidate this.
/dup #2933


[Proto Annotations] Better parsing of ResourceNameConfigs

Prioritize GAPIC config values over those from proto annotations.

PTAL

Breaking up this PR into smaller ones.


Object and array types not modified

When updating an array  (or object) field like this:
$entity->params['foo'] = 'bar';
the change is not detected by the entity. This is perfectly logical because the setter is never called (we're updating a reference). The correct value is stored in Entity::$_data, but not in Entity::$_dataModified.
This screws up the output for Entity::dataModified() and Entity::dataUnmodified(), and it's a problem when you're trying to save the object, because saving/updating will only look at the modified fields.
This fixes saving by the way :)
$entity->params['foo'] = 'bar';
$entity->params= $entity->params;

Seems like a bug. I will investigate.


Update StatusAction.php

I started using this bundle today and paid using stripe test card. One of the cards is supposed to return paid true and succeeded true but the bundle still say pending so i couldnt add credit to my user programaticaly. with this edit it works. Please double check before merge because im only a payum begginer and dont want to introduce a bug is a bundle as critical as this one for a business.

I cannot merge it here, it is a readonly sub tree split from payum/payum repo. Could you please open a PR on payum/payum repository.

Look at this one https://github.com/Payum/Stripe/pull/3


[SPARK-7237] Many user provided closures are not actually cleaned

Note: ~110 lines are tests.
In a nutshell, we never cleaned closures provided through the following operations:

sortBy
keyBy
mapPartitions
mapPartitionsWithIndex
aggregateByKey
foldByKey
foreachAsync
one of the aliases for runJob

For more details on a reproduction and why they were not cleaned, please see SPARK-7237.

Merged build triggered.

Merged build started.

@zsxwing @pwendell Please have a look.

Test build #31314 has started for   PR 5787 at commit 8ac3074.

Merged build triggered.

Merged build started.

Test build #31318 has started for   PR 5787 at commit e83699e.

Test build #31318 has finished for   PR 5787 at commit e83699e.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31318/
Test FAILed.

Um, retest this please

Merged build triggered.

Merged build started.

Test build #31328 has started for   PR 5787 at commit e83699e.

Test build #31314 has finished for   PR 5787 at commit 8ac3074.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31314/
Test PASSed.

Merged build finished. Test PASSed.

Test build #31328 has finished for   PR 5787 at commit e83699e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31328/
Test PASSed.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #31359 has started for   PR 5787 at commit 6498f44.

Sorry. Just deleted my wrong comments.
mapPartitionsWithContext needs to be updated too.

Test build #31359 has finished for   PR 5787 at commit 6498f44.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31359/
Test PASSed.

@zsxwing I didn't update that one (and others like foreachWith) because it's deprecated. I don't think it's necessary.

Merged build triggered.

Merged build started.

Test build #31640 has started for   PR 5787 at commit df3caa3.

Test build #31640 has finished for   PR 5787 at commit df3caa3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31640/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #31675 has started for   PR 5787 at commit 7265865.

Test build #31675 has finished for   PR 5787 at commit 7265865.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class Dialect
  class DialectException(msg: String, cause: Throwable) extends Exception(msg, cause)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31675/
Test PASSed.

Anything else? Can I merge this?

Alright, I'm merging this into master and 1.4, thanks everyone.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31886/
Test FAILed.


Add organizationalUnit to passtlscert middleware

What does this PR do?
Adds the Organizational Unit Name; aka OU (traefik annotation organizationalUnit to follow organization vs Organization Name) to the passtlscert middleware. This field is added to both the subject and the issuer. Initial discussion took place in #7951.
While the OU on the "issuer" not officially part of the RFC
(https://tools.ietf.org/html/rfc3739#section-3.1.1) I've included it
because traefik includes the "province" in the same fashion. In
addition, it would be extra logic to remove it when it might actually be
useful to have.
Motivation
I'd like to be able to access the OU passed without having to pass the entire pem block. Doing so requires a second pem decode (when traefik is already doing one).
More

[x] Added/updated tests

I added one additional test that we can get rid of if you'd like which tests to make sure it's not present if not requested, to ensure legacy requests aren't affected.

[x] Added/updated documentation

Additional Notes
I ended up changing more than I originally liked about the Vue UI so that Organization and Organizational Unit could be "next" to each other. I'm totally cool with reverting this portion and tacking OU onto the end to minimize diffs. Your call.
Here are previews of what the UI looks like with this PR:

The second screenshot shows what it would look like for existing users. For example if this was added in 2.5 and they didn't add the organizationalUnit, they'd get a red switch next to it:

Well, now that it's plastered everywhere (in my commit message and initial PR) I realized my mistake in the commit comment. The province is in fact included in stateOrProvinceName, so I guess there would be justification for removing this field from the subject.
Again, open to suggestions/ideas.

Hello @FernFerret ,
Thanks for your contribution!
This PR is now labeled needs-design-review,
as you can see in our contribution guide, this means that we have to take a closer look at the scope of impact for that PR to see, how it would interact with the other parts of Traefik.
We will come back to you soon when we did the first design review iteration.

Hello @FernFerret,
Thanks to your PR, we realized that it would be cleaner to separate the distinguished name of the issuer and the subject.
In that way, we can avoid providing non defined attribute in the rfc.
WDYT?

@jbdoumenjou I'm fine with that!
I think you're saying we separate the DistinguishedNameOptions into 2 structs (one for issuer and one for subject). IssuerDistinguishedNameOptions vs SubjectDistinguishedNameOptions?

Yes, to have structures containing only the fields defined by the RFC.
And split getDNInfo in something like getSubjectDNInfo and getSubjectDNInfo.
It will duplicate some code but it will be clearer and provide better support of the RFC.
However, to be backward compatible, we must support all the existing fields in the two structures and manage the deprecation (comment + doc).
We can create a PR to handle the refactor/doc so you can rebase on it and manage only the new field.
WDYT?

Sounds good to me I'll get the changes made soon!

Hi @jbdoumenjou I pushed another commit today that I believe makes the requested changes. I split the struct into one for issuer vs subject and I do like it better, even at the cost of the duplicated fields in the struct. It maps a lot nicer to the RFCs this way.
I wasn't exactly sure what you meant when you said:

However, to be backward compatible, we must support all the existing fields in the two structures and manage the deprecation (comment + doc).
We can create a PR to handle the refactor/doc so you can rebase on it and manage only the new field.

I ended up leaving CommonName in the Issuer despite it not being part of the RFC. I believe this is what you meant, but I just wanted clarification. Is there some action I'm expected to take for the deprecation guide? Is there any information you have that I could read up on that?
Thanks again and sorry for the delay!

Hello @FernFerret,
I was wrong for the deprecation.
In fact, the RFC says:

Additional attributes MAY be present, but they SHOULD NOT be
necessary to identify the issuing organization.

So, I think it is ok to keep the field as-is.

WIP on improving the doc.


CARBON-16076: Restructure OSGi related directories

This p/r is to resolve CARBON-16076.
The carbon kernel OSGi related directories have been re-structured as follow:
(Only OSGi related directories are mentioned here)
<CARBON_HOME>
├── lib
│   └── README.txt
└── wso2
    ├── default
    └── lib
        ├── artifacts.xml
        ├── features
        ├── p2
        ├── plugins
        └── README.txt

lib - Addtional OSGi bundles needed for carbon servers can be added here. It's similar to /osgi/dropins directory in kernel 5.2.0-m2

wso2 - This directory will have following sub directories:
2.1. lib - This will be the OSGi Repository for carbon which will have features, plugins and p2 directories.
2.2. profile-n - This directory will be profile-n directory which will have all the profile-n's configurations. The 'default' profile will be as below:

<CARBON_HOME>
└── wso2
    ├── default
    │   ├── configuration
    │   │   ├── config.ini
    │   │   ├── org.eclipse.equinox.simpleconfigurator
    │   │   └── org.eclipse.update
    │   └── eclipse.ini

In order to merge this P/R, carbon-maven-plugins version 3.0.0 has to be released with changes in P/R-38 and 'carbon.feature.plugin.version' has to be updated to 3.0.0 in 1.
Thanks.

Please note: This PR should not be merged till update the maven-feature-plugin version 3.0.0 is released.
@Thanu : Can you update the version to 3.0.0?

Updated the carbon feature plugin version to 3.0.0.

Closing the PR since there are conflicts. This is resolved in #1218


Update checkout and order price calculation - adjust to new promotion objects. Ensure the prices as properly recalculated based on promotions - checkout and draft order. The currently created orders shouldn't be changed (7 days) @IKarbowiak

Duplicate.


Iterating xor

To allow for large amounts of data to be xor-ed against a pad, utils.xor can take an Iterator, and Xor produces an Iterator.
Things that may not be cool with this.

Xor is a class, so I have named it as I would a class, but is this conventional.
The Iterator type is Iterator[int] with no real enforcement that the ints are valid for bytes.

Still I am almost certainly going to approve my own pull request.

Xor is properly named as a class, see discussion on Reddit


[Model Update]: Update Fleet.Vehicles -> update of shared shared.business_partner_number to latest version

Update Reason
The current version of Fleet.Vehicles was released 2 weeks ago. Afterwards we found a regex failure in the shared aspect model shared.business_partner_number that is used in this semantic model (BPNS regex failure).
Update is to change the reference to the lates shared model.
MS1 Criteria

[x] The model that should be updated exists
[x] The referenced use case exists Quality Management Use Case
[x] The potential updates are discussed with all stakeholders
[x] A decision on versioning was made in consensus with the affected parties according to the guidelines.
[x] The potential update will be either

[x] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

[ ] A modeling steward has been assigned

@agg3fe Please approve MS1 for this update