Regridding to a common non-spherical grid in curl()

Hi,
Wouldn't it be more logical to use the original cube in the curl components regridding in iris.analysis.calculus.curl()?
I.e. instead of this:
    if not spherical_coords:

        # TODO Implement some mechanism for conforming to a common grid
        dj_dx = _curl_differentiate(j_cube, x_coord)
        prototype_diff = dj_dx

have something like this:
    if not spherical_coords:

        # TODO Implement some mechanism for conforming to a common grid
        dj_dx = _curl_differentiate(j_cube, x_coord)
        prototype_diff = j_cube
        dj_dx = _curl_regrid(dj_dx, prototype_diff)

Should I create a PR?
Thanks.

Hi @dennissergeev, thanks for the suggestion. Sorry for the lack of a response, we're pretty busy trying to get v1.10 ready.
@pelson / @pp-mo - I know you're both very busy but could either of you offer a quick opinion?

Well, the result will not be the same, because dj_dx is a differential of 'j_cube' which does not have the same shape or grid (unless it is circular) -- as explained in the docstring of 'differentiate'.
I think the point of 'prototype_diff' is just to make all the partial differentials match the grid/shape of the first one calculated (dj_dx) so we can add and subtract them.
Maybe the grid of dj_dx is not really a 'natural' one for the results, being derived exclusively from the x-differential : so e.g. if the inputs are shape (ny, nx) on the same grid then the output will be (ny, nx-1).
Is that what you meant ?
I think this blanket regridding also allows the function to support inputs on staggered grids, which is probably an important requirement.
However, in that case neither i_cube or j_cube grids will be ideal (as they aren't the same).  In fact 'k_cube' would be a better candidate, as it is neutral to the X and Y directions.
When we don't have a k_cube, we would still need to form some kind of compromise grid from the i and j cubes ?
The comment "TODO Implement some mechanism for conforming to a common grid" seems to  indicate that the existing approach is a bit of a guess, and could be improved on.
Maybe it would be better to impose some extra requirements on the 'matching' of shapes and grids between to 2 or 3 input cubes.
From a practical point of view, improving any of this or changing it would now be a considerable fuss due to backwards-compatibility requirements.
Perhaps we could simply add a 'grid_cube' keyword that defines the grid on which the calculation is done (and have it default to dj_dx) ?

Well, the result will not be the same, because dj_dx is a differential of 'j_cube' which does not have the same shape or grid (unless it is circular) -- as explained in the docstring of 'differentiate'.

I agree, but then the argument still holds for the rest of the curl components: for example, di_dy's grid is centred along a different axis and different to the grid of dj_dx. So in my opinion, the choice of the first derivative for a prototype is not really 'physically justified'.

I think this blanket regridding will also allow the function to support inputs on staggered grids, which is probably an important requirement.

Are you sure it's permitted? Wouldn't it lead to an error after this line: bad_coords = coord_comparison['resamplable']?

However, we could perhaps add a 'grid_cube' keyword that defines the grid on which the calculation is done (and have it default to dj_dx) ?

Yes, that would be a good addition.
Thanks.

Are you sure it's permitted?
Wouldn't it lead to an error after this line: bad_coords = coord_comparison['resamplable']?

Ah, you are right, I just tried it.
So I think it does need them all to have matching coords, and if necessary you must regrid them onto a common grid before calling it.

If the i,j,k cubes must have common grid then it makes sense that the result should have the same.
@pelson can you see sense in this, or am I missing something ?
Unfortunately, to fix this we need to deprecate the existing behaviour before we remove/change it.
Despite what I said before about " 'grid_cube' keyword that defines the grid", I think maybe it is too confusing for the default behaviour be so broken,
In that case, I think an iris.FUTURE option would make much more sense.
E.G. with iris.FUTURE.context(curl_same_grid=True): ... .
The change isn't that complicated, though, so you can maybe quickly put up a PR which we can get  into v1.10 :wink:  ?
Then we are ready for the more sensible behaviour to become the default in v2.0.
(see : #1948).


auto-cpufreq: 2.3.0 -> 2.4.0

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

It is odd why disko is being included in the results for the build. Going to look into this a bit more.

I would imagine its beacuse disko needs nixos-install-tools and this package has always seemed to trigger nixos-install-tools and tests.nixos-functions.nixos-test to build

@isabelroses I see what you mean: https://github.com/NixOS/nixpkgs/pull/315383
It looks like other PRs also have disko showing up in their results too: https://github.com/NixOS/nixpkgs/pull/339874#issuecomment-2332481595


dnsmasq: 2.89 -> 2.90

Description of changes
Fixes CVE-2023-50387 and CVE-2023-50868.
Announcement:
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Built and tested on top of master.

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

Build tested after rebasing it on master. Builds on the four supported platforms. Static fails somewhere in nftables. The passthru tests are fine, except for the kubernetes ones, that fail elsewhere.


DCXY-25858 don't use ims token or pre-render for upsell redirections from extension

awaiting confirmation from the extensions team

Confirmed. @Blainegunn could you please take this to stage today?  The extensions team in Noida will test and if all goes well we can promote to prod before the restricted period begins.  Thanks!


@member/@private disables documentation generation

Hey @allenhwkim,
Thanks for creating this great template. I've found it remarkably useful.
However, it looks like certain tags will disable documentation generation for entries where present -- so far, I have encountered the issue with @member and @private. All other documentation will still be generated; it will simply skip entries with these tags.
Example:
/* globals angular:false */

'use strict'

/**
 * @ngdoc service
 *
 * @name app.notYourTypicalService
 * @description Doesn't really do anything. Oh well.
 * @memberof app
 *
 * @member {boolean} _superSecretPrivateVariable
 *
 * @ngInject
 */
function notYourTypicalService() {

    /**
     * @name _superSecretPrivateVariable
     * @description Indicates whether an email is currently being sent.
     * @type {boolean}
     * @private
     */
    var _superSecretPrivateVariable = false;

    return {
        // stuff
    };
}

angular.module('app').factory('notYourTypicalService', notYourTypicalService);

In the above example, the notYourTypicalService service will fail to be documented due to its use of the @member tag.
Similarly, even if the service were documented, the _superSecretPrivateVariable member will fail to be documented due to its use of the @private tag.
As soon as these offending tags are removed, documentation will successfully generate.
Is this intentional or am I missing something?
Thanks!

Thanks for using this.
I do not have intention not to generate documentation for @private and @member
JSDoc says @private won't generate documentation, http://usejsdoc.org/tags-private.html
Private members are not shown in the generated output unless JSDoc is run with the -p/--private command-line option.
Thus if you want to generate those, please make your own gulp file for that.


/scancode-toolkit-v31.2.4/configure throwing error

After initial setup done using below like on Centos 7(python 3.10)
https://scancode-toolkit.readthedocs.io/en/latest/getting-started/install.html#installation-on-linux-and-mac
seeing below error after running  ./scancode --help
**[vagrant@hostb scancode-toolkit-v31.2.4]$ ./scancode

Configuring ScanCode for first use...
/home/vagrant/scancode-toolkit-v31.2.4/configure: line 232: python3.8: command not found**

how to resolve this issue? please suggest. Thanks.

Let me move this to ScanCode toolkit.


Partial display of the table dedicated to the “Settings” option of the search page in “Mobile site” display mode

Describe the bug
v.: 5.192.2 | screen resolution: 1920 x 1200 | screen size (mm): 218 x 136
Hello. While the Mobile site display mode option is selected, and the search page is viewed along the vertical axis of the screen, the display of the table dedicated to the Settings option of the search page is partial.

How to Reproduce

Select the Mobile site option.
Display the search page along the vertical axis of the screen by rotating the screen accordingly; this requires Android's Auto-rotate option to be selected.
Click the Settings option which is found in the search page.

Expected behavior
The table dedicated to the Settings option that is found in the search page must be displayed in its entirety. See the case illustrated in this image, which was taken while the search page was viewed along the horizontal axis of the screen.

Environment
No response

Thanks @Ricky-Tigg.

conclude that this is not an issue specific to Duckduckgo for Android

Agreed. I will close this task on that basis, and share the feedback internally with the right team. Thanks for reporting!


STRtree segfault with empty geometries

Hi folks,
We observed a segfault in STRtree within the geopandas CI. See run here. Setting empty geometries to None before building the tree resolved the issue.
Strangely, the issue seems to only happen with Pandas == 0.24, so it might not be pygeos' fault, but I'm going to report it here because the segfault happens within pygeos.
I was not able to reproduce this locally using the latest Python 3.6 and Pandas == 0.24, so it might also be related to the specific Python binary or version Travis uses (I think it's not the latest).
If someone does decide to look into this, let me know if there is anything you need from me.

#147 reproduces the segfaults on Python <= 3.6

Wow that was quick! I'm impressed you were able to track it down so quickly, I thought it would be complicated.

#147 reproduces the segfaults on Python <= 3.6

Or it might be GEOS <= 3.6 ? (the python / GEOS versions are accidentaly all "aligned" ;))

Strangely, the issue seems to only happen with Pandas == 0.24, so it might not be pygeos' fault, but I'm going to report it here because the segfault happens within pygeos.

That's also the only build on pandas CI that uses GEOS 3.6, the others are at GEOS 3.7 or above, I think

This happened to Shapely too: https://github.com/Toblerity/Shapely/issues/345
It looks like this was fixed in GEOS > 3.6.  (since we're not seeing it in the test matrix after that)
I think the fix here is to simply not add empty geometries to the tree.  We'll still keep them in .geometries and preserve their indexes.

The GEOS version being the issue sounds a lot more likely than the Pandas version, thank you for pointing that out.

@brendan-ward bringing up the tree size thing here as well, since it's related to the segfault: if we aren't even adding empty geometries to the tree, shouldn't len(tree) not count them? I would expect len(tree) to have a concrete meaning, ex: number of leaves.

Unfortunately, that approach just runs into another segfault: if the tree is empty but count > 0, we attempt to query the tree and immediately fail (because the tree is not initialized with any geometries).  If we didn't increment the count for empty geometries, this would work correctly.
Ugh, empty geometries...
GEOS now ignores empty geometries on insert and correctly handles empty / uninitialized trees on query.
I'm not sure what the right thing to do is here.  Regardless of the segfaults, having empty geometries in the (GEOS) tree does not feel useful: they should never be returned for any query.
It does seem like the length of geometries and count should be the same value.
Right now, the way geometries is implemented on the tree, you only get back an array of non-None entries from the original array you pass in to construct the index (which means it is not a cache for your inputs).  These are used internally for testing predicates, and presumably could be used later to return geometries at a given index based on a query operation.  But since query will never return their indices, you'll never need to fetch them out that way.  Keeping them seems questionable.
@jorisvandenbossche what are your thoughts on dropping empty geometries during indexing, such that geometries only includes non-empty geometries (i.e., only those that are ever valid to test for predicates or return given indexes from query), and count thus becomes the count of non-empty geometries?

Sorry for the confusion above - I was conflating the two different arrays we keep of the geometry objects.
geometries is an ndarray of the original geometries; indexes into this is always valid.
_geoms is the vector at the C level of the geometries added to the tree, used only for predicate tests.
Based on this, I think so long as there isn't a good reason to return at count of all non-None geometries originally passed in, that we can instead simply omit empty geometries from the tree and count.

I'm +1 on that approach. geometries is an exact copy of the input to build the tree. _geoms can have the None/empty/invalid/etc. geometries set to a single empty type or omitted altogether, as long as the indexing is maintained it doesn't matter.

@brendan-ward  Do you know if this has been solved yet?

This was resolved by #147; apologies for not closing this at the same time!


Single format for documentation files

The repository documentation is currently a combination of Markdown and AsciiDoc.
We are in a situation where some files exists in both format and the same content requires to be updated twice.
Also contributors needs to constantly switch between between two markup languages.
While AsciiDoc allows for a more structured content, Terraform registry only supports Markdown.
I would suggest to use Markdown only.
Even if it is more limited that AsciiDoc, it is more common and would help when:

integrating with other solutions: if we start to automate some parts of the documents, Markdown support is more easily found than AsciiDoc
new contributors make changes: potentially less "new things" to learn before contributing

While this module's docs is simple enough to get away with Markdown, we've had a lot of formatting issues with Markdown in the past with other modules that require more structured documentation.
As such, we spent a considerable effort rewriting all related module docs (vcn, bastion, operator, oke, olcne) in AsciiDoc.
See https://mister-gold.pro/posts/en/asciidoc-vs-markdown/.
There's no need to 'learn' AsciiDoc like you would for a conventional language if all you're doing is writing docs with it. The reference is extensive and usually sufficient: https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/.
So, we'll duplicate in Markdown only the README of the main repo for the needs of Terraform registry. This README shouldn't change too often anyway. All other docs will be in AsciiDoc.

Agree with your points : Markdown is all but a standard when it comes to rendering ... My point of view is heavily influenced by Terraform registry capabilities, documentation of modules that use only basic formatting and no nested structures.
If dual-format is limited to README, we could probably auto-generate the Markdown version from the AsciiDoc version using tools like Pandoc or similar.


Feature/notifications

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Added table migrations for notification types and notification to users. Created seeds for the notification types that were on the google doc, followed the schema based on the google doc as well.
The endpoints, models, and routers were also created for both tables, they can be found in the api/notifs folder.
I already made the appropriate documentation changes to the README.md, so no need to update the documentation.

Fixes # (issue)

I'm wasn't sure if the profile router was supposed to be missing from the main branch, but since it wasn't there I thought I had to remove mine locally. The application ends up breaking, since it's required on the app.js file, so I added it back to main.

Type of change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)
[X] Bug fix, profileRouter.js is missing from the main branch.

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have removed unnecessary comments/console logs from my code
[X] I have made corresponding changes to the documentation if necessary (optional)
[X] My changes generate no new warnings
[X] I have checked my code and corrected any misspellings
[X] No duplicate code left within changed files
[X] Size of pull request kept to a minimum
[X] Pull request description clearly describes changes made & motivations for said changes

Test comment for Slack channel.


Unexpected operator error when using multidimensional array in ternary or gatekeeper statement

Describe the bug
When using the ternary statement or gatekeeper with a multidimensional array, you get an (invalid) unexpected operator error.
[ANTLR_068] Unexpected operator while parsing input text.antlers(ANTLR_068)
[ANTLR_002] Unexpected end of input; expecting operand for operator T_VFBK near "?=".antlers(ANTLR_002)

Impacted Products
Which Antlers Toolbox products does this bug apply to?

[x] Antlers Toolbox for VS Code
[ ] Formatter CLI
[ ] Antlers Prettier Plugin
[ ] Antlers Syntax Highlighting (external systems - not VS Code)

Versions and Other Plugins/Extensions
v2.6.20
To Reproduce
{{ _class = column_size > 0 ?= _column_sizes['md'][column_size] }}

If you remove the md key, you won't see any errors. Workaround is to use additional single braces like so:
{{ _class = column_size > 0 ?= {_column_sizes['md'][column_size]} }}

Expected behavior
It shouldn't show any syntax error.

Resolved in the following versions:

antlers-language-server: 1.3.14
Antlers Toolbox for VS Code: 2.6.21


Sentence similarity: The Code snippet would be blank on the Consume page after you close and reopen .mbconfig file.

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: <IP_ADDRESS>7701 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.4.4)
.Net: 6.0
Describe the bug

On which step of the process did you run into an issue:
The Code snippet would be blank on the Consume page after you close and reopen .mbconfig file.

TestMatrix
home-depot-sentence-similarity-small.csv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select "Sentence similarity" scenario and data source to complete the training.
Go to the Consume page, at this time, the Code snippet is displayed normally.
Close and reopen .mbconfig file, go to the Consume page again, at this time, the Code snippet is blank.

Expected behavior
The Code snippet should be diapled normally on the Consume page after you close and reopen .mbconfig file.
Screenshot

Additional context

The bug has been fixed on the latest main build <IP_ADDRESS>0301


Override book's title if Title is set in XML

In ComicRack XML Schema, there is a Title field that is not being used by KCC. In this PR, I changed so that if this field is set, it will automatically be used.
Also, pyinstaller is added to requirements.txt for building on M1 to avoid pyinstaller: command not found.

@vinhtq115
Thanks for your PR.
imho, we shouldn't add pyinstaller to requirements.txt
It is only needed for building an executable.
It is not needed when using the project from source
and in docker images, for example, it would add unneeded dependencies.

I have removed pyinstaller from requirements.txt. Since the building instruction for M1  did not mention about pyinstaller and appdmg, I suggest adding a Wiki page for users who want to build the binary themselves.

@vinhtq115
https://github.com/ciromattia/kcc/wiki/How-to-build-M1

@darodi I have updated the wiki page to be more specific.

Thanks for the PR


fix: popup: fixes pseudo element so it doesn't block cursor

SUMMARY:
Ensures CSS pseudo selector doesn't block cursor when over Popup
https://user-images.githubusercontent.com/99700808/230682142-54431dca-118e-4761-b228-2c0c666bffa5.mp4
JIRA TASK (Eightfold Employees Only):
ENG-48127
CHANGE TYPE:

[X] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[X] Tests for this change already exist
[ ] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Popup story behaves as expected.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@3b4a7db). Click here to learn what that means.
Patch has no changes to coverable lines.

