litefs: 0.2.0 -> 0.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/superfly/litefs/releases.
meta.description for litefs is: "FUSE-based file system for replicating SQLite databases across a cluster of machines"
meta.homepage for litefs is: "https://github.com/superfly/litefs"
meta.changelog for litefs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.3.0 with grep in /nix/store/zv99x1y398p58n0pax8s6klmmk029dqa-litefs-0.3.0
found 0.3.0 in filename of file in /nix/store/zv99x1y398p58n0pax8s6klmmk029dqa-litefs-0.3.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
litefs

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zv99x1y398p58n0pax8s6klmmk029dqa-litefs-0.3.0
ls -la /nix/store/zv99x1y398p58n0pax8s6klmmk029dqa-litefs-0.3.0/bin

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

1 package built:

litefs

Maintainer pings
cc @dit7ya for testing.

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

1 package built:

litefs


ImportError: cannot import name 'JSONWebSignatureSerializer' from 'itsdangerous'

Python 3.10.4
pipenv, version 2022.5.2
flask-oidc 1.4.0
Exception happens on the following import line:
from flask_oidc import OpenIDConnect

Hello,
This class has been removed in itsdangerous 2.1.0 : https://itsdangerous.palletsprojects.com/en/2.1.x/changes/#version-2-1-0
It was mentioned in https://github.com/puiterwijk/flask-oidc/issues/3 ...
In your Pipfile, could you please add itsdangerous = "<2.1" ?

How long can you stay in this deprecated functionality? Instead of going backward, it should be updated to use proper library as described here:
https://itsdangerous.palletsprojects.com/en/2.1.x/changes/
https://docs.authlib.org/en/latest/jose/jws.html

I honestly don't know, I had the same issue several days ago and thought it would be helpful to share ;)

Apparently fixed in https://github.com/puiterwijk/flask-oidc/pull/144

confirming that installing #144 fixes it.

Fixed? Install? What do you mean and how? https://github.com/puiterwijk/flask-oidc/pull/144 is not even merged yet!?

