explicitly create interpolants from functions

Description
In the standard parameter sets, create the interpolants from functions explicitly (instead of relying on the ParameterValues class to do it). This allows finer control of hyperparameters (e.g. interpolator).
Using "cubic" interpolator for OCV gives much faster performance than linear interpolator (e.g. 1s -> 0.5s solve time for Ai2020 on my laptop)
Fixes #2410
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

ready for review (changed a bit since @Scottmar93 reviewed)


Updated PywalZen for 1.0.1-a.14 + Preferences

I fixed the theme for the latest update and added some preferences, I hope they work. I couldn't find a way to test them with the browser.

I guess I'll create an issue, I don't really get those errors. Sorry.


Intra-timestamps join broken for spatial views on 0.18

See e.g. this:
import rerun as rr

rr.init("rerun_example_points3d", spawn=True)

rr.set_time_sequence("frame", 42)
rr.log("points", rr.Points3D([[0, 0, 0], [1, 1, 1]], radii=-5, colors=[255, 0, 0]))
rr.log(
    "points", rr.Points3D([[10, 10, 10], [11, 11, 11]], radii=-5, colors=[0, 255, 0])
)

On 0.17 this yields what you'd expect:

On 0.18 this will fail though:

The is a regression following https://github.com/rerun-io/rerun/pull/7199, which fixes that static/override case but breaks the common case.

urgh. I feared something like that would happen but we assumed all is well when we tested overriding static data :(

I've managed to reproduce in both Python and Rust.
Fun fact: this only happens when not logging to a custom timeline.
Python:
import numpy as np
import rerun as rr
import time

rr.init("rerun_example_image", spawn=True)

for i in range(0, 100):
    # NOTE: uncomment this line to fix the perf issue.
    # rr.set_time_sequence("frame", i)

    for j in range(0, 100):
        image = np.zeros((200, 300, 3), dtype=np.uint8)
        image[:, :, 0] = (i + j) % 255
        image[50:150, 50:150] = (0, 255 - ((i + j) % 255), 0)

        rr.log(f"images/{j}", rr.Image(image))

    time.sleep(0.010)

Rust:
use ndarray::{s, Array, ShapeBuilder};

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let rec = rerun::RecordingStreamBuilder::new("rerun_example_image").spawn()?;

    for i in 0..100 {
        // NOTE: uncomment this line to fix the perf issue.
        // rec.set_time_sequence("frame", i);

        for j in 0..100 {
            let mut image = Array::<u8, _>::zeros((200, 300, 3).f());
            image.slice_mut(s![.., .., 0]).fill((i + j) % 255);
            image
                .slice_mut(s![50..150, 50..150, 1])
                .fill(255 - ((i + j) % 255));

            rec.log(
                format!("images/{j}"),
                &rerun::Image::from_color_model_and_tensor(rerun::ColorModel::RGB, image)?,
            )?;
        }

        std::thread::sleep(std::time::Duration::from_millis(10));
    }

    Ok(())
}

Ha dang, this might be worse than I thought -- I think this breaks log_components workflow completely.
I'll add dedicated checklists so this doesn't surprise us again.

Found a lot more issues of that nature, many of which were not introduced by https://github.com/rerun-io/rerun/pull/7199.
I'll have a PR ready for all known visualizer-query bugs, at some point.
The first problem is that the basic overrides test suite doesn't even run on 0.18.0 it turns out:

https://github.com/rerun-io/rerun/issues/7294


Allow L.GeoJSON options to be passed

I was trying to use this, and was running into problems because I use some features like onEachFeature and filter from L.GeoJSON.  I used leadlet-realtime as a template to add support for passing the L.GeoJSON options.
Please let me know of any feedback you have, or anything I can do to help get this merged 😄

Ok for me!

Thanks!  Glad to help!


fix(settings): Extend ALLOW_TOKEN_PARSERS if custom one is provided

Closes #647

Hi @fsbraun ,
This one should fix it.
Exampe in interpreter that it works:


changed layout

moved student to top
showed substitute text in dimmed extra line

moved student to top
showed substitute text in dimmed extra line


IndexError: list index out of range

Hello, we use the code demo in the project page using the above image, the following error occurred:
      6 # prepare face emb
      7 face_info = app.get(cv2.cvtColor(np.array(face_image), cv2.COLOR_RGB2BGR))
----> 8 face_info = sorted(face_info, key=lambda x:(x['bbox'][2]-x['bbox'][0])*x['bbox'][3]-x['bbox'][1])[-1]  # only use the maximum face
      9 face_emb = face_info['embedding']
     10 face_kps = draw_kps(face_image, face_info['kps'])

IndexError: list index out of range

We find that the face_info in Line 7 is a empty list.

 Try another image.


As an admin, I want the CSV export to include source so that I can distinguish content from HathiTrust, Gale/ECCO, etc.

testing notes

[x] use the "download as CSV" link in django admin to download test data, including newly imported content; confirm that there is a "source" column and that it is set accurately to "Gale" or "HathiTrust"

dev notes

add source header and source display value to existing admin csv export

CSV download successful, "Source" column present on CSV with either "HathiTrust" or "Gale" accurately displayed.


Refactoring LPC17xx System Controller

Resolves #1140

Coverage increased (+0.6%) to 86.665% when pulling e439481ca32b38d4ca014ed35294a9dfc8d178fa on HuangDave:lpc17xx_system_controller into c886425c6ee9c51aa03a5df1aa06f4b9c3039205 on kammce:master.


Dropping six.

It seems that if py::exec get fixed (with respect to calling other functions defined in the same call), we should be able to

drop the custom six-based exec function.
drop the workaround due to the extra function in the traceback.

Also, six is used for selecting between PY3 and PY2 in is_complete_request.

https://github.com/pybind/pybind11/issues/1654


issue with large numbers

in typst floats are 64 bits, meaning we should be able to handle large numbers such as 10e300. Unfortunately oxifmt is doing a computation that goes out of bounds that prevents writing the typst code:
#strfmt("{0:e}",10000000000000000000)

In my case I'm reading numbers from a json file in typst and using strfmt to display them. Can you fix this?
error: the result is too large
    ┌─ @preview/oxifmt:0.2.1/oxifmt.typ:228:21
    │
228 │   let mantissa = f / calc.pow(10, exponent)
    │                      ^^^^^^^^^^^^^^^^^^^^^^

help: error occurred in this call of function `_strfmt_exp-format`
    ┌─ @preview/oxifmt:0.2.1/oxifmt.typ:374:20
    │
374 │       replacement = _strfmt_exp-format(calc.abs(replacement), exponent-sign: exponent-sign, precision: precision)
    │                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Ah, good catch! Will be taking a look once I can.

by the way, I got a temporary solution:
#let toMathRepresentation(number, digits: 2) = {

  if (type(number) != "float" and type(number) != "int") {
    [N/A]
  } else {
    // Define the maximum exponent to prevent overflow
    let max_exponent = 308;

    // Calculate the exponent
    let exponent = calc.floor(calc.log(calc.abs(number)));

    if exponent > max_exponent {
        "Infinity"
    } else {
        // Initialize mantissa
        let scaled_number = calc.abs(number);
        let remaining_exponent = exponent;

        // Scale down by powers of 10 within Typst's limits
        while remaining_exponent > 0 {
            // Determine the largest power of 10 we can divide by without overflow
            let scale_down = calc.min(remaining_exponent, 18);
            scaled_number = scaled_number / calc.pow(10, scale_down);
            remaining_exponent -= scale_down;
        }

        // Once scaled, the result is within [1, 10), so this is our mantissa
        let mantissa = scaled_number;

        // Round the mantissa to the specified number of digits
        let rounded_mantissa = calc.round(mantissa*calc.pow(10,digits))/calc.pow(10,digits);

        // Format the result
        [$#rounded_mantissa times 10^(#exponent)$]
    }
    }
};

maybe you can use this. Cheers!


Running PR for V1

Progress

Have introduced two packages: store and basic
Packages are now in typescript 🎉
Packages are now linted (with eslint)!
Included testing for the store and evaluation scripts
Move to a redux architecture that can include the evaluate middleware or not. (by default this will be included)
Opinionated styles are starting to be removed (e.g. color, font)
single file for each component
Removed boiler-plate code for creating components, including fighting with typescript generics so new components don't have too!!!
Performance improvements - only render the components that actually changed! 🚀

There are a few suggested breaking changes on name/value/bind as well as transform on the display component. I would be curious on hearing from  @lrq3000 or @J2thearo on these changes to see if they make sense!
New Basic Components
Working with material web components to bring new components!

<ink-switch> - material UI switch
<ink-checkbox> - material UI checkbox
<ink-radio> - material UI radio
<ink-select> - material UI select box #9
<ink-input> - material UI textarea
<ink-visible> - Div that makes things invisible on demand

[ ] var list? do we need this? Now that there is CSS control, maybe not?

Changes to Ink Article

Now using

Now using  for both asides and callouts.
These are now just plain CSS - so should be easy for people to re-theme
<ink-code> and <ink-demo> have been moved over
<ink-equation> is ported, and works a lot better on the rendering side (no more 1-frame lag)

[ ] Outline (to make @choldgraf happy)
[ ] Figure -->

[ ] Some level of cross-referencing on the page (is this <ink-ref>)? And a numbered attribute?
[ ] Helper functions to render math inline.
[ ] Quote, byline
[ ] Card --> not sure about this one?!

Charting
I would like to get this merged and then can move on to the chart library -- it is a different animal and needs some love.
Resume
Similar to charting, this should likely be mostly CSS? Different library, out of scope of this PR.
User-defined functions