: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
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #590   +/-   ##
=======================================
  Coverage        ?   84.88%
=======================================
  Files           ?      793
  Lines           ?    17187
  Branches        ?     6056
=======================================
  Hits            ?    14590
  Misses          ?     2531
  Partials        ?       66

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Patch release 2.3.1

The previous release didn't include the expected features, which we
suspect was due to quick successive merges.

Today We Learned. :shipit:


Audit R vignettes

One definite pending todo: for presentation purposes we can suppress annoying warnings (e.g. about the stable census version, and the deprecated special package) by annotating the markdown blocks with {r,message=FALSE,warning=FALSE} instead of just {r}

Thanks Mike! I did so for a few code blocks and completed the work in #686


added missing '}' at line 1723

The code was missing one simple parenthesis thus PowerShell was throwing error on execution.
The Script is great, keep the good work up!

Sorry, I forgot to push the fix! Thanks for the reminder


css

[x] Top-level README “Table of Contents” is updated
[x] Feature tasks for this challenge are completed
[ ] Unit tests written and passing

[ ] “Happy Path” - Expected outcome
[ ] Expected failure
[ ] Edge Case (if applicable/obvious)

[ ] README for this challenge is complete

[ ] Summary, Description, Approach & Efficiency, Solution
[ ] Link to code


