Specify yaml config file failed  "Invalid or unexpected token"

This works without config file:
svgo -r -f ./assets

Specify yaml config file failed:
$ svgo -r -f ./assets --config ./config/.svgo.yml
Invalid or unexpected token

./config/.svog.yml:
plugins:
  - removeXMLNS: true
  - removeViewBox: false
  - removeDimensions: true
  - sortAttrs: true

js2svg:
  pretty: true
  indent: ' '

svgo 2.0.1

Hi. Yaml is no longer supported. Also config format is changed. You can specify array of strings in this case. See release notes https://github.com/svg/svgo/releases/tag/v2.0.0

looks like yml support was removed and converting this config to json breaks removeAttrs and removeViewBox ... i'd hold off updating to 2.x until all bugs are fixed.

Neither the readme nor the release notes make clear how to disable a specific plugin, and things like --disable=removeViewBox on the command line do not work anymore. The documentation hasn't been updated too.
The release notes make it look like we need to list all plugins, overriding the default list but that seem unpractical. I might be mis-reading the release notes.

I updated docs here https://github.com/svg/svgo/pull/1337
Please tell if you have any questions.

Thank you @TrySound, that's mighty helpful! :)


Clarify RDP Requirements

There seems to be a missing requirement, possibly due to an assumption that has been made.
You cannot connect to the VM over RDP unless the PC you are connecting from is joined to the same domain or Azure AD Joined to the same Azure AD.
This information is noted on this page at this link  - https://docs.microsoft.com/en-us/azure/active-directory/devices/howto-vm-sign-in-azure-ad-windows#log-in-using-azure-ad-credentials-to-a-windows-vm
However since it is NOT in the requirements section it was missed by myself and 4 other Azure Engineers.
I propose the following requirement be added to the Requirements section:
RDP must be initiated from a Windows 10 PC that is Azure AD joined or hybrid Azure AD joined to the same directory as the target VM.

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

ID: c946fe0f-e18d-2529-2fbf-bce04759fbca
Version Independent ID: 885a61d1-6096-5aa0-fe8d-f1ec8d55e542
Content: Sign in to Windows virtual machine in Azure using Azure Active Directory (Preview)
Content Source: articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@DeanCefola
Thanks for your feedback! We will investigate and update as appropriate.

Hi @DeanCefola ,
Thanks for your feedback! We have reviewed both documents and this is mentioned in each. (It is in the notes on this document.) I re-read them and personally think it is clear as-is, but if you still feel this way you are very welcome to make a pull request yourself by clicking the edit button on the top right corner of the page. That way you will get credited for the change.

I'm closing this out but feel free to make a pull request if you'd like!


[building-rollup] preload babel-helpers

The babel helpers chunk is not preloaded in the HTML currently, while other static entrypoints are.

@LarsDenBakker Why the build needs babel-helpers?

@JosefJezek because we run babel to compile to a lower target. This is now solved on master though.


Acl::SetRule performance is very slow

We are dealing with rules in the 70k - 100k 1k - 2k range.  It currently takes setRule around 2.5 seconds to process all of these rules.
I have been able to increase the performance of this method by roughly 40% by simply eliminating the use of array_merge.
Suggested Change Acl line:580 to:
foreach($children as $child) {
    $resources[] = $child;
}

Suggestions on how this method can be improved further would be great appreciated. The tree that is being generated takes approximately 100-130ms to serialize/unserialize.
Note: Acl configuration will be cached in Production.
EDIT:
Sorry rules are in the 1500 - 2000 range.  Roughly 300 roles and 300 resources.

Here is the current benchmarks running 1538 rules.
Function                                        Count   Incl.       Excl.   Average (ms)
Zend\Permissions\Acl\Acl::setRule()             1538    1,463.07    832.59  0.95
Zend\Permissions\Acl\Acl::getRules()            70450   319.49      292.49  0.00
Zend\Permissions\Acl\Acl::getResource()         70214   132.21      98.47   0.00
Zend\Permissions\Acl\Acl::getChildResources()   70210   124.85      111.78  0.00
Zend\Permissions\Acl\Acl::hasResource()         70808   34.23       34.17   0.00

@steverhoades you can try patching the line you suggested, but you'd need to verify edge cases with string keys and array keys first.

@Ocramius good point.
How about:
foreach($children as $key => $child) {
    $resources[$key] = $child;
}

@steverhoades can work, yes.

@steverhoades again, I'd start from the tests: the snippet above overwrites numeric keys.

@Ocramius I should know better, I'll check out the tests.  From reading the code it appears as  though the keys should be resourceIds... perhaps i have that wrong.

This repository has been closed and moved to laminas/laminas-permissions-acl; a new issue has been opened at https://github.com/laminas/laminas-permissions-acl/issues/6.


When was the last time you see a path with backslash in linux?

For any weird reason, in this set up, the Visual Studio Code when I use copy relative path if copy to the clipboard a path with the useless  backslash
Version: 1.68.0-insider
Commit: 17c75e11805103026b943c8dc4d50a35f245f76f
Date: 2022-05-20T05:16:13.965Z
Electron: 17.4.4
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.15.38-1-MANJARO

nothing I recall immediately

I cannot reproduce on Ubuntu with latest insiders. Can you provide a gif please?

https://drive.google.com/file/d/1nUT2pUWGJ8ymtPjBdHjXTYDCr2pG7aDx/view?usp=sharing

I think to remember this occur after sync my vscode, the last installation had Windows 11

This is the commit https://github.com/microsoft/vscode/commit/17c75e11805103026b943c8dc4d50a35f245f76f has 4 days ago

In your video you can see the badge on the gear icon in the bottom left. Can you update to the latest insiders and give it a try?

Same behavior, commit from last day
Version: 1.68.0-insider
Commit: c0769274fa136b45799edeccc0d0a2f645b75caf
Date: 2022-05-23T05:18:06.482Z
Electron: 17.4.4
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.15.38-1-MANJARO

I can't update using the gear icon in Manjaro

In your settings ensure you don't override the path separator the setting for / is as follows:     "explorer.copyRelativePathSeparator": "/"

You are kidding me? 😂
This is the most extravagant thing a team has said to me 😂

Whatever, proceed as you wish 😂

Microsoft, king of software quality 😂

You can try changing that setting from auto to /. We of course want to help but there's only so many linux distributions I can test. I cannot reproduce this on macOS or Ubuntu and I do not have an Arch block nor does Azure VMs support one leaving me without a testing platform to dig deeper into your problem.

If you investigate all about the settings explorer.copyRelativePathSeparatorand the resources provide by me is impossible don't determine the cause of issue (Principle of sufficient reason), would be better ask the author of issue all the necessary to know how resolve it instead of write all extravagant thing I read, also exists a lot of solutions can run all the base distros, choice don't use it is a thing more of the will of the team than the possibility of see it for part of Microsoft, also the team ignore parts as I think to remember this occur after sync my vscode, the last installation had Windows 11 that require the team ask me the settings file or my email to see my settings
And also, in the case of "blablabla so many linux distributions" you can provide a package of Flatpak, Snap or AppImage and test a least all the base distros, is absurd I has to see a useless backslash in linux using explorer.copyRelativePathSeparator set as auto, does not exist any criteria to inferred the path in linux should contains backslash
The problem is "explorer.copyRelativePathSeparator": "/" resolve my issue, but doesn't resolve the issue with the default, instead of it Microsoft prefer be rude saying We closed this issue because we don't plan to address it in the foreseeable future. and then process lying about they can't reproduce the issue, but this issue should never have happened, this is the things the testing team should catch before other people sent their issue to Microsoft and it prefers be rude with it
Thanks for the useless support to Linux I suppose a multimillionaire team not have sufficient money to provide this support


Changes in process leave me lost as to how to get pipeline running

Deploying a previously working pipeline stopped when AZ Login made changes (links below). I've been reviewing docs but I can't find a way to remedy.
My application is a Django Website hosted on Azure Web App Services. The deployment file.yaml is automatically generated by Azure App Services, so I don't really know what I'm supposed to change. It automatically creates the environment secrets as well.
The the pipeline: https://github.com/BillmanH/exoplanets/actions/runs/12121138319/job/33791478871
The build.yaml: https://github.com/BillmanH/exoplanets/blob/main/.github/workflows/main_exodestiny.yml
The process is connected to GH through the default connector:

The error:
Error: AADSTS7002138: No matching federated identity record found for presented assertion subject 'repo:BillmanH/exoplanets:environment:Production'. The subject matches with case-insensitive comparison, but not with case-sensitive comparison. Check your federated identity credential Subject, Audience and Issuer against the presented assertion. See documentation at: https://learn.microsoft.com/entra/workload-id/workload-identity-federation. See breaking change notification and remediation at: https://learn.microsoft.com/en-us/entra/identity-platform/reference-breaking-changes#august-2024. Trace ID: 996708da-0191-4988-a3c3-00fc96a03501 Correlation ID: 1a333cae-e34a-4960-a43a-8815307975fb Timestamp: 2024-12-02 17:28:39Z

Error: Interactive authentication is needed. Please run:
az login

Error: Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.

https://github.com/Azure/login#readme
https://learn.microsoft.com/entra/workload-id/workload-identity-federation
https://learn.microsoft.com/en-us/entra/identity-platform/reference-breaking-changes#august-2024
As this is a pretty generic workflow for Azure Web App deployment, I imagine others will find the answer helpful. My repo is public which will make it easier for other users to see what they can change.
My question:
What do I need to do to make the pipeline run again. The links above and the readme offer a lot of information, but none of it directs me to "What I need to change in the pipeline?".  Can you offer me some clues?

Hi @BillmanH, according to the Note session given in https://learn.microsoft.com/en-us/entra/identity-platform/reference-breaking-changes#august-2024, please update the environment name property in your workflow from "Production" to "production" to comply with Azure App Service's requirements.

Hey, it was exactly what was in the instructions. Thanks for the pointer I really appreciate it. I was thinking it was a secret somewhere not the actual name of the environment.
For others who have the same issue (in case there are any), the actual deploy steps are case sensitive.  So in line 55 of my workflow.
  deploy:
    runs-on: ubuntu-latest
    needs: build
    environment:
      name: 'production'  <--- this right here.
      url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}
    permissions:
      id-token: write #This is required for requesting the JWT

The file is generated automatically by Azure Webapp, so it could be possible that this comes up again.
Thanks team!


Data from load function is not persistent after rendering

