Filtering collection

I only want to index records that are published. I have a boolean isPublished and I would only like records from my collection that are published to be indexed.
I've tried using the transform function but I get an invalid JSON error if I try to return anything other than the data.
Does the extension allow me to filter records before they are sent to Algolia?

What do you return from the transform function? This plugin reads .result of the response of the function. If you don't want to keep any, if I understand it correctly that response should be { result: [] }
https://github.com/algolia/firestore-algolia-search/blob/f29a83e6faf7b9fb6632e0558c314e3f8a4f395b/functions/src/transform.ts#L25-L31

Thank you, I see my error now.
I thought the function operated on each record individually rather than receiving an array of all the records.
That makes a lot more sense.

I'll close this issue now, but if you have further questions, feel free to ask!

OK, so having looked at this further it appears the transform function is applied to each individual record as described in the ReadMe.
(My biggest problem was actually that my function was in Europe-West-1 not Europe-West-2 and that returned the JSON error. Whoops.)
What I want to do is this:
import * as functions from "firebase-functions";

const searchIndexing = functions
  .region("europe-west2")
  .https.onCall((record: any, context) => {
    if (record.isPublished) {
      return record;
    } else {

      // Do not index this record or remove if it is already present

      return;
    }
  });

Having looked at the extension it looks like this is not possible at the moment as the transform function is applied after the decision to Create or Delete from Algolia.
Is there a better way to do this or should this be a feature request?

Sorry for explaining wrong, I think it makes sense as a feature request!

Hello @Bones5
Algolia Search configuration provides a way to filter your search results by using filtering or Query rules.  I would recommend this approach.  I am hesitant to add code for this use case.  Also, I would also suggest not sending attributes in the search results that might not be relevant in the search experience, https://www.algolia.com/doc/api-reference/api-parameters/unretrievableAttributes/.
Let me know if you have any questions.
Sajid

Thanks for your reply @smomin
It does look like this is typically done in Algolia. It is similar to an "inStock" for something like Shopify.
Looking at this example it is applied in at during the index https://www.algolia.com/doc/api-reference/api-parameters/numericFilters/#examples
I'm a bit confused how to replicate this using the plugin, do you know where I would add this search to the index?

If you have the "in stock" attribute as a key of the object/record, you can set it as attributesForFaceting and use filters frontend to hide or display those: facetFilters: [['inStock:true']] for example. You can also use InstantSearch' toggleRefinement or refinementList for making the UI

Thanks for your help @Haroenv
I got there in the end. I spent a lot of time trying to apply the API configuration when it was the was the Configure component I really needed.
<Configure facetFilters={[["isPublished:true"]]} /> 👍


Check only the primary pointing device's accuracy

This pull request changes mouseDetected to check only the primary pointing device and retains the existing logic.
I tested this change on my physical Samsung phone and a few different emulated iPhones in Firefox DevTools.
Context: I couldn't get the mobile-only buttons (including read-only mode) to appear in Firefox for Android, DuckDuckGo, or Samsung Internet on a Samsung Galaxy S22. any-pointer:fine evaluates to true even though I don't have a mouse connected. Based on this article, Samsung devices might be reporting the presence of both a touchscreen and a nonexistent touchpad.
I also tried various combinations of any-hover:hover, hover:hover, pointer:fine, and any-pointer:fine.

For some reason, const mouseDetected = window.matchMedia("(hover:hover) and (any-pointer:fine)").matches; worked in Firefox for Android but not other browsers.
const mouseDetected = window.matchMedia("(hover:hover) and (pointer:fine)").matches; worked but pointer:fine by itself already works.
No change with any-hover:hover by itself or other combinations

Awesome, thanks!


Chrono support?

Feature Request
The DateTimeRange type can be converted from a time crate type, but not a chrono crate type. Would be great if you could convert from chrono too

Thank for the feature request. We'll consider adding this in the future behind a feature flag. We'd also accept a PR

Hey @threecgreen , I'd like to work on this could you please assign?

Hi @Sadaf-A, Thank you for your interest. You're welcome to submit a PR


v4 docs edit

Title

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[ ] I have read the CONTRIBUTING document
[ ] I have read the  CORE VALUES document
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

Hey @spotDL/joining-developers if you have a free minute, this is a great way to get your foot into the door into helping dev spotDL!
Double checking, Feedback and opinions are welcome!
v4 release candidate 1 is coming out soon! Ensure to keep up to date on our Discord!


Item - Load Item and all its children

See #2
Since our basic Item is an ActivityPub Article object, and it doesn't have an outbox itself, this will be tricky to implement using strictly the AP spec.
An idea would be to have a way of filtering items by Audience - and expose it for Article items.
[Updated] All AP Objects have a Replies collection. I populate this collection with the URIs of those items.

For the moment I solved this by using a separate request from the frontend to the API which filters by inReplyTo.


find/create video content to replace some of the slides

hey,
great tool, great idea.
Concerning https://prereview.org/users/164141/articles/205430-how-to-start-a-prereview-journal-club-tips-email-templates, I would love to get more video content explaining:

what is preprints, why it is important
what are peer review, what kind of peer review
...

I will first try to find what is already existing.

you can add some more ideas and partners, I will come back to you at some point, with these questions. have fun and continue the good, hard work!


Making Autolab's Backend Scalable

Whow ok I'm working on one for Docker, fyi.

This is done now. Please let me know if you see any problems.

I'll be pretty busy until late Monday night, so I'll probably get to this Tuesday.

The 'r' in the 'Consumer' is on the second line. I'm pretty sure you're gonna change it but I just wanted to point it out in case it is missed.

Which 'r'? Are you talking about your comment?

I can merge this but I guess this needs to be in _posts directory right..? So I guess just move the files accordingly and then we can merge? Any thoughts, @jez?

As far as merging goes, I haven't thought about it too much. I figured we'd just clone locally, publish the draft using Octopress (octopress publish <draft>), and then push the changes directly to master with a commit message including something like "Closes #1".
Also, I really wished you had waited until Tuesday. I still want to take a look at this, but I'm studying for a very important test that I need to pass.

You are always welcome to make suggestions @jez. Nothing is set to stone and blog posts aren't really be the biggest priority.

While I thank you for reminding me that my input is valued, I whole-heartedly disagree with your assessment of the priority of the blog. Unfortunately, I fear that getting into this discussion now will have to wait, because I am vastly underprepared for my PnC test.

Good luck with your midterm man. PnC is a hard class!

Alright, I think that's enough comments for one round. This is a pretty interesting article :D!


Investigate why we obtains RuntimeError: Time step below 1e-10 for certain parameters

For the following combinations of (Phi0, Phi00):
(0.9, 0.5) (0.9, 0.6)  (0.9, 0.7)  (0.9, 0.8)
(0.8, 0.5) (0.8, 0.6) (0.8, 0.7)
(0.7, 0.5)
The integration stops with RuntimeError: Time step below 1e-10.
Possibly explicit solvers are not suitable for such combinations. In that case this would be addressed by #33. But we don't know so this needs investigation. I don't know how though, other than changing the solver.

So the first thing I will try after my vacation is to run those combinations on the Use_solve_ivp_without_py-pde_wrapper branch, I guess.

Sorry, I realized today I should have run them, hence the issue (so I don't forget anymore). I'll try to run them but I want to finish something else first.

I tried running it for (Phi0, Phi00) = (0.8, 0.5) but got the following:
Traceback (most recent call last):
  File "/Users/emilia/Documents/Documents - UU101746/GitHub/Integrating-diagenetic-equations-using-Python/ScenarioA.py", line 5, in <module>
    import matplotlib.pyplot as plt
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/matplotlib/__init__.py", line 210, in <module>
    _check_versions()
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/matplotlib/__init__.py", line 204, in _check_versions
    module = importlib.import_module(modname)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/kiwisolver/__init__.py", line 8, in <module>
    from ._cext import (
ImportError: dlopen(/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/kiwisolver/_cext.cpython-310-darwin.so, 0x0002): tried: '/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/kiwisolver/_cext.cpython-310-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/kiwisolver/_cext.cpython-310-darwin.so' (no such file), '/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/kiwisolver/_cext.cpython-310-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64'))

@NiklasHohmann could you try?

@EmiliaJarochowska running from the current main branch (this commit) get the same RuntimeError (Time step ...)

@EmiliaJarochowska tried with the Use_solve_ivp_without_py-pde_wrapper branch and got an installation error with pipenv linked to Python versioning issues. I'll try again once this is resolved.

I got it running, after replacing ._apply_operator  by .apply_operator, so dropping the underscore. Pushed it,  apparently the underscore had been deprecated.
I got successful runs for (Phi0, Phi00) = (0.9, 0.6) (0.9, 0.7) (0.9, 0.8)

Here is a result for (0.9, 0.8).
However, I realised that my branch had not been updated, so I was effectively on a commit from January 24 last year. That did not have the bottom boundary conditions effectuated properly, so that commit still had
self.bc_CA = [{"value": CA0}, {"curvature" : 0}]
self.bc_CC = [{"value": CC0}, {"curvature": 0}]

instead of
self.bc_CA = [{"value": CA0}, {"value": 1e99}]
self.bc_CC = [{"value": CC0}, {"value": 1e99}]

and e.g.
CA_grad_back = CA._apply_operator("grad_back", self.bc_CA)
CA_grad_forw = CA._apply_operator("grad_forw", self.bc_CA)
CA_grad = ScalarField(self.Depths, np.where(U.data>0, CA_grad_back.data, \
            CA_grad_forw.data))

instead of
CA_grad_back = CA._apply_operator("grad_back", self.bc_CA)
CA_grad = CA_grad_back

(and likewise for CC).
Apparently, although incorrect, that provided some extra stability that we lost.

It seems the constant porosity diffusion coefficient has not yet been implemented in this branch, i.e. the Use_solve_ivp_without_py-pde_wrapper branch.

