BOP solver: Using number_of_solvers results in abnormal status

Hi, I am current trying to use the multi-threading feature of the BOP solver with the pywraplp frontend. I'm using Python 3.7.4 with OR-Tools 7.3.7083.
The following code results in an ABNORMAL result status:
from ortools.linear_solver import pywraplp

def main():
    solver = pywraplp.Solver('test', pywraplp.Solver.BOP_INTEGER_PROGRAMMING)
    solver.EnableOutput()
    solver.SetSolverSpecificParametersAsString("number_of_solvers: 2 synchronization_type: SYNCHRONIZE_ALL")

    x = solver.IntVar(0, 10, "")
    y = solver.IntVar(0, 10, "")
    solver.Add(y == 2*x)
    solver.Maximize(y)

    result_status = solver.Solve()
    print(f"{pywraplp.Solver.OPTIMAL} == {result_status}")
    if result_status == pywraplp.Solver.OPTIMAL:
        print(f"x = {x.SolutionValue()}")
        print(f"y = {y.SolutionValue()}")

main()

Output:
0 == 4

However, when I comment out the solver.SetSolverSpecificParametersAsString line or use number_of_solvers: 1 instead it works as expected:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0815 11:40:39.133632 20305 bop_portfolio.cc:147]       30 .. inf Portfolio - SATRandomFirstSolution. Time limit: inf -- inf
I0815 11:40:39.133743 20305 bop_portfolio.cc:79] Stats. #new_solutions/#calls by optimizer:
                      SATRandomFirstSolution :   0/1    (  0.00%)  Total gain:      0  Total Dtime: 0.000 score: 0.000001
0 == 0
x = 5.0
y = 10.0

Are you sure this is a supported parameter? I guess not, and the solver tells you it could not parse this string.

And really, you should not use BOP for that, BOP is for Boolean problems. The support for integer variables is slow and experimental.
In fact, you should use the CP-SAT solver directly:
from ortools.sat.python import cp_model

def main():
    model = cp_model.CpModel()

    x = model.NewIntVar(0, 10, "")
    y = model.NewIntVar(0, 10, "")
    model.Add(y == 2*x)
    model.Maximize(y)

    solver = cp_model.CpSolver()

    result_status = solver.Solve(model)
    print(f"status = {solver.StatusName(result_status)}")
    if result_status == cp_model.OPTIMAL:
        print(f"x = {solver.Value(x)}")
        print(f"y = {solver.Value(y)}")

main()

which outputs
status = OPTIMAL
x = 5
y = 10

to add Parallelism, just add the line
solver.parameters.num_search_workers = 8

Thanks for the suggestion with CP-SAT but I'm currently comparing different MIP solvers, so I want to use BOP.

Are you sure this is a supported parameter?

Yes, I've discovered it here: https://github.com/google/or-tools/blob/v7.3/ortools/bop/bop_parameters.proto#L184
  // The number of solvers used to run Bop. Note that one thread will be created
  // per solver. The type of communication between solvers is specified by the
  // synchronization_type parameter.
  optional int32 number_of_solvers = 24 [default = 1];

I guess not, and the solver tells you it could not parse this string.

It actually does not give me any error message.
When I do something obviously wrong like:
solver.SetSolverSpecificParametersAsString("foobar: 1")

I get an error message:
[libprotobuf ERROR /home/hans/projects/or-tools/dependencies/sources/protobuf-3.9.0/src/google/protobuf/text_format.cc:324]
Error parsing text-format operations_research.bop.BopParameters:
1:7: Message type "operations_research.bop.BopParameters" has no field named "foobar".

But this works just fine without error message:
solver.SetSolverSpecificParametersAsString("number_of_solvers: 2 synchronization_type: SYNCHRONIZE_ALL")

So, is this an official feature of BOP or not?


Rebuild to check for segfaults using macos 3.13.0rc2

Seeing segfaults with import contourpy on macos using conda-forge's python 3.13.0rc2, so here bumping build version to run through CI.

Local build on macos arm passes full contourpy test suite so I'm merging this.


Mini lambdas

{ ... } should be an expression that evaluates to an anonymous function that takes zero arguments. This will make it easy to create control structures in nom itself.
forever {
...
...
}

well done you predicted what I'm working on right now :sparkles:

:sparkles:


Redragon mouse support (opendragon)

Hi, I am the author of https://github.com/GrbavaCigla/opendragon and I would like to add redragon support to libratbag. Can you give me directions on source code so I can add it? Thanks in advance.

Sorry no one got to you, at the moment we have a problem with lack of maintainers, or better said, maintainers with time.
I think the best approach is to take an  existing driver and modify it to work with redragon, the most feature complete driver is the hidpp20 I believe, this also means its probably more complicated though.
Sorry I can't get much indepth help I'm still getting familiar with the code base myself, but feel free to ask specific questions about anything.

This is excellent work, your PR will be appreciated.
As @perigoso said src/driver-hidpp20.c would be the best place to start, you can also look at src/driver-steelseries.c.
In general each driver exports a drive structure struct ratbag_driver.
struct ratbag_driver hidpp20_driver = {
	.name = "Logitech HID++2.0",
	.id = "hidpp20",
	.probe = hidpp20drv_probe,
	.remove = hidpp20drv_remove,
	.commit = hidpp20drv_commit,
	.set_active_profile = hidpp20drv_set_current_profile,
};

We would read all the settings in the .probe function and then write all the settings in the .commit function.
To reading and writing to a device we have.
ratbag_hidraw_output_report and ratbag_hidraw_read_input_report
or
ratbag_hidraw_get_feature_report and ratbag_hidraw_set_feature_report
Please feel free to ask if you have anymore questions

Thanks for the directions :D
Since redragon mice are partially reversed engineered and every mouse seems to be a little bit different, how should I structure it?

If they are all similar with slight differences, I think a single driver with "quirks" is the best approach, take a look at the src/driver-steelseries.c driver, that deals with problems like these

I'll close this for now as it doesn't seem like there is any work being done at the moment.
For Redragon mice also see #1217.


Consider Always Showing IDs in Problems Panel

The Problems panel lists reports showing the name specified in the report and falls back to showing their ID.
In this example the warning shows the ID while the the errors show the name:

We should consider always showing the IDs for the following reasons:

IDs are unique while names can be duplicated which would make it harder to distinct between reports
Names tend to be longer than IDs, rarely can the entire name be shown
Names might not actually help to identify problems quicker

Follow-up to https://github.com/camunda/camunda-modeler/pull/3257

Summary of current arguments:
Pro Name (+ ID fallback):

Names have a much higher chance to be set then the IDs
Users write the names themselves, which makes them easier to recognize then automatically defined IDs
Names are always visible on the canvas, IDs are not

Pro ID:

IDs are unique while names can be duplicated which would make it harder to distinct between reports

Contra argument: Duplicate task names are in general discouraged since it reduces understandability of the diagram

Names tend to be longer than IDs, rarely can the entire name be shown

Contra argument: Only the first n chars of the name are neccessary for the user to recognize the element

Flow nodes are often named "yes" and "no", and are hard to distinguish in the problems panel

Contra argument: Flow nodes rarely produce problems, and if they do, you are midst modeling and can easily make the connection between the "yes"/"no" shown in the panel, and the only flows annotated in the canvas (the ones recently added)

It may appear weird if you add a task, then you see the task id in the problems panel, then you rename the task, and then you see the name

@YanaSegal @philippfromme

Let's close this as the discussion on this item was non-conclusive. If we receive further feedback we can re-open.


Can't get this working with vue-router

Whenever I try to set up the vue router with this template I end up getting a Cannot GET / message in my browser. I have a project from a couple weeks ago, using this same template, and it works fine there. The major different that I've noticed is the build/webpack.dev.conf.js file has changed a lot. If I copy the other one over from my working project it starts working again.
To reproduce just set up a new project using this template from the cli and try to set up vue-router. Maybe I'm just doing it wrong too.

+1 reproduced this just a few minutes ago

It's working properly for me... any compilation errors? Can't help without a reproduction.

https://github.com/ebuchmann/VueRouterIssue
Here you go. It's the basic install with vue cli using webpack. In the build/webpack.dev.con.js file I've commented out an older version of the file that I had, which seems to work fine. Right now it just says Cannot GET / and doesn't show anything else in my browser that may help. No errors in the terminal other than linting issues with spaces.

Did you notice the lint warnings in the console after you do npm run dev? You need to fix the lint errors for the bundle to compile.

Interesting. Didn't think it would be so picky about leaving a warning about having four spaces instead of two. Thanks!

The template comes with pre-configured ESlint linting. You can either tweak it to your own preference or disable it by removing eslint in here and here.


(serveStatic plugin) Serve default file when no file matches

I ran into the same issue as #13 and was expecting the serveStatic plugin to server the default file if there wasn't a match in the file system, which is what the documentation implies.
This PR inserts a check to see if a default file was specified and to try and serve that instead of returning ResourceNotFound. There is also a check to make sure that we do send ResourceNotFound is the default file doesn't exist. This makes the serveStatic plugin match what the documentation describes.

Hey @JoeDoyle23,
We appreciate this PR! :heart:
It looks like this is in the home stretch for being merged, just pending tests. We are in the process of moving the plugins back into the main repo. If memory serves, we directed you here in the first place, sorry to send you back and forth. I'm going to close this PR for now so we can get the merge underway (it is one of the few things left blocking a 5.x release). If this PR is still important to you, please re-open it against the main repo with tests and we will be more than happy to merge :smile:


Typo: missing an "r"

https://github.com/UniStuttgart-IKR/AttributeGraphs.jl/blob/0c548f177ed02e6d671fcfedf978961bd414b088/src/abstractattributegraph.jl#LL1C15-L1C36

Closed by https://github.com/UniStuttgart-IKR/AttributeGraphs.jl/commit/6cb492a1c36c66c097009b9a83783b4604e1fa70


[WIP] adding interfaces for staggered grid implementation

working to fix #255

To add a bit more detail - my guiding example is the wave equation, following:
Staggered Time Integrators for Wave Equations Michelle Ghrist and Bengt Fornberg and Tobin A. Driscoll
Currently, one can implement the wave equation with periodic B.C.'s in MoL as:
using OrdinaryDiffEq, ModelingToolkit, MethodOfLines, DomainSets, Plots;

@parameters t x
@variables ρ(..) ϕ(..)
Dt = Differential(t);
Dx = Differential(x);

a = 0.1;
L = 10.0;

