Snapshot v2

Still working on integration test.

Still working on test and idempotent checks.

See https://github.com/rancherio/cattle/pull/380 for new PR.


Support relationships between content items and their modular items

Motivation
Kentico Cloud content items can be composed of other content items, so called modular content items. They can be put into modular content elements or into the rich text elements.
Design guidelines
Bring support for modular content linking by adding new navigation properties to content item nodes. Make use of the ___NODE convention to tell Gatsby that a field contains an ID of a linked node.
Reference

https://github.com/gatsbyjs/gatsby/issues/1583
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-filesystem/README.md
https://github.com/Kentico/cloud-gatsby/blob/master/plugins/gatsby-source-kentico-cloud/normalize.js

Implemented via https://github.com/Kentico/cloud-gatsby/commit/825080f1163853f507b4fe31e3cb9976fa6f7ad3 and https://github.com/Kentico/cloud-gatsby/commit/6d74079ebc31376ce4be11c0a24476e8f4beb5c6 .


Not parsing abfs protocol locations correctly.

<EMAIL_ADDRESS>doesn't parse out the full protocol.

Fixed by accounting for a potential '@' in the URI prefix.


Organizing SQL migrations in a specific order

Can we implement a solution for ordering the SQL migrations via some additional file.
Here's one scenario off the top of my head:
I need to put my version numbers in a way that they execute in order.
Application 1 Migration
V1_1_1__mytable.sql
V2_1_1__myview.sql
V3_1_1__myproc.sql
Now, a new change comes in where I need to create a new table and my view needs to be modified to use this new table. This change, however, has no real impact the myproc procedure, so no code change is required. Now, to ensure that the move happens correctly, I need to perform the following.
V1_1_1__mytable.sql        << NEW
V2_1_1__mytable2.sql      << ORIGINAL
V3_1_2__myview.sql         << MODIFIED
V4_1_1__myproc.sql         << MODIFIED
Now it appears that I have to migrate my procedure once again with a new version when in fact there's no real change in the contents at all.
It would also be helpful to include a setComparator method so we have more control in how we organize migrations through our own custom ResolvedMigrationComparator implementation.
Thanks

Thank you for your suggestion. This will be resolved with #128 instead.


why this repo moved out from react-native-community

any story here?

the same question

+1

Most libraries from the community org have moved to separate orgs/owners. This repo was moved as part of that change.


add hyperlinks in table example

Summary
Added a table to the Examples documentation (/docs/examples/index.qmd) that shows how to embed html links into the table, a common need in a table.
Related GitHub Issues and PRs

Ref: #69

Checklist

[x] I understand and agree to the Code of Conduct.
[ x I have followed the Style Guide for Python Code as best as possible for the submitted code.
[ ] I have added pytest unit tests for any new functionality.

Thanks for adding this example--it looks great! (I built the docs quickly on my laptop to double check):

Thanks @machow ! I don't have write access to the repo, so if you're happy, can you merge?


Add audio turn on/off button

Can you change the implementation of audio button from it's own function to a method of Board?

Would it be fine to just set it up in the constructor?

It would be fine.
Use => instead of regular functions just to make things consistent
If you are facing difficulties in classes I'll do it myself.

Let me know if there is anything else

Things I want to see changed:

Refactor sound on/off logic into it's own method like Board:handleAudio
reference audioButton with this.audioButton like other elements
Use Prettier formatting. You can get it from vscode marketpace if you use it.

Things I want to see changed:

Refactor sound on/off logic into it's own method like Board:handleAudio
reference audioButton with this.audioButton like other elements
Use Prettier formatting. You can get it from vscode marketpace if you use it.

@Jflyer45 Can you refactor code as per the requirement?

Here we go. I tried putting in a function before and it wasn't working, got it now.

Let me look at making audio button a attribute of board

LGTM

Thanks for everything you've done. Do you want to implement some more features?

Yeah, probably will later this week. Thanks for maintaining the repo and being a part of Octoberfest.
Sweet, I'll try to figure more issues and list them on issues tab. :clinking_glasses:


[perf-db] Purge invalid entries for ConvHipImplicitGemmBwdDataV4R1Xdlops (SWDEV-288976)

This is replica of #975 for develop.

@junliume Thanks!


Implement a method of computing residuals other than nrm2

Specify the method:

Float get_residual(vector &x);
https://github.com/ricosjp/monolish/blob/master/include/monolish_solver.hpp#L46

If you have a method of computing the residuals you want, please write here:
I think:

max element(nrm0?)
b-Ax


avoid using TRUE and FALSE in enum

this addresses a recent failed-to-build problem on Mac.
see #43421

Can you please solve conflicts?

close this, since this was addressed by 74027b89402720e598d5512dddf3ea7737df7ffe, that's why there are conflicts


Update sphinx to 4.1.2

to fix logo image url

Thanks!
pfnCI, test this please.

Seems this one https://github.com/sphinx-doc/sphinx/pull/9440

For the time being I setup a redirect /image/cupy_logo_1000px.png -> /_static/cupy_logo_1000px.png in RTD config.

Jenkins CI test (for commit 0b85bb448686bb006743474ce049c4a7da7d99e9, target branch master) succeeded!


Create utility to create subsets out of a full dataset

In SPDHG, and other stochastic algorithms being developed in the stochastic hackathon, we need to generate subsets from a full dataset.
We've done it manually, but it'd be nice to have it in a function.
I coded up something like the following that enables to create subsets as:

complete random choice of projections in subsets, it does not guarantee that each data is uniquely selected
random permutation, which guarantees that each projection is uniquely selected. Also this means that one stochastic algorithm epoch will visit each and every subset only once.
ordered subset with stride. This allows selection of projections with growing index with stride of 1 or larger, like [0,2,4,6] and [1,3,5,7]
uniform selection of contiguous indices, e.g. [0,1,2,3] and [4,5,6,7]

The following class with static methods will add this functionality. Potentially there is an issue when the number of projection in the full data is not exactly divisible by the number of subsets.
class AcquisitionGeometrySubsetGenerator(object):
    '''AcquisitionGeometrySubsetGenerator is a factory that helps generating subsets of AcquisitionData

    AcquisitionGeometrySubsetGenerator generates the indices to slice the data array in AcquisitionData along the
    angle dimension with 4 methods:

    1. random: picks randomly between all the angles. Subset may contain same projection as other
    2. random_permutation: generates a number of subset by a random permutation of the indices, thereby no subset contain the same data.
    3. uniform: divides the angles in uniform subsets without permutation
    4. stagger: generates number_of_subsets by interleaving them, e.g. generating 2 subsets from [0,1,2,3] would lead to [0,2] and [1,3]

    The factory is not to be used directly rather from the AcquisitionGeometry class.
    '''

    ### Changes in the Operator required to work as OS operator
    @staticmethod
    def generate_subset(acquisition_data, number_of_subsets, method='random'):

        ag = acquisition_data.geometry
        angles = ag.angles.copy()
        if method == 'random':
            indices = [ AcquisitionGeometrySubsetGenerator.random_indices(angles, number_of_subsets)
              for _ in range(number_of_subsets) ]

        elif method == 'random_permutation':
            rndidx = np.asarray(range(len(angles)))
            np.random.shuffle(rndidx)
            indices = AcquisitionGeometrySubsetGenerator.uniform_groups_indices(rndidx, number_of_subsets)

        elif method == 'uniform':
            rndidx = np.asarray(range(len(angles)))
            indices = AcquisitionGeometrySubsetGenerator.uniform_groups_indices(rndidx, number_of_subsets)

        elif method == 'stagger':
            idx = np.asarray(range(len(angles)))
            indices = AcquisitionGeometrySubsetGenerator.staggered_indices(idx, number_of_subsets)
        else:
            raise ValueError('Can only do {}. got {}'.format(['random', 'random_permutation', 'uniform'], method))

        # return indices
        subsets = []
        for idx in indices:
            g = ag.copy()
            angles = ag.angles[idx]

            #preserve initial angle and unit
            g.config.angles.angle_data = angles
            data = g.allocate(0)
            data.fill(acquisition_data.as_array()[idx])
            subsets.append( data )
        return subsets

    @staticmethod
    def uniform_groups_indices(idx, number_of_subsets):
        indices = []
        groups = int(len(idx)/number_of_subsets)
        for i in range(number_of_subsets):
            ret = np.asarray(np.zeros_like(idx), dtype=bool)
            for j,el in enumerate(idx[i*groups:(i+1)*groups]):
                ret[el] = True

            indices.append(ret)
        return indices
    @staticmethod
    def random_indices(angles, number_of_subsets):
        N = int(np.floor(float(len(angles))/float(number_of_subsets)))
        indices = np.asarray(range(len(angles)))
        np.random.shuffle(indices)
        indices = indices[:N]
        ret = np.asarray(np.zeros_like(angles), dtype=bool)
        for i,el in enumerate(indices):
            ret[el] = True
        return ret
    @staticmethod
    def staggered_indices(idx, number_of_subsets):
        indices = []
        # groups = int(len(idx)/number_of_subsets)
        for i in range(number_of_subsets):
            ret = np.asarray(np.zeros_like(idx), dtype=bool)
            indices.append(ret)
        i = 0
        while i < len(idx):
            for ret in indices:
                ret[i] = True
                i += 1
                if i >= len(idx):
                    break

        return indices
    @staticmethod
    def get_new_indices(index):
        newidx = []
        for idx in index:
            ai = np.where(idx == True)[0]
            for i in ai:
                newidx.append(i)
        return np.asarray(newidx)

Rename possibly to AcquisitionDataPartitioner and remove the random option.

@jakobsj suggests something like this for configuring SPDHG
(A1, …, An) = A.partition(n, mode)
(b1, …, bn) = b.partition(n, mode)
or
( (A1, …, An),  (b1, …, bn) ) = partition(A, b, n, mode)

I believe this function does what we need:

creates most of the subsets of the largest size, with one possibly with a different size if the number of indices cannot be divided by the number of batches requested
Allows staggering
Can be used to create random permutations of indices and then create the subsets.

Example with num_subsets=4 and num_indices=9
uniform: [[0, 1], [2, 3], [4, 5], [6, 7, 8]]
stagger: [[0, 4, 8], [1, 5], [2, 6], [3, 7]]
random_permutation: [[3, 5], [6, 8], [7, 0], [2, 1, 4]]

def partition2(num_indices, num_batches, indices=None, stagger=False):
    """Partition a list of indices into num_batches of indices.
    Parameters
    ----------
    num_indices : int
        The number of indices to partition.
    num_batches : int
        The number of batches to partition the indices into.
    indices : list of int, default None
        The indices to partition. If None, the indices will be generated
        automatically.
    stagger : bool, default False
        If True, the indices will be staggered across the batches.

    -------
    list of list of int
        A list of batches of indices.
    """
    min_batch_size = num_indices // num_batches
    # makes the last batch smaller if the number of indices is not divisible by the number of batches
    if num_indices/num_batches - min_batch_size > 0.5:
        batch_size = min_batch_size + 1
    else:
        batch_size = min_batch_size

    # Partition the indices into batches.
    if indices is None:
        indices = list(range(num_indices))

    if stagger:
        idx = indices.copy()
        batches = [ idx[0::num_batches] ]
        for i in range(1, num_batches):
            batches.append(idx[i::num_batches])

    else:
        batches = []
        for i in range(num_batches-1):
            batches.append(
                indices[i * batch_size : (i + 1) * batch_size:1]
                )
        # Add any remaining indices to the last batch.
        # the last batch may be smaller than the others
        rem = indices[(num_batches-1) * batch_size:]
        batches.append(rem)

    return batches

How do you see this in relation to my suggestion above:
(A1, …, An) = A.partition(n, mode)
(b1, …, bn) = b.partition(n, mode)
or
( (A1, …, An),  (b1, …, bn) ) = partition(A, b, n, mode)
As a helper function or instead of? What would the user do with the output batches? In the typical case they user shouldn't need to pass the indices as input since it would partition all the existing indices. Why boolean for stagger? That leaves just two options, how to get random_permutation? Why not a string input instead, then more ways to partition can be easily added later?


CASSANDRA-11930

Test non-compound RangeTombstone ser during upgrades
Done for CASSANDRA-11930

Looks good, except for my nits, which are small. Trying to run locally now.

These should be fixed, thanks.  I also forgot to push my minor changes to upgrade_base.py, so I did that here.

Cool, thanks for addressing my nits, and maaaaaan am I glad to see that API change to do_upgrade, great thinking there.
I'll want to see a CassCI run on these changes -- maybe a run of some subset of the upgrade tests -- but I'm +1 on the code. Unless you've run these somewhere @thobbs, we'll figure it out in TE and let you know the result.
Just to confirm, we'll wait to merge until CASSANDRA-11930 is closed, yeah?

@mambocab Russ is working on a run of the upgrade tests in CI here: http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-custom-11930-upgrade/.

Just to confirm, we'll wait to merge until CASSANDRA-11930 is closed, yeah?

Correct.


Fix max treated as exclusive on Gen.choose() for int and long - Fixes #1011

For Gen.choose() on the overloads with min and max, for int and long, the max was treated as exclusive and it should be inclusive. This is, of course, making the assumption that max is supposed to be inclusive. At least, that is the way the docs for the functions sound to me.

As a side note, would it be better to have parameters for Gen.int() and Gen.long() that have default values?
Then you could just have something like this:
fun Gen.Companion.int(minInt: Int = Int.MIN_VALUE, maxInt: Int.MAX_VALUE) = object : Gen<Int> {
   val literals = listOf(minInt, maxInt, 0)
   override fun constants(): Iterable<Int> = literals
   override fun random(seed: Long?): Sequence<Int> {
      val r = if (seed == null) Random.Default else Random(seed)
      return generateSequence { r.nextInt(minInt, maxInt) }
   }

   override fun shrinker() = IntShrinker
}

After submitting this PR, due to the Travis checks, I found the tests in GenTest. These tests expect the max to be exclusive, meanwhile, the tests for Gen.string() have the max being inclusive.
So, between the docs for Gen.choose(min, max) that seem in indicate inclusivity and Gen.string() which has an inclusive max, and the tests in GenTest that indicate exclusivity for max, which is correct?
In my opinion, it would make the most sense for min and max in all of these cases to be inclusive.

I agree with you. Go inclusive.
On Wed, 25 Sep 2019, 02:34 EarthCitizen<EMAIL_ADDRESS>wrote:

After submitting this PR, due to the Travis checks, I found the tests in
GenTest. These tests expect the max to be exclusive, meanwhile, the tests
for Gen.string() have the max being inclusive.
So, between the docs for Gen.choose(min, max) that seem in indicate
inclusivity and Gen.string() which has an inclusive max, and the tests in
GenTest that indicate exclusivity for max, which is correct?
In my opinion, it would make the most sense for min and max in all of
these cases to be inclusive.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/pull/1012?email_source=notifications&email_token=AAFVSGWPP4JGLERBCR223STQLMH63A5CNFSM4I2IUI4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7Q5ICY#issuecomment-534893579,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFVSGSPQWX6NNGJR3OAWNLQLMH63ANCNFSM4I2IUI4A
.

Everything should be working fine now.

Thanks for the pull request!


storage/uploads folder not persisted between restarts on docker. Public/uploads is correctly persisted

Describe the bug
According to the documentation about backup/restore, the following folders should be backuped:

public/uploads
storage/uploads

The public/uploads folder is symlinked to the config folder. This is also the folder that is persisted using a volume.
The storage/uploads folder is NOT symlinked to the config folder, hence has no persistence in a docker volume.
Steps To Reproduce
Steps to reproduce the behavior:

Create a folder or file in the storage/uploads folder
Re-create/redeploy the bookstack apps (app, database, backup, redis)
Check the storage/uploads folder by connecting the console to the bookstack app container
The in step 1 created folder or file is gone ;-)

