Shell log commands crash the system if CONFIG_SHELL_LOG_BACKEND is not defined

Describe the bug:
When accessing the shell over RTT channel 0 and the log backend over RTT channel 1, some log shell commands (e.g. log status, log go, etc.) will crash the system if the shell log backend (CONFIG_SHELL_LOG_BACKEND) is not configured.
It is easy to avoid the problem by not executing some log commands, however a new user of Zephyr RTOS is unlikely to be aware of such things and will likely have a bad initial experience.
Diagnosis:
I found that in log_cmds.c the function shell_state_precheck(...) does not check log_backend pointer before dereferencing:
static bool shell_state_precheck(const struct shell *shell)
{
	if (shell->log_backend->control_block->state
				== SHELL_LOG_BACKEND_UNINIT) {
...

and in shell_log_backend.c the pointer is defined as NULL.
https://github.com/zephyrproject-rtos/zephyr/blob/9bc9e15852559fd26f48882c92c4642d1ef0456f/include/shell/shell_log_backend.h#L103
Debugger shows that log_backend does not point to a valid control_block:

To Reproduce:

Configure a project to use RTT for the shell and log backends with following CONFIGs:

CONFIG_USE_SEGGER_RTT=y

CONFIG_SHELL=y
CONFIG_SHELL_BACKEND_RTT=y
CONFIG_SHELL_LOG_BACKEND=n

CONFIG_LOG=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_RTT_BUFFER=2

Ensure CONFIG_SHELL_LOG_BACKEND is not defined (as shown above).
Compile and flash a target.
After connecting to the shell run one of the log commands, e.g. log status.
The system will crash.

Expected behavior:
No output and the shell prompt should return, or an error message (that the shell log backend is not enabled).
Impact:
The bug crashes the system and this is overall a bad user experience.
Logs and console output:
Example of working command:
rtt$ log backend
backend - Logger backends commands.
Subcommands:
  log_backend_rtt  :
rtt$

Example of command that crashes the system:
rtt$ log go
<no output; hard fault>

Environment:

OS: MacOS
Toolchain: GCC 10.2.1
Commit: v2.6.0

@brycewilkins - it sounds as though you have identified the root cause. Would you be willing to make a PR to fix it?

@cfriedt Yes, I can put up a PR to fix it.

@brycewilkins i've disabled those commands when logging is not enabled.

@brycewilkins i've disabled those commands when logging is not enabled.

Yeah, I discovered yesterday that CONFIG_LOG_CMDS=n masks the problem, but it has to be done explicitly (CONFIG_LOG_CMDS will default to y if SHELL is enabled).
Thanks @nordic-krch for the fix!


Add manifest file for Adobe Acrobat Reader DC (MUI) 2020.012.20048

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

The manifest has been placed in manifest/Adobe/AdobeAcrobatReaderDC
I have deleted the other manifests in the folder, as requested

You can only modify one file per pr.

You can only modify (creating, deleting, change) one file per pr.
@azure-pipelines
azure-pipelines
/ WinGetSvc-Validation (Pull Request Validation)

Build log #L25
 The pull request contains more than one manifest file.

You're right, sorry for that ! I've deleted the other manifest I added in the pull request

You're right, sorry for that ! I've deleted the other manifest I added in the pull request

This rule (one file per pr) gonna change. You can look backlogs.
https://github.com/microsoft/winget-pkgs/milestone/1
Thanks for your contribution. 🥂


Regression in Falcon7b-prefill-128-async t3000 perf test

There has been a regression in the Falcon7b-prefill-128-async t3000 inference time from 0.09s to 0.1s.
Last passing run: https://github.com/tenstorrent/tt-metal/actions/runs/9465212387
First failing run: https://github.com/tenstorrent/tt-metal/actions/runs/9472989413

@pavlepopovic @s-jovic would you be able to take a look? The inference times for the other prefill configs seem unaffected.

I'll take a look

I've run the test locally 10 times on latest main on t3006 machine. 9 test runs result in inference time less then 0.09s, 1 took 0.119s, so it seems like some kind of a glitch happens once in a couple of runs.
Also, on latest run on main ( https://github.com/tenstorrent/tt-metal/actions/runs/9508548757 ) , 128-async-prefill took 0.081s (the tests failed due to mixtal seg fault, but prefill succeeded and reported numbers).

I saw the slower inference time a couple times on different runs, but if we see that the newer runs have better perf again perhaps we can just readjust the target.

Had a theory that machine was not in perf_mode, hence causing this (took inspiration from this thread). And indeed, t3006 was set to run in 'on demand' mode. Tried switching it to 'performance', and it made no difference, there's still flakiness)
Having an accurate value as expected inference time is welcome, so we know when the test fails it is due to a regression.
Thinking that we should maybe run the inference say 10 times, and report min as the model_inference_time? Hopefully that way it'll be more stable

Yes, warmup runs is a good idea in general, but I'm not sure if it will help fix this issue as it seemed specific to only this prefill config and not the other ones.


Minimize to System Tray

It would be simple and very useful to be able to leave the wallet running without disturbing the day to day with the window open.

Sorry but i hate this.  Minimizing should not make the program disappear from the window list in the taskbar.
I'll let others comment but i doubt this will change.

Placing another icon (ugly sugestion) would be an option or preferences to let the user decide.

or

I know this kind of thing is not a priority, but it helps to maintain user retention.


Commands: PMC cmdlets for xproj

Having to drop down to the cmd line and use dnx is very jarring compared to staying in VS.
We need to do some work to enable this, but most of it is in NuGet and xproj tooling:

https://github.com/NuGet/Home/issues/1174
https://github.com/aspnet/Tooling-Internal/issues/443

Work is required in NuGet and xproj tooling before we can light this up

Moving to RTM. This won't be unblocked for RC1.


Create vntu.txt

Please, create the right file vNtu.txt instead of vStu.txt for the domain vntu.net for Vinnytsia National Technical University

@siloenix A domain for this university seems to be vntu.edu.ua, not vntu.vinnica.ua. Could you please change the path to lib/domains/ua/edu/vntu.txt, if I am right regarding the domain?

Yes, you are right. But our university has 2 domains. Second is vntu.net, and a lot of students' emails are created on this domain, me too.
I'll create 2 files in 2 directories: edu and net – am I right?

@siloenix Yes, you did it right, but I see nothing in this request but lib/domains/ua/vinnica/vntu.txt. A domain vntu.vinnica.ua does not exist, thus you probably need to make a new request and submit both files for vntu.edu.ua and vntu.net there. Please ask for help here in comments if you have troubles with submitting the request.

@siloenix I am closing this request because you have created two new ones, which are correct. Thank you!


Needs to use v3 for the tone API

Currently the app is using version: 'v2-experimental', it should be v3

fixed


Search/filter styles

The dropdown for styles has a lot of entries in it. It would be great if there was a way to search or filter them. Or at least have them sorted alphabetically.

It's alphabetically sorted now, and there's an (All Styles) filter. Regarding search functionality (similar to UE5's menu search functionality), it would be great to just have some simple SComboBox default feature, but that's not there, sadly.


Software is letting me change the only admin account to normal account.

Changed my admin account to employee account. Now I am not able to go back as admin.

fixed with https://github.com/foradian/fluxday/commit/06fc0fe179de3fd472b79b786777e6340e4ed730


[RFC-0004] Allow disabling of insecure HTTP connections for alert providers

Hi,
Please review and suggest changes.
Thanks
Fixes: https://github.com/fluxcd/notification-controller/issues/386

@pjbgf I have done the suggested changes.
Please review

@makkes  I will work on the suggested changes by you and will update the PR
Thanks for the review

@makkes I'm not Ok with breaking Flux Grafana integration by disabling http by default. If you think this is acceptable please create an RFC.

@gunishmatta please hold working on this, a decision to break Flux for all users is not something that can be taken lightly in a PR, an RFC is needed.

@pjbgf @makkes I'm not Ok with breaking Flux Grafana integration by disabling http by default. If you think this is acceptable please create an RFC.

My line of thought is that https://github.com/fluxcd/notification-controller/pull/404#discussion_r945833752 recommends setting the default to true for backwards-compatibility to explicitly not break any existing integration.

@makkes  @stefanprodan  just wanted to check if we can go ahead with making this flag disabled by default?

@makkes @stefanprodan just wanted to check if we can go ahead with making this flag disabled by default?

No, I don't think we can without further discussion. Disabling plain HTTP by default would break Grafana integration as @stefanprodan pointed out. An RFC would be needed.

@makkes @stefanprodan just wanted to check if we can go ahead with making this flag disabled by default?

No, I don't think we can without further discussion. Disabling plain HTTP by default would break Grafana integration as @stefanprodan pointed out. An RFC would be needed.

Sorry, what I mean is releasing with enabling http scheme by default.
Anyways, please let me know whatever would be the update I will be doing it accordingly.
Thanks

@makkes @stefanprodan just wanted to check if we can go ahead with making this flag disabled by default?

No, I don't think we can without further discussion. Disabling plain HTTP by default would break Grafana integration as @stefanprodan pointed out. An RFC would be needed.

Sorry, what I mean is releasing with enabling http scheme by default. Anyways, please let me know whatever would be the update I will be doing it accordingly.

If all comments from my and @pjbgf's reviews are addressed, this should be fine to get merged.

@pjbgf  I have addressed all the changes requested above, Please review and merge if everything is okay

Other than the unnecessary condition this looks good to me now.

Done this optional change too, Please merge if everything is okay

Hi @pjbgf , I have squashed all commits into one and it was an amazing experience contributing to Flux, Also since I am new to Golang, thanks for patiently reviewing all my changes in PR.
I would love to contribute to Flux in future too.
Thanks everyone @makkes  @stefanprodan


encryption for embedded system

I am using open62541 with stm32 UaExpert as cleint , I don't have file system. Is this still possible to test it?

I have not used that platform yet, so I couldn't know.
I would suggest that you first try to run Qt on stm32, see what options you have to import data as QByteArray into a Qt app running on your system. Start with the blog post below:
https://blog.qt.io/blog/2018/05/03/qt-microncontrollers-mcu/
If Qt runs on stm32, and you find a way to import a QByteArray (via QFile filesystem or other mechanism), then it could work.
Hope this is helpful.

Closing due to inactivity.


System.MissingMethodException: Method 'Xamarin.Auth.Authenticator.GetUI' not found.

When I try to display the OAuth2Authenticator in Android, I got this error message:
System.MissingMethodException: Method 'Xamarin.Auth.Authenticator.GetUI' not found.
Here is my code:
[assembly: ExportRenderer(typeof(AuthenticationPage), typeof(AuthenticationPageRenderer))]
namespace my_project.Droid
{
    class AuthenticationPageRenderer : PageRenderer
    {
        private bool _isShown;

        protected override void OnElementChanged(ElementChangedEventArgs<Page> e)
        {
            base.OnElementChanged(e);

            if (_isShown) return;
            _isShown = true;

            var auth = new OAuth2Authenticator(
                Constants.OAuthGoogle.ClientId,
                Constants.OAuthGoogle.ClientSecret,
                Constants.OAuthGoogle.Scope,
                new Uri(Constants.OAuthGoogle.AuthorizeUrl),
                new Uri(Constants.OAuthGoogle.CallbackUrl),
                new Uri(Constants.OAuthGoogle.AccessTokenUrl));
            auth.Completed += OnAuthenticationCompleted;

            // Display the UI
            var activity = Context as Activity;
            activity?.StartActivity(auth.GetUI(activity));
        }

        private async void OnAuthenticationCompleted(object sender, AuthenticatorCompletedEventArgs e)
        {
            if (e.IsAuthenticated)
            {
                await AuthenticationHelper.FetchGoogleEmailAndPicture(e.Account);
            }
        }
    }
}

I have no compilation errors. Does anybody faces the same problem ?

Can you try turning linker off pls?

I'm seeing this as well. I just checked, and I don't have Linker turned on. However, when I turned linker on for SDK assemblies only, it worked.

Yes. linker removed some methods. Xamarin.Auth is not part of SDK.

I'm sorry for not being active on this post but this problem no longer appear on my project and I don't know how. :(

@BenDevelopment
Glad to hear that (you have not problems anymore).
The reason for fix can be multi-fold (update changed something in project file[s], or it was a bug in linker which was fixed in the meantime, build process changed - improved or fixed something).
When you have this error - Disable linking completely. When everything compiles and works and before release you can turn on linking step by step. This will give you insights about linking process.
Can I close this one?

Yes we can close it ! :)

I'll try me too. I've the same error.


TLS Failure

I am at my wits end and I am pretty sure this is not the correct forum but any directional help will be greatly appreciated.
Environment:
I have pgweb running as container in a kubernetes pod. Full deployment  with ingress, services, etc.
Issue:
The deployment works fine with zero issues until I enable TLS in the ingress config. Once tis is turned on assets are not loaded.  The '/' is working so the html is downloaded.  Some assets (the CSS files) are downloaded by the client no problem but non of the JS files are downloaded.  The only difference is the TLS change in ingress:
ingress.yml:
...
spec:
  tls:
  - hosts:
      - fqdn.host.tld
  ingressClassName: public
  rules:
...

For debugging I have removed annotations in the ingress file
So when requesting https://fqdn.domain.tld/ in the browser any js asset fails to download.  The request returns NULL.  No HTTP response, no HTTP response code, just NULL.
Debugging:

Everything works when not using the tis section in the ingress.yml (i.e. http://fqd.domain.tld).  This proves the deployment chain ingress->service->pod is working and the pgweb container is working just fine.
With TLS all asset paths are accessible. I can cURL all URLS (i.e. https://fqdn.domain.tld/, https://fqdn.domain.tld/static/css/.css, https://fqdn.domain.tld/static/js/.js) are all directly accessible.
When requesting https://fqdn.domain.tld/ only the requests for / or static/css/*.css show up in the ingress log. It seems like the javascript requests are not in log.
Assuming this is some browser issue default is Safari, I ran in Firefox and Chrome.  Same issue in each browser. FAILED
Assuming this may be browser security setting I turned disabled Developer Settings...>Disable cross-origin restrictions FAILED.
I have attempted to adjust the

Thanks for the report.
I've run pgweb on k8s with tls before, so it's definitely doable. Do you have any scripts/configs to share so i can try to repro the issue?

OMG! That would be great.
The code for the container is:  https://github.com/gautada/pgweb-container
The image repo is: https://hub.docker.com/repository/docker/gautada/pgweb/general
The deployment.yml is
apiVersion: apps/v1
kind: Deployment
metadata:
  name: pgweb
  namespace: data
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: pgweb
  strategy:
    type: Recreate
  template:
    metadata:
      creationTimestamp: null
      labels:
        k8s-app: pgweb
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: node.gautier.org/layer
                operator: In
                values:
                - troposphere
      containers:
      - name: pgweb
        image: gautada/pgweb:test
        imagePullPolicy: Always
        env:
        - name: PGWEB_DATABASE_URL
          value: "postgres://pgweb@psql.gautier.org:5432/postgres?connect_timeout=30&sslmode=disable"
        # - name: PGWEB_CORS_ORIGIN
        #   value: "http://pgweb.data.svc.cluster.local:8080/"
        livenessProbe:
          exec:
            command:
            - /usr/bin/container-liveness
          failureThreshold: 10
          initialDelaySeconds: 5
          periodSeconds: 5
        readinessProbe:
          exec:
            command:
            - /usr/bin/container-readiness
          failureThreshold: 10
          initialDelaySeconds: 5
          periodSeconds: 5
        startupProbe:
          exec:
            command:
            - /usr/bin/container-startup
          failureThreshold: 10
          periodSeconds: 5
        ports:
        - containerPort: 5432
          name: psql
          protocol: TCP
        securityContext:
          privileged: false
      restartPolicy: Always
      schedulerName: default-scheduler

The working ingress.yml (with the TLS commented out):

All the annotations are context that works for other containers, i.e. auth-tls... or attempts to correct the above problem. Note all have been commented out as it is the spec.tls...  section that breaks.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    # kubernetes.io/ingress.class: "nginx"
    # nginx.ingress.kubernetes.io/auth-tls-verify-client: "on"
    # nginx.ingress.kubernetes.io/auth-tls-secret: "data/ca-certs"
    # nginx.ingress.kubernetes.io/auth-tls-verify-depth: "1"
    # nginx.ingress.kubernetes.io/auth-tls-error-page: "https://youtu.be/t3otBjVZzT0"
    # nginx.ingress.kubernetes.io/auth-tls-pass-certificate-to-upstream: "false"

    # nginx.ingress.kubernetes.io/enable-cors: "false"
    # nginx.ingress.kubernetes.io/cors-allow-origin: "https://psql.gautier.org/"
    # nginx.ingress.kubernetes.io/cors-allow-credentials: "true"

    # nginx.ingress.kubernetes.io/ssl-redirect: "true"
    # nginx.ingress.kubernetes.io/hsts: "true"
    # nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    # nginx.ingress.kubernetes.io/preserve-trailing-slash: "true"

    # nginx.ingress.kubernetes.io/http2-push-preload: "true"

    # nginx.ingress.kubernetes.io/send_timeout: "3m"
    # nginx.ingress.kubernetes.io/proxy-connect-timeout: "3m"
    # nginx.ingress.kubernetes.io/proxy-read-timeout: "3m"
    # nginx.ingress.kubernetes.io/proxy-send-timeout: "3m"

    # nginx.ingress.kubernetes.io/add-base-url: "true"
    # nginx.ingress.kubernetes.io/rewrite-target: /
    # nginx.ingress.kubernetes.io/rewrite-target: /$1
  namespace: data
  name: pgweb
spec:
#  tls:
#   - hosts:
#       - psql.gautier.org
  ingressClassName: public
  rules:
  - host: psql.gautier.org
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: pgweb
            port:
              number: 8080

Cool, i'll try to get to it this weekend.

Btw you shared the deployment url in the example, and it seems like the API is up and operational, hopefully you don't have anything of importance running in your cluster.
Is this the error you're seeing in chrome? net::ERR_HTTP2_SERVER_REFUSED_STREAM ?

Yeah nothing of importance as I just pointed the production url to a test k8s cluster. I setup up the certauth just to be sure.
Yes I am getting net::ERR_HTTP2_SERVER_REFUSED_STREAM in chrome.  Safari just failed without an error code.  Referencing nginx user guide provided the config setting use-http2: "false" and this got the website working.  I will continue to work on these configs to re-enable http2 support.  But it works for now and thanks as this is clearly not a pgweb issue.


Add updated tests data and remove DebugListenerBlock

This PR removes the DebugListenerBlock and adds updated test data to eliminate asserts on donetcore 2.0 EventPipe generated data so that asserts will not fire on load
Related: #387

@nategraf,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@vancem The test for v1 EventPipe objects currently fails because it uses data without the write size fix. Is the best solution to cobble together a v1 object codebase with the size fix cherry-picked in and submit that as the new test data?

The test for v1 EventPipe objects currently fails because it uses data without the write size fix. Is the best solution to cobble together a v1 object codebase with the size fix cherry-picked in and submit that as the new test data?

No.   For better or worse, the V1 format has effectively shipped in .NET Core, and we can't change it.   The current test file accurately represents what a 2.0 .NET Core runtime will produce it is correct the way it is.
What this means is that we can't eliminate the DebugListenerBlock completely.  But we should only have it when running V1 format tests.  We probably should create a separate test for the V1 format (Don't lump it in with the others).  and when we don't care about the V1 format anymore we can eliminate it (and DebugListenerBlock), as a test case.

Codecov Report

Merging #389 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #389      +/-   ##
==========================================
- Coverage   17.43%   17.41%   -0.02%
==========================================
  Files         211      211
  Lines      122437   122434       -3
  Branches    11773    11773
==========================================
- Hits        21341    21322      -19
- Misses     100248   100265      +17
+ Partials      848      847       -1

Flag
Coverage Δ

#2017
17.41% <100%> (-0.02%)
:arrow_down:

#Debug
17.41% <100%> (-0.02%)
:arrow_down:

#Release
?

Impacted Files
Coverage Δ

...rc/TraceEvent/TraceEvent.Tests/EventPipeParsing.cs
65% <100%> (-22.31%)
:arrow_down:

src/TraceEvent/EventPipe/EventMetadata.cs
69.23% <0%> (-7.7%)
:arrow_down:

Continue to review full report at Codecov.

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

The fix to the payload sizes doesn’t effect the format of the data (or the ability of PerfView to read the files); it prevents extra empty/garbage bits from being written which TraceEvent correctly ignored, except in the DebugValidate function. The v1 test data with the fix (which was easier to generate than I originally thought) still verifies the ability of PerfView to read data from Core CLR that does not contain the fix, but it will not trigger asserts. In this sense I think we should use the new data because it still follows the v1 format, and will not degrade the value of the test, but it will allow us to fully eliminate the DebugListenerBlock (instead of creating a special case)

LGTM


New point release that includes BigDecimal semigroup

In particular it would be valuable to have a point release that includes https://github.com/twitter/algebird/commit/757712c3eb872b478153c8c1de934d00dcf87f28
Many thanks!

@piyushnarang would you have any time for this when (if) you do bijection?

@piyushnarang I think we are almost ready if we can merge #643
It would help us to be able to publish. Do you have time or can you give me the 👍  to publish?

I think develop is in shape to be the new point release.

@johnynek I'm in favor of a release, I'm guessing it's going to be 0.13.1? I'm probably not going to have time to get to it, but if you've got the sonatype perms etc feel free to do so.
@pankajroark wdyt?

I think actually it can be 0.12.x since mima should be running.
I'll re-run.

👍

oh yeah, that is 0.13.1... sorry, you are right @piyushnarang

just re-ran mima. Looks clean with 0.13.0. Will republish.

Ok great, thanks!

https://github.com/twitter/algebird/releases/tag/v0.13.1


Bug: Error after remove csv

If you open a CSV and set a conversion with appwrite and then remove the csv you'll get and error like this:

Linked to https://github.com/tannermeade/data-migrator/issues/3


Size verification fails on ~4 GB (< uint32) .tar.gz file

Hey!
First time finally using your library. Thanks for your work first of all. :)
While trying to see how it performs on some of my larger .tar.gz archives, I noticed that for one of the larger ones extraction via extractAll fails with a size verification error. The issue seems to be that the archive is larger than int32.high, due to the size check here:
https://github.com/guzba/zippy/blob/master/src/zippy/gzip.nim#L76
Given that isize is already a uint32 why do we mod the length of dst by (1 shl 31) and not allow the full uint32 range?
My archive has 476,932 files with a total size of 3,497,146,858 bytes (according to du . -b in the extracted directory).
I also wondered what would happen if we fully exceed the size of uint32, but with a quick try I wasn't able to build a .tar.gz archive that actually enters the uncompressGzip proc. Instead it seems to go here https://github.com/guzba/zippy/blob/master/src/zippy/tarballs.nim#L51 instead (I didn't actually check that, I only noticed that uncompressedGzip wasn't being run for my ~8 GB deflated archive).
Code to reproduce is pretty much just:
import zippy/tarballs
const tmp = "/tmp/foobar"
extractAll("/path/to/file.tar.gz", tmp)

I didn't open a PR, because I assume the line mentioned above is the way it is for a good reason. If it helps I can also send you the archive via google drive or w/e.
Thanks!

Looking quick it just seems like a bug to fix, should probably be (1 shl 32). https://www.rfc-editor.org/rfc/rfc1952.html is the boss and it says ISIZE This contains the size of the original (uncompressed) input data modulo 2^32.

Got it!

Thanks for reporting the issue and making a PR!


[feature] Project templates

In larger organizations, it is often useful to have some kind of tmeplate for starting new python projects to encourage (organizational) best practices. A popular solution for python projects would be the Cookiecutter project.
I was even thinking of some kind of mechanism, where something like django or other larger packages could define a template and rye would be able to list that (and others) as a possible project starter if django (or whatever) is already installed. Sort of an entrypoint-system or plugin system for project templates, that rye would provide and other packages could hook into, registering their templates with rye. Just an idea. You could also just wrap Cookiecutter, which takes git repository URLs for external templates, or leave it out completely. Packaging just has a lot of biolerplate, that a unified tool could take care of.
As for the interface, Hatchet has
hatchet new --ci --tests --docs

if I remember correctly. Rye could have a similar
rye init --app/--library --ci --tests --docs --django --vcs-versions --jupyter ...

Not saying I want rye to have these, just giving options (literally :grin: ).

I'd love for rye to have opinions. If rye has opinions here less is probably better. This does sound like plugin territory. I see this like rye supporting any other default. If there is a default it probably should be pretty minimal. I'm a fan of the src layout.
Here's an example project of mine:
xlcsv on  master is 📦 v0.1.0 via 🐍 v3.11.0
❯ tree .
.
├── LICENSE
├── Makefile
├── README.md
├── pyproject.toml
├── requirements-dev.lock
├── requirements.lock
├── src
│   └── xlcsv
│       ├── __init__.py
│       ├── error.py
│       ├── io.py
│       └── utils.py
└── tests
    ├── __init__.py
    ├── test_convert.py
    └── test_version.py

I think rye should not support templates in the core of it, but I'm a strong believer in promoting good defaults. I feel like rye init shoudl at least also create an src/project_name/__init__.py file.

Yeah, this more than a brainstorm than a feature request. Whole-hearted :+1:  for src layout.  If rye init created src/project_name/__init__.py that is already dangerously close to a template.  Maybe provinding a rye init --template <name> or something and then delegating that to a configurable external command, is an option?

What I really like about the cargo experience is that on an empty folder it puts you on the path of success. It creates src/lib.rs which is exactly what you want in 99% of cases. I think the same should apply to rye. You should be using src/package-name, so why not create it?

Yeah no, I absolutely meant that that should be the default behavior for rye init without further arguments. The --template would be a very optional, user/organization/project configurable type of thing in my mind.

I think tests (and coverage) config should be by default added when do rye init, probably also linting.
cargo new don't add tests config only because it has built-in support.

I initially also thought it would be nice, but then I realized running cookiecutter gh:my-gh-org/my-cookiecutter-template-repo is literally the same amount of effort as running rye init --template gh:my-gh-org/my-cookiecutter-template-repo😅


Crash when recycling default stairs

Steps to reproduce:

Open a world without moreblocks enabled
Craft stairs
Enable moreblocks
Insert input material for previously crafted stairs
Put previously crafted (default) stairs into recycle slot
Crash on line circular_saw.lua:261 bc cost is nil

What I believe is happening:
Due to alias definition, contains_item returns true for default stairs, but get_cost does not take aliases into consideration and returns nil.
This happened with acacia stairs, but is likely a problem with all aliased nodes.
Adding
if not cost then
  return 0
end

before line 261 (if (incost + cost) > maxcost then in circular_saw.allow_metadata_inventory_put) prevents crash from occurring, but a better approach would be to keep track of aliased nodes in aliases.lua try mapping old node into a new one to consistently calculate cost.

Adding
if not cost then
    return 0
end

before line 261 (`if (incost + cost) > maxcost then` in `circular_saw.allow_metadata_inventory_put`) prevents crash from occurring, but a better approach would be to keep track of aliased nodes in `aliases.lua` try mapping old node into a new one to consistently calculate cost.

Maybe we should return an extremely high cost in this case? We should avoid introducing a duplication bug while fixing this 🙂

Maybe we should return an extremely high cost in this case? We should avoid introducing a duplication bug while fixing this slightly_smiling_face

Returning 0 prevents the item from being inserted.
I suggested using aliases instead as it would result in expected behaviour instead of preventing players from recycling default stairs which might be confusing if they don't know what's going on.


Fixed peer dependencies in package.json for npm@2

^ in react version caused npm installation errors in npm@2 https://travis-ci.org/facebook/react-native/builds/132153309
Test Plan:

see Travis logs

Does it have to be the 'alpha' ? I had the issue when running samples and created the PL to use the<EMAIL_ADDRESS>https://github.com/facebook/react-native/pull/7692

closing in gavour of #7692

By analyzing the blame information on this pull request, we identified @cpojer and @davidaurelio to be potential reviewers.


Modification of ban -> Reason

In gitlab by @A-Lawrence on Jan 11, 2016, 21:13
Allow a reason for the ban modification to be added.

In gitlab by @A-Lawrence on Jan 11, 2016, 22:58
mentioned in commit 01f8249bbcb71fc465fd62ee85422ea5cc190799

In gitlab by @A-Lawrence on Jan 11, 2016, 22:58
Resolved in commit 01f8249bbcb71fc465fd62ee85422ea5cc190799.


[Impeller] Run the iOS module tests.

@jmagman was saying this probably wouldn't be too hard.
Run the framework iOS Module tests using impeller in addition to Skia. This should give us more coverage on simulators.

This is redundant now as we are not defaulting to Impeller.


Update enable-virtualization-based-protection-of-code-integrity.md

Why

Closes #[Issue Number]

Changes

Learn Build status updates of commit 6b8a9ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/device-guard/enable-virtualization-based-protection-of-code-integrity.md
:white_check_mark:Succeeded

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


local_path is shown twice on file hover

Describe the bug
Path to file is listed double when hovering the filename
'local_path' => env('RAY_LOCAL_PATH', '/var/www/intranet'),

Versions
Ray version: 1.7.0
You can use composer show to get the version numbers of:

spatie/ray package version: 1.14.0
spatie/laravel-ray package version: 1.8.0

PHP version:
Laravel version : 8.23.1
To Reproduce
Steps to reproduce the behavior:

Set a local_path in the config file
Send though a ray() message
Hover the file

Expected behavior
I wouldnt expect it to be listed twice :)
Screenshots

Desktop (please complete the following information):

OS: Ubuntu
Version  20.04
Running on Docker

Seems to be happen when missing a trailing / in local_path and remote_path
    'remote_path' => env('RAY_REMOTE_PATH', '/app/'),
    'local_path' => env('RAY_LOCAL_PATH', '/var/www/intranet/'),

Seems to be happen when missing a trailing / in local_path and remote_path
    'remote_path' => env('RAY_REMOTE_PATH', '/app/'),
    'local_path' => env('RAY_LOCAL_PATH', '/var/www/intranet/'),

I'll investigate this soon. If you already know a good fix, please send a PR!

I'll investigate this soon. If you already know a good fix, please send a PR!

The issue comes from the fact that str_replace() will replace all occurences found
The string will look like this /app/app/Http/Controllers/HomeController.php. So when replacing /app, it will be replaced twice.
I will look into helping out with a fix when I can find the time :)

The issue comes from the fact that str_replace() will replace all occurences found
The string will look like this /app/app/Http/Controllers/HomeController.php. So when replacing /app, it will be replaced twice.
I will look into helping out with a fix when I can find the time :)


What's the size of extracted frames and optical flow images?

The authors suggest using the tools provided in the TSN repo to extract frames and optical flow images. I wonder should I resize the images the same way as TSN repo? What's the image size the authors used?
One dataset used in TSN repo is UCF101. The original videos' size is 320*256. The command in TSN repo resize images to 340*256 as follows,
python tools/build_of.py ${SRC_FOLDER} ${OUT_FOLDER} --num_worker ${NUM_WORKER} --new_width 340 --new_height 256 2>local/errors.log

And in the *_train_val.prototxt the crop_size is 224.
The size of THUMOS14 videos is 320*180, in resnet/vgg/BNInception models input_size = 224, in InceptionV3/inception models input_size = 299.
I got worse results when I used reference models to evaluate my extracted images, which haven't been resized (320*180). (The image number is the same as the image number of denseflow extracted images)
action-detection$ python3 ssn_test.py thumos14 RGB none score_thumos14_rgb_reference.npz --use_reference
action-detection$ python3 eval_detection_results.py thumos14 score_thumos14_rgb_reference.npz

rgb reference model
+Detection Performance on thumos14------+--------+--------+--------+--------+--------+--------+---------+
| IoU thresh | 0.10   | 0.20   | 0.30   | 0.40   | 0.50   | 0.60   | 0.70   | 0.80   | 0.90   | Average |
+------------+--------+--------+--------+--------+--------+--------+--------+--------+--------+---------+
| mean AP    | 0.4375 | 0.3839 | 0.3266 | 0.2430 | 0.1639 | 0.1051 | 0.0588 | 0.0244 | 0.0059 | 0.1943  |
+------------+--------+--------+--------+--------+--------+--------+--------+--------+--------+---------+

action-detection$ python3 ssn_test.py thumos14 Flow none score_thumos14_flow_reference.npz --use_reference
action-detection$ python3 eval_detection_results.py thumos14 score_thumos14_flow_reference.npz

+Detection Performance on thumos14------+--------+--------+--------+--------+--------+--------+---------+
| IoU thresh | 0.10   | 0.20   | 0.30   | 0.40   | 0.50   | 0.60   | 0.70   | 0.80   | 0.90   | Average |
+------------+--------+--------+--------+--------+--------+--------+--------+--------+--------+---------+
| mean AP    | 0.4166 | 0.3769 | 0.3183 | 0.2538 | 0.1907 | 0.1208 | 0.0698 | 0.0250 | 0.0045 | 0.1974  |
+------------+--------+--------+--------+--------+--------+--------+--------+--------+--------+---------+

You need to resize images to the size required before crop

Resize to 340*256?

@HYPJUDY  Yes for BN-Inception

@HYPJUDY I just resize all images to 340*256 by using --new_width 340 --new_height 256,and both the RGB and Flow evaluation result looks as good as the SSN paper says,
in your case，did you use opencv2？ because the author‘s denseflow extraction program works fine only under opencv2 , not opencv3.
BTW  ,my environment for  extracted frames and optical flow  is python2.7+opencv2


Updated file paths to ensure consistency across documentation

The previous paths were incorrect and have been fixed to reflect the correct file locations in the repository. This update improves the navigation experience for users .

@AdarshKumarShorthillsAI , There some conflicts in your PR, Please fix the same.


The need to or the need for?

I picked "for", feel free to choose "to"!

https://forum.wordreference.com/threads/point-to-the-need-to-or-for.2660720/
https://english.stackexchange.com/questions/6623/need-of-vs-need-for

Thanks!


WPF Ext. Toolkit support

I'm thinking about support for more Editors in the Datagrid!
(DateTime, TimeSpan, Brush, UpDowns (Decimal,Integer,..))
by including Ext.Wpf Toolkit.
I've a fork of it at github: https://github.com/dotnetprojects/WpfExToolkit
It's okay when i create a Extension DLL with a new DataGridControlFactory wich uses additional Controls? Will it be possible to include this DLL to the main Project?

Great!
I think this should be in a separate project, so we can use PropertyTools.Wpf without adding additional dependencies. I suggest to name it PropertyTools.Wpf.Contrib or PropertyTools.WpfExToolkit

Also the PropertyGrid control could use these editors!

Ok, I look to implement it during this week!

Solved #75


libminc: 2018-01-17 -> 2.4.03 and disable broken checkPhase on OSX

Motivation for this change
checkPhase was broken on Darwin so the package wasn't building on OSX.  Also bumped from a git tag to a proper release.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[NA] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Thanks!


Wrong import in documentation

The scss theming page has this string as the main .scss file import:
@import 'vue3-date-time-picker/src/Vue3DatePicker/styles/main.scss';

when in reality it should be
@import 'vue3-date-time-picker/src/Vue3DatePicker/style/main.scss';

Tnx for reporting, will be corrected.


extend initialDelaySeconds of livenessProbe

To stabilize e2e test, extend initialDelaySeconds of livenessProbe. (it is workaround)
Signed-off-by: UMEZAWA Takeshi<EMAIL_ADDRESS>

Fix to stabilize CI. #105


How to integrate/build on Binder

Ideas

Maybe we can call a docker exec via a new API endpoint in BinderHub? The exec would execute a binary (to be implemented) that reads a codecheck.yml (finds the files to check), does the check, and then saves the result (with a "signature") back to the codecheck.yml (adding to potentially existing checks). We would manipulate the user container/pod from the outside... and since we would not tell the user about the pod, they also cannot manipulate it. But it would be exactly the same environment they have (i.e. a JupyterHub session/container) that they get when they start the binder for interactive use. We would run the analysis actually in a pod, and not hacked into the r2d build process. Since BinderHub started the JupyterHub, we (should) know the pod and container, so we can also save the container (hopefully) to a file.
[ ] papermill allows to execute notebooks via a CLI (and analogously possible with rmarkdown in R)
[ ] We need a small example (e.g. a Python script that generates random numbers based on a seed and a preliminary "check").
Nothing BinderHub, but enhance JupyterHub with Jupyter extension, see ideas/discussion at https://github.com/jupyterhub/binderhub/issues/579 and https://github.com/jupyterhub/binderhub/issues/674

Questions

How does a user "explore" the result of a check?
Do we need JupyterHub?

https://github.com/pangeo-data/pangeo-stacks/pull/10 adds a verify script which now is called as part of build.py, but that's more to verify the image works OK, not to actually run the analysis... BUT docker run -i -t ${IMAGE_NAME} "binder/verify" seems like something that we also want to run. JupyterHub API: https://jupyterhub.readthedocs.io/en/stable/api/

Can we assume a check happens automatically after a binder is started, or is it triggered (potentially allowing manipulation of content) manually? > Should start right after successful build and launch of the pod/container (?) by JupyterHub ?! checks are "manual", CodecheckersHub only supports that process.
Do we need a special UI?

Instead of getting the notebook, you just get a UI that runs the code configured in codecheck.yml within the container, then triggers the check, and puts the "Docker image + check result + badge" somewhere safe.

Can run commands in a pod's container with kubectl exec

nbtoolbelt can help running notebooks from CLI: https://gitlab.tue.nl/jupyter-projects/nbtoolbelt/, or nbless, or nbscript

Might JupyterHub be the better component to build CODECHECK on?
Can we run a CodecheckersHub instead of JupyterHub, that just starts a pod, runs the image, executes the analysis, executes codecheck (via kubectl exec) - Would BinderHub maintainers welcome this?

CODECHECKHub would be like a read-only JupyterHub? Or just a minimal UI that say "running" and then "check result"?
We likely need a BinderHub-level component that can save the container to a file after the check.

Does BinderHub keep a list of redirects it makes for users to JupyterHub (so it could execute stuff in user containers) ?

No.

How can we export the image to a file and make it available for download? Would that work via a new BinderHub API endpoint?
Is it feasible to run both binder and a binder-fork in the same k8s cluster, using the same Jupyter Hub?

codecheck.yml sketch
codecheck_version: 1
input:
  file: "main.ipynb"
  format: "ipython" # default, could also be 'rmarkdown' for Rmd documents, 'python3' for a python script, could be derived from file name
  command: "..." # for rare cases where user needs to define this, but normally should be auto-generated from format
output: # the files that the check uses, if empty, the check generates hashes for all?
  - "model_outputs.csv"
  - "fig1.png"
checks:
  - check_time: "2019-01-01 13:00:00"
    check_runner: "mybinder.org" # who executed the check
    check_signature: "..." # something crpytographic

https://github.com/codecheckers/binderhub/labels/breakthrough


Can the 'context_launch_lock' in the '_create_page' function be safely removed?

  async def _create_page(self, request: Request, spider: Spider) -> Page:
        """Create a new page in a context, also creating a new context if necessary."""
        context_name = request.meta.setdefault("playwright_context", DEFAULT_CONTEXT_NAME)
        # this block needs to be locked because several attempts to launch a context
        # with the same name could happen at the same time from different requests
        local_time = time()
        print("spider_start", request.url, context_name)
        # async with self.context_launch_lock:
        ctx_wrapper = self.context_wrappers.get(context_name)
        if ctx_wrapper is None:
            ctx_wrapper = await self._create_browser_context(
                name=context_name,
                context_kwargs=request.meta.get("playwright_context_kwargs"),
                spider=spider,
            )

Is there any potential risk if I remove the lock while using UUID for each context creation and only launching one page?
(edited for syntax highlighting)

Please elaborate on the motivation for this.


Roll engine 27fa60793bcb..9de48de0663e (2 commits)

git@github.com:flutter/engine.git/compare/27fa60793bcb...9de48de0663e
git log 27fa60793bcb..9de48de0663e --first-parent --oneline
2019-11-26<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from kzFUw... to xyyOR... (#14021)
2019-11-26<EMAIL_ADDRESS>Add a separate target for Dart coverter on FML types. (#14011)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5772203672469504

Commit queue failed; closing this roll.


Productionize vectorization prototype

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwchkdQkRUw6hZ3z/rec6XtFIj6grDDHAS?blocks=hide
PM: @awoods187

AFAICT, the documentation impact of vectorization will be minimal.
Quote from the Airtable entry:

This is not a customer facing feature--queries will be automatically faster to users.

Vectorization looks to be more of a performance improvement thing that we can really only document conceptually (which could still be very important!).
@awoods187 Am I missing something? Thoughts?

we will need to document the following:

how to turn off the default setting and return to DistSQL only
how to turn on the full setting for testing the further out prototype
how to return to the default setting with vec on for some queries

We should also begin to explain how vectorized execution works conceptually and mechanically similarly to other non-user facing architectural changes. We should document this, in the same manner, we would parallel commits from core.
Does that make sense?

Awesome. Thanks. Just added these as tasks in the issue. overview.


how can i user this in   and  in the same layout,@BindView cant bind the same widget but they are different Object;

how can i user this in   and  in the same layout,@BindView cant bind the same widget but they are different Object;

This is currently not supported but tracked by #394.


Update to Tailwind v1.4 which bakes-in Purge CSS support

Thank you for https://statickit.com/guides/next-js-tailwind
I followed it many times. Tried updating but Purge CSS deletes my CSS. Mind updating the guide?

Found the solution 🎉
Some changes required in the guide:
2. Install dependencies
Don't need to add @fullhuman/postcss-purgecss
npm install tailwindcss autoprefixer --save-dev

3. Configure the build pipeline
It becomes
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {}
  }
}

6. Generate tailwind.config.js & add purge property
module.exports = {
  purge: {
    content: ['./components/**/*.js', './pages/**/*.js'],
    options: {
      whitelist: ['text-pink-500', 'text-yellow-500'], // anything that needs to be whitelisted
    },
  },
  theme: {
    extend: {},
  },
  variants: {},
  plugins: [],
}

Reference: https://github.com/tailwindcss/tailwindcss/pull/1639

Thanks @deadcoder0904, worked like a charm! At the time of writing I had no need for whitelisting so the following minimal config was enough:
tailwind.config.js
module.exports = {
  purge: {
    content: ['./components/**/*.js', './pages/**/*.js'],
  }
};


ng serve needs to be restarted after syntax error

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[x ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 do not know
Description

saving a template with a syntax error will result in an unrecoverable error
after correcting the syntax error a simple reload of the page is not enough and the server needs to be restarted
🔬 Minimal Reproduction

delete one curly bracket inside one template and save the file {someVar}}
put curly bracket back and save.
it seams to happen only on templates that use pipes *ngFor="let foo of {'a':1,'b':2'} | keyvalue"
🔥 Exception or Error

core.js:5973 ERROR Error: NG0302: The pipe 'keyvalue' could not be found!
    at getPipeDef$1 (core.js:25451)
    at Module.ɵɵpipe (core.js:25408)
    at SysmapExplorerComponent_Template (sysmap-explorer.component.html:16)
    at executeTemplate (core.js:9269)
    at renderView (core.js:9076)
    at renderComponent (core.js:10338)
    at renderChildComponents (core.js:8941)
    at renderView (core.js:9101)
    at TemplateRef.createEmbeddedView (core.js:22678)
    at ViewContainerRef.createEmbeddedView (core.js:22809)

🌍 Your Environment

Angular CLI: 11.0.2
Node: 14.15.0
OS: win32 x64

Angular: 11.0.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.2
@angular-devkit/build-angular   0.1100.2
@angular-devkit/core            11.0.2
@angular-devkit/schematics      11.0.2
@angular/cdk                    11.0.1
@angular/fire                   6.1.3
@angular/flex-layout            11.0.0-beta.33
@angular/material               11.0.1
@angular/service-worker         11.0.3
@schematics/angular             11.0.2
@schematics/update              0.1100.2
rxjs                            6.6.3
typescript                      4.0.5

Anything else relevant?

Thanks for reporting this issue. Luckily, it has already been fixed in one of the recent releases. Please update to the most recent version to resolve the problem. See https://github.com/angular/angular/issues/39147#issuecomment-739094822
If the problem persists in your application after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use ng new repro-app to create a new project where you reproduce the problem.

Thanks for reporting this issue. Luckily, it has already been fixed in one of the recent releases. Please update to the most recent version to resolve the problem. See https://github.com/angular/angular/issues/39147#issuecomment-739094822
If the problem persists in your application after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use ng new repro-app to create a new project where you reproduce the problem.


the two way of nested values' mappedErrors are different?

req.assert(['user', 'email'], 'not valid email').optional().isEmail();
req.assert('user.mobile', 'not valid mobile').optional().isMobilePhone('zh-CN');
In the previous express-validator version, if i use the two req.assert above to check the nested params, I got the same mappedErrors as mappedErrors['user.email'] and mappedErrors['user.mobile'];
But now I get mappedErrors['user,email'] and mappedErrors['user.mobile'], notice the separator is a comma in the 'user,email', not a dot, is it on purpose?
And when I check three layers nested values like below, it does not work:
req.assert('user.personalInfo.idNo', 'not valid ID No.').optional().len(6, 20).isAlphanumeric();
And below is working, but again, I got a mappedError like mappedError['user,personalInfo.idNo'], notice the first separator is a comma, not a dot:
req.assert(['user','personalInfo.idNo'], 'not valid ID No.').optional().len(6, 20).isAlphanumeric();
Is it true that only two values nested is OK with the syntax of 'dot-notation'?

Thanks for the reporting this. What was the last version you used that worked?

@Jakeii or @chrissinclair: would either of you be able to look into this?

After doing some investigation, this errors seems to have occurred because of the giant code refactor a couple months ago. Essentially, in v2.11.0 (before the refactor), if you ran the test nestedInputTest.js, the errors would output as:
[ { param: 'user.fields.email', msg: 'not empty', value: '' },
  { param: 'user.fields.email', msg: 'not empty', value: '' },
  { param: 'user.fields.email', msg: 'valid email required', value: '' } ]

However, in v2.12.0 (after the refactor), they output as:
[ { param: [ 'user', 'fields', 'email' ],
    msg: 'not empty',
    value: '' },
  { param: 'user.fields.email', msg: 'not empty', value: '' },
  { param: [ 'user', 'fields', 'email' ],
    msg: 'valid email required',
    value: '' } ]

Notice how it doesn't convert [ 'user', 'fields', 'email' ] to 'user.fields.email' in the param field.
So we need to:

Figure out what was missed in that refactor between the two releases.
Enhance the tests for nestedInputTest.js and nestedInputSanitizeTest.js to check the output of the errors to make sure the param string is in the correct format.

Just to be clear on this - this is a regression issue and the correct behaviour is to output the param in the form 'user.fields.email'?
It's a bank holiday here in the UK so I might be able to get some time and have a look.

Yes, this is a regression issue. Actually, I may be reaching a point where I almost have a PR ready, but if you have time would definitely appreciate you looking over the PR. I'll tag you in it when it's ready.

Pull request is open for this now and ready for review.

This should be fixed in v2.17.1. Please reopen if this is still occurring.

Thanks guys, you awesome!


Add load balancer service type model actions

Purpose or Intent
The base classes for LoadBalancer provision, reconfigure and retirement actions. The actuall actions will be defined in the providers.
Steps for Testing/QA
None

@blomquisg btw. this can be merged regardless of automate implementation, these actions will stay in any case

@blomquisg This did not make it into Euwe branch.  Please label euwe/yes or euwe/no, as appropriate.


specify a timeout option to send_wait

At the moment send_wait waits until publish_confirmation is received from the server.
Better to put a timeout that will allow the function to continue if the timeout expires even if the message is not yet confirmed

This task also to revisit send_wait (we did most of the tests for send and send_batch at the moment)


raw-loader or equivalent support

https://github.com/angular/angular-cli/issues/21582
Looking for a decent way to produce documentation.
Normally I use raw-loader to pull in the html/ts file of a component and parse for comment markers to dynamically produce example docs along side the live demo, much the same way angular.io works with the custom <code-example> component.
As noted in the linked thread https://github.com/angular/angular-cli/pull/21305 seems to indicate webpack asset/source module is supported but seemingly no way to enable it for raw files.
Is there any workaround for importing raw text files at build time? I don't want to build a pre-build inlining process or copy all source-code to the assets folder to XHR them.

You can enable this by using a custom builder like https://github.com/manfredsteyer/ngx-build-plus or https://github.com/just-jeb/angular-builders and extend the default configuration.


serde 1.0.186 always depends on serde_derive, even if the derive feature is not used

When updating serde from v1.0.185 to v1.0.186 in my project, cargo also pulls in serde_derive as new dependency, even though the derive feature is not in use. (See https://github.com/striezel/corona/pull/155.) This should not happen.
I suppose the cause for this is https://github.com/serde-rs/serde/pull/2588.

Is it actually built? I think it only shows up in Cargo.lock and doesn't actually get built, right?
Even so, we could move the lockstep logic to serde_derive's Cargo.toml

Is it actually built? I think it only shows up in Cargo.lock and doesn't actually get built, right?

I don't know. I haven't merged and built those changes yet.

OK, here are some files for a minimal example:
Cargo.lock
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3

[[package]]
name = "serde"
version = "1.0.185"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be9b6f69f1dfd54c3b568ffa45c310d6973a5e5148fd40cf515acaf38cf5bc31"

[[package]]
name = "serde_example"
version = "0.1.0"
dependencies = [
 "serde",
]

Cargo.toml
[package]
name = "serde_example"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
serde = "1.0.185"

src/main.rs
fn main() {
    println!("Hello, serde!");
}

When I run a cargo update on this small example, the output is:
    Updating crates.io index
      Adding proc-macro2 v1.0.66
      Adding quote v1.0.33
    Updating serde v1.0.185 -> v1.0.186
      Adding serde_derive v1.0.186
      Adding syn v2.0.29
      Adding unicode-ident v1.0.11

... and the Cargo.lock grows from the previous 16 lines to 65 lines:
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3

[[package]]
name = "proc-macro2"
version = "1.0.66"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "18fb31db3f9bddb2ea821cde30a9f70117e3f119938b5ee630b7403aa6e2ead9"
dependencies = [
 "unicode-ident",
]

[[package]]
name = "quote"
version = "1.0.33"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5267fca4496028628a95160fc423a33e8b2e6af8a5302579e322e4b520293cae"
dependencies = [
 "proc-macro2",
]

[[package]]
name = "serde"
version = "1.0.186"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f5db24220c009de9bd45e69fb2938f4b6d2df856aa9304ce377b3180f83b7c1"
dependencies = [
 "serde_derive",
]

[[package]]
name = "serde_derive"
version = "1.0.186"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5ad697f7e0b65af4983a4ce8f56ed5b357e8d3c36651bf6a7e13639c17b8e670"
dependencies = [
 "proc-macro2",
 "quote",
 "syn",
]

[[package]]
name = "serde_example"
version = "0.1.0"
dependencies = [
 "serde",
]

[[package]]
name = "syn"
version = "2.0.29"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c324c494eba9d92503e6f1ef2e6df781e78f6a7705a0202d9801b198807d518a"
dependencies = [
 "proc-macro2",
 "quote",
 "unicode-ident",
]

[[package]]
name = "unicode-ident"
version = "1.0.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "301abaae475aa91687eb82514b328ab47a211a533026cb25fc3e519b86adfc3c"

All of those newly added packages are direct or indirect dependencies of serde_derive.
However, you seem to be right, @oli-obk. None of those additional packages are built when running cargo build. Only serde and the example program are built. Looks like those dependencies only get added to the lockfile and aren't actually built. I guess that's acceptable then, despite being a little bit annoying.

we could move the lockstep logic to serde_derive's Cargo.toml

I would have loved to do this. As far as I know, it is not possible, because the dependency in that direction would be circular. Serde_derive depends on serde (on "some" platforms) and serde depends on serde_derive (in some feature combinations) which is enough for Cargo to reject, despite "some" platforms not actually being any platforms.
error: cyclic package dependency: package `serde v1.0.186` depends on itself. Cycle:
package `serde v1.0.186`
    ... which satisfies path dependency `serde` (locked to 1.0.186) of package `serde_derive v1.0.186`
    ... which satisfies path dependency `serde_derive` (locked to 1.0.186) of package `serde v1.0.186`

I think circular optional dependencies are allowed though. So this would only work if serde_derive can know whether serde's "derive" feature is enabled, and only enable its lockstep dependency on serde if serde's "derive" feature is not enabled. As far as I know, Cargo cannot express that. Serde's "derive" feature can turn on a feature in serde_derive to notify it of serde's "derive" feature being on, but serde_derive cannot turn off a dependency in response to that feature, nor can serde turn off a serde_derive feature in response to "derive" being on.

Overall I think this is working as intended as currently implemented.
macro-dependencies (https://github.com/rust-lang/rust/issues/54363#issuecomment-1237544924) will allow the lockstep to be expressed in a tidier way (without adding to lockfile) when that becomes available. Serde_derive would then have [macro-dependencies] serde = { version = "=1.0.V", default-features = false }.


Does omnidb support linux ?

Hi,
I love omni and i would like to start using it. Where can i find the linux version, am using ubuntu 14.

Hello pmaigi.
Thank you for your feedback!
Yes, OmniDB is supported on linux. Note that OmniDB is a web application, so you need a webserver to host it.
On Linux you can use Mono (virtual machine) along with XSP4 (webserver) to run OmniDB.
It is very easy to install these requirements:
sudo apt-get install mono-complete mono-xsp4
After that, go to the folder where OmniDB is and just type
xsp4 --port PORT
where PORT is the port of your choice.
And that's it. Open your browser and type <IP_ADDRESS>:PORT
If you need further info, just ask :)

Thanks @rafaelthca


Two NPM pages causes confusion

Currently there are two NPM pages for the project:
https://www.npmjs.com/package/slack-client
https://www.npmjs.com/package/@slack/client
The old page states that We'll dual-publish both @slack/client and slack-client until at least 2.1.0 is released, and possibly past that, but please switch over before then.
However the current version on the old page is 2.0.4 so a user would be unaware that the project has transferred over.

There is a part of the old package's readme that states the move over? I guess it doesn't really mention that the transfer has already happened, but assuming they take the advice and move over, they'll likely notice.

Would help if npm deprecate was used on the old package though.

Thanks, oversight on my part. I'll do that and update the README.

Ok, fixed, thanks for catching this.

np - many thanks for the speedy action


AWS recently added a new feature

Hey @jithindevasia could you please sign the CLA first? Thanks!

👋 @jithindevasia .
Can you verify that you have signed the CLA?
Reach out if you need help. After the CLA is signed, this PR can be reviewed.

/close


Bottom Pixel overflow

How can I fix this? I'm new to Flutter. This is a great control btw

The overflow doesn't really seem to have major impact. It won't be visible in release mode. Cannot fix it myself for now unfortunately.


Release/0.27.0

Update to Polkadot-JS Apps 0.126.1 and support Substrate Node v0.9.31-38 (as tested)

Please address the conflicts in the workflows.


Add api handler to register app on psp backend and import location data

Closes #1371
Deploy control center after this is merged & online

run set-app-country script after deploy


Error: connect ECONNREFUSED Is node running with --debug port 5858?

Hello.
I'm brand new to node-inspector having downloaded it for the first time today.
I got version 0.6.1 which is running under node version 0.10.21.
Having followed the instructions (about 10 times now)
node-inspector gives me
Node Inspector v0.6.1
   info  - socket.io started
Visit http://<IP_ADDRESS>:8080/debug?port=5858 to start debugging.

I then ran:
$ node --debug app.js
debugger listening on port 5858

if I then open Chrome version 31.0.1650.57
I just get the error message
Error: connect ECONNREFUSED
Is node running with --debug port 5858?
```
I don't really know where to start here.
I've tried reversing the order for ````node-inspector```` and ````--debug app.js````
I've tried killing all the processes and starting again.
I've tried ````node-inspector --web-port={port}````  to run it under a a different port.
Same error message all the time.
Would someone mind pointing me in the right direction please.

I'm getting this problem with the latest version.
sudo node-inspector && sudo node --debug --no-preload -p 9362
Node Inspector v0.11.1
Visit http://<IP_ADDRESS>:8080/?ws=<IP_ADDRESS>:8080&port=5858 to start debugging.

And in chrome I get this error:
Request with id = 10 failed. "ErrorNotConnected: Error: connect ECONNREFUSED. Is node running with --debug port 5858?"

It's not letting me edit, but I wanted to add that just using "node-debug app.js" has the app running, but it doesn't seem reachable.  The app doesn't behave correctly (can't connect), and I can't access the inspector, getting ERR_CONNECTION_REFUSED
sudo node-debug app.js
Node Inspector is now available from http://<IP_ADDRESS>:8080/?ws=<IP_ADDRESS>:8080&port=5858
Debugging `app.js`

Debugger listening on port 5858

Hey i am founding this error on my Node
D:\howrah>ionic start project1 sidemenu
Creating Ionic app in folder D:\howrah\project1 based on sidemenu project
Downloading: https://github.com/driftyco/ionic-app-base/archive/master.zip
Error Initializing app:  Error: tunneling socket could not be established, cause
=connect ECONNREFUSED
at ClientRequest.onError (C:\Users\riturajcse\AppData\Roaming\npm\node_modul
es\ionic\node_modules\request\node_modules\tunnel-agent\index.js:174:17)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:107:17)
at Socket.socketErrorListener (_http_client.js:271:9)
at Socket.emit (events.js:107:17)
at net.js:459:14
at process._tickCallback (node.js:355:11)
Error: tunneling socket could not be established, cause=connect ECONNREFUSED
at ClientRequest.onError (C:\Users\riturajcse\AppData\Roaming\npm\node_modul
es\ionic\node_modules\request\node_modules\tunnel-agent\index.js:174:17)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:107:17)
at Socket.socketErrorListener (_http_client.js:271:9)
at Socket.emit (events.js:107:17)
at net.js:459:14
at process._tickCallback (node.js:355:11)
tunneling socket could not be established, cause=connect ECONNREFUSED (CLI v1.6.
4)
Your system information:
Cordova CLI: 5.2.0
Ionic CLI Version: 1.6.4
Ionic App Lib Version: 0.3.8
OS: Windows 8
Node Version: v0.12.7

start request failed { [Error: connect ECONNREFUSED]
I found my firewall is blocking this to run. Can somebody tell me how to allow this through firewall?
its blocking my jasmine test to run,

I have the same problem can some help please..??
Thanks in Advance.

npm-debug.zip


Unexpected COB

Unexpected COB
As I observed, a new amount of COB is added to the current COB that is active at night. But I don't do this addittion from the pump or the Nightscout careportal.  It is doing it itself. As a result, when the system is included in the calculation of active COB, it need to send more unnecessary insulin, which causes us to live low.
As you can see in the two photos below, the same day at 23:58 active COB is 5 and then  00:02 active COB will be 10. I don't do this addition

l am waiting for your help on the subject

Sorry for the slow response: we've been dealing with the fallout of Dana falling off a the side of a mountain in New Zealand.
Can you paste the full pump-loop.log output from one run just before midnight, and one run just after?  And the full cat-autotune output?
Thanks,
Scott

Closing due to logs/lack of activity in this thread + so we can keep the discussion over at the related issue: https://github.com/openaps/oref0/issues/977 (please target additional comments or logs with this issue there)


Some CONFIGURE left, mainly in test comment.

See JENKINS-XXXXX.

Proposed changelog entries

Entry 1: Issue, Human-readable Text
...

Submitter checklist

[ ] JIRA issue is well described
[ ] Changelog entry appropriate for the audience affected by the change (users or developer, depending on the change). Examples
* Use the Internal:  prefix if the change has no user-visible impact (API, test frameworks, etc.)
[ ] Appropriate autotests or explanation to why this change has no tests
[ ] For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers
@mention

However, in the JEP, the setPrimaryView appears as CONFIGURE/MANAGE, so we should change that there as well.


Notification Service

Issue Description
A notification service is necessary to inform users or RDS groups about events when assigned. The service will send notifications, ensuring that people or RDS groups are simply notified about the events.
Current Behavior
we don't have a feature as of now
[Explain what currently happens when this issue is encountered.]
RFC
https://github.com/Real-Dev-Squad/mobile-app/discussions/307
Environment

Operating System: [e.g., Windows, macOS, Linux]
Browser (if applicable): [e.g., Chrome, Firefox, Safari]
Version of Software/Project: [e.g., v1.0.0]

Additional Information
[Include any additional context, logs, or details that might be helpful in addressing the issue.]
Checklist

[ ] I have read and followed the project's code of conduct.
[ ] I have searched for similar issues before creating this one.
[ ] I have provided all the necessary information to understand and reproduce the issue.
[ ] I am willing to contribute to the resolution of this issue.

Thank you for contributing to our project! We appreciate your help in improving it.
📚 See contributing instructions.

Notification RFC is done !


Remove resolved TODO

Fixed in 5b8fa431ae8eb5a18ba913494119e394230d4b70
[ci skip]

Is this resolved in master only?

master & 1.1.0 only.
I will take care of a back-port for 1.0.2.

Did you forget to merge ff0426c to 1.1.0?

@bernd-edlinger Merged now.


Sorting of credentials

Summary
Ability to sort credentials by created at timestamp on all types of credentials (key-auth,hmac, oauth2, jwt, etc)

@mattsaddo would you be willing to submit a PR for this functionality?

@mattsaddo ping, any update?