Add an official plugin to support RasaHQ/rasa

作者什么时候搞在这插件哈，我也需要

@itmagus I have researched it, and it's easy to write the plugin but need to adapt some code of Turms server to support it, so it needs some time to design.
I am not sure when to deliver the feature, but I can spend 1~2 hours per day designing and writing code because I am busy and need to review my project experience + recite 八股文 + practice algorithms😅 recently to find a new job. So it will take some time for the plugin (maybe less than a month? I am not sure honestly)
And if you are interested in writing the plugin, you can have a try.

好的，我现这一两个星期的工作进展应该就会到这里了，我可以尝试一下

@JamesChenX 你调整完服务端的代码后，可以通知我哈

@itmagus The design and implementation are easier than I expected, so I have written the plugin without testing.
And the PR https://github.com/turms-im/turms/pull/1137 is just a draft, meaning that some workflow of the plugin may need a redesign and I will polish the code later.
If you are interested in it, you can check the PR to know whether the features of the plugin meet your requirements, and if you need more features, you can require them before I will the plugin, so the development process will be faster.

Done.
Doc: https://turms-im.github.io/docs/for-developers/chatbot.html


Typo

Missing 'd' in the following:
Factors inclue the traffic

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

ID: cedb9559-6da0-2e91-eaef-12d9e9bfff4f
Version Independent ID: cf9ff409-0028-5b6c-b77e-3987ad23671d
Content: BluetoothLEDevice.FromBluetoothAddressAsync Method (Windows.Devices.Bluetooth) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Devices.Bluetooth/BluetoothLEDevice.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Thanks, @olivier-basille, I have a fix for this on its way. It should be live soon but I'll keep an eye on it.
-Steve


When location permissions are removed and regranted, going to current location doesn't show symbol

This was one observation from Sarat's testing feedback (result from test case 1.5).

A PR is open for this issue.
https://github.com/Esri/data-collection-ios/pull/124

Verified on master.


fix(nebula_ros): limit cloud_max_angle param to 359 #44

PR Type

Bug Fix

Related Links
The issue: https://github.com/tier4/nebula/issues/44
Description
This PR changes default cloud_max_angle to 359 and also limits cloud_min_angle and cloud_max_angle to 359. By doing those, it fixes https://github.com/tier4/nebula/issues/44 .
Review Procedure
Range of the parameters, default values of them and readme can be checked.
Remarks
Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR: Required to pass before the merge.

Thank you for the PR! I see you have edited for Hesai and Velodyne - actually, Hesai sensors have a range from [0...360] whereas Velodyne sensors are typically [0...359].

Hello, thank you for the feedback! I discarded Hesai chagnes.

@mebasoglu cc @amc-nu
Thank you for the PR- upon investigation, unfortunately we can't limit Velodyne max angle to 360 degrees as it is used in software clipping so doing so results in a 1 degree gap in the cloud.
I will address this issue in a different PR.

Codecov Report
Patch coverage has no change and project coverage change: -2.13% :warning:

Comparison is base (cb25896) 13.38% compared to head (5cc5164) 11.25%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #45      +/-   ##
==========================================
- Coverage   13.38%   11.25%   -2.13%
==========================================
  Files         111       33      -78
  Lines       10991     4619    -6372
  Branches     1727     1145     -582
==========================================
- Hits         1471      520     -951
+ Misses       8339     3156    -5183
+ Partials     1181      943     -238

Flag
Coverage Δ

differential
11.25% <0.00%> (?)

total
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

..._ros/src/velodyne/velodyne_decoder_ros_wrapper.cpp
0.00% <0.00%> (ø)

...src/velodyne/velodyne_hw_interface_ros_wrapper.cpp
0.00% <0.00%> (ø)

... and 78 files with indirect coverage changes

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

@mebasoglu
Can you please test with this PR?
https://github.com/tier4/nebula/pull/50
If that fixes the issue then we can close this PR. Thank you.

Hello, I tested and it works, thank you.


Update terraform-docs config to prevent generating empty readmes

This updates the terraform-docs gh action config to use find-dir instead of recursion, which will prevent creating and empty README.md for directories without .tf files. Most of these are harmless, but the one created in .github overrides the README in the root directory when viewing the repo in github.
The first commit removes all auto-generated documentation so that we can confirm the new config generates all the documentation we want and none that we don't. The commits from the github action mostly restore this documentation, except the empty files, with some formatting changes.

Nice find!


fix cases for testing sql block rule may interfere other cases

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Add namespaced aliases

Fix issue #455

Thanks! I'd rather not put the logic inside the template, can you move that to Generator class?

I had a big problem with that... How to name theses variables ? 🤣

Thanks for the fix! Is there anything I can help with to make this be good enough to appear in master and be tagged?

@pinepain Can you give a try to this newest version ?

@zedentox Tried a new version and it seems to be working. There is minor comment on trailing white spaces in views/helper.php, but apart of that - 👍. Thank you for your time and efforts!

Okay merged, let me know if it's good or not

Thank you! Will do more intensive testing during this week, but the main issue looks solved.

Hi folks,
I'm not at a coding level to know if I'm on the right page or not, but I wanted to send you a little more info.   I've had a similar problem to Pinepain in #455 : I can not click through to methods in my namespaced aliases -- IDE doesn't recognize them, instead clicking points into the ide_helper file.  v2.2.3 does successfully work, latest version, including  b611cb5 does not.
I register these aliases in config.app only through the aliases array like so:
'aliases' => [
    'CacheHelper'=> \App\Helpers\CacheHelper::class,
]

Code functions fine, and always has (though I'm sure I'm screwing something up), and IDE Helper has always worked perfectly in identifying these until after 2.2.3.

@zedentox my apologies.  I thought this was related to this PR.  I thought the issue was namespaced aliases were not being picked up, and this PR was meant to fix that.  I was reporting that it does not for those aliases that I have registered.  Again, my apologies, I may not understand enough of this to know the difference between this and the issue looking to be fixed, though I thought they were the same.


Add ability to proxy VNC port

Should be able to proxy vnc port by session ID like the following:
/vnc/<uuid>

The request like this...
GET /vnc

... should return a list of currently available videos.

@vania-pooh would video files be available for pulling out from containers, or it'd be just a live streaming via selenoid-ui?

@sskorol this is one is about streaming only to Selenoid UI. Regarding video - this is a more complicated task. In my current understanding we can't capture video directly from VNC. In order to capture video we need to use something like this. The method described in the article requires installing ffmpeg and using x11grab driver. Installing all this software to every container will dramatically increase their size. So if you know a better way to capture video (e.g. directly from VNC) - please tell us.

So unless you know very simple way to capture video from VNC, video feature will be one of the next.

@vania-pooh personally I have used ffmpeg for video recording in containers. It was chosen for Allure compatibility (as it supports only html5-video formats at moment).


Some questions about the 360FV-Matterport dataset

Dear authors,
thanks for your excellent work! I have some questions about the 360FV-Matterport dataset. It would be great if you can help me out.

The original Matterport dataset has 90 scenes in total, but I can only find train61+val7+test18=total86 scenes in 360BEV paper. Where are the rest 4 scenes? Do I miss something?
I cannot figure out the train/val/test subset division of the 360FV-Matterport dataset. Would you mind giving me some suggestions on the subset division?

Thank you in advance for your help.
Best,
Junwei

Problem solved. Close.


combinator: add S.K

This is the (R.always) implementation suggested by @aaditmshah in https://github.com/ramda/ramda/issues/732#issuecomment-70383334. It may be too strict for Ramda, but it feels right at home here.

To be honest, when I read the title of this pull request I thought that you were implementing the SKI combinator calculus.

:+1:

@aaditmshah: Ditto!

That's currently over my head, @aaditmshah. :)


Metrics-related items within migration guide for dbt v1.6

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
Migration guide for dbt v1.6:
https://docs.getdbt.com/guides/migration/versions/upgrading-to-v1.6
What part(s) of the page would you like to see updated?
For projects that define metrics, give them any information that they need.
Additional information
Internal Slack link with context: https://dbt-labs.slack.com/archives/C0131TY7EEA/p1686330380388209?thread_ts=1686328666.241689&cid=C0131TY7EEA

@mirnawong1 @Jstein77 Does one/both of you want to take on this one?
I'm picturing a strongly worded note under the "Behavior changes" section of the migration guide:

Action required if your project defines metrics: The spec for metrics has changed...

hey @jtcohen6, i've added something in PR #3386 but would love to have @Jstein77 also review it since he's creating the migration script.

This is very timely! I had time carved out separately this week to work on a migration guide. It's also going to include how to update your cloud environments to migrate to the new SL.

@jtcohen6 @dbeatty10 here's the draft of the metrics migration guide

did you mean this one @Jstein77 ?


fix: fix imported scene lighting

DONE

Updated the import/export to include ambient lighting settings
Updated metallic and gloss values (still tweaking)

TO DO

Include shadows settings (eg soft shadows for SmallPetRacing)
Include object cast shadow settings (eg Sun should not cast shadows)
Fix colour difference (imported scene still seems a bit too orange)

I added the shadow settings. You can see if you like the results. Let me know if you think the colour difference is worth looking into.
There is one area I didn't fix, which is the specular highlights, because the glTF shader doesn't expose this such that it can be easily changed. Also let me know if you think this is important.

Thanks! I just found out that the difference is most likely due to the lack of environment reflections. I'll open one on that then.


Create User Table (User Management)

Why was the Issue closed again

Why was the Issue closed again

We have not fully splitted the tasks.


Add second KeyReuse check "near" issuance

