[tcl] Build failure on x64-windows-release

Package: tcl[core,profile,thrdalloc,unchecked,utfmax]:x64-windows-release@core-9-0-a1#7
Host Environment

Host: x64-windows
Compiler: MSVC 19.41.34120.0
vcpkg-tool version: 2024-08-01-fd884a0d390d12783076341bd43d77c3a6a15658
vcpkg-scripts version: 86fba1306 2024-09-13 (3 days ago)

To Reproduce
vcpkg install tcl[profile,thrdalloc,unchecked,utfmax]:x64-windows-release --recurse
Failure logs
-- Using cached tcltk-tcl-0fa6a4e5aad821a5c34fdfa070c37c3f1ffc8c8e.tar.gz.
-- Extracting source C:/tools/vcpkg/downloads/tcltk-tcl-0fa6a4e5aad821a5c34fdfa070c37c3f1ffc8c8e.tar.gz
-- Applying patch force-shell-install.patch
-- Using source at C:/tools/vcpkg/buildtrees/tcl/src/3f1ffc8c8e-0b0ee3e2ba.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows-release
-- Building and installing x64-windows-release-rel
CMake Error at ports/tcl/portfile.cmake:123 (file):
  file does not exist:

    C:/tools/vcpkg/packages/tcl_x64-windows-release/tools/tcl/debug/lib/tcl9.0/msgs
Call Stack (most recent call first):
  scripts/ports.cmake:192 (include)

reproduced locally, same error,
it looks like a release triplet bug or so...
as a temp workaround- build both dbg & release (builds fine), eg:
c:\Dev\vcpkg>vcpkg install tcl[profile,thrdalloc,unchecked,utfmax]:x64-windows
Computing installation plan...
The following packages will be built and installed:
    tcl[core,profile,thrdalloc,unchecked,utfmax]:x64-windows@core-9-0-a1#7
Detecting compiler hash for triplet x64-windows...
Compiler found: C:/Dev/VS2019/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe
Restored 0 package(s) from C:\Users\user\AppData\Local\vcpkg\archives in 182 us. Use --debug to see more details.
Installing 1/1<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Using cached tcltk-tcl-0fa6a4e5aad821a5c34fdfa070c37c3f1ffc8c8e.tar.gz.
-- Cleaning sources at C:/Dev/vcpkg/buildtrees/tcl/src/3f1ffc8c8e-0b0ee3e2ba.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Dev/vcpkg/downloads/tcltk-tcl-0fa6a4e5aad821a5c34fdfa070c37c3f1ffc8c8e.tar.gz
-- Applying patch force-shell-install.patch
-- Using source at C:/Dev/vcpkg/buildtrees/tcl/src/3f1ffc8c8e-0b0ee3e2ba.clean
-- Getting CMake variables for x64-windows
-- Building and installing x64-windows-dbg
-- Building and installing x64-windows-rel
-- Installing: C:/Dev/vcpkg/packages/tcl_x64-windows/share/tcl/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 1.5 s.
Elapsed time to handle tcl:x64-windows: 60 s
tcl:x64-windows package ABI: 985d92b7715c93953d1ed9d73554ef57318754da40da3b37eee995ce0541a907
Total install time: 60 s


Genome annotation statistics tool fails immediately at ORG

Tool id
toolshed.g2.bx.psu.edu/repos/iuc/jcvi_gff_stats/jcvi_gff_stats/0.8.4
Test history
https://usegalaxy.org/u/jen-galaxyproject/h/test-genome-annotation-statistics-jcvigffstats
No command line or logs

Still open, reported in bugs 10-23

I don't know what that means

The tool was mapped to an invalid destination (jetstream2_normal). I've taken out the mapping, it seems that comment about NFS and singularity didn't apply either since it ran fine on roundup within singularity.


How can i count the number of the functional group of the molecule?

Rdkitconfig has provided a text which named FunctionalGroups.txt, if i want to count the number of the functional group of the molecule, what should i do?

I'm closing this because it is a question, not a bug report or enhancement request.
Please ask questions using the "Discussions" tab.


Change Track 2 SB sendMessages() API for messages are being sent at a slow pace

Fix issue #16127

Change Track 2 SB sendMessages() API for messages are being sent at a slow pace
Changed file:
1). sdk/servicebus/azure-messaging-servicebus/src/main/java/com/azure/messaging/servicebus/ServiceBusMessageBatch.java
2). sdk/servicebus/azure-messaging-servicebus/src/main/java/com/azure/messaging/servicebus/ServiceBusSenderAsyncClient.java

@jongio, @conniey  for notification.

This time only the loop method and the synchronization method have been modified, and the Test Case is not involved.

@conniey
In the original code, the ServiceBusMessage collection uses messages.forEach and[for(int i = 0; i <batch.getMessages().size(); i++) for one-to-one loop processing, so we are More ServiceBusMessages have been added to ServiceBusBatch and it has become many times slower. It has now been changed to the parallel stream method to reduce loop processing time.
Can you tell me the target range value that the performance test hopes to achieve (for example: send 1000 pieces in batch within 3~4 seconds), so as to try to further locate the cause of the problem and find a better solution. In addition, can you provide the relevant test package perf-test-core-1.0.0-beta.1.jar to reproduce the performance failure site.

@g2vinay @hemanttanwar Can you add more context to this issue? If I remember correctly, this issue was opened because sending a message was exponentially slower.  The bug doesn't have exact metrics we were seeing for the perf tests.

In addition, can you provide the relevant test package perf-test-core-1.0.0-beta.1.jar to reproduce the performance failure site.
You can build this library from here : https://github.com/Azure/azure-sdk-for-java/tree/master/common/perf-test-core

@hongli19750210

Can you tell me the target range value that the performance test hopes to achieve (for example: send 1000 pieces in batch within 3~4 seconds), so as to try to further locate the cause of the problem and find a better solution.

I spoke to @g2vinay , who created original issue back in 2020.  One update is, The send performance was really back at that time And @srnagar had another PR https://github.com/Azure/azure-sdk-for-java/pull/17842  to  perform operation in parallel.  That did resolve the original "send performance" issue.
So I believe, we can consider original issue resolved.
But this PR does improve performance by using parallel stream to construct ServiceBusMessage. One test you  can do is to compare before and after your change , what is the performance improvement  and document it in this PR.

@hemanttanwar @conniey
compare before and after change
    Sending number setting:
         Number of bookings sent: 1000000
         Actual number sent: 1708
    Test Branch:
         master
         #16127_Messages_are_being_sent_at_a_slow_pace

Remarks: Due to the limitation of Message size, there is a big difference between the number of scheduled sending and the actual sending number, so you can test the performance difference of two different circulation methods.
Test result (the test result is accurate to two decimal places):
    branch: master         Total time: 5.46s
    Time-consuming distribution:
        `createMessageBatch` (including `getSendLink`) : 3.12s
             ----`getSendLink`: 2.88s
        `tryAddMessage` (loop): 0.88s
        Other process: 0.02s
        `link.send` and `withRetry`: 1.44s

    branch: #16127_Messages_are_being_sent_at_a_slow_pace    Total time: 4.56s
    Time-consuming distribution:
        `createMessageBatch` (including `getSendLink`): 3.05s
             ----getSendLink: 2.71s
        `tryAddMessage` (loop): 0.02s
        Other process: 0.01s
        `link.send` and `withRetry`: 1.48s

Through the above time-consuming distribution, I think the execution efficiency will be greatly improved when the loop is executed in the parallel stream mode.


Bug Report - Foreground text has become black in some cases, in powershell

Environment
Windows build number: 18362.145
Windows Terminal version (if applicable): 0.1.1431.0

Any other software?

Steps to reproduce
Had terminal up for a few days on remote machine, locked machine and when I came back after weekend and logged in, parts of the command text is now black
Expected behavior
All foreground text should be white
Actual behavior
Some text is white, some is black. It looks like command output is white, but commands I type are usually black, as well as error text.

Weird nuances though:

I saw this when I upgraded from 0.1.1431.0 to 0.1.1502.0, actually. Everything with a color becomes black, and everything with the default color stays correct.

Ah, Dustin I didn't figure out that correlation, but now that you say it yes, that appears to be the behaviour I'm seeing, thanks for clarifying it :)

This may be related to #742. I thought we had a migration in place, but maybe it's not not working?

Haven't seen reports of this in quite a long time, so I'm gonna close it out. Let me know if it's still happening!


[docs][material-ui] Slider in color customization playground twitches when sliding

Steps to reproduce
Link to live example: (required)
https://github.com/mui/material-ui/assets/110468377/af4c2657-662e-4537-acc7-13a9f04e840b
Steps:
1.Go to Settings
2.Click on "Edit documentation colors"
3.Slide the toggle from left to right.
4.Observe the behavior as it passes the 100 and 50 marks and the marks after that.
Current behavior
When sliding the Slider component's toggle from left to right, a noticeable twitch occurs around the 100 and 50 marks.
The marks for A700 and A400 are not displayed when the slider moves from left to right.
These issues do not occur when sliding from right to left.
Expected behavior
The Slider should move smoothly without any twitching at any point along the track.
All marks, including A700 and A400, should be visible when sliding from left to right.
Context
I am attempting to provide a seamless user experience when using the slider. This twitching effect is causing confusion and a less satisfactory user interaction.

  Output from `npx @mui/envinfo` goes here.

Search keywords: Slider, twitch, A700, A400, marks, animation issue

Thank you for your response and guidance @mj12albert - yes absolutely i would like to investigate the issue further, i have already located the code for the playground and I'm currently looking through it to pinpoint the exact cause of the twitching issue. I'll share my findings as soon as I have something concrete.

@mj12albert, I believe I've identified potential areas that could be causing the twitching issue with the Slider component. Here are my key observations:
-State Management in handleChangeShade:
This function updates several state variables simultaneously ([name]Shade, [name], and [name]Input). The frequency and scope of these updates might be causing the component to rerender inefficiently, leading to the twitching observed, particularly near the 100 and 50 marks. Here's code for reference:

-Dynamic Styling Calculations:
The Slider's sx property involves dynamic calculations that might be affecting its rendering performance. Reducing complexity in these style calculations could potentially improve performance. Here’s the relevant code:

I'm currently exploring optimizations in the handleChangeShade function to reduce the number of state updates and simplify the dynamic style calculations. These changes might help in achieving smoother interactions with the Slider.

@mj12albert, I've implemented several optimizations based on the initial observation to address the issue. Here are the changes and the solutions i came up with:

Optimized State Management in handleChangeShade:

I refactored the handleChangeShade function to minimize the number of state updates and potential re-renders. By consolidating the state updates into a single setState call, we reduce the overhead and improve the slider's responsiveness. Here's the revised code snippet:

Simplified and Improved Slider Styling:

To further enhance performance, I simplified the Slider's dynamic styling by moving the style calculations outside of the component render method. This approach minimizes recalculations and leverages CSS for better performance. The updated styling I applied is as follows:

Integrated Changes within colorPicker Function:

I ensured that these changes were integrated smoothly within the colorPicker function, keeping in mind the overall component structure and existing functionality. The focus was on ensuring that the modifications did not introduce any new issues or regressions.
Here's how the modified section looks now:

@yassinmars Thanks for looking into this - would you like you make a PR so we can try out the changes?


JEST tests for the RD2 Custom Fields component

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

@andrewyu-salesforce Would appreciate your comments.  Thank you for your help with this!!!
@bdvorachek @lparrott If you have time between class tasks, I'd be grateful for your comments.  And thank y'all for your help as well!


python311Packages.reolink-aio: 0.8.1 -> 0.8.2

Diff: https://github.com/starkillerOG/reolink_aio/compare/refs/tags/0.8.1...0.8.2
Changelog: https://github.com/starkillerOG/reolink_aio/releases/tag/0.8.2
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 272847 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.reolink
python310Packages.reolink-aio
python310Packages.reolink-aio.dist
python311Packages.reolink-aio
python311Packages.reolink-aio.dist


Expand the set of built-in functions

According to ticket, we need to add two new built-in functions:

get_cache_dir() - returns path to terragurnt cache directory
get_terraform_output() - returns terraform output, which can later be passed to the script in hooks

Please prioritise this issue as i tis important to add this feature request. Also, ensure that you are going to communicate the release number of terrarrunt application which will support get_cache_dir() and get_terraform_output() which will be passed to the script from the hooks.

@mirconstantin We will do our best to make the development of these built-in functions as fast as possible. As soon as we're done, I'll be sure to let you know the version containing these improvements.

After analyzing the issue, it became clear that this functionality is not needed. I close the question.


GEODE-9217: Adding memory overhead tests for redis

Adding integration tests that measure the memory overhead of both native redis
and radish.  These tests measure the memory used before and after adding
entries. They assert that the measured per entry overhead is within 1 byte of
the expected per entry overhead. They are measuring the all of the overhead -
whether it's from geode region entries or our radish data structures.
These are essentially the same tests from the feature/redis-memory-overhead
branch, but with assertions added that our expected overhead didn't change.

@sabbey37 - The main reason I left MemoryOverheadNativeRedisAcceptanceTest in there is so we can compare our numbers with native redis and see how close we are getting. It's also a framework and place to add new measurements - for example to measure the native redis overhead of sorted sets to compare with radish.
So I like having the code checked in somewhere. I guess I'm ambivalent about running it in CI every time. It takes about 4 seconds.

@upthewaterspout that makes sense and sounds reasonable!


Add torque measurement noise to Bullet interface

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