Execution is now in the main context and can access scripts defined there (see #12)

Runtime State
I have moved to a single redux store to manage the state. This is split up into {variables, components} the low-level interface looks like:
const x = store.dispatch(ink.actions.createVariable('scope.x', 3));
const max = store.dispatch(ink.actions.createVariable('scope.max', 9));

const range = store.dispatch(ink.actions.createComponent(
  'range', 'scope.myRange',
  { value: { func: 'x' }, min: { value: 1 }, max },
  { change: { func: '{x: value}' } },
));

// Can set/get the properties
x.get()
x.set(4)
const { min, max } = range.state;

A version of this will be exposed in the window as ink so that you can get/set variables in other programs which is needed for more control: (e.g. see #12 #10).
Creating a new component
I have added a base-class BaseComponent that does the generic registering and unregistering of the component as well as a class wrapper @withInk that injects properties that you define in a ComponentSpec and give the relevant setters/getters for properties and events as well as playing nice with lit-element. The basics of this new setup gets the boiler-plate from 74 --> 18 lines of code (~25% of the size). The @withInk wrapper I think is also more accessible (to debug etc.) than what I had before.
export const InkDisplaySpec = {
  name: 'display',
  description: 'Inline display of values',
  properties: {
    value: { type: types.PropTypes.number, default: NaN },
    format: { type: types.PropTypes.string, default: '.1f' },
  },
  events: {},
};

@withInk(InkDisplaySpec, { bind: { type: String, reflect: true } })
class InkDisplay extends BaseComponent<typeof InkDisplaySpec> {
  updated(updated: PropertyValues) { onBindChange(updated, this); }

  render() {
    const { value, format } = this.ink!.state;
    return html`${formatter(value, format)}`;
  }
}

Breaking Changes
Name/Value/Bind
There are a couple of issues with the previous naming conventions. It was is not specific enough for multiple event types (hover, drag, click, etc.) and there is no option for being able to add named components. This could be very helpful to react to events when a component enters the screen, show the component.min value, etc. The previous name attribute was used to set :value="${name}" and bind="{[name]: value}" which amounted to two way binding in the component. This was a handy shortcut and I think it should stay, however, be renamed to bind now that events are explicitly named.

name for components will now be used for the actual name of the component (should be unique in that scope)
introducing named events, which will allow components to have multiple types of events
bind is used as the default event type on components that allow it.

Previous version:
When you eat <ink-dynamic name="cookies" min="2" max="100"> cookies</ink-dynamic>,
you consume <ink-display :value="cookies * 50" format=".0f"/></ink-display> calories.

Changes to:
When you eat <ink-dynamic bind="cookies" min="2" max="100"> cookies</ink-dynamic>,
you consume <ink-display :value="cookies * 50" format=".0f"/></ink-display> calories.

This is equivalent to:
When you eat <ink-dynamic :value="cookies" :change="{cookies: value}" min="2" max="100"> cookies</ink-dynamic>,
you consume <ink-display :value="cookies * 50" format=".0f"/></ink-display> calories.

Action / Button
The bind syntax doesn't make sense for the ink-action and ink-button components, it should really be an event and there isn't a value to "bind" to. This should change to :click to return an event transform object.
Transform

I am not convinced that transform should remain on the display component. This can be done in a single call in the :value function: <ink-display :value="fullName.split(' ')[0]">. I do think that it should remain in the dynamic as the value is different than how you might display the variable.

Questions

[x] Should the store package be called runtime? Would be similar to svelte, observable, idyll, etc.
[x] Move the repo to @iooxa (likely) probably leave the repo ink-components on github/npm for the main package. So packages are @iooxa/runtime etc.
[ ] A lot of the ink-article work is really just CSS, these should probably be removed as WebComponents. e.g. ink-aside --> aside ink-article --> article as these are standard HTML components.

[x] Is there an HTML equivalent for a callout? update: I think this should be an aside with a class. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/aside

[x] I am questioning things like ink-p and ink-a, these are really common attributes and when parsing (e.g. SEO) have semantic meaning. The visible attribute is the main use case for these so that they react to changes in ink and the <ink-a> might have to be different? There could be something that is added that looks at the dom and toggles these on/off based on the state?

I really wanted to change to inherited components , but that is not supported by Safari. 😞 (and because of that lit-element doesn't support it either). Update: This could be done by wrapping the  in a custom component.
[ ] Explore the visible attribute on children of an article
[ ] Explore ink-preview

[ ] Should the setter on variable/component shortcuts return a promise? Right now it is sync, but that might not be the case if different evaluation middleware is used.
[ ] Add an example of a named component that is referenced.
[ ] Can you get access to the variable properties somehow? Sometimes nice for format so that you can define it once (right now this is set on bind if it is defined in the spec).

Outstanding Work

Adding in the other packages (CV, Chart, Article)
Packaging and publishing
Move the code I have left in /src into appropriate packages
Documentation update.

See #11

That looks awesome!!! Thank you so much @rowanc1 for working on it, I'm convinced ink-components has an amazing potential, and in fact it's already working so well that it's already my de-facto choice to make explorable components. I am in fact experimenting with bridging it with Brython (as I am more of a pythonist than a javascript coder :-) ) and so far it's working amazingly well!
So I'm not a great js coder, I'm kind of stuck in the era before node.js, so I'm going to give my perspective as a user, not as a developer as this is over the top of my head :-)
For the runtime state and exposition of ink as a js object that can be used in custom javascript code, that sounds awesome! Idem for creating new component, I didn't need to create my own components for now, but I can see the great potential here!
The change of bind to :change or :click or events is I think very good, as bind confused me a lot, even though I know how it works now, I still have a hard time getting my head around whether I should use :value or bind. With :change it's much clearer that the event happens when the component is used. Idem for :click.
About the removal of transform in the display component, yes I also found it was redundant, but I could understand it being retained to have a standardized API across components, but if not all components have this property (ie, it's not standard) then it can be safely removed I think.
About ink-article, I don't know what this does because it's not documented, but as a user I do not care much if it's using JS or CSS as long as it works in the browser without a server ;-) If this is useful to make scalable documents, then I would like it to stay, but that's up to you, you know better what is more maintainable and in the scope of the project (or if you have plans to provide a similar function but in another fashion, then no problem).
About ink-p and ink-a, yes I agree it would be better to drop them in favor of a wrapping approach, because as you stated it's better for SEO, but also because it's more generic, then ink can be used as an enhancer of any html tag or even other custom web components! eg something like
<ink-visible name="linkhider"></ink-visible>sometext<ink-visible name="linkhider"></ink-visible>
Would be generic and simple enough to use, although a bit redundant. If it could be set as an attribute (eg: sometext) it would be more concise but if this doesn't work on Safari as you say then the wrapping approach is fine I think.
About the rest, such as the store package, it's over my head so I can't say anything ;-)
However as an almost naive user, I fear that the transition to typescript will require compilation the library with node, so could you confirm whether ink.js will be embeddable in any HTML page as it was before with a simple


add optional s3_session_token variable and remove setting region to auto

Background
This fixes an issue when using graphql-hive with aws s3 as the artifact storage provider.
Description
Adding a way to pass the optional S3_SESSION_TOKEN variable. This should not change any existing behavior.
Also removing setting the region to 'auto'  while creating the AWS client. The region should be guessed correctly via:
https://github.com/kamilkisiela/graphql-hive/blob/d6c417837d9bcd80412d1b2283244d0dbf9e3649/packages/services/cdn-worker/src/aws.ts#L413
nit: added some indentation fixes to the Testing readme file.
By the way, this is a great project!

Thank you :)
Until we fix https://github.com/kamilkisiela/graphql-hive/issues/1436#issuecomment-1465111551, I need to merge your PRs to a local branch and run CI from there.


[WFLY-5709] Fix Messaging HA configuration

the shared-store-colocated configuration creates replication
live/backup configuration instead of shared-store ones.
live and backup configuration must always be created for colocated
configurations.
remove failback-delay attribute that is ignored in Artemis since
1.0.0.wildfly-008
add attribute initial-replication-sync-timeout to specify
deterministically how long to wait for the initial replication.

JIRA: https://issues.jboss.org/browse/WFLY-5709

Linux with security manager Build 3638 outcome was FAILURE using a merge of cef8df68d36c84bda0ebd2e118d2ab21d480a7a8
Summary: Tests passed: 781, ignored: 250; compilation error: Compiler (new) Build time: 00:03:59

Linux Build 8808 outcome was FAILURE using a merge of cef8df68d36c84bda0ebd2e118d2ab21d480a7a8
Summary: Tests passed: 781, ignored: 250; compilation error: Compiler (new) Build time: 00:04:17

Windows Build 3839 outcome was FAILURE using a merge of cef8df68d36c84bda0ebd2e118d2ab21d480a7a8
Summary: Tests passed: 781, ignored: 250; compilation error: Compiler (new) Build time: 00:06:17

Linux with security manager Build 3639 outcome was FAILURE using a merge of a39814c238905448c035259d18d6743464e15605
Summary: Tests passed: 781, ignored: 250; compilation error: Compiler Build time: 00:03:53

Linux Build 8809 outcome was FAILURE using a merge of a39814c238905448c035259d18d6743464e15605
Summary: Tests passed: 781, ignored: 250; compilation error: Compiler Build time: 00:04:01

Windows Build 3840 outcome was FAILURE using a merge of a39814c238905448c035259d18d6743464e15605
Summary: Tests passed: 781, ignored: 250; compilation error: Compiler Build time: 00:05:40

retest this please

Looks good if it gets into 10 Final; otherwise it's an API change, transformers, blah blah blah. I recommend you hassle QA for an ack. :)


Update message shows even if you already have the latest version

I made this issue and then immediately decided I was just gonna fix this now.
Fixed in #7


Export types and interfaces

This PR exports the packages types so that developers can use it in their projects
Related issue: https://github.com/psteinroe/supabase-cache-helpers/issues/350

Thanks @heloineto! Can you add a changeset for the two packages with "pnpm changeset"?

Thanks @heloineto! Can you add a changeset for the two packages with "pnpm changeset"?

Done.
I'm not sure if I did it correctly though, as I'm not familiar with the changesets package.

Thanks @heloineto! Can you add a changeset for the two packages with "pnpm changeset"?

Done.
I'm not sure if I did it correctly though, as I'm not familiar with the changesets package.

that's perfect, thanks!


Added CDN Link

In the readme file, there is no CDN script to use it in the code. I have provided the CDN script so that developers can directly  copy and paste it from the readme.

Could you please approve my pull request.


GUI async chat

@keybase/react-hackers
Here's a final PR for async chat, I've answered @chrisnojima's review comments from the WIP PR #4849.
Description:

When sending, we use the nonblock RPC and store the returned outboxID
When we get a NotifyChatChatActivityType.newMessage notification, we look to see if it has an outboxID -- if so, it was a pending messge that's now sent, so we call a new pendingMessageWasSent action, which finds the message that was sent, fills in its real messageID (which we just learned for the first time), and changes its messageState field to sent.
The render function now uses black_40 for pending messages, as per the Zeplin design.
The render function wasn't being called, because the react-virtualized List isn't changing dramatically -- it still has the same number of elements, we just updated some properties inside an element.  So now we manually call _invalidateChangedMessages() if we got an updated messageID for a message, which calls List.recomputeRowHeights(indexOfNewMessage) in response.  @chrisnojima and I struggled a whole bunch to get this working and it's still not very satisfying.

@chromakode Thanks for the review!  Applied changes for everything except the Message flow type.


operator mondoo-operator (1.8.0)

Signed-off-by: Christian Zunker<EMAIL_ADDRESS>

/merge possible

/merge possible


JS: Debouncing and Throttling in JavaScript

Description
Description

What is Debouncing ?
What is Throttling?
How Debouncing is different from Throttling ?
How can we use these techniques ?

Domain
JavaScript
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

@paramsiddharth Sir please check the issue that I created and please assign me this issue.

/assign


Support setting xhr responseType on the request

I want to set responseType on the xhr request, looking at the code I don't see an easy way to do this right now.
Similar to withCredentials, I'm thinking of adding a responseType which will set the responseType on the XHR request.

This shipped in 1.8 and I'm adding it to the docs now.


docs(validator): Validator.min and .max examples

https://docs.astro-reactive.dev/en/api/validator/validators/#validatorsmin
☝ the example code for Validators.min and Validators.max are better with type: number
const form = new FormGroup([
  {
    name: "price",
    label: "Price",
    type: "number",
    validators: [Validators.min(8)],
  },
]);

Ok so we just have to add type: "number" ?
I can work on this


Solved issue #46

Solved issue #46 completely in cpp and debugged some typos in links in readme file and updated it

Already merged and closed. Please verify from from previous pull requests.

Closing this PR.


Add Travis CI configuration

Coverage remained the same at 90.09% when pulling 84b973a4e4aff76760e42d66ffd3a605635342c9 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 86e4d62527f76978deff5a3e478bfa24b69bacfa on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 86e4d62527f76978deff5a3e478bfa24b69bacfa on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling e43a883459454219e7ce0a549ea2775e2f6f1cdf on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 6897fb5fec299da8194f5370ed3277a8bb8c23b8 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 6897fb5fec299da8194f5370ed3277a8bb8c23b8 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling ede5bc134cba95be67b78de28848732c1778edfe on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling ede5bc134cba95be67b78de28848732c1778edfe on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling dda3e58fef2785b73d7d2f7b5dfeabec7fff5c90 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 94dd2c642bca79cb405b39798d4666eba9e12b82 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 94dd2c642bca79cb405b39798d4666eba9e12b82 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 4c89147d17b15d7667feea38223e8dc664fe55ce on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 4c89147d17b15d7667feea38223e8dc664fe55ce on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.

Coverage remained the same at 90.09% when pulling 9cb6df948a1f1f48693f92c773ed603227315004 on travisci into 6551e7464ab595502a93b8b2d95307002f4e69e9 on master.


MAINT: interpolate: refactor PchipInterpolator to be a *Poly subclass

addresses gh-3742

OK, here's an alternative: gh-4486

OK, my preference is back here: gh-4486 is closed because of the overhead of axis handling in PPoly. This PR can possibly be made a bit more general by injecting the axis handing in between PPoly and subclasses so that Akima1DInterpolator gets a proper axis handling as well. While this is doable, I'd wait until there is a use case.
I'm also provisionally adding a 0.16 milestone.

Closing in favor of gh-4784


Change signature of Prism.highlight{Element,All,AllUnder}

Motivation
Similar to #3416, it would be nice to have all optional arguments of Prism.highlight{Element,All,AllUnder} in an options dictionary.
Description
So the new signature should be:
interface HighlightAllOptions {
  async?: boolean;
  callback?: (element: Element) => void;
}
function highlightAll(options?: HighlightAllOptions) { ... }
function highlightAllUnder(container: Element, options?: HighlightAllOptions) { ... }

interface HighlightElementOptions {
  async?: boolean;
  callback?: (element: Element) => void;
}
function highlightElement(element: T, options?: HighlightElementOptions) { ... }

We could also remove highlightAllUnder and make container?: Element an option in HighlightAllOptions. Example usage:
Prism.highlightAll({ container: document.querySelector("#page") })
// or mabye
Prism.highlightAll({ under: document.querySelector("#page") })

Thoughts? @LeaVerou @Golmote @mAAdhaTTah @JaKXz

Yes, agreed with removing highlightAllUnder() and making it an option in highlightAll(). Wrt naming, I think container is more common. Maybe also root?

I think root is probably the most ubiquitous / broadly accepted :)

Agreed. root sounds good.

Implemented in v2.


Add Typings

I added a TypeScript declaration file.
In case you're unfamiliar with this format, I'll explain it a little:

declare module 'js-levenshtein': this declares what module the types will be for (this one, of course)
export: this is how things are exported in TS and ESM, equivalent to assigning to exports in CJS (which is the traditional module resolution in NodeJS)
export default: this means that it's specifically the main export, equivalent to doing module.exports = something in CJS
function(a: string, b: string): number;: this represents the actual function exported by the module. It doesn't have a name, since it's the default export. It takes two strings and returns a number.

Let me know if I missed anything or got the types wrong.
Fixes #7

@tech6hutch Thanks for this!
I have seen that some add the typings-file to a types field in package.json, do you have an opinion about this? https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
Could you also squash the commits please?


select_prev_item() and select_next_item() loosing focus

I usually use C-j and C-k to move between items in a completion. That suddenly stopped working..I muss say I haven't been using nvim in weeks. Maybe something changed in the setup. I just don't know what.
Can somebody please look at my config?
Thanks

The following is what happens when I hit C-j to go to the next item in the snippet
https://user-images.githubusercontent.com/148098/208467516-35859925-ee41-458c-86f1-a1914950644b.mov

And idea how did you fix?


installation: Flask-Login<0.4.0 pin

Signed-off-by: Krzysztof Nowak<EMAIL_ADDRESS>

@krzysztof let's just fix Invenio-Accounts and bump its version. It will be painful to remove this Flask-Login pins from everywhere.

@krzysztof Please follow https://github.com/inveniosoftware/invenio-accounts/pull/169 and bump Invenio-Accounts v1.0.0a16 instead. Thanks

@jirikuncar Done :shipit: ?

LGTM


Expected bytes, got str

p = pyreBloom.pyreBloom('wufengBloomFilter', 100000, 0.01).decode('utf-8')
File "pyreBloom.pyx", line 47, in pyreBloom.pyreBloom.cinit (pyreBloom/pyreBloom.c:977)
TypeError: Expected bytes, got str

What version of Python are you using? I don't know that we've gotten Python 3 support going yet :-/

Python 3.7.0  also see it, the error message
p = pyreBloom.pyreBloom(b'BloomFilter', 100000, 0.01)
File "pyreBloom.pyx", line 49, in pyreBloom.pyreBloom.cinit (pyreBloom/pyreBloom.c:1004)
TypeError: expected bytes, str found

ye, I use python3.7.0 also see it when I execute
p.contains('h') or p.contains(b'h'), both raise TypeError: expected bytes, str found

I used python3.7.3 and got the same error
p = pyreBloom.pyreBloom('user_data',120000,0.001)

File "pyreBloom.pyx", line 47, in pyreBloom.pyreBloom.cinit (pyreBloom/pyreBloom.c:977)
TypeError: Expected bytes, got str

I use python2.7. It should be unsupported. I still use the redis 4.0+ plugin.

I use python3.8.6,got the same error


Support Management API and flow statistics

Enable manager API by specifying and IP address:
shadowsocks-server --manager-address <IP_ADDRESS>:6001

Protocol:
https://github.com/shadowsocks/shadowsocks/wiki/Manage-Multiple-Users#protocol

will this feature be merge to master branch?

It's very useful, could you merge to master branch?

It's cool!

LGTM
thx for contribute


Create an R package to handle CFF

Summary
Proposal for creating an R package that inputs from/outputs to CITATION.cff (tentative name: RCFF)
Motivation
The metadata for R packages are contained within a DESCRIPTION file, and I would like to create an R package to handle the translation between that format and the CFF. I couldn't find anything about this on this Issues page (hopefully it's the right place to look), so was wondering if there is anyone already working on it and what the CFF authors think about the idea. I, for one, think this could be a great asset in helping CFF establish itself as the de facto standard for research software citation.
R is very popular in academia, and it does have a base function called citation() that reads from a package metadata and prints citations in APA-like and Bibtex formats, as per the following example:
> citation("stats")