@khteh you can install the changes introduced by #144 by specifying directly the MR or the commit you want in your pip install command.
e.g.: pip install git+https://github.com/puiterwijk/flask-oidc.git@b10e6bf881a3fe0c3972e4093648f2b77f32a97c
On our end, we are using a custom security manager for Airflow to connect using OIDC, which relies on flask-oidc underneath (https://flask-appbuilder.readthedocs.io/en/latest/security.html#authentication-openid). Because the dependency on itsdangerous is not pinned, the latest build broke the oidc workflow to connect to Airflow, but adding the latest commit of  #144 as dependency in our docker build (command above) fixed it.

What stops you from merging and releasing the fix as a new version?

@khteh well, one would need to have the proper rights on the repo for that, so this decision relies on @puiterwijk’s approval of the PR.
In the meantime targeting the code of the PR for the install  is a workaround.

Ok. Thanks. BTW, what's MR?

Sorry, I mixed the Gitlab’s way of defining things. MR = Merge request (which is Gitlab’s denomination for Pull Request).

I failed to install it using pipenv:
$ pipenv install git+https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head#egg=flask-oidc
/home/khteh/.local/lib/python3.10/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 1.1build1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/khteh/.local/lib/python3.10/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.43ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
Installing git+https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head#egg=flask-oidc...
Error:  An error occurred while installing git+https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head#egg=flask-oidc!
Error text: Collecting flask-oidc
  Cloning https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head to /tmp/pip-install-2sdrfu86/flask-oidc_f913d0b02d084fdea2ae53e1b814d2d2

  Running command git clone --filter=blob:none --quiet https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head /tmp/pip-install-2sdrfu86/flask-oidc_f913d0b02d084fdea2ae53e1b814d2d2
  remote: Not Found
  fatal: repository 'https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head/' not found
  error: subprocess-exited-with-error

  × git clone --filter=blob:none --quiet https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head /tmp/pip-install-2sdrfu86/flask-oidc_f913d0b02d084fdea2ae53e1b814d2d2 did not run successfully.
  │ exit code: 128
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× git clone --filter=blob:none --quiet https://github.com/puiterwijk/flask-oidc.gitrefs/pull/144/head /tmp/pip-install-2sdrfu86/flask-oidc_f913d0b02d084fdea2ae53e1b814d2d2 did not run successfully.
│ exit code: 128
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

✘ Installation Failed

@puiterwijk could this PR please be merged and released?

Yes. See https://github.com/puiterwijk/flask-oidc/issues/147#issuecomment-1207160732

So it's 2023, 4 months later, is this still the issue and is it not yet updated?

Came here hoping for a fix too.

Still waiting on a fix…


Add french translation

Hello, i've translated your english config file to my native tongue.
Feel free to use it.
(Your template is really cool)

Thanks! :+1:


How to handle empty string to url transformations

Would love to hear what is a better approach in handling empty string to url transformations. Thanks.
    static func stringToURL(object: Any) throws -> URL {

        guard let string = object as? String else {
            throw MapperError.convertibleError(value: object, type: String.self)
        }

        // If string exists
        if string.isNotEmpty{
            return URL(string: string)!
        }else{
            return URL(string: "")! // ERRORS HERE BECAUSE STRING IS EMPTY AND IT IS TRYING TO UNWRAP THIS
        }

    }

In the case that you have an empty string, what would your expected output be? Actually until Swift 3, creating a URL with an empty string returned a non-nil string. But regardless if nothing else you'd be better off changing your logic to throw instead of crash, and then handle that from your model in the case you expected a URL but didn't get one. Something like:
if let url = URL(string: string) {
    return url
} else {
    throw MapperError.convertibleError(value: object, type: URL.self)
}

Let me know if you have any other questions! Also note that Mapper has this functionality built in, so you can already map a string to a URL without any added code, see that implementation here: https://github.com/lyft/mapper/blob/master/Sources/NSURL+Convertible.swift#L13-L23

@keith Thanks for the pointer!


Wrong output when resampling with Gaussian interpolation when employing streaming

Description
Since #988 was resolved with #998, it is now possible to resample with Gaussian interpolation when employing streaming, but the output differs from the result when streaming is not used.
Steps to Reproduce
Based on the (apparent) MWE from https://github.com/InsightSoftwareConsortium/ITK/pull/998#issuecomment-499882759, I tried to reproduce the problems found with my resamlple ITK-CLI:
https://gitlab.com/romangrothausmann/ITK-CLIs/commits/debugGaussRes
It turns out that when the streaming and the non-streaming are scoped (https://github.com/romangrothausmann/ITK-CLIs/commit/eb81cb5ea63d3ac4edf0a97471ae776b129b0dee), the resulting outputs (RAW from MHD) differ to each other but have the same MD5 as obtained with resamlple.
Expected behavior
The output from the resample filter should be the same no matter if streaming is used or not , this should hold for all available interpolators.
Versions
ITK @ 8d9f21db6 (#988)
Environment
DF from ITK-CLIs:
https://gitlab.com/romangrothausmann/ITK-CLIs/blob/eb81cb5ea63d3ac4edf0a97471ae776b129b0dee/Dockerfile

@dzenanz @blowekamp
Not sure though why the version without scoping behaves differently. Could it be that the filter is not re-executed even though it has filter->ReleaseDataFlagOn();? Without that it would be necessary to outdate the filter (with input->Modified();) to have it re-execute for the streaming.

Working on a test for the ITK test-suite:
https://github.com/romangrothausmann/ITK/tree/TestResampleSDI4GaussInterpolator

Minimal modification of the test program to reproduce the problem is just to write once per call using an extra parameter to define streaming or not: https://github.com/romangrothausmann/ITK-CLIs/commit/b5cfc691b8ce0983cfda4d060c0edc219c57eee7

@thewtex can you tackle this? test.cxx is an easy way to reproduce the problem.

Yes, I will take a look.


I'm not able to run 3D examples with Processing.py

Hello,
I installed Processing IDE according to Getting started tutorial on Processing.py and I tried some basic examples (from Getting started and Processing overview sections). After that I wanted to try examples from P3D section, but when I click on run, nothing happens. I don't get any errors. I tried same examples in Java and everything worked fine. Any ideas what could be wrong? Thank you.

Not sure what version of Processing and platform you're running on? Maybe this helps --
https://github.com/processing/processing/issues/6061

I tried version  3.5.4 and it works fine.


python311Packages.pysnmplib: 5.0.23 -> 5.0.24

Diff: https://github.com/pysnmp/pysnmp/compare/refs/tags/v5.0.23...v5.0.24
Changelog: https://github.com/pysnmp/pysnmp/releases/tag/v5.0.24
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

2 packages failed to build:

python312Packages.atenpdu
python312Packages.atenpdu.dist

6 packages built:

python311Packages.atenpdu
python311Packages.atenpdu.dist
python311Packages.pysnmplib
python311Packages.pysnmplib.dist
python312Packages.pysnmplib
python312Packages.pysnmplib.dist


fix: Disable hover on opportunity and click handler when not logged in.

[#151786925]

I've made the requested changes


Rancher AD Access Control Question

I have added the AD integration to Rancher but anywhere where I want to add a member to a project or cluster but it only pulls down my groups. I am confused how we are going to manage users. Should I be able to search any other AD user in that dropdown and add them as a member? I also noticed that under the users page even after I logged in there isn't one generated for my AD account which I also thought could be odd but it also could make sense that since I logged in as AD and not as a local account.

 You will only see the single user account in the accounts page.
Can you share a screenshot of how your user search and group search base?

@mitchellmaler Along with the user and group search bases, can you also share if you are experiencing this with a fresh setup of 2.0.1 or upgrade?

Version 2.0.1 (just ugraded)
Ah that makes sense. I tested with another user and it did create an account for them. I was thinking it wasn't working since I was expecting an account for my user.

The user and group search base is the basic 'dc=domain,dc=comany,dc=net' which seems to be working. It is able to find my account and it also lists my groups.
After messing around the the member adding for a cluster or project I think I figured out the issues. Right now the dropdown only returns "Group Group". If I then try to search anything in the text box nothing ever returns even if I search a "Name" of a user or their samAccountName. However I figured out finally how to get it work, if I start the search with "user or user-" since each rancher user account key starts with that it then returns the list of users created.
This makes me think the search logic on that text field is not searching on name and id but only on ID and the dropdown is not also showing a list of users but only my loaded groups.
As a user/admin I would expect the dropdown to show first a list of users or maybe new users as well with some groups (most of the time I wont be part of the group i would add to a project/cluster so my groups isn't the best). Then if I search for any users name, user id, or ad group (not just my own) it would return those so I can link it.

@mitchellmaler Thanks. The dropdown like you said, is only supposed to list the groups that the user is a part of. You can search and add users/groups via the search text box. To understand why user search isn't working for you, can you share your User Search Field attribute?
Also while searching for AD users, were you logged in as the Default Admin (Local user) or the Active Directory admin?

I tested it with a logged in AD user with Administrator access. When searching in the text box it never returns anything unless I type in 'user-'.
Search Field: (&(objectClass=user)(extensionAttribute15=LDAP))

@mitchellmaler In the User Search Attribute field, only attribute names should be entered. It can't accept LDAP filters.
In 2.0.1 while setting up AD, you'll see under Customize Schema that the Search Attribute for User has three fields sAMAccountName|sn|givenName. So when you enter anything in the text box for searching, we can query your AD server and find that user by sAMAccountName or last or first name. So to be able to search users by their sAMAccountName or first name, please edit this field and change it to sAMAccountName or sAMAccountName|sn|givenName. The only way to edit right now is via disabling re-enabling AD auth,  but the edit AD config option will be coming soon.

@mrajashree Thanks that fixed the issue! I guess I was a bit confused with what to put in that field but it makes more sense now.


Enable base64 decode of request in session view

Please add the ability base64 decode the originating request when reviewing a session (request headers).

Use CyberChef!


[LG] support parameters as expression to template resolution call

We need to support parameters to a template resolution call be an expression. So something like this is possible.
# Suggestions (list)
- \n \[Suggestions={join(list, '|')}]

# GreetPhrase
- Hi
- Hello
- Hiya

# WelcomeUser
- [GreetPhrase], I'm the todo bot. How can I help you today? \n [Suggestions(createArray('Add Todo', 'Show Todo', 'Delete Todo', 'Help', 'Cancel'))]

@vishwacsena This is doable via https://github.com/microsoft/botbuilder-dotnet/pull/2271
One question i have when i'm implementing this, since we support [Suggestions(createArray("a", "b")] and we treat what's inside it an expression. Why can't I use {Suggestions(createArray("a", "b"))}, and then the quesiton is, why bother using lgTemplate function, why just {TemplateName(args)}, or @{templateName(args)}, it's all made possible by this PR.

Opened a DCR to track this https://github.com/microsoft/botbuilder-dotnet/issues/2272

Closing this specific issue since the parametrization is now supported via #2271
Let’s continue the remaining discussions via the other active github issues.


emissary fails to recover after SIGTERM - possibly due to frequent reconfig

Describe the bug

emissary-ingress running on fairly demanding environment with many resources/mappings/services etc.,
Start seeing warnings such as:

"Memory Usage: throttling reconfig v2854 due to constrained memory with 112 stale reconfigs (60 max)"
...

No longer works, e.g., gives errors such as these where previously they would be 30x or 200.

ACCESS [2024-07-19T05:44:22.929Z] "GET /grafana/metrics HTTP/1.1" 503 UH 0 4172 16 - "<ip>,<ip>,<ip>" "Prometheus/2.35.0-gmp.4" "<uuid>" "<uuid>.<domain>" "-"

ACCESS [2024-07-19T09:59:29.493Z] "GET <path> HTTP/1.1" 403 UAEX 0 3984 0 - "<ip>, <ip>,<ip>, <ip>, <ip>,<ip>" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>" <uuid>" "<uuid>.<domain>" "-"

To Reproduce
Can work on providing a more concrete example if needed, but we are observing this after around 12-24h on a cluster as described.
Expected behaviour
Should be able to recover after being replaced. We have observed the SIGTERM due to a promotion which is expected, but also SIGKILL due to memory usage - the latter seems to have been fixed after increasing our resource limits.
Versions (please complete the following information):

Ambassador: 3.9.1
Kubernetes environment: GKE
Version: v1.27.14-gke.1042001

Additional context
Possibly related:

https://github.com/emissary-ingress/emissary/issues/3684
https://github.com/emissary-ingress/emissary/issues/3264

Some relevant configuration options:
spec:
  template:
    spec:
      terminationGracePeriodSeconds: 90
      containers:
      - name: ambassador
        lifecycle:
          preStop:
            exec:
              command:
              - sleep 60
        livenessProbe:
          failureThreshold: 6
          httpGet:
            path: /ambassador/v0/check_alive
            port: admin
            scheme: HTTP
          initialDelaySeconds: 30
          periodSeconds: 6
          successThreshold: 1
          timeoutSeconds: 1
        readinessProbe:
          failureThreshold: 6
          httpGet:
            path: /ambassador/v0/check_ready
            port: admin
            scheme: HTTP
          initialDelaySeconds: 30
          periodSeconds: 6
          successThreshold: 1
          timeoutSeconds: 1
        resources:
          limits:
            cpu: "1"
            memory: 900Mi
          requests:
            cpu: 200m
            memory: 600Mi

@fs185143, just to confirm, is this with Emissary or Ambassador Edge Stack? (It's a bug either way, just want to make sure of what I'm looking at. 🙂)

Failing to recover after the SIGTERM sounds like a bug.  But you can take some measures to address large reconfiguration or High CPU/memory usage with some of these specs.  You can also try reducing AMBASSADOR_AMBEX_SNAPSHOT_COUNT.
A common reason for high CPU and memory is a high number of automated snapshots of your configuration. Snapshots are only stored until the limit of AMBASSADOR_AMBEX_SNAPSHOT_COUNT is met.

Failing to recover after the SIGTERM sounds like a bug. But you can take some measures to address large reconfiguration or High CPU/memory usage with some of these specs. You can also try reducing AMBASSADOR_AMBEX_SNAPSHOT_COUNT.
A common reason for high CPU and memory is a high number of automated snapshots of your configuration. Snapshots are only stored until the limit of AMBASSADOR_AMBEX_SNAPSHOT_COUNT is met.

thanks - we will try this on our emissary/emissary-ingress deployment
spec:
  template:
    spec:
      containers:
      - name: ambassador
        env:
        - name: AMBASSADOR_AMBEX_SNAPSHOT_COUNT
          value: "5"
        - name: AMBASSADOR_FAST_RECONFIGURE
          value: "false"
        - name: AMBASSADOR_DRAIN_TIME
          value: "300"

@fs185143, just to confirm, is this with Emissary or Ambassador Edge Stack? (It's a bug either way, just want to make sure of what I'm looking at. 🙂)

I believe it comes under emissary as we are not using the enterprise application

We are now seeing these ambassador logs
Memory Usage 0.85Gi (96%)\n    PID 1, 0.14Gi: busyambassador entrypoint \n    PID 16, 0.04Gi: /usr/bin/python /usr/bin/diagd /ambassador/snapshots /ambassador/bootstrap-ads.json /ambassador/envoy/envoy.json --notices /ambassador/notices.json --port 8004 --kick kill -HUP 1 \n    PID 18, 0.34Gi: /usr/bin/python /usr/bin/diagd /ambassador/snapshots /ambassador/bootstrap-ads.json /ambassador/envoy/envoy.json --notices /ambassador/notices.json --port 8004 --kick kill -HUP 1 \n    PID 29, 0.11Gi: envoy -c /ambassador/bootstrap-ads.json --base-id 0 --drain-time-s 300 -l error \n    PID 246459, 0.10Gi (exited): envoy --service-node test-id --service-cluster ambassador-emissary --config-path /ambassador/snapshots/econf-tmp.json --mode validate \n    PID 246489, 0.08Gi (exited): envoy --service-node test-id --service-cluster ambassador-emissary --config-path /ambassador/snapshots/econf-tmp.json --mode validate \n    PID 246525, 0.09Gi: envoy --service-node test-id --service-cluster ambassador-emissary --config-path /ambassador/snapshots/econf-tmp.json --mode validate
...
time="2024-08-04 13:55:43.4550" level=warning msg="Memory Usage: throttling reconfig v41082 due to constrained memory with 15 stale reconfigs (1 max)" func=github.com/emissary-ingress/emissary/v3/pkg/ambex.updaterWithTicker file="/go/pkg/ambex/ratelimit.go:140" CMD=entrypoint PID=1 THREAD=/ambex/updater

which caused the emissary-ingress pod to restart after running for 3 days, and post-restart it only gives 403 errors.
This is with the following config
spec:
  template:
    spec:
      terminationGracePeriodSeconds: 90
      containers:
      - name: ambassador
        env:
        - name: AMBASSADOR_AMBEX_SNAPSHOT_COUNT
          value: "5"
        - name: AMBASSADOR_FAST_RECONFIGURE
          value: "false"
        - name: AMBASSADOR_DRAIN_TIME
          value: "300"
        - name: SCOUT_DISABLE
          value: "1"
        lifecycle:
          preStop:
            exec:
              command:
              - sleep 60
        livenessProbe:
          failureThreshold: 6
          httpGet:
            path: /ambassador/v0/check_alive
            port: admin
            scheme: HTTP
          initialDelaySeconds: 30
          periodSeconds: 6
          successThreshold: 1
          timeoutSeconds: 1
        readinessProbe:
          failureThreshold: 6
          httpGet:
            path: /ambassador/v0/check_ready
            port: admin
            scheme: HTTP
          initialDelaySeconds: 30
          periodSeconds: 6
          successThreshold: 1
          timeoutSeconds: 1
        resources:
          limits:
            cpu: "1"
            memory: 900Mi
          requests:
            cpu: 200m
            memory: 600Mi

Would appreciate any advice/support - thanks.

Going to try:

Lower AMBASSADOR_AMBEX_SNAPSHOT_COUNT from 5 to 0
Re-enable AMBASSADOR_FAST_RECONFIGURE
Increase memory limit from 900Mi to 2000Mi
Increase memory request from 600Mi to 1000Mi

Could the 403s be due to some cert issue that occurs after restart perhaps?

OK so I think it's actually more related to https://github.com/emissary-ingress/emissary/issues/5564
We are seeing these logs after enabling debug
[2024-08-07 11:02:15.136][31][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:152] dns resolution for authserver.authserver failed with c-ares status 12
[2024-08-07 11:02:15.136][31][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:245] DNS request timed out 4 times
[2024-08-07 11:02:15.136][31][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:278] dns resolution for authserver.authserver completed with status 1
[2024-08-07 11:02:15.136][31][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:184] DNS refresh rate reset for authserver.authserver, (failure) refresh rate 5000 ms

OK so I think it's actually more related to #5564
We are seeing these logs after enabling debug
[2024-08-07 11:02:15.136][31][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:152] dns resolution for authserver.authserver failed with c-ares status 12
[2024-08-07 11:02:15.136][31][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:245] DNS request timed out 4 times
[2024-08-07 11:02:15.136][31][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:278] dns resolution for authserver.authserver completed with status 1
[2024-08-07 11:02:15.136][31][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:184] DNS refresh rate reset for authserver.authserver, (failure) refresh rate 5000 ms

Do we think this may have been fixed by a version of envoy > 1.27.2? e.g.,

https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.28/v1.28.0#bug-fixes

dns: Fixed a bug where when respect_dns_ttl was set to true, c-ares dns resolver only considered address record for TTL calculation while ignoring CNAME records TTL. Now when respect_dns_ttl is set to true minimum of all TTL records is considered.

https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.29/v1.29.0#bug-fixes

DNS: Fixed a race condition that when multiple requests with the same authority header are sent to Envoy, sometimes some requests may receive 503 response with no_healthy_upstream from Envoy. The fix is guarded by runtime guard envoy.reloadable_features.dns_cache_set_first_resolve_complete, which defaults to true.

https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.30/v1.30.0#minor-behavior-changes

dns: Fixing a bug in the getaddrinfo resolver where it did not reresolve on EAI_AGAIN. This behavioral change can be temporarily reverted by setting envoy.reloadable_features.dns_reresolve_on_eai_again to false.

https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.31/v1.31.0#minor-behavior-changes

dns: Changes the behavior of the getaddrinfo DNS resolver so that it treats EAI_NODATA and EAI_NONAME as successful queries with empty results, instead of as DNS failures. This change brings the getaddrinfo behavior in-line with the c-ares resolver behavior. This behavior can be reverted by setting the runtime guard envoy.reloadable_features.dns_nodata_noname_is_success to false.

https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.31/v1.31.0#bug-fixes

cares: Upgraded c-ares library to 1.20.1 and added fix to c-ares DNS implementation to additionally check for ARES_EREFUSED, ARES_ESERVFAIL and ARES_ENOTIMP status. Without this fix, DestroyChannelOnRefused and CustomResolverValidAfterChannelDestruction unit test will break.

@fs185143 That's definitely the first thing to try, which is part of why I'm trying to do a new 3.10 release. 🙂
Note that there's a development branch of Emissary 4 that's already running Envoy 1.30: if you're interesting in testing that to see how it behaves here, let me know.


Diet template block default implementation.

Currently, diet template blocks cannot have a default implementation while in jade they can.
Ie.
layout.dt:
html

body
 block hello
  p world <-- error

page.dt:
extends layout

block hello
  p not world

Gives:
Child elements for 'include' are not supported.

(Which btw is also a slightly odd error, since it's extends, not include.)

Implemented by c5d8991b19175ff655bbf82ebff8d1f873502672. The "prepend" mode is also supported:
extends layout

prepend hello
  p hello

->

hello

world


Using the frameworks for making this project

We can discuss the different technology required for making this clone. Currently, I am planning to use Flask for backend, and React for frontend.

We can use YouTube API for accessing the videos. More info - YouTube API


Dump CREATE_OBJECT_CLASS_NOT_FOUND

I set up the option in abapGit to run a background job each night to get the latets version. Each night it dumps trying to create a class calledd PULL which obviously does not exist.

Class ZCL_ABAPGIT_BACKGROUND method RUN.
It could be this is too problematic to ever work, in which case maybe the background option should be removed from the abapGit menu.

whats the value of <ls_list>-method ?

It is PULL

@hardyp the proper value for <ls_list>-method should be ZCL_ABAPGIT_BACKGROUND_PULL. So check how lt_list is being put together.

First the contents of table ZABAPGIT is read with key BACKGROUND. It looks like it is getting an XML string with the user name (email) to use to connect with GitHub. It the fills this structure from the XML.

The SETTINGS are a table of KEY/VALUE pairs. The class methods are both static so I will write a test program and debug it.

OK, let us see how this gets built up (or not)

The XML contains the method name PULL, but the transformation does not extract the username, and the password is not even in the XML as far as I can see.

So, instead of PULL the value should be ZCL_ABAPGIT_BACKGROUND_PULL, and the username and password has to be extracted from the XML string, and the password needs to be set in the XML string i.e. in the ZABAPGIT table.

I think this was changed in the code very long time ago, try modifying the XML via the db util, and set it up the background from scratch

OK I added the entries manually, and all was well.
I then set up a new background pull for the "code pal" and this time the correct XML entries were saved. Therefore this issue is closed. The root cause was me setting up the background pull a long time ago, before the code was fixed.
I would end by saying this is a FANTASTIC bit of functionality and I am so happy I have got it working at last.


Fix race condition in Terminate which fixes flaky integration test MixedModeReadWrite

The test was flaky because after the Database had shutdown, background goroutines would continue running (sometime between the call to Terminate() completing and the actual process exiting) and when they called GetOwnedNamespaces() they would receive an empty list.
The empty list is bad, because when the list of namespaces is empty, the logic in this function allows M3DB to delete all commitlog files which triggers data loss / test failure.

Coverage decreased (-0.03%) to 78.327% when pulling eefcea71ff7ec720eb57285b66310c095ee2ac5d on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.06%) to 78.302% when pulling ae42e76643a5ce86b46d7f95c390b63dbacb1415 on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.06%) to 78.3% when pulling e3367be65c54dec1b89c8ed2dae676bae85d4830 on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.04%) to 78.318% when pulling 3ffeea7edf2c712db85ee951b64f1fe6d29cfacb on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.04%) to 78.318% when pulling 3ffeea7edf2c712db85ee951b64f1fe6d29cfacb on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.1%) to 78.244% when pulling 2857a46657b75b7f70dcd496ca231c7ad819c48f on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.05%) to 78.314% when pulling d4720a4daf06931a0c2ae29973faf142bc6e5ddf on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.