Describe the bug
I am passing a random string through load function. I am expecting that the already generated string that I get from load function will be persistent during rendering my webpage. However, the rendered string and the one generated during SSR is different.
Reproduction
https://stackblitz.com/edit/vitejs-vite-4uijlv?file=my-app%2Fsrc%2Froutes%2F%2Bpage.svelte
cd my-app/
npm install
vite dev

Notice that the string printed in the console is different than the one showing in the webpage.

Logs
No response
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (2) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^3.2.2 => 3.2.2
    @sveltejs/kit: ^2.5.18 => 2.5.18
    @sveltejs/vite-plugin-svelte: ^3 => 3.1.1
    svelte: ^5.0.0-next.1 => 5.0.0-next.183
    vite: ^5.3.3 => 5.3.3

Severity
blocking all usage of SvelteKit
Additional Information
I have the following questions:

Am I using the load function in a wrong way?
Why the load function seems to re-run itself during client side hydration and generates a different ID than the one I got during SSR?
Am I understanding SSR and load function incorrectly? Is sveltekit hydration re-runing the load function on the client side regardless I run it already during SSR or not?

PS: I tried both svelte 4 and svelte 5, both are the same.

This is the intended behavior. https://kit.svelte.dev/docs/load#universal-vs-server Universal load functions run on both the client and the server. Among other reasons, this is so that they can return things that can't be serialized and sent over the network. In your case, this results in the app being hydrated on the client side to a different value than was rendered on the server.

I guess I am misinterpreting what it means by running on "both" sides. I was under the impression that the client side code will not repeat whatever that is already generated from the server side so as to make the rendering faster.
It might be too magical for client side to "hydrate" in that fashion.
It turns out that only the REST API fetch inside of the load function is not re-run.
The feature I was imaging could possibly be the sale point of the Qwik framework.


FINERACT-1492: Hikari configuration based on application properties

Description
Hikari configuration based entirely on application.properties. Tuning can be done via environment variables without recompiling. I got also rid unnecessary configuration classes and environment variables. No additional environment variables for the tenant databases; everything necessary is discovered via the Hikari configuration.

@awasum could you have a look at this please and approve? Simplifies configuration. Thanks in advance :-)

Hi - I was looking at this and fully agree it's a great improvement - makes
things a lot cleaner and simpler.
The only concern I have is: it will break everyone's current configuration.
Do you think it would make sense to make this change backward compatible?
Ie use the same environment variables if they have been defined.
On Fri, Jan 21, 2022, 18:46 Aleksandar Vidakovic @.***>
wrote:

@awasum https://github.com/awasum could you have a look at this please
and approve? Simplifies configuration. Thanks in advance :-)
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2024#issuecomment-1018393053,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASJVCQ7DD5NNIAIR4YAZZ3UXE2SHANCNFSM5MDXYSRA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because your review was requested.Message ID:
@.***>

@ptuomola  @vidakovic - if you read  FINERACT-1115, you can see the dilemma that you just solved. In my simple understanding, I agree to removal of recompilation.

@ptuomola ... valid point... how about this: I'll add a easily removable compatibility - java - configuration that is activated only if these old (deprecated) configs are detected (environment variables etc.) and spins up things with a fat warning message on the console telling people to migrate their configuration?

Sounds like a great plan! That allows us to move to the new standard while keeping backward compatibility for at least a few releases….

On 21 Jan 2022, at 22:28, Aleksandar Vidakovic @.***> wrote:
@ptuomola https://github.com/ptuomola ... valid point... how about this: I'll add a easily removable compatibility - java - configuration that is activated only if these old (deprecated) configs are detected (environment variables etc.) and spins up things with a fat warning message on the console telling people to migrate their configuration?
—
Reply to this email directly, view it on GitHub https://github.com/apache/fineract/pull/2024#issuecomment-1018551326, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASJVCUPRLYUSDU6ILGKHIDUXFUPBANCNFSM5MDXYSRA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.

@ptuomola ... finally I found a quiet moment to wrap this up. While I was at it I introduced a mapping class for Fineract related properties (everything prefixed fineract.* in application.properties). The criteria I use to activate the backwards compatible configuration is a check on environment variable fineract_tenants_driver (if it's empty then the new configuration is assumed, if not empty then org.apache.fineract.infrastructure.core.config.CompatibilityConfig is activated. I've added some additional hints to the README and to docker-compose.yml. The Docker Compose file is configured to use the new stuff (with more options to tweak the Hikari pool configuration).
I've tried both configs, work as advertised. Would be great if you could approve to get this stuff out of the way for the next release. Thanks again.


Reduce buffer times in route calculation

Scenario:

compare TIXI24 and MS Access Systems using the same rides
TIXIZUG, test begin 03. Aprl 2017
test data, migrated from MS Access

The test showed that TIXI24 needs more resources than MS Access.
Reason:

TIXIZUG defines the buffer times in passenger field "extraminutes"
4 minutes for normal passengers, 8 minutes for passengers in wheelchairs
This data is migrated and included in the route duration calculation
ON TOP OF THE BUFFER TIMES IN TIXI24

3 minutes hop on
3 minutes hop off
5 minutes wait time before pickup

Workaround:
Change the buffer times in TIXI24 DispoVariables as follows:

0 minutes hop on (included in passenger extraminutes)
0 minutes hop off  (included in passenger extraminutes)
2 minutes wait time before pickup

Given the same data basis, the next test will show 9 MINUTES LESS FOR EACH RIDE.

This has been fixed in commit https://github.com/TIXI24/sfitixi/commit/47c903ca4216e3e5699302e0d36fd42f92a324ca


Compiling under mingw with clang error..

~/gemma.cpp$ cmake --build build -j 4
[79/81] Linking CXX executable benchmark.exe
FAILED: benchmark.exe
C:\WINDOWS\system32\cmd.exe /C "cd . && C:\msys64\clang64\bin\clang++.exe -O3 -DNDEBUG  CMakeFiles/b
enchmark.dir/benchmark.cc.obj -o benchmark.exe -Wl,--out-implib,libbenchmark.dll.a -Wl,--major-image
-version,0,--minor-image-version,0  libgemma.a  _deps/highway-build/libhwy.a  _deps/highway-build/li
bhwy_contrib.a  _deps/highway-build/libhwy.a  _deps/sentencepiece-build/src/libsentencepiece.a  -lpt
hread  -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvap
i32 && cd ."
ld.lld: error: undefined symbol: WakeByAddressAll
>>> referenced by CMakeFiles/benchmark.dir/benchmark.cc.obj:(main)
>>> referenced by CMakeFiles/benchmark.dir/benchmark.cc.obj:(hwy::ThreadPool::~ThreadPool())
>>> referenced by libgemma.a(gemma.cc.obj):(gcpp::GenerateGemma(gcpp::Gemma&, unsigned long long, un
signed long long, float, std::__1::vector<int, std::__1::allocator<int>> const&, unsigned long long,
 gcpp::KVCache&, hwy::ThreadPool&, hwy::ThreadPool&, std::__1::function<bool (int, float)> const&, s
td::__1::function<bool (int)> const&, std::__1::mersenne_twister_engine<unsigned int, 32ull, 624ull,
 397ull, 31ull,<PHONE_NUMBER>u, 11ull,<PHONE_NUMBER>u, 7ull,<PHONE_NUMBER>u, 15ull,<PHONE_NUMBER>u, 18ull, 18124
33253u>&, int))
>>> referenced 230 more times

ld.lld: error: undefined symbol: WaitOnAddress
>>> referenced by CMakeFiles/benchmark.dir/benchmark.cc.obj:(hwy::BlockUntilDifferent(unsigned int,
std::__1::atomic<unsigned int>&))
>>> referenced by libgemma.a(gemma.cc.obj):(hwy::BlockUntilDifferent(unsigned int, std::__1::atomic<
unsigned int>&))
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
[80/81] Linking CXX executable compress_weights.exe
FAILED: compress_weights.exe
C:\WINDOWS\system32\cmd.exe /C "cd . && C:\msys64\clang64\bin\clang++.exe -O3 -DNDEBUG  CMakeFiles/c
ompress_weights.dir/compress_weights.cc.obj -o compress_weights.exe -Wl,--out-implib,libcompress_wei
ghts.dll.a -Wl,--major-image-version,0,--minor-image-version,0  libgemma.a  _deps/highway-build/libh
wy.a  _deps/highway-build/libhwy_contrib.a  _deps/highway-build/libhwy.a  _deps/sentencepiece-build/
src/libsentencepiece.a  -lpthread  -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut
32 -luuid -lcomdlg32 -ladvapi32 && cd ."
ld.lld: error: undefined symbol: WakeByAddressAll
>>> referenced by CMakeFiles/compress_weights.dir/compress_weights.cc.obj:(hwy::ThreadPool::~ThreadP
ool())
>>> referenced by libgemma.a(gemma.cc.obj):(gcpp::GenerateGemma(gcpp::Gemma&, unsigned long long, un
signed long long, float, std::__1::vector<int, std::__1::allocator<int>> const&, unsigned long long,
 gcpp::KVCache&, hwy::ThreadPool&, hwy::ThreadPool&, std::__1::function<bool (int, float)> const&, s
td::__1::function<bool (int)> const&, std::__1::mersenne_twister_engine<unsigned int, 32ull, 624ull,
 397ull, 31ull,<PHONE_NUMBER>u, 11ull,<PHONE_NUMBER>u, 7ull,<PHONE_NUMBER>u, 15ull,<PHONE_NUMBER>u, 18ull, 18124
33253u>&, int))
>>> referenced by libgemma.a(gemma.cc.obj):(gcpp::GenerateGemma(gcpp::Gemma&, unsigned long long, un
signed long long, float, std::__1::vector<int, std::__1::allocator<int>> const&, unsigned long long,
 gcpp::KVCache&, hwy::ThreadPool&, hwy::ThreadPool&, std::__1::function<bool (int, float)> const&, s
td::__1::function<bool (int)> const&, std::__1::mersenne_twister_engine<unsigned int, 32ull, 624ull,
 397ull, 31ull,<PHONE_NUMBER>u, 11ull,<PHONE_NUMBER>u, 7ull,<PHONE_NUMBER>u, 15ull,<PHONE_NUMBER>u, 18ull, 18124
33253u>&, int))
>>> referenced 229 more times

ld.lld: error: undefined symbol: WaitOnAddress
>>> referenced by CMakeFiles/compress_weights.dir/compress_weights.cc.obj:(hwy::BlockUntilDifferent(
unsigned int, std::__1::atomic<unsigned int>&))
>>> referenced by libgemma.a(gemma.cc.obj):(hwy::BlockUntilDifferent(unsigned int, std::__1::atomic<
unsigned int>&))
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
[81/81] Linking CXX executable gemma.exe
FAILED: gemma.exe
C:\WINDOWS\system32\cmd.exe /C "cd . && C:\msys64\clang64\bin\clang++.exe -O3 -DNDEBUG  CMakeFiles/g
emma.dir/run.cc.obj -o gemma.exe -Wl,--out-implib,libgemma.dll.a -Wl,--major-image-version,0,--minor
-image-version,0  libgemma.a  _deps/highway-build/libhwy.a  _deps/highway-build/libhwy_contrib.a  _d
eps/highway-build/libhwy.a  _deps/sentencepiece-build/src/libsentencepiece.a  -lpthread  -lkernel32
-luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."
ld.lld: error: undefined symbol: WakeByAddressAll
>>> referenced by CMakeFiles/gemma.dir/run.cc.obj:(gcpp::Run(gcpp::LoaderArgs&, gcpp::InferenceArgs&
, gcpp::AppArgs&))
>>> referenced by CMakeFiles/gemma.dir/run.cc.obj:(hwy::ThreadPool::~ThreadPool())
>>> referenced by libgemma.a(gemma.cc.obj):(gcpp::GenerateGemma(gcpp::Gemma&, unsigned long long, un
signed long long, float, std::__1::vector<int, std::__1::allocator<int>> const&, unsigned long long,
 gcpp::KVCache&, hwy::ThreadPool&, hwy::ThreadPool&, std::__1::function<bool (int, float)> const&, s
td::__1::function<bool (int)> const&, std::__1::mersenne_twister_engine<unsigned int, 32ull, 624ull,
 397ull, 31ull,<PHONE_NUMBER>u, 11ull,<PHONE_NUMBER>u, 7ull,<PHONE_NUMBER>u, 15ull,<PHONE_NUMBER>u, 18ull, 18124
33253u>&, int))
>>> referenced 230 more times

ld.lld: error: undefined symbol: WaitOnAddress
>>> referenced by CMakeFiles/gemma.dir/run.cc.obj:(hwy::BlockUntilDifferent(unsigned int, std::__1::
atomic<unsigned int>&))
>>> referenced by libgemma.a(gemma.cc.obj):(hwy::BlockUntilDifferent(unsigned int, std::__1::atomic<
unsigned int>&))
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.

Hi, thanks for reaching out. When building on Windows, we require the Futex APIs added in Windows Server 2012 / Windows 8. You can work around this by defining HWY_DISABLE_FUTEX, then also building with C++20 enabled, or also defining HWY_FUTEX_SLEEP, but performance may be poor in the latter case. Hope this helps!

So? I should build it on linux?

Linux is also a good option, that's our main platform :)

Hi @0wwafa
Could you please confirm, if you are able to build it on linux platform?

Hi @0wwafa Could you please confirm, if you are able to build it on linux platform?

When I have time I'll check it on google colab. That's one of the best benchmark since it's a very small machine and CPU only :D

Closing for now, please reopen if there's any issue on Colab :)


Precision qualifier on shadow samplers causes crash on some Android devices

The following crash happens on Galaxy Core Prime:
02-22 11:42:36.676 21471-21487/com.diligentengine.tutorial03_texturing.Tutorial03Application A/Diligent Engine: Diligent Engine: CRITICAL ERROR in ShaderGLImpl() (ShaderGLImpl.cpp, 113): Failed to compile shader file "TexRegionRender : Pixel shader isampler2D"
    InfoLog:
    (11:0) : error : invalid type field for default precision statement
    (12:0) : error : invalid type field for default precision statement
    (33:0) : error : undefined identifier: 'Constants'
    (33:0) : error : undefined identifier: 'Constants'

The following is a potential fix to the problem:
GLSLSource.append(
    "precision highp float;\n"
    "precision highp int;\n"
    //"precision highp uint;\n"  // This line causes shader compilation error on NVidia!

    "precision highp sampler2D;\n"
    "precision highp sampler3D;\n"
    "precision highp samplerCube;\n"
-    "precision highp samplerCubeShadow;\n"
-    "precision highp sampler2DShadow;\n"
    "precision highp sampler2DArray;\n"
-    "precision highp sampler2DArrayShadow;\n"

    "precision highp isampler2D;\n"
    "precision highp isampler3D;\n"
    "precision highp isamplerCube;\n"
    "precision highp isampler2DArray;\n"

    "precision highp usampler2D;\n"
    "precision highp usampler3D;\n"
    "precision highp usamplerCube;\n"
    "precision highp usampler2DArray;\n"
);
+
+ #ifdef PLATFORM_ANDROID
+ if (IsES31OrAbove)
+ #endif
+ {
+     GLSLSource.append(
+         "precision highp samplerCubeShadow;\n"
+         "precision highp sampler2DShadow;\n"
+         "precision highp sampler2DArrayShadow;\n"
+     );
+ }

@dolphineye That looks like an actual compiler bug as ES3.0 shading language spec says the following (4.5.4):
The fragment language has no default precision qualifier for floating point types. Hence for float, floating
point vector and matrix variable declarations, either the declaration must include a precision qualifier or
the default float precision must have been previously declared. Similarly, there is no default precision
qualifier for the following sampler types in either the vertex or fragment language:
sampler3D;
samplerCubeShadow;
sampler2DShadow;
sampler2DArray;
sampler2DArrayShadow;
isampler2D;
isampler3D;
isamplerCube;
isampler2DArray;
usampler2D;
usampler3D;
usamplerCube;
usampler2DArray;

So there must be a precision qualifier for shadow samplers in ES3.0 and using it in ES3.1 only will likely cause errors on spec-compliant devices.

@dolphineye Did you have a chance to test this issue on other GLES3.0 devices?

Hi dude, I didn't have time to check yet, and since I'll be away for a couple of weeks, I'll keep in touch when I'm back ;)

