Feature Request: Markdown Parser via Plugin? Alternative, a block that takes a "HTMLRepresentable"

It would be nice to have the Markdown parsed via a "MarkdownParserService" or some patches of  HTML provided by an "HTMLProvider" protocol?
Perhaps that could even not be a site wide call? My "Recipes" Content folder could use the RecipeoParser package and "BandReviews" could use the MetalMarkerExtreme package...
Maybe the simplest would be a Block Element that would take in any  "HTMLRepresentable", not just an already rendered include.
I currently use hugo (partially to keep myself from fussing), but I really miss the plugin architecture of WordPress. hugo's lack of plugins is why I'll probably move on.  Maybe to Ignite!  Thank you!

Understood – that makes perfect sense. So perhaps if I declare a protocol that requires Markdown parsers to accept either a URL or some Markdown string, make it default to the current Markdown parser, then allow developers to override it at the site and/or ContentPage level. Would that solve your problem fully?

I think it might! WooHoo!

This is resolved, although perhaps not as fully as you might have hoped 😅
You can now adjust the Markdown renderer to use site-wide for rendering Markdown placed into the Content folder. This does not change the parser used for rendering inline Markdown, e.g. when using Text(markdown:), and I'm afraid there's no option to customize this at the ContentPage level – it's one setting for the entire site. Hopefully that's good enough!


What is "position_idx" in the deposit function?

Hi I was wondering what the position_idx input here in the deposit function is and how I can get it? https://github.com/Mirror-Protocol/mirror.js/blob/6862923bfe6a6d886af5287c65c0161b896598d0/src/contracts/MirrorMint.ts#L297
We are trying to use mirror js to interact with mirror but after reading searching the docs and testing out the mirror js deposit function for several hours, we are stuck on the position_idx input, it seems we are providing the wrong value (based on our error msg)
How do I get this position_idx input? Thank you!

Hi,
position_idx represents a Collateral Debt Position (CDP and Mirror's Mint contract handles that.
You get this value on opening a position with mirror.mint.openPosition where mint is an instance of a mirror.js Mirror class (that's part of a short farming flow on the Web App)  and provide it to perform activities on your position.
Like in your case, depositing collateral to a CDP would obviously require a position_idx identifying that CDP you're going to update.
I'm sure you've already found the answer, but let me post this here just in case someone's searching for the same.
Not sure if issues are the right place to talk about that though ;)
You might wanna close it and visit project Discord as an option.


PR description Release Notes missing some versions from GitHub releases

Package ecosystem
Rust / Cargo
Package manager version
N/A
Language version
N/A
Manifest location and content prior to update
/Cargo.toml: https://github.com/Malax/libcnb.rs/blob/917a1cb085ae7fcce6869dacb3254add001f9354/Cargo.toml
dependabot.yml content
https://github.com/Malax/libcnb.rs/blob/917a1cb085ae7fcce6869dacb3254add001f9354/.github/dependabot.yml
Updated dependency
semver from ^0.11.0 to ^1.0.4
What you expected to see, versus what you actually saw
Expected:
The "Release notes" section of the PR description to include references/content from all GitHub releases between v0.11.0 and 1.0.4. ie:
https://github.com/dtolnay/semver/releases/tag/1.0.4
https://github.com/dtolnay/semver/releases/tag/1.0.3
https://github.com/dtolnay/semver/releases/tag/1.0.2
https://github.com/dtolnay/semver/releases/tag/1.0.1
https://github.com/dtolnay/semver/releases/tag/1.0.0
Actual:
The "Release notes" section of the PR description only referenced the most recent GitHub release:
https://github.com/dtolnay/semver/releases/tag/1.0.4
Native package manager behavior
N/A
Images of the diff or a link to the PR, issue or logs
https://github.com/Malax/libcnb.rs/pull/39

Thanks @edmorley, the way this currently works is we try to fetch all the releases since the previous versions releases, however, there doesn't seem to be a release for 0.11.0, and so dependabot falls back to showing the latest release.
The releases I could find for this project:
gh api repos/dtolnay/semver/releases | jq .[].tag_name
"1.0.4"
"1.0.3"
"1.0.2"
"1.0.1"
"1.0.0"

The relavant code in dependabot: https://github.com/dependabot/dependabot-core/blob/33198c89f93d6bfc6734e8538d53d460f59ae021/common/lib/dependabot/metadata_finders/base/release_finder.rb#L204-L223
I'm not sure of a good way to fix this edgecase, but I think it should work as expected when there is a release for the previous version?

@jurre Thank you for the quick reply :-)
Ah true - there is not a GitHub release for 0.11.0, although there is a Git tag for that release.
I had thought it would look at both proper releases and Git tags, given both show up at:
https://github.com/dtolnay/semver/releases
...however it makes sense why they might not.

Yeah, it gets a little tricky with tags as it's hard to determine which ones are an actual release, and version naming varies across repo's so determining order is not straight forward.
I'm going to close this out for now because I don't think there's much we can do in this case, but please feel free to follow-up if you have any thoughts.
PS: Appreciate the clearly written report, made it really easy to figure out what was happening!


Uh what is this?

Severity	Code	Description	Project	File	Line	Suppression State
Error	CS1705	Assembly 'CharacterAI' with identity 'CharacterAI, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' uses 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version than referenced assembly 'System.Runtime' with identity 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'	CharAILayer	C:\Users\Administrator\source\repos\CharAILayer\CharAILayer\CSC	1	Active

idk
Did you change anything?
try this mby

still got the error even after removing bin folder

@aquadeve I completely rewrote the whole thing, please download the latest version and check out wiki/Getting-started


SelfTest binary leaks memory (or at least ASAN thinks so).

I found an old issue that talked about ASAN errors. Since it was during multithreaded run, old and without specifics, it was pointless, but I decided to look at the current state.
ASAN reports several leaks in the SelfTest binary, mostly in generators, but some of them I really don't know how to read (the ones at the top).

=================================================================
==17940==ERROR: LeakSanitizer: detected memory leaks

Indirect leak of 85 byte(s) in 1 object(s) allocated from:
    #0 0x5a1090 in operator new(unsigned long) (/catch-path/Build/SelfTest+0x5a1090)
    #1 0x7fb46c1f296c in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) (/usr/lib/x86_64-linux-gnu/libstdc++.so.6+0x12196c)
    #2 0x7ffe1bb02aff  (<unknown module>)
    #3 0x7ffe1bb02abf  (<unknown module>)

Indirect leak of 85 byte(s) in 1 object(s) allocated from:
    #0 0x5a1090 in operator new(unsigned long) (/catch-path/Build/SelfTest+0x5a1090)
    #1 0x7fb46c1f296c in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) (/usr/lib/x86_64-linux-gnu/libstdc++.so.6+0x12196c)
    #2 0x7ffe1bb0309f  (<unknown module>)
    #3 0x7ffe1bb0307f  (<unknown module>)

Indirect leak of 85 byte(s) in 1 object(s) allocated from:
    #0 0x5a1090 in operator new(unsigned long) (/catch-path/Build/SelfTest+0x5a1090)
    #1 0x7fb46c1f296c in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) (/usr/lib/x86_64-linux-gnu/libstdc++.so.6+0x12196c)
    #2 0x7ffe1bb02b5f  (<unknown module>)
    #3 0x7ffe1bb02b3f  (<unknown module>)

Indirect leak of 80 byte(s) in 1 object(s) allocated from:
    #0 0x5a1090 in operator new(unsigned long) (/catch-path/Build/SelfTest+0x5a1090)
    #1 0x69fcc3 in Catch::createGeneratorsForTest() /catch-path/include/internal/catch_generators_impl.hpp:81:16
    #2 0x70c2c5 in Catch::Context::getGeneratorsForCurrentTest() /catch-path/include/internal/catch_context_impl.hpp:73:30
    #3 0x70b67c in Catch::Context::getGeneratorIndex(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long) /catch-path/include/internal/catch_context_impl.hpp:32:20
    #4 0x63c669 in Catch::CompositeGenerator<IntPair*>::operator IntPair*() const /catch-path/include/internal/catch_generators.hpp:90:31
    #5 0x635565 in ____C_A_T_C_H____T_E_S_T____2() /catch-path/projects/SelfTest/GeneratorTests.cpp:38:18
    #6 0x6e332a in Catch::FreeFunctionTestCase::invoke() const /catch-path/include/internal/catch_test_case_registry_impl.hpp:151:13
    #7 0x6a12d9 in Catch::TestCase::invoke() const /catch-path/include/internal/catch_test_case_info.hpp:176:9
    #8 0x701513 in Catch::RunContext::invokeActiveTestCase() /catch-path/include/internal/catch_run_context.hpp:314:13
    #9 0x700de5 in Catch::RunContext::runCurrentTest(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&) /catch-path/include/internal/catch_run_context.hpp:285:21
    #10 0x6d8437 in Catch::RunContext::runTest(Catch::TestCase const&) /catch-path/include/internal/catch_run_context.hpp:104:21
    #11 0x69bb4c in Catch::runTests(Catch::Ptr<Catch::Config> const&) /catch-path/include/internal/../catch_session.hpp:78:27
    #12 0x72c257 in Catch::Session::run() /catch-path/include/internal/../catch_session.hpp:186:42
    #13 0x6e033f in Catch::Session::run(int, char const* const*) /catch-path/include/internal/../catch_session.hpp:165:30
    #14 0x6ae1fb in main /catch-path/include/internal/catch_default_main.hpp:15:12
    #15 0x7fb46b1e082f in __libc_start_main /build/glibc-t3gR2i/glibc-2.23/csu/../csu/libc-start.c:291

...

The full output is at pastebin, because it has ~50k.
http://pastebin.com/WCBAbWbK

