Need help with some functionalities

Hi, I am trying to switch from IRAF to Python so I tried this package but I think I might be missing something.
I need to get the wcs coordinates and the fwhm of some stars in an image I have.
To do this in IRAF I run imexa -> a , and that does the trick.
I can not figure out how to obtain that sort of data with this package. Could someone help me out?
Cheers.

Update: this issue occurs when using python3, numpy version 1.17.2 but not when using python2.7 numpy version 1.16.4.
I tried downgrading the numpy version in python3 but didn't solve the problem

try installing from the current mast, with python3, and see if you get the same issue?

definitely - the master branch is meant to be running in python 3 only, give that a go!

@sosey I still get the following error when runing imexam+a in python 3:
/anaconda2/envs/py3/lib/python3.7/site-packages/imexam/imexamine.py in aper_phot(self, x, y, data, fig)
    566                 # The bkg sum with the circular aperture is then
    567                 # then mean local background tims the circular apreture area.
--> 568                 aperture_area = apertures.area()
    569                 annulus_area = annulus_apertures.area()
    570

TypeError: 'float' object is not callable

It seems like this option has a problem calling a float. I don't have issues when running other options (letters).
In addition I wanted to ask you if there is any way to get the FWHM automatically (without having to click on the stars) once I know the coordinates of my stars.

Ok, my guess now is that I am too dumb to understand this package.
@sosey if you ever have time maybe I can tell you what I wanna do and you can walk me through. If not thanks anyway for writing the code.
Cheers

@pjpessi you are not too dumb! If you can't find the information it's because I probably need to organize it better. Don't be discouraged...you managed to ping me during a few weeks where I am working overtime and traveling.
One place to look for information on how to run the package without any GUI interaction is here: https://imexam.readthedocs.io/en/latest/imexam/examples.html#return-information-to-variables-without-plotting
the methods for imexam.Imexamine may also be called through the library, and save plots directly, or return the information that used to make them as arrays...or as the information itself. You can call the functions in imexam.math_helper as well.
I'm traveling again tomorrow, but the plane time might give me a chance to make an example for you.

@sosey Thanks for the reply, I've read the docs in the link you sent.
I found Imexamine. I have a coordinates array and I want the FWHM of the stars at those coordinates. I found that plots.aper_phot() return that. Although I am not able to return anything. Only a blank (no star or anything just the green and red circles) plot when using a toy array.
If you could send me an example it would be great. I'll wait.
Thanks again for answering while being busy, I understand that you might have a lot of work.

Here's an example that doesn't use a display connection:

start with a reasonable estimate for the center of an object, mine is at 476, 463
you can get the refined center using a 2D gaussian fit

Start by creating a control object

from imexam.imexamine import Imexamine
from astropy.io import fits # to get my data array
i=Imexamine()

grab the data you want and attach it to the control object i:

data = fits.getdata('iacs01t4q_flt.fits')
i.set_data(data)

x=476
y=463

get the results and save them to variables

amplitude, xcenter, ycenter, xsigma, ysigma = i.gauss_center(x,y)

Now we'd like to calculate the gaussian FWHM for this star, we'll use one of the functions in math_helper:

from imexam.math_helper import gfwhm
fwhmx, fwhmy = gfwhm(xsigma, ysigma)

If you want to do this for a list of objects, one way would be to  iterate over the locations and save to a dict:

star_locations = [(476, 463), (621, 604), (426, 627)]
star_measures={}
for x,y in star_locations:
amplitude, xcenter, ycenter, xsigma, ysigma = i.gauss_center(x,y)
fwhmx, fwhmy = gfwhm(xsigma, ysigma)
star_measures[(x,y)] = [amplitude, xcenter, ycenter, xsigma, ysigma, fwhmx, fwhmy]

In [30]: for x,y in star_locations:
...:     amplitude, xcenter, ycenter, xsigma, ysigma = i.gauss_center(x,y)
...:     fwhmx, fwhmy = gfwhm(xsigma, ysigma)
...:     star_measures[(x,y)] = [amplitude, xcenter, ycenter, xsigma, ysigma, fwhmx, fwhmy]
...:
xc=476.079945   yc=463.334336
xc=621.746534   yc=604.025901
xc=426.098969   yc=627.217134
In [31]: star_measures
Out[31]:
{(476, 463): [186.85484771427207,
476.07994512670734,
463.33433586987957,
0.5884975412258683,
0.6835437241428306,
1.3858058065301022,
1.6096224632666432],
(621, 604): [209.5162833512038,
621.7465337987292,
604.0259014678302,
0.6310587900801216,
0.5938579399164946,
1.4860298884736483,
1.3984285808161465],
(426, 627): [21.245743148440987,
426.0989685548685,
627.2171342445665,
0.5735289443714519,
0.6140807497649734,
1.350557454611335,
1.4460496588141938]}

if you have a viewer like DS9 connected, you can mark the locations of the stars on the viewer like so, it will use the (x,y) locations that are the keys into the star_measures dictionary:

a.mark_region_from_array(star_measures) # a is the object linked to my ds9

If you want to display a plot, you can see the fitting models that are available:

In [43]: i.show_fit_models()
The available astropy models for fittingare: ['Gaussian1D', 'Moffat1D', 'MexicanHat1D', 'AiryDisk2D', 'Polynomial1D']

Display the line fit to the star with the fit for a 1D Gaussian

i.line_fit(x,y)

I saved the image above using i.save('example.jpg')

@sosey thanks a lot for the example, it worked ok. Could you tell me where to find the documentation for math_helper.gfwhm?, I can not find it. Or let me know why is there a fwhmx and fwhmy?.
Thanks again.

In general when you are in a notebook or ipython session you can use syntax like this to get the document string help for a function: imexam.math_helper.gfwhm? .  I don't think I have more extensive documentation about the gaussian fwhm function at this point. The function is returning the fwhm for each dimension, x and y, as it's not expecting symmetry.

@sosey Ok, great. Thank you very much.


stats wishlist

get time-stamped stats at 5 mins & 60 mins blocks* (removing incomplete blocks -- eg in a 33 min rec, I'd have 6 5-min blocks and 0 60-min blocks)
get stats over the whole file*
get stats per hour (mean, min, max, med - across all hours; OR within user-provided range: eg 11-13 for mealtime, 7-19 for daytime)

For the following event types, get total duration, average duration, median duration, number:
KCHI/CHI: child vocalizations (VTC: KCHI & LENA: CHN), †child veg vocs (LENA: vfx), †child veg vocs (LENA: utt), child cry vocs (VCM: Y & LENA: cry), †child can vocs (VCM: C), †child non-can vocs (VCM: N)
OCH/CXN, FEM/FAN, MAL/MAN
For conversational stats, looks like chattr has it all:

Rate of turn-taking (i.e., rate of child--other and other--child transitions)
Frequency and duration of interactional sequences
Speed of turn transitions
Hourly and daily trends in interactional bursts
Ratio of vocalization by the child and others during turn exchanges
Differences in turn-taking between the child and different family members

I'm reassigning this to Nicolas, who is already working on it!

I will look at chattr function on the data then

We all do agree that these scripts should take this format as an input right : https://laac-lscp.github.io/ChildRecordsData/FORMATTING.html#annotations-format ?
It would be nice if they were integrated in the package maybe. @alsonicr, are you writing them in R or python ?

I'm fine with every input you previously decided. Currently I use rttm or the standardized format you produce.
I'm currently writing function in R, nothing to fancy.
@alecristia told me Chattr is not in a finish yet and i would agree looking at the github (look messy). More over, Chatter take rttm file as input or its if we look at the description. But from what i understand we are moving from those formats to a common one off our own.


Move problem_dict unpacking to BaseOptimizer class

Why unpack problem_dict every time in child classes, move it to the parent

Also, we can move initialization function to base class, because it almost the same

Sounds fair. Create a new issue then. I'm done with this one


Return null not just when the field is scalar but whenever it's non-null

Most other implementations I've seen do exactly this

@viniychuk I pushed a new tag (v1.6.0) but Packagist is not getting updated, can you help me out? Most likely you need to redo the Packagist integration since they changes how it's done a few months ago.


adds public access to spinnerColor

allows developers who are not using interface builder to change the spinner color

        acceptButton.spinnerColor = .red
        acceptButton.startLoadingAnimation()
        manager.acceptCurrentCall()
    }

its crash my app. may i know why ?


update to 8.20200522 with stack

Checklist

[X] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/core is it possible to increase the disk space available to the docker build?

Try this maybe.
https://github.com/conda-forge/omniscidb-feedstock/issues/5


Update sql-database-project-extension.md

the link was pointing at:
https://aka.ms/sqlprojects-dotnet
I believe it should point to (or the above link be updated) https://dotnet.microsoft.com/en-us/download/dotnet/8.0
The page should also call out which version of .net is required. I believe the answer is 6.0 or later?  I can add this text to the pr if it is correct

@dzsquared -
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Saisang - can't assign @dzsquared to this PR. is there a fix ? thanks.

#assign:dzsquared

PR is out of date now.  Closing as it now will cause problems to merge.


[plot] Make set|getSelectionMask support/return None

This PR changes the returned value of getSelectionMask to None when there is no mask and makes setSelectionMask accept None as input to reset the mask.
closes #1765
closes #834
Please check if it breaks anything in applications before merging.
Maybe not merge for v0.8?

We can merge it if there is no problem on PyMCA