29 of 36 (80.56%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 89.987%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

upkie/cpp/actuation/BulletInterface.cpp
12
15
80.0%

upkie/cpp/actuation/bullet/JointProperties.h
4
8
50.0%

Files with Coverage Reduction
New Missed Lines
%

upkie/cpp/actuation/BulletInterface.cpp
1
84.41%

upkie/cpp/actuation/bullet/JointProperties.h
1
55.56%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.1%

Covered Lines:
2714

Relevant Lines:
3016

💛  - Coveralls


Move assertj out of bom-test, define common deps in integration-tests parent

I see your point in general.
OTOH, uniformity should also be our goal, i.e. we should use assertj wherever possible (and not a mix of junit assertions and assertj assertions), so I even see a reason to push assertj all the way up to to quarkus-cxf-parent.
What about meeting in the middle for now: I put rest-assured back to each individual module but leave the other two (which are used in all ITs) in the IT parent. WDYT?
Also /cc @shumonsharif for a third opinion.

What about meeting in the middle for now: I put rest-assured back to each individual module but leave the other two (which are used in all ITs) in the IT parent. WDYT?

+1, thanks!

Alright, I'll adjust this PR today evening.

@famod @ppalaga Sorry for being MIA, the day job has been keeping me very busy of late.
I think both your perspectives are very valid, and even though my personal preference has always been for uniformity, consistency and conciseness (If I were working on it, I would probably implement exactly as per @famod) - I'm glad there was some balance achieved by meeting in the middle.  I never quite thought of things as @ppalaga mentioned, and I'm sure there's good reason and possibly some hard experience backing it!
Thanks so much to you both for the flurry of recent activities - some rock solid work on the extension; I hope I'm able to more actively participate after a couple more weeks ...


Peer PBFT Batch does not work on queue after two VPs bounce

Description
Some basic behavior with Consensus seems to be no longer working, in a specific scenario. This test fails on test images from 6/15 (f8ffcd1) and 6/16 (04f076b). The test passed on 6/9 image (a94f5a7).
In the following scenario, after recovery, the values for A and B seem to remain stuck with the same values prior to the failures. The Invokes that were requested while there were only 2 peers active, AND the Invokes that were requested after all 4 nodes recovered, are NOT processed and not reflected in the query results. Caveat: the failure occurs ONLY if we send Invoke requests WHILE only 2 peers active; if we stop and start two nodes and THEN Invoke and Query, then all seems to work fine. Another note: it does not make any difference whether we request Invokes while 4 peer nodes are up PRIOR to stopping two of them.
Describe How to Reproduce

Using Vagrant and docker containers, running go script using our SDK toolkit, we started 4 peer nodes with consensus and security enabled, running PBFT Batch and batchsize=2.

Deploy chaincode_example02 values for A (200) and B (100)

stop 2 peers

invokes to transfer from A to B

start the 2 peers again

invokes to transfer from A to B

query  <----- FAILURE : This query returns the original values of A (200) and B (100), essentially ignoring all the invokes.

Note: Pull Request #1867  represents a similar scenario with a Behave test - which PASSES. Our team also confirmed the 1867 passing result by using a similar Behave test with PBFT Batch (although we could reproduce the failure with the Behave test case using PBFT Classic). Not sure why the Behave test passes and our GO test fails. Maybe the config parameters being used are different. Maybe the logs will help. Attachments include the GO test script, the local_fabric.sh script used to start the docker peers and pass config parameters, and the logfiles. PEER3 may be of interest.
InvokesWhenNoConsensusCauseFreeze.tar.gz

You need to keep submitting invokes, or switch on periodic null requests.  If there is no activity in the network, the peers will not catch up.

@corecode,  i tried running the behave test from PR #1867 . Looks like we're not receiving any more requests after the initial deploy and invoke ? After restarting vp3 , I don't see vp0 saying it "received request"
ttd-1874.zip
and the behave test:
#@doNotDecompose
#    @wip
Scenario: chaincode example02 with 4 peers, two stopped TTT1
        Given we compose "docker-compose-4-consensus-batch.yml"
        And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
           | vp0  |
        And I use the following credentials for querying peers:
    	     | peer |   username  |    secret    |
		     | vp0  |  test_user0 | MS9qrN8hFjlE |
		     | vp1  |  test_user1 | jGlNl6ImkuDo |
		     | vp2  |  test_user2 | zMflqOKezFiA |
		     | vp3  |  test_user3 | vWdLCE00vJy0 |

        When requesting "/chain" from "vp0"
      	Then I should get a JSON response with "height" = "1"

        When I deploy chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" with ctor "init" to "vp0"
           | arg1 |  arg2 | arg3 | arg4 |
   	     |  a   |  100  |  b   |  200 |
	     Then I should have received a chaincode name
        Then I wait up to "60" seconds for transaction to be committed to peers:
           | vp0  | vp1 | vp2 | vp3 |

        When I query chaincode "example2" function name "query" with value "a" on peers:
           | vp0  | vp1 | vp2 | vp3 |
        Then I should get a JSON response from peers with "OK" = "100"
           | vp0  | vp1 | vp2 | vp3 |

        Given I stop peers:
           | vp2 | vp3  |
        And I wait "15" seconds

        When I invoke chaincode "example2" function name "invoke" on "vp0"
   	     |arg1|arg2|arg3|
           | a  | b  | 10 |
        Then I should have received a transactionID

        Given I start peers:
           | vp3  |
        And I wait "15" seconds
        When I invoke chaincode "example2" function name "invoke" on "vp0" "9" times
   	     |arg1|arg2|arg3|
           | a  | b  | 10 |
        Then I should have received a transactionID
        Then I wait up to "120" seconds for transaction to be committed to peers:
           | vp0  | vp1 | vp3 |

        When I query chaincode "example2" function name "query" with value "a" on peers:
           | vp0  | vp1 | vp3 |
        Then I should get a JSON response from peers with "OK" = "0"
           | vp0  | vp1 | vp3 |

@scottz64 can you please identify the exact commit that introduced the bug and let us know? git-bisect

@scottz64 There may have been some regressions around request resubmission in #1798 which have been addressed in #1877 if you could try applying to reproduce with that PR.

Not sure if caused by PR #1793 I merged this morning. CI was successful on the build.

If #1877 does not address this --
These consensus-related PRs were submitted after this test passed successfully (from oldest to newest): #1749, #1758, #1785, #1798, #1793.
See if you can revert back to them and let us know which one introduces the error.

The failure occurs today with 1793. The failure also occurs with 1798 (yesterday's load without 1793). Looking further...

Confirmed that #1877 fixed #1873 so it might be worth checking.

Missed the behave test above, tried it locally with #1877 and it did not pass.

@tuand27613 test works here - vp0,vp1,vp3 all execute 11 transactions.

Currently working on a solution for this, will post here when ready

I don't think this one is fixed yet. I am running tests with 35326c2 (from 6/18, 930am, includes 1877). In some tests I don't see the images getting created after stopping and starting peers. It might have something to do with which peers are stopped (e.g. if it includes peer0, the primary). That is strange, because that was a hallmark of 1873 (which appears to be fixed). I will recheck my tests for insufficient timing delays and such, and run some more tests tomorrow, just in case there is some inexperienced pilot error occurring.
Also, any Invokes received by the available 2 peers (when the other two are stopped) do not seem to be queued and processed after a third node is restarted and consensus capability resumes and further invokes and queries occur.

@scottz64 The behave test from @tuand27613 above is in and passing.  Could you identify any differences in your procedure and the behave test above?

Testcase steps look the same to me. Here is summary of test S1S2IR2IQ.go:
deploy (a=10, b=20)
query
stop vp1 vp2
sleep 60
invoke 2 times
sleep 15
start vp2
sleep 120
invoke 3 times
sleep 30
query vp0 vp2 vp3  (fails here: vp0 returns a==7, b==23 but should be a==5, be==25. And vp2 fails to return anything, even though the image for chaincode dev-vp2 did become visible in "docker ps" after the 3 invokes)

The behave test takes down vp2,vp3, but does not touch vp0. I just ran some other GO tests a couple ways, stopping only vp1,vp2 - while vp0 and vp3 stayed up the whole time. Seems to work much better - but not perfectly every scenario. Problems are seen much more often when stopping vp0 as part of the testcase.

@scottz64   "not perfectly" ? :)
Could you describe scenario ?  Also, I asked @2016nishi to add her scenario and logs
@jyellick ,  seems like view-change goes awry when primary is stopped ?

@tuand27613 @scottz64 I would need a set of logs at debug to determine exactly what is going on.  Have you tried this with periodic null requests enabled? I imagine that might bring the network back into a consistent state.

@jyellick  I'll tweak the behave test to reproduce
@scottz64 , try setting core_pbft_timeout_nullrequest=1s

@scottz64 @2016nishi @jyellick  does this behave testcase mimic your scenario ?
#    @doNotDecompose
#    @wip
@issue_1874
Scenario: chaincode example02 with 4 peers, two stopped including primary
      Given we compose "docker-compose-4-consensus-batch.yml"
     	And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
        | vp0  |
      And I use the following credentials for querying peers:
        | peer |   username  |    secret    |
        | vp0  |  test_user0 | MS9qrN8hFjlE |
        | vp1  |  test_user1 | jGlNl6ImkuDo |
        | vp2  |  test_user2 | zMflqOKezFiA |
        | vp3  |  test_user3 | vWdLCE00vJy0 |

      When requesting "/chain" from "vp0"
      Then I should get a JSON response with "height" = "1"

      When I deploy chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" with ctor "init" to "vp0"
        | arg1 |  arg2 | arg3 | arg4 |
        |  a   |  100  |  b   |  200 |
      Then I should have received a chaincode name
      Then I wait up to "60" seconds for transaction to be committed to peers:
        | vp0  | vp1 | vp2 | vp3 |

      When I query chaincode "example2" function name "query" with value "a" on peers:
        | vp0  | vp1 | vp2 | vp3 |
      Then I should get a JSON response from peers with "OK" = "100"
        | vp0  | vp1 | vp2 | vp3 |

      Given I stop peers:
        | vp0 | vp1  |

      And I register with CA supplying username "test_user3" and secret "vWdLCE00vJy0" on peers:
        | vp3 |
      When I invoke chaincode "example2" function name "invoke" on "vp3"
        |arg1|arg2|arg3|
        | a  | b  | 10 |
      Then I should have received a transactionID

      Given I start peers:
        | vp0  |
      And I wait "15" seconds

      When I invoke chaincode "example2" function name "invoke" on "vp3" "9" times
        |arg1|arg2|arg3|
        | a  | b  | 10 |
      Then I should have received a transactionID

      And I wait "60" seconds
      When I query chaincode "example2" function name "query" with value "a" on peers:
         | vp0  | vp2 | vp3 |
      Then I should get a JSON response from peers with "OK" = "0"
         | vp0  | vp2 | vp3 |

@tuand27613 Here is the behave test scenario that is failing:
@issue_1874
Scenario: chaincode example02 with 4 peers, two stopped, bring back vp0
  Given we compose "docker-compose-4-consensus-batch.yml"
  And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
                                | vp0  |
  And I use the following credentials for querying peers:
           	| peer |   username  |    secret    |
           	| vp0  |  test_user0 | MS9qrN8hFjlE |
           	| vp1  |  test_user1 | jGlNl6ImkuDo |
           	| vp2  |  test_user2 | zMflqOKezFiA |
           	| vp3  |  test_user3 | vWdLCE00vJy0 |

  When requesting "/chain" from "vp0"
  Then I should get a JSON response with "height" = "1"

  When I deploy chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" with ctor "init" to "vp0"
           	     | arg1 |  arg2 | arg3 | arg4 |
           	     |  a   |  100  |  b   |  200 |
  Then I should have received a chaincode name
  Then I wait up to "60" seconds for transaction to be committed to peers:
                 | vp0  | vp1 | vp2 |

  When I query chaincode "example2" function name "query" with value "a" on peers:
                 | vp0  | vp1 | vp2 | vp3 |
  Then I should get a JSON response from peers with "OK" = "100"
                 | vp0  | vp1 | vp2 | vp3 |

  Given I stop peers:
                 | vp0 |

  And I register with CA supplying username "test_user1" and secret "jGlNl6ImkuDo" on peers:
                | vp1  |

  When I invoke chaincode "example2" function name "invoke" on "vp1"
           	 |arg1|arg2|arg3|
                 | a  | b  | 10 |
  Then I should have received a transactionID

  Given I stop peers:
                 | vp3  |

  And I register with CA supplying username "test_user1" and secret "jGlNl6ImkuDo" on peers:
                | vp1  |

  When I invoke chaincode "example2" function name "invoke" on "vp1"
           	 |arg1|arg2|arg3|
                 | a  | b  | 10 |
  Then I should have received a transactionID

  Given I start peers:
                 | vp0  |
  And I wait "15" seconds

  When I invoke chaincode "example2" function name "invoke" on "vp1" "8" times
         	 |arg1|arg2|arg3|
                 | a  | b  | 10 |
  Then I should have received a transactionID
  Then I wait up to "60" seconds for transaction to be committed to peers:
                | vp2  | vp1 | vp3 |

  When I query chaincode "example2" function name "query" with value "a" on peers:
                        | vp3  | vp1 | vp2 |
  Then I should get a JSON response from peers with "OK" = "0"
                        | vp3  | vp1 | vp2 |

@corecode The above behave test scenario is what was executed receiving the assertion failure:
      Assertion Failed: For attribute OK, expected (0), instead found (100)

at the step:
 Then I should get a JSON response from peers with "OK" = "0"
           | vp3 | vp1 | vp2 |

The problem seems to be that peers do not reconnect to vp0 even when it comes up.  @jeffgarratt

@corecode @lhaskins this test seems to pass for me locally with latest master.

This fails here, because vp0 never connects back to anybody:

@issue_1874
Scenario: chaincode example02 with 4 peers, two stopped, bring back vp0
  Given we compose "docker-compose-4-consensus-batch.yml"
  And I register with CA supplying username "binhn" and secret "7avZQLwcUe9q" on peers:
                                | vp0  |
  And I use the following credentials for querying peers:
            | peer |   username  |    secret    |
            | vp0  |  test_user0 | MS9qrN8hFjlE |
            | vp1  |  test_user1 | jGlNl6ImkuDo |
            | vp2  |  test_user2 | zMflqOKezFiA |
            | vp3  |  test_user3 | vWdLCE00vJy0 |

  When requesting "/chain" from "vp0"
  Then I should get a JSON response with "height" = "1"

  When I deploy chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" with ctor "init" to "vp0"
                 | arg1 |  arg2 | arg3 | arg4 |
                 |  a   |  100  |  b   |  200 |
  Then I should have received a chaincode name
  Then I wait up to "60" seconds for transaction to be committed to peers:
                 | vp0  | vp1 | vp2 |

  When I query chaincode "example2" function name "query" with value "a" on peers:
                 | vp0  | vp1 | vp2 | vp3 |
  Then I should get a JSON response from peers with "OK" = "100"
                 | vp0  | vp1 | vp2 | vp3 |

  Given I stop peers:
                 | vp0 |

  And I register with CA supplying username "test_user1" and secret "jGlNl6ImkuDo" on peers:
                | vp1  |

  When I invoke chaincode "example2" function name "invoke" on "vp1"
             |arg1|arg2|arg3|
                 | a  | b  | 10 |
  Then I should have received a transactionID

  Given I stop peers:
                 | vp3  |

  When I invoke chaincode "example2" function name "invoke" on "vp1"
             |arg1|arg2|arg3|
                 | a  | b  | 10 |
  Then I should have received a transactionID

  Given I start peers:
                 | vp0  |
  And I wait "15" seconds

  When I invoke chaincode "example2" function name "invoke" on "vp1" "8" times
             |arg1|arg2|arg3|
                 | a  | b  | 10 |
  Then I should have received a transactionID
  Then I wait up to "60" seconds for transaction to be committed to peers:
                | vp2  | vp1 | vp3 |

  When I query chaincode "example2" function name "query" with value "a" on peers:
                        | vp3  | vp1 | vp2 |
  Then I should get a JSON response from peers with "OK" = "0"
                        | vp3  | vp1 | vp2 |

The problem is that nodes only reconnect to the rootnode when they are no longer connected to anybody.  Furthermore, nodes always only connect to the rootnode.  This can lead to a partitioned network.
The proposed fix is to try to maintain connections to all nodes in the rootlist.  By filtering ourselves from the rootlist, all nodes can be configured in the same way, with the rootlist being the complete list of validating peers.
@jeffgarratt is working on the fix.

For completeness, here are logs from a 2dI4upQIQ retest I ran today using June 20 image 35326c2.
2dI4upQIQ_35326c2_June20_fail.tar.gz

A couple of notes:

The test referenced by @lhaskins is incorrect, because we're waiting for the transaction to be committed on VP3 and then we also query VP3, but VP3 is down. I assume you probably mean VP0 there, given the title of the issue. (The new test still fails, but at least it's the right test now.)
The quick way of fixing this, via a static list of rootnodes won't work because it breaks our behave tests. Docker Compose does not allow circular dependencies, so vp0 and vp1 cannot set up links to each other, unless the ambassador pattern is used.
I am working on having the rootnodes list generated dynamically, and then persisted to disk.

