setupAutomaticSilentRefresh() works but is called too frequently

Hi,
We're using version 2.1.3 and are using silent refresh. It is configured like this:
this.oauthService.silentRefreshRedirectUri = window.location.origin + "/" + relativeAppPath + "silent-renew.html";
            this.oauthService.setupAutomaticSilentRefresh();
            this.oauthService.timeoutFactor = 0.9;

Our token currently has a lifetime of 10 hours. I know, far far too long and we'll be reducing it to a more reasonable and secure timeframe but that's what it is for now.
I have checked the expires_at field in session storage and the ticks it is writing converts to 10 hours relative.
My question is about the automatic silent refresh. It's happening every 4-5 minutes which is far too frequent given the configuration outlined above. Any ideas why this might be?

I have only little knowledge of pre 3.x versions, nor the inner workings of how silent refreshes are set up, but based on your code: shouldn't you configure the timeoutFactor before you set up the silent refresh? Perhaps that would help?

Is it possible, that your Id_Token is the reason? You can find it in your session storage and by coping it into the form on jwt.io you can see its expiration date.

Hi,
@jeroenheijmans That's a good point/catch. The default setting is .75 (75%) according to the documentation though so it shouldn't be refreshing for 6 hours.
@manfredsteyer I did just that before creating this issue. jwt.io is very handy. I confirmed that the token expiry matches what it should be as per the Identity Server configuration. It's represented in ticks so I had to use https://www.epochconverter.com/

Actually I just noticed here that there are two expiry settings in Session Storage.
"expires_at" is correctly set to 10 hours as per the Identity Server configuration
"id_token_expires_at" is 3 minutes or so.
Could it be that the Silent Refresh functionality is using the "id_token_expires_at" to set up the frequency of refreshing?

I looked at the code for doing the silent refresh and it seems to take the lesser expiry time which makes sense.
It would be good if the setupAutomaticSilentRefresh() method could accept a parameter which indicates which expiry time to use. My understanding is that the Id Token is only used to authenticate and will be short lived whereas the access token will live longer and is used to consume APIs.

@manfredsteyer Is there any chance we can get this out in an official npm release? It looks like it's merged in #462

Hello @manfredsteyer do you any timeframe for a new release with this feature please? We do have the same problem in our development and we are stuck...
Thanks

@martin1cerny Although the option is added to filter token_expires based on the listenTo parameter, the code that sets up the timers setupExpirationTimers() still continues to use the shorter expiring time which will be id_token. I dont think the issue is still fixed.

There's been a few new releases July 2019, so I'm assuming everything's available now. Let us know if the issue remains with new versions and we can reopen!

@jeroenheijmans the issue still remains the way @davdev82 described. If the id token has a shorter lifespan than the access token and you configure setupAutomaticSilentRefresh to only listen to access token expiration, the access token will never be refreshed. I created a pull request that always fires the token_expires event for both token. setupAutomaticSilentRefresh() then filters the token_expires event for the correct token type.

Okay cool, thx for the update and the PR, will reopen this issue then!

We are experiencing the same issue where we want to refresh only on access_token expiration, but only the id_token timer is set. Is there a plan to merge @harmpauw's PR anytime soon?


Change Cloudflare provider to use API tokens

Hey Hugo!
I've changed some of the workings for the Cloudflare provider to use an API token instead of a user's API key and email. Tokens were introduced last year as a more secure approach to the original global API key.
There's a few changes that come with this PR, so I've tried to summarise them below.
Require zone ID instead a domain name
Having the zone ID provided by the user removes the need to look up an account's zones, searching for the corresponding domain name and zone ID.
This means the only API calls we need to make are zone-related (read/update DNS records), which lends itself well to using API tokens.
Copying over the zone ID is a bit unwieldy, but it should only be a one-time change for users.
Use API tokens over API keys
Tokens can be scoped to only have access to individual zones, and can have granular permissions.
All a token should need is permission to edit DNS records for the target zone.
QOL changes
I've also added a few changes for problems I encountered while running this on my own system.

Hosts will maintain their existing proxy status (orange-clouded) instead of defaulting to false when updating records
Only A records will be requested - this should avoid accidentally overwriting other records (MX/TXT) for a host

Backwards compatability
These changes mean a release with breaking changes. To upgrade, users will need to update their config/environment variables.

CLOUDFLARE_ZONE -> CLOUDFLARE_ZONEID
CLOUDFLARE_EMAIL/CLOUDFLARE_APIKEY -> CLOUDFLARE_APITOKEN

If any of these old environment variables are used, I figured failing with a warning would be the best option.
CLOUDFLARE_ZONE=nicholas.cloud ./cloudflare-ddns -config nicholas.cloud.env
# 2020/05/08 21:14:04 Do not use CLOUDFLARE_ZONE, see https://github.com/hugomd/cloudflare-ddns#deprecated-environment-variables

This breaking change could be avoided by copying all of these files into a new provider (cloudflare-with-api-token?), though that would mean maintaining two Cloudflare providers.
Apologies for the wall of text, I know there's a bit to this PR.

It's just occured to me that only requesting A records from the API means trouble if someone is on IPv6, since they'll want to update an AAAA record instead.
It also means similar trouble if the IP of the host need to change from IPv4 to IPv6 or vice versa, but that's probably a separate issue.

Hey, thanks for taking the time to make this pull request!
I'll try to get a review done this week, but from a quick skim it looks great!

This means the only API calls we need to make are zone-related (read/update DNS records), which lends itself well to using API tokens.

This is great, much cleaner than the old implementation!

Use API tokens over API keys

Good stuff!

Regarding maintaining backwards compatibility, I have a few thoughts on how we can approach this.
Broadly, we can remain completely backwards compatible, either by adding a separate provider as you suggested, or just branching logic in the existing provider.
Or, we can avoid backwards compatibility and force users to make the required changes. I think this is okay, but it'd be nice to do this gracefully.
This  leads me to what I think is a nice middle ground, which would involve:

Adding warnings logs prior to merging this pull request, pushing those changes out on the latest tag, and then disabling pushes latest on master, so we don't break the previous implementation.
Merging this PR in, and giving it a versioned tag.

That way, users pulling latest will receive warning logs but retain existing usage, and we can give them a grace period of some kind. While new users can pull a specific image version.
Likewise, we can add to the warning log you've added, to advise users to either refer to documentation (as you've done here already), or rollback to a specific image tag rather than using latest.
Thanks again for the PR!

Sounds like a good compromise to avoid breaking latest in the short term, and to let users upgrade smoothly. I like it!


[sharry] use a config blockk

Description of the change
Use a config block for sharry and some clean up
Benefits
Fixes a security issue where using the chart would always expose admin:admin account
without the ability to disable it.
Possible drawbacks
User has to dig a bit in the configuration to configure authentication
Applicable issues
N/A
Additional information
I've tried to do a bit of clean up along the way, there may be a :bug:
Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

Maybe you need more information in the config?

...like
      bind {
        address = "<IP_ADDRESS>"
        port = {{- if .Values.service.port.port }}{{ .Values.service.port.port }}{{ end }}
      }```

Yeah but the error message was not really helpful here. I had to guess that the reason of the crash was that the service was not reachable on the port. Is that the actual check that is made here?


Cannot build a fresh install of ocaml + findlib after the update to 4.02.1

As of today I'm no longer able to use ocamlbrew to bootstrap a new environment, since the update to 4.02.1 broke the compilation of findlib as follows:
make[1]: Leaving directory `/home/piffio/ocamlbrew/ocaml-4.02.1/build/findlib-1.5.4'
Retrieving the latest version of opam
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2224k  100 2224k    0     0   442k      0  0:00:05  0:00:05 --:--:--  542k
Building opam
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for ocamlc... ocamlc
OCaml version is 4.02.1
OCaml library path is /home/piffio/ocamlbrew/ocaml-4.02.1/lib/ocaml
checking for ocamlopt... ocamlopt
checking for ocamlc.opt... ocamlc.opt
checking for ocamlopt.opt... ocamlopt.opt
checking for ocaml... ocaml
checking for ocamldep... ocamldep
checking for ocamlmktop... ocamlmktop
checking for ocamlmklib... ocamlmklib
checking for ocamldoc... ocamldoc
checking for ocamlbuild... ocamlbuild
checking for camlp4... no
checking for camlp4o... no
checking for camlp4of... no
checking for camlp4oof... no
checking for camlp4orf... no
checking for camlp4prof... no
checking for camlp4r... no
checking for camlp4rf... no
configure: error: You must install the Camlp4 pre-processor. On some operating systems, these are separate packages from the main OCaml compiler, such as camlp4-extra on Debian.

It looks like this new version requires camlp4 to be installed with a matching version, which is kind of against the whole concept of bootstrapping a fresh environment.
Manually changing back to the 4.01.0 version fixed the problem for me

I've updated ocamlbrew to install 4.02.1 again by default.  This breaks the ocamlbrew-based findlib installation.  Building OCaml + opam (ocamlbrew -r) should work properly though, and once opam is installed you can install findlib via opam.
I'm leaving this bug open for now as an opam-less findlib installation is still broken for OCaml 4.02.1.  I'm not sure if it would be better to address this by adding support for building camlp4 or by removing direct findlib support, effectively limiting ocamlbrew to building OCaml + opam.  I'm leaning toward the OCaml + opam approach as that is where the broader community's effort is focused.

Similar issue.
ocamlbrew/ocaml-4.02.1/.opam/system/build/camlp<IP_ADDRESS>+system/camlp4-14990-1872ec.err:
./check-camlp4.sh: line 3: camlp4orf: command not found

ocamlbrew/ocaml-4.02.1/.opam/system/build/camlp<IP_ADDRESS>+system/camlp4-14990-1872ec.out:
Please install a system-wide version of camlp4.  This is necessary since you
are using OCaml 4.02.1 and the system compiler switch (which uses your
preexisting installation rather than compile one from scratch).

