Breaking change in Purchase Line - TestStatusOpen

Issue #3717 was implemented in the last update, but not as requested. Instead of applying the logic from Purchase Line to Sales Line as requested, it was done the other way around.
This is breaking our solution. The OnBeforeTestStatusOpen is used to suspend the status-check in specific situations. Now it is not possible anymore to bypass the status-check by subscribing to this event. I don't see any reason why the OnBeforeTestStatusOpen is moved down a few lines, it doesn't make any sense to me.
Please revert the change asap and, please, please, never introduce this kind of breaking changes again with cumulative updates!
@jobulsin @JesperSchulz

Thanks for reporting. I would guess this was a mistake, as we may not do breaking changes without one years prior announcement - not in cumulative updates and not in major releases either! Now I wonder how we can make gated checks to prevent this from happening again???!!! So you're saying an even was moved? That should be rather hard to detect... I'll brainstorm a little :-)
Again, thanks for letting us know. A bug was created and we will be fixing this asap.

I wonder how OnBeforeTestStatusOpen could have been used to suspend status check, this event is not handled and does not have access to SuspendStatusCheck variable? I assume you manipulated by  "System-Created Entry" field to skip it, but this is not a good idea.
Event was moved simply to provide access to Sales/Purchase Header variable, it makes sence after GetPurchHeader, not before.
Anyway, we can add event before if StatusCheckSuspended then. Does it help?
procedure TestStatusOpen()
begin
    OnTestStatusOpenOnBeforeStatusCheckSuspended(Rec, StatusCheckSuspended); // NEW
    if StatusCheckSuspended then
        exit;

    GetPurchHeader;
    OnBeforeTestStatusOpen(Rec, PurchHeader);

    if not "System-Created Entry" then
        if HasTypeToFillMandatoryFields then
            PurchHeader.TestField(Status, PurchHeader.Status::Open);

    OnAfterTestStatusOpen(Rec, PurchHeader);

That's easy... You can suspend status check just by calling the function SuspendStatusCheck() on the Rec variable that is passed with the OnBeforeTestStatusOpen event.
I believe you shouldn't pass the global variable StatusCheckSuspended. Keep that variable hidden (that's called encapsulation in object oriented design 😉). Instead, the function SuspendStatusCheck() perfectly does the job.
So, if the goal is to call GetPurchHeader() before, which makes a lot of sense, then just move GetPurchHeader up to before the event. No need to introduce yet another event. Code will look like this:
procedure TestStatusOpen()
begin
    GetPurchHeader;
    OnBeforeTestStatusOpen(Rec, PurchHeader);

    if StatusCheckSuspended then
        exit;

    if not "System-Created Entry" then
        if HasTypeToFillMandatoryFields then
            PurchHeader.TestField(Status, PurchHeader.Status::Open);

    OnAfterTestStatusOpen(Rec, PurchHeader);

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

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


Attempted to free invalid ID when using shape keys

Godot version
4.0.1 + current master (49a1962)
System information
Ubuntu 22.04; Vulkan renderer
Issue description
When freeing a MeshInstance3D with shape keys, the following error occurs:
E 0:00:01:0331   _free_internal: Attempted to free invalid ID:<PHONE_NUMBER>333
  <C++ Source>   drivers/vulkan/rendering_device_vulkan.cpp:8394 @ _free_internal()

Steps to reproduce
Just run the attached project. The error message should appear automatically
Minimal reproduction project
shapekeybug.zip

Have the same bug but only when the ArrayMesh also has a Surface Material.
Without a material the error does not show up.

Should be fixed by https://github.com/godotengine/godot/pull/78433, can't repro the test project issue anymore after the PR.


Deduplication in BaseViewModel

https://github.com/igorwojda/android-showcase/blob/3f30d3333f06288adc6f3a1b31198fbd50b1c3aa/app/src/main/kotlin/com/igorwojda/showcase/base/presentation/viewmodel/BaseViewModel.kt#L24
Is this comment correct?
I think Delegates.observable do nothing with deduplication. Per documentation:

And implementation:

It just calls the callback after setting the new value (the new value could be the same).

Good point @bitvale.
Update the code thx


Covid 19 India Dataset Connector

There are three connectors being added.
This is basically a volunteer-driven API (Unofficial) - The idea of adding this to Tableau repository is to show you the power of WDC API build framework to work on dynamic and real time data set and it is purely built out of self-interest. Though you can reach out to me regarding issues, Tableau would not be responsible for any issues encountered with this API as it is built out of my own interest.

Covid 19 India Main - Containing patient information pulled from crowdsourced database. If you would like to analyse the current situation in your location or aim at carrying out analysis on flattening the curve eventually, then this data set can help you!
Covid 19 India Statewise - Containing statewise representation in the form of summary for each state. This is useful to analyse the overall trend and individual measures being taken by each state across India towards recovery process and hospitalization ratios.
Covid 10 India Daywise - Contains daywise representation of active/hospitalized/recovered and deceased patient information.

Coverage remained the same at 98.913% when pulling cd2a671878fe0348262f4b5a0606eb766fa248c8 on muthukumarsm:patch-6 into 92dcf3691c94b316408bf04502343798c6239314 on tableau:master.

Hi @muthukumarsm - Can you add in the WDCs description that the API that you are using is: A volunteer-driven API (Unofficial) please

I shall update the comments accordingly and re-submit the pull request.

I have updated the details specifying that this is unofficial API.

Thanks but I can't see the change in this pull request

Hi Muthu, i was trying to use the WDC you connected, can you please add the statewise_daily one. Thats the one piece missing. these are really helpful. thanks in advance.

Sure! The states are not decoded in the API. will need to decode them to
add to the repository. shall attempt to do the same...
regards
Muthukumar
On Mon, Apr 13, 2020 at 10:07 PM Amit Kumar<EMAIL_ADDRESS>wrote:

Hi Muthu, i was trying to use the WDC you connected, can you please add
the statewise_daily one. Thats the one piece missing. these are really
helpful. thanks in advance.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tableau/webdataconnector/pull/363#issuecomment-612978821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTJNM2QJQEE37V3F4PVBJTRMM5WPANCNFSM4MDFVCWA
.

Sure! The states are not decoded in the API. will need to decode them to add to the repository. shall attempt to do the same... regards Muthukumar
…
On Mon, Apr 13, 2020 at 10:07 PM Amit Kumar @.***> wrote: Hi Muthu, i was trying to use the WDC you connected, can you please add the statewise_daily one. Thats the one piece missing. these are really helpful. thanks in advance. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#363 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALTJNM2QJQEE37V3F4PVBJTRMM5WPANCNFSM4MDFVCWA .

Great, i will wait for it. Thanks.

Also, need some help. How to i contact you?


multi edit product problem

Hi,
Considering this multi edit product and it's corresponding reactants:
C1=CC=C(N([H])C2=CC=CC=C2)C=C1.C1=CC=C(N([H])C2=CC=CC=C2)C=C1.C(Br)1=C([H])C([H])=C(C2=C([H])C([H])=C(Br)C([H])=C2[H])C([H])=C1[H]>>C1=CC=C(N(C2=CC=C(C3=CC=C(N(C4C=CC=CC=4)C4=CC=CC=C4)C=C3)C=C2)C2C=CC=CC=2)C=C1

The code and models this repo provided can not generate the reactants above, what can I do to generate this reactants. Thanks very much for your advice.

Hi, I think you could try either RetroXpert or any of the transformer models potentially.


Better errors for environments

Right now, the CLI tool still has a variety of UI that uses "accounts", which is confusing because we no longer refer to environments as accounts.
We should:

[x] Make language consistent
[x] List all environments to which a user belongs if they fail to specify

Should be fixed by https://github.com/aptible/aptible-cli/pull/168


Serial number not unique