Looks like they all refer to the same Generators leak (well, in your truncated sample, anyway).
I had a quick look at the code and the leak is fairly obvious (fortunately generators aren't used much - or officially supported yet).
I've fixed that leak and pushed the changes. They should end up in the single include in the next release, but feel free to run your ASAN tests again before that.

It's clean now.


Pin service tester to an explicit version

Motivation
Because service-tester was broken at 4.2.0, it is now 4.2.1-RELEASE. We need to pin to that version otherwise service tester is broken and you can't run any tests.
Modification

There is now an interlokServiceTesterVersion variable pinned at 4.2.1-RELEASE
If interlokVersion ends in SNAPSHOT then we don't use interlokServiceTesterVersion

Post merge into develop this needs to be merged into master.
PR Checklist

[x] been self-reviewed.
[x] Added comments explaining the "why" and the intent of the code wherever it would not be obvious for an unfamiliar reader

Result

If they do nothing they get 4.2.1-RELEASE
They can now pin their version at whatever they want.
Not sure what the ramifications are on dependabot, this change could be reverted when 4.3.0-RELEASE is published.
Side effect is that we currently have no idea what happens if 4.2.1-RELEASE of interlokVersion happens before 4.3.0-RELEASE...

Testing
Create gradle project using this branch
ext {
  interlokParentGradle = 'https://raw.githubusercontent.com/adaptris/interlok-build-parent/service-tester-explicit-version/v4/build.gradle'
  // interlokVersion = '4.3-SNAPSHOT'
}
allprojects {
  apply from: "${interlokParentGradle}"
}

Do gradle -PbuildEnv=dev clean assemble
cd build/distribution && java -jar lib/interlok-boot.jar -version
Service Tester should be pinned at 4.2.1-RELEASE

Bootstrap of Interlok 4.2.0-RELEASE(2021-09-03:4.2.0) complete
Version Information
  Interlok Config/variable substitutions: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Config/xinclude: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/Annotations: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/Base: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/Bootstrap: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/Client: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/Common: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/JMX Client: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Core/Logging: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok HTTP/Apache HTTP(4): 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Management/REST: Base: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Management/REST: Health Check: 4.2.0-RELEASE(2021-09-03:4.2.0)
  Interlok Service Tester/Core: 4.2.1-RELEASE(2021-09-14:08:51:24 BST)
  Interlok Transform/JSON: 4.2.0-RELEASE(2021-09-03:4.2.0)

Uncomment the interlokVersion so that we're pinned at 4.3-SNAPSHOT, and run the commands again

Service Tester should be pinned at 4.3-SNAPSHOT

Bootstrap of Interlok 4.3-SNAPSHOT(2021-09-15:04:27:58 BST) complete
Version Information
  Interlok Config/variable substitutions: 4.3-SNAPSHOT(2021-09-15:04:41:05 BST)
  Interlok Config/xinclude: 4.3-SNAPSHOT(2021-09-15:04:41:40 BST)
  Interlok Core/Annotations: 4.3-SNAPSHOT(2021-09-15:04:27:13 BST)
  Interlok Core/Base: 4.3-SNAPSHOT(2021-09-15:04:27:58 BST)
  Interlok Core/Bootstrap: 4.3-SNAPSHOT(2021-09-15:04:27:14 BST)
  Interlok Core/Client: 4.3-SNAPSHOT(2021-09-15:04:27:20 BST)
  Interlok Core/Common: 4.3-SNAPSHOT(2021-09-15:04:27:21 BST)
  Interlok Core/JMX Client: 4.3-SNAPSHOT(2021-09-15:04:27:23 BST)
  Interlok Core/Logging: 4.3-SNAPSHOT(2021-09-15:04:37:25 BST)
  Interlok HTTP/Apache HTTP(4): 4.3-SNAPSHOT(2021-09-15:04:41:11 BST)
  Interlok Management/REST: Base: 4.3-SNAPSHOT(2021-09-15:04:56:12 BST)
  Interlok Management/REST: Health Check: 4.3-SNAPSHOT(2021-09-15:04:56:32 BST)
  Interlok Service Tester/Core: 4.3-SNAPSHOT(2021-09-15:04:47:08 BST)
  Interlok Transform/JSON: 4.3-SNAPSHOT(2021-09-15:04:42:03 BST)

Pin interlokVersion as "4.1.0-RELEASE", service-tester stays at 4.1.0-RELEASE

Bootstrap of Interlok 4.1.0-RELEASE(2021-06-21:12:33:34 BST) complete
Version Information
  Interlok Config/variable substitutions: 4.1.0-RELEASE(2021-06-21:12:47:44 BST)
  Interlok Config/xinclude: 4.1.0-RELEASE(2021-06-21:12:47:40 BST)
  Interlok Core/Annotations: 4.1.0-RELEASE(2021-06-21:12:32:52 BST)
  Interlok Core/Base: 4.1.0-RELEASE(2021-06-21:12:33:34 BST)
  Interlok Core/Bootstrap: 4.1.0-RELEASE(2021-06-21:12:32:54 BST)
  Interlok Core/Client: 4.1.0-RELEASE(2021-06-21:12:32:59 BST)
  Interlok Core/Common: 4.1.0-RELEASE(2021-06-21:12:32:58 BST)
  Interlok Core/JMX Client: 4.1.0-RELEASE(2021-06-21:12:33:02 BST)
  Interlok Core/Logging: 4.1.0-RELEASE(2021-06-21:12:43:05 BST)
  Interlok HTTP/Apache HTTP(4): 4.1.0-RELEASE(2021-06-21:12:47:05 BST)
  Interlok Management/REST: Base: 4.1.0-RELEASE(2021-06-21:13:02:11 BST)
  Interlok Management/REST: Health Check: 4.1.0-RELEASE(2021-06-21:13:02:31 BST)
  Interlok Service Tester/Core: 4.1.0-RELEASE(2021-06-21:12:53:10 BST)
  Interlok Transform/JSON: 4.1.0-RELEASE(2021-06-21:12:48:32 BST)

@mcwarman -> you might want to backport this into your env.


CONTROL+C on close instead of CONTROL_CLOSE_EVENT

Description of the new feature/enhancement

on closing the x button send a control+c signal to all processes by default instead of terminating them.
Definition: the x button is described as both the x button for windows terminal itself and every tab
Proposed technical implementation details (optional)

there are three ways to implement this maybe make them all options

Send Control+C signal and do nothing if processes don't respond. If nothing is done then the user clicks the X button a second time send a SIGTERM(CONTROL_CLOSE_EVENT) that gives the application 5s to respond before closing
Send Control+C signal and do nothing for 5-8s, After that prompt the user if they are sure they want to kill all processes inside before closing like macOs but not immediate as we want CLI programs to try and save on regular shutdown
Add an option to always use Control_CLOSE_EVENT (SIGTERM) on X button for those users that don't want the prompt and don't care about data loss / file corruption

Could you clarify why this is important to you? It would help us give this feature request a priority.

important

Most console apps using cli's are running important functions and will have file corruption if it's forcibly terminated. Always using the windows equivalent of SIGTERM isn't a good default solution.

But SIGTERM is the soft exit equivalent under UNIX. Did you mean SIGQUIT? That one forcibly terminates.
CONTROL_CLOSE_EVENT is a little bit like SIGTERM's usage in upstart and systemd, because it sends an exit signal but has a timeout of 5s until it sends an equivalent of SIGQUIT. It's very similar under UNIX when a service management software is being used.
I do understand what you mean however, so I'll bring it up for discussion.

I think we should investigate whether we should support this. If it's easy to implement: Let's just do it!
But we don't really believe that this is an important aspect to fix and implement right now, unless more people request this or if any other circumstances change.

Woops commented on the wrong issue. 😄


unsafe build flags error when including llmfarm_core

Hello
Each time I add llmfarm_core package as a dependency I see the following error:
The package product 'llmfarm_core' cannot be used as a dependency of this target because it uses unsafe build flags.
Any idea why?

https://stackoverflow.com/questions/67889931/the-package-product-mylibrary-cannot-be-used-as-a-dependency-of-this-target-be
Try the solution suggested here. Or add a library by dragging and dropping a directory into the project.  I will update the Readme later.

Solution didn't work for me, but drag and dropping the framework did. Thank you.


refactor: remove usages of secp256r1 in test sources

Description:
Remove usages of secp256k1 in test sources and old demo for jwt credentials
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

coverage: 51.631% (+2.3%) from 49.381%
when pulling 2c2e0f973e4afb9243aa3675a7a685e45e6c06ad on ATL-7117-secp256r1-to-secp256k1
into 975730ae5053721e5d16d5e0a15bd63b31405d9c on main.


NO_COLOR support

I see many projects using this library, and I don't see simple way to disable colored output for those apps (without code modification). In production environments I like to grep easily logs and colors are making it super difficult.
More info about NO_COLOR environment variable at https://no-color.org/

If NO_COLOR support is added, might be additionally good to add support for CLICOLOR_FORCE which allows you to always enable it. See http://bixense.com/clicolors/.

The good thing about standards is that there are so many to choose from.
  - Andrew Tanenbaum

The guy who created NO_COLOR was told about the existing and superior CLICOLOR as soon as he announced it. Unfortunately he didn't do the right thing and defer to that standard, so now we have this annoying situation where the worse standard (NO_COLOR) has better marketing.
It looks like bixense has incorporated NO_COLOR into their page but predictably there's no mention of CLICOLOR on no-color.org.


feat(dropdown): add open class support

Adds support for the uib-dropdown-open class to be toggled on the container element of a dropdown menu on dropdown toggle

This closes #4466.

Couldn't this be considered a BC?

Technically, but I doubt anyone is using a class named uib-dropdown-open in their app

I was more thinking of a user relying on the open class to do something and now it is a different one. (If I understood the issue correctly.)

This only affects appendTo and appendToBody

I see. Well, good to go.


Bluetooth: tests: shell: Fix build error

This fixes build error that happened if CONFIG_BT_CAP_ACCEPTOR_SET_MEMBER was not set. This fixes the build test case as well.

Rebased, as build failed due to unrelated issues

Rebased, as build failed due to unrelated issues

It failed again as the fix was not yet merged. Should be merged now, so I restarted your failing tests :)


not working when using module-info.java

Hello,
actually openglfx is the thing I was looking for. I use JavaFX with module-info.java (jpms).
I use the lwjgl library as my prefered opengl wrapper. I've added "requires lwjgl" and "requires core"
to the module-info.java.
I got JavaFX and LWJGL working per se. (classic way: offscreen rendering and download framebuffer with two PBOs and fill WritableImage's pixel buffer)
Even when I add the "--add-opens" listed on the project Page I get the error
class com.huskerdev.openglfx.OpenGLCanvas (in module core) cannot access class com.sun.javafx.scene.layout.RegionHelper (in module javafx.graphics) because module javafx.graphics does not export com.sun.javafx.scene.layout to module core
What else should I add to the module-info.java to get openglfx working with JavaFX when using modules?
kind regards.

Hi,
you can get the list of all add-opens on the main page.
https://github.com/husker-dev/openglfx#reflections-opens

If all opens are added, then everything should work. Note that —add-opens is command line argument. For module file you need to use it withou dashes. (I am not sure)

Hello,
thank you for the quick reply. I've added all of those --add-opens to the VM Options in the configuration settings (VM Options). But still does not work. Any other ideas?
just ofr the record
I've

created a new javafx project with intellij )maven, language: java
used your generator https://huskerdev.com/?page=tools/openglfx (java, maven, lwjgl)
added the maven dependencies
added all the --add-opens as VM Options