Error while using shellcheck on aursift and aursync inside chroot

I'm trying to build my fork of aurutils inside a chroot, and am getting this message when running shellcheck over aursift and aursync:
shellcheck -e 2016,2174 -x aursift aursync
aursift: uaursift: hGetContents: invalid argument (invalid byte sequence)
aursync: aursync: hGetContents: invalid argument (invalid byte sequence)

I downloaded aursift from your repository into the chroot in case there was some weird encoding issue with my version, but diff reports them as being identical, and I get exactly the same error. It all works just fine outside of the chroot.
I suspect something may be wrong with my chroot and am going to recreate it from scratch tonight, but I was wondering if you'd ever encountered this issue before, and if so, how it can be fixed?

The chroot seems to not have a configured locale. Reproduce with: LC_ALL=C shellcheck -e 2016,2174 -x aursift aursync
https://github.com/koalaman/shellcheck/issues/324

Please try again with aurutils-git.

Tagged a new release: https://github.com/AladW/aurutils/releases/tag/0.6.2

Sorry I didn't get back to you sooner. This did resolve the issue for me too. Thank you.


java.lang.RuntimeException: infe not implemented (crash)

Describe the bug
Give file source call convert it crashes
java.lang.RuntimeException: infe not implemented
   at linc.com.heifconverter.iso14496.part12.ItemInfoEntry.getContent(ItemInfoEntry.kt:27)

To Reproduce
Steps to reproduce the behavior:

download heic sample from https://filesamples.com/formats/heic
try to convert crash

Expected behavior
it should convert the file
Screenshots
no screenshots needed
Smartphone (please complete the following information):

Device: android emulator
OS: pie 9

The implementation in this repo works best on Android 10 and higher. Since it uses the built-in BitmapFactory to do all the decoding.
However for Android 9 and lower, it uses a custom implementation to decode the HEIF. Unfortunately in my testing this does not support the majority of HEIF files I've come across.
I have forked this repo, rewrote it, and added a bunch of features. Including support for Android 9 and lower. You can check it out here.


Missing Digest::MD5 in META6.json?

On Linux I get:
Digest::HMAC] ===SORRY!=== Error while compiling /tmp/d3ac52c281bb0e70d0d02596efa3b087837b709b.tar.gz/Raku-Digest-HMAC/t/01
Aborting due to test failure: Digest::HMAC:ver<1.0.6>:authzef:jjmerelo (use --force-test to override)
[Digest::HMAC] -basic.t
[Digest::HMAC] Could not find Digest::MD5 in:
[Digest::HMAC]     /tmp/1699633406.7895.753.2580966633129
[Digest::HMAC]     /home/runner/.raku
[Digest::HMAC]     /opt/hostedtoolcache/rakudo/2023.10-02/x86_64/share/perl6/site
[Digest::HMAC]     /opt/hostedtoolcache/rakudo/2023.10-02/x86_64/share/perl6/vendor
[Digest::HMAC]     /opt/hoste
[Digest::HMAC] dtoolcache/rakudo/2023.10-02/x86_64/share/perl6/core
[Digest::HMAC]     CompUnit::Repository::AbsolutePath<2526469925648>
[Digest::HMAC]     CompUnit::Repository::NQP<2526409019272>
[Digest::HMAC]     CompUnit::Repository::Perl5<2526409019312>
[Digest::HMAC] at /tmp/d3ac52c281bb0e70d0d02596efa3b087837b709b.tar.gz/Raku-Digest-HMAC/t/01-basic.t:6
and indeed  Digest::MD5 is used in 01-basic.t but not listed in META6.json

Will check this out. Thanks for the report.

IIRC, Digest::MD5 is now part of Digest, which is listed. Let me check anyway.

The new version should already be available in the ecosystem. It's low-pegged to 1, so it should install the latest one that includes Digest::MD5. I'd appreciate if you checked it, and reopen if the problem persists.


python isnt installed?

i installed python and gave it every permission and followed every step perfectly, but when i try to use ''runbot.bat'' it turns blinks for about half a second with no text. After that, I tried to run ''runbot_mac'' and it said that python was not installed.
HOW DOES ANY OF THIS WORK?!

Well runbot_mac obviously won't work if you're running it on Windows. Try deleting the text shown below inside runbot.bat:

Join our Discord server if you require help, as we check that more often: https://discord.gg/bots


homework 2 greater than or equal to

Either the question should be rephrased or the code should be changed - it asks about days above 0 degrees but the answer includes temps at 0 degrees. There are 218 days at or above but only 159 above.

How many data points are from days where the maximum ground temperature got above 0 degrees Celsius? What percent/proportion do these represent? Use:
filter() and nrow()
group_by() and summarize() or
sum()

How many data points are from days where the maximum ground temperature got above 0 degrees Celsius?
nrow(mars %>% filter(max_ground_temp >= 0))
[1] 218

thank you!!

This is done


Fixed order for parameters in the docs

For example, in Mesh3DGrid, it would be nice if h1, h2, and h3 were displayed in that order.

See relevant discussion for traitlets here: https://github.com/ipython/traitlets/issues/148

With return to properties, parameters are alphabetized. This should be satisfactory for now.


Give access to order attribute with a setter

Hello
Thanks for your very funny dashboard component.
But we cannot restore a previous widgets order  defined by the user.
Actually the attribute "order" is "readonly", a setter or another way will be great.
Thanks

Hello, the order depending only on the order of addition into the dashboard, so to restore the order, just add your widgets under the dashboard on the order to restore, no need more

Ok but if i understood correctly the api addItem, i am obliged to define a specific Widget Angular Component for each widget that i want to instantiate into the dashboard.
I would use a widgets list defined by tags into the html source of the dashboard and let it instantiate them. I had not defined a specific widget component for each of them.
After retrieve the order defined by the user I would restore it by any way you can suggest to me.
I can retieve the widgets collection with your getWidgetById api but i cannot restore it after clearing because addItem requires a Angular component as parameter.
But perhaps I make a mistake in understanding.

I solve the problem with dynamic widget content
Thanks


Clarify meta; cleanup some plugins; add wash info

I think we should take some time to double-check the plugin implementations and make sure they're consistent, clean, and that we're using meta where we're supposed to. As an example of the latter, would meta make sense for K8 contexts? I see some sort of object being returned in https://github.com/puppetlabs/wash/blob/master/plugin/kubernetes/root.go#L25-L40


Version string confusion for 0-versions

Reading the section on Semantic Versioning in the project readme, it seems the description (a) is in conflict with the examples (b) in that 0-versions seem to be treated differently.
(a)

Note: When you specify a version without an operator, dep automatically uses the ^ operator by default.

(b)

1.2.3 becomes the range >=1.2.3, <2.0.0
0.2.3 becomes the range >=0.2.3, <0.3.0
0.0.3 becomes the range >=0.0.3, <0.1.0

Following (a), a constraint"0.2.0" would be equivalent to "^0.2.0", yet dep will not, as it seems, fetch a version 0.3.0. Digging deeper,

Refer to the semver library documentation for more info.

https://play.golang.org/p/BB934lUCEj
The semver library seems to accept 0.3.0 as valid for the constraint ^0.2.0.
If dep behaves as intended in that it does not accept 0.3.0 for a version string saying "0.2.0", it would be helpful if the documentation could explain this in more detail.
Versions:

Go go version go1.9rc2 darwin/amd64
dep v0.3.0-142-g6ca8a48

As pointed out by @sdboyer in #vendor on Slack at 2017-08-18T13:56:54Z, dep is using NewConstraintIC on the 2.x branch of the semver library, which treats versions below 1.0.0 differently.
Updated example to illustrate: https://play.golang.org/p/zZcvI_2bCO
It would perhaps still be of use to clarify the docs to explain this more clearly.