Coverage decreased (-0.05%) to 78.314% when pulling a0835e0e138dea441fbd6b5bb0103766d53aba0d on richardartoul:ra_debug_flakiness into 16ef86362dcdc02d3b7ad8f8bc3f25c3661e5a1d on m3db:master.


V0.2 dev milling change current back

Hello @LucileNaegele! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file fibsem/ui/FibsemMillingWidget.py:

Line 697:1: W293 blank line contains whitespace
Line 769:80: E501 line too long (87 > 79 characters)
Line 771:80: E501 line too long (104 > 79 characters)
Line 772:80: E501 line too long (104 > 79 characters)
Line 773:80: E501 line too long (116 > 79 characters)
Line 777:80: E501 line too long (87 > 79 characters)
Line 778:17: E722 do not use bare 'except'
Line 779:80: E501 line too long (103 > 79 characters)
Line 781:80: E501 line too long (93 > 79 characters)


Add code coverage reporting

Coverage artifacts are viewable at https://build.sawtooth.me/job/Sawtooth-Hyperledger/job/sawtooth-core/job/PR-427/lastSuccessfulBuild/artifact/coverage/html/index.html


[Traefik Plugin Catalog] Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Plugin Catalog.
Cause:
failed to run the plugin with Yaegi: the load of the plugin takes too much time(10s), or an error, inside the plugin, occurs during the load: 1:21: import "github.com/gordonlukch/Keycloak-Introspect" error: /tmp/traefik-plugin-gop2053114730/src/github.com/gordonlukch/Keycloak-Introspect/keycloak_introspect.go:8:2: import "github.com/Nerzal/gocloak/v12" error: /tmp/traefik-plugin-gop2053114730/src/github.com/gordonlukch/Keycloak-Introspect/vendor/github.com/Nerzal/gocloak/v12/client.go:15:2: import "github.com/go-resty/resty/v2" error: /tmp/traefik-plugin-gop2053114730/src/github.com/gordonlukch/Keycloak-Introspect/vendor/github.com/go-resty/resty/v2/request.go:605:48: cannot use type resty.RetryConditionFunc as type func(*unsafe2.dummy, error) bool

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please contact us.

try fixed on new release


about the original resume

excellent work! and could you please give me some advice on how to set the value of original resume when I use DeepPrompt. thank you!

Hi, I'm not sure about the value, you mean the seed or some other parameters?

呃抱歉没讲清楚，就是open clip支持的模型不是有一个列表嘛，我把original_resume设为openai时能运行起来，但是指标好像一般般（我自己做了些改动，不过应该这边没问题），所以就想问下您这边模型选用哪个

you can try the laion or datacamp pretrained


PII Data Storage

The methods of which PII is stored is against PII Law. In addition, this is for a public school operating under government oversight...
Bruh. Encrypt that!


FIX #5001 bug with low-rank matrices

Throw away too small beta's, that caused numerical instability ( Issued #5001 ). Beta cutoff computed with the method adopted from scipy.sparse.linalg.svds (that adopted it from pinv).

@Mazay0 Could you check coding-style failures? (see Details link of Pre-review Tests for full logs)
./cupyx/scipy/sparse/linalg/_eigen.py:132:1: E302 expected 2 blank lines, found 1
./cupyx/scipy/sparse/linalg/_eigen.py:133:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:134:35: W291 trailing whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:137:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:138:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:139:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:141:1: E302 expected 2 blank lines, found 1
./cupyx/scipy/sparse/linalg/_eigen.py:150:1: W293 blank line contains whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:152:24: E231 missing whitespace after ','
./cupyx/scipy/sparse/linalg/_eigen.py:156:32: E261 at least two spaces before inline comment
./cupyx/scipy/sparse/linalg/_eigen.py:157:1: W293 blank line contains whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:261:1: W293 blank line contains whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:263:28: E231 missing whitespace after ','
./cupyx/scipy/sparse/linalg/_eigen.py:268:36: E261 at least two spaces before inline comment
./cupyx/scipy/sparse/linalg/_eigen.py:269:1: W293 blank line contains whitespace

