[Bug 2.3] Local aggregation root is searched to set the version

I think this peace of code from the SetMojo.java is not correct.
final MavenProject project = PomHelper.getLocalRoot( projectBuilder, getProject(), localRepository, null, getLog() ); getLog().info( "Local aggregation root: " + project.getBasedir() );
I end with my all project modified despite I only wanted to change a one maven module. It automatically searches for the local aggregator root which I think it should not.

I think that the local agregator is not used directly to define what projects will change.
If you want to change the version of one project only, make the maven call from that project. If the version is inherited from a parent pom, you can make the maven call from the parent pom and use the -pl  to change only the version of that specific project.

I do think it is used because I changed that piece of code to getProject and only the local pom and all the other modules it defined are changed.  You cannot assume automatically that I want to change the whole hierarchy of my maven project everybody is free to organise it as it wishes and my pom versions are evolving independently.  So I think it is a bug.  Because I have no easy way to get around this behaviour.

This is also problematic for me. I have a fork of two-module project living under a parent in the repository. Both modules inherit from the Spring Boot parent and NOT the reactor that is aggregating them. When trying to versions:set when in a module directory I see:
[INFO] --- versions-maven-plugin:2.3:set (example) @ server ---
[INFO] Searching for local aggregator root...
[INFO] Local aggregation root: /Users/jlebc/Projects/example
[INFO] Processing change of example:server:0.0.1-SNAPSHOT -> 0.1.0-SNAPSHOT
[ERROR]
java.io.FileNotFoundException: /Users/jlebc/Projects/example/server/server (No such file or directory)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:195)
        at java.io.FileInputStream.<init>(FileInputStream.java:138)
        at org.codehaus.plexus.util.xml.XmlReader.<init>(XmlReader.java:124)
        at org.codehaus.plexus.util.xml.XmlStreamReader.<init>(XmlStreamReader.java:67)
        at org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:118)
        at org.codehaus.mojo.versions.api.PomHelper.readXmlFile(PomHelper.java:1606)
        at org.codehaus.mojo.versions.AbstractVersionsUpdaterMojo.process(AbstractVersionsUpdaterMojo.java:321)
        at org.codehaus.mojo.versions.SetMojo.execute(SetMojo.java:298)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

And this is invoked from /Users/jlebc/Projects/example/server. Notice the duplicated module directory.

I think I am running into the same problem as @dweomer. Has anyone found a workaround for this?

I should also note that I see the exact same failure when invoking from the parent directing but specify the module via the -pl / --projects switch.

Does someone has an example project for that?

@khmarbaise, please find a sample project attached:
issue82.zip

i run into this problem as well when using gitflow-maven-plugin which uses versions-maven-plugin internally to update the versions in the released artifacts.
due to this bug other versions in the same git repository but outside the directory/module structure that is released are (automatically) modified as well and are part of the release commits.
in PR #400 i've added an IT for the problem and a fix - i've just removed the lookup of parent POMs to do the change - it makes no sense in my POV and none of the other ITs relayed on it.

I haven't fully gone through all the details above, but our project is now broken upon upgrading to v2.8.1 that contains the fix #400
We have a setup:
/project-root/pom.xml
    /parent-pom/pom.xml
    /module-1/pom.xml
    /module-2/pom.xml

Where module-1 and module-2 inherit from parent-pom.
On v2.7 running mvn versions:set --projects parent-pom -DnewVersion=x.y.z bumps the version in parent-pom/pom.xml and also in the <parent> element of module-1/pom.xml and module-2/pom.xml.
On v2.8.1 the same command only bumps the version in parent-pom/pom.xml.