eq = [Dt(ρ(t,x)) + Dx(ϕ(t,x)) ~ 0,
      Dt(ϕ(t,x)) + a^2 * Dx(ρ(t,x)) ~ 0]
bcs = [ρ(0.0,x) ~ exp(-(x-L/2)^2),
       ϕ(0.0,x) ~ 0.0,
       ρ(t,0) ~ ρ(t,L),
       ϕ(t,0) ~ ϕ(t,L)];

domains = [t in Interval(0.0, 100.0),
           x in Interval(0.0, L)];

@named pdesys = PDESystem(eq, bcs, domains, [t,x], [ρ(t,x), ϕ(t,x)]);

dx = 0.1;
# must use WENO, otherwise upwind is default, biasing one direction
discretization = MOLFiniteDifference([x=>dx], t, advection_scheme=WENOScheme());

prob = discretize(pdesys, discretization);

sol = solve(prob, RK4(), saveat=10.0, dt=dx);
p = plot();
for i in 1:length(sol[t])
    plot!(p, sol[x], sol[ρ(t,x)][i,:], label="t = $(sol[t][i])")
end
display(p)

The simplest PDE we can utilize staggered grids for is the 1D wave equation, with periodic boundary conditions as written in the code block above. If we discretize this  on staggered space and time, we obtain the update rules:
$$\rho_x^{t+1} = \rho_x^{t-1} - \left(\frac{\Delta t}{\Delta x}\right) \left( \phi_{x+1}^t - \phi_{x-1}^t \right) \ ; \qquad \phi_x^{t+1} = \phi_x^{t-1} - \left(a^2 \cdot \frac{\Delta t}{\Delta x}\right) \left( \rho_{x+1}^t - \rho_{x-1}^t \right)$$
Where the $x,t$'s in the $\rho$ update are distinct from the $x,t$'s in the $\phi$ update.
Next step is to write functionality to generate these grids...as mentioned in the above reference, time/space staggering may be independently desired, so I think it best that these are in fact distinct space grids (values in between solved grid points can simply be interpolated after the fact).

Just an update here - slow progress.
Many responsibilities split between PDEBase and MethodOfLines. Ultimately, the functionality to do the differencing already exists - I'm simply trying to generate code to compute centered finite differences in two steps. The rigidity is coming from an interaction between the two packages, where MethodOfLines refuses to leave dangling variables (fair), and once passing a system of equations to PDEBase, it fully discretizes them into a single function (also fair).
I think the most logical entry point here is to overwrite the PDEBase orchestrating "discretize", but this has such nice generality I've hesitated thus far, looking for a downstream entry...
Additionally, MethodOfLines does a good job ensuring a 1-1 matching of equations and unknowns, splitting the functionality into two functions makes this more difficult...
One could do this all in one go, i.e. write a new set of rules to discretize the space differential to do the staggering, but this gives away a lot of flexibility, and I don't see it generalizing to other space/time/boundary staggering easily - meaning it really doesn't solve the fundamental issue.
One could overwrite the MoL pass, checking for staggering type, breaking the pdesystem into component equations (and BCs) to be solved on the whole and half steps, removing the looping over all dependent variables (only generate functions for the variable the equation is for...this is identified somewhere), and instead loop over all such sets of eq=>var pairs. Only after all the discretization has been done, and whole and half timestep functions generated will we do the basic checks. This is probably best path forward.

Maybe this is a failure in segregation, the split between PDEBase and MOL is quite new and malleable, can you envisage a demarcation that would make this easier?
In any case, supporting all bcs in this scheme is hard. You are free to throw out the difficult to support the possible. Working out what the demarcation should be is the most difficult problem here. Do you have an intuition?

For context, no other discretizer currently uses anything outside of the variable map,  and the tools in symbolic_utils.jl.
I want to understand whether symbolic_discretize is a general procedure or if it belongs in MOL and all discretizers implement this manually.

Yeah, I think you cut to the heart of the issue. I want to say you could do it without ownership of symbolic_discretize (it lowers developer overhead and the generality of the unified implementation is certainly compelling).
Unfortunately, I think you might run into similar issues for other solution methods, for example operator splitting.
https://docs.sciml.ai/DiffEqDocs/latest/types/split_ode_types/
I'll first overwrite symbolic_discretize to get something working, and then perhaps it'll be easier to determine if the heavy hammer was necessary.

Even specializing SciMLBase.discretize isn't enough, as the engine of structural_simplify again forces closing the system of equations before generating a function (ExtraVariablesSystemException)
Much of this effort is to navigate around the constraint of closing equations at the individual function level - i.e. f(u, p, t) must update all components of u or we run into errors at essentially every step.
This doesn't seem like a fundamental limitation though - if one can generate from symbolics a function that updates all variables, one should also have the ability to generate a function that updates a subset...
I think next step is to diagram the flow and blocking functionality so we can discuss what to target with better visibility.

Good point, this will probably need an update to MTK to fix

Incremental update, via suggestions from @xtalax @ChrisRackauckas, used "symbolic tracing" to translate the single generated update function into two updates (integer and half-step updates).
Currently very hacky, but possible to see how this can be translated. Hurdles now are to

allow space staggering (this example is only time-staggered, not space).
solve the PDE, create regression test.
agree where this step fits, implement mvp and ask for PR review
once interior can be time and/or space staggered using periodic BCs, we can begin handling more general conditions.

using OrdinaryDiffEq, ModelingToolkit, MethodOfLines, DomainSets, Plots;

@parameters t x
@variables ρ(..) ϕ(..)
Dt = Differential(t);
Dx = Differential(x);

a = 0.1;
L = 3.0;
dx = 1.0;

initialFunction(x) = relu(x-L/4) - 2*relu(x-(2*L/4)) + relu(x-(3*L/4))

eq = [Dt(ρ(t,x)) + Dx(ϕ(t,x)) ~ 0,
      Dt(ϕ(t,x)) + a^2 * Dx(ρ(t,x)) ~ 0]
bcs = [ρ(0.0,x) ~ exp(-(x-L/2)^2),
       ϕ(0.0,x) ~ 0.0,
       ρ(t,0) ~ ρ(t,L),
       ϕ(t,0) ~ ϕ(t,L)];

domains = [t in Interval(0.0, 10.0),
           x in Interval(0.0, L)];

@named pdesys = PDESystem(eq, bcs, domains, [t,x], [ρ(t,x), ϕ(t,x)]);

discretization = MOLFiniteDifference([x=>dx], t, grid_align=MethodOfLines.CenterAlignedGrid());
#discretization = MOLFiniteDifference([x=>dx], t, grid_align=MethodOfLines.StaggeredGrid());

prob = discretize(pdesys, discretization);

#prob.f now has the generated function, want to symbolic trace to get integer and half step
# iterations
@variables rho[1:3] phi[1:3]

# choose which outputs we want..
drho = (prob.f([collect(rho); collect(phi)], nothing, 0.0)[1:3]);
dphi = (prob.f([collect(rho); collect(phi)], nothing, 0.0)[4:6]);

gen_drho = eval(Symbolics.build_function(drho, collect(rho), collect(phi))[2]);
gen_dphi = eval(Symbolics.build_function(dphi, collect(rho), collect(phi))[2]);

dynamical_f1(drho,rho,phi,p,t) = gen_drho(drho, rho, phi);
dynamical_f2(dphi,rho,phi,p,t) = gen_dphi(dphi, rho, phi);
prob = DynamicalODEProblem(dynamical_f1, dynamical_f2, prob.u0[1:3], prob.u0[4:6], (0.0,1.0))

Disgusting hack, bit of it works it isn't stupid!

Looking at commit history, I don't want to keep many of the hacks I put in place here - for ease of review I'll let that branch die and simply start fresh.


Use Web USB after pairing

The logic was broken when we moved the "Always use web USB" stuff into an experiment. With this change, here's the pairing experience:
1, If you never pair the device, we always download
2. If a paired device is connected, we try to use webUSB
3. If the paired device is disconnected, the user gets an error dialog and we go back to downloading until it gets reconnected

There's one critical caveat to the above logic:

if the target has overwritten the deploy logic (e.g. microbit does this), then pxt-core shouldn't unset their override.

This is what was happening when we called init(); again inside setWebUSBPaired, which broke webusb for micro:bit. It's pretty subtle logic so I'm going to try to make it more explicit in my PR.
FYI @riknoll ^^


Fix unzip schema files for RedHat

Zabbix rpms for RedHat don't provide gzipped schema files
So this tasks breaks for me with CentOS 6.6

Thanks!


In the standalone version of Vue devtools 7, the component picker button is nowhere to be found

Vue devtools version
7.0.10
Link to minimal reproduction
Any project
Steps to reproduce & screenshots

Just open the devtools, the component picker button that used to be in the topbar in v6 is nowhere to be found in the standalone version of v7

What is expected?
The component picker button is available
What is actually happening?
It's nowhere to be found
System Info
System:
    OS: macOS 14.2.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 68.42 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node
    npm: 10.3.0 - ~/.nvm/versions/node/v18.19.0/bin/npm
    pnpm: 8.14.0 - ~/.nvm/versions/node/v18.19.0/bin/pnpm
  Browsers:
    Chrome: 120.0.6099.234
    Safari: 17.2.1
  npmPackages:
    vue: 3.3.4 => 3.3.4

Any additional comments?
No response

Should be moved to vuejs/devtools-next


Open Graph Scraper Lite is for the browser, which means we want ES6 imports

Is this possible?

You can do some adjustments, but you'll eventually end with cors issues. It's always meant to be used outside a browser.

This library no longer does HTTP requests, it will now just pull Open Graph and Twitter Card info from HTML pass into it. Please open a new issue if you are still having problems.


Introduce Ninja Smart plug to devices.js

Implement support for Ninja Smart plug from Ninja Blocks Inc.
Support for ON/OFF and power metering.