The current CSR workflow checks for the reuse of a public key only when the user uploads it and only checks on already issued certificates. Therefore a user can upload the same CSR/Key twice as long as the first request has not been issued.
Suggested solution: Check for duplicate key when giving the approval (policy error).
Note: This might also be insufficient if we have delayed issuance in a system but it should work for all systems where requests are issued on approval.
See also #292

Fixed with 7245cd97f6f4bf1d4950a95c13a18d63d9cd9659


"showing 18 issues" when there's less

it says "showing 18 issues" on both "online" and "archived". 18 is the complete number of issues, it should probably only count the ones that are actually shown. (6 or 12 respectively)
(or just change the text to "18 issues in total" or something)

thanks for posting, working on it


Shutdown server and exit process on browser close

We should use the server's ability to listen for the websocket closing as a signal to shut down the server and end the process, just like killing the process closes the browser window.

Fixed in deec116faf1dfc43ee014284a2c088d44f057d4f


upgrade scala/zinc to 1.10.2

Upgrades zinc, the scala incremental compiler, to 1.10.2.
Context
Includes compiler avoidance bug fix https://github.com/sbt/zinc/pull/1382 which affects gradle multi project builds.
Contributor Checklist

[x] Review Contribution Guidelines.
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

A test case failure seems to indicate a regression with the zinc upgrade. I'm having a look.

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have failed:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle test this please

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have failed:

Pull Request Feedback (Trigger) (Check)

Build Scan


[TEST] Test image upgrade-test.5-3.3-3.1-1 not working properly on ARM64 pipeline

What's the test to develop? Please describe
Test image upgrade-test.5-3.3-3.1-1 not working properly on ARM64 pipeline
Describe the items of the test development (DoD, definition of done) you'd like

[x] Build correct test images
[ ] Verify test result

Additional context
https://github.com/longhorn/longhorn/issues/4615

cc @longhorn/qa

After longhornio/longhorn-engine:v1.3.x-head updated (cliAPIVersion 6),  ARM64 engine upgrade test fail on v1.3.x pipeline not happened again
As for v1.2.x test pipeline result, still need time to investigate

Engine upgrade test case on v1.2.x ARM64, v1.2.x AMD64), v1.3.x ARM64, v1.3.x AMD64, master-head ARM64, master-head AMD64, are all working properly now


Need add transport length check libspdm_mctp_encode_message()

In libspdm_pci_doe_encode_message(), there is length check for *transport_message_size. But the code is missing in libspdm_mctp_encode_message().
    LIBSPDM_ASSERT(*transport_message_size >=
                   aligned_message_size + sizeof(pci_doe_data_object_header_t));
    if (*transport_message_size <
        aligned_message_size + sizeof(pci_doe_data_object_header_t)) {
        *transport_message_size = aligned_message_size +
                                  sizeof(pci_doe_data_object_header_t);
        return LIBSPDM_STATUS_BUFFER_TOO_SMALL;
    }

@xiangfeima, would you please take this one?

@jyao1 I'm all set in China office. Please assigne this one to me.


Optimize assert() calls

Premise
Some time ago solc-typed-ast introduced pretty printing routines in https://github.com/ConsenSys/solc-typed-ast/pull/71. This PR removed duplicated codebase and reuses solc-typed-ast's functionality. Also it boosts speed as pp() and ASTNode.print() deferred until there is a necessity to throw and error and compose a message for it (currently a lot of pp()-ing is done, but results are not used).
Changes

[x] Updated dependencies.
[x] Tweak canonical signature composition calls to use newer API: default to ABI encoder v2.
[x] Removed src/util/pp.ts and src/util/struct_equality.ts and reused logic from solc-typed-ast.
[x] Cleanup in assert() calls to defer pp() and ASTNode.print() until error is actually thrown.
[x] Fixed a ton of places when assert() call had an empty message.
[x] Reduced use of big-integer library to just support scientific notation in expression parser.
[x] Slight code readability improvements.
[x] Tweaked affected test suites.

Notes

Were unable to completely get rid of big-integer dependency due to currently Scribble supports numbers with scientific notation in predicate expressions. Maybe there is a way to replace it with something light-weight (consider as a followup).

Regards.

Only CI failures are the intermittent segfaults due to nyc. Force-merging


#86 broke send_keys with shift plus special keys

page.send_keys([:shift, :home]) now errors with
Playwright::Error:
       Unknown key: "HOME"

I've got the same problem. I suspect commit 733e025e might have introduced it.
My Capybara code (that works on 0.5.2) looks like this:
find('body').send_keys :tab, 'blue', %i[shift return], 'red', :return

I'm getting the following error:
Playwright::Error: Unknown key: "ENTER"

I can take a stab at fixing this, it makes sense that only character-keys should be upcased

Took a stab in https://github.com/YusukeIwaki/capybara-playwright-driver/pull/90


generic-amd64: add device type

Make it private until we figure out what to do about genericx86-64-ext: https://github.com/balena-os/balena-generic/issues/21

@balena-ci rebase

@balena-ci rebase


colloid-gtk-theme: 2023-08-12 -> 2023.04.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for colloid-gtk-theme is: A modern and clean Gtk theme
meta.homepage for colloid-gtk-theme is: https://github.com/vinceliuice/Colloid-gtk-theme
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2023.04.11 in filename of file in /nix/store/q5zkzvkls0ylmz1gs8j878vqrx0m64kb-colloid-gtk-theme-2023.04.11

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
catppuccin-gtk
colloid-gtk-theme

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q5zkzvkls0ylmz1gs8j878vqrx0m64kb-colloid-gtk-theme-2023.04.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A colloid-gtk-theme https://github.com/r-ryantm/nixpkgs/archive/58bb9fe05a3aa28dd223b2834a7a4df957439c59.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/58bb9fe05a3aa28dd223b2834a7a4df957439c59#colloid-gtk-theme

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q5zkzvkls0ylmz1gs8j878vqrx0m64kb-colloid-gtk-theme-2023.04.11
ls -la /nix/store/q5zkzvkls0ylmz1gs8j878vqrx0m64kb-colloid-gtk-theme-2023.04.11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

catppuccin-gtk
colloid-gtk-theme

Maintainer pings
cc @romildo for testing.

Looks like gitUpdater was fooled by inconsistent tag formatting; this PR should be marked as draft until the update script is fixed or r-ryantm will keep submitting it.


add more info about the default model location using SAT

Take some time to find out the SAT_HOME env to prevent my system drive from being eaten by the large models.

Thank you for your contribution!


Fixed issue with unused lifetimes in struct

This PR fixes the case where there are no fields in a struct that defined a lifetime.

I tested this with all the iotas and fixed the issue


IE Options support in Capabilities class

Watir::Capabilities does not currently support IE Options class directly

Based on our discussion on Slack, IE does not allow us to bypass the insecure SSL certificates. Leaving this here in case anyone else is trying to bypass the certs through Capabilities.
Code to reproduce:
Watir::Browser.new :ie, {"acceptInsecureCerts" => true} or Watir::Browser.new :ie, { accept_ssl_certs: true, accept_insecure_certs: true }
2018-03-21 13:23:38 INFO Selenium -> POST session
2018-03-21 13:23:38 INFO Selenium    >>> http://<IP_ADDRESS>:5555/session | {"desiredCapabilities":{"browserName":"internet explorer","version":"","platform":"WINDOWS","javascriptEnabled":false,"cssSelectorsEnabled":true,"takesScreenshot":true,"nativeEvents":true,"rotatable":false,"acceptInsecureCerts":true,"ignoreProtectedModeSettings":null,"se:ieOptions":{"nativeEvents":true}},"capabilities":{"firstMatch":[{"browserName":"internet explorer","acceptInsecureCerts":true,"se:ieOptions":{"nativeEvents":true}}]}}
2018-03-21 13:23:38 INFO Selenium <- {"value":{"data":null,"error":"session not created","message":"No matching capability sets found.\nUnable to match capability set 0: acceptInsecureCerts was 'true', but the IE driver does not allow bypassing insecure (self-signed) SSL certificates","stacktrace":""}}
  Background:                                                              # features/unit_tests/AT-340_general_steps_unit_tests.feature:6
  No matching capability sets found.
  Unable to match capability set 0: acceptInsecureCerts was 'true', but the IE driver does not allow bypassing insecure (self-signed) SSL certificates (Selenium::WebDriver::Error::SessionNotCreatedError)

Hi @Rajagopalan-M ,
I think my issue #722 also looks similar to this.
I need solution for this ssl certificates handling. Please help on this

@evnraja32
I have answered there, can you please check it out?
https://github.com/watir/watir/issues/722

This was fixed via https://github.com/watir/watir/pull/803


InvalidArgumentError (see above for traceback): Cannot assign a device for operation prefix/Rank: Could not satisfy explicit device specification '/device:GPU:0' because no supported kernel for GPU devices is available.

When I tried to perform prediction on a single image, I am getting an error at Node prefix/Rank: saying could not satisfy explicit device specification '/device:GPU:0' because no supported kernel for GPU devices is available.
I am trying to solve this problem from quite a long time. Any help or suggestions are appreciated.

I believe you can fix this by passing the argument --gpu-id -1.
e.g. aocr train ./datasets/training.tfrecords --gpu-id -1 this will let the code to use cpu:0 instead.
see this model.py#L60 and this __main__.py#L88


Cleanup

General clean up of code to make development easier