@kchristidis can you explain (2)?

@corecode Maybe @kchristidis has more to add, but Docker only lets you specify dependencies for linking in one direction.  So, if service A depends on service B, docker will set up port forwardings and environment in A to direct to B.  But, because B must be created before A in this scenario, B cannot refer to any properties fo A.
@kchristidis I understand and appreciate the ambassador pattern in docker deployments, but if at all possible, this is something which would be nice to avoid in our tests.  Because of the userspace TCP forwarding of socat, the network errors you can encounter are often unintuitive and might make debugging painful.  For instance, when a TCP connection is attempted when the other end of the ambassador is not up, the connection opens, but then immediately closes with an EOF (indicating the other end us up, but for some reason not responding correctly).   Just my 2 cents against introducing the ambassador pattern into our tests.

Ah, so is it just a matter of not having name mappings to IPs?

@corecode: What @jyellick mentioned covers this, see for example: http://stackoverflow.com/questions/29307645/how-to-link-docker-container-to-each-other-with-docker-compose
@jyellick: The reason we're going with dynamic lists and persisting is so that we can avoid introducing the ambassador pattern.

@kchristidis  With your commit 6524f7c, for the original scenario (stop 2 nodes, invokes, restart 2 nodes, invokes), the behavior is improved: the consensus resumes and all peers are in sync and process additional invokes. However, the requests that were queued while only 2 peers were running appear to be lost.
Another thing we cannot explain yet: our behave test for the same original scenario (attached with other logs) passes.
june22_bug1874_repro_6524f7c.tar.gz

@scottz64: I will investigate further.

Issues 1942 and 1874 are fixed. We tested v0.5 commit 5efed61 (images built today 6/27 after noon, including PRs 2007 and 2016), and confirmed using testcases in both Behave and GO SDK.


no change in mining speed

after creating multiple singleplayer worlds and playing around in the configs, the mod does not seem to work at al.
I was hoping, that as per the original setting the block breaking speed would be doubled, but that seems to not have been the case. even after trying multiple times to get it to work with the instant break configuration 0.0, no changes in breaking speed could be identified.
game version 1.16.5

I'm sorry, but I cannot recreate this problem with said version.
Please attach more information, - attach your config file, upload a video of the problem you are having etc.


Superset In-memory engine

An in-memory engine on superset would be super helpful in reducing the number of queries that gets fired concurrently on the back end database. This in memory engine can be used to keep data in memory and run queries against it. This will improve speed and efficiency.

Well you can use in memory sqlite right now :) jokes aside see @mistercrunch comment in #3302 . Unless you are going to write a connector please close, maybe we can rename #3302.

Notice: this issue has been closed because it has been inactive for 242 days. Feel free to comment and request for this issue to be reopened.


feat(ktable): add options for table column header icons

Summary
Adds 7 new options to add and customize icons in table column headers. I did my best to make the options descriptive and specific so that there was as little ambiguity as possible.

Screenshots

PR Checklist

[ ] Does not introduce dependencies
[ ] Functional: all changes do not break existing APIs and if so, bump major version.
[ ] Tests pass: check the output of yarn test
[ ] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[ ] Framework style: abides by the essential rules in Vue's style guide
[ ] Cleanliness: does not have formatting issues, unused code (e.g., console.logs, debugger), or leftover comments
[ ] Docs: includes a technically accurate README, uses JSDOC where appropriate

@dustinryerson would it be possible to just allow slotting in an icon into the table header instead of defining all these props, etc.? Then the icon would still be controlled via the host app, but would prevent deepening the dependence/integration of KIcons into KTable.

@adamdehaven yep you're right, I think that's the best route. I'll close this. Thanks!


Security Portion of Onboarding Early Adopters#230

Describe the issue
Early Adopters will get an onboarding package for the managed cloud service. There is the potential for a privacy and security portion to be included in onboarding.
Which Sprint Priority is this issue related to?
Milestone ??
Additional context
Need to be familiar with the onboarding package before designing content for the privacy portion.
Definition of done

Clear understanding of the onboarding package and where privacy content would fit.
15 min PowerPoint slides with the CP branded deck to explain the findings from the security assessment of AWS (things to watch out for, things that are must haves when consuming services).
Documentation to include details around security next steps: what the stra covers, what their program stra will need to cover and where to go for help.

meeting w/bh
include info/visual from #231
ensure security staff/miso at meeting
review internally before submitting.


Password validation feature forces all passwords to be replaced

TL;DR
https://github.com/terraform-google-modules/terraform-google-sql-db/pull/376 introduced password validation feature and set special = true on random_password resource, which forces it to be re-created and thus change the password for all users.
Expected behavior
I'd expect passwords to remain untouched if the new feature isn't used.
Observed behavior
Random password is regenrated and user updated:
  # module.argo-workflows-dev-db-postgresql.google_sql_user.default[0] will be updated in-place
! resource "google_sql_user" "default" {
        id                      = "argo//argo-workflows-dev-db"
        name                    = "argo"
!       password                = (sensitive value)
        # (5 unchanged attributes hidden)
    }

  # module.argo-workflows-dev-db-postgresql.random_password.user-password must be replaced
-/+ resource "random_password" "user-password" {
!       bcrypt_hash = (sensitive value)
!       id          = "none" -> (known after apply)
!       result      = (sensitive value)
!       special     = false -> true # forces replacement
        # (10 unchanged attributes hidden)
    }

Terraform Configuration
N/A

Terraform Version
Terraform v1.3.7
on darwin_arm64
+ provider registry.terraform.io/hashicorp/google v4.51.0
+ provider registry.terraform.io/hashicorp/google-beta v4.51.0
+ provider registry.terraform.io/hashicorp/http v3.2.1
+ provider registry.terraform.io/hashicorp/null v3.2.1
+ provider registry.terraform.io/hashicorp/random v3.4.3
+ provider registry.terraform.io/winebarrel/mysql v1.10.6

Additional information
No response

An obvious workaround would be to set the password manually, but we have 50+ databases, so if it's possible to avoid doing that, it would be amazing.

Ay,
We got the same problem here, even if we're not using random password feature. We manually set all password from a secret :
    {
      name            = "xxx"
      password        = data.doppler_secrets.xxx.map.PASSWORD
      random_password = false
    },

But it still trigger the same problem as @kpocius :
  # module.xxx.module.postgresql.random_password.user-password must be replaced
-/+ resource "random_password" "user-password" {
      ~ bcrypt_hash = (sensitive value)
      ~ id          = "none" -> (known after apply)
      ~ result      = (sensitive value)
      ~ special     = false -> true # forces replacement
        # (10 unchanged attributes hidden)
    }

I don't understand what's happening here. :grimacing:

@KrustyHack, random_password resource is not conditional, so it is applied even if you don't end up using it. I believe in your case it is safe to apply -- it will regenerate those passwords, but they won't be used anywhere.

The fix from @bharathkkb will also resolve this issue once it's merged

Sorry for the delay everyone! https://github.com/terraform-google-modules/terraform-google-sql-db/pull/421 is merged


doc: fix multiple typos in library documents.

我都说了不要创建新的PR了……

Sorry for my impatience. I will spend time studying how to do it with "standard  operations".  Now it's on my task list.


Is that possible to install with paq?

Did you check docs and existing issues?

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

Neovim version (nvim -v)
Last version
Operating system/version
Arch last upgrade
Describe the bug
Hi, I am new on vim trying to setup it. I probably dont understand how manage things between vim and lua plugins, but I can't make flash to work. I am trying to install it via paq (I don't want to use Lazy, I want a lightweight plugin manager like vim plug). Paq install it well, but the keybindings are not working, nothing happens...
Here the code I wrote:
require "paq" {
{
  "folke/flash.nvim",
  opts = {},
  keys = {
    { "s", mode = { "n", "o", "x" }, function() require("flash").jump() end, desc = "Flash" },
    { "S", mode = { "n", "o", "x" }, function() require("flash").treesitter() end, desc = "Flash Treesitter" },
    { "r", mode = "o", function() require("flash").remote() end, desc = "Remote Flash" },
    { "R", mode = { "o", "x" }, function() require("flash").treesitter_search() end, desc = "Treesitter Search" },
    { "<c-s>", mode = { "c" }, function() require("flash").toggle() end, desc = "Toggle Flash Search" },
  }
}
}

I have installed treesitter of course. Thanks to any clues!
Steps To Reproduce
Write the code above in init.lua
Expected Behavior
I would like just to activate it...
Repro
require "paq" {
    "savq/paq-nvim", -- Let Paq manage itself

    { 'nvim-treesitter/nvim-treesitter' },

{ "folke/flash.nvim",
  opts = {},
  keys = {
    { "s", mode = { "n", "o", "x" }, function() require("flash").jump() end, desc = "Flash" },
    { "S", mode = { "n", "o", "x" }, function() require("flash").treesitter() end, desc = "Flash Treesitter" },
    { "r", mode = "o", function() require("flash").remote() end, desc = "Remote Flash" },
    { "R", mode = { "o", "x" }, function() require("flash").treesitter_search() end, desc = "Treesitter Search" },
    { "<c-s>", mode = { "c" }, function() require("flash").toggle() end, desc = "Toggle Flash Search" },
  }
}

}

well that keys table is lazy.nvim specific
you just have to define the keybindings yourself
and the opts={} makes lazy call the setup function. With paq you have to do that yourself as well then

Ah! OK, thanks! Calling the setup function, I see, about the bindings, what is the syntax ? I guess it is not something like map key <Plug>Command ? That 's the thing which muddles me : many plugins comes with commands I can run in the command prompt or link to keys in init.vim, for example Telescope. It is not the case with this plugin?
Or maybe, I saw for telescope I can use lua function like that nnoremap <leader>ff <cmd>lua require('telescope.builtin').find_files()<cr>, maybe it is the way to bind the flash plugin functions like : <cm>lua require("flash").jump()<cr> ??