Expected behavior
The storage/uploads folder is persisted. If possible using the same solution as the public/uploads folder.
Screenshots
public/uploads symlinked to config folder:

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): BookStack v0.29.3
PHP Version: 7.3.18
Hosting Method (Nginx/Apache/Docker): linuxserver/bookstack docker image

Additional context
Part of docker stack:
 app:
    image: linuxserver/bookstack
    volumes:
      - bookstack_config:/config

I just checked my running instance—/var/www/html/storage/uploads contains symlinks to /config/www/files and /config/www/images, but no regular files.  Do you have an example of a file that Bookstack saves in storage/uploads that doesn't really live in the config volume?

I just checked the friends installation again which was created from backup, and also created my own docker instance, and it seems to be a completely different problem!
The 'problematic' Bookstack instance was created from backup. So it seemed that after the re-creation of the Bookstack app, the storage folder had a problem with persistence. And that is what I tested and made the PR from.
However, after creating my own environment (app, database and backup containers), I just found out that as long as you don't upload an attachment, NO symlinks are made. Only after uploading a file/image two folders are created in the storage folder: files - symlinking to /config/www/files and images - symlinking to/config/www/images.
However the backup container was saving /config/www/uploads and /config/www/storage. The last one just doesn't exist!
So it is actually a problem with the documentation, resulting in a wrongly setup backup container. This one should, apart from the database itself, backup the following folders in a docker environment:

/config/www/uploads
/config/www/files
/config/www/images

So I will close this issue, and check the documentation.


Automated publish to https://hub.docker.com/

Is your feature request related to a problem? Please describe.
Currently, there is no automated process to publish Docker images for this project to Docker Hub when new releases are made.
Describe the solution you'd like
Implement an automated CI/CD pipeline, preferably using GitHub Actions, to build and publish Docker images to Docker Hub whenevera  new release is created.
The pipeline should:

Build the Docker image
Tag it appropriately (e.g., with version number for releases and 'latest')
Push the image to our Docker Hub repository

This is a good idea. We don't have a docker image on docker hub but it would be really good to have one.


Replace multiprocessing usage in test fixtures with subprocess

Some advantages would be:

no longer a necessity to use the "fork" method, which should allow the tests to run on windows as well
no potential for an unclean server start due to the "fork" method, the server processes would start in their own new python interpreter
due to the better separation it would become possible to e.g. start both an mscolab server with and without basic auth, enabling us to test different server configuration more effectively (right now the basic auth case can only be run separately)
it would become possible to test with different WSGI servers, if we want that

Could you assign this issue to me?

are these only changes I must do, or are there any more requirements ?
def _running_eventlet_server(app):
    """Context manager that starts the app in an eventlet server and returns its URL."""
    scheme = "http"
    host = "<IP_ADDRESS>"
    socket = eventlet.listen((host, 0))
    port = socket.getsockname()[1]
    url = f"{scheme}://{host}:{port}"
    app.config['URL'] = url
    start_method = multiprocessing.get_start_method()
    if start_method != "fork":
        pytest.skip("requires the multiprocessing start_method 'fork', which is unavailable on this system")
    args = ["python", "-m", "eventlet.wsgi.server"]
    process = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
    try:
        process.start()
        while not is_url_response_ok(urllib.parse.urljoin(url, "index")):
            time.sleep(0.5)
        yield url
    finally:
        process.kill()
        process.communicate()
        process.close()

No, I think this should start python mslib/mscolab/server.py start or its mswms counterpart using subprocess, depending on the fixture. This would also require a new approach to get the assigned port from the subprocess (or maybe a listening socket can be opened beforehand and its port can be re-used for the subprocess, not sure yet). This might also entail changes to tests (hopefully not many) and the configuration setup in the test suite might have to be adapted.
This is definitely a more complicated issue.


[GPU] Remove dependency on tpp's StructuredOpMatcher from LinalgToXeGPU conversion

We want to get rid of this file essentially:
https://github.com/intel/graph-compiler/blob/main/lib/gc/Transforms/Utils/StructuredOpMatcher.cpp

Hi dmitry, I have exactly the same dependency in this PR for CPU microkernel pipeline: #114, maybe we can share some joint effort to remove the dependency.

Hi dmitry, I have exactly the same dependency in this PR for CPU microkernel pipeline: #114, maybe we can share some joint effort to remove the dependency.

@huanghaixin008 have you made any progress so far in removing this dependency? I'm wondering, whether we should remove this (if it's not trivial) since there are already several places in GC where we depend on it
cc @kurapov-peter