For comparison, an example for a >1.0.0 constraint:
https://play.golang.org/p/90qaA0TCyN
And both results side by side:
Constraint: "0.2.0"

Check("0.1.0") -> 0.1.0 is less than the minimum of ^0.2.0
Check("0.2.0") -> match
Check("0.3.0") -> 0.3.0 is greater than or equal to the maximum of ^0.2.0
Check("1.0.0") -> 1.0.0 is greater than or equal to the maximum of ^0.2.0

Constraint: "1.2.0"

Check("1.1.0") -> 1.1.0 is less than the minimum of ^1.2.0
Check("1.2.0") -> match
Check("1.3.0") -> match
Check("2.0.0") -> 2.0.0 is greater than or equal to the maximum of ^1.2.0

yes, it would definitely be worth updating the docs! a PR to do so would be awesome 😄 😉 🎉


can't type numbers in html files

Hi, i have clean install latest atom on Ubuntu 14.04 64b. When i just save any file as .html file, i can't type numbers in that file anymore. All simbols like $#% works, but no numbers (from enhanced side keyboard also).

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:


Provenance

Generating  provenance metadata when editing an item:
Suggestions for addition based on existing data in clarin5:
11.	Add new bitstream - problem with finding right place for creating provenance, maybe the way is create new endpoint
12.	Add new license
13.	Update existing license
14.	Remove existing license
15.	Access Control for metadata and bitstream – EMBARGO
16.	Rejacted by and rejacted reason
17.	Submitter id changed
18.	Submitted by
19.	 Approved by
Suggestions for addition based on Item editor
:
20.	Move item to another collection
21.	Make item non-discoverable
22.	Manage mapped collections
23.	Edit item’s authorization policies

Access Control for metadata and bitstream – OPENACCESS, ADMINISTRATOR, LEASE

This issue is solving in https://github.com/dataquest-dev/DSpace/issues/643.


[WIP] Acknowledgements

@fdoflorenzano would it be possible to have an additional property for each person, so instead of:
        {
          "name": "Editing and Video Production: Mathieu Blanchette",
          "url": "https://mathieu.com"
        },

We'd have:
        {
          "name": "Mathieu Blanchette",
          "url": "https://mathieu.com",
          "role": "Editing and Video Production"
        },

Then the layout could look more like the following (with the url only linking to the name?)

@shiffman just pushed here the addition of role!


Crash while BP is trying to mixin to BeehiveBlockEntity in 1.15.2

https://hatebin.com/zuefrgqbrn
org.spongepowered.asm.mixin.injection.throwables.InjectionError: LVT in net/minecraft/block/entity/BeehiveBlockEntity::releaseBee(Lnet/minecraft/block/BlockState;Lnet/minecraft/nbt/CompoundTag;Ljava/util/List;Lnet/minecraft/block/entity/BeehiveBlockEntity$BeeState;)Z has incompatible changes at opcode 239 in callback net/minecraft/block/entity/BeehiveBlockEntity::applyNectarEffects.
Expected: [Lnet/minecraft/util/math/BlockPos;, Lnet/minecraft/util/math/Direction;, Lnet/minecraft/entity/Entity;, Lnet/minecraft/entity/passive/BeeEntity;]
Found: [Lnet/minecraft/util/math/BlockPos;, Lnet/minecraft/util/math/Direction;, Z, Lnet/minecraft/entity/Entity;]
This is occurring in my development environment with 0.4.32+build.292-1.15 Fabric and 1.0.2+1.15.1 BeeProductive. Please let me know if you need more information or for me to try something!

not again.

Lol I can hear the frustration from here 😂

seems to be picking up a boolean from somewhere and expecting it in the capture :-/


Add way to configure keyboard shortcuts

Please, ensure that the desktop app get proper treatment ^^ I'm particularly missing menu bindings à la "Alt+...", etc.

No need to comment to say "me too". Thumbs up on the original post is the convention to vote for it

Hello,
This would fix an issue we have on MacOS: it uses at least 1 OS-native shortcut, Cmd+M, which is meant to minimize the current window, the kind of shortcut we use dozens of times each day.

This would also solve the issue where the well known shortcuts have been changed without giving the users a way to revert the faulty changes back (see https://github.com/jgraph/drawio/issues/3632).


Track: On Framework boot: DPC: RP PIO log size 0 is invalid [Firmware Bug]: TMP interrupt not working, polling instead

See Benjamin-Loison/cinnamon/issues/65.

As I am unsure about the string, specifying a screenshot would be welcomed.
Could try booting the system in a virtual machine to check if this message comes from the motherboard firmware.


nothing provides gstreamer1.0-plugins-bad-opengl

As in https://github.com/OSSystems/meta-gstreamer1.0/issues/20, building a WPE 2.22.0 image with Yocto master yields this error.
Error:
 Problem 1: conflicting requests
  - nothing provides gstreamer1.0-plugins-bad-opengl needed by wpewebkit-2.22.0-r0.cortexa7t2hf_neon_vfpv4
 Problem 2: package cog-git0-r0.cortexa7t2hf_neon_vfpv4 requires libWPEWebKit-0.1.so.2, but none of the providers can be installed
  - conflicting requests
  - nothing provides gstreamer1.0-plugins-bad-opengl needed by wpewebkit-2.22.0-r0.cortexa7t2hf_neon_vfpv4

The answer in there already suggests a fix:

The OpenGL plugin was moved to -base in 1.14. So you need gstreamer1.0-plugins-base-opengl .

Should the logic for where to get the opengl plugins depending on the gstreamer version be added do the wpewebkit recipe?
Thanks!

Yes. I don't know if that's doable though? If gst 1.12 is selected we want opengl from -bad, otherwise if 1.14 is selected we want opengl from -base... If you find how to do that please file a PR :)

I asked about it on #yocto and they recommended:

#khem cramalho: you should just track release branches and match them with oe-core release branches

With this workflow essentially this meta layer (ideally) would be branched out to the versions (rocko, sumo, etc) and master would have the -bad -> -base change to match oe-core's gstreamer naming until thud is made stable and it is branched again.
Ok. A lot of rethinking on the repository workflow over one problem but I wonder if this is the usual yocto workflow? I'm new to Yocto btw.
It seems branches were created for krogoth, jethro and fido, but stopped doing this afterwards.

Yeah, right, release branches are a good approach indeed. Many layers do that. Until which release should we use 1.12? Rocko?

https://github.com/Igalia/meta-webkit/pull/47
rocko branch is already pushed.

Yeah, right, release branches are a good approach indeed. Many layers do that. Until which release should we use 1.12? Rocko?

1.14 is quite recent, right? Up until sumo 1.12 is used. Now in master (which will become thud) 1.14 is used.
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-multimedia/gstreamer?h=sumo
So I think until sumo 1.12 should be used. Then 1.14 in current master and forward.

Hm true, but OSSystems have a rocko branch shipping 1.14, maybe we could state in the README this is a highly recommended layer.

https://github.com/OSSystems/meta-gstreamer1.0/tree/rocko/recipes-multimedia/gstreamer

Yes, I think this layer would be really useful for compatibility with versions older than master. Especially for compiling with MSE, which now requires gst 1.14

As the README points to the Wiki, I edited the Wiki :) https://github.com/Igalia/meta-webkit/wiki

Thanks!

So if meta-gstreamer1.0 becomes a recommended dependency we can just assume gst 1.14 is used for rocko sumo & thud. That simplifies things.


Enable contrib classes on Linux

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

This fixes issue #17.

@conda-forge-admin, please rerender


Please consider adding jax.numpy.divide

Currently, jax.numpy.divide points to jax.numpy.true_divide.  This means that it doesn't support the parameters where and out, which can be used to conditionally set the output without warnings:
In [3]: import numpy as np

In [4]: np.divide(np.ones(4), np.arange(4))
<ipython-input-4-ddd914450938>:1: RuntimeWarning: divide by zero encountered in true_divide
  np.divide(np.ones(4), np.arange(4))
Out[4]: array([       inf, 1.        , 0.5       , 0.33333333])

In [5]: np.divide(np.ones(4), np.arange(4), where=np.arange(4) > 0, out=np.zeros(4))
Out[5]: array([0.        , 1.        , 0.5       , 0.33333333])

Thanks for the request! The out and where keywords are properties of numpy's ufuncs, and JAX wrappers generally do not support these. In the case of out, it's for good reason: JAX arrays are immutable, so it's not possible to update the out array in-place with the result.
In the case of where, JAX offers the same functionality by composition. In numpy, compositional approaches can be inefficient because they involve creating temporary arrays; this is one reason numpy ufuncs provide options like where. In JAX the XLA compiler can optimize sequences of operations, so composition is not a problem.
In JAX, you could do the above operation like this:
>>> import jax.numpy as jnp
>>> x = jnp.ones(4)
>>> y = jnp.arange(4)
>>> jnp.where(y > 0, jnp.divide(x, y), 0)
DeviceArray([0.        , 1.        , 0.5       , 0.33333334], dtype=float32)