The ‘stats’ package is part of R.  To cite R in publications use:

  R Core Team (2020). R: A language and environment for statistical
  computing. R Foundation for Statistical Computing, Vienna, Austria.
  URL https://www.R-project.org/.

A BibTeX entry for LaTeX users is

  @Manual{,
    title = {R: A Language and Environment for Statistical Computing},
    author = {{R Core Team}},
    organization = {R Foundation for Statistical Computing},
    address = {Vienna, Austria},
    year = {2020},
    url = {https://www.R-project.org/},
  }

We have invested a lot of time and effort in creating R, please cite it
when using it for data analysis. See also ‘citation("pkgname")’ for
citing R packages.

This covers the two most popular cases in academia, but I think it's missing an output to a more unversal format such as the CFF. Even within the R world, a CITATION.cff would be useful for non-packaged software such as scripts and Shiny apps.
An alternative to creating a package is to try to convince upstream R developers to extend the citation() function, but even if they agree to that, it wouldn't cover the "import from CFF" feature (or any other we might decide to implement along the process).
Repository location
Given how the PyCFF repository is part of the citation-file-format organization, I was wondering if an RCFF package should also be hosted there (an alternative would be for me to host it on my organization's page.

Hi @wleoncio, thanks for the proposal. I don't know that anyone is working on this yet. I think it would be a fantastic project! I also don't see a reason why this shouldn't be hosted in the CFF org.
I'm currently on holidays until mid July. Let me get back to you more comprehensively after then? If you want to start this elsewhere already, we can always transfer the repo later.
Thanks!

Thank you for the greenlight, @sdruskat! No rush on my part, I'm out on a short vacation absence myself next week, so we can pick this up after you're back. If I get too antsy, I'll start a local repo (or upload and transfer later, as you wrote).
Cheers,
Waldir

Hi @wleoncio, are you still working on this? If so, I'm happy to help where I can.

Hi @mariabnd, thank you for showing interest in the project. I got a bit of groundwork done while I was waiting for @sdruskat's follow up. Then other projects got in the way, so an extra set of hands and brains is very welcome.
If we get a greenlight from the CFF team (particularly regarding where on GitHub the project will be hosted), I'll push my local repo so you can take a look at it.
Happy holidays to all!

Hi @wleoncio, really sorry for the delay in replying. Don't have much bandwidth at the moment.
To get this underway, would you be happy to host under your GitHub org, and we'll link to it from here, as a first step?
I'd like to bring it into this org, but need more time to figure out how to best do this.
Thanks!

To get this underway, would you be happy to host under your GitHub org, and we'll link to it from here, as a first step?

Sure thing, @sdruskat! I'll set things up (repo, link here, add @mariabnd as external collaborator to my org) ASAP, likely before the end of the week.

To get things rolling, I've created https://github.com/ocbe-uio/RCFF and pushed most of my commits there (the only thing I didn't push is a branch where I started to implement some S4 classes, but that will probably go stale and be dropped due to it making things more complicated than they need to be).
At this point I don't think there are enough features to even consider this on "alpha" stage, but the package is technically installable and usable. As proof-of-concept, there's a function in there called r2cff() to (half-assedly) convert a package's title and version number from the "R DESCRPTION format" to CFF. I've also created a couple of issues to remind myself to polish all the hastly-coded things I wrote just to make this minimally presentable.
@mariabnd, how is your current availability to contribute? Times are tough for everybody. I, for one, am on partial parental leave, so my working hours are limited and I must prioritize other software over this, but I am really glad this is out so it stares at my face more prominently.

@wleoncio things are a bit hectic here too, but I hope to take a look over the weekend

I was looking for an R package that could deal with CFF files, and found this thread, among other results. You might be interested in the {citation} package that is in CRAN https://cran.r-project.org/web/packages/citation/ (https://github.com/pik-piam/citation), seems to have support to generate CFF files from the DESCRIPTION file of a package.
Also, the utils::citation() function parses the DESCRIPTION file into something that can be easily manipulated, and converted into other format.

@wleoncio Did you see this from a few days ago? https://twitter.com/natfriedman/status/1420122675813441540

@mariabnd, that was my motivation to check for a package to generate CFF files :-)