I think this is a Netvox plug (branded as Ninja Blocks Inc.?)(http://www.computex.biz/PhotoPool2/201504/201504281705364222.pdf). Can you confirm this?

It does look like it. I will see if i can access it as the Netvox Plug and use the identical code.
Not sure if i will be able to do this tonight, though.

@asgothian my guess is that this is exactly the same as https://github.com/Koenkk/zigbee-shepherd-converters/blob/master/devices.js#L1510 but then the EU version.

I did run a test trying to use it as the Netvox Plug by adding the Ninjas identifier to the netvox block:
zigbeeModel: ['Z809AER'] to
zigbeeModel: ['Z809AE3R', 'Ninja Smart plug'],:
I did get the message Failed to configure 0x00137a000001a9b0 Ninja Smart plug, and the metering did no longer work.
I would assume that the hardware is the same, but that Ninja Blocks did some of their own firmware stuff.
A.

Can you provide a link to this device? (url web link)

Unfortunately not, as the company went bankrupt 2015. I assume there is no more web link. People like me, who backed their Kickstarter or bought in early might have them lying around, though.
What i do have is the link to their Kickstarter, which is where i got it from:
https://www.kickstarter.com/projects/ninja/ninja-sphere-next-generation-control-of-your-envir?ref=nav_search&result=project&term=Ninja Sphere
What i can also provide is 3 images - they look very much like the plug you linked.

I did a few more tests, and was able to confirm that the plug does not support the haElectricalMeasurement Cluster. Attempting to read it returns
unsupAttribute {"msg":[{"attrId":0,"status":134}]}
while reading the seMetering Cluster returns
success {"msg":[{"attrId":0,"status":0,"dataType":37,"attrData":[0,2]}]}

Ok, thanks for figuring this out!


mstats.mannwhitneyu and stats.mannwhitneyu return inconsistent pvalues

Moved from https://github.com/scipy/scipy.org/issues/89

@cshowe
Assuming sample_population and base_population are masked arrays:
mstats.mannwhitneyu(sample_population, base_population)
and
stats.mannwhitneyu(sample_population.compressed(), base_population.compressed())
Return the same mann-whitney statistic but differing p-values.  The pvalue from mstats is twice the pvalue from stats suggesting that the mstats implementation is returning a 2 sided pvalue while the stats implementation returns the 1-sided pvalue - but there's nothing in the scipy documentation to indicate that this is the case.

A problem with the stats version that hasn't been changed because of backwards compatibility consideration, so far.
Note: The doc string mentions that p-value is one-sided and needs to be multiplied by 2
http://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.mannwhitneyu.html

The mstats docstring doesn't say what is returned, probably it should say that and that it's different from stats

Ok, the mstats version need to be made more explicit.
The general pattern is to return 2-sided p-values and the docstrings might not always say so.
AFAIR, stats.mannwhitneyu is the only exception and returns half of the two-sided p-value.


Time axis shows no ticks when all data points are less that the selected unit

When all data points have the same month, the month label is not shown
Expected Behavior
Show the current month in the labels section
Current Behavior
The month is not shown in the labels section

Possible Solution
I don't know
Steps to Reproduce
https://codesandbox.io/s/suspicious-field-fk4se?file=/src/App.js
Context
Environment

Chart.js version: 2.9.4
Browser name and version: Chrome 86

I fixed it with a workaround. I wrote a function that check if all data have the same month and year and set unit time to: day, otherwise set unit time to: month.

Labels are added at start if unit. No month starts in the example period.
I don't think this is a bug. But this could be turned into an enhancement request, for placing the labels in the middle of the unit.

I don't think there is anything we can do about this. If the automatic unit selection does not work correctly, that could be altered, but when config states unit, chart will obey that.


cls command doesn't immediately clear the terminal

issuing the cls command on windows, causes me to press enter twice before the terminal is properly cleared.

no wait, it only happens on several occasions. I have not yet figured out the exact problem. /closed/


Fix jsonName in generated json tag

Generator produced json tag with field name instead of jsonName:
e.g. before:
RunWhen     string `protobuf:"bytes,6,opt,name=run_when,json=runWhen" json:"run_when,omitempty"`

after:
RunWhen     string `protobuf:"bytes,6,opt,name=run_when,json=runWhen" json:"runWhen,omitempty"`

Hi, thanks for your PR, but unfortunately, we are no longer accepting any more changes that alter the json tag for several reasons:

This is a breaking change as it will cause the way JSON is serialized for existing users to change.
We consider it a mistake (see https://github.com/golang/protobuf/issues/183#issuecomment-353693510)

Hello @dsnet @tectiv3.  Maybe we can make this as a non-breaking change, --tagstyle or option go_tagstyle="normal"?


Mining system

Jira-Issue GER-14

Adding mining to the develop branch
Does not yet include handling alternative ground tiles for navigation.
I'd like to do those after the enemies and the mining system are both merged here

Don't forget:
Squash and merge


Accept new Phragmén solutions if they are epsilon better + Better pre-inclusion checks.

Closes https://github.com/paritytech/substrate/issues/6106

[x] Part1: Only accept solutions that are epsilon better. See the new EpsilonOrd trait tests and tests for is_solution_better for more detail. I also swapped the order of operands of this function to make it better.

[x] Fix pre_dispatch as explained here.

Ready for review. The second fix that this PR makes is pretty much untestable in our environment. Questions and critiques are welcome.

companion needed? @kianenigma

Here's more data.
https://gist.github.com/kianenigma/5b69005b326469c67bad2ddb35e643c1
Here we can also see how much (by percent) each solution score is improved or decreased. I was initially going to chose 0.1%, i.e. 1/1000 for the improvement factor. But for now, I will relax it a bit to the half of this value: 0.05%, 5/10_000.
Consequently, I will improve the iteration count to 10, giving validators more chance to run a large number of iterations and come up with better score.
Companion to be followed soon.


remove @types/ioredis from package.json

I think there is no need for @types/ioredis
ioredis contains build in typescript declerations
@types/ioredis is used with version 4.28.10
ioredis is used with version 5.2.3
This cause an error on my project when i want to do something like this:
import type Redis from 'ioredis';
import { Redisearch } from 'redis-modules-sdk';

class RedisAdapter {
  public client!: Redis;
  public search!: Redisearch;

  public async init() {
    this.search = new Redisearch({
      ...
    });
    await this.search.connect();
    this.client = this.search.redis; // type error
  }
}

export const redis = new RedisAdapter();

@JustGreg Can you share the error you have please?

@danitseitlin thank you for the fast response!
here is the type error:
src/adapters/redis.ts(18,5): error TS2322: Type 'import("/builds/projectname/node_modules/redis-modules-sdk/node_modules/ioredis/built/Redis").default' is not assignable to type 'import("/builds/projectname/node_modules/ioredis/built/Redis").default'.
  Types of property 'options' are incompatible.
    Type 'import("/builds/projectname/node_modules/redis-modules-sdk/node_modules/ioredis/built/redis/RedisOptions").RedisOptions' is not assignable to type 'import("/builds/projectname/node_modules/ioredis/built/redis/RedisOptions").RedisOptions'.
      Type 'RedisOptions' is not assignable to type 'CommonRedisOptions'.
        Types of property 'Connector' are incompatible.
          Type 'import("/builds/projectname/node_modules/redis-modules-sdk/node_modules/ioredis/built/connectors/ConnectorConstructor").default | undefined' is not assignable to type 'import("/builds/projectname/node_modules/ioredis/built/connectors/ConnectorConstructor").default | undefined'.
            Type 'import("/builds/projectname/node_modules/redis-modules-sdk/node_modules/ioredis/built/connectors/ConnectorConstructor").default' is not assignable to type 'import("/builds/projectname/node_modules/ioredis/built/connectors/ConnectorConstructor").default'.
              Type 'import("/builds/projectname/node_modules/redis-modules-sdk/node_modules/ioredis/built/connectors/AbstractConnector").default' is not assignable to type 'import("/builds/projectname/node_modules/ioredis/built/connectors/AbstractConnector").default'.
                Property 'connecting' is protected but type 'AbstractConnector' is not a class derived from 'AbstractConnector'.

I added @types/ioredis (v. 4.28.10) to my project and the error disappeared.
Now i removed @types/ioredis again and the error didn't show up again. ¯_(ツ)_/¯

So I took the code you shared and started testing and I couldn't reproduce the issue.
I am using dependencies: {
"ioredis": "5.2.3",
"redis-modules-sdk": "1.3.4",
"typescript": "4.2.3"
}
I ran tsc on the file and it doesn't seem to throw the error you are talking about.
Can you share what version of TS + redis-modules-sdk you're using?

I'm sorry, i can't reproduce this issue either.
I think you can close this issue?

@JustGreg All good! happy we looked into it anyways :)
If you have any questions, feel free to open issues and discussions.
Happy weekend ✌🏼


Terraform: unexpected Content-Type

problem starting stratus-red-team
2022/05/23 00:39:19 Checking your authentication against AWS
2022/05/23 00:39:20 Installing Terraform in /root/.stratus-red-team/terraform
2022/05/23 00:39:20 error installing Terraform: unexpected Content-Type: "application/vnd+hashicorp.releases-api.v0+json"

Hello!
Thanks for reporting, I confirm I'm experiencing the same issue on a fresh install. I'm investigating.

Seeing similar reports in https://discuss.hashicorp.com/t/cannot-run-terraform-provider-tests-unexpected-content-type-application-vnd-hashicorp-releases-api-v0-json/39643
Appears to be caused by https://github.com/hashicorp/hc-install/issues/56, fixed in v0.3.2. See #119 for upcoming fix in Stratus Red Team (will be released as part of v1.7.1

Thanks brother!!!


Cannot handle 429 responses

There has been a 429 response received from Husqvarna due to too many requests received.
Their documentation says one request per second, so most likely it was the auth->get mowers calls that caused the issue.
The automower services will need to handle 429 responses to perform an automatic delay + retry to make another attempt to perform the action needed.
Expected Behavior

The client is able to do the action against the api

Actual Behavior

The client received a 429 response and handles it similarly to a 500 generic error response.

Decided to make the fetch client handle 429s so the entire plug-in gets support for free.
Also added jittering support so the delay isn’t the exact same time when all the requests hit again.


67 mat-select has wrong label and underline color issue is fixed

Fixes #67  .

Changes proposed in this Pull Request:

updated the accent and warn palette to fixed this issue

Screenshots / Screen Recording (if applicable)

To Test:

yarn test

Any specific feedback you are looking for?

light theme and dark theme, outline select, warn variant: whether something is selected or not, the outline should be red. Right now it is unchanged. -FIXED

dark theme, fill select, warn and required variant: the background color is incorrect. - FIXED

@huayunh The background color for mat select text fields is changed to the correct color format as per your mention. The disabled text field is 50% transparent. see the image below
@daileytj @JeffGreiner-eaton Kindly review the angular code

screenshot looks good


Add Firejail configuration for new directories in $PATH

#115 and #114 introduced new directories in $PATH.
Please change the Firejail config to make those read-only.

Closed by #132.


Codesign error during the creation of the package release distributable on macOs BigSur

Describe the bug
Run the packageReleaseDistributionForCurrentOS command on macOs the build failed with the error:

Error in the console:

Command: [/usr/bin/codesign, -vvvv, --remove-signature, /compose/tmp/sign/libsodium.dylib]

Error in the log file created:

/Library/Developer/CommandLineTools/usr/bin/codesign_allocate: fatal error: file not in an order that can be processed (function
starts data out of place): /Users/user/IdeaProjects/appname/build/compose/tmp/sign/libsodium.dylib

/Users/user/IdeaProjects/appname/build/compose/tmp/sign/libsodium.dylib: the codesign_allocate helper tool cannot be found or > used

Affected platforms
Select one of the platforms below:

Desktop

Versions

Kotlin version: 1.8.0
Compose Multiplatform version: 1.4.2
OS version(s): macOs BigSur
OS architecture: x86
JDK (for desktop issues): 18

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

Download before the main library here
Then publish to maven local in your machine
After you need to install the desktop version
Run the packageReleaseDistributionForCurrentOS command
See error in the console

Expected behavior
After run that command should be created the package in the .pkg format for the release distributable

Judging by
the codesign_allocate helper tool cannot be found or > used

Can you type codesign_allocate in your terminal and ensure that it's installed (should be shipped with Xcode)?

Hi, sorry for the delay for the reply, I tried to execute the command you suggest and this is the response:
user@xxx ~ % codesign_allocate
Usage: /Library/Developer/CommandLineTools/usr/bin/codesign_allocate -i input [[-a <arch> <size>]... [-A <cputype>
<cpusubtype> <size>]... | -r] [-p] -o output

so I don't now if is effectively intalled, have you some tips about?
Thanks for the help anyway

It's installed, but the Gradle task can't resolve it for some reason, we'll investigate that.

Yes, thanks you for the help!

I couldn't reproduce it.
BUILD SUCCESSFUL in 1m 47s
9 actionable tasks: 9 executed
14:54:50: Execution finished 'packageReleaseDistributionForCurrentOS'.

It seems like there is some problem with your environment.

Did you run It on a macOs enviroment? Because in the other works correctly

Please, add this to build.gradle.kts in your desktop sources:
tasks.all {
    if (name == "packageReleaseDistributionForCurrentOS") {
        doFirst {
            println("Current PATH: " + System.getenv("PATH"))
        }
    }
}

Then check that your resolved PATH contains folder where codesign_allocate resides.
You can look up this folder using locate codesign_allocate.

Thank you, I try right now

Sorry I cannot execute the task, where I need to place that snippet?

In the end of your build.gradle.kts in Pandoro-Desktop.

Okay thanks

Maybe I wrong, but the task is not executed the gradle make only the task of the main task

I can executing the tesk, the result is:
Current PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

The result instead of the locate codesign_allocate is:
/usr/bin/codesign_allocate
/usr/libexec/DeveloperTools/codesign_allocate```

Do I have to change the project path?

No, there is /usr/bin in your PATH, and that's where codesign_allocate is contained. I have no idea why you are getting the message about missing executable.

Okay understood, sorry for the request but are days that I try to figure out with this.
Again thank you for the help

Hi, any updates about?

Sorry I really need build version also for MacOS and that problem is still occurs, what  I need to do to build correctly?


Add 4D language in Readme

Hello,
The repository https://github.com/highlightjs/highlightjs-4d has been recently added in the organization.
The PR adds a ref to this repository in the Readme.

@gkotulski Thanks for much for your contribution!


Update CSS token per new design system theming capability

Alaska Airlines Pull Request
Fixes: #47
Summary:

Update the design tokens to reflect the new theming conventions regarding tokens from the AuroDesignTokens and JetstreamDesignTokens repo.

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Hi @jason-capsule42 or @blackfalcon.
I'm not sure how to fix this npm ci error for node 11 in this pipeline error.
Please advise.
FYI some references:
https://stackoverflow.com/questions/9768444/possible-eventemitter-memory-leak-detected

I have pushed some more changes per feedback above.

Closing this PR as the work was handled in a different PR:

https://github.com/AlaskaAirlines/auro-card/pull/52


FontAwesome Glyphs Show Up As "Question Mark box".

I built from source.
1,000 words...

Hey @mralexgray
Sorry about that.  I'm planning on releasing a new version that won't use Font Awesome glyphs soon.
I would suggest using the official release until then.


Does not detect any dependencies in typescript project

Hey,
I just tried out the plugin and: it doesnt work :D
The dependencies table shows up in the docs but its always empty. I guess its due to the setup I made to make docs work with typescript.
const path = require("path");

module.exports = {
    addons: [
        "@storybook/addon-actions",
        "@storybook/addon-links",
        "@storybook/addon-viewport",
        "@storybook/addon-knobs",
        {
            name: "@storybook/addon-docs",
            options: {
                configureJSX: true,
                babelOptions: {}
            }
        }
    ],
    presets: ["@storybook/preset-typescript", "storybook-addon-deps/preset"],
    stories: ["../app/**/*.stories.(tsx|mdx)"],
    webpackFinal: async config => {

        config.module.rules.push({
            test: /\.(ts|tsx)$/,
            loader: require.resolve("babel-loader"),
            include: path.resolve(__dirname, "../app"),
            options: {
                presets: [["react-app", {flow: false, typescript: true}]]
            }
        });

        config.module.rules.push({
            test: /\.scss$/,
            include: path.resolve(__dirname, "../app"),
            loaders: ["style-loader", "css-loader", "sass-loader"]
        });

        config.module.rules.push({
            test: /\.tsx?$/,
            include: path.resolve(__dirname, "../app"),
            use: [require.resolve("ts-loader"), require.resolve("react-docgen-typescript-loader")]
        });

        config.resolve.alias["app"] = path.join(__dirname, "../app");

        config.resolve.extensions.push(".ts", ".tsx");
        return config;
    }
};
`

Thanks very much for the report. Typescript is not the problem as i am using it myself mostly on ts projects.
So you see the prop tables for the component in docs? Do you have a repo i can try to find the issue?

Hi @Paratron - any updates?

Hey, not right now. We are using this for a company project and the sources are hosted on an internal gitlab instance.
I will try and set up a repo on github with an reproducable example in the next days when there is some spare time left :)