@huanghaixin008
Initially when I was copying LinalgToXeGPU pass from tpp-mlir, I wanted to bring to GC as less external utils as possible. StructuredOpMatcher seemed as a redundant and easy-removable thing at first. Now given the facts, that it appeared not so trivial to remove, and that other parts of GC start also depending on these utils, it seems more logical to leave them in our project with no changes.
So no changes to StructuredOpMatcher and other utils, that I've added in #165, are planned from my side. Thus closing the issue.


Confusing Buttons on Samples Page

The Select, Links and Download buttons on the samples are unclear.
A cleaner UI is required. It should be clearer that download means download metadata for this selection.
Perhaps two split buttons with Links and 'Metadata' as the the options. The main button can deal with the current selection and the split button can give the option to download for all with the current specifications.

Closed by #121


Windows 11 - 22621.1848

''the number of connections to this computer is limited'' how to fix this ?

Duplicate of https://github.com/stascorp/rdpwrap/issues/2213

''the number of connections to this computer is limited'' how to fix this ?

If Fully supported and this error:
Try restart service or reboot.
OR
Try:

Download RDP Wrapper 1.6.2 and extract this to any directory.
Place rdpwrap.ini in the same directory.
Open CMD as administrator
Execute this commands

cd C:\path\to\directory\
rdpwinst -u -k
rdpwinst -i

Enjoy!

Original message: https://t.me/rdpwrap/49131


Update readme.md

Added explanation to load from "AppServiceProvider".
Added Lumen specific notes for installation before License.

You can just push more commits to this branch if you want.

Done.

Thanks!


Wrong Felix IptablesAllowAction setting in docs

The Felix docs here document a setting called IptablesAllowAction, but Felix actually uses two settings named IptablesFilterAllowAction and IptablesMangleAllowAction, for the filter and mangle tables respectively.

Fixed in latest docs (at least in v3.0+)


fix ReactionAreaVolumeValInRange with isotope

Codecov Report

Merging #26 (4eb5278) into main (8d238f0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #26   +/-   ##
=======================================
  Coverage   53.93%   53.93%
=======================================
  Files          37       37
  Lines        3586     3586
=======================================
  Hits         1934     1934
  Misses       1652     1652

Impacted Files
Coverage Δ

src/reactioncatalog/VariableStats.jl
80.41% <ø> (ø)

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 8d238f0...4eb5278. Read the comment docs.


refactor(virtctl/imageupload): use Printf from cobra library

What this PR does
Use Printf the default from cobra library
to print user-facing logs.
Requested by @0xFelix to cleanup imageupload
command.
Release note

None

/kind cleanup

/cc @0xFelix

@0xFelix @oshoval Can you please review?

@0xFelix
why is it better ? allows to use a more robust logger?

beside the question
/lgtm

/lgtm


Publish to npm only if version has changed

This is fixed.
When we were debugging the build last week we changed this line
npm run npmPublish

to
npm publish

It turns out that command was our strategy for not publishing if the version hadn't changed, but it was failing because it relies on an npm package publish that was being removed during the gh-pages smoke test. So I added it back and added a line to re-install that dependency before trying to publish.

Mystery solved! Thanks!


metabase: 0.29.0 -> 0.29.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/metabase/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
directory tree listing: https://gist.github.com/40a08752e83dd27b03a5e553c6f89582
du listing: https://gist.github.com/fe6508f6abc39c37b41465ae8e9efd81

meta.description for metabase is: '"The easy, open source way for everyone in your company to ask questions and learn from data."'.
cc @schneefux @thoughtpolice for testing.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: metabase
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


Inconsistent .mutual_information method

In our samplers .mutual_information() is a callable method, in tasks it is a @property. It would be nice for them to be consistent.

@grfrederic The reason for this is the following:

ISampler may need additional arguments to calculate mutual information (as we do with BMMs, which collect MC samples. Here one can potentially specify the required number of samples. I also recall that we used it in some discrete-continuous estimators where MI is analytically known as an infinite series and we truncate it after a given number of terms).
Task is supposed to already know MI. I.e., for ISampler .mutual_information(k) may have complexity $\mathcal O(f(k))$ and for Task querying .mutual_information property is supposed to be $\mathcal O(1)$.
How about adding .mutual_information() to Task for consistency?

@grfrederic Closing this for now, as I don't see a good way of reconciling – but please reopen if you think we can do something more :slightly_smiling_face:


project compile error

compile error:
1.
import pl.droidsonroids.gif.GifOptions;
import pl.droidsonroids.gif.GifTexImage2D;
2.
multiCallback= new MultiCallback(true);
I think  this project  is older?  I  want to see Newest,because I is first know this lib.I want to know more about this lib.so I need to see you sample ~

It seems that you have outdated library submodule. It can be updated eg. using git submodule update. Current HEAD is at commit: 52382bc062fb8fff5cd220c604e13b915bcdef51. Here you can see how travis clones sample and submodule: https://travis-ci.org/koral--/android-gif-drawable-sample

thanks


:children_crossing: :technologist: :wrench: :adhesive_bandage: Add  POC implementation of divineRGBVal

:children_crossing: :technologist: :wrench: :adhesive_bandage: DivineRGBVal
This is an initial stab at providing a server-side mechanism of determining the RGB values of tailwind-style colors.
I'm okay with it as is, but I'm totally open to adjusting the implementation if desired.
This adds two json datafiles:

data/congo.json
This provides an in-scope lookup table to facilitate resolution of the tailwind color names abstracted into primary secondary and neutral per color-scheme; and default shade/weight values.

data/twcolormap.json
This is the datasource actually referenced by the partial to return values to the calling entity.

It can likely be improved substantially, but I wanted to get it visible and get a conversation going before trying to perfect it.
I see this as a server-side replacement for the voodoo of appearance.js manipulating the color value of metatags client-side.
The partial is overly verbose if the debug variable is set to true, MOSTLY for the purposes of illustrating what was being done and why...
Here's the log output from me having the partial partials/favicons.html invoke this partial to determine the primary colorvalue for the site:
relevant snippit from partials/favicons.html:
{{- $favItch     :=            newScratch -}}
{{- $favItch.Set "logPrefix"   "[partials/favicons.html] " -}}
{{- $favItch.Set "debugPrefix" (print "[DEBUG]" ( $favItch.Get "logPrefix" )) -}}

