How to get http chunk size?

My requests are periodically timed out, as reslt not all data was inserted into DB. Im loading in my home hardware some data, so i've got this result
Request key     Total inserted
2019-01-20	100000 -- request completed
2019-01-21	33388   -- request timeout
2019-01-22	66612   -- request timeout

Little worrying about it - how to hande portions? For example, set portion to all data, to avoid corruption.

What is the timeout error you are getting?  There are many types of timeouts when inserting data in ClickHouse
You can increase increase the send_receive_timeout paramete when calling get_client (the default is 5 minutes), but in most cases that shouldn't be necessary.

Stack trace:
  File "C:\Python312\Lib\site-packages\clickhouse_connect\driver\httpclient.py", line 434, in _raw_request
    raise OperationalError(f'Error {ex} executing HTTP request attempt {attempts}{err_url}') from ex
clickhouse_connect.driver.exceptions.OperationalError: Error ('Connection aborted.', TimeoutError('timed out')) executing HTTP request attempt 1

BTW the task is not to increase timeout, my goal - not to get corrupted data in DB.

If your inserts are just taking a long time, then you may just need a less data or a more powerful ClickHouse server (more CPU cores and memory).
I can't tell you how to break up the data you are inserting -- it depends where it is coming from.  If it's pandas you can use iloc to split it -- see https://stackoverflow.com/questions/41624241/pandas-split-dataframe-into-two-dataframes-at-a-specific-column.  If it's some other array, you can do something similar with just array slices:

chunk1 = chunk[1000:]
chunk2= chunk[:1000]

Note that splitting DataFrames or arrays like that can be slow and take a lot of memory.
In any case I'm going to close this because that's really Python programming and not related to clickhouse-connect functionality.

eh. In my situation, clickhouse-connect functionality executes my batch partially - thats the point.
In productive environment i dont want to see my requests executed by random percent. Best scenario is "whole or nothing"

Well clickhouse-connect returns an error if you time out.  It's the application's responsibility to retry after errors; normally database drivers will not automatically retry because the user needs to make that decision based on the error.  For example, if your user has been deleted or the network is down, you wouldn't want the driver to retry forever.


[FR] Add starter code to the issue template

It would be super convenient to add some starter code to the issue template (i.e. jsfiddle)
It would make it much easier to create a repro to attach with bugs

If you would like to upvote the priority of this issue, please comment below or react with :+1: so we can see what is popular when we triage.
@vicb Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.


feat: add support for median

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Closes https://github.com/narwhals-dev/narwhals/issues/1190

Checklist

[x] Code follows style guide (ruff)
[x] Tests added
[x] Documented the changes

If you have comments or can explain your changes, please do so below.
WIP: I would need to better dig into details for pyarrow and dask. Already opened the PR to (also) get advices and/or guidance:)
My understanding per now (might be missing bits, though) is the following:

neither pyarrow nor dask do implement a "proper" median; otoh, they respectively implement approximate_median and median_approximate (dask's median_approximate fails tests when npartitions=2, though)
relying on already implemented quantile(s) would come with the following issues: for pyarrow, the issue of having an interpolation parameter which would not quite fit the nw.median() signature; for dask, the issue of having to hardcode a "linear" interpolation strategy and having to xfail tests as well when encountering dask_lazy_p2_constructor.

Also, need to revise docstrings so as to comply with https://github.com/narwhals-dev/narwhals/issues/1000 for median.

Hey @AlessandroMiola thanks for the effort! This already looks very promising.

neither pyarrow nor dask do implement a "proper" median; otoh, they respectively implement approximate_median and median_approximate

I think that's good enough as long as we document that results may slightly differ between backend because of the difference of underlying algorithms used

dask's median_approximate fails tests when npartitions=2, though

This may need some investigation

Also, need to revise docstrings so as to comply with https://github.com/narwhals-dev/narwhals/issues/1000 for median.

This is much appreciated 😁
I have a couple of additional considerations:

Polars on string series returns None, pandas raises an error, I don't know about others - should we check that the input is numeric and limit the functionality to that? cc @MarcoGorelli
Can we check that all algorithms ignore nulls/nans?

Thanks for your help @FBruzzesi! :) I'll try to address all of your comments!

I find it a bit odd that Series.median doesn't raise for Polars, and think it'd be ok for us to just always raise

A (possibly silly) question on my side for clarification. Should we make it so that it passes tests like the ones below (thus raising a custom error within the underlying backends) or should we just raise where it natively does not while keeping native behaviour as is?
I would have gone the first way, but I'm all ears! :D
data = {
    "a": [3, 8, 2, None],
    "b": [5, 5, None, 7],
    "z": [7.0, 8, 9, None],
    "s": ["f", "a", "x", "x"],
}

@pytest.mark.parametrize(
    "expr", [nw.col("s").median(), nw.median("s")]
)
def test_median_expr_raises_on_str(constructor: Constructor, expr: nw.Expr) -> None:
    df = nw.from_native(constructor(data))
    with pytest.raises(
        TypeError,
        match="`median` operation not supported for non-numeric input type."
    ):
        df.select(expr)

@pytest.mark.parametrize(("col"), [("s")])
def test_median_series_raises_on_str(
    constructor_eager: Any,
    col: str,
) -> None:
    series = nw.from_native(constructor_eager(data), eager_only=True)[col]
    with pytest.raises(
        TypeError,
        match="`median` operation not supported for non-numeric input type."
    ):
        series.median()

Please correct me if I'm completely off-road! Thanks

A (possibly silly) question on my side for clarification. Should we make it so that it passes tests like the ones below (thus raising a custom error within the underlying backends) or should we just raise where it natively does not while keeping native behaviour as is? I would have gone the first way, but I'm all ears! :D

Hey @AlessandroMiola , I would personally opt for the second option: you could create a InvalidOperationError class  in _exceptions.py and raise that one. For series it would be even possible to do so in narwhals.Series so that the type checking and raise does not get duplicated. For narwhals.Expr I would not know how to do it directly though, since datatype is not know until computation in polars.
So maybe first option 😂

Hey @AlessandroMiola , I think this is fairly ready for review, however in #1224 , compare_dicts was renamed to assert_equal_data and that's where the error in CI comes from.

Hey @AlessandroMiola , I think this is fairly ready for review, however in #1224 , compare_dicts was renamed to assert_equal_data and that's where the error in CI comes from.

Hi @FBruzzesi, thanks for having a look. Besides what you mention, I still have uncommitted changes related to:

Can we check that all algorithms ignore nulls/nans?

This is indeed pretty straightforward (as all backends seem to natively do it) and potentially ready for being committed and pushed.

I think that's good enough as long as we document that results may slightly differ between backends because of the difference of underlying algorithms used

As above.

A (possibly silly) question on my side for clarification. Should we make it so that it passes tests like the ones below (thus raising a custom error within the underlying backends) or should we just raise where it natively does not while keeping native behaviour as is? I would have gone the first way, but I'm all ears! :D
Hey @AlessandroMiola , I would personally opt for the second option: you could create a InvalidOperationError class in _exceptions.py and raise that one. For series it would be even possible to do so in narwhals.Series so that the type checking and raise does not get duplicated. For narwhals.Expr I would not know how to do it directly though, since datatype is not know until computation in polars.

Here, I see your point and I indeed had some issues in figuring out how to deal with Expr at the "narwhals-level" (if even possible), but I would need to revise everything

dask's median_approximate fails tests when npartitions=2, though

This may need some investigation

On this, I haven't started yet :|
Later today and tomorrow I should have time, so I'll hopefully update you and/or push something.

Hey @AlessandroMiola I have one more request 🙈 As median returns a scalar, could you add a test verifying that it works in a group_by context? I would expect that a remapping is required at least in the pyarrow case (median to hash_approximate_median)


Angular in Markdown

Which scope/s are relevant/related to the feature request?
content
Information
I've been using ng-doc lately as a Storybook alternative for my component library.  They have a nifty feature that allows you to use Angular components in markdown.  This brings me closer to the ideal React + MDX authoring experience that I want for my documentation site, but there are still some limitations (namely, speed).
I'd like to be able to render Angular components from Markdown.  Is this a possibility today?  If not, is it something that can be done in the future?
Describe any alternatives/workarounds you're currently using
None
I would be willing to submit a PR to fix this issue

[ ] Yes
[X] No

I do think being able to author docs with an MDX type workflow would be pretty cool.
You can do pretty close to this already with Astro and the Analog integration for Angular components.
Were you thinking about something different than this?

I was hoping to stay within the Analog ecosystem and avoid using Astro altogether.

Will be revisiting this soon with some discussion with @nartc

Curious about the status of this! Would love to move the spartan docs to an Mdx approach 😍

I might not have the technical chops to actually pull this off but if you can point me in a direction I'm keen to sink some time into figuring out how to get this done (or at least get some kind of prototype going) @brandonroberts

@joshuamorony Awesome. @nartc can add some perspective here too, but I would love to see Angular components able to be used within MDX files. That involves making a compatibility layer with the JSX runtime, and creating Angular components dynamically.
I have a prototype of this on a branch but it needs more work.
I think previous attempts have used a combination of markdown and Angular elements, but I wouldn't lean towards that solution again.
Interested to hear your thoughts