@Mazay0 Could you check coding-style failures? (see Details link of Pre-review Tests for full logs)
./cupyx/scipy/sparse/linalg/_eigen.py:132:1: E302 expected 2 blank lines, found 1
./cupyx/scipy/sparse/linalg/_eigen.py:133:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:134:35: W291 trailing whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:137:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:138:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:139:3: E111 indentation is not a multiple of four
./cupyx/scipy/sparse/linalg/_eigen.py:141:1: E302 expected 2 blank lines, found 1
./cupyx/scipy/sparse/linalg/_eigen.py:150:1: W293 blank line contains whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:152:24: E231 missing whitespace after ','
./cupyx/scipy/sparse/linalg/_eigen.py:156:32: E261 at least two spaces before inline comment
./cupyx/scipy/sparse/linalg/_eigen.py:157:1: W293 blank line contains whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:261:1: W293 blank line contains whitespace
./cupyx/scipy/sparse/linalg/_eigen.py:263:28: E231 missing whitespace after ','
./cupyx/scipy/sparse/linalg/_eigen.py:268:36: E261 at least two spaces before inline comment
./cupyx/scipy/sparse/linalg/_eigen.py:269:1: W293 blank line contains whitespace

I've fixed it, but Read the Docs test failed by timeout. Strange

Hi @Mazay0, any progress on this? Feel free to mention any of us if you have issues fixing the tests.

https://github.com/cupy/cupy/pull/7356#issuecomment-1409859290
#5001 issue should be fixed via #7356


Can't execute migration for table with prefix and comment

Environment

Elixir version (elixir -v): 1.4.0
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): (PostgreSQL) 9.5.3
Ecto version (mix deps): ecto 2.1.3 (Hex package)
Database adapter and version (mix deps): postgrex 0.13.1 (Hex package)
Operating system: Mac OS X 10.12.2

Current behavior
With the following migration:
defmodule EctoSchema.Repo.Migrations.AddSchemaTable do
  use Ecto.Migration

  @prefix "v1"

  def change do
    create table(:person,
      prefix: @prefix,
      primary_key: false,
      comment: "A user that interacts with the app"
    ) do
      add :id, :binary_id,
        primary_key: true,
        comment: """
        The primary unique identifier for the person.
        """

      timestamps()
    end
  end
end

When running mix ecto.migrate, the following errors are thrown:
sntran$ mix ecto.migrate

15:08:00.444 [info]  == Running EctoSchema.Repo.Migrations.AddSchemaTable.change/0 forward