It will be working with PyMca too, with a minor fix (https://github.com/vasole/pymca/pull/245).

I am just checking this on tomogui.

Good for me.


Adds fullscreen log viewer

Very basic fullscreen log viewer subapp.
Planned enhancements:

Scrollbar to display position with the log
Prevent scrolling up past one full screen of the log
Support for scrolling by page
Automatic scrolling while the dpad is held down (dependent on #90 )
Indication that the log is explicitly locked to the bottom and will scroll as new events come in (in case we start using more log messages in the FTP server or some other interesting background thread)

Great stuff, thanks!


PPL add doc note on f2f usage

Fixes #1011
Signed-off-by: Vitor Bandeira<EMAIL_ADDRESS>

It looks fine to me, but I'll let @arlpetergadfort and @dralabeing review and approve the PR.

Does the PPL tool now support face-to-face direct bonding? Does this change any of the current commands ?I am not clear what is to be reviewed here, other than the note on the f2f description- new usage of PPL is not described.

This update in the documentation is intended to give more context to the define_pin_shape_pattern and set_io_pin_constraint commands. By using both commands together (as described in the next paragraph after "Face-to-Face direct-bonding IOs" section), the user can place pins in the upper layer of the design, allowing f2f bonding.

@arlnigussie can you chime in?


Use start date info for course card display

Add additional fields to course test data - tweak for objc interaction

JIRA: https://openedx.atlassian.net/browse/MA-1602

@mikekatz please review

just a few questions, but :+1:


feat: experimental.buildAdvancedBaseOptions

Description
Fix #3522
Building on top of:

https://github.com/vitejs/vite/pull/7644

Read the description in #7644 first for context. See also @danielroe's comment: https://github.com/vitejs/vite/issues/3522#issuecomment-1090327274 where he describes why frameworks like Nuxt need dynamic/runtime base support. And why they would like to be able to define a separate base for hashed assets and for public files (the caching strategies could be different, and they may be in different CDNs).
In discussions with @Rich-Harris, they also expressed interest in being able to set relative base for in-assets paths and an absolute base for in-html paths. @matthewp and @FredKSchott also showed concerns about relative base when dealing with 404s. This PR may also help in that regard, but I need to better understand the use case.
It should be working already except for the plugin legacy and the manifest generation. Pushing it so we can start discussing the API while we take care of the implementation details.
There is a new config experimental.buildAdvancedBaseOptions: BuildBasedConfig, defined as:
export interface BuildAdvancedBaseOptions {
  relative?: boolean
  url?: string
  runtime?: (filename: string) => string
}

export type BuildAdvancedBaseConfig = BuildAdvancedBaseOptions & {
  assets?: BuildAdvancedBaseOptions
  public?: BuildAdvancedBaseOptions
}

If defined, these functions will be called for assets and public files paths that are generated in JS assets. For assets and public files paths in CSS or HTML, the corresponding url base urls or global base will be used. Example of a config with a dynamic function:
export default {
  experimental: {
    buildAdvancedBaseOptions: {
      url: 'https:/cdn.domain.com/'
      runtime: (url: string) => `window.__toAssetPath(${url})`
    }
  }
}

Nuxt (through @danielroe) requested being able to use different bases for hashed assets and public files, as both may need different cache strategies. The PR implements this by letting you override the global build base options using buildBaseOptions.assets and buildBaseOptions.build. When using relative base, the runtime function isn't needed for assets as all the asset paths will be computed using import.meta.url. The public.runtime function is still useful if the public files aren't deployed in the same base as the hashed assets
Example exercising all the features:

separate assets and public files base configuration
dynamic base in assets so the server can inject the correct URL without rebuilding the assets
absolute URL for in-HTML assets and public files paths (this could be a placeholder that is later replaced by the server avoiding the need to rebuild the HTML). Some frameworks like SvelteKit have their own logic and they will need to replicate the handling this PR is doing if to respect these config options.

export default {
  experimental: {
    buildAdvancedBaseOptions: {
      assets: {
        url: 'https:/cdn.domain.com/assets',
        runtime: (url: string) => `window.__assetsPath(${url})`
      },
      public: {
        url: 'https:/www.domain.com/',
        runtime: (url: string) => `window.__publicPath + ${url}`
      }
    }
  }
}

There is a replicated assets playground test using these new options. You can run it using
cd playground/assets
pnpm run build:runtime-base
pnpm run preview:runtime-base

For preview to work, it is expected that the user will build locally using a configuration that ends up generating assets and public files that can be served by a single server pointing at base. This is the same as when currently using an external URL as base. Frameworks could provide middlewares for redirecting these URLs to the local assets. We could maybe support this by default, I need to check the details.
We could deprecate the base relative shortcut ('./' or ''). For the moment the config is properly resolved to build.baseOptions.relative: true.
Alternatives
I considered having base: string | AdvancedBaseConfig instead of base + build.advancedBaseOptions, but I think it is better to have these options under build. When we use relative base, we are already setting the base as '/' for the dev and preview server. So relative base only affects build. The same goes for a runtime base, which uses the same mechanism as relative base to inject a JS function in the middle of an in-JS CSS string. And when we have an external URL as a base, it also only applies during build time.
So I think it is better to leave the global base as a global default + dev/preview setting and push all these build-only advanced options inside build.
A new hook to resolve these assets could be considered, or make the advanced build option a function. The problem with these is that context is needed to be passed (importer chunk name and type). And we need to also document that the user should return "\"+...+\"" string. This exposes the internal handling of strings and will limit us later if we want to move to template strings for example. We can't perform optimizations based on the options passed, if only a static URL is needed then we could avoid some indirect generation. So IMO, explicit options are better here.
edit: move from build.advancedBaseOptions to experimental.buildAdvancedBaseOptions

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

A better API could be:
export interface BuildBase {
  relative?: boolean
  url?: string
  dynamic?: (filename: string) => string
}

export type BuildBasePath = string | BuildBase

export type BuildBaseOptions = BuildBase & {
  assets?: BuildBasePath
  public?: BuildBasePath
}

This is easier to explain, here you can use relative, url, and dynamic without separating public from assets files which is what most projects would do. And support for separate assets and public is explained as an override of the general build base options.

We discussed with @Shinigami92 @sodatea and @sapphi-red, and the consensus was that we should try to hide these advanced options from the regular user (they are intended to help Framework authors more than final users, and are probably going to be used in the context of deploy adaptors?). So the suggestions were:

Don't remove the relative base shortcut, as it is something that most users will use (to deploy to github pages for example)
Rename build.baseOptions to base.advancedBaseOptions to make the intent more clear
Rename dynamic to runtime (unrelated to the above, but sounds more clear)

I don't have time to test this PR because there's a lot of code I'll have to refactor to get away from our current strategy for handling multiple hosts -- but I believe that the changes here would solve my team's problems long-term and I think they belong in core.
For a little context on our own use case, we build our application for four different targets:

production
qa
beta
onprem (i.e. to be included in a docker container and hosted on clients' own infra)

In the first three targets, the application lives on one domain (wandb.ai) while all the assets live on a CDN (cdn.wandb.ai). We've made this work by manually injecting a placeholder URL, which we then replace in CI, once for each target.
The onprem build is more complicated, though, since we have no knowledge ahead of time of exactly how it'll be hosted. To account for that, we ship the frontend build with the placeholder still in place, and perform replacement at runtime once we know where it'll be served. At least some of this replacement could be obviated by these changes, though not all. I also want to call out that for teams with many targets like this the alternative is to build n copies of their frontend (this is what we used to do) which, even with a super-performant build system, is extremely inefficient! I think there's a lot of value in Vite having a good story about how to support this.

This is really good to see; the API looks like it allows for a full range of customisation. Many thanks. 👌

We discussed this PR with the team, and we can't commit to an API until we get more feedback from the ecosystem. We decided to release the API in its current form as an experimental feature in v3. If you are interested in seeing these PR features as stable, please get involved. You can directly comment here or join https://chat.vitejs.dev to chat.

I just came across this PR when it was mentioned to me here: https://github.com/jy0529/vite-plugin-dynamic-publicpath/issues/13#issuecomment-1163928094
I'd love to share how this API benefits us and our use-case.
My team and I currently develop AIOSEO, the original SEO plugin for WordPress. Our plugin is currently running on over 3 million websites. This product has been on the market for 15 years as of today. About 2 years ago we did a complete rebuild of the plugin using Vue/Vue CLI.
Since all of our code lives inside our users websites, we have no way of knowing their domain name or path to the installed files until runtime. When we used Vue CLI we were able to use the handy webpack variable __webpack_public_path__ to fix this "on the fly".
However when we switched our build process to Vite a few months ago (🎉) there was no way to do this directly. We've been relying on the vite-plugin-dynamic-publicpath package to address this for us and this works okay, with some limitations. For example, we can't use import.meta.url anywhere as it always points to the wrong path. Another limitation is with web workers; we can only use web workers by adding them inline: ?worker&inline
We then have to rewrite the path to the URL's when in production like so:
if (import.meta.env.PROD) {
	const publicPath = window.aioseo.urls.publicPath || '/'
	window.__aioseo_dynamic_handler__ = importer => {
		return `${publicPath}dist/${import.meta.env.VITE_VERSION}/assets/${importer.replace('./', '')}`
	}
	window.__aioseo_dynamic_preload__ = preloads => {
		return preloads.map(preload => {
			return `${publicPath}dist/${import.meta.env.VITE_VERSION}/assets/${preload}`
		})
	}
}

Having the ability to do all of this directly inside vite would be 💯.
Our team is 100% behind vitejs/vue (even in the WP block editor where everyone else uses react!). We would really love to see this as a core feature.

Thanks for taking the time to share this use case @benjaminprojas, it looks like a perfect fit for this feature. And the current API should already allow you to do exactly what you want (docs for<EMAIL_ADDRESS>here https://main.vitejs.dev/guide/build.html#advanced-base-options). We are still discussing the final API (we have some ideas to make it more flexible), and it may completely change before v3, so please pin your Vite version if you use it. We are probably going to release it as experimental in v3, and try to keep it stable, as we will have another chance to rethink the API once we move from experimental to a stable feature.
If you test the API in your projects, please come back with feedback about how it is working for you.

Not sure if this is a bug or not, but the experimental.renderBuiltUrl option does not seem to apply to the asset preloading code. We are planning on using this option to load assets from a different CDN depending on which environment the app is deployed to, and we'd rather not run different builds for each environment.

@sciyoshi There's a issue here #9680.

This doesn't seem to support dynamic imports as in:
import React, { lazy, Suspense } from 'react'

const TodosList = lazy(() => import(
  './components/TodosList'
  )
)

const App = () => {
    //...
    <Suspense fallback={
Loading...
 }>
        <TodosList todos={ todos } />
    </Suspense>
}

The app directory is nested from site root hence the resulting TodosList.{hash}.js chunk ends up with incorrect URL and throws 404. Is there any workaround for this or am I doing/missing something?

@sciyoshi @paulcgdev would you review if #9938 would accommodate your use cases:

https://github.com/vitejs/vite/pull/9938

@patak-dev it looks likely it might work for my use case since I just need to do the same thing I'm doing for the asset files on per app dir for the dynamic chunks in the renderBuiltUrl (or wherever this ends up when out of experimental). Currently, I have something like:
experimental: {
  renderBuiltUrl: (fileName : string, { hostType }) => {

    if (hostType === 'js') {
      return {
        runtime: `window.myAppDir.url + '/dist/${ fileName }'`
      }
    }

    return fileName
  }
}

...which correctly loads the asset files on build for example from src/apps/page/settings/assets/react.svg.
The backend is from a WordPress plugin hence the root dir would be nested in something like https://domain.tld/wp-content/plugins/my-plugin. So the asset file in the example above would be loaded with https://domain.tld/wp-content/plugins/my-plugin/dist/apps/page/settings/assets/react.{hash}.svg and so, I just need the same thing for dynamic imports.

@paulcgdev yes, it should work after #9938 using only experimental.renderBuiltUrl. The only issue is that window.myAppDir.url +  will be appended to each so there may be a bit of repetition, and this replacement is done after minification so maybe a helper could be used in case that is an issue.

@patak-dev should be better than nothing... so, looking forward to trying it out. 🙂


~((√ZVIDEOs√))~ Turkish Referee Elif Karaarslan Leaked Full Video 2024 LINK Viral on Social Media X Today [FXC13KX]

33 sec ago, ™™Elif Karaarslan', ZFULL ™™Elif Karaarslan' Leaks Video On Social Media X Twitter[2B75K]

™™Elif Karaarslan''s latest video has taken social media by storm, captivating viewers and sparking widespread discussions. This young digital creator has garnered significant attention for her engaging content, particularly with her recent Spiderman-themed video that has gone viral. Fans are eagerly searching for where to watch the full video, turning to platforms like Instagram, X (formerly Twitter), and Discord for access.
As the buzz around ™™Elif Karaarslan' grows, fans are actively sharing their reactions online. The viral success of her video highlights the powerful role of social media in propelling creators into the spotlight.
Thank You

vxcbvcb

FG

vf

FG

vf

hgkhjk


Various delta adsc improvements

Fix and test panic on double remove
Avoid storing the full last xds response; this is expensive
Avoid global var usage in test

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test lint

unit-tests-arm64_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test lint

unit-tests-arm64_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test unit-tests-arm64

unit-tests_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test lint

unit-tests_istio
8f27394b92bd2f686f3e94ec34bee3eafa09e4a4
link
true
/test unit-tests

unit-tests-arm64_istio
b5795c073aa957a2ac8f057bb3d078224db52c6c
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b5795c073aa957a2ac8f057bb3d078224db52c6c
link
true
/test unit-tests-arm64

unit-tests_istio
b5795c073aa957a2ac8f057bb3d078224db52c6c
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
b5795c073aa957a2ac8f057bb3d078224db52c6c
link
true
/test unit-tests

unit-tests-arm64_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test unit-tests-arm64

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests-arm64

unit-tests_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests

unit-tests-arm64_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests

unit-tests-arm64_istio
80d27f500860e8620ab1d1ad47470fc14d21ad42
link
true
/test unit-tests-arm64

lint_istio
611b3f83fc053f35b98fdbc31693d2bf72fcd5f6
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
611b3f83fc053f35b98fdbc31693d2bf72fcd5f6
link
true
/test lint

integ-telemetry-mc_istio
611b3f83fc053f35b98fdbc31693d2bf72fcd5f6
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Stable DestinationsNavigator?

Hi, I'm wondering if it is possible to add a @Stable annotation to the DestinationsNavigator interface. After reading this article https://multithreaded.stitchfix.com/blog/2022/08/05/jetpack-compose-recomposition/ and reviewing the skipping rules https://developer.android.com/jetpack/compose/lifecycle#skipping I think the same issue as described in that article for view models applies to compose destinations.
Namely some code like
@Composable
fun FooScreen(navigator: DestinationsNavigator) {
  FooContents(onBack = { navigator.popBackStack() })
}
@Composable
fun FooContents(onBack: () -> Unit) { .. }

may miss out on potential skipping optimisations because the onBack lambda is capturing the DestinationsNavigator.
The Now In Android sample app also wraps the NavHostController in a @Stable class: https://github.com/android/nowinandroid/blob/main/app/src/main/java/com/google/samples/apps/nowinandroid/ui/NiaAppState.kt#L56
I think the contract should be possible to meet here as the DestinationsNavigator doesn't have any properties so it's just the equals contract that needs meeting.

A stable type must comply with the following contract:

The result of equals for two instances will forever be the same for the same two instances.
If a public property of the type changes, Composition will be notified.
All public property types are also stable.

Compose considers a type stable only if it can prove it. For example, an interface is generally treated as not stable

Yeah I actually made my own wrapper for the destinations navigator in a multimodule project, and it's marked as stable and working perfectly fine.
So the workaround may be to wrap the navigator in your own interface.

Hi @Skeletonxf ! 👋
First of all, have you actually noticed unexpected recompositions? I cannot test myself atm, but I remember checking this and I had no unexpected recompositions 🤔

On the app I've actually been building no, we've not been measuring recompositions and/as there hasn't been any performance issues.
However, I can adapt the example in the article I shared to reproduce the 'unstable lambda' issue with DestinationsNavigator

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            RecomposeTestTheme {
                // A surface container using the 'background' color from the theme
                Surface(
                    modifier = Modifier.fillMaxSize(),
                    color = MaterialTheme.colors.background
                ) {
                    DestinationsNavHost(navGraph = NavGraphs.root)
                }
            }
        }
    }
}

class RecompositionTestViewModel: ViewModel() {
    val state = MutableStateFlow(listOf("0", "1"))

    fun addName() {
        state.getAndUpdate { s -> s.plus(s.size.toString()) }
    }

    fun handleNameClick() {
        println("Clicked")
    }
}

@Composable
@Destination(start = true)
fun RecompositionTest(
    navigator: DestinationsNavigator
) {
    val viewModel = remember { RecompositionTestViewModel() }
    val state by viewModel.state.collectAsState()

    NameColumnWithButton(
        names = state,
        onButtonClick = viewModel::addName,
        onNameClick = viewModel::handleNameClick,
        onBackClick = { navigator.popBackStack() },
    )
}

@Composable
fun NameColumnWithButton(
    names: List<String>,
    onButtonClick: () -> Unit,
    onNameClick: () -> Unit,
    onBackClick: () -> Unit,
) {
    Column {
        names.forEach {
            CompositionTrackingName(name = it, onClick = onBackClick)
        }
        Button(onClick = onButtonClick) { Text("Add a Name") }
    }
}

@Composable
fun CompositionTrackingName(name: String, onClick: () -> Unit) {
    Log.e("*******COMPOSED", name)
    Text(name, modifier = Modifier.clickable(onClick = onClick))
}

Switching the onClick argument for CompositionTrackingName to the view model's method reference or a method reference for the DestinationsNavigator (navigator::popBackStack) ensures the expected log output where adding a new name only composes that new CompositionTrackingName. However, with no modifications the code in the snippet produces a log for every name in the list on each click of the button. ie clicking Add a name when there's 5 already logs 0 through 5.

The issue here is the List not being stable, and not the navigator itself.

The logging for compositions is for the CompositionTrackingName which doesn't take the List as an argument though.

@raamcosta It does, through an argument of an object that implements the Function1 interface.
@Skeletonxf  But I also think that compose is not smart enough to understand that CompositionTrackingName is smart enough to understand that the it argument which is part of the forEach block is not part of the List. I feel like we should inspect a compose compiler report instead of continuing this discussion.

@Skeletonxf thanks for the example. I got some time to try it out myself 🙂
Basically, it seems also if I use navigator::popBackStack, it fixes the issue. But if I annotate DestinationsNavigator with @Stable that also does the trick. Same thing for NavController and ViewModel. Since they're not annotated either, if I use method reference it avoids some compositions. This is very interesting thing to know, thanks a lot!
I don't see an issue with annotating DestinationsNavigator as Stable. It doesn't have any public fields, so the last two points are fine, and implementations don't override equals which means it defaults to reference comparison. So for two instances calling equals on them will always wield the same results for sure.

Thanks @raamcosta for making this enhancement! We're optimizing our Composables right now and 1.7.22-beta changed a  ton of items in our Compose Compiler metrics report from "unstable" to "stable".


using navtive JS to do obvious lodash stuff, reducing bundle size

@gilamran did you test this? I think there are multiple bugs here...

The module-registry doesn't have any tests except E2Es (That passed).
I think that I'll be best if I'll add a full unit test to this code...
Reject the PR and I'll create a new one with tests.

I actually really like that we depend on e2e, this library supports some very complicated use cases and we need to test them e2e. The problem here is that we have no test for event listener yet (and also probably not for rpc)

E2E does test the module registry, but in a very basic way.
I've added some minimal unit-tests.
please review


why there is release commit in the git repo?

Hi,
This is a question on the dev environment than an issue on the rancheros. I find it is not possible to checkout the commit that the official release was made, e.g. v4.4 is at 8afcd69. But if you do a
git checkout 8afcd69
In your repo, it will report a bad object. Can anyone explain how this could happen?
BR/Liyi

Try git fetch -t ....  I believe it's because the commit is not on a branch, but just one off and tagged.  We will change this in the future.

Thanks @ibuildthecloud! Now I can be calm with ease. :)
BTW, ubuntu 16.04 now have zfs built into kernel. Will rancheros follow?  I was about to make a PR to have zfs built into kernel, not sure if that will be welcome.