@joshuamorony Sure, its worth a shot. Definitely on board with the .ngx format. I think the last step in the proposal with rendering a compiled Angular component will be a challenge, but challenges are good 🙂.

Alright I'll get on it and see what happens 🤞

@brandonroberts I've been messing around with this and have an extremely early/unfinished prototype - I have actually managed to get an Angular component rendering in the markdown, but before I go further I wanted to check in to see if:

This idea will work with the overall AnalogJS approach/philosophy
The idea isn't completely ridiculous - this is definitely out of my comfort zone so I really don't have a good sense of whether this is sensible or not

The basic idea is this. I've been able to add a <script> section to the markdown files, e.g:
---
title: My Third Post
slug: my-third-post
description: My Third Post Description
coverImage: https://images.unsplash.com/photo-1481627834876-b7833e8f5570?ixlib=rb-4.0.3&ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&auto=format&fit=crop&w=928&q=80
---

<script>
import { TestComponent } from '../app/components/test.component'
</script>

### Section 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna

I then wrote a Vite plugin that transforms the code and returns it in this format:
          const outputCode = `
            export const markdown = \`${escapedContent}\`;
            export const componentMap = ${JSON.stringify(componentMap)};
          `;

Rather than returning the raw markdown, it returns a module containing both the markdown and a componentMap - this is generated from the <script> tag and maps the names of the components being used to their paths.
Within the generateBundle for the plugin I then create a file that exports every component that is being used in any of the markdown files (this of course assumes only standalone components are used). This file also export a map to map the string name of the component to the actual component:
        generateBundle() {
          const componentFile = `
          ${Object.entries(ngxComponentData)
            .map(([name, path]) => `import { ${name} } from '${path}';`)
            .join('\n')}

          export const MarkdownComponents = [${Object.keys(
            ngxComponentData
          ).join(', ')}]

          export const markdownComponentMap: Record<string, any> = {
            ${Object.keys(ngxComponentData)
              .map((name) => `'${name}': ${name},`)
              .join('\n')}
            }
        `;

          const filePath = path.resolve(__dirname, 'src/app/components.ts');
          fs.writeFileSync(filePath, componentFile);
        },

This results in a file that looks like this:
import { TestComponent } from '../app/components/test.component';

export const MarkdownComponents = [TestComponent];

export const markdownComponentMap: Record<string, any> = {
  TestComponent: TestComponent,
};

The rest of this process is perhaps even more hacky/less thought out, but for now just to see if I could actually get something rendering I added the MarkdownComponents from this file to the imports of the [slug].page.ts component. I'm also passing in the map of all components, and the specific components used in this blog post to the analog-markdown component:
      <analog-markdown
        [content]="post.content"
        [componentMap]="post.componentMap"
        [components]="markdownComponentMap"
      ></analog-markdown>

Where I then render each of the supplied components:
      for (const componentName of Object.keys(this.componentMap)) {
        const componentToRender = this.components[componentName];

        const componentRef =
          this.viewContainer.createComponent(componentToRender);
        this.viewContainer.insert(componentRef.hostView);
      }

For now this just renders them after the content - I will still need to get them rendering in the correct place.
This is all very rough and hacky obviously and a lot more thought would need to go into it, but I mostly just want a sanity check right now to see if this path is worth pursuing further or not.

@joshuamorony I think this approach is similar to one I tried also, and might work. I do have a few questions on pursuing it further, mostly because of the way Angular works today.

The file generated through the generateBundle happens during the build, right? We would have to have the file generated earlier so that file/import would be available during development also.
How viable is it to target the components in the markdown without selectors? And how do those selectors get mapped in this setup?

I think it ultimately depends on if we want the markdown authoring to be the sole source of the document and we use some sort of transform to turn that into a component that can be compiled. I have a couple of ideas, but need to dig into them more.

@brandonroberts

Yes - right now I am just creating that file manually to begin with but I suppose we have a few options here e.g a) it's something manually created when integrating this feature b) this file is just something that lives in all Analog projects c) maybe we use a schematic when integrating this functionality. Not sure what the best approach would be, and I suppose it will depend on how tightly integrated this feature is. At the moment I've actually just gone with .md files (rather than having separate ngx files) and it's all just part of the normal markdown handling - perhaps this is just something Analog could support out of the box with .md files, because it doesn't effect the normal parsing of markdown if components aren't being used (at least not at the moment)

This is another thing I need to put more thought into but what I have been planning on so far is using the "forbidden" syntax, e.g:

---
title: My Third Post
slug: my-third-post
description: My Third Post Description
coverImage: https://images.unsplash.com/photo-1481627834876-b7833e8f5570?ixlib=rb-4.0.3&ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&auto=format&fit=crop&w=928&q=80
---

<script>
import { TestComponent } from '../app/components/test.component'
</script>

### Section 1

<TestComponent />

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna

This removes any need to deal with selectors - I already have the name/path parsed in the script section, then when figuring out where to inject the components within the markdown content I can (theoretically) just use the component map to match up the name to where it needs to be added (i.e. I could just do a regex match for <TestComponent /> and then use that TestComponent name which is in the component map to create/add the component in the correct place.
I haven't actually given thought to how I would handle selectors if we want to go that way, but this seems harder since there is no direct link between the name from the import and the selector used in the markdown.

Given the work we've done with .analog files, this is now possible https://github.com/analogjs/analog/pull/879


Fix broken links in README

Wrong links to some Arduino examples (Missing underscores). Links now corrected

Thanks, fixed!


Corrected grammar

Ideally these reasons would be given in a bulleted list, as including them sequentially in a paragraph decreases readability.

#sign-off


Facet Filtering for DOCSEARCH

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I am mindful of the project scope

Proposal
Extend the configuration parameters of docsearch to support facets.
Motivation and context
Docsearch has something called 'facets' where you can restrict the results based on record attributes in the indexed results.
E.g. if the crawler extracts version information from your pages you can restrict search results to latest.  See
https://docsearch.algolia.com/docs/docsearch-v3/#filtering-your-search
In my case, the web page hosts the documentation for 5+ versions. So, searching for something brings often 5+ hits, all pointing to the same topic, in different versions.
If the feature will be accepted, I am happy to provide a PR.

If the code is just a very simple change and is coded in such a way that it works on both simple sites (the existing implementation) and multi-version sites (as in your use case), then sure a PR for such a feature is likely to be within scope and get merged.


Support for versions of Python

This issue is to track the discussion of how quickly we should drop support for Python 3.5 in order to use the nice features of 3.6, and more broadly how quickly we intend to drop support for old versions of 3.x as new ones are released. @hhslepicka brought this up over Hangouts, and I will here recap our conversation.
Reminder of current situation: The data acquisition stack (ophyd, bluesky, their dependencies) support Python 3.5+. The data retrieval stack (databroker and its dependencies) supports Python 2.7 and Python 3.4+.
We all seem to have consensus that databroker should continue to support Python 2.7 at least until 2020 when Python 2.7 stops getting security updates. Databroker should do this in order to interface with legacy analysis software that is not actively supported anymore.
But it's an open question how rapidly bluesky/ophyd should drop support for 3.5 in order to use nice features of 3.6 (and so, into the future). Of course, "migrating" from 3.5 to 3.6 is not at all the same as migrating from 2.7 to 3.x because API breakages between 3.x versions are rare and slow. In practice, forcing users to upgrade from 3.5 to 3.6 is only a burden on packaging; it does not require changes to user code. Nonetheless, as @hhslepicka correctly flagged, the impression that we are rapidly dropping support for old releases of Python 3.x might leave users wary. How should we balance these concerns?
Python 3.5 brought us async/await syntax, which is why we dropped 3.4. Python 3.6 has been touted as an especially big step forward for the language in general. (Both Fernando and Raymond have said something along the lines of, "It's the first Python 3 release that justifies the pain.") I would advocate for:

guiding our collaborators to target 3.6 for their deployments
supporting 3.5 for the next release or two
dropping 3.5 support by bluesky 1.0
sustaining long-term support for Python 3.6 through the bluesky 1.x release cycle

I agree with @hhslepicka we do need to be mindful of having a constant (and never ending) version churn.  We already have the reputation for constant changes, we don't want to add to the perception. 😄
Also, I would say a 👍 to maintaining Python 2.7 support for databroker, the more APIs that we have for different languages and versions will only enable more folks to use it! 🥇

Use of milestones, spaced at regular or irregular intervals, can help
On Jul 22, 2017 11:27 AM, "Stuart Campbell"<EMAIL_ADDRESS>wrote:

I agree with @hhslepicka https://github.com/hhslepicka we do need to be
mindful of having a constant (and never ending) version churn. We already
have the reputation for constant changes, we don't want to add to the
perception. 😄
Also, I would say a 👍 to maintaining Python 2.7 support for databroker,
the more APIs that we have for different languages and versions will only
enable more folks to use it! 🥇
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NSLS-II/bluesky/issues/699#issuecomment-317194359,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLKMJhWCPOviQRithRKAui-IQRPIKIUks5sQiLvgaJpZM4OgKFa
.

:+1: to @danielballan 's timeline (modulo not many more releases before 1.0).
Long term, I think we should strive for "last 2 minor releases of python" which gives each version of python about a 2 year window and only drop support for a version of python in a minor or major release (depending on how long we plan to support at the patch level which I would argue should be only until the next minor given the size, speed of development, and current installed base of the software).
also :+1: to maintaining 2.7 support for the data retrieval side for at least another 2 years.

Update on our roadmap and plan for support of Python versions:
Bluesky 1.0 and ophyd 1.0 will be tagged by November 1. We're thinking that bluesky 1.0 and ophyd 1.0 will support Python 3.5 and Python 3.6, but that future releases in 1.x may drop Python 3.5 support. Python 3.6 will have long-term support in future 1.x releases. Do you think that will be satisfactory, @hhslepicka? This is still very much negotiable. Python 3.6 has some great new features that we'd like to use, but we don't want to alienate our new collaborators!
Databroker 1.0 will not be tagged this year, as it is still in a less mature stage of development. To reiterate the consensus above, the data retrieval software including databroker and its dependencies will support Python 2.7 (as well as 3.x, of course) until at least 2020.
Once 1.0 is tagged, we will write a clear roadmap into our documentation.

Ok with py3.6 only for bluesky and ophyd [we will upgrade to 3.6 this week here at APS]
Agree with "& py2.7" for databroker as most of our users are using that now

Don't think it will be an issue here at SLAC

Ok with 3.5 & 3.6 for 1.0 & 3.6 only after that and also agree for py2.7 for data broker. Looks pretty good to me. Thank you @danielballan

We never got arround to dropping support for python 3.5 and are currently having issues getting the tests to pass on py3.7 (due to odd zmq issue see #1063 ).  Punting to next release.

I think you did drop support for python 3.5. The script for the zmq proxy has f-strings.

If you have not yet dropped suport for Py3.5, please consider keeping Py3.5 support since anaconda has no support for 3.6+ on the raspberry pi.  Lowly as it is, it's a great demo box (and can even run EPICS 7 and synApps 6).  The native Raspbian OS provides Py3.4.

Recall that ophyd lost its 3.5 support in https://github.com/NSLS-II/ophyd/pull/642 with signoff from all facilities involved.
@prjemian Have you come across https://github.com/jjhelmus/berryconda? The creator is a former Argonne employee, now full-time Anaconda maintainer, and a friend of ours. I think it's a bit of a hobby project, but it looks like it's still being actively maintained.
(For what it's worth, I personally just build Python 3.6, but it takes about an hour on an RPi Zero, and I haven't attempt the heavy numerical libraries yet. At that point I'm sure berryconda would be well worth it.)

As a sidenote conda-forge is actively pursuing arm builds https://github.com/conda-forge/conda-forge.github.io/issues/269 you might consider weighing in on that issue if that could help you.

I own part of that signoff, for sure.  These links are news for me.  Don't recognize that former Argonnenaut.

This chart shows major activity on this project just this past fall.

Numpy now provides guidance for scientific Python projects on this: https://numpy.org/neps/nep-0029-deprecation_policy.html.


Problem with flexslider

it is problem, flexslider not work correctly

I may assume that you're aware of the fact that these kind of bug reports don't really help me? :wink:
Can you describe what is (not) happening, what you expect to happen and how your code looks like.


Add benchmark for AMD Ryzen 4750u

The laptop is a Lenovo L14 (AMD version), with 8gb of memory running Fedora 36 (Gnome)


Use cmake_dependent_option with BLT options

Hey @gzagaris I'm going to merge from here just to make sure our internal CI is passing (I think Rich did the same thing with the RAJA PR)

LGTM

Yup. That's why I made the script to pull in branches from forked repos to make PRs that would run all the CI tools.

Awesome -- thanks @davidbeckingsale!


X close

I am trying to show the Close X at the top but for some reason It's not showing, I'm not sure what I am doing wrong, your help would be appreciated.
I am using inline content, click on the staff picture for the zoom to show
http://www.cyberjunkiesinteractive.com/ocdc/about-us/staff/
Your help would be appreciated.
Also for the videos on my homepage:
http://www.cyberjunkiesinteractive.com/ocdc/ scroll down to Investing where it matthers most, click on the banner the video will show, is there another unique CSS to use so the video is center and not full width since it uses the css from staff?
Thanks

Please read the documentation (http://dimsemenov.com/plugins/magnific-popup/documentation.html). You have incorrect code for the close button in your jQuery. Also, please use StackOverflow http://stackoverflow.com/questions/tagged/magnific-popup for support.
<button title="%title%" class="mfp-close"><i class="mfp-close-icn">×</i></button>

Thanks.

You're welcome. Please close this issue, since it's not an issue. Thank you.

@carasmo, thank you for help :)


Pipe to stdout

Summary
Pipe stuff to stdout of processSsingle
Motivation
Allow users to do cooler stuff

Hey 👋 Messer 0.5.2 has just been published with a bunch of bug fixes - install it and give it a whirl 🤘. If you’re still experiencing this issue, please comment below with your symptoms and we'll keep the ticket open. Thanks for supporting Messer 💬


modbus rs485/can to mqtt software on T-CAN485

Hi there,
I purchased the t-can485 board for the following project:
I'm trying to achieve rs485/canbus to mqtt converter over wifi ( and optional if there is the possibility to add rj45 wired lan extension to it)
Anybody can help me with this software ? Should be similar to Friendtrol's GW-1205B interface.
Read/write a few registers over mqtt protocol. Config the initial wifi credentials in AP mode.
Im interested in buying at least 200 boards like this if the software works.
I can also support this software development if necessary.
Many thanks,
Adrian

That does not sound to difficult 🤔 .. Fork and drop me an invite.
On Sat, Feb 5, 2022, 1:24 AM xjustbmw @.***> wrote:

Hi there,
I purchased the t-can485 board for the following project:
I'm trying to achieve rs485/canbus to mqtt converter over wifi ( and
optional if there is the possibility to add rj45 wired lan extension to it)
Anybody can help me with this software ? Should be similar to Friendtrol's
GW-1205B interface.
Read/write a few registers over mqtt protocol. Config the initial wifi
credentials in AP mode.
Im interested in buying at least 200 boards like this if the software
works.
I can also support this software development if necessary.
Many thanks,
Adrian
—
Reply to this email directly, view it on GitHub
https://github.com/Xinyuan-LilyGO/T-CAN485/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFIBXKERTZBGDJX5NBIGT3UZTUEXANCNFSM5NTWTTJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

As this does not seem to be an issue with the board. Would you mind closing this and opening it up in a fork?


Changing colours has no effect on b450 tomahawk max

Hi there,
Just typing this up as your app is awesome!
Minus one flaw, I can't get the solid colour or any to change anymore. All scripts work and the disable LED works as well but I believe after the first time I played with changing the LED colour, it is stuck on blue.

I've tried to set it as that to get that colour set as solid on the mobo but it wont change. I can run Hue wheel and it runs fine with changing colours just cant change the one colour.
In addition, the hue wheel never really allowed me to set those colours. It just goes all rgb.

Does this continue after restarting the computer? Can you shut down your computer, turn the power supply off, press the power button for about 10 seconds, and then turn everything back on? It should reset the chip. I'm not sure what the problem is since the script uses the same mechanism to change colours as the GUI, but maybe it will work.

Hey thanks for the quick response, I tried that as you said and it did indeed reset it but its made no real difference. I tried this:

It just gives me a solid white/bluish light now :/
If I play around with the hue wheel a lot:
Let it change colours for about 5 secs then stop it and pray I get the colour I want and it'll give me a different solid colour when I remove hue wheel. Not sure whats happening lol

But the scripts apply the correct colors?

i can confirm that . it not work well on B450 tomahawk max
the scripts not work too
the only thing work is DISABLE ALL LIGHTING
after i delete all file . it does not give me red light back too

But the scripts apply the correct colors?

The hue wheel script only cycles rgb. Selection of colours has no effect on it so I guess not?
Strobe and police lights do work. The pumpkin one I am using at the moment; with lots of fiddling.
I have to use hue wheel to cycle colours, after this, pressing apply stops it on a random colour. I use this with pumpkin to sort of set my systems and wallpapers rgb.
As the other user mentioned, the disable all lighting does work.

This is weird as other users have reported that it works with this motherboard. I'll look into it ASAP.

This is weird as other users have reported that it works with this motherboard. I'll look into it ASAP.

Thanks, look forward to the fix as this is a fantastic piece of software, just wish it would work with my mobo lol. Puts MSI to shame with the rubbish they have released to control the rgb. All I want to do is to be able to pick my colours even if they are solid lol.
Cheers mate

Did you fix this? Try the new version (v2.3.0) of MSIRGB.

Did you fix this? Try the new version (v2.3.0) of MSIRGB.

Have just tried the new version. Works perfectly!!!!
Brilliant work man, MSI needs to take note 👍

Great! Thanks for the feedback.


feat(un-es6-class): support extending super class

This PR only handles extending class (class C extends B {}) but doesn't handle super() call. super() call should be solved in separated PR.

At first, I thought this should be implemented in another way. Finding helper functions like _createClass  and _defineProperty is unreliable because minifier will destroy them. Instead, we can do this in the runtime helper transform (code). But these helper functions are too special to be implemented in that way.
This PR can be merged, and we can have another one that adds these helpers into the module scanning, and use the minified name from module scanning.

I see. We can wait for implementing helper functions detecting before merging this PR.

Helper functions like __extends or _inherits are generated as inline, not imported as modules:

Babel
SWC
TypeScript

How can we detect them?

Helper functions like __extends or _inherits are generated as inline, not imported as modules:
How can we detect them?

@g-plane While I don't know the specific answer to that off the top of my head, here are the relevant issues/references related to it:

Babel:

https://github.com/pionxzh/wakaru/blob/main/packages/unminify/src/transformations/runtime-helpers/index.ts#L11-L20
https://github.com/pionxzh/wakaru/tree/main/packages/unminify/src/transformations/runtime-helpers/babel

swc: #50
TypeScript: #55

Also:

https://github.com/pionxzh/wakaru/tree/main/packages/unminify#wakaruunminify

It covered most of patterns that are used by the following tools:

Terser (Check the Terser Progress)
Babel (Check the Babel Progress)
SWC (Check the SWC Progress)
TypeScript

https://github.com/pionxzh/wakaru/tree/main/packages/unminify/src/transformations/runtime-helpers

Helper functions like __extends or _inherits are generated as inline, not imported as modules:

Babel
SWC
TypeScript

How can we detect them?

I haven't had time to check on how they generate these helpers, but based on what I know, helpers can be inlined or extracted. Currently, the module scanning is based on regex matching (see babel reference).
And these examples have been updated to external-helper mode.

Babel
SWC

Detecting Babel runtime helpers is added.

Seems like these helpers can also be imported from the runtime helpers.
import _classCallCheck from "@babel/runtime/helpers/classCallCheck";
import _createClass from "@babel/runtime/helpers/createClass";
import _inherits from "@babel/runtime/helpers/inherits";
import _createSuper from "@babel/runtime/helpers/createSuper";

Oh, super will be handled in another PR, so it doesn't matter. OK OK


[modify] bunmp up rails to <IP_ADDRESS>

Coverage decreased (-20.9%) to 55.666% when pulling fffa3a28a8c9959a0f4966d3444bbb6632268739 on feature/rails into f6b9f8ff14904b21d593b9301ca7020e56f09afc on master.

Coverage decreased (-20.9%) to 55.666% when pulling fffa3a28a8c9959a0f4966d3444bbb6632268739 on feature/rails into f6b9f8ff14904b21d593b9301ca7020e56f09afc on master.


Get latest followers/notifications?

How can I get latest (new) followers?
This followers is displaying at "notifications" (likes) tab in app.

The answer is 'getRecentActivityInbox' thank you! <3


Adding TDOA (time difference of arrival) feature for direction finding

The Arduino library currently supports the ToA (time of arrival) feature of the DW1000 modules for two-way-ranging.
In addition to that it would be very useful to also use the TDOA (time difference of arrival) feature of the DW1000 modules for direction finding, e.g. if we could connect 3x DW1000 modules and get the time difference of the received signal between them. This would allow us to do direction finding (knowing the angle of the sender). Thereby, in addition to distance we would also get an angle, thus reducing the number of senders for position estimation (localization). In other words, we would not need 3 senders (3 distances), just 1 (1 distance, 1 angle) and that greatly reduces the required infrastructure for position estimation (localization) in a difficult outdoor environment like a robotic lawn mower.
Combining both methods (ToA and optionally TDOA) would be very intesting.
What do you think?

Looks similar to: https://github.com/lab11/polypoint

They both don't work as well as we expect, because of the short distances between each two antennas, we tested. The errors seem to be caused by the inner circuit of the IC or the signal detection algorithm rather than the environment surroundings or the clocks. We connected two DW1000 ICs to the same external reference clock, and  the standard variation of the time difference of arrival between them was about twice larger than that of the time of flight calculated by TWR, mathematically it implied that the errors of estimated timestamps of arrival of the same signal between two different sensors are independent.

Please move the information about TDoA to the wiki. Thanks.
duplicates #47 #77 #108 #128 #130 #152


update to docs reqs

Should fix dependency issues caused by this PR: https://github.com/fsspec/kerchunk/pull/258

Ah yup, the theme would change the look of the docs a bit. It is the pangeo-sphinx-book-theme, which pangeo-forge and a few other project use (https://github.com/pangeo-forge/pangeo-sphinx-book-theme).
Happy to pull it out into a separate PR and move the chat there if that is helpful.

This being an fsspec library, I would prefer to maintain the same look as the other fsspec libraries, RTD basic.

Sounds good, I'll revert it.

This PR actually broke the CI build...

This PR actually broke the CI build...

as you're probably aware, https://github.com/fsspec/kerchunk/pull/271 fixed the CI issue caused by the sphinx html_theme setting.
@norlandrhagen, https://github.com/fsspec/kerchunk/blob/main/ci/docs.yml will also need changes. Apologies for not bringing this up before #258 was merged, but my opinion is that it would actually be better to remove that file entirely because it is redundant with https://github.com/fsspec/kerchunk/blob/main/docs/requirements.txt, which is required for the GitHub action that's used to build the kerchunk docs. If you submit a PR to remove that file, you could also update the instructions in the contributing guide to use the docs/requirements.txt file:
conda create --name kerchunk-docs python=3.8
conda activate kerchunk-docs
python -m pip install -r docs/requirements.txt


Parse rust tests line number correctly

Rust classes contain colons, so the last colon is not necessarily the
second colon (as the current code expects).
This results in annotations like:
...
  annotations: [
    {
      path: 'project::admission_webhook_tests',
      start_line: NaN,
      end_line: NaN,
      start_column: 0,
      end_column: 0,
      annotation_level: 'failure',
      title: 'project::admission_webhook_tests.it_should_be_possible_to_update_projects',
      message: 'failed project::admission_webhook_tests::it_should_be_possible_to_update_projects',
      ...
    },
 ...

problem being the NaN entries, which are not accepted by github

closing this ... found a bug, will re-open later


gitreceived: Cache repos in blobstore.

Allows us to consistently cache repos across different gitreceived instances.
Signed-off-by: Blaž Hrastnik<EMAIL_ADDRESS>

Would testing a git repository with two pushes and detecting the second one reports
Counting objects: 1, done.
Writing objects: 100% (1/1), \n+ bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)

be sufficient?

Yeah, that sounds like a reasonable testing strategy.

@titanous All comments addressed.

@titanous Tests fixed.

@titanous Addressed yet again. Created a pkg/archiver with Tar(path, writer)/Untar(path, reader)

@titanous Addressed yet again.

LGTM pending CI


Provide better error messages from voluntary-exit command

fixes #5052
Documentation

[X] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[X] I thought about adding a changelog entry, and added one if I deemed necessary.

The acceptance test failure looks like we're now getting better messages and the AT expectation just needs to be updated which is great.


Consider banning underscore from username

Remotely related to #49 (what username to prohibit, e.g., root), we should consider banning underscore from the usernames. Assuming the current problem naming convention ({{problem-name}}_{{instance numeric}}), this will guarantee that no one can register a username that collides with problem usernames.

Only alphanumerics allowed :)
https://github.com/picoCTF/picoCTF/blob/bafd28cce2241e978e3c1ad32e2ca7eb57a2b66d/picoCTF-web/api/user.py#L22

Ah, perfect! (Sorry for my confusion! :>)


Experiment analysis after rewriting (but not running) MLF

For execution-depth=0,
Reports with no states

Commit
Now fixed?

98dc9eef38a8a3353d110786ffed93ec83d1cc02
YES. Changed 1.3 to 1.6.

9f598c25fbf4391891141d21b3005635eb35857f
NO. Patch introduces compilation error.

38b1c6e5763b55870959e6d75a6e5b46cacd382e
NO. Right states are not there because we do not record throw.

30896a1448dbdb0482f4f469b943ffe6e162608b
NO. Patch introduces compilation error. Missing return statement.

fcadcfa2001ad4a86718e6a98856b332d37a4825
NO. Multiple Hunks are not supported.

5f57bcfae6e6bebc98de9d9b49d01e6240b63554
NO. Patch introduces compilation error.

92430cd021f1afc55f40d99090893eddd620ed9b
NO. Patch introduces compilation error.

6ae26132188f016d96b87875f419738e597c22ed
NO. Left states are not there because method is not called.

30709758f0b33338fa697b400112fac836e4cef1
NO. Left states are not there because method is not called. (Same as above)

36ceb2ae32c903057a1f574e1e8963c3f26a5a2f
NO. Left states are not there because method is not called. (Same as above)

1482e9e4fba71651f86299f5abd0688af176e3db
NO. Patch introduces compilation error.

af6373a9778a4579626928b9eee8a8719398a7e7
NO. Left states are not there because method is not called.

3177794e4cd6e9d09813d5e0c750c0cac5bc3da7
NO. Left states are not there because method is not called.

Empty reports

Commit
Now fixed?

37757413c6d69946ea68c27c12ac0f7fd38b535c
NO. Timeout (10000s) reached.

6043bd63b93ee4565b6ef3efe0179fbb2351b9c3
NO. Multiple Hunks are not supported.

137c2eaf54c3c4eb5a428b6c55be1d86d33c5e4e
NO. Timeout (10000s) reached.

acf61536ac09406e477a5e900c5f0b0c9691fdf7
NO. Timeout (10000s) reached.

9a573745a43b4ea1d5ce939d67179ef13da88a4d
NO. Timeout (10000s) reached.

0077dfd7c6af8559c220c97ef5f073ed8b49af47
NO. Timeout (10000s) reached.

5f99f45853b5c98bff5dbcbfeac837aa2c686d8c
NO. Timeout (10000s) reached.

f4c53b9b7cff5492eb5b58799694a54cf828f6f9
NO. Timeout (10000s) reached.

737913664e57dad4768ff538a81ace8e0f0db559
YES. (Bug in matching using AST diff)

d5f817b6b3e6f63e542787f741b4ec8cb62a7662
NO. Multiple Hunks are not supported.

047ef2fcc23f713dc2e682d8b4f2ca5f994bb7ca
NO. Timeout (10000s) reached.

e707bbcc114bb0afa096454f9a57ff08323a5de8
NO. Timeout (10000s) reached.

6bf70cd6214303b773d2091b60e93ed0a52caea1
YES.  (Bug in matching using AST diff)

21dba3d0e53f1b2d8452aca3f760d418ff470cdc
YES. (Bug in matching using AST diff)

a8ad6b9853609e86cbf9534fff05377dfdf7790a
NO. Timeout (10000s) reached.

6e9e91677774089db6e6b9de2945716269216327
NO. Timeout (10000s) reached.

fbf87fd5c93e46b28c3987e16b05f1d1da0b021d
NO. Multiple Hunks are not supported. (Other is import statement)

3ae853a6464baa3dd498a43e2af9638f8ba09d86
YES. (Bug in matching using AST diff)

0a8a5d1d5fc3a6d0681e7344ddd773acdea27dda
YES. (Bug in matching using AST diff)

cc196972d29c2bf393ef85b23518c86a87708716
NO. Timeout (10000s) reached.

5db7253811426931ad8b303027542106bbe756e5
NO. Timeout (10000s) reached.

5b45b78464d5888ba60a3325f5ccc12876582cca
YES. (Bug in matching using AST diff)

There are two more commits for which report is not generated, but the project which they belong to is not a maven project.

af19a3800c20db42db18bc3ac51ce90236ca9517
885bbd7d0f6db843627986bf97d3f0db4cfddb02

Good commits: 565
Total commits: 602
Good commits + 13 + 22 + 2 = 602

@khaes-kth I have 35 commits to analyze. Their reason for failure is documented in #83. But now, I will post if they can be fixed with a newer version of MatchedLineFinder.

Thank you Aman!
Are the commits with the unkonwn problem also included here? I mean the bug where for some lines we couldn't add a breakpoint.

For patches where we could not add a breakpoint, we did not get any states or the file sahab-left/right was not created. All of those cases are analysed in the issue above.

See 6bf70cd6214303b773d2091b60e93ed0a52caea1, we could not find breakpoints initially for this patch. However, it is fixed after we rewrote the MLF.

Awesome.
We'll discuss it tomorrow. I just want to make sure I am understanding the change and its effects correctly.

@khaes-kth The flaky behaviour is not fixed. See the build failure here. This bug emanates from a bug in JDI, not collector-sahab.
You could send me a list of patches you think fail because of the same reason and I will try to find a trend among those patches. For example, if all of them have an offset of 2, we could add a workaround in our tool to handle it.

@algomaster99 I get an empty list of breakpoints and returns for the following commit id:
20e5b8c28c217749dbba407416cae169df3c3
Can you have a look?

Reasons why we fail, after second run:
https://github.com/khaes-kth/PatchExplainer/issues/4#issuecomment-1204343078


Kafka streams binder issues in custom environment

When kafka streams binder is used in the context of a custom environment, possibly
for a multi binder use case, it is unable to query the outer context as the normal
parent context is absent. This change will ensure that the binder context has access
to the outer context so that it can use any beans it needs from it in KStream or KTable
binder configuration.
Resolves #411

Merged this PR upstream.


[BUG] bad upgrade option on the Edit Cluster page for the "local" cluster

Rancher Server Setup

Rancher version: v2.7.5
Installation option: helm chart, RKE2 v1.26.6

Describe the bug
I had updated Rancher from v2.7.1 to v2.7.5. Next I upgraded the "local" cluster from RKE2 1.24.10 to 1.26.6. Everything seems to work fine, except that Cluster Management --> "local" burger menu --> Edit Config still shows Kubernetes version 1.24.10 as the installed version, and allows me to upgrade to 1.26.6, as it seems. I didn't dare to try, since this is obviously buggy. On other locations (e.g. the top level Cluster Management page) version information about the local cluster seems to be correct.
Screenshots

Additional context
Maybe I misunderstood the phrase "government cluster options". Sorry, but English is not my native language. Please elaborate, if I was wrong.

Does it refresh when you do a hard refresh in the browser?
Could you check with "edit as yaml" if the version showing is really the old one?
Did you upgrade with this option from 1.24 to 1.26 or did you upgrade via another way?
P.S. it is not supported to go direct from 1.24 to 1.26 - you have to go 1.24 -> 1.25 -> 1.26 - see also https://kubernetes.io/releases/version-skew-policy/ (even though this issue might not be related to this)

Ctrl-shift-reload doesn't help. I get the same bad version in other browsers as well.
 Except for Rancher's bad version string the local cluster seems to work fine, AFAICT.


[SPARK-22249][SQL] isin with empty list throws exception on cached DataFrame

What changes were proposed in this pull request?
As pointed out in the JIRA, there is a bug which causes an exception to be thrown if isin is called with an empty list on a cached DataFrame. The PR fixes it.
How was this patch tested?
Added UT.

Can one of the admins verify this patch?

@srowen do you mean replacing contains with exists? If so, might you please explain me why exists is a better option? Thanks.

@srowen I also updated the UT to check all the possible cases.

ok to test

Test build #82780 has started for PR 19494 at commit f5bc105.

Test build #82780 has finished for PR 19494 at commit f5bc105.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82780/
Test FAILed.

retest this please

Test build #82789 has started for PR 19494 at commit f5bc105.

Test build #82789 has finished for PR 19494 at commit f5bc105.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82789/
Test PASSed.

Merged to master/2.2

Sorry for my late review. @mgaido91 Could you submit a follow-up PR to address my comments. Thanks!

I will not revert this PR but please submit the fix ASAP.

I will, thanks for your suggestions @gatorsmile.

I created the followup PR: https://github.com/apache/spark/pull/19522. Thanks.


Missing /dev/shm on base image

I'm encountering errors when starting up celery worker processed on flynn. It seems that celery's default worker pool makes use of shared memory, which I imagine Python expects to find in /dev/shm.
While a number of fixes seem to exist, namely:
sudo ln -s /run/shm /dev/shm  # untested

However, I cannot gain permission to run this as part of the deployment process.
Can/should the base image be updated to include /dev/shm?

Looks like we need to do something along these lines:
<filesystem type='ram'>
    <source usage='10000'/>
    <target dir='/dev/shm'/>
</filesystem>

http://libvirt.org/formatdomain.html#elementsFilesystems
@josephglanville Any thoughts on this?


Create Components

Hi! I kindly ask you for a review of this project. I have completed this milestone where we were required to:

Delete all the boilerplate from CRA (text, images, styles).
Create a directory called components.
Inside components, create a new Calculator.js file.
In Calculator.js, create a React component that matches the design proposed from the exercise.
Develop just the UI of the calculator.
Use class-based components.
Test it in the browser.

Kind Regards,
Pedro

Thank you!


Review for missing documentation - at_events_flutter (API Reference)

[ ] Right nav bar under documentation API reference requires review to ensure documentation is up to date and complete (samples and examples)
[ ] Do we need a documentation link?

Please check libraries as well (current, samples and examples)
LIBRARIES

[ ] at_event_notification_listener
[ ] at_events_flutter
[ ] bottom_sheet
[ ] colors
[ ] concurrent_event_request_dialog
[ ] constants
[ ] contact_list_tile
[ ] contact_service
[ ] contacts_initials
[ ] create_event
[ ] custom_button
[ ] custom_circle_avatar
[ ] custom_heading
[ ] custom_popup_route
[ ] custom_toast
[ ] display_tile
[ ] draggable_symbol
[ ] enums_model
[ ] error_screen
[ ] event_key_location_model
[ ] event_key_stream_service
[ ] event_location_share
[ ] event_member_location
[ ] event_notification
[ ] event_notification_dialog
[ ] event_services
[ ] event_time_selection
[ ] events_collapsed_content
[ ] events_map_screen
[ ] floating_icon
[ ] home_event_service
[ ] hybrid_notifiation_model
[ ] init_events_service
[ ] invite_card
[ ] loading_widget
[ ] location_tile
[ ] one_day_event
[ ] overlapping-contacts
[ ] participants
[ ] pop_button
[ ] recurring_event
[ ] select_location
[ ] selected_location
[ ] sync_secondary
[ ] text_styles
[ ] text_tile
[ ] texts
[ ] triple_dot_loading

Hi @nitesh2599 we need to review this very old ticket for accuracy, potentially close it and divert to the new pub.dev publishing issue. Creating new issue cards today.


In Discover, sentence font should not be bigger than card title

Screenshot :

How it should be : Roboto 24px

Size: S


Extension Elements and Functions

Discussed in https://github.com/ballsteve/xrust/discussions/114

Originally posted by zackpcodes October 12, 2024
Hi all! My team and I are planning to modernize our tech stack and re-write our main back end API in Rust. One of the key features throughout our system is XSL transformation. One key functionality we utilize is extension functions with our current library. I browsed the xrust code base, correct me if I am wrong please, but it seems there is no way to register custom functions. Is this something y'all would be interested in taking pull requests on? If so, any ideas of how you would like this implemented?
Best

Created branch extensions for this development.

Hey Steve,
I messed with this a little today and was able to get XPath functions to to work. I missed your message on the discussion and created a pull request to "dev". Take a look and see if i am on the write track and I can get a pull request on the extensions branch.
Best

Looking at the Transform enum, perhaps we can extend the Invoke variant and the Callable struct to handle custom/extension functions?
I'll have a crack at that and see how far it goes.

Do we want the application callback to be a function that takes arguments (a vector of Transform), or a closure? The StaticContext already has a few closures (messages, external resources, parsing), and that's a more Idiomatic Rust way of doing things. However, there would need to be a closure for each different extension, identified by QName, so I'd have to see how that works.

The thing about closures is they can't be cloned, that's why there's a separate StaticContext structure. Context needs to be clonable.

Agreed. Based on what I read I think closure makes more sense than a function. I think carrying vars from the surrounding scope would be good. My team currently uses hash maps outside of the function scope to look up values and stuff.

I've checked in my (incomplete) code that adds extension functions as a closure to StaticContext and Callable. Have a look and let me know what you think. In the meantime, I'll keep working on it to get it compiling and with tests to show how it works.

Looks great so far man! Look forward to trying it out

Today's push into the extensions branch adds an extension callback to StaticContext. Have a look in tests/transformgeneric at the generic_tr_callable_extension_1 test to see how it will be used.
The test is failing - it's not finding the extension. I'll have a look at that tomorrow. In the meantime, you might like to see if you can develop another test that uses the Context to read a variable. After fixing the failing test, the next thing I'll do setup the FormalParameters for the extension so that they work like an xsl:function.

It would have helped to actually pull the extension closure out of the static context :-(
Today's push in to the extensions branch has a working example of calling an extension function, i.e. a closure.

It turns out that the previous implementation didn't allow for multiple extensions to be defined. To fix that I've Boxed the callback closure and made it dynamic. Having multiple extension functions now works, and there's a test in transformgeneric/mod.rs that demonstrates this.


[Frontend] Using sync llm engine in a separate process in openai server mode

Using the regular llm_engine rather than async_llm_engine in server mode, while separating server functionality and LLM into different processes.
Partial support of the existing endpoints
Currently limited to only using mp backend for multi GPU, or a single GPU
Currently a work in progress

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

do you have any evidence? is this separation also beneficial in the sync llm engine?


Add a way to inspect containers created

@khaledkbadr which kind of inspection you need? Please update the description

@grimpy Added description needed for me. Feel free to add any inspection you need in the description

It would be convenient to be able to read all the info we pass during the creation so :

root_url
mount,
host_network
zerotier
bridge
port
hostname
storage


How to configure gmail account?

Hi,
I want to add my gmail account to send and receive emails, what's the best way to configure within postal?

To tell the truth Postal does not support external mail accounts. It can be configured to use your own private domains only and not gmail or something like that.

The reason for this is DKIM and SPF records. Gmail will not approve of an IP outside of their range to "send" emails FROM gmail.com - the remote servers (your recipients) will reject this mail.
Unless you authenticate and send outbound mail with your Gmail account you will not be able to reliably deliver if your From is Gmail (or really any other big isp)

Actually Postal can now be configured to use a relay host for outbound mail. See smtp_relays in the config file.

You all need to update postal server to allow password smtp_relays . It is very important .


issue-2146: Optional load sensor definition from configmap

Checklist:

[ ] My organization is added to USERS.md.

wip

done with local testing. and no references to live reload. final todos:

add a basic e2e test (configmap option loads ok)
update the configmap watcher to be more granular

integration tests added, fixed case for sensor updates, watcher couldnt be modified. will raise pr once tests pass


HTTPS is the way

That .default thing caught me for a minute.  Really wish there was better
interop between cjs and ecmascript modules... Not sure if the .default is
better on the require (so the API works as "expected" w/r/t to cjs) or if you
want devCert.default() when invoking it.
Plus the {installCertutil: true} option doesn't seem to work on my mac at the
very least, as chrome and firefox still give security warnings?
Lastly should we be only HTTPS or HTTP by default with HTTPS opt-in or HTTPS
by default or HTTP opt-in
I figure if we can get this working on multiple platforms without security
issues there's no reason not to do HTTPS-only?

We might also want to wait for:
https://github.com/davewasmer/devcert/pull/7
https://github.com/davewasmer/devcert/pull/8
To land (if they do) since we can stop doing the data manipulation and let it occur upstream (which feels more proper).

Ohey, yeah alternatively we could just use https://github.com/Dexus/pem - it's what wzrd uses and means we don't have to deal with weird source code

Closed in favor of #217


[Python] array anyOf generating invalid Python code

What are you generating using Kiota, clients or plugins?
API Client/SDK
In what context or format are you using Kiota?
Linux executable
Client library/SDK language
Python
Describe the bug
Invalid python code causes python runtime exceptions to occur due to the generated python not being valid for anyOf.
Expected behavior
Python anyOf to produce python code that doesnt cause the runtime exceptions to occur when trying to call endpoints from the generated client
How to reproduce
    '200':
      description: The HTTP `200 OK` success status response code indicates that the request has succeeded.
      content:
        application/vnd.api+json:
          schema:
            type: object
            description: A list of LocationSpread entities.
            properties:
              links:
                type: object
                properties:
                  next:
                    type: string
                    nullable: true
              data:
                type: array
                items:
                  $ref: '#/components/schemas/LocationSpreadModel'
              included:
                type: array
                items:
                  anyOf:
                    - $ref: '#/components/schemas/PeriodModel'
                    - $ref: '#/components/schemas/LocationSpreadSpecificationModel'

Open API description file
energyapi.json
Kiota Version
1.14.0
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
No response
Debug output
PS C:\Projects\icis-openapi-kiota> .\generate-kiota-api-clients.ps1
Generating for https://developer.icis.com/portals/api/sites/icis-live-portal/liveportal/apis/energyapi/download_spec
info: Kiota.Builder.KiotaBuilder[0]
Cleaning output directory /app/output/Python/energy
dbug: Kiota.Builder.KiotaBuilder[0]
kiota version 1.14.0
dbug: Kiota.Builder.KiotaBuilder[0]
cache file /tmp/kiota/cache/generation/BA16C3B0119BBFE2AA3E7CA599D573E64E2A6E1D154015CF57C24062ED34671C/download_spec not found, downloading from https://developer.icis.com/portals/api/sites/icis-live-portal/liveportal/apis/energyapi/download_spec
info: Kiota.Builder.KiotaBuilder[0]
loaded description from remote source
dbug: Kiota.Builder.KiotaBuilder[0]
step 1 - reading the stream - took 00:00:01.0235017
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/volatilityIndex - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/diffToPrevBasisMid - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/volatilityIndex - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/volatilityIndex - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1basisPriceAssessments~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/diffToPrevBasisMid - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1dataEvents/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1dataEvents/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/volume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/numOfTrades - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/volume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/numOfTrades - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/volume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1indices~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/numOfTrades - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1locationSpreads/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1locationSpreads/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1locationSpreads~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/referenceDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/startDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/endDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/referenceDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/startDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/endDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/referenceDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/startDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1periods~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/endDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1priceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1priceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/volatilityIndex - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1priceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1priceAssessments/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/volatilityIndex - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1priceAssessments~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1priceAssessments~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/volatilityIndex - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1sparkAndDarkSpreads/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1sparkAndDarkSpreads/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1sparkAndDarkSpreads~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/volume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades/get/responses/200/content/application~1vnd.api+json/example/data/0/attributes/totalVolume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/volume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades/get/responses/200/content/application~1vnd.api+json/example/data/1/attributes/totalVolume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/createdForDate - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/volume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/paths/~1trades~1{id}/get/responses/200/content/application~1vnd.api+json/example/data/attributes/totalVolume - Data and type mismatch found.
warn: Kiota.Builder.KiotaBuilder[0]
OpenAPI warning: #/components/schemas/IndexModel/properties/attributes/properties/numOfTrades - The format integer is not supported by Kiota for the type number and the string type will be used.
dbug: Kiota.Builder.KiotaBuilder[0]
step 2 - parsing the document - took 00:00:00.1286369
dbug: Kiota.Builder.KiotaBuilder[0]
step 3 - updating generation configuration from kiota extension - took 00:00:00.0001125
dbug: Kiota.Builder.KiotaBuilder[0]
step 4 - filtering API paths with patterns - took 00:00:00.0026473
dbug: Kiota.Builder.KiotaBuilder[0]
step 5 - checking whether the output should be updated - took 00:00:00.0193923
dbug: Kiota.Builder.KiotaBuilder[0]
step 6 - create uri space - took 00:00:00.0024655
dbug: Kiota.Builder.KiotaBuilder[0]
InitializeInheritanceIndex 00:00:00.0031273
dbug: Kiota.Builder.KiotaBuilder[0]
CreateRequestBuilderClass 00:00:00
dbug: Kiota.Builder.KiotaBuilder[0]
MapTypeDefinitions 00:00:00.0218516
dbug: Kiota.Builder.KiotaBuilder[0]
TrimInheritedModels 00:00:00
dbug: Kiota.Builder.KiotaBuilder[0]
CleanUpInternalState 00:00:00
dbug: Kiota.Builder.KiotaBuilder[0]
step 7 - create source model - took 00:00:00.0900220
dbug: Kiota.Builder.KiotaBuilder[0]
127ms: Language refinement applied
dbug: Kiota.Builder.KiotaBuilder[0]
step 8 - refine by language - took 00:00:00.1278204
dbug: Kiota.Builder.KiotaBuilder[0]
step 9 - writing files - took 00:00:01.0558486
dbug: Kiota.Builder.KiotaBuilder[0]
cache file /tmp/kiota/cache/generation/BA16C3B0119BBFE2AA3E7CA599D573E64E2A6E1D154015CF57C24062ED34671C/download_spec is up to date and clearCache is False, using it
info: Kiota.Builder.KiotaBuilder[0]
loaded description from remote source
dbug: Kiota.Builder.KiotaBuilder[0]
step 10 - writing lock file - took 00:00:00.0130857
Generation completed successfully
dbug: Kiota.Builder.KiotaBuilder[0]
Api manifest path: /app/apimanifest.json
Other information
I'm aware of the other errors coming up the output, but I dont think those impact the include with anyOf not working.

It DOES generate the classes, however, Python seems to have an issue in recognising the imports and using the class. See line 53, even PyCharm is not sure what class is being referred to, despite the class being generated below. Is it because the class is nested within the response class?

Hi @pjmagee
Thanks for using kiota and for reaching out.
To be clear, is the import path is correct? i.e. is it constructed properly to point to the type to be imported? (no mismatch in structure/casing that you could edit out).
What happens if you create a schema component for the anyof type and refer to that for the items schema? Do you still run into the same issue?

I think because its nested, the import is also broken, so the import path is also kind of incorrect. It also doesnt get picked up correctly.
using Github Copilot, it actually mentions something similar...

I tried to import from the class, but im struggling to change the import statement to getting it to be detected correctly.

Removing the import and doing this seems to be "acceptable" according to Python/PyCharm
"included": lambda n : setattr(self, 'included', n.get_collection_of_object_values(PriceAssessmentsGetResponse.PriceAssessmentsGetResponse_included)),

I think this  may be part of a larger issue. Looking at the LocationSpreadsGetResponse_included generated class:
It seems to not generate some of the fields. Unsure if its related to the anyOf or due to the anyOf

Thanks for the additional information. @shemogumbe do you think this could be the same thing you were referring to in https://github.com/microsoftgraph/msgraph-beta-sdk-python/issues/391 ??

I know our spec isn't perfect, so also confirmed its not a spec specific thing and C# looks to be generating okay.. Just example showing intellisense/properties being generated correctly

Thanks for the additional information. @shemogumbe to confirm whether this could be the bug he was mentioning. (it's a holiday for him, we'll probably only hear back next week)

Yes, this could be related, classes are generated and nested, the more the nesting, we lose the ability to import the classes

@shemogumbe I can see the other issue has been closed, does that mean this one is solved as well?

If we have a new docker build, light me up and I'll give it another go!

Hello, this is not related to the earlier issue, the other issue was about imports not being available because the user was using a v1 client to execute functionality that is only on Beta.
The classes could therefore not be imported because of a client and APVersion mismatch.
I am currently working on this, started investigating from  generations involving anyof
Using the file shared at energyapi.json :

The structure is invalid josn
converting this to YAML - the file seemed malformed and I can't hus run generation.
To fix the generation, I would wish to generate uisng an openapi file that has anyOf and see the generatd output to help get context.

Any more  further context you might share to help me reproduce this @pjmagee

That's odd? Our EnergyAPI yaml file is valid that I am able to generate various language outputs, including the Python. The original file is yaml, not json.

Hello @pjmagee this works and generates the code https://github.com/shemogumbe/openapi/tree/main/openapi/msgraph-energy/python
Kindly confirm what you mean by, Generates Invalid code

Looking at the code, I notice imports to classes that  do not exist e.g:
In file basis_price_assesment_get_response.py we have two imports from modules not generated

        from .basis_price_assessments_get_response_included import BasisPriceAssessmentsGetResponse_included

and
        from .basis_price_assessments_get_response_included import BasisPriceAssessmentsGetResponse_included
```

The files generated in that directory are
1. basis_price_assesments_get_response_links.py with class `BasisPriceAssessmentsGetResponse_links`
2.  basis_price_assessments_request_builder.py with class `class BasisPriceAssessmentsRequestBuilder(BaseRequestBuilder):
`

Does this capture the issue you are facing?

I have a screenshot above showing the problem. The code generated is invalid, in that Python cannot detect the generated code, because the imports created and the nested classing is invalid python.

I notice the modules suffixed with _inlcuded are not actually generated, but imported and the classe suffixed _cluded used? right?

Hello, sorry been really busy. Please give me some time to check this. 🙏

Something still seem broken

The fields don't seem to be created in the Model

This is old code, I can see with new kiota version, the class is moved to its own file now

But actually, the fields is not existing here?

self.period_model and self.basis_price_assessment_speciciation_model both not defined on this class as fields

And here with intellisense you can see, it know the function on this class exist, but i cannot retrieve the properties

@shemogumbe

Re-opening for @shemogumbe to take a look

Hello @pjmagee
If I get you right, two things are happening:

create_from_discriminator_value, serialize and get_field_deserializer methods do not exist
The two class attributes referenced as self.basis_price_assesment_specificaton_model and self.period_model do not exist

Hello @pjmagee If I get you right, two things are happening:

create_from_discriminator_value, serialize and get_field_deserializer methods do not exist
The two class attributes referenced as self.basis_price_assesment_specificaton_model and self.period_model do not exist

the kiota methods in bullet point 1, do exist and you can see them in the screenshot intellisense
Correct on bullet point 2, the code is not generating the model attributes from the spec

Working on this

@rkodev to look try looking into this while @shemogumbe is OOF.

This was fixed with my PR https://github.com/microsoft/kiota/pull/4775, tested with https://raw.githubusercontent.com/shemogumbe/openapi/refs/heads/main/openapi/energyapi2.yml and we get perfectly usable code with no errors from the generated client.
Closing as fixed

Amazing!!


Unit type missing

What is your idea? Provide a use case.
I don't seem to find any mention on how to construct the unit type in the docs, I also tried some variations of (), unit, Unit to no avail. Why is that not included in the primitive types?
Why is it a good idea?
You can always declare your own unit type, but I just expected it to be present in the primitive types. If there is a good reason against having it, maybe it would be useful to add it to the docs.
What is the current alternative and why is it not good enough?
Declare your own unit type.
Thanks!

Void it is.
See: https://aiken-lang.org/language-tour/primitive-types#void

Thanks for the reply @KtorZ. However, I still don't understand why that should be called Void rather than Unit. I would expect those two types to have different semantics.
I think it could be beneficial to mention this explicitly in the docs you linked, maybe adding some examples around the semantics of matching against this type.

 If that's the case, then, well, we just have a different semantic than Haskell :).
We could potentially add a small note to the website documentation for the Haskellers, feel free to make a PR 👍

Yeah, you are right. But I would expect a lot aiken developer to come from a Haskell background as well :)
I did not know that other languages use the same convention (just found this https://en.wikipedia.org/wiki/Unit_type) thanks for pointing that out!


is this project still maintained?

is this project still maintained?
is there a newer maintained fork?

I'm asking myself the same question. Does anyone has an alternative?

I will try it
thx for the hint

I am wondering if the project is still maintained as well. The only other calendar plugin I know is jQuery UI's datepicker. But I am not sure if it has the functionality you need, @shadowempire123.
Maybe this stackoverflow post will help you.

thx @LapinskasL
but does not support times...
currently trying out this solution: https://www.reddit.com/r/sveltejs/comments/10udq4w/what_is_the_best_library_to_allow_dates_range/
but also did not get times working.
probably I will just use 2 date/time pickers with SveltyPicker: https://mskocik.github.io/svelty-picker/playground

@shadowempire123, I found a plugin call Air Datepicker. It seems to be still maintained. In the docs you'll find you can pick the day of the week the calendar starts on, and it has a time picker.

It's still maintained. Check https://github.com/flatpickr/flatpickr/discussions/2479

Project is dead.


[DISCUSS] Rename quickwit.json to metastore.json

Description
Rename quickwit.json to metastore.json. Something we discussed with @fmassot. WDYT @fulmicoton?

I think that's better since quickwit.json doesn't tell anything

I prefer quickwit.json but I don't care all that much.

I prefer quickwit.json but I don't care all that much.

We also wanted to avoid any confusion with quickwit.yaml.

Ah yes, Metastore.json is much better


get_variable  missing reuse parameter

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with the
documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go
here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script
provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
MacOSX 10.14.5 Mojave
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
happens on a mobile device:
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below):2.4.0
Python version:
python --version
Python 3.6.6 :: Anaconda, Inc.
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

v2.4.0-rc4-71-g582c8d236cb 2.4.0
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
tg.get_variable cannot reuse  existing variable.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
tf.get_variable cannot pass in the reuse parameter, see  logs below:
(TensorFlow-LiveLessons) bash-3.2$ python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
v2.4.0-rc4-71-g582c8d236cb 2.4.0
(TensorFlow-LiveLessons) bash-3.2$ python
Python 3.6.6 |Anaconda, Inc.| (default, Jun 28 2018, 11:07:29)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow.compat.v1 as tf
tf.disable_v2_behavior()
WARNING:tensorflow:From /Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/compat/v2_compat.py:96: disable_resource_variables (from tensorflow.python.ops.variable_scope) is deprecated and will be removed in a future version.
Instructions for updating:
non-resource variables are not supported in the long term
n_input = 784
n_dense = 128
W = tf.Variable(tf.random_normal([n_input, n_dense]))
tf.get_variable('W', [n_input, n_dense],
...                       initializer=tf.keras.initializers.VarianceScaling(
...                       scale=1.0, mode="fan_avg",
...                       distribution="truncated_normal"
...                         ))
<tf.Variable 'W:0' shape=(784, 128) dtype=float32_ref>
tf.get_variable('W', [n_input, n_dense],
...                       initializer=tf.keras.initializers.VarianceScaling(
...                       scale=1.0, mode="fan_avg",
...                       distribution="truncated_normal"
...                         ))
Traceback (most recent call last):
File "", line 4, in
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 1593, in get_variable
aggregation=aggregation)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 1336, in get_variable
aggregation=aggregation)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 591, in get_variable
aggregation=aggregation)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 543, in _true_getter
aggregation=aggregation)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 893, in _get_single_variable
(err_msg, "".join(traceback.format_list(tb))))
ValueError: Variable W already exists, disallowed. Did you mean to set reuse=True or reuse=tf.AUTO_REUSE in VarScope? Originally defined at:

File "", line 4, in

tf.get_variable('W', [n_input, n_dense],
...                       initializer=tf.keras.initializers.VarianceScaling(
...                       scale=1.0, mode="fan_avg",
...                       distribution="truncated_normal",
...                               reuse=tf.AUTO_REUSE))
Traceback (most recent call last):
File "", line 5, in
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 538, in new_func
return func(*args, **kwargs)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 605, in new_func
return func(*args, **kwargs)
TypeError: init() got an unexpected keyword argument 'reuse'
exit()

Digging into the  source code tensorflow/python/ops/variable_scope.py, missing parameter  reuse
@tf_export(v1=["get_variable"])
def get_variable(name,
shape=None,
dtype=None,
initializer=None,
regularizer=None,
trainable=None,
collections=None,
caching_device=None,
partitioner=None,
validate_shape=True,
use_resource=None,
custom_getter=None,
constraint=None,
synchronization=VariableSynchronization.AUTO,
aggregation=VariableAggregation.NONE):
return get_variable_scope().get_variable(
_get_default_variable_store(),
name,
shape=shape,
dtype=dtype,
initializer=initializer,
regularizer=regularizer,
trainable=trainable,
collections=collections,
caching_device=caching_device,
partitioner=partitioner,
validate_shape=validate_shape,
use_resource=use_resource,
custom_getter=custom_getter,
constraint=constraint,
synchronization=synchronization,
aggregation=aggregation)
if we can add  this  parameter to  the parameter list the above problem could be fixed.
Thanks
The argument list for get_variable must match arguments to get_local_variable.
So, if you are updating the arguments, also update arguments to
get_local_variable below.
@tf_export(v1=["get_variable"])
def get_variable(name,
shape=None,
dtype=None,
initializer=None,
regularizer=None,
trainable=None,
collections=None,
caching_device=None,
partitioner=None,
validate_shape=True,
use_resource=None,
custom_getter=None,
constraint=None,
synchronization=VariableSynchronization.AUTO,
aggregation=VariableAggregation.NONE,
reuse=None):
return get_variable_scope().get_variable(
_get_default_variable_store(),
name,
shape=shape,
dtype=dtype,
initializer=initializer,
regularizer=regularizer,
trainable=trainable,
collections=collections,
caching_device=caching_device,
partitioner=partitioner,
validate_shape=validate_shape,
use_resource=use_resource,
custom_getter=custom_getter,
constraint=constraint,
synchronization=synchronization,
aggregation=aggregation,
reuse=reuse)
Xiquan Ren

Was able to reproduce the issue with TF v2.3, TF v2.4 and TF-nightly. Please find the gist of it here. Thanks!

Was able to reproduce the issue with TF v2.3, TF v2.4 and TF-nightly. Please find the gist of it here. Thanks!

Please take a look at https://www.tensorflow.org/api_docs/python/tf/compat/v1/get_variable. You can create a variable_scope with reuse=True in order to achieve the intended behavior

Please take a look at https://www.tensorflow.org/api_docs/python/tf/compat/v1/get_variable. You can create a variable_scope with reuse=True in order to achieve the intended behavior

it will not recognize the parameter, please check.
tf.get_variable('W', [n_input, n_dense],
... initializer=tf.keras.initializers.VarianceScaling(
... scale=1.0, mode="fan_avg",
... distribution="truncated_normal",
... reuse=tf.AUTO_REUSE))
Traceback (most recent call last):
File "", line 5, in
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 538, in new_func
return func(*args, **kwargs)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 605, in new_func
return func(*args, **kwargs)
TypeError: init() got an unexpected keyword argument 'reuse'
exit()

it will not recognize the parameter, please check.
tf.get_variable('W', [n_input, n_dense],
... initializer=tf.keras.initializers.VarianceScaling(
... scale=1.0, mode="fan_avg",
... distribution="truncated_normal",
... reuse=tf.AUTO_REUSE))
Traceback (most recent call last):
File "", line 5, in
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 538, in new_func
return func(*args, **kwargs)
File "/Users/philren/.local/share/virtualenvs/TensorFlow-LiveLessons-G6MnyUB7/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 605, in new_func
return func(*args, **kwargs)
TypeError: init() got an unexpected keyword argument 'reuse'
exit()

thanks,fixed...

can you explain how did you fixed it. I didn't understand that variable scope thing


Change password page

We need a page to changed admin user password

We need a page to changed admin user password

can you please provide more information, I would like to contribute to the repo

@PritamP20 i am glade that you like to contribute.
Basically I guess I would start with setting up the local environment.
Add navigation on admin user dropdown.
create a page in react admin with a form current password and new password and button to submit.
Backend API to update the password in surrealdb.
We do have a update password method already which you can call from handler. https://github.com/avored/avored-rust-cms/blob/main/src/services/admin_user_service.rs
If you want i am happy to help you at any stage. Do you want me to assigned it you?
Thanks

@indpurvesh I would like to work on this. Can you please assign it to me?

@srushtiss
let me know if you need any help with setting up local setup or anything.

@indpurvesh May i know what username and password I need to use for .env file?

@srushtiss let me know if you need any help with setting up local setup or anything.

@indpurvesh May i know what username and password I need to use for .env file?

Are you talking about SMTP username and password can be left null as it is only used to sent email testing during forgot password email.
If you want to test that in that case you can create a sandbox account on mailtrap.io website and you will get your own email testing username and password.

Not that
Error: ConfigMissing("AVORED_DATABASE_NAMESPACE")

Basically you just have to rename the .env.example => .env in root of the project (rust backend project root)
Admin React Frontend app root:
root/react-admin/ rename .env.example => .env file

It worked. Thank you.

Let me know if you wanted me to work on backend api?


Zhexuany/improve readme

This change is

Thanks.  we update tutorial in https://github.com/pingcap/docs/blob/master/op-guide/ansible-deployment.md.