15:08:00.444 [info]  create table v1.person
** (Postgrex.Error) ERROR 42P01 (undefined_table): relation "person" does not exist
    (ecto) lib/ecto/adapters/sql.ex:195: Ecto.Adapters.SQL.query!/5
    (ecto) lib/ecto/adapters/postgres.ex:86: anonymous fn/4 in Ecto.Adapters.Postgres.execute_ddl/3
    (elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
    (ecto) lib/ecto/adapters/postgres.ex:86: Ecto.Adapters.Postgres.execute_ddl/3
    (ecto) lib/ecto/migration/runner.ex:98: anonymous fn/2 in Ecto.Migration.Runner.flush/0
    (elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
    (ecto) lib/ecto/migration/runner.ex:96: Ecto.Migration.Runner.flush/0
    (stdlib) timer.erl:181: :timer.tc/2
    (ecto) lib/ecto/migration/runner.ex:27: Ecto.Migration.Runner.run/6
    (ecto) lib/ecto/migrator.ex:121: Ecto.Migrator.attempt/6
    (ecto) lib/ecto/migrator.ex:71: anonymous fn/4 in Ecto.Migrator.do_up/4
    (ecto) lib/ecto/adapters/sql.ex:615: anonymous fn/3 in Ecto.Adapters.SQL.do_transaction/3
    (db_connection) lib/db_connection.ex:1274: DBConnection.transaction_run/4
    (db_connection) lib/db_connection.ex:1198: DBConnection.run_begin/3
    (db_connection) lib/db_connection.ex:789: DBConnection.transaction/3
    (ecto) lib/ecto/migrator.ex:244: anonymous fn/4 in Ecto.Migrator.migrate/4
    (elixir) lib/enum.ex:1229: Enum."-map/2-lists^map/1-0-"/2
    (ecto) lib/mix/tasks/ecto.migrate.ex:84: anonymous fn/4 in Mix.Tasks.Ecto.Migrate.run/2
    (elixir) lib/enum.ex:645: Enum."-each/2-lists^foreach/1-0-"/2
    (elixir) lib/enum.ex:645: Enum.each/2

Expected behavior
Table person should be created under v1 schema.
I believe it has to do with the comment option, as the generated query does not have the schema/prefix to the table. When I removed the comment on create table, it also errors out on the comment of the field.

@sntran A fix is in master. It would be great if you could try it and tell us if everything is ok now.

I can confirm that the fix works. Thank you!

I'm a little sad that this commit did not make 2.1.4, as it was released just 3 days after this. Is there a chance to have this in 2.1.5. I understand that you're all working on getting 2.2 released, but I do need this to run. Otherwise I have to override my phoenix app in the umbrella to use master branch, which it should only depends on phoenix_ecto and not ecto (I have all data related in a separate app).

2.1.5 was published.


Fix storage.get_available_name 'max_length' argument (Django 1.10)

Just forward max_length argument to Storage.
This change is for Django 1.10.

+1

@blacktorn See this.


Node for sadtalker

Hi, a comfyui nodes for sadtalker too will be pretty cool. Have you looked into sadtalker?

Hey, I have seen it, but currently I don't have time to look into it further and it's out of scope for this project.

Found this issue when searching for a Sadtalker node.
I have a ton of sound files I want to turn into talking avatars video's, Bio's for a guild I am in.
So far online methods are capped at 30 seconds and all nodes I have seen need a video to do the lipsync from.
So if I could plus one this request, even if its a long time away before you even look to do it, as there really isnt an alternative available (that I have found)

Found this issue when searching for a Sadtalker node. I have a ton of sound files I want to turn into talking avatars video's, Bio's for a guild I am in. So far online methods are capped at 30 seconds and all nodes I have seen need a video to do the lipsync from. So if I could plus one this request, even if its a long time away before you even look to do it, as there really isnt an alternative available (that I have found)

Check out this project, brand new, might work on it for Comfy if no one else does at some point: https://badtobest.github.io/echomimic.html

Found this issue when searching for a Sadtalker node. I have a ton of sound files I want to turn into talking avatars video's, Bio's for a guild I am in. So far online methods are capped at 30 seconds and all nodes I have seen need a video to do the lipsync from. So if I could plus one this request, even if its a long time away before you even look to do it, as there really isnt an alternative available (that I have found)

Check out this project, brand new, might work on it for Comfy if no one else does at some point: https://badtobest.github.io/echomimic.html

stumbled on that not long after posting the reply above. Have asked on their tracker if a comfyui node is available. Didnt notice how new it is though https://github.com/BadToBest/EchoMimic/issues/4
The LLMVISION stuff has me a bit nervous of non safetensor models though (I dont fully know enough of about the models to know fully whats safe though, atleast now comfyui does a safety check on start, would love to see a node for echomimic if at all possible (assuming one doesnt exist)


Fix warnings in tests

Codecov Report

Merging #1093 (8b5d6fc) into master (22d3e26) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 8b5d6fc differs from pull request most recent head 175ecf8. Consider uploading reports for the commit 175ecf8 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #1093   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           36        36
  Lines         2452      2450    -2
=========================================
- Hits          2452      2450    -2


octave: 6.4.0 -> 7.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/octave/versions.
meta.description for octave is: "Scientific Programming Language"
meta.homepage for octave is: "https://www.gnu.org/software/octave/"
meta.changelog for octave is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/mkoctfile-7.1.0 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/octave-config-7.1.0 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/octave had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/mkoctfile had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/octave-7.1.0 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/octave-cli-7.1.0 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/octave-cli had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin/octave-config had a zero exit code or showed the expected version
0 of 8 passed binary check by having a zero exit code.
0 of 8 passed binary check by having the new version present in output.
found 7.1.0 with grep in /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0
found 7.1.0 in filename of file in /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0

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

84 total rebuild path(s)

78 package rebuild(s)

78 x86_64-linux rebuild(s)
6 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
gama
librsb
minc_widgets
octave
octave-jit
octaveFull
octavePackages.arduino
octavePackages.audio
octavePackages.bim
octavePackages.bsltl
octavePackages.cgi
octavePackages.communications
octavePackages.control
octavePackages.data-smoothing
octavePackages.database
octavePackages.dataframe
octavePackages.dicom
octavePackages.divand
octavePackages.doctest
octavePackages.econometrics
octavePackages.fem-fenics
octavePackages.financial
octavePackages.fits
octavePackages.fpl
octavePackages.fuzzy-logic-toolkit
octavePackages.ga
octavePackages.general
octavePackages.generate_html
octavePackages.geometry
octavePackages.gsl
octavePackages.image
octavePackages.image-acquisition
octavePackages.instrument-control
octavePackages.interval
octavePackages.io
octavePackages.level-set
octavePackages.linear-algebra
octavePackages.lssa
octavePackages.ltfat
octavePackages.mapping
octavePackages.matgeom
octavePackages.miscellaneous
octavePackages.msh
octavePackages.mvn
octavePackages.nan
octavePackages.ncarray
octavePackages.netcdf
octavePackages.nurbs
octavePackages.ocl
octavePackages.octclip

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0
ls -la /nix/store/397y857bgvn9q9cdph0smj619cs2d6s9-octave-7.1.0/bin

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

4 packages marked as broken and skipped:

octave-jit
octavePackages.fem-fenics
octavePackages.vibes
octavePackages.vrml

24 packages failed to build:

octavePackages.communications
octavePackages.data-smoothing
octavePackages.econometrics
octavePackages.fits
octavePackages.geometry
octavePackages.image
octavePackages.io
octavePackages.lssa
octavePackages.mapping
octavePackages.ncarray
octavePackages.nurbs
octavePackages.ocl
octavePackages.octclip
octavePackages.octproj
octavePackages.optim
octavePackages.quaternion
octavePackages.signal
octavePackages.sockets
octavePackages.sparsersb
octavePackages.statistics
octavePackages.stk
octavePackages.strings
octavePackages.tisean
octavePackages.tsa

50 packages built:

gama
librsb
minc_widgets
octave
octaveFull
octavePackages.arduino
octavePackages.audio
octavePackages.bim
octavePackages.bsltl
octavePackages.cgi
octavePackages.control
octavePackages.database
octavePackages.dataframe
octavePackages.dicom
octavePackages.divand
octavePackages.doctest
octavePackages.financial
octavePackages.fpl
octavePackages.fuzzy-logic-toolkit
octavePackages.ga
octavePackages.general
octavePackages.generate_html
octavePackages.gsl
octavePackages.image-acquisition
octavePackages.instrument-control
octavePackages.interval
octavePackages.level-set
octavePackages.linear-algebra
octavePackages.ltfat
octavePackages.matgeom
octavePackages.miscellaneous
octavePackages.msh
octavePackages.mvn
octavePackages.nan
octavePackages.netcdf
octavePackages.optics
octavePackages.optiminterp
octavePackages.parallel
octavePackages.queueing
octavePackages.splines
octavePackages.struct
octavePackages.symbolic
octavePackages.video
octavePackages.windows
octavePackages.zeromq
openems
python310Packages.python-csxcad
python310Packages.python-openems
python39Packages.python-csxcad
python39Packages.python-openems

Maintainer pings
cc @7c6f434c @doronbehar for testing.

@KarlJoad Have you noticed some packages are broken ever since this update?
This line seem to fail:
https://github.com/NixOS/nixpkgs/blob/7392416a539344c3b3d19c7e6cb7f4e6f49f72aa/pkgs/development/interpreters/octave/build-octave-package.nix#L115
For example:
$ nix build -Lf. octave.pkgs.io
octave> Sourcing write-required-octave-packages-hook.sh
octave> Using writeRequiredOctavePackagesPhase
octave> unpacking sources
octave> unpacking source archive /nix/store/zh1w2v3fh79hrkx0cx37a1a48hvwhjiy-io-2.6.3.tar.gz
octave> source root is io-2.6.3
octave> setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file io-2.6.3/src/octave_4_2_co
octave> patching sources
octave> building
octave> error: unlink: operation failed: No such file or directory
octave> error: called from
octave>     build at line 80 column 7
octave>     pkg at line 720 column 7

I failed to figure out what is this unlink failure.

I have not been closely watching Octave packages for the past few months due to school.
To the best of my knowledge, the only use of unlink in the package codebase is in:
https://github.com/NixOS/nixpkgs/blob/7392416a539344c3b3d19c7e6cb7f4e6f49f72aa/pkgs/development/interpreters/octave/build-env.nix#L32
I will not be able to look into this issue in-depth until after the first week of May, again due to school.

the only use of unlink in the package codebase is in:

That's where I looked into initially as well, but apparently, it's not where things fail, but they fail where octave-cli pkg build is running. Let's keep track this in #168943 .

I will not be able to look into this issue in-depth until after the first week of May, again due to school.

Best of luck with that!


Made updates for the 21st meetup

I updated the goals page for the 21st, added links for Flask-Mega-Tutorial, and Corey Schafer's video series, and a few other small changes.

Basic Smoke Test of the different tabs and looking at the 'goals' page, everything looks good.


Enhance Redirector logic

Redirector should allow to act in two modes: strict (default) and non-strict:
# strict mode with 5 max hops
HTTP.follow(true)
HTTP.follow(:strict => true)
HTTP.follow(:max_hops => 5, :strict => true)

# strict mode with unlimited hops
HTTP.follow(:max_hops => false)
HTTP.follow(:max_hops => false, :strict => true)

# non-strict mode with 5 max hops
HTTP.follow(:strict => false)

# non-strict mode with unlimited hops
HTTP.follow(:max_hops => false, :strict => false)

Strict mode VS non-strict
Thus in strict mode if original request was neither GET nor HEAD, and it received redirect 300, 301 or 302, a StateError exception will be raised. In non-strict mode, request will be redirected with GET verb. Notice that redirects with 307 and 308 codes will work same in both modes - redirect preserving verb of original request.
Notice, that such behavior is a mix of current RFC and proposed (1) changes (2) to that RFC.
RFC2616 says that upon any request but GET or HEAD, if response is redirect 300, 301, 302 or 307, user agent SHOULD NOT continue. Extension to that RFC says that old clients actually will change verb to GET in this case, but it also says, that correct behavior is to follow redirect with original verb if that verb is defined as "safe" (all methods are safe by default except PUT, DELETE and POST), otherwise user agent should halt. Experimental RFC that introduces redirect 308 says that 301 and 302 redirects should be followed with GET verb while 307 and 308 with original verb.
Also, notice that, main difference between 301 VS 308 (permanent redirect) and 302 VS 307 (temporary redirect) is the way how user agent should handle caching (this comes from original RFC).
List of references to keep in mind:

https://tools.ietf.org/html/rfc2616#section-10.3
https://tools.ietf.org/html/draft-reschke-http-status-308-07
https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-6.4

Previous issue: #94

@ixti how are you feeling about this one for 0.8?

@tarcieri will finish today/tomorrow.

I mean - will be ready for 0.8

Sweet


[move-prover] Adds a command-line option to use cvc4 as the backend solver

Adds a command-line option to use cvc4 as the backend solver.
Also fixes a bug where the generate-only command-line option was being ignored

@bors-libra r+

:exclamation: Invalid command

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

@bors-libra land


Update google-cloud-storage minium version higher than 1.30

Hi! Thanks for creating this great library! I've been using it for years.
google-cloud-storage version 1.3 changed to use google-apis-iamcredentials_v1 and google-apis-storage_v1 instead of google-api-client. So google-cloud-storage has some minor changes. (google-api-client is deprecated now.) If you'd like to  know more detail, please read this change log

Closing in favor of #47.
Thanks for the PR anyway!


"Add VMs" button doesn't change to "Add" on selecting Autoscale on VPC LB.

ISSUE TYPE

Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

ACS 4.18.0

CONFIGURATION

VPC
OS / ENVIRONMENT

NA
SUMMARY

On selecting the Autoscale "Yes" when adding a load balancer rule on VPC public IP the Button doesn't change to 'Add' from 'Add VMs'. Adding VMs is not expected for Autoscale load balancer rules. We can click on 'OK' on the instance selection form to add the rule but this is inconsistent with isolated networks and also does not make sense.
STEPS TO REPRODUCE

1. Create a VPC.
2. Add a tier.
3. Go to VPC and click on the 'Public IP Addresses' tab.
4. Acquire a new public IP.
5. Click on the acquired 'Public IP Address' and select the 'load balancing' tab.
6. Add a load balancing rule and select 'Autoscale' as 'Yes'.
7. Observe that you are unable to add the Autoscale LB rule without going to the 'Add VMs form'.

EXPECTED RESULTS

Should be able to add an Autoscale load balancing rule in VPC without viewing the Add VMs form.

ACTUAL RESULTS

Unable to add an Autoscale load balancing rule in VPC without viewing the Add VMs form.

ISOLATED GUEST NETWORKS

VPC

added to <IP_ADDRESS> milestone and assigned to myself

@rajujith
this seems not to be a bug.
the load balancing rules needs to be associated to a network.
You need to choose a VPC tier in the popup, but please do not select any VM

@weizhouapache  but the 'Add VMs' is still a little confusing when we are not expected to add any VM right?

fixed by #7841

fixed by #8793


2.1 Preview is leaking into 2.0.x Ubuntu packages

Related to #1427.
I've found if I try to
apt-get -s -o Debug::pkgProblemResolver=yes install -y dotnet-hosting-2.0.6

I get a error that something with the preview of 2.1 blocking the install.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) dotnet-hostfxr-2.0.6:amd64 < none -> 2.0.6-1 @un uN Ib >
Broken dotnet-hostfxr-2.0.6:amd64 Depends on dotnet-host:amd64 < none | 2.1.0-preview2-26406-04-1 @un uH > (>= 2.0.6)
  Considering dotnet-host:amd64 0 as a solution to dotnet-hostfxr-2.0.6:amd64 4
  Holding Back dotnet-hostfxr-2.0.6:amd64 rather than change dotnet-host:amd64
Investigating (0) dotnet-runtime-2.0.6:amd64 < none -> 2.0.6-1 @un uN Ib >
Broken dotnet-runtime-2.0.6:amd64 Depends on dotnet-hostfxr-2.0.6:amd64 < none | 2.0.6-1 @un uH >
  Considering dotnet-hostfxr-2.0.6:amd64 4 as a solution to dotnet-runtime-2.0.6:amd64 3
  Holding Back dotnet-runtime-2.0.6:amd64 rather than change dotnet-hostfxr-2.0.6:amd64
Investigating (1) dotnet-hosting-2.0.6:amd64 < none -> 2.0.6-1 @un puN Ib >
Broken dotnet-hosting-2.0.6:amd64 Depends on dotnet-runtime-2.0.6:amd64 < none | 2.0.6-1 @un uH >
  Considering dotnet-runtime-2.0.6:amd64 3 as a solution to dotnet-hosting-2.0.6:amd64 10001
    Reinst Failed early because of dotnet-runtime-deps-2.1.0-preview2-26406-04:amd64
    Reinst Failed because of dotnet-host:amd64
    Reinst Failed because of dotnet-hostfxr-2.0.6:amd64
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dotnet-hosting-2.0.6 : Depends: dotnet-runtime-2.0.6 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Emphasis on Reinst Failed early because of dotnet-runtime-deps-2.1.0-preview2-26406-04:amd64

I'm experiencing the same issue that @daniel-white has raised.
Key issue here appears to be the dotnet-host package which has a dependency on dotnet-runtime-deps-2.1.0-preview2-26406-04. This issue applies to any dotnet-.2.0. package. As a result package manager install is not possible.

@leecow any insight to what @robert-ovens noted?

@robert-ovens is correct. The host package is authored such that the latest version is pulled in by the package manager. Until we get the packages re-posted, I was able to workaround this by manually install the specific version of the host first. This can be done with apt-get install dotnet-host=2.0.6-1. Available versions on deb-based systems can be seen with apt-cache madison dotnet-host. Once the host is installed, install whatever version of the runtime or sdk you need.
Here's what it looked like in my 17.10 vm
leecow@lbc-1710:~$ sudo apt-get install dotnet-host=2.0.6-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  dotnet-host
0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded.
Need to get 33.9 kB of archives.
After this operation, 133 kB of additional disk space will be used.
Get:1 https://packages.microsoft.com/repos/microsoft-ubuntu-artful-prod artful/main amd64 dotnet-host amd64 2.0.6-1 [33.9 kB]
Fetched 33.9 kB in 0s (63.1 kB/s)
Selecting previously unselected package dotnet-host.
(Reading database ... 100797 files and directories currently installed.)
Preparing to unpack .../dotnet-host_2.0.6-1_amd64.deb ...
Unpacking dotnet-host (2.0.6-1) ...
Setting up dotnet-host (2.0.6-1) ...
Processing triggers for man-db (<IP_ADDRESS>-2) ...
leecow@lbc-1710:~$ sudo apt-get install dotnet-sdk-2.1.104
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  aspnetcore-store-2.0.0 aspnetcore-store-2.0.3 aspnetcore-store-2.0.5 aspnetcore-store-2.0.6 dotnet-hostfxr-2.0.6 dotnet-runtime-2.0.6 liblttng-ust-ctl2
  liblttng-ust0 libunwind8 liburcu6
The following NEW packages will be installed:
  aspnetcore-store-2.0.0 aspnetcore-store-2.0.3 aspnetcore-store-2.0.5 aspnetcore-store-2.0.6 dotnet-hostfxr-2.0.6 dotnet-runtime-2.0.6 dotnet-sdk-2.1.104
  liblttng-ust-ctl2 liblttng-ust0 libunwind8 liburcu6
0 upgraded, 11 newly installed, 0 to remove and 31 not upgraded.
Need to get 94.0 MB/126 MB of archives.
After this operation, 376 MB of additional disk space will be used.
Do you want to continue? [Y/n] y

Fix is done and tested. Should have everything updated by midday tomorrow at the latest.

Update on this:
Debian, Ubuntu, OpenSUSE and SLES feeds should be up and running for Preview 2 with a fix dotnet-host fix to resolve the compat issue. Still having trouble with the rhel feed used for RHEL, Fedora, CentOS and Oracle need another team to do some surgery to the repo so will need to wait for Monday.


Error: Encrypted private key detected, but no passphrase given

I am using the config from the example:
module.exports = function(deployTarget) {

  var ENV = {
    build: {
      environment: deployTarget
    },
    'revision-data': {
      type: 'git-commit'
    },
    'ssh-index': {
      remoteDir: "/app/myapp",
      username: "user",
      host: "host",
      privateKeyFile: "/Users/user/.ssh/id_rsa",
      allowOverwrite: true
    },
    rsync: {
      dest: "/app/myapp",
      username: "user",
      host: "host",
      delete: false
    }
  };

  return ENV;

};

...
+- upload
|  |
|  +- rsync
|    - Uploading using rsync...
|    -
|  |
|  +- ssh-index
|    - Attempting to connect to remote host: user@host:22
|
+- didFail
Error: Encrypted private key detected, but no passphrase given
Error: Encrypted private key detected, but no passphrase given
    at Client.connect (/Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/node_modules/ssh2/lib/client.js:151:15)
    at /Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/lib/ssh.js:151:14
    at lib$rsvp$$internal$$initializePromise (/Users/user/myapp/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1084:9)
    at PromiseExt.lib$rsvp$promise$$Promise (/Users/user/myapp/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:546:53)
    at new PromiseExt (/Users/user/myapp/node_modules/ember-cli/lib/ext/promise.js:32:8)
    at CoreObject.module.exports.CoreObject.extend._connect (/Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/lib/ssh.js:137:12)
    at CoreObject.module.exports.CoreObject.extend._establishSftp (/Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/lib/ssh.js:107:17)
    at CoreObject.module.exports.CoreObject.extend.fetchRevisions (/Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/lib/ssh.js:81:17)
    at CoreObject.module.exports.CoreObject.extend.upload (/Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/lib/ssh.js:32:17)
    at Class.DeployPluginBase.extend.upload (/Users/user/myapp/node_modules/ember-cli-deploy-ssh-index/index.js:56:20)|
Pipeline aborted

@eighteight - It looks like I forgot to document it, but you should be able to provide your private key's passphrase by providing a passphrase configuration property:
'ssh-index': {
  remoteDir: "/app/myapp",
  username: "user",
  host: "host",
  privateKeyFile: "/Users/user/.ssh/id_rsa",
  passphrase: "YourPassphrase", // or better, process.ENV.YOUR_PASSPHRASE_VAR
  allowOverwrite: true
}

Let me know if that solves your problem. I will make sure to update the Readme to point out that option.

@green-arrow I tried that but got the same error. What fixed it for me is rebuilding the ssh keys and leaving the passphrase empty.
Thanks!

@eighteight - Glad you got it working!
I am going to leave this issue open and try and look into verifying that passphrase protected key files work as expected.

Had the same issue.  This fixed it for me: https://github.com/green-arrow/ember-cli-deploy-ssh-index/pull/2

Fixed by #2

passphrase support (along with agent support) is now available in v0.2.1


CAS: URLs used for blob download and upload do not match protocol spec

See original issue on GitLab
In GitLab by [Gitlab user @juergbi] on Aug 10, 2018, 11:16
The latest remote execution API specifies resource_name for downloads as {instance_name}/blobs/{hash}/{size} and for uploads as {instance_name}/uploads/{uuid}/blobs/{hash}/{size}. Our implementation currently uses {hash}/{size} for both. {instance_name} is optional, however, the other parts are not.
While this does not affect BuildStream clients talking to bst-artifact-server, it breaks interoperability with other CAS implementations and should be fixed as soon as possible.

In GitLab by [Gitlab user @juergbi] on Aug 14, 2018, 13:40
assigned to [Gitlab user @juergbi]

In GitLab by [Gitlab user @juergbi] on Aug 14, 2018, 15:55
mentioned in commit e440d00725079da80e85d248d44ab1d0ad533c40

In GitLab by [Gitlab user @juergbi] on Aug 14, 2018, 16:05
mentioned in merge request !660

In GitLab by [Gitlab user @juergbi] on Aug 14, 2018, 16:42
mentioned in commit b7fa14cc18623a25ba2e24c93657af72633acbf6

In GitLab by [Gitlab user @juergbi] on Aug 15, 2018, 14:02
mentioned in commit 1202ef8af64d328bd5db2ebf19d9246b9bfec195

In GitLab by [Gitlab user @juergbi] on Aug 15, 2018, 15:13
closed via merge request !660

In GitLab by [Gitlab user @juergbi] on Aug 15, 2018, 15:13
mentioned in commit 007624429f22972a9d2d2620cbbbad18411ff4c9

In GitLab by [Gitlab user @juergbi] on Aug 15, 2018, 15:13
closed via commit 1202ef8af64d328bd5db2ebf19d9246b9bfec195

In GitLab by [Gitlab user @juergbi] on Aug 23, 2018, 10:57
mentioned in commit 53b98109df0f888dacdfdd374bcb408deb15c5d7

In GitLab by [Gitlab user @juergbi] on Aug 23, 2018, 12:05
mentioned in commit 96ff4c064ff0b39b5d1c10bf4cfd7b2821b7ad7e


The Future of ioctls

With my recent PR cleaning up the ioctl module I saw some references to cmr/ioctl and how the ioctl module was based on that work. That crate is now deprecated, but I wanted to bring up what we see as the future of nice bindings to ioctls. There is the dcuddeback's ioctl-rs crate, but that appears unmaintained as well.
I know that rust-spidev and serialport-rs both have their own custom implementation of ioctls and it's a little cumbersome. They, among others, would likely benefit from a central location of ioctl bindings.
i was thinking of bringing the cmr/ioctl repository under the nix-rust organization as a new repo & crate. We'd then provide unsafe bindings around ioctls, ideally with a significant amount of type safety thrown on top of them. We'd need at least one person willing to oversee this crate and move it forward, maybe @cmr if you're willing? As I don't think we have any left-over developer time with the existing nix maintainers.

I'm willing, but I might not have the time :) We'll see! I might come back to it.

What sort of benefits do you think we could get from a centralized ioctl repo?  Ioctls are extremely variable; aside from our ioctl! macros I don't think there's much common functionality we could provide.  I have a lot of experience writing Ruby bindings for ioctl-heavy APIs, and I've never come across a single one that I've wanted to reuse elsewhere.  Leaving the bindings in separate domain-specific gems has worked out well for me.

Wait, rust-spidev uses ioctl!. I'm not sure it's a good idea to have all the wrapper code for every ioctl in a single crate. https://github.com/cmr/evdev, the reason I made the original ioctl crate at all, just uses nix instead.

@asomers That's a fair point. The common functionality between ioctls is mostly handled by nix, so other crates would need to create nice APIs that would be pretty specific to the given ioctl. It just seemed more appropriate to have one large crate than a ton of small specifc crates. If we have multiple people using the ioctl crate they might find bugs even if they're using different ioctls that wouldn't otherwise be found if people were using separate ioctl crates. There's a decent amount of overhead on the maintenance side of things when having very small crates, so we could reduce that by having CI framework and issue tracker etc all shared across those crates. Could even feature-gate it so people didn't even need to build ioctls they didn't want.


API: duplicate workflows showing up in workflow list

Unclear why as the API shows these have the same workflow ID (unless this is memory pointer in for loop issue):

Closed by #59


Android: Issues on hot-restart

If an app using flutter_nsd is hot-restarted while discovery is active, calling startDiscovery() will fail.
In case timber logging is active it can be seen that a warning is printed, because NSD is already active, but no error is sent back to the app.
This is due to the exception handler in private fun startDiscovery(serviceType: String), which is doing nothing but printing the warning.
To get working discovery after a hot-restart, currently a cycle of discoverServices()->stopDiscovery()->startDiscovery() is required. If the initial error would be notified back to the app it could detect that error condition and only then do an additional stop/start cycle.
Doing only stopDiscovery()->startDiscovery() after a restart is currently not working, because the onDiscoveryStopped handler is called after startDiscovery() only, as at the time of the initial stopDiscovery() call, no method handler is set in the plugin's channel.

Effectively it's even a bit worse. Due to stopDiscovery() not being synchronous and no callback being existant for onDiscoveryStopped, the simple start,stop,start sequence is unreliable and currently the only way out is doing some extra waiting.

Thanks for reporting this issue. Have you tried what happens on iOS in this case?

It's actually pretty much the same on iOS. Just the plugin's native code is missing even more things to make it possible to detect this error condition on iOS. Working on this right now.
For Android I've got a branch which makes it possible to detect the error and work around it on the app level: https://github.com/jusst-engineering/flutter_nsd/tree/fix/notify-startdiscovery-failure

Pull Request would be greatly appreciated 👍


Playwright with webkit keeps creating an error on Apify Platform with the default Dockerfile

Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/playwright (PlaywrightCrawler)
Issue description
Steps to produce:

Create the actor with PlaywrightCrawler
Use the webkit launcher for the initation
Use the webkit Dockerfile
Deploy the actor on Apify Platform and run the actor.

After these steps, I constantly get the following error and no request has been dispatched. Depending on the needs, I can send the Run ID with DM also.
No headers based on this input can be generated. Please relax or change some of the requirements you specified.
Code sample
// PlaywrightCrawler Config
maxRequestRetries: 20,
maxConcurrency: 5,
launchContext: {
    launcher: webkit,
    launchOptions: {
        headless: false,
    },
}

// Dockerfile
# Specify the base Docker image. You can read more about
# the available images at https://crawlee.dev/docs/guides/docker-images
# You can also use any other image from Docker Hub.
FROM apify/actor-node-playwright-webkit:18

# Copy just package.json and package-lock.json
# to speed up the build using Docker layer cache.
COPY --chown=myuser package*.json ./

# Install NPM packages, skip optional and development dependencies to
# keep the image small. Avoid logging too much and print the dependency
# tree for debugging
RUN npm --quiet set progress=false \
    && npm install --omit=dev --omit=optional \
    && echo "Installed NPM packages:" \
    && (npm list --omit=dev --all || true) \
    && echo "Node.js version:" \
    && node --version \
    && echo "NPM version:" \
    && npm --version

# Next, copy the remaining files and directories with the source code.
# Since we do this after NPM install, quick build will be really fast
# for most source file changes.
COPY --chown=myuser . ./

# Run the image. If you know you won't need headful browsers,
# you can remove the XVFB start script for a micro perf gain.
CMD ./start_xvfb_and_run_cmd.sh && npm start --silent

Package version
3.5.4
Node.js version
18
Operating system
Linux
Apify platform

[X] Tick me if you encountered this issue on the Apify platform

I have tested this on the next release
No response
Other context
No response

This is caused by the header-generator from crawlee's dependencies. In the core, it's not a bug - there is very little data on Webkit usage on Linux (crawlee sets the fingerprint OS by your actual OS, which is Linux for Apify Actors).
However, I've just released<EMAIL_ADDRESS>(and<EMAIL_ADDRESS>), which try to relax some of the constraints when they encounter this error. This way, your fingerprint might not totally match the system setup, but the crawler run shouldn't end with an error.
Just keep in mind that if the fingerprint doesn't match your setup completely, you might start getting blocked more (the antibot services might pick up on this discrepancy).
@vladfrangu how do we release Docker images now? should I update the lockfile in Crawlee or?

Docker files get released beta wise on every commit to master and stable wise on every release of crawlee 👀
But it shouldn't matter, a clean lockfile should bump it manually

@barjin Thank you very much for the detailed explanation and quick turnaround. To understand the context: Within the latest update, the webkit-based actor will run smoothly on the Apify Platform but since the fingerprints do not perfectly match up with the OS, it might still cause some blockage. Is that correct?

@tugkan Yes, that's correct.
@vladfrangu The docker images take the repo root lockfile during publish, right? Or is this not necessary? I'm still slightly confused by our Docker pipeline :)

Docker images don't come with a lockfile by default, so it'll just probably install whatever matches semver ranges 👀

Hi @tugkan , just to reiterate - in the past week, I've updated the way the browser headers are generated - so now, you shouldn't be encountering the relax or change some of the requirements exception anymore (at the risk of some of the generated fingerprints not matching your environment fully).
You can still enable the old behaviour by adding the strict: true option to fingerprintGeneratorOptions - just beware that setting anything fingerprint related overrides Crawlee's attempts at matching the current OS / browser, so you have to do so yourself.
browserPoolOptions: {
      fingerprintOptions: {
          fingerprintGeneratorOptions:
+             strict: true,
              operatingSystems: ['linux'],
              browsers: ['safari']
          },
     },
},

To try those fixes out, it should be enough to simply rebuild your actor on Apify with the latest Crawlee version (3.5.5) and the latest Docker images.
I'll close this issue as solved now, but let us know in case of any problems. Thanks! :)

Hey @barjin ! Thank you very much for the response. I just bumped the version and deployed it on Apify with the headful webkit. But seems like there is another bug that occurred after the fix. The snippet is below. Can you please take a look? I was wondering if there is some other thing that got broken by the update.
WARN  PlaywrightCrawler: Reclaiming failed request back to the list or queue. TypeError: Cannot read properties of undefined (reading 'filter')
2023-10-02T18:49:39.942Z     at /home/myuser/node_modules/header-generator/header-generator.js:129:30
2023-10-02T18:49:39.950Z     at Array.reduce (<anonymous>)
2023-10-02T18:49:39.953Z     at FingerprintGenerator.getHeaders (/home/myuser/node_modules/header-generator/header-generator.js:121:133)
2023-10-02T18:49:39.956Z     at FingerprintGenerator.getHeaders (/home/myuser/node_modules/header-generator/header-generator.js:163:25)
2023-10-02T18:49:39.959Z     at FingerprintGenerator.getHeaders (/home/myuser/node_modules/header-generator/header-generator.js:163:25)
2023-10-02T18:49:39.961Z     at FingerprintGenerator.getHeaders (/home/myuser/node_modules/header-generator/header-generator.js:163:25)
2023-10-02T18:49:39.963Z     at FingerprintGenerator.getFingerprint (/home/myuser/node_modules/fingerprint-generator/fingerprint-generator.js:72:35)
2023-10-02T18:49:39.965Z     at /home/myuser/node_modules/@crawlee/browser-pool/fingerprinting/hooks.js:23:48
2023-10-02T18:49:39.967Z     at BrowserPool._executeHooks (/home/myuser/node_modules/@crawlee/browser-pool/browser-pool.js:549:19)
2023-10-02T18:49:39.969Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Thank you for your feedback @tugkan. This exact error has been fixed in the latest version of the header-generator yesterday - can you confirm you are running<EMAIL_ADDRESS>and not an older version? Thanks!

@barjin Wonderful news. I'll take a look and let you know the results. Also, a quick question to ask. We are keeping the versions without ^ in the package.json and this fix caused a problem on the Dataset.pushData. Currently, none of the actors we have, pushes any data into the Apify Platform and requires a version bump for each. Are there any workarounds regarding this point? We experienced that one more time in the past.


adds configurable polling count for message gathering

Pull Request Test Coverage Report for Build 160

50 of 64 (78.13%)  changed or added relevant lines in 3 files are covered.
22 unchanged lines in 1 file lost coverage.
Overall coverage increased (+4.2%) to 58.755%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

aws_message/sqs.py
15
21
71.43%

aws_message/gather.py
0
8
0.0%

Files with Coverage Reduction
New Missed Lines
%

aws_message/mock_sqs.py
22
0.0%

Totals

Change from base Build 155:
4.2%

Covered Lines:
265

Relevant Lines:
426

💛  - Coveralls


Convert notes queries to string interpolation

We're doing notes queries all wrong. Instead of having a separate column, let's use this :title: and :description: string interpolation syntax that we do here: https://github.com/andymeneely/vulnerability-history/blob/master/app/models/event.rb#L38-L42
This lets us embed notes details in the freetext using our own syntax. Maybe we can do something like this:
:notes~bounty: would translate to the notes column and bounty substring.
This lets us put lots of notes details into an event description all at once.

[x] Rip out notes queries column in schema.rb
[x] Rip out the if-statement and just do embed_details on these methods
[ ] Enhance embed_details with syntax like this: :notes~bounty: should pull from the notes query in title, description, etc.
[ ] Enhance embed_details with syntax like this: :notes~bounty_announced~date: should pull from the notes query in title, description, etc.

Use TDD for this. Write new unit tests in the model tests.

@andymeneely What exactly is meant by it should pull from notes query. Wasn't that ripped out in the schema?

It should pull from the notes field is what I meant. So that way you can pull things out of the notes hash and use it as part of your description, date, or title.

And that should be done in embed_details or in cve methods? I would have to play around with it if it should be done in embed details. Also should it have its own def note similar to title and description?

@andymeneely ^

Should be in embed_details. Although it's a bit more thorny than it looks. Might be better to put it in its own class so you can test it more easily.
This is a tricky one. Here's a unit test to specify what I mean:
Go into test/fixtures/events.yml and change custom_event_3 to:
custom_event_3:
  detail_type: Vulnerability
  detail: cve_2013_2878
  title_template: 'CWE Determined for :title:'
  description_template: 'CWE was :note~cwe:'

See that last line? That's got the note syntax we're looking for. Here's the test case I would expect in test/models/event_test.rb:
test 'event notes in description' do
    e = events(:custom_event_3)
    assert_equal('CWE was 119', e.description)
  end

Get that one to pass first. THEN start thinking about deeper accesses like this: :notes~a~b~c:. If you can't get that part immediately that's fine - we can iterate and improve if you get the above test case to pass.

@andymeneely For the portion of the parsing for  :notes~bounty_announced~date: is this for a structure like this:
notes:
(tab)bounty: 1000.0
(tab)(tab)bounty_announced: Mon Mar 9 15:32:34 2009 +0000
if so, it seems as though the yaml will not parse it. Not sure if this is a yaml bug or a bug on my end.

For our discussion tomorrow, I'm putting this little snippet to save it somewhere:
':notes~a~b~c:'.scan(/~(\w+)/).flatten


Block credential stealing from the Windows local security authority subsystem (lsass.exe)

What is the official test case / proof that lsass.exe credential stealing is protected (9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2) ?
we tried this on 1803 with both mimikatz and kekeo and nothing is protected here.

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

ID: f9de2e9a-c4c1-3763-6160-9427556291f1
Version Independent ID: 74160e2f-0f99-a37f-7123-81a31a6fab61
Content: Use Attack surface reduction rules to prevent malware infection
Content Source: windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-exploit-guard.md
Service: unspecified
Product: w10
GitHub Login: @andreabichsel
Microsoft Alias: v-anbic

@officedocsbot assign @mypil

@rrsit I know you asked this question quite some time ago, but did you test it with a Windows E5 license? Did you also have WD Antivirus enabled at the time of the test (and no other AV present on the machine)?
If the answer is yes to all the above questions, i would recommend to open a support ticket with Microsoft: https://support.microsoft.com/en-us/contactus/

@rrsit - We would like to follow up. Can you please respond to the query of VLG17? Thanks.

Hello,
this was quite some time ago, what i know for sure is that there was no other antivirus software present, this was defender only. we're happy to review this again, but it will take some time. i've tasked my coworker and will update this case with the results.

@tecxx thank you, it would be best to run the test again (with a Windows E5 license and WD Antivirus enabled).

@rrsit @tecxx - Thank you for submitting this feedback.
From our understanding, the issue you raised has been answered by VLG17. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


[WIP] A sketch of checkpointing normalisation

This attempts to address issue #235 where checkpointing does not work for "complex" parameters.
On some work for DESC I was encountering enough frustration that I sketched out the attached code which performs recursive normalisation on known datatypes for memoization purposes, and more aggressively informs the user (via exceptions) that unknown datatypes haven't been whitelisted.
Further workflow-specific handling for types can be added by importing parsl.dataflow.memoization and adding a type-specific implementation, as happens in parsl.dataflow.memoization.
Key ideas:

only known types can be used as parameters when using memoization
known types all have a defined identity function which knows how to give a reproducible bytestream for comparing for equality. implemented in id_for_memo
known basic types use the existing serialisation style
lists and dicts are recursively normalised - the key missing piece for fixing #235
new known types can be added either inside parsl source code or in workflow source code

One thing I'm concerned about is how this interacts with subclasses: normalising a dict doesn't necessarily mean a subclass of a dict (with other interesting fields) would normalise the same way.

I've also noticed that functions often serialize the same between runs but not always - for example in the presence of some source code modifications away from the function definition that I haven't entirely tracked down (perhaps the list of imports?)


CSS motion path Firefox 69

See https://trello.com/c/Ef3V38Yh/212-css-motion-path-fx-69 for original trello card.
Acceptance criteria

[ ] Implement offset-distance for motion path

[ ] Implement offset-rotate for motion path

[ ] Make offset-rotate animatable

I think this stuff is only enabled in Nightly, and hidden behind a pref in Beta/release — I've asked Boris for clarification on this in https://bugzilla.mozilla.org/show_bug.cgi?id=1429299#c14

Yes, for clarification, this stuff is only enabled in Nightly, and hidden behind the layout.css.motion-path.enabled pref in beta/release.
I've added BCD at https://github.com/mdn/browser-compat-data/pull/4708. Note sure if there is much mroe work to do on this.

I have gone on to make sure the rest of the documentation is as complete as it needs to be for now:

Filled in the landing page with a bit more detail: https://developer.mozilla.org/en-US/docs/Web/CSS/Motion_Path
Made sure the existing property pages are as complete as they can be for now. See https://developer.mozilla.org/en-US/docs/Web/CSS/Motion_Path#Reference
There are interactive examples missing from offset, offset-distance, and offset-rotate. I'm not that fussed about them for now because they are only supposrted by default one browser currently. We can add those later on.

I checked the mdn pages of offset-distance and offset-rotate, and they look good to me. Thanks for updating these and adding the examples.

And motion-path page as well. :)