@jakevdp Thanks for the thorough explanation!  The only problem with your workaround is that if JAX_DEBUG_NANS is true, then it will raise if you try to do jax.divide(y, y)—even if you're inside a jnp.where.
I've been trying to think of a perfect workaround.  Any ideas?

If that's a concern, you could use a double where:
jnp.where(y > 0, jnp.divide(x, jnp.where(y != 0, y, 1)), 0)

This pattern also turns out to be helpful in the case of avoiding NaNs in autodiff.

@jakevdp Nice, that's really clever!  I guess I'll wrap that up in a function like this:
def divide(x: Array, y: Array, *, where: Optional[Array] = None, out: Optional[Array] = None):
    if where is None:
        return jnp.true_divide(x, y)
    x_prime = jnp.where(where, x, 1.0)
    y_prime = jnp.where(where, y, 1.0)
    quotient = jnp.true_divide(x_prime, y_prime)
    return jnp.where(where, quotient, out)

I think numpy's use of out here is a quirky since it's both an input and the output.  Someone over-valued optimization.

I think it would be confusing because it's not possible for the result to be written to the out array, which is the main purpose of this argument.
And without out, there's no way to specify a default value for where, so implementing that argument alone wouldn't make much sense.

Okay, fair enough, I'll just close this then.  Thanks for pointing me in the right direction.

@NeilGirdhar  This might not be directly relevant, but I thought I'd mention that you can get finer-grained control over nan-debugging if you use the jax.debug_nans context manager rather than the flag:
In [1]: import jax

In [2]: jax.numpy.divide(0, 0)
Out[2]: DeviceArray(nan, dtype=float32)

In [3]: with jax.debug_nans(True):
   ...:     jax.numpy.divide(0, 0)
---------------------------------------------------------------------------
FloatingPointError                        Traceback (most recent call last)
...snip...
FloatingPointError: invalid value (nan) encountered in div

In [4]: with jax.debug_nans(False):
   ...:     jax.numpy.divide(0, 0)
   ...:

In [5]:

@mattjj Oh that is helpful, thank you!


[MODULE] Vampire Projectiles - Life

Boss Module - Vampire Projectiles
Basic Functionality:
When a projectile of this kind damages an enemy ship (not an asteroid or some other not-enemy target), the player will restore health proportional to the amount of damage done.
Stats: Projectile damage is decreased to 80% of its original value
Level 1: player recovers 10% of inflicted damage as health.
Subsequent Levels: + 5% of inflicted damage. + 5% damage.
Note: values are guidelines only, please feel free to modify them to see what looks good, feels powerful (it is a boss module) but not game-breaking.
Note: values are quite low as presently there are no drops or other easy ways for the player to recover health, so health steal is very powerful. If this changes, vampire projectiles should recover more health. (Alternatively, if 10% is too much, please lower)

Task Estimation (time): 3
Task Estimation (difficulty): easy
Risks: Unfamiliar with targeting multiple entities in one module (projectile and ship).
Risk Resolution: Will ask for help if stuck

Actual time taken: 2.5 hr
Actual difficulty: Very easy
Testing procedure: Playtest
Test Pass Condition(s): Ship health is healed when projectile hits enemy ship. I will check this by using the health bar and the Debug Log.
Risks: Ship entity is given to Projectile entity to apply heal.
Risk Resolution: Set value of Ship entity within Projectile entity to null so only comes into play when a module specifically targets it. Left a comment describing what it's for.


Implement compression support in ObjC

This is an issue to track progress on the compression support in ObjC

Duplicate of #2433


Fix uncaught exception when open file dialog is cancelled

Fixes an uncaught exception when the open files dialog is cancelled. The openPaths function just needs to check to ensure initialPaths isn't null or empty when called (issues #10315 and #10308).
Should probably add a spec for this?

Yes, please add specs.
Out of curiosity, what was the uncaught exception?

I can't reproduce the aforementioned issues on master. It seems like they both refer to an older version of Atom: can you confirm this is still an issue as of the latest version? If yes, is there a way of reproducing this consistently?
Thanks, @drewmnoel! 🙇

Just tried reproducing using the Open File and Open Folder dialogs (but not Add Project Folder) but could not reproduce.  Once the dialog appeared I would Esc to cancel it.

Hmm, I can reproduce this 100% of the time. It doesn't cause a crash, but it does log an error:
$ atom --version
Atom    : 1.9.0-dev-21a5ef6
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0

$ apm --version
apm  1.10.0
npm  2.13.3
node 0.10.40
python 3.5.1
git 2.8.3

$ atom -f --safe /tmp
[7111:0525/092200:ERROR:browser_main_loop.cc(217)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
App load time: 1277ms
[7111:0525/092204:INFO:CONSOLE(52)] "Window load time: 1438ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (52)
[7111:0525/092205:INFO:CONSOLE(0)] "/deep/ combinator is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.", source:  (0)
Cannot read property 'length' of undefined
TypeError: Cannot read property 'length' of undefined
    at AtomApplication.<anonymous> (/usr/share/atom/resources/app.asar/src/main-process/atom-application.js:718:40)
    at AtomApplication.module.exports.AtomApplication.openPaths (/usr/share/atom/resources/app.asar/src/main-process/atom-application.js:723:10)
    at /usr/share/atom/resources/app.asar/src/main-process/atom-application.js:1054:24
    at Function.wrappedCallback (/usr/share/atom/resources/electron.asar/browser/api/dialog.js:89:14)

The exception is thrown in the following situations:

"Open File", "Cancel"
"Open File",
"Open Folder", "Cancel"
"Open Folder",

It doesn't trigger on the "Add Project Folder" situation, however.

Thanks, @drewmnoel! I'm 🆒 with merging this after solving the merge conflicts. ✨

Thanks, @drewmnoel! ✨


Come up with plan for roll out

We'll need to figure out a plan for rolling this out. We should discuss with Clair how we should communicate updates to Source folks

Rolled project out to the team today.

Yayayayay!!!!!!!!!
On Fri, Dec 17, 2021 at 10:14 AM Kyle Hoehns @.***>
wrote:

Rolled project out to the team today.
—
Reply to this email directly, view it on GitHub
https://github.com/sourceallies/hacker-rank-queue/issues/45#issuecomment-996844902,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYEYDJ2V2QOLMJOJERELW3URNOXRANCNFSM5GBDASLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

--
*Clair Williams-Vavra, M.A. *
515-339-1640
@.***
[image: Facebook icon] https://www.facebook.com/ClairBiddy14  [image:
LinkedIn icon] https://www.linkedin.com/in/clairwilliamsvavra/


Fix multiplying polynomials, addition bug, simplify / optimize code

Multiplying did not work due to get_monomial() calls:
a = Polynomial(1, 2, 3) * Polynomial(1, 2, 3)
>>> Traceback (most recent call last):
>>> [...]
>>> AttributeError: 'Polynomial' object has no attribute 'get_monomials'

Adding 0 to a value would return the value itself, which would allow the initial value to be modified.
a = Polynomial(1, 2, 3)
p = a + 0
p.a = 5
print(a.a)
>>> 5

I  optimized other parts of the code and reduced the number of redundant calls (eg. return self + Constant(other) would then call add again, which is inefficient)
I also implemented slices, so it is now possible to get a portion of the coefficients from a Polynomial and or set them (eg. do Polynomial(1, 2, 3)[0:2] to get 3, 2.)

All fixed.


Bitwise: Introduce method are_bits_on.

As form of improvement I introduced the method are_bits_on in bitwise.rs to check if a certain sequence of bit is all set to 1; In this way it is possible to get rid of redundant code in SingleDataTransfer.

Great!


Fixed the thread issue

https://pastebin.com/Fh9mkxHs
Also: don't forget to add the transform function and your includes
gl
upit fpomh htrsy '[

Thnks


Why does subsribe take fetch but ubsubscribe takes authenticatedFetch?

In most Solid libraries, passing an authenticated fetch function commonly uses the fetch parameter. For both internal consistency and aligning with the convention of other libraries, I think the parameter passed to unsubscribe should also be called fetch. If there is a good reason that unsubscribe renames the parameter, it would be helpful if that was documented in lib/unsubscribe.

I'll not this for an update.


[BUG] nightly integration test failed OOM kill in JDK11 ENV