👍


[SVCS-55] Stop Github uploads which cause empty commits

Purpose
When a "revision" is uploaded with no changes, waterbutler treats this like a real revision and creates an empty commit. This PR compares the new and old files to see if they are the same and skips creating a commit if they are the same.
Changes
Changes code in _fetch_content to include content is a way which is comparable to old content then compared the two and immediately returns metadata if they are the same. Edit: There's now new methods for fetching and checking git info.
Side Effects
Though I couldn't see any immediate difference I think this could could cause performance decreases, because it forces another api call.
Ticket
https://openscience.atlassian.net/browse/SVCS-55

Thanks, @Johnetordoff!  Merged as de340a7adb63d57fc94a63d3d99557a4d30bbd91.


fix docstring in _version.py

Codecov Report
Base: 89.61% // Head: 89.61% // No change to project coverage :thumbsup:

Coverage data is based on head (24d0408) compared to base (658ca32).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #373   +/-   ##
========================================
  Coverage    89.61%   89.61%
========================================
  Files           56       56
  Lines         4892     4892
========================================
  Hits          4384     4384
  Misses         508      508

Impacted Files
Coverage Δ

sentinelhub/_version.py
100.00% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Logger configuration

Currently, the logger in bilby adds handlers by default (see here). This goes against the recommend practice:

Note: It is strongly advised that you do not add any handlers other than NullHandler to your library’s loggers. This is because the configuration of handlers is the prerogative of the application developer who uses your library. The application developer knows their target audience and what handlers are most appropriate for their application: if you add handlers ‘under the hood’, you might well interfere with their ability to carry out unit tests and deliver logs which suit their requirements.

I think we should consider changing this, what do people think?

As a developer of a downstream pipeline, it would be handy for this to be the case. Currently, to get around it, I have my own logging functions hijack the bilby/bilby_pipe loggers.


Not possible to send files

Goofy doesn't send files neither via the button on the main window nor by dragging & dropping.

Yeah I am wondering what the problem here is, but I can reproduce it, too. I hope I'll find the issue. Any help is highly appreciated /cc @peterjosling

Hi, I cannot send any files through Goofy. It is a really important feature, because I have to open f****** facebook website every time i want to send files :/

I have just found out that it is www.messenger.com problem. I get the same error trying send files there.

I think not... I can send files through messenger.com and not with Goofy

Merge with #90 ?

having the same issue

@andremiguelaa Yep same issue as #90, have created a pull request to fix it too so hopefully fixed soon :)

@jklp Great news ;)

@jklp Great news!


Initial changes to OCP 4.12 and update GI versions

Bringing in changes attempted on the now deprecated repo to the new repo.
@vsnyc Was there an email sent about the new repo and is there a way I can be added to whichever board/location announcements and fyis are made? This caught me blind sided and I had no idea about this.
Thanks.

@bkukoyi - Sorry for the inconvenience and thanks for the PR on this repo. This was a wide move spanning all the Partner Solutions, but largely an internal one as this should have limited impact on customers. We have kept the old repo publicly available as well as the content in old aws-quickstart S3 buckets, and will keep them there to ensure continuity.

/do-e2e-tests

/do-e2e-tests


Use int_sqrt

Issue
Spec now uses int_sqrt instead of floating point sqrt and then an integer cast.
Proposed Implementation

implement int_sqrt in helpers