@BorisChiou thanks for the review!


add Drone CI for the harvester-ui

need to add Drone CI for the harvester-ui

link to PR https://github.com/rancher/harvester-ui/pull/1

close as this is done in https://github.com/rancher/harvester-ui/


VXLAN UDP Port configuration support

This PR chnages allow user to configure VxLAN UDP
port number. By default we use 4789 port number. But this commit
will allow user to configure port number during swarm init.
VxLAN port can't be modified after swarm init.
Signed-off-by: selansen<EMAIL_ADDRESS>

Sorry just saw that is WIP

@fcrisciani , now it is ready for review. Pls provide your comments.

fixes https://github.com/moby/moby/issues/33416
replaces https://github.com/docker/libnetwork/pull/1431
engine changes are in https://github.com/moby/moby/pull/38102


move rate limiting logic to the MessageSchedulerLib

Separating robofleet client into a lib and a wrapper is nice, but things were a bit entangled with rate limiting. This moves all the rate limiting, scheduling, etc. logic into the lib side of things. However, I will point out this means we do pay the cost of encoding all the messages, even those that won't get sent quite yet because of rate limiting. I think this is ok because it's not too much cost, and also it allows us to queue up messages immediately, which helps in in case the rate limit timing is off from the publication timing in a way that would otherwise leave some dead space