just use lua keybindings
vim.keymap.set({"n","o","x"},"s",function()...end,{desc="Flash"})

Thank you very much @max397574, it works! I am glad because it is a nice plugin, I like the fact than the all page is grayed out when jumping, usefull to focus on the target and distinguishing the labels.
Anyway, at the end, I set up my vim with vim-plug. Simple and efficient. I post here the full code to help people after me:
Install with vim-plug
In init.vim:
...
Plug 'folke/flash.nvim'
...
call plug#end()
...
source ~/.config/nvim/plugrc/flashrc.vim

In the file named here flashrc.vim:
lua << EOF
    require('flash').setup{
        search = {
            mode = function(str)
              return "\\<" .. str
            end
        },
        jump = {
            autojump = true,
        },
        label = {
            rainbow = {
              enabled = true,
              shade = 9,
            }
        }
    }

    vim.keymap.set({"n","o","x"},"j", function() require("flash").jump() end, {desc="Flash"})
    vim.keymap.set({"i"}, "<C-j>", function() require("flash").jump() end, {desc="Flash"})

EOF


console.assert is not a function

Overview
I have a react native app which I am running on android.
I have event-target-shim as a dependency.
Issue
The app was working fine with react-native version 0.59.
But when I upgraded it to react-native version 0.60, I started seeing an error
"console.assert is not a function"
When I remove console.assert statement from line 46 of event-target-shim.js, everything works fine.

Thank you for your report.
But I think that this is not a problem of event-target-shim because the console.assert is standardized in the web standard and is in Node.js. Would you open an issue on React Native?

Thanks for the response.
I will close this issue and open another one on React Native.


Publish in software repos

Is it possible to publish this as a software package in open source software repos like Debian / centos repos. People can discover and install this by using
sudo apt install gitql

or
sudo yum install gitql

That would be a very good one @jsixface! I dont have much time right now but will try to do will when I get some time! Thanks!

This is what I had in mind.

Homebrew for mac
Debian repo for apt install
Centos Extras Repo for yum install
Arch Repo

For homebrew: https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md

Gitql is available on homebrew.
I think it's better to have different issues for each software repo (apt-get, chocolately and so on) so I'm closing this and feel free to help us to give support for the other OS.


HSEARCH-3565 Upgrade to Hibernate ORM 5.3.10.Final

https://hibernate.atlassian.net//browse/HSEARCH-3565
Waiting for CI.

Pull Request Test Coverage Report for Build 1

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.004%) to 83.934%

Files with Coverage Reduction
New Missed Lines
%

engine/src/main/java/org/hibernate/search/store/impl/FSMasterDirectoryProvider.java
1
80.0%

Totals

Change from base Build 1:
-0.004%

Covered Lines:
23755

Relevant Lines:
28302

💛  - Coveralls


How do you get smoother hyperlapses

I've got this working but it's really choppy. What parameters are there for me to change to get a more smooth hyperlapse?

change zoom : 3


Add "reverse" method

The collection.reverse() method reverses the collection. The first item becomes the last one, the second item becomes the second to last, and so on:
Example
await Collect([4, 6, 8, 9])
  .reverse()
  .all()

// [9, 8, 6, 4]

Hi! I want to contribute!
Could you please assign it to me?

Thanks!
Waiting for review


[Django + Python] Error catching for dining dates

As we were in a rush to fix dining menus, we left out key error catching! Here is one example. Help us verify the date and make sure it is within range (if today is Monday, then we want the date to be no further than next Sunday).

Wouldn't something as simple as this suffice?
class Menus(generics.ListAPIView):
    """
    GET: returns list of menus, defaulted to all objects within the week,
    and can specify the filter for a particular day
    """
    serializer_class = DiningMenuSerializer

    def get_queryset(self):
        if date_param := self.kwargs.get("date"):
            date = make_aware(datetime.datetime.strptime(date_param, "%Y-%m-%d"))
            if date < timezone.now().date():
                raise Http404
            return DiningMenu.objects.filter(date=date)
        else:
            start_date = timezone.now().date()
            end_date = start_date + datetime.timedelta(days=6)
            return DiningMenu.objects.filter(date__gte=start_date, date__lte=end_date)


Version 4.18.0 fails to compile maven modules

When building the recently released 4.18.0 on Archlinux via the AUR package with
gradle -Pversion=4.18.0 fatJar
I get the following error:
`A problem occurred evaluating root project 'Raccoon-desktop'.

Could not find method compile() for arguments [net.dongliu:apk-parser:2.6.10] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler`

Uncommenting the apk-parser yield the same result with the next maven module, so this seems to be a general issue. Is this my fault, did I miss a change? Or is this a real issue?

Instead of using your local gradle version you should better use gradlew which currently defaults to Gradle 6.8.2. Different gradle versions can cause errors like those you have encountered.

Thanks, that indeed solved the problem.


Fix OSName setvariable failures

Noticing a bunch of failures in our release pipelines because the OSName variable is flagged as read only and we are attempting to change it in the verify OS template. This removes that line altogether. Although I am not sure what side effects this will cause since I don't know why this setvariable was in there in the first place.

/Adding @weshaggard
If we're removing the setting of the OSName we should probably be removing where OSName is being used. Is the check it's doing in here even still valid?
Java -
eng\pipelines\client.yml <-- This file should be deleted, it's referencing older pom files that don't exist but there's still a linger pipeline connected to this.
sdk\management\pipelines\fluentJavaMgmt.yml, there's an OSName: 'Windows' in the strategy matrix which can probably just be removed.
JS - Only used to print the test run title:
testRunTitle: "$(OSName)...
eng\pipelines\templates\jobs\archetype-sdk-client.yml lines 267 and 277
eng\pipelines\templates\jobs\archetype-sdk-integration.yml lines 260 and 270
Net - Only used to print the test run title
testRunTitle: "$(OSName)....
eng\pipelines\templates\jobs\archetype-sdk-client.yml line 156
eng\pipelines\templates\jobs\archetype-sdk-mgmt.yml line 67
eng\pipelines\templates\jobs\archetype-sdk-tests.yml line 125
Python - Used in the test run title
testRunTitle: '$(OSName)...
eng\pipelines\templates\jobs\tests-nightly-python.yml line 49
eng\pipelines\templates\steps\build-test.yml line 57
Set in each test matrix entry in the following
sdk\eventhub\tests.yml
sdk\servicebus\tests.yml
azure-sdk-for-c/azure-sdk-for-cpp - neither repository use this

We had already made this change before then reverted it . The agreement then was to not set OSName until after verify agent OS has run then it can be used anytime after that step. So I believe what need to be done is remove the cases where it is being set prior to verifyin the agent OS. For the testRunTitle it can remain.

Closing in favor of https://github.com/Azure/azure-sdk-for-python/pull/12147


Session problem