def int_sqrt(n):
    x = n
    y = (x + 1) // 2
    while y < x:
        x = y
        y = (x + n // x) // 2
    return x

replace usage of int(sqrt()) in rewards calculations with int_sqrt

taking care of this

Linking to the two relevant PRs in the spec repo
https://github.com/ethereum/eth2.0-specs/pull/13
https://github.com/ethereum/eth2.0-specs/pull/14


Disable kubernetes upgrades on embedded cluster

https://github.com/rancher/rancher/issues/29412
This PR stops the k3s portion of provisioner from setting the K3sConfig and Driver type on an embedded cluster.  UI shown below. Upgrading the cluster is then not possible in the API as k3sConfig is gone.
"driver": "k3s" -> "driver": "local".
Local gets set directly off embedded here: https://github.com/rancher/rancher/blob/master/pkg/data/dashboard/cluster_data.go#L40-L42
Potential caveats: Is it bad for the cluster not to be labeled as k3s ? As far as I can tell that just stops some validating logic around upgrade version, and stops k3s-upgrade-controller, which is what we want. The version on an embedded cluster should never be upgraded.

If the driver shows local maybe the UI can say something different than imported?

Is it bad for the cluster not to be labeled as k3s ?

@cbron I'm not entirely sure, but I've seen monitoring v2 has some additional logic for k3s clusters. So if the local cluster is not detected as k3s, we might miss out on that? cc @aiyengar2

@cbron I think the safer route is to set the driver but leave the k3s config as nil. If you check the upgrade code it will skip if the k3s config under spec is nil. https://github.com/rancher/rancher/blob/master/pkg/controllers/management/k3sbasedupgrade/k3sbased_upgrade_handler.go#L52

I went Dan's route and that seems to work the same way. UI/API still can't upgrade, and that should solve the potential monitoring issues as not its labeled as K3s driver. Had to move around some conditionals to make it work. Only downside is that other features might not be able to tell if its embedded or not, but they could check to see if config is nil, and this whole area will be deprecated in the end anyway. I'll talk to Wes about "imported" phrase in UI but that would be fixed separately.


Fix "Uncaught TypeError: Cannot set property 'opacity' of undefined"

Resolves #14

cc @abehaskins


fix(registry): Emit npm-session header

Partially fixes https://github.com/npm/npm/issues/16889

Hey! Thanks a bunch for this! 🎉


Find free cloud hosting for Golang

https://www.reddit.com/r/golang/comments/ama7jb/any_free_cloud_hosting_for_golang

Heroku + Deploy to Heroku GitHub action?


SE Fault Tolerance follow up

Environment Details

Helidon Version: 2.x
Helidon SE

Follow up tasks:

[ ] Configure defaults from config for each FT handler (currently only executor service configured)
[x] Add SE documentation for Fault Tolerance
[ ] Wrap executor services with context (if explicitly configured)
[ ] Use named handlers (as is done with Bulkhead) to allow nicer debugging, logs and metrics
[ ] Add support for metrics

@tomas-langer Other than docs (in progress), do you see any of the other items in this checklist as must haves for 2.1.0? If so, could you elaborate more on those?


fix: tristate toggle logic for tab visibilty

This removes the "toggle live" option for tab visibilty options, including the hotkey. so this tries to remove the hotkey if it hasn't been touched by the user
This changes the tab visibilty options in the menu from "toggle" & "toggle live" to "show all", "show live only", and "hide all" in a submenu
This removes all tab visibility options for the emote popup
For previous context, see https://github.com/Chatterino/chatterino2/pull/5353
The existing toggle option will reset the live only filter, and switch between "hide all" and "show all"
Fixes #5341

It would probably be good to know if the removed hotkey was used.

Anecdotally, I've only heard of people using the removed hotkey accidentally and wondering why some of their tabs are missing


raidemulator: Convert CombatantState to typescript

Looks like I was able to pull this conversion to its own PR after all.
PR 3 of 4 for #2936, I guess. Once the last PR is open, I'll close the old PR.

Whoops, made those changes on the wrong branch...

Looks like this has a conflict, but I don't have any other comments.  Can you resolve that and then I'll merge this?


Why the GPLv2 license instead of the MIT?

I would like to make use of Typey in a CSS framework using NPM. While the framework does not modify Typey, I cannot include a minified version *.css because of license restrictions (the CSS framework is MIT licensed while Typey is GPLv2).
Is there a particular reason you chose the GPLv2 license for Typey?

Sorry, been awhile. I can change it to MIT if you would prefer? Honestly doesn't bother me, and MIT looks like the better choice as you've mentioned.

Hi @jptaranto
MIT would be preferable as then I can also change my framework back to MIT.

Hey @pryley I have just released 1.1.2 which uses the MIT license now.


I would like to ask, is there any preparation to support forge1.18?

I would like to ask, is there any preparation to support forge1.18?

The guy who did Forge ports of my mods in the past is busy with his own projects now. As I'm primarily making mods for myself, I have no reason to make a Forge version. Anyone who wants to do it is free to do so though.


[Question/feature request] Where is configuratoin stored now?

I lost this note in the 6.1.3 release note https://dbeaver.io/2019/07/31/dbeaver-6-1-3/
New project configuration format was implemented. Main advantages:
Which direcotories should i now backup to save my DBeaver configuration?
$HOME/.local/share/.DBeaverData/workspace6/ is full of stuff i do not need to backup (logs, locks, plugins, ...)
old dir $HOME/.dbeaver4/ seams ot be dead and gone, correct?
Could you please save logs, locks ands stuff in one dir, which again i do not need to backup, and real config files that help me bootstrap a new dbeaver install from scratch with no pain (logins, credentials, shortcuts, windows/tabs positions, ...) in one dir, which basically will be the only dir i will need to backup? Pretty please... :-)

well, old .dbeaver4 did contain logs as well...

well, old .dbeaver4 did contain logs as well...

https://github.com/dbeaver/dbeaver/wiki/Workspace-Location

https://github.com/dbeaver/dbeaver/wiki/Workspace-Location
$XDG_DATA_HOME is not a standard defined env variable (Ubuntu Mate 18.04)

well, old .dbeaver4 did contain logs as well...
Yes, correct. Which means, i backup useless stuff in order to have a working backup.
Putting logs in one path/subdir, and just configuration in another, will allow me not to backup log files, which i don't need i case i have to restore my machine/installation.
PLUS, those file tend to be very big in size; i would like ot have a "single" and "safe" plain i could tell logrotate or whatever script to cleanup/rotate/delete/whatsoever

:-)

Wish this was configured in the UI.

@wiwwo It is ~/.local/share if XDG_DATA_HOME not set (just fixed the wiki page, thanks for noticing)
@snakyjake1 You can change default location by passing -data path command line parameter (or add it in dbeaver.ini file)

Regarding original question:
Workspace contains all the stuff (including working files). You can skip metadata folder if you don't need it. Also all dbeaver configs may be placed in different projects. Eg. you may have one local project + several shared projects (cloned from Git). All projects reside in workspace folder. Default project name if General.
So if you don't use multiple projects you can backup just folder workspace6/General.

Workspace contains all the stuff (including working files). You can skip .metadata folder if you don't need it.

Tested the shortcut config is stored in the file:
DBeaverData/workspace6/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
...


how to avoid handling a deep link twice on cordova android application?

Hi,
I am facing an issue with regards to branch io deep linking.
Environment: I am using
Android Marshmallow SDK, platform: 25
Cordova 7.0.1 and
Branch SDK
"io.branch.sdk": "~2.2.3"
"branch-cordova-sdk": "^2.2.5",
Below are the scenarions in which im facing issue:
Scenario 1: Calling  Branch.InitSession in OnResume call back function.
Failed case:
Steps:

Installed the app for the first time. (Did not open the app)
clicked on Branch IO Deep Link,
It opens up the app on my phone, but does not redirect to the url that is specified in the parameters of the Deep Link, as the InitSession is being called twice.
a) In the OnDeviceReady call back function.
b) In the OnResume Function ( This is because, since my app is opening for the first time, it request the user for   	   permission, which pauses the application and resumes when user deny's/ approves the permission calling the 	   onresume method).
Second time when the InitSession is invoked from OnResume call back it recives empty parameters from Deep Link and the application does not redirect to the URL as expected.

Scenario 2: If i remove the Branch.InitSession in OnResume call back fucntion.
Success case: The above scenario works well, if remove the InitSession in OnResume function
Failed case:

Installed the app.
Opened the app and let the app be in the background.
Clicked on a Branch IO deep link.
The application does not recieve the deep link data or the parameters to process the information, since the initsession is not avaible in the onresume method.

Can you please let me know how to handle such a scenario, let me know if i need to publish any further information which might help you in finding if i am implementing it in wrong way.
Thanks & Regards,
Jyothi.

Hello,
It looks like you have 2 versions of Branch installed:
"io.branch.sdk": "~2.2.3"
"branch-cordova-sdk": "^2.2.5",

io.branch.sdk is our outdated Branch SDK which is no longer supported. I would recommend following this guide to make sure you are only running one version of the Branch SDK. I would also recommend following the integration guide on this Github's readme.

Thank you for the response. I really appreciate that.
We were using io.branch.sdk earlier, but currently we are using "branch-cordova-sdk": "^2.2.5".
As suggested, i have ensured removing the older version of io.branch.sdk and tried with<EMAIL_ADDRESS>But still i am facing the same issue in the scenario's(scenario1 and 2) that i have shared in my post.
This is how i am added branch SDK:
cordova plugin add<EMAIL_ADDRESS>--variable BRANCH_KEY=key_live_XXXXXXXX --variable URI_SCHEME=xxxx
Also, I tried with the latest version of branch sdk version 2.6.0 and modified the  in config.xml

<branch-config>
    <branch-key value="key_live_xxxxxxxxxxxx" />
    <uri-scheme value="xxxxx" />
    <link-domain value="xxxxx.app.link" />
    <android-prefix value="/U09p" />
</branch-config>

But cordova build android is throwing an error:
Error: BRANCH SDK: Invalid "id" or "ios-CFBundleIdentifier" in  in your config.xml. Docs https://goo.gl/GijGKP.
Please let me know if i have missed anything.

Hello hello,
Unfortunately, Branch no longer supports installing the SDK from the CLI:

I have modified the config.xml to add the latest sdk.

Hello hello,
Unfortunately, Branch no longer supports installing the SDK from the CLI:
cordova plugin add<EMAIL_ADDRESS>--variable BRANCH_KEY=key_live_XXXXXXXX --variable URI_SCHEME=xxxx

This is a remnant of our old our SDK (io.branch.sdk) which we had to deprecate. The Branch SDK now installs from your config.xml (we had to do this to support all the flavors of Cordova including Ionic Cloud and PhoneGap Build).

The error you are receiving is because Android does not accept hyphens and iOS does not accept underscores as a bundle id (also known as a package name or widget id). This is a restriction of the devices.
If you are reliant on a hyphen or underscore, then you will need to update your config.xml to include something like this:
<widget ios-CFBundleIdentifier="com.eneff.branch.cordovatestbedios" android-packageName="com.eneff.branch.cordovatestbedandroid" version="1.0.0" xmlns="http://www.w3.org/ns/widgets" xmlns:cdv="http://cordova.apache.org/ns/1.0">

https://github.com/BranchMetrics/cordova-ionic-phonegap-branch-deep-linking#testing-optional-app-config
Thanks,

Hi ethan,
Thanks for your response,
As you said before i installed Branch SDK from my config.xml.(
),and also i updated my config.xml to include this  .
but still iam facing two Scenario's which i asked before.
Below are the scenarions in which im facing issue:
Scenario 1: Calling Branch.InitSession in OnResume call back function.
Failed case:
Steps:
Installed the app for the first time. (Did not open the app)
clicked on Branch IO Deep Link,
It opens up the app on my phone, but does not redirect to the url that is specified in the parameters of the Deep Link, as the InitSession is being called twice.
a) In the OnDeviceReady call back function.
b) In the OnResume Function ( This is because, since my app is opening for the first time, it request the user for permission, which pauses the application and resumes when user deny's/ approves the permission calling the onresume method).
Second time when the InitSession is invoked from OnResume call back it recives empty parameters from Deep Link and the application does not redirect to the URL as expected.
Scenario 2: If i remove the Branch.InitSession in OnResume call back fucntion.
Success case: The above scenario works well, if remove the InitSession in OnResume function
Failed case:
Installed the app.
Opened the app and let the app be in the background.
Clicked on a Branch IO deep link.
The application does not recieve the deep link data or the parameters to process the information, since the initsession is not avaible in the onresume method.
Can you please let me know how to handle such a scenario, let me know if i need to publish any further information which might help you in finding if i am implementing it in wrong way.
Thanks & Regards,
Jyothi.

Hello,
Thank you for bringing this to my attention. Yes, the branch.initSession() will be called whenever you ask for device access permission because this functionality is handled on the device level and not the app (which triggers the app delegates again where the branch.initSession() resides at).
Whenever your branch.initSession() gets called twice, does data come back empty both times after a Branch deep link click? If not, you can do something like the following so you will not see the branch.initSession() called twice or come back empty:
Branch.initSession(function(data) {
  if (data['+clicked_branch_link']) {
    // read deep link data on click
    alert('Deep Link Data: ' + JSON.stringify(data));
  }
});

Let me know if this fixes your issues and I'll update the readme guide.
Thanks,


invoice_paid_event: Verify invoice before activating fixed-price plan.

Earlier, we were not verifying that the invoice which got paid is for the fixed-price plan.
That could result in a bug where another support invoice with collection_method = "send_invoice" got paid while a fixed-price plam is already configured. The fixed-price plan would be falsely activated.
This PR is to verifiy the invoice before activating the fixed-price plan.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

I think we should be able to do this without regenerating every Stripe fixture, and that's well worth doing.

(zulip-py3-venv) vagrant@1d875425cadd:/srv/zulip$ ./tools/test-backend corporate/tests/test_stripe.TestRemoteRealmBillingFlow.test_upgrade_user_to_fixed_price_plan_pay_by_invoice corporate/tests/test_stripe.TestRemoteServerBillingFlow.test_upgrade_server_to_fixed_price_plan_pay_by_invoice --generate-stripe-fixtures
-- Running tests in serial mode.
Found 2 test(s).
Destroying test database for alias 'default'...
Using existing clone for alias 'default'...
Running corporate.tests.test_stripe.TestRemoteRealmBillingFlow.test_upgrade_user_to_fixed_price_plan_pay_by_invoice
Running corporate.tests.test_stripe.TestRemoteServerBillingFlow.test_upgrade_server_to_fixed_price_plan_pay_by_invoice

----------------------------------------------------------------------
Ran 2 tests in 3.208s

OK
Destroying test database for alias 'default'...

Okay, we don't need any change in fixtures here.

Merged, thanks @prakhar1144!


Error running reports

I've downloaded and extracted SQLNexus_<IP_ADDRESS>.  I used the PowerShell script SetupSQLNexusPrereq.ps1 to check and install the prerequisites.  When I run SQLDiag on the database host with both ProfilerCollector enabled="true" and ProfilerCollector enabled="false", import the files (import is successful with no errors), trying to use report SQL Perf Main / Perfmon Summary I get an error about a missing database object.  When I inspect the database sure enough, it's not there.  I'm just wondering if I missed a step with the set-up or is this a bug?  I can't seem to find too many hits about "Invalid object name 'dbo.tbl_ServerProperties'".  In the following error stack after tbl_ServerProperties it mentions ... A data source instance has not been supplied for the data source DataSet_CPU.  The default database sqlnexus was created and I can see a lot of other objects, any help much appreciated.
SQL Nexus - Report Issues.docx
Thanks
Michael

Hello @micky3102. Thanks for your interest in SQL Nexus. The problem you describe points to a missing table: dbo.tbl_ServerProperties as you pointed out. And the logs for that table are gathered if you use SQL LogScout https://github.com/microsoft/SQL_LogScout/releases/tag/v<IP_ADDRESS> (using Basic and many other scenarios) or PSSDIAG (which calls SQLDiag is not in active development but still used). The idea is that SQL Nexus needs this table at a minimum as a reference to many reports.
The needed data comes from the --ServerProperty-- rowset
In SQL_LogScout this is the file
https://github.com/microsoft/SQL_LogScout/blob/ac483ee181d2840f4f84917140dabc3b53dd0552/SQL LogScout/Bin/MiscDiagInfo.sql#L145
In PSSDIAG this is the file
https://github.com/microsoft/DiagManager/blob/21f07c4a1c6936b9211352d3653086c3ee5a3c28/DiagManager/CustomDiagnostics/SQL Base/MiscPssdiagInfo.sql#L131
Bottom line, you need the output that will be imported in that table.
So best option is to collect the logs on your SQL host by using SQL LogScout and then the tbl_ServerProperties table will be created for you. If you need performance logs gathered (Xevent in this case), you can use either the GeneralPerf or DetailedPerf scenario. There's a LightPerf scenario also, but it doesn't gather Xevent. Sorry long answer, hope it helps.


USNG layer not loading as a feature service, but worked as a basemap?

Logging on behalf of<EMAIL_ADDRESS>This is the service in question...
http://napsg.maps.arcgis.com/home/item.html?id=dc352c5f18854d82b32bce92c0b6656b
http://maps1.arcgisonline.com/ArcGIS/rest/services/NGA_US_National_Grid/MapServer
Can someone test this to confirm? We are in the middle of an exercise but wanted to log it before we forget.

Bill,   For you to use it as a Feature Layer you would have to specify a specific sublayer (i.e. http://maps1.arcgisonline.com/ArcGIS/rest/services/NGA_US_National_Grid/MapServer/1). I think you need to add it as a dynamic layer so that you can use http://maps1.arcgisonline.com/ArcGIS/rest/services/NGA_US_National_Grid/MapServer and load all the layers. I tested it as a dynamic layer and it work fine. Robert

I will check with Bill ASAP
Sent from my iPhone

On Jul 23, 2015, at 09:05, Robert J Scheitlin<EMAIL_ADDRESS>wrote:
Bill, For you to use it as a Feature Layer you would have to specify a specific sublayer (i.e. http://maps1.arcgisonline.com/ArcGIS/rest/services/NGA_US_National_Grid/MapServer/1). I think you need to add it as a dynamic layer so that you can use http://maps1.arcgisonline.com/ArcGIS/rest/services/NGA_US_National_Grid/MapServer and load all the layers. I tested it as a dynamic layer and it work fine. Robert
—
Reply to this email directly or view it on GitHub.

Hi Robert, I tried it again and it loaded right up for me.  I've got no idea what the issue was yesterday, the only way I could get it to load was by adding it as a base map layer.  Maybe all I needed was restart....my computer and my day.


DISM exited with code 5

Hey, tried to deploy with the tool and got this error message.
As reference, I'm using the 1809 ARM version updated in March.

Here's the error code screenshot

Here's the Log file
Log-20190313.txt

Problems with .WIM files aren't a problem with WOA Deployer itself. Please, regenerate your .iso (wim) again. Maybe it's because of file corruption.


Local installation: Ai renders but won't show in Blender

Describe the bug
Blender will not show the resault image
Blender's system console is not helping much too
To reproduce
Rendering scene with Local Backend (Automatic1111 before Oct 21)
will resault in image beeing processed as expected
(shows progress in webUI console and can find the image in webUI output folder)
Error log
AI Render Error:  Couldn't load the image from Stable Diffusion
Environment

Blender version 3.3.0
AI Render version 0.3.3
Operating system Windows 10
WebUI running on Anaconda Environment

Screenshots/video
No response
Additional information
No response

If it's not working with Automatic1111, it's probably because it's not the right version of it. I've added more to the instructions, and now included a section about how to get it to the right commit version. Try this: https://github.com/benrugg/AI-Render/wiki/Local-Installation

I just made a new release that should work much more reliably with Automatic1111 going forward. You'll need to follow slightly updated instructions (the key difference being that you will now enable API mode): https://github.com/benrugg/AI-Render/wiki/Local-Installation

Fixed in 433637e39bfd10fb39ed1489e1bf4266d75c2067


ssh plugin should allow for a timeout option

There should be a default timeout of 60 seconds, and you should be able to provide a custom value:
timeout: 10

ah yes, like a TCP timeout in case the server is down?

Yeah, there might be a timeout option in the native go ssh binding?

yep, instead of using ssh.Dial we'll have to manually construct the ssh connection. There is an example SSHDialTimeout function here that we can use:
http://stackoverflow.com/questions/31554196/ssh-connection-timeout

let's move this issue to the ssh plugin repository at https://github.com/drone-plugins/drone-ssh

Should be solved via https://github.com/drone-plugins/drone-ssh/pull/8/commits/f3b01e70fe560b6a827f74521f67fde520f0abf8 on 0.5


docs(gcp): management cluster install/upgrade instruction for KF 1.2

/assign @joeliedtke @chensun @subodh101
for review

Many problems raised in this PR have been fixed in https://github.com/kubeflow/website/pull/2372, so I'd suggest directly taking a look at preview page on #2372 instead for review.


File opened from integrated Terminal is not listed in Recent Files

Issue Type: Bug
I commonly use the integrated terminal to open files that I use regularly. I have a couple of scripts that I use to help with this.

go - Navigates to a predefined location
ffind - Dumps a list of all files in the current location matching a search string

I then CTRL+Click on the located file to open it. This works great. However for some reason if I then close and reopen VsCode the file I opened via the Terminal is never displayed in Recent Files.
https://user-images.githubusercontent.com/18445931/159664123-1531115b-e2d4-4e0f-bf99-76714f3565b1.mp4
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.86GB (4.96GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (41)

Extension
Author (truncated)
Version

Bookmarks
ale
13.2.4

rtf
ale
2.5.0

ng-template
Ang
13.3.0

armview
ben
0.4.6

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.3.0

remotehub
Git
0.26.0

vscode-journal-view
Gru
0.0.26

vscode-jasmine-test-adapter
hbe
1.7.3

vscode-test-explorer
hbe
2.21.1

vscode-nuget-package-manager
jmr
1.1.6

vscode-jest-test-adapter
kav
0.8.1

azure-pipelines
ms-
1.202.0

vscode-azureappservice
ms-
0.23.1

vscode-azurefunctions
ms-
1.6.0

vscode-azureresourcegroups
ms-
0.4.0

vscode-azurestorage
ms-
0.13.0

vscode-azurevirtualmachines
ms-
0.5.0

vscode-bicep
ms-
0.4.1318

vscode-cosmosdb
ms-
0.18.1

vscode-docker
ms-
1.21.0

csharp
ms-
1.24.1

vscode-dotnet-runtime
ms-
1.5.0

remote-containers
ms-
0.224.3

remote-ssh
ms-
0.76.1

remote-ssh-edit
ms-
0.76.1

remote-wsl
ms-
0.64.2

vscode-remote-extensionpack
ms-
0.21.0

azure-account
ms-
0.10.1

azurecli
ms-
0.5.0

live-server
ms-
0.2.12

test-adapter-converter
ms-
0.1.5

vscode-node-azure-pack
ms-
0.2.1

azurerm-vscode-tools
msa
0.15.6

vscode-journal
paj
0.11.2

vscode-xml
red
0.19.1

rewrap
stk
1.16.3

indent-one-space
use
0.2.8

vscode-todo-highlight
way
1.0.5

markdown-all-in-one
yzh
3.4.0

html-css-class-completion
Zig
1.20.0

To clarify: you mean the list of recently opened files in File > Open Recent? That location is limited to only a few interactions such as opening from a native file dialog or drag and drop or from the command line externally.

It seems that's the way it is, but it shouldn't be. The defining characteristic of an entry in the Recently Opened list, should be that it was opened recently. Not that it was opened recently in a specific manner. From a UX perspective that just makes no sense.

"That list will see an entry for every editor you open, independent how."
The problem is that this statement isn't correct. If I understand correctly the workspace editor picker only shows editors opened as part of a workspace, and only in the current session.
That leaves two entire classes of files that can be opened which the editor then provides no way whatsoever to open them again. Namely files that were not opened as part of a workspace, and files that were not opened in the current session.
What you have to keep in mind is that people use VsCode not only as an IDE, but also as a basic editor. So opening a file, not as part of a workspace, then closing the editor, and then wanting to reopen the same file at a later time is a very common use case.
The Recent Files list only showing files that were opened in specific ways just makes it so inconsistent as to be useless. If I want to open a file I last opened 3 days ago I will likely not even remember how I opened it, in which case I won't know whether it will show up in the Recent Files list or not. In which case I might as well not bother using Recent Files and instead just start looking through Fire Explorer to start with, which is what I usually do. But every now and again I try to use the Recent Files list and then I rediscover why I don't usually bother with it.

Can you make a suggestion how "File > Open Recent" should be populated then? Would you add an entry for any editor that opens independent how, even you just click through files in the VSCode file explorer?


extend password_hashes test case to allow sssd

What would you like to be added:
The tests/helper/tests/password_hashes test looks for a line  in /etc/pam.d/common-password that contains "[success=1 default=ignore]".
Then 2 checks happen:

only one line allowed containing *"[success=1 default=ignore]"
yescrypt or sha512 must also be defined in that line

By a default non-modified make metal build , the /etc/pam.d/common-password file looks like:
password        [success=1 default=ignore]      pam_unix.so obscure yescrypt
# here's the fallback if no module succeeds
password        requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password        required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config

Installing sssd changes the /etc/pam.d/common-password file to:
password        [success=2 default=ignore]      pam_unix.so obscure use_authtok try_first_pass yescrypt
password        sufficient                      pam_sss.so use_authtok
# here's the fallback if no module succeeds
password        requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password        required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config

Why is this needed:
If a user decides to use sssd, the test should not fail if the required modules are configured.

tl;dr: What does sssd change in terms of Password modules? Adds use_authtok and  try_first_pass, and another fallback module named pam_sss.so.
Long:
If sssd is installed, the /etc/pam.d/common-password looks like this:
password        [success=2 default=ignore]      pam_unix.so obscure use_authtok try_first_pass yescrypt
password        sufficient                      pam_sss.so use_authtok
# here's the fallback if no module succeeds
password        requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password        required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config

sssd tries to add use_authtok and  try_first_pass modules to the first line. I assume this should be no problem.
The matching config in /usr/share/pam-configs/ for the pam_unix.so module should be /usr/share/pam-configs/unix.
This /usr/share/pam-configs/unix exists independently of sssd, it is not changed by sssd:
cat /usr/share/pam-configs/unix
Name: Unix authentication
Default: yes
Priority: 256
Auth-Type: Primary
Auth:
        [success=end default=ignore]    pam_unix.so nullok try_first_pass
Auth-Initial:
        [success=end default=ignore]    pam_unix.so nullok
Account-Type: Primary
Account:
        [success=end new_authtok_reqd=done default=ignore]      pam_unix.so
Account-Initial:
        [success=end new_authtok_reqd=done default=ignore]      pam_unix.so
Session-Type: Additional
Session:
        required        pam_unix.so
Session-Initial:
        required        pam_unix.so
Password-Type: Primary
Password:
        [success=end default=ignore]    pam_unix.so obscure use_authtok try_first_pass yescrypt
Password-Initial:
        [success=end default=ignore]    pam_unix.so obscure yescrypt


downgrade webex

Downgrade webex to exact-version 2.4.2 due to reported issues with the Framework.

@jpjpjp - for your review and approval

LGTM.   One question.  How did you determine that 2.4.2 was the right version?   Are you certain that this version supports the fedramp option that you added into the framework recently?   Assuming so this is approved (if I can figure out how to approve on mobile!$

2.4.2 fixes the Logger Proxy issue.
1.156 is where FedRamp support was introduced.

@jeremywillans thanks for checking that.   I updated the version number in version-history.mc.   I think this is good to commit!


fix(aws): Extend opensearch_service_domains_use_cognito_authentication_for_kibana with SAML

Context
The check opensearch_service_domains_use_cognito_authentication_for_kibana fails if Amazon OpenSearch has Amazon Cognito authentication for Kibana not enabled. However, besides Cognito, AWS recommends to use SAML authentication for Kibana which means that Cognito must be disabled. Since the opensearch_service_domains_use_cognito_authentication_for_kibana does not test whether either Cognito or SAML is enabled, it will fail when SAML is enabled.
Description
Therefore, I renamed the check opensearch_service_domains_use_cognito_authentication_for_kibana to opensearch_service_domains_use_cognito_or_saml_authentication_for_kibana and extended it in a way that it tests whether either Cognito or SAML is enabled for Kibana on AWS OpenSearch. If either is enabled, opensearch_service_domains_use_cognito_or_saml_authentication_for_kibana will pass.
That's by the way also what the corresponding prowler v2 check check_extra780 did at its time. See its corresponding pull request that had been merged into main at that time. It's a pity that this change hadn't been migrated neither to prowler v3 nor to v4.
Since my company has not yet migrated from prowler v3 to v4, I'm opening this PR for v3 first. Do you want me to open a PR also for prowler v4?
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @kagahd, thanks for your contribution!
We'll review the PR as soon as possible but some things to consider:

We cannot rename the check since it'll introduce a breaking change in the outputs and unique ids.
If you can open this PR too to v4 it'd be great.
We have to include more tests cases to handle this new behaviour, I can help you with that.

Hi @jfagoagas , thanks for your fast reply.
Ok, I rename the check to its former name but then its title would be a bit misleading. Is this ok?
Great to have your help for adding more unit tests!

Hi @jfagoagas , thanks for your fast reply. Ok, I rename the check to its former name but then its title would be a bit misleading. Is this ok? Great to have your help for adding more unit tests!

The title and description can be kept as you did.

I already renamed back the check to its original name before I installed pre-commit? Do I need to commit and push again to let pre-commit kick in?

I already renamed back the check to its original name before I installed pre-commit? Do I need to commit and push again to let pre-commit kick in?

I've just made some changes for you to review it but I need push access to your forked branch, could you give me access?

I've just made some changes for you to review it but I need push access to your forked branch, could you give me access?

I added you.
I also added unit tests. I hope we were not cross-working.


Exclude 'type' from common field names

Reasoning -- as discussed in the API Guild meeting:

its purpose is to be a discriminator for polymorphic types
not needed anymore since discriminators are supported by OpenAPI 3.x -- see https://swagger.io/docs/specification/data-models/inheritance-and-polymorphism/
current definition and documentation is poor

:+1:

:+1:


operator couchbase-enterprise-certified (2.5.2-1)

Added label to skip check_operator_name test as well as entry in config.yaml to apply skip automatically.


Export the variables if no command is given

Would you be open to exporting the variables for use after running the cli?
My use-case is, In package.json scripts, I would like to reference the variables in the .env file.
Ideally, dotenv echo $VAR_NAME would work, but $VAR_NAME is evaluated too early so I have to do something like echo $(dotenv -p $VAR_NAME) which is very verbose.
I was thinking we could support dotenv; echo $VAR_NAME or maybe a new flag if you'd prefer?

@RamIdeas this is simply not possible because it's not dotenv-cli who evaluates too early but your shell before even passing this value to dotenv-cli, see also https://github.com/entropitor/dotenv-cli/issues/31#issuecomment-599196485 for more information

I feel like I didn't explain myself clearly enough. I'm await it's the shell that evaluates early.
My recommendation is to export the vars if no command is given. Notice the semicolon in the example on last line?

Ah okay, that makes more sense.
However, I don't think dotenv can change the env values of the outer shell script, that seems like it would be dangerous security wise?
$ URL=example.com
$ bash -c 'echo $URL' # doesn't output google.com because wasn't exported
$ export URL=example.com
$ bash -c 'echo $URL' # does output goolge.com because it was exported
$ bash -c 'export URL=google.com'
$ echo $URL      # doesn't have google.com because child doesn't export to parent

I'd be happy to implement something if you can prove me wrong. I'd probably put it behind a feature flag then but for the rest it should be fine. I'm just not sure if it can be done.


System-tests: brokered: test address types

create brokered address space A
create queue A
create topic A and expect 'already exists' error
verify that can send/recv from A
create topic B
create 2 subscribers for B and receive 1000 messages each
create 1 producer for B and publish 600 messages and close
create 1 producer for B and publish 400 messages and close

done as part of: https://github.com/EnMasseProject/enmasse/pull/370


perf(docs): add custom registration example

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Summary:
Add missing custom registration example to index doc
Type of change:
Please delete options that are not relevant.

[ ] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[x] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 2.9.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Provide status of ZTF

It would be helpful if the page 'Lasair Ingestion Status' either showed the current status of ZTF or else have a link to a ZFT status page. I wondered why my filter had stopped working and from the size of the logfiles on the ZTF site and the lack of transients ingested into Lasair it appears the telescope is not working at present.
Users following up the alerts automatically woulf probably like to know that the status so they can redirect their follow up activities to other work.

You can look at the weather situation at Palomar
https://www.wunderground.com/forecast/us/ca/palomar-mountain.
You can look at the ZTF data monitor
https://monitor.alerts.ztf.uw.edu/ (username=ztf, password=fullofstars)

You can look at the weather situation at Palomar
https://www.wunderground.com/forecast/us/ca/palomar-mountain.
You can look at the ZTF data monitor
https://monitor.alerts.ztf.uw.edu/ (username=ztf, password=fullofstars)

Hello,
Unfortunately those links do not really explain why the telescope is
not operating at present - the page at
https://ztf.uw.edu/alerts/public/ shows it stopped operating on
20120120 when there was a very small alerts file - the 74 (Byte ?)
files appear to be blank.
I have had a search and can't find a current status page on the ZTF
site or in any of the other event brokers.
It's quite frustrating not knowing and from the point of view of the
event broker operators presumably if it is going to be offline for some
time it is a good oppertunity for housekeeping or upgrades.
Regards
John
On Fri, 2021-01-29 at 01:03 -0800, Roy Williams wrote:

You can look at the weather situation at Palomar
https://www.wunderground.com/forecast/us/ca/palomar-mountain.
You can look at the ZTF data monitor
https://monitor.alerts.ztf.uw.edu/ (username=ztf,
password=fullofstars)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "
https://github.com/lsst-uk/lasair/issues/224#issuecomment-769675358",
"url": "
https://github.com/lsst-uk/lasair/issues/224#issuecomment-769675358",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

Hello,
Unfortunately those links do not really explain why the telescope is
not operating at present - the page at
https://ztf.uw.edu/alerts/public/ shows it stopped operating on
20120120 when there was a very small alerts file - the 74 (Byte ?)
files appear to be blank.
I have had a search and can't find a current status page on the ZTF
site or in any of the other event brokers.
It's quite frustrating not knowing and from the point of view of the
event broker operators presumably if it is going to be offline for some
time it is a good oppertunity for housekeeping or upgrades.
Regards
John
On Fri, 2021-01-29 at 01:03 -0800, Roy Williams wrote:

You can look at the weather situation at Palomar
https://www.wunderground.com/forecast/us/ca/palomar-mountain.
You can look at the ZTF data monitor
https://monitor.alerts.ztf.uw.edu/ (username=ztf,
password=fullofstars)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "
https://github.com/lsst-uk/lasair/issues/224#issuecomment-769675358",
"url": "
https://github.com/lsst-uk/lasair/issues/224#issuecomment-769675358",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


chore(resolver): reuse cached lookup of package.json files

Summary
Supporting exports field will lead us to reading way more package.json files than before, so in preparation we should try to make these caches cooperate and populate the same one.
I've also dropped escalade as it does a bunch of statSync calls - we do as well and cache them, so re-using makes sense.
Lastly, I've moved the clearing of these caches until just before running tests (instead of only before runs in watch mode) in case some resolution is different between config loading and test running

Test plan
Green CI

Codecov Report

Merging #11969 (313346a) into main (696c472) will decrease coverage by 0.07%.
The diff coverage is 59.72%.

@@            Coverage Diff             @@
##             main   #11969      +/-   ##
==========================================
- Coverage   68.76%   68.69%   -0.08%
==========================================
  Files         322      323       +1
  Lines       16621    16640      +19
  Branches     4797     4800       +3
==========================================
+ Hits        11430    11431       +1
- Misses       5158     5176      +18
  Partials       33       33

Impacted Files
Coverage Δ

packages/jest-core/src/watch.ts
86.36% <ø> (-0.07%)
:arrow_down:

packages/jest-resolve/src/defaultResolver.ts
85.71% <ø> (-2.97%)
:arrow_down:

packages/jest-resolve/src/resolver.ts
55.86% <0.00%> (ø)

packages/jest-resolve/src/shouldLoadAsEsm.ts
9.30% <0.00%> (+0.60%)
:arrow_up:

packages/jest-resolve/src/fileWalkers.ts
61.76% <61.76%> (ø)

packages/jest-core/src/runJest.ts
68.75% <100.00%> (+0.32%)
:arrow_up:

Continue to review full report at Codecov.

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


TFS/AzureDevOps pull request excluded if no label

If the pull request has no label, then it will be excluded from the results. Is there a particular reason?
this line specically

Just looking at BitBucket provider it has the same issue, possible even others. Sounds like I messed up something to do with -ExcludeLabel feature, should only return null from GetPullRequestDto() if the exclude label matches. So this issue is valid and needs to be fixed in every provider affected.

Fixed in #43


MaxTrainTime exceeded and Segmentation fault in both train and test mode

Lately, I noticed Segmentation fault when calling train/test.
To see whether its a custom issue or not, I ran examples/classification_ag_news.sh, and interestingly enough, I got the following errors (of course, with the latest Starspace build using the default params as in the shell script):

after the 3rd epoch, it gives :

'MaxTrainTime exceeded.'

then it saves the model and gives:

./examples/classification_ag_news.sh: line 62:  1315 Segmentation fault      ./starspace train -trainFile "${DATADIR}"/ag_news.train
-model "${MODELDIR}"/ag_news -initRandSd 0.01 -adagrad false -ngrams 1 -lr 0.01 -epoch 5 -thread 20 -dim 10 -negSearchLimit 5 -maxN
egSamples 3 -trainMode 0 -label "label" -similarity "dot" -verbose true

Similarly, in test mode it throws Segmentation fault as well. Did anyone notice similar issues?
Thanks,
Oliver

@ben0it8 Hi Oliver, thanks for reporting. I cannot reproduce the error using the current version and the examples/classification_ag_news.sh script. Could you try make clean first and make again to see if the error persist?

@ledw Thanks, make clean worked out!


#6084 #6062 #6074 Easy form changes and Python plots not publishable

Cover:
#6084
#6062
#6074

text field is not the right width:

check box label is on wrong side:


Feature/bibliospec-maxquant-external-spectra

I'm not too happy with the duplication between BiblioSpecLiteBuilder.BuildLibrary and BuildPeptideSearchLibraryControl.BuildPeptideSearchLibrary but a better solution has not occurred to me outside of a significant refactoring of BuildPeptideSearchLibraryControl.BuildPeptideSearchLibrary.

Strange. When I build this locally, I fail ConsoleImportPeptideSearchTest with the error:
Error: ERROR: Error parsing modifications file: Failed to open input file 'C:\proj\pwiz_x64\pwiz_tools\Skyline\TestResults\Brendan 2018-11-23 13_17_11\Out\modifications.xml'.

Figured it out. Only happens in Visual Studio because modifications.xml is not included in the .testsettings file. I will fix.


Split the error type between structural and linalg errors

Recent work has made the structural constraints of sparse matrices and vectors clearer, making it clear that there can be a single enum discriminating all possible structural errors. Having linalg errors in the same error type was clumsy: structural errors happen when creating a matrix, while linalg errors happen much later, when solving systems or performing other linear algebra operations. Therefore, by splitting the types, it should be easier to react to both kinds of errors.
Since the linalg part of this crate is still small, it's expected that I'm missing possible errors, which is why the error type is a non
exhaustive enum.
Additionaly, I took this refactoring as an opportunity to fix #255, using the same pattern used by the CsMatBase and CsVecBase constructors to return the storage in case of an error.
@mulimoen I'm very interested in your remarks on the design of these new error types.

Looking at this on my phone it looks great! Will have access to my computer later this week for a proper look.
Would it be an idea to have some error-type which is an enum (SprsError) of these two for end-users? Would make migration very easy

Looking at this on my phone it looks great! Will have access to my computer later this week for a proper look.
Would it be an idea to have some error-type which is an enum (SprsError) of these two for end-users? Would make migration very easy

Would it be an idea to have some error-type which is an enum (SprsError) of these two for end-users? Would make migration very easy

I'm not sure how it would help migration. Constructors will return a StructureError, so I don't see how the user would get an enum (SprsError) of LinalgError and StructureError.
Something that could be done to ease migration, would be to have a type alias pub type SprsError = StructureError, which would mean constructors would not need much migration, but linalg functions would. But since the variants have changed, it's not a guarantee there would be no breakage.

Would it be an idea to have some error-type which is an enum (SprsError) of these two for end-users? Would make migration very easy

I'm not sure how it would help migration. Constructors will return a StructureError, so I don't see how the user would get an enum (SprsError) of LinalgError and StructureError.
Something that could be done to ease migration, would be to have a type alias pub type SprsError = StructureError, which would mean constructors would not need much migration, but linalg functions would. But since the variants have changed, it's not a guarantee there would be no breakage.

Ok I get it now, looks nice indeed, I'll add it. Thanks!

Ok I get it now, looks nice indeed, I'll add it. Thanks!

@mulimoen the SprsError type you suggested is now present.

@mulimoen the SprsError type you suggested is now present.

I had another look, and the PR seems ready to merge. Excellent work @vbarrielle, will make future error handling a breeze

I had another look, and the PR seems ready to merge. Excellent work @vbarrielle, will make future error handling a breeze


[KYUUBI#1056] Output error log when currentEngine is None

Why are the changes needed?

When createSpark in SparkSqlEngine get sparksession or execute initialize.sql failed, we cannot get any error info in logs. At this time, currentEngine is None.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[X] Run test locally before make a pull request

Codecov Report

Merging #1057 (f7d2882) into master (6509a6b) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

:exclamation: Current head f7d2882 differs from pull request most recent head 44ead3b. Consider uploading reports for the commit 44ead3b to get more accurate results

@@             Coverage Diff              @@
##             master    #1057      +/-   ##
============================================
- Coverage     78.70%   78.67%   -0.03%
  Complexity       61       61
============================================
  Files           169      169
  Lines          6249     6251       +2
  Branches        725      726       +1
============================================
  Hits           4918     4918
- Misses          907      909       +2
  Partials        424      424

Impacted Files
Coverage Δ

...rg/apache/kyuubi/engine/spark/SparkSQLEngine.scala
69.44% <0.00%> (-1.99%)
:arrow_down:

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 6509a6b...44ead3b. Read the comment docs.

@hddong  the change LGTM, is it possible to add a test ?

thanks, merged to master and v1.3.1


bug(global-ui-plugin): selected electrode not showing up in GlobalUIPlugin

During meeting, selected electrode did not show up in the GlobalUIPlugin.

9f95210e4fd77ee20206d1f4e673cf9fba79f305


[SPARK-16344][SQL] Decoding Parquet array of struct with a single field named "element"

What changes were proposed in this pull request?
Please refer to SPARK-16344 for details about this issue.
How was this patch tested?
New test case added in ParquetQuerySuite.

cc @yhuai

Test build #61611 has started for PR 14013 at commit 9620b48.

Test build #61612 has started for PR 14013 at commit c40bccb.

Test build #61611 has finished for PR 14013 at commit 9620b48.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/61611/
Test FAILed.

@rdblue Would you mind to help review this one? My initial investigation suggested that parquet-avro probably suffers the same issue. Will file a parquet-mr JIRA ticket soon.

Test build #61612 has finished for PR 14013 at commit c40bccb.

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

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

Merged build finished. Test PASSed.

@rdblue Verified that parquet-avro also suffers from this issue. Filed PARQUET-651 to track it.

Test build #61812 has started for PR 14013 at commit e44451e.

Test build #61812 has finished for PR 14013 at commit e44451e.

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

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

Merged build finished. Test PASSed.

Test build #61838 has started for PR 14013 at commit 70b2e9c.

Test build #61838 has finished for PR 14013 at commit 70b2e9c.

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/61838/
Test PASSed.

Test build #62052 has started for PR 14013 at commit b942dca.

Test build #62052 has finished for PR 14013 at commit b942dca.

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/62052/
Test PASSed.

I'm closing this one since we decided to fix this in master only.


Update itertools to 0.12.0 and added .DS_Store to gitignore

Hi!
Not sure how you want to handle version bumps - I thought that since this is a minor version bump of itertools that doesn't seem to have any breaking changes, 0.18.0  -> 0.18.1 seemed appropriate.

@someguynamedjosh any thoughts on this PR?

no problem, thanks very much!


Dependency checker

Q
A

Is bugfix?
✔

New feature?
✔

Breaks BC?
❌

Fixed issues
-

👍


Change NPC name check to nameEquals

The NPCQuery inside of the clue scroll plugin used nameContains to check which NPCs to highlight. This lead to a case where the wrong NPCs could be highlighted.
I looked over ciphers and cryptics and didn't see any clue that looked like it was relying on a partial name, so I don't believe this is a breaking change.
Fixes #2077

fixes #1985

I saw something like this, I got an easy clue which told me to talk to the tool leprechaun at draynor manor, and it highlighted the tool leprechaun at south falador farming patches when I teleported there. Is there a way to factor in location?

I made a PR to factor in location, but no one ever looked at it so I dropped it. Someone else might be able to take it over.

https://github.com/runelite/runelite/pull/2202


Add Danish translation

Thanks for providing this translation!
Can you also add an entry for yourself with (optionally) a URL or mail address in the Credits.rtf file?
I'd like to give credit to anyone who provides translations 😃

Not sure I did it the right way. But it should be there now :) #81


Simplify the fallback logic for shared_fs

This PR is a light refactoring, which moves the special case handling for SharedFd which falls back to synchronous file close if the runtime or driver is unavailable. It moves it from being implemented in Op, and available to all Ops, to within SharedFd, to make its purpose more clear.
Relates to #150 (doesn't close)

@Noah-Kennedy @FrankReh This is ready for review

Does this fix a panic? Is there a reproducer for that panic or is this help for the discussion in #150? Just trying to understand the context when looking at the diffs.

Totally unrelated to this PR. Is anyone else getting confused by the src/driver directory structure?
There is an driver/op subdirectory but its not used for defining driver operations. The driver operations get their own files under src/driver but there's also bind and  pool and util. When I saw the driver/close.rs mentioned in this PR, my mind when to "oh, the close of the driver". Actually it's the "close" operation the driver supports, having nothing to do with closing the driver.

Time to throw my hat into the ring about file descriptors.
I don't have a clear picture yet of where it will affect the model that tokio-uring creates, but soon, we should be supporting the uring direct descriptors, available since the 5.15 kernel, that can be created with the openat, openat2, or accept operations and closed with the close operation. I suspect anywhere we are using a fd that we think of as a normal file descriptor, it could also be a direct descriptor that was created by one of the ops mentioned above or that was created with the register_files uring register variant.
The liburing manpage for io_uring_register_files gives a short explanation why an app would want to use direct descriptors. Of course, it boils down to getting better performance.

@FrankReh this PR is purely cosmetic, it gives no new functionality, and changes no behaviour. I was trying to understand the special case logic on Close, and realised the logic for it was contained in try_submit_with, which is only called in Close.
I just moved the logic into Close to make it clearer what's going on

this PR is purely cosmetic, it gives no new functionality, and changes no behaviour. I was trying to understand the special case logic on Close, and realised the logic for it was contained in try_submit_with, which is only called in Close.
I just moved the logic into Close to make it clearer what's going on

Thanks. That context helps. I'm for it but let's wait some for @Noah-Kennedy to free up and have a look too.
And regarding the file layout, if you also think something could be done, let's try to convince @Noah-Kennedy. My suggestion would be that we come up with a proposal ahead of time for file movement, but we get all the old PRs taken care of before we make those changes and we warn any fresh PRs coming in that files are about to change - I don't trust git to merge changes well when file names change and content changes. I mean Noah might feel its not worth changing and everything is clear in his head and over time, they will be in ours too, and the churn would be too much work for PRs we didn't resolve ahead of time. Let's see.

I've been wanting to restructure the file layout for everything, but am waiting for a break in PRs to quickly move things around.

What I'm wondering is if we even want to do this, or if we just want to do a synchronous close on drop. I really don't like the whole deferred cleanup semantics this drop behavior has created.

What I'm wondering is if we even want to do this, or if we just want to do a synchronous close on drop. I really don't like the whole deferred cleanup semantics this drop behavior has created.

I think the alternative is to tie the lifetime of the runtime to that of all Ops, or at least, ops you want to have shutdown semantics

Because it's not just Close, it's also multi poll ops

@Noah-Kennedy How do you feel about merging this until we get round to working out a better scheme for Close/cancellation semantics?

I'd be down with merging while we work out a better scheme.


specific words cause the plugin to fail

hello.
whenever I use the word "context" (upper or lowercase) in an alias definition under the frontmatter YAML of an mkdocs.yml file, the build process fails with the following error:
meta_data['alias']['text']
~~~~~~~~~~~~~~~~~~^^^^^^^^

I'm using Python 3.11, mkdocs 1.5.3 with mkdocs-material 9.4.1
thanks!
Jorge

Interesting, I'll take a look!

it was really weird because I work with a few hundred files in the same folder and I was processing them automatically through another tool that inserts names of files as aliases in the same file. and everything was running fine until it hit a file called "somethingcontext.md". tested it with several files with the same results and ended up having to rename the alias to something like "ctx". maybe there's a reserved keyword, beats me, but the plugin is really useful (great work!) so I wanted to give you a heads-up anyway :)

pretty dumb, yeah, and I should know because I made several of those in my programming life :) I hadn't even checked the code before I opened the issue, shame on me.
just tested 0.7.1 and it works fine now! thank you very much for the fix and for doing it lightning-fast!

Awesome, thanks for the report!1


symfony 3 recipe support

Seems like the symfony recipe doesn't support the symfony 3 directory structure yet.

console command moved to bin folder
cache & logs moved to var folder.

I guess the recipe just needs to be tweaked some more to accommodate these

Current, Deployer support symfony 2.x as default.
If you want switch to symfony 3.0, you can modify recipe follow http://deployer.org/docs/recipes
set('shared_dirs', ['var/logs']);
set('writable_dirs', ['var/cache', 'var/logs']);
set('bin_dir', 'bin');
set('var_dir', 'var');
after('deploy:vendors', 'database:migrate');

IMO Deployer should support Symfony 3, it makes it easier to integrate with a project.
There is nowhere a cookbook or article to get Deployer to run with Symfony 3, so it might not be immediately clear for developers what they need to do.
Also Deployer already supports Drupal 7 & 8, Yii & Yii 2, so why not add support Symfony 3 as well?
I have created a simple PR (#515) to add a new recipe for Symfony 3

Current, Deployer supported Symfony 3.0, but it not default (because at that time, symfony 3.0 is not stable).
Please see docs before make issue.
http://deployer.org/docs/recipes
We can make it to dèault.

Symfony 3 is stable for a couple of months now. But I don't think the Sf3 structure should be default, since it might take a while for all projects to upgrade to version 3.
That is why I suggest having a recipe for both version 2 and 3. That makes it the easiest for developers to get started with Sf3.
Not everyone will always read the docs

@elfet What are you think about making recipes with framework and version?

I think having framework+version (symfony,symfony3 recipe) bad idea. A lot of task will be same, as a lot of configs. But for now i do not see any other solution. Maybe have a config for version?

I think having framework+version (symfony,symfony3 recipe) bad idea. A lot of task will be same, as a lot of configs

But you do this for Drupal (7 & 8) and Yii (1 & 2)

Yes, maybe it's time for finding better solution. Or to keep adding version recipes.
framework + version is simplest solution for now. Maybe live it as it?


Markdown rendering and html snippets

This PR remove the marked package and uses remarkable instead.
The reason is that marked has a xss vulnerability, and doesn't appear to be an active project anymore.
See: https://nodesecurity.io/advisories/marked_content-injection

Create a sluglify function to generate better slugs.

Add support for html files on snippets

Add testing for markdown rendering

Coverage remained the same at 100.0% when pulling 025a256d6e67c9860d8229c2dc357d6ba2324edb on markdown into c0fff0ec60cfe54cf912763dcbb983bb0f0769a8 on master.

Coverage remained the same at 100.0% when pulling 96a9113b5677867e99e8807576c9f61c862b40bf on markdown into c0fff0ec60cfe54cf912763dcbb983bb0f0769a8 on master.