Might there be something that I forgot to do?
kind regards

I can not say exactly.
It's possible that your JavaFX project is calling the main method without using your arguments.
Check your execution target in IntelliJ IDEA. Also it happens when you use JavaFX plugin.  But do I need the "real" lwjgl dependencies or only those provided by you?

My LWJGL module is just a bridge (addon) to core library especially for LWJGL (there is also module for JOGL).
So, you need to use both of them.

I downloaded the source code and added the module-info files and configured the requried modules and exports. but the problem remains with sun.prism libraries/modules that are not beeing exported by javafx.graphics. seems to be a problem of javafx per se and how they export or not export modules.

after some time searching the web, i found that the com.sun..... classes are internal classes and that these are not exported by javafx.graphics module. so they are actually not for use. and when using modules that it is not working. i also tried export stuff with maven plugin and also removed the javafx maven plugin. to sum up.. I'cant use it when using javafx with modules. kind regards.

I'll close this issue.
If you have any questions, please reopen it again.


Gradle plugin: generate logback.xml even with missing gatling resources directory

Currenly, logback.xml is generated together with processGatlingResources task.
When resources directory (src/gatling/resources) is missing or users changes default location - the plugin may skip generation of logback.xml at all.
This may lead to improper logging configuration.
Improve generation of logback configuration
This is refactoring

Detect if gatling resources contains either logback.xml, logback.groovy etc. Currently the file location is hardcoded, this should be changed to analyze source directories and only limit sources to gatling resources.
If gatling resources has logback configuration - do nothing.
If gatling resources doesn't include any logback config files - then

generate logback.xml somewhere in build directory. A separate directory should be used, the file must not be put into build/resources as now. The generated file is better to place into build/generated to prevent interference with real resources processed by Gradle.
As now generated logback.xml should use gatling.logLevel parameter to configure root logger level

Generated logback.xml should be passed to every forked JVM that executes Gatling via additional -Dlogback.configurationFile system property as logback docs explains.
Make sure current tests work.
Add test cases for other files, like logback.groovy etc.

Add possibility to configure HTTP requests via gatling configuration closure
This is new feature

Add a new parameter to gatling configuration closure

named logHttp
values: enum of [NONE, ALL, FAILURES]

during logback.xml generation logHttp should enable logger of HTTP request (io.gatling.xxx), according to passed value
create tests

Prevent logging misconfigurations and improve plugin UX
This is a new feature

If a user puts logback.xml or similar to resources folder, but the same times uses logLevel or logHttp parameters of gatling closure - plugin should throw an exception

as an option - WARN log should be logged, without an exception.

create tests for this feature

How do a user know how to enable HTTP traffic logging?

How does a user know how to enable HTTP traffic logging?

right now - it's possible to add a section to plugin's docs explaining how to do this with custom logback.xml
then - new issue should be created, to add more logging related options to gatling configuration closure.

right now - it's possible to add a section to plugin's docs explaining how to do this with custom logback.xml

Sadly, that wouldn't suffice. We copied those files everywhere for a reason.
Please understand we're not only aiming at professional developers who do read documentation.
Lots of our users don't read doc. Check on our community mailing list or Gatling questions on StackOverFlow.

right now - it's possible to add a section to plugin's docs explaining how to do this with custom logback.xml

Sadly, that wouldn't suffice. We copied those files everywhere for a reason.
Please understand we're not only aiming at professional developers who do read documentation.
Lots of our users don't read doc. Check on our community mailing list or Gatling questions on StackOverFlow.

So - let's include this feature into this issue.
Please explain detailly what parameters should be added.

Let's focus on what most users want:

use the default non verbose mode
have options for debugging either failing HTTP traffic, or all HTTP traffic. Those options should be easy to discover (how? suggestions?).

What we could do would be to generate a logback.xml file on the fly (somewhere in target) when the user doesn't provide one (see http://logback.qos.ch/manual/configuration.html#auto_configuration), meaning typically detecting none of the possible files exists in the classpath (or at least in the target dir). The easiest solution then would be to set this file thanks to the logback.configurationFile System property.
WDYT?

Currently

logback.xml is already generated on the fly, using gatling configuration closure.
generated logback.xml is already included into classpath if there's no provided file

But there's some bugs with this and using logback.configurationFile may be a one option to solve this
Also, currently plugin doesn't support HTTP traffic loggin.
For this I planned to introduce new parameters to gatling configuration
gatling {
   logLevel = "WARN" // already exists
   logHttp = // new parameter, one of ALL, FAILED, NONE
}

This will allow to almost exclude a need to deal with custom logback.xml in souce code and only rely on plugin configuration.

Also, currently plugin doesn't support HTTP traffic loggin.
For this I planned to introduce new parameters to gatling configuration
gatling {
logLevel = "WARN" // already exists
logHttp = // new parameter, enum, one of ALL, FAILED, NONE
}

Fine with me as long as those options are displayed but commented in the sample. Are we good?

Fine with me as long as those options are displayed but commented in the sample. Are we good?

Isn't it too early  to discuss this, the feature is not yet started.

Fine with me as long as those options are displayed but commented in the sample. Are we good?

Isn't it too early to discuss this, the feature is not yet started.

Until this feature is implemented, we should let the example files in place.

Isn't it too early to discuss this, the feature is not yet started.

Sorry, I should have explained that we have an agenda :)
We're currently finishing QA for the upcoming release of Gatling 3.4.0 and FrontLine 1.12.0. We want to release the new gradle plugin at the same time (including doc and sample). We wanted to release by the end of the week but we'll probably be a bit late.
So the point is:

if we can have this feature by end of this week => we can drop the logback.xml in the sample
if not => we have to keep the file in the sample for the release, and remove it in a next release when we'll have the feature

Making things clear: I'm not pressing you to work on this if you don't have the cycles in order to meet our own deadlines. That's something we can work on ourselves.

Ok I got the idea.
Definately won't be able to finish ot EoW :(
Let's keep logback.xml for now, and I'll be working on this issue meanwhile.

I've had a look at the current implementation and I have some questions/remarks:

It only looks for logback.xml. We should look for other possible files, in particular logback.groovy and logback-test.xml.
Why do you search in the resources directory? Why not search in the binary output directory? The file should have been copied there as the plugin triggers after compilation.
Same remark for the generated file. It shouldn't be generated in the resources directory which is monitored by the VCS. It should be generated in the binary output directory.

WDYT?

All those options are reasons for creating this issue .
The current imeplementation causes inconsistencies, and this issue was created to address all of them, improving logback config generation.

I was asking for your insights if you already had some, in case we go with implementing the fix to cope with our deadline.

It's generated in build directory, not in sources. FYI

Yes, I stand corrected.

This is task description
Improve generation of logback configuration (refactoring)

Detect if gatling resources contains either logback.xml, logback.groovy etc Currently the file location is hardcoded, this should be changed to analyze source directories and only limit sources to gatling resources.
If gatling resources has logback configuraiton - do nothing.
If gatling resources doesn't include any logback config files - then

generate logback.xml somewhere in build directory. Separate directory should be used, file must not be put into build/resources as now. The generated file is better to place into build/generated to prevent interferention with real resources processed by Gradle.
As now generated logback.xml should use gatling.logLevel parameter to configure root logger level

Generated logback.xml should be passed to every forked JVM that executes Gatling via additional -Dlogback.configurationFile system property as logback docs explains.
Make sure current tests work.
Add test cases for other files, like logback.groovy etc.

Add posibility to configure HTTP requests via gatling configuration closure (new feature)

Add a new parameter to gatling configuration closure

named logHttp
values: enum of [NONE, ALL, FAILURES]

during logback.xml generation logHttp should enabled logger of HTTP request, according to values
create tests

Improve UX for logging

If a user puts logback.xml or similar to resoures folder, but the same times uses logLevel or logHttp parameters of gatling closure - plugin should throw an exception

as an options - WARN log should be logged, wihout an exception.

create tests for this feature

@slandelle put an whole task description above.

@eshepelyuk @Isammoc PTAL https://github.com/gatling/gatling-gradle-plugin/pull/8

This issue became a mess, closing it
Created #3948 #3949 #3950

Just for the record, the cause which started this issue seems to be the same problem as described in:

https://github.com/lkishalmi/gradle-gatling-plugin/issues/110
https://github.com/lkishalmi/gradle-gatling-plugin/issues/111
https://github.com/lkishalmi/gradle-gatling-plugin/issues/115


feat: add ability to specify which Kubernetes workload resources to scan

Description
This PR adds the "targetWorkloads" config field which lets users specify the Kubernetes workload resources they want to scan using the vulnerability-report and config-audit report scanners. By default, all workload resource types are scanned.
PR adds logic to do this, adds a test case for the config, updates the usage documentation, updates the helm chart and static manifests.
I had a use-case similar to the related issue and made these modifications for personal use. I saw the related issue today and wanted to open this PR in case it could also benefit the wider community.
Please let me know if anything else is required, or needs to be changed. Thanks!
Related issues

Close #265

Checklist

[x] I've read the guidelines for contributing to this repository.
[x] I've added tests that prove my fix is effective or that my feature works.
[x] I've updated the documentation with the relevant information (if needed).
[x] I've added usage information (if the PR introduces new options)
[x] I've included a "before" and "after" example to the description (if the PR is a user interface change).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@tks98 Look's good , thank you for the contribution , I have added couple of comments


Fix typo in README

Fix typo so that code snippet in README can run.

Thanks for this!

Sorry it took so long you caught me on vacation

It's okay :)


Configs and training scripts for LDRNeRF and Un+RawNeRF

Hi there,
Thanks for your amazing work in Dark-Nerf.
I wonder if you would like to provide the training scripts and configs for LDR-Nerf and Un+RawNeRF for raw datasets?
I noticed in llff_raw.gin it shows:

########################## RawNeRF specific settings ##########################
Config.rawnerf_mode = True
Config.data_loss_type = 'rawnerf'
Config.apply_bayer_mask = True
Model.learned_exposure_scaling = True
.....

But I'm not sure how to modify each parameter to get results of LDR-Nerf and Un+RawNeRF
Thanks!

Hello! I would like to know if you solve this? I use llff_raw.gin without some configs about Raw data, but I only get blur results. Thanks!


Update BasicCapsuleExperiments.cfg