cleaned up all indentation
renamed some variables for readability
moved block for translators to top of file
streamlined code where possible (especially some if...then blocks)
normalized variable references (omit {} where possible)
bug fix: chapter loop should have used < and not <=
bug fix: new content appended to main file instead of recreating file on subsequent runs
added The Bible (###) exported folder to .gitignore

Thank you for contributing!


 Would be not great UX to play, and I don't see a good way around that.

It's not a super terrible idea. I just don't think I know enough about asyncio yet to manage that, cuz I can imagine a couple race conditions that I can't think of a.


Incorrect macro playback if it involves <c-d> and <c-u>

Steps to reproduce:

start a macro
append text to line
<c-d>
append text to line
<c-u>
Replay macro.

Observed: consequent macros append to a line below, as if <c-u> and <c-d> actually were j and k

The scrolling command are not instantaneous, it creates a timer that runs until the scrolling finishes. They do have an instantaneous j/k as the first movement before the timer starts because vim.loop.new_timer() doesn't call its callback function until the first time-step has passed. That is why it looks like only j or k are pressed. Sadly, I don't think there is a way to fix this. Do other smooth-scrolling plugins handle macros properly (to get some inspiration)? Also, in what instances would you use <C-u>/<C-d> in a macro? Usually macros are for precise actions.
I'll close this issue for now but if anyone has any ideas on how to fix this I'll reopen.
side note: If you press <C-u> and later in the macro <C-d> you will end up in the same place at the end of the macro because that is what would happen if you rapidly press <C-u><C-d>.

Why not add an option to disable neoscroll in mappings?
--@ rturns true or false
M.is_recording = function()
  return vim.fn.reg_recording() ~= nil
end

The sbove function could be used to create an option: disable_in_macros (bollean)
if disable_in_macros == true and not is_tecording ...


i want to improve home page UI

i want to improve home page UI

i would like to work on this issue and apply my technical knowledge to make the home page UI better

I would like to know what changes you gonna make , may be sample can help me understand better


Update README.md

Adding information how to get [dockerhost] IP address. I couldn't figure out for long time what is and how get [dockerhost] so I just want to spare other folks same effort.

Thanks!

Thank you :)


Do you know a forum for Ghidra?

I want to ask my questions there about Guidora and its settings and function and the definition of micro.
For example, what about the coldfire mcf5372 memory map?

This is the official "forum". You could ask your question either in a new Issue or new Discussion.


fix: bump pgadmin schema diff to 0.0.5

What kind of change does this PR introduce?
Bug fix https://github.com/supabase/cli/issues/369
What is the current behavior?
unable to diff with pgadmin
What is the new behavior?
updated pgadmin image to 0.0.5
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 25.767%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/db/diff/diff.go
0
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1276

Relevant Lines:
4952

💛  - Coveralls


Rework podman preflight checks/support

I noticed that the podman URL that crc uses is outdated (https://storage.googleapis.com/libpod-master-releases rather than https://github.com/containers/podman/releases/download/ ).
However, since podman will be shipped with the bundle, this URL should not be needed.
The podman preflight check is also disabled at the moment, but the podman binary from the bundle is currently not used.

Done in 1.26.0


Generators are no currently supported?

tsc definitely supports generators when targeting es6, but vs2015 still says that generators/yield aren't supported, which is annoying. Why?

Generators have an extremely non-trivial emit that requires rewriting your function into a state-machine. The emitted code is not at all canonical JavaScript. We're hoping to have generators, along with async/await, in in the version that follows 1.6.

I get that and currently trying to use babel: I first tsc --target es6 and then use babel to convert the generators into that state machine. This works, but when I open the .ts file in vs2015, I see that all these yeild things are underlined with red. My question was how to make vs2015 not consider yield as a syntax error.

Tools > Options
    Text Editor
        TypeScript
            Project
                ECMAScript version for files that are not part of a project:  ECMAScript 6

This didn't help. I'm using vs2015 community edition and have only a tsconfig.json (with target=es6), so when I open my .ts files, they become a part of a "virtual typescript project" - maybe that's why the setting didn't work.

@d180cf what version of TypeScript do you have installed? what is the error message text you are seeing? can you share a snapshot of the "virtual project" created?

It's a virtual tsconfig project - vs2015 doesn't allow to save it in any form.

Errors:
TS9001	Generators are not currently supported.
TS9000	'yield' expressions are not currently supported.
TS9000	'yield' expressions are not currently supported.
TS2488	Type must have a '[Symbol.iterator]()' method that returns an iterator.

In \Microsoft SDKs\TypeScript I found only 1.5

the roadmap says the Generators will be supported at 1.6, for now, current release is 1.5.4.
https://github.com/Microsoft/TypeScript/wiki/Roadmap

I see. Then can I somehow update my local \Microsoft SDKs\TypeScript to version 1.6?

The nightly builds may help, but I don't know how to do exactly, I just wait 1.6.
npm install -g typescript@next

@d180cf install the nightly TypeScript 1.6 and enable dev mode using typescript in your global node_modules folder.

It seems the errors have gone after that. Thanks! However I noticed, that the generator function (i.e. function * F()) is ruturning any, according to the language service from<EMAIL_ADDRESS>


Add custom field validators

Validate custom video input field and and custom admin input fields before save them

Validation for custom video fields is done.. Admin setting validation is missing


LibWeb: Fix infinite loop in Storage::internal_own_property_keys

Since Storage::item_value never returns an empty Optional, and since PlatformObject::is_supported_property_index only returns false when item_value returns an empty Optional, the loop in PlatformObject::internal_own_property_keys will never terminate when executed on a Storage instance.
This fix allows youtube.com to load successfully :^)

Looks good, but could you provide an in-tree test for this?

Is this not testable with pure HTML/JS?


Limit snippet typing bounds

VSCode Version: Version 0.10.11
Commit f291f4ad600767626b24a4b15816b04bee9a3049
Date 2016-03-11T16:19:03.130Z
Shell 0.35.6
Renderer 45.0.2454.85
Node 4.1.1
OS Version: Linux Mint 17.3 Cinnamon 64 bit.

Steps to Reproduce:

create a snippet that has (same) ids
use that snippet.
go to one of them, type something then delete. continue deleting beyond the starting position.
OR
go to one of them, type something then enter, it will continue to the next line, in all of the location markers.

result: it deletes text in all the locations, since it uses multi cursors but has no bounds. it also goes to next lines if pressing enter.
expected behaviour: limit the bounds. from starting position until end of the line.

fyi @jrieken

if you need more information, contact me here.

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


MacOSX OS.get_enviroment("PATH") and OS.execute() do not use correct env path, but use a a different version, thereby running an app from wrong path.

Tested versions
v4.3.stable.official [77dcf97d8]
System information
Mac OS X Catalina 10.15
Issue description
On Mac OSX, the Environment PATH is different when retrieving it using gdscript than from the BASH command line. This cause confusion if you are for example running OS.execute("which",["awk"], value, true, true) to locate an application to execute.  This issue doesn't appear on Linux using same commands.
To verify I copied a test version of /usr/bin/awk to /usr/local/bin/awk  and then used BASH commands followed by gdscript.
First tested from command line:
MacOSX Bash commands to determine shell and path
~$ echo $SHELL
/bin/bash
~$ echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:
~$ which awk
/usr/local/bin/awk

Now test with Godot
same commands using gdscript. PATH comes up different, even though the shell is BASH.
	print(OS.get_environment ("SHELL")) #/bin/bash
	print(OS.get_environment ("PATH")) #/usr/bin:/bin:/usr/sbin:/sbin
	var value=[]
	var err=OS.execute("which",["awk"], value, true, true)
	prints(err, value) #0 ["/usr/bin/awk\n"]

Steps to reproduce
see above
Minimal reproduction project (MRP)
na

This is expected behavior, macOS GUI apps do not use shell environment by default, and it's impossible to change PATH for the GUI apps (globally, app itself can change it), sandboxed apps distributed via App Store can't use it at all.
See https://github.com/godotengine/godot/pull/81266 (which implement workaround).

Will this be backported you think?


Bron–Kerbosch Algorithm (Graphs) in C, C++, Python and Java

Is your feature request related to a problem? Please describe.
Yes, my feature request is related to a problem. I would like to implement Bron–Kerbosch algorithm using C, C++, Python and Java languages.
The Bron–Kerbosch algorithm is an enumeration algorithm for finding maximal cliques in an undirected graph. It lists all subsets of vertices with the two properties that each pair of vertices in one of the listed subsets is connected by an edge, and no listed subset can have any additional vertices added to it while preserving its complete connectivity.
Describe the solution you'd like
I would like a solution that provides an implementation of the Bron–Kerbosch algorithm using C, C++, Python and Java languages.
I would like to work on this issue under SSOC 2023. Please assign it to me.

Assigned!
@Trisha-tech : C, C++, Python and Java

@Trisha-tech What is your status on this issue?


Fix CLI command and Improve Python readability

The previous Azure CLI command for obtaining the master key is being deprecated.
Python samples were not very readable. I improved the style (indentation, line breaks) for readability.

FYI @deborahc @moderakh

@berndverst - thank you for the contribution! The changes look good to me. Adding @southpolesteve  to take a look and help merge it in.

By the way, I assume some of this will change soon? I've been using azure-cosmos 4.0.0b6 which has a rather different SDK

Thanks @berndverst! We just shipped 4.0.0 today which is nearly the same as the beta. What you see on master is the latest.

Thanks, @berndverst! We did GA our v4 SDK this week which lives here https://github.com/Azure/azure-sdk-for-python. Further SDK development will happen in that repo. I'll be cleaning up this one soon and semi-archiving it.


Update to Xcode 8 class properties

Related:

https://github.com/NativeScript/ios-runtime-docs/pull/54
Tests for https://github.com/NativeScript/ios-runtime/pull/635

Requires Xcode 8

run ci


Allowing arguments to be passed to scripts executed by MockTestRunner

It looks like this is because setInput lives on mock-run, and not mock-test (which is called from the outer process).
Do you think it would make more sense if mock-test exposed an overload that accepted an env dictionary to be used when spawning the child process? That would achieve two things:

Avoids arg parsing code in target script. I'm thinking it may be easier (less code) and better for readability (avoids requiring an arg parsing module and/or interpreting positional parameters passed to the process).

Avoids quoting issues involved in passing command line args to child processes. When spawning a child process on Windows, Node applies quoting logic that (hopefully) matches up with how the target process parses it's own command line. Since this is for testing, I imagine it might be useful to test corner cases with special characters. If so, then avoiding the quoting/parsing altogether seems good - less likely to run into issues from that extra layer of translation.

By exposing an env dictionary overload, technically you could even just set INPUT_FOO directly from the outer script (without dirty-ing the outer process env). Another option would be to add a setInput function to mock-test, but I have concerns that having two setInput functions would be confusing for consumers.

I'd be ok with passing a dictionary to the run method. Avoiding parameter parsing on the target script's end is appealing, but I'd prefer to have a method to retrieve the "testScriptValues" rather than directly accessing the environment variables. The env vars is an un-scoped bag of "stuff" with no guarantee of avoiding name collisions, so wrapping this access would be cleaner.

Do we still need this? It seems like it could be useful, I think I agree with Eric that passing in a dictionary feels cleaner though.

I'm going to close. We'll look into changing how we do this with the new major version


update pip install line to use 'stdlib-list' instead

Clearly not a huge deal, but trying to remove a little confusion.
From the docs
I got "pip install stdlib_list".
But if one searches for it like this:
pip search stdlib_list

It yields nothing. That got me confused.
If instead you search for 'stdlib-list', you can see it:
pip search stdlib-list

Good catch. Thanks!


Auto-update sticks on "Scheduled" or "Running"

[x ] I have verified that I am on the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero
[ x] I am posting a single question, bug or feature request
[x ] I have included a descriptive subject of the problem
[x ] I am available for follow-up questions and testing

With reference to bug report: 4VMI4ZGN
When I do a biblatex export of one of my collections, and tick the keep updated button, the auto-export shows up where it should:

But it just stays at either "running" (as I've shown here) or, sometimes, "scheduled".
It's one of these really annoying issues where "it used to work", then I fiddled with some stuff (I think relating to the "Export unicode as plain-text latex command" options under the "Export" options menu, and then it never worked again.
I can run the export through Zotero by doing File > Export as normal, but it no longer automatically updates on changes.

:robot: this is your friendly neighborhood build bot announcing test build 5530 ("fixes #903").

Can you try 5530?

It works for me

Also work for me. THX

Yep. It all works fine now. Wow! Fastest turnaround ever! Thank you retorquere.

Only I and @blip-bloop can close issues; I keep issues open until I've merged the changes into the main development line. Tests on the merge are running and should drop as a new release in a few minutes. Thanks for your help guys, it's so important to get test feedback (and sorry for the disruption in your workflow).

:D thank you
On 6 Feb 2018 12:24 pm, "Emiliano Heyns"<EMAIL_ADDRESS>wrote:

Only I and @blip-bloop https://github.com/blip-bloop can close issues;
I keep issues open until I've merged the changes into the main development
line. Tests on the merge are running and should drop as a new release in a
few minutes. Thanks for your help guys, it's so important to get test
feedback (and sorry for the disruption in your workflow).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/903#issuecomment-363406721,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEiz1z2-IDgiLqrY7lAu0btaUWySta4wks5tSER4gaJpZM4R5156
.

@blip-bloop will also re-open issues if you comment on them :smile:


Serial plugin - Adjust buffer reading

if there are more changes, please open a new PR and do not reuse a closed PR


Clean up

@arjuhe Only a few errors left and fixing them makes things worse not better :)

Doesn't it sting when fixing things makes it worse. We will need to do a synchronous review for this one.

This is too big to practically review and now its out of date. I'll split this into smaller cunks instead.


Create a simple calculator as a web app.

I am not familiar with modern development languages. I want to create a simple web application that starts out as a simple calculator. What language and frameworks would work best for this. I am looking for something simple to maintain and enhance. Style the calculator to mimic the iPhone calculator.

To get started with GitHub Copilot Workspace Select the Open in Workspace button for this issue. You can generate a plan, implement the suggested plan, debug the code in a Codespace and more.


fix: change error proptype from string to object

Description of the Changes
change the error proptype from string to object in NetworkWalletButton
Checklist

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

:tada: This PR is included in version 1.8.0-dev.12 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Macro definition of snprintf conflicts with Standa rd Library function declaration

From the looks of it this fails with Microsoft Visual Studio 14.0

We're keeping track of Visual Studio problems over in #182.


How to change language without restart the app?

I want to change the app's language without restart the app. Then I notice this library. I have already saw the sample app. But because I'm new in WinUI, so I didn't find the way to change the language in that sample app. Could any one please tell me the way to change the language? You can offer a document or give me a functhion. Any help are appreciated.

Hi @sciencekiller!
You can get the entire code from this repo.
I'd recommend cloning the repo and run the sample app so you can see how it's implemented.
Let me know if you need further help.

I'm closing this but let me know if you have any questions.


Debug Failure. Did not expect JsxSelfClosingElement to have an Identifier in its trivia

From 3.1.3
Error processing request. Debug Failure. Did not expect JsxSelfClosingElement to have an Identifier in its trivia
Error: Debug Failure. Did not expect JsxSelfClosingElement to have an Identifier in its trivia
    at addSyntheticNodes (tsserver.js:113841:30)
    at createChildren (tsserver.js:113830:9)
    at NodeObject.getChildren (tsserver.js:113774:56)
    at getTokenAtPositionWorker (tsserver.js:91057:43)
    at Object.getTokenAtPosition (tsserver.js:91049:16)
    at Object.getRangeOfEnclosingComment (tsserver.js:104660:68)
    at isInComment (tsserver.js:91368:30)
    at isInReferenceCommentWorker (tsserver.js:91485:21)
    at Object.isInReferenceComment (tsserver.js:91477:16)
    at Object.getCompletionsAtPosition (tsserver.js:93544:20)
    at Object.getCompletionsAtPosition (tsserver.js:114818:35)
    at IOSession.Session.getCompletions (tsserver.js:122608:64)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:121665:61)
    at tsserver.js:123086:88
    at IOSession.Session.executeWithRequestId (tsserver.js:123077:28)
    at IOSession.Session.executeCommand (tsserver.js:123086:33)
    at IOSession.Session.onMessage (tsserver.js:123106:35)
    at Interface.<anonymous> (tsserver.js:124369:27)
    at emitOne (events.js:116:13)
    at Interface.emit (events.js:211:7)
    at Interface._onLine (readline.js:282:10)
    at Interface._normalWrite (readline.js:424:12)
    at Socket.ondata (readline.js:141:10)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)

Command was completionInfo.

Looks like @andy-ms may have fixed this? https://github.com/Microsoft/TypeScript/issues/25487

All I did was add better error reporting so it would show us the file contents on error. Though it shouldn't show up in telemetry.

Duplicate of #25487


snet: fuller error reporting to app, with filtering

Currently an app that uses snet will, when an SCMP error reply is received, be passed back the L4 scmp header as an OpError. While most scmp errors should kill the connection, there are a few exceptions:

revocation
oversize packet
expired HOF
It's application-specific whether the above errors should be passed back to the app or not, depending on its level of sophistication and control. To make this generally useful, an app should be able to mask non-fatal SCMP errors, to allow it to choose which ones to handle. E.g. an app that's letting snet handle path selection probably doesn't need to receive revocation scmp errors.

There is another case, such as with QUIC/SCION, where a library is using the interfaces that snet provides without being SCION-aware. If an application using such a library wants to manage its own paths, a wrapper around snet should be used, which allows the application to specify a callback to be used when certain events happen (e..g a revocation is received). This allows a clean interface combined with flexibility.

Also, the scmp payload should be exposed to the app, not just the l4 header.

Applications can now customize how they want work with SCMP via the snet SCMP handler:
https://github.com/scionproto/scion/blob/2f106c5b1e33b6c9e7d3342d81ac049ce6b16858/go/lib/snet/dispatcher.go#L66-L67


Why a try catch in the thumbnail.php?

Was wondering what the reason was for the throw in the thumbnail.php if there is an error?
Its a bit of a show stopper. If you try to make multiple images from a list of mp4s, and there is an error, eg file name incorrect, or is a dead link, the function stops. Would be good to have some set up to allow that to just return an error?
Best

@saffabook yeah that was good idea. Bit occupied these day, would be good if we see a PR for this.


Replace HttpTryFrom with std::convert::TryFrom

Would it be possible to implement TryFrom  for all types that implement HttpTryFrom without breaking backward compatibility, using conditional compilation ?
https://dev.to/jeikabu/rust-tryfrom-and-conditional-compilation-46fe

@lovasoa it's possible! We're just moving towards 0.2 already, and in that branch, we don't need to support the older compiler. See https://github.com/hyperium/http/pull/308#issuecomment-497448119

Completed in the 0.2.x branch.


Drop unused docs-linux task on Cirrus

@godofredoc @tvolkert @Hixie