@sirianni  you're right - this is no longer working. in my pov the new behavior is correct - with the --projects command you define maven to execute on the child module "parent-pom", and it operates also on siblings of it.
but of course it see that your use case makes sense. did you check if any of the other goals can be used instead?
https://www.mojohaus.org/versions-maven-plugin/
alternatively we might think about adding a new switch to this goal that restored the previous behavior, but only if explicitly wanted as it can lead to unexpected results in other scenarios (that's why this bug exists).

I think this change should be reverted as it breaks for my use-case.  I have checked the other goals and none of them seem to work, I tried the update-parent goal but all it says is 'Project's parent is part of reactor' or 'Project version is inherited from parent' and no changes are made to the pom.xml
For now I have reverted back to v2.7.
This issue is tracked in #426

see my comment in https://github.com/mojohaus/versions-maven-plugin/issues/426#issuecomment-676209416 - would this help for you?


Fps unlocker doesnt work for me, i am on latest version for both genshin and the fps unlocker

#439


✨ Integrate Where do you want to go today

Cc: @kikibianc @AttackOnMorty @adamcogan

Pain

Request from @kikibianc:

As per our chat, I am giving this task to the SophieBot team. In the past, Patrick tested QnaMaker with our "Where do you want to go today" page at https://sswcom.sharepoint.com/SitePages/where-do-you-want-to-go-today.aspx and it worked nicely.
With SophieBot on a new framework now, I believe this task can be revisited to add that page to our SophieBot.
Questions like:

Where is the intranet?
Where is CRM?
How to see reports?

Should be answered based on that page

SSW has a nice "Where do you want to go today" page acting as a navigation entry for the intranet. As per request from @kikibianc and @adamcogan, we need to integrate the data on that page into SophieBot queries.
Suggested Solution

Create Qna service for static content like this

Tasks

[x] Investigate on the data source
[x] Create Qna service
[x] Implement dialogs for asking about intranet, e.g.

Where is the intranet?
Where is CRM?
How to see reports?

More Information

See "Where do you want to go today" page at https://sswcom.sharepoint.com/SitePages/where-do-you-want-to-go-today.aspx
Thanks!

Done -  Implemented QnA service to access "Intranet | Where do you want to go today?" in the SophieBot

Figure: Exmples of response from the SophieBot regarding "Where do you want to go today?"

Done -  Implemented QnA service to access "Intranet | Where do you want to go today?" in the SophieBot

Figure: Examples of response from the SophieBot regarding "Where do you want to go today?"

As per the feedback from Adam, System Admins and other teams members, there are some changes in this query in order to make responses consistent and hide sensitive information.

[ ] Make all links to the actual URL in the response of "Where is the SSW DevOps?".

Figure: SophieBot Response when you ask "Where is SSW DevOps?".

[ ] Hide password manager information.
[ ] Hide UNC.

As per the conversation during Sprint Review, we have to investigate how we can manage confidential information such as Google Accounts, Password Manager name and UNC's.

[ ] Investigate.

As per the conversation, the source should be clickable to the "Where do you want to go?" SharePoint Page for each response of the QnA.

Figure: Make this source clickable.

[ ] Action.

As per the conversation with Adam and Jean, we need to dynamically get QnA content from SharePoint instead of adding them through the .tsv file.

[ ] Investigate how you can achieve the result.
[ ] Implement it.

Done – It is no longer hardcoded. SophieBot works with QnA Maker and automatically refreshes content from SharePoint now using Power Automate flows.


ARM64 compilation issues in Visual Studio 2022

Required Info

Camera Model
D415

Firmware Version
I don't know

Operating System & Version
Win 10

Kernel Version (Linux Only)

Platform
Android

SDK Version
2.50

Language
C#

Segment
others

Issue Description
I'm trying to compile the library to ARM64, because we need this library in order to connect to a Intel Realsense D415 connected to an Android Device. As such, we are building a mobile application using Xamarin, by project requirements. At this time, it will be a big step to just execute a simple example demo code in the mobile app using C#.
However, when i run the application, in logcat, I see the following error:
[DOTNET] System.TypeInitializationException: The type initializer for 'Intel.RealSense.Context' threw an exception.
[DOTNET]  ---> System.DllNotFoundException: realsense2
[DOTNET]    at Intel.RealSense.Context..cctor()
[DOTNET]    --- End of inner exception stack trace ---
[DOTNET]    at mauiExample.Fragments.RealsenseFragment.OnViewCreated(View view, Bundle savedInstanceState) in C:\Users\juan.avendano\Codes\Thales\Singapur\mauiExample\AndroidProject\Fragments\RealsenseFragment.cs:line 28
[DOTNET] System.DllNotFoundException: realsense2
[DOTNET]    at Intel.RealSense.Context..cctor()
Having this code in a simple fragment:
        try
        {
            Context ctx = new Context(); // ***LINE 28 ***//
            var list = ctx.QueryDevices(); // Get a snapshot of currently connected devices
            if (list.Count == 0)
            {
                textViewtest.Text = "No device detected. Is it plugged in?";
                return;
            }
            Device dev = list[0];
        }
        catch (Exception ex)
        {
            textViewtest.Text = "Error Initializing Camera. See Logcat for error.";
            Console.WriteLine(ex);
            Console.WriteLine(ex.InnerException);
            return;
        }

I was checking my compiled SDK in visual studio, and i see that realsense C# library is telling there is an error with realsense2 C++ project:
Warning: The project 'realsense2' cannot be referenced. Intel.RealSense

And I think this is happening because the SDK compilation does not end correctly because there are some headers which needs to use only X86 or X64 architecture, no ARM64.

Severity
Code
Description
Project
File
Line
Suppression State

Error (active)
E0035
#error directive: This header is specific to X86 and X64 targets
realsense2
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include\emmintrin.h
20

Error (active)
E0035
#error directive: This header is specific to X86 and X64 targets
realsense2
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include\emmintrin.h
28

It also happends in:
realsense2	C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include\mmintrin.h	17
realsense2	C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include\pmmintrin.h	16
realsense2	C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include\tmmintrin.h	10
realsense2	C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include\xmmintrin.h	27
Example:

I have seen similar issues in other libraries googling, and the problem usually is that the compilation in ARM is not well tested. But maybe there is something i can do to override this issue.
And of course im selecting the correct build:

Thanks in advance.

Hi @juamar  I should first highlight that you are the first RealSense user I know of who has actually used VS 2022 with the librealsense SDK and so there is no previous information about how well librealsense works with that VS version.  The most commonly used VS before 22 is VS2019.
Furthermore, librealsense is typically used with Arm devices that have Linux installed (e.g Ubuntu 18.04 on Nvidia Jetson, or the Linux Debian-based Raspberry Pi OS on the Arm-based Raspberry Pi).  Windows is not usually used with librealsense on Arm devices.  so that represents another unknown factor.

The closest project that I know of to your description is one where the C#-based Unity engine was used with a RealSense D435i, Windows, the RealSense Unity compatibility wrapper and the RealSense Android wrapper to connect to an Arm / Android based Oculus Quest VR headset.
https://github.com/GeorgeAdamon/quest-realsense
In this way, C# code in Unity was able to be used with an Android-based device (the Quest headset) and a RealSense camera.
If use of Xamarin is currently a requirement of your project though then it is difficult to see how it could be used with the above project, since the C# code would be being input into Unity.

I'm still having the same issues in VS2019. I did a new Make-Generate with CMake for this version of VS and ARM64, but this time left the VS Solution generated with .NET Framework 3.5. Previously i changed the configuration to .NET 4.8 as proposed by VS.

Still, i made a quick read to the quest-realsense, i think this can be usefull, i will also try do it that way, but i think it will be better and more efficient by architecture if i can discard using Java in my xamarin app. This can be an unnecesary step in the app architecture.
I'm not quite sure about compiling the library in linux, because i need Xamarin solution to access it, and for that i need a DLL (Maybe it can be done, but is it really necessary?).

Just to try something different (and at least check error given when trying to load a X64 library into ARM64) i was trying to generate de C# wrapper for X64 arch. The thing as, althought VS tells it successfully compiles and no Errores givven, i still have the  realsense2 warning icon next to the reference.

i 've tried to delete it, but when i do, I get the following error:

The Windows aspect of the setup complicates things a bit.  If Linux was being used to build librealsense on an Arm device such as Nvidia Jetson or Raspberry Pi then I would typically suggest building the SDK from source code using CMake and including a flag called RSUSB_BACKEND set to True.  On Windows though, a CMake source code build is typically done though a CMake GUI interface, as described in the link below.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_windows.md
My research did locate a reference about compiling on Windows for Arm64 at https://github.com/IntelRealSense/librealsense/issues/9173

Hmm... https://github.com/IntelRealSense/librealsense/issues/9173 it's not the same issue. I was hoping to at least reach that error XD

RSUSB backend is most often used with Linux builds of the SDK, as it bypasses Video4Linux so that a build is not dependent on Linux versions or kernel versions and does not require patching.  On Windows the RSUSB backend flag is usable too, but instead replaces Windows Media Foundation as the backend of the build, as described in https://github.com/IntelRealSense/librealsense/issues/8526
I do not know how to check if the DLL is loaded, unfortunately.
In the RealSense C# wrapper, the files realsense2.dll and Intel.RealSense.dll are placed next to your application, as described in the C# wrapper documentation.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/csharp#building
Have you got these files in the same location as your application?
If you have installed the full RealSense SDK on Windows then pre-built versions of these files that you can simply copy and paste instead of compiling them yourself are provided at:
C: > Program Files (x86) > Intel RealSense SDK 2.0 > bin > x64

Okey, your appointment is interesting. I was not taking in consideration that you should have two dlls next two each other. But still i'm not being able to build realsense2.dll for ARM64 architecture, and as Intel.RealSense.dll depends on realsense2.dll, i'm neither being able to build Intel.RealSense.dll for the exposed Arch.
I think this ARM64 build should be able to be done using VS and windows on a X64 host.
Maybe someone else can review this issue or explain why this does not make sense (maybe i'm missing something).
Thanks in advance

My current understanding of Arm64 support is that it can be installed on Linux for Ubuntu 16.04 and 18.04 but not for Ubuntu 20.04 at the time of writing this, as described in https://github.com/IntelRealSense/librealsense/issues/9040#issuecomment-847442449
There are plans to provide Arm64 package support for Ubuntu 20.04 as part of a future update to the networking API, though I do not have a time estimate for when it will be released.
I do not have information about Arm64 compilation of librealsense on Windows though.

Because of @MartyG-RealSense recomendation, i started to research about binding Android Libraries into my Xamarin App inpired by this:
https://github.com/GeorgeAdamon/quest-realsense
What i finally did was to use a Xamarin Android library binding with the AAR Intel Realsense Library for Android/Java and call it from  the C# code. It works pretty well, but i don't know if this will be the best options for our needs, since we need to integrate some previous project which was made using the C# Intel Realsense Library, which keeps giving me the same result no matter what architecture, emultor, or android version i use.
[DOTNET] System.TypeInitializationException: The type initializer for 'Intel.RealSense.Context' threw an exception.
[DOTNET] ---> System.DllNotFoundException: realsense2
[DOTNET] at Intel.RealSense.Context..cctor()
[DOTNET] --- End of inner exception stack trace ---
[DOTNET] at mauiExample.Fragments.RealsenseFragment.OnViewCreated(View view, Bundle savedInstanceState) in C:\Users\juan.avendano\Codes\Thales\Singapur\mauiExample\AndroidProject\Fragments\RealsenseFragment.cs:line 28
[DOTNET] System.DllNotFoundException: realsense2
[DOTNET] at Intel.RealSense.Context..cctor()
Even i tried to call the API Version first from Contect, some KISS data, but same result!
Maybe will be nice to open a new issue more focused on this matter rather than the ARM64 compilation (which maybe can be sorted out with linux).
If what i'm pretending to do it's not meant to be (only the Android/Java library is expected to work there) maybe we will have to think in some adapter.
Thanks in advance!

It's excellent news that you made significant progress in a Xamarin-based approach, @juamar  :)
I found a C# case at https://github.com/IntelRealSense/librealsense/issues/7037 that seems to be relevant to the Context-related error that you are receiving.

Okay, so i've made myself with a Debian Virtual Machine, and i'm trying to compile realsense2.dll for ARM64, but i'm not being able to compile, i'm getting this error when executing the following command:
$ cmake -S ../ -DFORCE_RSUSB_BACKEND=true -DBUILD_SAHRED_LIBS=true -DBUILD_TOOLS=true -DCMAKE_GENERATOR_PLATFORM=ARM64
CMake Error at CMakeLists.txt:3 (project):
  Generator

   Unix Makefiles

  does not support platform specification, but platform

   ARM64

  was specified.

CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!

What am i  missing? maybe i need some other generator?
I have already seen https://github.com/IntelRealSense/librealsense/issues/9173 and https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md.

I note that your CMake instruction has a typing error: -DBUILD_SAHRED_LIBS=true.  It should be SHARED rather than sahred.

Same error with typo fixed. thanks for the appointment XD

Now no -S and same error:
$ cmake ../ -DFORCE_RSUSB_BACKEND=true -DBUILD_SHARED_LIBS=true -DBUILD_TOOLS=true -DCMAKE_GENERATOR_PLATFORM=arm64
CMake Error at CMakeLists.txt:3 (project):
  Generator

    Unix Makefiles

  does not support platform specification, but platform

    arm64

  was specified.

CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
See also "/home/javendano/codes/librealsense/librealsense/buildArm64/CMakeFiles/CMakeOutput.log".

When performing a CMake build for Arm64 on Jetson, a RealSense team member has previously suggested in https://github.com/IntelRealSense/librealsense/issues/5618#issuecomment-575113313 to put an override at the start of the CMake instruction.
override_dh_auto_configure: dh_auto_configure
Whilst you are not using Jetson, it may be worth trying the above method.

Finally, On friday we have decided to proceed using the Xamarin Android library binding with the AAR Intel Realsense Library for Android/Java and desist of compiling the realsense2.dll for ARM64. It was getting pretty hard to reach that point. I was starting to deploy some QEMU Emulators in order to run the compilations, but still no luck.
I had gotten stuck when launching ./scripts/patch-realsense-ubuntu-lts.sh with some Ubuntu Server image because uvcvideo driver was not being found at some step. So i was trying to install a full Ubuntu Server or a Desktop in QEMU, till time run out.
All compilation procedures are expected to be done in the same device you have the Intel RealSense Camera connected. Trying to get out of that flow can be really tought (unless you use the Android Library).
Thanks @MartyG-RealSense for your help!


[Feature] Enable controller and apiserver to write logs to file path

Search before asking

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

Description
Currently, we use stdout to catch control plane logs. This is inconvenient under some cases. Alternatively, we want to dump logs to a file path and use log shipper to send to remote logging system like ELK etc.  So the ideal way is we both write logs to stdout and file.
Use case
As a user, I want to ship my logs to the logging system.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

/cc @Basasuya

This seems --  writing to disk could be enabled by an option in the operator entrypoint.

My preliminary conclusion is that using klog to write to file and stdout.
I will research on the writing file feature of  klog

sgtm
Let's just make sure not to alter the default behavior. (So by default, don't write to disk.)

After testing, I found Dockerfile is using gcr.io/distroless/static:nonroot as based image, which can not exec into the container. Writing to file is meaningless because I can not see them.
So should we use swap the based image?
\cc @Jeffwan @DmitriGekhtman

This issue is resolved by #632. Close it.


Default Experience on Tools is WAY TOO High!

The default in the configs is set to 20,000! Which would require 20,000 blocks to be mined to gain a SINGLE level on the tool, (not to mention the minimum multiplier is 2x, meaning each additional level is DOUBLE as much XP required), was this a typo as a few of the tools are set to "2000" and "2500" respectively?
Also, can you make the configs adjustable on the fly or at the very least compatible with the "/relaodConfigs" command?
Having to wait 8-12mins after restarting the entire client, just to change some small values, isn't right.

Default base XP is 500 per this line of code, you sure you are seeing 20000, and you did not set that value yourself/your modpack maker set it?
As for a config reload command, once you have the config set up you will not need to reload anymore, will you? Pretty sure there is no forge reload config command by default, some mod is likely adding that for you.


Use nix infra for ci.yml jobs

This refactors ci.yml to make it use the new nix infra.
This should make it considerably easier to reproduce
the CI results locally.
This closes #2627.
Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Ready for review! There is quite some trickiness with running the tests as root, but at least it's all in one place and well documented with comments now. Other than that, I think this greatly simplifies the CI and makes local runs a breeze.
I intend to look at simplifying the embedded CI next.

Ack on both high level comments. Will update this PR when https://github.com/iovisor/bpftrace/pull/2712 and #2714 are in.

Did a final rebase to make sure no breakage occurred.


Revert "Update kernel version of ubuntu microkernel to 3.16.0-25-generic."

Reverts RackHD/on-tasks#108
Per @benbp and @stuart-stanley reverting this PR - to be re-introduced later so as to avoid some internal EMC logistical issues.

+1

*** BUILD #78 ***
Test Name: test_node_workflows_post
Error Details: valid != succeeded
-------------------- >> begin captured logging << --------------------
urllib3.connectionpool: INFO: Resetting dropped connection: localhost
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 0 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 1 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 2 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 3 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 4 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 5 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 6 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 7 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 8 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 9 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 10 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 11 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 12 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 13 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 14 sec(s)
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 15 sec(s)
tests.workflows_tests: INFO: Timed out after :15
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/usr/local/lib/python2.7/dist-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/usr/local/lib/python2.7/dist-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/usr/local/lib/python2.7/dist-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/var/lib/jenkins/jobs/on-tasks/workspace/RackHD/test/tests/workflows_tests.py", line 138, in test_node_workflows_post
    assert_equal(status,"succeeded")
  File "/usr/local/lib/python2.7/dist-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
'valid != succeeded\n-------------------- >> begin captured logging << --------------------\nurllib3.connectionpool: INFO: Resetting dropped connection: localhost\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 0 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 1 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 2 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 3 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 4 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 5 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 6 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 7 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 8 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 9 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 10 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 11 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 12 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 13 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 14 sec(s)\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 15 sec(s)\ntests.workflows_tests: INFO: Timed out after :15\n--------------------- >> end captured logging << ---------------------'

^^ known issue with workflow test.. @tannoa2 is looking into it.

merging with verbal :+1: from @benbp


Q: Support for queryParam() and formParam() with default values - removed in 4.x API

Effectively #1291 introduces a breaking API change for queryParam() and formParam() that take a default value.
Previous API was:
      String myParam = ctx.queryParam("my-param", "one");

I believe this now needs to use a Validator and needs to be written as:
      String myParam = ctx.queryParamAsClass("my-param", String.class).getOrDefault("one");

Is that correct, have I missed something?
Noting that for people like myself that prefer external validation and are not interested in using Javalin Validation this API change appears to be a step backwards. Noting that it is pretty common for queryParam and formParam to have default values and this is now incurs some extra runtime overhead along with a difference in style when a default value is desired.
Maybe I have missed something. It looks to me like the API for queryParam/formParam that takes a  default value as String could be re-instated for backward compatibility given the queryParamAsClass() validator approach of 1291. What are the thoughts on that?
Thanks, Rob.

Personally, I'm fine with the new syntax and didn't find it very hard to switch (https://github.com/thomasboyt/jam-buds/pull/97/commits/2d2f1409170995402a767818da389f8ff42097bb). That said, I absolutely think it should be pointed out in the migration guide - while it mentions the new getOrDefault and allowNullable, it does not mention the removal of getOrNull() or queryParam(key, default).

Added to docs!

I'll close this for now, but would be willing to consider xyzOrDefault methods if someone wants them enough to provide a PR.


Headers instance is turned into an array

Something is turning Headers { 'content-type': 'application/json' } into [ [ 'content-type', 'application/json' ] ] in node.
To be more specific
  const request = new Request(resource, {
    headers: new Headers(headers),
  })

  await fetch(resource)
  // resource.headers is now an array

Hi, @hugomrdias. Can you provide a reproduction repo please?
If request.headers is not an instance of Headers, there's a chance your environment is broken. If Interceptors is the one breaking it, I'd be happy to look into the repro and fix the issue.
We've got a sufficient test suite to claim that we don't modify request.headers to be a different type out of the blue.

starts with msw 2.4.4 and interceptors 0.35

these fail if i update msw
https://github.com/hugomrdias/iso-repo/blob/main/packages/iso-web/test/request.test.js#L298-L332

pnpm test:node inside iso-web package ( https://github.com/hugomrdias/iso-repo/blob/main/.github/CONTRIBUTING.md )
Just fails when getting a header with request.headers.get() which fails cause it's an array
Yeah

Already tried to strip any trace of MSW and it works as expected also the same tests in a real browser works as expected. There's no weird envs here just straight node and reals browsers.
Pinned MSW to 2.4.3 and it's working now but 2.4.4 fails as I said previously.
As a side note the MSW folder inside iso-web may be interesting to you it's a wrapper to MSW to make the setup API the same for browser and node.


when I add cv's row , why can't I insert property

row = cv.collection.add_row()
row.name = 'name'
row.Status = 'New'
row.title = 'why'

when I run this code, cv's row added normal
but property didn't insert Why??

I Confirm Success when I change property's name to lower case
Why Can't use upper case

The property names, when accessed as attributes on the record instance, are "slugified", which makes them lowercase and replaces special characters and spaces with "_".
To make it a bit more tolerant, I've added some normalization code in https://github.com/jamalex/notion-py/pull/88 that will go into an upcoming release, which will allow varied case when setting attributes.


An L1  should be able to resume a CAR transfer from another L2 if it's original L2 disconnects midway through a transfer

The transfer resumption feature is important given the flaky connectivity of resouce constrained L2s.
It is important to note that an L1 should never have to download the blocks/part of the CAR file it already has.
We should engineer this feature in such a way that it only needs work on the L1 and L2s are completely stateless and context-in-aware. They way to do this is by L1s constructing the selector/byte-range for a transfer based on the content it already has.

This is done in L2s. Now we need to build the L1 client functionality.


Clarified plugin directory header

Fixed header to make it more clear plugin directory is either 0.13 or 1.0.

Merged. Thanks!


Recommendation on supporting int64/long values

The following discussions cover the issue of why a json-schema integer cannot be used to represent int64 or long numbers:

https://github.com/json-schema-org/json-schema-spec/issues/574
https://github.com/json-schema-org/json-schema-spec/issues/361
https://github.com/OAI/OpenAPI-Specification/issues/704

Is there a recommendation on how to define a schema that needs to support integers that support the full spectrum of int64/uint64?
The approach mentioned in the json-schema repo discussions has been to use strings and enhance the format support for such integer/decimal types. A reference approach taken by Google (https://developers.google.com/discovery/v1/type-format) follows a similar line however the format types used are not yet part of the standard.
Until a new draft of the spec is published to introduce these new formats, it would be good to have a recommendation in place.

Well, JSON Schema is not the real problem, actually. JSON Schema has a type integer which says the Number does not have a fractional part. JSON itself from a syntactic perspective is not a problem, either: The Number production just defines how a number must be formatted.
The real problem comes from interoperability and this mostly from the way JavaScript is defined, see for example the June 2018 revision specification of the JavaScript Language Number Type, which is based off of double-precision 64-bit format IEEE 754-2008. So factually only 53 Bit integer Numbers can be precisely represented in any compliant JavaScript implementation.
IMHO the discussion in JSON Schema issue 361 provides the best approach to this problem: Using a string type with a format specification.
For example extending the JSON Schema Validation specification with new sections as follows:

6.2.X precision
The value of "precision" MUST be a number, representing an inclusive upper limit on the number of places for the fraction part of a numeric value.
If the instance is a number or a string with format decimal, then this keyword validates only if the instance's numeric value is less than or exactly equal to "maximum".
7.3.X. Decimals
These attributes apply to string instances.
decimal
: A string instance is valid against this attribute if it is a valid JSON string representation of a JSON Number according to the RFC 8259, section 6 number production without the exp part.
integer
: A string instance is valid against this attribute if it is a valid JSON string representation of a JSON Number according to the RFC 8259, section 6 number production without the fracand exp part.
The intent of the decimal and integer formats is the ability to represent exact decimal (and integer) values exceeding the limitations imposed by double precision IEEE754 numbers underlying numberand integer typed values.
The validation keywords of Schema Validation section 6.2 apply to the numeric value of the string.
Note: Technically an integer is a decimal with a zero precision. But in the interest of readability and ease of use, the integer format is also defined.

Likewise the JSON Schema meta schema would need to be extended:
"nonNegativeInteger": {
    "type": [ "integer", "string" ],
    "format": "integer",
    "minimum": 0
},
...
"multipleOf": {
    "type": [ "number", "string" ],
    "format": "decimal",
    "exclusiveMinimum": 0
},
"maximum": {
    "type": [ "number", "string" ],
    "format": "decimal",
},
"exclusiveMaximum": {
    "type": [ "number", "string" ],
    "format": "decimal",
},
"minimum": {
    "type": [ "number", "string" ],
    "format": "decimal",
},
"exclusiveMinimum": {
    "type": [ "number", "string" ],
    "format": "decimal",
},
"precision": { "$ref": "#/definitions/nonNegativeInteger" },

We could add this to our meta schemas already today as an extension to the standard JSON meta schema.

@fmeschbe - What about just copying the approach of Google and instead define int64 values (or long) as type:string and we then introduce a new format value of "int64". We would update our exiting data validators to know how to interpret this new format value.
Whatever we decide, we need to update the table here ASAP so users can define the fields correctly.

Technically speaking the value range of int64 compared int54 is only 1000 times larger (9E18 as compared to 9E15). I don't think we buy us much with a format=int64.

So it would be easy to just define a subschema for int64 with appropriate minimum and maximum values.
All in all, I am not sure the story will end with int64 but with the format=(decimal|integer) proposal we are open to all needs.

I'm a bit confused here...
The JSON Schema spec, as referenced, is very clear that NUMBER/Integer is arbitrary precision - which means that there is no need to specify if it is a "short" or a "long" integer.  Clients will handle it as they are able to (though we should, of course, be sure to update our docs to make that clear to clients).
Using strings for numbers is just bad/wrong (esp. for security concerns) and we shouldn't be supporting that, except as a last resort.  I am going through this same issue with the AEM Forms team and their desire to add "big decimal" support to PDF forms.

Hi @hiteshs do we have a specific case where a 64-bit integer is required, and a 53-bit integer is not sufficient?
As you and others have noted, there simply isn't an interoperable way to represent the full range of a 64-bit integer in Javascript/JSON.  Anything we define is going to be limited to processors that understand our proprietary extensions, and have the capability to operate on the extended range.  So we need to consider the implications.
A proprietary 64-bit integer format is only going to be useful in cases where integer values are used, 53-bits is too narrow, but the values never exceed 64-bits.  (This is also assuming a signed value...is the need for an unsigned value?)  I'm not sure what cases this applies to.
We have discussed support for BigDecimal numbers (which @lrosenthol mentions).  Do we need both a 64-bit integer and a BigDecimal?  Or if we supported BigDecimal would that cover the cases that we think require a 64-bit integer?
A definitely think we should outline a concrete use case before introducing a new, proprietary data type.  This would help answer all of these questions.

I don't have a specific use-case on where the 53-bit space is insufficient. My main concern is that existing users already use long/bigint/int64 in various systems (Hadoop, relational DBs).
Using a decimal or big decimal also has potential performance overheads (both compute and memory).
Do we plan to make the transition for existing users of long/int64 easier? An explicit int64 type also makes life simpler for application developers. Having only decimal adds a high amount of burden on applications to become smarter about what primitive types to leverage for the necessary perf optimizations?

@hiteshs, I believe that we already have an approach:  in XDM the equivalent of a long/int64 in other systems is an "integer" type.  The limitation is that this type is only 53-bits wide.  Users of int64 in other systems should use "integer" in XDM, being aware of the narrower range.
The only reason this approach would not work is if there are cases where values exceed the 53-bit space.  But we haven't identified any such cases.
As has been described in this thread, JSON simply doesn't support a full 64-bit integer.  Which means the only way we can define one is to create an encoding into a type that JSON does support.  This will necessarily put burden on applications and tools to handle this proprietary extension.  So we shouldn't do it without some careful consideration.  it is difficult to do that without a use case.

@kstreeter The limitation of 53bits is only in specific implementations (eg. JavaScript), not systemic to XDM or JSON.   JSON itself is format & implementation agnostic (as noted in its spec).

Technically @lrosenthol is right, that ideally there is no limit on the size and precision of number fields. In all practically, this does not hold true, though. Particularly RFC 7493 suggests in Section 2.2, Numbers to assume numbers are IEEE 754 binary64. This in practice limits the precise representation of integer values to a range of roughly 2**53.
I agree with you @lrosenthol that using string is suboptimal, but this just biting the bullet of reality.
So we are left, with three options for this issue:

do nothing, and assume type=integer provides enough of a hint, that we are dealing with an integer number of potentially arbitrary size.
do simple and use type=string with format=int64 which solves a short-term issue but requires different approaches as we want to indicate arbitrary precision
go all-in and go with a new format=decimal which allows to describe desired precision. This is more involved and provides most flexibility, event the ability to define in the schema, that numbers have limits which might be defined such that implementations may optimize to using int64.

I have a preference for the flexible approach which, of course, gives power and thus responsibility.

I>  As far as what else to do, I would be willing to consider #3 if we picked a very specific standard (eg. BigDecimal from Java) that it meant. Leaving it vague is no better than the problem that got us here in the first place.
I think my proposal for #3 is pretty well defined without going into implementation detail for a single implementation:

The intent of the decimal and integer formats is the ability to represent exact decimal (and integer) values exceeding the limitations imposed by double precision IEEE754 numbers underlying number and integer typed values.

We could certainly go for better wording.
But if we'd go for #3 I would be inclined to actually push this into the JSON Schema Validation spec.


add tracking for individual ids for list types

Another feature request, though I understand if you wouldn't want to include this as there is currently a workaround:
How about the ability to have a list type automatically watch all of its children? That way if you have a live query that returns some type [Post], for instance, and you have some mutation which invalidates Post:1, if you're watching that list, it will automatically stay in sync.
Maybe this feature should be opt-in? Since you can essentially do this with the extensions.liveQuery.collectResourceIdentifiers field on your resolver. It would just prevent somebody from having to write that function on every live list they need to keep track of.

That should already works without these changes.
See sample response from the todo example app:
    {
        "data": {
            "todos": [
                {
                    "id": "1",
                    "content": "foo",
                    "isCompleted": false,
                    "__typename": "Todo"
                },
                {
                    "id": "51013707",
                    "content": "l",
                    "isCompleted": false,
                    "__typename": "Todo"
                },
                {
                    "id": "94f56a8",
                    "content": "l",
                    "isCompleted": false,
                    "__typename": "Todo"
                }
            ]
        },
        "isLive": true,
        "extensions": {
            "liveResourceIdentifier": [
                "Query.todos",
                "Todo:1",
                "Todo:51013707",
                "Todo:94f56a8"
            ]
        },
        "id": 0
    }
```
Or am I missing something?

Ah you know what, I was running into this issue on my work project and I realize now that I had something incorrectly setup on my end, so nevermind!


Initiated the Google OAuth 2.0 for the admin login

Hi @pradeeban ,
I have successfully initiated the Google OAuth 2.0 process for the admin login. This implementation will enhance the security and streamline the authentication process for our administrative users by leveraging Google's robust OAuth 2.0 protocol. But the authentication's next process is yet to be developed.
Please let me know if you have any questions or need further details.
Best regards,
@mdxabu

Thanks, Mohamed, for your excellent contributions!  Looks neat. Merged.


Add glob function

This branch adds the glob function to Hush, so we can get a list of filenames in a directory that match an input.

Awesome! Thanks a lot for the contribution. Let me know when we can have a beer :smile:


Pull release with Terraform Cloud removed

Describe the task
Create a new release version for CAS-CIF that includes the migrated Terraform code from #1887.
Acceptance Criteria

[ ] Release to -test
[ ] Release to -prod

Will release this to -test once #1887 is merged during the merge party (and it goes smoothly).
Will budget half a day to this test/prod release, as there may be unanticipated issues with packeges due to infrequent releases. Will assign a planning value once we've decided on our methodology in our inceptiuon meeting Feb 13, 2024.


Description
If spawned via sandbox menu or admin menu.
This is part of broad issue where Aghost can pick up all items on the ground and use some of them.
Also, if Aghost picks up an item inside the client viewport, that client will crush. (Picking up items outside the viewport is fine)
Screenshots

https://user-images.githubusercontent.com/91910481/143085555-2eae0c43-9640-4e7c-97d6-42b8d279a0d1.mp4
Additional context

That's really not an idea, like, that kind of the purpose, to use stuff.

aghosts being able to pick up items is not an issue, aghost pickups being broken because of PVS is known


Update CI/CD to GitHub Actions

Travis used for old CI. Should probs update to GitHub Actions

Actions to include:

[ ] python-package.yml


"Yank" older meltano versions which are missing Python constraints

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2853
Originally created by @aaronsteers on 2021-07-14 20:04:12

We have a problem right now that many users are installing meltano on Python 3.9 - which is not supported - but the install is moving forward anyway on older versions (specifically 1.67) which were published without an explicit max supported Python version. The net result is (1) the new user gets a stale version of Meltano, and (2) they don't get any messaging about 3.9 being unsupported.
Long-term mitigation needed
Although we are soon going to launch 3.9 support (#2545) this issue will resurface again in October when Python 3.10 is expected to release.
"Yanking" old versions
According to the PyPi docs:

https://pypi.org/help/#yanked
https://www.python.org/dev/peps/pep-0592/

Risk of Resurgence Post-Fix
If we do the one-time yank of old versions, this issue should not resurface because all published versions have a max supported version.

View 1 previous comment from the original issue on GitLab


add usmba university domain

@AyoubRez I am sorry, the domain usmba.ac.ma is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


[SPARK-42579][CONNECT] Part-1: function.lit support Array[_] dataType

What changes were proposed in this pull request?
This is the first part of SPARK-42579, the pr is aims to support Array[_] data type for function.lit.
Why are the changes needed?
Make function.lit support nested dataType
Does this PR introduce any user-facing change?
No
How was this patch tested?

Add new test
Manually checked Scala 2.13 test

build/sbt "connect-client-jvm/test" -Phive -Pscala-2.13
build/sbt "connect/test" -Phive -Pscala-2.13

cc @hvanhovell @HyukjinKwon

Some other things to do, will update later

Merging.

Thanks @hvanhovell


[IMPROVEMENT] less verbose log on longhorn-manager

Is your improvement request related to a feature? Please describe
longhorn-manager pods currently use level=debug on logs, such as:
time="2022-05-25T16:52:21Z" level=debug msg="Found 0 node has at least one schedulable disk" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 state=attached volume=pvc-11f3737c-0f4e-4bce-8378-8bfaf7d37d6b
time="2022-05-25T16:52:27Z" level=debug msg="Found 2 use zones [anexo1 anexo3]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 1 use nodes [k8s-worker-b2]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, 2 volume replicas are running on different zones" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 0 replica candidate for auto-balance" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceOption=least-effort state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, volume replicas are running on different nodes" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=node state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 0 replica candidate for auto-balance" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceOption=least-effort state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, volume replicas are running on different nodes" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=node state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 2 use zones [anexo1 anexo3]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 1 use nodes [k8s-worker-b2]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, 2 volume replicas are running on different zones" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 0 node has at least one schedulable disk" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 2 use zones [anexo1 anexo3]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 1 use nodes [k8s-worker-b2]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, 2 volume replicas are running on different zones" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 0 replica candidate for auto-balance" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceOption=least-effort state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, volume replicas are running on different nodes" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=node state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 0 replica candidate for auto-balance" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceOption=least-effort state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, volume replicas are running on different nodes" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=node state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 2 use zones [anexo1 anexo3]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 1 use nodes [k8s-worker-b2]" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Balanced, 2 volume replicas are running on different zones" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 replicaAutoBalanceType=zone state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021
time="2022-05-25T16:52:27Z" level=debug msg="Found 0 node has at least one schedulable disk" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8s-worker-a1 owner=k8s-worker-a1 state=attached volume=pvc-5ce9de33-3ed4-4cc2-b8dc-52269212b021

This generates gigabytes of logs on each worker node, causing kubernetes disk pressure events.
Describe the solution you'd like
A less verbose log of longhorn-manager pods.
Describe alternatives you've considered
The possibility to set the level of degub, such as level=info
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Longhorn version: 1.2.3

There are lots of duplicate messages, so we need to check and reduce it.

Right now, I believe we don't differentiate well what logs should be in which log level but rather mostly at debug level.
So the first thing we should do is to improve the right differentiation, then expose the configuration of the log level.

@PhanLe1010 IIRC, you pointed out where the verbose log from. Can you update that finding here as well?

Yeah, it was from this function https://github.com/longhorn/longhorn-manager/blob/f5f3a1ba68e1f852af2020e7baf697e8bd9bc9b4/controller/volume_controller.go#L2117-L2197

let's tackle this issue at https://github.com/longhorn/longhorn/issues/5888

Change to tackle this issue at https://github.com/longhorn/longhorn/issues/6019


Basic docs for collide_aabb

How can Bevy's documentation be improved?
This is prominent in the breakout example but has no documentation at all. This needs a simple definition that expands the acronym.
I don't expect this function to live for terribly long in its current form, so basic docs are fine.

I think this should be closed, since the PR got merged.


Adding new Advocate

Adding Jen Looper

Docs Build status updates of commit c301c06:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/index.html.yml
:white_check_mark:Succeeded
View

advocates/jen-looper.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/jen-looper.png
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[run_benchmark.sh] Few cores are running on HBM when batch-size >16 or 32

Tried both xft 1.6.0 and 1.7.1.
For Chatglm3-6B,  issue can be seen when batch-size > 32 (Tried 48, 64, 128).
For Llama2-13B, issue can be seen when batch-size >16.(  Tried 32)
Specifically, only few CPU cores are running, but still lots of HBM memory available.

Could you provide more info? CPU info(lscpu), running cmd, and CPU and memory usage in that situation.

Sure.
lscpu:  Xeon Max 9468
root@2952c6e7ae31:~# lscpu
Architecture:            x86_64
CPU op-mode(s):        32-bit, 64-bit
Address sizes:         52 bits physical, 57 bits virtual
Byte Order:            Little Endian
CPU(s):                  192
On-line CPU(s) list:   0-191
Vendor ID:               GenuineIntel
Model name:            Intel (R) Xeon (R) CPU Max 9468
CPU family:          6
Model:               143
Thread(s) per core:  2
Core(s) per socket:  48
Socket(s):           2
Stepping:            8
CPU max MHz:         3500.0000
CPU min MHz:         800.0000
BogoMIPS:            4200.00
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_
known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 i
nvpcid_single intel_ppin cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt av
x512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req hfi vnmi avx512vbmi u
mip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr ibt amx_bf16 avx512_fp16 amx_ti
le amx_int8 flush_l1d arch_capabilities
Virtualization features:
Virtualization:        VT-x
Caches (sum of all):
L1d:                   4.5 MiB (96 instances)
L1i:                   3 MiB (96 instances)
L2:                    192 MiB (96 instances)
L3:                    210 MiB (2 instances)
NUMA:
NUMA node(s):          16
NUMA node0 CPU(s):     0-11,96-107
NUMA node1 CPU(s):     12-23,108-119
NUMA node2 CPU(s):     24-35,120-131
NUMA node3 CPU(s):     36-47,132-143
NUMA node4 CPU(s):     48-59,144-155
NUMA node5 CPU(s):     60-71,156-167
NUMA node6 CPU(s):     72-83,168-179
NUMA node7 CPU(s):     84-95,180-191
NUMA node8 CPU(s):
NUMA node9 CPU(s):
NUMA node10 CPU(s):
NUMA node11 CPU(s):
NUMA node12 CPU(s):
NUMA node13 CPU(s):
NUMA node14 CPU(s):
NUMA node15 CPU(s):
CMD
bash run_benchmark.sh -m chatglm3-6b -d bf16 -s 1 -bs 48 -in 1024 -out 512 -kvd fp16 -i 1
Screenshots when running the above cmd

There should be all cores of one socket running, but you can see from the picture that only a few are running.

Tried in another server and this issue is not related with XFT, thanks.

This is because the pre-allocated buffer size for SHM is insufficient, causing the program to hang during the communication. This bug may occur randomly, but the patch for the fix has already been merged.
https://github.com/intel/xFasterTransformer/pull/457


[BUG] Confd could not update file against key/value changed in etcd(confd[25]: INFO Target config /etc/nginx/conf.d/default.conf out of sync)

I have a nginx config file: default.conf which is managed by etcd and confd, Normal access.log when sth was changed shows below:

confd[991]: INFO /etc/nginx/conf.d/default.conf has md5sum 85ccd17c5e41f19e148bd11e02ac7c82 should be 1c120b15e37a7f72acb8bffe91730344
confd[991]: INFO Target config /etc/nginx/conf.d/default.conf out of sync
confd[991]: INFO Target config /etc/nginx/conf.d/default.conf has been updated

but today i had met very a strange problem, confd could not update key from etcd, but  get " "(" " : empty character),thus http:// ;,  it should be http://<IP_ADDRESS>:8080, path in getv {{getv "path"}} is correct!
error logs:

confd[677]: INFO Target config /etc/nginx/conf.d/default.conf out of sync
confd[677]: ERROR "2017/05/25 09:43:15 [emerg] 683#683: no host in upstream "" in /etc/nginx/conf.d/default.conf:58\nnginx: [emerg] no host in upstream "" in /etc/nginx/conf.d/default.conf:58\nnginx: configuration file /etc/nginx/nginx.conf test failed\n"
confd[677]: ERROR Config check failed: exit status 1
[nginx] waiting for confd to create initial [nginx] configuration...

so, I changed default.conf file, switch  " " to the right one by hand, then problem solved and never happen again.
I want to know how to trace this problem when happen again and what is the potential reason for this problem? Thanks a lot for all your effort that will make for this issue.

@HeavyHorst :)

Might anyone help me?
It happened again. : (

@HeavyHorst, I found the bug!!!!
If i set nginx default.conf proxy to "proxy_pass http://;", it never update file and report error:

2017-05-26T04:35:38Z 39e7805e3c78 confd[25]: INFO /etc/nginx/conf.d/default.conf has md5sum b74d1108b3a9c87cab7faa8f2ab8782f should be ea53ad0b08c6f34667363a0d2569c262
2017-05-26T04:35:38Z 39e7805e3c78 confd[25]: INFO Target config /etc/nginx/conf.d/default.conf out of sync
2017-05-26T04:35:38Z 39e7805e3c78 confd[25]: ERROR "2017/05/26 04:35:38 [emerg] 584#584: invalid number of arguments in "proxy_pass" directive in /etc/nginx/conf.d/default.conf:14\nnginx: [emerg] invalid number of arguments in "proxy_pass" directive in /etc/nginx/conf.d/default.conf:14\nnginx: configuration file /etc/nginx/nginx.conf test failed\n"
2017-05-26T04:35:38Z 39e7805e3c78 confd[25]: ERROR Config check failed: exit status 1

@regardfs did you run the check command against your real destination config?
Try to use {{.src}} instead of the final destination of the config to use the staged config file.

check_cmd = "nginx -t -c {{.src}}"  should work.

@HeavyHorst
It does not work in my scenario, cause I use nginx.conf and conf.d/default.conf, only check {{.src}} would fail cause it only have server {} content.

@HeavyHorst For temp solution
I add a nginx.conf in /usr/local/etc/ and only include "/etc/nginx/conf.d/.default.conf*"
and check_cmd: nginx -t -c /usr/local/etc/nginx.conf for temp source file check


Fix type of Nullable.t which was not untagged in the implementation.

See https://github.com/rescript-lang/rescript-compiler/pull/6669#issuecomment-2165347349

Great! Want a release with this right away?

That would unblock the compiler fix.

@cristianoc great, releasing!

@cristianoc out in 1.5.0.


sosfiltfilt_dyn missing padding functionality

Hi and thanks for the work on this library so far
The sosfiltfilt_dyn function is missing the padding arguments and functionality of the upstream function. If you are meant to use the pad function in conjunction with it to replicate this it's not very clear how to do that.

With the current implementation, you should be able to get the same results as scipy for the default configuration. sosfiltfilt_dyn has the default padding options implemented: https://github.com/qsib-cbie/sci-rs/blob/bdeaf1da03de4fffc7a7a879c6c956e548ca350e/sci-rs/src/signal/filter/sosfiltfilt.rs#L31
I don't think we ran across a use case that needed the other options, but feel free to add it. It would require a breaking interface change to add an enum, but we could bump the minor version of the crate.
I think ConvolveMode provides an example similar to what would be required for all the padding options. https://github.com/qsib-cbie/sci-rs/blob/bdeaf1da03de4fffc7a7a879c6c956e548ca350e/sci-rs/src/signal/convolve.rs#L6-L29
As I am writing that, I am seeing some stale comments about the similar situation that function used to have
 /// - `mode`: Convolution mode (currently only Full is supported)

We could start out with something like pub enum Pad { Odd } and add cases as we have support.

Ah - I totally missed that it was using padding by default. For whatever reason I thought it was equivalent to the scipy function with padding set to None since it did not have the padding argument and didn't look at the source code - my bad, sorry about that.
I don't think I have any need for other padding options either as of now so no rush from my side to implement anything else. Might be worth noting it in the documentation though.

Good to hear.
Closing the issue since this is the current situation on most of the interfaces.


Uncaught stacked series cannot have differing numbers of points for preview

To fix it, I had to add unstack:true in buildGraph

Rickshaw.namespace('Rickshaw.Graph.RangeSlider.Preview');

Rickshaw.Graph.RangeSlider.Preview = Rickshaw.Class.create({
.........
var buildGraph = function(parent, index) {

                        var graphArgs = Rickshaw.extend({}, parent.config);
                        var height = self.previewHeight / self.graphs.length;

                        Rickshaw.extend(graphArgs, {
                                element: this.appendChild(document.createElement("div")),
                                height: height,
                                width: self.previewWidth,
                                series: parent.series,
                                unstack: true
                        });

Can you post the whole code?


Schema validation errors not caught by error handler

Description
Schema validation errors are not caught by error handlers.
I want my application to have a "standard" JSON error format.
For this i register an error handler to format the error response.
Schema validation errors bypass the error handler and do not allow to format the response.
Expected behaviour
HTTP 500
{ "error": 'My custom error format" }

Actual behaviour
HTTP 400
{
  "detail": "1000 is greater than the maximum of 90",
  "status": 400,
  "title": "Validation error",
  "type": "about:blank"
}

Steps to reproduce
application.py:
connexion_app = connexion.App(root_path, specification_dir='src/api/rest')

def handle_connexion_exception(exception):
        return '{ "error": 'My custom error format" }', 500

connexion_app.add_error_handler(ProblemException, handle_connexion_exception)

Cause a openAPI schema error (call an endpoint with invalid JSON).
Additional info:
The culprit seems to be validate_schema https://github.com/zalando/connexion/blob/master/connexion/decorators/validation.py#L188 that does not throw an error and just returns the endpoint response.

I think this is fixed by #955
Can you try the latest release?

Fixed


BarChart bug when Label is string.Empty

Hello, I found bug in BarChart when Entry Label is string.Empty. When I have more entries I set Entry Labels empty and I found a bug when its empty chart is not showing correctly. But when I used Label = " "; it works. You can see example on my screenshot (https://imgur.com/QSJXfNm). Its same on Android and iOS. Thanks.

Noted! Thank you for the information. Can you tell me which version of Microcharts you're using?

Also, if you wouldn't mind, could you send up your xaml and supporting data (even if it's contrived), if you've got it handy, it'll speed up the debugging process.

I have noticed this bug too, i could make a project for you if you want but i only code on Xamarin.Android


[fud2] Add ability to look for a config key that must be associated with a constrained set of values

This PR allows one to use config_constrained_* methods to ensure that the value passed in via --set is constrained to a set of values.
This seems useful for things expected to be true or false and is used in #2136
If this goes against the grain of what we hope fud2 to be, we can close this without merging.

Merging!

Looks great!!


Add the "rpm" remote dependency

Hi guys. Here's a patch that provides remote dependencies on RPM-based systems.

Thanks for bringing this back Nick! WIll try to make time for it in the coming days.

You're welcome, Lee. It was dead simple to implement, and I finally got around to needing it.


requirements.txt should use explicit and fixed version numbers

The current setup means that fresh pip install calls might produce different installations in case any dependency version advances. This affects reproducibility and testing.

I'm not sure I'm a huge fan of this... for instance, [1, 2] do not enforce version constraints; there are also other sources of randomness, e.g. the nltk and spacy models being used
[1] https://github.com/tensorflow/tensor2tensor/blob/master/setup.py
[2] https://github.com/fchollet/keras/blob/master/setup.py

I don't think it's a time sink. It has to be done once, and then we just need to be explicit about when dependencies change. And that's a good thing. For example, I think it's important to make the change from TF 1.13 to 1.14 explicitly, and not finding out because something obviously failed a test.

@riedelcastro what if the user wants the latest TF for his project(s), but jack is a bit late and still requires an older version?

Idea - we can just avoid specifying the version number in requirements.txt, and perform some tests (e.g. the overfit ones) with TF 1.x and all other tests with the latest TF version

I can ask Wercker to use TF 1.x for the overfit tests (so they don't fail for random reasons) and the latest TF for all other tests - that should fix the problem!

Seems very weird to use different TF versions for different tests.
@pminervini a good reason for us to keep up and maintain jack regularly :)

I think TF is stable enough such that we can fix a version and update it once in a while with the test results.

Indeed at some point we had this feature in Jack (because I grew bored of tests failing) - but then, I wanted to use the latest TF and jack didn't, and I quickly reverted that change


Correct gradle build text replacement and version #s

I can't compile, so I can't test, but these changes should fix broken version numbers in the compiled mod metadata.
Line 27 of build.gradle is mainly there for consistency and string deduplication, but I can revert that if you don't want it.

I was also unsure about this change. It looked like a typo, so I changed it to be consistent with the mod metadata format.

It looks like something else might be broken in the build flow. I had thought the problem was that the variables didn't start with project. (and that might also be a problem) but %LIBVULPESVERSION% already used project.libVulpesVersion as a replacement, and that's not replaced in the decompilation of AdvancedRocketry-1.12.2-2.0.0-248-universal.jar: https://gist.github.com/Brycey92/12b9adb00e6ed83c7ca3de1c00152ece#file-advancedrocketry-java-L314-L323

I managed to fix deps.gradle enough that gradle can build again, and the generated sources have the version numbers replaced correctly. I'll open a new PR for that when I have deobf and universal jars building.


fromZero works fine for the line, but not for the points

After adding fromZero to the LineChart props, line behaves like it should, but datapoints are rendered as if the bottom line was still equal to the minimal value.

I have the same issue. Any one can help on this?

Hi @Bar-Marz,
I was facing same issue.

To resolve this, I have updated code in node_modules/react-native-chart-kit/src/line-chart.js in renderDots function as below:
Replace below line
const cy = (height / 4) *  3 * (1 - (x - Math.min(...datas)) / this.calcScaler(datas)) + paddingTop
with
const cy =
(baseHeight -  this.calcHeight(x, datas, height)) / 4 * 3 + paddingTop
Result :

@bhoomika911 What's the baseHeight?

I created a pull request to fix this issue as suggested by @bhoomika911

This is fixed in v3.3.1

I've update to the latest (v3.3.1), but I still have the issue. The dots are totally off. Any idea?


Types: accept string as function.

The module already works with strings, only the types should be updated.
Probably type AsyncFunction = (...args: any[]) => Promise<unknown>; should be type AsyncFunction = ((...args: any[]) => Promise<unknown>;) | string

It would also have to be documented and tested.

Arright', gonna make a PR! Very nice work, btw!!:)


Add color format

Adding asColor to the Formatter Class

What's the use case for displaying colors in a grid?

Hi Sam,
When we use the color field in our forms to pick colors, we need to see the color (not the hexa value). So instead of showing a hexa code, we display the color.
When using in the DetailView or GridView, we just need to add in our attributes values: 'attribute_name:color'. For example:
echo DetailView::widget([
    'model' => $model,
    'attributes' => [
        'title',             // title attribute (in plain text)
        'cover_color:color'	 // color of the cover
        'description:html',  // description attribute in HTML
        [                    // the owner name of the model
            'label' => 'Owner',
            'value' => $model->owner->name,
        ],
    ],
]);

I don't think it's common enough to be in the core. Feel free to release it as an extension though.


Control panel below the player

"Control panel below the player" ON not working with videos from watch later for example.
Once the video is loading the player buttons disappear. Click to pause and you can only see a small progress bar.

The videos from personal playlists don't work with "Control panel below the player" ON.
If "Control panel below the player" is OFF everything works fine.
Script latest. Firefox latest, Violentmonkey 2.13.3.

https://www.youtube.com/playlist?list=PLD954AD90548599FE

Tested with latest Chrome and same playlists don't work with "Control panel below the player" ON.

Once I sign out it works. Maybe my account is probably in some beta test. Thanks for everything!

I just noticed (in your screenshots) that your player has straight corners. See my screenshot my player has little round corners (I never seen that before). So it is clear that my account is under beta test. Thanks!

This script fixed my bug
https://greasyfork.org/en/scripts/453802-youtube-non-rounded-design

"Square avatars" it has no effect. After full screen/Exit full screen the player buttons disappear (as in my first screenshot).
With that script the player buttons are kept.

The videos were from my personal playlists. So, I was always logged in.
Yes, the new version fixed both issues:

Player buttons not disappear after Full screen/Exit full screen.
Player has straight corners.

Thanks a lot!

No premium.


Running a request with OAuth2 configured show the result of the OAuth2 request instead of the result of the request itself

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
I use Bruno to send requests on API protected with OAuth2.
When I use directly the Bearer token, I run the request and I get the right response.
When I configure OAuth2, I run the request and I get only the response from the OAuth2 server (with the token and the scopes).
.bru file to reproduce the bug
No response
Screenshots/Live demo link
OK Case using the bearer token, the response is correct

Buggy case using OAuth2, see that the response contains an access_token, the structure is not the expected one.
Clicking on "Get Access Token" or the right arrow on top right to send the request does the same.

Thank you for reporting this, @Oznup!
Bruno handles the OAuth2 flow a bit differently from other API clients. Currently, the process requires two separate requests: the first request manages the OAuth2 flow and stores the token in a variable, while the second request (the actual endpoint call) uses that token.
We understand this can be confusing, and we are actively working on improving the OAuth2 experience. In November, we plan to revamp the OAuth2 UI so that the entire flow happens seamlessly within a single interface.
In the meantime, please refer to our documentation for guidance on how to use OAuth2 with the current setup: https://docs.usebruno.com/auth/oauth2/overview

We also encountered this peculiarity when my colleague executed a request to get a second access token from the .../token endpoint, and this request had OAuth 2.0 authorization configured (to fetch first access token). Instead of the second access token, he actually received the first one, which related to the configured authorization, and not to the result of the request execution. We thought that the authorization logic here is similar to the Postman logic, so it took a long time to find the problem.
It's great that this will be fixed, thanks!


[Access Request] codeunit 7010 "Purch. Price Calc. Mgt." ConvertPriceLCYToFCY

Could you please change the remove the local scope of the procedure ConvertPriceLCYToFCY?
//+kisexx
//-local procedure ConvertPriceLCYToFCY(CurrencyCode: Code[10]; var UnitPrice: Decimal)
procedure ConvertPriceLCYToFCY(CurrencyCode: Code[10]; var UnitPrice: Decimal)
//-kisexx
var
    CurrExchRate: Record "Currency Exchange Rate";
begin
    if PricesInCurrency then begin
        if CurrencyCode = '' then
            UnitPrice :=
                CurrExchRate.ExchangeAmtLCYToFCY(ExchRateDate, Currency.Code, UnitPrice, CurrencyFactor);
        UnitPrice := Round(UnitPrice, Currency."Unit-Amount Rounding Precision");
    end else
        UnitPrice := Round(UnitPrice, GLSetup."Unit-Amount Rounding Precision");
end;

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. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52559.


Update PSBT test

implement walletcreatefundedpsbt rpc
implement getaddressinfo rpc (by biproduct)
fix subtle bug in multisig script finalization.
enable finalization only in a NBitcoin-aware type of script.

FWIW, segwit support for importmulti is merged in this pr
It seems bitcoin core is heading towards to the trend for using the word "redeemscript" exclusively for p2sh script, btw.

Thanks, reviewing. Next time can you make several PRs instead of one big? it is faster to review.

closing in favor of #630 #631 #632


Is there a consistent approach to mapping a classification of assets in the AAS?

In the "Generic Frame for Technical Data for Industrial Equipment in Manufacturing" (IDTA 02003), a guideline for the creation of submodel templates for technical data of assets, for example, the SubmodelElementCollection ProductClassifications is described. Would not be a classification of assets also in AssetInformation usefull for every kind of Asset?

This is out of scope of the working group, we are not able to change the metamodel. Feel free to reopen.

I am reopening because the information might be interesting for others as well:

Which working group is maintaining this question-and-answers repo and what topics can be adressed here?
Is there a repo to place issues/ideas for the metamodel existing?

we (group IDTA-workstream "Best modeling practice" are maintaining it, our self-understanding is to remove ambiguities while modeling, e.g. creating SM templates, but not changing the meta-model itself
https://github.com/admin-shell-io/aas-specs/issues would be the proper place


Add Gboard gifs support

reported by @yj:matrix.org
https://github.com/matrix-org/riot-android-rageshakes/issues/990

Yesss

This is working for me on Android 8.1. Is it still not working on your devices?

Duplicate of #1516


lib: Remove duplicate select in reset_select_{write,read}_only

Using these functions would send the select rom command as data after the actual select rom command corrupting any actual data that was supposed to be read/written.

I can confirm that without this fix DS18B20 always returns 85 instead of correct temperature.


Search taking lot of time using clg binary

Bug
We are using CLP for compressing logs generated by our Kubernetes cluster which are in JSON format. A sample log is given below:
{
"log_time": "2023-08-29T13:55:09.477456Z",
"stream": "stdout",
"time": "2023-08-29T13:55:09.477456564Z",
"@timestamp": "2023-08-29T19:25:09.477+05:30",
"@version": "1",
"message": " Method: POST;Root=1-64edf8bd-5c762a676349ee71616bb687 , Request Body : {"orders":[{"order_type":"normal","external_reference_id":"69426","items":[{"offset_in_minutes":"721","quantity":"1","external_product_id":"225090"}]}]}",
"level": "INFO",
"level_value": 20000,
"request_id": "6f3f3651-a22b-42a0-b5fe-412d2167c5ca",
"kubernetes_docker_id": "caa9102a169a1495e5790cb2c17cb21d0a279ffc50d802d413938870ba59c7c0",
}
When we are using the clg binary to search through the generated archive using various search queries, It is taking a lot of time to process each query (around 25-30s on average). We only search for request_id and namespace name as mentioned below. It is not feasible for us if the search takes so much time for each archive. Ideally, for one archive 4-5s is the expected search time by us.
For example, To search for the request_id in the above log, we generally use the following queries

info6f3f3651-a22b-42a0-b5fe-412d2167c5ca*
6f3f3651-a22b-42a0-b5fe-412d2167c5ca
Our archives are sized 40MB on average wherein the sizes of the internal files and folders of an archive is as given below:
var.dict : 18.2MB
/s: 16.8MB
var.segindex: 2.6MB
metadata.db: 1.9MB
logtype.dict: 736KB
logtype.segindex: 36KB
metadata: 4KB

Is this the correct way to write search queries (the correct way in the sense that will it use the log type and other dictionaries to search through the archives efficiently)? because as mentioned earlier searching through a single archive itself takes more than 30s which is very infeasible. We expect the search time for each archive to be around 4-5s, not more than that for a single archive. Please guide me If I am doing wrong anywhere like the search query being inefficient, etc.
CLP version
3a20c0d2bb831de7fa267d57d187dab8c3f092c1
Environment
UBUNTU 20.04
EC2 instance type: m5.8xlarge
Reproduction steps
NA

Hi @bb-rajakarthik,
Sorry for the delayed response.
I assume your JSON log events are printed with one event per line? Either way, I think CLP is having trouble parsing the timestamps from your events, which means it will store those strings in the variable dictionary. You can verify this by using make-dictionaries-readable to create human-readable versions of the dictionaries (which you can inspect). Storing the timestamps in the dictionary would lead to quite a large variable dictionary, which in turn would be slow to load and slow to search.
CLP currently doesn't have good support for parsing timestamps spread across a message (we are improving our schema-based parser to handle these cases); for unstructured log events, typically the event's timestamp appears at relatively fixed locations, so it's easy to parse. However, in JSON events, it can move around and there can be multiple timestamps.
One potential solution for your case might be to preprocess the events to convert the timestamps to epoch timestamps; that way CLP could at least encode the timestamps as numbers rather than strings.
In the future, we hope to open-source a tool specifically designed for compressing and searching JSON log events.
With respect to your queries, including delimiters around the strings you search for might improve performance. E.g., for query 1, you could try: *"INFO"*"6f3f3651-a22b-42a0-b5fe-412d2167c5ca"*. Without the delimiters, the wildcards are directly connected to the tokens, so CLP has to scan the dictionaries looking for substring matches rather than performing a table lookup.
Hope that helps.

hi @kirkrodrigues
Thanks for taking time to respond and giving me a detailed answer. So @kirkrodrigues based on your answer to my question, If my log message is as following:
{
"stream": "stdout",
"@Version": "1",
"message": " Method: POST;Root=1-64edf8bd-5c762a676349ee71616bb687 , Request Body : {"orders":[{"order_type":"normal","external_reference_id":"69426","items":[{"offset_in_minutes":"721","quantity":"1","external_product_id":"225090"}]}]}",
"level": "INFO",
"level_value": 20000,
"request_id": "6f3f3651-a22b-42a0-b5fe-412d2167c5ca",
"kubernetes_docker_id": "caa9102a169a1495e5790cb2c17cb21d0a279ffc50d802d413938870ba59c7c0",
}
where all timestamp fields have been removed from the json log, Search will definitely be faster as the size of the variable dictionary is reduced significantly. Is my understanding correct?
Also, If I decide to filter out specific fixed fields from all of my json logs, Will the time taken for searching through the archives get reduced? According to my understanding of CLP, If all json logs are of similar structure, Even the compression rate has to increase. Is my understanding correct @kirkrodrigues ?

If my log message is as following ... where all timestamp fields have been removed from the json log, Search will definitely be faster as the size of the variable dictionary is reduced significantly. Is my understanding correct?

Yes, that should improve search performance.

Also, If I decide to filter out specific fixed fields from all of my json logs, Will the time taken for searching through the archives get reduced?

To some extent, yes, just because CLP needs to scan less data. The size of the improvement will depend on how much of the logs are occupied by those fields.

According to my understanding of CLP, If all json logs are of similar structure, Even the compression rate has to increase.

Yes, if we compare

compressing JSON logs with similar structure to
compressing JSON logs with many different structures,

the compression ratio should be better for (1). The improvement will depend on how many different structures there are in total and, again, how much of the logs those structures occupy.
Hope that helps.

Hi @bb-rajakarthik,
We now have a distributed version of CLP (clp-json) specifically designed for compressing and searching JSON logs; we also have a single-threaded version, clp-s, which I think you've tried. Both should improve the performance of the searches you mentioned.
Let us know if you notice any more bottlenecks, otherwise I will close this issue.


[BUG] lsp-python-ms should download executable to doom-local-dir

lsp-python-ms downloads the language server to .emacs.d/mspyls by default. This should likely be moved to doom-etc-dir. This can be done by setting lsp-python-ms-dir.

As of b1f9965 this should be resolved. Let me know if that isn't the case and I'll reopen this. Thanks for bringing it to my attention!


Header and footer text color too dark in dark mode

When I switch to dark mode, the header and footer text remains black, making it barely readable. E.g. the line that reads "Crisp, minimal, personal blog theme for Astro".
It looks like there's some code in "global.css" to handle this, but as far as I can tell, this doesn't seem to be working. I also saw a possibly related open pull request.
(Beautiful theme otherwise - thanks!)

Yes, the contrast is very low and not accessible. 1.43:1 contrast for the black text on the dark background. You can edit header__desc in Header.astro and post-preview__desc in PostPreview.astro to change the font colors on the index page.

Hey, @digitalhobbit and @drewbitt This issue is fixed now.
Thank you for your patience.


Dict.update alter fn is passed a Result

Zulip discussion https://roc.zulipchat.com/#narrow/stream/304641-ideas/topic/Dict.2Eupdate.20alter.20fn.20work.20with.20a.20Result.3F/near/471562715

@Anton-4, any concerns about when we land this? It looks like it will break two examples in other roc-lang repos. Otherwise, it breaks a lot of old advent of code examples, but not too much otherwise in the community.

Thanks for the ping Brendan, I'm going to look at https://github.com/roc-lang/examples/issues/207 first and will come back to this after.


[Draft] OnError command support in GoSQlCmd

Description :
OnError Command support in GoSqlCmd
For details refer : https://learn.microsoft.com/en-us/sql/tools/sqlcmd-utility?view=sql-server-ver16
Find details test cases : https://microsoft.sharepoint.com/teams/sqltools/_layouts/OneNote.aspx?id=%2Fteams%2Fsqltools%2FSiteAssets%2FSQL Tools Notebook&wd=target(SQL DB Emulator.one|ACFE716C-A04C-4711-B338-012A51291AB8%2FGo Sql Cmd OnError Investigation|8D2F054E-1FC8-46A4-B2B1-08C3A98481A5%2F)
onenote:https://microsoft.sharepoint.com/teams/sqltools/SiteAssets/SQL Tools Notebook/SQL DB Emulator.one#Go Sql Cmd OnError Investigation&section-id={ACFE716C-A04C-4711-B338-012A51291AB8}&page-id={8D2F054E-1FC8-46A4-B2B1-08C3A98481A5}&end
WIP : Adding UTs

I just noticed that you are adding unit tests. In that case you can mark the PR as draft till it's ready.

There seems to be some merge conflicts with main branch. Can you resolve that? Please add unit test case to test this implementation and in combination with -b and -V .

Resolved merge conflicts. And UTs are still WIP

  	if err == ErrExitRequested || once {

check if any code that returns ErrExitRequested here should be bound by the new setting to not request exit when :on error ignore has been used.

Refers to: pkg/sqlcmd/sqlcmd.go:148 in 4a16d79. [](commit_id = 4a16d790743690a710c3cb913f03351e192d3124, deletion_comment = False)

as you push new commits, resolve the relevant discussions in the PR.


basic contributing guide on contributing and opening a PR

Pull Request
Description

Basic improvements to CONTRIBUTING.md guide, besides a PR template for raising better/detailed PRs
Changes Made

inside /docs/ a pull request template folder, with a default PR template like this has been created.
inside CONTRIBUTING.md doc, some best-effort ways to open/raise a PR, and install/develop along the main repo's master is suggested.

Related Issues

Screenshots (if applicable)

Checklist

[ ] Code follows the project's style guidelines
[ ] All tests related to the changes pass successfully
[ ] Documentation is updated (if necessary)
[ ] Code is reviewed by at least one other team member
[ ] Any breaking changes are communicated and documented

Additional Notes

@bohemia420 many thanks for your contribution!


Chapter 11 typo

(p367) In 2nd and 3rd bullet, "distance matrix" should be "linkage matrix".

great catch, totally overlooked this ...


Yet another cloud development configuration

gitpod.io is very similar codespaces, but with different pricing models. It has some interesting GitHub-specific configuration options, but I'll leave that up to you if you want to configure those or not (I think they require the gitpod GitHub app).

:thinking: Maybe the workflows should ignore this file :sweat_smile:

I wanted to enable the prebuilds but I got scared by the level of access rights requested 😩

I don't blame you! Better to be on the safe side 🙁
Anyway, gitpod usage is pretty simple: just paste gitpod.io#/ in front of your repo's URL. So contributing instructions could be

Fork this repository, then go to gitpod.io#/https://github.com/<YOUR-USERNAME>/onefetch

(This works for PR URLs, too, BTW 🙂 )


A successful face match is not displaying the message in sharing device.

Describe the bug
A successful face match is not displaying the message in sharing device.
To Reproduce
Prerequiste: VC is downloaded and stored in sharing device and downloaded VC should contain photo of resident.
Device A - Requesting device (iOS)
Device B - Sharing device (iOS)
steps:

open qr code in Device A
open scanner in Device B
scan the qrcode from Device B
select VC to share and click on ""verify presence and share"".
camera opens up - captures photo of resident

Current behavior
The message is not displayed in residents phone after successful face match

Expected behavior
If photo matches with the VC - displays ""Presence verified"" sharing... should be  displayed in Device B

Smartphone (please complete the following information):
Device: iPhone 8 & iPhone 11
OS: 16.0.2 (20A380), 15.6.1
Inji app version: 0.4.1 (4) -> Testflight
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa5.mosip.net

this issue is a copy of issue no. #303 , hence close this issue,


TFSA-2018-001 commit link is invalid

https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2018-001.md
Links to:
https://github.com/tensorflow/tensorflow/commit/49f73c55d56edffebde4bca4a407ad69c1cae4333c55
Which is 404. Can you please update this with the correct commit? Thanks!

Created the PR #20725 for the link fix.

Thank you for the really quick response!


ifExists does not give opportunity to pass extra parameters to invariant function

This utility will be removed due it it's uselessness


Slider clamps value if attributes set in wrong order

Slider clamps Value to be between Minimum and Maximum which causes
 <Slider Width="400" Minimum="0" Maximum="1000" Value="500" />
to produce a different outcome to
<Slider Width="400" Value="500" Minimum="0" Maximum="1000"  />
which  has value clamped to 100 by the default Maximum value.
if binding is used the order also matters but with hard coded values having priority so
<Slider Value="{Binding filterLow}"
        Minimum="{Binding filterLowMin}"
        Maximum="{Binding filterLowMax}" />

clamps to 0 or 100
but
<Slider Minimum="{Binding filterLowMin}"
        Maximum="{Binding filterLowMax}"
        Value="{Binding filterLow}"/>

does what I expected
and so does
<Slider  Value="{Binding filterLow}"
        Minimum="-6000"
        Maximum="6000" />

Maybe this is expected behaviour but it caught me out. A simple fix would be to set the default limits to double.MinValue and double.MaxValue

Wpf does not have this behaviour, it does not appear to bind the clamped value back to the source unless the slider is moved.

Yeah, we need a way to signal to the XAML reader that Minimum and Maximum should be set before Value. XAML has a [DependsOn] attribute which does something like this, but it's only specified for XAML writers.
We should see how easy it would be to add support for [DependsOn] when reading in the XAML compiler.
cc: @kekekeks