Upgrade to distroless envoy

Changes
Upgrade envoy to distroless-v1.27 for less vulnerabilities.
grype docker.io/envoyproxy/envoy:distroless-v1.27-latest
 ✔ Vulnerability DB                [no update available]
 ✔ Loaded image                                                                                index.docker.io/envoyproxy/envoy:distroless-v1.27-latest
 ✔ Parsed image                                                                                sha256:f41d403a28eef76aea46c78f4445851a097483bc0a87d1e21ff4bf339494b5dc
 ✔ Cataloged contents                                                                                ee5d42d10f744ff27bdc90decf1c21cc195f467815f71bbc8f0a5b271aef25b0
   ├── ✔ Packages                        [4 packages]
   ├── ✔ File digests                    [1,219 files]
   ├── ✔ File metadata                   [1,219 locations]
   └── ✔ Executables                     [274 executables]
 ✔ Scanned for vulnerabilities     [7 vulnerability matches]
   ├── by severity: 0 critical, 0 high, 0 medium, 0 low, 7 negligible
   └── by status:   0 fixed, 7 not-fixed, 0 ignored
NAME   INSTALLED       FIXED-IN  TYPE  VULNERABILITY     SEVERITY
libc6  2.36-9+deb12u7            deb   CVE-2019-9192     Negligible
libc6  2.36-9+deb12u7            deb   CVE-2019-1010025  Negligible
libc6  2.36-9+deb12u7            deb   CVE-2019-1010024  Negligible
libc6  2.36-9+deb12u7            deb   CVE-2019-1010023  Negligible
libc6  2.36-9+deb12u7            deb   CVE-2019-1010022  Negligible
libc6  2.36-9+deb12u7            deb   CVE-2018-20796    Negligible
libc6  2.36-9+deb12u7            deb   CVE-2010-4756     Negligible

Old envoy container.
$ grype docker.io/envoyproxy/envoy:v1.26-latest
 ✔ Vulnerability DB                [no update available]
 ✔ Loaded image                                                                                index.docker.io/envoyproxy/envoy:v1.26-latest
 ✔ Parsed image                                                                                sha256:f63d21feeb3ca857a72182892c6c14fd8ed75dc3871c57f4578b342e1409b64d
 ✔ Cataloged contents                                                                                264d816f68880c01a3daf9ec3b56e15723ddc0e952e8c623f42a2149ddae9c3f
   ├── ✔ Packages                        [95 packages]
   ├── ✔ File digests                    [2,127 files]
   ├── ✔ File metadata                   [2,127 locations]
   └── ✔ Executables                     [734 executables]
 ✔ Scanned for vulnerabilities     [47 vulnerability matches]
   ├── by severity: 0 critical, 0 high, 16 medium, 28 low, 3 negligible
   └── by status:   11 fixed, 36 not-fixed, 0 ignored
NAME          INSTALLED                 FIXED-IN            TYPE  VULNERABILITY   SEVERITY
coreutils     8.30-3ubuntu2                                 deb   CVE-2016-2781   Low
gcc-10-base   10.5.0-1ubuntu1~20.04                         deb   CVE-2023-4039   Medium
gpgv          2.2.19-3ubuntu2.2                             deb   CVE-2022-3219   Low
libc-bin      2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33602  Medium
libc-bin      2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33601  Medium
libc-bin      2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33600  Medium
libc-bin      2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33599  Medium
libc-bin      2.31-0ubuntu9.14          2.31-0ubuntu9.15    deb   CVE-2024-2961   Medium
libc-bin      2.31-0ubuntu9.14                              deb   CVE-2016-20013  Negligible
libc6         2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33602  Medium
libc6         2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33601  Medium
libc6         2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33600  Medium
libc6         2.31-0ubuntu9.14          2.31-0ubuntu9.16    deb   CVE-2024-33599  Medium
libc6         2.31-0ubuntu9.14          2.31-0ubuntu9.15    deb   CVE-2024-2961   Medium
libc6         2.31-0ubuntu9.14                              deb   CVE-2016-20013  Negligible
libgcc-s1     10.5.0-1ubuntu1~20.04                         deb   CVE-2023-4039   Medium
libgcrypt20   1.8.5-5ubuntu1.1                              deb   CVE-2024-2236   Medium
libgnutls30   3.6.13-2ubuntu1.10        3.6.13-2ubuntu1.11  deb   CVE-2024-28834  Medium
liblzma5      5.2.4-1ubuntu1.1                              deb   CVE-2020-22916  Medium
libncurses6   6.2-0ubuntu2.1                                deb   CVE-2023-50495  Low
libncurses6   6.2-0ubuntu2.1                                deb   CVE-2023-45918  Low
libncursesw6  6.2-0ubuntu2.1                                deb   CVE-2023-50495  Low
libncursesw6  6.2-0ubuntu2.1                                deb   CVE-2023-45918  Low
libpcre2-8-0  10.34-7ubuntu0.1                              deb   CVE-2022-41409  Low
libpcre3      2:8.39-12ubuntu0.1                            deb   CVE-2017-11164  Negligible
libssl1.1     1.1.1f-1ubuntu2.22                            deb   CVE-2024-5535   Low
libssl1.1     1.1.1f-1ubuntu2.22                            deb   CVE-2024-4741   Low
libssl1.1     1.1.1f-1ubuntu2.22                            deb   CVE-2024-2511   Low
libstdc++6    10.5.0-1ubuntu1~20.04                         deb   CVE-2023-4039   Medium
libsystemd0   245.4-4ubuntu3.23                             deb   CVE-2023-7008   Low
libsystemd0   245.4-4ubuntu3.23                             deb   CVE-2023-26604  Low
libtasn1-6    4.16.0-2                                      deb   CVE-2021-46848  Low
libtinfo6     6.2-0ubuntu2.1                                deb   CVE-2023-50495  Low
libtinfo6     6.2-0ubuntu2.1                                deb   CVE-2023-45918  Low
libudev1      245.4-4ubuntu3.23                             deb   CVE-2023-7008   Low
libudev1      245.4-4ubuntu3.23                             deb   CVE-2023-26604  Low
login         1:4.8.1-1ubuntu<IP_ADDRESS>                      deb   CVE-2023-29383  Low
login         1:4.8.1-1ubuntu<IP_ADDRESS>                      deb   CVE-2013-4235   Low
ncurses-base  6.2-0ubuntu2.1                                deb   CVE-2023-50495  Low
ncurses-base  6.2-0ubuntu2.1                                deb   CVE-2023-45918  Low
ncurses-bin   6.2-0ubuntu2.1                                deb   CVE-2023-50495  Low
ncurses-bin   6.2-0ubuntu2.1                                deb   CVE-2023-45918  Low
openssl       1.1.1f-1ubuntu2.22                            deb   CVE-2024-5535   Low
openssl       1.1.1f-1ubuntu2.22                            deb   CVE-2024-4741   Low
openssl       1.1.1f-1ubuntu2.22                            deb   CVE-2024-2511   Low
passwd        1:4.8.1-1ubuntu<IP_ADDRESS>                      deb   CVE-2023-29383  Low
passwd        1:4.8.1-1ubuntu<IP_ADDRESS>                      deb   CVE-2013-4235   Low

/kind enhancement

/ok-to-test

/test integration-tests_net-kourier_main

Thanks for reviewing @skonto.
I've added 1.31  and the other versions between 1.26 for test coverage.
If it looks good, I am ready for integration test approval.

Shutdown checks fail, I guess we dont have curl in distroless.

Hm, building our own command seems a lot of work for this, also adding curl would mean we have to rebuild every new version of envoy docker images (we can’t do that for patches and such). Not sure if having distroless is worth all that effort.
+1 for the version bump without it, I’ll do a PR for that.

Thanks y'all.  I am happy with the updated envoy version to the latest and understand the curl entrypoint issue.
I am closing this issue.


Fix scope client reference on copy/fork

closing this in favor of one against master
https://github.com/getsentry/sentry-python/pull/3857


Print Dialog Shown Off Screen

Windows Terminal version (or Windows build number)
Windows Terminal Version: 1.9.1942.0
Other Software
vim 8.2 outside WSL
Steps to reproduce

Install Windows Terminal 1.9 and Vim 8.2 on a new Windows 10 box.
Execute "C:\Program Files (x86)\Vim\vim82\vim.exe"
Print via :hardcopy

Expected Behavior
I expect the print dialog to be centered on the screen or on the shell like console host.
Actual Behavior
The print dialog is positioned past the top-left of the screen.
To bring the dialog into view:

Click to focus on the dialog.
Press Alt + Space
Press m
Press Up Arrow to attach the dialog to the mouse cursor.
Move the mouse cursor to drag the dialog into view.

I'm gonna guess that this is /dup #2988. This just has all the same hallmarks of that bug.

I don't think this is a duplicate. I'm talking about x,y not z. When I type start . I don't have the same problem as reported in 2988. My issue reproduces today.

Okay yea, I see how that was confusing. Lemme try to explain better:
I'm guessing the root cause of your issue here is that vim can't reliably find the HWND of the Terminal. It probably wants to display the print dialog relative to the window that it's running in. I'm guessing that they use GetConsoleWindow for that value. However, when running in the Terminal, that value is a garbage value. So instead of it opening near the Terminal, it just defaults to (some location).
The start . repro for #2988 is intermittent, but shares the same root cause.

Okay, even after investigating down all the other leads in #2988, :hardcopy is still busted. I'm quite confident that vim.exe is getting the actual position of the console window here to try and center the print dialog on top of it. Problem is, GetConsoleWindow in any ConPTY session (read: terminal) is going to have a 0x0 sized window as the result of that API.
This is gonna require some changes on the part of vim.exe. They'll need to do some combo of

maybe use GetAncestor() to try and find the Terminal's HWND as a ROOTOWNER of the console HWND
Before 1.14, detect that the HWND that's returned is totally transparent (WS_TRANSPARENT), or 0x0 and then just display the print dialog in the center of the screen

So this is no longer a duplicate issue, it's actually something we can't solve. Sorry!

Thanks for checking into this.


Record Receipt for Dist List Settling

When Dist Lists get settled, the output of these transactions should be:

signed / saved to be used as "proof" that a payment happened
paid dids should have negative weights added to the pool to record that the new weight for this did is 0. This would allow the same pool to be re-used for future transactions.
(side effect of above) Any id that was below the minimum threshold would be carried-over to the next settlement period where it may have the opportunity to get paid again.