This is connected to https://github.com/ut-amrl/robofleet_client_lib/pull/2


esp_http_client_perform never returns if the server does not send anything after connection (IDFGH-1132)

Development Kit:      none
Module or chip used:  ESP32-WROVER
IDF version: v3.2
Build System: Make
Compiler version: 1.22.0-80-g6c4433a
Operating System: Linux
Power Supply: External 3.3V

Problem Description
All the fields in http client is set and the esp_http_client_perform is called.
The connection is opened but the server does not respond to the device and esp_http_client_perform did not return.
Expected Behavior
After some time, it must return even if the function failed.
Actual Behavior
Infinite loop in the esp_http_client_perform function.
Steps to repropduce

Prepare a server which does not respond to any request but accepts tcp requests.
Send a request using esp_http_client_perform.

Edit: I need to add that the client is configured as blocking and as TCP connection, not as SSL.
Configuration struct is as follows:
esp_http_client_config_t httpConfig;
memset(&httpConfig, 0, sizeof(esp_http_client_config_t));
httpConfig.url = defaultURL;
httpConfig.method = HTTP_METHOD_PUT;
httpConfig.buffer_size = 8 * 1024;
httpConfig.disable_auto_redirect = false;
httpConfig.is_async = false;
httpConfig.max_redirection_count = 20;
httpConfig.port = 80;
httpConfig.timeout_ms = 5000;
httpConfig.transport_type = HTTP_TRANSPORT_OVER_TCP;
if(uploaderClient.initialize(uploaderClient_name, &httpConfig) != K_OK)
{
ESP_LOGE(TAG, "uploader client cannot be created!");
esp_restart();
}
if(esp_http_client_set_url(uploaderClient.client, uploadLocation) != ESP_OK ||
esp_http_client_set_header(uploaderClient.client, "header1", header1) != ESP_OK ||
esp_http_client_set_header(uploaderClient.client, "header2", header2) != ESP_OK ||
esp_http_client_set_post_field(uploaderClient.client, (char*)buffer, strlen(buffer)) != ESP_OK )
return;
if(esp_http_client_perform(uploaderClient.client) != ESP_OK ||
esp_http_client_get_status_code(uploaderClient.client) != 200}
return;
We can see HTTP_EVENT_ON_CONNECTED event. Then the code stops there and never logs, esp_http_client_perform does not return.
Thanks in advance.