Thanks for checking this. These differences show how much you have done to improve this model and the implementation since we last discussed this branch.
The constant porosity diffusion coefficient was supposed to provide stability but apparently it isn't essential.
In other news, Pipfile in this branch had not been updated either. So the problem I reported earlier disappeared after upgrading Pipfile. So I can run this branch on macos again (not on linux but that's a problem on my side).

It runs for me now too, although I get an underflow warning with the default parameters for scenario A

CA_grad_back = CA._apply_operator("grad_back", self.bc_CA)
CA_grad_forw = CA._apply_operator("grad_forw", self.bc_CA)
CA_grad = ScalarField(self.Depths, np.where(U.data>0, CA_grad_back.data, \
            CA_grad_forw.data))

instead of
CA_grad_back = CA._apply_operator("grad_back", self.bc_CA)
CA_grad = CA_grad_back

(and likewise for CC).

I am digesting these results....
It seems accommodating for switches in U, i.e. switching from forwards to backwards differencing and vice versa, depending on the sign of U provides for extra stability, needed when there is some "gap" between Phi0 (surface value) and PhiIni.
Well, this switch just means that you always apply the "upwind solution" and we kwow from the literature that that provides extra stability, so that shouldn't be a surprise.
We removed the switch to make sure that our dummy bottom boundary condition is never enforced, following L'Heureux.
But it has a downside.

Fortunately, py-pde, since the end of last year supplies for boundary conditions depending on the state.
This may be a way out.
However, suppose we want to go for that extra stability, and always use the upwind solution, which boils down to forward differencing for a negative U, i.e. for an upward advective flow, what would be our bottom boundary condition? Because for forward differencing one would need a bottom boundary condition instead of a surface boundary condition.
Well, only if U is negative at the bottom, U may change sign along depth.

Perhaps the former "dummy" bottom boundary conditions for CA and CC were not so weird, i.e. that these compositions should have zero curvature (i.e. second derivative) along depth:
        self.bc_CA = [{"value": CA0}, {"curvature" : 0}]
        self.bc_CC = [{"value": CC0}, {"curvature": 0}]

On the other hand, there is no physical reasoning to support it, afaik.
What we do see, for any run that I can remember is that the steady-state solutions show flat profiles at deep levels, i.e. even the first derivatives are zero.

Perhaps the easiest way to achieve our goals is to revert this commit.

for any run that I can remember is that the steady-state solutions show flat profiles at deep levels, i.e. even the first derivatives are zero.

But U<0 could still happen before a steady-state solution is reached? Which we wouldn't see after the run is completed (unless we run for very short times)? And possibly this could lead to derailing, as in the main branch at the moment? Could this be the reason for not reaching solutions for certain combinations of Phi0 and PhiIni?
In the series of runs I made using the main branch in December, I didn't switch on tracking U at the bottom. Perhaps I need to re-run some combinations to see whether/how often U<0 happens.

We discussed running these cases, i.e. Phi0, Phi00) = {(0.9, 0.5) (0.9, 0.6) (0.9, 0.7) (0.9, 0.8) (0.8, 0.5) (0.8, 0.6) (0.8, 0.7) (0.7, 0.5)} for a very short time to see if we would capture how U changes before they derail. So I ran them for 0.1 * Tstar.
But they all derailed immediately. And U at bottom is only written into a file if the solution is completed, so we didn't get any record of whether it was guilty of the error.
However, I ran (0.8, 0.8) for that same short interval and got a very weird result for porosity. This is before reaching steady state (that was the point), but it does look like a likely source of potential instability.
Final_distributions.pdf.
But this had U>0 throughout. It's very handy to be able to track U.
So the way U is currently exported we can't tell if it's behind the error, because if the error occurs, it won't be saved. However, I will still investigate if we encounter U<0 in the runs that complete.

Okay, which branch are you currently running?
I guess main. What you could do is to revert the changes from this commit manually into LHeureux_model.py.
(disregard the small change in ScenarioA.py, that is also part of that commit).
And preferably use the .apply_operator attribute instead of the deprecated ._apply_operator.
If you are really confident, you could of course do some reverted cherry-picking, but not sure  if such a git command exists.
That will most likely give you completed runs, because this should add stability to the integration of the compositions.

Thanks! My runs of the main branch yesterday were what we discussed in the morning: finding out if the error is related to U reversing direction. But I didn't consider that U wouldn't be saved unless integration completes.
Today I made some runs with high Phi0 and PhiIni and tracking U at the bottom turned on, over 30 T* to see if U ever gets negative. I will see if I can cherry-pick a version that completes the runs that gave us the error.

Okay. I you got completed runs with high porosity from the current main branch, I guess that means that you set Phi0=PhiIni, since a discrepancy between these two values seems to induce an instability.
We could consider adding a feature to make sure that U at the bottom is also saved before integration completes.

Yes. Sorry that was unclear. I ran (Phi0, PhiIni) = {(0.9, 0.9) (0.8, 0.8) (0.8, 0.9) (0.7, 0.8)}, just working on plotting them in an organized manner. Saving U during the run would be just for the purpose of finding the source of error so let me check this first.

Interesting. So discrepancies between Phi0 and PhiIni with the opposite sign, i.e. with Phi0<PhiIni do not seem to induce instabilities.
How can we explain that?

My hypothesis for now is that Phi0 > PhiIni enforces upwards advection at the start of the integration. Of course, compaction should with time smoothen out the difference between these two values, but compaction acting slowly is an essential point of this model. Also at the surface, the effective stress acting upon the sediment (and thus the compaction) are the smallest.
Of course we have the same absolute difference when Phi0 < PhiIni but in that case U should be positive. This is why I suspect the sign makes a difference.
I couldn't register it though because these runs derail so fast that only the state at the initial step is written into the hdf5.
Under hydrostatic equilibrium, the porosity profile should be exponential (see e.g. part 2.2.2 in Chapter 5 of Jourabchi's PhD thesis that was the basis of this part of Ivan's model), so e.g. for a non-oscillatory steady-state this would be the solution for the porosity profile. So tweaking the parameters of Eq. 24 could give us an insight into how quickly the porosity re-quilibrates, but we've seen the stability is very sensitive to these parameters

I have to stop here for now but the runs of the main branch show highly positive U:

I do wonder what this sudden jump in U is though.

Interesting. Perhaps some time you can try e.g. (Phi0, PhiIni) = (0.9, 0.8) which will complete without erro when the revert of the modifications, discussed above, has been applied.