Rather than signing this, it stores a receipt struct including a transaction:
{
  "poolName": "april-20-2023",
  "pool": {
    "CWHoduMvxnkNYhrheqswfs": {
      "identifier"<EMAIL_ADDRESS>      "id": "CWHoduMvxnkNYhrheqswfs",
      "ts": "2023-04-20T13:36:33Z",
      "weight": "1",
      "traceId": "CWHodpXjgL8gxHusjJKYXF"
    },
    "H2hBKrcmM5SNstY8EJHq2B": {
      "identifier"<EMAIL_ADDRESS>      "weight": "-1",
      "id": "H2hBKrcmM5SNstY8EJHq2B",
      "traceId": "GSvRodGLPW6NbAEoEjXDbZ",
      "ts": "2023-04-20T13:37:34Z",
      "receipt": {
        "type": "direct",
        "amount": "0.039988",
        "address": "rEt8yCY2rcbY94vyGrUDUAiRfea1cncpYU",
        "tx": "9F46FCB65A01EE458DA5EA8C057F7CF05B2532D8FD6A30462C053D599C33B261"
      }
    }
  }
}

This should probably have more context on what network was used for setling, etc.
(setling -> we intentionally are spelling it that way)

This was fixed as part of https://github.com/LoremLabs/kudos/pull/17


Registry for grid, topography, region mask files

It appears that all grid, topography, region mask files used in regrid.py are hosted in various locations on Glade.  I was wondering if it would be feasible to have some kind of central registry for these? How big can these files get? Can we curate them in a public place (GitHub repo)?
https://github.com/NCAR/esmlab/blob/538185f5f0dd75f243f39008da947a4a14d707c1/esmlab/grid_definitions.yml#L14-L16
https://github.com/NCAR/esmlab/blob/538185f5f0dd75f243f39008da947a4a14d707c1/esmlab/grid_definitions.yml#L149
Cc @matt-long

@andersy005, those particular files are binary files that the model reads and are in a version control system associated with CESM.
I think a higher priority would be to curate the grid files on which the esmlab regridding workflow depends. These can be big, however, so not obvious how to proceed.
At this point, I don't believe grid_definitions.yml is really used by esmlab at all. I had thought we might use this to store "known grids"...but we currently just check for the grid file.

the model reads and are in a version control system associated with CESM.

Are these publicly accessible (e.g: GitHub)??

To be clear, the POP grids are in a repo...the T62 grid is not.
They are in an Subversion repo:
https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/ocn/pop

Maybe grid files could be handled in a manner similar to how cartopy manages remote datasets, from Natural Earth, for instance.
https://github.com/SciTools/cartopy/blob/master/tools/feature_download.py
https://github.com/SciTools/cartopy/blob/master/lib/cartopy/io/__init__.py

To be clear, the POP grids are in a repo...the T62 grid is not.

T62 grid is also in the svn repo (Along with some other shared grids): https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/share/scripgrids/


Clean up fan light accessory

Hi @iRayanKhan,
I arranged a few changes which work on my setup. They should be compatible with the existing config. I have put the reasons for the changes in the commit messages. Let me know what you think Cheers.

Thank you!


Update pkinit code and place in own files

certipy auth sometimes fails with the following error message:
"KRB_AP_ERR_BAD_INTEGRITY(Integrity check on decrypted field failed)

I suspect that this happens with newer domain controllers on which a particular patch is installed, but could not confirm. The PKINITtools by @_dirkjan would succeed, however. I updated the code and now it works. While I was at it, I placed Dirk-Jan's code into its own files to make it clearer where it comes from. It now also contains some more copyright notices which should be more compliant with the respective MIT licenses, even though it might still not be fully compliant.
Ideally, Dirk-Jan will package PKINITtools and publish it on PyPI so we can simply import it instead of having to copy it. I had to change one line in myPKINIT.decrypt_asrep(), though, to expose the AS-REP encryption key.
Works for me, but please test thoroughly before merging.

This Twitter thread assisted with a temporary workaround: https://twitter.com/AndrewOliveau/status/1599906851016933376
A fix via Certipy would be great though!

Thank you for you contribution. However, it was just a matter of a small patch in the code to pack the data correctly. I'm still not sure what caused this issue, but I went from marshalling with pyasn1 to asn1crypto in the PKINIT request.

It has been fixed in 4.1.0


fix(fetch): relative locations redirect

Should we add a comment to explain why we use request.url as a base?

You mean like this?
https://github.com/nodejs/undici/blob/a163e7f7f80d42522f2b0c602777b45c45560d13/lib/core/util.js#L223

Thanks! Yes. Still not sure

Yes, please

Released: v0.35.1 🎉
This has been released in v0.35.1!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


openssh: fix static build

This pull requests fixes static build of openssh and its dependency,
keyutils:
$ nix-build -A pkgsStatic.openssh

It seems that this is symptom of more general problem: if library "foo"
depends on library "bar", then to link dynamically program that uses
library "foo" it is enough to pass "-lfoo" to compiler, but it is
necessary to pass "-lfoo -lbar" (in that order) to compiler to link it
statically.
Maybe proper fix would be to add -l{bar} into NIX_LDFLAGS for every
{bar} in build closure when static build is requested
(stdenv.hostPlatform.isStatic)?

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

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

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

