Add new + working splash page, css, and js functionality

Final commit for the splash page and (unfilled) other pages. Will be creating a new branch to further work on content for the other four pages + image sizing issues.

I guess the name for a83d7c5 should be More DRY, more JS... oops.


Base home org or xyz URL path not accessible via REST

-bash-4.1$ curl -c cjar -b cjar -k -H "Content-Type: application/json" -X  GET https://$BMC_IP/org/
{
  "data": {
    "description": "Trying to access Blocked URL"
  },
  "message": "404 Not Found",
  "status": "error"
}

-bash-4.1$ curl -c cjar -b cjar -k -H "Content-Type: application/json" -X  GET https://$BMC_IP/org/open_power/
{
  "data": [
    "/org/open_power/control",
    "/org/open_power/sensors"
  ],
  "message": "200 OK",
  "status": "ok"
}

Nagaraju Goruganti [10:44]
{
"urls": [
"/org/open_power/*",
"/com/ibm/*",
"/xyz/openbmc_project/*",
"/enumerate",
"/list",
"/login",
"/logout",
"/subscribe",
"/upload/image",
"/download/dump/*"
]
}

are whitelisted.
Reference : https://github.com/openbmc/openbmc/issues/2378

https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/11608/


Support redefined password authentication

@xuxiaowei-com-cn Thank you for signing the Contributor License Agreement!

This function is used to customize the password of the authentication client

It is useful to prevent http requests from being intercepted and improve security

@xuxiaowei-com-cn This project has reached it's end-of-life. Please see latest announcement.


fix(versions): update Activiti/activiti-cloud-audit versions into master

UpdateBot pushed helm dependency: common to: 1.1.17

UpdateBot commands:
updatebot push-version --kind helm common 1.1.17


Remind us that tokens may only be used to define a run number

@MarkIannucci : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @MarkIannucci!
#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Introduce ExperimentalFeatures

These allow the parser to optionally support new Swift features that haven't yet been enabled by default.

https://github.com/apple/swift/pull/67826
@swift-ci please test

https://github.com/apple/swift/pull/67826
@swift-ci please test Windows

https://github.com/apple/swift/pull/67826
@swift-ci please test macOS


Overhaul benchmark control protos and tests themselves

Also start using message proto from end2end test so that we can then more easily integrate security, etc., which is already accounted for in those protos.
Renamed RunTest to RunClient for parallelism and clarity
Side issue: straightened out sign conversion issues on low-level network benchmark.
Dynamic generation of server port will come in a different PR: the proto already supports a port field in the response from RunServer.

I put DNM on this because I'm observing a strange behavior: on my Mac, this has no perf impact but on my Linux desktop this hurts median latency by a factor of 2x. Makes no sense to me.

@sreecha, please also take a look.

Also, don't forget to delete the old qpstest.proto file in this PR.

ping?

Please let me know once this is ready of final review pass.

Sure, I'll make some more cleanup changes and let you know when this is ready for a final review. The main hurdle now is copying in the TLS and getting that working.

I will write some security tests in the morning and then pull the DNM since I think the code will be greatly more usable once that piece is in.

This is ready to review. I would appreciate eyes from @ctiller (if possible) and @yang-g (particularly on commit f8603ad) . @sreecha - you may want to see what's up with this.

Reviewed 3 of 25 files at r1, 3 of 30 files at r4, 1 of 10 files at r5, 4 of 31 files at r6, 9 of 18 files at r8, 3 of 6 files at r9, 1 of 1 files at r10.
Review status: 24 of 43 files reviewed at latest revision, 25 unresolved discussions.

test/cpp/qps/client.h, line 176 [r10] (raw file):
We should still be able to do a switch here, right?
switch (load.load_case()) {
  case LoadParams::kClosedLoop: // ...
  // ...
}

test/cpp/qps/qps_test_with_poll.cc, line 1 [r10] (raw file):
Can we keep this? It's actually caught bugs in the past for me.

test/cpp/qps/secure_sync_unary_ping_pong_test.cc, line 86 [r10] (raw file):
We shouldn't need signal() anymore

test/cpp/qps/server.h, line 89 [r10] (raw file):
Simple accessors should be lowercase

test/cpp/qps/server.h, line 90 [r10] (raw file):
Same here

test/cpp/qps/single_run_localhost.sh, line 45 [r10] (raw file):
nice

Comments from the review on Reviewable.io

@ctiller - not sure how to respond on reviewable (need to learn this), but question about signal . I think I should keep it in qps_worker since that SIGINT is there to consider the case of the server that runs from the qps_worker. Am I wrong about this?

I think I was looking at an outdated file... I saw a SIGPIPE in
secure_sync_blah_blah
On Wed, Nov 4, 2015 at 2:53 PM Vijay Pai<EMAIL_ADDRESS>wrote:

@ctiller https://github.com/ctiller - not sure how to respond on
reviewable (need to learn this), but question about signal . I think I
should keep it in qps_worker since that SIGINT is there to consider the
case of the server that runs from the qps_worker. Am I wrong about this?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/3905#issuecomment-153895428.

There definitely were SIGPIPE in *test , and I took those out now.
I think that the SIGINT is functional, though, so let's keep it.

@jtattermusch - I think that I have addressed Craig and Yang's issues. Can you review?

The changes to .proto files LGTM.  Do I need to review the C++ code as well or has it been covered by Craig and Yang?
The Jenkins issues on windows are https://github.com/grpc/grpc/issues/4050 and another unrelated issue I'm looking into.

@ctiller and @yang-g , are you ok with the C++ files in this PR ?

LGTM

LGTM
On Thu, Nov 5, 2015, 12:17 AM Yang Gao<EMAIL_ADDRESS>wrote:

LGTM
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/3905#issuecomment-153984393.

Also: why no auto response with that.
On Thu, Nov 5, 2015, 7:07 AM Craig Tiller<EMAIL_ADDRESS>wrote:

LGTM
On Thu, Nov 5, 2015, 12:17 AM Yang Gao<EMAIL_ADDRESS>wrote:

LGTM
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/3905#issuecomment-153984393.


dotnet new install Auth0.Templates does not install all templates

As per you documentation, I have executed the following command:
dotnet new install Auth0.Templates
This is a screenshot:

Your documentation suggests that the following .Net templates will be available:

Auth0 MVC Application
Auth0 Web API Application
Auth0 Blazor Web App
Auth0 Blazor Server Application
Auth0 Blazor WebAssembly Application
Auth0 MAUI Application

This is clearly not the case

Hi @DermotMurphy,
Thank you for bringing up this issue. Actually, the current published package contains the 4 templates shown in your screenshot.
Currently, I'm experimenting with a trunk-based development approach to allow PRs from forks. So, the current main branch is the development branch that will end up in version 2.2 of the NuGet package, which I hope to publish soon.
I understand that this way the docs and the code in the main branch do not match the current package published on NuGet, and it may cause confusion. Sorry for that. I hope to find a better solution for the future releases.


Improved Readme.md

i added more info to the readme
i added a logo, release icon, license icon and also improved note.
Improved note preview:

ok, I will publish it to the devforums soon™ [no specified release date and I didn't focus on the module because I am focusing on other stuff]


feat: add pm-g generator

🔗 Linked issue
(https://github.com/unjs/automd/issues/50)
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Add a generator like pm-install but for global package like CLI
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

The generator works, I just don't know why it's not recognized in the docs when everywhere else (tests, code, etc...) it works.
Don't hesitate to send me any feedback!

Thanks for PR. But i guess you can make it an arg for pm-install global

Yes indeed, I thought about it, but I thought that for a global installation, all the arguments available with pm-install are not necessarily interesting.


add a feedback section Feat:

Describe the feature
we can add a feedback section such that user can give feedback
Add ScreenShots

we can add this type of page to make it visually appeling
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

please assign me this

I want to resolve the issue, kindly assign me the task


Colored pitch accent can't determine PA from AJTJapanese field

In the prerelease version, when the PAOverride and PAPositions fields are both empty, JPMN should be able to figure out the pitch accent from the AJTJapanese field, but this functionality is currently broken.

Fixed


Flaky tests and/or goroutine leaks

Your environment.

Version: 3af728a6c0f7d27c1fc2278a85e60fffed72a09a

What did you do?
I run go test -v -count=5 ./... on the master-branch.
What did you expect?
I expected all tests to pass all the time.
What happened?
I frequently see tests fail with either Unexpected routines on test startup or goroutine is leaked.

At least the test TestAssociation_Shutdown appears to be failing regularily:
https://github.com/pion/sctp/actions/runs/5021866113/jobs/9004672764

The above log has expired. When I ran locally, I saw this error at high occurrance:
% go test -v -count 1 -race ./...
 :

 === RUN   TestAssocStressDuplex
    util.go:44: Unexpected routines on test startup:
        goroutine 10534 [chan send, 1 minutes]:
        github.com/pion/sctp.TestAssocReset.func2.2()
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2225 +0xdc
        created by github.com/pion/sctp.TestAssocReset.func2 in goroutine 10344
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2221 +0xad4

        goroutine 14423 [chan send]:
        github.com/pion/sctp.TestAssocReset.func2.2()
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2225 +0xdc
        created by github.com/pion/sctp.TestAssocReset.func2 in goroutine 14437
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2221 +0xad4

        goroutine 2602 [chan send, 2 minutes]:
        github.com/pion/sctp.TestAssocReset.func2.2()
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2225 +0xdc
        created by github.com/pion/sctp.TestAssocReset.func2 in goroutine 2629
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2221 +0xad4

        goroutine 6555 [chan send, 1 minutes]:
        github.com/pion/sctp.TestAssocReset.func2.2()
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2225 +0xdc
        created by github.com/pion/sctp.TestAssocReset.func2 in goroutine 6569
        	/Users/ytakeda/Projects/pion/bugfix/sctp-270/sctp/association_test.go:2221 +0xad4
--- FAIL: TestAssocStressDuplex (10.20s)

What failed was not TestAssociation_Shutdown but the cause was Unexpected routines on test startup as the original report. I'd assume I am seeing the same one.  I will try to fix the goroutine leak from TestAssocReset.

Now I see the ci test error:
TestAssociation_Shutdown (2s)
      association_test.go:2604:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2604
          	            				/opt/hostedtoolcache/go/1.19.13/x64/src/runtime/asm_amd64.s:1594
          	Error:      	Received unexpected error:
          	            	association closed before connecting
          	Test:       	TestAssociation_Shutdown
      association_test.go:2622:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2622
          	            				/home/runner/work/sctp/sctp/association_test.go:2643
          	Error:      	timed out waiting for a1
          	Test:       	TestAssociation_Shutdown
      association_test.go:2628:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2628
          	            				/home/runner/work/sctp/sctp/association_test.go:2643
          	Error:      	timed out waiting for a2
          	Test:       	TestAssociation_Shutdown
      association_test.go:2640:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2640
          	            				/opt/hostedtoolcache/go/1.19.13/x64/src/runtime/panic.go:890
          	            				/opt/hostedtoolcache/go/1.19.13/x64/src/runtime/panic.go:260
          	            				/opt/hostedtoolcache/go/1.19.13/x64/src/runtime/signal_unix.go:[83](https://github.com/pion/sctp/actions/runs/7353192438/job/20018854151?pr=292#step:9:135)9
          	            				/home/runner/work/sctp/sctp/association.go:1380
          	            				/home/runner/work/sctp/sctp/association_test.go:2645
          	Error:      	Not equal:
          	            	expected: 2
          	            	actual  : 6
          	Test:       	TestAssociation_Shutdown
          	Messages:   	goroutine is leaked
  panic: runtime error: invalid memory address or nil pointer dereference [recovered]
  	panic: runtime error: invalid memory address or nil pointer dereference
  [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x6c430d]

  goroutine 2616 [running]:
  testing.tRunner.func1.2({0x774b40, 0x9cb[86](https://github.com/pion/sctp/actions/runs/7353192438/job/20018854151?pr=292#step:9:138)0})
  	/opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1396 +0x372
  testing.tRunner.func1()
  	/opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1399 +0x5f0
  panic({0x774b40, 0x9cb860})
  	/opt/hostedtoolcache/go/1.19.13/x64/src/runtime/panic.go:[89](https://github.com/pion/sctp/actions/runs/7353192438/job/20018854151?pr=292#step:9:141)0 +0x262
  github.com/pion/sctp.(*Association).OpenStream(0x0, 0x0?, 0x0?)
  	/home/runner/work/sctp/sctp/association.go:1380 +0x6d
  github.com/pion/sctp.TestAssociation_Shutdown(0xc0005e2680)
  	/home/runner/work/sctp/sctp/association_test.go:2645 +0xd9
  testing.tRunner(0xc0005e2680, 0x7e6038)
  	/opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:1446 +0x217
  created by testing.(*T).Run
  	/opt/hostedtoolcache/go/1.19.13/x64/src/testing/testing.go:14[93](https://github.com/pion/sctp/actions/runs/7353192438/job/20018854151?pr=292#step:9:145) +0x75e
  exit status 2

From a quick glance, the root cause of this appears to be a panic.  (will look into it closer)

I have been trying different things and I finally got some clue why TestAssociation_Shutdown fails.  Write operation on a net.Conn (a connected UDP using loopback interface) fails with some permission error:
❌ TestAssociation_Shutdown (2s)
  sctp DEBUG: 08:31:53.073542 association.go:1002: [0xc0009fa000] state change: 'Closed' => 'CookieWait'
  sctp DEBUG: 08:31:53.073558 association.go:1002: [0xc000248000] state change: 'Closed' => 'CookieWait'
  sctp DEBUG: 08:31:53.073574 association.go:377: [0xc0009fa000] sending INIT
  sctp DEBUG: 08:31:53.073589 association.go:377: [0xc000248000] sending INIT
  sctp DEBUG: 08:31:53.073620 association.go:538: [0xc0009fa000] readLoop entered
  sctp DEBUG: 08:31:53.073640 association.go:564: [0xc000248000] writeLoop entered
  sctp DEBUG: 08:31:53.073658 association.go:564: [0xc0009fa000] writeLoop entered
  sctp DEBUG: 08:31:53.073656 association.go:538: [0xc000248000] readLoop entered
  sctp WARNING: 2023/12/30 08:31:53 [0xc0009fa000] failed to write packets on netConn: write udp <IP_ADDRESS>:41866-><IP_ADDRESS>:58766: write: operation not permitted
  sctp DEBUG: 08:31:53.073939 association.go:577: [0xc0009fa000] writeLoop ended
  sctp DEBUG: 08:31:53.074058 association.go:1002: [0xc0009fa000] state change: 'CookieWait' => 'Closed'
  sctp DEBUG: 08:31:53.073963 association.go:1066: [0xc0009fa000] chunkInit received in state 'CookieWait'
  sctp DEBUG: 08:31:53.074192 association.go:1099: [0xc0009fa000] use ForwardTSN (on init)
  sctp DEBUG: 08:31:53.074[163](https://github.com/pion/sctp/actions/runs/7362909083/job/20041824067?pr=292#step:9:232) association.go:600: [0xc0009fa000] writeLoop exited
  sctp ERROR: 2023/12/30 08:31:55 [0xc0009fa000] client handshake canceled: state=Closed
  sctp ERROR: 2023/12/30 08:31:55 [0xc000248000] client handshake canceled: state=CookieWait
      association_test.go:2686:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2686
          	Error:      	Received unexpected error:
          	            	context deadline exceeded
          	Test:       	TestAssociation_Shutdown
      association_test.go:2682:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2682
          	            				/opt/hostedtoolcache/go/1.20.12/x64/src/runtime/panic.go:540
          	            				/opt/hostedtoolcache/go/1.20.12/x64/src/testing/testing.go:980
          	            				/home/runner/work/sctp/sctp/association_test.go:2686
          	Error:      	Not equal:
          	            	expected: 2
          	            	actual  : 7
          	Test:       	TestAssociation_Shutdown
          	Messages:   	goroutine is leaked

Does any one have any idea what causes this logs message? sctp WARNING: 2023/12/30 08:31:53 [0xc0009fa000] failed to write packets on netConn: write udp <IP_ADDRESS>:41866-><IP_ADDRESS>:58766: write: operation not permitted
@stv0g @Sean-Der

This might be related: https://github.com/golang/go/issues/63322

FYI: goroutine is leaked was also caused by false-positives by how goroutine leak was detected. I have improved it in the PR #292.

I have tried quick-go's workaround but now it causes a connection refuse error on the reader side which really does not make any sense.
At this point, I am leaning toward not using the mutually connected UDPConn pair in the test, and use a mocked net.Conn, or vnet instead.  pion/sctp does not actually use the mutually connected UDPConn anyway.
❌ TestAssociation_Shutdown (1s)
  sctp DEBUG: 07:03:37.660217 association.go:334: [0xc0009714a0] retryFirstWriteError=true
  sctp DEBUG: 07:03:37.660316 association.go:1030: [0xc0009714a0] state change: 'Closed' => 'CookieWait'
  sctp DEBUG: 07:03:37.660331 association.go:334: [0xc000938960] retryFirstWriteError=true
  sctp DEBUG: 07:03:37.660415 association.go:1030: [0xc000938960] state change: 'Closed' => 'CookieWait'
  sctp DEBUG: 07:03:37.660431 association.go:545: [0xc000938960] readLoop entered
  sctp DEBUG: 07:03:37.660345 association.go:545: [0xc0009714a0] readLoop entered
  sctp DEBUG: 07:03:37.660453 association.go:571: [0xc000938960] writeLoop entered
  sctp DEBUG: 07:03:37.660347 association.go:384: [0xc0009714a0] sending INIT
  sctp DEBUG: 07:03:37.660439 association.go:384: [0xc000938960] sending INIT
  sctp DEBUG: 07:03:37.660361 association.go:571: [0xc0009714a0] writeLoop entered
  sctp DEBUG: 07:03:37.660614 association.go:624: [0xc000938960] initial write succeeded
  sctp DEBUG: 07:03:37.660636 association.go:624: [0xc0009714a0] initial write succeeded
  sctp DEBUG: 07:03:37.660700 association.go:567: [0xc0009714a0] readLoop exited read udp <IP_ADDRESS>:44500-><IP_ADDRESS>:39991: read: connection refused
  sctp DEBUG: 07:03:37.660741 association.go:537: [0xc0009714a0] association closed
  sctp DEBUG: 07:03:37.660761 association.go:538: [0xc0009714a0] stats nDATAs (in) : 0
  sctp DEBUG: 07:03:37.660779 association.go:539: [0xc0009714a0] stats nSACKs (in) : 0
  sctp DEBUG: 07:03:37.660795 association.go:540: [0xc0009714a0] stats nT3Timeouts : 0
  sctp DEBUG: 07:03:37.660809 association.go:541: [0xc0009714a0] stats nAckTimeouts: 0
  sctp DEBUG: 07:03:37.660830 association.go:542: [0xc0009714a0] stats nFastRetrans: 0
  sctp DEBUG: 07:03:37.660856 association.go:1030: [0xc0009714a0] state change: 'CookieWait' => 'Closed'
  sctp DEBUG: 07:03:37.660896 association.go:607: [0xc0009714a0] writeLoop exited
  sctp ERROR: 2023/12/31 07:03:37 [0xc000938960] client handshake canceled: state=CookieWait
      association_test.go:2675:
          	Error Trace:	/home/runner/work/sctp/sctp/association_test.go:2675
          	Error:      	Received unexpected error:
          	            	association closed before connecting
          	Test:       	TestAssociation_Shutdown
      association_test.go:2111: leaked 4 goroutines

At this point, I am leaning toward not using the mutually connected UDPConn pair in the test ...

Now I am using a mock'd connection using "dumbConn2". Now, all the flaky tests are stable and ready for review.


Using Achordion with custom keys that send a different key tap when held

I've been giving Achordion a shot and so far I am really liking it. In feel it's quite similar to the custom solution that I had made previously, but it was much easier to deploy and customize. I may have missed something, but one issue I encountered was with the use of custom key codes that send a different tap event when held. On my Planck I mainly use these to send : when holding . or to send a number when holding the respective top row key longer than the tapping term. These key codes follow the following pattern to override the hold event (in process_record_user):
case Q_KEY:
    if (record->tap.count && record->event.pressed) {
        // normal processing when tapped
        return true;
    } else if (record->event.pressed) {
        // send a different key code when held
        tap_code(KC_1);
        return false;
    }
    return true;

When I let Achordion handle these key codes the held event is not sent. I was under the impression, that Achordion would process the key's hold event "normally" after a certain timeout. So currently, the only way for me to get these keys to work is to define them as exceptions in achordion_timeout and set their timeout to 0. Is there any way to get the desired behaviour of these keys (sending the hold event, i.e. an alternative key tap after the tapping term expired) while also retaining the benefits of Achordion with these keys?
I hope that this issue is not just relevant for my specific use case and that other users of Achordion can also benefit from an answer to this issue. At any rate, thanks for sharing this awesome (and very well documented) userspace library!
Best,
jweickm

Thanks for the report and kind words! You are right, while Achordion passes along tap events, it isn't passing on hold events as it should.
I want to make sure I understand the use case you describe. Is this essentially a tap dance-like effect to do two different things on tap vs. long press? I read something similar in filterpaper's repo: tap-hold macros. For this "tap-hold dance" use, I would think the tap-hold decision would preferably be based only on whether the key is held longer than the tapping term, without consideration about other key events while the key is down, and bypassing Achordion seems reasonable to me. But I don't have much experience with this use of a tap-hold key, so this may be naive. For these keys, is there something about the tap-hold decision that you would want to customize with Achordion?
In any case, it's an oversight that Achordion doesn't pass along the hold events. I'll look into fixing that.

Hi Pascal,
thank you for your quick reply. I am not actually using the QMK tap dance feature but my custom keycode is very similar in function. These custom keycodes override the hold event of LT() key macros to send a tap event of a different key. For example, when I hold the Q key it will tap KC_1 once after a short delay, allowing me to use the top row of my Planck as a number row without having to switch layers.
I just looked through the link you shared. It is indeed very similar.

For this "tap-hold dance" use, I would think the tap-hold decision would preferably be based only on whether the key is held longer than the tapping term, without consideration about other key events while the key is down, and bypassing Achordion seems reasonable to me.

Yes, that is the desired behaviour but bypassing Achordion entirely doesn't provide me with the benefits of preventing the accidental triggering of hold-events when rolling. What I like about your Achordion is, that I can type a little more lazily without triggering accidental hold events. When using home-row mods, LALT_T(KC_R) + LSFT_T(KC_S) becomes rs when typed in quick succession with the finger lingering on the first key. When doing the same with one of the custom keycodes where Achordion is bypassed, the result of lazily typing is 9u instead of yu for example (so the hold event is triggered for the first key).
It would be great if these keys could be handled in the same way as mod-taps (as they are essentially "layer taps").
Thanks for looking into that! Overall, still a truly awesome userspace library. I hope that it will be included in the main QMK distribution at some point!
Best,
jweickm

Hi Jakob! I just pushed commit https://github.com/getreuer/qmk-keymap/commit/87eb4e57623fee5eefda37951c31327a7234f7eb which should fix this issue, but please reopen if you notice anything further. Thanks again for reporting this!

Hi Pascal! Thanks for being so amazing to change the whole way that Achordion handles held events to allow for a broader range of custom keycodes to be used with it! Will try it out asap.

You're welcome =) Thanks for helping make Achordion better!

Just wanted to check in again to report that it has been working just as expected and the feeling of Achordion is really great! Especially on Colemak with a lot of rolls, I feel that I can type much faster and less carefully now! Thanks again for sharing and updating your userspace libraries! =)


Updated validations.py python script.

…ong in validation.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

CLA is not issued yet


Is there any way to see what watchtower is doing? E.g. a Logfile?

Looks like a very good idea - however I have zero information about if watchtower is doing something on my docker host and if it was done successfully. How to get logs out of watchtower? Any docs about this?

Just take a look onto the console output.
docker logs your_watchtower_container
You can also set --debug as mentioned in the README.md for more detailed information.

The console output should give enough information. I'll close the issue, feel free to open a new one if you have any further questions or problems.


Sample file "CyTOF_ClusterCellTypes_Panel3.xlsx"?

Is the file "CyTOF_ClusterCellTypes_Panel3.xlsx" available as a sample input file (i.e. one mentioned in your sample code)?

Hi,
Attached is the sample excel table.
Thanks for your interest.
Best wishes,
Masato

From: Christopher Bottoms @.>
Sent: Monday, May 23, 2022 1:23 PM
To: casanova-lab/iMUBAC @.>
Cc: Subscribed @.***>
Subject: [casanova-lab/iMUBAC] Sample file "CyTOF_ClusterCellTypes_Panel3.xlsx"? (Issue #13)
Caution: External email
Is the file "CyTOF_ClusterCellTypes_Panel3.xlsx" available as a sample input file (i.e. one mentioned in your sample code)?
—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_casanova-2Dlab_iMUBAC_issues_13&d=DwMCaQ&c=JeTkUgVztGMmhKYjxsy2rfoWYibK1YmxXez1G3oNStg&r=A4m3pu6CGBcaZg_kv2aoNfSAIrd7GqjXWxbxxd25Vdw&m=jzak8SuU0xMNk20Ii__F5fYpGiqlofYR2CD-_-u405MGhV8962RWimfqXZ0AtsUa&s=Kf70icezcj5KgHychKTZxBlGN0A0XXniO2NRllKUYEc&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AP5USTUE5AXESTBXMYG5FV3VLO5JFANCNFSM5WWRLLZA&d=DwMCaQ&c=JeTkUgVztGMmhKYjxsy2rfoWYibK1YmxXez1G3oNStg&r=A4m3pu6CGBcaZg_kv2aoNfSAIrd7GqjXWxbxxd25Vdw&m=jzak8SuU0xMNk20Ii__F5fYpGiqlofYR2CD-_-u405MGhV8962RWimfqXZ0AtsUa&s=BXj_36GDJudalaPPJeEErRQ9oJMuAFPTohg_X_PmJ4E&e=.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


process.stdin

Would be nice to support this in Node. e.g. taking an PNG image input, modifying it with WebGL/Canvas2D APIs, and then writing it to process.stdout.

related: https://github.com/dominictarr/electro/blob/master/index.js#L50-L76

nice :+1:


build issue with boot >=1.70

                 from /home/ilejn/projects/.../HttpServer.cpp:1:
/home/ilejn/projects/.../3rdparty/crow/include/crow/socket_adaptors.h: In member function ‘boost::asio::io_service& crow::SocketAdaptor::get_io_service()’:
/home/ilejn/projects/.../3rdparty/crow/include/crow/socket_adaptors.h:22:28: error: ‘boost::asio::ip::tcp::socket’ {aka ‘class boost::asio::basic_stream_socket<boost::asio::ip::tcp>’} has no member named ‘get_io_service’
   22 |             return socket_.get_io_service();

There are already couple of issues in this project with boost lib version. Also couple of pull request - you can choose one of them ;) On my fork those changes are merged, so feel free to download updated version.

Thanks,
no luck in making my own PR ;(

https://github.com/ipkn/crow/pull/343


Refactor project

So I've been looking at this repository for a while now, and I cannot understand one bit of any of this.
Why is there minified files in the src directory?
Why is there minified javascript in the index.html file?
No dist folder for the minified shit?

Working on it. I want there to be a single minified index file (to reduce network requests), but I haven't found a good packager/config that can do it.
The four lines in the index file represent substitutions for

Respectively. Hope that helps in the meantime.

please mind your manners  @SkoshRG

@alcor I would recommend using something like HTML5Boilerplate or Googles Web Starter Kit for web projects, they speed up development and keep everything neat well structured. They are very easy to setup too.
@p3k Yes, my bad

@SkoshRG
I for one, like Paul Irish, am against dist folders for "minified shit"... there is a releases feature on gitlab/github. They increase git size dramatically, and make it a real pain to build in dev, as you can't ignore them easily.
This is a very wierd project with extreme requirements, I would not blame you for hand coding a build process.


Enable video recording and upload on failure

This updates the E2E test workflow to record video of the cypress tests. The videos and screenshots for any failed test cases are uploaded as build artifacts. There will be an artifact called cypress-artifacts-node<version> for each workflow job where cypress tests failed.
Here's an example workflow run where I made the learn_spec.js fail: https://github.com/rcowsill/NodeGoat/runs/1987578217
Note that this currently uploads videos for every spec rather than just the failed ones. It should be possible to exclude the videos for successful specs, but the whole set is <5MB so this is ok for now. Fixed: see below

Converted to draft as I have a plan for how to only upload videos for failed specs. See:
https://github.com/rcowsill/NodeGoat/tree/test/error-videos-only
Also I forgot to add the videos folder to .gitignore. Once those changes are done I'll force-push this PR branch.

Landing it.


Error opening PRs in Github web editor

When I try to open a PR in the Github web editor (by pressing .), I get an error message:
Unable to open '....'

Further investigation leads me to believe that the issue might be caused by the Github Repositories extension. Opening the output panel for it, I see this message:
[2021-09-08 21:11:25:777] Failed to get repository info for 'Un-index/vscode'
GraphqlResponseError: Request failed due to following response errors:
 - Could not resolve to a PullRequest with the number of 132524.

The error is for a PR I randomly picked from the vscode repo: https://github.com/microsoft/vscode/pull/132524
The issue is reproducible for different PRs from different repos. The only requirement seems to be that the PR is coming from a different fork, quite common when working on open source projects.
Although I'm not completely certain, I believe the issue was introduced with the last update this month. It worked last month.

This should now be resolved -- please let me know if you are still seeing issues.


Matcher ->toBeAn() as a copy of ->toBeA()

Is it possible to implement matcher ->toBeAn() as a copy of ->toBeA() in the same way as we have ->toContainKey() and ->toContainKeys()?
Just for situations like:
expect($some)->toBeAn('int');
expect($some)->toBeAn('array');

Grammar nazi doesn't let me sleep well.

Afaik it's already the case: https://github.com/crysalead/kahlan/blob/master/src/cli/Kahlan.php#L316-317 no ?

Yeap, that's it. So I was misinformed with static analysis of IDE.
Please, add required phpdoc line to src/Matcher.php .

Fixed in https://github.com/crysalead/kahlan/commit/2009cd65a5fc8b980bcb8ac136f11edaa5665eaa

Oooops, forgot to make a PR :sob:

Haha, didn't even notice.


latest commit version errors out on replies.

commit 387099e5f23ff10306a3fa7fbc85536640133656
I've verified that every setting is correctly set.
How can I produce debug logs?

It's impossible that this commit broke anything

Latest commit runs fine, please delete configuration files and try again

c:\Users<YouUserName\AppData\Local\IsolatedStorage\


create doesn't work when ssh session multiplexing is enabled

So when SSH config contains e.g. ControlMaster auto, ControlPath ..., ControlPersist yes so that when ssh command is run it spawns a process in the background which maintains the network connection and allows multiple sessions to be run over the same connection which improves performance as connection is only established once.
With that configuration docker-machine runs an ssh command and appears to hang when the command finishes:
$ docker-machine --debug create --driver=digitalocean ...
Creating SSH key...
Creating Digital Ocean droplet...
Created droplet ID ..., IP address x.x.x.x
Getting to WaitForSSH function...
Testing TCP connection to: x.x.x.x:22
...
Using SSH client type: external
About to run SSH command:
exit 0
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /.../.docker/machine/machines/test/id_rsa -p 22<EMAIL_ADDRESS>exit 0] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}

hangs here.
I've confirmed that if I close the master with ssh -S /path/to/socket -O exit none, docker-machine continues to run, at least up until the next ssh command is run (which establishes a new master and docker-machine hangs again).
Looks like this is because while the the ssh master process is run in the background, it leaves fd 2 (stderr) open for outputting error messages.  I'll have a look if there's a way to make ssh close stderr, but do you think there's something that can be done in docker-machine to handle that?

Looks like I have the same problem on Windows 7: docker-machine version 0.3.1 (40ee236)
on VirtualBox 4.3.18
docker-machine -D create --driver virtualbox dev2
STDERR:
Using SSH client type: external
About to run SSH command:
ip addr show dev eth1
&{D:\Program Files (x86)\Git\bin\ssh.exe [D:\Program Files (x86)\Git\bin\ssh.exe -o PasswordAuthentication=no -o IdentitiesOnly=yes -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i C:\Users\myf
ear\.docker\machine\machines\dev2\id_rsa -p 54361 docker@localhost ip addr show dev eth1] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <n
il> false [] [] [] [] <nil>}
SSH cmd err, output: <nil>: 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:60:0e:6a brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe60:e6a/64 scope link
       valid_lft forever preferred_lft forever

SSH returned: 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:60:0e:6a brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe60:e6a/64 scope link
       valid_lft forever preferred_lft forever

END SSH

The machine is up and running and I can ssh into it.
No certificates are generated. Regenerating with regenerate-certificates hangs at the same ssh command.
docker-machine env --shell cmd dev
open C:\Users\myfear.docker\machine\machines\dev\ca.pem: The system cannot find the file specified.

bug report against OpenSSH

@myfear you seem to be getting response from SSH, are you sure this is the same issue?

Would adding -o ControlMaster=no to the ssh options fix it?

@mdub if you mean if docker-machine used an option to disable multiplexing explicitly then yes (could even use -S none); however I'd actually be more interested in having docker-machine play well with multiplexing; I know it can be done (e.g. ansible uses multiplexing internally and also reads stderr from commands it runs), just not sure how yet :-)

@jitakirin after you pointed it out, I'm no longer sure. What would be your
suggestion?
Happens with both the mysysgit ssh client and the native go version.
On Jul 24, 2015 12:44 PM, "jitakirin"<EMAIL_ADDRESS>wrote:

@mdub https://github.com/mdub if you mean if docker-machine used an
option to disable multiplexing explicitly then yes (could even use -S none);
however I'd actually be more interested in having docker-machine play well
with multiplexing; I know it can be done (e.g. ansible uses multiplexing
internally and also reads stderr from commands it runs), just not sure how
yet :-)
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/1572#issuecomment-124471000.

docker-machine --debug --native-ssh create -d virtualbox default
and then
docker-machine --native-ssh start default
has worked now twice in a row :)

the disk image still seems to be inconsistently mounted, though that's a different issue I guess

+1

+1
Mine was hanging on 'About to run SSH command', I use these options in ~/.ssh/config
host *
  Protocol 2
  Compression yes
  CompressionLevel 6
  ServerAliveInterval 15
  ServerAliveCountMax 3
  ControlPersist 1h
  ControlMaster auto
  ControlPath ~/.ssh/master-%r@%h:%p
  AddressFamily inet

This should work fine now due to the new added SSH options.


Top filling tanks

Would it be possible to implement top filling of the tanks? with a discharge line separate from the distribution line?
If i can help for any thing, i'm available.

Have you seen the FAQ on the EPANET docs on how to implement top filling of a tank?
https://epanet22.readthedocs.io/en/latest/13_questions.html#fig-tank-inlet-above-water

How do I model a tank inlet that discharges above the water surface?
Use the configuration shown below (Fig. 13.1):

Fig. 13.1 Example of Tank Inlet Discharging above Water Surface.
The tank’s inlet consists of a Pressure Sustaining Valve followed by a short length of large diameter pipe. The pressure setting of the PSV should be 0, and the elevation of its end nodes should equal the elevation at which the true pipe connects to the tank. Use a Check Valve on the tank’s outlet line to prevent reverse flow through it.

I've used the above arrangement for UK networks and it's worked as expected, though maybe its not the most "clean" to set up. If we were to add support for this natively, I'd suggest it should be done in the library first before the GUI.


WIP autoencoder

Thus PR adds an autoencoder to muffnn. The autoencoder supports a variety of metrics and is compatible with the scikit-learn transform interface.
I additionally

refactored the MLP classes into their own subpackage.
pinned conda to 4.0.5 to avoid conda bugs
upgraded TensorFlow to 0.11.0rc2

Closes #8

@mheilman See the code in this PR for my first pass. I am still shaking the bugs out, but the MSE metric only works great.

This is a conda bug. :(

@mheilman Thus PR is ready. Unfortunately it ballooned to ~1500 after I wrote all of the tests. :(
I suggest we do it in chunks:

The refactoring of the MLP and base classes and the Dockerfile.
The autoencoder class itself.
The autoencoder tests.

I am going to add a test for sparse inputs because why not. :)

sorry for the slow response on this. i'm at a conference, so i probably won't be able to take a close look until next week.

No worries! I am continuing to hack away on this in the mean time.

@mheilman I rewrote the tests to eliminate a several hundred lines of duplicate code and removed a bunch of tests that duplicated each other for the most part.

lemme know whenever you're ready for me to take another look

Yeah def. Will do this afternoon. Sorry for the delay.

oh, no rush!  i just wanted to be clear i was done looking for the time being

OK. This is fixed and ready for a second look @mheilman!

ah, i just remembered your comment about doing this in chunks.  gonna do a first pass on the whole thing since i'm mostly done.

@mheilman This is ready for another look!

hmmm... sorry i didn't think about this until now, but is there a check to make sure that indices aren't specified for both sigmoid and softmax, or for indices above the number of inputs?  input validation like that would be useful to help users avoid silly mistakes

The docstring still says "Note that dropout is not applied to the input layer", which isn't the case anymore.

Good call on index checking. I will move this into a separate routine.

@mheilman I have addressed these comments. Back to you!

only a couple minor comments.  thoughts?

OK @mheilman. I think we are really close now!

    __    ______________  ___
   / /   / ____/_  __/  |/  /
  / /   / / __  / / / /|_/ /
 / /___/ /_/ / / / / /  / /
/_____/\____/ /_/ /_/  /_/

(LGTM)

my only thought, which would be for another PR, is that it might be nice to have options for penalties on the hidden layer (a la this paper).


BSC bridge loading issue

Page keeps loading after clicking withdraw
See https://github.com/threefoldtech/tf_support/issues/408

tried to to open the BSC bridge
connect to wallet
it shows only  You're connected to an unsupported network.
it doesn't show or load any other option


Https listener not working in 2.1.0 as in 2.0.7

Hello,
I have been experiencing problems with the https listener since the upgrade to version 2.1.0.
Same result in Ubuntu 16.04 and Windows 7 (both 64 bits).
Steps:

Download emqtt distribution (stable - 2.0.7 and development - 2.1.0)
Change only the file etc/plugins/emq_dashboard.conf with the following content (disable http listener and enable https):

##--------------------------------------------------------------------
## Dashboard
##--------------------------------------------------------------------

## HTTP Listener
##dashboard.listener.http = 18083
##dashboard.listener.http.acceptors = 2
##dashboard.listener.http.max_clients = 512

## HTTPS Listener
dashboard.listener.https = 18084
dashboard.listener.https.acceptors = 2
dashboard.listener.https.max_clients = 512
## dashboard.listener.https.handshake_timeout = 15
dashboard.listener.https.certfile = etc/certs/cert.pem
dashboard.listener.https.keyfile = etc/certs/key.pem
dashboard.listener.https.cacertfile = etc/certs/cacert.pem
## dashboard.listener.https.verify = verify_peer
## dashboard.listener.https.fail_if_no_peer_cert = true

Start the broker
In version 2.0.7 it is possible to navigate to https://localhost:18084 and the dashboard works.
In version 2.1.0 when accesing https://localhost:18084 an error is shown by the web browser. When accesing http://localhost:18084 (no https) the dashboard is loaded correctly.

Is there any changes in the configuration of version 2.1.0 that I should be aware of?
Best regards,

Hi,
I have just tested this with version 2.1.1 in Ubuntu 16.04 and it seems fixed. I think this issue can be closed.
Thanks for the quick fix.
Best regards


Dismiss button doesn't work on Firefox

I have implemented a very simple example of the Cookie Consent bar, which is working great on Chrome and Safari. However, on Firefox the dismiss button (labelled "OK" in my case) doesn't actually dismiss the cookie bar. The page's cookie is added to the list of cookies just like it should, though (so the bar is also gone when the page is reloaded).
import 'cookieconsent';

window.addEventListener('load', () => {
    window.cookieconsent.initialise({
        'content': {
            'message': 'Some intelligent message about cookies.',
            'link': 'Learn more',
            'href': '/imprint',
            'dismiss': 'OK'
        }
    });
});

I'm using the Firefox 59.0 (which I believe is the newest version).

I can confirm the issue (i.e. I have the same problem).
The opt-in cookie banner works in Chrome but not in the latest Firefox version. The status is not saved in Firefox.

Is there any workaround or solution for this bug yet?

I've written a small (albeit hacky) workaround, but would prefer a "proper" solution:
// Workaround for Firefox and IE
const cookieBar    = document.getElementsByClassName('cc-window')[0];
const cookieButton = document.getElementsByClassName('cc-btn cc-dismiss')[0];
cookieButton.addEventListener('click', () => {
    cookieBar.style.display = 'none';
});

I've tested this with our latest release in Firefox 61 and can't replicate it.
If this issue persists, please respond + tag me.


Change default pagination dot spacing

How can I change the pagation dots spacing ?

It's mentioned in the pagination usage section:
https://github.com/archriss/react-native-snap-carousel/blob/master/doc/PAGINATION.md#note-on-dots-colors
Change the marginHorizantal field in the dotStyle from 8 to desired value

@l0h1t still not working.

I think the marginHorizontal is not on the dotStyle, but on the dotContainerStyle prop of Pagination. So you can give a style with an given value of marginHorizontal to overwrite the default value

@voisinhugo your suggestion works correctly!

Hi
This is not working for me, the space is always the same between the dots. Any ideas ?
@nguyenhoanglam @voisinhugo

Can confirm its not working...

Set the spacing betwene dots:
dotContainerStyle={{ marginHorizontal: 5 }}


Make healthy_panic_threshold configurable in config files

Right now, seems we can only configure the values from (https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_runtime#core) by runtime file-system files.
To make envoy circuit breaking/outlier detection behave a little more like hystrix from netflix, we should be able to configure the healthy_panic_threshold a little easier. Setting the value to "0" causes envoy to behave like hystrix. If we can configure this a little easier (i.e., in config file) that would make life easier.

I will fix this.

https://github.com/envoyproxy/data-plane-api/pull/465

I'm having trouble with this with the latest (by hash not tag) docker hub image.
Is this wrong syntax?
    - name: example
      connect_timeout_ms: 300
      type: static
      lb_type: round_robin
      common_lb_config:
        healthy_panic_threshold:
          value: 49
      hosts:
        - url: tcp://<IP_ADDRESS>:41091
        - url: tcp://<IP_ADDRESS>:51091

Getting
source/server/server.cc:71] error initializing configuration '/app/envoy.yaml': JSON at lines 0-0 does not conform to schema.
 Invalid schema: #
 Schema violation: additionalProperties
 Offending document key: #/common_lb_config

@josdotso  In case you had not resolved it try:
common_lb_config: { healthy_panic_threshold: { value: 35 } }
This worked for me

Exposure of the panic threshold in config is great. Is the ability to define fallback paths for open circuits still a TBD capability?

Can this value be 0 ex: common_lb_config: { healthy_panic_threshold: { value: 0 } } in envoy 1.9.1? When I set it to 0. I get "common_lb_config": {         "healthy_panic_threshold": {}        }       }, in config_dump


Add nodes required by MCUboot

Please update commit messages with the link to upstream PRs and open PR on sdk-nrf with manifest update

@michalek-no can you also add third commit: https://github.com/zephyrproject-rtos/zephyr/pull/68393/commits/580fb8479b9785ea51c655671ca0bc03ab061d72
this is also added in upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/68393


LUIS timeout

LUIS seems to be having some problems at the moment and I can't find a way for my Slack bot to handle it.  In the last few days LUIS has gone down several times and when this happens, I'm not getting any error messages, console logs or anything.  I can talk to the bot, it hears and sends the message to LUIS for recognition.  Slack shows the bot as 'typing' for a few seconds and then nothing else happens.
Is there a way to catch a timeout from the LUIS service and send a message to the user on Slack so they know something's wrong and don't keep talking to the bot?  I've tried looking through the source code and there does seem to be error handling in there. However, I can't see anything that will enable me to send a message to Slack telling anyone using it that the bot is temporarily a brainless zombiebot.

I'm assuming this is using Node.js? Are you not seeing a error logged to the console?

Yes I'm using Node.js and I wasn't seeing anything in the console.  After I posted I noticed that there had been a new release which mentions that LUISDialog 'on' had been stopped from eating exceptions (this might have been the cause) so I've installed that now.  However LUIS was back up and running at that point so I haven't managed to test it yet.

That was definitely an issue.  You should be at least getting an error now. There's not an easy way to report this to users right now but there are some changes coming that may help that.

I haven't been able to easily simulate LUIS going down on my development machine so I'll can't even tell you if I get messages. Until LUIS goes down I'll have to put the issue on the backburner.  That said, I'll keep a close watch on your release notes for any helpful changes.
Thanks for the info.

I can't mimic this either but there was definitely an issue with LuisDialog eating exceptions. Ive tested that it doesn't do that anymore.

I'm also having issues with timeout that look as though they are related to using LuisDialog, I'm going to create a quick library to see if accessing Luis via rest works better

@mattlanham I just use REST under the hood.  You can look at the code for LuisDialog.recognize() and see that it only goes through about 10 lines of code while calling the REST API.  The issues are on their side.  Are you at least getting an error?

I'm getting nothing, I have it deployed on Heroku, and it's just timing out after 30 seconds, but hitting luis directly seems to be fine - so not 100% sure what's going wrong.
I will have a look at the code and see if I can add some additional debugging console logs to see if I can narrow done where it's getting to @Stevenic

thanks much

@Stevenic Is there a function to reset the session in node?

So, I think i've narrowed my issue down to not calling session.endDialog(); at the end of every function invoked by Luis - so far now seems to be working correctly and not timing out.

Ok good... I can see how it could look like you're hanging in that situation.

LUIS just seems to have gone down again for a few minutes and I quickly logged everything I could in the terminal.  At the time, the LUIS query url simply returned a 503 or kept loading.
Whilst this was happening, sending a first message to the bot elicited no reply, a second message crashed the server with the logs showing
events.js:154
      throw er; // Unhandled 'error' event
      ^

Error: Intent recognition error: Unexpected token <
    at c:\dev\project\node_modules\botbuilder\lib\dialogs\IntentDialog.js:41:44
    at Request._callback (c:\dev\projectBlatter\node_modules\botbuilder\lib\dialogs\LuisDialog.js:41:21)
    at Request.self.callback (c:\dev\project\node_modules\request\request.js:200:22)
    at emitTwo (events.js:100:13)
    at Request.emit (events.js:185:7)
    at Request.<anonymous> (c:\dev\project\node_modules\request\request.js:1067:10)
    at emitOne (events.js:95:20)
    at Request.emit (events.js:182:7)
    at IncomingMessage.<anonymous> (c:\dev\project\node_modules\request\request.js:988:12)
    at emitNone (events.js:85:20)

Should the botbuilder be handling this error or should my code and, if so, what should I be wrapping in a try/catch block?

We talked and we're going to add a global error handler that fires in the scope of a conversation which gives you a chance to tell your user that the bot is having problems. Will provide a default implementation that 1) resets the dialog stack for the conversation so that the user isn't stuck. and 2) sends a generic "the bot is currently having problems" error message,
May be a couple of weeks before we get this added though,

Closing this issue due to age. @rlbeckett - please open a new issue if this issue is not fixed and needs further discussion. @Stevenic - reopen if necessary. Thanks!


FancyZones: WinKey + arrow ignore excluded apps list

Environment
PowerToys version: master

Steps to reproduce

Create zones, have "override windows snap keys" setting on
Add app to the  "excluded apps list"
Try to zone it with WinKey + arrow

Expected behavior

App is not assigned to a zone

Actual behavior

App is assigned to a zone

Fix available in 0.15.0 https://github.com/microsoft/PowerToys/releases


elements conflicts with React 18 (and Next.js 13.4)

See below. I can get elements to work in the project, but am seeing errors in the console that I believe are related to these issues.  This is a blocker for moving forward with this upgrade as we cannot move past the type errors without the dependency upgrading. We have opened an issue are tracking the fix for https://www.npmjs.com/package/@stoplight/mosaic. Once that is updated, we can resume work on this issue.

The draft PR has been linked to this issue
Additional PRs have been opened to update types to be React 18 compatible, those are also linked to this issue.

@brendarearden can you provide the link to the other issue that you are tracking that is needed to fix this one? thanks

@brendarearden @chohmann any updates on this? Looks like the linked pull request was closed.


Fix hawk_client to properly send unicode string metrics

use isinstance instead of checking type to include unicode type
https://github.com/openshift/openshift-tools/pull/1830 from stg
@twiest @joelddiaz

👍 #1830 in stg


HDFS-16276. RBF: Remove the useless configuration of rpc isolation in md

HDFS-16276
Description of PR
The dfs.federation.router.fairness.enable configuration is not used in the code, but there is it in md, we should delete it.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 26s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 46s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
shadedclient
57m 15s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
shadedclient
21m 51s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 32s

The patch does not generate ASF License warnings.

83m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3557/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3557

Optional Tests
dupname asflicense mvnsite codespell markdownlint

uname
Linux 8589bcb8618e 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d3e5c24d74c3a31776619b13a13aa6b07f048c21

Max. process+thread count
748 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3557/2/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Create Bulk endpoint for converting slp addresses

Similar to our other GET/Single and POST/Bulk endpoints we need a POST/Bulk endpoint for converting slp addresses.
https://rest.bitcoin.com/#/slp/slpAddressConvert

Overview
The scope of this task is to add a POST endpoint to create a bulk-upload version of the existing GET call slp/slpAddressConvert. The GET call is used for converting an address to the different types of address format one-at-a-time. The POST endpoint would allow an array of addresses to be passed, to do the conversion on many at once.
An example of a similar endpoint using this scheme is the GET and POST endpoints for block/detailsByHash:

GET block/detailsByHash user interface

GET block/detailsByHash source code

GET block/detailsByHash unit tests

POST block/detailsByHash user interface

POST block/detailsByHash source code

POST block/detailsByHash unit tests


[Outlook] (mobile) Clarify add-ins support

Fixes https://github.com/OfficeDev/office-js-docs-pr/issues/3184

Docs Build status updates of commit fdea649:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 74b2bb3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/requirements-for-running-office-add-ins.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.md
:white_check_mark:Succeeded
View

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

After testing, it looks like add-ins are supported on Outlook on the web via Safari on iOS devices, but not via browsers on Android mobile devices. Testing details are as follows:
Android
Hardware: Pixel 6 Pro
OS: Android 12
Add-in tested: Microsoft Translator
Outlook account used: M365 account

Application
Version
Results

Outlook on Android
4.2201.2
Able to access and run add-ins

Outlook for web (Chrome)
97.0.4692.98
Add-ins not supported

Outlook for web (Edge)
97.0.1072.69
Add-ins not supported

iOS
Hardware: iPad Air (4th Generation)
OS: iOS 15.3
Add-in tested: Microsoft Translator
Outlook account used: M365 account

Application
Version
Results

Outlook on iOS
4.2203.0
Able to access and run add-ins

Outlook for web (Safari)
15
Able to access and run add-ins

Screenshot of add-in access and usage on Outlook for web via Safari:

Screenshot of Outlook for web on Android:

@samantharamon Thanks for your diligent testing and verification. I'll update the documentation accordingly. Thanks!

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

File
Status
Preview URL
Details

docs/concepts/requirements-for-running-office-add-ins.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.md
:white_check_mark:Succeeded
View

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 562d081:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/requirements-for-running-office-add-ins.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.md
:white_check_mark:Succeeded
View

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

docs/concepts/requirements-for-running-office-add-ins.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.md
:white_check_mark:Succeeded
View

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


how to get past geo top artist?

i need past geo top artist
now i get current geo top artist
ex> 2016/ 5 spain geo top artist
but, i want get past geo top artists
ex>2015 4 16
pls, give me some tips

You can get current geo top artists like this:
artists = self.network.get_geo_top_artists(
            country="United Kingdom", limit=1)

You can get current geo top artists like this:
artists = self.network.get_geo_top_artists(
            country="United Kingdom", limit=1)

You used to be able to get weekly charts for a metro (a city) like this:
        metro = self.network.get_metro("Madrid", "Spain")
        dates = self.network.get_metro_weekly_chart_dates()
        (from_date, to_date) = dates[0]

        # get metro.function_name()
        func = getattr(metro, function_name, None)

        # Act
        chart = func(from_date=from_date, to_date=to_date, limit=1)

But it looks like Last.fm have removed that after they relaunched ("re-imagined") their website last August and broke lots of functionality.
Have a look through the available list of methods here: http://www.last.fm/api If it's not there, it's not available in pylast. If it is there, it should be available here too (and should be addable if not yet here).

thanks


updated for swift 3

The current PR is for master branch. Please create a new branch for swift 3.

Fixes: https://github.com/Ramotion/animated-tab-bar/issues/124

I'm not sure if I'm leaving this in the right place but I'm getting a few errors in the RAMFumeAnimiation file "no '+' candidates produce the expected contextual result type 'AnyObject'" at all the playMoveIconAnimation calls

Which Xcode are you using? I have not updated this for the Xcode 8 release.

Ok, there's my problem then. I'm using Xcode 8 but so far thats my only problem with it.


Data Security: Security oversight - an internal security team isn't necessarily require

The Security oversight section says:

The company has an internal security team that conducts security audits on the company's products and services.

I don't think having an internal security team is the only way - take debian linux or the openwrt project, for example, which have distributed community of people who respond to security threats.
I think the sentiment is great, but it excludes the open source community, or community-supported products.

I think the fact that it excludes the open source community may have a purpose. It depends on what TheDigitalStandard is meant to be.
A product that is developed and maintained by a (big?) company in cooperation with a distributed community of people is rare. The current situation is mainly: There are companies / brands on one side. And open source & community supported products on the other side.
Open source & community supported efforts quite often prove that certain things are possible, and can be done in a better way, than (appearantly) in a company setting.
Example; A big company produces a topspec smartphone. And drops softwaresupport & maintenance after 2 years. A community of firmware builders goes on adding the support years after that, up to the current Android with all patches applied.
Actually the community is doing the work, that the company should do.
The Openwrt project is something similar, but then for routers.
Anyhow, when TheDigitalStandard is meant to describe how companies should function in the classic way, then the used words in the Security oversight sections are "OK".
Otherwise, maybe the Security oversight section could be:
"The company has [at least] an internal security team that conducts security audits on the company's products and services. Alternatively it has interaction with, or at least a policy for implementing security related input by, community supported development groups."

Mudge, thoughts?

We already have a separate indicator for the company conducting third party testing, but internal testing and auditing is valuable - in an ideal world, the company tests their product first, and then the outside audit is for finding things that they missed.
I agree that we should maybe change the wording to allow for cases where the company outsources security functions (both internal product & service testing and corporate/network security), rather than having an internal team - possibly replace "internal" with "dedicated".
It's important to note that this standard is comparative, not pass/fail - an organization that has a dedicated security team should get credit for that, so we want to have it be something we look for, but it doesn't mean that an organization without one cannot get a good score.

The core of this valid feedback could be incorporated by an indicator and procedure that trapped for an additional (or alternative) mechanism of security review, and transparency around that review process.
This is somewhat covered by (or related to) participation in bug bounties, although that doesn't address or include the initial example of an open source project with a distributed security team.


Read Environment Variables in Settings.txt

This one line change allows environment variables to be referenced in the settings.txt file using ${VAR_NAME} or $VAR_NAME.  For example:
...
proxy:${HTTPS_PROXY}
...

Corey:
I logged Nvm for Windows issue 756https://github.com/coreybutler/nvm-windows/issues/756, and I’ve got a fork and a the fix as described.  I’m also going to need to Sanitize the display of URL’s w/ passwords, for which I’ll crate an issue.  Do you need a separate PR for each issue, or can I bundle them?
Let me know,
Mark
From: Corey Butler @.>
Sent: Saturday, September 11, 2021 1:24 AM
To: coreybutler/nvm-windows @.>
Cc: Mark Scott @.>; Author @.>
Subject: [EXTERNAL] Re: [coreybutler/nvm-windows] Read Environment Variables in Settings.txt (#632)
Merged #632https://github.com/coreybutler/nvm-windows/pull/632 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/coreybutler/nvm-windows/pull/632#event-5287221130, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS425IMXKZH5FBFIYEZ3BL3UBLRYRANCNFSM4ZNFQ6DQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

If I understand you correctly, you want to clear sensitive data from the URL setting so it does not display when nvm proxy is executed. That seems reasonable. I'd make that a separate PR, because I'm not entirely clear about the need in issue 756 (which I replied to)... but that doesn't have to block a PR for URL sanitization.

Sounds good.  I’ll have 2 PR’s.
Thanks!
Mark
From: Corey Butler @.>
Sent: Tuesday, March 8, 2022 5:16 PM
To: coreybutler/nvm-windows @.>
Cc: Mark Scott @.>; Author @.>
Subject: [EXTERNAL] Re: [coreybutler/nvm-windows] Read Environment Variables in Settings.txt (#632)
If I understand you correctly, you want to clear sensitive data from the URL setting so it does not display when nvm proxy is executed. That seems reasonable. I'd make that a separate PR, because I'm not entirely clear about the need in issue 756 (which I replied to)... but that doesn't have to block a PR for URL sanitization.
—
Reply to this email directly, view it on GitHubhttps://github.com/coreybutler/nvm-windows/pull/632#issuecomment-1062272387, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS425IK6WV5VEA7AM4KNXWDU67GQLANCNFSM4ZNFQ6DQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


one node view ui: list view

User Story
As an Automate user, I'd like to have a way to quickly understand which of my nodes are failing the compliance scans but passing their client runs, which nodes just started failing compliance scans or client runs when they were previously passing, which nodes failed a scan during a timerange, etc.
We've done the work to answer these questions via api (https://github.com/chef/automate/blob/master/components/automate-chef-io/content/docs/nodes.md#examples).
Now we need to build a list view to help our users out.
sample request and response from api:
➜  compliance-service git:(master) curl -s --insecure -H "api-token: token-val" https://a2-url/api/v0/nodes/search -d '{
  "filters": [
    {"key": "last_run_status", "values": ["PASSED"]},
    {"key": "last_scan_status", "values": ["FAILED"]}
  ]
}' | jq

{
  "nodes": [
    {
      "id": "ef530be5-2a0e-4968-9d64-60693238c46c",
      "name": "chefdk-rhel-6-tester-11555e.cd.chef.co",
      "platform": "redhat 6.9",
      "platform_version": "6.9",
      "manager": "",
      "tags": [
        {
          "key": "chef-tag",
          "value": "chefdk"
        },
        {
          "key": "chef-tag",
          "value": "slave"
        },
        {
          "key": "chef-tag",
          "value": "tester"
        }
      ],
      "last_contact": "2019-05-31T19:16:36Z",
      "status": "unknown",
      "last_job": null,
      "target_config": null,
      "manager_ids": [],
      "connection_error": "",
      "state": "RUNNING",
      "name_prefix": "",
      "projects": [],
      "run_data": {
        "id": "7139d6eb-3df9-4b16-a953-d570735f3012",
        "status": "PASSED",
        "penultimate_status": "PASSED",
        "end_time": "2019-05-31T19:16:36Z"
      },
      "scan_data": {
        "id": "22ffdea1-d5d9-499b-b4ef-c4683c117fa9",
        "status": "FAILED",
        "penultimate_status": "UNKNOWN",
        "end_time": "2019-05-14T20:36:33Z"
      }
    },
    {
      "id": "8907a72f-c589-4e6d-b222-86ef606a9446",
      "name": "chefdk-rhel-7-tester-a3a252.cd.chef.co",
      "platform": "redhat 7.3",
      "platform_version": "7.3",
      "manager": "",
      "tags": [
        {
          "key": "chef-tag",
          "value": "chefdk"
        },
        {
          "key": "chef-tag",
          "value": "slave"
        },
        {
          "key": "chef-tag",
          "value": "tester"
        }
      ],
      "last_contact": "2019-05-31T19:45:03Z",
      "status": "unknown",
      "last_job": null,
      "target_config": null,
      "manager_ids": [],
      "connection_error": "",
      "state": "RUNNING",
      "name_prefix": "",
      "projects": [],
      "run_data": {
        "id": "c052ac64-2e75-42b9-8ae9-25a5c864916e",
        "status": "PASSED",
        "penultimate_status": "PASSED",
        "end_time": "2019-05-31T19:45:03Z"
      },
      "scan_data": {
        "id": "009d582d-fbd5-4079-8730-001ecee40896",
        "status": "FAILED",
        "penultimate_status": "UNKNOWN",
        "end_time": "2019-05-14T20:41:31Z"
      }
    }
  ],
  "total": 2,
  "total_unreachable": 2640,
  "total_reachable": 21,
  "total_unknown": 1595
}

Mock Up of List Page

Definition of Done
Under feature flag, we will have a temporary link in the top navigation listed as "Nodes" where you can access this page. This will change when we merge all the infrastructure items together under one top nav item.
Filters Buttons:
There will be 4 actions:

Show all Nodes
Show all nodes that contain client runs (if they also have compliance scans - include those as well)
show all nodes that contain compliance scans (if they have client runs - include those as well)
show all missing nodes (this is when a node gets marked as missing) and when there is no data on compliance scans as well.

Searchbar:

can search by node name, platform, environment
search for values by using the functionality introduced in https://github.com/chef/automate/issues/667

Sortable Columns:

Node Name
Platform
Environment
Last Infra Run
Last InSpec Scan

Action Items within Table:
Last Client Run Link:  Will go to the Client Run Node Details page
e.g. /client-runs/b39584f3-82f8-46f3-8bac-7a963dc90638/runs/048ea4f9-5f16-4a25-9d43-5f295e0be558;end_time=2019-06-20T22:20:46Z
Last Scan Job Link: Will go to the Node Details page via the Compliance page.
e.g. /compliance/reports/nodes/8dc5a451-d3f0-4b06-957a-d6bd06f51bec

i have a few questions:

why is there a "no data" placeholder on a couple of the nodes/when does that apply?
even if the node is now "missing", wouldn't it have a last client run?

is this list (including unchecked items) just the same list that's on client runs? do we need all that information? why does this view require all that info? what about things like "node state" (running/stopped/terminated/missing/unknown) - do we want to show that?

what fields should the user be able to search by in the searchbar?

in client runs, you can only delete the missing nodes if you are an admin - does the same logic apply here?

all the fields listed here: https://github.com/chef/automate/blob/master/components/nodemanager-service/pgdb/nodes.go#L593 + tags are filterable for nodes. we'll need to do a small amount of backend work to "suggest" field values (we already support this to some degree, need to make sure we can "suggest" on all the fields we support for filtering)

ah yes, we can search on all the filterable fields and return suggest field values by adding to https://github.com/chef/automate/blob/master/components/nodemanager-service/pgdb/nodes.go#L890

i have a few questions:
* why is there a "no data" placeholder on a couple of the nodes/when does that apply?
  even if the node is now "missing", wouldn't it have a last client run?

Im not sure when that occurs. I saw this on dev, and the little info icon mentions that there is no client run data in there, yet it still pulls in.  I just threw that in there to cover for that case. Also, looks like a good talking point to get a better understanding.

* is this list (including unchecked items) just the same list that's on client runs? do we need all that information? why does this view require all that info? what about things like "node state" (running/stopped/terminated/missing/unknown) - do we want to show that?

Yes. This is just the same list pulled from Client Runs for parity.  As for do we need all this?  Is a good question. I know some things like client version was an ask. But I threw all the things on the table. Ideally, if we can track which items through telemetry, we can know which items are useful or not.
As for Node state, I thought a while on this. Originally I had that node status in there which combined if it was missing (client runs) and stopped,terminiated, unknown, etc. (compliance) For simplicity for first round I decided to remove it.  We can totally add it back in if we want, but I think this is another talking point I would like to discuss and figure out.

* what fields should the user be able to search by in the searchbar?

I thought it was going to be the combination of both search field items from both Client Runs and Compliance?

* in client runs, you can only delete the missing nodes if you are an admin - does the same logic apply here?

Yes.

I would suggest not adding the "Remove Nodes" button functionality to this view. I think it would make sense to only allow the user to be able to delete nodes from the Client Runs page for now.
For the "No Data" label. I would say not to bring that label to this view. The backend does still store the last Client Run date-time if there is no client runs data. It would be better to display the date-time.

i'm +1 on the suggestions from @lancewf

Note: we currently support filtering on this list of fields: https://github.com/chef/automate/blob/master/components/automate-chef-io/content/docs/nodes.md#filtering-nodes

Sweet. I will remove the 'Remove  Nodes'

Note: we currently support filtering on this list of fields: https://github.com/chef/automate/blob/master/components/automate-chef-io/content/docs/nodes.md#filtering-nodes

Oh. wow. would we be able to pull in other searchable items in the future like the Client Version, cookbooks, profiles, environments etc?
If this is all we can search, we may be able to remove some of the configurable columns then.

Oh. wow. would we be able to pull in other searchable items in the future like the Client Version, cookbooks, profiles, environments etc?

Yes -- I think it would probably be a good idea to figure out what the most important/relevant fields are to filter on there. Then we can look at adding that data in the call to nodemanager

If this is all we can search, we may be able to remove some of the configurable columns then.

👍

How do we feel about renaming Last Client Run to Last Infra Run?

^^^ yes, good point!!

@jerryaldrichiii ah yeah. funny you mentioned that. This just came up in our UX meeting about how we are going to integrate the new Infra terminology into Automate. I think we are reconvening next week on it after we get time with product managers

Love the combined look and simplicity of combining compliance and client run views. Is this going to be carried forward to the individual node as well when clicked? Simply adding a new tab next to attributes that shows the scan controls in a similar way the resources tab does would make things alot cleaner and more intuitive.
The node view you could also bring back the graphical ring from the client runs and add next to it the graphical ring from compliance view to get a quick overview of entire infrastructure status in this new nodes view. You could also do the same when clicking on an individual node add the graphic ring with compliance info along side the client run info ring.

@stromweld

Love the combined look and simplicity of combining compliance and client run views. Is this going to be carried forward to the individual node as well when clicked? Simply adding a new tab next to attributes that shows the scan controls in a similar way the resources tab does would make things alot cleaner and more intuitive.
The node view you could also bring back the graphical ring from the client runs and add next to it the graphical ring from compliance view to get a quick overview of entire infrastructure status in this new nodes view. You could also do the same when clicking on an individual node add the graphic ring with compliance info along side the client run info ring.

Yes, there are designs for that, but not sure when it will get out. I am still working out concept, exploring different charts, etc for comparing all the data.

I like the idea of combining the view - it's kind of rough looking at client run vs. compliance result pages separately.

I think combining "Client Runs" and "Compliance" tabs to have a unified view is going to make for a better user experience in the long run. Just yesterday I had to explain what the difference was in those two tabs to someone who is relatively new to Automate.
This might be a little bit outside of the scope of this particular topic, but one item that we struggle with is seeing what has caused client/infra runs to fail at scale. Our automate instance has 10,000+ nodes checking into it, so, naturally, when something fails it will fail across many nodes. If we see a spike in failed nodes, let's say an additional 50, the only way to know if all of those 50 are failing due to the same problem is to look into each node individually. The latest release of A2 has helped in this scenario with the ability to filter based on Error, but having aggregation for each error would assist in determining where we need to focus on resolving failed client/infra runs.

@jonong1972 are there more finalized designs that account for the feedback given in the issue that you could post?
that way i can check if there's any remaining backend work to complete for this

just cleaning up a bunch of old comments that have been addressed

closing this; we'll be doing something for the ui, but it won't be this list ui. stay tuned!


added 2024 minting periods, removed from faq

to answer this issue
note: we remove the minting questions in the qna, and set a new subsection in farming optimization

one of the side goals is to reduce the faq length, and add the qna content within the manual itself

note: we leave the 2023 periods for references for the farmers

@Mik-TF


Ethan: Watch nacagha.com

Ethan requests the watch of the watch_keyword nacagha\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

nacagha\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Wrong type definition for BTPayPalGetDeviceDataResult

I believe that the type BTPayPalGetDeviceDataResult is wrongly defined.
Currently it is defined as type BTPayPalGetDeviceDataResult = string and it is used as a return type for method getDeviceDataFromDataCollector(). This method however returns an object with correlation_id field in it.

Either type definition or return value of the method needs to be adjusted.

I see it is actually a serialized (stringified) object being returned.
Wouldn't it be better to actually return an object instead of a serialized object? Or is there any particular reason to decide to stringify it instead?


Styling: left, right, and yAxis line color?

I'm able to set the color of the grid lines in the ticks definition, but I can't seem to set the vertical lines for the left/right of the grid as well as the vertical line for the yAxis scale. Any ideas? See the screenshot below where the vertical lines are dark grey while others are set to a color.

UPDATE: nevermind - I found the option but will leave here in case anyone else needs it.
On the scales, you need to set the grid: { borderColor: someColor }


Qbt cumulative versions use potentially insecure sha1 hash

The hashing code chooses sha1 here:  https://github.com/TerabyteQbt/qbt/blob/a234d9d13d84701b0960299f9c5f3b516a005d07-qbt-6b09307ffd7af1eb7810d595108de34e502e512c/lib/main/src/qbt/QbtHashUtils.java
The sting that is hashed is generated here:
https://github.com/TerabyteQbt/qbt/blob/a234d9d13d84701b0960299f9c5f3b516a005d07-qbt-6b09307ffd7af1eb7810d595108de34e502e512c/app/main/src/qbt/recursive/cv/CumulativeVersion.java
Given that sha1 is now known to have collisions, we should have a plan for migrating to sha-256 or some other hash algorithm

If we change the hash, we should also change the "qbt version" constant (which is a randomly generated hash).  It lives here: https://github.com/TerabyteQbt/qbt/blob/a234d9d13d84701b0960299f9c5f3b516a005d07-qbt-6b09307ffd7af1eb7810d595108de34e502e512c/app/main/src/qbt/recursive/cv/CumulativeVersionDigest.java#L15


.NET / ASP.NET Core

Can this be used with .NET / ASP.NET Core?
It has a new config mechanism, but doesn't look as sophisticated as this lib.

If you are happy to take a dependency on the IConfiguration you could give this a try https://github.com/dasiths/NimbleConfig


gcc is not dot-repeatable in contrast to vim-commentary

I have switched from vim-commentary by tpope.
Motivation:

This plugin has native treesitter support for calculating commentstring which works for multiple (injected/embedded) languages like Vue or Markdown.

I miss the possibility to repeat 10gcc with the dot ..
I have found following comment

toggle_current_linewise_op is dot-repeatable whereas toggle_linewise_count is not.

Is it possible to make toggle_linewise_count dot-repeatable as well?
In particular, at the moment the buffer is changed in a suprising way:
hello
world
hello
world

Press on first line 2gcc and then move to third line to press ., you get:
/* hello */
/* world */

ello
world

A line is inserted and a character is removed. This does not feel like it is intended. vim-commentary handles this flawlessly:
/* hello */
/* world */
/* hello */
/* world */

@kiryph [count]gcc and [count]gbc both doesn't support dot-repeat. I wasn't motivated enough to support that as I don't use them very often.
(I would like to assume this ticket as feature request not a bug)

It's already there https://github.com/numToStr/Comment.nvim#count-prefix

Oh my bad. Sorry.


[KED-990] Remove snapshot history

BREAKING CHANGE - do not merge until v3 release
Description
As phase one of the coming redesign, we're removing the snapshot history panel, and instead that info will be displayed elsewhere.
Major changes:

Delete snapshot history, tabs and description components
Remove changeActiveSnapshot action/reducer
Change API data format: Remove the top level snapshots array prop, so now there is only a single pipeline datum
Change the mock data format, so that instead of an array of two snapshots, now there are two named data objects ('lorem' and 'animals')
Refactor the data formatter/normaliser, to break it up into shorter functions and simplify it
Remove/rename mentions of snapshots

Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Checklist

[x] Read the contributing guidelines
[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[x] Updated the documentation to reflect the code changes
[ ] Added new entries to the RELEASE.md file
[x] Added tests to cover my changes
[x] Assigned myself to the PR
[x] Added Type label to the PR

@ottis Thanks a lot for your feedback! Really useful comments. I've addressed and resolved the two that I think need to be fixed in this PR. There's a few others that I think are really good feedback, but are more generally feedback about KedroViz architecture rather than this PR specifically, so I'll make a note of them and address them in future PRs. If that's okay with you, can you please chuck a ✅  on this PR so that merging is unblocked?