You know how to send me down a rabbit hole 😉 I've learned that it is possible to make git diff for two different files on different branches but not how to do this at a specific commit. So I hoped my semi-manual attempt didn't introduce any errors, but I did not manage to resolve this error:
Traceback (most recent call last):
  File "/Users/emilia/Documents/Documents - UU101746/GitHub/Integrating-diagenetic-equations-using-Python/marlpde/Evolve_scenario.py", line 143, in <module>
    integrate_equations(**all_kwargs)
  File "/Users/emilia/Documents/Documents - UU101746/GitHub/Integrating-diagenetic-equations-using-Python/marlpde/Evolve_scenario.py", line 96, in integrate_equations
    sol, info = eq.solve(state, t_range=End_time, dt=dt, \
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/pdes/base.py", line 604, in solve
    final_state = controller.run(state, dt)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/controller.py", line 326, in run
    self._run_single(state, dt)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/controller.py", line 176, in _run_single
    stepper = self.solver.make_stepper(state=state, dt=dt)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/base.py", line 602, in make_stepper
    adaptive_stepper = self._make_adaptive_stepper(state)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/explicit.py", line 392, in _make_adaptive_stepper
    return super()._make_adaptive_stepper(state)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/base.py", line 495, in _make_adaptive_stepper
    single_step_error = self._make_single_step_error_estimate(state)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/explicit.py", line 368, in _make_single_step_error_estimate
    return self._make_single_step_error_estimate_rkf(state)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/explicit.py", line 289, in _make_single_step_error_estimate_rkf
    rhs = self._make_pde_rhs(state, backend=self.backend)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/solvers/base.py", line 177, in _make_pde_rhs
    rhs = self.pde.make_pde_rhs(state, backend=backend)  # type: ignore
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/pdes/base.py", line 278, in make_pde_rhs
    rhs = self._make_pde_rhs_numba_cached(state, **kwargs)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/pdes/base.py", line 235, in _make_pde_rhs_numba_cached
    self.check_rhs_consistency(state, rhs_numba=rhs, **kwargs)
  File "/Users/emilia/.local/share/virtualenvs/Integrating-diagenetic-equations-using-Pyt-hTapD1hM/lib/python3.10/site-packages/pde/pdes/base.py", line 181, in check_rhs_consistency
    self._logger.warning(
AttributeError: 'LMAHeureuxPorosityDiff' object has no attribute '_logger'

I'm sorry I couldn't make it work. I'll dig some more to see how to resolve this but maybe you have a suggestion?

Ah too bad.
I couldn't find the source of error immediately.
Which is really why does evolution defined by evolution_rate vs. _make_pde_rhs_numba give different results?
You seem to have implemented things correctly.
Let me fix this tomorrow.

Okay, indentation lines 353-358 was incorrect.
You can git pull.

Btw, since we introduced a change in algorithm, it is not surprising that a regression tests fails.
In this case test_integration_Scenario_A.
The other ones still pass, which is interesting.
Anyway, we cannot merge with main. If we want this kind of stable integration in main, we would first have to adjust that regression test.

I'm sorry for this stupid error 🫣
Let's take a look at the results first. I ran it with the values currently in the repo, but got an odd non-physical result:

well, I think it is non-physical, because both carbonate minerals on the surface are gone. Zero. Since we have a steady supply of fresh sediment of which 90% is CA and AR, it is not possible that they dissolve so fast. Possibly this is not steady-state, I have to check.
L'Heureux has a 0-0 state (Fig. 5a and 7) but that's at the bottom of the system. I re-run with (0.9, 0.5) and that reached A-0 at the bottom:

But it's fast 😅

Np, such coding errors are very hard to prevent.
Happy to see that no integration now derails!
So we got ourselves some extra stability.
At the cost of a bottom boundary condition for calcite and aragonite.
But indeed that first plot seems to show an unphysical result. Weird.

Rerun with a different solver (0.9, 0.9)

Let's take a look at the results first. I ran it with the values currently in the repo, but got an odd non-physical result:

So that would be (Phi0, Phi00) = (0.8, 0.7), right?
And not (0.9, 0.9)?

Yes, sorry, you're correct.

I think we are satisfied with runs at (0.8, 0.8) so this issue can also be archived. Please let me know if you agree.

Wouldn't that severely limit initial conditions?

We have not checked if this issue persists upon your most recent changes so we can check that if you want. But if runs at (0.8, 0.8) illustrate the inadequacy of the model sufficiently, we don't have to put work into stabilizing runs with other arguments.

We don't want to fix something we don't want solutions for


Type inference does not find imported type

Describe the bug
When I perform the "Create function" with types action an argument that is declared as a type that was imported the parameter of the generated function will be any:
// hocusPocusMyType.ts
export type MyType = {
	aNumber: number;
};

// hocuspocustest.ts
import { MyType } from "./hocusPocusMyType";

function bla() {
	const c: MyType = { aNumber: 3 };
	doSomething(c);
}

->
function doSomething(c: any) {
  // Implement
}

How to reproduce
Use the code above, any imported type should repro this issue.
Expected behavior
The generated function signature will include the actual type instead of any.
Additional information
The action behaves correctly if the type is declared within the same module.

Version of the extension impacted: v1.4.0

Yeah, I'm not surprised about this. It's doable but not easy work.
For the moment, type inference works on the file itself, isolated. There's definitely a way to give TS access to the project so it can resolve imported files. We'll need to tackle this 👍

Hey, thanks for reporting but it's been a while since I updated this extension and I'm not planning to do this in the foreseeable future. I'm archiving the extension 👍


In slack notifier default channel should not be required

Rancher versions: 2.0 master 2/22
Results:  Since the webhook is already pointing to a channel, the default channel should not be required.

@tfiduccia There are several reasons we have the default channel:

over time user might forget which channel the webhook pointing to, so we can keep this info for the user.
Actually, the webhook can send messages to any channel in the org, here we provide a chance for the admin to point to another channel.
In the add alert page,  users can see the default recipient of the notifier. to make it consistent with other notifiers, we should have a default recipient for the slack notifier.

ok.


[UIWebView] Wrong input takes value when moving from one  to another  (each  in )

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ x ] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[ x ] bug report
[ ] feature request

Current behavior:
Moving from input 1 (inside iframe1) to input2 (inside iframe2) when autocorrect is triggered on input1 causes the user input(meant for input2) to be appended inside input1.
Expected behavior:
User input is sent to currently focussed input.
Steps to reproduce:

Create base ionic app (ionic start)
Replace home.html with snippet.
Host the safari2.html snippet in and set the src of iframes in home.html to point to the hosted page.
Ensure that CordovaWebViewEngine is set to UIWebViewEngine in config.xml
Ensure in app.html that the iframe can be loaded (set allow-navigation and origin appropriately)
In the app, type something in the first input wait for autocorrect to suggest something.
Move to another input and type.

Related code:

home.html
<ion-header>
  <ion-navbar>
    <ion-title>
      Ionic Blank
    </ion-title>
  </ion-navbar>
</ion-header>

<ion-content padding>
    <form>
        <iframe src="http://<IP_ADDRESS>:8001/safari2.html">
	<iframe src="http://<IP_ADDRESS>:8001/safari2.html">
    </form>
</ion-content>

safari2 (to be hosted and used in home.html)

        <input  type="text" />

Other information:

I think this might be related to ionic's handling of taps as removing all JS libraries in index.html does not reproduce this issue with the same case.
GIF: https://user-images.githubusercontent.com/4116675/39105599-7a58562c-46d4-11e8-8ab8-7d2fee3d1bc0.gif
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/usr/local/lib/node_modules)

    @ionic/cli-utils  : 1.19.2
    ionic (Ionic CLI) : 3.20.0

global packages:

    cordova (Cordova CLI) : 7.0.1

local packages:

    @ionic/app-scripts : 3.1.9
    Cordova Platforms  : ios 4.4.0
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 26.1.1
    ios-deploy        : 1.9.0
    Node              : v9.5.0
    npm               : 5.6.0
    OS                : macOS High Sierra
    Xcode             : Xcode 9.2 Build version 9C40b

Environment Variables:

    ANDROID_HOME : /Users/sriduth.jayhari/Library/Android/sdk

Misc:

ionic-team/ionic-v1#380
Issue was initially reported in ionic v1. For a temporary fix we set autocorrect="off" on the input inside the .


Remove the early return when generating sitemap

avoid breaking getting config by webpack function
Description

The webpack config is returned too early when it is isServer.
Related Issue

Nope.
Motivation and Context

Get custom config with input webpack function.
How Has This Been Tested?

Working in my local machine and deployed to Vercel successfully.
Types of changes

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hi @fattomhk, :) I do hope that you will make a PR if this was an issue that I missed. Thank you for noticing it if it happened to you

Done. Sorry for not having time to test it.

Done. Sorry for not having time to test it.

Hi @fattomhk, thank you making the fix, very much appreciated. I will double check it again and the github Actions should also run 👍


add GA tracking snippet to CPP docs

@jtattermusch

This was generated using https://github.com/grpc/grpc/pull/15494


Experimental Skill Prototypes

This commit contains to sample scenarios for Skills:

A SimpleBotToBot example that shows the basics on how to consume an Echo Skill from a root bot.
A more advanced DialogToDialog example that shows how to consume a skill that can perform several activities using a SkillDialog

Reviewed files in the DialogRootBot project. Will continue reviewing tomorrow.


Svelte 4 compatibility

Svelte 4 is here! I'm happy to report that this plugin mostly works with it as is, but there are some minor issues you could address for a smoother experience.
Documentation
Svelte 4 was restructured to be importable exclusively by package exports, which Parcel doesn't support by default. I recommend you add a note to the readme including that link and asking users to turn that on so they won't run into errors.
Console warning for format option
Svelte 4 doesn't support the format option any more, and prints a console warning when plugins like this one use it. It looks like official plugins get around this by importing VERSION from svelte/compiler and setting the option only when VERSION[0] === '3'.

Thanks for the analysis. I have made the changes, and will release them soon

Thank you muchly for your efforts on v0.2.10!


Split goreleaser configuration per distribution

Even though GoReleaser is fast on local machines, it's really slow at CI. Two distributions with the current matrix of arch/platforms are sufficient to cause the default timeout to happen (30m).
Ideally, we would split the workflows and goreleaser files per distribution.

Duplicate of #429?

I'm closing this in favor of the newer issue, given that it has more information than this here.


feat: Avoid gradient background results without input.

Fixes Issue
My PR closes #430
👨💻 Changes proposed(What did you do ?)

Do not show the result screen if the inputs are not entered.
Change the Get Result button to grey color if the inputs are not entered.
Add an error indicator if the Get Result button is clicked and the input is not provided.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots
The button color is turned to grey when the input is not entered:

When the user tries to click on Get Result button without entering the input:
https://github.com/Dun-sin/Code-Magic/assets/61418965/59e76491-c971-4c45-ac03-f96c610b1e23

PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project.  The results are listed in the  following section.
Conventional Commit PR Title
In order to be considered for merging, the pull request title must match the specification in  conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:

docs: correct typo in README
feat: implement dark mode"
fix: correct remove button behavior

Linting Errors

Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
No subject found

@saakshiraut28

You also have some build errors please fix that, you can see what it says by running "npm run build"

I'll fix the errors.

Hi @Dun-sin, the changes have been made. Please review and let me know if there's anything else you'd like me to add.

:tada: This PR is included in version 2.64.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Missing Mayaqua/cpu_features in the source releases.

It seems the default github release logic wont include external git projects, so Mayaqua/cpu_features is not included for the release and a build will fail. This means projects like openWRT can't use those archives and still need to use the rather large/slow 320MB git version.
So you could either switch to a copy/fork of cpu_features or manually add them to a local tar.gz and upload the releases.

From https://github.com/SoftEtherVPN/SoftEtherVPN/issues/731#issuecomment-427116553:

We could setup Travis CI so that it archives the repository and pushes the archive to GitHub.

Hooray, I've fixed it in Launchpad by nesting it before the build! So Launchpad is not an issue anymore.

@paskal , do you mean something like "build step" within launchpad recipe ?

Yes. Now it fails in different place, I'll try to finally fix it.

Debian folder restored from last available before deletion version and now lives in separate repo. For now it successfully builds packages (trough likely improperly), I'll test and fine-tune it shortly.
I think we could include a note to readme what in case of trouble with Ubuntu packages people should create issues in this separate repo.

as for cmake (very recent cmake required), you can take something like that
https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/.gitlab-ci.yml#L7-L8