@liyimeng I'm afraid of the legal implication there.  Canonical has a much bigger legal team :)  You can definitely get ZFS to work in RancherOS, but I don't think we will include it by default.

I read Internet, some ZFSonLinux guys say it is legally to have zfs in Kernel and then see Ubuntu is doing so. Make me believe the legal issue was resolved. Did not know that  legal = bigger legal team though :)
Anyone, thanks so much again!  I will close this issue now.

@liyimeng Apparently it's hard to get lawyers to agree: https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/

@ibuildthecloud surprise, surprise that it is GPL guys shout out. The discussion I read have been looking from Oracle perspective.


Use state serializer content type when saving actor states.

Description
Use state serializer content type when saving dapr states.
Issue reference
Please reference the issue this PR will close:  https://github.com/dapr/java-sdk/issues/1031
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

I am want to take this PR, although it is a breaking change.

Be my guest. Thanks for take it.

Did I understand correctly that @artursouza will take this PR to the goal?
Or Can I still do something? like fixing Integration tests, or documentation?

@artursouza Qq if state serializer is used when serializing, shouldn't there be an option during desirialization as well?
Also do you think serializer option could be part of StateOptions? useCustomSerializer or useStateSerializer, and that could be used during both Save and Get State also?

@artursouza Qq if state serializer is used when serializing, shouldn't there be an option during desirialization as well? Also do you think serializer option could be part of StateOptions? useCustomSerializer or useStateSerializer, and that could be used during both Save and Get State also?