Hi, I'm new to Dash, and I'm using dash-cognito-auth. My application uses Client Sessions (I don't have Flask-Session), and I log in and out normally. However, in some situations, if another user logs in after me (in another browser/workstation), my session starts to show the other person's user. As if their session replaces mine.
Any idea why this happens?
Thank you!

By "client sessions", are you referring to Cookie-Based sessions?
This is usually an indicator that you're storing data in global variables or something like that which persist over the lifecycle of multiple requests. Essentially something that circumvents the existing session management mechanisms of Flask / Dash.
IMO it's very unlikely that this is something related to this library or the way Flask handles sessions (which this library builds on).

Thanks, Maurice. Yes, the app uses cookie-based sessions.
I'll look into the code based on your recommendation.


Emit proper log messages in verified-destinations

Working on this issue - Here's the link to my  forked branch: Link


Add convenience constructor: Stream.single(T value)

I often find myself returning streams with a single value.  A convenience constructor would alleviate the following:
new Stream<T>.fromIterable(<T>[value])

There is new Future<T>.value(value).asStream().

I lump that in with new Stream<T>.fromIterable(<T>[value]) -- both work well enough, but they obscure the code ever so slightly.
I'm of two minds on convenience methods/constructors.  On one hand, they bloat the API, but on the other, they make calling code look cleaner...

It is indeed a balancing problem. The utility constructor (or function or class) should be used often enough that it outweighs the extra complexity, be it space, namespace, or user consideration of whether to use it (which requires understanding it), that the feature adds just by existing.
I'm not sure a Stream.single carries its own weight in the platoform libraries, but it could if put in package:async (by being optional, not everybody is affected by the extra complexity, something the platform libraries cannot claim).


Show project CI/test status

Useful to have an overview over whether changes that were pushed passed in CI (and not just locally).
Should probably default to the tracking branch of the branch one is currently on, but at least also allow to show latest master and recent tags. Optionally also allow to browser other builds/versions.
Probably best done using the Github API, as we already have API key, and most CI service providers (like Travis CI) report their status there.

Out of scope


docs: add web_search.ipynb

@willbakst
I applied your suggestion to quickstart.ipynb
But, I keep the branch until merge the new PR.


Fix Caching

Addresses issues in the caching introduced by #363. Currently, the CI should fail, as it has no database to connect to, which is required for the tests introduced by this PR.

Is there a distinction between using workspace_mapping() and cached_workspace_mapping() now? What I mean is, are there places where you must use one and not the other?

Example:
https://github.com/multinet-app/multinet-server/blob/7c309821094f4a9a04a53b97bdbc1805f0261c4b/multinet/db.py#L110-L112
In general, places where you don't want the use of workspace_mapping to have any effect on the cache. I could see wanting to rename workspace_mapping to uncached_workspace_mapping (or similar), and renaming cached_workspace_mapping to workspace_mapping (or similar), as we use the cached version more often.

Is there a distinction between using workspace_mapping() and cached_workspace_mapping() now? What I mean is, are there places where you must use one and not the other?

Example:
https://github.com/multinet-app/multinet-server/blob/7c309821094f4a9a04a53b97bdbc1805f0261c4b/multinet/db.py#L110-L112
In general, places where you don't want the use of workspace_mapping to have any effect on the cache. I could see wanting to rename workspace_mapping to uncached_workspace_mapping (or similar), and renaming cached_workspace_mapping to workspace_mapping (or similar), as we use the cached version more often.

So the problem here is the technical debt we're about to introduce: developers now have to know the effect of consulting the workspace mapping, which means our abstraction is leaking in a bad way. Renaming workspace_mapping to uncached_workspace_mapping would be good in that it would signal to devs that there's some choice to be made here, but it doesn't protect them from making the wrong call and breaking correctness.
It feels like this issue of asking for a workspace by name vs. creating a new entry or changing an existing entry is starting to become larger than can just be handled by the naive use of the lru cache decorator. I see two ways out of this:

The simpler way is to use the fix I suggested on Slack yesterday: to simply invalidate the cache whenever a renaming, deletion, or creation occurs, and let the cache handle the common case of lookups when the state isn't changing. This would be a bad option if workspace_exists() is used more often than I think it is.

The more complex, but probably correct way is to abstract these operations into a module, make the workspace mapping collection into a private variable, and export public functions to do the actual operations (create, rename, delete, and check for existence). The caching mechanism would probably become more explicit, like a dict we maintain in that same module between invocations of the public functions. Perhaps there's an actual LRU cache implementing object in the standard library we could use, but access at a finer granularity than the @lru_cache decorator does.

The other issue here is testing--we need to figure out how to run those tests in CI, because a feature like this really will require us to make sure it's working long term.
To summarize though: the divergence of our once easy-to-use function into explicitly cached and uncached variants represents a broken abstraction and an associated large amount of technical debt that I'm not willing to take on in the current form. This is a really important crossroads, so let's discuss what to do in good detail before we move on.

So the problem here is the technical debt we're about to introduce: developers now have to know the effect of consulting the workspace mapping, which means our abstraction is leaking in a bad way. Renaming workspace_mapping to uncached_workspace_mapping would be good in that it would signal to devs that there's some choice to be made here, but it doesn't protect them from making the wrong call and breaking correctness.
It feels like this issue of asking for a workspace by name vs. creating a new entry or changing an existing entry is starting to become larger than can just be handled by the naive use of the lru cache decorator. I see two ways out of this:

The simpler way is to use the fix I suggested on Slack yesterday: to simply invalidate the cache whenever a renaming, deletion, or creation occurs, and let the cache handle the common case of lookups when the state isn't changing. This would be a bad option if workspace_exists() is used more often than I think it is.

Currently, this is what's being done. On calls to creating, renaming or deleting a workspace, the cache is invalidated. I'm not sure what you mean referring to workspace_exists being possibly called often? That function won't affect the cache, because it's not using the cached version of workspace_mapping.

The more complex, but probably correct way is to abstract these operations into a module, make the workspace mapping collection into a private variable, and export public functions to do the actual operations (create, rename, delete, and check for existence). The caching mechanism would probably become more explicit, like a dict we maintain in that same module between invocations of the public functions. Perhaps there's an actual LRU cache implementing object in the standard library we could use, but access at a finer granularity than the @lru_cache decorator does.

I'm kind of weary to try to implement our own caching, as now we'd have to worry about general caching bugs, as well as bugs in the caching mechanism itself. Can you explain why you think we should stray away from lru_cache?
I do think we should be explicit about what's being cached, and where. For example, cached_workspace_mapping vs workspace_mapping. I think separating the two, and having cached_ functions that just cache calls to the original function is a good approach, because it makes it clear that we're using caching, and allows us to use the original functions if we need to. If we were to do this, I'd have to (and should) apply the same change to get_workspace_db. Let me know what you think about this approach.

The other issue here is testing--we need to figure out how to run those tests in CI, because a feature like this really will require us to make sure it's working long term.

I agree. If we were to just specify ARANGO_HOST, ARANGO_PROTOCOL and  ARANGO_PASSWORD in the environment where the tests run, they'd succeed (assuming we actually point to a valid arango instance). As far as what that should be, I'm not sure, but I think we can agree it should be separate from our production db.

I agree. If we were to just specify ARANGO_HOST, ARANGO_PROTOCOL and ARANGO_PASSWORD in the environment where the tests run, they'd succeed (assuming we actually point to a valid arango instance). As far as what that should be, I'm not sure, but I think we can agree it should be separate from our production db.

If we go for a full staging set up at some point, could this be the staging db?

If we go for a full staging set up at some point, could this be the staging db?

Depends on what we define as staging. The database specified here will be running tests on it whenever there's a PR, so we'd have to specify if we want to mix the two or not.

So the problem here is the technical debt we're about to introduce: developers now have to know the effect of consulting the workspace mapping, which means our abstraction is leaking in a bad way. Renaming workspace_mapping to uncached_workspace_mapping would be good in that it would signal to devs that there's some choice to be made here, but it doesn't protect them from making the wrong call and breaking correctness.
It feels like this issue of asking for a workspace by name vs. creating a new entry or changing an existing entry is starting to become larger than can just be handled by the naive use of the lru cache decorator. I see two ways out of this:

The simpler way is to use the fix I suggested on Slack yesterday: to simply invalidate the cache whenever a renaming, deletion, or creation occurs, and let the cache handle the common case of lookups when the state isn't changing. This would be a bad option if workspace_exists() is used more often than I think it is.

Currently, this is what's being done. On calls to creating, renaming or deleting a workspace, the cache is invalidated. I'm not sure what you mean referring to workspace_exists being possibly called often? That function won't affect the cache, because it's not using the cached version of workspace_mapping.

I thought the bug we had was caused by checking for workspace W's existence leading to None being cached as the (wrong) mapping value for W? What I meant about the frequency of workspace_exists was that, under this scheme, if we are calling that a lot we'd be invalidating the cache a lot, and losing out on the performance benefits.

The more complex, but probably correct way is to abstract these operations into a module, make the workspace mapping collection into a private variable, and export public functions to do the actual operations (create, rename, delete, and check for existence). The caching mechanism would probably become more explicit, like a dict we maintain in that same module between invocations of the public functions. Perhaps there's an actual LRU cache implementing object in the standard library we could use, but access at a finer granularity than the @lru_cache decorator does.

I'm kind of weary to try to implement our own caching, as now we'd have to worry about general caching bugs, as well as bugs in the caching mechanism itself. Can you explain why you think we should stray away from lru_cache?

The reason is that the simple caching strategy isn't working, and is leading us to explicitly create cached and uncached paths (see more about this below). The alternative is to refine the caching strategy in some manner. I agree that I don't want to implement function memoization myself, but we're stuck between a rock and a hard place as things stand.

I do think we should be explicit about what's being cached, and where. For example, cached_workspace_mapping vs workspace_mapping. I think separating the two, and having cached_ functions that just cache calls to the original function is a good approach, because it makes it clear that we're using caching, and allows us to use the original functions if we need to. If we were to do this, I'd have to (and should) apply the same change to get_workspace_db. Let me know what you think about this approach.

But this is what I'm trying to avoid. What I want is a solution where no one ever needs to know which workspace mapping to call.
If what you're saying is that once we fix this, future developers (including future versions of ourselves) won't have to worry about this anymore, then that's one thing, but I can't imagine that's what the situation will be. For instance, at some point we might want to create "symlinks", at which point we'll want to add a mapping entry that maps a name to an existing name (or something like that; just making up the example off the top of my head). We'll be back to thinking hard about whether to use the cached or uncached variant, and we'll likely get it wrong like we did in this instance.
Ultimately what I'm saying is, we should be able to design the workspace mapping functionality in such a way that all this cached/uncached complexity is hidden away inside the module, and we devs can happily just call functions like add_mapping(), remove_mapping(), workspace_exists(), get_workspace(), etc., without every thinking about caching unless we're implementing new functionality within that module.
I would be fine with deferring such a thing to a new PR, but I wouldn't be fine with delaying that work for very long.
It is also possible that I'm misunderstanding the problem here, but this is just setting off my spider sense.

The other issue here is testing--we need to figure out how to run those tests in CI, because a feature like this really will require us to make sure it's working long term.

I agree. If we were to just specify ARANGO_HOST, ARANGO_PROTOCOL and ARANGO_PASSWORD in the environment where the tests run, they'd succeed (assuming we actually point to a valid arango instance). As far as what that should be, I'm not sure, but I think we can agree it should be separate from our production db.

Don't we currently have some tests that are using the live db for testing? I agree that that's not ideal but if it's what we're doing now we should continue, and we should also file an issue to figure out a better staging/testing scenario.

Had a chat with @AlmightyYakob. He convinced me that this approach is largely correct. We identified two TODOs:

[ ] instead of a cached and uncached variant, we can simply have the cached function, and refer to its __wrapped__ attribute to access the underlying (uncached) function. This will resolve my fears about confusing future developers.
[ ] since we don't have a good solution for CI testing with a live database, we'll mark those tests as skipped for now so that CI passes and the automated deployments succeed. @AlmightyYakob has run those tests locally, so we have some confidence that the code is correct. At a future time, we will figure out a robust live testing strategy and unskip those tests.


Typescript "reactive" nested "computed" will lose all types and become "any" type

import { reactive, computed } from 'vue'

// "reactive" nested "computed", the type of "state" attribute used in "computed" is all wrong with "any"
const state = reactive({
  name: 'name',
  age: 18,
  getName: computed(() => state.name)
})
// "state" becomes "any" type
state.age = 'any'
console.log(state === 1)

Duplicate of https://github.com/vuejs/vue-next/issues/963


PurpleI2P.i2pd version 2.53.0

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-07-31 04:49:47.827 [FAIL] Installer failed security check. Url: https://github.com/PurpleI2P/i2pd/releases/download/2.53.0/setup_i2pd_v2.53.0.exe Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
(Automated response - build 887.)

/azp run


Update fiddle features/macos-dock-menu

Template: features/macos-dock-menu
Rel: #6

This task is for organizational and tracking purposes. Refer to the linked 'Rel:' issues for further details.

EDIT: Fixed template

Don't know if there's a way to link this to the PR in the electron repo.

GitHub doesn't support cross-org linking yet but you can add it to the issue either in the first comment blurb or down here in a new comment.


[CCEE] Remove limitation / whitelisting for CCEE regions from provisioner

Description
Caused by #3294, we introduced a restriction of allowed CCEE regions to the provisioner. WE agreed with @kyma-project/gopher to remove this limitation from provisioner and to take the KEB as single point of truth which provides us this data pre-validated.
AC:

[x] Provisoner is not limiting the region for CCEE and using the value provided by KEB without applying further checks

Changes have been successfully propagated to environments (Dev, Stage, Prod)


coverage added

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6272867). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #22   +/-   ##
=========================================
  Coverage          ?   89.52%