hi, @Andy2244 , @paskal
I added tar + submodules in new releases
(it is done via AppVeyor machinery  https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/.appveyor.yml#L79)
in the next release (which I expect in few days) full archive will look like that:
https://github.com/chipitsine/SoftEtherVPN/releases/download/v666.666.666/v666.666.666.tar.gz

It won't affect Ubuntu builds, however it seems it should fix Andy's problem.

Thanks will test this next week, if i have some time for openWRT again.


Fixed Issue #707: Buttons with background images now have shape options

#707
@halatmit @jisqyv
Buttons with background images no longer default to the rectangular shape and now instead have shape options that are available to buttons without background images (Default, Rounded, Rectangular, Oval).
Users can also adjust the height and the width of the button and the image will change accordingly.

Note: I increased the radius from the default 10f to 100f for the rounded shape button because the rounded feature could not be seen on the phone or companion with 10f.

Comments help developers & they are not useless. Deleting comments is unrequired commit.

Can one of the admins verify this patch?

This was merged as PR #2843.


Modified Filer to cache blobs of live docs - part of multiple files patch

This patch is part of the fix for [issue #69] (https://github.com/humphd/brackets/issues/69) along with this [PR] (https://github.com/humphd/brackets-browser-livedev/pull/28)

Can this be closed now?  I think we've dealt with it in other patches.  cc @gideonthomas

Yes it was done in this [PR] (https://github.com/humphd/brackets/pull/157).


validate markdownSaveLocation exists before doing anything else

Tried pushing a PR for this but don't have access :)

Fixed in this commit!


Add Threshold fulfillments

Implement a method to create threshold fulfillments for an input. For this purpose is needed the fulfillment in the makeCreateTransaction and makeTransferTransaction methods that was null until now.

Codecov Report

Merging #119 into master will decrease coverage by 3.29%.
The diff coverage is 63.63%.

@@            Coverage Diff            @@
##           master     #119     +/-   ##
=========================================
- Coverage    82.2%   78.91%   -3.3%
=========================================
  Files          21       22      +1
  Lines         281      313     +32
=========================================
+ Hits          231      247     +16
- Misses         50       66     +16

Impacted Files
Coverage Δ

src/transaction/makeTransaction.js
100% <100%> (ø)
:arrow_up:

src/transaction/makeTransferTransaction.js
100% <100%> (ø)
:arrow_up:

src/transaction/makeCreateTransaction.js
100% <100%> (ø)
:arrow_up:

src/transaction/makeFulfillment.js
50% <50%> (ø)

src/transaction/signTransaction.js
62.5% <50%> (-37.5%)
:arrow_down:

Continue to review full report at Codecov.

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


style(mypy): Fix memoize watch type

SUMMARY
The watch variable type was incorrectly encoded as as I wasn't aware of (or forgot) the ... syntax for defining a tuple of arbitrary length, i.e., Tuple[str, ...].
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN
CI.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

to: @serenajiang

Codecov Report

Merging #9970 into master will decrease coverage by 11.95%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9970       +/-   ##
===========================================
- Coverage   71.34%   59.39%   -11.96%
===========================================
  Files         585      401      -184
  Lines       30914    12762    -18152
  Branches     3246     3246
===========================================
- Hits        22057     7580    -14477
+ Misses       8747     5003     -3744
- Partials      110      179       +69

Flag
Coverage Δ

#cypress
?

#javascript
59.39% <ø> (ø)

#python
?

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

@villebro it was working correctly. The reason for the change was to adhere to the original intent where the author used a tuple rather than a list. That's a whole other discussion as I sense in Superset (and other Python repos) many objects which could/should be tuples are defined as lists.


MERC-456 Update the continue url to point to a new specific url instead of home

What
Change the url for the "continue" button to point to a specific url instead of to the home url.
Why
Currently the url doesn't take redirects during account signup into account, which means adding to wishlist while not signed in doesn't work when you create an account (among other things).
Ping @hegrec @mickr @mcampa

:+1:


Update README.md

Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

This partially fixes #1


[WIP] Initial proposal for the preupdate hook.

I created an initial draft for the preupdate hook that seems to work ok after preliminary testing.
Some questions arose and I'm looking for some input/feedback:

Does it needs it own feature flag instead of being bundled with all the other hooks (it needs a special feature flag on the libsqlite3-sys crate).

If it's behind a separate one, I'll probably have to extract some of the hooks code to be included if one or the other is active.

How close do we want to map the original API:

According to SQLite3 docs, the 6th and 7th parameter of the original API are dependent (and can be undefined) on the type of operation. I think it would be more idiomatic Rust if this was exposed through an enum instead of closely mapping the API.

During the preupdate_hook, you have access to some special functions (see docs again), but it depends on which type of operation is done.

Here I was thinking to use an enum for which the variants expose the appropriate functions, to prevent UB from occurring and provide a safe interface.

If anyone can help me and give some feedback on what the best way forward would be, that would be much appreciated.

May I suggest that hooks is kept untouched and a new feature pre_update_hook = ["libsqlite3-sys/pre_update_hook", "hooks"] is used instead (libsqlite3-sys/pre_update_hook should be used to activate the SQLITE_ENABLE_PREUPDATE_HOOK compile-time option).

@gwenn , of course you can suggest that, that is also the first point I touch in my initial message. However the "problem" with that is that it might be confusing that hooks does not encompass all hooks. Of course changing this (i.e. rename hooks to something more specific so it doesn't encompass the preupdate hook) would be a breaking change.
This is my first time writing something that has an interface with C-code so I'm being very cautious and trying to make as little change as possible at a time.

However the "problem" with that is that it might be confusing that hooks does not encompass all hooks.

By default, SQLite does not encompass all hooks so it seems "normal" that rusqlite does the same, no ?
go-sqlite3
tclsqlite

By default, SQLite does not encompass all hooks so it seems "normal" that rusqlite does the same, no ?

The difference (unless I'm mistaken about SQLite itself), is that SQLite will have some hooks by default and you can add a flag for the preupdate_hook. But in rusqlite you have to specify that you want hooks (by using the hooks feature), but then there are hooks that are not in there (i.e. the preupdate hook).
Just to clarify, I am completely on board with having a separate flag for the preupdate hook since it requires a special compilation of SQLite, but I'm concerned that it might not be clear if or how these different features interact.

@gwenn , I just tried to run this hook with a lot of inserts/updates/deletes, and during update after a while it suddenly runs into a SIGSEGV, with gdb this is the top of the stack trace:

Do you have any idea what could cause this?


Error (It asked me to report it)

import numba

@numba.jit()
def primes():
    cache=set()
    def generator():
        n=0
        i=2
        while True:
            if i in cache:
                yield i
            else:
                f=True
                for x in p:
                    if not i%x:
                        f=False
                        break
                if f:
                    p.append(i)
                    cache.add(i)
                    yield i
            i+=1
    return generator
primes()

`ERROR: numba.errors.LoweringError: Failed at object (object mode backend)`
`make_function(code=<code object generator at 0x130820ae0, file "<string>", line 5>, name=$const0.6, defaults=None, closure=$0.4)`
``
`File "<string>", line 5:`
`<source missing, REPL in use?>`
`[1] During: lowering "$0.7 = make_function(code=<code object generator at 0x130820ae0, file "<string>", line 5>, name=$const0.6, defaults=None, closure=$0.4)" at <string> (5)`
`-------------------------------------------------------------------------------`
`This should not have happened, a problem has occurred in Numba's internals.`
``
`Please report the error message and traceback, along with a minimal reproducer`
`at: https://github.com/numba/numba/issues/new`
``
`If more help is needed please feel free to speak to the Numba core developers`
`directly at: https://gitter.im/numba/numba`
``
`Thanks in advance for your help in improving Numba!``

Sorry about it being ugly to read, I'm not sure how to force it to format code properly

Thanks for the report.
RE formatting in GitHub issues, for future reference triple backticks are needed around a code block (with optional language syntax specified), for example: ```python <your code> ```. GitHub also has a basic guide to its markdown syntax available here.

Report is now formatted.

Which version of Numba are you using? I have 0.45 and it report this:
numba.errors.UnsupportedError: Failed in object mode pipeline (step: ensure IR is legal prior to lowering)
Numba encountered the use of a language feature it does not support in this context: <creating a function from a closure> (op code: make_function not supported). If the feature is explicitly supported it is likely that the result of the expression is being used in an unsupported manner.

File "issue4616.py", line 6:
    cache=set()
    def generator():

Closing this issue as it seems to be resolved. If this is not the case please re-open with a comment about any item that appears to be unresolved. Many thanks.


[TVMC] Allow options on --target to contain dots.

Allow options on --target to contain dots.

Allow tvmc compile --target=*** options to accept dots
Adds testing for dot separator in quoted and unquoted values
Add an "unquoting" conditional so that quoted and unquoted strings look the same when parsed

cc @u99127 @comaniac @giuseros  for reviews when possible.

Thanks @leandron @giuseros.
The follow-up PR will improve the readability and unit tests of target matching regex.


Changed intrinsics for compatibility with the base hypervisor

Signed-off-by: JaredWright<EMAIL_ADDRESS>

This PR updates the extended apis for base hypervisor RFC #675
Note that In a few places, I changed auto var = 0ULL;  into uint64_t var = 0;. To clarify why I did that: many of the intrinsics now take references of type uint64_t, which is a different type on different systems (uint64_t ==  unsigned long on my system, but I believe that uint64_t == unsigned long long on Windows). If we just declare the variable as uint64_t in the first place, it handles both cases.
Thoughts @connojd @rianquinn?

@JaredWright +1. I fully support the change from ULL to uint64_t so long as we are not defining the type twice, which does not seem to be the case in your example.


[DRAFT] Reset build script

Fixes #2748.

This PR will need to update CI pipeline.
To-do

[x] Rename .babelrc.js back to babel.config.json

Make sure to modify babel-jest-config.js

[ ] Update /.github/CONTRIBUTING.md
[ ] Clean up/packages/README.md
[x] Update Azure Pipelines

Changelog Entry
(TBD)
Description

Decreased npm install time by about 4x

Do not install/build samples and embed
Down to ~7 packages to install

npm start will start dev mode

Watch mode on all packages
Serve samples and bits (today, we need to run serve manually)
Instrumented build (i.e. bits good for both local dev and Docker tests)

npm prepublishOnly will build production bits
Support source maps for development build of CDN bundle

Specific Changes

[x] Testing Added

This is build script changes, our current PR validation CI pipeline should be sufficient to test this PR.
However, since the build script is new, we should spare some time making sure daily builds are correct.

what about this? https://github.com/microsoft/BotFramework-WebChat/issues/2394

Are we closing #2394 in this PR too? could you add to Fix line in top comment?


Support for QML

QML

https://doc.qt.io/qt-5/qmlapplications.html
Logo
https://github.com/QMLCommunity

Upstream support

[x] tokei supports this language

Hi, I added the qml support to language.rs file to my fork
https://github.com/mapau/onefetch/tree/feature/add-qml-support
https://github.com/Aaronepower/tokei already detects the qml files only the mapping in onefetch is missing.
Would be my first contribution to any GitHub Project.

Hi, I added the qml support to language.rs file to my fork

Great! Would you like to make a pull request?

https://github.com/o2sh/onefetch/pull/362

Didn't know about the cargo test. Sorry it's my first steps with rust and the tools around it.

You're doing great! looking forward to merge your PR :+1:

I'll fix the ascii file and Update the PR, or should I create a new pull-request?

Just update it.


check public parameters match

This PR adds a new check to the fungible integration test. Namely, the check verifies that the public parameters used by the FSC nodes matches those stored at the backend.
The API has been update to be able to fetch the public parameters from the backend. The API can be used also for debugging in case a mismatch appears.
Signed-off-by: Angelo De Caro<EMAIL_ADDRESS>

Hi @KElkhiyaoui , please, could you push the changes directly so that we can merge this? 😃


Arrow functions for Javascript

Support for Javascript arrow function (=>).

Nice idea!
I think the merge conflict is likely some silly issue with some recent changes to master. Probably just the README. Would appreciate a quick merge of master into your fork to resolve it.
Otherwise looks good. If you don't get around to that soon I'll just merge it in and get it sorted.
Thanks for the work!

Strange that I used the last branch. I will create a new request today or tomorrow I think.

No worries! Thanks. I would've tried it myself but sort of forgot. I suppose it isn't a major major feature.
Thank you, and I'll try to get to it over the weekend if you don't.

I did a new request, so I'm closing this.


3 Errors Returned On Import

Hello, when I import this into my Unity asset folder I am returned the following errors:
Removing Assets/MRDesignLabs_Unity_Tools/HUX/Resources/Models/Cursor/Cursor_move/CursorRing.fbm/templates because the asset does not exist
UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
UnityEditor.DockArea:OnGUI()
Unsupported DDS file.
UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
UnityEditor.DockArea:OnGUI()
Assets/HoloToolkit/SpatialSound/Scripts/UAudioManager/UAudioManager.cs(463,10): error CS0616: `ContextMenu': is not an attribute class
any suggestions?  thanks!

Sorry for the late reply on this.  The first 2 errors you can ignore.  The first one is a bad meta file on an auto-generated directory from an fbx import.  The second one is a dds file that is coupled with the cursor fbx.
However the 3rd one could be based on the version of Unity you're using or not have the build settings targeting UWP.  What are your settings for building and which version of Unity are you using?
thanks,
-pat

I also have this issue, I'm using unity 5.6, and I'm targeting the windows store (I can paste a screen shot of the build settings if that's easier)
Thanks,

I'm using 5.6.2f1 and the build setttings are set to UWP with hololens as a target.  I can get it to work if I download HUX from the github source repo rather than from the git submodule, however I am still returned the top two errors but I can still build.

As I mentioned the top 2 errors are just import errors and not critical ones.  I'll remove the offenders anyway but what to make sure that use it as a submodule should but the correct approach.  So @reillydonovan you have a git repo that you were creating the submodule in and getting the 3rd error above from HTK?
To be clear on the repo steps I'm going to test with the following (as all of them should work):

Option 1: Create a new project and clone MRDesignLab_Unity_Tools into Assets
Option 2: Create fork of HoloToolkit and add MRDesignLabs_Unity_Tools as a submodule
Option 3: Create a stand alone repo and project and add MRDesignLabs_Unity_Tools as a submodule

Do these are seem viable and which structure are you using?
thanks,
-pat

Option 1 above worked for me.
I didn't try Option 2.
Option 3 is the option that I did try without success, but I can try again.

Awesome!  All 3 should be resolved.   I removed the offending dds and meta file to nowhere and updated the context menu in HUX to be in the cursors namespace as well as named it appropriately.  It's now ContextCursorMenu since that's really what it was intended for.

That worked, thanks, I can now use the submodule.  The DDS still reports an error but doesn't prevent me from building the solution.

D'oh! I'll delete the other dds then as well as they're not being used currently.
Thanks,
-pat


Hire?

Hi. Are you perhaps available for hire? I need to setup authentication in proxy and I am looking for a developer.

Sorry, I'm a beginner in Android development
I'm afraid I'm not up to it


Not able to change SSPR email id when using username(not emailid) to sign in in the contect of Azure B2C

Not able to change SSPR email id when using username(not emailid) to sign in in the context of Azure B2C
Using Azure B2C
Using username (not email id) to sign in
Email is provided for SSPR
Issue - do not see any instruction around how to change SSPR email id in this case.

@sogetidev1 Thank you for the question! In order to best address your question, could you provide us with the URL of the MS Doc that you were following, if any?

It was mentioned on this thread that this will be possible and available in next 6 months but I do not see any confirmation since then on same.
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/17902447-change-user-s-primary-email-address-primary-email

@sogetidev1 Thank you for the response. We regret the inconvenience caused.
I'd like to let you know that this channel (the Azure Docs repository) is only for driving improvements related to the Azure documentation. The best place for specific answers about implementations is going to be the Microsoft Q&A platform.
Request you to open a question here under the [azure-active-directory] tag: https://docs.microsoft.com/en-us/answers/topics/azure-active-directory.html so we can look into this in greater detail. We actively look through posts in the forums, and will do our best to get you going in the right direction!
Thanks again for your understanding.

@sogetidev1 We will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Rename postTemplate as postConfig, textPostTemplate as textPostConfig [pr]

What's this PR do?
Makes code updates per Contentful changes described in the title ☝ , because it was getting too confusing having the word template in the field and content type names. This is prep work for the last remaining item in #1021, where we need to pull fields like askText and invalidText from the campaign postConfig reference entry to render as properties within the templates object of a GET /campaigns/:id response.

Moves the template data defined in config.templates into config.templates.botConfig. The template data from other content types like textPostConfig and photoPostConfig will be defined here too as properties -- e.g.config.templates.textPostConfig, config.templates.photoPostConfig

Adds a getTemplatesFromBotConfig botConfig helper function, that returns a templates object. It's currently looping through all templates defined in config.templates.botConfig, but eventually will loop through the relevant config.template.textPostConfig object keys to add our askText and invalidText template properties.

Updates lib/middleware/campaigns/single/bot-config-parse middleware accordingly
Moves module.exports to the bottom of lib/helpers.botConfig per https://github.com/DoSomething/gambit-campaigns/pull/1028#discussion_r179258770

How should this be reviewed?
I've made the relevant changes in Contentful for Get Lucky (created a textPostConfig and set it to the botConfig's postConfig reference field).  Upon staging deploy, verify:
Get Lucky returns a botConfig.postType set to 'text': https://ds-mdata-responder-staging.herokuapp.com/v1/campaigns/2900
And other campaigns return botConfig.postType set to 'photo': https://ds-mdata-responder-staging.herokuapp.com/v1/campaigns/2299
Any background context you want to provide?
what else?
Relevant tickets
#1021  #1026, #1027
Checklist

[x] Documentation added for new features/changed endpoints.
[x] Tested on staging.

@rapala61 mind giving a quick 👀 👍 before merge?


Import images from remote

I tried importing images in a remote project with an import statement.
The final parsed image request is not taken over by es-module-polyfill, but by the browser.
Causes remote image resources to not be used properly.
So I need config remote base and host proxy to forward the request.
However, when I added the base configuration to remote, nothing worked.
e.g. remoteEntry.json can not be found and the shared deps import name has been changed.
Does this plugin support configuring base?
Or do I need to do something extra?
It should be noted that this functionality is normal for builds, and esbuild-plugin-inline-image is able to build images into base64, but does not take effect in Dev.

🤔 Have you got a basic reproduction repo?

Yes, I just made one.
https://github.com/He110te4m/module-federation-issue-10-reproduction-repo

Thanks.
Looking forward to your good news.

I found a way to use import.meta.url modifies the image address of import in the TS file.
Imports in CSS need to be replaced manually with the postcss-url plugin.
It was a temporary solution, but it was strange.
From a maintainable point of view, proxy is more appropriate.

Can you share me the code pls?

I needed a little more time, and found that the images used in CSS needed to be processed separately in esbuild.
You can use this plugin if you are importing images directly from a file such as TS or Vue:
import { type Plugin } from 'vite'

const defaultSuffixes: string[] = [
  'png', 'webp', 'jpg', 'gif',
  'jpeg', 'tiff', 'svg', 'bmp',
]

export interface PluginOptions {
  suffixes?: string[]
}

export default function transformImageUrlPlugin({ suffixes = defaultSuffixes }: PluginOptions = {}): Plugin {
  const staticResourceReg = new RegExp(`\\.(${suffixes.join('|')})($|\\?)`)

  return {
    name: '@dsp-plugins/vite-static-url',
    transform(code, id) {
      if (staticResourceReg.test(id)) {
        return {
          code: code.replace(
            /(export\s+default)\s+(".+")/,
            '$1 new URL($2, import.meta[\'url\']).href',
          ),
          map: null,
        }
      }
      return undefined
    },
  }
}

Although this solves my problem, I think it would be more convenient to use proxy.
This solution must be built with the server address in mind, and can not be adapted to various environments.
Although this solves my problem, I think it would be more convenient to use proxy.
This solution must be built with the server address in mind, and can not be adapted to various environments.
Unless the Nginx forwarding address is used.
But the nginx configuration also needs to be build-time generated, which involves too many steps.

Nice 🙂 will you use this solution or something base on proxy? Can we close the issue?

If this problem is just dealing with image loading, I think it can be turned off.
However, as mentioned earlier, there is still a problem with vite configuring base to not open the page properly.
Maybe we can open a new issue to track this?

yep, let's close this one and we can create a specific one for the base issue


Move the ermrest URL formulation from chaise to ermrestjs

Right now, chaise determines which ermrest API to use (e.g. entity, attribute, attributegroup, etc.) and pass that to the resolver. This logic should be done at the ermrestjs level.

isn't this done already?

This is done by us using the Reference API now.


Fix #261: RE 2, random BGM requires RE1 installation

Fixes #261

First attempt at an actual code contribution to open source, so let me know if I missed anything - not sure if I need to have this issue assigned to myself, and if I should add myself to CONTRIBUTORS.md if my changes make it through (not sure if someone else is supposed to do it)?

Sure, add yourself to CONTRIBUTORS.md

First attempt at an actual code contribution to open source, so let me know if I missed anything - not sure if I need to have this issue assigned to myself, and if I should add myself to CONTRIBUTORS.md if my changes make it through (not sure if someone else is supposed to do it)?

Sure, add yourself to CONTRIBUTORS.md

Thanks, will do that tonight - should that be in this PR or a separate one?

Thanks, will do that tonight - should that be in this PR or a separate one?

You can use the same PR.

Have added myself to the list :)


Enable basic tx-level tracing

Currently, tracing is possible only on the address-graph level, i.e., by following the sending and receiving addresses. We could enable a basic form of tx-level tracing by utilizing the "Transactions" field in the property box. Necessary steps:

[] Split "Transactions" into "Incoming Txs" and "Outgoing Txs"
[] For "Incoming Txs" display the number of "Input Addresses" and allow expansion of address + value in another child-level box
[] For "Outgoing Txs" display the number of "Output Addresses" and allow expansion of address + valuein another child-level box
[] Enable selection of addresses to be added to the dashboard

might be a duplicate with https://github.com/graphsense/graphsense-dashboard/issues/402


Multitarget single table

Here is an example notebook: https://github.com/TeamHG-Memex/eli5/blob/multitarget-single-table/notebooks/explain_text_prediction.ipynb
When dense_multitarget=True is passed, feature weights for multiple targets are shown side-by-side in separate tables (that are put inside one big table) with global weight range. Wrapping tables (instead of rendering it as one table) makes code easier, and seems to work fine.
As for feature highlighting in text, the best idea I came up with was to show text only for the winning prediction. Maybe you had something else in mind here @kmike ?

Current coverage is 95.93% (diff: 77.77%)

Merging #62 into master will decrease coverage by 0.12%

@@             master        #62   diff @@
==========================================
  Files            27         27
  Lines          1270       1279     +9
  Methods           0          0
  Messages          0          0
  Branches        215        221     +6
==========================================
+ Hits           1220       1227     +7
  Misses           26         26
- Partials         24         26     +2

Diff Coverage
File Path

•••••••    77%
eli5/formatters/html.py

Powered by Codecov. Last update 0fae477...6b99a1d

Horizontal layout looks awesome, much easier to read!

For in-text highlighting I was also thinking about highlighting different words in different colors, color=class. I don't know how well would it work. Maybe bars of different colors for each words. Or maybe color of the top class for this word, with intensity proportional to its difference from weights of other classes. Or maybe this is all pointless, and interactive example could be simpler and easier to implement - just allow to click on a class to highlight text according to weights for this class.

@kmike I left only the horizontal layout option here, renamed it to horizontal_layout and made the default.

Thanks @lopuhin!


Improve labels in model registry

Currently the labels in the model registry (see /system/console/modelregistry) are misleading and should be improved.
Filter: mapping to
is used to filter the models by only showning those which can map the resource behind the given path.
Suggestion
Only show models that can map the (resource belonging to the) path [/content...]
Filter: compatible to
is used to filter the models, by only showing does which could be cast to a certain (super-)class or interface. Basically only showing those for which "instanceof" would return true.
Suggestion
Only show models that can be cast to [class/interface]

Indeed, the labels can be improved. However, there is very limited space in the console, thus long texts are not a good option. I'd rather go with
"adaptable from" for the resource path and "assignable from", as those are well defined technical terms. In addition, I would provide a placeholder text in the form fields illustrating the expected input.

Implemented - done!


Added client testing docs

After a couple of days struggling to test the client side with webmock, I decided to share the solution as the original docs lacks of this information.
Hope this helps other users!

Updated the docs and added the example as a working test.
Thank you!

One more fix regarding the test methods, please.
If you feel like it, since this is a schema for an invoice API, maybe rename schema.json into invoice_api.json and things like 'returns expected data' into 'returns invoice fees', just to show intent. I'm really nitpicking :)

Updated PR with requested changes

Merged, thank you!


Make touch to be an instance property

Since Store defines touch as an instance property, typescript throws on this:
node_modules/connect-typeorm/out/app/TypeormStore/TypeormStore.d.ts:38:5 - error TS2425: Class 'Store' defines instance member property 'touch', but extended class 'TypeormStore' defines it as instance member function.

Shame on me, this duplicates https://github.com/makepost/connect-typeorm/pull/2

Thanks too. Sorry for the delay to both of you.


[ci] Update MacOS version at Travis

There is a new version of The macOS Build Environment. So I propose changes for you to use a modern one. https://docs.travis-ci.com/user/reference/osx/

ah I see, ok then I am ok with this change.


Exception Thrown When Rendering Base64 Encoded PDFs (iOS)

<PDFReader
  source={{
    base64: `data:application/pdf;base64,${data}`,
  }}
/>

The "data" variable is set to this value.

It's also worth noting that I'm using your latest merged commit on master, which updates the code to work well with Expo SDK 34. (My project uses Expo SDK 35).

Should be fixed at v0.5.0.


AMQP-572: Always commit only in afterCompletion

JIRA: https://jira.spring.io/browse/AMQP-572
Since RabbitMQ doesn't support XA transactions and it really doesn't care about the transaction boundaries,
it doesn't matter when we call channel.basicAck() and channel.txCommit().
Therefore any TransactionManager looks the same for RabbitMQ and we don't need to distinguish if we are within a local transaction or XA.

Move this.resourceHolder.commitAll() in the RabbitResourceSynchronization to the afterCompletion() permanently, unconditionally.
All test passes and now the ACK on the RabbitMQ will be done only if the commit to the DB is successful, for example.
And it doesn't matter now if we use  XA transactions or Dave Syer's Best Efforts 1PC pattern with the ChainedTransactionManager

NOTE: There might be some breaking effect for end application if they do some "hard" work around TX synchronizations and rely on the previous behavior.
Since it is minor release, I think we can live with that and provide some workaround on demand.

Should we add a TransactionTemplate test, as discussed in the JIRA?

??? See that modified tests-case in PR - testSendInGlobalTransactionGuts
It is fully based on the TransactionTemplate.
But right now we don't need to worry about TransactionAspectSupport.currentTransactionStatus().isNewTransaction(), because we don't care about that at all. We always just wait for the end of TX.

Doh - I should have looked at the code, not just the PR - all I saw was a bunch of deleted stuff.
Sorry.


Add file watcher to auto-refresh game list on Archive tab

When an .sgf file is uploaded into the app via iTunes, the file does not automatically show up in the list of games on the "Archive" tab. Several workarounds currently exist (e.g. lock/unlock the device), but they all involve sending the app to the background.
#240 suggests adding a refresh button, but this still requires the user to take manual action to see the added file(s). A better approach would be to have a file watcher that automatically refreshes the list of games whenever it detects a change in the app's document folder.
This issue replaces #240.

Initial research indicates that GCD (Grand Central Dispatch) can be used to receive notifications about filesystem changes.

https://stackoverflow.com/questions/21827786/how-to-monitor-file-change-on-ios-platform
https://stackoverflow.com/questions/1386743/observe-a-file-or-folder-in-objective-c


fix: update node and types

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move to 7TV API v3

Fixes #633
Changes

moves emote to new 7tv API
removes support for 7tv cosmetics

Checklist

[x] My change builds
[x] I tested my change
[x] I use the "bttv_" prefix for all resources I propose
[x] When adding a string I also added it to the bttv.Res.strings Enum and res/values/strings.xml (in mod) and res/values/public.xml (in disass)
[x] If my change is significant enough, I added it to the CHANGELOG.md under master
[ ] I'll add myself and everyone else who contributed to this change to the contributors list using all-contributors
[x] I license my changes according to the MIT License.

@all-contributors please add @zakary2841 for bug

@all-contributors please add @ecan18 for bug


Teach Activity log input to enter LLM Content arrays

It errors with Uncaught TypeError: a.map is not a function
Board attached.
board-2024-05-23T09_50_20.401Z.json
I'll be honest, I'm not sure if I should be passing in LLM Content but all the other tools do.

The input can now handle LLM Content Arrays!


safe jQuery & faster live binding

Using anonymous function with safe jQuery
Remove document ready - live method no need to wait for dom ready

Ok thanks :)


fix: Add restart condition when network interface multiqueue is enabled

What this PR does
This change adds the restart required condition to VMs when
the current VMI has only a single socket and NetworkInterfaceMultiqueue is
enabled to prevent failures when trying to change existing tap devices.
Before this PR:
VMs with NetworkInterfaceMultiqueue enabled would fail to hotplug additional CPUs.
After this PR:
VMs with NetworkInterfaceMultiqueue enabled require a restart to hotplug additional CPUs.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

VMs with a single socket and NetworkInterfaceMultiqueue enabled require a restart to hotplug additional CPU sockets.

/test pull-kubevirt-unit-test

/test pull-kubevirt-unit-test

/lgtm

One of the reasons CPU unplug requires a restart is related to networkInterfaceMultiqueue, for additional details please see https://github.com/kubevirt/kubevirt/pull/11883.

@orelmisan Is that the only reason why unplug requires a restart?

/approve

/cherry-pick release-1.3

/kind bug

@orelmisan Is that the only reason why unplug requires a restart?

No, it was also problematic to perform with dedicated CPUs.

@0xFelix Please see https://issues.redhat.com/browse/CNV-38723.

/cherrypick release-1.3

/cherrypick release-1.2

/retest-required

/retest-required

@0xFelix

@0xFelix
Hi. Can I ask you a question，If the network interface multiqueue is enabled, is it possible to change the number of queues at the same time when the hotplug cpu sockets。
Apply a new xml file with modified queue numbers: virsh migrate xxx.xml。

@leonhardt2020 Hi, not from the KubeVirt API. On the libvirt side of things changing queues might work but that needs to be verified. What definitely doesn't work is enabling multiqueue during cpu hotplug when it wasn't enabled before.

@0xFelix Hello, I would like to consult the details again. Why does the cpu hotplug need to restart the virtual machine when the network queue is enabled? Is the reboot to keep the network queue and cpu count in line? And why the VM needs to be restarted for cpu reduce。

@leonhardt2020 Hi, yes, the restart is needed to keep the network queue and cpu count in line. Both, on adding and removing CPUs currently.
Perhaps @orelmisan can shed some more light on this topic.

Hi @leonhardt2020, When using network multi queues, the tap device created by virt-handler is created with a number of queues derived from the number of vCPUs:
https://github.com/kubevirt/kubevirt/blob/32ab077c9362f62b2fae26bf430c08aba8205e78/pkg/network/setup/netconf.go#L104
The domain also have the same number defined on the NIC:

This is the error that we've encountered:
{"component":"virt-launcher","kind":"","level":"error","msg":"Received a live migration error. Will check the latest migration status.","name":"rhel9-uefi","namespace":"default","pos":"live-migration-source.go:714","reason":"error encountered during MigrateToURI3 libvirt api call: virError(Code=38, Domain=0, Message='Unable to create tap device tap0: Invalid argument')","timestamp":"2024-02-23T06:08:28.229919Z","uid":"a61dfb1c-d138-4bcc-b87a-1c4e5b098577"}

@0xFelix @orelmisan
Thank you both for your answers


Add a "keyword" search on online opengee documentation.

once you are on the http://www.opengee.org/geedocs/,  it would be good to have some smart keyword searches.

Duplicate of #371


Moved "bootstrap" to be build with "windows" variant

High-level description
For some reason adding of bootstrap package to the list of packages to be built for variant "windows" has been missed for DC/OS open.
Corresponding DC/OS tickets (required)

DCOS_OSS-5765 WinpandaApp: Add Bootstrap Package Into Sorted Dependency List.

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot changelog-not-required reason

@mesosphere-mergebot request-review @DominikDary

@mesosphere-mergebot request-review @jongiddy

need to squash several commits before


[Fixes #6979] Orchard.Projections - Added operator IsNull and IsNotNull to date time filter handling to be able to filter NULL values of DateTime? columns correctly

see issue #6979

Hi @ViRuSTriNiTy, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Instead of adding the IsNull and IsNotNull operators, would it perhaps be better to simply use the IsEqual and IsNotEqual operators, and add the ability to specify a NULL value instead?

@sfmskywalker Yeah that would be another solution, i thought about that too initially, but the implementation would be a bit more complicated as

the equal operator implementation uses calculated min / max variables, this is not compatible with NULL values, so there needs to be a new path for the NULL value handling

the view to configure the condition needs to be extended with a new input that accepts NULL values instead of the current solution (that is simply hiding the value input controls)

I don't see a benefit of adding additonal complexity by enabling the ability to specify a NULL value here.
Also, imho IsNull and IsNotNull does communicate clearly what is going on under the hood.

Can someone try the changes and ensures it doesn't break the current scenarios?

I've tried the changes and it works for existing projections (several years old) and new projections which use the new Null and NotNull filters. The additional null checks also seem to fix some issues (crashing queries that is), I had before when creating projections on DateTime? fields.

@Xceno Thx, awesome.

@Xceno I changed the base branch to 1.10.x as requested in https://github.com/OrchardCMS/Orchard/issues/6979#issuecomment-258402945

Does this need a review again? We would still like to have this PR in 1.10.x

Thank you sir! =)

Bitte schön


CC3 opdm

Description
Adding CC3 one-particle density matrix for the calculation of dipole moments, useful in RT propagations.
Todos

[x] Adding CC3 terms to opdm in ccdensity;
[x] Adding triple drivers for the nested loops over virtual orbitals for Doo (already in lambda_cc3 PR);
[x] Modifying the dipole function in rtcc in terms of the contraction involving T1-transformed integrals;
[x] Adding the test for electric dipole moments.

Status

[ ] Ready to go

This branch includes all changes in lambda_cc3;
The new test (test_032) will replace test_031 after lambda_cc3 being merged;
The CC3 part of the density matrix is not generated automatically when ccdensity is initiated since it's relatively costly and not necessary when calculating dipole moments.

Codecov Report

Merging #56 (34a9056) into main (bc0b03d) will decrease coverage by 3.45%.
The diff coverage is 63.97%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more


Bug fix wrong result on mark join + other conjunct

Proposed changes
fix wrong result on mark join + other conjunct
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

Does pipelinex have this problem?
it is common code

run buildall


docs(MIGRATION): remove shareReplay

Description:
Remove shareReplay from the Operators Renamed or Removed list in MIGRATION.md, as it was implemented in 5.4.0 and its listing is causing confusion.
Related issue (if exists): #3034

Coverage remained the same at 97.204% when pulling 16ff153093b20013a96e5e2db7001ff986774ed1 on cartant:issue-3034 into cff9dfa7c5fdc6606721a2efcee23327ff966a5f on ReactiveX:master.

Thank you @cartant


Support pagination when collection certificates

This is submitted as a fix for issue #104 I raised.
Without this fix, only the first 500 certificates would be searched and
found period.  This enables us to search the entire listing of certificates in your
developer portal.
Tested and worked to renew a certificate on my account with 773 certificates.

Looks great, thanks for providing this pull request :+1: This will be in the next release :rocket:

Sure thing, thanks for the great tools!


chore(package): update sinon to version 1.17.4

https://greenkeeper.io/

Tests depend on this update and they pass so :shipit:


missing assets? failed to load visual mesh & random lengthy training

Hi.
It seems like there is an issue with the textured objects of 9918 and 10090, it reports "Failed to load visual mesh" when running random_action.py. Can you please check on this issue?
My temporary solution is to modify the task setting and omit these 2 objects, does this potentially lead to training issues? I have been experiencing random lengthy training epochs that takes a long time on env.step(), which almost looks like it's stuck in a loop.
Thank you in advance for the help!

in the process of debugging the lengthy training time, i discovered that you commented out a few lines in the early stop section link to code
                if self.target_kl is not None and approx_kl_div > 1.5 * self.target_kl * scheduling:
                    # continue_training = False
                    num_early_stopping += 1
                    # if self.verbose >= 1:
                    #     print(f"Early stopping at step {epoch} due to reaching max kl: {approx_kl_div:.2f}")
                    continue

these 3 lines are not commented out in the stable baselines3 code link to code
May I know the reasons for commenting out these lines? Thank you!

Hi, @xwong22 . Thanks for using our benchmark. For your first question, please refer to #1 . For your second question, we comment it out to observe the performance of the designed reward function when the environment is not finalized at the early developing stage(if early stopping happens too frequently, we cannot understand why it works or does not work). I think you can align it with the sb3 version as well and this will not affect the overall performance too much.

I see, thank you so much for the prompt reply!


Monitor metrics endpoints on services

I'm trying to get the prometheus configured here to scrape the metrics endpoints of the containers, not just the stats coming from cadvisor. Maybe finding them via a label?
Just wondering if you've seen or done something similar.
Cheers,
E.

I ended up getting this working great using dns-sd... if its useful to put, add to in the docs (or for anyone googling..)
Before starting dockprom I add a little extra to the config
    echo "
  - job_name: 'services'
    scrape_interval: 5s
    dns_sd_configs:
      - names:
          - scrape.me.prometheus
        type: 'A'
        port: 9999
    " >> prometheus/prometheus.yml

Then, on each of my services in docker-compose that I want to be monitored i provide the metrics at ":9999/metrics" and add the right alias...
  my-service:
    image: "super-special-service:latest"
    networks:
      default:
        aliases:
         - scrape.me.prometheus

And add prometheus to the network docker-compose made for my app....
docker network connect myapp_default prometheus

And, done!

Your config is similar to what I've used for Docker Swarm in this project (swarmprom)[https://github.com/stefanprodan/swarmprom].
How will you differentiate the services since the job name will be the same for all? The containers IPs will change after each deploy.

Hmm. I... don't know. Something fun to play with next.

My approche was this https://github.com/stefanprodan/swarmprom#monitoring-applications-and-backend-services

Hello, I have a question, I have multiple services from the same web application but each is a different environments, I'm using this config:
  - job_name: 'app'
    metrics_path: /services/app/metrics
    scheme: https
    scrape_interval:  5s
    tls_config:
      insecure_skip_verify: true
    dns_sd_configs:
    - names:
      - 'tasks.app'
      type: 'A'
      port: 443

How can I get like a Swarm Service Label || Container Label || Task Label in order to differentiate each task?


[do not merge] Test only remote test branch

ci test

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 65.92%. Comparing base (8765218) to head (1808049).
Report is 364 commits behind head on release-next.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                Coverage Diff                @@
##           release-next     #938       +/-   ##
=================================================
+ Coverage         48.98%   65.92%   +16.94%
=================================================
  Files                96      131       +35
  Lines             13105    12131      -974
=================================================
+ Hits               6419     7997     +1578
+ Misses             6049     3159     -2890
- Partials            637      975      +338

Flag
Coverage Δ

e2e-test
36.79% <ø> (?)

e2e-test-runtime-go
26.37% <ø> (?)

e2e-test-runtime-node
25.77% <ø> (?)

e2e-test-runtime-python
25.77% <ø> (?)

e2e-test-runtime-quarkus
25.86% <ø> (?)

e2e-test-runtime-rust
24.92% <ø> (?)

e2e-test-runtime-springboot
24.95% <ø> (?)

e2e-test-runtime-typescript
25.85% <ø> (?)

integration-tests
52.67% <ø> (?)

unit-tests
51.24% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Improve docs on local dev with Pages and D1

Which Cloudflare product does this pertain to?
Pages and D1
Existing documentation URL(s)
https://developers.cloudflare.com/pages/functions/bindings/#interact-with-your-d1-databases-locally
and
https://developers.cloudflare.com/d1/learning/local-development/#develop-locally-with-pages
What changes are you suggesting?
The 2 sections above are not directly linked and it would be nice if they were.
Working thru the Pages docs here this statement:

While developing locally, interact with a D1 database by adding --d1 <BINDING_NAME>=<DATABASE_ID> to your run command.

led me to believe I needed to add the --d1 arg to my start script like so
npx wrangler pages dev --d1 DB=the-id-of-your-D1-database-goes-here -- pnpm run dev

which does not work, but the terminal output makes it seem like it did, which definitely added to my confusion.

A couple lines later the wrangler.toml file is suddenly mentioned even tho it hasn't been before. At that point a link to this section would be super helpful.
Thank you!
D1 on Pages are so cool, along with wrangler dev the DX is just 🤌
Additional information
No response

If you are only using Pages + D1, you only need the below in your wrangler.toml to interact with D1 locally.
[[d1_databases]]
binding = "DB" # Should match preview_database_id
database_name = "YOUR_DATABASE_NAME"
database_id = "the-id-of-your-D1-database-goes-here" # wrangler d1 info YOUR_DATABASE_NAME
preview_database_id = "DB" # Required for Pages local development

Thank you!


Create a GMTSession context manager

Would be created and returned by gmt.begin. Should return itself when calling __enter__ and call gmt.end() upon __exit__.
See https://docs.python.org/3/library/stdtypes.html#typecontextmanager

Related to #15


Ghc panic if stale *.hi or *.o files are found

If ob run or ob repl are interrupted, after I try to restart them, during the executions of the tests the following error will appear:
ghc: panic! (the 'impossible' happened)
  (GHC version 8.4.3 for x86_64-unknown-linux):
	Loading temp shared object failed: /run/user/1000/ghc4731_0/libghc_12.so: undefined symbol: FrontendziWidget_staticzq_closure

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

...done

I noticed that this issue can be solved if I remove all the **/*.hi and **/*.o files, that are probably generated by my dante emacs setup. For the time being I disabled dante and will rely only on ob watch to check errors.

Heads up: If you use cabal new-repl or cabal build, this will trip off ob run as well, you need to get rid of that ".ghc..." file.

Should we consider triggering some script whenever this error occurs?

We're now using ghc 8.6 so I wonder if the situation has improved at all.

Please reopen if you're still encountering this.


noVNC behind reverse proxy

Hi,
I'm trying to use handbrake behind a swag reverse proxy.
I'm using linuxserver/swag with their sample format for routing the url.
The first problem is that I got a 404 error from nginx.
Looking at access.log and error.log I figured out that the container was looking for files at /opt/noVNC/handbrake/ instead of /opt/noVNC/.
I worked around this by making that directory and then moving everything from noVNC inside.
Now I get nice screen with a red bar on top that says "Failed to connect". There is no new errors at error.log but access.log has a bunch of stuff.
Could this still be about my routing?
I'm not sure who can help me, but I would really appreciate any help :)
My proxy config:
`location /handbrake {
return 301 $scheme://$host/handbrake/;
}
location ^~ /handbrake/ {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app handbrake;
set $upstream_port 5800;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

location /handbrake/websockify {
	proxy_pass $upstream_proto://$upstream_app/websockify/;
	proxy_http_version 1.1;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection $connection_upgrade;
	proxy_read_timeout 86400;
	}

}
`
Is there any other checks I can do?
I'm really new to all of this but I can google whatever you throw at me :)
Thanks!!

This works for me:
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name handbrake.*;
add_header X-Robots-Tag "noindex, nofollow, nosnippet, noarchive";

include /config/nginx/ssl.conf;

client_max_body_size 0;

# enable for ldap auth, fill in ldap details in ldap.conf
#include /config/nginx/ldap.conf;

# enable for Authelia
#include /config/nginx/authelia-server.conf;

location / {
    # enable the next two lines for http auth
    auth_basic "Restricted";
    auth_basic_user_file /config/nginx/.htpasswd;

    # enable the next two lines for ldap auth
    #auth_request /auth;
    #error_page 401 =200 /ldaplogin;

    # enable for Authelia
    #include /config/nginx/authelia-location.conf;

    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app <IP_ADDRESS>;
    set $upstream_port 5800;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;

Only slightly modified from default. I have used <IP_ADDRESS> as SWAG and Handbrake are on different servers.
And I use subdomain not subfolder.
`

@johnvick

This is default setting. Most Docker/SWAG setups work better with subdomains than subfolders in my experience.  As I said I made minimal changes to the default nginx profile, just IP address and authentication.

You may want to check the example in documentation: https://github.com/jlesage/docker-handbrake#routing-based-on-url-path
Note that the presence or not of the ending / in path is very important.

I maybe should have made it clearer - I use the SWAG Nginx proxy-conf and it work fine with minor modifications for my setup.

OK, I almost got it!
I added the / in my proxy pass so now it's proxy_pass $upstream_proto://$upstream_app:$upstream_port/;
This solved the problem of looking for the files in the wrong place. I removed the container and image to clear up the mess I made inside. Now my problem is that there is no graphics on the page, just some text, textboxes, and broken pictures. Looking at the network tab of Firefox developer tools showed that for ui.js I get an error NS_ERROR_CORRUPTED_CONTENT.
Any idea what to do with that?
Thanks!


Issue while rendering the HeatMap Chart for the 2nd time.

We have a feature that uses your HeatMap chart to display some data. I have a refresh icon that gives a chart preview after selecting the values. Thereafter, Every time when I change the xAxis and yAxis values from the drop-down, I am trying to re-render the chart to preview it. But, I am getting the below error.

container.ts:92 Uncaught TypeError: Cannot read property 'filter' of undefined
at Group.Container.getBBox (container.ts:92)
at MatrixLegend.getBBox (legend.ts:108)
at padding.ts:95
at each (each.ts:11)
at PaddingController.processOuterPadding (padding.ts:93)
at HeatmapLayer.ViewLayer.getViewRange (view-layer.ts:705)
at HeatmapLayer.ViewLayer.init (view-layer.ts:248)
at HeatmapLayer.Layer.render (layer.ts:110)
at HeatmapLayer.ViewLayer.render (view-layer.ts:295)
at plot.ts:222
at each (each.ts:11)
at Heatmap.BasePlot.eachLayer (plot.ts:226)
at Heatmap.BasePlot.render (plot.ts:222)
at default_1. (index.js:28)
at helper.js:17

v1 has so many bugs, so I start v2 version.


Move shell package from libmachine to crc

This is the only location where this package is used.

I added the error from AppVeyor. I guess it's an error due to cygwin or it is launched (cmd instead of powershell?).

/retest

Funny, someone pinged me to merge this https://github.com/docker/machine/pull/4788#issuecomment-734809216
I guess we should include it :)


New login flow on Kick

Kick has updated its login flow, replacing direct use of kick-token-provider with CSRF requests. Could you update the library to support this new flow?

Fixed and updated on npm. Cheers!


Using a constant instead of string magic

IdentityServer4 is feature complete. All new feature work is happening in our new organization. This means we can only accept bug fix PRs.
What issue does this PR address?
small fix in documentation
Does this PR introduce a breaking change?
no

Thanks - I prefer the strings to actually see what you get....

Thanks - I prefer the strings to actually see what you get....

it makes sense, but on the other hand, modern IDEs deal with it as well


CpModel.AddAllowedAssignments return value

The documentation for AddAllowedAssignments in the ortools.sat.python.cp_model.CpModel class says:
    Returns:
      An instance of the Constraint class.

But, the function returns None. Looks like a Constraint object is created but just not returned.
Version: ortools==6.9.5824

Yes, code seems to return nothing
src:
https://github.com/google/or-tools/blob/d44fb1b423f9d6658c142c041143a4f54b5106d3/ortools/sat/python/cp_model.py#L671-L707

Added a pull request to fix this: https://github.com/google/or-tools/pull/910

I fixed it on my side.
Thanks for the report.


fix: Update typescript-eslint

Previous typescript-eslint version didn't support TS v5.0 syntax (we had none, but it was giving a warning).

Codecov Report
Patch and project coverage have no change.

Comparison is base (3d37d87) 88.95% compared to head (44bcee8) 88.95%.

:exclamation: Current head 44bcee8 differs from pull request most recent head 498ddfa. Consider uploading reports for the commit 498ddfa to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##            alpha    #5467   +/-   ##
=======================================
  Coverage   88.95%   88.95%
=======================================
  Files          70       70
  Lines        2382     2382
  Branches      624      624
=======================================
  Hits         2119     2119
  Misses        218      218
  Partials       45       45

Impacted Files
Coverage Δ

packages/query-core/src/queryClient.ts
96.93% <ø> (ø)

packages/query-core/src/queryObserver.ts
86.12% <ø> (ø)

packages/query-persist-client-core/src/persist.ts
40.42% <ø> (ø)

packages/react-query/src/suspense.ts
100.00% <ø> (ø)

packages/solid-query/src/createBaseQuery.ts
69.31% <ø> (ø)

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


Change ReturnIfFailed to ThrowIfFailed in Python\device.cpp

I find that device.cpp uses ThrowIfFailed to handle errors, but I used ReturnIfFailed in my last PR. I am so sorry for that and now change it to align, please help to take a look! Thanks very much! @adtsai

A soft ping~thanks! @adtsai