fix for
https://github.com/Standecco/ROKerbalism/issues/7
and
https://github.com/Standecco/ROKerbalism/commit/7e2cbe7c019d4bde2fbf85d69f970ccc157a00c5
Thanks

This works.


Gizmo 3d grids

Objective

Adds 3d grids, suggestion of #9400

Solution

Added 3d grids (grids spanning all three dimensions, not flat grids) to bevy_gizmos

Changelog

gizmos.grid(...) and gizmos.grid_2d(...) now return a GridBuilder2d.
Added gizmos.grid_3d(...) which returns a GridBuilder3d.

The difference between them is basically only that GridBuilder3d exposes some methods for configuring the z axis while the 2d version doesn't.

Allowed for drawing the outer edges along a specific axis by calling .outer_edges_x(), etc. on the builder.

Additional information
Please note that I have not added the 3d grid to any example as not to clutter them.
Here is an image of what the 3d grid looks like:

Apparently there is something wrong with bevy_reflect. Can someone help here?
😅


Sometimes stuck unit tests

As a Pillarbox developer I need a reliable CI to have a smooth workflow.
Acceptance criteria

PR and merge queue status checks are not stuck anymore.

Hints
Sometimes unit tests get stuck, either locally or on CI agents. This issue appeared after we started work on comScore.
The issue was always appearing when updating Swift packages in the logs so we initially thought this could have a relationship with network issues we recently had. We were wrong.
The issue occurs consistently when packages are updated because it occurs at the end of a package test target execution. If we pause debugging when such hangs occur on a local development machine we can see that all tests passed but that execution is stuck, preventing the test target from exiting properly. Checking the stack trace it is likely this issue is related to a deadlock which might occur during comScore cleanup:
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
  * frame #0: 0x0000000100dcfce8 libsystem_kernel.dylib`__psynch_mutexwait + 8
    frame #1: 0x0000000100e34888 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_wait + 80
    frame #2: 0x0000000100e32398 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_slow + 244
    frame #3: 0x0000000106556a04 ComScore`ComScore::CriticalSection::enter() const + 12
    frame #4: 0x00000001064dc154 ComScore`ComScore::TaskExecutor::shutdown() + 108
    frame #5: 0x00000001064efba0 ComScore`ComScore::Core::shutDown() + 24
    frame #6: 0x0000000106513ff4 ComScore`ComScore::CoreContainer::~CoreContainer() + 24
    frame #7: 0x000000018010aeb4 libsystem_c.dylib`__cxa_finalize_ranges + 424
    frame #8: 0x000000018010b248 libsystem_c.dylib`exit + 28
    frame #9: 0x0000000102c95fe4 XCTestCore`_XCTestMain + 104
    frame #10: 0x0000000100b4c868 xctest`main + 156
    frame #11: 0x0000000100d09fa0 dyld_sim`start_sim + 20
    frame #12: 0x0000000100ea9e50 dyld`start + 2544

The reason why this issue sometimes consistently appears and sometimes not is yet unclear. Some fix ideas:

Wait at the end of a test suite.
Clear / flush pending SCORAnalytics events.
Disable parallel test execution for analytics.

Tasks

[ ] Fix unreliable CI.

If we disable analytics tests in the Pillarbox-Package-NoDebug scheme tests run fine, otherwise they quite surely get stuck on our CI agents.

With parallel testing disabled for the analytics test target the result is no better but the log is more readable and CI gets stuck earlier and in a way more identifiable in the logs. So parallelization removal might be helpful during investigations.

It seems that calling SCORAnalytics.clearOfflineCache() during the teardown phase helps.

Maybe talking to a former self might help.

Here is the full stack trace for all threads:
(lldb) bt all
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
  * frame #0: 0x0000000104d33ce8 libsystem_kernel.dylib`__psynch_mutexwait + 8
    frame #1: 0x0000000104ebc888 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_wait + 80
    frame #2: 0x0000000104eba398 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_slow + 244
    frame #3: 0x000000010a48ea04 ComScore`ComScore::CriticalSection::enter() const + 12
    frame #4: 0x000000010a414154 ComScore`ComScore::TaskExecutor::shutdown() + 108
    frame #5: 0x000000010a427ba0 ComScore`ComScore::Core::shutDown() + 24
    frame #6: 0x000000010a44bff4 ComScore`ComScore::CoreContainer::~CoreContainer() + 24
    frame #7: 0x000000018010aeb4 libsystem_c.dylib`__cxa_finalize_ranges + 424
    frame #8: 0x000000018010b248 libsystem_c.dylib`exit + 28
    frame #9: 0x0000000106a55fe4 XCTestCore`_XCTestMain + 104
    frame #10: 0x0000000104850868 xctest`main + 156
    frame #11: 0x0000000104a0dfa0 dyld_sim`start_sim + 20
    frame #12: 0x0000000104c45e50 dyld`start + 2544
  thread #4
    frame #0: 0x0000000104d32dec libsystem_kernel.dylib`__workq_kernreturn + 8
  thread #5
    frame #0: 0x0000000104d32dec libsystem_kernel.dylib`__workq_kernreturn + 8
  thread #6
    frame #0: 0x0000000104d32dec libsystem_kernel.dylib`__workq_kernreturn + 8
  thread #7, name = 'ComScore-Thread'
    frame #0: 0x0000000104d32edc libsystem_kernel.dylib`__ulock_wait + 8
    frame #1: 0x000000018013605c libdispatch.dylib`_dlock_wait + 52
    frame #2: 0x0000000180135e0c libdispatch.dylib`_dispatch_thread_event_wait_slow + 52
    frame #3: 0x0000000180146218 libdispatch.dylib`__DISPATCH_WAIT_FOR_QUEUE__ + 392
    frame #4: 0x0000000180145d18 libdispatch.dylib`_dispatch_sync_f_slow + 160
    frame #5: 0x000000010a469d20 ComScore`ComScore::Core::getCurrentHostApplicationState() + 220
    frame #6: 0x000000010a450874 ComScore`std::__1::__function::__func<ComScore::Core::start(ComScore::String, long long)::$_8, std::__1::allocator<ComScore::Core::start(ComScore::String, long long)::$_8>, void (ComScore::Task*)>::operator()(ComScore::Task*&&) + 2000
    frame #7: 0x000000010a413634 ComScore`ComScore::Task::run() + 44
    frame #8: 0x000000010a44be8c ComScore`ComScore::ContextTasksThread<ComScore::Core>::run() + 204
    frame #9: 0x000000010a48b1e0 ComScore`ComScore::Thread::threadEntryPoint() + 104
    frame #10: 0x000000010a48f570 ComScore`threadEntryProc + 32
    frame #11: 0x0000000104ebf4e4 libsystem_pthread.dylib`_pthread_start + 116
  thread #8, name = 'ComScore-NetworkThread'
    frame #0: 0x0000000104d347b0 libsystem_kernel.dylib`__psynch_cvwait + 8
    frame #1: 0x0000000104ebfacc libsystem_pthread.dylib`_pthread_cond_wait + 1264
    frame #2: 0x000000010a48a9a0 ComScore`ComScore::WaitableEvent::wait(int) const + 152
    frame #3: 0x000000010a44bf08 ComScore`ComScore::ContextTasksThread<ComScore::Core>::run() + 328
    frame #4: 0x000000010a48b1e0 ComScore`ComScore::Thread::threadEntryPoint() + 104
    frame #5: 0x000000010a48f570 ComScore`threadEntryProc + 32
    frame #6: 0x0000000104ebf4e4 libsystem_pthread.dylib`_pthread_start + 116
  thread #10
    frame #0: 0x0000000000000000
  thread #11
    frame #0: 0x0000000000000000
  thread #12, name = 'com.apple.NSURLConnectionLoader'
    frame #0: 0x0000000104d312ac libsystem_kernel.dylib`mach_msg2_trap + 8
    frame #1: 0x0000000104d42154 libsystem_kernel.dylib`mach_msg2_internal + 76
    frame #2: 0x0000000104d394b8 libsystem_kernel.dylib`mach_msg_overwrite + 536
    frame #3: 0x0000000104d3161c libsystem_kernel.dylib`mach_msg + 20
    frame #4: 0x00000001803708ac CoreFoundation`__CFRunLoopServiceMachPort + 156
    frame #5: 0x000000018036aff4 CoreFoundation`__CFRunLoopRun + 1152
    frame #6: 0x000000018036a75c CoreFoundation`CFRunLoopRunSpecific + 584
    frame #7: 0x0000000183fd40fc CFNetwork`___lldb_unnamed_symbol13283 + 344
    frame #8: 0x0000000180bf29d8 Foundation`__NSThread__start__ + 704
    frame #9: 0x0000000104ebf4e4 libsystem_pthread.dylib`_pthread_start + 116

Even if keeping only ComScorePageViewTests and deleting all other tests the issue can still arise.

Here is a test project with which the issue can be reproduced. This project:

Is an SPM package.
Uses comScore as dependency.
Implements a single test with an expectation fulfilled asynchronously.

We can likely use it to file a bug report or maybe find a workaround.

Quick summary of investigations so far:

Our tests started to get stuck randomly after our tests began to start the comScore SDK.
If the comScore SDK is started it seems that asynchronous tests (with either standard XCTest expectations or Nimble ones) might lead to deadlocks upon comScore main tracker cleanup.
When reading CI logs we see the process being stuck on package retrieval but this is misleading. This is due to the fact that all targets have finished their testing work but that at least one of them is stuck.

We can continue our investigations using the test project above and maybe find a solution or file a report. Otherwise we might need to find a way to temporarily avoid starting the comScore SDK on our CI, as having stuck jobs is incompatible with the concept of a CI.

Tested but not working:

Revert to version 6.9.0 (see release notes for 6.10.0).
Avoid persistent labels (see release notes).
Add large delay after startup / on teardown.

We have investigated this issue by reducing analytics tests to the minimum. Fortunately only running the AnalyticsTests target or all delivers the same results so, without loss of generality, we could focus on a single target.
We noticed that having a single comScore test for page views works fine. Just adding a CommandersAct event test in a parallel test suite fails, which is how we could deduce that the issue appears when a test suite ends without comScore having ended its startup phase, i.e. before the start event is sent for comScore.
An obvious mitigation is therefore to always wait for the start event at the beginning of a test suite, especially if this test suite is not testing comScore behavior (as testing comScore behavior only implies the start event has been emitted first). A simple implementation could be tested on our CI agents and could be run successfully without deadlocks several dozens times.