I'll add the help wanted label to this issue. Let me know if you'd rather have it removed again, just thought that it may help to attract more contributions.

@jmcastagnetto, @mariabnd and @sdruskat, thank you for the messages. I've just came back from vacation (literally 20 minuts ago), but I'll take a carefull look at these references ASAP to see what's the most sensible course of action (merge RCPP, keep it as a separate package or drop it altogether).

See an example, this have been generated automatically by cffr:

cff-version: 1.2.0
message: 'To cite package "cffr" in publications use:'
type: software
license: GPL-3.0-or-later
title: 'cffr: Generate Citation File Format (''cff'') Metadata for R Packages'
version: <IP_ADDRESS>00
abstract: The Citation File Format (version 1.2.0) <doi:10.5281/zenodo.5171937> is
  a human and machine readable file format which provides citation metadata for software.
  This package provides core utilities to generate and validate this metadata.
authors:
- family-names: Hernangómez
  given-names: Diego
  email<EMAIL_ADDRESS>  orcid: https://orcid.org/0000-0001-8457-4658
preferred-citation:
  title: 'cffr: Generate Citation File Format (''cff'') Metadata for R Packages'
  authors:
  - family-names: Hernangómez
    given-names: Diego
  year: '2021'
  url: https://dieghernan.github.io/cffr/
  type: manual
repository-code: https://github.com/dieghernan/cffr
url: https://dieghernan.github.io/cffr/
contact:
- family-names: Hernangómez
  given-names: Diego
  email<EMAIL_ADDRESS>  orcid: https://orcid.org/0000-0001-8457-4658
keywords:
- attribution
- citation
- credit
- citation-files
- cff
- metadata