If you cannot install a system-wide camlp4, then you can still use OCaml
4.02 by switching to a local installation via `opam switch 4.02.1`.

Here are some installation instructions for camlp4 if you obtained OCaml
via the OPAM binary packages:

http://software.opensuse.org/download.html?project=home%3Aocaml&package=ocaml

* Debian/Ubuntu: sudo apt-get install camlp4-extra
* RHEL/CentOS/Fedora: sudo yum install ocaml-camlp4

Then running below commands and succeeded install.
opam switch 4.02.1
opam install oasis

I'm closing this since camlp4 shouldn't be a requirement any longer and the ticket is approaching years old.  Please reopen if there's still a problem.


Invalid type for SETITEM: ByteString when assigning value at index in bytearray

Describe the bug
An attempt to set a value at a given index of a bytearray fails at runtime with:
boa3_test.tests.test_classes.TestExecutionException.TestExecutionException: Invalid type for SETITEM: ByteString
How to Reproduce
Compile and invoke this contract:
from boa3.builtin import public

@public
def main() -> bytearray:
    a = bytearray(b'\x01\x02\x03\x04\x05\x06\x07\x08')
    a[0] = 0x02
    return a

This is basically the same code as in https://github.com/CityOfZion/neo3-boa/blob/master/boa3_test/test_sc/bytes_test/BytearraySetValue.py which also fails with the same error
Expected behavior
You should be able to set individual bytes within a bytestring by index, as in regular Python
Platform:

OS: OSX 12.4
Version: 0.11.2
Python version: 3.9.4

AFAIK, the exception occurs in NeoVM at ExecutionEngine.
I have an assumption that the compiler uses a different type at the end where NeoVM expects VMArray.

@meevee98 cool, thank you for the fix. Any information on when the fix will be available with a new version? It's kinda blocking issue for us.


Kindly Partner Outreach

[x] Follow-up with Codecademy if we don't hear from them
[x] Email Google's Jigsaw team re: connecting with Google Classroom + YT Kids
[x] Connect Cheryl with Codecademy (Codecademy providing curric to DPG accelerators)
[x] Follow-up with Rob from Stanford if we don't hear by Thurs

Will create a new task for this:  Outreach to at least 10 more edtech companies


feat(imports): support import attributes - fixes #14674

Description
Fixes https://github.com/vitejs/vite/issues/14674
Adds support for import attributes by parsing them in the import analysis plugin.
Additional context
How this works:

es-module-lexer provides information about where the attributes are. We already use this to clip them off.
We grab the string, which is an object literal { foo: 'bar' }
We use Acorn to parse this string.
Iterate over the AST to extract the values into an object
Pass this through to resolveId where plugins can do what they want.

What is the purpose of this pull request?

[X] Bug fix
[X] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Update the corresponding documentation if needed.
[X] Ideally, include relevant tests that fail without this PR but pass with it.

I'm not sure why this is failing in CI, likely a race condition some how. I'll take a look.

I'm not working on this at the moment, so closing.


Failed loading language 'eng' - Windows Server 2016

Environment:

I am getting this error in one specific server (Windows Server 2016 x64) when I try to use tesseract. Failed loading language 'eng'

Can someone help me?
Tesseract Version:

tesseract-ocr-w64-setup-v<IP_ADDRESS>90314 (rc1) (64 bit) resp.

Platform:

Windows Server 2016 Standard 64x

Test:
cmd: Tesseract-OCR>tesseract tessert\IMAGE.jpg test
Error opening data file C:\Program Files\Tesseract-OCR\eng.traineddata
Please make sure the TESSDATA_PREFIX environment variable is set to your "tessdata" directory.
Failed loading language 'eng'
Tesseract couldn't load any languages!
Could not initialize tesseract.

Please respect guidelines for posting issue: use tesseract user forum for asking questions/support.
And spent at least 1 second for searching on internet.


Create deeplink for headers inside HTML pages

Some pages are long.
We want to be able to deeplink sections inside the page using #section2.
So, all sections should have a ... anchor to make that possible.

We'll do this where necessary (like the faqs table of contents)


Hangs when vendoring from repo

Unfortunately I can't put the actual repo url in here, but this is hanging when trying to vendor one of our (Uber's) repositories:
gb vendor <host>/<path>/<repo>.git
2015/04/29 15:00:53 INFO project root "<project root>"

...and just stays there until I Ctrl-C.

Surely you mean gb-vendor?

More info after letting it time out:
gb vendor <host>/<path>/<repo>.git
2015/04/29 15:00:53 INFO project root "<project root>"
package code.google.com/p/snappy-go/snappy: Get https://code.google.com/p/snappy-go/source/checkout?repo=: read tcp <IP_ADDRESS>:443: operation timed out
2015/04/29 15:08:50 exit status 1
2015/04/29 15:08:50 command "vendor" failed: exit status 1

code.google.com/p/snappy-go/snappy is directly go-gettable, though.

interesting, both gb vendor and gb-vendor seem to be valid commands?

Strange!  gb-vendor works.  Why are they both valid and why does the latter work but not the former?

gb-vendor is a git style plugin. It's a bug that t doesn't properly protect itself from being run directly. I'll fix that.
As an aside, gb-vendor is just a thin shim that sets GOPATH to the project's vendor directory and shells out to go get.
Gb-vendor is just a hack to bootstrap your project, you can always just popular the vendor/src directory manually.

OK thanks for the clarification, closing, although definitely fix the gb vendor issue, that was quite confusing.


Network graph is broken

I'm trying this on a linux host running Gentoo 3.13.1, and the "Network Traffic" graph seems to be broken. I've tried running as a normal user and as root, and with Ruby 1.9.3p484 and 2.1.1p76, to no avail. The title shows up, but the box which should hold the bandwidth number is just a line and the graph itself is nonexistent:

It is somewhat atypical of a network setup; rather than eth0 I have a bunch of different interfaces such as wan0, lan0, wlan0, br0, he6, etc. I couldn't find anywhere to specify which interfaces to watch.

Tried my best as well with no luck. Here's my cat /proc/net/dev:
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
enp2s0:<PHONE_NUMBER>1 63696691    0   52    0     0          0         0<PHONE_NUMBER>3 69274256    0    0    0     0       0          0
docker0:     792      15    0    0    0     0          0         0    14819     203    0    0    0     0       0          0
    lo:<PHONE_NUMBER> 2243560    0    0    0     0          0         0<PHONE_NUMBER> 2243560    0    0    0     0       0          0

ruby -e "puts RbConfig::CONFIG['target_os']"
linux

cat /etc/redhat-release
Fedora release 22 (Twenty Two)

This was happening to me when Docker was running, for @ronilaukkarinen and others, open network.rb with: nano /var/lib/gems/2.3.0/gems/server_metrics-1.2.18/lib/server_metrics/collectors/network.rb
Change line next if iface =~ /^(lo|veth\w{4,})$/ to next if iface =~ /^(lo|docker0|veth\w{4,})$/
Save and restart Scout Runtime.


Allow Ctrl+C to terminate the menu cleanly

If we don't show the cursor again, then future menus are broken when they try and read the cursor location.

Great thanks for this PR and sorry for late (oh, soooo late) reply. Currently it the fix is already covered by another PR so not going to merge this one. All in all functionality is covered and works fine.
Thanks for your support.


VR support

Add support for virtual reality (primarily quest 3)

Very low priority due to complexity and difficulty. All other fundamental features must first be implemented.


Change API of ImageCleaner to be __call__(self, event: ArrayEvent)

Please describe the use case that requires this feature.
Currently, the ImageCleaner has the API of __call__(self, tel_id, image, peak_time).
For more advanced cleaning methods that e.g. require monitoring information about the current NSB / pedestal variation, it is impossible to use this information.
Describe the solution you'd like
Also switch to __call__(self, event) so the cleaning algorithms can access all relevant information.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
E.g. LSTs cleaning is using a factor of the pedestal standard deviation as a lower bound for the cleaning threshold.

I don't really like passing too much info to low-level algorithms as it makes it hard to follow what they actually use, and the code becomes needsly confusing (this was one of the "lessons learned" we tried to avoid in ctapipe).  Since I think pedestal variances are clearly useful for image cleaning, I would prefer just to pass those to all image cleaners explicitly in ImageProcessor.
for the discussion about the array structure, see #1165

I think it is important here to make a difference between low-level code in small, self-contained functions with well-defined inputs and outputs and processing components that need to be flexible to allow access to more information that might be needed and which we currently do not anticipate.
E.g. the low-level tail_cuts_clean function would stay as it is, but the Component should get the ArrayEvent (or TelescopeEvent once we implement what is proposed in CEP 2 / #1165) so that the levels can be adapted to the monitoring info before passing to the tailcuts clean.
We have seen time and again, that more information becomes useful or is needed and expanding the API every time that happens is I think worse than just providing the high level API with the full event container.

See also comment in this issue which I closed as duplicate of this one:

You are now arguing some hypothetical use cases against a real one that was brought up multiple times.
A usecase that is so important to e.g. the analysis of LST commissioning data, that lack of support for it prevents moving to using the ctapipe tools for the analysis.
We need to enable this.
Since the components can be configured, I don't see a reason why we can't add the needed configuration options needed for the use cases you mentioned even if we change to the more general API.
Another possibility would be to have two public methods in ImageCleaner: __call__(self, ArrayEvent) and a lower-level clean(tel_id, image, peak_time).

Any update on this? Now magic-cta-pipe moved to ctapipe v0.19, and I would really like to be able to move to use ctapipe tools for the pipeline, at least at the low level. Right now I am still stuck because I cannot implement the MAGIC cleaning inheriting directly from ImageCleaner. If there is another solution, of course let me know.


Added loglogistic probability density function

Summary
Implemented the loglogistic_lpdf with manual gradients #2320. The implementation is based on the implementations of logistic_lpdf and normal_lpdf.
Tests
Added a test for the loglogistic_lpdf.
Release notes
Implementation of the loglogistic probability density function.
Checklist

[x] Math issue #2320

[x] Copyright holder: Gregor Pirš

Nice! Are you working on the lcdf/lccdf and rng functions as well? I believe we need all of them for new distributions in the math library

Also does it look like the docs I have for the pdf function will apply to the cdf? The doc for rng will be different but for the cdf I think the same stuff will apply

Just fyi: I suggested to Gregor to start with the pdf and get feedback and once that is merged, open another one with cdf/rng. Hopefully I didnt mislead him :) Its fine merging distributions in pieces.