A mitigation has been implemented as part of #344 since this branch was very difficult to merge due to the above problem (the likelihood of having unit tests get stuck was very high, preventing status checks from ending correctly).

Failure conditions for archiving, code quality, documentation and UTs have been configured so that jobs fail after 5 minutes. This seems quite aggressive but should be enough.

We have something that works fine enough for now, even without time limits. Reporting a reproducible scenario to comScore is likely difficult as well. Closed for now.


Groupby in transformation and event detection functionality

Description of the problem
Currently the gaze dataframes are not grouped by trials.
This is problematic, as recording is potentially interrupted between trials.
For example, when transforming positional data into velocity data, this will create artifacts with very high velocity between each trial as the position changes instantly.
Description of a solution
This can be mitigated using a groupby argument to the gaze transformations and event detection functions.
For the Dataset class this could be done implicitly (maybe with the ability to specify/override optionally?) by a new attribute in the DatasetDefinition class.
Minimum acceptance criteria

[x] add groupby argument in the transformation functions in the GazeDataFrame class.
[x] add groupby attribute to DatasetDefinition
[x] use groupby attribute of DatasetDefinition for the transformation in the Dataset class
[x] use groupby attribute of DatasetDefinition for the event detection methods in the Dataset class

Yes please! Additionally, the values of the trial columns are missing for the gaze data within the resulting EventDataFrame.

Closed by #655


PARQUET-889: Fix compilation when SSE is enabled

bit-util.h was missing a couple of include. cpu-util.h was including
parquet/logging.h which is an internal header so the implementations of
the static functions have been moved in the source file.

I'm keeping an eye on it. If you enable Travis CI for your fork then we can get faster builds (right now we're in the general ASAF queue, which can sometimes get congested)

The build passed https://travis-ci.org/daedric/parquet-cpp/builds/204262490 -- the Linux failures are because of coveralls (we should make coveralls only run on the main repo maybe). Merging

Thanks for your contribution!

My pleasure :)


Prefer SubFields vs. SelectionSet

Looks like a pretty cool library!
Not sure if it is well known, but the ResolveFieldContext does have a SubFields property which is the fields that should be requested.  It looks like that Dapper.GraphQL may have a bug in that even though a field is in the SelectionSet, it may not necessarily be allowed to be returned (due to directives mainly).

Well, I think you'd know better than most :)  I'll update the source to use SubFields instead.

Nice work guys. Going to start using this today on a personal project and see how it goes. Thanks for logging the issue @joemcbride!

Another note for this change @dougrday , looks like when you upgrade to a later version of GraphQL that GraphQL.Type.Schema.ResolveType has been deprecated in favour of using the DependencyResolver property which is no longer a func but a concrete type implementing GraphQL.IDependencyResolver, so the docs/example will need to update similarly.

The main library is server agnostic so it does not have any dependencies on ASP.NET Core.  There is a FuncDependencyResolver provided for ease of transition.
services.AddSingleton<IDependencyResolver>(
    s => new FuncDependencyResolver(type => s.GetRequiredService(type)));

Hey @joemcbride,
I've just come into a scenario as follows which reminded me of this ticket and your mention of using context.SubFields over SelectionSet. Right now I am using SubFields, but I'm needing to do paging and so I've setup the following:
A basic connection type, based off GraphQL.Types.Relay.ConnectionType that just gives me a totalCount property for my UI.
public class BasicConnectionType<TTo> : ObjectGraphType<object>
        where TTo : IGraphType
{
    public BasicConnectionType()
    {
        Name = $"{typeof(TTo).GraphQLName()}Connection";
        Description = $"A basic (old-school paging) connection from an object to a list of objects of type `{typeof(TTo).GraphQLName()}`.";

        Field<IntGraphType>(
            name: "totalCount",
            description: "A count of the total number of objects in this connection, ignoring pagination."
        );

        Field<ListGraphType<TTo>>(
            name: "items",
            description: $"A list of objects of type `{typeof(TTo).GraphQLName()}`."
        );
    }
}

In my root Query class:
FieldAsync<BasicConnectionType<BookingType>>(...,
    resolve: async context =>
    {
        var fieldsRequested = context.SubFields.Keys; // ["totalCount", "items"]
        // I need whats under items, i.e. the fields on BookingType that were requested
    }
)

Basically I want to get those fields required on BookingType and pass them down to my DB query. That worked well when I was operating on the ListGraphType<BookingType>>, but now I'm wrapped in a BasicConnectionType<TTo> that SubFields list is ["totalCount", "items"]. I can see what I want is under context.SubFields.SelectionSet but is it ok to use that given your comments above?

Hey @joemcbride, I'm currently re-visiting this TODO and wondering... is it possible now to get the SubFields of the SubFields yet? Doesn't look like it as Field doesn't have a SubFields prop yet. Should I create an issue in the GraphQL repo, or is this just flat out impossible?
If I just use SelectionSet, it seems like it still only gives you what was asked in the query, so are you saying that directives are the only graphql feature that should would make SubFields and SelectionSet different? Or are there other cases?


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #19.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

@conda-forge-admin , please re-render

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@conda-forge-admin , please re-render

@conda-forge-admin , please re-render

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11591765229.

Ok now have this working. This is ready for review! 🙂

Please let me know how these changes go. Happy to follow up on anything as needed


Document opt-level 's' and 'z' stabilized in 1.28.

r? @matklad
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit ad5d79c9d543594f994449decbe6fa0c9a290999 has been approved by alexcrichton

:hourglass: Testing commit ad5d79c9d543594f994449decbe6fa0c9a290999 with merge 35b7e66b7dd0287cf71500556a66cdaf39009b00...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 35b7e66b7dd0287cf71500556a66cdaf39009b00 to master...


Unit Testing XBEE - mock

Hi,
I have been using this api for a while now and it is great :-)
I was wondering if anyone has figured out how to mock out a xbee packet to simulate a number of packets arriving through the serial channel.
Thanks in advance!
Jon

I mocked part of the library for tests in xbee-rx.  The mock is here and one instance of its use is here.

Thanks for the advice, will look into it :-). I've only used the xbee-api so far and not the xbee-rx version, would you say there is value in moving to the rx version?

@jonhardman xbee-rx builds upon xbee-api and takes care of the serial port connection and pairing off API calls with their responses.  It is based upon RxJS and provides streams for command results, messages and responses.  The simpler xbee-promise library handles local and remote commands with promises but doesn't handle incoming messages (since the promise model only handles single events, not multiple events in a row like a sequence of incoming messages).


BZ 1319777: add reproducer

Add reproducer for NPE when marshalling a persistent KieSession with partially matched forall.

Merged and fixed by https://github.com/droolsjbpm/drools/commit/b5062bb3997f1c2a535a97b9ce411e228b2e270d


needs more owo

As a suggestion, when OwO is found, perhaps it can post a picture with 'bulge' as a tag?

might be a bit much for all them. I might implement it for every 100th one

sounds good.

It looks like it already only takes action every hundred: https://github.com/smileytechguy/furbot/blob/auto-bulge/furbot_v2.py#L396-L405
My PR proposes that it send a bulge every 50.


Needs updating

This is outdated since Office 365 CN now has Teams

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

ID: 169a20a6-ebf7-1093-3cb1-fb438b9b7e13
Version Independent ID: b2074fd8-724e-75fa-bafb-a0f7966bf593
Content: Coexistence with Skype for Business - Microsoft Teams
Content Source: Teams/coexistence-chat-calls-presence.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Hi @danmyhre, thank you for your feedback.
Could you explain more about this? Could you let me know what update you're asking for? Do you think the first sentence in the article is not enough?
Thanks!

So since 21vianet (CN) now has teams, this section needs updating:
https://learn.microsoft.com/en-us/microsoftteams/coexistence-chat-calls-presence#federation-and-interop-with-office-365-operated-by-21vianet
Federation with the global cloud doesn't work and isn't supported yet (per Microsoft support)

@MikePlumleyMSFT, I'll need your help to confirm this information. Thanks!

@MikePlumleyMSFT hope all is well. Wanted to check if there was an update here. Thanks.

@MikePlumleyMSFT hope all is well. Wanted to check if there was an update here. Thanks.

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Cannot support Unicode or Chinese characters!

VSCode Version:1.2.0
OS Version: Windows 10 1511

Steps to Reproduce:

install C++ extension
create a c++ file with blankspace or Unicode or Chinese character in the filedir or filename
compile by using vscode command (use my own compiling batch script which will echo the filename)
garbled characters appear in the output panel, and cannot debug normally(cannot open source code file when meet the breakpoint)

This illustrates that VSCode can not support Unicode or Chinese character completely. Please add complete support to those character. Thank u!

compiling batch script code:
`@echo off
rem ----config----
set directory="C:\Program Files (x86)\MinGW64"
rem --------------
echo Compiling...
set "directory=%directory:"=%"
if exist "%directory%\bin\g++.exe" (
path="%directory%\bin"
cd /d "%directory%"
echo MinGW64 Directory: "%directory%"
echo g++.exe %1 -o %2 -g3
bin\g++.exe %1 -o %2 -g3
echo Complete!
exit
)
echo Please correctly config the MinGW64 Directory in Compile.bat!
`
launch.json:
{     "version": "0.2.0",     "configurations": [         {             "name": "C++ Launch (GDB)",             "type": "cppdbg",             "request": "launch",             "launchOptionType": "Local",             "targetArchitecture": "x64",             "program": "${workspaceRoot}/a.exe",             "args": [],             "stopAtEntry": false,             "cwd": "${workspaceRoot}",             "environment": [],             "externalConsole": true,             "miDebuggerPath": "C:\\Program Files (x86)\\MinGW64\\bin\\gdb.exe"         }     ] }
tasks.json:
{     "version": "0.1.0",     "command": "${workspaceRoot}\\.vscode\\Compile.bat",     "isShellCommand": true,     "args": ["${file}","${workspaceRoot}\\a.exe"],     "showOutput": "always" }

Dups #3550.


[Bug] nil type isn't inferred in multiple assignments

Problem
Given this example
local a,b,c = 1

the compiler produces the following AST
[
    VARIABLE {
        local: true,
        names: [
            "a",
            "b",
            "c",
        ],
        values: [
            [
                SYMBOL(
                    "1",
                ),
            ],
        ],
        line: 1,
    },
]