So between cffr, citation and handlr (I've merged my RCFF functions into the citation package), I feel like we have more than enough R packages to handle CFF, which gives us enough cause to close this issue IMO. Further discussions on the topic are of course welcome, though.
Let's keep this conversation easy to find (maybe admins can pin the issue for a while?), hopefully more people find this thread before starting their own work and further fragmenting our efforts.

Thanks @wleoncio , no need to say but if you have any suggestions or improvements for {cffr] please do let me know,
Regards

Thanks all!

So between cffr, citation and handlr (I've merged my RCFF functions into the citation package), I feel like we have more than enough R packages to handle CFF, which gives us enough cause to close this issue IMO. Further discussions on the topic are of course welcome, though.

I agree. I'll close once I've added handlr and cffr to the tools table in README.

Let's keep this conversation easy to find (maybe admins can pin the issue for a while?), hopefully more people find this thread before starting their own work and further fragmenting our efforts.

Good point. I would think that people check the tools table before starting to work on their own packages, so does it suffice to list available packages there?

I would think that people check the tools table before starting to work on their own packages, so does it suffice to list available packages there?

Sounds good enough, nothing else comes to mind, right now.

Hi, FYI the {cffr} package now is part of rOpenSci!

https://github.com/ropensci/cffr
https://docs.ropensci.org/cffr/

I am planning an upcoming release on CRAN, will keep you posted
See https://github.com/ropensci/software-review/issues/463#issuecomment-955576106


Make 0 closed issues not show 50% closed on activty page

Fixes #3656. Also adds a light grey bar when there are both 0 merged
prs/closed issues and 0 open prs/issues.
Before

After

Codecov Report

Merging #3802 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3802   +/-   ##
=======================================
  Coverage   23.02%   23.02%
=======================================
  Files         126      126
  Lines       24894    24894
=======================================
  Hits         5731     5731
  Misses      18287    18287
  Partials      876      876

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 bec69f7...866441f. Read the comment docs.


Clicking on the empty space of tree triggers treeClickAction

If I switch to tab I previously opened and click on the empty space, it switches back to the tab of the item selected in the tree, whose cursor position is lost (it jumps back to the class definition).

@coin3x fixed, thanks for report :+1:


server: remove disable learner option

What problem does this PR solve?
We don't need DisableLearner anymore.
What is changed and how it works?
This PR removes this unused option.
Check List
Tests

Unit test

Related changes

Need to update the documentation

I don't think it's a good idea to remove a public option, because it breaks the compatibility.
If this option won't be used anymore, marking it as deprecated is a better way.
If this option won't work anymore, leaving it there and give a warning or error in log if somebody changed it is more elegant.

It looks to be a good idea to keep the option and do nothing but gives a warning :smile:

The main purpose I did this is to reduce the output item of config show. Any better idea? @disksing @Luffbee

config show output is too noisy. I think it is another problem that need to get fixed, maybe we can handle it separately.

Codecov Report

Merging #1669 into master will increase coverage by 0.12%.
The diff coverage is 79.31%.

@@            Coverage Diff             @@
##           master    #1669      +/-   ##
==========================================
+ Coverage    76.6%   76.72%   +0.12%
==========================================
  Files         158      158
  Lines       15573    15559      -14
==========================================
+ Hits        11929    11937       +8
+ Misses       2623     2611      -12
+ Partials     1021     1011      -10

Impacted Files
Coverage Δ

server/coordinator.go
85.22% <ø> (ø)
:arrow_up:

pkg/mock/mockoption/mockoption.go
92.3% <ø> (-0.2%)
:arrow_down:

server/cluster.go
83.01% <ø> (+0.16%)
:arrow_up:

server/config/option.go
91.79% <ø> (-0.07%)
:arrow_down:

server/version.go
72.72% <ø> (ø)
:arrow_up:

server/server.go
81.9% <0%> (-0.32%)
:arrow_down:

server/schedule/operator/operator.go
86.3% <100%> (+0.3%)
:arrow_up:

server/handler.go
50.39% <100%> (+0.79%)
:arrow_up:

server/statistics/store_collection.go
88% <100%> (+1.28%)
:arrow_up:

server/checker/replica_checker.go
80% <100%> (ø)
:arrow_up:

... and 8 more

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 14b91e8...8300457. Read the comment docs.

@disksing PTAL.

@rleungx LGTM. Please resolve conflict.


No module named yum

Hi,
Just tried to checkout the project and run it but got this error:
root@ec8bb6959862:~# git clone https://github.com/crohr/rpm-s3 --recurse-submodules
Cloning into 'rpm-s3'...
remote: Counting objects: 176, done.
remote: Total 176 (delta 0), reused 0 (delta 0), pack-reused 176
Receiving objects: 100% (176/176), 137.46 KiB | 0 bytes/s, done.
Resolving deltas: 100% (52/52), done.
Checking connectivity... done.
Submodule 'vendor/pexpect' (https://github.com/pexpect/pexpect.git) registered for path 'vendor/pexpect'
Cloning into 'vendor/pexpect'...
remote: Counting objects: 6188, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 6188 (delta 0), reused 0 (delta 0), pack-reused 6183
Receiving objects: 100% (6188/6188), 8.26 MiB | 1.74 MiB/s, done.
Resolving deltas: 100% (3849/3849), done.
Checking connectivity... done.
Submodule path 'vendor/pexpect': checked out 'fcf4ad9b744f845b9c88f63c735ff686f24381e2'
root@ec8bb6959862:~# rpm-s3/bin/rpm-s3
Traceback (most recent call last):
  File "rpm-s3/bin/rpm-s3", line 13, in <module>
    import yum
ImportError: No module named yum

root@ec8bb6959862:~# python --version
Python 2.7.9

This has more requirements than just python and the S3 credentials.
The following solves my issue:
apt-get install -y rpm yum createrepo


docs(hub-nodejs): add docs for utils.md

Motivation
Fixes #735. See: https://github.com/vinliao/hubble/blob/nodejs-docs/packages/hub-nodejs/docs/Utils.md
Change Summary
Add examples and the tables for each function in utils.md
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[x] PR title adheres to the conventional commits standard
[ ] PR has a changeset
[x] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
[x] PR does not require changes to the protocol

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers

Should be good now, @varunsrin.


Ignore vulnerability support

You can now specify which vulnerabilities should be ignored.
Running the following wercker.yml:
build:
    steps:
        - shrinkwrap-security-audit:
            ignore: >
                qs=https://nodesecurity.io/advisories/28,
                qs=https://nodesecurity.io/advisories/29

Can now result in the following output:
Ingoring:
 - module: qs
   - https://nodesecurity.io/advisories/28
   - https://nodesecurity.io/advisories/29

2 vulnerabilities/issues detected:

Title:    Denial-of-Service Extended Event Loop Blocking (ingored)
Module:   qs
version:  0.6.6
Patched:  >= 1.x
Path:     request > qs
Advisory: https://nodesecurity.io/advisories/28

Title:    Denial-of-Service Memory Exhaustion (ingored)
Module:   qs
version:  0.6.6
Patched:  >= 1.x
Path:     request > qs
Advisory: https://nodesecurity.io/advisories/29

Ignored all found vulnerabilities

lgtm :+1:


Typeahead and slow queries

As expected, typeahead mode sends the query action for each letter typed (even the empty string). With a lot of data, the first requests sent to the server (with less letters to filter the results) will take a lot longer than the next ones. Now if a request is resolved (deferred.resolve) after a value has been selected by the user, the value is unselected and disappears from the field.
It feels like, when multiple query actions are sent, only the data coming from the last one should be processed by ember-select-2. I'm not sure if it is the concern of the library, or of the user implementing  the query action. What do you think ?

You are correct, the component should only process the last promise issued. Additionally, previous promises could be resolved (to null maybe?) so that in theory, the developer could check if the value is still needed by the component.
It might take me some time to look into the exact behaviour, but the fix should be quite easy from there on. Thanks for letting me know!

In a similar vein, it'd be nice to optionally be able to stop the component from firing queries while the user is still typing, as it's just wasted queries on the backend
I have something like this implemented in a simple search box component to achieve that:
export default Ember.Component.extend({
  delay: 500
  q: "" // the bound search property
  term: "" // the internal search term
  search: (function() {
    var min, term, timer;
    timer = null;
    term = this.get('term');
    min = this.get('searchMinimum');
    clearTimeout(timer);
    if (term.length >= min || term.length === 0) {
      return timer = setTimeout((function(_this) {
        return function() {
          return _this.set('q', term);
        };
      })(this), this.get('delay'));
    }
  }).observes('term')
});


updated base.py. (winfunc added in logfbank)

Previously I was using fbank for feature extraction. Then when I found that when I used log on the Fbank the accuracy of the model was better. But I was using hamming frame on windows for feature extraction, because of this I was taking log after implementing fbank. So it would be better if we have a choice to apply window function while using logfbank function as well.

Thanks mr yamraj


How to static link app.

Hi I'm a Nim newbie, Please tell me how to static link app use csfml.

This is not specific to this library.
You need to build CSFML for static linking, then tell Nim to statically link. I can't help you with either of those steps.


Remove setting guild commands from attributes

Passing guild id for guild command in attribute renders it useless, because it requires saving guild id in code. The attribute should be removed and changed to loading guild setting from outside the code (maybe from database?)

Additional idea: Change this attribute to just indicate the command is a guild command (cannot be used in DMs). It such command should be registered not as global, but for each guild the bot has access to


Some work on DOMParser; needs help

@Sebmaster I was hoping you could take a look at this. The problem comes with the "add strict parsing errors when parsing XML documents" commit. Flipping that causes a bunch of tests to start failing for weird reasons having to do with tree construction in htmltodom.js. The last commit modifies the web platform tests manifest so that it only runs the tests which have shown failures.
What's weird is that the failures are due to stuff that should have nothing to do with strict vs. non-strict XML parsing. It's something about how nodes are emitted and what's on the stack at that time. I figure since you plugged in sax in the first place maybe you had some ideas.

the fact that HTML entities were unknown I think? Pretty sure it errors out on those by default.

It's actually correct to error out on HTML entities; that's what browsers do for strict XHTML.
However, a bunch of level1 tests failed due to throwing on unknown entities, which some of the level1 tests use. I fixed that with https://github.com/tmpvar/jsdom/pull/1535/commits/cb4c8587734797efbbdb5c92beee7fb99f0f7524 and now everything is mostly passing.
I'd definitely appreciate if you had the time to look in to the node stack stuff that's causing failures.


Automate tests for Setting page

Description

Automate tests for Setting page:

Change theme
Show hidden Namespaces
Delete without confirmation

Duplicated with: https://github.com/kyma-project/busola/issues/557


Add SlipStream instance name in usage email

Users with account on multiple instances can not easily know in the daily usage email the source (SlipStream instance).

Proposed solution:


[V2V] Add a helper method to check if virtv2v is running

In https://github.com/ManageIQ/manageiq/pull/18853, @agrare suggested to create a helper method to check whether virt-v2v is running. This makes it more comprehensive.

@miq-bot add-label transformation, enhancement
@miq-bot add-reviewer @agrare


Investigate question version update data integrity

We've had two cases so far where versions_questions hasn't been updated properly.
#1797 and #2040  In both cases other questions used by a program had their versions advanced but not some in both cases.
This causes blocking failures in CiviForm and would seem to indicate a data integrity issue when updating questions related to a program.  It may be that a transaction is not being used as intended or that one needs to.
Note: This has become a general roundup of issues around configuration being updated improperly.
User Errors to investigate

[ ] #1797
[x] #2040  (#2249)

Identified Issues

[x] Editing the same active program in different tabs doesn't work. #2247
[ ] Editing the same active question in different tabs doesn't work. #2497
[x] Deleting an enumerator draft doesn't update other Question drafts that reference it. #2249
[x] Question Bank doesn't update with new drafts.  Tab 1 Edit program, Tab 2 edit a question in another tab, Tab 1 add question to program, publish, site break because Tab 1 was using the Active not the Draft question. #2375
[ ] Question discardDraft has 2 phases (remove question draft, and update dependencies) and error between these will leave the data corrupted.  The first needs to be committed for the second part to "just work" as it relies on the existing state of the DB.

Program Editing specific issues

[x] #2402

#2179 may also be related

I diagnosed #2179 and left details there. the root cause is when an out of date view of a program is used to make a new draft when one had otherwise already been made since the page was loaded.  Unsure the behavior in other inconsistencies like if a draft is already made but has been updated in a different tab etc.
Seemingly questions would have the same problem, but their only interdependency is limited to enumerators.

sounds good to me.


Issue for:"Turn an Image into a Link"

Ok, so this is my code:
<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

Everything is correct. I did it how it tells me to do, but everytime i run the tests there is this problem:
"Your a element should be a dead link with a href attribute set to #." Can you fix it please?

@Sashokmd Thank you for reporting this issue. Your code does not satisfy the requirements of the challenge. Please take a look at the instructions again.

Place the existing image element within an anchor element.

This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on Free Code Camp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!


Failover on master when there aren't slaves

I think can be useful (in a sentinel environment where role: 'slave') to have an option to failover on master when there aren't slaves alive.

I think this could be done subscribing to sdown|odown channel on sentinel instance and mapping the state of the slaves as they and fallback to using the master. Also, but resource wasteful, by long polling SENTINEL REPLICAS <master name>

The reverse (failover to a slave when using master role) would be useful too. My initial idea about this is in https://github.com/luin/ioredis/issues/840.
I think a unavailable master can be detected via error MASTERDOWN, not sure if a similar error code exist for the reverse situation. Main challenge about this is probably the recovery.

Yeah new roles like master-slave and slave-master sgtm.
Don't feel we need to subscribe to any events as ioredis will reconnect when the connected server is down so the only thing we need to do is to add the fallback logic in https://github.com/luin/ioredis/blob/main/lib/connectors/SentinelConnector/index.ts#L328
The only case it won't work is when the master is down but the connection to the server is still live. But it should be a separate job that has already been addressed by https://github.com/luin/ioredis/blob/main/lib/connectors/SentinelConnector/FailoverDetector.ts.


Code from core

This PR adds the code of the base module, which used to be a part of core-java repository.
The version of Spine in this PR is one number ahead from that in core-java (the related PR there is: https://github.com/SpineEventEngine/core-java/pull/532).
It done so to allow dependency on spine-base from spine-core with a following PR in core-java.

@armiol, pleases pick it up from this point. The build of model-compiler does not pass because it depends on spineVersion which is not yet published.


Extension uninstall "x" is not centered

VSCode Version: 0.10.12-alpha (latest)
OS Version: Windows 10

Steps to Reproduce:

Open installed extensions

b1572f504ea9001a28928aae6eb968259b777165 introduced this

@joaomoreno checkout my fix, I am just adding maring-right to the x icon to make it nicely aligned - seems to work well for me.


Add missing comma

There is a syntax error in networking.html page (missing comma after {nodelay, true}):
[
  {rabbit, [
  {tcp_listen_options, [
                        {backlog,   128},
                        {nodelay,   true}
                        {sndbuf,    196608},
                        {recbuf,    196608}
                       ]}
  ]}
].

Looks good, @santif. Could you please submit this to the live branch? That's the branch that corresponds to the current release of RabbitMQ.

@bdshroyer we can merge this and then cherry-pick, too. WDYT?


fix(examples): update react app code

Update react code as outlined here to remove compatibility mode warnings.
https://react.dev/blog/2022/03/08/react-18-upgrade-guide#updates-to-client-rendering-apis
Update react types for stricter checking and fixes.
Fixes react running in compatibility mode.
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

This is said to have a perf benefit as well but I can't tell.  Its always been very performant.

Did you test the examples?
I changed this myself too (with many other changes) and I observed some examples don't work properly afterwards:
function main() {
    const oldWay = !true;
    console.log("oldWay", oldWay);
    if (oldWay) {
        // render out the app
        ReactDOM.render(
            jsx(MainLayout, null),
            document.getElementById('app')
        );
    } else {
        // render out the app
        const container = document.getElementById('app');
        const root = createRoot(container);
        root.render(jsx(MainLayout, null));
    }
}
window.onload = () => {
    // Just a little timeout to give browser some time to "breathe"
    setTimeout(main, 50);
};

For example a slider doesn't fire any longer or this canvas is just half-visible:

Based on this minified source, it doesn't seem to be updated yet: https://playcanvas.github.io/index.js (I only find createRoot once)

Yes.  All directional controls work.
I would not rely on what is published to github pages in the link provided.  That is not the branch these commits have been made to.  I do not know which version is being to the "github pages".
Your code does not match what was replaced.  What is your 'jsx' referring to ?  I don't know what else you say you changed.
In the examples directory, ensure you have run npm install then npm build.


Cant get to run on Linux

I seem to be running into a mismatch between the latest spektrum source, and the rtlspektrum 'Processing' library, which I fetched from pavels repository.
There's a mis-match between your code, and some of the API calls, like your code
assumes that an extra parameter can be passed in "setFrequencyRange", but with pavels
latest rtlspektrum library, that fails, due to an argument mis-match.

Please use the included jar from the binary distro here. Does this work ?
Also, I just updated the .java here .

On 11/22/2018 10:44 AM, George Ioannou wrote:

Please use the included jar from the binary distro here
https://www.dropbox.com/sh/c7vjbvm0mhi4xqu/AAAnuL9OkGZnQfcmRo2nRf8Ia?dl=0.
Does this work ?
Also, I just updated the .java here
https://github.com/SV8ARJ/processing-rtlspektum-lib.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SV8ARJ/spektrum/issues/7#issuecomment-441067328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx5L1BBHrqI35YCHIwmiwadwJoI-H1Eks5uxsZEgaJpZM4YsaWW.

Actually, in the mean-time, I've gotten it to build in my own instance
of Processing, and have gotten "crop" to work properly as well.
I spent last night and added a crude ability to data-log as well.
Once it's "lovely", I'll put together a PR.


Prefix ids plugin don't add prefix if prefix is false

i use it like this:
plugins: [
          {convertPathData: false},
          {prefixIds: {
            prefix: node => {
              const elementName = node && node.elem
              if(!elementName || elementName === 'svg' || elementName === 'use'){
                return false
              }

              return 'some-prefix'
            }
          }}
        ]

and i expect no prefix when i return prefix as false.
it can also be used as
plugins: [
          {convertPathData: false},
          {prefixIds: {prefix: false}}
        ]

@vzaidman: This is very similar to this issue (please also check out the code sample in that issue):
https://github.com/svg/svgo/issues/913#issuecomment-369423275

reabsed my fix on develop

Why don't i see it in thew latest version?
can you please publish it?

SVGO v1.1.0 with the fix has been just released.


The curl install throws an error

Describe the bug
I tried to use the curl install but it just throws an error:
$ curl -L https://install.quickwit.io | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   134  100   134    0     0    375      0 --:--:-- --:--:-- --:--:--   374
sh: 199: Syntax error: "(" unexpected (expecting "fi")
 87 15202   87 13253    0     0  23965      0 --:--:-- --:--:-- --:--:-- 23965
curl: (23) Failure writing output to destination

Steps to reproduce (if applicable)
Steps to reproduce the behavior:

Run the curl command

Expected behavior
App would get installed
System configuration:
Release version (or git SHA-1), OS, ...
Pop!_OS 21.10
Additional context
Add any other context about the problem here.

@larksoftware we will look into this but it seems your bash environment does not support some constructs used in the install script.
You can try curl -L https://install.quickwit.io | bash in the meantime.
We will investigate the offending bash syntax.

I don't know if it makes a difference but I run zsh.  That said I would think the shebang would send it to the proper shell.


Incorrect table mapping when using EntityGenerator with entitySchema

Describe the bug
When using the EntityGenerator helper to generate the entities from existing database schema, the generated entity is mapped to wrong or non-existing table name especially when the table name has underscore (_).
This may be happening for other special characters as well.
Stack trace
...

To Reproduce
Steps to reproduce the behavior:

Create a table Address_lines

CREATE TABLE `Address_lines` (
`nodeId` char(25) CHARACTER SET utf8 NOT NULL,
`position` int(4) NOT NULL,
`value` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
PRIMARY KEY (`nodeId`,`position`),
KEY `value` (`value`(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

setup the entity generation

const orm = await init({
  // ... other config
  entitiesTs: [`./src/entities`],
  entityGenerator: {
    entitySchema: true,
    identifiedReferences: true,
  },
  type: 'mysql',
})

await orm.getEntityGenerator().generate({
  baseDir: path.join(__dirname, `./src/entities`),
  save: true,
})

await orm.close(true)

the following is the generated after the execusting the generation

  export class AddressLines {
    nodeId!: string
    position!: number
    value!: unknown
  }

export const AddressLinesSchema = new EntitySchema({
  class: AddressLines,
  tableName: 'AddressLines', // This is wrong and should be inferred as `Address_lines`
  properties: {
    nodeId: {
      primary: true,
      fieldName: 'nodeId',
      columnType: 'char(25)',
      length: 25
    },
    position: { primary: true, type: 'number' },
    value: {
      type: 'unknown',
      columnType: 'mediumtext',
      length: 16777215,
      index: 'value',
    },
  },
})

Expected behavior
Entity class and schema files generated with corresponding table name.
tableName: 'Address_lines',

Additional context
A possible issue could be in this line https://github.com/mikro-orm/mikro-orm/blob/master/packages/entity-generator/src/EntitySchemaSourceFile.ts#L45
Versions

Dependency
Version

node
16.x

typescript
4.9.4

mikro-orm
5.6.3

your-driver
mysql

Hi @B4nan,
Thanks for following up on the PR.
Any plan on getting this released this week ?


delete xrefmap.yml which is causing build failure

Docs Build status updates of commit 87627d4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 136: [Error] Restore nuget package W:\yv11-s\.optemp\dependentPackages\Microsoft.OpenPublishing.CommonPlugins\packages.config in folder:W:\yv11-s\.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in https://SiteHelp and include the build report and the following error message for our team to troubleshoot: Errors in packages.config projects     Unable to find version '1.0.222' of package 'Microsoft.OpenPublishing.CommonPlugins'.       C:\Users\ContainerAdministrator\.nuget\packages\: Package 'Microsoft.OpenPublishing.CommonPlugins.1.0.222' is not found on source 'C:\Users\ContainerAdministrator\.nuget\packages\'.       https://docfx.pkgs.visualstudio.com/docfx/_packaging/docs-build-v2-prod/nuget/v2: Package 'Microsoft.OpenPublishing.CommonPlugins.1.0.222' is not found on source 'https://docfx.pkgs.visualstudio.com/docfx/_packaging/docs-build-v2-prod/nuget/v2'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

I don't have permission to this repo, but can anyone help force rebuild master branch of this repo and then try re-opening this PR? It should build pass.


Create codeql.yml

Thanks for the PR, but CodeQL is already run: https://github.com/anchore/syft/blob/main/.github/workflows/codeql-analysis.yml


Adding checker workflow does not update, needs refresh

The descriptor type should be carried over from the workflow itself.

Seems correct
DockstoreAPI - 1.5.0-beta.0
DockstoreUI - 2.2.0-alpha.8

That said, adding a checker workflow doesn't seem to update immediately which can be confusing.
I had to refresh for the Checker Workflow to show the correct button
Re-naming ticket

Note: The current entry is no longer selected in the sidebar after adding checker workflow

Well, one step forward, one step back.
The button seems to update. But it doesn't actually seem to work until a refresh.

Seems functional on
DockstoreAPI - 1.5.0-beta.3
DockstoreUI - 2.2.0-beta.2


Add raise_typeof helper

I want to make it easy for beginners to figure out the types of things. This will be helpful when using assigns in Pages, or really for anytime you need a type
macro show_typeof(var)
  raise "Type of `{{var.id}}` is: #{typeof({{var}})}"
end

number = 1
show_typeof(number)

Only downside is this does it at runtime. Maybe it's better to teach people how to figure out types in a different way :S


Add warning when className prop is not used

https://github.com/styled-components/styled-components/issues/349
I tried several options like using getters/Proxy but it doesn't work because of copying props inside React (https://github.com/facebook/react/blob/master/packages/react/src/ReactElement.js#L193)
Proposed code warns in such cases:
const Test = () =>
;
const StyledTest = styled(Test)`
  background: white;
`;


tweak build

I saw this on Android Weekly — nice!
Thought I'd tweak the build a little, hope the PR's ok.

good catch 👍


overhead of recompile

I wonder if I can see some info about overhead of ghidra
I mean is there any difference of the overhead between the original binary and the binary decompiled by ghidra and exported by ghidra

If you're talking about the binary export functionality (which due to #19 only works after importing as "Raw Binary") - then the output should be the exactly same binary.
As for compiling the decompiled output (which will most likely not work) - that can differ vastly from the original source code of the application and I have not seen anyone (nor do I think it's possible) to recompile full executables.

I don't understand what  the raw binary is .is there any difference between raw binary and ELF?
why it will most likely not work as for compiling the decompiled output?
I want to test the overhead of ghidra so that's why I recompile the output decompiled by ghidra to get the binary. if the overhead of the binary obtained from ghidra is higher than the original binary, it doesn't work for me

It sounds like you aren't interested in exporting the bytes of the binary that was imported and having it run.  Instead, it seems like you are asking about recompiling the decompiler's code back into an executable and running it.  For anything but the simplest of binaries, the effort to do this correctly will most likely not be worth the effort, especially if your motivation is to optimize the binary.  That is not a goal of Ghidra.

Indeed, ever since van Emmerik invented the proof of SSA over 15 years ago this question comes up every now and then.
The thing is for a small binary of 10k WITH debuginfo it might be possible to recompile output from a decompiler (been there done that)

@ryanmkurtz @weiwang999 one must understand that this is partly the goal of a decompiler however the way as weiwang seem to want to do it is not even a way forward. This can however be achieved by understanding and reimplemtning the code in a DSO and overload the original code, at least given how ELF loaders works; How they work and everything about it is left for the reader as an exercise.


Status changes and bonuses removed after enchanting

Apotheosis-1.19.2-6.5.0.jar
In the Enigmatica 9 Expert Mod Pack
Enigmatica9Expert-1.20.1.zip
I had just re-forged this axe and it had the correct stats but was removed after I enchanted it.
I then re-forged it again and this time it didn't give the stat bonuses indicated but also didn't change the top bonuses.
(The reforge had loot pinata and the finished product doesn't and I am pretty sure it didn't change)

Appears to still give stats even if it doesn't show when hovering over weapon.

This is typically seen with a specific version of irons spells try updating it to the latest

Likely related to https://github.com/Shadows-of-Fire/Apotheosis/issues/1234


Duplicate markers in clusters when zoomed in

[x] I'm reporting a bug, not asking for help
[x] I'm sure this is a Leaflet.MarkerCluster code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[x] I've searched through the issues to make sure it's not yet reported

How to reproduce

Leaflet 1.6.0
Leaflet.MarkerCluster 1.4.1
Browser: Google Chrome 81
OS/Platform: Windows 10
Large dataset (>1000 markers)

The behaviour I'm expecting and what I'm seeing
I have quite a large dataset (1078 markers and circles in total) and the clusters/groups are of the proper size when zoomed out to around zoom level 10. The problem lies when I zoom into an area and the groups recalculate and split out. It seems that duplicate markers are introduced at this point as the spider view of most clusters shows multiple duplicate markers and circles. Then, when zoomed in further to the point that the clusters disappear, the correct placement and number of circles/markers is restored.
I originally thought this was a problem with the dynamic JSX components I was adding to the MarkerClusterGroup (as this bug was originally found in React, using react-leaflet and react-leaflet-markercluster). However, I have recreated the issue in plain JavaScript and the problem persists.
I think the problem might lie with the size of my dataset and the density of the points messing with the clustering and spiderfy calculations?
Minimal example reproducing the issue

[x] this example is as simple as possible
[x] this example does not rely on any third party code

Original example with React.
Example in plain JavaScript (probably what will be more useful here).
Images illustrating the problem

Hi,
Looks to me as expected behaviour, given the fact that you have duplicate locations in your data.
Once zoomed in enough, you see the actual position of these places, hence duplicates exactly stack, and you may not notice it.
But when clustered or spiderfied, Leaflet.markercluster will count each place separately, even if all their data is identical: hence the "extra" counts and "ghosts" in spider.
For example I see 2x "Surrey Square Park" and 4x "Burgess Park" in your db.json file, all with exact same data. Therefore when clustered, they count as 6 items.

Hi @ghybs,
You're absolutely right, I can't believe that I didn't see that my data was being duplicated. I have now added a unique index to my DB to stop this from happening.
Thanks everyone else and I'm sorry for wasting anyone's time, just never crossed my mind to check the actual data,
Josh


fix: migrate to TransactionTokenType type

What it solves
Build issues with latest SDK types
How this PR fixes it
Wherever TokenType was being used, relative to transactions, TransactionTokenType is not being used in accordance with the following: https://github.com/gnosis/safe-react-gateway-sdk/pull/62

The client gateway returns NATIVE_TOKEN for TokenType enum and Transaction type uses NATIVE_COIN to define native chain token.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 4 (0.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 34.848%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/safe/components/Transactions/TxList/TokenTransferAmount.tsx
0
1
0.0%

src/routes/safe/components/Transactions/TxList/TxInfoDetails.tsx
0
1
0.0%

src/routes/safe/components/Transactions/TxList/modals/ApproveTxModal.tsx
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3364

Relevant Lines:
8724

💛  - Coveralls

I am not sure if we need all the changes or if its enough to only change occurrences of NATIVE_COIN to TransactionTokenType since everything else is the same in both types.

Although that makes total sense, when types themselves use TransactionTokenType as a value, we have to follow. Erc20Transfer is a good example.

@dasanra, I've addressed your two comments here.


Change Shape In Icon background.

How can I change the shape of icon background. E.g I want rectangular shape with rounded corners on the back of selected icon.

Try the indicatorSides property :)

@craiglabenz  i just saw you refactor code, so can you push new version to pub.dev?


[Locale selector] React: Visual QA of design inconsistency fixes

This work is a follow-on to the development work done to create / change the same Web Component version. The Web Component development was managed under the same epic (#6395 )
User Story

As a [user role below]:
DDS Designer and Developer

I need to:
test the Locale selector

so that I can:
be sure the developer's code correctly works as designed

Additional Information

See the Epic for the Design and Functional specs information
Designer will be added as a reviewer to the Pull Request.  Visual QA reviewer will be notified by Github when review is needed.
Creating a QA bug
React Dev Issue (#6583 )
Testing links provided in the Pull Request

Tasks
Ensure the Locale selector component has been tested and reviewed by design + dev.
Acceptance criteria

[ ] Pattern is reviewed by designer and design defects are identified
[ ] New issues are opened to log individual defects
[ ] Screenshots of as-is and to-be design should be added to the issue when needed
[ ] Developer associated with building the pattern is assigned to the new issues
[ ] Appropriate labels are added to the issue  eg.  bug, dev

Consolidated into Web Components dev issue (#6582 ).  Closing.


Replaced protection macroses with pragma once

This PR closes #508

Can one of the admins verify this patch?

Can one of the admins verify this patch?

verify

Windows test PASSed.

Linux test PASSed.

verify

Linux test PASSed.

Windows test PASSed.


Viewer Crash: when using contextOptions

while trying to make Viewer container transparent, using -
contextOptions: {
webgl: {
alpha: true,
},
}.
scene is suddenly undefined after it passes as filled.
using version 1.16.1
thanks for any help.

Found a solution, Suggesting added it to documentation for those who need transparent map
when using contextOptions u need to use "useCesium" in children and not use the ref of viewer, other wise its crashing the viewer.


License?

I'm guessing that this code is intended to be open sourced otherwise it wouldn't be here, but is there a particular license that you'd like to choose for your work?

no particular license yet. you can add one if you like.

发件人: slremy<EMAIL_ADDRESS>发送时间: 2018年5月8日 13:30
收件人: brightmart/text_classification
抄送: Subscribed
主题: [brightmart/text_classification] License? (#52)
I'm guessing that this code is intended to be open sourced otherwise it wouldn't be here, but is there a particular license that you'd like to choose for your work?
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/brightmart/text_classification/issues/52, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASuYMMB-6r3_gDBGnZMldWWYwP6W59Qzks5twS15gaJpZM4T2CY7.


dev docs: Document how to fix cached state issues

Motivation
We want any developer to be able to fix CI issues. Sometimes fixing cached states is complex.
Required Documentation
TODO: make a list of what needs to be documented here

Here is how to test a change to the cached state CI workflows:
https://github.com/ZcashFoundation/zebra/pull/7557/files#r1325230754

Here is an example of a test that passes in Rust, but fails in the CI workflow:
https://github.com/ZcashFoundation/zebra/actions/runs/6165092427/job/16733752210?pr=7515

Here's how to manually rebuild a cached state:
https://github.com/ZcashFoundation/zebra/pull/7507#discussion_r1322038826

Here's how to delete an invalid cached state:
https://github.com/ZcashFoundation/zebra/pull/7555#issuecomment-1718658271

I think we should probably document how to check the cached state details to identify whether it may have a problem or not, so:

How to find the cached state
how to figure out when/how it was generated
how to extract other meaningful data from it

An example of how to find the cached state used by a test:
The cached state used by the failing PR is not from #7531, it was generated by the self-hosted runners branch (the branch name and commit are after the cache type prefix):
zebrad-cache-self-hosted--7c7e860-v25-mainnet-tip-075639
Here is where the cached state is logged in CI:
https://github.com/ZcashFoundation/zebra/actions/runs/6169241952/job/16744865315?pr=7349#step:10:133
That cached state was created using a full sync. Full syncs have different tags from updates (the start height, original version, and update flag -u are all different). Here is a link to the list of cached state images and their tags:
https://console.cloud.google.com/compute/images?tab=images&hl=en&project=zfnd-dev-zebra&pageState=("images":("s":[("i":"creationTimestamp","s":"1"),("i":"creator","s":"1"),("i":"name","s":"0")],"f":"%255B%257B_22k_22_3A_22Created%2520by_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22zfnd-dev-zebra_5C_22_22_2C_22i_22_3A_22creator_22%257D_2C%257B_22k_22_3A_22Name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22self-hosted_5C_22_22_2C_22i_22_3A_22name_22%257D%255D"))&pli=1

Cached states are only written if they are higher than the previous state by at least 1000 blocks (1 day).
Here's how to force a new cached state to be saved, regardless of its height:
https://github.com/ZcashFoundation/zebra/pull/7560#discussion_r1325288736

Sometimes cached states are saved with a very low number of blocks due to a Rust test or CI bug. This issue has come up recently with both Zebra and lightwalletd cached states.
Here's an analysis of one bug like that:
https://github.com/ZcashFoundation/zebra/pull/7555#issuecomment-1718658271

Fix steps from ticket #7661:

[ ] Find all the lightwalletd cached states with heights less than 2 million
[ ] Work out which PR, branch, and CI job created them, and open a ticket to fix it
[ ] Optional: stop creating new invalid images, by stopping running CI on that PR, or disabling that scheduled CI job (if that's possible)
[ ] Delete all the lightwalletd cached states with heights less than 2 million (they are all invalid)
[ ] Repeat these steps until the original bug is fixed, merged, and all PRs are updated with that fix


getMedias() 404 and how to check comment closed on post

Hi, method getMedias return 404 a few days ago and question about how to check comments closed or open on post?
P.S. Sorry for my english, i'm not like translaters)))))

update to the last version of the library


Update solutioncomponent.md

Updated term from CRM to Dataverse

@ericregnier The entity reference documentation is generated from the web service. Any change to the published reference docs will be overridden when we next do a doc refresh.
@KumarVivek Can you please verify if Eric's doc change in this PR cannot be done this way.


Rendering component wrapped in withRouter throws when no Router is present

Version
4.0.0, 4.0.0-beta.8
Test Case
import React from 'react' // 15.4.2
import renderer from 'react-test-renderer' // 15.4.2
import { withRouter } from 'react-router'

const Component = () =>

const WrappedComponent = withRouter(Component)

it('will render', () => expect(renderer.create(<Component />)).toBeDefined())
it('will fail', () => renderer.create(<WrappedComponent />))

Steps to reproduce
Run above tests in Jest, or any other test runner.
Expected Behavior
Rendering WrappedComponent with react-test-renderer does not fail.
Actual Behavior
  ● will fail

    TypeError: Cannot read property 'route' of undefined

      at Route.computeMatch (node_modules/react-router/Route.js:66:22)
      at new Route (node_modules/react-router/Route.js:43:20)
      at node_modules/react-test-renderer/lib/ReactCompositeComponent.js:295:18
      at measureLifeCyclePerf (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:75:12)
      at ReactCompositeComponentWrapper._constructComponentWithoutOwner (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:294:16)
      at ReactCompositeComponentWrapper._constructComponent (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:280:21)
      at ReactCompositeComponentWrapper.mountComponent (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:188:21)
      at Object.mountComponent (node_modules/react-test-renderer/lib/ReactReconciler.js:46:35)
      at ReactCompositeComponentWrapper.performInitialMount (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:371:34)
      at ReactCompositeComponentWrapper.mountComponent (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:258:21)
      at Object.mountComponent (node_modules/react-test-renderer/lib/ReactReconciler.js:46:35)
      at ReactCompositeComponentWrapper.performInitialMount (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:371:34)
      at ReactCompositeComponentWrapper.mountComponent (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:258:21)
      at Object.mountComponent (node_modules/react-test-renderer/lib/ReactReconciler.js:46:35)
      at mountComponentIntoNode (node_modules/react-test-renderer/lib/ReactTestMount.js:55:31)
      at ReactTestReconcileTransaction.perform (node_modules/react-test-renderer/lib/Transaction.js:140:20)
      at batchedMountComponentIntoNode (node_modules/react-test-renderer/lib/ReactTestMount.js:69:27)
      at ReactDefaultBatchingStrategyTransaction.perform (node_modules/react-test-renderer/lib/Transaction.js:140:20)
      at Object.batchedUpdates (node_modules/react-test-renderer/lib/ReactDefaultBatchingStrategy.js:62:26)
      at Object.batchedUpdates (node_modules/react-test-renderer/lib/ReactUpdates.js:97:27)
      at Object.render [as create] (node_modules/react-test-renderer/lib/ReactTestMount.js:125:18)
      at Object.<anonymous> (src/components/Button/Button-snapshot.js:9:118)
      at process._tickCallback (internal/process/next_tick.js:109:7)

Route.computeMatch (node_modules/react-router/Route.js:66:22) is
  Route.prototype.computeMatch = function computeMatch(_ref, _ref2) {
    var computedMatch = _ref.computedMatch,
        location = _ref.location,
        path = _ref.path,
        strict = _ref.strict,
        exact = _ref.exact;
    var route = _ref2.route; // _ref2 is undefined

Passing { withRef: true } to withRouter has no effect.
This makes it hard to unit test any component that renders as one of its children a component wrapped in withRouter.
Can be worked-around by inserting a Router.
import { MemoryRouter as Router, withRouter } from 'react-router-dom' // 4.0.0

it('will pass', () => {
  expect(
    renderer.create(<Router><WrappedComponent /></Router>)
    .toJSON()
  ).toEqual({children: null, props: {}, type: 'div'})
})

Thanks!
possibly related bugfix here https://github.com/ReactTraining/react-router/issues/4292

hello ，
is  react-router-rom 4.0.0,  support dynamic component?  and load component by required
here is my test code

    <Router>
        <Route   path="/"    component= {  ()=>{
                    import ('  ./modal ')
           }  }  >
    </Router>

The testing guide covers the necessity of rendering inside of a <Router>.
I'm not sure if react-test-renderer allows you to pass in a context object, but if it does you can use react-router-test-context to simulate the context a router would provide. While I wrote it, I actually believe that it is usually better to just use a <MemoryRouter>. From my limited experience testing it, shallow rendering does not work well with <Route>s.
Also, I'm not positive, but is your reference to withRef just related to computeMatch having _ref and _ref2 as arguments? That is just a babel thing. I'm not actually sure how ref works with withRouter because I haven't had a need to use them together. I know that some HOCs have to do some hoisting, but I haven't seen anyone bringing up having issues with that yet.

Also, I'm not positive, but is your reference to withRef just related to computeMatch having _ref and _ref2 as arguments?

No, it's related to when that existed:
https://github.com/ReactTraining/react-router/pull/3735
https://github.com/ReactTraining/react-router/pull/3740
Anyway, it'd be better if a component using withRouter didn't throw outside a router for a variety of reasons -- which is why y'all merged a bugfix for this same issue in December of 2016: https://github.com/ReactTraining/react-router/issues/4292
Hope you reconsider closing this.

I'll re-open for the time being for the ref issue, but I can say that I'm about 99% sure adding functionality to components just for testing purposes isn't going to happen.

There are non-testing applications. Imagine a component that is used in two component trees -- one having a Router and another not.

but I can say that I'm about 99% sure adding functionality to components just for testing purposes isn't going to happen.

I'm not sure I get your reasoning, I like RR4 so far but if it that means I can't test my components I'm going to have to revert to using RR3. I have a component A that renders a component withRouter(B).
Currently I can't test A because if I don't wrap it the test crashes, and if I wrap it in per example a MemoryRouter then I can't use most of enzyme's methods (setState etc.) as they can only be called on the root component, which is now the router.
Maybe there's a better way I haven't thought of though, I checked a bit on both enzyme and RR's repositories and didn't find much but I haven't worked with RR4 for long so :/

It makes sense that if you wrap a component in something called withRouter that it wouldn't work correctly if you don't render it in the context of a <Router>. If you didn't, what props would you expect to receive?

If you didn't, what props would you expect to receive?

undefined

Maybe I can phrase it differently: if you're not planning on rendering a component inside a <Router>, why are you wrapping it in withRouter?
// This makes sense to me.
<Router>
  {withRouter(MyComponent)}
</Router>

// This doesn't.

  {withRouter(MyComponent)}

What's preventing you from just not using withRouter when you unit test your component?

Nothing, that's what I'm doing now to work around this.
It requires me to export the unwrapped component and import that in my test, which is a mild inconvenience.
Crux of the issue is that I don't expect withRouter to throw in this case, and think it would be nicer if it behaved as it did after https://github.com/ReactTraining/react-router/pull/4295 was applied to fix this issue once before.

Perhaps a noop with a warning message would be best?

We ended up inserting a  in our tests for those cases.

That's the way all of our tests work here; they all render a <Router> at the top of the component hierarchy.
I get that this is really inconvenient for you, but I'm just not sure the best way to fix it. What does redux do if you render one of your connected components without a <Provider> up top? Does it just give you no props and a warning?

We fire an invariant, but we have a special case of not requiring a context provider, as we also support the store prop. It's a little different from our use case here.
But I think #4939 will cover this if we can get it merged.

I'm just not sure the best way to fix it

My vote is for
if (!router) {
  return <WrappedComponent {...this.props} />
}

Well, #4939 is now merged which is going to yell at people if they try to use any of <Route>, <Switch>, <Link>, or withRouter outside the context of a <Router>. I personally think this makes a lot of sense: don't use our API if you're not going to render a <Router> up top. At least that should help people to know what they're doing wrong.
I'm open to ideas, but I don't like the thought of making withRouter (or any of our API) a no-op when there's no router on context. That just opens up a whole category of issues that I don't believe we should be responsible for addressing.

What's the conclusion for this case mentioned the above:

There are non-testing applications. Imagine a component that is used in two component trees -- one having a Router and another not.
This actually happened in our codebase just moments ago

But all the later discussions are about testing. We are actually experiencing the issue with non-testing application; we have an complete React application with routing and React components which are just a part of pages generated by Rails.
The components as parts of Rails pages should not manipulate history. Instead, it should navigate to the page by requesting the destination page.
See https://github.com/tootsuite/mastodon for our case. In the case,

The landing page is generated by Rails, but contains a preview built with React (the part titled with "a look inside" at https://mastodon.social/about.) Actions using history are prohibited or delegated to actual navigation.
The page after signing in is built with React and uses react-router and it handles all routing.

this question is not related but anyone can help where I must to  write throw function to display errors?
it's not clear on tutorials...

const SignInWithData = graphql(signInMutation)(withRouter(SignInFormContainer));

const mapDispatchToProps = dispatch => ({
  signInDispatcher(token) {
    dispatch(signIn(token));
  },
});

const SignInWithDataAndState = connect(
  null,
  mapDispatchToProps,
)(SignInWithData);

export default SignInWithDataAndState;

Use react-router-dom mock like this:
import React from 'react' // 15.4.2
import renderer from 'react-test-renderer' // 15.4.2
import { withRouter } from 'react-router'

jest.mock('react-router-dom'); // <- Use this line

const Component = () =>

const WrappedComponent = withRouter(Component)

it('will render', () => expect(renderer.create(<Component />)).toBeDefined())
it('will fail', () => renderer.create(<WrappedComponent />))


Microsoft Learn

Type of issue
Other (describe below)
Description
Please Update latest.
Page URL
https://learn.microsoft.com/en-us/python/api/azure-ai-ml/azure.ai.ml.constants.assettypes?view=azure-python
Content source URL
https://github.com/MicrosoftDocs/azure-docs-sdk-python/blob/main/docs-ref-autogen/azure-ai-ml/azure.ai.ml.constants.AssetTypes.yml
Document Version Independent Id
f05d6281-33e2-ead9-c566-11d12299fce4
Article author
@lmazuel
Metadata

ID: fc8926ce-c1ad-3c3f-8c22-14b85c55240a
Service: machine-learning

@raman000 - What is the ask here? What needs to be updated?

have a Fixed.


Each block doesn't work and crash all app when parameter is not iterable

Describe the problem
Some times I get the wrong data and then the whole app crashes cause each block doesn't work with something that is not iterable(object, null, undefined, number, etc.). I cannot even logout cause my code runs after mount. And I should {#if isIterable} or {#if exist} or {#if exist || iterable} checks everywhere even if I not consider login logout case. There is {:else} which works only when it is empty array. And I cannot use await blocks cause many times there is no promise and etc or promise result binds to specific variable which goes to other each block in component of component. If check to each blocks makes my code very large and ugly. Is there only each block or each in each in each. But in second case it makes my code even uglier and I want to drop my code.
Describe the proposed solution
I would like to see {:catch er} addition to s-each-else group which prevents app crashing when it is in code. This will give a choice what to do if params are not iterable. Something like s-each(iterable)-else(iterable-empty)-catch(not-iterable)
Alternatives considered
1)Or just make each block itself check if params are iterable values and if not then it is just like {#if con} block doesn't show and works {:else} block. This would be better cause there is a bug - each block works even if I write it in if block. I don't know why this happens, I just solved it and don't remember how. If checks are very annoying. This solution is the same like the main proposed solution, it is just ignores any error or just shows it in console
2)Or make another block like {#for} which will work like 1)
Importance
i cannot use SvelteKit without it
Additional Information
No response

Duplicate of https://github.com/sveltejs/svelte/issues/9005 and other issues.

@Conduitry the whole app crashes which doesn't happen when you use React or Vue, in them crashes only one function. If this is not problem then what is problem

@Rich-Harris as I read other issues many people asked for this feature

There is a proper way to fix this problem — error boundaries — that we will implement once it's a possibility (the Svelte 5 rewrite is partly about enabling this). The fix you propose here is the wrong approach and isn't going to happen, and @-ing me isn't going to change that.

@Rich-Harris thank you. And sorry for @. The reason why I did is that Conduitry didn't say a couple of word that there is coming solution like you did and he closed as not planned, and in the referenced issues there is || [] solution which is good but errors are still there crashing whole app.