I'm alright with it! We can just wait to expose them to the language until all the pieces are in

@SteveBronder yes, I'll also start on other functions. I think that the docs will work for the cdf also. Should the other functions be part of this PR, or should I make a separate one for each?

Should the other functions be part of this PR, or should I make a separate one for each?

That is up to you. Just don't make a single PR is too big if possible (up to ~1000 changed lines of code). Reviewing huge PRs is harder.

@t4c1 Thank you for the review, I'll make the suggested changes. If it is up to me, I'll create a separate PR for each function. I think it makes it easier to follow, review, and fix issues.

Also does it look like the docs I have for the pdf function will apply to the cdf? The doc for rng will be different but for the cdf I think the same stuff will apply

A somewhat tangential comment — if we’re going to enforce that all distributions include a density, cdf, and rng (which I definitely think we should) then I would encourage not merging the implementations piecemeal.  It’s much too easy for only a density to be defined and merged only to have the contributor not follow up on the rest, especially with how surprisingly challenging the derivatives for the CDF and the implementation of an effective PRNG can often be.  In my opinion tests can be run and feedback acquired on a forked branch just as easily in stages as each piece is implemented before considering a PR into develop.
To be clear this comment in no way reflects upon @gregorp90; just general polices to help avoid incomplete implementations.

@betanalpha Thank you for the comment! I'll open a single PR for the cdf and the rng. I guess these three are the main elements that we want for a distribution and lcdf/lccdf can be added later in a separate PR?

@betanalpha https://github.com/betanalpha Thank you for the comment! I'll open a single PR for the cdf and the rng.

That would be great.

I guess these three are the main elements that we want for a distribution and lcdf/lccdf can be added later in a separate PR?

Yeah — ideally the lcdf and lccdf would have custom numerical implementations but we haven’t required that of the others distribution families which are mostly just logging the existing cdf implementation.

Thank you for the information!


Null safety support

Env info

Bug info

https://github.com/flutter-studio/flutter-icons/issues/41

Made the PR that addresses the problem: https://github.com/flutter-studio/flutter-icons/pull/47.

I pushed out a fork which includes all missing icons including Fontisto fonts and jibiel's fixes for null safety support: https://pub.dev/packages/flutter_font_icons