{{- $priCol := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary"  )) -}}
{{- warnf "%s - divineRGB: %s " ( $favItch.Get "logPrefix" ) $priCol  -}}

Log output:
WARN  [DEBUG][partials/favicons.html]  Debug Enabled
WARN  [DEBUG][util/divineRGBVal.html]  Debug enabled
WARN  [DEBUG][util/divineRGBVal.html]  ..-. Theme colorScheme not provided on invocation. Read 'avocado' from site.Params.colorScheme.
WARN  [DEBUG][util/divineRGBVal.html]  +... Color given: primary
WARN  [DEBUG][util/divineRGBVal.html]  --.. Color 'primary' doesn't seem to be a tailwind-style (color)-(shade) combo.
WARN  [DEBUG][util/divineRGBVal.html]  -.-. Color 'primary' references a theme-abstracted value. Further divination required
WARN  [DEBUG][util/divineRGBVal.html]  .--. Desired Shade unknown. Will lookup theme-value default for primary
WARN  [DEBUG][util/divineRGBVal.html]  .+.. Desired Shade: primary
WARN  [DEBUG][util/divineRGBVal.html]  .--? Shade not provided on invocation. Determining fallback value for 'primary'.
WARN  [DEBUG][util/divineRGBVal.html]  .--. Iterating default weights: neutral primary
WARN  [DEBUG][util/divineRGBVal.html]  .--. Iterating default weights: primary primary
WARN  [DEBUG][util/divineRGBVal.html]  .+-. Found weight for K:primary. Set shade to:600
WARN  [DEBUG][util/divineRGBVal.html]  .--. Iterating default weights: secondary 600
WARN  [DEBUG][util/divineRGBVal.html]  -.-? avocado Scheme Color names unknown. Shortcut this by setting Site params.divineRGBVals.(primary,secondary,neutral) to the values discerned from divination.
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Theme Datafile congo Accessible
WARN  [DEBUG][util/divineRGBVal.html]  -.-?  Iterating themeData: K:0 V:map[cherry:map[neutral:neutral primary:rose secondary:green]]
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Evaluating Scheme 0 Name:cherry
WARN  [DEBUG][util/divineRGBVal.html]  -.-?  Iterating themeData: K:1 V:map[congo:map[neutral:gray primary:violet secondary:fuchsia]]
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Evaluating Scheme 1 Name:congo
WARN  [DEBUG][util/divineRGBVal.html]  -.-?  Iterating themeData: K:2 V:map[fire:map[neutral:stone primary:orange secondary:rose]]
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Evaluating Scheme 2 Name:fire
WARN  [DEBUG][util/divineRGBVal.html]  -.-?  Iterating themeData: K:3 V:map[ocean:map[neutral:slate primary:blue secondary:cyan]]
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Evaluating Scheme 3 Name:ocean
WARN  [DEBUG][util/divineRGBVal.html]  -.-?  Iterating themeData: K:4 V:map[sapphire:map[neutral:slate primary:indigo secondary:pink]]
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Evaluating Scheme 4 Name:sapphire
WARN  [DEBUG][util/divineRGBVal.html]  -.-?  Iterating themeData: K:5 V:map[avocado:map[neutral:stone primary:lime secondary:emerald]]
WARN  [DEBUG][util/divineRGBVal.html]  ..-? Evaluating Scheme 5 Name:avocado
WARN  [DEBUG][util/divineRGBVal.html]  ..*? Matched Scheme avocado! P: lime, S: emerald N: stone
WARN  [DEBUG][util/divineRGBVal.html]  +.+? Setting the value of scratch object $rgbItchy.neutral. Reading it Back to verify: stone
WARN  [DEBUG][util/divineRGBVal.html]  +.+? Setting the value of scratch object $rgbItchy.primary. Reading it Back to verify: lime
WARN  [DEBUG][util/divineRGBVal.html]  +.+? Setting the value of scratch object $rgbItchy.secondary. Reading it Back to verify: emerald
WARN  [DEBUG][util/divineRGBVal.html]  +.+? Color primary disambiguated to lime
WARN  [DEBUG][util/divineRGBVal.html]  +.+? Role secondary is emerald
WARN  [DEBUG][util/divineRGBVal.html]  +.+? Role neutral is stone
WARN  [DEBUG][util/divineRGBVal.html]  ...- Tailwind ColorMap Datafile twcolormap Accessible
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 0:slate lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 1:gray lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 2:zinc lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 3:neutral lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 4:stone lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 5:red lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 6:orange lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 7:amber lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 8:yellow lime
WARN  [DEBUG][util/divineRGBVal.html]  *..- Evaluating Tailwind Mapdata 9:lime lime
WARN  [DEBUG][util/divineRGBVal.html]  **.+ Found color %!s(int=9) lime
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :100 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :200 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :300 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :400 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :50 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :500 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :600 600
WARN  [DEBUG][util/divineRGBVal.html]  **.+ Found  lime:%!d(string=600) RGBVal: #65a30d
WARN  [DEBUG][util/divineRGBVal.html]  **** ReturnVal set #65a30d
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :700 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :800 600
WARN  [DEBUG][util/divineRGBVal.html]  **.- Evaluating 9:lime Shades :900 600
WARN  [partials/favicons.html]  - divineRGB: #65a30d

In its current state, it can be used as follows:
Divine the default RGB Value for a theme-abstracted tailwind color
{{- $rgbval := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary"  )) -}}
{{- $rgbval }}

Would output:  #65a30d
Divine the tailwind color name of a theme-abstracted color
{{- $twColor := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary" "return" "TWColor"  )) -}}
{{- $twColor }}

Would output:  lime
Divine the default tailwind-style color-shade Value for a theme-abstracted tailwind color
{{- $twC-S := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary" "return" "TWColorShade"  )) -}}
{{- $twC-S }}

Would output:  lime-600
Divine the RGB Value for a theme-abstracted color-weight combo
{{- $someOtherRGB := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary" "shade" 500 )) -}}
{{- $someOtherRGB }}

Would output:  #84cc16
Divine the RGB Value for a theme-abstracted color-weight combo of another colorscheme
{{- $someOtherColorSchemesColor := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary" "shade" "500" "scheme" "cherry" )) -}}

{{- $someOtherColorSchemesColor }}

Would output:  #f43f5e
Divine the tailwind-style color-shade  for a theme-abstracted color-weight combo for another colorscheme
{{- $someOtherColorSchemesDefaultColor := (partial "util/divineRGBVal.html" (dict "context" . "color" "primary" "scheme" "cherry" "return" "TWColorShade" )) -}}
{{$someOtherColorSchemesDefaultColor }}

Would output:  rose-600
with a little bit of iteration and a smattering of HTML/css:
Show me a  list[^1] of all the colors of all congo colorschemes:
{{- $t  := slice "cherry" "congo" "fire" "ocean" "sapphire" "avocado" "slate"  -}}
{{- $tc := slice "primary" "secondary" "neutral" -}}
{{- $w  := slice 50 100 200 300 400 500 600 700 800 900 -}}
{{- range $tK, $scheme := $t -}}

      {{- $scheme }}

{{-   range $cK, $color := $tc -}}

          {{- $color }}
{{-   $tcolor := (partial "util/divineRGBVal.html" (dict "context" . "color" $color "scheme" $scheme "return" "TWColor" )) -}}
{{-	  range $sK, $shade := $w  -}}
{{-      $val := (partial "util/divineRGBVal.html" (dict "context" . "color" $color "shade" $shade "scheme" $scheme  )) -}}

            {{- $val }}

            {{- printf "%s-%d" $tcolor $shade -}}

{{-	   end -}}

{{-	 end -}}

{{- end  -}}

or:
Create an ugly table of all the tailwind colors
{{- $t  := slice "avocado" -}}
{{- $tc := slice  "slate" "gray" "zinc" "neutral" "stone" "red" "orange" "amber" "yellow" "lime" "green" "emerald" "teal" "cyan" "sky" "blue" "indigo" "violet" "purple" "fuchsia" "pink" "rose" -}}
{{- $w  := slice 50 100 200 300 400 500 600 700 800 900 -}}
{{- range $tK, $scheme := $t -}}

Tailwind Colors

{{-   range $cK, $color := $tc -}}

{{- $color }}
{{-	    range $sK, $shade := $w  -}}
{{-       $val := (partial "util/divineRGBVal.html" (dict "context" . "color" $color "shade" $shade "scheme" $scheme  )) -}}

              {{- $val }}

{{printf "%s-%d" $color $shade}}

{{-	    end -}}

{{-	  end -}}

{{- end  -}}

Thoughts?
[^1]: (Admittedly, somewhat terribly formatted, but you get the point.)

I really like the idea behind this feature. One of the things that has really bugged me is that the RGB values are required to make the Tailwind theming work as I think it's a horrible hacky way of solving it. I had hoped they would implement a cleaner way in the upstream project but alas it doesn't seem to be happening.
There's lots of voodoo that I've done around the place to implement the colours into various features and so this is potentially one way to clean it all up. I've only had a very quick look at your implementation but some high level questions pop to mind:

Can we automate getting the colour mapping from tailwind directly? For instance, in npm when building the stylesheet could it also copy the latest colours into the data folder so they're always in sync?
I wonder if the config part is too rigid in terms of the shades it's using and if it should support passing a shade value?

There's probably a lot more but that's my initial thoughts.

yeah.. there’s a few ways to make this less fucky™
my intent with submitting this as-is was to come to the party with beer…
IE this works and serves as a starting point for a more elegant solution.

I’ll ask the tailwind kids if there’s a way to emit a truthy tailwind color map that’s programatically consumable, and report back.

re config question: i’m not sure i grok what you’re asking.

as I understand it:
tailwind supports T color names, each with the  S shade values:
50, 100, 200, 300, 400, 500, 600, 700, 800, 900
congo provides C color schemes, each of which abstracts 3 tailwind T colors into ‘primary’ ‘secondary’
if tailwind is configured to provide more S shades per T color, the tailwind color map would need to be expanded, to, say include
50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 11
the only validation I’m doing wrt shade is that the requested shade ends with a 0. so as written, a shade with an ending value of 1-9 would be unparsable, but the liklihood of that scenario is pretty low unless we opt to start using quarter values ie 25, 50, 75; which feels unlikely?
as far as “default values” go, the existing congo data file provides

a “default” S shade for primary secondary and neutral, (the values of which i pulled out of…… uh…. thin air)
a fallback value in case the user requested a T color and did not provide an S shade.

if you ask it to divine the rgb value of T: blue S: 100, it should work properly assuming the tailwind color map has a value for blue-100.
if you feed divineRGBVal C “primary” S “900” it should return the rgb vals of the T color associated with C primary at S shade 900
what am I missing?

I reached out to tailwind here^1. Will followup as that conversation unfolds.

I also think using the word "divine" here is odd... something like getRGBFromTailwind sounds clearer as to what the function is actually doing. That said, I haven't really come up with a naming standard for theme functions.

definitely different, for sure...
I was going with divination
https://en.wikipedia.org/wiki/Divination
https://en.wikipedia.org/wiki/Greek_divination
To convey the voodoo/waving of hands/consumption of snake oil/ etc...
Because we're creating a secondary truthy source, and blindly trusting it....
I'm not ATTACHED to the name... I just didn't want it to convey a sense of
"I AM TOTALLY ACCURATE AND YOU SHOULD BELIEVE ME WITHOUT QUESTION" as is ;)

so whats next here?

I've since refined the way I'm presenting the currently usable colors here
I could add this into the PR if ya want, but I figured that the point was to have a tool to determine a color value...

:) Kno yer busy. Lmk if you have moar thots.


Set max-row-limit to default value

The Influx Documentation states a default value of 0 for the max-row-limit parameter. This circumvents an issue with Grafana, where InfluxDB just responds with partial data for large data sets.

This change is

I signed it!

I signed it!

/ok-to-test

/lgtm


Menu bar icon does not work with Bartender 5

When using Radiola 7.0.2 with Bartender 5.12 on MacOS 14.3.1, the icon on the menubar is unresponsive, and sometimes it shows a danger triangle like the one below:

If I close Bartender, the icon works again.
The feedback from Bartender support was: "Occasionally, we'll hear of apps that have code that's meant to never show or never hide them from the menu bar although I can't say for certain that's what's happening here."

Unfortunately Apple doesn't provide an API to determine which mouse button is clicked in the menu bar. So I had to use some hacks, they don't seem to work with programs like Bartender.
I'll install the trial version and try to fix the bug.
Bartender is it from www.macbartender.com?
What does the yellow exclamation mark on the program icon mean?

Yes, Bartender is that one. I don't know what the exclamation mark means. It is the first time I see it, maybe it is the Bartender app that overlays it.
If it helps, Caffeine is another open-source app that detects right clicks and has no problems with Bartender.

Thanks so much for the Caffeine, I'll have a look at how they did it.

It's very strange. I downloaded Bartender 5.1.2 from their website. And I have everything working, no yellow triangle and work fine:

left click
right click
middle mouse button click
scroll wheel

Apple M1,
macOs Sonoma 14.6.1
Bartender 5.1.2
Radiola 7.0.2
I only see one difference, I have a slightly newer macOS. If you get a chance try upgrading the OS.

I just upgraded MacOS to 14.6.1, but the problem persists. Sorry for not specifying that it was also working initially for me, but it suddenly stopped working.

P.S. Have you tried using the option "Show menu bar items in a bar below the menu bar" (see below)?

I've just found that if I deactivate this option the Radiola icon starts working again. Even though it is suboptimal, it can be used as a workaround.

It still works. Send me screenshots of your settings.

I couldn't reproduce the problem. I wrote to Bartender support about the triangle, maybe that will clear things up.
By the way, if you close Bartender, does the triangle disappear?

Yes, if I close Bartender the triangle disappears. Then if I open Bartender again, the triangle appears after I try to interact with the Radiola menu bar icon. I also wrote another email to Bartender support pointing to this issue on GitHub.
Here below is a screen record of the issue.
https://github.com/user-attachments/assets/5bfc612c-92cb-47a0-a3f9-e7c2a1176f41

I was able to reproduce the situation. I have fixed the problem, I hope.
I am posting a link to the test version of the program .
Radiola-7.0.2-dev.dmg.zip

With the new version, the triangle doesn't show up anymore, but the radio works only when the menu icon is visible. When bartender hides it, the music stops.

The previous version didn't work quite right. I am posting a new one.
The fixes are not related to playback stopping, but I don't understand why playback might stop.
I have a few questions.

What does “music stops” mean?

the program pauses
the program turns on mute (a small letter M appears on the icon)
the program shows that it is playing, but there is no sound?

There was an update to Bartender today, did you update?
Send me screenshot of the “Controls” tab of the Radiola settings window.

Radiola-7.0.2-dev2.dmg.zip

I've now updated Bartender and with your 7.0.2-dev2 the problem seems solved. Thank you!
Regarding your questions:

What does “music stops” mean?

With the previous version, when I say that the music stops I meant that the music was not audible whenever the icon was hidden because of Bartender operation.

the program pauses
the program turns on mute (a small letter M appears on the icon)
the program shows that it is playing, but there is no sound?

I can't say if the program was paused or muted, because it all happened while the icon was hidden. When the icon reappeared, the music would resume without any other user interaction.

There was an update to Bartender today, did you update?

My last message was before updating Bartender.

Send me screenshot of the “Controls” tab of the Radiola settings window.

Here are the screenshots taken with 7.0.2-dev2. I haven't changed any settings.

Released in 8.0.0


fix: fork metamask's phishing detection functionality

currently we are still using their list
https://github.com/MetaMask/eth-phishing-detect/blob/bdcd288d76dc574ff93e68d148f66d14f432d48c/src/config.json
which is list of sites targeting ethereum user

This change is

Builds ready [3d8828e]builds: chrome, firefox, opera
bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
dep viz: background
all artifacts


Refactor Signup Method: Signup Flow and Shift Structure

[x] QualificatioMixStructure
[x] race condition
[x] what happens when deleting a Qualification configured in the shift structures
[x] check PDF export
[x] update tests to work again
[ ] add new tests
[ ] update plugin dev docs
[ ] update user docs and make sure it's linked correctly
[ ] profiling and performance improvements
[ ] display flow/structure descriptions
[x] migration
[x] delete old plugin

coverage: 85.955% (-1.8%) from 87.72%
when pulling 89e26dfba8aa42c3f8919fd7f174e2a5168ee63d on signup-flow-refactor
into 5025baa91aae7fcbdf754319fc061d51a6093e9f on main.


Authentication failed. Please check your DeepL API key. You may be using the DeepL Pro API by mistake.

Thank you for creating the extension!
The message "Authentication failed. Please check your DeepL API key. You may be using the DeepL Pro API by mistake." remained the same even after I turned on deepl.usePro.
However, when I changed my plan from DeepL Pro Advanced to DeepL API, the error disappeared and I was able to translate! It seems that this extension is not compatible with the DeepL Pro Advanced API key.
But then, another issue came up. Even though translations work fine, I now get the message, "Unfortunately, the DeepL API cannot accept any requests at the moment. Please try again later. (Value for 'source_lang' not supported.)"
I would like to have this message removed.

The feature that automatically displays the translation of selected text in a pop-up window is working very well. It works so efficiently that it's almost worrisome. Is it normal that the text is translated automatically just by selecting it (without using a command)? That's incredibly amazing!
After selecting text, if I choose "DeepL: Translate" or "DeepL: Translate below the original" from the right-click menu, the message "Unfortunately, the DeepL API cannot accept any requests at the moment. Please try again later. (Value for 'source_lang' not supported.)" appears. The same thing happens when I select these options from the command palette.
When I press 'alt+t', a '†' symbol is displayed, and since 'ctrl+alt+t' is used by another extension, I haven't tried it.

Hi @bakemocho,
Could you please provide the debug information from the output window?

It seems that there is a problem with the source language - Does it work when you use the command "DeepL: Translate from ... to ..."?

After receiving your reply, I tried 'DeepL: Translate from ... to ...' and the error message stopped appearing! If it was just a matter of using it incorrectly, I'm sorry...
I'll attach the debug information that I was able to obtain. I hope it will be helpful.
error_bakemocho.txt

I'm not 100% confident what your issues caused but I made some stability and usability improvements to avoid future issues like this. These improvements are released with version 1.0.8.
If the issue occurs again just reopen this issue and reach out to me.
Thanks for your support.


Can't get away from a ready-only filesystem error.

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az group show
Errors:
Resource group 'eshop-learn-rg' could not be found.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az group show -g {} -o {}

Expected Behavior
Environment Summary
Linux-4.15.0-1082-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Installer: DEB

azure-cli 2.5.1 *

Additional Context

add to S171

add to S172

@speediefarf Could you please show the details of the error?

Because there is no reply to this question for a long time, I will close it temporarily. If you have any questions, please feel free to let us know.


fix: migrate from k8s.gcr.io to registry.k8s.io

What type of PR is this?
Kubernetes is migrating its image registry from k8s.gcr.io to registry.k8s.io.
Part of kubernetes/k8s.io#4780.
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

@00pf00 PTAL when/if you have some time.

@dodiadodia can you PTAL?


add = "" to make it easier to understand directions

The instructions on this waypoint are pretty confusing. I've added = next to the vars for the sake of helping clear things up. Several users have joined the glitter chat with the same question & confusion.

You'll need to escape the double quotes.

You'll need to escape the double quotes.

Thank you. fixing that now.

Thanks for the fix! One more request: you'll need to squash your commits. After that we'll be good to merge :smile:

looks like I have some other things to correct before this is squashed properly. Let's close this for now and I'll make a new pull request some other day.


[BACKPORT][v1.2.x][IMPROVEMENT] Support failed/obsolete orphaned backup cleanup

ref: https://github.com/longhorn/longhorn/issues/3898

Hi @mantissahz ,
Follow test steps https://github.com/longhorn/longhorn/issues/3898#issuecomment-1214773993, ( I set Failed Backup Time to Live to 5), after 5 minutes passed by, the error state backup will not cleanup until I create a snapshot or create a new backup, this behavior not found in master-head, could you help me to clarify this? thank you.

The failed backup deletion would be trigger when update the backup volume by polling backup target and it is 300 seconds now, and creating a new backup would update the backup volume as well.
https://github.com/longhorn/longhorn/blob/fba0c5c1673285d447b888acd18d96b14bb5e5a0/chart/questions.yml#L331
It might wait in 10 minutes if the polling backup target is not started. @chrisc1981 Could you shorten the Backupstore Poll Interval and try again?

Suggest having an automation test case for consistent testing and results.
https://github.com/longhorn/longhorn/issues/4481

Verified on longhorn-manager v1.2.x-head 36a84d
Result Pass
Test steps or (https://github.com/longhorn/longhorn/issues/3898#issuecomment-1214773993):

Deploy Longhron and backupstore
Set Failed Backup Time to Live to 5 (by default it's 1440 minutes)
Create a volume then attach to worker node and write some data
Create a backup to backup target then crash the instance-manager-r such as this command kubectl delete pods -l longhorn.io/instance-manager-type=replica -n longhorn-system --wait.
Then backup state should become Error in a few seconds.
Wait after Failed Backup Time to Live passed
Verify failed backup had been deleted from UI and command kubectl get backups.longhorn.io -n longhorn-system
Test on both S3 and nfs type of backupstore

Suggest having an automation test case for consistent tests and results. #4481

Thanks @c3y1huang.
@longhorn/qa QA should decide whether needs to add test cases before closing, even though the source ticket does not has require/automation-e2e. If needed, return back to implementation, then ask the Eng assignee to at least create the test case description/skeltion.


Discuss structure of modules, functions and data model

This issue should discuss the general structure of our Python modules, the functions and our internal data model. This will be entangled with the discussion and decision of the implementation details of the indicator correlation functions (see #6), but the general layout of the modules can already be discussed now.
It is not yet clear to me how we logically split up the code from PWSQC and pws-pyqc. Since both have a part which does flagging of faulty periods and a part which does bias correction, it seems logical to also have separate modules for flagging and bias correction. But it is also logical to keep code from PWSQC and pws-pyqc closely together.
First draft of module structure
flagging.py <-- not sure if this is the correct English term for adding the flags to the PWS timeseries
|── fz_filter()
|── hi_filter()
|── station_outlier_filter() <-- maybe needs a more descriptive name that indicates what method is used
|── indicator_correlation_filter() <-- not sure about this and the next one
|── calc_indicator_correlation()
|── ...

bias_correct.py
|── quantile_mapping() <-- use what is in pws-pyqc, but not yet sure about details
|── ... <-- something from PWSQC bias correction that is done in station-outlier-filter?
|── ...

Note that we can reference the papers and original codebase for each function in their docstring. Hence, we do not have to hint the origin of the methods in their function name.
Also not that finding neighboring sensors shall be done with the implementation from poligrain, see https://github.com/OpenSenseAction/poligrain/issues/15
Data model
Since we fully embrace xarray and xarray.Dataset in poligrain, it seems logical to also rely on it here. I would, however, first do some experiments when example data and an example workflow is ready. If we can write simple functions that work with 1D time series, we could just pass np.arrays and would have much more generic code. We can still use xarray.Datasets for loading and handling the data, but when passing to function we do not have to rely on it and just use the underlying numpy.arrays. But, let's do some experiments first.

Here is one idea for how the inputs of the filters like, faulty zero or high influx, could look like.

def some_filter_function(ds_to_check, ds_others, max_distance, min_n_of_valid_neigbors, parameter_1, parameter_2):
    """ Bla bla...

    Parameters
    -----------

    ds_to_check:
        xr.Dataset with dimension (id, time) of all time series that shall be flaggged. This can
        also be just one time series.
    ds_others:
        xr.Dataset with dimension (id, time) of the other time series from potential neighbors of
        the data in `ds_to_check`. This can be the same `xr.Dataset` as in `ds_to_check`, but it
        can also be a different one.  Within this function here, the fitting neibors will be selected.

    Returns
    --------

    ds_flag:
    ```
    # loop over PWSs:
    for pws_id in ds_to_check.id.data:
         # find neighbors and exclude `pws_id` if it is there
         # ...
         for id_neigbor in list_of_neigbor_ids:
             # do something with pairs of time series
   # aggreagte results to xr.Dataset with dim = (id, time)
   # ...
   return ds_flags

This way it can be applied to one full dataset of PWSs. But it can also be split up and be applied to one PWS by selecting one and passing it as  ds_to_check but still pass all neighbors (which will be passed are reference and not as copy, hence there should not be a large computational penalty). With this approach it should be easy to apply the functions on a very large dataset in an embarrassingly parallel manner. e.g. on HPC or on large workstation with many CPUs.


Created Locale for en-GH

Created test case for en-GH
Updated README file

@wocodes Thank you for the PR.
Please help resolve the issues with tests.

@mastermunj This has been updated

@mastermunj Thanks for the heads up. I've updated this PR. Kindly review

Thank you!


WIP, MAINT: Rename examples and tutorials

Adds automated redirect from plot_* to all of our examples, and renames them. @drammock for:

I should note that some, but not all, of the tutorials have had a number added to their filename, to enforce a specific sort order within their category. With the links changing anyway, now would be a good time to add numbers to the rest of them.

I implemented (but did not test) some custom_redirects code that you can use. I think you'll want to adapt it to take care of the number renaming. I added the conditional fname not in needed_plot_redirects.values() to the auto-plot_-redirect code, but you'll need to do a bit of testing to make sure things work. Can you take over and make the necessary code changes and git mvs?

FYI @drammock I push-forced after a rebase

TODO:

[ ] "modifying data in-place" is now in the intro category.  It should be made much more general (right now it appears to be mostly a showcase for raw.apply_hilbert and raw.apply_function, neither of which appear in any other tutorials)
[ ] the mne.Report tutorial is now in the intro category. It would benefit from a short introductory paragraph explaining what mne.Report is good for / why you might want to use it.
[ ] 4DBTi phantom tutorial is missing its dipoles in the final figure (should be a separate PR)

Fix crossref to this sklearn tutorial which doesn't have a target name

SG will give it one automatically:
$ python -m sphinx.ext.intersphinx https://scikit-learn.org/stable/objects.inv | grep ".*sphx_glr_auto.*blind_source_separation.*"
	sphx_glr_auto_examples_decomposition_plot_ica_blind_source_separation.py Blind source separation using FastICA   : auto_examples/decomposition/plot_ica_blind_source_separation.html#sphx-glr-auto-examples-decomposition-plot-ica-blind-source-separation-py

So you should be able to do something like:
:ref:`sphx_glr_auto_examples_decomposition_plot_ica_blind_source_separation.py`

4DBTi phantom tutorial is missing its dipoles in the final figure (should open a separate issue/PR)

No need, I think this is a dup of #9007 . Will comment over there / in @GuillaumeFavelier's PR

@larsoner this appears to be working now in my local testing.  Ready for review once CIs come back green.

This has a conflict again unfortunately

@larsoner I've put in an upstream PR for the meta is undefined theme error: https://github.com/pydata/pydata-sphinx-theme/pull/395
In the meantime I'll push a theme override here with the fix in place, to get Circle building again.

@drammock there is another conflict but I'll fix + push + merge in quick succession once CircleCI comes back happy here

Changed my mind, the build wasn't that far along

proof of concept: https://27567-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/misc/plot_ecog.html redirects to .../clinical/30_ecog.html

Awesome work @drammock !


OSFUSE-579: Fixed file permissions for all platforms

[merge] lgtm

Code not merged because @dhirajsb (Dhiraj Bokde) is not in the Admin list.

[merge] lgtm


Connect instructor training sessions to partnership agreements

We need a way to say "this event satisfies or partially satisfies our obligations for that partnership agreement".  (Right now, I'm storing that as free text.)  A many-to-many between events and partnership agreements (not partners) would do this.

A many-to-many between events and partnership agreements (not partners) would do this.

@gvwilson, do you mean Membership?

Yes, sorry.

The mechanics for this exist for tracking workshops. We should track the number of instructors we commit to in the agreement and the number trained. This way we can report on it to the partner organization when we have periodic meetings with them. The mechanics of this should already exist for how we're doing "imposed/completed/remaining" for two classes of workshops. Rather than workshops this would be people attending a special workshop (a ttt).

@gvwilson does it solve this issue? If yes, please close this issue.

I don't think so - the many-to-many between a specific membership agreement (rather than a specific institution) and specific training events still isn't there.  We'll tackle this after we get v1.9 out of the way.

We need a way to say "this event satisfies or partially satisfies our obligations for that partnership agreement". (Right now, I'm storing that as free text.)

@gvwilson, why storing this kind of information in notes is not enough?

Because then there's no easy way to find out what the status of our
obligations to partners is - right now, if I want to know that
2016-10-20-ttt-online fulfilled our commitment to Michigan State
University, I have to... well, I just have to know.

OK, so what about a simpler approach:

adding Membership.obligation_status which can be 1) not fulfilled, 2) partially fulfilled or 3) fulfilled
continuing to store more details in notes?

That lets you filter memberships (or even organizations) by our obligation status.

Let's discuss this after v1.9.

@maneesha do you want this feature in v1.10 or can we move it to the backlog? If you want this feature, what do you think about the simpler approach I proposed?

I'm reactivating this discussion based on conversations that the Instructor Training team (@maneesha, @karenword, and myself) and @tracykteal and @sheraaron have been having about changes to how we allow members to divide up their seats in instructor training events.
When an institution signs on as a member, they receive a certain number of seats in instructor training. Currently (at least in theory), all of those seats are supposed to be in a single event, making it possible to do this binary "fulfills"/"doesn't fulfill" tracking.
However, we are moving to a system where we allow members to divide their seats across multiple instructor training events. To accommodate this, we need to be able to record for a particular member institution:

how many seats in instructor training they have for a particular time period,
how many trainees they have had assigned to an instructor training event already.

Together, these will allow us to calculate:
3) how many seats they have remaining.
The number in (1) is the number of seats in their membership contract PLUS (potentially) any additional seats they have purchased in instructor training. This means that number needs to be editable.
The number in (2) should be calculated by assigning trainees to a member institution as well as a training event. We already assign trainees to events, if we can assign to a member institution, then we can do this math.
Currently, for tracking membership information we have the following:

We would need to add a field to the membership category that tracks (1), (2), and (3) above. I know it's too late to get this change into the Aug 31 release. Can you please take a look at what we're requesting and let me know if it's possible to get it into the release after this one? What is the timeline for the subsequent release? I'm happy to provide any more information that is needed, just let me know.

We currently track the number of workshops run under a membership agreement. We also need to track the number of instructors allowed and the number trained under each agreement.  Here is a draft of what I thought this may look like.

@maneesha the draft looks doable. Just one question to make sure I understand it correctly:
this change means that memberships will not be about "regular" (non-TTT) workshops, but about seats in TTT workshops, correct?

@pbanaszkiewicz  Yes this refers only to TTT workshops.

@maneesha so "workshops w/o fee per agreement" and "self-org. workshops per agreement" will not change?

@pbanaszkiewicz  - That's correct. Those fields would continue to be tracked as they are currently. There would be a new field (or fields) to track the information about number of seats in TTT events.

@maneesha @ErinBecker @karenword @sheraaron @tracykteal  I have it almost complete now. We should schedule a video conference this week so that I can present it to you (it's faster than setting up a AMY development instance server).

👍 🎉


Update aws provider to remove existing dns records on update

What
Update the AWS DNS provider record update to first remove existing records and then re-create them (Much the same as google provider)
Why
Changing things like the type or record, routing policy etc.. will currently cause a failure like the following:
InvalidChangeBatch: [RRSet of type CNAME with DNS name myapp.mn.hcpapps.net. is not permitted as it conflicts with other records with the same DNS name in zone mn.hcpapps.net.

This prevents us from switching routing policy types in the dnspolicy (simple/loadbalanced) since the type could be different (CNAME vs A record)

This issue is stale because it has been open for 60 days with no activity.

This issue was closed because it has been inactive for 30 days since being marked as stale.


Implement Expected Error Classes/Messages, add Ignored Classes/Messages

Before contributing, please read our contributing guidelines and code of conduct.
Overview
This PR implements Expected Errors in the Ruby agent, and allows server-side configuration for ignored/expected error classes and messages. This PR does NOT implement ignoring/expecting errors by status code; this will be addressed in a future PR.
Formerly the error collector only used a single config setting for ignored error classes and stored this in an instance variable. In this PR, the work of loading ignored/expected errors and determining at runtime whether an error is ignored/expected/neither is handled by the ErrorFilter class, which is instantiated by the error collector on initialization. Some internal method names in error collector were renamed for clarity.
Related Github Issue
https://github.com/newrelic/newrelic-ruby-agent/issues/454
https://github.com/newrelic/newrelic-ruby-agent/issues/456
Testing
Unit tests for ErrorFilter and updated tests for ErrorCollector are included. Further end-to-end testing may also include:

test no Errors/* metrics are incremented
test ErrorsExpected/all is incremented for expected errors
test nothing is recorded for ignored errors
test changing SSC properly updates ignored/expected errors in running agent

Reviewer Checklist

[ ] Perform code review
[ ] Add performance label
[ ] Perform appropriate level of performance testing
[ ] Confirm all checks passed
[ ] Add version label prior to acceptance

Just noting that I will probably add additional multiverse tests to this branch.


Update TypeScript definition of messages. Fixes #246

Coverage remained the same at 88.527% when pulling 42315980a91900f39cdc933520f879660a07ba43 on jorispz:master into 4bc3a134bcb45feb9376a754f9499a18fc85756f on nats-io:master.

I believe the proper definitions for publish are:
	publish(subject: string, callback: Function):void;
	publish(subject: string, msg: any, callback: Function):void;
	publish(subject: string, msg: any, reply: string, callback?: Function):void;

For request, they are somewhat ill-formed, as the callback is always required:
	request(subject: string, callback: Function): number;
	request(subject: string, msg: any, options: SubscribeOptions, callback: Function): number;

Can we have request do a more async/wait or promise syntax vs callback?

@derekcollison - yes by using ts-nats. There's no point in starting to mix the event library with the promise/async library.

Thanks for the feedback, I updated the TS definitions to your proposal.
For my personal project I switched over to ts-nats, because the async/await syntax suits my problem much better. Thanks for working on these libraries!

@jorispz thanks for the contribution - glad you are liking ts-nats.


[WIP] first attempt at Python package

adds Travis CI
setup.py for installation
tests with py.test
uses recent TESTED_DONT_TOUCH code

This is a work in progress. Things left to be done:

[ ] merge in latest changes
[ ] verify that latest version of TESTED_DONT_TOUCH produces same results as this package
[ ] make Travis CI work

@talumbau How did you get those check boxes in your comment?

@evan-magnusson Github understands a special syntax that happens to very handy:
https://help.github.com/articles/writing-on-github/

@talumbau, @evan-magnusson and I will go over this tomorrow morning.

OK @rickecon, but don't get into the guts too much. The main contributions are:

use a function run_.... inside of SS.py and TPI.py so that we don't have to use subprocess to call that work

try to avoid using pickle files to pass data between SS and TPI (mostly successful, still some work to do)

abstract certain read-only parameters to a parameters.py file

The goal is to get this in to a reasonable shape so that further changes to TESTED_DONT_TOUCH can happen inside this package.


Control: design the simplest form of the MRAC controller

@Capri2014 Fixed the first two issues per your comment. For the third one (anti-windup design), I will fixed it with another new pr.


Type issue with Select component multiple prop

Current Behavior

Expected Behavior

Steps To Reproduce

Add multiple={true} to <Select.Root.

Link to Reproduction / Stackblitz (reproduction template)
No response
More Information
I'm using this component: https://www.shadcn-svelte.com/docs/components/select
This issue may be related to MeltUI.

Closed by https://github.com/huntabyte/bits-ui/releases/tag/v0.10.0 (some minor breaking changes to check before updating bits-ui)


Output uncorrected tables without going through all of curate

We recently encountered a case, where samples were (intentionally) extremely similar to each other, despite being tagged as different tissues. This led to amalgkit removing a couple of samples. Additionaly for that dataset, we didn't need the amalgkit corrected output at all. So it would be nice to have an option to just output all data before the SVA correction and then stop, saving some time in cases where SVA correction is not desired.

Done here:
9a63d9dfd7cb9e30db31a8d341adceea6bab73c7
--skip_curation yes stops curate after the transformation of the  count table and the curate_group.mean version of that table and before any kind of batch-effect removal/outlier removal/mapping-rate cut-off.
--skip_curation no behaves normally (default. https://github.com/kfuku52/amalgkit/commit/22e34c6d2779138bb7729d37e300a89fab9b54a9).

Thank you. Could you bump the version?

done


Osb responses to include the broker name if an error occurs

Pull Request Template
Motivation
Sometimes it is hard to know whether the problem for certain OSB calls is because of the Service Manager or the broker itself. This change sends also the name of the broker and its response to the user.

Coverage decreased (-0.007%) to 89.726% when pulling<PHONE_NUMBER>9b910eca3e573d4aa9b61bff9866ca on osb_responses into e9af4a3617ebf581e6215e49d288f337427e0d8e on master.


Training for CAPE dataset

Hi
I would like to train CAPE dataset by myself.
By following the guidance, I put CAPE dataset under the data directory as shown below.

data/CAPE/03375
data/CAPE/cape_release

And I run the command for training.

python train.py datamodule=cape subject=3375 datamodule.clothing='blazerlong' +experiments=cape

Then the error was shown below.

ValueError: Dataloader returned 0 length. Please make sure that it returns at least 1 batch

Do you have any idea to solve it?
Thanks

The CAPE dataloder looks for data in data/CAPE/03375/<sequence_name>/<sequence_name>..npz. Could you check if the files are indeed there?

this issue seems no longer active so I am closing it. Feel free to re-open it if the problem remains


Refactor transform code to use functions from Horizon

Many of the go files in the stellar-etl/transform repo are almost direct copies of functions contained in the Horizon/internal/ingest repo. This appears to be happening for one of two reasons:

Some of the copied functions in Horizon are not exportable.
The data structures passed in to some of the functions are transformations and are not the expected data structure in the original function.

Is it worthwhile to refactor the stellar-etl repo to import the Horizon functions instead of supporting one-off functions?
Pros

guaranteed to stay in sync with Horizon when there are changes to the schema
SDF only has to support one, unified codebase instead of multiple with the same functionality
will make stellar-etl easier to maintain

Cons

time spent doing the refactor takes away from other Hubble 2.0 tasks
could be unaware of breaking schema evolutions if downstream tables do not have the appropriate columns defined
If function is not exportable, would need to work with Horizon team to make it exportable

Example
The extractOperationDetails function matches the Details function in ingest/processors

Hubble will start deviating from Horizon. We have decided to keep the two decoupled at the moment, though if the community starts using the ingest data it may be useful to make the processors library public (just the part that transforms ledger entries, does not need to create new records/ids in horizon)


Expose IdToken

Would it be possible to make com.microsoft.aad.msal4j.IdToken public and have com.microsoft.aad.msal4j.IAuthenticationResult be able to return a parsed token object?
The code already exists in AuthenticationResult, but isn't exposed, creating unnecessary work.

Hi @maltalex, ITenantProfile from IAuthenticationResult contains all claims from idToken in the form of key-value pairs,  do you consider exposed IdToken (contains only standard claims) easier to use compared to all claims in ITenantProfile?

Hi @SomkaPe
I haven't realized that ITenantProfile contains the fields from the id_token. Thanks!
But I think that somewhat highlights the problem - keeping the id_token values in a generic map makes the API less discoverable.
I think it would be more convenient to expose an object so developers will be able to explore the API in the IDE rather than looking up the documentation at every step. Or at least add some actual documentation to the tenantProfile field beyond the laconic tenant profile javadoc and add an enum of id_token field names to make looking through the map easier.

Not planning to revisit this API at this time.


The course listing is not correctly refreshed when returning from another view

When returning from another view, the course listing shows only the featured content.
to get the full course list, one has to enter the featured content and close it again (no action is required).
The course list should be always fully visible.

fixed now.


Seattle Building Footprint Digitizing

Dashboard
Spreadsheet

Use the building Ids below to view the data on the dashboard website
Go to the spreadsheet, find the row with that building id, get the building address, and use google maps to preview the satellite image of the building
In ArcPro create a shapefile and digitize / create a polygon for the building outline as you see it in the satellite image (use the lat longs from the spreadsheet to get you to the correct location).  The shapefile should have a column "building_id" and record the associated building id for each geometry.

Digitize these Seattle Building IDs:
21231 - digitize building in NW corner
21616 - digitize school
49894 - digitize 4 buildings
50067

For Joseph to fix:

21231 - split, and remove everything but the NW corner

For Joseph to fix:

21231 - split, and remove everything but the NW corner

Fixed-- tool to break apart merged/multipoint polygons is "Explode" in ArcGIS Pro.

Great, here is a new list to digitize.  I have added details for how to digitize each one / what to look for specifically.

Dashboard Building ID
Notes

21570
Current shape in Seattle Dashboard is wrong (school was rebuilt recently).  Please use satellite to digitize correct footprint.

50175
There are two L shaped buildings in this apt complex.  One is in the dashboard, one isn't.  Please digitize missing building (East one).

27774
There are three buildings in this apt complex, two of them are already in the dashboard, but one is missing.  Please digitize the missing building (on satellite, it has a black rooftop like the other two, and it is on the West side of the other two).

All new entries should be up to date. The file path to the updated shapefile is here:
P:\proj_p_s\Seattle Building Dashboard\2023 update\DigitizingFootprints_20230921\DigitizedFootprints_20230926.shp
And the file path to the project (in case you want to tour around for QA) is here:
P:\proj_p_s\Seattle Building Dashboard\2023 update\DigitizingFootprints_20230921

For Joseph to fix:
21321 - explode into mult. polygons, delete all but NW corner.
49894 - you digitized one of the four buildings, but there are three other buildings that need to be part of this (again, leave them as single polygons)
50245 - explode into mult. polygons
50309 - redo this one, just a single building
50177 - explode into mult. polygons

21321- Exploded and deleted all but NW corner (View at Bitter Lake Apartments)
50245- Exploded into separate records (Cascade I and II Combined)
50177- Exploded into mult. records
50481-Exploded into mult. records (Sorento Flats)
49894- Added three buildings to make 4 total for Array Apartments
50309- Re-digitized single building and ensured the geometry calculated/ zoom-to fiunction works.
Updated Shapefile location:
P:\proj_p_s\Seattle Building Dashboard\2023 update\DigitizingFootprints_20230921\DigitizedFootprints_20230926.shp


Resolve custom credential types

https://github.com/hyperledger-labs/acapy-java-client/issues/82
Signed-off-by: Philipp Etschel<EMAIL_ADDRESS>

obsolete


Dev navbar

Functionality:
Added Navbar Service and component
Solution:
Added service to add the navbar to the list and component to display the navbar
Risk level:

[x] high
[ ] medium
[ ] low

How to test:
Check the top of page in board

Created by mistake

Created by mistake


Update README.md

fixed a typo

I signed it!

Sorry for the delay, and thank you for the PR!
Unfortunately, it looks like this was superseded by some other changes and is no longer valid, so I'm going to go ahead and close it. If you find any more in the future, I'll try to get them merged in pretty quickly.
Thanks!

No problem.
Thanks!


Fix high cpu usage of Invoker under certain cases

Not reading from a socket with event could result in that socket always being ready and can cause high cpu usage on select.
This makes sure that for disconnected/crashed process, we always drain the socket.
cc @iffyuva @kgrz

Never faced this issue. I will try out this PR locally for a day and let you know. Thanks.

Been trying out this PR for 2 days. No issues found.


Unable to use latest version of Redux & React-Redux

Describe the bug
Soya-next seems not compatible with the latest redux version (7.0.0^). We got this error when trying to update the redux library version. Since we plan to migrate the class component to the functional component, we want to utilize useDispatch and other new functions in the latest react-redux version.
To Reproduce
Steps to reproduce the behavior:

Update redux higher than version 7.0.0 and also update the react-redux following the dependencies requirement
Load any page and the error page will appear

Expected behavior
Able to use the latest version of redux & react-redux
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I think this issue can be closed ya since you already successfully updated the react-redux package to v7 in this pr #430. :tada:


Feature/jsonapi links

Takes care of first two issues on #55

[] Properly support links on included resources
[] Clarify namings

[Current coverage][cc-pull] is 95.41%

Merging [#65][cc-pull] into [master][cc-base-branch] will decrease coverage by 3.32%

@@             master        #65   diff @@
==========================================
  Files             6          7     +1
  Lines           318        371    +53
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            314        354    +40
- Misses            4         17    +13
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [0427396...12e3c41][cc-compare]
[cc-base-branch]: https://codecov.io/gh/devlucky/Kakapo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/devlucky/Kakapo/compare/04273960c0665e3bab878ffb36c3fe16a68d2ea7...12e3c414e6b070595675a3a9df9a914db39eb5a5
[cc-pull]: https://codecov.io/gh/devlucky/Kakapo/pull/65?src=pr


When you have a multi value date & time field, and you try to filter, you are getting error

Error: Could not load record list: unsupported IN operator on a single value field. (same happens when you are also having just a date and just a time field)

Fixed:
What:

Fixed record field issue with contain/not contain filter for multi value data time field.

How:

By adding explicit type casting for date time values to cast into jsonb format while parsing the record filter query.

Tested and can confirm the error isn't present anymore


Network Discovery

No mention which choice to make when presented, on first login to vm, with the choice to allow /disallow this new vm to be discoverable by other PCs and devices on this network.

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

No bearing, huh?


[BUG] - Title Goes Here...Community Page is Not Responsive – Heading Font Size Issue

Current behaviour
Currently, the heading font on the Community Page does not scale properly when the page is resized or viewed on different devices. It remains small even on larger screens, making the page look unbalanced and not optimized for responsiveness. The font size should increase in proportion to the screen size, ensuring better visual hierarchy and readability across devices.

Expected behaviour
The heading font on the Community Page should adapt responsively to different screen sizes. It should use a relative unit like rem so that on larger screens, the font size is appropriately bigger, and on smaller screens, it adjusts to a smaller, readable size. This ensures better readability and a user-friendly design across all devices.
Reproduction steps
Go to the Community Page on the website through phone view.
Scroll down to view the entire page content
See the error with the heading font size not adjusting based on screen size.

Screenshots

Browsers
Chrome
OS
Windows
Are you contributing for a program ?
GSSoC23
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@Dipu2552003  you can start working on this


Can you show an example of the problem? It's not clear what you are talking about. Are the strings not converted correctly?

computer A works fine, but computer B bad.
computer A uses 'utf-8' for encode and decode in python side, but computer B uses 'gbk' for encode and decode in python side, the encode and decode way depends on System way.
how to resolve this? looking help.

@extremeheat


Release endpoints returning 404

Are release endpoints working? If I make a request to _apis/build/builds?api-version=5.1-preview.5 I get results fine, but I have a 404 when I hit _apis/release/releases?api-version=5.1-preview.5.

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

ID: f88a412f-b63d-af24-2dc5-b72c79a87d4f
Version Independent ID: 44a6c5d6-3f8a-563e-434d-e19ec337224e
Content: Releases (Release)
Content Source: docs-ref-autogen/5.1/release/Releases.yml
Product: devops
GitHub Login: @wnjenkin
Microsoft Alias: whjenkin

hello,
how you solve this problem? also I get a 404 error page not found message...

You need to use "vsrm" i.e. https://vsrm.dev.azure.com/<your_org>/ instead of https://dev.azure.com/<your_org>/ or $env:System_TeamFoundationServerUri instead of $env:System_TeamFoundationCollectionUri


Me

[Enter feedback here]

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

ID: d80fc813-0f5a-a286-fc1c-c792c96c15b9
Version Independent ID: cd89f9f6-c81b-e64e-49fb-54cf639eef37
Content: Contribute to the .NET documentation repositories - Contributor guide
Content Source: Contribute/content/dotnet/dotnet-contribute.md
Product: non-product-specific
GitHub Login: @carlyrevier
Microsoft Alias: cahublou

Closing this issue because there is no issue content.


JoErNanO: Watch fetchbus.com

JoErNanO requests the watch of the watch_keyword fetchbus\.com. See the MS search here and the Stack Exchange search here.

fetchbus\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Fix isolateModules not working correctly when module has already been imported

Summary

This addresses #7863 where any requires inside isolateModules callback were retrieving modules from the regular module registry if the module was previously required in a non-isolated scope.
It didn't work previously because the logic checked for this._moduleRegistry.get(modulePath) FIRST to assign the variable as a regular module, which would always evaluate to true if the module had already been loaded.
The fix was to update the associated if block to check that this._internalModuleRegistry exists FIRST to assign the variable as an isolated module.
Test plan

Additional unit tests in runtime_require_module_or_mock.test.js
Linked jest-cli to my local sandbox project and ran additional tests (see below)

import incrementor from './incrementor';

describe('incrementor', () => {
  it('gets incrementor from the registry', () => {
    incrementor.increment()

    const cachedIncrementor = require('./incrementor').default

    expect(cachedIncrementor.getState()).toBe(2)
  })

  it('gets isolated incrementor', () => {
    let isolatedIncrementor

    jest.isolateModules(() =>
      isolatedIncrementor = require('./incrementor').default
    )
    expect(isolatedIncrementor.getState()).toBe(1)

    isolatedIncrementor = require('./incrementor').default
    expect(isolatedIncrementor.getState()).toBe(2)
  })

  it('can isolate the same module multiple times', () => {
    let isolatedIncrementor

    jest.isolateModules(() =>
      isolatedIncrementor = require('./incrementor').default
    )
    isolatedIncrementor.increment()

    jest.isolateModules(() =>
      isolatedIncrementor = require('./incrementor').default
    )
    expect(isolatedIncrementor.getState()).toBe(1)
  })
})

Codecov Report

Merging #8634 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8634      +/-   ##
==========================================
- Coverage    63.4%   63.39%   -0.01%
==========================================
  Files         274      274
  Lines       11342    11341       -1
  Branches     2770     2770
==========================================
- Hits         7191     7190       -1
  Misses       3534     3534
  Partials      617      617

Impacted Files
Coverage Δ

packages/jest-runtime/src/index.ts
68.96% <100%> (-0.09%)
:arrow_down:

Continue to review full report at Codecov.

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

This only updates behavior with regular modules and not mocked modules. The field name _isolatedMockRegistry exists and there's similar code inside requireMock method but I left it alone since I'm not even sure what the use case would be for isolating mocked modules

This only updates behavior with regular modules and not mocked modules. The field name _isolatedMockRegistry exists and there's similar code inside requireMock method but I left it alone since I'm not even sure what the use case would be for isolating mocked modules

From what I understand the use case for this is for whenever you are requiring a module that is mocked, which could be stateful. In some cases that mock might have been declared outside of the test file. For example in a setupFilesAfterEnv or moduleNameMapper

Made some revisions addressing @rogeliog's comments:

Accommodate isolating mocked modules
Dependencies being imported within an isolated module won't be indirectly isolated. This is accomplished by adding a new boolean field _isolatedRequireInProgress to the Runtime class. Its purpose is to keep track of the current isolated module being loaded. If the value is set to true, avoid isolating any modules. A local variable disableIsolatedRequireInProgress within requireModule and requireMock signal when to begin isolating again.

(also idk what happened here, a bunch of checks just failed on a single test in jest-util. I'm without context but it seems unrelated to my changes)

Not sure about CI... Master just passed, would you mind rebasing. Maybe circle was weird for a moment?

Seems like the test failure's reproducible with my code. Not sure what to do about this one 😕

@rogeliog Ready for re-review

@willym1 could you rebase this, please?

Any updates here? @willym1 do you need any help?

No updates since November. What's going on here ?

Just waiting for a rebase, I think it's good to land? Maybe @rogeliog wants to give it another lookover?

Hi - sorry this had been sitting for a while and I've forgotten about it. Last time I checked it seems there was still some unresolved implementation discussion.
Will hop on this PR again this weekend and see whether there's additional changes needed on my latest update and try to merge if everything's good to go.

Good to see that you're all still working on this.
Thank you for all the good work :+1:

@willym1 seems like this broke a test in packages/jest-regex-util, could you take a look? Whatever the regression there was, we should add a dedicated test for it

Yeah there's an issue with how isolated modules deals with mocks. Will investigate some more

@willym1 were you able to look more into this?

I'm unsure if this has been fixed by another PR, but I'll just comment here to prevent bot supremacy.

I've merged in main and resolved the conflicts. That said, I don't know the state of this. @willym1 are you still up for finishing this? 🙂

#10963 seems to have addressed the same issue?


As a j40 team member, I want my data pipeline tested so that I know when we generate new versions of the score or available processed data, we'll get good data in the expected format.

Description
This user story is all about making sure we have adequate testing in place to consider our backend (data pipeline and score generation) production ready!
Solution
Write tests! See the issues!
Describe alternatives you've considered
We can not have tests and continually live in a state of anxiety and freakouts and fire-fighting when doing new data processing or score experimentation.
Links to user research or other resources
Tasks
Definition of "Done"

Next step is that @esfoobar-usds and I sync on this to figure out holistically how we want to do end to end testing with docker compose.
Some notes so far:

Tile generation is CPU heavy and that works, so we think compiles will work in github actions.
This data is public, so rather than generating a small synthetic dataset, we can instead pull out a subset of the data (maybe just one state).
We can run this just on merges to main, rather than every push to a PR.

Unfortunately I think we need to run on every merge. I also believe the data should come from S3 mini-fixtures and not from the data sources themselves. We can discuss this afternoon.

Also, no tile generation needed -- just the score and score-post.

@esfoobar-usds Assigning this to you because I think you are taking over https://github.com/usds/justice40-tool/pull/1134