Can you elaborate because this PR is just about setting the content type.

Did I understand correctly that @artursouza will take this PR to the goal? Or Can I still do something? like fixing Integration tests, or documentation?

Sorry for the ambiguity. By taking this PR, I meant accepting it. But the validation is failing.

Did I understand correctly that @artursouza will take this PR to the goal? Or Can I still do something? like fixing Integration tests, or documentation?

Sorry for the ambiguity. By taking this PR, I meant accepting it. But the validation is failing.

Ah sorry, I missed your answer. Perhaps some NPE exception somewhere, I can have a look

Dapr side car doesn't seem to like the content type if the state is null. I checked for it. Please review @artursouza

@mukundansundar did you have time to review this MR?

I don't see the button "Merge PR", is it because the branch is out of date? or because I don't have access to merge a PR ?

Only maintainers have the ability to merge - cc: @artursouza plz take another pass

@holopin-bot @antoniomaria Thank you!


Issue row redesign in dashboard

What
Redesign how we showcase issues across Polar (dashboard/sites etc) to reflect some incoming and updated changes that all influence what & how we show Polar date related to issues e.g

https://github.com/polarsource/polar/issues/1104
https://github.com/polarsource/polar/issues/1105
https://github.com/polarsource/polar/issues/1125
https://github.com/polarsource/polar/issues/1103
https://github.com/polarsource/polar/issues/1109

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog :^)

Update https://github.com/polarsource/polar/issues/1228 once it's done

Design & Figma link: https://www.figma.com/file/1p2oOjsRBgSrr3SC4zySJG/Polar-v0.3%3A-Rewards-%26-Social?type=design&node-id=288-1691&mode=design&t=FphuEgKnbb5OOyUW-0


ENH: Remove numpy legacy RNG

Currently, randomness is handled via numpy.random. This should be replaced by a JAX random number generator.

Should switch to JAX rng! This was always just a placeholder.

Done in #38


clearPeriodicTimer called before removing subscribers

Hello everyone,
I am using PeriodicTimer in my Topic and I noticed that they are still active even if there is no more subscribers.
I found that clearPeriodicTimer() is called before the cleanTopic() function. As we check if there is no more subscribers before removing the last one, clearPeriodicTimer() is never called.
We must also replace clearPeriodicTimer() with cancelPeriodicTimer()
https://github.com/GeniusesOfSymfony/WebSocketBundle/blob/e2f61a50aa59733eedcfa7dbda87295c616f673d/Server/App/Dispatcher/TopicDispatcher.php#L199-L202
  0 === count($topic)  => count($topic) cannot be 0 here
https://github.com/GeniusesOfSymfony/WebSocketBundle/blob/ffcb476aaff2290fbafa878215717ccf438ef650/Topic/TopicManager.php#L135-L146
I did not read the full bundle so maybe I am wrong.
Thank you in advance for your help :)
(Tested on 1.8.13)

Fixed in 1.10.3 for 1.x and released, will be fixed in 2.5.0 when next 2.x tag comes around.


Standardize the ug

The ug does not look standardized.
The ug should look like it was written by one person.
Let's make the format of the ug standardized.

Codecov Report

Merging #291 (5a6d151) into master (02cc78e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #291   +/-   ##
=========================================
  Coverage     63.42%   63.42%
  Complexity      815      815
=========================================
  Files           140      140
  Lines          2906     2906
  Branches        379      379
=========================================
  Hits           1843     1843
  Misses          937      937
  Partials        126      126

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

LGTM


Bug: Graphql schema Check Failed after latest release

What are you trying to achieve?
In the pre-commit configuration, there are problems with the GraphQL schema check following the most recent release.
Steps to reproduce the problem

Clone the latest salero repo
cd saleor
python manage.py get_graphql_schema | diff saleor/graphql/schema.graphql -

What did you expect to happen?
The schema check should yield no variances between the result obtained from the get_graphql_schema method and the saleor/graphql/schema.graphql file
Logs
< Event sent when user requests to delete a payment method.
<
< Added in Saleor 3.16.
<
< Note: this API is currently in Feature Preview and can be subject to changes at later point.
< """
< type StoredPaymentMethodDeleteRequested implements Event @doc(category: "Payments") {
<   """Time of the event."""
<   issuedAt: DateTime
<
<   """Saleor version that triggered the event."""
<   version: String
<
<   """The user or application that triggered the event."""
<   issuingPrincipal: IssuingPrincipal
<
<   """The application receiving the webhook."""
<   recipient: App
<
<   """
<   The user for which the app should proceed with payment method delete request.
<   """
<   user: User!
<
<   """
<   The ID of the payment method that should be deleted by the payment gateway.
<   """
<   paymentMethodId: String!
<
<   """Channel related to the requested delete action."""
<   channel: Channel!
< }
<
< """
< Event sent to initialize a new session in payment gateway to store the payment method.
<

Environment
Saleor : 3.18.3
Poetry (version 1.6.1)
Operating System: Ubuntu 22.04.3 LTS
Python Version: 3.9.18

Arę you sure python manage.py get_graphql_schema is not crashing for you?

@patrys I'm confident that python manage.py get_graphql_schema is not causing any crashes on my end.

I don't think it's crashing because I haven't made any modifications.
What steps can I take to confirm that manage.py is running smoothly without any crashes?
Previously, it was functioning well with my custom modifications.
To validate, I cloned the repository freshly with the latest releases and attempted to run it, but there's a significant difference in the output, and it doesn't seem to make sense.

Can you run the command without the  | diff … part and check if it outputs the schema?

@patrys  Yes it does
"""
Event sent when user continues a tokenization of payment method.
Added in Saleor 3.16.
Note: this API is currently in Feature Preview and can be subject to changes at later point.
"""
type PaymentMethodProcessTokenizationSession implements Event @doc(category: "Payments") {
"""Time of the event."""
issuedAt: DateTime
"""Saleor version that triggered the event."""
version: String
"""The user or application that triggered the event."""
issuingPrincipal: IssuingPrincipal
"""The application receiving the webhook."""
recipient: App
"""The user related to the requested action."""
user: User!
"""Channel related to the requested action."""
channel: Channel!
"""Payment gateway data in JSON format, received from storefront."""
data: JSON
"""
The ID returned by app from PAYMENT_METHOD_INITIALIZE_TOKENIZATION_SESSION webhook.
"""
id: String!
}

Is that all the command returns? it should output many screens of text, starting with:
schema {
  query: Query
  mutation: Mutation
  subscription: Subscription
}


Cannot reuse WinBle after Dispose