Why did you remove common api ``FlutterIcons`?

It's duplication of functionality from the other methods. I also don't have the split function that the other library had because I plan to implement that differently.

I pushed out a fork which includes all missing icons including Fontisto fonts and jibiel's fixes for null safety support: https://pub.dev/packages/flutter_font_icons

Thanks a lot @josephcrowell. This one is working: flutter_font_icons 2.2.4

@josephcrowell do you have any plan to implement a common api? This way, it is hard to search and find icons.

No


SideBar Glitches - Hardware Acceleration Disabled

Describe the bug
I seem to get the well-known sidebar glitchiness in runelite.  I have tried all methods of disabling hardware acceleration and none seem to work.
Screenshots
https://prnt.sc/tegk10
Environment (please complete the following information):

OS: Windows 10 Home Build 18363
RuneLite version: <IP_ADDRESS>
Launcher version: 2.1.3

PC is running a Ryzen 9 3900X and RTX 2080 Super
Only seem to have gotten this issue on this newer PC I have.  I do not recall it on my last PC though.

Duplicate of #11727


Too many open files while using materialized view with kafka source

Greetings.
I have Ubuntu 18.04 source system. Clickhouse server version - 18.12.17. Default config.
Database structure creation:
create table a (EventDate Date) ENGINE MergeTree() partition by toYYYYMM(EventDate) order by (EventDate) settings index_granularity=8192;

create table k (EventDate Date) ENGINE=Kafka SETTINGS
  kafka_broker_list = 'localhost:9092,localhost:9093,localhost:9094',
  kafka_topic_list = 'a',
  kafka_group_name = 'group1',
  kafka_format = 'JSONEachRow';

create materialized view w to a as select * from k;

As soon, as materialized view was created, amount of file descriptors for clickhouse server process starts to grow each second to the limit of max open files.
Error logs are empty. Usual log contains only debug ant trace info. However syslog contains following errors:
Sep 22 18:22:38 kernel: [25449.716131] netlink: 'TCPHandler': attribute type 1 has an invalid length.
Sep 22 18:22:38 kernel: [25449.729949] netlink: 'TCPHandler': attribute type 1 has an invalid length.
Sep 22 18:22:40 kernel: [25451.228134] netlink: 'ParalInputsProc': attribute type 1 has an invalid length.
Sep 22 18:22:40 kernel: [25451.228175] netlink: 'ParalInputsProc': attribute type 1 has an invalid length.
Sep 22 18:22:42 kernel: [25453.227433] netlink: 'ParalInputsProc': attribute type 1 has an invalid length.

Am I missing something? Any help would be much appreciated.

Does setting kafka_num_consumers = 1 in the Kafka table stop the errors?
https://clickhouse.yandex/docs/en/operations/table_engines/kafka/

Thank you for response. Changed kafka table creation to:
CREATE TABLE default.k ( EventDate Date) ENGINE = Kafka SETTINGS kafka_broker_list = 'localhost:9092,localhost:9093,localhost:9094', kafka_topic_list = 'a', kafka_group_name = 'group1', kafka_format = 'JSONEachRow', kafka_num_consumers = 1
Unfortunately, problem is still present.

We are also seeing this issue.  Our clickhouse version is 18.12.13 revision 54407. I'm happy to provide more info to help debug the problem.

We meet this problem too. So sad!

Do you use clickhouse from packages, or build from sources?
can you also check clickhouse-server.log (not an err.log) for something suspicious?
how many nodes do you have in your kafka cluster.
can you try to consume messages with kafkacat from the same host where CH is installed?

Kafkacat and native consume\produce scripts of kafka dist work normally with local kafka.
Clickhouse was installed from package
Nothing suspicious in either log.
3 nodes of kafka.

Kafka is running via following docker-compose:
version: '2'
services:
  zookeeper:
    image: wurstmeister/zookeeper
    ports:
      - "2181:2181"

  kafka1:
    image: wurstmeister/kafka
    ports:
      - "9092:9092"
    environment:
      HOSTNAME_COMMAND: "route -n | awk '/UG[ \t]/{print $$2}'"
      KAFKA_ZOOKEEPER_CONNECT: "zookeeper:2181"
      KAFKA_BROKER_ID: "1"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

  kafka2:
    image: wurstmeister/kafka
    ports:
      - "9093:9092"
    environment:
      HOSTNAME_COMMAND: "route -n | awk '/UG[ \t]/{print $$2}'"
      KAFKA_ZOOKEEPER_CONNECT: "zookeeper:2181"
      KAFKA_BROKER_ID: "2"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

  kafka3:
    image: wurstmeister/kafka
    ports:
      - "9094:9092"
    environment:
      HOSTNAME_COMMAND: "route -n | awk '/UG[ \t]/{print $$2}'"
      KAFKA_ZOOKEEPER_CONNECT: "zookeeper:2181"
      KAFKA_BROKER_ID: "3"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

Clickhouse server is running on system outside of created docker network. If clickhouse is added as new service to docker-compose - all works fine. So as workaround for now we moved production implementation to separate docker container.

Kafkacat and native consume\produce scripts of kafka dist work normally

Kafkacat is more representative for debugging (it uses the same lib for Kafka access as ClickHouse).

work normally with local kafka.

What do you mean by local? Can you check to consume messages by kafkacat in the same configuration where ClickHouse had problems? I.e. (if I understand you correctly): local kafkacat consuming messages from 3-node docker based cluster.
@arstd , @snorecone in your case it's also related somehow to docker?

@filimonov no we're not running with docker at all. Kafka, Zookeeper and Clickhouse are all running on ec2 instances - ubuntu 16.04; clickhouse is installed from packages - 18.12.13 revision 54407.

Sorry for misunderstanding. I have only one implementation of kafka on local environment - 3-node docker based cluster. Kafkacat successfully produce and consume messages from this cluster. If clickhouse server is running on host machine - bug takes place. If clickhouse added as a service to docker network with kafka - all works fine.
Bug also takes place on production environment, where we hadn't any docker at all. Source system there is Debian Jessie, 3 node kafka cluster.

I have kind of the same issue. But my logs have huge numbers of error.
I have  Ubuntu 18.04.1, Clickhouse 18.14.9 revision 54409, instaled without docker from packages, 3
Kafka nodes.
2018.10.24 12:38:08.038702 [ 22 ] {} <Error> r0.events (ReplicatedMergeTreeRestartingThread): void DB::ReplicatedMergeTreeRestartingThread::run(): Code: 999, e.displayText() = Coordination::Exception: All
connection tries failed while connecting to ZooKeeper. Addresses: <IP_ADDRESS>:2181, <IP_ADDRESS>:2181, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 24, e.displayText() = I/O error: Too many open files, e.what() = I/O error, <IP_ADDRESS>:2181
 (Connection loss), e.what() = Coordination::Exception, Stack trace:

0. /usr/bin/clickhouse-server(StackTrace::StackTrace()+0x16) [0x99e9626]
1. /usr/bin/clickhouse-server(Coordination::Exception::Exception(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int, int)+0x31) [0x7cabf81]
2. /usr/bin/clickhouse-server(Coordination::Exception::Exception(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x1a5) [0x7cacd35]
3. /usr/bin/clickhouse-server(Coordination::ZooKeeper::connect(std::vector<Poco::Net::SocketAddress, std::allocator<Poco::Net::SocketAddress> > const&, Poco::Timespan)+0x40a) [0x7ccdc7a]
4. /usr/bin/clickhouse-server(Coordination::ZooKeeper::ZooKeeper(std::vector<Poco::Net::SocketAddress, std::allocator<Poco::Net::SocketAddress> > const&, std::__cxx11::basic_string<char, std::char_traits<c
har>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&, Poco::Timespan, Poco::Timespan, Poco::Timespan)+0x3e9) [0x7cce279]
5. /usr/bin/clickhouse-server(zkutil::ZooKeeper::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::a
llocator<char> > const&, int, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+0x390) [0x7cbf840]
6. /usr/bin/clickhouse-server(zkutil::ZooKeeper::startNewSession() const+0xd9) [0x7cc0309]
7. /usr/bin/clickhouse-server(DB::Context::getZooKeeper() const+0xe0) [0x7570d90]
8. /usr/bin/clickhouse-server(DB::ReplicatedMergeTreeRestartingThread::run()+0x79) [0x78d8b99]
9. /usr/bin/clickhouse-server(DB::BackgroundSchedulePool::TaskInfo::execute()+0xef) [0x796d23f]
10. /usr/bin/clickhouse-server(DB::BackgroundSchedulePool::threadFunction()+0xba) [0x796e00a]
11. /usr/bin/clickhouse-server() [0xa3da90f]
12. /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f404ba826db]
13. /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f404b00188f]

When I tried to connect to clickhouse I receive
ClickHouse client version 18.14.9.
Connecting to localhost:9000.
Connected to ClickHouse server version 18.14.9 revision 54409.

prusech003 :) Cannot load data for command line suggestions: Code: 32, e.displayText() = DB::Exception: Attempt to read after eof: while receiving packet from localhost:9000, <IP_ADDRESS>, e.what() = DB::Exception

Also, I have 2 Gb * 3 nodes logs from last 12 hours, if you need something, let me know.

2018.10.26 17:11:45.063142 [ 616383 ] {} <Error> void DB::ThreadStatus::initPerformanceCounters(): Code: 412, e.displayText() = DB::Exception: Can't create PF_NETLINK socket, errno: 24, strerror: Too many open files, e.what() = DB::Exception, Stack trace:

0. /usr/bin/clickhouse-server(StackTrace::StackTrace()+0x16) [0x99e9626]
1. /usr/bin/clickhouse-server(DB::Exception::Exception(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x22) [0x3087172]
2. /usr/bin/clickhouse-server(DB::throwFromErrno(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int, int)+0x1bc) [0x99ce23c]
3. /usr/bin/clickhouse-server(DB::TaskStatsInfoGetter::TaskStatsInfoGetter()+0x1bc) [0x99f0c1c]
4. /usr/bin/clickhouse-server(DB::ThreadStatus::initPerformanceCounters()+0x281) [0x99f21b1]
5. /usr/bin/clickhouse-server(DB::ThreadStatus::attachQuery(std::shared_ptr<DB::ThreadGroupStatus> const&, bool)+0x221) [0x767e971]
6. /usr/bin/clickhouse-server(DB::CurrentThread::attachTo(std::shared_ptr<DB::ThreadGroupStatus> const&)+0x3a) [0x767edea]
7. /usr/bin/clickhouse-server(DB::ParallelInputsProcessor<DB::UnionBlockInputStream<(DB::StreamUnionMode)0>::Handler, (DB::StreamUnionMode)0>::thread(std::shared_ptr<DB::ThreadGroupStatus>, unsigned long)+0x78) [0x75fd648]
8. /usr/bin/clickhouse-server(std::thread::_State_impl<std::thread::_Invoker<std::tuple<DB::ParallelInputsProcessor<DB::UnionBlockInputStream<(DB::StreamUnionMode)0>::Handler, (DB::StreamUnionMode)0>::process()::{lambda()#1}> > >::_M_run()+0x4f) [0x75fdc9f]
9. /usr/bin/clickhouse-server() [0xa3da90f]
10. /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f8f86c0f6db]
11. /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f8f8618e88f]

Try setcap cap_net_admin=-ep /usr/bin/clickhouse
NETLINK is used for 'collecting metrics from kernel'
We got too many open files when we added net_admin caps for clickhouse binary. We are using kafka too.

We don't use neither kafka nor docker (and we use just very basic features of Clickhouse) but I see lots of such messages (I also don't run out of socket handlers):
kernel netlink: 'TCPHandler': attribute type 1 has an invalid length.
kernel netlink: 'TCPHandler': attribute type 1 has an invalid length.
kernel netlink: 'TCPHandler': attribute type 1 has an invalid length.
kernel netlink: 'TCPHandler': attribute type 1 has an invalid length.
kernel netlink: 'AsyncBlockInput': attribute type 1 has an invalid length.
kernel netlink: 'ParalInputsProc': attribute type 1 has an invalid length.
kernel netlink: 'ParalInputsProc': attribute type 1 has an invalid length.

@fillest I see similar dmesg output for a Ubuntu 16.04.5 server which have clickhouse-server 18.14.15 installed. We are also using basic features of ClickHouse.
Simply run clickhouse-client and connect to local host would generate such error messages in dmesg.
[Mon Dec  3 13:31:06 2018] netlink: 'TCPHandler': attribute type 1 has an invalid length.
[Mon Dec  3 13:31:06 2018] netlink: 'AsyncBlockInput': attribute type 1 has an invalid length.
[Mon Dec  3 13:31:06 2018] netlink: 'ParalInputsProc': attribute type 1 has an invalid length.
[Mon Dec  3 13:31:06 2018] netlink: 'ParalInputsProc': attribute type 1 has an invalid length.
[Mon Dec  3 13:31:06 2018] netlink: 'AsyncBlockInput': attribute type 1 has an invalid length.
[Mon Dec  3 13:31:06 2018] netlink: 'TCPHandler': attribute type 1 has an invalid length.

The server is for test purpose and don't have much workload. ClickhouseServer have only 104 open file, connecting a client will increase open file number to 106.
 But seems like any query can trigger the above dmesg log, e.g. show databases, show tables and any select query on data tables.

@splichy I've tried the setcap command as you mentioned, but still gets netlink log messages.

netlink dmesg problem solved - https://github.com/yandex/ClickHouse/pull/3749

@proller Thanks. The netlink error message disappears after applying your fix.

But still there is problem with netlink file descriptors open
> ps aux | grep clickhouse
clickho+ 23434 12.9 11.8 7978952 967100 ?      Ssl  Dec25 184:24 /usr/bin/clickhouse-server --config=/etc/clickhouse-server/config.xml

> sudo lsof -p 23434 | wc -l
184505

The number  is constantly growing!
And upon reaching the limit - server going down

Have anyone faced this issue after new release?
Our clickhouse version is at 19.1.6 version.
However, the netlink file descriptors still keeps constantly increasing.
lsof -p 23434 | wc -l

We upgraded from an older version 18.12.17 with apt-get upgrade clickhouse-server from ubunto 18.04. The issue still persists, however, by completely remove clickhouse package and reinstall the new package, the issue is resolved.

The following has been observed, when ever the materialized view is trying to query the consumer(queue) table. It would increment the file descriptor count by 4. When there is no materialized view, there is no increment.
#4017 is in 19.1.6 release. However, this behavior still exists
2019.02.12 01:12:45.289371 [ 44 ] {} <Debug> StorageKafka (search_request_consumer): Started streaming to 1 attached views 2019.02.12 01:12:45.291034 [ 148 ] {} <Trace> StorageKafka (search_request_consumer): Creating formatted reader 2019.02.12 01:12:45.291077 [ 150 ] {} <Trace> StorageKafka (search_request_consumer): Creating formatted reader 2019.02.12 01:12:45.291045 [ 149 ] {} <Trace> StorageKafka (search_request_consumer): Creating formatted reader 2019.02.12 01:12:45.291088 [ 151 ] {} <Trace> StorageKafka (search_request_consumer): Creating formatted reader 2019.02.12 01:12:47.792008 [ 148 ] {} <Trace> ThreadStatus: Thread 148 exited 2019.02.12 01:12:47.792104 [ 149 ] {} <Trace> ThreadStatus: Thread 149 exited 2019.02.12 01:12:47.792170 [ 150 ] {} <Trace> ThreadStatus: Thread 150 exited 2019.02.12 01:12:47.792293 [ 44 ] {} <Trace> UnionBlockInputStream: Waiting for threads to finish 2019.02.12 01:12:47.792313 [ 151 ] {} <Trace> ThreadStatus: Thread 151 exited

A bit more info, our setup is with Kafka Engine with kafka_num_consumers = 4
with gdb setting break point at TaskStatsInfoGetter::TaskStatsInfoGetter() and TaskStatsInfoGetter::~TaskStatsInfoGetter()
We can see that for each materialized view interval, the constructor is called 4 times and no destructors is called.


Feature: Make the application's name more readable in the sealos data directory at /var/lib/sealos/data/default/applications

What is the problem this feature will solve?

default-template,default-terminal...maybe better
If you have solution，please describe it
No response
What alternatives have you considered?
No response

The user does not seem to need to be aware of the directory, and the same situation exists for the name

I want to uninstall the terminal application from my self-hosted sealos, just need to find out how to do it.

Yes, you can also query the corresponding directory by executing sealos ps

Thx

Same issue: https://github.com/labring/sealos/issues/2433
The fastest way to accurately find the image path currently
sealos ps -f ancestor=cni-plugins --notruncate


[Question]: aTokens displayed use internal API or directly call AAVE contract(s) (LendingPool)?

Library name
<EMAIL_ADDRESS>Describe your feature request
Hi Ledger,
I see that aTokens are now showing an accurate balance over time, with interest accruing. As far as I can tell, this is a somewhat new feature but I don't know when or where it was introduced.
Could you please help me find where this happens? I don't know if you are calling a contract directly or using an (internal) Ledger API within your servers.
Thank you.

Hello, i'm very sorry for the delay but Ledger Live Desktop is not a library, for questions it is better to directly contact our customer support, Github issues is currently mainly be used for tracking discussion around technical libraries.
https://support.ledger.com/

Hi @gre . So what I get from this answer is that the implementation is within a library somewhere, but you don't indicate which library. Is it an upstream library? All I'm asking is how the app gets the appropriate information. Thank you.


[BUG] Cannot create a Azure open AI connection through Prompt flow UI

Describe the bug
Cannot create a Azure open AI connection through Prompt flow UI
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:

Create a "Standard flow" in prompt flow
Try to add a Azure openAI connection by clicking "Add connection"

screen keeps blinking and doesn't load the connection details page
Expected behavior
should load the Azure open AI connection form
Screenshots
If applicable, add screenshots to help explain your problem.
Running Information(please complete the following information):

Brower- tested with chrome and Edge
Promptflow Package Version using pf -v: [e.g. 0.0.102309906]
Operating System: [  Windows 11]
Python Version using python --version: [e.g. python==3.10.12]

Additional context
Add any other context about the problem here.

@samithaj thanks for reporting, we will fix this bug. BTW, since this is AML Studio prompt flow issue, you can open ocv to us for AML Studio prompt flow issue in the future.


[MGDOBR-348] Setup run local script for integration tests

MGDOBR-348
Issue splitted into different PRs for better review:

https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/364
https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/365
https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/366
https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/367
https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/368

Please make sure that your PR meets the following requirements:

[ ] Your code is properly formatted according to this configuration
[ ] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[ ] All new functionality is tested
[ ] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to trigger pipelines and use the bots:

Run the end to end pipeline
Annotate the pull request with the label: safe to test. If you want to run the pipeline again, remove and add it again.

Rebase the pull request
Comment with: /rebase.

@sutaakar readme updated

Thanks


Port to use awilix-router-core

Closes #5

@ jeffijoe do you mind taking a look at that? :)

@jeffijoe do you mind taking a look at that? :)

For sure! I’ll review tomorrow. 😄

Great, thanks a lot!

Coverage remained the same at 100.0% when pulling b1b0b71c8e32dc252101de2d97f3f3407f4886d1 on port-to-awilix-router-core into 3e5d427e85950e783d7c396f8be12fb2781e5414 on master.

Coverage remained the same at 100.0% when pulling b1b0b71c8e32dc252101de2d97f3f3407f4886d1 on port-to-awilix-router-core into 3e5d427e85950e783d7c396f8be12fb2781e5414 on master.


[Tablet_config] Revert "Enable SELinux for ivi"

This reverts commit ea7e907dee22c67ca3d4906d5e0a7873d622c8fb.

Improper Commit Message
Tracked on not found in commit message,
make sure Tracked-On: Jira-ticket  is present.


feat: subsingleton tactic

The subsingleton tactic tries to close equality goals by arguing that the underlying type is a subsingleton type. It might be via a Subsingleton instance (via Subsingleton.elim), but it also handles some cases where morally the types are subsingletons; for example, it can prove that two BEq instances are equal if they both have LawfulBEq instances. For heterogeneous equality, it tries the HEq version of proof irrelevance.
This tactic avoids the issue where
example (α : Sort _) (x y : α) : x = y := by apply Subsingleton.elim

is a "proof" that every type is trivial. Changing this to by subsingleton prevents it from assigning the universe level metavariable in Sort _ to 0.
This tactic can accept a list of instances subsingleton [inst1, inst2, ...] to do something like have := inst1; have := inst2; ...; subsingleton, but it elaborates them in a lenient way (like simp arguments), and they can even be universe polymorphic. For example, subsingleton [CharP.CharOne.subsingleton] is allowed even though the type of CharP.CharOne.subsingleton is Subsingleton ?R with a number of pending instance problems.
This PR also eliminates a number of uses of Subsingleton.elim, either by switching a congr to congr! or by using this new tactic.

!bench

bors merge

bors r-

Can you merge master, fix the build, and send it back to bors?
bors d+

bors r+

bors r-

bors r+


Astro integration

Since Astro supports middleware, we could integrate Fedify with Astro as well.  For easier integration, it would be great if Fedify provides an integration function like @fedify/fedify/x/astro.
Some context: https://github.com/dahlia/fedify/discussions/37#discussioncomment-9372276.

Due to the details of the behavior of Astro's middleware, it looks like the next release (v0.12.0) may not be able to ship with the Astro integration.


[PT-BR] Translations (2/3)

Translated by Alconost

@joefernandez Lint warning are inherited from source (English) files: e.g. missing license sections or links


Add returns to plot functions

Proposal to return plotted images/collections/lines in all our plot functions.
It's quite useful to be able to customize plots, and it essentially doesn't cost us anything. Plus it mimics the behavior of many matplotlib functions, e.g. dq.plot.wigner is essentially a glorified plt.imshow so it should return the same kind of object.

I'm torn on this idea, on one hand it's convenient to obtain the main plot object from the function for advanced plots, on the other hand:

Plot methods will output something in every Python intepreter (see the failing CI > https://github.com/dynamiqs/dynamiqs/actions/runs/11327666084/job/31499221146?pr=756) or notebook, which is a bit invading, especially since the return won't be used most of the time.
Every sub-object of the plot can already be accessed in one line with the native Matplotlib methods ax.get_images()/ax.get_children()/ax.patches.

Following discussion with @pierreguilmin, closing for now because we're not sure the upsides outweigh the downsides. Happy to reopen this if we change our mind later on, depending on requests too.


Add default context to Android implementation

To eliminate the need to initialise KVault from both platforms we have to give the Android implementation a default context. Preferably by a non-hacky way.

https://developer.android.com/topic/libraries/app-startup 👀

Won't do


Scoring system

How does scoring work?
What do we all get points for?
How many points do I get for each award?

Score Table:
Asteroid:
    10 PTS
Cosmo-Mine:
    20 PTS
I-Type (Missile):
    50 PTS
P-Type:
    60 PTS
E-Type:
    70 PTS
Spy Ship:
    Mystery
Enemy Base Cannon:
    200 PTS
Enemy Base:
    1500 PTS


[Button] Documentation update

Update of the button guidelines is available here.
Changes coming with the update:

[x] Secondary border-width changes from 2px to 1px, focus state remains as 2px.
[x] Height of the component is reduced from 43px to 40px
[x] Removal of text-transform: uppercase property
[x] Increase in the font-size from 14px to 16px
[x] Spacing between icon and label is 8px
[x] Reduced padding-left and padding-right from 30px to 24px

Changes implemented in the branch advance-theme. They will be available in the next release. Closing issue.


Weather module doesn't work for some cities

When I asked Jarvis:
"weather san diego" or "weather sacramento,"
it said: "I couldn't get the weather info you asked for."
I'll start working on this when I get some time.

It does work when I ask:
"what's the weather in san diego?"

@cyrokamogawa are you working on this issue or can i start looking into it?

Hi, go for it! I never got the time.

ok, I will start looking into it today.


Doc custom

Superseding : https://github.com/expressjs/morgan/pull/123
Dropped for: #125 #127
Documents custom tokens and formatters a bit more/makes the API public knowledge in order to keep it stable in future. Also adds a few tests. Used *Each in tests because after doesn't work as expected.

Thanks, @bmeck . Looks like there is a lot going on in this PR than just a docs change, so will need some time to look through it.

I'm not sure what is happening and where some of your comments are disappearing to; there is so much happening and every email for your comments simply link to https://github.com/expressjs/morgan/pull/124 which is not helpful. Please forgive me if I'm not responding to everything, because some of your comments I just cannot find to respond to.

Gonna just take a step back and probably bail on this, seems a lot of
pushback.
On Oct 6, 2016 9:07 PM, "Douglas Wilson"<EMAIL_ADDRESS>wrote:

I'm not sure what is happening and where some of your comments are
disappearing to; there is so much happening and every email for your
comments simply link to https://github.com/expressjs/morgan/pull/124
which is not helpful. Please forgive me if I'm not responding to
everything, because some of your comments I just cannot find to respond to.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/expressjs/morgan/pull/124#issuecomment-252136717, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAOUoxPDbBXyfSRNWsIjh7wGllMsieRcks5qxalHgaJpZM4KQJUH
.

Sorry, reading back my comment I see what you mean. The "not helpful" was a comment to GitHub, in that the emails they are sending me are not helping me locate where your comment is in order for me to actually reply; it was not directed at you, I'm sorry if it came off that way :(

@dougwilson took another stab at this on https://github.com/expressjs/morgan/pull/125

@dougwilson split into #125 and #127

Thanks you two; I have taken a look at both PRs now. It seems like some of the review comments from this review got lost in the shuffle to new reviews, so if you re-read through here and see any that apply to your PR, that would help a lot! Otherwise I'll spend some time over this week cherry picking theones that still apply :)


Update view-service-health.md

Updating content for the latest changes that have been made to the service health dashboard.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@JoeDavies-MSFT Please merge this PR. Thanks


Add support for downloading files from a DICOMweb server

This will require implementing this function.
It would be beneficial to support offsetting, if possible.
Note the discussion here.

One thing that complicates this is that currently each item is associated with a series, and there is a single file per item. However, each series typically contains more than one DICOM file (which is often referred to as an "instance").
We could, for instance, use this function to retrieve all instances in a series. However, this is likely to return multiple DICOM datasets (each of which can be written to a file).
Alternatively, this function can be used to retrieve a single instance (a.k.a., a single DICOM dataset).
Perhaps we should modify our assetstore model to make separate files for each instance, so we can more easily support downloading files?
For actually downloading the files themselves (as raw data in chunks): the DICOMwebClient API doesn't provide us an easy way to do this. However, I think we can take inspiration from their code. For instance, this function is a way to obtain a resource in chunks. We could obtain a DICOM file this way (using the application/dicom content type), as long as we can figure out the URL as well.

If we used the retrieve_series to get all of the files conceptually, and downloaded them and then created a zip of those, does that zip file open with our dicom source reader?  If so, perhaps we should expose that conceptually (range requests will be tricky, but if the individual files don't have further compression inside the zip, this could work).


Can't catch and can't explore

On giving the commands catch and explore, the following error happens
panic: runtime error: index out of range [1] with length 1
goroutine 1 [running]:
github.com/shahank42/poketext/internal/repl.Init.func6({0xc00002a110?, 0xc000024a20?, 0xc00000a1f4?})
C:/repos/poketext/internal/repl/repl.go:63 +0x3c
main.main()
C:/repos/poketext/main.go:29 +0x1c2

Sorry my bad, I should've been clearer with the instructions.
Here's how you would use the application:

map and mapb commands to move through the list of areas (no arguments)
explore  to see the available Pokemon in an area
catch  to catch a particular Pokemon
inspect  to inspect an already caught Pokemon
pokedex to view your caught pokemon

It's basically an error handling problem, and I need to add the argument info to the help as well.


GTK library autocomplete is not present, infact there is no extension present for same.

You probably need to use the C++ extension and configure it for your project - https://github.com/Microsoft/vscode-cpptools


Remove unused Filter/Pagination from Iterations

Related to #572
https://github.com/almighty/almighty-core/pull/572#discussion_r92841860

Current coverage is 69.68% (diff: 100%)

Merging #597 into master will decrease coverage by 0.05%

@@             master       #597   diff @@
==========================================
  Files            74         74
  Lines          4286       4285     -1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           2989       2986     -3
  Misses         1012       1012
- Partials        285        287     +2

Powered by Codecov. Last update 1d5aacc...d54f4ea


Carousel gradient leaves 1px black line on inner edge in Safari

The carousel gradient leaves 1px black line on inner edge. This seems to be Safari specific and introduced with v8.0 (I'm running MacOS 10.10.1). It is also browser window size dependent, as you grow and shrink the window you'll see this line flicker and come and go. The color of this line appears to follow the color of the opposite side of the gradient as well, so if I make the far end green, this 1px line will be green.
I am seeing it reproduce on a few public websites on the left gradient, and on the bootstrap examples page on the right gradient.
Examples:
http://www.sccmas.org/dayatfield.php

http://thecurlybaker.com

http://getbootstrap.com/javascript/#carousel

Is there a workaround for this?

Nope, unless you get rid of the gradient entirely.
File a duplicate Radar problem (of http://openradar.appspot.com/19434933) at https://bugreport.apple.com if you want to help bring Apple's attention to the problem.

This has been fixed in WebKit Nightly as of r186963: http://wkbug.com/139803


inviting room

Do you plan inviting room plan?

Yes. This is a duplicate of #243.

Thanks a lot :+1:


Updating 6.0 Service Fabric spec

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@samedder Your code changes have created new linter errors that need to be fixed. Please fix them and update the PR

Closing and re-opening so that CI can leverage bug-fixes. Thanks!

@sarangan12 AFAIK all the errors are just camel-case convention guidelines. @VipulM-MSFT can comment more but we won't be fixing these as they're named in the convention our tools expect.

@sarangan12 and @vishrutshah - Can you let us know what is needed to merge this?

@VipulM-MSFT We have talked to @salameer about this and being this data-plane, so please add the suppression in the README.md file so that we can get this going.
@sarangan12 would be able to help you guys with the suppression if you need it :)

The suppressions are going to take time and will be in the 6.1.x.x release. I will add you to that thread. This the 6.0.x.x release we should continue with the current process.

@VipulM-MSFT Sounds good. Just opened an issue to this on the radar. https://github.com/Azure/azure-rest-api-specs/issues/1786.
@sarangan12 Feel free to merge this in if we do not have any more comments/feedbacks apart from cameCase. Thanks!

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-ruby

 https://github.com/Azure/azure-sdk-for-python/pull/1508


Init new blogpost

New Blogpost Series: Handling asynchronous task in Cloudflare workers

@brettimus I already opened a PR for the blog but would be still good to get your eyes on this before publishing


Add feature

Can you add download file from shell?

what do you mean by that, that the attacker sends a file and the victims download it and runs it?

No, i mean the execute shell. Can i put a command download file from victim?

you mean that the attackers received a file from the victim's pc?

waiting for a reply, or i will close this

Yes

you mean that the attackers received a file from the victim's pc?

I mean that


Wheel build for Datajoint failing on macOS 12 using mamba

See here: https://github.com/SainsburyWellcomeCentre/aeon_mecha/actions/runs/6004715050/job/16285882719#step:3:1161
@JaerongA noted that it's attempting to install datajoint from @ttngu207 's fork

The one known potential cause for this issue has been resolved. Please try running this again


Grammatical error in Cloud-Bot-Account

Repeatedly use of the word 'an' in one place , grammatical error and incorrect use of grammatical symbols

Summary

Ticket Link

Hello @megamer07,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

Closing this PR


"No Healthy Upstream" Error on Multiple Networks and Devices

What is the issue?
I am experiencing a recurring issue when attempting to access the Ollama website and download models across multiple networks and computers. The error message "no healthy upstream" appears consistently in the following scenarios:

When I access the Ollama website from different networks and computers, the site fails to load, returning "no healthy upstream."
When trying to install or pull models using the command:curl -fsSL https://ollama.com/install.sh | sh

I receive the following error:curl: (22) The requested URL returned error: 503

Attempting to run a model (llama3.1) using the following command:./ollama run llama3.1

results in:pulling manifest
Error: pull model manifest: 503: no healthy upstream

Steps to Reproduce:

Open the Ollama website from multiple devices and different network setups.
Run the installation command:
curl -fsSL https://ollama.com/install.sh | sh
Attempt to pull or run the llama3.1 model using:
./ollama run llama3.1

Expected Outcome:
I expect the website to load correctly and for the installation and model pulling processes to complete without errors.
Actual Outcome:
The website fails to load, and the commands return a "503: no healthy upstream" error across different networks and devices.
Environment:

OS: Ubuntu 24.04
Networks: Tested on multiple networks (office, phone, servere)
Devices: Multiple computers

OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.3.6

This should be fixed now. Sorry about that!


Make fake in db-sync optional

It should be optional in case you would want to sync your data between for example two live servers.

Nice work!


RFC: Remove flags from language representations

There's a strong argument against using flags to represent languages. Flags are symbols for countries, however, a language may be spoken in many countries while a single country may have multiple official+unofficial languages. This makes flags at least a weak, usually blatantly wrong, and in some cases offensive representation for a language.
Here's a good summary resource for this argument: http://www.flagsarenotlanguages.com/blog/why-flags-do-not-represent-language/
I believe it would be a good decision to drop flags from the progress report panel and anywhere else in the UI.

The exception may be when the language key includes a locale. en is English without geographical context, so it could be for UK, Australia, Malta or India, or even Japan, you wouldn't know. en-US is clearly for United States, which makes it ok (but still unnecessary) to use a flag.
I believe the best representation would be the name of the language in itself, optionally followed by the name of the language in the language of the editor/OS

English
Français - French
Svenska - Swedish
Türkçe - Turkish

Emmm... I don't know. I am happy to provide a config field to disable flags if anyone feels being "offensive" (although it's absolutely not intentional).
Anyway, I am feeling that I am not knowledgeable enough to make the decision (to completely drop it). I have pinned this issue and labeled rfc. I would love to hear comments from anyone. Thanks in advance.

Maybe a config field is a good idea.

Not to mention, please do not confuse the ISO 639-1 language code with the ISO 3166-1 country code.
ca in ISO 639-1 stands for the Catalan language, while ca in ISO 3166-1 stands for Canada.

This is quite a hairy issue, best avoided 😬🤯😅

Thanks for the info! Will fix it.

Good luck with that :)
Made a spreadsheet for you with the fake match between country and language codes.
Out of the 186 language codes and 250 country codes, there are 110 codes that match. Out of those 110 matches, only 22 of them have some semblance of connection between the country and the language (ie. at least it is an official/major language there).
88 matches in that list are almost totally wrong outright.

@edgerunner wow, thanks a lot! How do you get the results? Do you have any tools or just by manually checking?

Just went through the list and marked the (somewhat) relevant ones. Took about 3 minutes. I may have missed one or two.
My point is: This is a bottomless hole. Don't jump in 😅

I am trying to find some balance point to this issue.
Now in v2.2.4
Config to disable the flags
"i18n-ally.showFlags": false

Not to use language code as country code
Two letters locales are not be used as country code to display flags anymore. While BCP-47 with region/country code will try to match a flags

If you have preference on mapping a two letter locale to country code, you can do it in config:
"i18n-ally.localeCountryMap": {
  "en": "br", // show UK's flag instead of US's
  "zh": "cn", // show Chinese flag for 'zh'
  "ko": "ko", // show Korean flag for 'ko'
}

Let me know if you have any comments. Thanks

You're getting things done at breakneck speed 🚀 ❤
I think it is great as it is :)


fsstore backend for Store2

Release note:

fsstore: "fs://" store backend is added to Store2 too. Helpful for e2e tests.

This change is

PTAL
Updated the implementation to follow what @mandarjog is saying.
Also, due to offline discussion with @mandarjog, contextch.go file is removed. That's not necessary anymore with an assumption that a store supports a single watch channel at the same time.

@jmuk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
143274dd979ef2df72b01d68ab83b233d2547aae
link
/test mixer-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Apart from nits... would be good to fix during rebase
/lgtm

/approve cancel
Apparently I need to hold of lgtm until the nits are resolved.

/lgtm

/lgtm


Replace SOM in list of counties accepting transcribers

For 1901 census

Hi Denise,
Notts are also accepting 1901 transcribers as well
On Mon, 23 Mar 2020 at 11:36, DeniseColbert<EMAIL_ADDRESS>wrote:

For 1901 census
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/828, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIL3VV4MJ5SB5G4KQR2YGLRI5CTVANCNFSM4LRZVOLA
.

Thanks, Brenda. Just to note, Allan tells me that FreeBMD Coords are able to do this themselves:

Coordinators are able to switch on and off a recruitment flag, when
it is switched off their details will not appear in the selection list
mentioned in 1 above.

Done for CEN2; no idea on CEN1

Hi,
Not checked but the COORDS are happy to be getting more helpers.
Therefore the ability to turn it off is not an issue at the moment.
I will check it out though as I have not seen it myself.
I have just tried to find it but not had any luck so if someone can say which of the many boxes to search is the one I need.
I did not know that it was switched off so I assume that Geoff raised this query now he has some 1901 to work on.
From: DeniseColbert<EMAIL_ADDRESS>Sent: 23 March 2020 16:32
To: FreeUKGen/FreeCENMigration<EMAIL_ADDRESS>Cc: Brenda<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [FreeUKGen/FreeCENMigration] Replace SOM in list of counties accepting transcribers (#828)
Thanks, Brenda. Just to note, Allan tells me that FreeBMD Coords are able to do this themselves:
Coordinators are able to switch on and off a recruitment flag, when
it is switched off their details will not appear in the selection list
mentioned in 1 above.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/828#issuecomment-602712516 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIL3VXEDLPIUUJ3HYNHZTDRI6FIZANCNFSM4LRZVOLA .

All syndicate coordinators in both REG2 and CEN2 have that ability now

Hi Brenda, ] If a Coord has a county with no/limited images, they might need to turn that county off.
I will draft instructions, for you to road test, if you will.

No change needed on FreeCEN1 as there is no information on that site about counties looking for transcribers.

Hi Brenda,
It is ihe list of coord actions in FreeCEN2.  If a Coord has a county with
no/limited images, they might need to turn that county off.
I will draft instructions, for you to road test, if you will.
Cheers,
Pat
On Mon, 23 Mar 2020 at 18:02, Brenda<EMAIL_ADDRESS>wrote:

Hi,
Not checked but the COORDS are happy to be getting more helpers.
Therefore the ability to turn it off is not an issue at the moment.
I will check it out though as I have not seen it myself.
I have just tried to find it but not had any luck so if someone can say
which of the many boxes to search is the one I need.
I did not know that it was switched off so I assume that Geoff raised this
query now he has some 1901 to work on.
From: DeniseColbert<EMAIL_ADDRESS>Sent: 23 March 2020 16:32
To: FreeUKGen/FreeCENMigration<EMAIL_ADDRESS>Cc: Brenda<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [FreeUKGen/FreeCENMigration] Replace SOM in list of counties
accepting transcribers (#828)
Thanks, Brenda. Just to note, Allan tells me that FreeBMD Coords are able
to do this themselves:
Coordinators are able to switch on and off a recruitment flag, when
it is switched off their details will not appear in the selection list
mentioned in 1 above.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <
https://github.com/FreeUKGen/FreeCENMigration/issues/828#issuecomment-602712516>
, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ADIL3VXEDLPIUUJ3HYNHZTDRI6FIZANCNFSM4LRZVOLA>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/828#issuecomment-602764245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADK5GHL2ICHLS6CWT3XPMATRI6P27ANCNFSM4LRZVOLA
.

--
- -
Dr Pat Reynolds
Executive Director
Free UK Genealogy  http://www.freeukgenealogy.org.uk/
A Charitable Incorporated Organisation registered in England and Wales,
number 1167484
VAT registration: 233 0105 70
Join us on social:
Please read our Privacy Notice
https://www.freeukgenealogy.org.uk/files/Documents/Privacy-Notice.pdf for
information on how we will protect and use your data.
+44 1723 362616   +44 7943 145387
Westwood House,Westwood, Scarborough YO11 2JD, UK

Draft sent to Brenda 29/4/2020

@PatReynolds to ask Brenda again

Tansferring to Denise.

@Pat to ask Geoff

contacted 11/8/2020

I have tested this in test3 and it works fine.
I have also included Pats notes on how to use it in  the FreeCEN Handbook.
Geoff

Thanks @geoffj-FUG


Move startup into its own method.

Makes it easier to import glados into other modules (eg any UI that may happen to exist!)
Should probably move some files around to make everything PEP compliant. At the moment there is both a module and a package called glados, which plays havoc with installers, and necessitates monkey patching to get it installed properly.  But that is for another PR.

Summary by CodeRabbit

Refactor

Streamlined the server setup and execution process by consolidating the main script logic into a new start() function.

Looks fine, nice catch.


npm run dev / npm run watch Error on fresh Laravel installation

Description:
First off, thanks for creating Laravel Mix, it's a godsend. That said, we're still having this issue with npm run watch or npm run dev with a fresh installation of Laravel (no code changes at all). I know there is a workaround (see below), but not sure why we'd have to go through so many steps?
$ laravel new testmix
$ npm run dev
The following error is seen:
OneStepAtATime:testmix kunalpunjabi$ npm run dev

> @ dev /Users/kunalpunjabi/Code/testmix
> npm run development

> @ development /Users/Code/testmix
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: spawn node_modules/webpack/bin/webpack.js ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
    at onErrorNT (internal/child_process.js:407:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:744:11)
    at startup (internal/bootstrap/node.js:285:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
    at onErrorNT (internal/child_process.js:407:16)
    [... lines matching original stack trace ...]
    at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ development script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR!      /Users/kunalpunjabi/.npm/_logs/2019-06-08T00_58_49_951Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ dev: `npm run development`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR!      /Users/kunalpunjabi/.npm/_logs/2019-06-08T00_58_49_988Z-debug.log

Steps To Reproduce:
See above.
Environment:

Laravel Mix Version: #.#.# (npm list --depth=0)
/Users/Code/test-mix
└── (empty)
Node Version (node -v): v10.13.0
NPM Version (npm -v): 6.9.0
OS: Mac OS High Sierra 10.13.4 (17E199)
Laravel Framework: 5.8.21

Workaround:
Run the following commands, but again, why are these necessary? Can't we fix this and avoid the pain for many a developer?
composer update
rm -rf node_modules
npm cache clean --force
npm install
npm run dev

Your work around steps worked for me.

Thanks for this update.

This did not work for me, i still get errors

@UgwuObed  can you post the exact errors you are getting? Along with the errors can you gives is steps to reproduce your specific situation?


Setup Help

I am following your code and am a little confused. I have a default cakephp instal and would like to use your plugin. Right now I would like to use the sql as defined as it will work perfect. How do I set this up the best? Do I need a users controller and model?
Also reading through your UserToolComponent.php I see you defined the emails like below.
'reset_password' => [
    'method' => 'resetPassword',
    'view' => 'UserTools.UserTools/reset_password',
],
'request_password' => [
    'method' => 'requestPassword',
    'view' => 'UserTools.UserTools/request_password',
],
'verify_email' => [
    'method' => 'verifyEmailToken',
    'view' => 'UserTools.UserTools/verify_email',
],

But in the package I see new_password.ctp , password_reset.ctp and verification_email.cp.

These are not the emails but the views for the actions.
The component intercepts the request for actions that don't exist in the controller and uses the plugin methods + plugin views for that. What you pasted above is the mapping of the action to the component method + it's view.

I have read the readme but could you explain the install for a default cake installation? I added in a example login from their example pages.

What exactly is unclear in the documentation? It explains it pretty well I think.
If you have trouble with composer please check it's documentation. If you don't know how CakePHP plugins work see this page.
I don't mind fixing bugs and giving some community support but if you want personal support feel free to hire me for my usual rate.

I tried reaching you by your website but the CAPTCHA won't verify, Are you available for a small task. I am looking for a default cakephp3 install with your user-tools and https://github.com/dereuromark/cakephp-tinyauth

Thanks, I've fixed the form, fugly Wordpress, should switch to Croogo.
I can install TinyAuth for you but this is easy, just configure Auth in your AppController and the plugin will use these settings and not load the Auth component and use it's default settings.
Try using the contact form again, it it still doesn't do it's job please let me know. Send me your exact requirements so that I can estimate it.


Remove the ability for the superuser to delete users

Summary
Remove the button for deleting users from the admin's user list
Why?
We don't need it, there is potential confusion, and if it is used on a partner who has ever made a requests, we get a 500.
Details
Remove the button for deleting users from the admin user index (N.B. not the button for deleting roles on the individual view)
To see this,  sign in as<EMAIL_ADDRESS>click Users in the left-hand menu, then All Users
Criteria for completion

[ ] the button is removed
[ ] tests modified to reflect the new behaviour
[ ] tests pass
[ ] screenshots in the PR are a nice-to-have.

Hello @cielf, could I try taking this on?

Go for it!


chore: update readme and add secrets baseline

Close #1

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


[FEATURE] Having a langchain4j-test module with helper classes

Is your feature request related to a problem? Please describe.

Today we have test classes (such as ChatModelMock) that would be helpful to expose so we can use them in our unit/integration tests. It would be nice to have a separate langchain4j-test module that we could use.
Describe the solution you'd like

Have a separate langchain4j-test module, have langchain4j-core depending on it.

After a quick analysis, ChatModelMock implements ChatLanguageModel. If we move ChatModelMock to a langchain4j-test module it will depend on langchain4j-core module... which will depend on langchain4j-test. This will break because of cyclic dependency.
I'll investigate a bit more


Support v2 plugins in swarm mode

This PR vendors a swarmkit PR that adds awareness of v2 plugins to the scheduler. Services that depend on a particular volume or network plugin will only be dispatched to nodes which have that plugin installed.
It updates the agent's executor to publish a list of v2 plugins to the manager.
It also fixes a problem in volume creation when the volume driver is a plugin. Trying to create a volume with the same name and parameters as one that already exists generally returns no error, but if a plugin name without a tag is specified, this always resulted in a conflict (plugin vs plugin:latest). The fix is to resolve the volume driver and compare its canonical name instead of the name passed in by the caller.
ping @anusha-ragunathan @vieux @tonistiigi @aluzzardi @nishanttotla @cpuguy83

@aaronlehmann test failure seems genuine. also does this depends on https://github.com/docker/swarmkit/pull/1808 ?

Yes, this depends on docker/swarmkit#1808. I updated this PR to formally vendor SwarmKit now that docker/swarmkit#1808 has been merged. I was originally going to do it in a separate PR, but it's important that the changes here get merged at the same time.
This also seems to fix the IPAM test failure. I think the branch being vendored here before was outdated.
The volume create test failure is because the test uses a volume driver that doesn't exist, and now it will get an error about that, instead of getting the name conflict it's looking for. Any ideas on how to solve that? Are there two volume drivers that can be used by the test to trigger the condition?

Fixed the other test. PTAL. This should be good to go.

LGTM, minus the Windows failure

The Windows failure should be fixed now. I moved TestVolumeCLICreateOptionConflict to DockerExternalVolumeSuite because it now uses some Linux-specific code.
After this PR is merged, I plan to open a similar PR against the 1.13 branch. It will revendor swarmkit to the latest version of swarmkit's 1.13 branch (which includes the changes vendored here), and cherry-pick the two engine commits from this PR.

Opened a 1.13 version of this PR here: https://github.com/docker/docker/pull/29433. Removing the process/cherry-pick label and 1.13 milestone from this PR, since 1.13 will get this from the backport PR.

This should be merged ASAP because the 1.13 backport in #29433 was already merged.


Beta: Name of the challenge missing in a map.

I've often seen this issue, while opening the map, I am not able to see the recent completed challenge on the map. Maybe it's an issue to look on?

Relates to #14949

Hello,
this my first time contributing to open-source, so sorry if I made any mistakes.
I have checked the source code. It's not a css or js problem. The text hasn't been written.

@moaz-eldefrawy Thanks, and yes @jonathanihm you are correct. Closing this as a duplicate


Build fails for webview feature

Hi, this crate is currently failing to build with the webview feature turned on.
From the build errors it looks like this is due to the recent refactoring work on the Layout components:
Build errors
```
-cargo build --features=webview
   Compiling cacao v0.1.0 (/Users/david/gits/cacao)