While not invalid the compilation step fails because the compiler can't handle b, c having no assigned value so the actual compilation steps fails
Backtrace
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/main.rs:191:94
stack backtrace:
   0:        0x108823824 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::ha91aabaedad056ac
   1:        0x10883d14b - core::fmt::write::h7f97e3fd364350dc
   2:        0x108820fd8 - std::io::Write::write_fmt::h0e066bfd479ec021
   3:        0x108824dbd - std::panicking::default_hook::{{closure}}::h32539b3840f9f60c
   4:        0x108824b14 - std::panicking::default_hook::hc1eaf31bd9d94572
   5:        0x1088252e8 - std::panicking::rust_panic_with_hook::h2173a17e4bf36be5
   6:        0x1088251ea - std::panicking::begin_panic_handler::{{closure}}::hc31bf00fee812eea
   7:        0x108823ca7 - std::sys_common::backtrace::__rust_end_short_backtrace::h91456626e7de558e
   8:        0x108824efa - _rust_begin_unwind
   9:        0x108848bd3 - core::panicking::panic_fmt::hf9bbc3974c4088ec
  10:        0x108848ab7 - core::panicking::panic::h2554e7c9fbba2a12
  11:        0x1087a6ed7 - clue::main::h1bb9af1451bca2f9
  12:        0x1087aad6b - std::sys_common::backtrace::__rust_begin_short_backtrace::hbaac911544a2b697
  13:        0x1087ae5a8 - std::rt::lang_start::{{closure}}::he990c930998175a4
  14:        0x10881cabe - std::rt::lang_start_internal::h1a04d881dc83f51a
  15:        0x1087a7079 - _main

this will be fixed in the next update
also, the AST seems to come from a different example as it has a, b and c as variables while the example you gave only has a and b

this will be fixed in the next update also, the AST seems to come from a different example as it has a, b and c as variables while the example you gave only has a and b

I copied the wrong example yeah. I edited it with the right one

I tried making this crash happen, but it doesn't
for me Clue just outputs local a, b, c = 1;

since this doesn't seem to happen anymore I'll close it for now

nevermind, it happened now.


compose: Exiting custom profile view closes compose box.

Looking at a user's custom profile before sending a message is pretty natural, and I think we should leave compose open after exiting the modal.

@zulipbot claim


Update global.css with newly designed color palette

What happened?
As we are preparing to transition into our newly developed website redesign, all assets have become outdated and must be updated to the rebranded materials.
Link to new color palette: https://www.figma.com/file/9fVKqPGdURItxIuazrKzKs/Design-Library-v3-Assets?node-id=0%3A1&t=ckVVJBCtQSOY044u-0
Related: #792

Resolved with #797.


Show Emojis used in Chat

If it is possible, can we do it? Example: https://www.opendota.com/matches/3364690481/chat
Note how the Emoji gets shown as . I think it would be neat if it showed the actual emoji that has been entered

Duplicate of https://github.com/odota/ui/issues/1056


SPIKE: Non-graph and linear queries approach for Universal Metadata Search

Description:
Propose a solution to support report stream (RS) universal pipeline (UP) metadata search and test report back tracking with the following requirements:

Conceptually straight forward (no need to leverage graph to describe the concept) for users and implementors
Metadata can be obtained with straight forward SQL (Relational DB) in linear order
Back tracking the origin and transformation / filtering of tests and / or reports can be done with simple SQL in linear time
Underlying tables and their relationships relatively simple, the number of join operations needed to achieve 2. and 3. are minimum

AC:
A proposal is delivered, e.g. as a mark done file under RS repo proposal folder, for team to discuss.
the document includes:

concept description and diagram, use cases
pros and cons
SQL queries for use cases

@JFU-NAVA-PBC Please amend this ticket to use the Platform User Story template via Github.

@JFU-NAVA-PBC Please move to ready for grooming or let me know if we should icebox this story.


Why are the model weights saved at each epoch the same when using DeepSpeed?

Hi @konioy, can you provide more details? We haven't encountered this issue while using Deepspeed.


chore: upgrade knex to 0.95.2

This is a BC, as knex now requires TS 4.1 and a TS bump for us is breaking (new features that are not backcompatible, like template literal types, or the ts-morph support).
Also please stick to the code style and rules in the repo - I don't want namespaced imports (Knex.Transaction etc), and the version should stay pinned as it was (0.95, not ^0.95).
Build is failing, so would be nice if you first get it passing locally (as each push sends an email to me). I would actually expect more changes to be needed...

This is a BC, as knex now requires TS 4.1 and a TS bump for us is breaking (new features that are not backcompatible, like template literal types, or the ts-morph support).
Also please stick to the code style and rules in the repo - I don't want namespaced imports (Knex.Transaction etc), and the version should stay pinned as it was (0.95, not ^0.95).

I pinned the version now. But I don't think named imports work anymore: https://github.com/knex/knex/blob/master/UPGRADING.md#upgrading-to-version-0950

Build is failing, so would be nice if you first get it passing locally (as each push sends an email to me). I would actually expect more changes to be needed...

Sorry I didn't mean to bug you with emails..
I'm actually not sure why the tests are currently failing. So I probably should close the pr :(

Lol I see, what a weird decesion with the namespaces, I guess we will need to live with that. For me this is a bad move, I feel like in TS world namespaces are quite discouraged. Would be great to understand the reason for it...
Let's keep the update for later, I am planning to start with v5 quite soon (let's say in few weeks).


Duplicate key

Raise a runtime warning if a key is bound with KeyBinder that already has a binding.