According to the BugFix section of the IDF3.3Beta3, this problem may have been solved. Infinite loop on esp_http_client_fetch_headers may be the reason behind it. The test will be done after the official release of the 3.3.

@sysizlayan I tried to send a request from ESP32 HTTP Client to a HTTP server hosted on another ESP32 which does not respond to any request.
esp_http_client_perform returns with the following ERROR message:
HTTP_CLIENT: HTTP PUT request failed: ERROR
Can you please check once?
If it works fine, we can close this issue.

@sysizlayan Closing per above comment, please feel free to reopen if you observe any issues on your side.


Update cs0507.md

Summary
This doc only contains two examples, the "Example 3" was only the second part of Example 2
Fixes #Issue_Number (if available)

@dotnet-policy-service agree


Defining a key multiple times should be invalid as per spec.

This crate advertises as TOML v1.0.0-rc.1 compliant and the spec forbids defining a key multiple times however as of  v1.0.0-alpha.4, i can define multiple keys:
# taplo = "1.0.0-alpha.4"

const SOURCE: &str =
"ip = '<IP_ADDRESS>'
ip = 'xxx'

[secret]
github = 'github-xxxxxxxxxxxxxxxxx'
travis = 'travis-xxxxxxxxxxxxxxxxx'
azure = 'azure-xxxxxxxxxxxxxxxxx'";

let rect = taplo::parser::parse(SOURCE);

assert_eq!(rect.errors.len(), 1);

parse only parses the syntax, and thus only reports syntax errors. (e.g. missing =).
Other checks happen when a DOM is created, so a workflow should look like this:
    const SOURCE: &str =
    "ip = '<IP_ADDRESS>'
    ip = 'xxx'

    [secret]
    github = 'github-xxxxxxxxxxxxxxxxx'
    travis = 'travis-xxxxxxxxxxxxxxxxx'
    azure = 'azure-xxxxxxxxxxxxxxxxx'";

    let rect = crate::parser::parse(SOURCE);
    assert_eq!(rect.errors.len(), 0);

    let root = rect.into_dom();
    assert_eq!(root.errors().len(), 1);

I'll have to get to document the library eventually, so I'll keep this issue open as a reminder.

I've added documentation that covers this in 791e86d504105f6223fefc1077ae9b808477227a.


CIV-12812 Dashboard Notification Mediation Unsuccessful - Defendant

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-12812
Change description
Defendant dashboard notifications for Mediation Unsuccessful

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Minor point - on the ticket there's a full stop at the end of the link, but not in this PR.  I expect we're all being quite inconsistent with these but might be worth checking.


TILA-1983 | Prefill rervee info from profile

Change log

Add logic to fetch user info from profile
Use the logic in reservation create serializer for fetching prefill data.

Deployment reminder

[ ] PR requires deployment changes
[ ] Pipeline configuration change PR [link here]
[ ] Azure devops library updated if needed
[ ] Pipeline configuration change PR merged

Refs TILA-1983

Address reading needs the foreign address option as last resort:
address = self.vp_info.get("permanentForeignAddress", {})
if address:
	return {
		"postalCode": "",
		"address": address.get("streetAddress"),
		"city": "",
	}


Multi-Touch and Gesture Support

Touch Screens needs Multi-Touch support and Gestures
There is a need to use gestures on touch screen platforms. Multi-Touch input is required for that.
Get Native Input Touch Data from platform
With the planned Android, iOS and Ubuntu Touch support, there is a need to register and record multiple touch events, so that gestures like pinch zoom, palm swipe etc can be used, platform appropriately. I am guessing this should also extend to touch screen desktop.

Multi touch support is definitely a high priority feature for the mobile support.

From my research it seems that there is no way that we can avoid having to port a bunch of drivers, if we want complete support for Touch on Desktops as well, which is a pain.
This is list of Linux drivers for Touchscreen Devices.
It might be best/easiest to start with the Raspberry Pi Touchscreen port, I might be able to look at that in February.
I am guessing it will be easier on Android and iOS as the gesture recognition is supported natively.
The standard gestures of Ubuntu are listed here:
https://wiki.ubuntu.com/Multitouch/
Ubuntu Touch might be a different, I haven't been able to locate any info on it yet.


update for latest symfony

could you update it for latest symfony 4.1 and tcpdf 6.2.17?
also some non ASCII codes not show properly
also if I use
class PdfController extends AbstractController
is not working
it work only with
class PdfController extends Controller

checkout the latest version 4.x, if you're still on 1.x branch. 4.x works fine with symfony 4.0 and 4.1.
i just updated the docs for some symfony 4.x instructions.
there is no AbstractController in this bundle, you probably want to ask this on an other repository?