error[E0599]: no variant or associated item named `new` found for enum `LayoutAnchorY` in the current scope
   --> src/webview/mod.rs:131:33
    |
131 |             top: LayoutAnchorY::new(unsafe { msg_send![view, topAnchor] }),
    |                                 ^^^ variant or associated item not found in `LayoutAnchorY`
    |
   ::: src/layout/vertical.rs:11:1
    |
11  | pub enum LayoutAnchorY {
    | ---------------------- variant or associated item `new` not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorX in the current scope
--> src/webview/mod.rs:132:37
|
132 |             leading: LayoutAnchorX::new(unsafe { msg_send![view, leadingAnchor] }),
|                                     ^^^ variant or associated item not found in LayoutAnchorX
|
::: src/layout/horizontal.rs:14:1
|
14  | pub enum LayoutAnchorX {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorX in the current scope
--> src/webview/mod.rs:133:38
|
133 |             trailing: LayoutAnchorX::new(unsafe { msg_send![view, trailingAnchor] }),
|                                      ^^^ variant or associated item not found in LayoutAnchorX
|
::: src/layout/horizontal.rs:14:1
|
14  | pub enum LayoutAnchorX {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorY in the current scope
--> src/webview/mod.rs:134:36
|
134 |             bottom: LayoutAnchorY::new(unsafe { msg_send![view, bottomAnchor] }),
|                                    ^^^ variant or associated item not found in LayoutAnchorY
|
::: src/layout/vertical.rs:11:1
|
11  | pub enum LayoutAnchorY {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorDimension in the current scope
--> src/webview/mod.rs:135:43
|
135 |             width: LayoutAnchorDimension::new(unsafe { msg_send![view, widthAnchor] }),
|                                           ^^^ variant or associated item not found in LayoutAnchorDimension
|
::: src/layout/dimension.rs:20:1
|
20  | pub enum LayoutAnchorDimension {
| ------------------------------ variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorDimension in the current scope
--> src/webview/mod.rs:136:44
|
136 |             height: LayoutAnchorDimension::new(unsafe { msg_send![view, heightAnchor] }),
|                                            ^^^ variant or associated item not found in LayoutAnchorDimension
|
::: src/layout/dimension.rs:20:1
|
20  | pub enum LayoutAnchorDimension {
| ------------------------------ variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorX in the current scope
--> src/webview/mod.rs:137:38
|
137 |             center_x: LayoutAnchorX::new(unsafe { msg_send![view, centerXAnchor] }),
|                                      ^^^ variant or associated item not found in LayoutAnchorX
|
::: src/layout/horizontal.rs:14:1
|
14  | pub enum LayoutAnchorX {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorY in the current scope
--> src/webview/mod.rs:138:38
|
138 |             center_y: LayoutAnchorY::new(unsafe { msg_send![view, centerYAnchor] }),
|                                      ^^^ variant or associated item not found in LayoutAnchorY
|
::: src/layout/vertical.rs:11:1
|
11  | pub enum LayoutAnchorY {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorY in the current scope
--> src/webview/mod.rs:162:33
|
162 |             top: LayoutAnchorY::new(unsafe { msg_send![view, topAnchor] }),
|                                 ^^^ variant or associated item not found in LayoutAnchorY
|
::: src/layout/vertical.rs:11:1
|
11  | pub enum LayoutAnchorY {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorX in the current scope
--> src/webview/mod.rs:163:37
|
163 |             leading: LayoutAnchorX::new(unsafe { msg_send![view, leadingAnchor] }),
|                                     ^^^ variant or associated item not found in LayoutAnchorX
|
::: src/layout/horizontal.rs:14:1
|
14  | pub enum LayoutAnchorX {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorX in the current scope
--> src/webview/mod.rs:164:38
|
164 |             trailing: LayoutAnchorX::new(unsafe { msg_send![view, trailingAnchor] }),
|                                      ^^^ variant or associated item not found in LayoutAnchorX
|
::: src/layout/horizontal.rs:14:1
|
14  | pub enum LayoutAnchorX {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorY in the current scope
--> src/webview/mod.rs:165:36
|
165 |             bottom: LayoutAnchorY::new(unsafe { msg_send![view, bottomAnchor] }),
|                                    ^^^ variant or associated item not found in LayoutAnchorY
|
::: src/layout/vertical.rs:11:1
|
11  | pub enum LayoutAnchorY {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorDimension in the current scope
--> src/webview/mod.rs:166:43
|
166 |             width: LayoutAnchorDimension::new(unsafe { msg_send![view, widthAnchor] }),
|                                           ^^^ variant or associated item not found in LayoutAnchorDimension
|
::: src/layout/dimension.rs:20:1
|
20  | pub enum LayoutAnchorDimension {
| ------------------------------ variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorDimension in the current scope
--> src/webview/mod.rs:167:44
|
167 |             height: LayoutAnchorDimension::new(unsafe { msg_send![view, heightAnchor] }),
|                                            ^^^ variant or associated item not found in LayoutAnchorDimension
|
::: src/layout/dimension.rs:20:1
|
20  | pub enum LayoutAnchorDimension {
| ------------------------------ variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorX in the current scope
--> src/webview/mod.rs:168:38
|
168 |             center_x: LayoutAnchorX::new(unsafe { msg_send![view, centerXAnchor] }),
|                                      ^^^ variant or associated item not found in LayoutAnchorX
|
::: src/layout/horizontal.rs:14:1
|
14  | pub enum LayoutAnchorX {
| ---------------------- variant or associated item new not found here
error[E0599]: no variant or associated item named new found for enum LayoutAnchorY in the current scope
--> src/webview/mod.rs:169:38
|
169 |             center_y: LayoutAnchorY::new(unsafe { msg_send![view, centerYAnchor] }),
|                                      ^^^ variant or associated item not found in LayoutAnchorY
|
::: src/layout/vertical.rs:11:1
|
11  | pub enum LayoutAnchorY {
| ---------------------- variant or associated item new not found here
error[E0308]: mismatched types
--> src/webview/mod.rs:219:76
|
219 |     fn get_from_backing_node<F: Fn(&Object) -> R, R>(&self, handler: F) -> R {
|        ---------------------                      -                        ^ expected type parameter R, found ()
|        |                                          |
|        |                                          this type parameter
|        implicitly returns () as its body has no tail or return expression
|
= note: expected type parameter R
found unit type ()
error: aborting due to 17 previous errors
Some errors have detailed explanations: E0308, E0599.
For more information about an error, try rustc --explain E0308.
error: could not compile cacao
To learn more, run the command again with --verbose.
</p></details>

Hmmm, wouldn't surprise me - but I can patch this up today. Will probably write some GitHub CI tests to at least try building on each push to catch stuff like this; my "kitchen sink" app uses just about everything... except the webview, lol
Appreciate the heads up!

This should be fixed - there's also a (very basic, this week is rough time-wise for me) browser example that can be run with the following:
cargo run --example browser --features webview

Thanks for getting it updated so quickly!