=========================================
  Files             ?       20
  Lines             ?      296
  Branches          ?        0
=========================================
  Hits              ?      265
  Misses            ?       31
  Partials          ?        0

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

tested several coverage packages. the only one trat ran in OK mode is CodeCov. need to merge for more statik info and badge beacuse it is connected to master. created in c5c169f658f285ec3c23712555438adca8c11abd


feature/setup_18

PyPi 0.0.18

Will fail until https://github.com/macrosynergy/macrosynergy/pull/500 has been approved.

Problem still persists. Will revert to the original solution.


php bin/console audit:schema:update something with steps

So I am trying to launch command ang I get "Unable to display the estimated time if the maximum number of steps is not set.". where do I set them?
php bin/console audit:schema:update
Introspecting schema...
Unable to display the estimated time if the maximum number of steps is not
set.

@mechemsi Thanks for the report, I've never encountered such an issue :/
I need to investigate a bit so can you tell me more about your environment:

what version of the bundle are you using? (latest stable or "unstable" master branch)
what kind of database are you using and which version? (MySQL 8, Postgresql...)
are you in the process of upgrading an already audited schema or are you setting up the bundle for the first time?

using 2.5 version
mysql 8 database
trying to set up for the first time with seperate database for audit log

Thanks. I'll look at it in a few hours and keep you updated

@mechemsi well, I can't find a way to reproduce the issue other than running the command on a system with no audited entity :/
Is that your case? Can you post your dh_doctrine_audit.yaml file?
Can you test master branch and provide some feedback?

Also bin/console doctrine:schema:update --force doesnt create audit tables now i checked, do not know why.
dh_doctrine_audit.yaml:
dh_doctrine_audit:
enabled: true
table_prefix: ''
table_suffix: '_audit'
entities:
App\Entity\Company: ~
and services.yaml:
dh_doctrine_audit.manager:
class: DH\DoctrineAuditBundle\AuditManager
arguments<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>public: true
dh_doctrine_audit.event_subscriber.create_schema:
    class: DH\DoctrineAuditBundle\EventSubscriber\CreateSchemaListener
    arguments<EMAIL_ADDRESS>    tags:
        - { name: doctrine.event_subscriber, connection: log }

okay with command  php bin/console doctrine:schema:update --em=log --force i created tables but needed to change entity manager settings to match default to create audit tables, but audit trying to insert data to default database instead to second one even when I have configured for second database as i posted above

@mechemsi I'll update the README.md file to add the --em option when using a separate database, thanks for the reminder.
Then I don't really understand what you mean with:

[...] but needed to change entity manager settings to match default to create audit tables, but audit trying to insert data to default database instead to second one even when I have configured for second database as i posted above

Yea for some reason some configuration of entity manager had to match default one , fields dir and prefix then audit tables are created in second database, but also main tables not only audit ones are created. But after creating audit tables in second database audit bundle makes sql query to insert data to default database (which doesnt have audit tables), when configuration is for other database where audit tables exist

I'm going to try to reproduce on a test environment

@mechemsi Can you test against master branch again please? I've just pushed some changes regarding using a secondary database to store audits.
Note: you have to change your services.yaml as described here

Now it is working, posting to second database, but found one configuration thing, if I only leave configuration in services.yaml as now described in documentation doctrine:schema:update doesn't create audit tables in second database, but if I use configuration like that:
dh_doctrine_audit.manager:
    class: DH\DoctrineAuditBundle\AuditManager
    arguments<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    #alias: dh_doctrine_audit.manager
    public: true

dh_doctrine_audit.event_subscriber.create_schema:
    class: DH\DoctrineAuditBundle\EventSubscriber\CreateSchemaListener
    arguments<EMAIL_ADDRESS>    tags:
        - { name: doctrine.event_subscriber, connection: log }

dh_doctrine_audit.configuration:
    class: DH\DoctrineAuditBundle\AuditConfiguration
    arguments:
        - "%dh_doctrine_audit.configuration%"
        -<EMAIL_ADDRESS>        - "@request_stack"
        -<EMAIL_ADDRESS>        -<EMAIL_ADDRESS>
everything works fine, tables created in second database and audit sql executed to second database for audit

@mechemsi well, I do not need such configuration to have it work: setting the dedicated (secondary) entity manager suffice in my test environment.
Here is my configuration as an example:
# config/doctrine.yaml
doctrine:
    dbal:
        default_connection: default
        connections:
            default:
                driver: 'pdo_sqlite'
                charset: utf8mb4
                default_table_options:
                    charset: utf8mb4
                    collate: utf8mb4_unicode_ci
                url: '%env(resolve:DATABASE_URL)%'
            audits:
                driver: 'pdo_sqlite'
                charset: utf8mb4
                default_table_options:
                    charset: utf8mb4
                    collate: utf8mb4_unicode_ci
                url: '%env(resolve:AUDITS_DATABASE_URL)%'
    orm:
        default_entity_manager: default
        auto_generate_proxy_classes: true
        entity_managers:
            default:
                connection: default
                naming_strategy: doctrine.orm.naming_strategy.underscore
                auto_mapping: true
                mappings:
                    App:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
                        alias: App
            audits:
                connection: audits
                naming_strategy: doctrine.orm.naming_strategy.underscore

# config/services.yaml
    dh_doctrine_audit.configuration:
        class: DH\DoctrineAuditBundle\AuditConfiguration
        arguments:
            - "%dh_doctrine_audit.configuration%"
            -<EMAIL_ADDRESS>            - "@request_stack"
            -<EMAIL_ADDRESS>            -<EMAIL_ADDRESS>
Then, running bin/console doctrine:schema:update --force creates both regular tables in main database and audit tables in secondary database.
But, bin/console doctrine:schema:update only displays/counts queries that go to main database (queries related with a concrete entity precisely, which is not the case for audits as there are no entity mapped to audit_tables)

Okay thanks now it is completely working :)

bin/console doctrine:schema:update --force not creating now tables if i use configuration like yours for some reason, to create tables my entity manager config must be like this
        log:
            naming_strategy: doctrine.orm.naming_strategy.underscore
            connection: log
            mappings:
                Log:
                    is_bundle: false
                    type: annotation
                    dir: '%kernel.project_dir%/src/Entity'
                    prefix: 'App\Entity'
                    alias: Log

@mechemsi can you post (or use a private gist if you prefer) your doctrine.yaml and services.yaml files please?

# services.yaml
# This file is the entry point to configure your own services.
# Files in the packages/ subdirectory configure your dependencies.

# Put parameters here that don't need to change on each machine where the app is deployed
# https://symfony.com/doc/current/best_practices/configuration.html#application-related-configuration
parameters:
    locale: 'en'

services:
    # default configuration for services in *this* file
    _defaults:
        autowire: true      # Automatically injects dependencies in your services.
        autoconfigure: true # Automatically registers your services as commands, event subscribers, etc.

    # makes classes in src/ available to be used as services
    # this creates a service per class whose id is the fully-qualified class name
    App\:
        resource: '../src/*'
        exclude: '../src/{DependencyInjection,Entity,Migrations,Tests,Kernel.php}'

    # controllers are imported separately to make sure services can be injected
    # as action arguments even if you don't extend any base controller class
    App\Controller\:
        resource: '../src/Controller'
        tags: ['controller.service_arguments']

    fos_user_fact:
        alias: fos_user.registration.form.factory
        public: true

#    fos_user.registration.form.factory:
#        class: FOS\UserBundle\Form\Factory\FormFactory

#    fos_rest.view_handler:
#        class: FOS\RestBundle\View\ViewHandler

    FOS\OAuthServerBundle\Entity\ClientManager:
        alias: fos_oauth_server.client_manager.default
        public: true

#    FOS\RestBundle\View\ViewHandler:
#        alias: fos_rest.view_handler
#        public: true

#    fos_rest:
#        format_listener:
#            rules:
#                - { path: ^/, prefer_extension: true, fallback_format: json, priorities: [ json ] }

    App\Command\OauthClientCreateCommand:
         arguments:
            $client_manager<EMAIL_ADDRESS>
    app.form.registration:
        class: App\Form\RegistrationType
        tags:
            - { name: form.type, alias: app_user_registration }

#    fos_rest.view_handler:
#        alias: fos_rest.view_handler.default

#    App\Command\:
#        resource: '../src/Command'

    # add more service definitions when explicit configuration is needed
    # please note that last definitions always *replace* previous ones
    #FOS\OAuthServerBundle\Document\ClientManager: ~

#    FOS\OAuthServerBundle\Document\ClientManager:
#        alias: fos_oauth_server.client_manager.default
#        public: true
#
#    FOS\OAuthServerBundle\Model\ClientManager<EMAIL_ADDRESS>    App\Service\FileUploader:
            arguments:
                $targetDirectory: 'tmp/'

#    dh_doctrine_audit.manager:
#        class: DH\DoctrineAuditBundle\AuditManager
#        arguments<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>#        #alias: dh_doctrine_audit.manager
#        public: true
#
#    dh_doctrine_audit.event_subscriber.create_schema:
#        class: DH\DoctrineAuditBundle\EventSubscriber\CreateSchemaListener
#        arguments<EMAIL_ADDRESS>#        tags:
#            - { name: doctrine.event_subscriber, connection: log }

    dh_doctrine_audit.configuration:
        class: DH\DoctrineAuditBundle\AuditConfiguration
        arguments:
            - "%dh_doctrine_audit.configuration%"
            -<EMAIL_ADDRESS>            - "@request_stack"
            -<EMAIL_ADDRESS>            -<EMAIL_ADDRESS>
# doctrine.yaml
parameters:
    # Adds a fallback DATABASE_URL if the env var is not set.
    # This allows you to run cache:warmup even if your
    # environment variables are not available yet.
    # You should not need to change this value.
    env(DATABASE_URL): ''
    env(DATABASE_URL2): ''