Describe the bug
internal pipeline rapids_integration-dev-github #758 #762
the executor failed test cases due to lost executor.
After investigation, we found that the memory usage of testing w/ jdk11 is abnormal, and it exceeded the resource limitation of our test ENV.
all other combinations took around 45~50G memory at most,
but jdk11 one consumed more than 55G and caused the OOM kill, this seems always reproducible

Steps/Code to reproduce bug
Please provide a list of steps or a code sample to reproduce the issue.
Avoid posting private or sensitive data.
Expected behavior
A clear and concise description of what you expected to happen.
Environment details (please complete the following information)

Environment location: [Standalone, YARN, Kubernetes, Cloud(specify cloud provider)]
Spark configuration settings related to the issue

Additional context
Add any other context about the problem here.

The default garbage collector changed to G1 in JDK 11. JDK 8 default is Parallel Scan.
@pxLi Could you try setting spark.executor.extraJavaOptions="-XX:+UseParallelGC" and see if that helps?

The default garbage collector is different for different JDK versions:

JDK 8 default is Parallel.
JDK 11 default is G1
JDK 12+ default is Shenandoah

@pxLi Could you try setting spark.executor.extraJavaOptions="-XX:+UseParallelGC" and see if that helps?

sure, I will take a try in the CI

no more oom reporting. closing this for now


To Do List

@praeclarum  Do you have any todo list or priority list?
I would love to work on Xamarin.Forms part.

You can see Issues labeled as enhancements.
On the other hand, if you have something in mind that is not registered, you can create an Issue and Frank and the community will help and review it.

Thank you for your interest. We now have status doc that you can choose from. https://github.com/praeclarum/Ooui/blob/master/Documentation/OouiFormsStatus.md
Thanks for helping!


Repo sync for protected CLA branch

The pull request is created from master637604991402649583 to master to fix git push error for protected CLA branch

@Taojunshen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add support for parsing *FLAGS with shlex

Hello,
This PR adds support for parsing *FLAGS with the shlex crate. This effectively fixes #847, and means *FLAGS with spaces designed for meson, make and cmake will work with no extra configuration.
In order to preserve compatibility with existing setups, the behavior must be opted into with CC_PARSE_FLAGS_WITH_SHLEX, or the parse_flags_with_shlex method on the Builder.

I'm wary of adding a dependency since it literally always causes us big problems but I don't see why this one would so I suppose we can give it a shot.
I think I'd prefer this be optional. We probably also shouldn't mention shlex in the interfaces because we could change the implementation to another crate (or no crate).

We probably also shouldn't mention shlex in the interfaces because we could change the implementation to another crate (or no crate).
Good idea, I changed the env var to be CC_SHELL_ESCAPED_FLAGS.

I think I'd prefer this be optional
Do you mean the dependency being optional / gated behind a feature? If it might hurt the user experience a bit, but I think it would be fine since callers of cargo who set CFLAGS could use --config

Do you mean the dependency being optional / gated behind a feature?

Given how small shlex is (no dependency, no build-script), I don't think we need to a feature for it.
In the future we could vendor it, given that the code for splitting based on shell isn't very large, so I don't think it's necessary.

Given that there's no objection, I'd merge it in


Build fails with nativescript-dev-webpack@rc

Environment
package_json.txt
Describe the bug
After updating to  nativescript-dev-webpack@rc the app cannot build anymore.
To Reproduce

npm i -g @angular/cli
npm i -g @nativescript/schematics
ng new --collection=@nativescript/schematics TestApp --shared
tns run iOS the app runs on device
npm i nativescript-dev-webpack@rc --save-dev
node_modules/.bin/update-ns-webpack --deps --configs
tns run iOS the app build exits with error:
Log:
log.txt

#260


Make timings & meta info easier to review

Both of those pieces of information are available (thank you), but are difficult to access for responses with large bodies. Currently, to review this, one has to open the request info pane and scroll past the response body (however long it might be).
Suggestion

add timing and meta to hover preview,
and/or move them (and perhaps test results too for consistency) above the response body when opening the request info pane.

I would have made timings, testResults and meta more easily accessible. Do you think this is so good?

I noticed it yesterday (well my yesterday anyway) thanks!
This works very well for me, and the total time is also shown above. Typically, besides the body, I care about the status code, test summary, total time, content size (all of which are shown at the top)...and will typically only look at the rest if one of the above bothers me. :)

Thx:-)


Talisman Config not updated from superset_config.py

When setting content-security-policy options through the superset_config file these are not accepted during startup
I am running superset from scratch (3.0.0. installed via pipenv from pypi) und python3.10. my superset config file as dev environment
How to reproduce the bug

Go to superset_config and amend / change the talisman content-security policy with 3rd party websites like (I copied this also under TALISMAN_DEV_CONFIG):