When I call dispone of WinBle, cannot reuse this object even I called Initialize again.
could you check this?
[ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception: Bad state: Cannot add new events after calling close
#0      _BroadcastStreamController.add (dart:async/broadcast_stream_controller.dart:243:24)
#1      WinBle._processMessage
package:win_ble/src/win_ble.dart:89
#2      WinBle.initialize.<anonymous closure>
package:win_ble/src/win_ble.dart:56
#3      _rootRunUnary (dart:async/zone.dart:1434:47)

@dirablue yes some part missing for reinitialising streams after calling dispose , will fix this
till then i would suggest , don't use dispose

@rohitsangwan01
got it. thank you

fixed in release 1.0.0


Fill in CloudWatch documentation

I filled in all AWS docs pages, but I don't remember if/where Codium documented their CloudWatch configuration.

Closing as we can probably just read AWS docs if we need to re-do or change anything.


[Feature]: integration of vite-plugin-lit-css for better DX

Hi! Currently, I'm developing the vite-plugin-lit-css as my free time project. Unfortunately, I do not have enough feedback :c an I think this project could be suitable for trying to adopt it.
This plugin tries to fix some problems with the lit css ecosystem, in this case, allows to remove all
css`${usafeCss(styles)}`

overload, to simply import styles as any other framework does, keeping all the power of vite css(scss, sass, etc).
PD: link to npm package https://www.npmjs.com/package/vite-plugin-lit-css

Hello @thebug404 It's seem to be realed to external regex used by rollupOptions since it checks for lit string for external dependencies.
I change regex based on create vite template for older version of vite 3e60b77


Uncaught TypeError: Cannot read property '_pasvSocket' of null

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Unknown Windows Version
Thrown From: Remote-FTP package, v0.7.8
Stack Trace
Uncaught TypeError: Cannot read property '_pasvSocket' of null
At C:\Users\fred369h\.atom\packages\Remote-FTP\lib\connectors\ftp.js:321

TypeError: Cannot read property '_pasvSocket' of null
  at C:\Users\fred369h\.atom\packages\Remote-FTP\lib\connectors\ftp.js:321:19

Commands

Config
{
  "core": {}
}

Installed Packages
# User
color-picker, v2.0.13
drunken-php, v0.2.1
Remote-FTP, v0.7.8

# Dev
No dev packages

Can you please checkout the last version from github and test?

Patch is published now, if the issue persists after the latest update please reopen the issue


take year boundaries into account

e.g. if you are scheduling a race on december 30th for january 2nd, that will not work right now

no i just handled this on my way


Queue scheduler fails to create queue on broker

Saw this is the logs when colocated test was failing:
WARNING: Receiver closed with error
io.vertx.core.impl.NoStackTraceThrowable: Error{condition=amqp:internal-error, description='AMQ219001: error creating temporary queue, Journal must be in state=LOADED, was $
STOPPED]', info=null}
2017-09-08 13:24:14 ERROR QueueScheduler:145 - Error adding broker
java.util.concurrent.ExecutionException: io.vertx.core.impl.NoStackTraceThrowable: Error{condition=amqp:internal-error, description='AMQ219001: error creating temporary que$
e, Journal must be in state=LOADED, was [STOPPED]', info=null}
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
at io.enmasse.queue.scheduler.QueueScheduler.lambda$connectionOpened$7(QueueScheduler.java:119)
at io.enmasse.queue.scheduler.QueueScheduler.lambda$executeBlocking$9(QueueScheduler.java:138)
at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:271)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Should be fixed by #175


Getting Unsupported operation: Infinity or NaN toInt.

Randomly getting  Unsupported operation: Infinity or NaN toInt.  while zooming or navigating through Map. Steps are not reproducible but many times occur.
======== Exception caught by widgets library =======================================================
The following UnsupportedError was thrown building _VectorTileLayer-[<'clgp8xzs200b301qm7i8k8xo4_vnone_VectorTileLayer'>](dirty, state: _VectorTileLayerState#cc4f6):
Unsupported operation: Infinity or NaN toInt
When the exception was thrown, this was the stack:
#0 double.toInt (dart:core-patch/double.dart)
#1 double.round (dart:core-patch/double.dart:193:34)
#2 CustomPoint.round (package:flutter_map/src/core/point.dart:57:41)
#3 FlutterMapState.getNewPixelOrigin (package:flutter_map/src/map/flutter_map_state.dart:596:47)
#4 new TilePositioningState (package:vector_map_tiles/src/grid/grid_tile_positioner.dart:94:18)
#5 _VectorTileLayerState.build (package:vector_map_tiles/src/grid/grid_layer.dart:332:9)
#6 StatefulElement.build (package:flutter/src/widgets/framework.dart:5080:27)
#7 ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4968:15)
#8 StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5133:11)
#9 Element.rebuild (package:flutter/src/widgets/framework.dart:4690:5)
#10 BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2743:19)
#11 WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:863:21)
#12 SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1289:15)
#13 SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1218:9)
====================================================================================================

Thanks for the issue. Can you confirm which version of the library you're using? If it's 4.0, you may want to try  3.3.5 instead.

I'm having troubles reproducing. Can you provide the exact version of flutter_map and vector_map_tiles (e.g. from pubspec.lock) and if this is in your own application or one of the example applications?
Looking at flutter_map is a similar issue: https://github.com/fleaflet/flutter_map/issues/409

There's historically been a few cases of that error. I think most recent was https://github.com/fleaflet/flutter_map/issues/1370 which hopefully is resolved.

@greensopinion
I have encountered that when enableMultiFingerGestureRace is enable in FlutterMap widget then this is issue is being produced frequently.


Bounce behaves strangely with small objects

Godot 4.02
Windows 10
Intel(R) Core(TM) i7-7700K CPU
Nvidia 2080 Super
Let me give you a little bit of context on how i've found this potential issue. I'm making a pinball using real measurements, meaning that the ball actually has a radius of 1.4cm. The issue that i have is that the ball does not bounce on any part of the pinball even with a material with bounce=1.
After some testing :

Raising the radius enables the bouncing at some point but i'm not sure it's relevant or more related to the angular or linear speed (Check scene bounce2 on MRP)
Droping sphere from different heights leads to different behaviours. The weirdest one is the ball bouncing higher and higher (check scene bounce on MRP)

EDIT : Please check the difference with godot physics engine
bouncing-godot-jolt.zip

That does look a bit strange. I'll see if I can reproduce it in Jolt's Samples application.
In the meantime, it might be relevant to point out something written under the "Conventions and limits" part of Jolt's documentation:

Note that the physics simulation works best if you use SI units (meters, radians, seconds, kg). In order for the simluation to be accurate, dynamic objects should be in the order [0.1, 10] meters long and have speeds in the order of [0, 500] m/s. Static object should be in the order [0.1, 2000] meters long. If you are using different units, consider scaling the objects before passing them on to the physics simulation.

Your objects obviously fall within these conventions, so I wouldn't expect them to behave like this, but you're getting close to having objects that are "too small" for Jolt.
I should really mention this somewhere in the README.
Thanks for all the issues by the way, very much appreciated. Keep them coming. :)

the ball actually has a radius of 1.4cm

dynamic objects should be in the order [0.1, 10] meters long

Your objects obviously fall within these conventions, so I wouldn't expect them to behave like this, but you're getting close to having objects that are "too small" for Jolt.

Ball diameter is 2.8cm so it is smaller than 0.1 meter(10cm) and it isn't within range.
I think it is a good idea that OP makes everything in project 5 times bigger and test it again.

Ball diameter is 2.8cm so it is smaller than 0.1 meter(10cm) and it isn't within range.

Yes, you're right, sorry, I completely skimmed over the numbers and didn't address the dimensions in bounce2.tscn. Those are indeed not within the above mentioned range and are likely too small.
The sphere shapes in bounce.tscn are however 0.2 m in diameter, and still behave somewhat strangely.
I've managed to reproduce this in Jolt's Samples application, so now I'm curious to hear what @jrouwe thinks about this.
Here's the equivalent setup in Samples:
CreateFloor();

BodyCreationSettings ball1(new SphereShape(0.1f), RVec3(0, 0.15f, 0), Quat::sIdentity(), EMotionType::Dynamic, Layers::MOVING);
ball1.mOverrideMassProperties = EOverrideMassProperties::CalculateInertia;
ball1.mMassPropertiesOverride.mMass = 1.0f;
ball1.mRestitution = 1.0f;
ball1.mLinearDamping = 0.1f;
ball1.mAngularDamping = 0.1f;

BodyCreationSettings ball2(new SphereShape(0.1f), RVec3(-0.25f, 0.16f, 0), Quat::sIdentity(), EMotionType::Dynamic, Layers::MOVING);
ball2.mOverrideMassProperties = EOverrideMassProperties::CalculateInertia;
ball2.mMassPropertiesOverride.mMass = 1.0f;
ball2.mRestitution = 1.0f;
ball2.mLinearDamping = 0.1f;
ball2.mAngularDamping = 0.1f;

BodyCreationSettings ball3(new SphereShape(0.1f), RVec3(-0.5f, 0.17f, 0), Quat::sIdentity(), EMotionType::Dynamic, Layers::MOVING);
ball3.mOverrideMassProperties = EOverrideMassProperties::CalculateInertia;
ball3.mMassPropertiesOverride.mMass = 1.0f;
ball3.mRestitution = 1.0f;
ball3.mLinearDamping = 0.1f;
ball3.mAngularDamping = 0.1f;

mBodyInterface->CreateAndAddBody(ball1, JPH::EActivation::Activate);
mBodyInterface->CreateAndAddBody(ball2, JPH::EActivation::Activate);
mBodyInterface->CreateAndAddBody(ball3, JPH::EActivation::Activate);

Which looks like this:
https://github.com/godot-jolt/godot-jolt/assets/4884246/6ac05869-adb2-47e5-9f3d-2ab7e7b324ee

The behavior is certainly a bit odd. I'd need to step through the simulation to get to a definitive conclusion, but at first glance the objects are indeed quite small and don't work well with the default PhysicsSettings. First of all I set the PhysicsSettings::mSpeculativeContactDistance to 0.005 and mPenetrationSlop to 0.005 too (was 2 cm). But with a body with EMotionQuality::Discrete the body can step into the floor and the next step it is pushed out again (at which point it gains extra velocity). Switching the body to the LinearCast quality and lowering mLinearCastThreshold to 0.2 to ensure that linear casts are actually performed for these small shapes makes the simulation behave better.

I only just now noticed that @mgiraud had actually enabled "Continuous CD" (aka LinearCast) for the bodies in the repro project attached above, so my port wasn't entirely accurate. Unfortunately I haven't exposed mLinearCastThreshold in the project settings, so that's something I need to do.
I can confirm that changing the project settings "Contact Speculative Distance" (aka mSpeculativeContactDistance) and "Contact Allowed Penetration" (aka mPenetrationSlop) to the values you suggested, along with the above mentioned CCD settings, makes the simulation behave better in the repro project as well.
Although, I just randomly tried setting the linear/angular damping to 0 for the spheres, and that seems to undo some of the effect of the CCD and they once again start bouncing higher and higher.

I just released version 0.1.0-rc3, which includes a new project setting for mLinearCastThreshold, as well as a project setting for mLinearCastMaxPenetration.
Note that they're both percentages in Godot Jolt, as opposed to factors, so the value of 0.2 for the movement threshold mentioned earlier would instead be 20% in Godot Jolt.

I've done some further debugging and found a bug in speculative contact resolution, with this fix it looks like:
https://github.com/godot-jolt/godot-jolt/assets/1621693/1213daa5-2461-4fc4-bb4b-2887fa0bab31
The rightmost sphere doesn't bounce because its velocity is lower than PhysicsSettings::mMinVelocityForRestitution. Adding this to the test:
PhysicsSettings settings = mPhysicsSystem->GetPhysicsSettings();
settings.mMinVelocityForRestitution = 0.5f;
mPhysicsSystem->SetPhysicsSettings(settings);

Makes it look like this:
https://github.com/godot-jolt/godot-jolt/assets/1621693/85264ba5-f7f9-4e9f-9969-71cdd7fae452
You can see it still picks up speed, but I don't think that can be avoided unless you have a restitution < 1 or more linear damping is applied. This is why it happens:

The rightmost sphere doesn't bounce because its velocity is lower than PhysicsSettings::mMinVelocityForRestitution

Seems like I have another project setting to add. :)
I'll make sure to update Jolt to get the bug fix in.