doctrine:
    dbal:
        default_connection: default
        # configure these for your database server
        connections:
            default:
                driver: 'pdo_mysql'
                server_version: '5.7'
                charset: utf8mb4
                default_table_options:
                    charset: utf8mb4
                    collate: utf8mb4_unicode_ci

                url: '%env(resolve:DATABASE_URL)%'
            log:
                driver: 'pdo_mysql'
                server_version: '5.7'
                charset: utf8mb4
                default_table_options:
                    charset: utf8mb4
                    collate: utf8mb4_unicode_ci

                url: '%env(resolve:DATABASE_URL2)%'
    orm:
        default_entity_manager: default
        auto_generate_proxy_classes: true
        entity_managers:
            default:
                connection: default
                naming_strategy: doctrine.orm.naming_strategy.underscore
                auto_mapping: true
                mappings:
                    App:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
                        alias: App

            log:
                naming_strategy: doctrine.orm.naming_strategy.underscore
                connection: log
                mappings:
                    Log:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
                        alias: Log

#    dql:
#        datetime_functions:
#                test_datetime: App\DQL\DatetimeFunction

@mechemsi ok, I can't figure out right now why you have to set the mappings part in your doctrine.yaml file to have it work, it works without this on the systems I did my tests.
I close this issue for now as you confirmed everything works now. Feel free to reopen it otherwise.


TODO: setup github actions on the api branch

I think we need to have actions set up so that we can also check for commits/pushes on the api branch. Thoughts?

Github Actions has a solution for that : https://medium.com/@SammyRulez/git-monorepos-with-github-actions-e47f56d8793b
We could build a specific action file for the api folder.

Should the behavior be the same as for master ? (Pre-commit / Package / Test)
Could we insert an integration test between package / api ?
To locally test pipelines, act is quite useful.


Store disk image info and add actions

Whenever we generate a disk image, update a json file in extension storage containing the image name, type, and disk image path.
Use this to add Launch VM or Open Folder actions on the original image.

We've added history, which for now is only used to pre-fill the output folder when generating again. We are dropping tentative plans for a vfkit launcher, so there is nothing else to do here and I'm closing this issue.
The rest of the image-generation history we're saving isn't required atm and could be removed... but since there's a good chance that we'll find other tools to launch with or have other actions in the future I plan to leave it in as it'll give us a good list of images pre-whatever-release that we can act on.


LIBXSMM DNN Error: Unsupported architecture in case of legacy compiler

Some of our intrinsic based code paths are incorrectly dispatched if the code was compiled with an insufficient compiler (e.g., GCC 4.8). Everything works as expected with ICC (or newer/sufficient GCC).
make -j
cd samples/deeplearning/cnnlayer; make -j
./run_resnet50.sh 56 1000 -1 f32 F L 0

Above command shows LIBXSMM DNN Error: Unsupported architecture! in case of an insufficient compiler (see above).

The error code is assigned at libxsmm_dnn_convolution_forward.c:64. However, this code path is likely entered due to an invalid handle setup.

No, this code path is entered if no AVX512 target is provided by the compiler, however the cpuid check confirmed that AVX512 is there.
https://github.com/hfp/libxsmm/blob/master/src/libxsmm_dnn_handle.c#L92
This check can only happen, if the used compiler has sufficient AVX512 support. If the compiler has no AVX512 support a platform with AVX512 support needs to be treated as non-AVX512.
-> This if needs to be guarded by compiler versions support AVX512

It's not guarded at all. If a compiler doesn't have AVX512 support, then we the if mentioned above needs to be #ifdef away. When we have such a preprocessor macro, then it's 1min fix.

The issue is still current (and will be resolved once the DL domain is reimplemented).

Fixed in a separate branch (to be merged asap).


Improve warning wording

unexpect -> unexpected

@bragadeesh
Would you merge this for me? I do not have permissions to do so.
Thanks,
Mark

@bragadeesh Would you merge this for me? I do not have permissions to do so. Thanks, Mark

Thanks Mark for your contribution.
I just merged it.


Pt 156915425 store calls in separate state tree v2

Cleaned up branch.

I see this PR had superseded #1064


Feature request: support for cmd.exe console

Hello,
as you state, this package only works with Windows Terminal of Win10. It would, however, be incredibly useful if the classic Windows console which is provided by cmd.exe/conhost.exe could be supported as well.
Even some basic support (i.e. without colors or other fancy things, just cursor positioning and writing) would be welcome. :)

This works with the standard windows console (cmd.exe) it just requires a current version of Windows 10.
I will not provide support for older versions of Windows, because I don't want to do like twice the effort just for supporting outdated  systems like Windows 7 or something like that


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20230524)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

It's compatiable with gluten


Double clicking an element in the Markdown preview does not automatically open the editor

Issue Type: Bug
Documentation says:
Additionally, double clicking an element in the Markdown preview will automatically open the editor for the file and scroll to the line nearest the clicked element.
But I was unable to get it working...
VS Code version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T02:26:57.615Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 x 3597)

Memory (System)
15.88GB (2.07GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe .

Screen Reader
no

VM
67%

Extensions (1)

Extension
Author (truncated)
Version

open-in-browser
tec
1.1.0

0907h.vip

Duplicate of #47188


Girlscript Summer of Code Introduction/Tracking

👋 Hi @subhadeeproy3902,
I am Prince,web developer Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.
As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you :octocat:

[x] #4
[x] #5
[x] #6
[x] #7
[x] #8

Go ahead @Princegupta101 except issue #5


MM-47238 Add MM_BOARDS_DEV_SERVER_URL environment variable for MPA

This PR is based on https://github.com/mattermost/mattermost-webapp/pull/11355. Changes specific to it are here: https://github.com/mattermost/mattermost-webapp/compare/MM-46981_production-mpa...MM-47238_boards-dev-server-url
This makes it so that people who develop MM on a URL other than http://localhost can redefine the URL, port, and protocol that the Boards Webpack dev server runs on for MPA development. Without it sets, it still defaults to running the dev server on http://localhost:9006
Ticket Link
https://mattermost.atlassian.net/browse/MM-47238
Related Pull Requests
https://github.com/mattermost/mattermost-webapp/pull/11355
https://github.com/mattermost/focalboard/pull/4026
https://github.com/mattermost/mattermost-server/pull/21435
Release Note
NONE

You can change the PR base to that branch, and then change it back to master once that PR is merged. That keeps the diff only to the related commit.
Anyways, looks good!


Fix rails cops enabled in the documentation

In the documentation, rails cops are disabled by default.
The cause is here https://github.com/bbatsov/rubocop/blob/master/config/disabled.yml#L5-L6

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

Guess this is an OK solution for now, but if we ever have any Rails cops that are not enabled by default it might become problematic.

if we ever have any Rails cops that are not enabled by default it might become problematic.

It works without any problems. Rails/SaveBang is disabled by default, and it is disabled in the documentation.
https://github.com/bbatsov/rubocop/blob/master/manual/cops_rails.md#railssavebang


Adding work section

Added Work Section and About Me Section in My Portfolio

I used grid and grid items to align my cards for the work section
I also used ul and li for categories in both the sections
Followed Microverse guidelines for fixing Linters errors

Thank you so much for the review :)


Build instructions in README don’t work

Instructions in the ghc-9.0 branch are out of date. They say:
cabal v2-build -w ghc-8.10.1
cabal v2-test -w ghc-8.10.1 all

But I had to do:
ghcup set ghc <IP_ADDRESS>01227
ghcup set cabal <IP_ADDRESS>-rc4
cabal build --allow-newer="Cabal"

The --allow-newer is needed because of ghc-paths, see https://github.com/simonmar/ghc-paths/pull/24

Fixed by fcf9a04224fed910d01cf6f4d9c2d1bdc7c085af


Sync stage with 1.2.x branch

Purpose

This PR syncs the stage branch with the 1.2.x branch and bumps the version to 1.2.1

Codecov Report

Merging #22408 into stage will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            stage   #22408   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 216be7f...216be7f. Read the comment docs.


sched: remove all spin_lock_irqsave(NULL)

Summary
sched: remove all spin_lock_irqsave(NULL)
Impact
sched
Testing
ci
qemu-armv8a:nsh_smp

(this comment is not specific to this PR)
do you have a plan to document which lock protects what? it isn't so obvious to me.

which lock protects wha

We replace a big lock with smaller locks. Generally, it's easy to find which lock protects what through file searching.

which lock protects wha

We replace a big lock with smaller locks. Generally, it's easy to find which lock protects what through file searching.

sometimes it's obvious. sometimes not.


[librdkafka] Snappy compression option

librdkafka is not being compiled with the "snappy" option. I've made some changes here to fix it.
CONTROL.txt
portfile.cmake.txt

Hi @rotrida, can you creat a pull request to commit your changes?
Thanks!

Done. Thanks!


App crashed when open on iOS simulator

Xcode 6.1.1. Console output:
IOError: invalid Python installation: unable to open /Users/....../lib/python2.7/config/Makefile (No such file or directory)

did you copy Python-iOS-support under app_packages

@skyline75489  can this be closed?


⚠ Bofrost.at has degraded performance

In 885ede1, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1138 ms

Resolved: Bofrost.at performance has improved in f5fb071.


First time using your library, example did not work for me

Hello, I am trying to use your library but so far I didn't get the data from my test csv file and need help.
Below is my current code, for a single component that uses your library as a button, which, when clicked, supposed to trigger the use of csvtojson.
const csv = require('csvtojson');
const csvFilePath = '../test.csv';
import React, { Component } from 'react'
import { Button } from 'reactstrap';
// import fs from 'fs';

const getCsv = () => {
        csv()
        .fromFile(csvFilePath)
        .then((jsonObj)=>{
            console.log(jsonObj);
            return jsonObj

        })
    }

class Csvjson extends Component {

    render() {
      return (
        <Button onClick={getCsv}>Get CSV</Button>

      )
    }
  }

export default Csvjson

It is giving errors:
Error: Cannot find module 'fs'
But it's not clear how this occurred when I am not calling fs.  So I left fs there commented but even when I uncomment it, it still gives same  error.

fs module is supported by nodejs, not raw JS