TALISMAN_CONFIG = {
    "content_security_policy": {
        "default-src": ["'self'"],
        "frame-src": ["'self'", "https://service.xxxx.com"]
        "img-src": ["'self'", "data:", "https://service.xxxx.com"],
        "worker-src": ["'self'", "blob:"],
        "connect-src": [
            "'self'",
            "https://api.mapbox.com",
            "https://events.mapbox.com",
        ],
        "object-src": "'none'",
        "style-src": [
            "'self'",
            "'unsafe-inline'",
<EMAIL_ADDRESS>        ],
        "script-src": ["'self'", "'unsafe-inline'", "'unsafe-eval'"],
    },
    "content_security_policy_nonce_in": ["script-src"],
    "force_https": False,```

Start superset
Create markdown chart with img-src / frame-src pointing to third party website

-

Load page
Links are NOT loaded and browser console shows (directive in error message does NOTinclude changes to content-security-policy):

Refused to load the image '<URL>' because it violates the following Content Security Policy directive: "img-src 'self' data:".

However changing the config.py code directly can be used as a workaround:

change the superset/config.py file directly in the package directory.
Repeat steps 2 & 4 with fully refreshing browser  - content is loaded

Expected results
content-security-policy should be read from the superset_config.py file and b e considered during startup
Actual results
settings are ignored and can only be changed in superset source code directly
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

browser type and version: Edge Version 117.0.2045.60 (64-Bit)
superset version: 3.0.0
python version: 3.10.13
node.js version: node not installed
any feature flags active:

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.

Even I face the same problem... Unable to load image file in Superset 3 dashboard.

Same here, but with the added bonus that including the TALISMAN_CONFIG block into my superset_config.py file (running a docker instalation of 3.0.1), makes superset crash on boot with a load of python errors.

same here. Version 3.1.0

TALISMAN_CONFIG is in there by default now, so it shouldn't be crashing (we would hear a LOT about that).  You should be able to set img-src to be 'self' data: <URL> and it should work. Closing this since it's a config issue rather than a bug, but happy to revisit if needed.

@rusackas could you please kindly point to the manual where 'content_security_policy' and other TALISMAN_CONFIG kvs can be set using helm? I've got nowhere.
Thanks,

I don't know if there is such a guide, actually. I also don't use Helm (I live in a luxurious world where @craig-rueda and @dpgaspar do the infra magic for Preset), but maybe @villebro or @nytai can suggest something. If this does get resolved, we'd love to see the addition of more details in the documentation if you're up for it (cc @sfirke).

In general for every deployment method it would be nice if we added both instructions specific to that method for where to put superset_config.py (I have a PR open to make this clearer for PyPI) and a troubleshooting step for users trying to verify that file is getting picked up.
I have sometimes advised people to enable a feature flag, then look to see if that corresponding functionality is enabled in the application. But we can do better and this comes up a lot.

same here. Version 3.1.0

resolved

I am unsure why this was closed as completed when the core issue was not addressed. Per the documentation of superset "All the parameters and default values defined in superset/config.py can be altered in your local superset_config.py". Yet as of this moment the Talisman configuration defined in the local superset_config still does not override superset/config.py.

@chrisvnimbus how are you deploying Superset? There isn't something specific to Talisman here but it sounds like your superset_config.py file is not placed where it can be picked up by the application upon startup.

All my superset_config settings are transferred correctly, yet the Talisman configuration does not seem affected. Other overrides in the file such as SECRET_KEY and the SQLALCHEMY_DATABASE_URI are loaded correctly, so the issue is not with my config file. However, the web frontend seems unaffected when it comes to any specified content security policy defined therein.

I have my TALISMAN_CONFIG in my superset_config.py with my other settings and it's all getting picked up fine.  I'm on Superset v4.0.2 but this has worked since Talisman got introduced.  So I don't think it's that this simply doesn't work inside Superset.
Let's see, want to try temporarily setting TALISMAN_ENABLED = False in your superset_config.py as a test?  I'm just trying to think of things to try.

So is this two problems, then?  1) You have set TALISMAN_ENABLED = False and got confirmation in the form of the warning, yet the default security policy is still applying.  2) The TALISMAN_CONFIG you specify in superset_config.py is not getting applied, despite being sure that this file's other settings are being honored.
What version of Superset is this?  Do you see anything relevant in the logs upon startup?  And https://github.com/apache/superset/blob/master/superset/initialization/init.py#L590 seems to be the relevant part of the codebase if you want to look for possible problems.

This is the latest version of Superset, running from the composed docker image at apachesuperset.docker.scarf.sh/apache/superset:${TAG:-latest}. It is delivered the custom superset_config .py in a volume mounted to /app/configs, which is specified in the environment variable SUPERSET_CONFIG_PATH, for good measure also in CONFIG_PATH_ENV_VAR, and the mount path /app/configs is added to PYTHONPATH.
While the backend part of Superset grabs this file succesfully and retrieves among other things the SECRET KEY and database connections from this, it seems the frontend related talisman configurations are not grabbed.
I am currently making a custom build from scratch and deploying the different containers seperately, but it's still strange that the delivered 'fast start' compose yaml ends in a container where only part of superset accepts te overrides made in the local superset_config.

Can you see a version number in the UI or from running a command in the container? If that version is 4.0.2 (the latest official release) I'm still baffled but if it's 0.0.0-dev the nightly build then perhaps an error has crept into Superset.

It is in fact version 4.0.2.

For anyone still facing this, I had DEBUG=True in my Superset configs, which makes TALISMAN_DEV_CONFIG override TALIMAN_CONFIG: https://github.com/apache/superset/blob/18c2376b5022afb9214314289636b0480081806a/superset/initialization/init.py#L617


SIGTERM / SIGINT not supported by windows

When running websocketd on windows, when a client disconnects, I get ERROR "SIGINT unsuccessful to [pid]: not supported by windows" and ERROR "SIGTERM unsuccessful to [pid]: not supported by windows" and the command to execute is never terminated.

Surely I am missing something here? How do you get commands spawned for each client to be killed off?
I have a (poor) work around which is to have the client periodically send data to the command, and the command programmed to terminate itself if it gets no stdin for a while.
But is there a better way?

Interesting... You should not see pile up since KILL will eventually take place and it works on Windows... But there is a code that should not send signals that not supported  in first place. So it might be a bug to fix...

Ah yes this is actually a problem with antivirus which was interceptting command and calling it as a child, so websocketd was killing the antivirus instance for the command, and the actual command was just left to run.
I blame mcaffee.

I'll reopen just to not forget to check this at some point.


Webhooks not allowed for global service

https://github.com/rancher/rancher/issues/7629
@cjellick

LGTM


Publish 1.7.2 (Dec 3, 2024)

[x] Use durable messages inside durable queues
[x] Tweak the parsing of single-word definition

tests ok


Migration from discord.js

Hey!

I have a few questions:

Are there ANY API differences and gotchas I should be looking out for while I switch to this library, or is it literally just a drop-in replacement without caching? I assume I do have to make sure data is in cache now before pulling it, which i could basically avoid before since discord.js caches everything, but I mean anything other than that.
Would you be interested in migrating discord.js-light's codebase to Typescript? If i ever find the courage I might be interested in doing that, doesn't seem like a huge amount of work from what I've seen.
Are github issues the best way to contact you? In case I have problems & bugs as I migrate my project, I wanna make sure I ask in the right place.

hey there,
All differences should be explained in the readme unless i forgot something. As for typescript, im personally not a ts user, and since discord.js itself is not using it (yet) i didnt give it much thought either, but feel free to explore such endeavor. Im usually more active on discord, feel free to dm me or join my support server, otherwise i usually respond here as well within a day or two.
cheers!


Hello from ScratchABit, "interactive disassembler with IDAPython-compatible plugin API"

I bet you implemented more of idaapi: https://github.com/pfalcon/ScratchABit/blob/master/idaapi.py
But I have cute UI attached ;-) :

hey @pfalcon
You're project is quite neat; I've kept my eyes on it over the years.
Do you see a way that we can integrate our projects? Like perhaps to initialize a ScratchABit workspace from an existing IDB?

Ah cool! I wished I'd have known about your project earlier. At least, as it's from this summer, I didn't miss it by a lot.

Do you see a way that we can integrate our projects?

Well, I'd love if there was a way ;-).

Like perhaps to initialize a ScratchABit workspace from an existing IDB?

Well, such a feature would be interested for someone regularly using IDA, or having many IDB files. I'm neither. I'd even think that the better approach would be to write a converter from IDB to  ScratchABit's textual DB format.
But I find "example: run an existing IDAPython script" section of the README to be really cool, that's what I'd target for ScratchABit, except that myself I didn't have a strong need for going beyond a single CPU plugin so far. But I submitted https://github.com/pfalcon/ScratchABit/issues/26 to remind to try to reuse python-idb implementation of the API rather than code it from scratch. It would be cool is someone with enough interest tried to run some plugin with ScratchABit and added missing pieces (which are many) ;-).
I won't be able to lead that anytime soon I guess, the next goal for ScratchABit is to develop a Capstone-based CPU plugin(s). But now that ScratchABit is mostly "done" (new functionality would be added via plugins), I switched to trying to get some juice out of 2.5 years of ScratchABlock development, and decompilation is of course much less trivial than writing a TUI around a disassembly module ;-).

closing as discussion appears complete


Matrix Multiplication

Title of article
Write a GO program to print multiplication of 2 matrices.
Additional information
First matrix
1  1  1
2  2  2
3  3  3

Second matrix
1  1  1
2  2  2
3  3  3

Product matrix
6  6  6
12 12 12
18 18 18

Code of Conduct

[X] I have read and agree to the Codinasion project's Code of Conduct

working on it


Is there a way to change Recipe Order for Radiation Shielding for Armors?

I either want to disable them all but still allow them to be crafted (so hide it) or a way to order it better so they show up behind the armor recipes.
Thanks :)

The shielding recipes have been pushed back to post-initialistation and so should be registered after all other recipes for the armour and appear at the back of the JEI recipe list :)

Thanks mate you been awesome!


Better console handling

Instead of using bare Serial.print() calls, write log() functions:

log(int)
log(char *)
logln(int)
logln(char *)

Shorter code in the body and more centralized control - we can turn off logging in 4 places.
Or maybe we can use C macros?

No, didn't do this due to limited C compiler features.
Did switch to using Serial.printf() though.


enable github action testing

This pull request enables continuous testing using Github Actions.
Once #23 is merged, you can enable macOs as well.

Closing this PR; I'm going to open a new PR for review that includes Windows, macOS and Linux.


Remove rav1e::Frame::new()

It is a big footgun (#2461) and should be avoided.

Coverage increased (+1.6%) to 82.418% when pulling 6c640035fa1fa0d910563d13b16ef267a4b6e87e on rust-av:remove-frame-new into df5817668c5d72210225c22e6191bf7a2bbec6ca on xiph:master.

Thank you, it landed yesterday by mistake.


out put is broken at png with alpha channel

the model is trained for grayscale img
so we have to convert or alert for png with alpha channel img

I have one question. Not sure where to ask it so I try here and hope I get a answer. If I install this localy. Will paintsschainer be able to output larger images? Like if my base image is 3000 to 3000 pixels would paintschainer put out a colored version of it with the same size / resolution?
I tried the docker installation route but that gave me only the web version it seems!?
also about installing this on windows. Step 3 is confusing to me. “Deep learning SDK” What exactly do I need to download and install here since there are a lot of tools under this tab im kind of confused.
Hope you can help me. thanks

Dont ask entirely different topic from title. Make new Isuues.

the input image size is decide in the code at img2imgdataset.py.  so if you want to change you have to change the code.
you need CUDA & cuDNN


when postgresql down,some requests  failed

Summary
I'm using kong 1.1.1 and test the  Datastore Cache feature. So I stop postgresql-11 and continue request kong proxy server, the result is some requests succeeded but others failed.
Steps To Reproduce

Default config  and all normal run.

db_update_frequency = 5
db_update_propagation = 0
db_cache_ttl = 0
db_resurrect_ttl = 30

Stop postgresql

# systemctl stop  postgresql-11

do some requests

while true ;do curl -i  -H"Host:testserver.com" 'http://<IP_ADDRESS>:8000/';sleep 1;done
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 36
Connection: keep-alive
Server: openresty/<IP_ADDRESS>
Date: Wed, 17 Apr 2019 03:16:15 GMT
Last-Modified: Fri, 01 Mar 2019 12:18:19 GMT
X-Kong-Upstream-Latency: 2
X-Kong-Proxy-Latency: 1
Via: kong/1.1.1

<IP_ADDRESS> port 9991 serving....
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 37
Connection: keep-alive
Server: openresty/<IP_ADDRESS>
Date: Wed, 17 Apr 2019 03:16:16 GMT
Last-Modified: Wed, 06 Mar 2019 02:56:18 GMT
X-Kong-Upstream-Latency: 1
X-Kong-Proxy-Latency: 0
Via: kong/1.1.1

<IP_ADDRESS> port 9991 serving....
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 37
Connection: keep-alive
Server: openresty/<IP_ADDRESS>
Date: Wed, 17 Apr 2019 03:16:17 GMT
Last-Modified: Fri, 12 Apr 2019 07:32:35 GMT
X-Kong-Upstream-Latency: 1
X-Kong-Proxy-Latency: 0
Via: kong/1.1.1

<IP_ADDRESS> port 9991 serving....
HTTP/1.1 500 Internal Server Error
Date: Wed, 17 Apr 2019 03:16:18 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Content-Length: 42
Server: kong/1.1.1

{"message":"An unexpected error occurred"}HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 36
Connection: keep-alive
Server: openresty/<IP_ADDRESS>
Date: Wed, 17 Apr 2019 03:16:19 GMT
Last-Modified: Fri, 12 Apr 2019 07:33:02 GMT
X-Kong-Upstream-Latency: 1
X-Kong-Proxy-Latency: 0
Via: kong/1.1.1

<IP_ADDRESS> port 9992 serving...
HTTP/1.1 500 Internal Server Error
Date: Wed, 17 Apr 2019 03:16:20 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Content-Length: 42
Server: kong/1.1.1

{"message":"An unexpected error occurred"}HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 36
Connection: keep-alive
Server: openresty/<IP_ADDRESS>
Date: Wed, 17 Apr 2019 03:16:21 GMT
Last-Modified: Fri, 01 Mar 2019 12:18:19 GMT
X-Kong-Upstream-Latency: 2
X-Kong-Proxy-Latency: 0
Via: kong/1.1.1

<IP_ADDRESS> port 9991 serving....

Additional Details & Logs

Kong version ($ kong version) : 1.1.1
Operating system :  Red Hat Enterprise Linux Server release 7.5 (Maipo)
Kong error logs (<KONG_PREFIX>/logs/error.log)

when request failed, these logs can find
2019/04/16 21:02:06 [debug] 8457#8457: *144252 [lua] init.lua:650: balancer(): setting address (try 1): <IP_ADDRESS>:8550
2019/04/16 21:02:06 [info] 8457#8457: *144252 client <IP_ADDRESS> closed keepalive connection
2019/04/16 21:02:07 [debug] 8458#8458: *144262 [lua] init.lua:650: balancer(): setting address (try 1): <IP_ADDRESS>:8550
2019/04/16 21:02:07 [info] 8458#8458: *144262 client <IP_ADDRESS> closed keepalive connection
2019/04/16 21:02:08 [debug] 8459#8459: *144272 [lua] handler.lua:188: rebuilding router
2019/04/16 21:02:08 [crit] 8459#8459: *144272 [lua] handler.lua:192: could not rebuild router: could not load routes: [postgres] connection refused, client: <IP_ADDRESS>, server: kong,
 request: "GET / HTTP/1.1", host: "testserver.com"
2019/04/16 21:02:08 [error] 8459#8459: *144272 [kong] handler.lua:686 no router to route request (reason: could not load routes: [postgres] connection refused), client: <IP_ADDRESS>, s
erver: kong, request: "GET / HTTP/1.1", host: "testserver.com"
2019/04/16 21:02:08 [info] 8459#8459: *144272 client <IP_ADDRESS> closed keepalive connection

2019/04/17 11:16:18 [debug] 12731#12731: *21058 [lua] init.lua:175: rebuilding plugins map
2019/04/17 11:16:18 [crit] 12731#12731: *21058 [lua] init.lua:680: rewrite(): could not ensure plugins map is up to date: failed to rebuild plugins map: [postgres] connection refused, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "testserver.com"
2019/04/17 11:16:18 [info] 12731#12731: *21058 client <IP_ADDRESS> closed keepalive connection
2019/04/17 11:16:19 [debug] 12736#12736: *21068 [lua] init.lua:650: balancer(): setting address (try 1): <IP_ADDRESS>:8550
2019/04/17 11:16:19 [info] 12736#12736: *21068 client <IP_ADDRESS> closed keepalive connection
2019/04/17 11:16:19 [debug] 12736#12736: *21070 [lua] cluster_events.lua:224: [cluster_events] polling events from:<PHONE_NUMBER>.591 to:<PHONE_NUMBER>.812
2019/04/17 11:16:20 [debug] 12731#12731: *21087 [lua] init.lua:175: rebuilding plugins map
2019/04/17 11:16:20 [crit] 12731#12731: *21087 [lua] init.lua:680: rewrite(): could not ensure plugins map is up to date: failed to rebuild plugins map: [postgres] connection refused, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "testserver.com"
2019/04/17 11:16:20 [info] 12731#12731: *21087 client <IP_ADDRESS> closed keepalive connection

You might want to try this branch:
https://github.com/Kong/kong/tree/perf/async-rebuilds
With:
KONG_ASYNC_REBUILDS=true

But this error is kinda expected. We make no gurantees that DB access is never needed.
What has happened here is that you have added route or something and that would have invalidated the router on all the workers across the cluster. Not those workers will build a new router on a first use, and it seems you have not triggered all the workers before running this tests. And router rebuild needs db access. The above PR will make situation better even without KONG_ASYNC_REBUILDS=true, among the other things.

If you endup testing that branch, feedback is greatly appreciated here:
https://github.com/Kong/kong/pull/4488

You might want to try this branch:
https://github.com/Kong/kong/tree/perf/async-rebuilds
With:
KONG_ASYNC_REBUILDS=true

But this error is kinda expected. We make no gurantees that DB access is never needed.
What has happened here is that you have added route or something and that would have invalidated the router on all the workers across the cluster. Now those workers will build a new router on a first use, and it seems you have not triggered all the workers before running this test. And router rebuild needs db access. The above PR will make situation better (I am pretty sure the problem will go away at least on router and plugins) even without KONG_ASYNC_REBUILDS=true, among the other things.

and it seems you have not triggered all the workers before running this test

you are right. I have tried setting the nginx worker_processes to 1,and then request,and then stop postgresql,no request failed,all successed!

We have added a lot more to make Kong more resilient on db down issues, thus I am closing this. There are still of course places like plugins that need to access db no matter what.


Icons Misalignement & Incorrect Target

Issue: Misaligned Icons in Chefs Section and Incorrect Target for Social Links
Description:
In the chefs section of our website, the icons are not properly aligned. They appear to be misaligned, which affects the visual consistency of the section.
Furthermore, when clicking on the social links provided in the chefs section, they open in the same tab. It would be more user-friendly if the social links opened in a new tab, allowing users to easily return to our website.
Steps to Reproduce:

Navigate to the chefs section of the website.
Observe the alignment of the icons in the section.
Click on one of the social links.
Notice that the link opens in the same tab instead of a new tab.

Expected Behavior:

The icons in the chefs section should be properly aligned, maintaining visual consistency.
When clicking on a social link in the chefs section, the link should open in a new tab, allowing users to easily return to our website.

Additional Information:

This issue can be observed on different browsers and devices.
The misalignment of icons may be related to the CSS styling or container properties.
The target attribute of the social links should be set to "_blank" to open them in a new tab.

Attachments:

Please let me know if you require any further information.

Please assign me this issue to solve.

I have raised the Issue and I have the solution to it
I have updated the code according to the feature i raised
I will raise the PR as soon I will be assigned
So please assign this issue to me


Understanding unique_id and "x" category

Hi,
When forecasting multiple Time-series at a time, I was wondering whats the mechanics  between the "unique_id" and "x" category feeded to the ESRNN ?
Does the model learns each Time series independently of each others by unique_id and learns interactions between Time series with same unique_id and different "x" categories values ?
Can we use the "x" to learn hierarchies ? For example if we decompose the same Time serie into 3 others Time series (for example using 3 different data filters), the unique_id is the same for the 3 (same original Time series) but different categories (filter1, filter2, filter3), soo each dates are multiplied 3 Times here for the same unique_id, one by category.
Whats is the mechanics here ?
Thanks!

There is an example of the 'unique_id' and 'x' variables in the README.
https://github.com/kdgutier/esrnn_torch
The 'unique_id' identifies the univariate time series from your panel data. While the the 'x' categorical variable is a static variable (one hot encoded within the model) that shows a single discrete characteristic of the time series, that is constant over time.


Feature:  Allow users to sign-in via username

Feature description
Currently, the user can only log-in using email address, I would like to have this login via username feature added
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Can you assign me this issue.

I am a GSSoC'23 contributor, and I would like to work on this. Kindly assign it to me.


Notifications not loading while there are unread notifications on eventyay

Describe the bug

No notification is being shown in the app while the eventyay account has two new notifications.
(Tried reloading the app and re-logging in but it didn't change)
Eventyay:-

Application:-

Not reproducible.