Running the shard itself would be good, just to get people feedback about docs errors (a lot of contributions we get by people who can't use LUCI before getting review are docs-related). But we can get rid of the credentials part.

test-exempt: this is a test.

Ahh, I was falsely under the impression that we were running this on LUCI presubmit - we only run it on LUCI postsubmit.

Ahh, I was falsely under the impression that we were running this on LUCI presubmit - we only run it on LUCI postsubmit.

we do run it on pre-submit: https://ci.chromium.org/p/flutter/builders/try/Linux docs
it didn't trigger on this PR because none of hte run_if globs matched the file diff: https://github.com/flutter/flutter/blob/master/dev/try_builders.json#L39

So should we just drop the cirrus task after all?

The plan is to not run any LUCI shards for non-team-members until a team-member has reviewed the PR. That's why we want Cirrus shards at all.


Add prefix to all objects when spawning new objects in engine

It should be fine to do so. I wonder if we need to do this in engine.spawn_object where the object id can be obj.__class__.__name__ + uuid.

relates to #659

A more aggresive way is to default the name of object to be:
self.id = self.class_name + uuid4()

But I am afraid it will harm the replay and record system.

Just try it. If the test is passed, then it is fine


add ssh keys for Jonathan Newman

@jonathannewman - I noticed this PR has been open for a while. If it's still valid, please rebase.

I can't remember what I was trying to do back in August where I needed these keys.


Config reference in docs is unreadable

Also missing ToC

We want reference to be included in common docs deploying pipeline and to have consistent formatting with the rest of the doc to make further improvements
We have three types of references

Python references - most important is context(ctx) reference and second one is config reference
examples:
https://flask.palletsprojects.com/en/3.0.x/api/
https://docs.djangoproject.com/en/4.2/ref/
CLI reference
examples:
https://docs.docker.com/engine/reference/commandline/cli/
YAML reference for dipdup.yaml
https://docs.docker.com/compose/compose-file/compose-file-v3/#service-configuration-reference

Key features for all references:

Frontend should be generated from intermediate format(output of tools such as Sphinx and https://github.com/cloudflare/doca)
Support for current search
Support cross-referencing and content hierarchy

They are pretty nice now.


Make cluster scaling retry threshold a user configurable option.

A new configuration parameter has been added to allow users to
configure the scaling retry threshold, thus determining the number
of attempts and failures replicator will attempt to scale the
cluster out before disabling scaling. The default has been set to
2.
Closes #77

No changes has been made to the README as when this change is merged I will add the following page to the Replicator wiki and update the README to point to this page for the agent configuration:
Agent Configuration
The Replicator agent has various configuration options that can be specified via the command-line or via configuration files. All of the configuration options are completely optional and you can run Replicator with its default configuration. Defaults are specified with their descriptions.
Configuration precedence is evaluated in the following order:

Command line arguments
Configuration files

Command Line Flags

-aws-region The AWS region in which the cluster is running. If no region is specified, Replicator attempts to dynamically determine the region.

-cluster-autoscaling-group The name of the AWS autoscaling group that contains the worker nodes. This should be a separate ASG from the one containing the server nodes.

-cluster-identifier A human readable cluster name to allow operators to quickly identify which cluster is alerting.

-cluster-max-size Indicates the maximum number of worker nodes allowed in the cluster. The default is 10.

-cluster-min-size Indicates the minimum number of worker nodes allowed in the cluster. The default is 5.

-cluster-node-fault-tolerance The number of worker nodes the cluster can tolerate losing while still maintaining sufficient operation capacity. This is used by the scaling algorithm when calculating allowed capacity consumption. The default is 1.

-cluster-retry-threshold Replicator fully verifies cluster scale-out by confirming the node joins the cluster. If it does not join after a certain period the actioned is marked as failed. This retry is the number of times Replicator will attempt to scale the cluster with new instances.

-cluster-scaling-cool-down The number of seconds Replicator will wait between triggering cluster scaling actions. The default is 600.

-cluster-scaling-enabled Indicates whether the daemon should perform cluster scaling actions. If disabled, the actions that would have been taken will be reported in the logs but skipped.

-cluster-scaling-uid The cluster UID is an identifier which represents a run book entry which allows operators and support to quickly work through resolution steps.

-config The path to either a single config file or a directory of config files to use for configuring the Replicator agent. Replicator processes configuration files in lexicographic order.

-consul This is the address of the Consul agent. By default, this is localhost:8500, which is the default bind and port for a local Consul agent. It is not recommended that you communicate directly with a Consul server, and instead communicate with the local Consul agent. There are many reasons for this, most importantly the Consul agent is able to multiplex connections to the Consul server and reduce the number of open HTTP connections. Additionally, it provides a "well-known" IP address for which clients can connect.

-consul-key-location The Consul Key/Value Store location where Replicator will look for job scaling policies. By default, this is replicator/config/jobs.

-consul-token The Consul ACL token to use when communicating with an ACL protected Consul cluster.

-dev Start the Replicator agent in development mode. This runs the Replicator agent with a configuration which is ideal for development or local testing.

-job-scaling-enabled Indicates whether the daemon should perform job scaling actions. If disabled, the actions that would have been taken will be reported in the logs but skipped.

-log-level Specify the verbosity level of Replicator's logs. The default is INFO.

-nomad The address and port Replicator will use when making connections to the Nomad API. By default, this http://localhost:4646, which is the default bind and port for a local Nomad server.

-pagerduty-service-key The PagerDuty integration key which has been setup to allow replicator to send events.

-scaling-interval The time period in seconds between Replicator check runs. The default is 10.

-statsd-address Specifies the address of a StatsD server to forward metrics to and should include the port.

Configuration Files
Replicator uses the HashiCorp Configuration Language for configuration files. By proxy, this means the configuration is also JSON compatible. If a directory of configuration files is passed, Replicator will parse these in lexical order. Replicator can also reload its configuration when it receives the SIGHUP signal.
Configuration Key Reference

aws_region (string: "") The AWS region in which the cluster is running. If no region is specified, Replicator attempts to dynamically determine the region.

consul (string: "localhost:8500") This is the address of the Consul agent. By default, this is localhost:8500, which is the default bind and port for a local Consul agent. It is not recommended that you communicate directly with a Consul server, and instead communicate with the local Consul agent. There are many reasons for this, most importantly the Consul agent is able to multiplex connections to the Consul server and reduce the number of open HTTP connections. Additionally, it provides a "well-known" IP address for which clients can connect.

nomad (string "http://localhost:4646") The address and port Replicator will use when making connections to the Nomad API. Ideally in a full cluster setup this would be a DNS endpoint which load balances requests across the quorum servers.

log_level (string "debug") Specify the verbosity level of Replicator's logs.

scaling_interval (int 10) The time period in seconds between Replicator check runs.

cluster_scaling Configures Replicators cluster scaling ability and has the following keys:

autoscaling_group (string "") The name of the AWS autoscaling group that contains the worker nodes. This should be a separate ASG from the one containing the server nodes.
cool_down (int 600) The number of seconds Replicator will wait after a scaling action before allowing another.
enabled (bool false) Indicates whether the daemon should perform scaling actions. If disabled, the actions that would have been taken will be reported in the logs.
max_size (int 5) Indicates the maximum number of worker nodes allowed in the cluster.
min_size (int 3) Indicates the minimum number of worker nodes allowed in the cluster.
retry_threshold (int 2) Replicator fully verifies cluster scale-out by confirming the node joins the cluster. If it does not join after a certain period the actioned is marked as failed. This retry is the number of times Replicator will attempt to scale the cluster with new instances.

job_scaling

consul_key_location (string "replicator/config/jobs") The Consul Key/Value Store location where Replicator will look for job scaling policies.
consul_token (string "") The Consul ACL token to use when communicating with an ACL protected Consul cluster.
enabled (bool false) Indicates whether the daemon should perform job scaling actions. If disabled, the actions that would have been taken will be reported in the logs but skipped.

telemetry This is a nested object that configures where Replicator sends its runtime telemetry, and contains the following keys:

statsd_address (string "") Specifies the address of a StatsD server to forward metrics to and should include the port.

notification This configures Replicators notifications backends and has the following keys:

cluster_scaling_uid (string "") The cluster UID is an identifier which represents a run book entry which allows operators and support to quickly work through resolution steps.
cluster_identifier (string "") A human readable cluster name to allow operators to quickly identify which cluster is alerting.
pagerduty_service_key (string "") The PagerDuty integration key which has been setup to allow replicator to send events.

Examples Configuration File
consul           = "consul.systems"
nomad            = "http://nomad.systems:4646"
aws_region       = "us-east-1"
log_level        = "info"
scaling_interval = 10

cluster_scaling {
  enabled              = true
  max_size             = 100
  min_size             = 80
  cool_down            = 900
  node_fault_tolerance = 10
  autoscaling_group    = "container-agent-dev"
}

job_scaling {
  consul_key_location = "core-engineering/scaling-docs"
  consul_token        = "278F9E37-8322-4EDC-AFDC-748D116B3DCE"
  enabled             = true
}

telemetry {
  statsd_address = "<IP_ADDRESS>:8125"
}

notification {
  cluster_scaling_uid   = "els1"
  cluster_identifier    = "core-prod"
  pagerduty_service_key = "xxxxxxxx"
}


NickAkhmetov / HMP-99 / Improve user-passed marker gene handling, fix spatial anndata view connection

This PR:

Fixes generation of views for anndata with spatial views to make spatial views properly connect to passed gnees
Adds a best-effort attempt to map passed user parameters to Ensembl ID's for the anndata encoding version currently supported by our pipeline

Support for the 0.2.0 encoding used in newer versions of the standard to come at a later date; documented in HMP-137

Bumps the library version to 0.0.11

With these changes, providing HUGO symbols in URL parameters for anndata files will now load the correct view:

Fixes https://github.com/hubmapconsortium/portal-ui/issues/2937

@ilan-gold should you be looped in on changes here?


Merge installer and upgrader packages

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #833
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Fixes cloud-config file was not changed during cluster upgrade #833

/retest

/retest
Seems like AWS was flaky last night

/test pull-kubeone-license-validation

/test pull-kubeone-e2e-aws-conformance-1.18

/test pull-kubeone-e2e-aws-conformance-1.18

/retest


report-uri sample rate

One thing about CSP that I've always found extremely dangerous is it's ability to generate an enormous amount of traffic for a reporting endpoint if you hit browser bugs or use a misconfigured policy. This was a very real issue for us and something we've mitigated using a patch to only send a percentage of the reports to the reporting endpoint. We tune this number up and down based on the risk when we roll out an updated policy.
My question to the other users of secureheaders is whether or not this configuration option would be valuable to you? If so, I'm happy to open a PR with our base implementation and we can expand on it from there. To give you a bit of an idea around the implementation:
# initializer
config.csp_report_only = {
  # .. snip
  report_uri: %w(https://report-uri.io/example-csp-report-only)
  sample_rate: 0.3 # only send 30% of violations
}

The above configuration would then result in the report-uri directive for the policy only being appended 30% of the time and the remaining 70% would not have the report-uri directive at all.

I think this would be a welcomed addition that I am just researching how to accomplish over at @ Square.

Both us and GitHub are now running 5.2 which supports CSP out of the box. I know we have replaced majority of secure_headers with framework defaults (@oreoshake will have to yay/nay for GitHub) so I probably won't be adding this seeing how we don't really use it anymore.
In rails 5.2 we handle the sampling in the initializer
Rails.application.config.content_security_policy do |policy|
  # .. snip
  policy.report_uri(proc { "https://collector" if Random.rand(100) < 2 })
end

This doesn't work before 5.2.2 though as we had to file rails/rails#34200 in order to have proc work with the CSP methods.

(@oreoshake will have to yay/nay for GitHub)

Nay but it's certainly on our backlog. I have been trying to pass ownership of this repo on to someone else but I plan on archiving this repo in the not to far future. I hope to see someone fork this project and become the new home.
This library still has value for out of date applications or non-rails applications, neither of which I support anymore. I have a strong policy against maintaining code you don't use and soon I won't be using secure_headers.


Unable to parse version spec: =>96

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
pixi init --import conda/environment-test-3.10.yml

Issue description
I wanted to try contributing something to bokeh, so I cloned their repo, and ran the above command in their repo
I get
$ pixi init --import conda/environment-test-3.10.yml
0: at line 1, in Tag:
=>96
 ^

1: at line 1, in Alt:
=>96
 ^

2: at line 1, in version:
=>96
 ^

  × Unable to parse version spec: =>96

Expected behavior
I don't really know, I'm new to pixi, first time trying it out

It means the environment file contains a requirement with a constraint =>96 which is not a valid version constraint. Most likely >=96 is ment.
You could create a PR to environment.yml because its definitely not correct!

thanks! indeed, fixing that, it builds. I'll report upstream then!


Remove deps/ from git ignore file

The deps folder contains clog which is a mandatory third-party lib of cpuinfo and should therefore not be ignored. Also updated Bazel version.

@malfet Can you have a look?

@malfet Can you approve?

The deps is intentionally in .gitignore to avoid committing clog build objects and artifacts when the latter is configured/built within cpuinfo tree. Whenever clog is modified (extremely rare), it is added to commit via git add -f ....


[Bug]: Missing meta data with symbol in Semantic API when retrieving the symbol at the cursor position

Description
When we keep the cursor position and try to retrieve the symbol we get type-symbol instead of the wrapper struct. We can observe this in two scenarios

Params in function type

annotation record {int x;} annot on parameter, field;

type Foo int;

public function main() {
    function (@annot {x: 0} <c1>Foo) f;
}

Here when we call the symbol at <c1>, we get the Foo type-ref type symbol, instead of the param symbol. THerefore, we are not getting any information in @annot {x: 0}
3. Tuple members
annotation record {int x;} annot on parameter, field;

type Bar string;

type TupleType [@annot {x: 0} <c2>Bar];

The same behavior happens in <c2>
We need to decide on which symbol we should return when calling symbol() API  and what information we need to expose without breaking the LS features
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Related issues:

https://github.com/ballerina-platform/ballerina-lang/issues/39263


No workspaces found with name={} in subscription={}

Hi Guys,
I'm having the following error on the 01-Getting_Started_with_Azure_ML lab.
WorkspaceException: WorkspaceException:
Message: No workspaces found with name=dp-100-mlstudio in subscription=""
InnerException None
ErrorResponse
{
"error": {
"message": "No workspaces found with name=dp-100-mlstudio in subscription=""
}
}

Having this exact same problem!!

The problem seems to be case sensitivity. I had called my workspace "aml-DP100", but the error I got stated "No workspaces found with name=aml-dp100".
A hack to get around this is to use Workspace.get
ws = Workspace.get(subscription_id= "your_sub_id",                    resource_group = "your_resource_group",                    name = "aml-DP100")
The config.json file I downloaded locally was correct, so I could copy all the details from there. I don't know yet if the problem is in the compute instance OR with Workspace.from_config() function.

Hi @ikeaney for sure is something related to the case sensitivity. I recreate my workspace in lowercase and everything works fine.


Consider uploading to https://spark-packages.org/

https://spark-packages.org/

https://spark-packages.org/staging?id=3630


python310Packages.yalexs-ble: 1.12.5 -> 1.12.7

Diff: https://github.com/bdraco/yalexs-ble/compare/refs/tags/v1.12.5...v1.12.7
Changelog: https://github.com/bdraco/yalexs-ble/blob/v1.12.7/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.05 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

home-assistant-component-tests.august
home-assistant-component-tests.yalexs_ble
python310Packages.yalexs-ble
python311Packages.yalexs-ble


System.IO.Pipelines support [POC] [WIP]

This PR adds System.IO.Pipelines support. I expected this to be a performance improvement but the performance tests i did showed i was wrong, as the performance is almost identical:
This table shows the time it takes to upload 20 files of the specified size (average of 10 runs)

File Size
Pipelines
Streams

1KB
1047,2ms
944,9ms

10KB
1183,3ms
1128,7ms

100KB
1505,7ms
1366,8ms

1MB
1721ms
1656,7ms

10MB
4723,2ms
4850,7ms

Because it doesnt really give a performance improvement, i made it an opt-in option named EnablePipelines
To use the pipelines feature, the ITusStore has to implement ITusPipelineStore
The only thing that currently doesnt work is handling client disconnects.
What is also interesting is i also tried different buffer implementations:
Tested with 1 Client, 20 Files, 10MB, 3 runs

Run #
Streams
Pipelines (Without buffer)
Pipelines (BufferPool)
Pipelines (FileStream buffer)

1
5265ms
8391ms
5485ms
4813ms

2
5110ms
8513ms
4883ms
4706ms

3
4979ms
8978ms
4757ms
4738ms

The reason why the pipelines without a buffer implementation is so slow is because of the kestrel buffer size of only 4096, which results in unneccesary many IO operations.
The Pipelines version should use less memory and less GC collections, but i didnt do any tests yet to confirm that.

This looks very promising! Thank you very much! I honestly thought that the time it took would be far worse with pipelines, given that it's not a consecutive memory buffer.
I would love to run some benchmarks on this when it can handle client disconnects and see how it holds up against the current implementation. There is a performance app in the repo (tusdotnet.performance) that can be used to measure the performance in a more "real" way by spinning up multiple clients and having them upload a file.
Is the code for your benchmarks available somewhere? It would be nice to see the different implementations and how they differ. Is Pipelines (BufferPool)  using ArrayPool.Shared or something else? Pipelines (FileStream buffer) seems to have very good performance (timewise) but I'm guessing that it will be an issue that it uses the disk as buffer, since we want to use buffers to reduce disk I/O.
I have added some comments to your PR, don't take them to seriously. :) They don't need to be fixed right now, it's just thoughts that I had when reading the code and things that we should probably change before releasing this to the public. Feel free to correct me if I'm wrong in any of it.

I would love to run some benchmarks on this when it can handle client disconnects and see how it holds up against the current implementation. There is a performance app in the repo (tusdotnet.performance) that can be used to measure the performance in a more "real" way by spinning up multiple clients and having them upload a file.

I actually used a modified version of tusdotnet.performance to do the benchmarks.😄  You can already run this kind of benchmark, because the client disconnect issue only occurrs if the client disconnects unexpectedly during a read operation (which results in an unhandled exception). If the client disconnect occurrs at the end of a read operation (like tusdotnet.performance simulates) then it works completely fine.

Is the code for your benchmarks available somewhere?

Its basically just tusdotnet.performance wrapped in a StopWatch:
            Stopwatch stopwatch = new Stopwatch();
            Dictionary<int, List<int>> ms = new Dictionary<int, List<int>>();

            for (int run = 0; run < 10; run++)
            {
                for (int j = 0; j <= 4; j++)
                {
                    // increase the filesize in powers of 10
                    var filesize = (int)(1_000 * Math.Pow(10, j));
                    Console.WriteLine("Testing filesize: " + filesize);

                    var file = new byte[filesize];
                    //_random.NextBytes(file);

                    var halfFileSize = (int)Math.Floor((decimal)file.Length / 2);

                    var clients = new List<Task>(NUMBER_OF_CLIENTS);
                    stopwatch.Restart();
                    for (int k = 0; k < NUMBER_OF_CLIENTS; k++)
                    {
                        clients.Add(Task.Run(async () =>
                        {
                            for (int i = 0; i < NUMBER_OF_FILES_TO_UPLOAD; i++)
                            {
                            // Create file
                            var response = await httpClient.SendAsync(GetCreateFileRequest(file)).ConfigureAwait(false);
                                response.EnsureSuccessStatusCode();

                                var fileLocation = response.Headers.Location;

                            // Send first half of file to emulate a disconnect
                            response = await httpClient.SendAsync(GetWriteFileRequest(file, 0, halfFileSize, fileLocation)).ConfigureAwait(false);
                                response.EnsureSuccessStatusCode();

                            // Get the file info to continue the upload
                            response = await httpClient.SendAsync(CreateTusResumableRequest(HttpMethod.Head, fileLocation)).ConfigureAwait(false);
                                response.EnsureSuccessStatusCode();

                            // Upload second half of file
                            var uploadOffset = int.Parse(response.Headers.GetValues("Upload-Offset").First());
                                response = await httpClient.SendAsync(GetWriteFileRequest(file, uploadOffset, file.Length - uploadOffset, fileLocation)).ConfigureAwait(false);
                                response.EnsureSuccessStatusCode();
                            }
                        }));
                    }
                    await Task.WhenAll(clients).ConfigureAwait(false);
                    stopwatch.Stop();
                    Console.WriteLine($"Elapsed time for {filesize} bytes: {stopwatch.Elapsed} ({stopwatch.ElapsedMilliseconds}ms)");
                }
            }

It would be nice to see the different implementations and how they differ. Is Pipelines (BufferPool) using ArrayPool.Shared or something else?

The implementation of "Pipelines (FileStream)" is the current implementation used in the PR.
The implementation of "Pipelines (BufferPool)" is these commentend out lines of the PR:
https://github.com/SnGmng/tusdotnet/blob/7e293f1560e8b688559368b57b545965e05401fd/Source/tusdotnet/Stores/TusDiskStore.cs#L156-L171
It basically uses the same BufferPool that the Stream implementation uses.

Pipelines (FileStream buffer) seems to have very good performance (timewise)

I dont think it even performs better because if you look at the 3rd run, the time is almost exactly the same as using BufferPool (~4700ms). Averaged over 10 runs, there is basically no difference in performance between BufferPool and FileStreams buffer.

but I'm guessing that it will be an issue that it uses the disk as buffer, since we want to use buffers to reduce disk I/O.

It doesnt use the disk as a buffer, it uses FileStreams own buffer which unfortunately is a byte[] (see my comment reply)

Pardon the very late reply here, I've been swamped the last couple of weeks.
I think you came to the same conclusion as I did earlier :) Basically to reduce memory usage etc we need to read as small chunks as possible and save it in some way (PipeReader is a good implementation here) but at the same time we need a large buffer to write the data in an efficient way. Not an easy thing to solve!
I put together a POC for pipelines just to play around with it myself to get a better understanding. https://github.com/tusdotnet/tusdotnet/tree/POC/pipelines
The POC was inspired by your work and adds support for user disconnects. I haven't done any serious benchmarks to see if the file writes are slow but I would think that they are as the code now needs to context switch between writing the file and running our code.
Looking back at the original PR I would think that the issue was the early versions of the TusDiskStore read data and then directly wrote it to disk (repeat from 1 over and over until the request was done). This would use a lot of CPU as described in the PR. I'm thinking that changing to Pipelines will optimize the CPU used so there might not be an issue with how files are written? What do you think?
If there really is an issue with file buffering I guess we could add some kind of "hard" pool which never recycles and have say 10 large arrays ready. Fill the pipereader until we are ready to write the file -> wait for a large array to be free -> copy pipereader content to the array -> write to disk -> return array to pool. Not sure if it's worth the extra effort though?

@SnGmng After doing some more research and testing of your code I now agree that this is the way forward :) I'll merge this into a dev branch and do some minor fixes before merging it to master (e.g. writing tests, move to .NET Core 3.1 etc).
Thank you for the PR! <3


I got the esp-fs-webserver working using aioweb

I made work the https://github.com/cotestatnt/esp-fs-webserver using your framework. Would you be interested in this code?
Also I'd like to have this functionality in a different file so it is in its own module, that way it doesn't clutter the main code and I can easily disable it. What would be the best way to do this?
BTW big thanks! This is the best web server for the esp8266 by far and every project out there should use it!

Hello @aguaviva,
is your port of the esp-fs-webserver the pull request that you made here?
I'm very interested in it. If it would work it would be a big achievement.
Did you continue your work on it?
How did you come to find that micropython-aioweb is the best web server? Which ones did you try out / compare to?
I'm currently exploring network functionality on the Winner w600. This port has increased it's capabilities immensely in the last weeks (heap memory is now at > 100K for example, webrepl is functional,....).
It is similar to the 8266 in many respects (WIFI on one core, FreeRTOS).
I'm searching for the optimal webserver for it, that allows to be used asynchronously, so that some robot-controlling stuff can be running in parallel without using threads.

Got your pull request running. I can edit .htm files now, and after making slight changes in edit, also .py files.
Impressing stuff, server is running quite solidly. I will study it's code thoroughly.

Awesome, it is ages I don't touch that code, good to know it is helping :)

Not even a year, actually.
I was as enthusiastic now as you then, it seems. Great looking website and impressing functionality!
It ran quite solidly for half a day here, until I shut it down.
A number of questions appeared:
First I saw I cannot edit python files. That I was able to enable by slight changes in edit.htm.
Now such edit is possible, but there is no syntax highlighting.
In your pull request you have mode-html.js.gz and mode-json.js.gz in subdirectory edit. Seems to me that these two
are taken for editing in syntax-highlighting modes.
As the ace.js is taken preferrably from cloudflare, isn't that possible with the above (and more) syntax files as well?
I might add a mode-python.js.gz. Didn't try that so far.
More thoughts (no need to answer, but your comments are appreciated, of course)

Did you think about using a more compact js editor like Codemirror?
Is there a Javascript module that displays the files on the host computer in the same way like those on the device?
How about adding a WebRepl to the whole thing?

Did you try more MP web frameworks? If yes, which ones with what results?

I just made a small contribution by merging two existing projects:
1- one is this webserver
2- https://github.com/me-no-dev/ESPAsyncWebServer/find/master
but I am glad it helped you and that you are thinking about making some improvements, that is the spirit of OS :)