You can see it still picks up speed, but I don't think that can be avoided unless you have a restitution < 1 or more linear damping is applied.

Any theories as to why Godot Physics doesn't seem to exhibit this problem, even without CCD? For reference, here's what that looks like:
https://github.com/godot-jolt/godot-jolt/assets/4884246/ef11e7ba-e97f-4827-93e8-41de759afd41

I honestly have no idea, I tried several theories but didn't find anything.

Running with the bugfix for speculative contacts, as well as the new project setting "Bounce Velocity Threshold" (that maps to mMinVelocityForRestitution) and the now custom restitution combiner, this is what Godot Jolt looks like if you dial the restitution back to 0.9:
https://github.com/godot-jolt/godot-jolt/assets/4884246/9a085892-95c6-47e3-9453-8b7f34b0f454
Since this issue was mostly about small objects acting strangely, and the restitution 1.0 thing seemingly affecting objects of all sizes, I'll go ahead and close this now.

The issue that spheres bounce higher and higher should have been fixed by jrouwe/JoltPhysics#1328.
Note that this change needs to be integrated to godot-jolt before it can be tested.

The above mentioned change has now been pulled in (#1019).


CSUB-155 Delete an authority

Description of proposed changes:
Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[X] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[X] The positive scenario is exercised
[X] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #557 (5af410f) into dev (6d24926) will increase coverage by 0.08%.
The diff coverage is 97.05%.

@@            Coverage Diff             @@
##              dev     #557      +/-   ##
==========================================
+ Coverage   78.16%   78.24%   +0.08%
==========================================
  Files          46       46
  Lines        8551     8593      +42
==========================================
+ Hits         6684     6724      +40
- Misses       1867     1869       +2

Impacted Files
Coverage Δ

pallets/creditcoin/src/lib.rs
88.44% <75.00%> (-0.17%)
:arrow_down:

pallets/creditcoin/src/tests.rs
99.22% <100.00%> (+0.01%)
:arrow_up:

pallets/creditcoin/src/weights.rs
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@jfrank-summit @atodorov I noticed that this function was meant to be named 'remove_authority'. Do we stick with 'delete' or do I change it?

@jfrank-summit @atodorov I noticed that this function was meant to be named 'remove_authority'. Do we stick with 'delete' or do I change it?

I don't think it really matters, i prefer remove but not sure why


Get traffic bandwidth on wan interface

Hi
Is there a way to get the consumed speed on wan interface like the data we get under Status -> Traffic Graph?
Bandwidth In and Bandwidth Out
Thanks

Following up on this
A new function interface_stats has been added that partly answers your requirement here, the issue however is that the way bandwidth usage is computed in the pfSense GUI in these graphs under Status -> Traffic is via client side javascript that computes rates based on the cumulative total bytes that pfSense provides underneath.
In short, you can achieve the same effect but you'll have to do the same as the pfSense GUI does by polling (fauxapi) and computing the bandwidth rates you are looking for.
Release 1.3 due shortly
N


WSL Ubuntu Python Path - not working [Aider works in zsh terminal but not with this extension]

NOTE: Aider works in ZSH terminal on Ubuntu. It works in the terminal in Visual Studio Code. But the Aider.Composer Extension is not working.
I have tried the following paths for the Python Path.
vscode://settings/aider-composer.pythonPath'

/usr/bin/python3
/bin/python3
/usr/bin/python3.12
/usr/local/bin/python3
~/.local/bin/python3

I believe the correct path should be: /usr/bin/python3.12

I have also tried the alternative method of setting up a virtual env.

python3 -m venv env
source env/bin/activate
pip install aider-chat flask

and last
I also tried

code --uninstall-extension lee2py.aider-composer && code --install-extension lee2py.aider-composer
Uninstalling lee2py.aider-composer...
Extension 'lee2py.aider-composer' was successfully uninstalled from WSL: Ubuntu-24.04!
Installing extensions on WSL: Ubuntu-24.04...
Installing extension 'lee2py.aider-composer'...
Extension 'lee2py.aider-composer' v1.3.5 was successfully installed.

I also tried
code --uninstall-extension lee2py.aider-composer && code --install-extension lee2py.aider-composer
Uninstalling lee2py.aider-composer...
Extension 'lee2py.aider-composer' was successfully uninstalled from WSL: Ubuntu-24.04!
Installing extensions on WSL: Ubuntu-24.04...
Installing extension 'lee2py.aider-composer'...
Extension 'lee2py.aider-composer' v1.3.5 was successfully installed.

this need to start a server in the extension host. if use WSL, extension may not connect the server in the WSL?
when start a server in the WSL and listen to <IP_ADDRESS>, the windows host can connect this server by <IP_ADDRESS>?

this need to start a server in the extension host. if use WSL, extension may not connect the server in the WSL? when start a server in the WSL and listen to <IP_ADDRESS>, the windows host can connect this server by <IP_ADDRESS>?

Hi @lee88688, thanks for the great work.
I'm also using WSL on windows, I have the same issue.
Windows can NOT connect a server running on WSL by <IP_ADDRESS>, it's another address.
For example, mine is <IP_ADDRESS>
I get this address by running "ip a" command inside my WSL.
I hope this can help you to make aider-composer work in WSL

I am not sure if the official has provided relevant APIs for forwarding the host's port. so that I can use it to auto redirect the aider's server port.
by the way, @eddieai do you install the python and relative packages(aider-chat, flask) in WSL, and the python path is also in WSL's path.

I am not sure if the official has provided relevant APIs for forwarding the host's port. so that I can use it to auto redirect the aider's server port. by the way, @eddieai do you install the python and relative packages(aider-chat, flask) in WSL, and the python path is also in WSL's path.

I just forgot to pip install flask in my WSL python environment (I only installed aider-chat). After installing that and setting the aider-composer python path to the correct python environment, all works in VS Code WSL.
Thanks! We can close this issue IMO


Getting error "Amplify service is not available in the region us-west-1 init failed"

Describe the bug
First, I was having the problem described in #4918. After that I connected the app from console itself and was trying to connect the app using command amplify init --appId <ID>. That's when I encountered above error.
Amplify CLI Version
4.36.0
To Reproduce
Steps:

amplify init from console. The app is not created in console.
amplify add hosting>Hosting with Amplify Console (Managed hosting with custom domains, Continuous deployment). Get issue #4918.
Create app from console by linking from github
Try amplify init --appId <ID>.
Get the following error at terminal:
Amplify service is not available in the region us-west-1 init failed Error: Amplify service is not available in the region us-west-1  at Object.run (/home/rafee/.nvm/versions/node/v14.15.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/amplify-service-migrate.js:44:11)  at processTicksAndRejections (internal/process/task_queues.js:93:5)  at Object.run (/home/rafee/.nvm/versions/node/v14.15.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/initializer.js:96:5)

Expected behavior
Console app and terminal app gets connected
Screenshots

Desktop (please complete the following information):

OS: ubuntu 20.04-wsl
Node Version.: v14.15.1

Additional context
Add any other context about the problem here.

Amplify Console currently does not support backend environments powered by Amplify CLI in us-west-1  We are hoping to have support for this before the end of the year.

@litwicki It looks like there's still not support for us-west-1. Any update here?

@litwicki It looks like there's still not support for us-west-1. Any update here?

@djamcon we obviously missed that original target and apologize for that. We are working on getting an updated timeline given the new requirements for Amplify Admin UI as well, and will share as soon as we have an update.

@djamcon we obviously missed that original target and apologize for that. We are working on getting an updated timeline given the new requirements for Amplify Admin UI as well, and will share as soon as we have an update.

Thanks @litwicki. What do you mean new requirements?
Also, in that case, what is the shortest path forward to getting the Amplify Admin UI if we're currently working in us_west_1?

Thanks @litwicki. What do you mean new requirements?
Also, in that case, what is the shortest path forward to getting the Amplify Admin UI if we're currently working in us_west_1?

@djamcon just updating you that @kaustavghosh06 and I are reviewing our plans this week and will have an update on a timeline for us-west-1 before EOW.

@djamcon just updating you that @kaustavghosh06 and I are reviewing our plans this week and will have an update on a timeline for us-west-1 before EOW.

Any update on this timeline for supporting us-west-1?

I had a successful build yesterday, but today I am getting this error:
"Amplify service is not available in the region us-west-1"
Is Amplify available in us-west-1?  Or is this some temporary outage?

Will eu-north-1 be supported? I am getting the same error:
amplify init --appId foo
Note: It is recommended to run this command from the root of your app directory
? Do you want to use an existing environment? Yes
? Choose the environment you would like to use: sandbox
Using default provider  awscloudformation
Amplify service is not available in the region eu-north-1
Error: Amplify service is not available in the region eu-north-1


Extend Resoure API: User Grants

We want to implement the user grants requests in our new resource based api.
We currently have multiple different names for the user grants depending on the place where we use it. So we also want to align that.
Proposal: User Roles
Acceptance Criteria

[ ] Align naming to newly defined name (user roles?)
[ ] Naming is aligned in documentation, new api, etc. In places where we cant use the new naming we have a note, that it in future xy is used.
[ ] Create new service for user roles (is this needed? Or is it the user service?)
[ ] Implement the following requests
- [ ] User Role By ID
- [ ] Search User Roles (query possibilities analog to current implementation (mgmt api))
- [ ] CRUD
- [ ] Bulk Remove

Additional Information
Current Query in Management API:

UserGrantProjectIDQuery project_id_query
UserGrantUserIDQuery user_id_query
UserGrantWithGrantedQuery with_granted_query
UserGrantRoleKeyQuery role_key_query
UserGrantProjectGrantIDQuery project_grant_id_query
UserGrantUserNameQuery user_name_query
UserGrantFirstNameQuery first_name_query
UserGrantLastNameQuery last_name_query
UserGrantEmailQuery email_query
UserGrantOrgNameQuery org_name_query
UserGrantOrgDomainQuery org_domain_query
UserGrantProjectNameQuery project_name_query
UserGrantDisplayNameQuery display_name_query
UserGrantUserTypeQuery user_type_query

@livio-a @muhlemmer can you please have a look at the issue for estimation?
Also if the proposed naming makes sense?

user roles?

We roles defined in project and those are granted to users. If grant is too technical, what about "user authorization" like we currently use in the console.

Create new service for user roles (is this needed? Or is it the user service?)

Yes. because it involves organization, projects and users.

Implement the following requests

[ ] User Role By ID
[ ] Search User Roles (query possibilities analog to current implementation (mgmt api))
[ ] CRUD
[ ] Bulk Remove

We believe that Get by ID and CRUD is enough for one sprint. Bulk remove as a concept is something we have to find a solution for in general. (We can't just create N amount of remove events, that gave issues already the custom texts for example.)

First, we do #7592, #7649 and #7650


Remove global install in README

The README has you install observatory globally. This seemed incorrect to me, but I might be missing something. Feel free to close if wrong.
Thanks!

Ha, good find, thanks!


Broken image for private templates on first load

This happens only on fist loading of list.

Fixed in dev


Ignore 404 when deleting schedule

We only want to ensure that the schedule does not exist, so let's ignore 404 responses when deleting schedules

Would love to see a better proposal ;)


[Sluggable] Support for PHP 7.4

The default transliterator used for the slug creation throws deprecations warnings with PHP 7.4. This should be fixed upstream or another default implementation should be used.

Thank you for your contribution, @binarious.
As you noted, it is an upstream issue that we have no direct control over. A new default implementation is definitely an option, although one that is very far down on the priority list right now.
I'm sorry I can't be more helpful at this time.


new_version script gives wrong line endings on Windows

Not just on CHANGELIST.md but also VERSION

Did I fix it?  :-D


[Info] - Similar repo - reusability

Have you seen the following repo? Both of these are very similar but I really like overlay work been done in this repo - newworld-coordinate-tracker I'm wondering if both could assist each other.

Closing because we are no longer performing OCR since switched to Overwolf.


Looks fine, let's merge it and double check that :)


Make failback (balancer plus error) more usable and informative to users

Currently, during critical short-notice reloads and other immediate issues where we have to pull amigo from service, we have a choice between possibly ignorable notice/messages and a severe white page 503. We'd like to have something that is still AmiGO-like, but shuts out users from getting at bad data.

This gets the 503 page more in line with how the standard error.tmpl pages work.
A known feature/limitation is that it "highlights" the last error.


Add option to remember the last window position

Haven't yet updated all the translations.
Also made it such that the window is no longer movable when "Last position" isn't selected as it may be confusing if moving the window has no effect (this may not be desirable, if so it can be reverted).
Some additional thought:
The window center method could be converted to "Presets" for .lastPosition together with the current default position of .lastPosition. I imagine this being an additional dropdown with Options ["Default", "Center", "Custom"], where Custom is selected if the window is moved. This way the reset button could also be removed as resetting is a matter of changing it back to Default.

Changes: More reliable detection of deliberate window movement

Added the remaining translations using Deepl and Google Translate.

Im waiting for last 5 hours but no any one i find here..help me pls


popover-title: Remove class.

Fixes #26821
Remove bootstrap-tooltip class popover-title from code.
It was only used in user_card_popover for showing user avatar, so cleaned up properties that were duplicated or not required.

Removed  popover-content and popover-title classes and some additional ones that were not being used.

Added a bonus commit to remove the last vestiges of bootstrap-tooltip; otherwise, lgtm, marked to merge once CI passes, thanks for cleaning this up @amanagr!
We might find that the 5px margins are something we want to use a common class for in popovers.css, but I think it'll feel nicer to think about that as we're cleaning up the Bootstrap nav-list CSS and thus removing the last Bootstrap code affecting those popovers.


Always copy cumulusci.yml from default branch

Cute animal pic

Link to Trello card (if applicable)
https://trello.com/c/AuBMdrEm/287-always-use-cumulusci-project-config-from-main-branch
Description
The commit messages say what you did; this should explain why and/or how.

[x] Description is in Trello card

Steps to test/reproduce
Run any action that checks out a branch locally. Previously if the default branch made changes to cumulusci.yml the checkout would fail validation and crash the site. Now instead of failing we simply copy cumulusci.yml from the default branch every time and avoid crashing.
Show me
Provide screenshots/animated gifs/videos if necessary.

 Always use CumulusCI project config from main branch


Need date format for PAT table temporal columns

Should we use  '%Y-%m-%d %H:%M:%S'  ?

@vaishvikr Thank you for flagging this! Added date format to the patient table variables - birth_date and death_dttm.


Sharding console

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Excuse me, I just want to know, what do want do?


Initial content

Pull requests:

https://github.com/Senzing/poc-csv-tools/pull/2
https://github.com/Senzing/poc-csv-tools/pull/3


Pacifists can throw Items that Hurt People

Description

Pacifists have no block if the item deals damage on hit, IE: Can kill someone by cutting them with glass shards
Reproduction

Thow a glass shard as pacifist

Yeah, pacisfism is in need of some rework on what they should and should not be able to do. Right now throwing is just blocked by a few specific components attached to the item.


Palo Alto case study

I added the Palo Alto case study.

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.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

retest this please

staging is not working today, due to jenkins issues. this change LGTM

retest this please

retest this please

retest this please

Run Website_Stage_GCS PreCommit

staging
http://apache-beam-website-pull-requests.storage.googleapis.com/16915/case-studies/index.html
Merging


Update showcase.md

Add table and shields for plugins list

I like this. @kulakowka can you re-issue this PR to the auk branch? We're hoping to get the new docs out in the week or so.

@ekryski yes. i can do it. it here? https://github.com/feathersjs/feathers-docs/tree/auk/ecosystem

@kulakowka yup! That same table structure in each section will look great. Just make sure to keep the Feathers icon around to denote core maintained modules. 🍻

@ekryski cool! I do it tonight!

I really like this but it has unfortunately gone a little stale. I'm going to close this PR but it would be great to see this for the new Ecosystem page.


Environment variable assignments on Configure command line

For Unix, it's pretty easy to temporarly assign environment variables on the command line:
CC=clang ./config

On other platforms, it's not as easy, so therefore, this implements an alternative (VMS shown as example):
perl Configure "CC=whatevercc" vms-alpha

Futhermore, this also save away the environment values more effectively, and also makes sure the saved away values are used before anything on the environment when reconfiguring.

Should we use a flag like -e FOO=... rather than just matching on the pattern?

Why?  This is already a well known pattern, both with make and autoconf``s configure`...  and it doesn't compete with current option patterns either.

Okay, fine, thanks for the answer.

would it be appropriate to do something different.

Speaking of something different. As side note. It might be useful to "freeze" some variables. Well, it's not something one can do by assigning variables in makefile, but one might do something through template... Just in case for reference, In VC case it might be interesting to "freeze" environment variables such as CL, _CL_, INCLUDE, LIBPATH... So that one can re-run make "in another window" without having to replicate environment... Well, just a wild thought, might be worth considering in "background"...

Speaking of something different. As side note. It might be useful to "freeze" some variables. Well, it's not something one can do by assigning variables in makefile, but one might do something through template... Just in case for reference, In VC case it might be interesting to "freeze" environment variables such as CL, _CL_, INCLUDE, LIBPATH... So that one can re-run make "in another window" without having to replicate environment... Well, just a wild thought, might be worth considering in "background"...

Uhmmm, so preserving the environment in {perlenv} and recalling it when a ./Configure reconf is made, doesn't that do exactly what you ask for?  Or oh, are those environment variables that we ignore but that are used by the compiler?  That could be done, and quite easily so, just add this in your favorite targets:
        env => [ env('CL'), env('_CL_'), ... ],

That attribute is unused, but will automatically add those variables to $config{perlenv}...
...  but that makes me think that we probably need a lazy variant of sub env...

Uhmmm, so preserving the environment in {perlenv} and recalling it when a ./Configure reconf is made, doesn't that do exactly what you ask for?

Once again, it's just a wild thought that might be worth considering, eventually [or never]. Being a "wild thought" ii might be inconsistent and turn out dumb. But to elaborate. This is not only about environment variables at config time, but even at build time. This is why I brought up makefile template...

I see. I did think about that, but didn't finish the thought...

I wonder what's intention with squashing? I mean will everything be squashed?

I don't generally squash everything into a single commit.  That's simply not how I do things.

I don't generally squash everything into a single commit.

I wasn't directly suggesting to, but at the same time I see no point in keeping small adjustments resulting from feedback.

I wasn't directly suggesting to, but at the same time I see no point in keeping small adjustments resulting from feedback.

I'll have another look...  but I try to partition into pieces that hold their own, so to say.

Ok, I think I've adressed all concerns expressed so far.

Merged.  7ecdf18d80cba14ad1afa6c0d18574d2ad2929c3 to e7a206694451be19432d079691610994473f53b7

Thank you!


No module named 'alpyne'

After installing pip install anylogic-alpyne, i encountered the error (No module named 'alpyne') when trying to run the script

After running the setup.py in the folder, it has addressed the issue.


[RIP-14] Specify user for Pre- and Post start commands

Docker implementation for this Pull Request:
https://github.com/theCapypara/riptide-lib/pull/6
See it for more details.
@Naftula70 @aptudock @hktudock
I can't add you as reviewers since you aren't collaborators of this repo, but can you still have a look? If I get no opposing comments I would merge this on Thursday.

@theCapypara for me ok

@theCapypara lgtm


(question) different configuration for each extractor

Checklist

[x] I'm asking a question

[x] I've looked through the README and FAQ for similar questions

[x] I've searched the bugtracker for similar questions including closed ones

Question

Is there any way to use different configurations for different extractors? For YouTube I would like it to be used:
-f "webm[height=1080][fps=60]"+bestaudio/"webm[height=720][fps=60]"+bestaudio/"webm[height=1080]"+bestaudio/"webm[height=720]"+bestaudio/"mp4[height=1080][fps=60]"+bestaudio/"mp4[height=720][fps=60]"+bestaudio/"mp4[height=1080]"+bestaudio/"mp4[height=720]"+bestaudio/best
While for all other extractors: -f bestvideo+bestaudio/best
If it is not possible, could anyone consider implementing this idea in youtube-dl?  Thank you!

Not possible. Though custom config can be specified with --config-location.


feat(): dark mode for bull board experimental

Some changes yet to be make and test if all components are in dark mode.

@felixmosh

Hi, thank you for the initiative...
Why did you changed cx lib with classnames?
I think that a better approach is using css custom props, which means you set one class which changes all colors...


Cluster Dashboard resource gauges show incorrect max values

The resource gauges (at least for CPU and Memory, don't know about Pod) in Cluster Dashboard seem to show incorrect max values.

For example, the Memory Used gauge shows 30 of 31 GiB, now the actual usage of 30 GiB seems correct but the max of 31 GiB doesn't because the cluster has a lot more resources. This particular gauge sometimes shows 103% usage so it's obviously wrong.
The CPU gauges seem wrong too since the cluster has more than 10 cores.
Cluster info:
Kubernetes 1.20.5
Rancher 2.5.7
7x CentOS 7 control plane nodes (1 is currently down) 2vCPU 8GB each
2x CentOS 7 worker nodes 2vCPU 8GB each
2x Windows Server 2019 worker nodes 2vCPU 4GB each

@gaktive , The concern is with the calculation of total memory and not the usage.
In my case, the total memory of nodes are more than 1TB, but UI shows 503GB which is not correct.

Internal reference: SURE-4027
We're getting feedback that alerts are being sent out falsely based on these high numbers, whereby 112% usage is wrong

@gaktive been taking a look at this. We don't have the charts anyone (afaik) and the resources count doesn't point to any issues, although I might not have a proper edge-case, so I can't really reproduce it.
The only strange thing that I have found is that the resources count on the side menu is affected by the namespace filter on the header. If you check the screenshots, the "cluster page" shows a total of 60 pods being used, but when you look at the side-menu workload > pods count, it shows 40... That's because the namespace filter on the top is set to "only user namespaces".
If we set no namespace filtering the numbers match.
Otherwise, from a first glance, nothing odd here. Maybe we need to monitor this to see if any issue pops up.
How shall I proceed?
Thanks

@gaktive @nwmac
Will move forward this issue to testing. Thank you

@deniseschannon @gaktive what is the goal for my testing then closing out this issue here?
We could not reproduce but identified this is working as expected? Is due to namespace filtering?
What does QA need to do? I see no PRs attached.

Possible other internal reference: SURE-4148 -- I'll check if namespace filters are being applied there.
@aalves08 I may have missed some notes here after Alex's diagnosis, but we should be clear here if this is actually expected or not based on our current inability to repro this.

Also SURE-4090 so we're getting more feedback about this discrepancy.

@aalves08 Where are we with this ticket?

Neil & several inconsistencies in the counts between the home page and the cluster dashboard for RKE1 and RK2 clusters, but in the case of displaying incorrect max values for clusters in 2.6.3, we can confirm that those values are correct.
We will open another related issue related to the discrepancies we found and link it to the SURE issues you mentioned as well.
Our recommendation is to move this to test and QA to make sure that the max values for CPU and MEM are correct in 2.6.3.
@gaktive

rancher/rancher:v2.6.4-rc10

Deployed several clusters
Deployed several fleet bundles and feature charts to use some cluster resources
The CPU / memory stats appear to be correct as far as the total use of available cores and memory for the total number of nodes in the cluster
Percentages are appearing and seem to be calculated correctly


Remove excess newlines from migration and GRPC modules

Continuation of #699
Applies the EmptyLineSeparator check to the migration and GRPC modules
No functional changes are part of this change.
One logic code change for the following:
- As the ConfigBuilder collects all forwarding keys from provided files, it will put into the final list instead of creating intermediate lists and adding them together. Result is the same in both cases.

Removed excess newlines in code
Added separation between class members for more readability (not to interfaces)

Codecov Report

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

@@             Coverage Diff              @@
##             master     #724      +/-   ##
============================================
- Coverage     99.44%   99.44%   -0.01%
  Complexity     1890     1890
============================================
  Files           285      285
  Lines          5621     5615       -6
  Branches        284      284
============================================
- Hits           5590     5584       -6
  Misses            5        5
  Partials         26       26

Impacted Files
Coverage Δ
Complexity Δ

.../java/com/quorum/tessera/client/GrpcP2pClient.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...java/com/quorum/tessera/client/GrpcClientImpl.java
100% <ø> (ø)
7 <0> (ø)
:arrow_down:

...om/quorum/tessera/client/GrpcP2pClientFactory.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

...in/java/com/quorum/tessera/grpc/p2p/Convertor.java
100% <ø> (ø)
6 <0> (ø)
:arrow_down:

...rum/tessera/config/migration/LegacyCliAdapter.java
100% <ø> (ø)
19 <0> (ø)
:arrow_down:

...um/tessera/grpc/api/APITransactionGrpcService.java
100% <ø> (ø)
8 <0> (ø)
:arrow_down:

...um/tessera/config/builder/SslTrustModeFactory.java
100% <100%> (ø)
2 <1> (ø)
:arrow_down:

...m/quorum/tessera/config/builder/ConfigBuilder.java
100% <100%> (ø)
38 <0> (ø)
:arrow_down:

...orum/tessera/config/builder/JdbcConfigFactory.java
100% <100%> (ø)
4 <4> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Add resync cache logic upon watcher reset

Fixes a race condition which in watcher is trying to re-connect and ANP is deleted by the user. In this case, when the watcher re-connect, it will not receive delete event for those objects and those objects will remain in network policy controller cache and in cloud too.
Here, we introduce a resync logic in which, upon any re-connect, the cache will be resynced first and then new cache will be compared with in-memory cache to figure out stale objects and explicitly delete them.

/nephe-test-e2e-agentless

/nephe-test-e2e-agentless

/nephe-test-e2e-aks

/nephe-test-e2e-aks

/nephe-test-e2e-aks

/nephe-test-e2e-aks


typescript definitions broken?

Version

react-native-router-flux v3.26.24
react-native v0.26.3
react v15.0.2

type definitions:

registry:dt/react#0.14.0+20160602151522

Expected behaviour
Typescript definitions should work
Actual behaviour
.. doesn't work. The type definitions tries to use properties on React that aren't defined in the react-definition as far as i can see.

Will be fixed by #831.

I had same problem.
Versions:

react-native-router-flux v3.30.0
typing: "react-native": "registry:dt/react-native#0.19.0+20160501140141"

I've fixed the problem by #831.
@AlmaasAre Could you try using it?

I'll close this issue since it should be fixed now, let me know if it's not.


Fix Typo in PluginBaseClassNotFoundException

1. Why is this change necessary?
The message is displayed to shop admins. We should have correct grammar/spelling here.
2. What does this change do, exactly?
Only fix a simple spelling mistake.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

thanks for your contribution @mkreusch 👍🎉💙


Fix title of the documentation

Currently, the generated documentation have the wrong title. Seen in:
https://firebase-messaging.readthedocs.io/en/latest/

coverage: 79.595%. remained the same
when pulling 4ad6929fc18be0570a7591a59924fb48cd3fac80 on cpina:fix-documentation-title
into ca0faead9e9ef8e3fb7253accf094a7bf200b648 on sdb9696:main.

Thanks for the pr @cpina!


[Package Request]: Visual Studio Build Tools 2017

Package Requested

[ ] I would like someone else to build the manifest.
[ ] I would like help so I can submit the manifest.
[X] I have performed a search and couldn't find this package.
[ ] I have checked that the installer for this package is not contained in a .zip file
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: Microsoft
Publisher Url:
Package Name: Visual Studio Build Tools 2017
Description: VS2017 build tools for VS2022
Package Version:
Installer URL:
Current Package Identifier (for new versions):

We don’t currently have the 2017 stuff, I can look into adding it.

VS2017 build tools for VS2022

is there a specific workload you’re looking for? If it can be installed through the VS22 installer, I can give you a command to install it with winget now.

I don't have a specific workload in mind. The package is present in several of my machines, where the VS22 installer reports an update's available... but winget can't apply it.... yet.

#90827 adds 15.8.9, but the latest version reported by the VS22 installer is 15.9.51.
Bottom line: winget upgrade --all still doesn't keep that package up-to-date.
@denelon what's the process so that the owners of "VS2017 build tools" push all their updates to the winget package store?

Oh darn, they don't post versioned links for the latest build of 2017 like they do for 2019 and 2022. They post a latest redirect link, I can use that I suppose...

@jedieaston shouldn't that issue be reopened?


[flash_ctrl] fixes for hanging transactions

fixes #13689

propagate data error through the read pipeline and store
it into the buffer if a buffer had been allocated.

any future reads that match this location will also error
until evicted.

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

i'm going to merge this one as is right now.
There will be a follow-on PR to address some of the poitns @jeoongp made and also another issue i found along the way.