anisotropic remeshing

What would it take to implement the anisotropic remeshing similar to ACVD?

Probably a bit of work as I'd have to go over the algorithm again.  The paper I used to reference isn't out there, do you know where I could find it?

Are you talking about ACVD?
here are the links for the three papers mentioned in ACVD repo.
https://hal.archives-ouvertes.fr/hal-00537025/document
https://hal.archives-ouvertes.fr/hal-00534535/document
http://www2.imm.dtu.dk/projects/MeshMed/2011/MeshMed2011Proceedings.pdf (starting at page 176)

I'm not seeing references to anisotropic remeshing in the referenced papers.  pyacvd currently implements the uniform remeshing algorithm using voronoi tessellation which is nearly identical to that in ACVD.  I'd have to go through his code (which would take quite some time) to figure out exactly how he implemented anisotropic remeshing.
Currently, I think I've only implemented isotropic (uniform) remeshing, though there is an option to increase the density of the mesh nearby areas of high curvature.

Essentially that is anisotropic remeshing. “Increase the density at areas of high curvature” I didn’t see where this option is in pyavcd. In acvd there was an option to specify 0 for uniform and higher to increase the density as a function of curvature.

I'll have to add that in.  Let me see if I can get an update over the weekend.

Took a look at this again today and it's not something I'll be able to easily implement.  pyacvd really takes only a tiny subset of the acvd code and implements that within cython.  I'm considering just wrapping the acvd interface with a small interface file to provide a python interface to the actual acvd code, but I'm quite busy at the moment and this might take a while to accomplish.


opnsense theme (no expansion delay / animation)

deleted expansion delay / animation -> https://github.com/opnsense/core/issues/2554
sidebar toggle-button ->  animation definition is not needed anymore

Merged, thanks!
This is great. But there is still a third-level animation going on :)

@fichtner when I have fixed it I will merge it with the open pr. I do the same then for tukan and cicada too

looks good now, communication error on my side. it's second level actually. depends on how you look at it. all good :)


New throwIfResponseIsError hook

We previously removed didReceiveResponse which let you override the main "is it an error or not" logic. This restores it in an error-specific way. This means you can throw errors even on 200s if you want (or vice versa).
This also changes the errorFromResponse hook to take options instead of a single argument, in case you want the error to reflect more data.
One negative change is you can no longer prevent parseBody from being called, though you can always override parseBody to do less.
Fixes #32.

This does conflict a bit with #110, sorry.
I didn't update README because the original hook wasn't documented. At some point I think you do need to assume that people who want to customize by overriding protected methods will just read the source...


Fast-RTPS Fails to Compile on CentOS 7

It looks like Fast-RTPS fails to compile on CentOS 7 due to a call to std::put_time() inside src/cpp/log/Log.cpp. This is because put_time wasn't implemented until Gcc 5.0 according to this bug. Unfortunately, CentOS 7 ships w/ Gcc 4.8.5 and upgrading may not be an option for all users.
I realize that put_time is part of C++-11, however, CentOS / RHEL are very popular OS's that may be worth supporting. Is there any chance there is an alternative implementation that you will accept to get around this issue?
This particular method appears to be pretty innocuous. I will take a look at an alternative implementation and open a PR. Thanks

Hi @jml1795
We will discuss this issue internally once we release version 1.8.0. But our first thoughts are focused on don't step back in this kind of issues.
Advance user shouldn't have problems upgrading their GCC, installing different versions if several are needed or installing different compilers like clang. I guess you understand that fixing an already fixed bug in a compiler due to users that don't want to upgrade isn't worth for us.
Additionally, this kind of users is always able to modify the code as you did to meet their requirements.
In any case, as I mentioned at the beginning, we will talk about it.
Thank you very much, best regards.

@LuisGP Understood. I appreciate your consideration and the team's efforts w/ fast-rtps.

FYI, I have Fast-RTPS 1.7.2 compiling just fine on CentOS 7.
Two things I've noticed:

CMake 2 doesn't seem to be sufficient to generate the build environment. Need CMake 3 (don't remember if it was in the EPEL repo). Don't think this is adequately captured in the eProsima docs.

Yes, the default compiler is old. But you can easilly grab a new one via devtoolset.

https://www.softwarecollections.org/en/scls/rhscl/devtoolset-6/
Based on these two points, 1.7.2 built just fine for me.

We decided to not apply patches for this kind of issues. As mentioned, you can upgrade your GCC or install clang if you prefer.


Fix the extra white space which is there below the carousel at homepage

@swapnilsparsh I would like to work on this issue.

I would like to contribute to this issue, am a part of GSSoC'21

I would like to work on this issue, I am GSSOC 2021 participant.

@saaiswetha and @medhavi11
You can start your work and soon I will be adding the level tag.

there are no white spaces below the carousel while viewing in desktop.

@swapnilsparsh Have submitted a PR, do review it and let me know in case of any changes.

@swapnilsparsh I have submitted a PR, do review it and let me know in case of any changes.

@sakshikhachane Please assign this issue to me . I am a GSSOC'21 participant .

Hi I am a Gssoc'21 participant and would like to work on this issue , I have experience in css and js , please assign me this issue

@simranbhalla3 Go ahead with this issue. Happy learning:)

@sakshikhachane  @swapnilsparsh  can i work on this ?

@sakshikhachane @swapnilsparsh can i work on this ?

Sure

@swapnilsparsh  @sakshikhachane  there is no white space probelm see however the gif is going below the navbar so may i correct it

@swapnilsparsh @sakshikhachane there is no white space probelm see however the gif is going below the navbar so may i correct it

OK


Update README.md

correct import

@RGBmaia, The import should "from pyzerox" (different from the js sdk) as we recently update the package name in our the last release on pypi: https://github.com/getomni-ai/zerox/releases/tag/v0.1.0
The package source - "zerox" folder was renamed to pyzerox, so the imports are correct: https://github.com/getomni-ai/zerox/tree/eaf13b2daab7e88e2c8648c1d9bc2a2e7d47b938/py_zerox
@RGBmaia, are you facing issues in importing package?

@tylermaran , I found out the issue, the package hosted in pypi is still the 0.0.3 version and that version used the older import name, could you push the latest releases to pypi.
@RGBmaia, for now you can uninstall pyzerox and reinstall the latest version via the git repo using pip install git+https://github.com/pradhyumna85/zerox.git


Asynchronously import / export server middleware

Is your feature request related to a problem? Please describe.

I just started using nuxt but I have a problem with not being able to asynchronously use server middleware. I am using the serverMiddleware option to make a backend server with TypeScript and ExpressJS, but I have an asynchronous function that needs to finish before the handler function can be used.
Describe the solution you'd like

Being able to asynchronously import server middleware will make it a lot easier to use ExpressJS or any other http server / server middleware that has asynchronous tasks that need to be done so that the server middleware will work properly. Please look at my example below for a better understanding of the issue.
Say you want to add a server middleware to /api and it should be handled by express, then you could do this:
./nuxt.config.js:
export default {
  serverMiddleware: [
    {
       path: '/api',
       handler: './api/app.ts'
    }
  ]
}

./api/app.ts:
import express from 'express';

const app = express();

app.use(function (req, res, next) {
  res.status(200).send('Hello');
});

export default app;

Now I propose adding the option to return a promise that resolves to a server middleware:
./api/app.ts
import express from 'express';
import { ServerHandle } from 'connect';

const app = express();

app.use(function (req, res, next) {
  res.status(200).send('Hello');
});

// A function that returns a promise which can resolve
// to a server middleware
function someAsyncFunction(): Promise<
  ServerHandle | { path: string; handler: ServerHandle }
> {
  return new Promise((resolve) => {
    setTimeout(() => {
      resolve(app);
    }, 1000);
  });
}

// Export promise
export default someAsyncFunction();

Describe alternatives you've considered

I have looked at using nuxt programatically but I think that using server middleware works better. Importing nuxt also doesn't work very nicely with TypeScript.
Additional context