Upgrade @material/* form related dependencies version to 0.42.0

Requirements
Dependencies to update:

@material/form-field
@material/checkbox
@material/textfield
@material/line-ripple

@material/line-ripple has no 0.42.0 version released yet, latest stable 0.41.0


Truffle Dashboard Blank White Page

Hello,
I duplicated my deploy folder to keep a backup copy of my project, I then went ahead and followed the same steps I did on the original fully functional folder. This includes running sudo -s and npm install truffle -g in the new duplicate terminal. yes, I know this is not how it is suggested to be done, this is however how I did it the first time and its the only way I could get it truffle to install.
Now the issue is no matter what folder I run truffle dashboard in, I get a blank white truffle dashboard at http://localhost:24012/. There is no longer a connect Wallet option. I deleted the duplicate folder and started a new nft-erc721-collection-main zip folder, the same exact issue appears here too.
Thanks,

Hi @granthughes1999, Truffle Dashboard is a stand-alone tool so it's not related to our project in any way (you can also run it from any folder and it's gonna work exactly the same.
I suggest you reporting this issue to the Truffle team on GitHub. Unfortunately I'm on mobile now so I can't send you the link, but you can find it pretty easily.
Thank you, I hope you will be able to solve this soon. I'm also gonna publish 3 videos early next week about how to setup any operating system with all the basic requirements. You will find these on my YouTube channel (Liarco DevTips).

Thanks @liarco,
This lead me to the truffle GitHub, where I noticed they just released truffle v5.5.4.
My solution was to simply do the following

npm uninstall -g truffle
npm install -g<EMAIL_ADDRESS>

Oh, that's good to know. Thank you very much!


How do we Identify Accepted Organizations?

Hi, I am an aspiring GSoD'21 intern.
I have gone through the list of Interested organizations and saw a few that I would really love to work with.
However, after reaching out to them, I get a response that they were not accepted for this year's GSoD. I've gotten that same response from 2 organizations I reached out to, and a friend got the same response from another organization.
I previously thought organizations on this list were accepted organizations, but apparently they aren't. How do we identify organizations that were accepted for this year's GSoD?

+1 on this too

Hi folks! You can see the accepted orgs for 2021 on the official Season of Docs site
I'll update the repo to add this link! Thanks for pointing this out!

Hi @mohzulfikar.
I eventually found it here.
Although I might have missed it, I don't think the link visible anywhere(GitHub or GSoCs website) even though I checked severally. On the website, it is on the "results" tab. That was a bit misleading as the name does not give context to the information it contains IMHO. Perhaps it could be updated somewhere where it's more visible?

Cool, thanks for the info @emckean @gabrielapivetta


Link conversion from v3 -> v4

Middleware to convert V3 links to V4

We still need to handle /slowzones

Middleware doesn't seem to be working in beta right now: https://dashboard-v4-beta.labs.transitmatters.org/rapidtransit?config=Blue,70051,70039,2023-06-12,
It just seems to drop you on the 404 page

But it works locally right? Did we ever test in beta?

Yep works locally, so this may not work in static bundles

Whoops 😔

Also doesn't include redirects and headers. Is there any way to fix this without those...?

Yeah. I'll have to take a look at this again. We may have to manually handle this by making routes and using browser redirects


Infinite loop on play

I'm trying to use one mouse with 2 HID-compatible devices (that only give Mouse X and Mouse Y values). The demo scene gets stuck when trying to start playmode. Probably an infinite loop somewhere as Unity hangs completely.
I'm using latest 2021.3 LTS.

I just released a new version of this package, the issues you've encountered should be fixed with this release!
https://github.com/jackyyang09/Multi-Mouse-Unity/releases/tag/v0.0.2-alpha

I just released a new version of this package, the issues you've encountered should be fixed with this release!
https://github.com/jackyyang09/Multi-Mouse-Unity/releases/tag/v0.0.2-alpha

I will test it when I get home. Btw, any possibility to get the source of the MultiMouseLib.dll to compile it for MacOS and Linux?

I haven't been able to get in contact with the creator of the .dll for several months now, so I can't give you an answer to that. I don't have access to the source code either.

I encountered a problem: when running the Lightgun01 scene, using only one mouse (the computer is only connected to one mouse) to click on the game screen, Unity exits.
Unity uses version 2021.3 or higher


Does not support "explicit" in C++

str = 'class B {\n' +
     '  public:\n' +
     '    explicit B(const A& a) : a_{a} {}\n' +
     '};\n' +
     '\n'
hljs =require("highlight.js");
console.log(hljs.highlight("c++", str))

prints
{
  illegal: true,
  relevance: 0,
  value: 'class B {\n  public:\n    explicit B(const A&amp; a) : a_{a} {}\n};\n\n'
}

but it works after removing "explicit".

Thanks for reporting this.  Currently this is known issue.
Closing as a duplicate of https://github.com/highlightjs/highlight.js/issues/1980.

I have a fix for this laying around but its' mixed in with a bunch of other stuff and hasn't been a priority yet.


Farming location bug

There's no farming location listed for the Caster, Assassin and Berserker Pieces. Not sure if it's an issue with the Atlas Academy spreadsheet or what, but figured I should report it.

Thanks for the report! Yeah, weirdly the drop rate is missing from these three entries, so the script I wrote to import this data skipped over those rows. This should be now fixed.


Simplify call hierarchy of createWorker in TachyonWorker

Currently, the TachyonConf is not updated when creating worker.
this change makes Tachyon always create worker through createWorker(TachyonConf conf) API.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2862/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2871/
Test PASSed.

@calvinjia I have modified the code according to your comments

@calvinjia
I have made the change according to your comments.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2879/
Test PASSed.

+1 LGTM

Thanks. Did a followup commit on this: https://github.com/amplab/tachyon/commit/773bbc1b92ce257fecf155f95c2e477c1b60c784 ;


CLI ?

Running using npm script would be very convenient

It will be nice to have.

I'm not sure how to implement it ...
I can think of two ways:

To add code to index.ts inspect process.argv searching parameters ...
To add new module, ie: cli.ts that import and use bundle function from index.ts...

@basarat can you tell me about?
I not sure how to determine if a module is running directly with nodejs or included from other ...

I not sure how to determine if a module is running directly with nodejs or included from other

With examples :
Developer (you)

To allow running as a node script a module provides bin in package.json : https://github.com/alm-tools/alm/blob/master/package.json#L7 pointing to a js file which can then safely assume that it is being run as an executable.

Ideally the script should have shebang : #! /usr/bin/env node https://github.com/alm-tools/alm/blob/master/bin/alm

User

To use such a file they can either do npm install -g alm. This gives them the executables from the package.json bin on the user system command line
They can install it as a dev dependency and use scripts option in package.json to drive it e.g. :

"scripts": {
    "build": "alm -p ./src"
},

:rose:

Done.


Release 1.9.2

We forgot to backport some fixes for 1.9.x, so we need a new release

To be merged -> https://github.com/apache/camel-k/pull/3277

#3277 has been merged. I'll start a new release today.

Is there something more to add to release-1.9.x before releasing?

Starting the release process.

Hi @oscerd any chance we can get https://github.com/apache/camel-k/pull/3278 in ?

Merged on main, please backport, I'm still doing the preliminary steps to release.

@oscerd Can we close this?


fix: Removed FirebaseFirestoreSwift from umbrella framework for FlutterFire & React Native Firebase projects

closes https://github.com/invertase/firestore-ios-sdk-frameworks/issues/62

Let me know if this works for RNFB, @mikehardy (I thought this was an issue on RNFB but can't seem to find it now. I can remove the if condition for RNFB although I would think it's not needed anyway and it is being built for nothing). It works for FlutterFire.
Use:
pod 'FirebaseFirestore', :git => 'https://github.com/invertase/firestore-ios-sdk-frameworks.git', :branch => "@russell/ios-10"

in your Podfile if you want to test 😄

@russellwheatley
It stuck in this with pod install for me. Any clues?
Pre-downloading: `FirebaseFirestore` from `https://github.com/invertase/firestore-ios-sdk-frameworks.git`, branch `@russell/ios-10`

I will test later this morning, rnfb does use this sometimes it is just not logged as I'm tracking personally and using the FF issue as a proxy
To make sure I understand, zip and pod may interoperate with this shared swift pod in between, but only if it comes in via cocoapods, not as a zip component? Same as leveldb it seems and will inform how to handle any future shared stuff if it's in a new component

@leehack show me your Podfile, please?

# Override Firebase SDK Version
$FirebaseSDKVersion = '10.0.0'
# Uncomment this line to define a global platform for your project
platform :ios, '13'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  pod 'FirebaseFirestore', :git => 'https://github.com/invertase/firestore-ios-sdk-frameworks.git', :branch => "@russell/ios-10"
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      # Using the un-qualified names means you can swap in different implementations, for example ccache
      # https://reactnative.dev/docs/0.69/build-speed#xcode-specific-setup
      config.build_settings["CC"] = "clang"
      config.build_settings["LD"] = "clang"
      config.build_settings["CXX"] = "clang++"
      config.build_settings["LDPLUSPLUS"] = "clang++"
      # config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
    end
    flutter_additional_ios_build_settings(target)
  end
end

To make sure I understand, zip and pod may interoperate with this shared swift pod in between, but only if it comes in via cocoapods, not as a zip component? Same as leveldb it seems and will inform how to handle any future shared stuff if it's in a new component.

FirebaseFirestoreSwift has a dependency on FirebaseSharedSwift. We don't need FirebaseFirestoreSwift with our FF project because it is an obj-c project. We only need FirebaseFirestore framework.
I don't believe a zipped + compiled dependency like FirebaseFirestoreSwift which has a dependency on FirebaseFirestoreSwift will work if there is another dependency which has a sub-dependency for FirebaseSharedSwift coming from Cocoapods. I don't think they are interoperable to answer your question.

@leehack  hmmm, not sure based on your Podfile. Have you fully cleaned your project?

@leehack might be worth building in xcode as well, you will likely get better logging to debug.

@russellwheatley Sure. Let me try it.
Just for your info, it doesn't stick with 10.0.0.

@russellwheatley wait. I can't build from xcode anyway without pod install no?

Send me your podspec as well. I'll see if I can build

@russellwheatley I meant the pre-download part works with:
pod 'FirebaseFirestore', :git => 'https://github.com/invertase/firestore-ios-sdk-frameworks.git', :tag => "10.0.0"

➜  ios git:(main) ✗ pod install --verbose
  Preparing

Analyzing dependencies

Inspecting targets to integrate
  Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

Fetching external sources
-> Pre-downloading: `FirebaseFirestore` from `https://github.com/invertase/firestore-ios-sdk-frameworks.git`, branch `@russell/ios-10`
  $ /usr/bin/git ls-remote -- https://github.com/invertase/firestore-ios-sdk-frameworks.git @russell/ios-10
  7b936d57d4ae0c04d05c2096892927dc326a2c0c	refs/heads/@russell/ios-10
 > Git download
 > Git download
     $ /usr/bin/git clone https://github.com/invertase/firestore-ios-sdk-frameworks.git
     /var/folders/b8/__12f73541qdmx847t78zk680000gp/T/d20221026-37065-kam5m5 --template=
     Cloning into '/var/folders/b8/__12f73541qdmx847t78zk680000gp/T/d20221026-37065-kam5m5'...

Send me your podspec as well. I'll see if I can build

Let me prepare a clean project for this.

@russellwheatley
name: test_ff
description: A new Flutter project.

publish_to: 'none' # Remove this line if you wish to publish to pub.dev

version: 1.0.0+1

environment:
  sdk: '>=2.18.2 <3.0.0'

dependencies:
  flutter:
    sdk: flutter
  firebase_core: ^2.0.0
  cloud_firestore: ^4.0.1
  cloud_functions: ^4.0.1

  cupertino_icons: ^1.0.2

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^2.0.0

flutter:
  uses-material-design: true

Not sure why but no matter the dependency I have, It just can't download the precompiled SDK from the branch.

@russellwheatley
-> Pre-downloading: `FirebaseFirestore` from `https://github.com/invertase/firestore-ios-sdk-frameworks.git`, tag `10.0.0`
 > Git download
 > Git download
     $ /usr/bin/git clone https://github.com/invertase/firestore-ios-sdk-frameworks.git
     /var/folders/b8/__12f73541qdmx847t78zk680000gp/T/d20221026-41430-4rscaw --template= --single-branch --depth 1 --branch 10.0.0
     Cloning into '/var/folders/b8/__12f73541qdmx847t78zk680000gp/T/d20221026-41430-4rscaw'...
     Note: switching to '74360c9d2a3197257646c78cb4a6c277e9263d66'.

     You are in 'detached HEAD' state. You can look around, make experimental
     changes and commit them, and you can discard any commits you make in this
     state without impacting any branches by switching back to a branch.

     If you want to create a new branch to retain commits you create, you may
     do so (now or later) by using -c with the switch command. Example:

       git switch -c <new-branch-name>

     Or undo this operation with:

       git switch -

     Turn off this advice by setting config variable advice.detachedHead to false

     Updating files: 100% (3558/3558), done.

I tried pod cache clean and install with the 10.0.0 tag. I see a difference in that it has --single-branch --depth 1 for the clone.
It's obviously not an issue from your PR. I suspect it was just taking a lot of time to download the whole repository.

@russellwheatley
https://andresalla.com/en/stop-using-branch-in-your-podfiles/

did it work using :tag =>?

@russellwheatley @russel/ios-10 is not a tag, so I can't do it. I don't know how long it will take but let me try to wait while I'm doing something else ;)
I don't know what the tagging policy is in this repository, but if you could push a tag, that would help people try it out.

@leehack The article you shared says you can use tag instead of branch and it will get the branch? Hence my question. Not pushing a tag until the next iOS SDK update. This is a temporary measure, it won't get merged (and subsequently tagged) until we're sure it's a solution. I'm awaiting feedback from users. Thus far, you're the only one not able to pod install.

@russellwheatley Finally, the download is complete. It took around 20min ;) I also confirm the tag works. No need to push a tag.

I also confirm that the ios build worked as well for my flutter project.


store lpnft

If we detected a new asset but could not get its metadata from grpc, we store the generated metadata using the bech32 string prefixed with passet  as base denom
https://github.com/penumbra-zone/web/blob/288ac1d180a8b815e50716258dc5385a8707cfa7/packages/query/src/block-processor/index.ts#L122
But at the same time, it will cause a serialization error if we try to pass generated asset to wasm
https://github.com/penumbra-zone/penumbra/blob/f08d72db8d8aa22dbd8bdd4b371a9ba983897646/crates/core/asset/src/asset/denom_metadata.rs#L91
Error:   denom metadata has mismatched penumbra asset ID

If we send an Open LP position transaction, we get this scanning error script

Detected new notes with unknown asset
Grpc query denomMetadata() did not return asset information
We stored the generated DenomMetadata for the asset in indexed-db
We also found our transaction in block, and tried to get TransactionInfo for it via wasm
Wasm while executing transactionInfo() read our asset from indexed-db but failed to serialize it and threw error denom metadata has mismatched penumbra asset ID

It seems that the issue denom metadata has mismatched penumbra asset ID is related to the fact that in extension we get TransactionInfo once during synchronization, while in rust view service TransactionInfo is generated every time a transaction retrieval request is executed

A simple solution is that we should store LPNFT before calling transactionInfo()


How to control a 'Coupled' point by calling program？

I want to control a certain point on the line and  it can move according to my calling program/script. But I only know the 'Coupled' point, which can be controlled by calling program, but I don't know how to implement it. There is no clear explanation in the documentation. Do I need to make modifications in the source program? Which source program can be modified to achieve control over  the 'Coupled' point ?thank you

I assume you are considering the version 2.
You can take a look to the tests. e.g. https://github.com/FloatingArrayDesign/MoorDyn/blob/v2/tests/quasi_static_chain.cpp#L201
As you can see, no need to change a single line of the source code. When you call MoorDyn_Step() you are meant to pass the positions and velocities of all the coupled entities.
In your case you just need to pass a 3 components array x with the position of the point and another 3 components array xd with the velocity of the point.

Hello, I would like to use Moordyn for my project and may need to make some changes to its source code. It is a real-time hybrid test of the mooring system, which requires Moordyn to be made into a numerical substructure and an experimental substructure. The mooring line needs to be cut off from the middle, with a portion of the upper mooring line retained, and specific displacement or force applied at the cutoff point to simulate the true dynamic response of the mooring line in an unbroken mooring. The problem I am facing now is that I don't know how to apply displacement or force in real-time at the cutoff point, or how to control the endpoint of the mooring line in real-time through external programs such as MATLAB. I hope you can give me some suggestions or tell me where to modify the source code? The following is a schematic diagram of my project.thanks


NameError: name 'activation_visualization' is not defined

After successful installation of tf_cnnvis, I was able to import tf_cnnvis but running example 1 using python 3 in jupyter notebook throws the following error:
NameError: name 'activation_visualization' is not defined
I have followed the same steps as given in readMe file. Is there anything that needs to be done after installation to be able to use activation and deactivation functions?

Thanks, @falaktheoptimist for the response. I have 2 python versions but I executed setup.py file using python 3 which is why I am able to import tf_cnnvis module. Since my Jupyter notebook kernel is also using python3 and I am still not able to use inbuilt functions, I am not able to figure out the issue.
Any suggestion will be helpful.

If you were able to run the command from tf_cnnvis import * without any error and are still getting the error saying activation_visualization is not defined, then I'm not sure what could be the error here. Please post the error log here - maybe that would help with the debugging


General bot usage instructions

Added a little instruction.

Sweet! I'm gonna merge it, and add some examples below


Fix Ray worker start for static cluster

Current dependencies on/for this PR:

main

PR #337   👈

This stack of pull requests is managed by Graphite.


Change 'enum' to 'enum class' in src/archive/ai.hpp

Change 'enum Directions' to 'enum class Directions' in src/archive/ai.hpp.
After continue with more.

Hi @Chris99999, thanks for the PR! :smile_cat:
I like this PR to use more clearer defined enums! I agree that it's important to use this style wherever you can. :mag:
However, the file you worked on, ai.hpp, is "archival". It is currently dormant in the code repo as the AI portion of the 2048.cpp is on pause. The file would most likely to be deleted soon.
Unfortunately because of this, I cannot accept the PR to the codebase, however feel free to submit Issues or PRs with the active part of the codebase.
Thanks again and sorry for the confusion. :cat2:


Reinitialize after ajax page load

Basically Ive built an ajax driven site. When you click a nav link its rel value will load that page and grab its content using jquerys contents function as follows
    namespace.ajax.done(function(msg) {
       var lll = $(msg).find("#containment");
       var dd = lll.contents();
            $("#containment").html(dd);
    }),

I am using modernizer to load page specific script for each page and in the script for the homepage i have slick initialized as so
$('.social-wall-masonry').slick({
dots: false,
infinite: true,
slidesToShow: 5,
autoplay: true,
});
this works fine when you manually refresh but when the page contents are pulled in it cant find the element '.social-wall-masonry' and initialize the slick for that page.... is there any kind of way to get the dynamic js file to execute the slick slider everytime or to find that dynamic element ?

Hey @padjodev I think you'll want to reinit the slick on the ajax callback or remove/add slides.
I'm going to close this because it's a support request and not a bug
Hope that helps


Navigation bar in .d.ts file ignores interfaces when cursor is outside the interface

For the following code:
declare namespace M {
    // cursor here
    interface I {

        prop;
    }

    var v;
}

One would expect the middle nav bar to show M, and the right nav bar to show I. But the right nav bar shows v. Effectively, it skips interfaces and shows the upcoming var instead.
The middle nav bar does show I when the cursor is inside I, as expected.

I don't think that's a bug... the problem is that I is not shown in the nav bar at all, when the cursor is above the declaration.

But a var is shown when the cursor is above the declaration. So why not an interface?

@JsonFreeman that's what I said..

Now, now, everybody can be right. :trophy:

Oh I think I got confused when you said "I don't think that's a bug", instead of "the bug" (using the indefinite article).

this looks fixed now.


[WIP] Revert v1.x

unix-cpu/gpu are failing on v1.x. This pr checks if https://github.com/apache/incubator-mxnet/commit/031dc5b7c2b7f5c1cb61d0193b048c0d77abb9d8 is the cause

@Zha0q1 unix-gpu job has been failing in my PR #19799 before #19670 was merged.

@szha Thanks for the info! @waytrue17 is creating an issue and the current oncall will look into this

Closing pr for now since we confirmed the ci issue was not caused by that pr

@Zha0q1 unix-gpu job has been failing in my PR #19799 before #19670 was merged.

@szha I looked at your PR and our log of the v1.x branch. After the PR #19670 there is only one PR merged(#19837) and its CPU unittests passed 4 days ago. Your PR passed its first 13 days ago and then remaining 3 re-runs started 2 days ago. I am currently running unix_CPU CI w/ and W/o #19670 to verify. Will update shortly

@Zha0q1 unix-gpu job has been failing in my PR #19799 before #19670 was merged.

@szha I looked at your PR and our commit log of the v1.x branch. After the PR #19670 there is only one PR merged(#19837) and its CPU unittests passed 4 days ago. Your PR passed its first 13 days ago and then remaining 3 re-runs started 2 days ago. I am currently running unix_CPU CI w/ and W/o #19670 to verify. Will update shortly

I think Sheng was right that #19670 was not the cause of the ci issue. In this PR even after reverting #19670 the failure still happened. @josephevans opened a pr https://github.com/apache/incubator-mxnet/pull/19872 to attempt to fix the issue

ok ... i will stop then. Since you already verified that reverting the PR doesn't fix the issue.


[v2 App] Link player and global records to the period they were achieved

Closes #843

btw we now get preview links for frontend changes (with v2) which is really nice, a few notes:

I think the whole "box" should become a link, instead of just the "gained value", and have some sort of hover style, maybe just hover:bg-gray-800 is enough tbh
you could also add these links to the global record leaderboards, those currently redirect to /players/:username/records

Player records: made the whole box clickable
Global records: Just corrected the link to go to the correct gained time frame. If we want to make the whole box clickable here, we need to make some more changes than just correcting the link because it's a table. If I'm not mistaken.

Also made the link open the correct metric.


Add PUT method to exported list

I don't  understand why the commit-message-check failed, my message is less than 72 chars :/

Oh nice catch!

The issue was that the commit message didn't match the format defined https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md#git-commit-guidelines
I modified the commit message to match, thanks!

They are very uncommon, and you can always access them as hyper::Method::Patch etc.


Support json?

I have an OpenAPI v3 spec as json. Are you planning on supporting json files?

Thank you for your feedback.
I currently don't have any plans, but I'll keep it in mind for future updates.


RSA SigVer

I wanted to flag this before it becomes an issue. RSA supports multiple revisions of the FIPS-186. At the moment libacvp seems to default to "1.0" within the "Revision" tag. This seems to work okay for now and returns FIPS 186-4 vectors. The documentation posted here:
https://usnistgov.github.io/ACVP/draft-celi-acvp-rsa.html#FIPS186-2
Section 5 indicates that "1.0" should not be used within the "Revision" tag for SigVer. With FIPS 186-5 about to be final then the "Revision" tag could become quite critical with your implementation.
Thanks!

Thank you for the heads up! I will be looking into this (and am making sure we better track features we don't currently support in general).
Thanks,
Andrew

Yeah FWIW this will be a (small) breaking change to clients as we're renaming a few RSA related algo/mode/revisions to better reflect the FIPS document they come from.  With FIPS186-5 coming shortly, it seems to make sense to be more explicit, rather than "1.0" which could mean 186-4 or 186-2 depending on the algo/mode, we'll be eliminating the 1.0 revision and going with the standard name instead.
https://github.com/usnistgov/ACVP/issues/990 related

Thank you @Kritner for the information. Might you have an ETA or a ballpark for when this change will be live on servers?
Thanks,
Andrew

FYI the current plan is to get this changed rolled out to demo today
https://github.com/usnistgov/ACVP/issues/990#issuecomment-690396982

This change is now deployed to our demo environment

Libacvp is now updated to reference FIPS186-4 instead of 1.0 for RSA.


QEMU based cross compiled testing

With a little set up, Debian provides an ability to use QEMU to execute programs compiled for other architectures.  Using this, most of our cross compilation CI builds can be executed.
This PR does this.

[ ] documentation is added or updated
[x] tests are added or updated

These take too long to execute on every pull request.  However, the builds are useful in finding compatibility problems.
My proposal is to run the compiles on PRs and the tests via QEMU on pushes.
The yml file will need an update to support this but for testing it needs to run on PRs.

Great work @paulidale !
I suppose we will just disable the tests for rare architectures that are currently broken unless the problem is obvious enough to easily fix it as those architectures are not primary target anyway. Someone using them would have to provide help fixing them. In theory it could be also a qemu emulator issue.

I'm still working on the tests.  Some tests consistently don't work across several platforms (test_includes, test_store and test_x509_store), some platforms fail these and more, some platforms just don't seem to work and some pass all tests.
I'm seeing behavioural differences between my local machine and the VMs which is unfortunate and perplexing.

Some tests consistently don't work across several platforms (test_includes, test_store and test_x509_store)

Looks like there might be some 32bit issues in there or something like that. Probably worth investigating the failures.

Great Github CI Fu!

My google-fu was strong today :)
I plan on looking into the issues further -- especially the ones that passed locally but not in actions.

This all looks great and promising! Thanks @paulidale!

@romen, feel free to investigate the three consistent test failures: test_store, test_x509_store, test_includes

Merged, thanks for the review.


PGP-Key 0x4E730A3C expired

Hello,
It seems that GPG key 71AE099B262DC0B493E6EE71975DC25C4E730A3C expired on 2022-07-23. I could not find renewed one.
The actual problem is with Debian repository:
Err:4 http://repo.13-37.org stable InRelease
  The following signatures were invalid: EXPKEYSIG 975DC25C4E730A3C Code Signing Key 13-37.org<EMAIL_ADDRESS>

I am experiencing this as well, just bought one from Crowd Supply and can't add the repo due to expired key.

PGP key expiry has been extended/renewed. Repository should be back up & running again.
Now working on a new release (0.3.3)!


Added scripts to generate OLM metadata

removed integration with make

responded to feedback

Is this something we would want to incorporate into a CI check, e.g. verifying that the generated files are up to date?

responded to feedback

So, the idea is to delete the current dir /manifests and once this gets merged, run it twice for community/product and then check in both dirs? Then RPM's spec should be changed to pick the correct one and install it at /manifests?

Manifests dir can contain multiple versions of metadata, each in it own sub-dir named after the version number. Metadata dir containing all bundles that we want to publish needs to be present in the container image.

Is this something we would want to incorporate into a CI check, e.g. verifying that the generated files are up to date?

Potentially?

Added jira number to the commit message

removed controlplane from the csv template
removed function that was generating controlplane crd from the shell-script

updated wording in the "description" metadata in the csv template

thanks for the reviews, everyone!


Docs: Import/Export references a function with a deprecation warning

In the Import/Export docs page, the very first example uses a deprecated function, as warned by Python linters.
The example in question:
with BuildPart() as box_builder:
    Box(1, 1, 1)
box_builder.part.export_step("box.step")

The warning:
The method "export_stl" in class "Shape" is deprecated
  Use the `export_stl` function instead
Pylance

I'm not sure if the issue is that the example shows the wrong method, or if the deprecation warning shouldn't be there, but it seems there's an issue.

Thanks for pointing it out -- the docs need to be updated.

What is the correct way? I could probably submit a quick PR for this :)

@DeflateAwning here is the correct syntax:
with BuildPart() as box_builder:
    Box(1, 1, 1)
export_step(box_builder.part, "box.step")

A PR is not necessary as I already added it to my draft docfix PR.

Out of curiosity, why is this better? This seems less easy to find, and at the very least, doesn't seem like it needs to have a deprecation associated with the old way

It is deprecated because we are planning to remove it, just trying to give some warning before we do that. The imports have always been functions, so making the exports functions as well offers better consistency. I am sure there are other benefits too.
If you are new to build123d, I highly recommend you go through the examples here which covers some common use cases -- including this one. https://build123d.readthedocs.io/en/latest/introductory_examples.html

In most other similar DSL-like systems (e.g., Polars, Pandas, etc.), the imports are viewed as a constructor-like entry point, and thus are not tied to an object. However, exports are an operation on an object (exporting that object), and thus are a method of that object.
I've done that introductory example. Quite good overall.
I just think this is a very strange choice, and that the reasoning isn't quite there.


Update the README file based on your experience of local installation

Update the README file according to the CONTRIBUTING.md file there should not be any Duplicacy
Include every that's being used in this project to install on locally or updated commands.
Only update the commands that are valid for the installation to setup the project locally.
Include the screenshot in the PR of the changes you made.

Could you please assign me the task of updating the README file based on my experience with local installation? I'll ensure that it aligns with the CONTRIBUTING.md file, remove any duplications, include all relevant installation commands, and add screenshots of the changes."

Hi @Jasmeetkaur-13 it yours. let me know if you need any help.

Hi @Jasmeetkaur-13, what's the update on the issue?

Hey @Jasmeetkaur-13, please update me what's the progress on the issue!
Otherwise I have to unassign you from this issue so that other contributors can work. Hope you understand!

I already updated the readme file
On Sat, Oct 19, 2024 at 4:29 PM Suraj @.***> wrote:

Hey @Jasmeetkaur-13 https://github.com/Jasmeetkaur-13, please update me
what's the progress on the issue!
Otherwise I have to unassign you from this issue so that other
contributors can work. Hope you understand!
—
Reply to this email directly, view it on GitHub
https://github.com/Suraj-kumar00/Flash-Fathom-AI/issues/6#issuecomment-2423760755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCFBXWR5JR6OQPXKLJJL3BDZ4I3PRAVCNFSM6AAAAABP3QLA4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTG43DANZVGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

I already updated the readme file
…
On Sat, Oct 19, 2024 at 4:29 PM Suraj @.> wrote: Hey @Jasmeetkaur-13 https://github.com/Jasmeetkaur-13, please update me what's the progress on the issue! Otherwise I have to unassign you from this issue so that other contributors can work. Hope you understand! — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCFBXWR5JR6OQPXKLJJL3BDZ4I3PRAVCNFSM6AAAAABP3QLA4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTG43DANZVGU . You are receiving this because you were mentioned.Message ID: @.>

where? Why i'm not able to see you PR, have you raise PR?

Hi @Jasmeetkaur-13, are you interested in doing this issue?
Please share what's the status on this issue?
Are you facing any issue?

Already completed
On Sun, Oct 20, 2024 at 4:32 PM Suraj @.***> wrote:

Hi @Jasmeetkaur-13 https://github.com/Jasmeetkaur-13, are you
interested in doing this issue?
Please share what's the status on this issue?
Are you facing any issue?
—
Reply to this email directly, view it on GitHub
https://github.com/Suraj-kumar00/Flash-Fathom-AI/issues/6#issuecomment-2424850035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCFBXWXXJSWWRUZA7TVNDZ3Z4OEVRAVCNFSM6AAAAABP3QLA4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUHA2TAMBTGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @Jasmeetkaur-13, Please tell me what you have completed?
Where is the PR?


decrypt Only decrypts received messages, not the ones the user has sent

Not sure if this is a bug, a limitation, or a design decision. When using identity to decrypt DMs, it only seems to decrypt the received DMs, and not the ones that the user has sent to the conversation.
bitclout.com seems to be storing the sent messages in local storage before they get encrypted, and that's how they're able to be rendered in the conversation.
My gut is telling me this is probably because they get encrypted using the receiving user's public key, and therefore require that user's private key to decrypt, and because the sender doesn't have that private key, they can't be decrypted?
Just wondering if there's anything that can be done about that, or is the only option to cache the unencrypted messages client side before they get sent? This would mean that if the browser storage (or app storage if using a native app) was cleared, those messages would be lost forever to the person who sent them.

Because the sender doesn't have that private key, they can't be decrypted

This is unfortunately correct


Sidebar menu icon of 'about' page need to be replaced by info icon

Currently about menu item has 'bell' icon(which is less fit for about page menu)
It will be better (my opinion) to replace this icon with 'info' icon of antd library (as it with other icons)

I think this issue is a double of #341 and we can close it


Chart Y-axis seems to break when using high decimal values

Hi,
I have an issue with the Y axis decimal display. It works fine on the tooltip but somehow the data gets distorted when building the Y axis. see image for effect: http://s14.postimg.org/45iapoc9d/Snippet.png
Below a export of what i am using to import into the data option. i already tried using  scaleLabel: "<%=value/10%>"  to no effect. Could any of you help me figure this out? Thanks in advance.
PS: Using 2.0
"data":[0.6643,0.45425,0.58569,0.43931,0.42672,0.72525,0.39372,0.22726,0.35708,0.22957,0.27658,0.59887,0.22491,0.4371,0.22125,0.69883,0.27378,0.70195,0.64294,0.57762,0.45721,0.5271,0.23895,0.45011,0.43622,0.72534,0.24624,0.32526,0.24353,0.3964,0.45706,0.47261,0.22154,0.45711,0.60606,0.45845,0.69264,0.68918,0.4317,0.29426,0.44826,0.72271,0.23905,0.29668,0.42264,0.69302,0.7406,0.27639,0.48588,0.45503,0.72872,0.4623,0.32052,0.24283,0.47802,0.45109,0.22341,0.46537,0.73607,0.43248,0.49917,0.48263,0.47537,0.52098,0.41672,0.73156,0.42078,0.22884,0.62218,0.46779,0.48347,0.70743,0.43707,0.45504,0.21793,0.23289,0.48097,0.53957,0.71103,0.41379,0.45274,0.53172,0.46726,0.23946,0.72871,0.2206,0.47352,0.28852,0.48035,0.5625,0.26552,0.45054,0.4192,0.72993,0.4633,0.3659,0.64941,0.26142,0.47383,0.42972,0.47024,0.52879,0.43003,0.31592,0.40757,0.34867,0.7258,0.73346,0.2654,0.65444,0.6308,0.23472,0.45207,0.43381,0.46185,0.45642,0.63917,0.7027,0.2234,0.59185,0.39008,0.74193,0.45739,0.44908,0.75391,0.43176,0.25748,0.46031,0.70905,0.24771,0.47099,0.56469,0.23194,0.45767,0.47352,0.39417,0.5859,0.71971,0.46343,0.21947,0.72772,0.47236,0.73155,0.21694,0.47729,0.34208,0.27404,0.23766,0.22338,0.45881,0.44809,0.56945,0.47258,0.22257,0.24462,0.25271,0.45863,0.49615,0.42728,0.41358,0.68443,0.46783,0.56644,0.46178,0.44063,0.21996,0.45271,0.44224,0.54231,0.21727,0.4837,0.47109,0.72047,0.73005,0.25705,0.46459,0.22361,0.501,0.75282,0.43567,0.23002,0.38745,0.36189,0.70665,0.46768,0.46589,0.76461,0.30276,0.22625,0.46506,0.674,0.4535,0.4679,0.22582,0.4545,0.60796,0.46018,0.3206,0.63213,0.46281,0.25736,0.26347,0.45997,0.30626,0.45205,0.36205,0.62813,0.65838,0.71933,0.41301,0.45547,0.46217,0.57134,0.24078,0.50261,0.22815,0.62243,0.45564,0.3271,0.23269,0.44053,0.22587,0.6175,0.68276,0.43819,0.22337,0.45746,0.47228,0.72468,0.44749,0.24863,0.22048,0.52071,0.43946,0.46735,0.26216,0.61273,0.37493,0.22294,0.43211,0.21706,0.42974,0.38954,0.22345,0.28868,0.23296,0.22827,0.74919,0.4697,0.45573,0.2329,0.4554,0.23405,0.46059,0.4675,0.7158,0.4666,0.55068,0.29338,0.74497,0.65824,0.27568,0.38208,0.45187,0.46051,0.27887,0.62094,0.6765,0.48408,0.4604,0.25018,0.31763,0.67901,0.30625,0.49875,0.44996,0.42073,0.50724,0.60124,0.29013,0.43083,0.45493,0.47959,0.21953,0.51736,0.23795,0.54413,0.44421]`

You can "fix" the number of decimal using the callback function.
Here is the way to do it with 3 digit.
yAxes:[{
ticks:{
callback:function(value){
return Number(value).toFixed(3);
}
}
}],

thanks going to try that...

Can you point where this code should be included?

works now thx for the help.


Added support for mempool messages

Looks good, thanks!

Oh -- can you bump the minor version number in Cargo.toml so that I can update the version on crates.io?

Alright, done!


Plugin or Custom workflow Testing with Easy Repro

Hi There,
Does Easy Repro framework support Plugin or Custom workflow Testing in Dynamics 365.
Thanks in advance.

Hi @TYLEROL and @bwmodular, I have posted same question but related to javaScript.
I have gone through FakeXrmEasy. But, it seems that this is out date tool. Do you recommend any other tool which is currently active such as https://medium.com/capgemini-dynamics-365-team/unit-test-web-api-calls-with-xrm-mock-and-sinonjs-73584504639

Hi There,
I want to check the statuses of all the Duplicate detection rules, Plugins, Workflows etc on post deployment of any solution. I should be able to verify the status of each item and check if it is published and in active state. If there are any processes which are not published or not in active state then throw an error or send out an email saying there are processes which are not published. This is a kind of sanity test need to be done when solution is moved from one environment to another environment.
Please suggest if there are any possibilities to achieve this.

Hi @krishnacs1993, this kind of post deployment smoke test does not need to be done using EasyRepro. You can do this using a plain old integration test using the API to retrive the data you want.
We do this quite a lot, for example we have integration tests running after each release to do things like:
Check that all workflows called 'xxx' are active
Check the right number of message processing steps are registered on an entity
Check the right number of message processing steps are registered for a particular assembly
Check that the Active and Inactive views have the same layout for particular entities
Here's an example - the IorganizationService _service has been instanttiated in the ClassInitialise method and then:
[TestMethod]
        public void CheckCorrectNumberOfMessageProcessingStepsHaveBeenDeployed()
        {
            String fetchCountSteps = @"<fetch aggregate='true' >
            <entity name='sdkmessageprocessingstep' >
             <attribute name='name' aggregate='count' alias='count' />
             <filter>
                  <condition attribute='eventhandlername' operator='begins-with' value='SomethingOrOther.Plugins' />
             </filter>
             </entity>
            </fetch>";

            EntityCollection countMessageProcessingSteps =
                _service.RetrieveMultiple(new FetchExpression(fetchCountSteps));

            Assert.AreEqual(34, ((AliasedValue)countMessageProcessingSteps.Entities[0]["count"]).Value);
        }

Your tests will be much faster and easier to test/debug if you just rely on the API to retrieve the data you want.

Well, that sounds good and this is what I am expecting. Thanks for that @bwmodular.
If possible, can you please share the code for API and some test examples to my email ID<EMAIL_ADDRESS>


Automated Package Upgrade

:tada: This PR is included in version 7.7.110 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Do a first realistic Playright E2E test script

Need to come up with a decent Playright script that exercises some of the basic functionality.

login as data owner
create a new release (manual)
go to the new release
do some select all/none
manually add some people in
change some sharing settings
enable sharing

We also have to start thinking about how we would set up the test data state (test scenarios) for this. There is a very basic mechanism where on entrypoint.ts we can also specify a scenario number. But the whole mechanism needs to be more robust and well though through

are test scenarios independent of each other or does making a test scenario delete all the other data (likely yes)
how can the test scenarios set up users correctly such that we can do demos? (i.e does the test scenario all need to take the email address of the PI for example?)

Everyone will get one of these - so the first one is just a simple scenario going through the start of creating a new release and editing something


Update README.adoc

Thanks Brad!

Changed happen on the development branch, which uses snapshot versions. I 'll fix it there too :)


Any planned updates

I was getting ready to write a plugin very similar to yours at the request of some of my players, and noticed that yours has plans very similar to my own. I also saw in the other open issue that you're working on a new version. What's the status there? Do you need any help getting it updated or reworking it?
Edit: I guess I should have paid attention to the "month" timeline noted in the other comment ;)

This plugin has been updated to work with version 1.20 of PaperMC (and probably many other servers and versions). Apologies for the very long delay, but hopefully it's useful!


Discover and Series issue

I'm having issue where whenever I added new items into series, discover does not include them. The following is a partial sample of my config:
templates:
  cartoons:
    series:
      settings:
        anime:
          propers: 3 days
          quality: <=720p
          identified_by: sequence
          sequence_regexp:
            - (\d+)
            - S(\d+) (\d+)
          from_group: horriblesubs
          set:
            path: '/mnt/storage1/Videos/TV Series/Various/{{series_name}}'
      anime:
        - Kuromukuro:
            from_group: DeadFish
        - Bungou Stray Dogs
        - Big Order

tasks:
  NyaaTorrents:
    template: [cartoons]
    discover:
      what:
        - emit_series:
            backfill: no
            from_start: yes
      from:
        - nyaa: anime
      interval: 1 hour

Executing the task NyaaTorrents will display the following log,
[date] [time] VERBOSE  discover      NyaaTorrents    Discovering 3 titles ...

follow up with the correct list being searched.
Now, say we add 2 new items like this,
templates:
  cartoons:
    series:
      settings:
        anime:
          propers: 3 days
          quality: <=720p
          identified_by: sequence
          sequence_regexp:
            - (\d+)
            - S(\d+) (\d+)
          from_group: horriblesubs
          set:
            path: '/mnt/storage1/Videos/TV Series/Various/{{series_name}}'
      anime:
        - Kuromukuro:
            from_group: DeadFish
        - Bungou Stray Dogs
        - Big Order
        - Hundred
        - Endride

tasks:
  NyaaTorrents:
    template: [cartoons]
    discover:
      what:
        - emit_series:
            backfill: no
            from_start: yes
      from:
        - nyaa: anime
      interval: 1 hour

Executing the task NyaaTorrents now (with or without --no-cache) will show the following log
[date] [time] VERBOSE  discover      NyaaTorrents    Discovering 3 titles ...

and the list being search is the original 3 items. The 2 new items will not appear.
However, if I edit the existing list, for example, add from_group to refer to other group, it will be executed correctly for the original items. Eg,
        - Kuromukuro:
            from_group: DeadFish
        - Bungou Stray Dogs          # this updated item will be searched correctly
            from_group: DeadFish
        - Big Order

Looks like the same issue as i described in #957

Fixed by 7c29d3e925a5729a30e59f40f2fae009ea8aa4b6


[Land and see - Stries] "Previous" and "next" buttons should take user to the top of the page to continue browsing

Current
Its awkward when the user is taken to the same scroll position on the page if there is no new content. Its also just confusing about what happened.

Should be
Take user to top of new content

As mentioned in #728, I'm not sure amphtml provides a function or component that can scroll to top with JavaScript. An alternative would be to try and use href="#" with an anchor. It depends on if that can be used in conjunction with amp-binds on action.

I took a look at this, with mixed results: https://github.com/ampproject/ampstart/issues/728#issuecomment-341855157

DUPE of #728


Register v0.1.8

@JuliaRegistrator register
Release notes:

multi-threaded reading
bug fixes

Registration pull request created: JuliaRegistries/General/101896
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.8 -m "<description of version>" 45effb72a71247c61e6680b69ffa0d825194b746
git push origin v0.1.8


Change spin plugins list to be installed only

This is the breaking part of the changes requested in #1716.  It changes the default for spin plugins list from "all" to "installed."
Considerations:

This results in different signatures for filtering according to whether you are doing installed (spin plugins list --filter cloud) vs all plugins (spin plugins search cloud).  This follows from the different naming but is a bit weird when testing them side by side.  Is this a concern?
I dithered for ages about whether to support spin plugins list --all (or --available).  It feels like a nice option to me (and would mitigate the asymmetry between list and search), but in the end I didn't because it seemed like a lot of people didn't like having more than one way to do the same thing.
I kept --installed as a hidden no-op option on spin plugins list so that any existing scripts that relied on spin plugins list --installed didn't break, but maybe that's not worth it?

Incidentally the original ask in #1716 was just for spin plugins list to get latest before listing.  I added search as part of that work.  I am not sold that this final change to make list installed only, and to require users to use a separate verb for available, is truly beneficial, but here it is if we decide we want it!

This wasn't approved in time for v2, and as it's a breaking change, we have to put it on ice.


support variable length instances in a mini-batch

In rnn and other sparse input examples, each instance in a mini-batch must have the same length. I saw this is because of embedding layer just support this manner of mini-batch input. The solution in rnn example is to split data into buckets where each bucket has a unique instance length. However, if the data num in a bucket is less than batch_size, all data in this bucket will been discarded.
I don't find solution that can read libsvm data directly. The solution I found is to transform the original data into dense data firstly. But it is absolutely not right when feature num is very very large. I think this restriction is also related to current implementation of embedding layer.
So, is there any solutions to resolve those problems like embedding_lookup_sparse in tensorflow? Thanks.
@piiswrong

@pluskid

@formath For the case of RNN with variable sequence length, the support is via masking or indicating the sequence length. For example, the loss layer support ignore_label, which you can use to ignore parts of the tails in each sequence in your mini batch. Other RNN operators also takes something like seq_len to indicate the exact sequence length of each sample.
It is true that you need to pad all sequence to be the same (maximum) length in a minibatch, and the tails will be discarded. This is why we need bucketing to avoid too huge wasting when some sequences might be very long.

@pluskid thanks. About the second problem, namely directly reading libsvm data where each instance has hundreds sparse features but the whole feature num may be a hundred million, can you give some suggestions? Maybe bucketing is not appropriate there.

No bucketing is not for this problem. I'm not sure what would be a better way to handle this (and I'm not even sure if deep networks will work better in this case than traditional methods). One way is always to convert that to dense vectors, and use smaller mini-batch. That is of course very wasteful. Maybe one can implement some custom layer like the Embedding layer, that could handle sparse vector with multiple non-zeros (instead of only one non-zero entry).