Using the first 4 bytes of the MAC address as a serial number has an issue.
These 4 bytes are largely identical across a batch of chips.
In a batch of 6 boards I had 3 with the same serial number.
I'd suggest using bytes 2,3,4,5 instead of bytes 0,1,2,3
Or find a way to reduce the 6 bytes to 4 bytes. Maybe XOR byte0 with 1 and 2 with 3
uint32_t GetBoardSerialNumber() {
uint8_t chipid[6];
esp_efuse_mac_get_default(chipid);
return chipid[0] + (chipid[1] << 8) + (chipid[2] << 16) + (chipid[3] << 24);

Good catch, thanks! My intention was to use the four last bytes. The first 3 bytes of MAC address are the Organisationally Unique Identifier. I don't know how many OUIs a big manufacturer gets, but definitely there's very little entropy in the current implementation. I quite like your XOR suggestion, but I'd take it a bit (pun intended) further: Calculate the checksum of the first three bytes and use it as the output first byte, and copy the last three bytes as is.
Actually, it gets more interesting than this. In HALMET's example codebase, I already use a variant that returns a 64-bit serial number. Obviously, that's the correct thing to do rather than throwing information away. And in SH-wg's context, there's no good reason to not use the full 48-bit MAC as the serial number.
I'll implement the change in the repo and in the factory image but I'll refrain from pushing an update because the issue is not relevant for most users and I hope to make a major update with SensESP v3 in a couple of months or so.

I'll let you double-check the PR if you want.


[CARBONDATA-2611] Added Test Cases for Local Dictionary Support for Create Table comand

Unit Test Cases are added for Create table command and Describe formatted command for Local Dictionary support added in [CARBONDATA-2585][CARBONDATA-2586] #2375
SDV test cases are added for the same
Dependent on #2375

[x] Any interfaces changed?
NA
[x] Any backward compatibility impacted?
NA
[x] Document update required?
NA
[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.
UT test cases added
[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5183/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5295/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5187/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6350/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5300/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6374/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5212/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6386/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6389/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5223/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6392/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5226/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5333/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5336/

LGTM

LGTM


Realm: error when compiling with HIP

When I try to compile Realm with HIP support on a machine with Nvidia GPUs, I get the following error
/home/mariodr/legion2/runtime/realm/hip/hip_module.cc:3509:24: error: use of undeclared identifier 'hipJitOptionInfoLogBuffer'
      jit_options[0] = hipJitOptionInfoLogBuffer;
                       ^
/home/mariodr/legion2/runtime/realm/hip/hip_module.cc:3510:24: error: use of undeclared identifier 'hipJitOptionInfoLogBufferSizeBytes'
      jit_options[1] = hipJitOptionInfoLogBufferSizeBytes;
                       ^
/home/mariodr/legion2/runtime/realm/hip/hip_module.cc:3511:24: error: use of undeclared identifier 'hipJitOptionErrorLogBuffer'
      jit_options[2] = hipJitOptionErrorLogBuffer;
                       ^
/home/mariodr/legion2/runtime/realm/hip/hip_module.cc:3512:24: error: use of undeclared identifier 'hipJitOptionErrorLogBufferSizeBytes'
      jit_options[3] = hipJitOptionErrorLogBufferSizeBytes;
                       ^
5 warnings and 4 errors generated.
make[2]: *** [runtime/CMakeFiles/RealmRuntime.dir/build.make:580: runtime/CMakeFiles/RealmRuntime.dir/realm/hip/hip_module.cc.o] Error 1

Does anyone have an idea of what is going on?
@elliottslaughter, can you add this issue to #1032?

What versions of Legion and ROCm are you using?
Our CI has been passing recently and tests ROCm 5.4.3, 5.6.0, 5.7.1, and 6.0.0. So unless you're building with some newer ROCm version, or some flag we're not testing, I don't see why this should be breaking for you.

Legion is at the latest version in stable
Rocm is at 6.1.4.
The same versions of Legion and Rocm do not produce errors on AMD-based systems.
It seems necessary to use HIP with the CUDA backend to reproduce the error.

I missed that you were running on NVIDIA GPUs.
To be honest, I have never run HIP on NVIDIA GPUs. @eddy16112 might know more, he was the one who set up that configuration.

Just a kind reminder of this discussion.
At least having a workaround for this issue would enable working on #1688, which is critical for the PSAAP project.

I think the error is because the version of the hip you are using does not support the conversion of hipJit to CU_Jit anymore. Actually, this piece of code is never used by the hip module. I pushed a fix to disable it. Can you try to patch this commit 477745b31b1bcd3a1b9c1fb172419ccae4ec90e7 ?

It helps though the following patch is also necessary
diff --git a/runtime/CMakeLists.txt b/runtime/CMakeLists.txt
index 871d3a5d8..48f2b5db4 100644
--- a/runtime/CMakeLists.txt
+++ b/runtime/CMakeLists.txt
@@ -625,7 +625,7 @@ if(Legion_USE_HIP)
     target_link_libraries(RealmRuntime PUBLIC CUDA::toolkit)
     # Advertise our driver link to Realm consumers while ensuring libcuda.so isn't in Realm's RPATH
     target_link_libraries(RealmRuntime INTERFACE CUDA::cuda_driver)
-    target_include_directories(RealmRuntime PRIVATE ${HIP_ROOT_DIR}/include)
+    target_include_directories(RealmRuntime PRIVATE ${HIP_INCLUDE_DIRS})
     # for backwards compatibility in applications
     target_compile_definitions(RealmRuntime INTERFACE USE_HIP)

@@ -975,12 +975,14 @@ if(Legion_USE_HIP)
     target_compile_options(LegionRuntime PRIVATE $<$<COMPILE_LANGUAGE:CUDA>:
                            -Xcudafe=--diag_suppress=1444 # Remove once Point class is updated
                            -Xcudafe=--diag_suppress=boolean_controlling_expr_is_constant>)
-    target_include_directories(LegionRuntime PRIVATE ${HIP_ROOT_DIR}/include)
+    target_include_directories(LegionRuntime PRIVATE ${HIP_INCLUDE_DIRS})
+    set_target_cuda_architectures(LegionRuntime ARCHITECTURES ${Legion_CUDA_ARCH})
     # complex reduction ops bring in a public dependency on cuda headers
     if(Legion_REDOP_COMPLEX)
       target_link_libraries(LegionRuntime PUBLIC CUDA::toolkit)
-      target_compile_definitions(LegionRuntime PUBLIC __HIP_PLATFORM_NVIDIA__)
     endif()
+    target_compile_definitions(LegionRuntime PRIVATE __HIP_PLATFORM_NVIDIA__)
+
   elseif(Legion_HIP_TARGET STREQUAL "ROCM")
     set(HIP_LIBRARIES ${HIP_ROOT_DIR}/lib/libamdhip64.so)
     set_source_files_properties(${LEGION_HIP_SRC} PROPERTIES HIP_SOURCE_PROPERTY_FORMAT 1)


HTTP Host Availability (the doctor check crashed)

I NEED HELP FIXING THIS ISSUE, EVERYTHING ELSE IS WORKING FINE EXCEPT HTTP HOST
[✓] Flutter (Channel stable, 3.0.2, on Microsoft Windows [Version 10.0.22000.739], locale en-NG)
• Flutter version 3.0.2 at C:\Packages\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision cd41fdd495 (2 weeks ago), 2022-06-08 09:52:13 -0700
• Engine revision f15f824b57
• Dart version 2.17.3
• DevTools version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
• Android SDK at C:\Packages\Android\sdk
• Platform android-33, build-tools 33.0.0
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[✓] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.16)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
• Visual Studio Build Tools 2019 version 16.11.32602.291
• Windows 10 SDK version 10.0.22000.0
[✓] Android Studio (version 2021.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
[✓] VS Code (version 1.68.1)
• VS Code at C:\Users\YELSIN SADIQ\AppData\Local\Programs\Microsoft VS Code
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22000.739]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 102.0.5005.115
• Edge (web)        • edge    • web-javascript • Microsoft Edge 102.0.1245.44
[☠] HTTP Host Availability (the doctor check crashed)
✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know
about this issue at https://github.com/flutter/flutter/issues.
✗ HandshakeException: Connection terminated during handshake
•
! Doctor found issues in 1 category.

THE ISSUE WAS FROM MY ISP. SOLVED


⚠ Bofrost.nl has degraded performance

In 7478ad2, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1784 ms

Resolved: Bofrost.nl performance has improved in 5c0ec94.


Exclude the numpy backend when reporting coverages

Summary
This PR excludes he numpy backend when reporting coverages. This affects only calculating test coverages.
Related Issues
#10802
#10801
#9942
#9568
#9223
PR Overview

[ ] This PR requires new unit tests [y/n] (make sure tests are included)
[ ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[ ] This PR is backwards compatible [y/n]
[ ] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

The results are:

Before
After

Python 3.6 + TF
91.46%
91.38%

Python 3.6 + TH
89.25%
89.25%

Python 3.6 + C
88.65%
88.74%


How to send pgp/mime emails?

I'm trying to send encrypted emails via mailgun-js but passing the option of 'h:Content-Type': multipart/encrypted; protocol="application/pgp-encrypted"; doesn't do anything. I'm assuming it's calling out to /messages rather than /messages.mime (which would ignore content-type), but even if it did that the mailgun docs indicate that you need to pass a multipart/form-data encoding.
Any ideas?

Hi @bmclain, this is fixied in v2.0.3 but haven't released yet to npm. I'll do my best to handle it this week. Sorry for late response :)

Now you can try newer version.
I'm closing this issue, in case you still have it or face with new one please, open a new one.


Output: Boogie program verifier finished with 0 verified, 0 errors

Hello, I successfully run Boogie on my machine.
Environment
Ubuntu 18.04+mono
Z3
Question
When I try to run a .bpl file which contains many types, axioms, functions, and procedures(please see attached file) ,
I meet this result:
yue@ubuntu:~/TAP/SGX$ mono ~/boogie/Binaries/Boogie.exe sgx_type.bpl
Boogie program verifier version <IP_ADDRESS>03, Copyright (c) 2003-2014, Microsoft.
Boogie program verifier finished with 0 verified, 0 errors
Actually, there are many procedures that could be verified in the file. Codes in the file are created by others and have been verified to work correctly. So I am confused by this result. I think I should get a result saying "finished with xx verified, 0 errors".
Could you please give me any hints about the possible problem?
Thanks for the help!
Code of the sgx_type.bpl file
sgx_type.txt

All the procedures in your input file are decorated with {:inline 1} attribute.  This indicates to Boogie that these procedures should be inlined at their call sites.  Boogie does not verify such inlined procedures instead delegating their verification to their callers.  You should either removed the inlined attribute or add non-inlined procedures that call these inlined procedures to get verification done.


Fix links to mailing lists

@jbayer you seem to be the man in control here

Just realized this isn't even the bosh.io website. Is that on Github? It also has the wrong links.

@cppforlife a question for you

redirected to bosh.io


support flink1.14

support flink1.14

Thanks @wangxiaojing for the contribution, but the end to end test failed, we need to fix it.

Hey @wangxiaojing, do you need any help with this?

Looks like @wangxiaojing doesn't have time to update this PR，@sap1ens Would you like to take over this PR and continue contributing base on @wangxiaojing existed work?

2. Add e2e tests to verify that they pass with both 1.14 and 1.13

@kjatti You're right, would you like to contribute for this ticket?

I help update this PR as there're too many users are waiting this feature.

The CI passed, merging...


colmena build doesn't report instructions to the user with requireFile

$ colmena build --on node-a,node-b
[INFO ] Enumerating nodes...
[INFO ] Selected all 2 nodes.
   (...) ❌ 1s Build failed: Nix exited with error code: 1
[ERROR] Build of 2 nodes failed. Last 10 lines of logs:
[ERROR] cannot build derivation '/nix/store/1khfxa0dmx97wv77qq1zcn9rfycl3l18-citrix-workspace-<IP_ADDRESS>_fish-completions.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/4q5valvk93ik876k68r05lllss5v7bh9-man-paths.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/78pr4yq09i2f931f8f0vivdqf0aahfcw-man-paths.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/51ydcyabqskp1kjvbglpbdnf994zjnjh-system-path.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/dmg1invb23034fsi7llm0h6k1xiz73aj-system-path.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/jq7wnzqwj4cqmh6x0d7ff7478p1vlsfg-nixos-system-entadono-20.09pre-git.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/rwwrsry5c9k01dyshi8v8xwz5hsvrabn-nixos-system-hp-20.09pre-git.drv': 1 dependencies couldn't be built
[ERROR] cannot build derivation '/nix/store/v5f169c76497djjhj4ib1lc6ab7z73jg-colmena-hive.drv': 1 dependencies couldn't be built
[ERROR] error: build of '/nix/store/v5f169c76497djjhj4ib1lc6ab7z73jg-colmena-hive.drv' failed
[ERROR]

It looks like colmena doesn't report instructions to the user with requireFile unless you use the -v option:
   (...) | ***
   (...) | In order to use Citrix Workspace, you need to comply with the Citrix EULA and download
   (...) | the 64-bit binaries, .tar.gz from:
   (...) |
   (...) | https://www.citrix.com/de-de/downloads/workspace-app/linux/workspace-app-for-linux-latest.html
   (...) |
   (...) | (if you do not find version <IP_ADDRESS> there, try at
   (...) | https://www.citrix.com/downloads/workspace-app/
   (...) |
   (...) | Once you have downloaded the file, please use the following command and re-run the
   (...) | installation:
   (...) |
   (...) | nix-prefetch-url file://$PWD/linuxx64-<IP_ADDRESS>.tar.gz
   (...) |
   (...) | ***

I'm using the ee52032e4ced76b14114194e0c8a80d860cce46a build of colmena.

I agree. Now Colmena dumps the full log for failures in the eval and build phases, so it's easier to debug problems like this.

Great, thanks!


Add more basic tests for NavigationServer3D

This PR adds simple tests for basic entity management, empty queries, setters, getters etc.
More serious tests will be added in the next PR.

@Scony Indeed we can. We only now started to merge 4.2-targeting PRs. Before we were merging 4.1.1-targeting PRs.

Thanks!


pref: dispatch to all events causes performance degradation

Describe the bug
when I use collect in the useDrag
collect: monitor => ({
      isDragging: monitor.isDragging(),
      didDrop: monitor.didDrop()
})

source: https://github.com/Himself65/react-dnd-perf-example/blob/274200de09ea040c9f4f1a63053552a4318bcbfc/src/App.js#L25-L28

I found the slow performance in react-dnd because it dispatches all the target
https://github.com/react-dnd/react-dnd/blob/2a3e2db93120c7f73a8579d5622884de04a25f2b/packages/core/dnd-core/src/actions/dragDrop/drop.ts#L21-L33
Reproduction

Way 1

git clone https://github.com/Himself65/react-dnd-perf-example.git
cd react-dnd-perf-example
yarn install
yarn start

Way 2

Live Reproduction
Steps to reproduce the behavior:

Drag the left item like '1', '2', '3'..., to the right part
See Severely slow performance. (and if you add a log in DragItem, and you will find they all re-rendered.)

Expected behavior
text: 'dropped' should be fastly appear
Screenshots
Youtube Video: https://youtu.be/_IIyEDSMVgA
Desktop (please complete the following information):

OS: Windows10
Browser: Chrome
Version  80.0.3987.116

I'm noticing the same problem, are there any solutions or workarounds?

I'm noticing the same problem, are there any solutions or workarounds?


FSL parser v0

TODO

[ ] unittests
[ ] viz example
[x] dedicated CI script

a v0 is already there
many comments:

What level to choose for an Activity ? Is it a single bash command ? an entire Markdown chapter ?
For now markfown files are handled, but very different file types are presents in NIDMresults-examples

Here is the first graph I got (quite big I admit)

@cmaumet considering the graph I attached above, which is impressively big, I suggest we opt for attaching a single activity to a single section in the logs file

@cmaumet  as discussed here is an - buggy- example when I try to use the prov library
>> from prov.model import ProvDocument
>> d = ProvDocument()
>> d.add_namespace("prov", "http://www.w3.org/ns/prov#")
>> d.agent(identifier="RRID:SCR_002823")
---------------------------------------------------------------------------
ProvElementIdentifierRequired             Traceback (most recent call last)
<ipython-input-16-32e33baeea1d> in <module>
----> 1 d.agent(identifier="SCR_002823")

/usr/local/Caskroom/miniconda/base/envs/bids-prov/lib/python3.6/site-packages/prov/model.py in agent(self, identifier, other_attributes)
   1835             of tuples to be added to the record optionally (default: None).
   1836         """
-> 1837         return self.new_record(PROV_AGENT, identifier, None, other_attributes)
   1838
   1839     def attribution(self, entity, agent, identifier=None, other_attributes=None):

/usr/local/Caskroom/miniconda/base/envs/bids-prov/lib/python3.6/site-packages/prov/model.py in new_record(self, record_type, identifier, attributes, other_attributes)
   1603             )
   1604         new_record = PROV_REC_CLS[record_type](
-> 1605             self, self.valid_qualified_name(identifier), attr_list
   1606         )
   1607         self._add_record(new_record)

/usr/local/Caskroom/miniconda/base/envs/bids-prov/lib/python3.6/site-packages/prov/model.py in __init__(self, bundle, identifier, attributes)
    558         if identifier is None:
    559             # All types of PROV elements require a valid identifier
--> 560             raise ProvElementIdentifierRequired()
    561
    562         super(ProvElement, self).__init__(bundle, identifier, attributes)

ProvElementIdentifierRequired: An identifier is missing. All PROV elements require a valid identifier.

@cmaumet I've been doing some modifications

I removed wasAttributedTo links going from entities to FSL
fsl_parser now creates one "group activity" per part (chapters in .md files) and links sub actictivites with a prov:wasInfluencedBy to this group activity

This gives the following graph

@remiadon - thanks for this. I think we need a bit more documentation before I can review this further. Could you:
* Update the top comment in this PR to describe what the PR is doing.

* Add some comments to the CI tests, at minima a description of what each test is doing.

This will help me (and future readers of this repo) better understanding what the code is doing.

@cmaumet both have been done :)

@cmaumet  I just fixed merged conflicts with the newest master branch
Can we merge this before we integrate the new ontology ?
Thx

@remiadon -- as discussed above can you add some comments (e.g. in https://github.com/bids-standard/BEP028_BIDSprov/blob/a902c3def20bcbf81fb57ac5a98bd16fd1f6de09/bids_prov/fsl_parser.py) so that the code is easily to understand later on?

I close this PR. The current FSL parser is based on this PR but has since evolved.


⚠ Guya.moe Proxied has degraded performance

In aded4bb, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 12997 ms

Resolved: Guya.moe Proxied performance has improved in 09136be after 48 minutes.


JdbcTokenStore removes/inserts on every /token request

We started using the JdbcTokenStore and noticed some DuplicateKeyException's when testing with multiple threads.  From looking at the code it looks like the interactions between AbstractAccessGranter, DefaultTokenServices, and JdbcTokenStore leads to a remove and insert of tokens into the DB on every request to /token.
When multiple threads are getting the token for the same username, this leads to DuplicateKeyException because when the remove happens on the first thread (before the insert occurs), the second thread gets back empty results from the DB and creates a new token.  By the time the second thread tries to write to the DB, it finds that there is a token already there.
In AbstractTokenGranter
	protected OAuth2AccessToken getAccessToken(ClientDetails client, TokenRequest tokenRequest) {
	    return tokenServices.createAccessToken(getOAuth2Authentication(client, tokenRequest));
	}

In DefaultTokenService.createAccessToken
	// Re-store the access token in case the authentication has changed
	tokenStore.storeAccessToken(existingAccessToken, authentication);
	return existingAccessToken;

In JdbcTokenStore.storeAccessToken
	if (readAccessToken(token.getValue()) != null) {
	    removeAccessToken(token.getValue());
	}

By the way, originally this lead to two tokens in the DB, which lead to errors in every /token request for that username.  We had to make the 'user_name' field in the 'oauth_access_token' table unique.  This at least turns the problem into a sporadic problem, versus locking the username from ever being authenticated.

I had the same problem,
		if (accessToken != null
				&& !key.equals(authenticationKeyGenerator.extractKey(readAuthentication(accessToken.getValue())))) {
			removeAccessToken(accessToken.getValue());
			// Keep the store consistent (maybe the same user is represented by this authentication but the details have
			// changed)
			storeAccessToken(accessToken, authentication);
		}

JdbcTokenStore::getAccessToken is not thread safe.
I made 'authenticate_id' field in the 'oauth_access_token' table unique.

@liuneng1994
To prevent the excessive removal and insertion of the key into the DB, we keep a threadsafe reference to the last token value (accessToken::getValue) that was read by JdbcToken::getAccessToken.  Then, when JdbcTokenStore::storeAccessToken is eventually called, it checks if this is the same token that was read previously in the same thread.  If it is, then do not remove/insert it.
For us, that IF statement that you posted in your message was not the code that lead to the constant remove/insert.  In our case, it is the DefaultTokenService::createAccessToken method that is requesting that the retrieved token be saved.
In DefaultTokenService.createAccessToken
// Re-store the access token in case the authentication has changed
tokenStore.storeAccessToken(existingAccessToken, authentication);
return existingAccessToken;

But I can see how in your case, that code you provided, can lead to similar behavior.  I just checked our logs, and that if statement in JdbcTokenStore::getAccessToken has never returned TRUE for us, so we have not encountered it.

How to solve this problem?
My SpringBoot service is deployed on two servers, There are currently many clients that need to request token(use client_credentials and JdbcTokenStore) and they use the same set of clientId and clientSecret。I don't know how to solve JdbcTokenStore removes/inserts on every /token request。
When client-A get token and  carries token to access the API, client-B request token at the same time。I found client-B‘s request would delete first then insert a same token。。。client-A carries token to access the API  throws an exception because there no token in DB，why need delete first？I don't understand and  I think it's possible to generate multiple effective tokens through OAuth。。。


SENTENCE_STARTERS ignores defined language

PragmaticSegmenter::AbbreviationReplacer::SENTENCE_STARTERS is a constant that does not care about the defined language:
SENTENCE_STARTERS = %w(A Being Did For He How However I In It Millions More She That The There They We What When Where Who Why)

I suggest it to be defined in PragmaticSegmenter::Languages::SomeLanguage , with an empty array as default.
If given the explanation/regex on how to analyze a dataset for appropriate sentence starters), I could provide the array for German.

Thanks, great point. In that case this method would also change depending on the language https://github.com/diasks2/pragmatic_segmenter/blob/master/lib/pragmatic_segmenter/abbreviation_replacer.rb#L62-L92

Oh, true! And besides the gsub chaining GC issue, one could refactor it to pass an array or hash containing the regexs to it, this way one could store these as a language constant too.

Thanks for all your help and pointing out these issues. I really appreciate it! I'm kind of busy at the moment so I'm not sure when I can get to these...but if you would like to submit a pull request I would welcome it with open arms.

@diasks2 I've just created a PR for the GC reduction. As for this issue here I don't yet understand enough of how pragmatic_segmenter works, but believe it should be enough to set PragmaticSegmenter::AbbreviationReplacer::SENTENCE_STARTERS as empty array and only overwrite it with the english words in PragmaticSegmenter::Languages::English::AbbreviationReplacer ?

@maia Thanks for the PR on the GC reduction! As for this issue - yes, I think that would work.

I think your PR (https://github.com/diasks2/pragmatic_segmenter/commit/f1cf4bd8dc8f4c771024f05f7181ba2d95ff6e47) closes this issue. Thanks for your help! Much appreciated! :+1:


Remove duplicate pre-commit req

Signed-off-by: Gábor Lipták<EMAIL_ADDRESS>

Anything else you would like see here?


WIP: Zookeeper Charm Configuration

Add various charm configuration options.
Zookeeper configuration is changed to have specific configs as well as an additional-properties config that allows for a more advanced zookeeper.properties outside of the charm configs.

This probably needs more thought - we should not be including a config option to allow arbitrary lists of config options to this charm. Please work with @marcoppenheimer and @delgod and spec out those config options we need to expose at this point :slightly_smiling_face:


Add Shapella fork times

Added the timestamp for Shanghai & epoch for Capella decided on https://github.com/ethereum/pm/issues/729.
Also renamed SHARDING to DENEB.

Can we not mix the two PRs in one? Is there any reason to have to change SHARDING for DENEB in time for the Goerli fork?

@potuz fixed - will open a separate PR for the SHARDING -> DENEB change


Improved chunking of TTS

Issue

Specifically related to TTS  implementing Chunking is a bit challenging for users.

Acceptance Criteria

Chunking by having a native interface for different LLM responses
Return TTS data as blobs through events when using chunking

@dvonthenen

This PR https://github.com/deepgram/deepgram-go-sdk/issues/240 obsoletes this one.


bug: Trouble to install nvim-orgmode

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0-dev-37+gccc0980f8
Operating system/version
Mac
Describe the bug
Does not open the agende or the capturing mode.
Steps To Reproduce
In LazyVim
Installed nvim-orgmode.
Press oa   ==> nothing happens
Press oc  ==> nothing happens
Add under plugins/nvim-org.lua:
return {
  "nvim-orgmode/orgmode",
  dependencies = {
    { "nvim-treesitter/nvim-treesitter", lazy = true },
  },
  event = "VeryLazy",
  config = function()
    -- Load treesitter grammar for org
    require("orgmode").setup_ts_grammar()

    -- Setup treesitter
    -- Commented out because got following warning:
    -- Missing required fields in type `TSConfig`: `modules`, `sync_install`, `ignore_install`, `auto_install` [missing-fields]
    -- require("nvim-treesitter.configs").setup({
    --   highlight = {
    --     enable = true,
    --     additional_vim_regex_highlighting = { "org" },
    --   },
    --   ensure_installed = { "org" },
    -- })

    -- Setup orgmode
    require("orgmode").setup({
      org_agenda_files = "~/Documents/org-files/**/*",
      org_default_notes_file = "~/Documents/org-files/refile.org",
    })
  end,
}

Expected Behavior
Open Agende or Capture Mode.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

It works for me with the recommended configuration from the repo. Also this is a personal user configuration, so I believe it's more appropriate for the Discussions section and not an issue of Lazyvim.

It works for me with the recommended configuration from the repo. Also this is a personal user configuration, so I believe it's more appropriate for the Discussions section and not an issue of Lazyvim.

Ok thanks. Do you know how can i troubleshoot this problem? And why i get the warning message : Missing required fields in type TSConfig: modules, sync_install, ignore_install, auto_install [missing-fields]

You can disregard these messages. They come from Lua LSP. Alternatively, you could also just extend the default Lazyvim Treesitter configuration to include these options for Treesitter. I didn't do anything else except from copy/pasting the instructions for lazy.nvim. Then I just pressed <leader>oa and the agenda menu opened.

You can disregard these messages. They come from Lua LSP. Alternatively, you could also just extend the default Lazyvim Treesitter configuration to include these options for Treesitter. I didn't do anything else except from copy/pasting the instructions for lazy.nvim. Then I just pressed <leader>oa and the agenda menu opened.

Okay that's really interesting. But this should work with a minimal.lua config right? if other plugins causing this problem. Can You maybe me provide a minimal.lua config so i can test it? I tried to put the configurations in this repro.lua file under plugins with {...} but i think maybe i did something wrong.

1. mkdir ~/.config/newstarter && cd ~/.config/newstarter
2. git clone https://github.com/LazyVim/starter .
3. rm -rf .git*
4. `NVIM_APPNAME=newstarter nvim` and wait for installation of plugins to finish
5. Quit Neovim and start again with: `NVIM_APPNAME=newstarter nvim lua/plugins/orgmode.lua`
6. Paste the contents of the installation steps for `lazy.nvim` mentioned [here](https://github.com/nvim-orgmode/orgmode#installation) in the file that you opened.
7.

I didn't test anything else, since I don't use the plugin and don't know how it works.


Get rid of the @web5/api/browser bundle

We now know how to use @web5/api in docusaurus without using the /browser bundle.
Reference: https://github.com/TBD54566975/bundler-bonanza/pull/57
Now we need to replicate it here.

can you describe more

@leordev this one is done, yeah? can we close?

Correct @angiejones


ETL examples are unclear and hard to use

Filing some feedback from SpotHero earlier today so we can track and improve this.
We have some Python scripts as examples to ETL data into datahub. However, it was a SpotHero developer's experience that these made onboarding difficult.
Specific issues:

Python 2.7 rather than Python 3
Deals with large, untyped json blobs that make it hard to A) read and B) determine if it matches the schema
Was unclear if Python was the suggested method. Companies are likely to use this a little more literally and use them as a basis for their own ETL scripts; Python is perhaps not the best choice. Even at LI we don't use Python for these; most (if not all) our ingestion pipelines are in Java.

So specific action items:

If we keep the Python example around, upgrade to Python 3 and see how else we can improve typing (are there avro / pegasus bindings?)
Write Java or other language examples too.
Write better documentation around best practices. Make it clear these are just examples. Give other examples of what we do at LI (we have instrumented services to write metadata and also some crawlers and also some Azkaban jobs; it totally depends on the source data and how it can be extracted).

cc @keremsahin1

I believe we've already migrated all the ETL scripts to Python 3 and updated the doc to reflect that: https://github.com/linkedin/datahub/tree/master/metadata-ingestion
That said, agree that the Python avro binding is not the easiest to use. We can also do a better job communicating the expectation, and finally we can also use more Java examples.

Thanks @jplaisted & @mars-lan . I agree that we should consider to provide Java based ETL code maybe closer to what we use internally at least for some of the most wanted platforms.

Ideally we'll find the SQLAlchemy-equivalence in Java so we can have one ETL that works across many systems.

I also agree that Java based ETL solution. The reason is that Datahub has had built-in Serders for different aspects of an entity. If the ETL users are just feeding in data with JSON format (compared to the current Avro), and run something like
java  -jar ETL.jar produce -d data.json

We are also trying to build a java based ETL solution.
This ETL solution is based on the following design considerations:

Should sit outside the datahub tool, so as to promote loose coupling in handshakes between internal data systems and datahub tool
should be able to host adapters for various kind of source systems, so that it becomes as easy as plugNplay
adapters would be having business logic, specific to the source system

Creating MCE messages in JSON-interpolation way(the way python mce-cli and others are doing currently) is looking error prone as

JSON blobs are very huge; hard to test and debug
string interpolation is error-prone, hard to maintain and prone to formatting issues.

I see java bindings being generated in the build along with JSON. Is it a good idea to publish them as jar, so that can be used for programmatic contracts, instead of relying only on AVSC? This could also be exposed as multiple-language bindings to promote ecosystem around.
Thanks

The metadata-events/mxe-avro-1.7 module's jar should already contain the Java generated avro classes in it.
We should probably publish it to a maven repository, along with a lot of our other jars. The only artifacts we have right now are our docker images on commit to master, and source code tars on release. I'll make a separate issue for that.

Also fwiw we really only use Java for our pipelines that emit MCEs at LI. For much the reasons you describe. Again, the original idea behind the Python scripts in open source was that they were smaller and easier to set up. But I think since most people would prefer Java due to the type bindings we should provide those examples.


registry.js typo

https://github.com/prayerslayer/js.spec/blob/master/lib/registry.js#L14
Symobl should be spelled Symbol

Don't remember if this was merged or not, but since the registry is gone there's no need to fix it anyways.


GH-42107: [C++][FS][Azure] Ensure setting BlobSasBuilder::Protocol

Rationale for this change
BlobSasBuilder::Protocol is used in BlobSasBuilder::GenerateSasToken() and it doesn't have the default value. If we don't specify it explicitly, GenerateSasToken() result may be unexpected.
What changes are included in this PR?
Set BlobSasBuilder::Protocol explicitly based on AzureOptions::blob_storage_scheme. It's https by default but can be http when enable_tls=false query parameter is specified.
If it's http, both of https and http are accepted as protocol.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.

GitHub Issue: #42107

@github-actions crossbow submit test-conda-cpp-valgrind

So the blob_storage_scheme option was entirely ignored up to now?

No. It's used to create a BlobServiceClient:
https://github.com/apache/arrow/blob/512d2458ff777f15354ee2a88bde7723ec3d5035/cpp/src/arrow/filesystem/azurefs.cc#L301-L303
https://github.com/apache/arrow/blob/512d2458ff777f15354ee2a88bde7723ec3d5035/cpp/src/arrow/filesystem/azurefs.cc#L364-L389

And what about dfs_storage_scheme? It seems ignored at well.

It's also used to create a DataLakeServiceClient:
https://github.com/apache/arrow/blob/512d2458ff777f15354ee2a88bde7723ec3d5035/cpp/src/arrow/filesystem/azurefs.cc#L305-L307
https://github.com/apache/arrow/blob/512d2458ff777f15354ee2a88bde7723ec3d5035/cpp/src/arrow/filesystem/azurefs.cc#L391-L417

Do we have other options that are ignored like this?

No, we don't have.

No. It's used to create a BlobServiceClient:

Ah, I had misread the code. Sorry!

I merge this as-is.
I'll add {blob,dfs}_storage_scheme validation as #42134.


Swift overriding a function from commonMain interface

Hey!
I have trouble figuring out how I can use this library to help override suspend functions from an interface declared in commonMain of a KMP project.
I am unable to share my entire code, but this is what it generally looks like (for the sections I'm confused on).
Project structure is similar to this:

KMP Module

shared

exampleModuleA

exampleModuleB

With the Android and iOS app in their own repos and ingesting the KMP Module as a submodule (in Android) and as a static framework (in iOS).
I have an interface (ExampleManager) in a file (ExampleManager.kt) located in KMPModule/exampleModuleA/commonMain.
import com.rickclephas.kmp.nativecoroutines.NativeCoroutines
import com.example.me.multiplatform.exampleModuleB.extensions.Result

interface ExampleManager {
    @NativeCoroutines
    suspend fun signUp(
        username: String,
        password: String,
        email: String,
    ): Result<Unit, String>

    @NativeCoroutines
    suspend fun accountDoesExist(email: String): Result<Boolean, SignInError>

    fun updateName(name: String)
}

Due to necessary iOS libraries being unable to be used in the KMP Module's commonMain, the implementation of this interface is created in the Android app code and the iOS app code and injected into the commonMain code with Koin.
Example implementation in iOS:
class IOSExampleManager: ExampleManager {
    // overridden functions here
}

I am using KMP-Coroutines version 1.0.0-ALPHA-10 (for Kotlin 1.8.21 compatibility). I see it does generate the functions within a new NativeKt interface, but how may I override this on iOS/Swift to provide the implementation? I have read the README on the interface workaround with the extension (as well as this thread https://github.com/rickclephas/KMP-NativeCoroutines/issues/103), but I'm still confused on how I can override a method from the interface (e.g. signUp). Thanks!

Hi! At the moment the library only supports Kotlin to Swift cases. Swift to Kotlin cases (like implementing an interface) are still a work in progress. Please keep an eye on https://github.com/rickclephas/KMP-NativeCoroutines/issues/42

Ah, I see. Thanks for the quick reply and the great work with this library! I'll go ahead and close this and refer to https://github.com/rickclephas/KMP-NativeCoroutines/issues/42.


NextCloud 11.0.1 has been released

https://nextcloud.com/changelog/
Please update the Dockerfile. Thanks.

Done


Smart Scrolling

Describe your idea
Currently, the detox scrolling API does not account for the visible portion of the scroll view and attempts to scroll from the edge. This approach is ineffective when elements like toasts or snack bars partially obscure the scroll view. The detox scroll functionality should be enhanced to intelligently calculate the starting position, considering only the visible parts of the view.

Duplicate of #3972


acl-anthology.md file updated

This PR is linked to the issue #2109 .
As the support for Solr has been droped, "Indexing the ACL Anthology with Anserini" has been updated to just use Pyserini to index ACL Anthology.

Codecov Report
Patch and project coverage have no change.

Comparison is base (30269d6) 58.93% compared to head (1df8397) 58.93%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##             master    #2112   +/-   ##
=========================================
  Coverage     58.93%   58.93%
  Complexity     1188     1188
=========================================
  Files           194      194
  Lines         11328    11328
  Branches       1486     1486
=========================================
  Hits           6676     6676
  Misses         4170     4170
  Partials        482      482

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


Cannot adjust z-index for lean-overlay

The z-index for lean-overlay cannot be adjusted because the index itself is hard coded and dynamically added by JavaScript in the openModal: function(options) function.
There's supposed to be a CSS style that optionally allows for an override of the default value which is set at 999, but adjusting the z-index via styling has no affect, again because the z-index is set dynamically.

You shouldn't need to change it as it will then conflict with other modals, but you can always use a !important if for whatever reason you have to change it.


OKD >= 4.11 installs may fail on various AWS region due to AWS S3 policy change

OKD 4.11 / 4.12 installation on AWS will report errors as shown below.
$ ./openshift-install create cluster --dir t9
...
level=info msg=Creating infrastructure resources...
level=error
level=error msg=Error: error creating S3 bucket ACL for t9-r5h2p-bootstrap: AccessControlListNotSupported: The bucket does not allow ACLs
level=error msg=	status code: 400, request id: YGX5Z64B70KEB5W4, host id: wnWfplUMk+SKTydGm66E47JP4F7BaKC7WTfgj5goCJAJoGFc+IpyBF0nw5aIQfeMGuQHTL0NM18=
level=error
level=error msg=  with aws_s3_bucket_acl.ignition,
level=error msg=  on main.tf line 62, in resource "aws_s3_bucket_acl" "ignition":
level=error msg=  62: resource "aws_s3_bucket_acl" ignition {
level=error
level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failure applying terraform for "bootstrap" stage: failed to create cluster: failed to apply Terraform: exit status 1
level=error
level=error msg=Error: error creating S3 bucket ACL for t9-r5h2p-bootstrap: AccessControlListNotSupported: The bucket does not allow ACLs
level=error msg=	status code: 400, request id: YGX5Z64B70KEB5W4, host id: wnWfplUMk+SKTydGm66E47JP4F7BaKC7WTfgj5goCJAJoGFc+IpyBF0nw5aIQfeMGuQHTL0NM18=
level=error
level=error msg=  with aws_s3_bucket_acl.ignition,
level=error msg=  on main.tf line 62, in resource "aws_s3_bucket_acl" "ignition":
level=error msg=  62: resource "aws_s3_bucket_acl" ignition {
Seems to be described here https://access.redhat.com/solutions/7007136
Can you provide a fixed 4.11 stable version?

OKD 4.11 / 4/12 in AWS

How reproducible

Dupe of #1573


fix: aes_decrypt params and code styling

Summary by CodeRabbit

Bug Fixes

Improved handling and decryption of serial numbers for more consistent and secure data management.
Enhanced message parsing by ensuring the decrypted data is correctly formatted as bytes, improving data processing accuracy.

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 24.33%. Comparing base (6c91350) to head (14c1452).

Files
Patch %
Lines

midealocal/device.py
0.00%
3 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #175   +/-   ##
=======================================
  Coverage   24.33%   24.33%
=======================================
  Files          78       78
  Lines        6794     6794
=======================================
  Hits         1653     1653
  Misses       5141     5141

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add RPC connections pool

[x] Implement simultaneous connections to different validators' nodes
[x] Remove arbitrary instantiation of web3 clients

@superbeefyboy, I assume there is no side effect when using different endpoints for reading operations and I didn't find write usages


Where is the code for Supplementary Information?

Dear Professor,
I want to know where is the code for Supplementary Information. Since there are lots of graphs and tables in the paper and the supplementary Information, where can I find the code for figures in Supplementary Information and paper?
Thank you so much! Very appreciated!

Please wait for a while as we are busy with the manuscript revision. All the code will be made available. Thank you for your attention.

Got it! Thanks a lot! Very appreciated!


Kafka scaler doesn't scale beyond 100 replicas

Report
According to  Kafka scaler documention:

In other words, by default the maximum replicas is the same as the partitions number.
But, if the partitions number is more than 100 the scaler doesn't scale to more than 100 replicas.
Expected Behavior
If we have a topic with 300 partitions we expected that the maximum replicas number will be 300.
Actual Behavior
The scaler maximum replicas is 100.
Steps to Reproduce the Problem

Create a Kafka topic with more than 100 partitions, for example 300 partitions
Create deployment that consume messages (with sleep) from the created kafka topic
Create a scaledobject with Kafka scaler (don't set the maximum replicas field)
Produce a lot of messages to the created Kafka topic
The replicas number will stuck at 100 and don't at 300 as excepted

Logs from KEDA operator
We can see the problem via the HPA

You can see that via the target field should be scale up but because the  maximum replicas is 100 we stuck on 100 replicas.
KEDA Version
2.6.1
Kubernetes Version
1.23
Platform
Any
Scaler Details
Kafka
Anything else?
Reason
This bug is happend duo the implementation in Kafka scaler to the maximum scale as the partitions number.
if !s.metadata.allowIdleConsumers {
	// don't scale out beyond the number of topicPartitions
	if (totalLag / s.metadata.lagThreshold) > totalTopicPartitions {
		totalLag = totalTopicPartitions * s.metadata.lagThreshold
	}
}

This is the mechanism that limit the replicas to the number of partitions. This mechanism actually send "fake" metrics to the HPA in order to don't scale beyond the partitions number.
But, the HPA that created is limit to 100 replicas by default so we can't scale beyond 100 replicas.
Workaround
I found a workaround for this bug.
You can simply write in the Kafka scaler:
maxReplicaCount: 10000

In this case we still don't scale beyond the partitions number but will be able to scale up to 10000 in case of topic with 10000 partitions.

100 is the default value for maxReplicaCount, so if you don't specify this value, 100 will be used, see the doc: https://keda.sh/docs/2.6/concepts/scaling-deployments/#scaledobject-spec
What prevents you in setting maxReplicaCount: 300 ?

100 is the default value for maxReplicaCount, so if you don't specify this value, 100 will be used, see the doc: https://keda.sh/docs/2.6/concepts/scaling-deployments/#scaledobject-spec
What prevents you in setting maxReplicaCount: 300 ?

I can configure the maxReplicaCount field. But as document in the Kafka scaler the default maxReplicaCount is as the partitions number. This is what I also except, that if I have a topic with 300 partitions by default the maxReplicaCount will be 300.

It's clearly written there: https://keda.sh/docs/2.6/scalers/apache-kafka/

That is, if maxReplicaCount is set more than number of partitions, the scaler won’t scale up to target maxReplicaCount.

But we are definitely open in improving the docs clarity, though this behavior is definitely not a bug.

It's clearly written there: https://keda.sh/docs/2.6/scalers/apache-kafka/

That is, if maxReplicaCount is set more than number of partitions, the scaler won’t scale up to target maxReplicaCount.

But we are definitely open in improving the docs clarity, though this behavior is definitely not a bug.

I am not sure that this is not a bug.
In the docs is written that by default maxReplicaCount = topic partitions number' but its clearly not true. The real behavior is maxReplicaCount = min(topic partitions number, 100)'
I will also mention that I think that if I have a topic with 300 partitions I would like that without any configuration (by default) the scaler will scale up to 300 replicas and I would not need to configure maxReplicaCount: 300 manually.

In the docs is written that by default maxReplicaCount = topic partitions number but its clearly not true.

Could you show me, where is this written?

In the docs is written that by default maxReplicaCount = topic partitions number but its clearly not true.

Could you show me, where is this written?

Ahh ok, I understood.
In the docs is written that That is, if maxReplicaCount is set more than number of partitions, the scaler won’t scale up to target maxReplicaCount., or in other words maxReplicaCount <= topic partitions number
But no one say that maxReplicaCount = topic partitions number.
This is very tricky. I already open a PR in the docs about it, I will change it a little bit.
This is not a bug this is unclear behavior but I will still say (or ask for feature) that I would like that buy default maxReplicaCount = topic partitions number

Cool, I am glad that we understand each other :) If you are going to propose change to the docs, please change it in more versions, not just 2.6, (add please at least 2.5 and 2.7).

Do you agree that the reasonable behavior is that maxReplicaCount = topic partitions number?
As a simple user this is the behavior that I want. If I have a topic with 300 partiontions I want that my deployment will be able to scale to 300 by default.
I don't know if to call this issue a bug or feature request but I think this is an issue that should be solved.

Ok, I will open a feature request for this issue.
Can you approve my PR in the docs about this issue? I think that right now the docs really unclear (my PR solved this issue)

I would find it surprising if the maxReplicaCount defaulted to 100 but that value got ignored and instead allowed 300 replicas. Are there any other triggers that override and allow more replicas than the maxReplicaCount?
If we're looking to have unsurprising behavior, then it feels like clarifying the documentation is the better approach for this one.

There aren't any scalers that exceedes maxReplicaCount. This has been already resolved in the docs.


No data is shown

Laravel Rest Api Version
2.8.7
Laravel Version
11.30.0
PHP Version
8.3.13
Database Driver & Version
No response
Description
Following the installation instructions and creating the quick-start resource, then no data is displayed when hitting the https://myapp.test/api/users.
I have added the name and email to the fields()
Steps To Reproduce
new laravel 11 app, and then follow the installation in the documentation.

Working well on my side please make sure others routes in your web.php are working
No response might not be related to the package, you would have a php error

other routes are working
{
  "data": {
    "actions": [],
    "instructions": [],
    "scout_instructions": [],
    "fields": [
      "id",
      "name",
      "details"
    ],
    "scout_fields": [],
    "limits": [
      10,
      25,
      50
    ],
    "scopes": [],
    "relations": [],
    "rules": {
      "all": [],
      "create": [],
      "update": []
    }
  }
}

I have a policy

I have tried with authentication, without authentication, with gates and without gates all the same I created a new Product resource, seeded 50 entries still the same

my repository is here: https://github.com/rabol/encrypt

Working with your project on my side:

I removed authentication middleware and authorizations
https://laravel-rest-api.lomkit.com/digging-deeper/authorizations

Also it could be possible your 'no response' is a redirection response to login ... 😅

Well... I simply did what was in the documentation and the 'default' /api/user is working with the authorization and when clicking the authorise icon on the /api-documentation page and enter a valid bearer token it say 'Authorised'
Also I wold expect that api/resource will display all resources, which IMHO is normal, but I can see from above that one have to do /api/resource/search
My assumptions on endpoints is from https://jsonapi.org/


[Feature] Introduce metrics about the busyness of compaction thread

Search before asking

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

Motivation
This metric monitors how busy the writer is, and if it is too busy, it can alert the user to add resources in advance.
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I would like to work on this. Please assign this ticket to me.


Updating accordion styles

Updating the accordion styling to match updated designs.

Is that story you deleted no longer relevant?

Correct. I did the changes with Blaze and moving forward we won't be using that design pattern.

Just chiming in here - that story may not have been a real world use case, but was highlighting issues with margin collapsing that came up at one point. The story was probably still relevant to illustrate that issue that might occur.

Just chiming in here - that story may not have been a real world use case, but was highlighting issues with margin collapsing that came up at one point. The story was probably still relevant to illustrate that issue that might occur.

I'll put in a PR to add it back in then.


[NCL-7628] Fix chart and card descriptions

New descriptions will be pushed including additional statistics boxes improvements. All PR changes needs to be checked again.


Auto switch profiles based on file type

A feature to automatically switch profiles based on file type would be majorly beneficial. It is much more convenient and performant than manually switching profiles each time I open a file/folder.

/duplicate
https://github.com/microsoft/vscode/issues/174211

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Problem with jquery plugins and server side rendering

Hi, I have got stuck in a propensity of using : https://uiv.wxsm.space/typeahead
Whenever I add it in plugins with ssr: false it does not produce the dropdown section on page refresh . because the produced html through server rendering ,  does not have it .
When I set the ssr : true , it shows that window is undefined.
How should i use this plugin in nuxt

@ahadyekta, you mean bootstrap plugin, right? (jquery?)

This package is bootstrap components built for vue.
When I use it , the server and client rendering don`t match because the jquery makes some html that only client has it. The server rendering does not run jquery. So the SSR result is not what is expect.

@ahadyekta Try putting typehead component in <no-ssr></no-ssr> tags.

window is undefined is a bug of uiv lib, and already been fixed in the latest version.

Do you still have this isssue in 1.4.0?


Smokey tests fail to run on Windows

Smokey Detector includes a Windows incompatible library: sh. This is clearly noticed when running tests locally.
sh will not support Windows
pbs will no longer be supported
ImportError while importing test module 'H:\Development\SmokeDetector\test\test_chatcommunicate.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
test\test_chatcommunicate.py:3: in <module>
	from chatcommunicate import *
chatcommunicate.py:10: in <module>
	import chatcommands
chatcommands.py:13: in <module>
	from gitmanager import GitManager
gitmanager.py:1: in <module>
	from sh import git
h:\Anaconda\lib\site-packages\sh.py:36: in <module>
	support." % __version__)
E   ImportError: sh 1.12.9 is currently only supported on linux and osx. please install pbs 0.110 (http://pypi.python.org/pypi/pbs) for windows support.

Is there an alternative we can utilize that will allow developers in both environments to work without the above error?

VPS, Windows Subsystem for Linux maybe, and also VMs.
I don't think Smokey was designed to be Windows compatible...
Sent from my iPhone.  Please excuse any typos, as they are likely to happen by accident.

On Feb 22, 2017, at 08:59, A Wegner<EMAIL_ADDRESS>wrote:
Smokey Detector includes a Windows incompatible library: sh. This is clearly noticed when running tests locally.
sh will not support Windows
pbs will no longer be supported
ImportError while importing test module 'H:\Development\SmokeDetector\test\test_chatcommunicate.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
test\test_chatcommunicate.py:3: in
from chatcommunicate import *
chatcommunicate.py:10: in
import chatcommands
chatcommands.py:13: in
from gitmanager import GitManager
gitmanager.py:1: in
from sh import git
h:\Anaconda\lib\site-packages\sh.py:36: in
support." % version)
E   ImportError: sh 1.12.9 is currently only supported on linux and osx. please install pbs 0.110 (http://pypi.python.org/pypi/pbs) for windows support.
Is there an alternative we can utilize that will allow developers in both environments to work without the above error?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I disagree @teward. For a long time it worked just fine on Windows. My Zephyr bot is built using the same architecture as Smokey.
It is the gitmanager module itself that makes it Windows incompatible, not Smokey as a whole.

Well, I have an evil-potential solution.  Basically, looking at gitmanager, we can try and determine if the system is Windows or not and load a custom library that relies on subprocess.Pcall() and similar to handle git calls.  I can probably write this 'layer' but it'll be a very hacky approach to it.  And it'll take time for me to set up a testing environment.
The core issue is that sh is just a wrapper for the git commands being called on the shell - creating a Windows-compatible wrapper shouldn't be infinitely hard.  Making it all work proper, that may be tricky.

Notes: This is going to be a massive hack - we'll need the library to exist in nocrash and in gitmanager.

So, I've looked into this a little.  It'll be a hackish mess where we have to replace the sh library with, essentially, a single git command and have to specify the commands we want to execute as a string passed to a subprocess call.  This is... not very pretty actually, and very hard to actually get working the same way that sh's git functionality operates.
Even with such hackish approach, it's got some headaches and evils with it, such as we then have to strip shell colors, etc. and we have to reapproach how we handle exit codes and git calls in many places.  For now, I'm going to mark this as 'status: declined', but we can revisit this in the future when we're all a bit less busy.  Between me, ArtOfCode, and Undo, we are all trying to figure when Smokey would be run in Production environments, and we can't think of any - we all currently run in Linux environments, either on our own systems or EC2 instances, or VPSes, or other such environments which support the sh module.

As a contributor who does not have a Linux environment readily available, I find this very disappointing.

@AWegnerGitHub I think this is only a temporary state - we can revisit this when the primary developers are less busy, but not at this second.

Note: The current approach will be to check if we're on Windows, and disable Git functionality there.  That way, we don't have to worry about 'git' failures.  (This may fail Flake8 though, not sure...)

I created a docker env that can run SmokeDetector on any system that can support Docker
https://github.com/Charcoal-SE/SmokeDetector/pull/541

Is Docker a good-enough solution, @AWegnerGitHub?

@AWegnerGitHub indicated in Charcoal HQ they'd test the docker instance yesterday.  I did point them at my "Don't Support Git Functions" warning approach for Windows runs - untested, but ultimately doesn't require additional containerizaiton, etc. on the host system.  And eliminates the git function issues that @AWegnerGitHub  was complaining about.
This approach is in https://github.com/Charcoal-SE/SmokeDetector/tree/windows_git_warnings, also in PR #544, and one or both approaches may be useful enough for them.


Can not turn off the SIP.

Describe the bug
After disabling the SIP in recovery and restart, the SIP is still enabled.
I entered Recovery by selecting it in the boot picker: Recovery (dmg). Maybe I did it in a wrong way?
Expected behavior
The SIP should be disabled.
Configuration

HaC Mini version : 2.4
OSX version : 10.15.1
NUC model : NUC8i7HVK
Boot SSD model and protocol :
First DIMM model : Kingston HyperX Impact DDR4-2666 16GB
Display port(s) used : Mini-DP
Display resolution(s) : 2K
Any TB3 devices: None yet.
Any USB devices: Mouse receiver, Keyboard, etc.

Modifications
None

And why is it so slow to get into the Recovery? It took me several minutes waiting for the progress bar to show up.

It could not be disabled in that way. Check below:
https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/config.plist/kaby-lake#nvram

In 10.15, besides @dickding said, you may also need sudo mount -uw / after rebooting.

Thanks!
Some funny idea came to my mind that made me believed it may work the same as Mac, but obviously not, still the same as we did in Clover...
So what is the significance of enabling SIP by default in this project? Besides, does that mean the Recovery is useless in Hackintosh?

This project is designed to build the first real secure hackintosh. Eventually secure boot option in installer will be default (opt out). Intel is unique that it allows us to secure the boot almost as good as T2. https://osy.gitbook.io/hac-mini-guide/details/secure-boot

This project is designed to build the first real secure hackintosh. Eventually secure boot option in installer will be default (opt out). Intel is unique that it allows us to secure the boot almost as good as T2. https://osy.gitbook.io/hac-mini-guide/details/secure-boot

HaC Mini 2.4 successfully implemented SecureBoot.

#78


Update injector.js

In my case, I'd like to change the path to the scripts in the end. So my "app" folder is not called app anymore. I was sucessful removing it, but I missed an option to prefix the new path with the new folder name.
Example:
 injector: {
                options: {
                    ignorePath: 'app/',
                    addRootSlash: false,
                    prefix: 'cyclone/'
                },
                index: {
                    files: {
                        'wwwroot/default/index.html': [
                            'app/**/*.module.js',
                            'app/**/*.js',
                            'app/**/*.css'],
                    }
                }
            }

@Hobart2967 Thanks for the PR. I'd hapilly merge it with a unit test and an updated README :+1:

Thanks! :) Happy to find one of the competent developers watching for their pull request! TOP! (y)

Done modifying :)

Heya :) When will there be a new version including this so I can replace my commit version by the official in my npm config?

I'm waiting for a feedback from @joakimbeng


Add option to hold inbound transport sessions for longer than processing the message

When building an agent that interacts with other agents that don't have an endpoint (lets say you're a mediator), you can communicate with the other agent by using the inbound transport as a return route.
When we have auto accept for mediation requests enabled, and also auto accept for connections enabled this works pretty well. The response is created when we receive the message (e.g. we send the mediate-grant directly as response to the mediate-request).
However when auto accept is not enabled and the external controller would like to decide whether to respond to an incoming message it is not possible to respond. The other agent has an endpoint of didcomm:transport/queue which makes it impossible to send a message.
We should look at adding an option to delay the termination of the inbound route, so it gives time to create a response to the incoming message. Another option is to require autoAcceptConnection and autoAcceptMediationRequests to be enabled when interacting with agents without an inbound transport.
I recently interacted with a discord JS library that managed this pretty nicely I think, which we can maybe us as inspiration. Whenever a command is invoked you have 3 seconds to respond to the incoming message, if you want to reply you should invoke a deferReply method which gives you 15 minutes to respond. If deferReply is not called, you can't reply anymore directly
Maybe we can look at something like the following:

If a response is created and sent over the channel which also closes it (http can only give 1 response), the channel is already closed. Nothing we can do here.
If no response is created we emit an event with the session attached. You can listen to these events, and call a method on the session to delay the closing.
If the session hasn't been kept open it will automatically be closed after X seconds. If it has, it will be closed once used, or X amount of time has passed.

It can be quite hard to know whether you want to keep a session alive. For example for mediation requests you would need to monitor all mediation requests, find the associated connection id and also find associated sessions with that same connection id. Therefore it may be useful to add an option that, if enabled, detects whether the other agent has an endpoint of didcomm:transport/queue and if so, it will keep the connection alive for longer. This allows the user to still just use the normal grantMediation call, but internally it kept on to the session, because it knows this is the only way to reply to the incoming message.
I think the websocket transport already keeps session open, but in the HTTP inbound transport we have the following statement after processing a message:
        // If agent did not use session when processing message we need to send response here.
        if (!res.headersSent) {
          res.status(200).end()
        }

@TimoGlastra -- it seems to me that this would be an issue for ACA-Py as well.  Correct?  Should we be doing the same thing?

Yes this is also an issue in ACA-Py, had to enable auto-accept as well to be able to interact with agents without an endpoint

However when auto accept is not enabled and the external controller would like to decide whether to respond to an incoming message it is not possible to respond. The other agent has an endpoint of didcomm:transport/queue which makes it impossible to send a message.
We should look at adding an option to delay the termination of the inbound route, so it gives time to create a response to the incoming message. Another option is to require autoAcceptConnection and autoAcceptMediationRequests to be enabled when interacting with agents without an inbound transport.

I don't think it is strictly needed to require both autoAcceptConnection and autoAcceptMediationRequests enabled, as it is possible to queue responses to  InMemoryMessageRepository and then the client can retrieve it by polling (e.g. using explicit pick-up messaging). Currently, this flow using AFJ for both mediator/mediatee roles works in WebSocket (as you said, the session is not closed) and HTTP. But in the latter it is needed to do a pickup loop on the client until mediation is granted (e.g. something like await agent.mediationRecipient.pickupMessages(mediatorConnection)).
That said, there is certainly room to improve a lot this use case, as currently there are no guarantees regarding the time the sessions would be valid (and the message queue will be stored).


Fixes _.isNaN for wrapped numbers

Issue https://github.com/jashkenas/underscore/issues/2257

Looks like the linter won't allow the use of !=.

why not just //eslint-disable-line eqeqeq?

Using the native isNaN achieves the same goal, and, cleaner code : )

Perhaps.  This issue does seem to go back and forth a lot: https://github.com/jashkenas/underscore/commit/2dff99d518a7fc3024334b9c517338e9c2557157

Back to square one lol. I think it's a matter of how they define the behavior of the function.

This LGTM.

Looks like the bug was introduced with the linting rules.

Whoops, my bad.


[test] Ignore stack lines from outside our test code

Splitting #40 into multiple PRs for easier review.
This stops the tests from breaking with Node.js updates.

This makes the test too relaxed. It was this way a long time ago, but there are some bugs related to removing lines that this won't test for.

Ok, would you like a PR that fixes failing tests by updating them for node v11, the version being used by the TravisCI tests?

Sure, we can do that. I don't care that much about a green TravisCI myself. I just use git diff as a sanity check that things are good.


Multis-screen compatibility ?

Hey !
I am having issues with multi-screen display and I'm wondering if maybe Ly is the issue.
I have done a minimalist GUI setup on Arch Linux (latest) with :

Ly as Display manager
Xorg as Display server
i3-wm as window-manager

My graphics card is an NVidia GTX-1060 and I chose proprietary drivers (nvidia & nvidia-prime + nvidia-utils & nvidia-settings).
I also installed xorg-randr, autorandr and even tried believer, but with no success.
Xorg and i3 are known to fully support multihead, so my question is the following :
Am I doing something terribly wrong or is it just Ly that doesn't fit my needs ?

What kind of issues are you experiencing? I also have this setup except instead of i3 i have awesome and it works perfecty fine.

Well the secondary screen just isn't detected.
It never shows up in autorandr's output or shows up as off/disconnected.
It's not in my NVidia settings either.
It acts as if nothing is plugged in.

Okay, that doesn't sound like it has something to do with ly. Have you tried starting it with xinit? That way you can make sure it isn't ly's fault (most likely isnt).

Interesting. I'll try fiddling with them. If I find a solution I'll come back here. :)

Ly does not configure displays directly, this should be done in .xprofile


Could not find source context with default setup

Describe the bug
I followed the default README, I get the Could not find source context error when trying with 2 of the default widgets.
To Reproduce
This is my sanity.config.ts
import {dashboardTool, projectUsersWidget} from '@sanity/dashboard'

plugins: [
    dashboardTool({
      widgets: [projectUsersWidget({layout: 'medium'})],
    }),
]

Error: Could not find source context
at useSource (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-LUKJXHXC.js?v=cb01cd93:40830:11)
at useUserStore (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-LUKJXHXC.js?v=cb01cd93:56080:50)
at ProjectUsers (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_dashboard.js?v=cb01cd93:272:175)
at renderWithHooks (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:15406:26)
at mountIndeterminateComponent (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:18784:21)
at beginWork (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:19772:22)
at beginWork$1 (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:23619:22)
at performUnitOfWork (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:23064:21)
at workLoopSync (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:23003:13)
at renderRootSync (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-QJQEJBP3.js?v=cb01cd93:22982:15)
Screenshots
If applicable, add screenshots to help explain your problem.
Which versions of Sanity are you using?
@sanity/cli (global)          3.43.0 (latest: 3.52.4)
@sanity/dashboard              4.0.0 (up to date)
@sanity/eslint-config-studio   4.0.0 (up to date)
@sanity/icons                  3.3.1 (up to date)
@sanity/presentation          1.16.2 (up to date)
@sanity/ui                     2.8.8 (up to date)
@sanity/util                  3.52.4 (up to date)
@sanity/vision                3.52.4 (up to date)
sanity                        3.51.0 (latest: 3.52.4)

What operating system are you using?
MacOS
Which versions of Node.js / npm are you running?
10.2.3
v20.10.0

This can happen if you're running inside of a monorepo or that node_modules is clobbered with multiple copies of sanity - try deleting your lockfile and reinstalling dependencies?


[TACHYON-989] Update the run tests script.

Follow up to #1636 to make runTests work again.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5837/
Test PASSed.

one minor comment left.

+1 LGTM

@apc999 Resolved the conflict, thanks.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5887/
Test FAILed.

Jenkins, test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5892/
Test PASSed.

I just had a question about the types. Thanks!

Ok, I am fine with adding the UnderStorageType in another PR.

LGTM


Document new application property to configure conversion errors displaying

Relates cuba-platform/cuba#1877
Environment

Documentation version: 7.2
Part of the documentation: Manual
Existing page: Application Properties

Description of the bug or enhancement
Application property cuba.web.conversionErrorDisplayType defines how the conversion errors will be displayed, like exceptions or notifications.
The property has two values: EXCEPTION and NOTIFICATION. The default value is EXCEPTION.

wait for cuba-platform/cuba#1877


chore: release main

:robot: I have created a release beep boop
accesskit_c: 0.3.2
Dependencies

The following workspace dependencies were updated

dependencies

accesskit_macos bumped from 0.7.0 to 0.7.1

accesskit_macos: 0.7.1
0.7.1 (2023-06-20)
Bug Fixes

Set proper target to build accesskit_macos documentation (#226) (9cd6bb1)

accesskit_winit: 0.14.1
Dependencies

The following workspace dependencies were updated

dependencies

accesskit_macos bumped from 0.7.0 to 0.7.1

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_macos-v0.7.1 :sunflower:

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_winit-v0.14.1 :sunflower:

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_c-v0.3.2 :sunflower:


feat(indexer-common): log endpoint in freshness checker

Today indexers do not have a way to know what subgraph is "not fresh" this PR aims to introduce the endpoint of subgraph we consider is "not fresh" in the freshness checker
closes https://github.com/graphprotocol/indexer/issues/803

Hey sorry forgot to detail this before you submitted PR.
Would you mind altering commit format a bit to be consistent with past contributions on this repo?
<package_name>: <Commit description>
Lately I've been shortening the package name to leave more room for description, so using common instead of indexer-common. * for something that applies to all packages.


 Commit Fail message when there is  a warning.

Model: SRX5600 standalone
Module: junos_install_config over console port.
Precondition: Device is zeroized and in amnesiac mode
YAML Code
  - junos_install_config:
       host={{ inventory_hostname }}
       file=/usr/local/junos/config/asthra_policy.conf
       timeout=3000
       user=root
       console="--telnet=bngsquid49-7044.englab.juniper.net,7044"
        logfile=/usr/local/junos/log/config_console.log
        overwrite='yes'
      register: junos

Since the device was zeroized, the license info was lost and configuration has ldp license configuration.
On running YAML code, on the device, the new config gets applied BUT with a warning.
[edit]
regress@asthra# commit
[edit security idp]
'security-package'
warning: requires 'idp-sig' license
commit complete
rpc error:
regress@asthra> junoscript netconf need-trailer
<!--

This issue is present in both netconfiy and pyez.  Deferring for now and will look at fixing this in concert with PyEZ.

resolved it here -> https://github.com/Juniper/py-junos-netconify/pull/27


chebyu/chebyt fail at infinity

Good:
>>> mpmath.chebyu(4,1e4)
mpf('1.599999988e+17')

>>> mpmath.chebyu(4,1e5)
mpf('1.5999999998799999e+21')

>>> mpmath.chebyu(4,1e100)
mpf('1.6000000000000002e+401')

bad:
>>> mpmath.chebyu(4,float('inf'))
mpf('5.0')

The expected answer is mpf('+inf').  Instead it seems to give n+1: haven't debugged it any further than that.

The underlying reason seems to be the "fast path":
https://github.com/mpmath/mpmath/blob/05dc18acea83229f80b46957db2502493ae33f2c/mpmath/functions/hypergeometric.py#L443-L449
with infinite z in our case.
I would expect here AND condition for abz before OR-ed conditions for parameters.  @fredrik-johansson ?


make elasticsearch provider optional if search.elasticsearch not defined

Hey, I just made a Pull Request!
For the new backend, make adding the elasticsearch search provider optional if search.elasticsearch is not defined in the config
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks for this @aochsner, at a high level this makes sense to me, will leave the final say to the @discoverability-maintainers.
I did leave a pair of comments that should be pretty easy to address 👍

Thanks for the feedback!  Incorporated.


Refactor LocIndexerLike__getitem__.

Looks good if tests pass

Codecov Report

Merging #1152 into master will decrease coverage by 2.59%.
The diff coverage is 90.32%.

@@            Coverage Diff            @@
##           master    #1152     +/-   ##
=========================================
- Coverage   95.24%   92.64%   -2.6%
=========================================
  Files          35       35
  Lines        7080     7080
=========================================
- Hits         6743     6559    -184
- Misses        337      521    +184

Impacted Files
Coverage Δ

databricks/koalas/indexing.py
93.7% <90.32%> (-1.75%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
24.32% <0%> (-72.98%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
78.72% <0%> (-6.39%)
:arrow_down:

databricks/conftest.py
92% <0%> (-6%)
:arrow_down:

databricks/koalas/frame.py
93.64% <0%> (-3.24%)
:arrow_down:

databricks/koalas/groupby.py
89.62% <0%> (-2%)
:arrow_down:

databricks/koalas/namespace.py
85.97% <0%> (-1.53%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0%> (-0.96%)
:arrow_down:

databricks/koalas/testing/utils.py
78.51% <0%> (-0.75%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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

Thanks! I'd merge this now.


add helm-dm charts proposal to dm docs

The is the markdown version of the helm-dm chart proposal.

/cc @jackgr on issue #236. User stories are laid out in this doc. Would this suffice or were you envisioning a separate doc with workflows?

@michelleN Nice to have this in MD. Would like to have a document that describes:

All supported flows
Processing done for each flow

/cc @technosophos

@michelleN there are some significant comments not yet addressed in this PR. Given the importance of this document, it would be great to get them addressed before the use case walk through.

@michelleN there are some significant comments not yet addressed in this PR. Given the importance of this document, it would be great to get them addressed before the use case walk through.

Agreed @jackgr. I've gone through and hopefully resolved most of them. The bigger open issues might require a discussion on 1. Dependencies 2. Github repo support and 3. License files with the rest of the team. cc/ @bmelville @vaikas-google @technosophos @adamreese


fix: Add MIRACL reranking

These is just a few minor changes to #641
Still need to add the results from running the model

@crystina-z seems like the dataset is gated. Is this intended?

heyy @KennethEnevoldsen the access request is removed now. I'm taking a look at where the duplicates come from

I added results - I believe this concludes this PR - I additionally also fixed some broken dataset reference (unrelated, due to failing tests)


iminuit error during ctapipe installation

Hi All,
I got an issue when trying to install ctapipe on mac with miniconda3 and python 3.6:
moderski$ conda install -c cta-observatory ctapipe
Fetching package metadata .............
Solving package specifications: .UnsatisfiableError: The following specifications were found to be in conflict:

ctapipe -> iminuit -> python 2.7* -> openssl 1.0.1*
python 3.6*
Use "conda info " to see the dependencies for each package.

On my linux distribution I have iminuit 1.2 installed from the cta-observatory channel, but it seems that it is no longer there.
Is this a bug or there is a way around to install ctapipe?
Cheers,
Rafal

THe problem is just that iminuit is not in the default anaconda channel.  You need to add the astropy or openastronomy channel to get it (perhaps we should add a copy of the package to the cta-observatory one, but then we'd have to maintain it).
conda config --add channels astropy

should fix that.  That's done automatically if you create your environment with the environment.yml file to install all packages.

Hi Karl,
Thanks. That worked.
RM
On Wed, Oct 11, 2017 at 8:52 AM, Karl Kosack<EMAIL_ADDRESS>wrote:

THe problem is just that iminuit is not in the default anaconda channel.
You need to add the astropy or openastronomy channel to get it (perhaps we
should add a copy of the package to the cta-observatory one, but then we'd
have to maintain it).
conda config --add channels astropy
should fix that. That's done automatically if you create your environment
with the environment.yml file to install all packages.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cta-observatory/ctapipe/issues/564#issuecomment-335700488,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIHhiKNrlM8mpnHUYGz4r55p646ZU1rQks5srGW4gaJpZM4P0WLY
.


Update README.md

created a README.md file for the Digital-Nomad-App

created a README.md for Digital-Nomad-App


about nq_open results

Hi,
I have problems reproducing the results of Natural Question dataset from this PR. This is the command I use:
For llama1-0-shot
lm-eval --model hf --batch_size auto --task nq_open --model_args pretrained=huggyllama/llama-7b

For llama1-5-shot
lm-eval --model hf --batch_size auto --task nq_open --model_args pretrained=huggyllama/llama-7b --num_fewshot 5

For llama2-0-shot:
lm-eval --model hf --batch_size auto --task nq_open --model_args pretrained=meta-llama/Llama-2-7b-hf

For llama2-5-shot
lm-eval --model hf --batch_size auto --task nq_open --model_args pretrained=meta-llama/Llama-2-7b-hf --num_fewshot 5

This is the results I got:

0-shot-llama1-7b
5-shot-llama1-7b
0-shot-llama2-7b
5-shot-llama2-7b

original PR
18.3
23.9
17.5
26.1

reproduced
13.3
21.5
14.5
25.2

I notice there was a refactor of the database, I am not sure if this would cause discrepancy here.

Hi! Thanks for opening this. Are you using the most recent version of this codebase?
I think the discrepancy may be due to the lack of passing a prepended description (see https://github.com/EleutherAI/lm-evaluation-harness/pull/789#issuecomment-1685487046 )--we changed from expecting users to pass this via the CLI, to allowing it to be specified for a task in that task's config. Would you be willing to add description: "Answer these questions:\n\n" into the NaturalQs YAML file and see if you can replicate one of these results?
If so then we can merge that fix. I'm sorry for the issues!

Hi, thanks for response! I used the latest version by git clone the repo and pip install -e. The commit id is 588a493c41b58d048d3994f99800edd27223bd3a.
The YAML file I use for nq_open is this: https://github.com/EleutherAI/lm-evaluation-harness/blob/main/lm_eval/tasks/nq_open/nq_open.yaml.
There is already description filed. https://github.com/EleutherAI/lm-evaluation-harness/blob/588a493c41b58d048d3994f99800edd27223bd3a/lm_eval/tasks/nq_open/nq_open.yaml#L6
Do you mean I should change it to "Answer these questions:\n\n"? I would try it out.
Thanks again for your help!

Haha, this is crazy. Simply adding a \n to the current description make llama-2-7b-0-shot from 14.5 to 18.4.

sigh Sometimes I hate LLM evals. I'm glad this works to reproduce though!
To match the old master implementation, \n\n is needed. I'll PR this fix!

Hi, thanks for fixing!
For anyone who is also interested in the nq_open results:

llama1
Description
0-shot
1-shot
5-shot

7b
Answer these questions:\n
13.4
17.3
21.4

7b
Answer these questions:\n\n
17.3
18.8
23.0

13b
Answer these questions:\n
14.7
21.5
26.5

13b
Answer these questions:\n\n
22.2
23.5
28.0

llama2
Description
0-shot
1-shot
5-shot

7b
Answer these questions:\n
14.5
21.3
25.2

7b
Answer these questions:\n\n
18.4
22.5
25.5

13b
Answer these questions:\n
14.4
23.9
28.5

13b
Answer these questions:\n\n
22.8
26.0
29.7

Slightly lower than results in this PR, reason unknown


Add semicolon at start

A good practice when working with multiple JS files is to add a single semicolon at the very beginning of each file to terminate any preceding malformed logic.

Thanks buddy
On Oct 5, 2016 7:22 AM, "Daniel James"<EMAIL_ADDRESS>wrote:

@danieltj27 approved this pull request.
Probably a good idea considering this file will be concatenated into a
minified js file with other scripts. No harm in doing this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kenwheeler/slick/pull/2524#pullrequestreview-2884173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABS5DRki0CgTu6fBwOjv9gMcQr-P2U8nks5qw3pegaJpZM4KDer7
.