https://github.com/nuxt/nuxt.js/blob/4db7e432df6e0980f4f6324d374491323801c0c1/packages/server/src/server.js#L132-L134
It will require making the useMiddleware function support promises. It won't require much work to make the setupMiddleware function support it because it is already async.
https://github.com/nuxt/nuxt.js/blob/4db7e432df6e0980f4f6324d374491323801c0c1/packages/server/src/server.js#L71
The useMiddleware function should be able to resolve a promise because it is what adds the handler to the connect server:
https://github.com/nuxt/nuxt.js/blob/4db7e432df6e0980f4f6324d374491323801c0c1/packages/server/src/server.js#L274-L277
So if the server middleware is a promise, then it should wait for it to be resolved.
https://github.com/nuxt/nuxt.js/blob/4db7e432df6e0980f4f6324d374491323801c0c1/packages/server/src/server.js#L174-L183
It will require modifying the _normalizeMiddleware function to return a promise and await the middleware argument if it is a promise.
Could make just the server middleware support promises by adding a function called useAsyncMiddleware, that way it is clear that this function is intended to be used with a promise. If you want to programatically use nuxt to add a server middleware that returns a promise then you could use this function too.
Example modifying the Server class:
  // ...

  async setupMiddleware() {
    // ...

    for (const m of this.options.serverMiddleware) {
      await this.useAsyncMiddleware(m)
    }

    // ...
  }

  async useAsyncMiddleware (middleware) {
    const { route, handle } = async this.resolveAsyncMiddleware(middleware)
    this.app.use(route, handle)
  }

  async resolveAsyncMiddleware (middleware, fallbackRoute = '/') {
    // Ensure middleware is normalized
    middleware = await this._normalizeMiddleware(middleware)

    // Fallback route
    if (!middleware.route) {
      middleware.route = fallbackRoute
    }

    // Resolve final route
    middleware.route = (
      (middleware.prefix !== false ? this.options.router.base : '') +
      (typeof middleware.route === 'string' ? middleware.route : '')
    ).replace(/\/\//g, '/')

    // Strip trailing slash
    if (middleware.route.endsWith('/')) {
      middleware.route = middleware.route.slice(0, -1)
    }

    // Assign _middleware to handle to make accessible from app.stack
    middleware.handle._middleware = middleware

    return middleware
  }

  async _normalizeMiddleware (middleware) {
    // Resolve promise
    if (isPromise(middleware)) {
       middleware = await middleware;
    }

    // Normalize plain function
    if (typeof middleware === 'function') {
      middleware = { handle: middleware }
    }

    // If a plain string provided as path to middleware
    if (typeof middleware === 'string') {
      middleware = this._requireMiddleware(middleware)
    }

    // ...
  }

  // ...

This shouldn't break anything because it only adds extra functionality to the server middleware setup. Though functions that use the _normalizeMiddleware function should either return a promise, or an async variant of them should be made. Could even make a function called _normalizeAsyncMiddleware to not break other functions.

This is now implemented with defineLazyEventHandler in Nuxt 3/Nitro.


Correct publish date in Section Foreword, as soon as known.

This will be something that @MaryLJ will do as part of the publication for formal ballot.

@MaryLJ we will need to do similar balloting of this as with the HIE-Whitepaper, as we are now only writing this in markdown.


Update to ember cli 2.16

Ran yarn upgrade
Update ember-cli to 2.16.2
Update blueprints for ember-cli 2.16.2

Apparently the latest updates broke ember-cli-github-pages. This won't block the release, but I filed #66 to track as I won't have time to do any more digging after spending 10 minutes trying to get it to work just now.


Suggestions: see list

Add command !info (used in thread gives info of the user who opened the thread) should give:

Basic info like from zeppelin
Current avatar as well as server avatar from the main server for the user (can separate into !avatar) command.
Custom statuses (as well as bios, unless we can't request those from the API yet)

Add integration with zep so you can bring up cases from the main server for the user with !cases through modmail.

this can be done by using a bot token (doesnt matter, just has to be valid) to call /api/users/|D (HTTP GET)


Convert "Status" field in "Sales Header"/"Purchase Header" into ENUM

Please convert the "Status" field in the Sales Header (and Purchase Header) into an enum.
Verify that all references to that field are explicite ( "=" or "IN" operator) and not implicite ("<", ">", NOT IN)

Done


Fix KafkaTableProviderIT

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @suztomo

Run SQL PostCommit

I see "SQL Post Commit Tests" still failed:
16:52:38 > Task :sdks:java:extensions:sql:integrationTest
16:53:19
16:53:19 org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT > testFakeNested[0] FAILED
16:53:19     java.lang.AssertionError at KafkaTableProviderIT.java:252
16:53:50
16:53:50 org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT > testFakeNested[1] FAILED
16:53:50     java.lang.AssertionError at KafkaTableProviderIT.java:252
16:54:31
16:54:31 org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT > testFakeNested[2] FAILED
16:54:31     java.lang.AssertionError at KafkaTableProviderIT.java:252
16:54:37
16:54:37 org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT > testFake2[3] FAILED
16:54:37     java.lang.AssertionError at KafkaTableProviderIT.java:158
16:54:42
16:54:42 org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT > testFakeNested[3] FAILED
16:54:42     org.apache.beam.sdk.extensions.sql.impl.ParseException at KafkaTableProviderIT.java:230
16:54:42         Caused by: org.apache.beam.vendor.calcite.v1_20_0.org.apache.calcite.tools.ValidationException at KafkaTableProviderIT.java:230
16:54:42             Caused by: java.lang.IllegalArgumentException at KafkaTableProviderIT.java:230
16:55:18
16:55:18 org.apache.beam.sdk.extensions.sql.meta.provider.kafka.KafkaTableProviderIT > testFakeNested[4] FAILED
16:55:18     java.lang.AssertionError at KafkaTableProviderIT.java:252
17:01:03
17:01:03 55 tests completed, 6 failed

https://ci-beam.apache.org/job/beam_PostCommit_SQL_PR/491/console

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit


List of bugs & PRs related to Animations: Additive blending ; running blend spaces in parallel

May be resolved but needs to be tracked on Godot Engine org.


Error during upsert - Document store document-stores not found

Describe the bug
Running upsert from within a chatflow seems to work..
But doing it through document stores errors.
Jumping onto the pod and viewing the logs, I can see the .pdf files are being sent to different locations:
/data/storage/0e343de5-1c95-42d3-9d89-1504b8b29870/ Works as expected and is the chatflow file upload location.
/data/storage/docustore/6410ed8e-2ef6-4f6f-891c-96415f7e720a/ Does not work and is the document-stores upload location.
I can see it's meant to be doing:
curl 'https://host.com/725e5c87-7165-4b94-8351-4aca6d7f132d/llm-tool-flowise-master-flowise/api/v1/document-store/store/6410ed8e-2ef6-4f6f-891c-96415f7e720a'

But what it's actually calling for some reason:
curl 'https://host.com/725e5c87-7165-4b94-8351-4aca6d7f132d/llm-tool-flowise-master-flowise/api/v1/document-store/store/document-stores'

So for no reason at all, the storeId in the browser is being set to document-stores instead of the actual storeId, no idea why yet tho.
To Reproduce
Steps to reproduce the behavior:

Go to document-stores, create new store, add a file and process it.
Click on upsert
See error

Oh snap!
The following error occured when loading this page.
Status: 500
Error: documentStoreServices.getDocumentStoreById - Error: documentStoreServices.getDocumentStoreById - Document store document-stores not found
Please retry after some time. If the issue persists, reach out to us on our Discord server.
Alternatively, you can raise an issue on Github.

Expected behavior
Upserts document correctly
Screenshots

Flow
N/A
Setup
Helm/K8s/Docker

Installation [e.g. docker, npx flowise start, pnpm start]
Flowise Version [e.g. 1.2.11]
OS: [e.g. macOS, Windows, Linux]
Browser [e.g. chrome, safari]

Additional context
Using legacy mode doesn't help. Tested with multiple different pdf files, all with same error

Is this via API or from the UI?

This is via the UI.
I've done a ton of debugging on this as it makes no sense at all, but I'm also not that familiar with react.
The issue again is basically when clicking on the upsert chunks button on any document loader type (tried multiple), it redirects the call to
https://host.com/725e5c87-7165-4b94-8351-4aca6d7f132d/llm-tool-flowise-master-flowise/api/v1/document-store/store/document-stores
However we can see that the button should be making this call.
In src/packages/ui/src/views/docstore/DocumentStoreDetail.jsx
console.log("ds:", documentStore)
navigate(`/document-stores/vector/${documentStore.id}/${loader.id}`)

The document store when clicking the button is correct in logging, however somewhere during the navigate the URL get's altered.
ds: {id: '3c74933a-dc08-4199-8dd2-49da9c87f08f', name: 'test-store', description: '', loaders: Array(1), whereUsed: Array(0), …}

In src/packages/server/src/controllers/documentstore/index.ts I've added some logging and can see that the Request from express is already incorrect.
const getDocumentStoreById = async (req: Request, res: Response, next: NextFunction) => {
    try {
        if (typeof req.params.id === 'undefined' || req.params.id === '') {
            throw new InternalFlowiseError(
                StatusCodes.PRECONDITION_FAILED,
                `Error: documentStoreController.getDocumentStoreById - id not provided!`
            )
        }
        console.log("updating get: ", req.params)
        const apiResponse = await documentStoreService.getDocumentStoreById(req.params.id)
...

As the logs below show me clicking on the document loader, then on upsert chunks button.
updating get:  { id: '3c74933a-dc08-4199-8dd2-49da9c87f08f' }
store ID 3c74933a-dc08-4199-8dd2-49da9c87f08f
updating get:  { id: 'document-stores' }
store ID document-stores

What happens between these two steps, and where does the Req come from that leads to storeID being set incorrectly?


Getting negative values for t_done with angularjs plugin

Hi,
I am using boomerangjs with angular plugin. My build includes rt, bw and angular plugins. The version is latest from git. For specific angular soft navigation changes, i am getting t_done as negative on the beacon received back.  Please find below one of the events converted to key/value pairs. Its not always but only for specific soft navigation urls.  I am using it from a local browser, so i know the response is fairly quick but don't understand how it can be negative.
Mon Jul 25 11:11:53 2016 :  rt_start=manual v=0.9 vis_st=visible ua_plt=Linux_x86_64 ua_vnd=Google_Inc. bw=44368532 bw_err=24730676.15 lat=13 lat_err=6.96 bw_time=1469425309 nu=http://<IP_ADDRESS>/app/xxxxx/xxxxxxx rt_tstart=1469425312313 rt_bstart=1469425305236 rt_end=1469425304810 t_done=-7503 r=http://<IP_ADDRESS>/XYZ u=http://<IP_ADDRESS>/app/xxxxx/xxxxxxx-*?g(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now%2Fw,mode:quick,to:now%2Fw))&a(tab:indexedFields) http_initiator=spa
I would like to understand on what conditions, t_done can get back a negative value? I am seeing this behaviour only while using it with angular plugins.
-Raja

Moved the issue to the new dev location https://github.com/SOASTA/boomerang/issues/100
Thanks
-Raja

Please also close the issue here.


Fixed infinite loop when the view appears

I've noticed a very high CPU usage when the view appears and found an infinite loop:
graph LR
id1("viewDidLayoutSubviews()")
id2("updateUI()")
id3("view.layoutIfNeeded()")

id1-->id2
id2-->id3
id3-->id1

That's a very important issue, thanks a lot for pointing this one out. Unfortunately, I need to call .layoutIfNeeded multiple times (e.g. when I change the size of the Split View screen on iPad). With the flag set to false, the UI wont be adjusted anymore.

Thanks, I've fixed this issue. Are there any other instances where you need to update the UI?

These would be all instances, thanks. On another note, I suggest moving needsUIRefresh = true from traitCollectionDidChange(_:) within the scope of viewWillTransition(to:with:) and I can merge and close this issue: This fixes the size class change issues in all use cases while preventing an infinite loop on viewDidLayoutSubviews().
override func viewWillTransition(to size: CGSize, with coordinator: UIViewControllerTransitionCoordinator) {
    super.viewWillTransition(to: size, with: coordinator)
    needsUIRefresh = true
}

Your help on this one is much appreciated. This was a critical issue that I completely oversaw while updating the framework for the iPad.

Sure, I've added the second method. Thanks for merging!


The three link examples on the page don’t link to anything

These links are missing an href attribute:
Just add the status code you want to the URL, like this:
httpstat.us/200

for example
httpstat.us/random/200,201,500-504.

like this:
httpstat.us/200?sleep=5000

Should be:
Just add the status code you want to the URL, like this:
httpstat.us/200

for example
httpstat.us/random/200,201,500-504.

like this:
httpstat.us/200?sleep=5000

I wanted to make a pull request but it turns out these links are not HTML in the code but generated by some syntax I don’t recognise:
https://github.com/aaronpowell/httpstatus/blob/29baee85ab420c6515303f732947636cc8bb7fdd/src/Teapot.Web/Pages/Index.cshtml#L10
https://github.com/aaronpowell/httpstatus/blob/29baee85ab420c6515303f732947636cc8bb7fdd/src/Teapot.Web/Pages/Index.cshtml#L30
https://github.com/aaronpowell/httpstatus/blob/29baee85ab420c6515303f732947636cc8bb7fdd/src/Teapot.Web/Pages/Index.cshtml#L36

Nice catch - that'd be a hold-over from before it was using minimal API and I don't think those HtmlHelpers did what was required anymore so I've removed them for standard  tags.


RangeSlider inside ScrollView unresponsive

If you put a Slider inside a ScrollView, then touching the slider adjusts the slider.
If you put a RangeSlider inside a ScrollView, then touching the slider attempts to scroll the scrollview.
This is tested on Windows only.
This used to be an issue with Slider https://bugzilla.xamarin.com/show_bug.cgi?id=21478 . Perhaps it would be a similar fix for RangeSlider?
(This is using 0.6.18)

@charlesroddie I can't reproduce the issue. Do you have a sample project?

This is a UWP issue. It happens in the simplest project with a rangeslider inside a scrollview:
https://github.com/charlesroddie/RangeSliderSample
This does not affect mouse drags, only touch.
Tested on a Surface Pro 2 and also on an external touchscreen.

@halkar Any ideas about how to fix this on UWP?

Oh, sorry. I forgot about this one. Will check it today or tomorrow.

@charlesroddie sorry. I still can't reproduce the problem. Which device are you using for testing?

Tested on Surface Pro 2 and on a Win10 desktop with an old touchscreen. Mouse works but touch does not inside scrollviews.

I've tested it on my Dell XPS with touchscreen and can't reproduce the issue.


CH EMED: Fixed Values for system in codings don't allow multiple codings (annatina (based on Ticket by Michaela from Projectathon 2020))

ch.fhir.ig.ch-emed#0.2.0 /StructureDefinition-ch-emed-medication-medicationstatement.html
In different codings are the system as "fixed Value" defined. This way multiple codings with different systems are not allowed. This should be changed, so that it is possible.
e.g.: Medication.code.coding
http://fhir.ch/ig/ch-emed/StructureDefinition-ch-emed-medication-medicationstatement.html
Where this issue is present everywhere, needs to be reviewed.
annatina (based on Ticket by Michaela from Projectathon 2020)

yes, needs to be reviewed

http://localhost:52330/output/Bundle-MedicationCard-DifferentAuthors.json.html has a local code/local system in the medication and this works (slice is open). do we have an example where it does not work @ziegm ?

This issue has already been solved: https://github.com/ehealthsuisse/ch-emed/issues/6


Please improve messaging when calling "brew desc -s XXX"

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
Currently if you call "brew desc -s XXX" it will return like this. It makes it seem as if there are no results. I will use the term "radio" in my examples.
MacPro:~ mike$ brew desc -s radio
Warning: Calling brew desc is deprecated! Use brew desc --eval-all or HOMEBREW_EVAL_ALL instead.
==> Formulae

==> Casks

This is confusing because this used to deliver results, but with the exact same deprecation message. But now it seems as if there are no results for "radio", when there are certainly are.
If "brew desc -s XXX" feature is fully removed, you should not return as if there might be results (i.e, having the Formulae and Casks headers).
Instead, you should return a message such as "Warning: Calling brew desc is removed! Use brew desc --eval-all or HOMEBREW_EVAL_ALL instead". Fully omit the other lines.
Also, if the user is using the -s flag, then the suggestion given is not very helpful. A naive user, having run "brew desc -s radio", and given your suggestion, may immediately then try this:
MacPro:~ mike$ brew desc --eval-all radio
Error: No available formula with the name "radio". Did you mean gradio or rtaudio?

Instead, brew should know that the -s flag was used, and suggest that the user try "brew desc --eval-all --search".
In that case, then the user might try the following invocation, and would experience success:
MacPro:~ mike$ brew desc --eval-all --search radio
==> Formulae
airspy: Driver and tools for a software-defined radio
airspyhf: Driver and tools for a software-defined radio
get_iplayer: Utility for downloading TV and radio programmes from BBC iPlayer
gnuradio: SDK for signal processing blocks to implement software radios
gradio: GTK3 app for finding and listening to internet radio stations
hackrf: Low cost software radio platform
hamlib: Ham radio control libraries
inspectrum: Offline radio signal analyser
libbladerf: USB 3.0 Superspeed Software Defined Radio Source
liquid-dsp: Digital signal processing library for software-defined radios
luaradio: Lightweight, embeddable flow graph signal processing framework for SDR
rtl_433: Program to decode radio transmissions from devices
urh: Universal Radio Hacker

==> Casks
chirp: (CHIRP) Tool for programming amateur radio
cubicsdr: (CubicSDR) Cross-platform software-defined radio application
fldigi: (fldigi) Ham radio digital modem application
flrig: (flrig) Ham radio rig control
gqrx: (Gqrx) Software-defined radio receiver powered by GNU Radio and Qt
gridtracker: (GridTracker) Warehouse of amateur radio information presented in an easy to use interface
jt-bridge: (JT-Bridge) Acts as a bridge between WSJT-X and ham radio logging application
macloggerdx: (MacLoggerDX) Ham radio logging and rig control software
pandora: (Pandora) Desktop client for the Pandora web radio service
radio-silence: (Radio Silence) Network monitor and firewall
remotehamradio: (RemoteHamRadio) Desktop console app for RemoteHamRadio service
tunein: (TuneIn) Free Internet Radio

What is the motivation for the feature?
To make brew as easy to use as possible for all users regardless of skill level.
How will the feature be relevant to at least 90% of Homebrew users?
It is certainly possible that 90% of former users of "brew desc -s" would appreciate these clarifications.
What alternatives to the feature have been considered?
Bringing back "brew desc -s" as it was, but this seems unlikely.

It sounds like there are two things here.

Some parts of the brew desc command are deprecated and don't return the expected results without the --eval-all flag. This is unfortunately in line with the expected behavior and will be completely disabled with a warning at the next major or minor release (https://github.com/Homebrew/brew/pull/14382). Note that this was originally deprecated for security reasons (more discussion https://github.com/Homebrew/brew/issues/14010).
The messaging should be clearer with deprecation/disable warnings and include flags and options. This is a bit bigger of an ask but something I think we should keep in mind. In this case, the brew desc doesn't have too many options so it sounds plausible but for other commands having variable deprecation/disable warnings for each set of options sounds a lot more difficult. We wouldn't want to recommend an alternative that is also invalid.

Some parts of the brew desc command are deprecated and don't return the expected results without the --eval-all flag. This is unfortunately in line with the expected behavior and will be completely disabled with a warning at the next major or minor release

This will definitely help the situation. Because deprecation does not mean "removal" (it means something more like "pending removal"), the behavior right now makes it seem as if there are no search results for "brew desc -s XXX", no matter what one actually puts for "XXX".
I really thought for a few minutes that there were no results for "brew desc -s radio", but I distinctly remembered finding the desired package (gqrx) this way a couple of years ago. (I can never remember gqrx).
As an aside, I really do think there is a lot of value in being able to search the package descriptions easily. Certainly a safer way could be established to do so; even a web service would be acceptable. Did brew desc -s XXX really run (Ruby?) code from every repository while conducting the search?

Crappy quick example of how a web service might return results:
{
   "results" : {
      "formulae" : {
         "blahradioblah" : "This results appears because radio is in the name of the formula.",
         "gqrx" : "Description of a radio related thing."
      },
      "casks" : {
         "radioiswaves" : "Wow waves are neat.",
         "somecask" : "This cask does radio stuff. Wow!"
      }
   }
}

We will address this in the next release when they are disabled. Sorry for the pain!


Plan Metadata and Data Dictionary

We have metadata in the format that socrata expects for one product. We need to work backwards to derive a DCP base format, from which we'll generate the socrata metadata

because the feature would be helpful for testing metadata logic, I added "export as a shapefile" to the open Template DB enhancement issue https://github.com/NYCPlanning/data-engineering/issues/268


feat: support view original inscription

Refs: https://github.com/Magickbase/ckb-explorer-public-issues/issues/528

Please have a review @Daryl-L @PainterPuppets

Using search on the view original inscription page should stay on the current page and now returns the Rebase satrt status page.

Fixed.

The CSV Export related information at the bottom should be hidden, similar to https://pudge.explorer.nervos.org/inscription/0x1a865222f00d305dde4dae6c6c37c2c6b9a5d5bb2570e2e22e19fb232b655a9d

This feature was temporarily hidden before because the backend interface was still under development. Now that it has been developed, it can be displayed.

There is a problem with the icon adapting to the mobile terminal. Pay attention to the icon size and margins.

Fixed.


warpprb only works properly when there is a triangle mesh in the scene

I want to use the warpprb config instead of warp in a multiview setting, as it can model indirect illumination effects. However, it does not work properly when the scene only contains an SDF and no mesh. Strangely, it works properly when the scene contains a mesh, even if it is far away and not seen by any camera. Since adding a mesh to the scene greaterly slows down the JIT compilation of the CUDA backend, I really want to fix the issue and allow optimizing a scene that only contains an SDF.
How to reproduce:

Seems that the warpprb config is only used on the mirror-opt scene. I confirm it works properly on that scene:

python optimize.py mirror-opt --optconfig mirror-opt-hq --config warpprb --outputdir ./outputs --llvm --force

yields
https://github.com/rgl-epfl/differentiable-sdf-rendering/assets/25758401/ce0b8bd0-19c5-4942-9c42-2e18dd3ae14f

Changing the --optconfig from mirror-opt-hq from no-tex-12 also works:

python optimize.py mirror-opt --optconfig no-tex-12 --config warpprb --outputdir ./outputs --llvm --force

yields
https://github.com/rgl-epfl/differentiable-sdf-rendering/assets/25758401/3cdc11ae-d1bc-499e-853a-27ae7df73647
Note that three views are completely blocked by the wall.

Removing the <shape type="rectangle"> meshes in mirror-opt.xml (scene file at mirror-opt-2.zip) however, does not work properly

python optimize.py mirror-opt-2 --optconfig no-tex-12 --config warpprb --outputdir ./outputs --llvm --force

yields
https://github.com/rgl-epfl/differentiable-sdf-rendering/assets/25758401/2da82af6-6fca-4f12-8fb2-448ce114669c

Finally, if I do not remove the mesh shapes but put them at very high positions, it works properly even if no camera can see the rectangle shapes (scene file at mirror-opt-3.zip).

python optimize.py mirror-opt-3 --optconfig no-tex-12 --config warpprb --outputdir ./outputs --llvm --force

yields
https://github.com/rgl-epfl/differentiable-sdf-rendering/assets/25758401/7027ac78-8c46-4fb9-bc5e-c79ad22a49ac
Note
Some videos are shorter than others because I often encounter a crash
Assertion failed in /project/ext/drjit-core/ext/nanothread/src/queue.cpp:354: remain == 1

Thus, the optimization stops before running for full iterations.

Hi,
Thanks for the detailed bug report. I am not surprised that the warpprb is not so robust to many different scene configurations, this integrator was only used for this particular result in the paper.
I unfortunately don't have time right now to properly look at this. I would suggest to see if the integrator base class does something different if a mesh is together. There should be some logic to switch between using optix (when meshes are present) and the simple case when we only have an SDF.
Otherwise, you can also try using an LLVM variant, as the LLVM compiler is a lot faster than the Optix compiler.
For the last error (remain==1): are you using the latest Mitsuba/drjit? If not, can you try updating to their latest releases?

Thanks for your reply! I'm looking into the base ReparamIntegrator class for details.
For the last error (remain==1), I confirm that I am using the lastest pypi prebuilt mitsuba, drjit and fastsweep on Python 3.10.11 on Linux. Should I post an issue to the Mitsuba3 repo?
 ✗ pip list
Package         Version
--------------- --------
...
drjit           0.4.2
fastsweep       0.1.2
mitsuba         3.3.0
...

Posting an issue on the Mitsuba issue tracker only really makes sense if you can reproduce the problem in a more minimal example. Otherwise it would just be too difficult to debug. Does it also happen when running some of the tutorials?

Unfortunately, I only encounter this problem when running this project, and only in --llvm mode, not cuda mode. I will try to simplify the reproduction script.

I see. Yes in that case your best bet is to try to simplify the script further and further until you can isolate the problem.


separate wielder skills into "skills" and "startingskills"

convert.mjs now separates skills into startingSkills and skills
added WielderDTO.startingSkills field
render startingSkills in own table in pages/wielders/[type].tsx
removed "Command" from WielderStats.tsx since it's shown in the startingSkills

i forgot to run assetRipper prior to running the extractor


Rejecting this API request due to config loading error

After deploying the openapi.json and deploying an app to google app engine I'm getting an error in gae log console:
com.google.api.control.ConfigFilter init: Failed to load service
com.google.api.config.ServiceConfigException: Failed to fetch default config version for service 'myapplicationname.appspot.com'. No versions exist!
	at com.google.api.config.ServiceConfigSupplier.fetchLatestServiceVersion(ServiceConfigSupplier.java:181)
	at com.google.api.config.ServiceConfigSupplier.fetch(ServiceConfigSupplier.java:146)
	at com.google.api.config.ServiceConfigSupplier.get(ServiceConfigSupplier.java:131)
	at com.google.api.config.ServiceConfigSupplier.get(ServiceConfigSupplier.java:50)
	at com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:243)
	at com.google.api.config.ServiceConfigFetcher.fetch(ServiceConfigFetcher.java:41)

and at every request I'm getting the following error:
com.google.api.control.ConfigFilter doFilter: Rejecting this API request due to config loading error

There was no other problem, deployment of openapi.json went without problems:
Service Configuration [2020-07-25r0] uploaded for service [myapplicationname.appspot.com]

deployment of backend also succeeded:
File upload done.
Updating service [default]...
........................................................................................................................................................................................done.
Setting traffic split for service [default]...
...................................done.
Deployed service [default] to [https://myapplicationname.ew.r.appspot.com]

I have set up everywhere the project_id = myapplicationname, and I am deploying to this project.
When I am deploying to my dev project - myapplicationname_dev, everything works fine. The only difference is that at deployment I get different summary in gradle:
for "myapplicationname_dev" I get url without region:
target url: [https://myapplicationname_dev.appspot.com] - this one works

for "myapplicationname" I get url with region:
target url: [https://myapplicationname.ew.r.appspot.com] - for this one I'm getting above error

It appeared that my problems were related to lack of the gcloud permissions. This helped me:
https://stackoverflow.com/questions/42421042/com-google-api-config-serviceconfigsupplier-failed-to-fetch-default-config-ver
especially reference to:
https://cloud.google.com/endpoints/docs/frameworks/java/get-started-frameworks-java
gcloud services enable servicemanagement.googleapis.com
gcloud services enable servicecontrol.googleapis.com
gcloud services enable endpoints.googleapis.com

It was a surprise that after three years my production env ceased to work for 3 days... Interesting though I did not have such problems on dev env which is next to the prod and I'm using the same gcloud console?


Redirect to previous page after editing group description

The group edit page can get opened from multiple places:

Group overview page (in sidebar, the "three dots menu")
Group description page (one of the action buttons)
If no store or group location is set: group map in sidebar

@mr-kojo I updated the list (searching for name: 'groupEdit').
I guess the logic should be as follows:

if there is a previous page, redirect to it
if not, go to group home page (group wall)

With this, we don't need to know about all the places where groupEdit gets opened.

I'll work on this one

I visited #999 again and came to the conclusion that router.go(-1) is not fitting here. Main problem is that it breaks "back button navigation".
This is how it should be:

user visits some group page and clicks edit
user makes a change and clicks save
user sees effects and wants to edit again, clicks back button
user is on group edit page again

#999 will break (4). Right now, (3) is slightly broken because the user may end up on a different page.
I see two solutions:

keep track of the previous route and router.push it
add more inline editing so that the user can stay on the same route while editing

I'd close this because of high complexity and no user requests.


When a container is restarted, first ~50 seconds of logs are lost

We noticed that first ~50 seconds of logs after a container startup are not captured.
For example:

I started a container at 12:50:00
After 50 seconds, Sumologic pods logs the following:

2017-02-15 12:50:42 +0000 [info]: following tail of /mnt/log/containers/my-pod-name-87d9f1b535e11c02690567e7b4bb65016346c263b683c96f720b90e52ca6982e.log

Logs between 12:50:00 and 12:50:42 are lost.

This is a showstopper for us. Not only we are loosing logs, but we are loosing the most important log entries (application startup). Crashing application are not showing any log!

Hi @mfornasa this repo used fluentd tail plugin. I suspect maybe the files are disappearing before the tail plugin can pick it up.
I wonder if there are some docker/kube settings we can tune to keep it around for longer or perhaps the better solution is to look at using the native fluentd driver as suggested in #9

@mfornasa  bc96bcc should fix this issue.  I need to work on getting this pushed to Dockerhub though.  Will update once available.

@mfornasa: new image with the fix is now available in docker hub

@frankreno seems good. Thanks!


Whack a mole game

The game is set in a grid of holes, and the objective is to “whack” or hit the moles that randomly pop up from these holes.
Tech-stack used: HTML,CSS and javascript.
@kunjgit please assign me this task under GSSOC'24.
Thankyou!

Hey @Sunainabhave !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Sunainabhave ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Sorry, why is this issue closed? i couldnt understand
is there a game already? i am unable to reach you out on discord.
Please let me know how to reach you out.
please help me out as i am very new to open source contribution


Error while running the sourceNodes lifecycle when I attempt to change a field type

This seems like a bug, where gatsby-source-prismic throws the following error on build after I changed a field on a custom type in my schema JSON file from key text to rich text. Running gatsby clean does not help.
The app builds fine when that field is removed, or reverted to the old type, or simply renamed but with the new type.
gatsby-source-prismic v3.3.6
"gatsby-source-prismic" threw an error while running the sourceNodes
lifecycle:

e.reduce is not a function

  61 | }
  62 |
> 63 | const buildAll = async (
     |               ^
  64 |   pluginOptions: PluginOptions,
  65 |   gatsbyContext: SourceNodesArgs,
  66 |   typePaths: TypePath[],

File: node_modules/gatsby-source-prismic/src/gatsby-node.ts:63:15

  TypeError: e.reduce is not a function

  - prismic-dom.min.js:1 Function.value
  - [project]/[prismic-dom]/dist/prismic-dom.min.js:1:9753

  - prismic-dom.min.js:1 Object.t.default

[project]/[prismic-dom]/dist/prismic-dom.min.js:1:17350

  - prismic-dom.min.js:1 Object.asHtml

[project]/[prismic-dom]/dist/prismic-dom.min.js:1:4903

  - environment.node.ts:170 env
    [project]/[gatsby-source-prismic]/src/environment.n
ode.ts:17    0:3

  - documentsToNodes.ts:89 env
    [project]/[gatsby-source-prismic]/src/documentsToNo
des.ts:89    :77

  - documentsToNodes.ts:196
    [project]/[gatsby-source-prismic]/src/documentsToNo
des.ts:19    6:65

  - utils.ts:100 key

[project]/[gatsby-source-prismic]/src/utils.ts:100:5

  - Array.map

  - utils.ts:101 normalizeObj

[project]/[gatsby-source-prismic]/src/utils.ts:101:40

  - documentsToNodes.ts:196 normalizedData
    [project]/[gatsby-source-prismic]/src/documentsToNo
des.ts:19    6:36

  - documentsToNodes.ts:211 doc
    [project]/[gatsby-source-prismic]/src/documentsToNo
des.ts:21    1:9

  - environment.node.ts:29 createContentDigest
    [project]/[gatsby-source-prismic]/src/environment.n
ode.ts:29    :3

  - Array.map

  - documentsToNodes.ts:202 L
    [project]/[gatsby-source-prismic]/src/documentsToNo
des.ts:20    2:9

  - gatsby-node.ts:63
    [project]/[gatsby-source-prismic]/src/gatsby-node.t
s:63:15

  - task_queues:96 processTicksAndRejections
    node:internal/process/task_queues:96:5

This is the only change:

Hi @tjjjwxzq,
This happens because the documents in your Prismic repository probably are still formatted as Key Text rather than Rich Text. Key Text is returned as a string while Rich Text is an array of objects.
The plugin expects the fields' values to be Rich Text according to the schema and so it converts it to HTML and text. This will throw an error when it is given a string, however.
When converting from Key Text to Rich Text (and vice versa), you will need to go into each document and resave the contents. The easiest way to do this is to type a character into a field and then remove that character. This enables you to save a new version of the document where the Rich Text field is now properly updated.

Thanks for the explanation! That makes sense...though it's not a very obvious gotcha 🙃

You're welcome! I wish the content would be converted for you automatically in Prismic, but unfortunately that is not how it works right now. That certainly can be confusing, however.


fix(command-deploy): update alias description

Summary
Addresses docs-related feedback from a couple of different Support Forums posts:

https://answers.netlify.com/t/using-alias-is-deploying-to-production-without-prod/33975
https://answers.netlify.com/t/headers-not-read-for-alias-deploy-from-netlify-cli/40264

Addresses docs-specific concerns in https://github.com/netlify/cli/issues/1984
Test plan
View the docs in the branch.
Note This PR addresses docs feedback, but the referenced issue contains suggestions for CLI warnings as well.

I noted that I need to build the docs, but I ran npm run docs and got some errors including`Error: Cannot find module 'markdown-magic'.

I noted that I need to build the docs, but I ran npm run docs and got some errors including`Error: Cannot find module 'markdown-magic'.

The docs are generated from another sub project, you'll need to install its' dependencies via npm run site:build:install

Should have waited to get your 👍🏻 before merging @overlordofmu; thanks for taking a look.


Bundle pdf.js with Rollup

Reasons:

https://github.com/Rich-Harris/bundler-comparison#results

An analysis on bundlers:

https://twitter.com/jaffathecake/status/1277879396074995714

There doesn't seem to be anywhere near enough context/information provided here, to make this an actionable/valid issue for the PDF.js project, considering that replacing the entire build system would be a very significant undertaking (and definitely less of a priority compared to e.g. fixing rendering bugs).
All-in-all, the following paragraph from https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md seems relevant:

The issue tracking system is designed to record a single technical problem. A bug report is something where a developer/contributor can work on. The GitHub issue tracker is not a good place for general, not well thought out or unworkable ideas. Most likely a discussion-type issue will not be addressed for a long time or closed as invalid. The best place for general discussions is our Matrix room at https://chat.mozilla.org/#/room/#pdfjs:mozilla.org.

I agree. We're open for pull requests, but unless there are major problems with Webpack right now we're not considering doing this.

Thanks guys. Apologies, it was just a general suggestion — something to maybe consider for the future. I appreciate that such a big change is likely not a priority.


Automate nightly Turbopack release tagging

This adds a new workflow which automatically releases nightly alpha versions of turbopack. Coupled with https://github.com/vercel/next.js/pull/45506, we'll be able to fully automate our release process into Next.js.

The process kicks of with cron every midnight-ish PST.
We find the latest commit that passes CI
We bump the latest tag version (more on this in a bit)
We generate a new GH release with this version

The automated tagging version will break with our current turbopack-YYMMDD.XYZ release process just a bit. The tag action that I'm using can't generate a date-like tag, it can only handle semver (with optional prefix). So I've set it up to generate turbopack-MAJOR.MINOR.PATCH-alpha.XYZ tags. The turbopack- here differentiates us from Turborepo, and the alpha tag denotes this a non-release software.
I hope that I've configured this correctly to always bump patches, but I'm not 100% confident until it runs.
Fixes WEB-502

@jridgewell let us know if it would be helpful for us to start prefixing turborepo tags - we're just squatting on the vanilla semver tags now. Same goes for Github releases.

let us know if it would be helpful for us to start prefixing turborepo tags

From a technical standpoint, no it's not necessary. From a product standpoint, maybe?

Yea I think it might be beneficial to help everyone understand the state of each project


Update Trivy Version in Dockerfile

Update the Dockerfile to use the latest release of Trivy.
The version of Trivy used in the action currently has errors when generating table output for scans of some files. The latest version, 0.28.1 has fixed these errors.

@b34rd-tek  can you share the command how did you test the table output for scans? I would like to test it and maybe add a test for this.

@krol3 are you on slack? I can go over all the details much faster there.
This issue goes over things a bit:
https://github.com/aquasecurity/trivy/issues/2174

Yes I'm in the slack, same as here krol


Running the development server in the background with the reloader enabled stops the process

Running the development server with a Flask application as a background process causes the process to be immediately stopped, but only when using the reloader. Without the reloader, the process runs normally in the background.
To replicate, create a Flask app and run it either with werkzeug.serving.run_simple, Flask.Flask.run, or the Flask CLI. Pass use_reloader=True if using the first option or enable debug mode if using either of the others. For example:
from flask import Flask
from werkzeug.serving import run_simple

app = Flask(__name__)

@app.route("/")
def hello_world():
    return "
Hello, World!
"

if __name__ == "__main__":
    run_simple("localhost", 8000, app, use_reloader=True)

Run the module in the background:
python test.py &

Press enter, and see:
[1]+  Stopped                 python test.py

Using bg afterward has no effect:
$ bg %1
[1]+ python test.py &

[1]+  Stopped                 python test.py

If use_reloader is instead set to False, then python test.py & works correctly, with the process running in the background and no stop signal.
I believe this behavior is a result of werkzeug._reloader.ensure_echo_on. This function sets the terminal to echo mode if it's currently disabled, which it is if the process is running in the background. Doing this triggers a SIGTTOU signal, which stops the process.
I don't think that the reloader ought to make a difference concerning whether or not it's possible to run the development server as a background process. Even redirecting stdout doesn't avoid the problem; only redirecting stdin does, since that causes ensure_echo_on to return early.
I understand that ensure_echo_on was added to handle a bug where code reloading during a PDB session breaks terminal input (see #1317/#1318), so I don't necessarily suggest removing that function. Can we just ignore SIGTTOU from inside of it? (I'll make a PR for that preemptively since it's such a simple change.)
Environment:

Python version: 3.10
Werkzeug version: 2.2.2
OS: Ubuntu 22.04

The development server is meant for development, not production. Running a process in the background sounds like something you'd do in production. I'm fine with that not working, especially with the reloader which definitely shouldn't be run in production.

My use case is that I wish to run end-to-end tests with a testing framework that depends on the server already running, Cypress. It's convenient to have the server running in the background in this context, and it certainly makes sense to use a development server. I also can't think of any disadvantage to ignoring SIGTTOU during the specific system call that triggers it.

You shouldn't run the reloader during tests, you should be testing a fixed version of the code.

Why? What if I find that, for example, my front-end code makes an API request that triggers an internal server error, and I want to make a change to the server followed by running the test again without having to manually restart the server?

Have your test process manage running the app, stopping it when the tests end, and then it requires no manual background process.

That's reasonable, but it seems to me like a matter of personal preference. I can think of other cases where it might be helpful to run the development server as a background process, like if you're using microservices, where one Flask app is a REST API and another is a front-end server. Some people might like to run the REST API in the background while running the front-end server in the foreground. In that case, you'd still want to have the reloader in order to debug issues with the REST API.

If they're only developing the frontend, then why would the backend reload? And if it's a background task, how would they see logs about any errors in the backend, to know to fix them and then trigger a reload?
I'm not particularly convinced by the reasons presented here, so I don't plan to make backgrounding the dev server with the reloader a feature at this time.

If they're only developing the frontend, then why would the backend reload?

They could discover an issue with the backend while working on the frontend, and then modify the backend accordingly.

And if it's a background task, how would they see logs about any errors in the backend, to know to fix them and then trigger a reload?

By logging to a file.

I don't plan to make backgrounding the dev server with the reloader a feature at this time.

Just to be clear, have you looked at #2572 yet? It's an extremely simple fix and there doesn't seem to be any disadvantage to merging it from what I can tell.

The disadvantage is that it enables backgrounding the dev server reloader, which as I've stated in multiple ways now isn't a good idea. Technical reasons aren't the only reasons to approve or reject PRs. I'm sorry, it's hard to hear "no" to a feature request, but no.

I don't consider this a feature request: I consider it a bugfix. There's nothing in the documentation that suggests running the development server in the background should be impossible, and I really think it's a common practice, even in development. Django clearly agrees with me, at least. That said, I respect your decision, and thank you for all your work in maintaining these great projects.


Missing a zero, to display partitions bigger than 8GB

In section "Troubleshoot issues with diagnostics queries"
point 14, there is a missing zero in the query. Now it displays partition information that is bigger than 800MB. When the query should show partitions over 8GB should be:
AzureDiagnostics
| where ResourceProvider=="MICROSOFT.DOCUMENTDB" and Category=="PartitionKeyStatistics"
| where todouble(sizeKb_d) > 8000000

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

ID: e65b6971-ea56-5e85-b199-d357fbc97580
Version Independent ID: 219058ac-5460-a33f-bec1-810f40cd2be7
Content: Monitor Azure Cosmos DB data by using Azure Diagnostic settings
Content Source: articles/cosmos-db/cosmosdb-monitor-resource-logs.md
Service: cosmos-db
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@davihern We are checking this and will get back to you.


InputEventMouse.global_position not correctly accounting for transformations

Godot version:
3.1.1 (Mono)
Issue description:
When adding Controls with manually specified positions, there are a number of scenarios where global_position gives incorrect results when handling InputEventMouse events through _gui_input.
I have not tested to see if the same happens with Node2D and the _input_event callback.
Steps to reproduce:
Create a wrapping control with a _gui_input handler to test events and print the global_position

Negative Offset
Add a child control with Position (set in code or editor) to (-200, 0).
Click the top left of the visible portion of the control (i.e. the very top left corner of the window). Expected global position is (0, 0) but global_position returns (-200, 0).

Positive Offset
Add a ColorRect child control with Position (set in code or editor) to (0, 500), with MinSize of (500, 500).
Click the bottom right of the visible portion of the control. Expected global position is (500, 1000) but global_position returns (500, 1500).

Minimal reproduction project:
Testing-MouseGlobal.zip

I can't seem to be able to reproduce it in the master branch of the Engine(Non-Mono).
Have you tried this in the master or can someone else test and verify this problem?
I am using Windows 10 64bit, Master with commit at 89c37da

I experience the same behaviour with 3.3.1.stable.official (Non Mono)
However, if I add the same input handling code to the color rects, then the reported position and global_position will be just fine. It seems as if Godot applies the position of the control that is directly under the mouse as an offset to both the position and the global_position of the event.

Fixed by #31915


failing to use correct screenshots path assuming and adding 'screenshots' folder to all images

failing to use 'screenshotPath' property in wdio.conf.js for images taken by wdio testrunner
wdio-mochawesome-reporter adds 'screenshots' meanwhile 'screenshotPath' in wdio.conf.js could be set to './screenshots/errors'.  images are now broken in report.
failing to use path defined by developer for all other images
a developer may be calling browser.saveScreenshot(myPath) throughout a test where 'myPath' is user defined.  wdio-mochawesome-reporter adds 'screenshots' to 'myPath'.  images are now broken in report.
we have tested a fix in reporter.js below.  if we can get a fix and updated npm package we would greatly appreciate it.
const screenshotPath = this.config.screenshotPath.replace(//$/, "")
screenshotCommands.forEach(cmd => {
if(cmd.payload.filename.indexOf(path.sep) === -1)
{
context.push({title: Screenshot: ${cmd.payload.filename},value: path.join(screenshotPath,cmd.payload.filename)})
}
else
{
context.push({title: Screenshot: ${cmd.payload.filename},value: cmd.payload.filename})
}
});

temporary package published until this issue is fixed
https://www.npmjs.com/package/wdio-mochawesome-reporter-fixed

@kirksl Sorry for the slow response.  I'm on vacation for the holidays and haven't spent much time on my computer.  Did you submit a PR for the issue?

@fijijavis no worries.  i needed a quick fix before end of year and created a temporary npm package(below).  i updated reporter.js with the code posted in the opening of this bug and it works perfect.  let me know if you have any questions on the code.
https://www.npmjs.com/package/wdio-mochawesomefixed-reporter

I am seeing the same issue as @marcelas - and all my errorshots image urls are broken on my reports

@davidjgonzalez what version of the reporter are you using?

I have the same issue in 2.0.1 reporter

I have the same issue in 2.0.1 reporter.

Hello guys, i have the same particular issue. I don't get the png files in my mochawesome report to provide screenshots in the reporter. I see now broken images, because the filepath is incorrect! Only when i paste the screenshots manually  in the mochawesome-report path i see nicely the screenshots in the report showing. See below for details:
    mochawesome: {
      outputDir: './mochawesome-report',
      mochawesome_filename: 'wdiomochawesome.json',
    },
mochawesomeOpts: {
  includeScreenshots:true,
  screenshotUseRelativePath:true,

},

Closing as this will not be an issue with the wdio v5 compatible version of the report


2.2.0 - Docs - No instructions for removing a Windows node from a cluster

@mbentley commented
What's the problem/feature request?
Attempting to remove a Windows node from a cluster results in the Windows node being broken because of how we are modifying the Docker service.  I did not see any docs for cleanly removing a
Windows node.
Who is asking for this?
me
What is the (customer) Impact of this request or severity of the issue?
Broken Windows node after removal
What versions/components are affected?
UCP 2.2.0
/cc @joaofnfernandes

@friism commented
hm, interesting - @wsong is this a problem you've pondered? I guess we could just document how to manually restore the windows node to normal operation

@mbentley commented
Also, I noticed the windows node join info is here: https://beta.docs.docker.com/datacenter/ucp/2.2/guides/admin/configure/join-windows-worker-nodes/#install-ucp under there instead of https://beta.docs.docker.com/datacenter/ucp/2.2/guides/admin/install/#step-7-join-worker-nodes ?  It would be good to at least have a link.

@wsong commented
I'm not sure if there's any documentation here, but it'd have to be some cleanup that the user does manually. In particular, we don't save the old Docker certs or port or anything like that, so it'd be up to the user to restore their Docker install to the way they want.

Relates to #4412


flet-client-flutter: 0.24.1 -> 0.25.2

flet-client-flutter: 0.24.1 -> 0.25.2

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-reviewd workflow started
Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12519129837
Extra args: ``

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12519129837
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368599

x86_64-linux

:x: 12 packages failed to build:

python312Packages.flet
python312Packages.flet-core
python312Packages.flet-core.dist
python312Packages.flet-runtime
python312Packages.flet-runtime.dist
python312Packages.flet.dist
python313Packages.flet
python313Packages.flet-core
python313Packages.flet-core.dist
python313Packages.flet-runtime
python313Packages.flet-runtime.dist
python313Packages.flet.dist

:white_check_mark: 3 packages built:

flet-client-flutter
flet-client-flutter.debug
flet-client-flutter.pubcache

nixpkgs-reviewd workflow started
Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12520380100
Extra args: ``

I'll reorganize the commit history later

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12520380100
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368599

x86_64-darwin

:white_check_mark: 4 packages built:

python312Packages.flet
python312Packages.flet.dist
python313Packages.flet
python313Packages.flet.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368599

aarch64-darwin

:white_check_mark: 4 packages built:

python312Packages.flet
python312Packages.flet.dist
python313Packages.flet
python313Packages.flet.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368599

x86_64-linux

:white_check_mark: 19 packages built:

flet-client-flutter
flet-client-flutter.debug
flet-client-flutter.pubcache
python312Packages.flet
python312Packages.flet-cli
python312Packages.flet-cli.dist
python312Packages.flet-desktop
python312Packages.flet-desktop.dist
python312Packages.flet-web
python312Packages.flet-web.dist
python312Packages.flet.dist
python313Packages.flet
python313Packages.flet-cli
python313Packages.flet-cli.dist
python313Packages.flet-desktop
python313Packages.flet-desktop.dist
python313Packages.flet-web
python313Packages.flet-web.dist
python313Packages.flet.dist

Is the flutter builder supposed to build on Darwin?

nixpkgs-reviewd workflow started
Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12526774039
Extra args: ``

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12526774039
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368599

x86_64-linux

:white_check_mark: 19 packages built:

flet-client-flutter
flet-client-flutter.debug
flet-client-flutter.pubcache
python312Packages.flet
python312Packages.flet-cli
python312Packages.flet-cli.dist
python312Packages.flet-desktop
python312Packages.flet-desktop.dist
python312Packages.flet-web
python312Packages.flet-web.dist
python312Packages.flet.dist
python313Packages.flet
python313Packages.flet-cli
python313Packages.flet-cli.dist
python313Packages.flet-desktop
python313Packages.flet-desktop.dist
python313Packages.flet-web
python313Packages.flet-web.dist
python313Packages.flet.dist


[TEECAKE] Re-enable notification about previous drive state during SNS operation…

Created by: qnikst
… abort.

Closing as an obsolete


live demo link not working

http://hackathonstarter-sahat.rhcloud.com/

this has been opened on issue #756


Soss.jl interface

Basic version working:
using Soss, Distributions, MuseInference, Zygote, DynamicHMC

funnel = @model () begin
    θ ~ Normal(0, 3)
    z ~ MvNormal(zeros(512), exp(θ/2))
    x ~ MvNormal(z, 1)
end

(;x,) = predict(funnel, θ=0)
prob = SossMuseProblem(funnel | (;x), autodiff=MuseInference.ZygoteBackend())
result = @time muse(prob, (θ=0,), get_covariance=true)

and its 10X faster than Turing :tada: Also this was awesome easy to write and is very few lines of code.
Remaining TODO:

[ ] How do I do NUTS with Soss to compare results? Can't figure this out from docs / googling.
[ ] Account for transformations, ie implement [inv_]transform_θ and account for θ_space.
[ ] Can I get a better default for hyper parameters from digraph automatically without needing to specify by hand? Basically the tree leaves?
[x] Understand difference between args and observed values, and handle these accordingly. Like, is this valid Soss? And how do we handle the manipulations correctly in this interface?funnel = @model (σ) begin
    θ ~ Normal(0, σ)
    z ~ MvNormal(zeros(512), exp(θ/2))
    x ~ MvNormal(z, 1)
end

I'd probably write this as
julia> using MeasureTheory

julia> funnel = @model σ begin
           θ ~ Normal(σ=σ)
           z ~ Normal(σ=exp(θ/2)) ^ 4
           x ~ For(z) do zj
               Normal(μ=zj)
               end
           end;

(4 instead of 512 so it's easier to display)
Then for a little demo,
julia> truth = rand(funnel(3))
(θ = -0.0379977, z = [-0.864762, 1.39213, -0.800246, 0.0144543], x = [-1.41632, 1.65007, -0.875127, 1.05682])

julia> obs = (x = truth.x,)
(x = [-1.41632, 1.65007, -0.875127, 1.05682],)

julia> using SampleChainsDynamicHMC

julia> post = funnel(3) | obs
ConditionalModel given
    arguments    (:σ,)
    observations (:x,)
@model σ begin
        θ ~ Normal(σ = σ)
        z ~ Normal(σ = exp(θ / 2)) ^ 4
        x ~ For(z) do zj
                Normal(μ = zj)
            end
    end

julia> s = sample(post, dynamichmc())
4000-element MultiChain with 4 chains and schema (θ = Float64, z = Vector{Float64})
(θ = -1.2±1.8, z = [-0.47±0.69, 0.54±0.74, -0.29±0.61, 0.33±0.64])

For transformations, we use TransformVariables.jl. You can get the transform for a given model using xform, like this:
julia> import TransformVariables as TV

julia> tr = xform(post)
TransformTuple{NamedTuple{(:θ, :z), Tuple{Identity, ArrayTransform{Identity, 1}}}}((θ = asℝ, z = ArrayTransform{Identity, 1}(asℝ, (4,))), 5)

julia> TV.dimension(tr)
5

julia> TV.transform(tr, randn(5))
(θ = -0.462708, z = [1.17351, -0.631122, -0.637643, 1.28246])

Also, I want to extend this functionality some more, but for now you can do
julia> prior(funnel, :x)
@model σ begin
        θ ~ Normal(σ = σ)
        z ~ Normal(σ = exp(θ / 2)) ^ 4
    end

julia> likelihood(funnel, :x)
@model z begin
        x ~ For(z) do zj
                Normal(μ = zj)
            end
    end

Thanks for the replies! Couple followups.
With the model defined as above with MeasureTheory it looks like Zygote gradients are failing. Prevoiusly I had only looked at Distributions and there both Zygote/ForwardDiff work. Is this a known issue and/or is my call OK?
(;x,z,θ) = rand(funnel(3))
logdensity(funnel(3) | (;x, z), (;θ)) # ok
ForwardDiff.derivative(θ -> logdensity(funnel(3) | (;x, z), (;θ)), θ) # ok
Zygote.gradient(θ -> logdensity(funnel(3) | (;x, z), (;θ)), θ)[1]
# ERROR: Need an adjoint for constructor MappedArrays.ReadonlyMappedArray

Btw I had noticed that with Distributions, Zygote.gradient(θ -> logdensity(funnel(3) | (;x, z), (;θ)), θ) is slightly better performance than Zygote.gradient(θ -> logdensity(funnel(3), (;θ, x, z)), θ) since the former seems to entirely drop the gradients w.r.t. (x,z), which here is what I want, so that's why I did it that way in this interface. Is that OK?
Re the likelihood/prior thing, yea those are super useful. For MUSE the prior I need is P(θ) so I ended up with
https://github.com/marius311/MuseInference.jl/blob/55fe15f50062c34a90b7b54aa512f28eabaebf64/src/soss.jl#L26
which from what I can tell propagates the argvals too should the prior depend on them.
And thanks for the HMC code and transform code, that's helpful!

Thanks, I hadn't tried Zygote in a while. Maybe some context will help for this, and we should add an issue in MeasureTheory.
For builds a product measure based on some parameterization. It's not itself an array, but you can describe it in terms of an array of measures. Like this:
julia> d = For(randn(3)) do μ Normal(μ=μ) end
For{Normal{(:μ,), Tuple{Float64}}}(#7, [0.1560796508305534, 0.6416014978488057, 0.3847545293905175])

julia> marginals(d)
3-element mappedarray(#7, ::Vector{Float64}) with eltype Normal{(:μ,), Tuple{Float64}}:
 Normal(μ = 0.15608,)
 Normal(μ = 0.641601,)
 Normal(μ = 0.384755,)

Those are the same as if you had used map:
julia> map(d.f, d.inds...)
3-element Vector{Normal{(:μ,), Tuple{Float64}}}:
 Normal(μ = 0.15608,)
 Normal(μ = 0.641601,)
 Normal(μ = 0.384755,)

But map requires an allocation, which we want to avoid. So there are some cases where we delegate to MappedArrays.jl.
But it looks like MappedArrays is missing ChainRules to let Zygote do its thing. But it looks like this does work ok in the dev branch of MeasureTheory, which will be the basis for the next Soss release:
julia> x = randn(3)
3-element Vector{Float64}:
 -0.930351
 -1.24049
  0.355545

julia> f(β) = For(x) do μ Normal(μ=β + μ) end
f

julia> Zygote.gradient(β -> logdensityof(f(β), x), 0.3)
(-0.9,)

Btw I had noticed that with Distributions, Zygote.gradient(θ -> logdensity(funnel(3) | (;x, z), (;θ)), θ) is slightly better performance than Zygote.gradient(θ -> logdensity(funnel(3), (;θ, x, z)), θ) since the former seems to entirely drop the gradients w.r.t. (x,z), which here is what I want, so that's why I did it that way in this interface. Is that OK?

If I'm thinking of it right, that should just give you the partials, so it should be fine. Maybe worth adding a test just to be safe?
BTW, I'll need to figure out how to square Soss.likelihood with MeasureTheory.likelihood, which works like this:
julia> f(β) = For(x) do μ Normal(μ=β + μ) end
f

julia> post = Lebesgue() ⊙ likelihood(f, x)
Lebesgue(ℝ) ⊙ Likelihood(f, [-0.9303505027587362, -1.2404857664253213, 0.3555452843296289])

julia> logdensityof(post, 0.3)
-2.89182

# compare
julia> logdensityof(f(0.3), x)
-2.89182

I'm setting things up this way because for some cases like linear models, the likelihood can be evaluated a lot more efficiently than the naive approach.

All basically working. Here's my benchmark if you're curious

This is with the model written as
Soss.@model () begin
    θ ~ Normal(0, 3)
    z ~ MvNormal(zeros(512), exp(θ/2))
    x ~ MvNormal(z, 1)
end

rather than your way since I want to use Zygote (which is faster than ForwardDiff here). Full code here if curious: https://gist.github.com/marius311/295164a0bbfbdb281a2dd6fb473597b6
Will probably merge shortly, but of course happy to iterate on stuff pending Soss changes or any comments you might have.

Wow! This is great! I haven't done much performance tuning, so I'm surprised to see it's doing so well. At the same time, I think as MeasureTheory progresses we should be able to get close to that "Julia" time


BUG: scipy.optimize.bracket sometimes fails silently

Describe your issue.
Sometimes scipy.optimize.bracket fails to find a bracket (e.g. see example below).  Thats probably ok.  There are some weird functions out there.  But at least one of the following should probably be true

scipy.optimize.bracket should throw an exception if it fails
functions that use scipy.optimize.bracket (e.g. brent) should be aware that it might return an invalid bracket

Otherwise you can have people using functions like brent and getting answers that don't make sense.
Reproducing Code Example
import scipy.optimize
import numpy

def f(x):
    return x**2 if ((-1<x)&(x<1)) else 100.0
brack=scipy.optimize.bracket(f,-1,1)[:3]

# this isn't a valid bracket
print(brack)  # <-- (-1, 1, 4.2360679999999995)
# f(-1)=f(1)=f(4.23)=100, so thats not a valid bracket.
# valid bracket should have f(a) > f(b) < f(c)

# now if you ask brent to find a bracket for you,
# it calls scipy.optimize.bracket, gets an invalid bracket (namely -1,1,4.23)
# tries to use this invalid bracket, and yields a nonsense answer
print(scipy.optimize.brent(f,brack=(-1,1)))  # <--4.23, not the argmin

# though if you explicitly tell brent to use this brack
# it will notice that it is a  Bad Bracket
print(scipy.optimize.brent(f,brack=brack)) # <-- raises ValueError (as it should)

BTW I'm not entirely sure what the right definition of "failure" is.   If f(xa)=f(xb)<f(xc) then it seems to me that this is actually still a useable bracket.  But my 1d optimization intuitions have failed me before.
Error message
No problematic error messages.  The problem is the lack of error messages :).

SciPy/NumPy/Python version information
1.7.1 1.19.5 sys.version_info(major=3, minor=9, micro=6, releaselevel='final', serial=0)

I think the problem is that optimize.bracket does not check the results whether the results satisfies " f(xa) > f(xb) < f(xc)" or not here.
https://github.com/scipy/scipy/blob/47bb6febaa10658c72962b9615d5d5aa2513fa3a/scipy/optimize/optimize.py#L2661-L2667
I came up with two options to fix the issue:
[Option 1]
Throwing exception here if the results do not satisfy " f(xa) > f(xb) < f(xc)" like "optimize.brent" and "optimize.golden".
But this might break someone's code (backward compatibility).
[Option 2]
Update the doc that the objective function criteria from " f(xa) > f(xb) < f(xc)" to " f(xa) >= f(xb) <= f(xc)".


Adding T8codeMesh support.

Title says it all.

Is this ready for a review or does it require something else first?

Is this ready for a review or does it require something else first?

Ready for review!

t8code reference files are still missing in the Trixi2Vtk_reference_files repo. However, for t8code, testcases analogous to the p4est testcases are run and the same file names (not folders) for the reference solutions are used. Therefore the previously downloaded p4est reference files are picked up during the t8code tests. In 2D this works, the t8code results compare equal to the p4est results. In 3D, this is no longer the case.


[Bug] Move all build time variables to runtime variables in the client

Description
Instead of using REACT_APP_* variables (that are set at build time), we should move them to APPSMITH_* variables that can be set at runtime. This will ensure that users are able to configure their instances on the fly and not need to rebuild the client application.

@mohanarpit is this done?

We've migrated the variables that could be migrated. There are a select few that still remain but we don't have a good solution for them yet. Closing this issue.


Added plugin to app, directly failed build after trying to run the app

The issue:
I am trying to implement the Google AdMob plugin into my Flutter app, but the build fails after doing flutter run as soon as I have installed the plugin. Of course, I first ran the install command, flutter pub get and flutter run (after flutter clean), but nothing works.
This is the error I am getting:
D:\Flutter\MYAPPNAME\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java:24: error: package io.flutter.plugins.googlemobileads does not exist
      flutterEngine.getPlugins().add(new io.flutter.plugins.googlemobileads.GoogleMobileAdsPlugin());

                                                                           ^
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

I even tried, as a last resort, to do this in build.gradle, but sadly no luck.
dependencies {
    implementation 'com.google.android.gms:play-services-ads:22.6.0'
}

My pubspec.yaml:
dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^1.0.6
  http: ^1.1.2
  flutter_html: ^2.2.1
  get: ^4.6.6
  url_launcher: ^6.2.2
  html_unescape: ^2.0.0
  flutter_linkify: ^6.0.0
  intl: ^0.19.0
  provider: ^6.1.1
  shared_preferences: ^2.2.2
  share_plus: ^6.3.4
  async: ^2.11.0
  flutter_native_splash: ^2.2.0+1
  google_mobile_ads: ^2.4.0

(I also tried ^ 4.0.0, same issue)
How can we solve this?

Hi @Siyaho,
I'm unable to replicate the issue you are experiencing running our google_mobile_ads example project. From the example project, I opened the android folder directly (e.g. example/android) in Android Studio and was able to run it.
Are you able to run the example Android project following these steps? If so, try something similar for your own project.


Add prettier through eslint

This is a follow up on #278, it was a bit easier to redo the changes of @AlanFoster

@rotemmiz If there are no objections I will merge this the next days and apply prettier on this part of the repo. I will also add instruction on how to rebase other branches with the prettier changes (or do it myself if these are branches on this repo)

@DanielMSchmidt For visibility, I had made changes to eslintrc to remove rules that actively conflicted with prettier :)
I had decided not to use .prettierrc to align with the eslintrc approach :)

@DanielMSchmidt For visibility the original PR is rebased and should be good to go still :)

Awesome, lets use that one instead 👍


Added section about Unsafe Reflection in Security best practices doc

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues

Hello, just a little note about avoiding arbitrary object instantiations.

Thank you.


Update each pipeline with its contextual Analyze CTAs like the JobLog Analyze CTAs

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1393
Originally created by @derek-knox on 2019-12-06 20:02:19

Our LogModal.vue has contextual Analyze CTAs (analysis models) specific to the corresponding pipeline. The pipeline UI needs to have these exact same contextual CTAs. When I implemented the initial temporary solution (the ideal being https://gitlab.com/meltano/meltano/issues/1395) there wasn't a clean way to do so as I initially suspected.

View 10 previous comments from the original issue on GitLab


[NFC] Format lit checks for better readability.

If we use "hide whitespace" feature in the review, we'll only see some rename (e.g., zero -> C0).


[v2int/4.1] Revert to shallow clone to reduce bundle size

Description
Revert #15124 to release a v2int/4.1 patch without a bundle size increase. We'll re-apply an alternative version of the fix to that doesn't increase bundle size to main once we decide what that looks like.
Related: #15362 .

Current POR: Abandon this and port https://github.com/microsoft/FluidFramework/pull/15368 instead

Decided to use this PR to fully revert the change, and take another approach to fixing the original bug which only affected AzureClient/T9s and was only recently discovered


Problem with Sign In

When I do a request to 'backendurl//users/sign_in', backend return me a http code 500.

This error should be fixed now.


[589] Allow expression statements for attribute values in no-noninteractive-tabindex

Introduces an allowExpressionValues option for the rule that let's an implementer choose to ignore expression statements in certain attribute values.

Coverage decreased (-0.09%) to 99.47% when pulling d4845ec07b7c47de7ce593efd9bfe44e8ee91ea0 on 589--make-expressions-pass-in-recommended-mode into 85d8c1a071925927560337e2a8d7af274941b9f8 on master.


Add a issue template

Currently there is no issue template
Add a issue template (bug report and feature request)

Shall I work on this ?


Vector Search Support

Is there a way to make vector search work with this repository and react instantsearch? I've looked into custom widgest by algolia and the federated search demo repo as it is at least using the multi search endpoint. I just couldn't find a way to make vector search work and after looking in the code, it seems it is not a permitted param for collectionSpecificSearchParameters.
Can you give me a hint on which level I would need to implement it or if this repo is the right place for it?

Given that Algolia doesn't support vector search, Instantsearch does not expose any mechanism that triggers vector searches, so the adapter doesn't have anything to hook into.
So you would have to use the typesense-js client directly to do vector searches... For eg, have a look at the "Find Similar" link under each product in this demo. Here's how I trigger the vector search, outside the instantsearch lifecycle.

Thanks for the quick answer!
So if I wanted to use vector search and filter in parallel with filter widgets and sort by widget, I wont be able to use instantsearch, right?

So if I wanted to use vector search and filter in parallel with filter widgets and sort by widget, I wont be able to use instantsearch, right?

I haven't explored Instantsearch's custom widgets enough to be able to answer this question confidently unfortunately.
If you're able to build a custom widget that somehow calls the typesense-js library directly and then updates the internal instantsearch state based on the response you get... may be? I'm not sure if this is possible or how complex it is to pull off.

Okay, thanks for your time. I was hoping I could simply add vector search to the collectionSpecificSearchParameters and it would work. I'm not quite sure how your adapter translates those params or if theres a way to pass params to typesense directly via the adapter as some comments  suggested it (at least thats how I understood it).

Adding vector_query to collectionSpecificSearchParameters is easy - but then that parameter will get sent to Typesense on all searches initiated by instantsearch... I'd imagine you'd want vector_query to be dynamic based on some user input?

No, I want to have a static vector query for each page load. We basically use a data object that implies a certain search (filter and vector) and then filterRefinement widgets. But the vector search only changes with another (different) page load (different data object loaded). Would that be possible? I guess even if it was possible it would be a misleading addition to your repo, right?

If that solves for your use-case, happy to add vector_query to collectionSpecificSearchParameters - we anyway try to keep all parameters that can be used inside that config, in sync with all the search parameters available in typesense-js and let users decide which ones to use.
I'll push out an rc release shortly with this.

Could you update to v2.6.0 of the adapter and give it a shot now? You should be able to now set vector_query in collectionSpecificSearchParameters.

I would add to the schema of the document:
forVectorize: ["keywords", "name", "description"] then typesense on adding documents would automatically vectorize the documents by adding some variable to the document.
And by what you could search for a document similar to this.
client.index('products').similar(*1).limit(8)
*1 - id or the whole document, or a variable with a vector (neither)

Before I finished implementing it, I realized the available vector similariy function is not what I was looking for. I have a model A which contains a set of attributes and a model B which also contains the same type of attributes. I want to match them in a way that I look for A's that have the same values as B where B has values and I want to discard any differences that come from values that A has but B doesn't.
From a vector perspective:
A1:      [1 ,0 ,1]
A2:     [1 ,1 ,1]
should match equally to
B:      [1,0,1]
With the distance being 0 here. The function would be:
for each dimension:
 di = Math.max(Bi - Ai, 0)

Using cosine similarity would result in vector A1 matching better. For more complex vectors that can even mean that a vector gets preferred even if it matches worse.
However this is probably not a discussion for this repo.
From my perspective you can close that issue as the parameter vector_query is known now :)
Thanks for implementing the parameter, I really appreciate the work and typesense as an easy to setup search engine!

If anyone's looking to implement semantic search with Typesense's vector search feature + Instantsearch.js UI, here's how: https://github.com/typesense/typesense-instantsearch-adapter#vector-search

thanks @jasonbosco ! is there a demo app which uses the above (https://github.com/typesense/typesense-instantsearch-adapter#vector-search)

@jasonbosco hi, are there any ways to implement the same vector search with embedding from query string in React instant search?


Spring (Rails pre-loader) and dry-monads are incompatible

Thank you for your work on the dry project.
I wanted to make you aware of this incompatibility with spring. Even though I'm opening this ticket on your project first, I intend to open a ticket with spring as well.
Describe the bug
Spring (Rails pre-loader) and dry-monads are incompatible. Spring replaces Kernel#raise with a version that sanitizes backtrace. dry-monads raises an instance of Halt with a frozen EMPTY_ARRAY. An error is generated when Failure(..) is used an a dry-monads Do implementation.
Spring is a installed by default on rails new
To Reproduce
https://github.com/johnmaxwell/spring_dry_monads_break
require 'dry/monads/do'

class BreakHalt
  include Dry::Monads[:result]
  include Dry::Monads::Do.for(:call)

  def call()
    yield break_halt
  end

  def break_halt
    Failure('anything')
  end
end

BreakHalt.new.call

Results in an error like:
.../lib/ruby/gems/2.6.0/gems/spring-2.1.0/lib/spring/application.rb:305:in `reject!': can't modify frozen Array (FrozenError)

Expected behavior
Returns Failure instance
Your environment

Affects my production application: NO
Ruby version: 2.6.5
OS: Mac
Rails: 6.0.1
Spring: 2.1.0
dry-monads: 1.3.2

Thanks for letting me know and for all the work to narrow it down. I'm pretty sure it's a bug in rails. I don't patch ruby neither do I use dirty hacks, only Ruby. I can change EMPTY_ARRAY to [], not a big deal though. We'll see what they say :)

Pushed 1.3.3


Prod: Fix PATCH request on edit

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test pre-kyma-dashboard-prod

/test pre-kyma-dashboard-prod

/retest

/test pre-kyma-dashboard-prod


(fix): missing timestamp data type in Timestream

Feature or Bugfix

Bugfix

Detail

Add datetime related data types to pyarrow2timestream conversion method
Handle edge case of timestamp conversion
Add test

Relates

#1853

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 26413d64d0ea899b82ef2e325a2300f9f39f04b2
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


All files in Tree marked as New(Green)

I just updated to Atom 1.5 and now when opening any folder within a local repo each file in the tree is marked as green (marked as a new file). If I click and open the file it un-marks it green and goes back to clean. Note: The files are marked as green but Git doesn't pick them up as new files so I can still work with the files per normal.
I ran in Safe mode and was still able to reproduce the bug. I also tried different UI and Syntax themes and it still occurs.
I did notice that if I open the project from the root of the repo it works as intended, and the issue only seems present when opening a folder deeper within the repo.
Tree in root Git project

Tree in sub dir of same project (files in screenshot are NOT new)

Additional note. Happens on all projects and doesn't seem to be limited to that one project above.

Yep, have the same thing since Atom 1.5.0. Only non github hosted repositories seem to be affected from what it seems;

+1

I have the same problem, but not limited to non-github repositories.

opening atom with non-root folder displays everything as added
adding a sub-folder after opening the root-folder works (sub folder shows the repo-book-symbol )
adding the root-folder after opening a sub-folder keeps everything in the subfolder as added

MacOS 10.11.3
atom 1.5.0

Related issue: https://github.com/atom/tree-view/issues/717

Can confirm @AnimiVulpis happens also on github repositories. Opening at project root ( containing .git folder instead of the part I'm working with ) fixed this for me.

I have found the reason for such behavior.
Atom v1.5 includes a pull request https://github.com/atom/atom/pull/10249 which updates the version git-utils up to 1.4.0 (see https://github.com/atom/atom/commit/a962bba3a1299a7e27955c3c63dd3a16af4418ce) which changed the original behavior: https://github.com/atom/git-utils/commit/d4b0127852ff0857ca3cdb7e61c094e1c8503d47

Same issue here.

Same here :hand:

I've come across this issue today updating to 1.5.0, and it only affects opening Atom in a sub folder of a git project rather than the root.
The image below shows the root on the left with the sub-folder on the right.

Tried with different UIs and all the same.

We just released 1.5.1 which fixes this. Thanks for all the reports and sorry for the hassle!

Works great on 1.5.1, thanks!

Smooth! It works perfectly, thanks!

Having this issue. The folders that are highlighted are not accessible.

I'm having this issue. The issue is that I'm on a mercurial repo (using https://atom.io/packages/atom-hg) but git version control kicks in, it shows I'm in master and all files are new. If I issue a git init + git add . the files go back to white. ping @chrishiestand

@sweetspot-mgdepoo I haven't had this issue recur for me (just with git). I recommend looking for an issue which covers this and if there isn't already one, file a new one.

Hi, issue born again. Why my local folders are green ? :/ its sad.

My folders are green too... I installed Atom just now

I have the same issue

Same issue 1.12.1 64x

i have the same problem

ok , Thank  You.
<EMAIL_ADDRESS>On Nov 12, 2017 10:50 PM, "Gabriele"<EMAIL_ADDRESS>wrote:

i have the same problem
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/10746#issuecomment-343748364, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ad7Vpg5xwSol4OcX88pXSyYCvvZwPu7wks5s1xrlgaJpZM4HWyqe
.

I haven't experienced this anymore for a very long time.

Atom 1.25, the same, on Mac

I had the same issue on 1.24.0. I downloaded 1.25.0 manually (without going thru the update), then re-added my project folders and they are no longer green.

Thanks, unfortunately doesnt work for me, any other ideas?

It looks like everyone commenting on this issue saying they are seeing it after this was fixed is on macOS. It's possible you may all be hitting https://github.com/atom/atom/issues/1890, but the symptoms reported do seem to be a bit different.
Would somebody that is able to reproduce this please file a new issue and completely fill out the template? Steps to reproduce, like an example repository to clone, would be immensely helpful in tracking down this new issue.
Thanks!

I am still getting this issue I am on windows

Same issue (;~~~;)


Update Labels for E2E tests

Replace 'prblocker' with 'quickstart' to clarify intent
Remove 'slow' and 'network' as every test had it making it moot
Expand scope of 'capx-feature-test' to target all nutanix interactions
Add 'scaling' to target all tests involving node churn

/hold

/retest

/unhold


Bug in Templates?

I had two macros referencing files "command.start" and "command.end".
Unfortunately the last one didn't work. Instead the first one was always applied.
I found the reason in this line:
https://github.com/kovetskiy/mark/blob/5428cc683302a7679901e23d4e97fc83838a788b/pkg/mark/includes/templates.go#L29
Is there any reason for using just the filename without path and extension as the name?

Not really, we can remove this operation. It's mostly for dropping .template or other file extensions.

Not really, we can remove this operation. It's mostly for dropping .template or other file extensions.

Will you do?


Inonsistency in fonts of headings

Title and Issue number : Inonsistency in fonts of headings https://github.com/apu52/Travel_Website/issues/372

Title : Inonsistency in fonts of headings #372
Issue No. : 372
Code Stack :
Close #<issue_no>

Video/Screenshots (mandatory)

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?
GSSoC'24

@apu52