Exactly, thank you.

I'm a little confused. How is this micropython project being used in - https://github.com/cotestatnt/esp-fs-webserver?

https://github.com/cotestatnt/esp-fs-webserver
is a project mainly of javascript.
There is the ACE web editor and the file browser (both written in javascript, available as pre-build libraries, minimized and gzipped) and a nice gui html page. What was needed is glueing this together - both need info of the file system, and the file contents and send commands for file changes and creation/deletion etc.. This was provided to the HTML/Javascript originally via a lot of server handler code and is now provided by this Micropython aioweb via websocket.

Any updates on integrating my code as a sample?


Store kernel info into ipynb only when saving

For #13755

Codecov Report

Merging #13787 into main will increase coverage by 0.02%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main   #13787      +/-   ##
==========================================
+ Coverage   59.88%   59.90%   +0.02%
==========================================
  Files         678      682       +4
  Lines       37867    37933      +66
  Branches     5458     5460       +2
==========================================
+ Hits        22675    22724      +49
+ Misses      14034    14033       -1
- Partials     1158     1176      +18

Impacted Files
Coverage Δ

src/client/datascience/notebook/helpers/helpers.ts
41.00% <50.00%> (+1.58%)
:arrow_up:

src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/platform.ts
56.00% <0.00%> (-8.00%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/logging/levels.ts
61.11% <0.00%> (ø)

src/client/logging/logger.ts
62.74% <0.00%> (ø)

src/client/logging/formatters.ts
53.57% <0.00%> (ø)

src/client/logging/transports.ts
65.11% <0.00%> (ø)

... and 14 more

Continue to review full report at Codecov.

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


List of speakers projection problems

Create new Agenda item
Create new projector for list of speakers
Project list of speakers

Result: List of speakers is empty; Subtilte contains "0 speakers"
Expected: Show speaker count only if >0

Add Speaker
Start and stop

Result: The speaker remains in the list even though the setting "Number of last speakers to be shown on the projector" ist set to 0.
Expected: List should be empty.

Issue need to be reopened, because the last speaker on the slide of List of speakers are still visible after the speech is stopped. The user is only grayed ou, but still visible.

Reproduction:

open meeting
open agenda
create a new a agenda item by clicking on the plus-icon.
project the new agenda item to standardprojector by clicking on the camera icon in the new agenda item line.
open the autopilot and add some users . at least two - to the speaker list.
open projector
create a list of speakers projector. open it. click on current list of speakers and click on the slide icon.
now go back to the autopilot and start and stop a speech
head back to the list of speakers projector. a grayed out user should appear.

Expected behavior: If the current speaker is stopped, he will be deleted from the list of speakers and is not visible anymore.

With the way it is displayed this doesn't seem to be a loading error to me
When looking into it the code, the list of speakers slide looks like this:

list of all past speakers (grey)
current speaker (with mic icon)
list of the next speakers (as a list with row numbers)

This "bug" seems to be in line with that
Could it be that this is just not supposed to show for the current list of speakers?
Or is this actually supposed to be there (in which case I've noticed that the slide is not always showing all of the past speakers)?

Yes, I've meant the current list of speaker in the projector. There the grayed out last speakers should not be visible like OS3 handles this.
Does this answers you questions? :)

@MSoeb There is a "Number of last speakers to be shown on the projector". Could you check if this is set to "0"?
I can't replicate the issue with that setting set to "0"


[Fabric 1.17.1] Continuous loading screen

Enabling this mod make the loading screen continously loading (when it finishes loading it restarts).
Log: https://pastebin.com/ZXSPESKu

This is a known incompatibility with Fabric Capes.

This will be fixed in the next version of Fabric Capes


Support for service in Frankfort

To support a NLC instance in Frankfurt with apikey:

I've added a line in the .env file and commented the password line
NATURAL_LANGUAGE_CLASSIFIER_USERNAME=apikey
/#/ NATURAL_LANGUAGE_CLASSIFIER_PASSWORD=<add_NLC_password>
NATURAL_LANGUAGE_CLASSIFIER_IAM_APIKEY='xxxxxxxxx....xxx'
NATURAL_LANGUAGE_CLASSIFIER_URL='https://gateway-fra.watsonplatform.net/natural-language-classifier/api'

I've modified the welcome.py file (the line with  the url)

and

Not sure it's enough, but at least my credentials are recognised .
As the model is not trained yet , I still have an error :

Hi Thank you !
I'll be patient !

@PhilippeComte Is this still an issue for you?

No. Thanks for your help .


Fix an issue where nested ScrollViews would not be detected properly

As the title implies, this PR fixes an issue where if you have the following setup:
ScrollView {
    Text("Item 1")
    ScrollView {
        Text("Item 1")
    }
    .introspectScrollView { scrollView in
        // scrollView contains a reference to the outer ScrollView
    }
}

the outer ScrollView would always overshadow the inner. This was due to the internal code for looking up the ScrollView using a depth-first search instead of breadth first - causing it to skip over a potentially matching sibling in the process.
Let me know if there's anything I missed, or should add!

Thanks a lot for this PR! 🎉
Looks great so far, could you add a test for macOS too?
We also require a changelog entry for every PR. Please merge the latest master branch into the PR and add a line to the CHANGELOG.md file under the master section,, describing the fix.
Once that's done, I'll be happy to merge 👍

@SplittyDev Thank you for the review! I've updated the PR with the latest changes from master, added tests for macOS, and written a changelog entry 👍🏻

@simba909 we just merged the new Github CI integration into this branch and sadly the macOS test for nestedScrollView is failing with the following message:
✗ testNestedScrollView, XCTAssertNotEqual failed: ("<SwiftUI.HostingScrollView: 0x7fa4e1116000>") is equal to ("<SwiftUI.HostingScrollView: 0x7fa4e1116000>")

Which suggests that the code doesn't work properly on macOS.
Could you look into this?

@SplittyDev Absolutely, I'll have a look!

Alright this should be good to go now, turns out that the behavior on macOS 10.15 matches that of iOS 13 (which makes sense I guess) so I needed to change the way that NSScrollViews are found on 10.15 too to make it work in the case of nested views. The tests seem to be passing correctly now, both for Big Sur and Catalina 🎉


Labels overlapping prefilled content in forms

I'm having issues in form : when i'm binding my inputs to an asynchron loaded data, the label are overlapping the values.
It seems to be a known issue. At first, I fixed it by adding 'active' class to the form labels.
It worked well until I add a select directive to the form.
Calling Materialize.updateTextFields(); could help, but I don't really know how to get the Materialize object in my component (need some webpack configuration ?).
My project is generated with the latest angular-cli, using webpack under the hood.
Thanks a lot for your help !

Not sure if Materialize.updateTextFields() is the best option, but Materialize is a global object so you should be able to just call it. I'm not a webpack user but I know you could use the "export" or other plugins to inject global objects into your components.
If you post example code maybe someone could pick that up and try to fix the problem.
If you find a solution please post it here and we can incorporate that into the library.
Thanks.

Thanks for your answer.
To reproduce the issue, you only have to bind your form example to a string value on your component.
I think it's a knows issue since on the materialize website we can read :

If you are having trouble with the labels overlapping prefilled content, Try adding class="active" to the label.
You can also call the function Materialize.updateTextFields(); to reinitialize all the Materialize labels on the page if you are dynamically adding inputs.

In fact, on your quick sample, you can see it on the first field : http://angular2-materialize.surge.sh/#/ModelBindings

Link 404

@dh-fallen have you found a solution for this issue? I used to set the label class to active, but I realize it doesn't work when importing the MaterializeModule.

I have just the same issue. Adding class="active" to the label doesn't work.

What I did at work was create a directive, which I put on my FormGroup. When the any form values change, I do Materialize.updateTextFields().

@lengtche could you please show some real code that worked for you? Thanks

You can do something like this:
import { Directive } from '@angular/core';
import { NgModel, FormControl } from '@angular/forms';

@Directive({
    selector: '[updateTextFields]',
    providers: [NgModel]
})
export class UpdateTextFieldsDirective {
    constructor(private model: NgModel) {
    }

    ngOnInit() {
        // haven't really looked into how to handle form groups or binds using ngModel
        let m = this.model.formDirective ?
            this.model.formDirective :
            this.model;

        m.valueChanges.subscribe(value => {
            Materialize.updateTextFields();
        });
    }
}

With that you should be able to add directive updateTextFields to your form fields.

@lengtche Thanks, but I get an error that Materialize couldn't be found. Actually I'm not able to use Materialize.updateTextFields(), while other materialize features are working well in template. I've imported and enabled Materialize accordingly to this doc: https://www.npmjs.com/package/angular2-materialize

Calling Materialize.updateTextFields() upon form update doesn't seem to fix this issue for me.

Put class = "active" in label works for me but it looks a little ugly.

Did any one found a good solution for this problem ?
I'm actually using the following workaround :
declare var Materialize:any;

export class MyComponent implements OnInit, AfterViewChecked {
...
  ngAfterViewChecked() {
    Materialize.updateTextFields();
  }
}

The idea is to call Materialize.updateTextFields(); after the dom initialization.

same here. tried both methods but cant make it work. any workaround ?
Uncaught (in promise): Error: Error in :0:0 caused by: Cannot read property 'updateTextFields' of undefined

@rvaliev this sounds like a problem importing MaterializeCSS. The Materialize object should be available globally. Try checking in the browser console if it exists ( console.log(Materialize) ). If it doesn't, then you should review how you're importing the MaterializeCSS library to your project.

It's possible. Can you help ? I followed these steps:
npm install materialize-css --save
npm install angular2-materialize --save

At angular-cli.json :
Go to section apps and find styles array inside it (with only styles.css value by default), add the following line inside array before any styles:
"../node_modules/materialize-css/dist/css/materialize.css"
Go to section apps and find scripts array inside it, and add the following lines inside array
"../node_modules/jquery/dist/jquery.js",
"../node_modules/hammerjs/hammer.js",
"../node_modules/materialize-css/dist/js/materialize.js"
Add to the top of app.module.ts
import { MaterializeModule } from 'angular2-materialize';
Add MaterializeModule inside imports array of @NgModule decorator in app.module.ts
Add this line to header of index.html
<link href="http://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
But when tried console.log(Materialize) I got an error":
ERROR in /jolet_angular/src/app/app.component.ts (27,21): Cannot find name 'Materialize'

@rvgarimrj the steps look fine. You can double-check and confirm with the sample JSON in the repo (https://github.com/InfomediaLtd/angular2-materialize/blob/master/sample/.angular-cli.json).
Would you like to share your project? Will be easier to provide help with a reproducible use case.

@rubyboy here is my reposiroty. As I can see the only difference between their .angular-cli.json to mine is the fact I use Docker. But I think it is not the case. If you kindly could take i look here and see what i am doing wrong, I would be very pleased.
Github

@rvgarimrj I'm glad you've solved it. Thanks for letting us know.

Duplicate: https://github.com/InfomediaLtd/angular2-materialize/issues/106

No clean solution available ?

Try setting a timeout function after the ajax call and before calling the Materialize.updateTextFields() method:
$timeout(function () {                         Materialize.updateTextFields();                     }, 10);

For those who use the files from CDN.
I got it fixed by changing the way of inclusion of js and css files.
<head>
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
<link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.5/css/materialize.min.css">
</head>
<body>
------------------------
---------------------------
<script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.1/jquery.min.js"></script>
<script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.5/js/materialize.min.js"></script>
</body>

Just that change and it worked.

thanks for the suggestions! @Keshava11 and @anacarol91
i tried both ways, but i am still having the overlap issues
has anyone found anything else that works for them?

put a ngClass in your label like this
<label for="name" [ngClass]="{'active': user.name }">Name

Just put an empty placeholder in input, for example where I want the date template to pre-fill the form and force the label to be active:

I'm not sure why narxiss24's answer got a downvote. It fixed the problem for me and seems like the easiest solution. Why the downvote? Is there an accessibility issue with this fix? I can't see a visual issue with it.

Same issue here. Since I'm using the CSS Framework for a Chrome extension with vanilla JS, loading some data from the Chrome storage triggered the issue. using the empty placeholder workaround  (thank @narxiss24 ) works just fine, while the Materialize.updateTextFields(); won't work. Btw. Adding timeouts to is not a very smart solution from my pov.

Add style to material-icons
.material-icons {z-index:1}


Testing new CI actions

Description
Describe the content of the PR and links to related issues, bugs of features.
Requirements
Before submitting this PR, please make sure:

[ ] You have run the code checks, tests and documentation build successfully
[ ] All fixes and all new functionality are tested and documentation is up to date
[ ] You looked at the review checklist

Additionally, if this PR contains code authored by new contributors:

[ ] All the authors are covered by a valid contributor assignment agreement,
signed by the employer if needed, provided to ETH Zurich
[ ] The names of all the new contributors have been added to an updated
version of the AUTHORS.rst file included in the PR

Codecov Report

:exclamation: No coverage uploaded for pull request base (functional-test@989ea81). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             functional-test     #664   +/-   ##
==================================================
  Coverage                   ?   79.40%
==================================================
  Files                      ?       53
  Lines                      ?     4025
  Branches                   ?      825
==================================================
  Hits                       ?     3196
  Misses                     ?      690
  Partials                   ?      139

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 989ea81...63ceba2. Read the comment docs.

Yes, this PR can be closed now.

Closing in favor of #866