@KAction You'll have to base the PR against staging because it's a mass rebuild (you can do it by rebasing with git and then using Github's Edit button at the top).

@nh2 Rebased on staging, @FRidh changes target branch for me.

It would be great to get this merged!

It would be great to get this merged!

I just replied https://github.com/NixOS/nixpkgs/pull/100906#discussion_r530677030

@nh2 Sorry for confusion. I believe it is not ready for merging.

This break cross-compilation because krb5-config gets taken from the build platform package. *-config scripts are generally problematic for cross-compilation, but in this case it should work if we add host platform kerberos.dev to nativeBuildInputs, or just manually add krb5-config to PATH. This works because krb5-config is just a shell script.


fix: use 1px check for layout rect

https://github.com/popperjs/popper-core/issues/1223
@mkrds

@atomiks I've tested it locally and it looks like it has fixed the issue :)


Margin and Spacing are missing on TMX load

Margin and Spacing are missing in the dictionary when loading from TMX file

@Urthstripe29 The margin and spacing are in the dictionary for me. They are a part of each tileset. Can you reproduce a dictionary without them in it?

Added some margin and spacing to the tilesets in SampleMap0 and they are working. I'll look into this more if you can provide a sample project where it's not working.

Issue wasn't actually spacing. the width/height was flipped. Fixed on development branch.


Update the Readme file

Examples:

Dryrun command
Cronjob
Configs

You could update that. But we have other things that need to be updated as well. I can take care of the rest.

Cool, I updated the cloning command on my machine. It should update when I push updates for #1437

Cool, I updated the cloning command on my machine. It should update when I push updates for #1437

@sosa-e Thank you! It will be better to have independent changes in separate pull requests.


Team section

We can add a team section in the navbar. That will consists of team of the project including its photo and social media handle links..

we can add this in the navbar

We can add a team section in the navbar. That will consists of team of the project including its photo and social media handle links..

we already have a contributors page. where we show all contributors list.

okay


Rewrite namespace field in HTTPProxy Spec to the name of vcluster host namespace

HTTPProxy permits the splitting of a system’s configuration into separate HTTPProxy instances using inclusion. Inclusion, as the name implies, allows for one HTTPProxy object to be included in another. Importantly, the included HTTPProxy objects do not have to be in the same namespace, they can be referenced in the root HTTPProxy by specifying their name and the namespace to which they belong.
spec:
  virtualhost:
    fqdn: sachinlobo.io
  includes:
    - name: httpproxy-nginx
      namespace: nginx
    - name: httpproxy-apache
      namespace: apache

With this PR, when the root Proxy is synced to the host cluster, the namespace field is rewritten to the name of the vcluster host namespace, since all resources created inside the vcluster belong to this namespace on the host cluster.
Additionally, the name field also needs to be rewritten appropriately taking a hint from the namespace field. Currently, this gets rewritten as 'httpproxy-nginx-x-default-x-vcluster' instead of 'httpproxy-nginx-x-nginx-x-vcluster'. This is not part of the current PR and needs to be worked upon.

@neogopher thanks for the PR! In general I like the idea, however the problem here is that the rewritten name depends on the namespace, so for example:
name: test
namespace: test

rewrites to test-x-test-x-vcluster, while
name: test
namespace: other

rewrites to test-x-other-vcluster.
So I guess for this use case we don't need an extra patch, rather we modify the existing rewriteName type to also take a namespacePath field:
patches:
- op: rewriteName
  path: spec.includes..
  namePath: name # sub path within spec.includes
  namespacePath: namespace # sub path within spec.includes

And then you would replace both fields name and namespace.

Thanks for the feedback, @FabianKramm . It makes sense to do it this way.
I have pushed another commit to the PR to reuse existing rewriteName Type for supporting both the translations in a single patch operation.
Have also added unit tests to cover all the probable ways in which these fields could be supplied.
Sequence Node
spec:
  includes:
    - name: name1
      ns: ns1
    - name: name2
      ns: ns2

Mapping Node
spec:
  includes:
    name: name1
    ns: ns1

spec:
  includes:
    names:
      - name: name1
      - name: name2
    ns: ns1


feat(linter)!: parse and display syntax errors for regular expressions

cc @leaysgur shipping to production!
This is marked as breaking change because there may be false positives.

NOTE: As I commented somewhere (sorry, I forgot), this means that invalid regexp literal will be reported in the parser stage.
Still some lint rules like eslint/no-invalid-regex can report error for regexp constructor usage, but not for literal(= never reports).

It conforms to the spec if the regex parser throws a syntax error for /regex/ syntax, everything else should go into a linter 😅

I also think it is natural. Early errors are good. 🙂↕


Update to 18.0

Oops, sorry. I guess I messed up with the pull request feature of GitHib and should just keep things in my fork. Thank you for pointing out.

lol what a PR!
Side note: There is really no need for this code anymore...
Now it's much easier to use https://github.com/arkadiyt/protodump on the ProPresenter binaries!


Update issue templates

Adds issue templates for bugs and feature requests.
Refs:

#19

Thanks for reviewing @jspaaks :cherries:


PBL-32223 Move default templates to SDK

@Katharine

This looks pretty reasonable to me, apparently-stray import aside. :+1:


DebianPackage version method always fails when package is not installed

Hello,
I apologize for not attaching this to #321 but this method inside of DebianPackage also looks like it suffers from the same problem as is_installed did.  If the package is not installed this will fail every time with an AssertionError.
https://github.com/philpep/testinfra/blob/b47c3b181dc445e4661876e909050cc4394b93b1/testinfra/modules/package.py#L99-L104
I wonder if we can apply similar fix for is_installed to version?
    @property
    def version(self):
        result = self.run_test("dpkg-query -f '${Status} ${Version}' -W %s" % (self.name))
        assert result.rc == 0, 'The package "%s" is not installed'.format(self.name)
        out = result.stdout.strip().split()
        if out[0].lower() in ["install", "hold"]:
            return out[3]

        # If we get here then None is returned, should we raise an error?  I feel like we should raise an error that the version cannot be determined.

Hi, thanks for reporting!
I think this isn't a bug since this already fail with an assertion error that say unexpected return code 3 while running dpkg-query with stderr of dpkg-query displayed as dpkg-query: no packages found matching ....
However in some cases (I guess for packages that where installed but then uninstalled), dpkg-query can exit with a return code 0 and unknown ok not-installed as stdout, so I this case we return None and I also think we should raise instead.


⚠ Fetchers has degraded performance

In 1b0f3e4, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 430 ms

Resolved: Fetchers performance has improved in 20e8f2f.


Cd856 action with provideriface

This pull request includes the implementation of the already recognized IMPORT CATALOG sentence for the C* connector.
It also provides with interfaces and examples for new implementations of tables and catalogs imports from any compatible connector. Any new relation being able of exploring datasources schemes should implement the TableInventory interface.

+1

I'd create a temporary table using catalog.table for testing to avoid the double highschool.students count
Some doc with the new grammar would be great.
I'd replace catalog with tables both in the logical plan and in the parser

+1


Adding missing requirement to requirements.txt

Proposed changes
Tiny tweak adding openai's tiktoken which seems to be required to run qa.py script

thanks!


Pivot table V2 not formating timestamp

In Pivot Table v1, TIMESTAMP columns are nicely displayed as dates.
In v2 : the long value is displayed as-is.
Expected results
Having timestamp displayed as human readable dates.
Actual results
long numerical value is displayed
Screenshots
The created_at value in this example is a timestamp.
Pivot V1 :

Pivot V2 :

Environment
(please complete the following information):

superset version:  Superset 1.2.0  (note : its the RC2)
python version: Python 3.7.9
node.js version: not present inside container

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Done by https://github.com/apache-superset/superset-ui/pull/1217


Add support for GNSS location

Allow user to enable / disable GNSS location. This may be useful for the Solar Thingy in case the device is outdoors.

[x] show GNSS location on map

Fixed via https://github.com/hello-nrfcloud/web/commit/c830f2fb40c02613db7c46e5a89889735d32534e


The StackOverflow exception is raised if Razor view contains a generic object that nests a heirarchy of generic types

Hi,
I've created the following hierarchy of generic classes:
public class Builder<TItem> : BuilderBaseEx<Builder<TItem>> {
	public Builder<TItem> SomeMethod(object arg) {
		return this;
	}
}

public class BuilderBaseEx<T> : BuilderBase<T> where T: BuilderBaseEx<T> { }

public class BuilderBase<T> : IHtmlContent where T : BuilderBase<T> {
	public void WriteTo(TextWriter writer, HtmlEncoder encoder) {
		writer.Write("Foo");
	}
}

When I call the SomeMethod method in a View of ASP.NET Core 2.0:
@(new Builder<object>().SomeMethod(ViewBag.SomeProperty))
the StackOverflowException is raised. Note that the exception occurs only when I send a dynamic type object to the SomeMethod. If I a send non-dynamic type object, no error occurs.

This is a C# behavior, not Razor. I'd recommend filing your issue over in the https://github.com/dotnet/Roslyn repo to get more feedback.


Random README stuff (mostly custom card)

Fixes #125

@KTibow,
I think that with last release I generated some work for you😊.
I changed names for many attributes in washer, dryer and dishwasher, this could require some review in your documentation.
Please let me know if you need more details...

I don't have a dishwasher, but I'll update now.


Enhance chart with local SF analysis to show good/best/brilliant moves

Use eval api and local SF to fill in the missing info from the server analysis.

show good move when max 0.25 winning changes shift from best move

Win% = 50 + 50 * (2 / (1 + exp(-0.00368208 * centipawns)) - 1)

show best move star emoji if best move

maybe with a little number to show depth?

show brilliant move where a move was both interesting and good

depending on https://github.com/Siderite/lichessTools/issues/681

Partially implemented in v2.3.109

Implemented in v2.3.127


Add "go generate" instructions to documentation

With Go 1.4 out, we can use one of the new features "go generate" - this seems like a great fit for ffjson.
Actually it is extremely easy to add ffjson generation. In your files you would like to have generated, add the following line:
//go:generate ffjson $GOFILE

To re-generate ffjson for all files with the tag, simply execute:
go generate

To generate for the current package and all sub-packages, use:
go generate ./...

Added in PR #96


"Object Closed" and no clue

Hi
Continuing with https://github.com/cwzx/nngpp/issues/10#
I had similar issue, as well, using SWIG to interface some socket management functions like the following:
static nng::socket_view getIpcIndexSocket()
{
	std::string sLane = "ipc:///aBridgeIndex";
	nng::socket_view _socket(nng::survey::open());
	// nng::set_opt_recv_timeout(_socket, 1000);

	_socket.dial(sLane.c_str());

	std::cout << "ipc index socket open" << std::endl;

	return _socket;
}

And the Swig interface file (.i) declares:
nng::socket_view getIpcIndexSocket();

It compiles great now, but when importing the generated (python in this case) module, running that method throws an nng::exception:
terminate called after throwing an instance of 'nng::exception'
  what():  Object closed

right when the _socket.dial(...) method is called.
Any clue about what's wrong with the code? There is nothing else going on in the Swig side, this is just a proof of concept, only method called.
Thanks
Originally posted by @webpolis in https://github.com/cwzx/nngpp/issues/10#issuecomment-544793162

nng::survey::open() returns an nng::socket object, which owns the socket. This means when the socket object is destroyed, the underlying socket is closed.
In your first example the socket object was destroyed at the end of the same line on which it was created.
The normal way to write this function is:
static nng::socket getIpcIndexSocket()
{
	nng::socket sock = nng::survey::open();
	sock.dial("ipc:///aBridgeIndex");
	return sock;
}

which transfers the ownership out of the function to the caller.
However, SWIG does not properly support move semantics (see here), so this will not compile.
As a result you will not be able to use the RAII classes such as nng::socket across the boundary.
The workaround is to release the ownership and use the non-owning views instead:
static nng::socket_view getIpcIndexSocket()
{
	nng::socket sock = nng::survey::open();
	sock.dial("ipc:///aBridgeIndex");
	return sock.release();
}

The view classes have all of the same functionality, but no ownership, so the socket will persist until it is explicitly closed.
To close a socket manually, you can put it back into an nng::socket and allow it to be destroyed:
static void closeSocket(nng::socket_view sv)
{
	nng::socket sock(sv.get());
}

Amazing explanation, thank you. It provides some enlightenment considering
I haven't used C++ for years.
I had found an alternate way to solve this a short while after I posted
that. My solution looks like:
nng::socket&& _socket = nng::respond::open();

_socket.dial(addr);

_indexSocket = std::move(_socket)

That _indexSocket is a private member of the exported class via Swig.
Do you see anything out of place? It works pretty well, even under
stressful tests.
Greetings.
Nicolas
On Thu, Oct 24, 2019, 7:18 PM Chris Welshman<EMAIL_ADDRESS>wrote:

nng::survey::open() returns an nng::socket object, which owns the
socket. This means when the socket object is destroyed, the underlying
socket is closed.
In your first example the socket object was destroyed at the end of the
same line on which it was created.
The normal way to write this function is:
static nng::socket getIpcIndexSocket()
{
nng::socket sock = nng::survey::open();
sock.dial("ipc:///aBridgeIndex");
return sock;
}
which transfers the ownership out of the function to the caller.
However, SWIG does not properly support move semantics (see here
http://email.arpado.site/c/eJxFjk-PgjAQxT8NHE3_TMUeeigqKVGJboQQbgUr1EAgFpfdb79dLyYvM28m-eW9m9AYmgiHVmylOjBGYVMzrvmpGZaRfJdF1NHxx7ilQsmDOXk84-mKqhLyS0DiSwBo0LZfte_ZjEPYCWSwIXfgvAbNMOLorg0mBoP_s5pFYS-6eZ5cQGVAEq_Wzt2r_qf94RbbfpZ17mWcNxgBhE_xNFP_64OlTBOm0lzmkqRVcSXHZHdWGS3Z1zreF3GmVAx0m6mTb_iGVp-UP5H8Spk), so this will not compile.
As a result you will not be able to use the RAII classes such as
nng::socket across the boundary.
The workaround is to release the ownership and use the non-owning views
instead:
static nng::socket_view getIpcIndexSocket()
{
nng::socket sock = nng::survey::open();
sock.dial("ipc:///aBridgeIndex");
return sock.release();
}
The view classes have all of the same functionality, but no ownership, so
the socket will persist until it is explicitly closed.
To close a socket manually, you can put it back into an nng::socket and
allow it to be destroyed:
static void closeSocket(nng::socket_view sv)
{
nng::socket sock(sv.get());
}
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
http://email.arpado.site/c/eJxFUE1zgjAQ_TV4q0OyCdQDBxAxKARRDMilgxiVVoERrLa_vlEPndnZj3n7Zt--nVUgUppoUFljm80pBfK-paNiFJbnW4O_M2EeobnL7pbr3ift7GCB2kTPM7KONezEGtHPRXUaHp65bM6Do6UXJpKlvitBJ7iQprEvRrAnJiCCjQKjwck69n3baWBr2FNxqPrjdftgq6G8_d5VqetD26padd1VdqpBSANPPs58dM31UkoN3Lrpq31VFn3V1GrHeMF98yVrhdq271E2I9RNqRM5kArmziKIY59zx6Zj7q1CMnPnHp7gzQYWXKTpHJJ1QDFbEdcTy0k2JSBC4aQGBDwUGZvNE5fTNMV5EEXLRbrKp9FkPE1if6NheIpVb5xl3b9RYiBM3-locLEusj39KL9ekvy1vbaxn4sEB567YBwyujSciXA4Yw6BMWehMvZJGv6b8wcLY4L5,
or unsubscribe
http://email.arpado.site/c/eJxFj8lugzAARL8Gbo3A2CwHDoYEmSRY0ACl3IwxwRWbWJr270vTQ6XRSDPSk2Zql-mQW7oqXR-TC0IGtCvkMCfi_WMEn0Vutcb4JZZHqQUfaMHXWJ9SrSxglijASxSo9Ux2h_vT-dirrVtrTV0Lm0GumbaAhskbBpGFHCBqq7GE2rntuk6LYmAFBLvucm236pfewzCuspGcrXIclj1vw7JVC59lJV7YtrZ7hXEYIHKO4rT0o5hgQt7eLT9NkpBSD1OfBrcIno-XAJwSdXZnMXXf-9g_LMxwhkFY5im4BseYUKNAr6Z3yj1KiAcNn5Jof_WEDv_LfgCr3lxS
.

To unsubscribe click: http://email.arpado.site/u/eJwdzcsOQ0AAQNGvYSnzLBazGFoZaYk2JWLHPNAQolrt37exubuTq1gNiXSh3bOQizOlmHgN9Ws_keM2oXdZuB2ePvq5VSB60Ce_ZHC-g6ok-dVCwdUiYKz7wWn3ymm0O6YUMsAoLWXTSG2IhwmByHiGQgmU1vbCFj0P37_nPI6oiHOecxRXxR1domMmUlzS2yE4FUEqREBwmIrkP9qR0_Zr92r21cosxH-TATtM

Amazing explanation, thank you. It provides some enlightenment considering I haven't used C++ for years. I had found an alternate way to solve this a short while after I posted
that. My solution looks like:
nng::socket&& _socket = nng::respond::open();
_socket.dial(addr);
_indexSocket = std::move(_socket)

That _indexSocket is a private member of the exported class via Swig.
Do you see anything out of place? It works pretty well, even under
stressful tests.
Greetings.
Nicolas


Return empty value on error, not "Element not found"

When an element is not present or empty, please return an empty string and not the actual error text.
Given the yaml
version:
lab: 1.0.0
dev:
I would like  both   niet version.dev   and  niet version.prod   to simply return an empty string.
The documentation gives a  'deal with errors' example but does that work ?

@fvant thanks for this issue.
Yep "deal with errors" example works!
I want to add an command line option that allow you to return empty string when an element is not present only (key not found).
When the key exist and the value are equal to empty then we will just return an empty value.

Fixed in the development version.
It will be available on pypi inside the version 1.4.0 when we publish this version, that is to say, as soon as possible.
Example of use:
```sh
$ echo '{"foo": "bar", "fizz": {"buzz": ["1", "2", "3"]}}' | niet fizz.gogo --silent # with silent mode
$ echo $?
1
$ echo '{"foo": "bar", "fizz": {"buzz": ["1", "2", "3"]}}' | niet fizz.gogo # without silent mode
Element not found: fizz.gogo
$ echo $?
1

Have fun!

Well! Now Available on niet 1.4.0
This feature is now available on pypi!
You can get it by updating niet:
pip install -U niet

Or by using the version 1.4.0:
pip install niet==1.4.0


[BUG] AttributeError in mlx.core.conj and mlx.core.conjugate functions

Describe the bug
While using the mlx.core.conj and mlx.core.conjugate functions, I encountered the following errors:
AttributeError: module 'mlx.core' has no attribute 'conj'
AttributeError: module 'mlx.core' has no attribute 'conjugate'
To Reproduce
Include code snippet
import mlx.core as mx
result = mx.conjugate(mx.array([1j,2j,3]))

Expected behavior
The function should return the conjugate of the given input without any errors.
Desktop (please complete the following information):

OS Version: [e.g. MacOS 14.4]
Version [e.g. 0.13.0]

Additional context
I have verified that I have the latest version of the mlx package installed. Please let me know if there are any information I can provide to help diagnose the issue.

The conjugate function is in main but not distributed in the latext MLX PyPI version (0.13.0). It will be in 0.14.0,  but if you need it sooner you can build from source

Note we'll probably do a 0.14 (or maybe 0.13.1) tomorrow, so it won't be too long.

Thanks!


Fix typo in comment in a code snippet

URL to the relevant documentation
Comment should says using the estimator
https://github.com/Qiskit/documentation/blob/9256be30c4b34f86ed87d556c4c4868915c76ee0/docs/guides/q-ctrl-performance-management.ipynb#L216
Select all that apply

[x] typo
[ ] code bug
[ ] out-of-date content
[ ] broken link
[ ] other

Describe the fix.
Modify sampler by estimator

Thank you for reporting! Will be closed by https://github.com/Qiskit/documentation/pull/2458


Integrate CompatPowerShellGet into v3

Summary of the new feature / enhancement
Integrate the compatibility layer into v3 so that users can continue to use existing cmdlets
Proposed technical implementation details (optional)
No response

That seems like it will be confusing having the v2 and v3 cmdlets side by side. What is the plan to phase out v2 cmdlet names?

Spoke to @SydneyhSmith during summit. Her plan is to integrate the CompatPowerShellGet in PowerShellGet v3 module and NOT have PowerShellGet v3 have a required dependency on CompatPowerShellGet.
My thoughts on this are:

When and how will the old cmdlets be deprecated and removed or will they stay around forever? For example, GA in 7.4 and removed in 7.5.
This will cause confusion for new and existing users by having the old and new cmdlets shipped in the same module. You'll get the question when should I use Install-Module and when do I use Install-PSResource.
There should be a way to remove/disable/hide the old cmdlets for users and organizations that have migrated to the new cmdlets.

To summarize if you have to have the old cmdlets built-in PowerShell or available on PowerShell v3 upgrade so it does not break CI then one of two things should be implemented.

Have PowerShellGet v3 have a required dependency on CompatPowerShellGet. This is good because it doesn't pollute the Get-Command -Module PowerShellGet output with deprecated cmdlets.
If you cannot or will not have the old cmdlets shipped via required dependency then, there should be a way to disable/hide the old cmdlets.

@SydneyhSmith it may be helpful for the team to put the design on the issue before implementation so the community can provide feedback before work has started.

We have discussed this issue at length internally, and plan to discuss this issue more tomorrow but I wanted to summarize some of the discussion that has occurred so far and provide an update as to options we are considering.
Not breaking CI/CD (and automation scenarios generally) on day 1 is a goal of ours which left us with three primary options:

Ship compat as a part of PowerShellGet
Ship compat as a dependency of PowerShellGet
Rename compat to be PowerShellGet and then take a dependency on v3 which is renamed as PSResourceGet

Initially we leaned towards option 2 (ship compat as a dependency of PowerShellGet) however this breaks anyone who uses fully qualified names, through our searches on GitHub this includes a lot of automation scenarios. This alone essentially eliminated option 2 for us as not breaking CI/CD was a primary motivator for including compat. Some other factors we have considered:
•	We are leaning towards supporting v2 syntax for the foreseeable future. We want to have an ability of removing it though should the time come that it is no longer needed.
•	We view supporting v2 syntax as a compatibility feature, not a place we would continue to make feature investments—future feature investments such as installation of arbitrary nupkgs would only come to Install-PSResource
•	Collecting telemetry on the Gallery side will enable us to know when it may be appropriate to deprecate v2 cmdlets, but this is not something we expect to do over the short term
•	Need to think about what will be preferred approach for going into Windows PowerShell in the future to replace PSGet v<IP_ADDRESS>
•	We should make changes to user agent header in v3 for collecting telemetry on Gallery side. Can we do something to find out if it was invoked from compat proxy?
•	There are concerns with marketing of "PSResourceGet", would it be considered a subset or inferior to the "real" PowerShellGet. Would moving people for PSGet to PSResourceGet be difficult?
•	Top priority should be making adoption of PSGetV3 as easy and seamless as possible.
•	PSGetV2/PSGetV3 running side-by-side is not a significant scenario that we should support, PSGetV3 should replace V2 and we should plan to deprecate V2

I did not take into account people who use fully-qualified cmdlet names. Is it a lot of users?

There are concerns with marketing of "PSResourceGet", would it be considered a subset or inferior to the "real" PowerShellGet. Would moving people for PSGet to PSResourceGet be difficult?

I feel this statement is also applies to the new cmdlet names in the same module as the old ones. Which cmdlet is the "real" one and why should I use the new names when the old ones are still there? If you have both legacy and new cmdlets in the same module why even have the renamed cmdlets and just use the legacy ones?
When the RFC was open I was behind using a new module name for this migration since the cmdlet names would be changing.
I believe that if the new user experience is better and has feature parity with v2 than you'll get people to migrate to the new module/cmdlets on their own.

Top priority should be making adoption of PSGetV3 as easy and seamless as possible.

I also agree with this statement. My main concern is the user experience and having legacy cmdlets and new cmdlets in the same module creates user confusion about when and where to use which.
My opinion is to take option 3 which solves the fully-qualified name issue and is backwards compatible with v2 by shipping both PowerShellGet module as a compatibility layer while also having a clean break for users with the new module and cmdlets. However, I feel the PSResourceGet could have a better name (remove Get) 😄

We had another discussion so I wanted to update with more options. We discussed that because 7.4 is an LTS we want to be very cautious about introducing breaking changes, especially coming in much later than we hoped in the release cycle, so another option we discussed is shipping PowerShellGet v2 and v3 side by side in 7.4 (with no Compat layer). We initially didn't consider this option because it was not possible due to the way that PowerShell is built (and at the time we weren't considering renaming the module), however it is now possible with the option to rename PowerShellGet or not rename PowerShellGet. This would break the fewest people possible, but still allow those who wanted to upgrade to do so. The down side is that this would slow adoption to v3 implementation (although could potentially accelerate adoption of v3 syntax since those who wanted to get the benefits would be more inclined to update scripts, still Compat would be available on the Gallery). Since 7.5 is not LTS and we could ship beginning in Preview 1 we could stop shipping PowerShellGet v2 in 7.5 and introduce one of our compatibility options described above. This would allow us more time to figure out gaps in the proxy functions and help folks with the transition. Personally I am eager to get v3 out there and would love to see it fully replace v2 in 7.4 but want to make the decision that is best for the broader PowerShell community (1 billion monthly sessions).

I like this option the best, just ship both v2 and v3 in PowerShell without the compat layer as its not needed. Users that haven't migrated will still use the exact same version they're use to and for users that have migrated will get the new experience. This also has the added benefit of keeping the module name the same for familiarity.
I would recommend to do the following:

Update PowerShellGet v2 with a warning message when used if the module has been loaded from $PSHOME that the module will no longer be shipped in PowerShell in the future (or X release) and can be installed explicitly if they still need to stay on v2.
Since the warning only goes out to people who are using the built-in module they would be impacted while users that have installed it through PowerShellGet even if they upgrade PowerShell, v2 would still stay around in their AllUsers or CurrentUser path not breaking them.
The warning also serves the purpose for CI/CD like how GitHub actions will write a warning if using an out of date image that will be removed in the future.
You can also use telemetry to determine when PowerShell v3 adoption has reached acceptable levels to remove v2 in-box.

I believe with adequate notice with warnings serves is reasonable to notify users to migrate without the need to place the compat layer in PowerShell. You can also use telemetry to determine when v3 adoption has reached acceptable levels to remove v2 in-box. This is still way in the future and we don't know how quickly v3 adoption will take place to warrant shipping the compat layer after v2 has been removed in 7.5/7.6+.

@ThomasNieto, I love the suggestion of adding the warning into v2.  We hadn't thought of adding warnings there in particular, but I think the plan you laid out is a great way to get the deprecation warning out.

closing this in favor of #1120


fix: Prevent task.frontmatter.tags being null if no tags in frontmatter

Types of changes

Changes visible to users:

[x] Bug fix (prefix: fix - non-breaking change which fixes an issue)

A small fix to an unreleased feature
See https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2480

[x] Sample vault (prefix: vault - improvements to the Tasks-Demo sample vault)

Internal changes:

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Description
In src/:

fix: Prevent task.frontmatter.tags being null if no tags in frontmatter
Remove TasksFile.frontmatterTags
Improve JSDocs of TasksFile.ts

In tests/:

Add safety checks to the mock functions getAllTags() and parseFrontMatterTags()
Add more tests, just exploring the behaviour

In sample vault:

Update sample code that demoed use of now-deleted task.file.frontmatterTags

Motivation and Context
More progress on https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2480
How has this been tested?

Adding new tests
Exploratory testing in demo vault

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follows this project's contributing guide
[x] I agree to follow this project's Code of Conduct

@ilandikov FYI...
I'm going to merge this as I want to explore its use on my main vault, but you might be interested in the changes, or we can review them in the next session.
Note that I've started a checklist in the https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2480#issuecomment-2223266515 comment - to get info out my head and out of my personal vault...

Well spotted! Thanks =)


[Snyk] Security upgrade node from hydrogen-buster to 18.19.0-slim

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to node:18.19.0-slim, as this image has only 36 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

500
Out-of-bounds Read SNYK-DEBIAN10-DB53-2825169
No Known Exploit

500
Out-of-bounds Read SNYK-DEBIAN10-DB53-2825169
No Known Exploit

400
Improper Input Validation SNYK-DEBIAN10-PYTHON37-3325305
No Known Exploit

500
Integer Overflow or Wraparound SNYK-DEBIAN10-ZLIB-6008964
No Known Exploit

500
Integer Overflow or Wraparound SNYK-DEBIAN10-ZLIB-6008964
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Input Validation

Upgrade node version


severe performance degradation between 0.5.2 and 0.6.2

Hello,
i was building numpy documentation with pydata-sphinx-theme/0.5.2 (which is the version pinned in their requirements.txt), but that's affected by https://github.com/pydata/pydata-sphinx-theme/issues/394 which is fixed in 0.6.2, but when i've upgraded to that version, the build time spiked substantially.
I've run a test with these pydata-sphinx-theme versions, with the time (in mm:ss.00 format) it took to rebuild numpy's doc with each version:

0.5.2: 5:17.99
0.6.2: 25:20.05
0.6.3: 24:53.24
0.7.0: 24:34.35
0.7.1: 24:52.37

as you can see, in using 0.6.2 onward the time is 5x what it was with 0.5.2 (granted, numpy's doc fails with that version, but at the very end of the build process, so that's still relevant), and the only thing changing in this build environment is the pydata-sphinx-theme version used.
I'm wondering if this is something you're aware of and plan to address, or is this a news and maybe some investigation is required?
Thanks,
Sandro

As this issue is related to numpy and the underlying problem is dealt with in other issues should we close this one ?

Yep we have made and documented ways around this in this PR:

https://github.com/pydata/pydata-sphinx-theme/pull/492

so I think we can close


Text layout of About Tab on About Screen is incorrect

Describe the bug
The "About Text" on the "About Tab" on the "About Screen" is incorrectly formatted. The text width appears to be 1/2 of the page width, resulting in formatting that looks very unexpected.
See screen shot below.
Version
Composer Nightly.
BotFramework-Composer-1.4.0-nightly.234969.d950804-windows-setup.exe
Browser

[X] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[X] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to About Page
Click on the About Tab
Read the About Text
Observe that the text isn't full-width, and is curring off at what looks like ~40 columns.

Expected behavior
Normally formatted / justified HTML.
Screenshots

@mewa1024 does issue #7121 encapsulate the items within this bug?  If so please close as a dup. If not, let's get everything for the About page into a single issue and close the others to reduce noise.

Good point. Closing as a dupe of #7121


[FLINK-3218] Merging Hadoop configurations overrides user parameters

Thanks for the patch!
+1 to merge

Merging this PR


Where can I see the themes?

Would be nice to be able to see the themes without having to install the package.

+1

It's not even documented how you use them. Do you include the regular CSS file and the theme or is just the theme CSS enough?

+1

https://chmln.github.io/flatpickr/themes/


child and parent views data is bind unexpectedly

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[ x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
i push a page with parameters (object) and grab them in the second page with navparams.
if i change this object in the second page it is changed in the first page too. how is that possible without me doing so? or is it expected behavior?
Expected behavior:
i think first page data should not change.
Related code:
insert any relevant code here
`<div *ngFor="let control of controls;let i=index">
    <ion-list-header *ngIf="control.header==true">{{control.label}}</ion-list-header>
    <button ion-item (click)="showDeviceControlPage(control)" *ngIf="control.header==false">{{control.label}}<ion-note item-right>{{control.value}} {{control.units[0]}}</ion-note></button>
  </div>

  showDeviceControlPage(control) {
    this.navCtrl.push(DeviceControlPage, { control: control });
  }
//from the DeviceControlPage i get the object
this.control = this.navParams.get('control');
//so if i change this.control.value from the DeviceControlPage it is changed in the first page too.

`

**Ionic info:** (run `ionic info` from a terminal/cmd prompt and paste output below):

Cordova CLI: 6.1.1
Ionic Framework Version: 2.0.0-rc.4
Ionic CLI Version: 2.1.17
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.47
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v6.7.0

Hello, thanks for opening an issue with us! Can you create a plunker that demonstrates this issue please?

ok i think i did it
http://plnkr.co/edit/ZnBNWXTcPkZD7Nvzfe4s?p=preview
click a button change the label from second page and pop back.

I also can confirm this:
https://plnkr.co/edit/Gg4iuH?p=preview

Hi there! This is most definitely the expected behavior. Objects are always passed by reference in JavaScript, unless you explicitly make a (deep) copy.

@loopezz that works. thank you.

Closing as this is the expected behavior


Docs are broken for latest aka 1.7.0

Describe the bug at a high level.
Welp, the latest version's doc page seems to be broken.
What are the steps to reproduce the behavior?
Goto,
https://docs.rs/regex/latest/regex/index.html
What is the actual behavior?
From 1.6.0,

What is the expected behavior?
For latest,

Notes
I am open to fixing this issue if it's something that I can open a PR for, haven't had the time to look into it, I will take a look at the weekend.
The bug is repeatable on my friend's system and also on mobile devices.

Oops(used the wrong id), ping me here, not sure if I will check my work github for notifications. :P

OK, I've kicked off a new release with the hope it was just a temporary glitch, and that appears to be the case. The rendering for 1.7.1 looks good to me.


Always send shopperReference in HPP call

ShopperReference is required for all OpenInvoice payment methods.

Sorry only applied for M2.


1.4 & 1.4.1 "Space" descriptions

Starting with the betas of 1.4, the description on the space videos just says "Space". I have removed the screensaver, and the cache, the reinstalled, but still have the issue. I also have the issue on another Mac.

You mean on the list on the left ? Can you post a screenshot of what you see ? It says space > space ??
Also, macOS version ?
Here's what I have here FYI on 2 macs (10.13.6 and 10.14.1beta):

The list is okay, it is the deception when viewing the screensaver.
MacOS 10.14

Thanks for your quick reply. In the Text panel, do you have the "Display in preferred language when available" selected ? If so, what does the line just below says ?
Also, just to confirm, you don't see this in other videos ?
Thanks for reporting this, I'll have a look.

No, it’s not checked. I have tried it with it checked, and I have the same issue. The line underneath says preferred language: English (United Kingdom).
On the other videos I’m only getting the city names, not the detailed descriptions that are visible in the sidebar.
Something to note; in the cached folder, there are only videos. There used to be JSON files and the like, with metadata about the videos. Have you moved these?

Ha that explains it ! I definitely haven't and they definitely should be there. Did you perhaps change the cache folder to another place ?
FYI, the extra strings are contained in the  ~/Library/Caches/Aerial/TVIdleScreenStrings.bundle file
So since you don't have those, it fallbacks to the short name.
You still see Aerial working because the JSONs are saved in the preference files (something that remains of the old original version) and I use that if available and don't try to redownload the files. In your specific case though that's an issue.
 You'll also see extended descriptions in the "old" videos like London as a bonus !
I'll try to add a better mechanism to redownload the .tar/jsons in the next version, sorry about that again !

I did not move the cache folder. The issue must have arisen when I cleared the cache and removed the screensaver via the finder, but not the plist, before installing the first release you made.
I have done why you have suggested, and it has fixed it! Thanks!
I guess most people will not have this issue. I only cleared out the cache manually to remover excess videos from before, because it did not work through the screensaver preferences.

Makes sense, by removing the cache the files were gone but not the plist.
While unusual, still better to have a fix in a upcoming release. Thanks for your report on this !

Also the flaw in removing screensavers on a Mac, I does not remove the associated files.
You're welcome!

where are the other files?

I'm not sure we can cleanup anything at uninstall, I'll have a look !

The error pane will be useful!
Do you have to remove the old version before installing a new version?
I understand when you are updating to a new versions, maintaining the plist is useful to ensure the settings stay them, but for people who want to fully remove it, an uninstall option may be nice.
On a related note; is it possible to have an update feature from the preferences pane?

Do you have to remove the old version before installing a new version?

You don't, but you probably need to restart the System Preferences (close and reopen) in order to properly reload the plist (ironically !) and the ressources (you may see the wrong version show up and an unresponsive UI). As far as we know, that's a bug with the way Swift plugins are loaded.
It fixes itself the next time you launch System Preferences and we have no workaround so far. I'll try to make a sample project and submit a radar to Apple when I have a sec.

I understand when you are updating to a new versions, maintaining the plist is useful to ensure the settings stay them, but for people who want to fully remove it, an uninstall option may be nice.

The thing is, Aerial is not a standalone app, it's a "plugin" for System Preferences. So the install/uninstall mechanism is a bit more restricted. That's why when you double click the .saver, it starts System Preferences who then asks you if you want to install/replace existing version.

On a related note; is it possible to have an update feature from the preferences pane?

Same thing as above, we can't really do that for the same reason. We can probably do a new version check (and probably download the new version), but won't be able to install. I'm thinking about adding the version check in the new error pane and point people to the new version.
As of today, the supported mechanism for auto update is brew cask. It may lag a bit though (by a few hours usually). They seem to have a few issues right now with their integration server but hopefully 1.4.1 will be there ASAP, we have the pull request ready : https://github.com/Homebrew/homebrew-cask/pull/53694

That makes sense. Maybe some instructions would suffice?

We do have that !
https://github.com/JohnCoates/Aerial/blob/master/Readme.md#uninstallation
I've updated it with the location of the plist.

A notification that there is a new version would be good. VirtualBox for example directs users to a website to download the latest version, which I find bizarre for a company as large as Oracle can not have a proper updater for a standalone app! Adobe does the same with the Flash updater in the System Preferences pane, but that is pretty much dead.
That lag would not be noticeable for most users to be fair.
I use coderelease.io to tell me about your releases.

Marking as an enhancement for a future version.

Still not working for me. The files are not there for me. Where else could they be?

You have the same issue of the titles not showing, that's right ?
First, go to the Cache panel, click "Show in Finder", that will open your current cache. This is where the missing files should go.
Or are you looking for the plist to delete it ?
/Users/YOURUSERNAME/Library/Preferences/ByHost/com.JohnCoates.Aerial.{UUID}.plist
Where YOURUSERNAME is your user name, and {UUID} is a series of numbers/letters.
Another place to look at, maybe, /Library/Preferences although I'm not sure it would go there. Maybe if you installed the screensaver for all users, although I'd think every users would have it's own plist.

I already tried both places. weird

Well, here's a workaround, download : https://sylvan.apple.com/Aerials/resources.tar
Put that file in the cache folder (look the Show in Finder button in my previous comment). Then untar the file and keep the tar too. If you need help untaring let me know.

thx

Put both in?  Or just one?

Put the tar and untar in place.
You just need the TVIdleScreenStrings.bundle to solve the issue in practice. That file needs to be in the cache folder.

I did it and it still isn't working it this right:

nearly there. move the files from the resources folder in the main cache directory (copy them one level down if you see what I mean ?).

Thank you so much it is working for me now!

You're welcome :)

Maybe put that guide in to the readme doc.
I mean troubleshooting

Good idea, done  : https://github.com/JohnCoates/Aerial/blob/master/Readme.md#troubleshooting

Closing as fixed in 1.4.2beta1 : https://github.com/JohnCoates/Aerial/releases/tag/v1.4.2beta1


0 handling in whole part

Do we accept handling padding 0 at the beginning ?
Such as 0042, or 001.234
If we accept stuff like this, do we accept 000.0 or 000 ?

I have no idea, it is up to @elusyo ;)

It is easier to accept them...

Maybe we shouldn't accept them.... It's not useful to make this language more complex. When we will transform them with the parser the 0 will disappear! We must accept 0 and 0. because there is a different type.
It's my point of view, @FauconFan you decide :smile:


Missing Images for Paperowl

I have tried to execute the steps as enlisted here for extracting the PaperOwl dataset. Can you please confirm if these images are really missing or is there something wrong in extraction?
imgs/2106.08905v2/figures/out_28170.png
imgs/2106.08905v2/figures/28170.png
imgs/2303.16501v1/tables/table_7.png
imgs/2305.16835v1/figures/fig_result_2.png
imgs/2102.12037v3/figures/table-AUROC-boed.png
imgs/1908.09231v1/tables/table_1.png
.... more images are missing

Hi, @BajajSmriti , I have checked these images are contained in the ./imgs directory. Please check you have downloaded all partial-imgs files, the 'cat' and 'tar -zxvf'  can also run without errors when the lase partial-imgs file is missing.


fix: Cron Scaler e2e test works during min 59

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>
Before this fix, if we execute the e2e test at XX:59, the generated cron expressions are 60 * * * * and 61 * * * * which are incorrect, this PR ensures that cron's minutes are between 0 and 59
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

/run-e2e cron*


Put pCloud Drive back in the Drives list

What feature or improvement do you think would benefit Files?
Quick access to pCloud
Requirements
Allow user selectable cloud drives to also show in the Drives section.
Maybe Right-click on the cloud drive and select Add To Drives
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.2861
Comments
No response

Thanks for the feedback, Have you used the cloud drives section in Files?

Thanks for the feedback, pCloud can be found under the Cloud Drives section. If it's not displaying there, please let us know and open a bug report so that we can look into it.

I confused Explorer with Files. pCloud in Explorer shows up in Devices and Drives, which I like.

Thanks for the clarification, we display it under cloud drives to be consistent with OneDrive and the other cloud drive providers.


Add mastodon support, add mastodon for Belgium

Hi,
With Mastodon taking off, I wanted to add the Belgian Mastodon account, but support seemed to be missing.
I did a best effort to add the support for this where needed, but I probably forgot something somewhere; so a thorough review would be welcome.

sounds good to me, thanks!


Report the taxid and or name

Hello again,
I've been using Conifer for a bit now and I find it very useful. Thank you for that. At the moment, Conifer in its simplest form reports

kraken output
read1 confidence
read2 confidence
average

Since Conifer can obviously do this, as seen for the summary report, I would love to get the output as

taxid
name (optional)
read1 confidence
read2 confidence
average

and simply have additional rows for the same taxid. Does this make sense? Would you consider adding this output option? Or maybe there is a different simple way to map the kraken output to the taxid that I am missing right now.

Hello,
kraken2 output contains taxids. So, in bash you can do something like
./conifer -i example.out.txt -d taxo.k2d \
    | cut -d$'\t' -f3,6,7,8 \
    | sort -k1,1n > output.txt

or some sed magic if you have names in kraken output:
conifer -i example.out.txt -d taxo.k2d \
    | cut -d$'\t' -f3,6,7,8 \
    | sed -E 's/(^.*)\s\(taxid ([0-9]*)\)/\2\t\1/' \
    | sort -k1,1n > output.txt

I hope this helps.

Okay, thanks for getting back to me. Yes, this information is contained. I was feeling a bit lazy and I thought since your summary mode already cleans up the name/ID, you must have helper functions to do this already and it would be a straight forward addition.

Yeah, it does, however there are multiple fields that one might want to include/exclude. In my opinion, the best way would be to implement something like blastn's outfmt option where user can specify a list of fields to be included in the output. I might add it in future, but for now the fastest way to get the output you need would be piping through bash utilities.


How do i run Osiris on linux

Linux distro: Pop-OS 21.04
If you are gonna make post about how to run osiris on linux
please add everything that is need to run it!

ubuntu
can't get it to inject using load_osiris.sh
csgo will just quit
any idea ?


WebServer taken down due to an exception from channels

Not sure where the bug is. It is related to #4. I think there was a write when the connection was being killed due to XmlHttpRequest time out. It brought the entire server down.
System.InvalidOperationException occurred
HResult=-2146233079
Message=No ongoing producing operation. Make sure Alloc() was called.
Source=Channels
StackTrace:
at Channels.Channel.AdvanceWriter(Int32 bytesWritten)
at Channels.DefaultWritableBufferExtensions.Write(WritableBuffer buffer, Span1 source)        at Channels.WritableChannelExtensions.WriteAsync(IWritableChannel channel, Span1 source)
at Channels.ChannelStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at Microsoft.AspNetCore.SignalR.JsonNetInvocationAdapter.Write(Object value, Stream stream) in C:\source\NetworkingProtoype\src\Microsoft.AspNetCore.SignalR\JsonNetInvocationAdapter.cs:line 39
at Microsoft.AspNetCore.SignalR.JsonNetInvocationAdapter.WriteInvocationDescriptorAsync(InvocationDescriptor invocationDescriptor, Stream stream) in C:\source\NetworkingProtoype\src\Microsoft.AspNetCore.SignalR\JsonNetInvocationAdapter.cs:line 31
at Microsoft.AspNetCore.SignalR.DefaultHubLifetimeManager1.InvokeAllWhere(String methodName, Object[] args, Func2 include) in C:\source\NetworkingProtoype\src\Microsoft.AspNetCore.SignalR\DefaultHubLifetimeManager.cs:line 68
at Microsoft.AspNetCore.SignalR.DefaultHubLifetimeManager1.InvokeAllAsync(String methodName, Object[] args) in C:\source\NetworkingProtoype\src\Microsoft.AspNetCore.SignalR\DefaultHubLifetimeManager.cs:line 46        at Microsoft.AspNetCore.SignalR.AllClientProxy1.InvokeAsync(String method, Object[] args) in C:\source\NetworkingProtoype\src\Microsoft.AspNetCore.SignalR\Proxies.cs:line 53
at SocketsSample.Hubs.Chat.d__1.MoveNext() in C:\source\NetworkingProtoype\samples\SocketsSample\Hubs\Chat.cs:line 16
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
InnerException:

It turned out to be an unhandled exception thrown on a ThreadPool thread. Fixed in 217f707456e250326cec4e551880074623e75084


Appending secure flag to existing application cookie

Do you want to request a feature or report a bug?

Bug/More of a question.

What did you do?

Hi,
I want to append/set the "Secure;HttpOnly" flags to an application cookie that is generated in the backend by Service A which is passing it to Service B via Traefik. I have ingress routes attached to the service B as follows.
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: jupyter-ingress
  namespace: kube-system
spec:
    routes:
        - match: Host(`test-xyz.com`) && PathPrefix(`/jupyter`)
          kind: Rule
          services:
            - name: proxy-public
              port: 443
    tls:
        secretName: self-signed-tls

As i understand, setting middlewares to either headers.customResponseHeaders or headers.customRequestHeaders would replace existing cookie value to the value we set. The application cookie here is a token, which is not a static value so we will not be able to use either of those header middlewares.
What did you expect to see?
Application session cookie to be having flags "Secure;HttpOnly" when communicated across different services.
What did you see instead?
Blank Cookie with Secure;HttpOnly flag. or No Secure;HttpOnly flags when passing between different services.
Output of traefik version: (What version of Traefik are you using?)

2.2.1

What is your environment & configuration (arguments, toml, provider, platform, ...)?
Environment
AWS EKS v1.16

Installation
helm install traefik traefik/traefik --values config.yaml -n kube-system

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
Would be great to know if there is any way to fix it or will this be part of a future release.
Thanks.

Hello @tirumerla,
Thanks for your interest in Traefik :D
Currently, it is indeed not possible, and the flags should be added to the cookie by your backend service to control how it should be used.
It is also a current proposal #6047, but if you cannot change or configure the backend behaviour, it is always possible to implement a plugin.
Unfortunately, we will close this issue accordingly.

Hello @tirumerla,
Thanks for your interest in Traefik :D
Currently, it is indeed not possible, and the flags should be added to the cookie by your backend service to control how it should be used.
It is also a current proposal #6047, but if you cannot change or configure the backend behaviour, it is always possible to implement a plugin.
Unfortunately, we will close this issue accordingly.

Thanks for the information @kevinpollet. We have workarounds for now, will wait until the current proposal is executed and merged.


UI_Improvements_In_Edit_mode

Describe the bug

[x] Environment & Clients & Databag Item Create Button is not vertically aligned
[x]  In Acceptance the font styles are not loading in Environment
[x]  Environments Cookbook Constraints - Hover on edit button needs to be the light blue, and its overlapping the line.
[x]  Form elements when they have focus - have a blue border.
[x]  Databag > Databag Item: when there are no data bag items, reduce the top margin (approximately "top-margin: 5%)
[x]  In some cases, when creating a data bag item, it doesnt show up?
[x]  Databag Item > Delete link should be secondary button with the hover of the blue background.
[x]  Delete modal dialuge text needs to be updated
[x]  Client Details: Tab bottom border needs to match the other tabs
[x]  Client Details - reset key - button needs to match styles. (after the click the border remains)
[x] invalid admin  key message

Closing these issues , created different issues from this and added to epic #4965


Cipher version mismatch

Using Teams Web in Edge.  Trying to open the settings brings up an Edge error about cipher mismatch.

why does it end with mcas.ms

That's a specific config used by bitglass


Google Storage: googleapi: Error 404: Not Found, notFound

I am trying to use Google Storage to upload a file. I have successfully uploaded a file with the same code base in dev environment which use service json for authorization. However, when I deploy same code in GCE and try to upload a file, the server return "googleapi: Error 404: Not Found, notFound" to me. I have checked the permission of my instance. It is full-control for Google Storage. What's the problem?
The following is my authorization method to return "context"
func GetAuth() (ctx *context.Context) {
	var _ctx context.Context

	if IsDev() {
		jsonKey, err := ioutil.ReadFile("path-to-my-json")
		if err != nil {
			log.Panic(err)
		}

		conf, err := google.JWTConfigFromJSON(
			jsonKey,
			datastore.ScopeDatastore,
			datastore.ScopeUserEmail,
			storage.ScopeFullControl,
		)
		if err != nil {
			log.Panic(err)
		}

		_ctx = cloud.NewContext("my-project", conf.Client(oauth2.NoContext))
	} else {
		client := &http.Client{
			Transport: &oauth2.Transport{
				// Fetch from Google Compute Engine's metadata server to retrieve
				// an access token for the provided account.
				// If no account is specified, "default" is used.
				Source: google.ComputeTokenSource(""),
			},
		}

		_ctx = cloud.NewContext("my-project", client)
	}

	ctx = &_ctx

	return
}

This is my "default" scope retrieving from GCE
https://www.googleapis.com/auth/bigquery
https://www.googleapis.com/auth/cloud-platform
https://www.googleapis.com/auth/compute
https://www.googleapis.com/auth/datastore
https://www.googleapis.com/auth/devstorage.full_control
https://www.googleapis.com/auth/logging.admin
https://www.googleapis.com/auth/monitoring
https://www.googleapis.com/auth/sqlservice.admin
https://www.googleapis.com/auth/taskqueue
https://www.googleapis.com/auth/userinfo.email

Which call is returning this error?  It sounds to me like your Objects.Insert call is missing the object's name.  If it were me, I would debug this by instrumenting the call to get the full response from the server when the Objects.Insert call is being made.

Finally, I found the issue. It's my fail. I am using different config in GCE environment and I haven't create any bucket for that environment. Thanks for you reply @gmlewis


ci: Nightly tests are needed for stable branches

Otherwise we are missing on possible failures that are already fixed in master but they aren't in the stable branch, like PR #1231

@alfredodeza we have nightlies for stable-3.0 and I've pushed a PR to add stable-3.1
do you think we can close this? any suggestion?


[top_earlgrey] Remove AST_MISC pad

This commit removes the AST_MISC pad from top_earlgrey.  That pad will be replaced by a VSS supply pad.  This partially addresses #22990.
TODO Items (pre-merge)

[x] Run chip_padctrl_attributes
--> passes 100%.
[x] Check other mentions of #18988 in the code and confirm that all of them are fixed (util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -t vcs -i chip_padctrl_attributes --waves fsdb).
--> They are not, so this PR won't close that issue.

I'm currently running this through AST-related TLTs (util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_ast_clk_outputs chip_sw_ast_clk_rst_inputs) to check that I didn't miss something there.

The failing rv_dm_access_after_wakeup_dev_fpga_cw310_sival test in the CW310 SiVal non-ROM_EXT Tests CI check can also be found in other PRs, so most likely unrelated to this PR. All other CI checks pass.


[Task]: Player Movement Transitions

Rubric Criteria

[x] Gameplay
[ ] Graphics
[ ] Design
[ ] User Experience
[x] Scripting
[ ] Sound
[ ] Quality
[ ] Process

Briefly, what are you going to work on?
I am going to improve the player movement mechanic using lerp to add a moving animation to the player, rather than just teleport to the path. Maybe also improve the camera to rotate for future purposes.
Provide at least one example of a similiar element in another game.

Game Name: Overcooked 2
Link: https://store.steampowered.com/app/728880/Overcooked_2/
What is needed to implement the task?
Scripts: Modify the player movement script using lerp to allow the player to smoothly transition over to the next path.
What is the biggest risk it will not get done?
If I can't figure out how to program the player to move from point A to point B using lerp to transition smoothly.
How do I know it is ready? (Test case)
When the player chooses a path, which will activate the player movement code using lerp to transition smoothly to the stop. The Gray boxing will also have to be finished before we can merge the Player movement.

I would have listed this as gameplay and scripting. UX is really meant to be UI and quality is for bug fixes.
What does it mean to transition to the other stop are we talking about player movement and animation? If the player isn't teleporting, then what is it doing?
What game is in the image and where is a link to the game?
Scripts to do what? How many? What are they attached to?
So knowledge is the risk, that's good. What do you mean by transition?
No need to add the part about bugs, we can assume everything will have bugs in it. Again, what does it mean for the player to transition smoothly to a stop? What would the player do to initiate a transition? What steps have to happen to have a transition?

(Test case) What does the player do to make the transition happen? If you wanted me to test if you implementation worked, what would you tell me to do?
(Needed to implement) What are the names of the scripts? How many are there? What will it/they be attached to? We need implementation details.
(Risk) It's great that you mention understanding how to use Lerp, that is the kind of implementation details we need.


[FEATURE] Upgrade file_picker package to latest version.

Can we upgrade the file picker version to latest stable version, it is causing a vulnerability and using getExternalMediaDirs in the older version.

Yes please!


Add dag_weighted_longest_path_length() function

As a follow up to #383 what the underlying Qiskit user case for #381
would like is to use floats for the edge weighting. However for the
existing dag_longest_path_length() function our hands are tied with the
return type being an unsigned integer for backwards compatibility. To
workaround that limitation this commit adds a new function
dag_weighted_longest_path_length() which requires a weight function and
works with f64 weights. To accomplish this, the inner longest_path() rust
function is made generic for any numeric type returned by the callback
function, which required leveraging the num-traits crate. The new
pyfunction is then just a thin wrapper that works with f64 instead of
usize.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.475%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5634

Relevant Lines:
5901

💛  - Coveralls

Yeah, that's a good idea, there wasn't an immediate use case for it but it's only a few extra lines so better to have it, I'll add it now.


Jekyll escaping of {{ is missing on some pages

{{ characters are not being escaped on a few pages - they look ok in GitHub, but they disappear completely on spinnaker.io.
For exampe, in the Example Usage section of annotations-ui, {{ name }} is missing, but is present in the code (guides/user/kubernetes-v2/annotations-ui/index.md).
I found a few other cases like this as well, so escaped them in the accompanying PR (like {{"{{ name "}}}}, as was done in some existing pages).

Added fix in PR #774


[CT-338] Add materialization Table Function

Describe the feature
Be able to create table functions using dbt. Basically just create a macro for this that does something like
I guess the macro for creating table could be a guide, but add some more parameters.
Describe alternatives you've considered
I think either this fits or it doens't :slightly_smiling_face:
Additional context
Since bigquery has released table functions which is basically a parameterized table
Who will this benefit?
This is good if you want to parameterize your tables, e.g. if you want to be able to do some filtering based in datastudio parameters but also want to version control you queris.
Are you interested in contributing this feature?
Yes but I would need some input on how. Found the materializations in https://github.com/dbt-labs/dbt-bigquery/tree/main/dbt/include/bigquery/macros/materializations but I'm not sure if the implementation is a straightforward as I see it.

@Jaxing Thanks for opening, this is very cool!
"Table functions" in BigQuery (docs) look a lot like "tabular functions" in Snowflake (docs) which look a lot like "SQL functions returning table" in Postgres (docs). This feels less like a net-new thing in the world, and more like BQ extending support for a construct that's existed for some time in other databases.
In terms of how one might want to use this inside dbt: I'm not totally sure! For models with predictable structures, that only vary by a few inputs — such as the models templated by the dbtvault package—the current art is to define macros that template a common model structure. Each model calls the macro, and provides just the arguments that differ for its instantiation. Should these models simply be calls to a table function (which take static inputs), rather than calls to a dbt macro? Preferences may vary here! I like the idea of seeing "source" and "compiled" SQL, a thing you obviously lose with table functions, but I imagine the latter might have some desirable performance characteristics.
Where it gets more interesting is thinking about metrics queries. Could the dynamic queries templated by the new metrics package, which take time bounds and a set of dimensions as inputs, actually be a call to a reusable table function instead? Maybe! On databases that support table functions, we might want to consider them as a potential behind-the-scenes implementation—but certainly not require them across the board as the precondition to metrics support.
For now, you could use table functions in dbt + BigQuery the same way you can use non-tabular UDFs, or any other database feature that is SQL-addressable. I do think we want to eventually add first-class support for UDFs in dbt (https://github.com/dbt-labs/dbt-core/issues/136, https://github.com/dbt-labs/dbt-core/issues/3391). In the meantime, using existing constructs, I've seen two decent approaches, each with its own benefits and limitations:

Wrap UDFs in macros, which get called during on-run-start hooks to ensure they're available
Create a UDF "materialization," define UDFs as models (!), and ref them in downstream models (!!), which ensures that they are created in proper DAG order and the lineage is tracked in a straightforward manner

@jtcohen6 Thanks for your reply!
Yes I think I can find a work around for this using UDF, and metrics seems like it might handle the general use case :+1:

Should these models simply be calls to a table function (which take static inputs), rather than calls to a dbt macro?

In my use case these table functions would be used to parameterize a query in bigquery so that I can send a parameter from datastudio into a properly version controlled model. I.e. in datastudio I would have a custom query that looks something like this:
select * from my_table_function(@some_parameter)

Which would then allow the user of the dashboard to enter some value to modify the calculations being done (e.g. the size of a window that is applied).

"Table functions" in BigQuery (docs) look a lot like "tabular functions" in Snowflake (docs) which look a lot like "SQL functions returning table" in Postgres (docs). This feels less like a net-new thing in the world, and more like BQ extending support for a construct that's existed for some time in other databases.

Yeah maybe this is more general then the dbt-bigquery lib and should be moved to dbt-core?

This would be a really great feature to have, so that we can parameterize the views we create at runtime. How do we reopen this?
The linked/mentioned issue is different and more complex to implement

Do we have any updates on this? I have the same use case where I want to versionate tables that depend on user inputs in a DataStudio dashboard. It would be awesome to have the possibility to create table functions via dbt!

@Jaxing, did you find a workaround?
Is there any update on this?

Looks like there is still ongoing discussion about how to best incorporate this into dbt proper, we added custom materialization in meantime (gist).


Adding UnqiueBot

This pull request was made by the Gatsby Branch Editor.

This is literally a red clone

Redbot


.pick ignores quality?

I'm trying to use incoming HTTP headers to serve up the most appropriate translation of a site, and it seems like .pick is exactly what I need, but it's not respecting the quality value of headers. When I run this:
parser.pick(["en", "nl"], "en-GB,nl;q=0.5"

I would expect it to return en, but it's giving me nl. Is this on purpose or would you like a PR to fix it?

This is correct. In the pick, you should use the full languages you support, like ['en-GB', 'nl-NL']. In that scenario, the picked would be en-GB.

Ah! loose actually returns the same, presumably because nl is an exact match?

I would advise to put full locales and nog languages in the array of options. Together with loose, you will in that case always get the full locale and will solve your issue:

parser.pick(["en-US", "nl-BE"], "en-GB,nl;q=0.5"

Should in this case indeed return en-US as language matches. Using split you can extract the language from the locale.

I added some tests for the readme examples and corrected the readme based on the results here: https://github.com/opentable/accept-language-parser/pull/35

I ran into specificity issues as well.
acceptLanguageParser.pick(['en-GB', 'es', 'en'], 'en')

The expected result, to me, would be en as it's a perfect match, but instead if returns en-GB.

parser.pick(["en", "nl"], "en-GB,nl;q=0.5"

I think It is correct to return "nl" for this scenario.
"nl" and "en-GB" have the same priority (q=0.5), so why a non-matching locale should be preferred to a matching one?
The user expect "nl" or "en-GB", why give him "en" (that is also much more like en-US than en-GB in terms of date-time formats), instead of something that is "right" for him?
Typical Accept-Language values are:

fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5
en-US,en;q=0.5

Your "en-GB,nl" is like the first example where you replaced "fr" with "nl", so why it should provide "fr" if "en" or "de" are accepted (also within the same q in your case)?
In your scenario, the missing "en" seems to indicate it really don't wan't it.

I believe in this case, fr-CH and en-US have weights of 1.  When the ;q= is missing, the q value is 1.
See here: https://developer.mozilla.org/en-US/docs/Glossary/Quality_values
Since this is a strict search, though, nl wins because that value is in the supported language array.

I wrongly assigned q=0.9  to both fr-CH and fr.
Said that, yes probably the higher q should define the priority when loose is True.

pick does ignore quality though.  if you look at the source, there's literally nothing in there that even looks at the quality number.
// en-GB: 0.2, en-US: 0.4
// this returns en-GB
parser.pick(['en-GB','fr-FR','en-US'], 'zh-CN,zh;q=0.8,en;q=0.6,en-US;q=0.4,en-GB;q=0.2'


Migrate toolchain to LLVM 13

This updates the tools used by the build scripts, CI pipeline, and linter/formatter to LLVM 13. Notably, the update to the newer version of clang-tidy required cleaning up some C++ patterns that were previously accepted under LLVM 11.

/azp run

/azp run


Add header-only build

Codecov Report

Merging #20 (942c8fb) into main (66e4a4c) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   64.94%   64.94%
=======================================
  Files           2        2
  Lines         930      930
=======================================
  Hits          604      604
  Misses        326      326

Impacted Files
Coverage Δ

include/snatch/snatch.hpp
95.45% <ø> (ø)

Continue to review full report at Codecov.

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


the "Name" filter is not working on /api/stacks

Bug description
the "Name" filter is not working on API /stacks
Expected behavior
The json answer should give only the requested stack
Steps to reproduce the issue:

Deploy 2 stacks with name : 'test','regular'

Search return the 2 stacks
curl -X GET 'https://localhost:9443/api/stacks?filters={"Name":"test"}' -H 'x-api-key: ptr_='

Search return the 2 stacks
curl -X GET 'https://localhost:9443/api/stacks?filters={"EndpointId":1}' -H 'x-api-key: ptr_='
Search return empty
curl -X GET 'https://localhost:9443/api/stacks?filters={"EndpointId":2}' -H 'x-api-key: ptr_='

The filters on Endpoint is working fine, but not the Name/name key

Technical details:

Portainer version: portainer/portainer-ce  2.11.1
Platform : Linux
Command used to start Portainer (docker run -p 9443:9443 portainer/portainer-ce):
Browser: curl
Use Case (delete as appropriate): Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? Yes
Have you googled/overflows/github issues ? Yes

@cyklodev
These are the only available filters: EndpointID, SwarmID

@samdulam
Facing the same issue, but I think adding the Name filter should also be considered because it's more flexible, especially in cases where we don't know the SwarmID. I believe It's even more expensive to process, let's say in cases where a lot of stacks need to be retrieved and parsed based on Name


Issue with SelectTab, ExpandTab and CollapseTab

Hi,
I have a latest v9 CRM online edition and when I use the commands say -
xrmBrowser.Entity.SelectTab("Product_Line_Items"); or
xrmBrowser.Entity.CollapseTab("Summary");
It gives me an exception indicating the tab was not found.
Not sure I was doing something wrong or if it is a bug. Anyways to fix the same I made the below changes and it is working fine now.
FileName: Microsoft.Dynamics365.UIAutomation.Api\DTOs\ElementReference.cs
       //Entity
        //{ "Entity_TabId"       , "[NAME]_TAB_header_image_div"},  //COMMENTED THIS LINE
          { "Entity_TabId"       , "[NAME]_header_image_div"},   //ADDED THIS LINE

FileName: Microsoft.Dynamics365.UIAutomation.Api\Pages\Entity.cs
Made below changes to ExpandTab, SelectTab and CollapseTab functions
           //if(!driver.HasElement(By.Id(Elements.ElementId[Reference.Entity.Tab].Replace("[NAME]", name.ToUpper())))) //COMMENTED THIS LINE
            if (!driver.HasElement(By.Id(Elements.ElementId[Reference.Entity.Tab].Replace("[NAME]", name))))  //ADDED THIS LINE

            //var section = driver.FindElement(By.Id(Elements.ElementId[Reference.Entity.Tab].Replace("[NAME]", name.ToUpper()))); //COMMENTED THIS LINE
            var section = driver.FindElement(By.Id(Elements.ElementId[Reference.Entity.Tab].Replace("[NAME]", name)));  //ADDED THIS LINE

Regards,
Nikhil

Thanks @SolzIT (Nikhil) for raising this issue. We'll take a look at the Element References to see what/why these may have changed. A couple of questions for you:

What is the version of your Dynamics 365 instance (9.0.X.XXX)?

Was this functionality working previously and broke after an update? Or was this your first attempt to utilize the Tab methods?

Regards,
Tyler

Hi Tyler,
The Dynamics CRM instance version is <IP_ADDRESS> and this was my first attempt to utilize the Tab methods.
Regards,
Nikhil

@SolzIT - Updating to confirm that I can replicate these issues. We're going to look at refactoring the underlying code to be more resilient depending on the Name value passed into the method.
The method was built to handle display name input, however it made an assumption that the Schema Name would be [NAME]_TAB. Your workaround should unblock you for now, however be aware that case syntax should match the schema name exactly as shown in the form editor.
I'll update once a fix is made available for this scenario. Thank you again for raising this issue to us!
Regards,
Tyler

@SolzIT - I pushed a change this afternoon to utilize XPath for the SelectTab, ExpandTab, and CollapseTab methods. This change should allow usage of the Display Name as seen on the form instead of the Schema Name.
If you have any problems with the new implementation behind this, please re-open this issue.
Thanks!
Tyler


contrib/lite: add missing include assert.h (spectrogram.cc)

tensorflow/contrib/lite/build_ios_universal_lib.sh fails with:
error: use of undeclared identifier 'assert'

@deltheil You legend!
I can confirm this works on my Mac where current master 7ad74a0d66c5b8547382dfd3aad503288f051ae9 does not work!
I followed instructions here:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/lite/g3doc/ios.md
I now have:
/tensorflow/contrib/lite/gen/lib/libtensorflow-lite.a

I can also confirm the app compiles and works with this code fix above! 👍


Bug: When parsing a new paragraph after any list, the paragraph is parsed as part of the list.

Lexical version: 0.17.1
Steps To Reproduce

Open lexical playground
Enable "Preserve newlines in Markdown"option
Create bullet or numbered list
Create new paragraph after the list without additional line breaks

Related to the fix: https://github.com/facebook/lexical/pull/6020 by @potatowagon (as part of the release https://github.com/facebook/lexical/releases/tag/v0.16.0)

Link to the video:
https://github.com/user-attachments/assets/700229aa-c055-4b41-a881-920069d2de9f

The current behavior
The paragraph becomes part of the list
The expected behavior
The paragraph remains independent
Impact of fix
Critical. Reproduce rate: 100%.

You should enable this configuration to preserve new lines.

With this configuration, this is the issue in the second part of the video.

With this configuration, this is the issue in the second part of the video.

GitHub's markdown editor also has this effect.

Yes, it's true.
Is it correct to put two line breaks after the list?

Yes, it's true.

But now the “preserve newlines in markdown” setting removes the line break after the list, which it should not do. I recorded a video as an example. By the way, github does not remove it.
https://github.com/user-attachments/assets/32470d84-7001-443d-9e84-543d67b8013b

@keiseiTi
Do you think we can fix it, given what I wrote above?
From our discussion, the “preserve newlines in markdown” setting should put two line breaks after the list and preserve line breaks between paragraphs. It doesn't work with lists yet.

@potatowagon
Hi, could you look at this issue please?


fix: fixed for the issue (#282)

1. Description

1.1. Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

1.2. Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

1.3. Related Issues

Codecov Report

Merging #284 (befcb4f) into main (a3ae82e) will decrease coverage by 0.39%.
The diff coverage is 64.28%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #284      +/-   ##
==========================================
- Coverage   75.88%   75.50%   -0.39%
==========================================
  Files         107      109       +2
  Lines         817      845      +28
==========================================
+ Hits          620      638      +18
- Misses        197      207      +10

Impacted Files
Coverage Δ

...esky/lib/src/entities/embed_record_with_media.dart
100.00% <ø> (ø)

...es/bluesky/lib/src/entities/embed_view_images.dart
100.00% <ø> (ø)

...lib/src/entities/embed_view_record_with_media.dart
100.00% <ø> (ø)

.../src/entities/converter/embed_media_converter.dart
64.28% <64.28%> (ø)

...entities/converter/embed_view_media_converter.dart
64.28% <64.28%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Make single_line_comment_style runs after no_useless_return

Fixes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/5382
Ping @mvorisek for review (as a reporter of bug).

Ping @mvorisek for review (as a reporter of bug).

LGTM, thanks @kubawerlos!

Thank you @kubawerlos.


What GPU did you use, may I ask?

We train our model with one GPU (Nvidia RTX A6000) that has a memory of 48G and the CPU is Intel Xeon Silver 4214R.