Tracking duplicates takes too much effort (just checking when binding doesn't work).


Produce trees in presence of rename/typecheck errors

And allow dev version of GHC

Nice, thanks! (OOC: What are you using ghc-dump-tree for?)

I'm working on https://phabricator.haskell.org/D836 and trying to track
down why some of the rename/should_fail tests are giving the wrong error
message.
I am using it to compare master version of ParsedSource with the one my
patch generates.
On Fri, May 1, 2015 at 10:33 AM, Edsko de Vries<EMAIL_ADDRESS>wrote:

Nice, thanks! (OOC: What are you using ghc-dump-tree for?)
—
Reply to this email directly or view it on GitHub
https://github.com/edsko/ghc-dump-tree/pull/3#issuecomment-98077049.


Permit @auto_hash_equals_cached with mutable struct types.

Either

Require that all declared fields are const, or
Add const to each declared field (with a warning?) if not already declared so.

The advantage of doing this is that we get both an efficient hash code and an efficient equality (because of the === shortcut)
const on a field is only available in Julia 1.8 and later.

The ability to mark fields of a struct with const was added in Julia 1.8.

(The disadvantage is that every field access has to go to the heap. With an immutable struct, fields can be pulled onto the stack or into registers, which can improve the performance of a function that spends a lot of time with those fields.


I can not recover the image from the gradients.

Why can't I reproduce the effect of the paper? According to your code, the image I get is just some disordered pixel blocks, even if I increase the number of iterations.

It should set a little learning rate, otherwise the dlg model will not converge.

应该设置一点学习率，否则dlg模型不会收敛。

能详细说下怎么解决吗


Add vercel.json

This adds a vercel configuration file that does two things, in order of importance:

rewrite all paths to the demo app (not just /)
silence GitHub notifications for new deployes (remove if you actually want them)

I'm not familiar with your Vercel configuration, so it's possible that you need to move this file somewhere else, but by default Vercel looks for it at the root of the deployed repository.

Great stuff!

I wonder if this will deploy actually, since you might need to be a developer on the target Vercel Team for it to accept it?

I wonder if this will deploy actually, since you might need to be a developer on the target Vercel Team for it to accept it?

Not sure I understand the question. This is just meant as a fix so URLs like
https://react-three-rapier.pmnd.rs/kinematics
don't 404.
(I'm assuming that the examples app is being deployed to Vercel. Was this wrong?)

The config is great, but the deployment fails due to it coming from a non-authed user. I am also not added to this project on Vercel, so I'm not sure if this will be accepted by Vercel's deployment bot, unless it is accepted by @drcmda.

I've approved the deployment now! 🙂

And the URL rewrite works 👌


Adds release for automated GitOps triggered image builds for KFServing

What this PR does / why we need it:
This PR enables images built from HEAD. This will be the foundation of our image versioning system. The images will be provided in gcr.io and paid for by Google until further notice.
Special notes for your reviewer:
I was considering going the PROW route, but I'm really not a fan of the kubeflow infrastructure for this. This enables a simple, straightforward, cloudbuilder experience to build images for head.
Of course, our release process will mature over time, but I imagine we being cutting release branches which tag images after successful e2e testing.
Release note:
NONE

This change is

/assign @yuzisun

/assign @hougangliu

No actually. Master is the git branch. I'm intentionally not using latest
since we don't have a safe way to guard it.
On Fri, May 17, 2019, 5:30 PM Animesh Singh<EMAIL_ADDRESS>wrote:

@animeshsingh commented on this pull request.
In config/default/manager_image_patch.yaml
https://github.com/kubeflow/kfserving/pull/99#discussion_r285320882:

@@ -8,5 +8,5 @@ spec:
spec:
containers:
# Change the value of image field below to your controller image URL

 - image: kfserving-controller:latest

 - image: gcr.io/kfserving/kfserving-controller:master

I assume 'master' in context of gcr maps to 'latest' in context of docker?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/kfserving/pull/99?email_source=notifications&email_token=AATXLCG3YTY2MMGYNZEOK5DPV5EZDA5CNFSM4HNYCYTKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOBZAYMSI#pullrequestreview-239175241,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATXLCAINLEJJ5X3Y6G2EWDPV5EZDANCNFSM4HNYCYTA
.

No actually. Master is the git branch. I'm intentionally not using latest since we don't have a safe way to guard it.

If latest is always pushed by a github merge passing the test, what`s the difference?

No actually. Master is the git branch. I'm intentionally not using latest since we don't have a safe way to guard it.

If latest is always pushed by a github merge passing the test, what`s the difference?

The difference is when you run the tests. I think you're right though, we probably would want to run the full suite of integration tests before anything gets through. The only reason you might want to decouple these is if the tests take prohibitively long. This is not a problem for us yet.
I'll make this latest.

Hey all, I've opened up permissions on the Cloud Build resources. Can you confirm you can access them (README.md)

Hey all, I've opened up permissions on the Cloud Build resources. Can you confirm you can access them (README.md)

Cool, I can download the image from gcr.io/kfserving/kfserving-controller:latest !

Can you see the builds page linked in the readme?
On Sat, May 18, 2019, 10:58 AM Dan Sun<EMAIL_ADDRESS>wrote:

Hey all, I've opened up permissions on the Cloud Build resources. Can you
confirm you can access them (README.md)
Cool, I can download the image from
gcr.io/kfserving/kfserving-controller:latest !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/kfserving/pull/99?email_source=notifications&email_token=AATXLCB3J2ZCT37U75EPDVLPWA7VZA5CNFSM4HNYCYTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWTD3Q#issuecomment-493695470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATXLCCDZJGUEMZZRXNPJ2DPWA7VZANCNFSM4HNYCYTA
.

/lgtm

@yuzisun @animeshsingh waiting for approval

/lgtm
/approve

/retest


Re- topic edit typeahead

This is a small tweak to https://github.com/zulip/zulip/pull/14033, I added some changes to typeahead.js, as the first commit, and I removed is_typeahead_open and the tests related to it from @aero31aero 's original PR (also removed details about that helper from commit message), the rest of the commits are unchanged from that branch.
This is still a draft (not merge ready) as the changes I made to the third party typeahead have NO TESTS yet, because I'm not sure where to put them.
Testing Plan:
Need to add tests for changes to typeahead.js

As it now stands, the zjquery commit doesn't have any context for it's addition since we have removed the is_typeahead_open() approach, but it still is a change we should make for zjquery in general.
Thanks @YashRE42 for taking this over.

This was won't fix for a little bit because I had done something that broke form submission, that has been corrected, GIF attached:

Furthermore:
I realized that we don't have any tests for our changes to typeahead.js:
63e2009 (Automated selection)
83cbd62 (Custom selection triggers)
6c34d99 (Header text)
Hence, I've marked this ready for review, since it's a complete change, but I really feel as though we should figure out a way to test changes to this file. It is scary not to.

I'm thinking we should first pull in changes from upstream and since the
project isn't being maintained much now, maybe move this from third to
static/js and maintain it like our own codebase.
I've yet to check if the upstream repository has any tests. If they have,
we can maybe run those as well.
On Sat, Mar 7, 2020, 2:11 PM Yash Rathore<EMAIL_ADDRESS>wrote:

Furthermore:
I realized that we don't have any tests for our changes to typeahead.js:
63e2009
https://github.com/zulip/zulip/commit/63e200997d1a666fc9741236eb476a2eec71c83c
(Automated selection)
83cbd62
https://github.com/zulip/zulip/commit/83cbd62ba13a949c358b77490a7bb6fe514537ec
(Custom selection triggers)
6c34d99
https://github.com/zulip/zulip/commit/6c34d99ad068eb42cc2a21d2012a7580e105127b
(Header text)
Hence, I've marked this ready for review, since it's a complete change,
but I really feel as though we should figure out a way to test changes
to this file. It is scary not to.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/14122?email_source=notifications&email_token=AB5JHVRTYIHMP6VX6FNUPNTRGICEBA5CNFSM4LDMP3OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEODTCJI#issuecomment-596062501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5JHVVWPGPYEQQTO7FAAVTRGICEBANCNFSM4LDMP3OA
.

Closing this in favour of #14033 since @aero31aero is available to handle this again.


[Bug] Build failed with no matching function for call to 'doris::segment_v2::Segment::open

Search before asking

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

Version
master
What's Wrong?
Use docker build failed with:
doris/be/src/olap/rowset/beta_rowset_writer.cpp:392:43: error: no matching function for call to 'doris::segment_v2::Segment::open(std::shared_ptrdoris::io::FileSystem&, std::__cxx11::basic_string&, std::__cxx11::basic_string&, int&, doris::TabletSchemaSPtr&, std::shared_ptrdoris::segment_v2::Segment*)'
392 |         auto s = segment_v2::Segment::open(fs, seg_path, cache_path, seg_id, _context.tablet_schema,
|                  ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
393 |                                            &segment);
|                                            ~~~~~~~~~
What You Expected?
build with no error
How to Reproduce?
Use docker image apache/doris:build-env-ldb-toolchain-latest and run bash build.sh
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

It seems  https://github.com/apache/doris/pull/14058/ fixed the issue


Add ability to register free usernames

Using subdomain registrar at registrar.stacks.co, similar to what we've had in the past for Blockstack Connect and Blockstack Browser.
We have the option of adding this functionality as part of the authentication flow for new users, or post-authentication as a subsequent step.
If you have a need for username registration as part of your app's onboarding flow, please leave a comment below with details about why you need it and how you are using usernames in your app's UX generally.

For Sigle, we require our users to register usernames. With blockstack connect this is something that users have to do when creating a new account.
For the extension, we are fine implementing the registration ourselves in our UI if a simple API is provided for this.
We use usernames to resolve the Gaia storage of a user on Sigle by using the lookupProfile function. It also provides user-friendly URLs when sharing your blog.


react-hot-loader doesn't hot replace changes to react-jss styles

This seems unrelated to https://github.com/cssinjs/react-jss/issues/117 but it may be.
I've set up a minimal repo to show the issue here: https://github.com/cjevning/jss-hot-broken
Essentially, HMR works as expected when changing any component code, inline component styles, or theme values (theme value changes require a full reload, which makes sense), however it fails to replace existing jss styles. Webpack-dev-server is aware of the changes and claims to update the modules, but the changes aren't reflected.
In the example repo above, changing the injected styles for Counter or Counter3 has no effect until refresh, while changing Counter2's inline styles hot swap fine. WDS seems to think all of the changes have been swapped:

Ultimately this may be related more to webpack-dev-server itself, as a similar codesandbox example seems to handle jss style changes, albeit while losing the internal component state: https://codesandbox.io/s/zk29z664ml

#117 is the right issue I think. We still haven't implemented a proper integration, also see https://github.com/cssinjs/react-jss/pull/123


Import / require not working in unit tests

After upgrading my old tests with import module from '../../../../path' no longer work.
I get this error:
Uncaught SyntaxError: Unexpected token import
  at http://localhost:9876/__karma__c:/www/genolab/genolab-frontend/client.js/src/main/webapp/test/unit/shared/manage_frequencies/manage_frequencies.controller.spec.js:5

Similar as the require();
markDuplicatesScript = require('./../../../../app/js/settings/manage_frequencies/scripts/mark_duplicates.script')

 Uncaught Error: Cannot find module './../../../../app/js/settings/manage_frequencies/scripts/mark_duplicates.script'
  at http://localhost:9876/__karma__C:/Users/USER/AppData/Local/Temp/e1aeeef0fb863108c4be5f9b2e98d7bb.browserify:1 <- node_modules/browserify/node_modules/browser-pack/_prelude.js:1:0

Basically I'm trying to include modules which are just scripts that export methods and not services so they cannot be injected.
How can I target those methods?

Good catch! Should be fixed in #164, this was due to test files not being preprocessed by Browserify (or Babel)


disable during testing

Likely unnecessary for testing. Also, preloader may interfere with testem.

It might be not harmfull for headless testem runs, but depending on your preloader styling it might completely break your qunit tests page (http://localhost:4200/tests) as it overlays the preloader over the page with the test results. Just added a PR with a quick fix!


Remove unnecessary code

I think this code is not used.

Coverage remained the same at 100.0% when pulling b601407035ac745da5ab44835355f451b94e27e6 on 38elements:patch-2 into dd7ef5b4b1cc643a84657cc75aea1e23f24b81c3 on developit:master.


Fixed an issue where DnnPlugins package was not being produced

The declaration in thirdparty.json was missed in #5724
Closes #5740

Thanks!


Sometimes dataset list in storage section will have reversed sequence.

Describe the bug
When exporting a document the datasets listed in the storage section 3a will sometimes have a reversed sequence (i.e. P* IDs go from highest to lowest).
Is this a regression?
No.
Steps to Reproduce
Currently unknown how to reproduce.
Expected behavior
The P* IDs of the datasets should always be in ascending sequence.
Example
"P3 (Marekting materials), P1 (Survey whith Horizon Projects) will be stored in..."
Environment

Damap version 2.4.0

could not reproduce. Closing it for now. Can be reopened if such issues surface again.


nightly e2e failed

https://github.com/spidernet-io/egressgateway/actions/runs/5479625454/jobs/9987160041
https://github.com/spidernet-io/egressgateway/commit/d1ce4a91ec6cf406e1117ff9d51ef6b534a9605c
remove the target in CI

Fixed in https://github.com/spidernet-io/egressgateway/pull/547.
We don't need swagger checks, it's not cleaned up the first time


CAMEL-9226 - check metrics are counted correctly in multicast sub-routes

Retrospective test for CAMEL-9226 - check metrics are counted correctly in multicast sub-routes
This problem was fixed in 2.16.0

Didn't realise PRs were dynamic.  Will recreate from a branch with just the relevant changes


fix: simply redirect the /v1 request to albert-api.

Can we merge this @anthonyjacquelin ?

@anthonyjacquelin, thanks.
Could you notify me when this change is propagated to an instance ? Which one do you recommand me to use franceservice.dev.etalab.gouv.fr ?


Added Student Version support

Bug fix in Edb.py Database Opening

We need to document the student_version parameter before merging this in the applicable classes.


Razzberry + pokeball for greatball

In the latest version the pokeball rules have improved. However there's one small thing that I really hope will get improved. When we encounter high cp commons with a catchrate below 35. I believe it will use razzberry+pokeball, however since we encounter high cp commons all the time. the bot uses razzberry very quickly. Leaving the trainer with very low amount of razzberrie. I was wondering if it the razzberry combo could be changed to just a greatball and if it's still too low add razzberry after.
Here's the log
[03:42:50] Something rustles nearby!
[03:42:51]  A Wild Poliwag appeared! [CP 410] [Potential 0.73]
[03:42:51] IV [Stamina/Attack/Defense] = [15/3/15]
[03:42:53] Catch Rate with normal Pokeball is low (33.48%). Thinking to throw a Razz Berry... (88 left!)
[03:42:53] Threw a berry! Catch Rate with normal Pokeball has increased to 50.22%
[03:42:53] Using Pokeball (chance: 50.22%)... (18 left!)
[03:42:56]  Captured Poliwag! [CP 410] [Potential 0.73] [15/3/15] [+210 exp]
[03:43:01] Moving towards fort This is Where The Children Work, 0.05km left
[03:43:06]  Releasing Poliwag with CP 410 and IV 0.73. Matching release rule: CP < 550 AND IV < 0.9.
Hope I posted this in the right place!

Magikarp is VIP pokemon because of IV >0.9, I just don't think razzberry was needed here
[04:28:44]  A Wild Magikarp appeared! [CP 35] [Potential 0.96]
[04:28:44] IV [Stamina/Attack/Defense] = [15/15/13]
[04:28:46]  [-] Magikarp is a VIP Pokemon! [CP 35] [Potential 0.96] Nice! Try our best to catch it!
[04:28:46] Catch Rate with normal Pokeball is low (96.47%). Thinking to throw a Razz Berry... (94 left!)
[04:28:46] Threw a berry! Catch Rate with normal Pokeball has increased to 144.70%
[04:28:46] Using Pokeball (chance: 144.70%)... (19 left!)
[04:28:47]  Captured Magikarp! [CP 35] [Potential 0.96] [15/15/13] [+210 exp]

@Takkwon I think the problem is the way to consider the which one is more important for a player: Great Ball or Razz Berry?
I have an intuition that they are quite equal (according to the loot rate I find in game)?


[EventRequest] Codeunit 1402 Cancel Posted Purch. Cr. Memo - OnTestInventoryPostingSetupOnBeforeGetInventorySetup

Requesting a new event publisher on Codeunit 1402 Cancel Posted Purch. Cr, Memo
Event
OnTestInventoryPostingSetupOnBeforeGetInventorySetup(VAR PurchCrMemoLine : Record "Purch. Cr. Memo Line"; VAR InventoryPostingSetup : Record "Inventory Posting Setup";VAR IsHandled : Boolean)
Code
LOCAL TestInventoryPostingSetup(PurchCrMemoLine : Record "Purch. Cr. Memo Line")
WITH InventoryPostingSetup DO BEGIN

>>> New Code
  OnTestInventoryPostingSetupOnBeforeGetInventorySetup(PurchCrMemoLine, InventoryPostingSetup, IsHandled);
  IF NOT IsHandled THEN

<<< New Code End
    GET(PurchCrMemoLine."Location Code",PurchCrMemoLine."Posting Group");
  TESTFIELD("Inventory Account");
  TestGLAccount("Inventory Account",PurchCrMemoLine);
END;

In Our Solution we create new Locations for evey Job (Job Locations). We do not want to create a new record for every new Job Location in combination to the Posting Group. Therefore we create just one per Posting group without a Location Code. So we can setup accounts per posting groups for all Job Locations with just one record. To Support this we need to get a Inventory Posting Setup Record with a blank Location Code in case of the current Location is a Job Location (Is specified by a field on the Location Table). Please add the Publisher.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Update English strings

Updates the English localized strings file to the generated one that has been provided to the localization team.

Thanks all! @njarecha I've also updated the localization team's copy on the network share export folder.

@dfeinzimer Thank you!


Auth on Collection level

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
Hey guys,
let me first take the opportunity to thank you for building an alternative to Postman.
Today I tried it out and could not get collection wide auth to work.
I setup my concrete GET to "inherit".
Using the collection auth it gives me back a successful token acquiring.
But the collection setting seems not to be taken into account when doing the GET request.
.bru file to reproduce the bug
No response
Screenshots/Live demo link

Works now! I think you should add this to the official documentation (if I have not missed it!)
Once again: Thanks for your work!!


stream settings parent always has a field for children

Previous code throws an exception if the parent is added before any children. The parent node is defined, but doesn't have an object assigned to children. This just adds an additional check.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Support older package installation

uv version: 0.2.30
UV pip compile fails for installation of old python packages
Error:

We recently changed the env variable NO_BUILD_ISOLATION to true and from there we saw this issue
When we were not using the env var it was working as expected
Note that the env was added due to latest breaking setuptools issue (https://github.com/pypa/setuptools/issues/4519)

I have a similar error with django-push-notifications
> [webserver compiler 7/7] RUN uv pip install -p /opt/venv/bin/python --compile --no-cache-dir -r /requirements.txt 'setuptools==71.1.0' --no-build-isolation:
3.430   × No solution found when resolving dependencies:
3.430   ╰─▶ Because django-push-notifications==3.1.0 has inconsistent metadata and
3.430       you require django-push-notifications==3.1.0, we can conclude that the
3.430       requirements are unsatisfiable.
3.430
3.430       hint: Metadata for django-push-notifications==3.1.0 was inconsistent:
3.430         Package metadata version `0.0.0` does not match given version `3.1.0`

I started getting this error only after adding the --no-build-isolation flag while fighting with setuptools 72, without that flag the istall did not give any error.
Now that setuptools 72 has been yanked I have removed that flag and it is working again.
I do not have any local cache and I am not providing any custom URL for that repository.

I am installing aloe from official pypi repo
https://pypi.org/project/aloe/
There can be scenarios with same issue (0.0.0 in version file) but pypi listed version is something else
Can this be handled?
As @sevdog mentioned this is after adding the --no-build-isolation flag
If we don't provide this flag uv pip compile and install works fine

Also one suggestion
While installing uv can it take setuptools, wheel and pip from envs?
Like UV_PIP_VERSION, UV_SETUPTOOLS_VERSION (by default it can be latest)
With this user will have more flexibility over choosing the required versions instead of using latest
And this would have also not affected the setuptools issue that we faced yesterday
References:
https://github.com/pypa/setuptools/issues/4519#issuecomment-2256189683
https://github.com/astral-sh/uv/blob/51b7e9bff1cbf0c8ad18c5447f808176e902db22/crates/uv/src/commands/venv.rs#L278

uv pip install aloe==0.2.0 -n is working as expected for me. Any way I can reproduce?

Maybe the problem was related to setuptools==72.0.0, which was yanked.

Yes
I am also able to install it now
Maybe if we take this ticket issue will also be resolved
https://github.com/astral-sh/uv/issues/5557#issuecomment-2257745704

@charliermarsh
Tagging you if you missed this


GDAL error with this polygon

Warning in CPL_wrap_dateline(x, options, quiet) :
GDAL Error 1: TopologyException: Input geom 0 is invalid: Self-intersection at 24.216398416915379 68.517368722058578
sh_geocat_20230214 (1).csv

Double-checked this, its not really a error with geocat or the data or the algorithm. The convex hull is correct but projected across 180. Not sure we can do anything with these almost impossible polygons which do not fit 2d map when they are largely 3d! needs to be moved to rcat 2, but as this projects the data its unlikely to be solved.


Patch varnish vulnerability

Motivation for this change
https://nixos.org/releases/nixpkgs/nixpkgs-0.12/manual/
Things done
Please check what applies. Note that these are not hard requirements but merely serve as information for reviewers.

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Maybe better to upgrade 5.1.2 -> 5.1.3 than include the patch ?

We're not able to upgrade to 5.1.x on the stable 17.03 at this time, and 5.0.x isn't receiving any additional patching.

ah, it is 17.03. missed that


Span Sort

Fixes #186
Information
Provides Span Sort.
Proposed Changes

Sort based on .Net introspective sort.

Please fix the CodeFactor issues before merging


Warning message from HA suggesting alternative call

**Describe the bug **
Warning message from HA suggesting alternative call
**Screenshots / Logs / Pcap File **
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:565
First occurred: 10:24:17 AM (1 occurrences)
Last logged: 10:24:17 AM
Entity climate.garage_ac (<class 'custom_components.midea_ac.climate.MideaClimateACDevice'>) is using self.async_update_ha_state(), without enabling force_update. Instead it should use self.async_write_ha_state(), please report it to the custom integration author.
Versions (版本信息)

Home Assistant version: 2023.6.3
Midea msmart version: 0.2.3

This issue is resolved in my updated fork mill1000/midea-ac-py

Excellent! I just switched over. Thank you!

Make sure you update msmart as well to get all the features.
e.g. In your HA system/container/env
pip install git+https://github.com/mill1000/midea-msmart.git@future

Make sure you update msmart as well to get all the features.
e.g. In your HA system/container/env
pip install git+https://github.com/mill1000/midea-msmart.git@future

I did this and now my cool mode is not an option in the drop down

Ah, that can happen if (for some reason) the device doesn't report the correct capabilities.
You can work around this by manually adding the cool mode in the integration configuration like so

That worked! And no warnings or errors in my logs.
Off topic, but have you fixed the issue with devices being unresponsive due to having multiple client instances?
In my case I'm using Carrier's app and HA... https://github.com/mac-zhou/midea-ac-py/issues/95#issuecomment-1631598926

Unfortunately, most of the underlying network code is unchanged so this will probably still be an issue
What are you using the carrier app for that this extension can't do?

I'm using it to configure schedules and I'm not aware of this extension supporting it.

 Now I'm trying to recall exactly why I relied on the carrier app... I think a while ago the extension or my system was not reliable so I depended on carrier's cloud service. I need to reconsider this

| I'm using it to configure schedules and I'm not aware of this extension supporting it.
...
| I know that sounds idiotic considering I can use HA to automate my own schedules. Now I'm trying to recall exactly why I relied on the carrier app... I think a while ago the extension or my system was not reliable so I depended on carrier's cloud service. I need to reconsider this
Hahaha that's alright. Might be worth ditching the Carrier app for a little bit just to see if it makes the integration more reliable. If its still flaky then the integration won't be of much use will it.


Manage version bump of EpiNow2

We need to move to a newer release, once we have deterministic output

Adding that the new version expects a 0-indexed GI, which will be another breaking change. See: https://github.com/cdcent/cfa-parameter-estimates/issues/48#issuecomment-2383113839


When enabling InfiniBand on the ND40rs_v2 VM, please use the 4.7-<IP_ADDRESS> Mellanox OFED driver.

Important sections says:
When enabling InfiniBand on the ND40rs_v2 VM, please use the 4.7-<IP_ADDRESS> Mellanox OFED driver.
I believe 4.7-<IP_ADDRESS> was the latest version of the driver at the time of writing, but current version is 5.1-<IP_ADDRESS> according to https://www.mellanox.com/products/infiniband-drivers/linux/mlnx_ofed
MLNX_OFED-5.0-<IP_ADDRESS> driver is used in the example which InfiniBand points to,
Should article say
please use the 4.7-<IP_ADDRESS> or later Mellanox OFED driver.
instead of
please use the 4.7-<IP_ADDRESS> Mellanox OFED driver.

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

ID: 74427887-6734-a054-8c88-d63b8f4db064
Version Independent ID: a2f1b4f2-18b5-7708-a629-82ca1d10b712
Content: NDv2-series - Azure Virtual Machines
Content Source: articles/virtual-machines/ndv2-series.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @vikancha-MSFT
Microsoft Alias: jushiman

Thanks for the feedback! We are currently investigating and will update you shortly.

@VladimirKhvostov I've routed your issue to the doc author to made the doc edit. Thanks for bringing up the issue.

@Karishma-Tiwari-MSFT please assign this to @iafinder

Assigning to @iafinder

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close