TypeError: Cannot read property 'setFlag' of null

Hi there,
I'm encountering this error on W10, on my first run of TypeDoc v0.10.0. Tried on both Node 9.5.0 and 8.9.3.
PS C:\...\MyProj> yarn docs
yarn run v1.3.2
$ typedoc --excludePrivate --excludeNotExported --out docs/ src/

Using TypeScript 2.7.1 from C:\...\MyProj\node_modules\typedoc\node_modules\typescript\lib
C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\variable.js:74
                    variable.setFlag(index_1.ReflectionFlag.Const, true);
                             ^

TypeError: Cannot read property 'setFlag' of null
    at VariableConverter.convert (C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\variable.js:74:30)
    at Converter.convertNode (C:\...\MyProj\node_modules\typedoc\dist\lib\converter\converter.js:127:53)
    at C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\variable-statement.js:39:33
    at Array.forEach (<anonymous>)
    at VariableStatementConverter.convert (C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\variable-statement.js:34:47)
    at Converter.convertNode (C:\...\MyProj\node_modules\typedoc\dist\lib\converter\converter.js:127:53)
    at C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\block.js:85:29
    at Array.forEach (<anonymous>)
    at BlockConverter.convertStatements (C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\block.js:84:26)
    at C:\...\MyProj\node_modules\typedoc\dist\lib\converter\nodes\block.js:62:27

Hello, that looks like it may have been caused by #611. Do you have a small amount of code that can reproduce this error. Are you using const anywhere other than for variable declaration?

I'm not sure what code that I have that would trigger this, the codebase is pretty simple and it lints just fine. I don't think I have any special or weird uses of const. I'm also encountering this issue in WSL (Ubuntu on Windows).

I'm not able to reproduce the error. Do you have a small repo demonstrating the issue that you could share?

@aciccarello I'm not sure where the issue even exists as it's my first time running it in this project. It's not exactly a small codebase but I'm in the process of trying to publish it publicly on GitHub.

@aciccarello I've narrowed the cause of the error down.
The issue occurs when trying to require() a dependency that's not installed (for example, a peer dependency) WHILE using the --excludeNotExported argument.
The following file will throw the setFlag() error:
const localForage = require('localforage');

Ah, the exclude exported flag appears to be the cause. Creating a const variable without exporting it and using the --excludeNotExported flag reproduces it. I don't think the require() call is significant.

Closed via #694

This is still happening for me with the latest version (and TypeScript 2.7.1), but I managed to narrow it down to the following simple case.
Code
abstract class BaseTryImpl {
}

I run
 ../typedoc/bin/typedoc --mode file --out doctest --excludeNotExported test.ts

which results in
Using TypeScript 2.7.1 from /home/mad_gaksha/Applications/typedoc/node_modules/typescript/lib
/home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/class.js:43
                reflection.setFlag(index_1.ReflectionFlag.Abstract, true);
                           ^

TypeError: Cannot read property 'setFlag' of null
    at ClassConverter.convert (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/class.js:43:28)
    at Converter.convertNode (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/converter.js:127:53)
    at /home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/block.js:78:33
    at Array.forEach (<anonymous>)
    at BlockConverter.convertStatements (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/block.js:76:29)
    at /home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/block.js:67:23
    at Context.withSourceFile (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/context.js:87:9)
    at BlockConverter.convertSourceFile (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/block.js:58:17)
    at BlockConverter.convert (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/nodes/block.js:48:18)
    at Converter.convertNode (/home/mad_gaksha/Applications/typedoc/dist/lib/converter/converter.js:127:53)

It works once I remove the --excludeNotExported flag, or the abstract modifier from the class.

@blutorange Thanks for investigating. A fix has been merged into master but I still need to make a release after testing another bug fix.

@aciccarello Thanks for replying so quickly. Do you mean the fix mentioned above (#694)? I cloned this repository and tried it with a fresh build of that. It only seems to be fixing a null variable in file variable.js, whereas with the example I tried there is a null variable in file class.js.

@blutorange Ah, I missed that it was showing up in a different class. I'm curious if there is a problem with the createReflection method.

So createReflection should be expected to sometimes be null. Therefore we should add a check of the result in class.ts. The other instances should be fine. Any uses in context.withScope(reflection, ...) are fine because withScope checks if the scope exists. The few other cases are already handled.
I'm surprised this hasn't been identified before but the fix should be simple.


Added a new rebus worship

Associated Issue: #
Summary of Changes

change 1
change 2

Pull Request Test Coverage Report for Build 635

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Xcode - Archiving the project will not show in Organizer

If I build the project and running it on real device or simulator everything is fine. But when I do Product -> Archivei t will complete the archive with success but the archive is not in Organizer. If I remove the package from package.json and cd ios && pod update and try again to archive it eveything is fine. Any reason?

Are you using @react-native-mapbox-gl/maps as well with this library?
It is related to this issue here - https://github.com/react-native-mapbox-gl/maps/issues/1097
This can be fixed by updating @react-native-mapbox-gl/maps to 8.1rc5 and adding the following to your Podfile -
  pre_install do |installer|
    $RNMBGL.pre_install(installer)
    # other pre install hooks
  end
  post_install do |installer|
    $RNMBGL.post_install(installer)
    # other post install hooks
  end

You'll also need this at the top of your Podfile also -
$ReactNativeMapboxGLIOSVersion='6.3.0'

I have an alternate solution if this does not work for you.

I am not using @react-native-mapbox-gl/maps

This below should solve the problem for you.
Open this file at ios/Pods/Target Support Files/<EMAIL_ADDRESS>and comment out lines 85 thru 89 -
#install_dsym<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>

Now this seem to work. Can you please explain how this makes the difference?

It gets rid of the underpants gnomes.
:~)
Well not really... but if you look at this whole thread here - https://github.com/react-native-mapbox-gl/maps/issues/1097 and specifically this comment https://github.com/react-native-mapbox-gl/maps/issues/1097#issuecomment-770064084 and the one after that.
This solution from that thread is something I'm interested in trying to see if I can get rid of this pod hack

Now make sense and thank you

This below should solve the problem for you.
Open this file at ios/Pods/Target Support Files/<EMAIL_ADDRESS>and comment out lines 85 thru 89 -
#install_dsym<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>#install_bcsymbolmap<EMAIL_ADDRESS>

It's working, Thanks.


Resolve issue with EBCDIC header of SEGY created by Petrel

OS windows10; python 3.9; MDIO v0.1.6
SEGY files generated by Petrel crash with an error related to the EBCDIC.

UnicodeDecodeError                        Traceback (most recent call last)
Cell In [14], line 1
----> 1 segy_to_mdio(
2     segy_path=f,
3     mdio_path_or_buffer="tst3d_cube.mdio",
4     index_bytes=(5, 9),
5     index_names=("inline", "crossline"),
6 )
File C:\appl\python\env\mdio_tst\lib\site-packages\mdio\converters\segy.py:173, in segy_to_mdio(segy_path, mdio_path_or_buffer, index_bytes, index_names, index_lengths, chunksize, endian, lossless, compression_tolerance, storage_options, overwrite)
169 # Read file specific metadata, build grid, and live trace mask.
170 with segyio.open(
171     filename=segy_path, mode="r", ignore_geometry=True, endian=endian
172 ) as segy_handle:
--> 173     text_header = parse_text_header(segy_handle)
174     binary_header = parse_binary_header(segy_handle)
175     num_traces = segy_handle.tracecount
File C:\appl\python\env\mdio_tst\lib\site-packages\mdio\segy\parsers.py:66, in parse_text_header(segy_handle)
54 def parse_text_header(segy_handle: segyio.SegyFile) -> list[str]:
55     """Parse text header from bytearray to python list of str per line.
56
57     The segyio library returns the text header as a  bytearray instance.
(...)
64         Parsed text header in list with lines as elements.
65     """
---> 66     text_header = segy_handle.text[0].decode()
67     text_header = [
68         text_header[char_idx : char_idx + 80]
69         for char_idx in range(0, len(text_header), 80)
70     ]
71     return text_header
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd5 in position 155: invalid continuation byte

Petrel EBCDIC appear to require encoding='ISO-8859-1' rather than the default UTF-8
Using
segy_handle.text[0].decode(errors='ignore')
should get around this issue

Thank you for reporting this issue, @gmac161.
Would you mind sending a PR? If not, will push a fix soon.

@gmac161, thanks for reporting it. I fixed it in #51
Can you please try it from that branch and let us know if it resolved the issue?
If you are using GitHub CLI
git clone https://github.com/TGSAI/mdio-python.git
gh pr checkout 50
pip install -e .

@tasansal I've run my cube using this branch and it works

@gmac161, thank you very much for your feedback and testing! I will close the issue.


Data Transfer - Gateway to HIP HRP

As a developer, I would like to have gateway to hrp interaction related code.
Implementation details can be part of separate issue.

This has been taken care of.


BeSman repo updated with 'bes open' command

Added 'bes open'  command.
Removed 'bes publish' command.

@jobyko @panickervinod LGTM.
@jobyko Please address the comments.

Removed repeated function, __besman_open_file from repo helper file.

@jobyko @asa1997


fix: fixing valid svg checking

some JSDoc fixes

Suggestion: moving from mocha to jest. Current problem is with inability of mocking modules. For example in test/svg-shape.test.js I have to copy-paste test input strings from  test/fix-xml-string.test.js instead of mocking lib/svg-sprite/fix-xml-string.js behavior.
But there is two problems:

Jest is a BIG package
Current test dependency. All test a designed to run step-by-step, but jest is designed to run parallel tests with random orde

Fixes #454

OK I start to believe there's indeed something wrong with the tests. They seem to fail frequently in calculateSvgDimensions. Something weird is going on there or the Windows runners are slow on many occasions.
We should try to increase mocha's timeout to see if it fixes the issues.
Unrelated to this PR, though, we just need a steady CI :)

@XhmikosR I'll check. I think it's regardless of calculateSvgDimensions test and not depends on tests order. We'll see

@XhmikosR I've changed the order of the tests and it working now in 100% times.
I am sure this isn't appropriate solution, but it make CI stable again. I am not sure what was causing the problem, but it surely not calculateSvgDimensions itself

@Kreeg can you make a separate PR for the tests fix please? And maybe choose better names, maybe numbers if a specific order is needed? Although, I don't quite get why this is needed.

@XhmikosR I did it just to demonstrate that is calculateSvgDimension is not the problem itself but the real reason is somewhere around.
I'll dig it. For now I'll rollback my changes.
What I mean here is what the changing the order of tests should not be a solution. This makes it weak and hardly and non-obviously intertwined.

@yisibl what do you think? This problem appeared after the resvg was added. The tests start failing by timeout (10s) randomly on windows machines with node v12, v14, v16

@yisibl what do you think? This problem appeared after the resvg was added. The tests start failing by timeout (10s) randomly on windows machines with node v12, v14, v16

For test timeout, try increasing the test timeout.

I the issue is solved by changing the order of tests, it means it's not a timeout issue but rather an issue with a test actually failing and as a result hitting the timeout without success.

All right, the Windows issue will be fixed by #567. It's unrelated to resvg or anything.

@yisibl thanks for the answer! Sorry to bother :)


Adding 'has' devdependency in  package.json

-->while running test error is coming that says "Cannot find module 'has' because of following line of "ReactEighteenAdapter.js" const has_1 = __importDefault(require("has"));
--> As a fix added 'has' as devdependency

@cfaester  could you please help with review of this PR-changes

Hi @siyadava-sindhu This dep is indeed a "dependency" not a dev. I will create a release with that, but I will have to reject this MR 😄

[like]  Sindhusha Yadavalli reacted to your message:

From: Christian @.>
Sent: Monday, April 29, 2024 2:57:08 PM
To: cfaester/enzyme-adapter-react-18 @.>
Cc: Sindhusha Yadavalli @.>; Mention @.>
Subject: Re: [cfaester/enzyme-adapter-react-18] Adding 'has' devdependency in package.json (PR #11)
Hi @siyadava-sindhuhttps://github.com/siyadava-sindhu This dep is indeed a "dependency" not a dev. I will create a release with that, but I will have to reject this MR 😄
—
Reply to this email directly, view it on GitHubhttps://github.com/cfaester/enzyme-adapter-react-18/pull/11#issuecomment-2082966653, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5XA4ADKNZGZKNBZMBGQMHLY7ZNUJAVCNFSM6AAAAABFRZ3YSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSHE3DMNRVGM.
You are receiving this because you were mentioned.Message ID: @.***>

Thank you so much for adding fix in latest version.
From: Christian @.>
Sent: Monday, April 29, 2024 8:27 PM
To: cfaester/enzyme-adapter-react-18 @.>
Cc: Sindhusha Yadavalli @.>; Mention @.>
Subject: Re: [cfaester/enzyme-adapter-react-18] Adding 'has' devdependency in package.json (PR #11)
Hi @siyadava-sindhuhttps://github.com/siyadava-sindhu This dep is indeed a "dependency" not a dev. I will create a release with that, but I will have to reject this MR 😄
—
Reply to this email directly, view it on GitHubhttps://github.com/cfaester/enzyme-adapter-react-18/pull/11#issuecomment-2082966653, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5XA4ADKNZGZKNBZMBGQMHLY7ZNUJAVCNFSM6AAAAABFRZ3YSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSHE3DMNRVGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Dates on X axis ?

Hey, nice project !
I have a question, is it possible to get dates on the X axis ?

There really isn't room to get date info within a single character, but I could add tick marks and include the date range as part of the result text at the bottom. Like "(12/5/2020 - 12/25/2020)".

Added the text and a fancy box
https://github.com/cgsimmons/covid-graph/pull/4


Build on java 17

This commit updates elasticsearch-hadoop to build on java 17. I did not look into it very much but Scala 2.10 and
Java 18 do not seem to be compatible. So I have removed support for Scala 2.10 as part of this. That also means
that support for Spark 1.x goes away altogether.
Relates #1791

I don't think we have any need to actually build on java 17 (yet) if we merge #1791.

Closing this in favor of the much smaller #1802


[DOCFIX] Modify docs/cn/Architecture.md

Modify chinese version of Architecture.md corresponding to revised English version

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/Alluxio-Pull-Request-Builder/17942/
Test PASSed.


Update easy-arch.sh

useradd problem when I was testing it in VM

Thanks, that "find and replace" screwed me!


Feature/rqmupdate

Thank you for your contribution.
Before submitting this PR, please make sure:

[x] PR description and commit message should describe the changes done in this PR
[x] Verify the PR is point to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
[x] Latest Code from master or specific release branch is merged to your branch
[x] No unwanted\commented\junk code is included
[x] No new warning upon build solution
[x] Existing unit test cases are passed
[ ] New Unit tests are added for your development
[x] Sanity Tests are successfully executed for Existing Functionality
[x] After creating pull request there should not be any conflicts
[ ] Resolve codacy comments
[x] Builds and checks are passed before PR is sent for review
[ ] Resolve code review comments

Unit test is added in Rqm Repository we are not able to added unit test in ginger because we only used Rqm Repository dll in ginger so need to add into Regression suite

NEw PR Created For the Same


Improve styling and responsive design

Problem
There are multiple issues with the current theme style file:

The monospace font is specified as a list of system fonts, unlike the body text, where the fonts are bundled with the theme. It is possible to override this behavior via a custom Sphinx style file, but it is relatively complicated because the additional fonts also need to be installed and picked up during build time, also, a bunch of elements do not use the right font family by default (see an override here: https://github.com/logikal-io/logikal-docs/blob/main/logikal_docs/static/css/logikal_docs.css#L4-L35). Using something like Roboto Mono would go well with the current text fonts. Issue https://github.com/readthedocs/sphinx_rtd_theme/issues/1295 is also related to this point.
Long monospace text snippets and class/function descriptions can make the page width go out of the viewport in mobile because the wrapping is wrongly configured (override here: https://github.com/logikal-io/logikal-docs/blob/main/logikal_docs/static/css/logikal_docs.css#L64-L71, example here: https://docs.logikal.io/stormware/1.0.0/auth.html and here: https://docs.logikal.io/stormware/1.0.0/connectors.html). Issue https://github.com/readthedocs/sphinx_rtd_theme/issues/1347 is also related ("content wider than screen" point).
The default background is slightly off-white, which makes displaying plots with white backgrounds look odd. It is also difficult to override the background color in the theme (overrides here: https://github.com/logikal-io/logikal-docs/blob/main/logikal_docs/static/css/logikal_docs.css#L73-L85), it would be much better if we could just override a few CSS variables instead of the current fragile approach.
The responsive design breakpoints are off, the sidebar covers a lot of space between 768px and 1100px. An improved approach can be seen here: https://github.com/logikal-io/logikal-docs/blob/main/logikal_docs/static/css/logikal_docs.css#L146-L194. This override makes the sidebar width more consistent and maximizes the space for the content, which is the most important part. This is especially important on modern high-DPI mobile screens. The issue can be reproduced on this page: https://docs.logikal.io/mindlab/1.0.0/ (try viewing it on mobile around 780px+).

Reproducible Project
Many of the issues can be seen in the MindLab (https://docs.logikal.io/mindlab/1.0.0/) and Stormware (https://docs.logikal.io/stormware/1.0.0/) documentation pages. The patches/overrides are applied through https://github.com/logikal-io/logikal-docs, but this approach is quite fragile. It would be much better to incorporate the overrides upstream.

Hi @GergelyKalmar :wave:
Thanks for describing your issues. To make each item actionable and to have a simpler communication, would you mind opening up one issue per item?
Also, in case you haven't seen - this project has a roadmap: https://sphinx-rtd-theme.readthedocs.io/en/stable/development.html#roadmap

Awesome, thanks :100:


Adding Azure Monitor Logs Dedicated Cluster workbook

PR Checklist

[ ] Explain your changes, so people looking at the PR know what and why, the code changes are the how.
[ ] Validate your changes using one or more of the testing methods.

This workbook will help finding details about workspaces, tiers, pricing tiers current ingestion, estimation of chargeback
If adding or updating templates:

[ ] post a screenshot of templates and/or gallery changes
[ ] ensure your template has a corresponding gallery entry in the gallery folder
[ ] If you are adding a new template, add your team and template/gallery file(s) to the CODEOWNERS file. CODEOWNERS entries should be teams, not individuals
[ ] ensure all steps have meaningful names
[ ] ensure all parameters and grid columns have display names set so they can be localized
[ ] ensure that parameters id values are unique or they will fail PR validation (parameter ids are used for localization)
[ ] ensure that steps names are unique or they will fail PR validation (step names are used for localization)
[ ] grep /subscription/ and ensure that your parameters don't have any hardcoded resourceIds or they will fail PR validation
[ ] remove fallbackResourceIds and fromTemplateId fields from your template workbook or they will fail PR validation

unclear: why are there 3 sub parameters of which 2 are hidden?

why not just have one sub parameter that finds all subs that have the resource type you're looking for, like
resources
| where type =~ 'microsoft.operationalinsights/clusters'
| distinct subscriptionId

if i replace all the other sub parameters with just that one it seems to work fine, but i'm not entirely sure why you did that.
then later there's 10 parameters that do strange things to filter down resources with some really strange queries which seem to all produce the same resource for me for 2-10?  1 is a list, everything else is the same single item?
for me i get errors that i can't query some of the workspaces involved so that's strange as well, so i don't think i can see the whole content of the workbook, so i'm not sure the intent of what it is doing, but the fact that it tries to figure out 10 different workspaces that way is strange to me?

seeing some screenshots of what it looks like in full action for real users with real access would also be good?

Hey @gardnerjr ,
the 3 parameters are supposed to relief the customer from the pain of selecting subscription containing the Cluster and the workspaces which might be different. this way they just get all the subscription to which they have access to with no need to select the one containing the cluster. Regarding the parameter, I needed 10 since the cross-resource limit is 100 and we could have up to 1000 workspaces linked to a cluster (if not mistaken, the limit has been recently moved to 7000).
As far as the screenshots go, I can add something or I can demo using a customer env. Up to your choice.

@gardnerjr : attaching some screenshots. Let me know if there's any other question I did not answer. Thanks.

@gardnerjr : what is missing to merge?

given that it isn't even running the build validation, i'm presuming it means you are not a member of any of the teams that have write access to the repo?
see the contributing docs around joining a team or creating a team
aside: i see this in the "Azure monitor - workspaces" folder and am not 100% sure that's where it should be?  gallery wise, azure monitor i get, but i wonder if this template should really be in the LogAnalytics Workspace folder to fall under the LA team's ownership?

Got you ... so far I am only member of microsoft/observabilityagents given my contribution to the 'AMA health' one. I thought about 'Azure Monitor - workspaces' since the cluster embraces more than one workspace and it works more at the Azure Monitor level. Don't you think so? If you agree, could you pls add me to the 'microsoft/azure-monitor-workspaces' group or point me to the proper person to do that?

@brunoga-ms you are not a member of https://github.com/orgs/microsoft/teams/observabilityagents, or you would have write access to the repo.  If you get added to that group, you'd be able to complete this PR.
the confusion about that folder, and the azure-monitor-workspaces team is that there is a literal actual resource type called "Azure Monitor Workspaces", which is not the same thing as "Log Analytics Workspaces"

strange thing, since Shayoni granted me that membership. As far as the confusion goes, feel free to advise for the best in term of visibility and context. Do you who can I ask for the right membership? I am going on vacation till the end of August, I will work again on this one once back.

strange thing, since Shayoni granted me that membership. As far as the confusion goes, feel free to advise for the best in term of visibility and context. Do you who can I ask for the right membership? I am going on vacation till the end of August, I will work again on this one once back.

i pinged Shayoni internally, but as i said you can look at the membership of that group and you are not there.  You'd have to talk to the owners of that group if you're contributing for something they intend to own.  Ownership here is tied to who supports these templates once they are released.


DOC - Add section about disabling Grammarly

Adds a section about disabling Grammarly for mobiledoc-kit instances due to https://github.com/bustlelabs/mobiledoc-kit/issues/422.
Small reorganization of the headers

+1 thank you, @YoranBrondsema !

released in v0.10.10.


Fix Typo in ProcessStataManagerRebuildNotification

@aswin89thee : Thanks for your contribution! The author, @mcoskun, has been notified to review your proposed change.


Latest nuxt version delays the load of CSS on SSR

Environment

Node Version:     v20.9.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
https://codesandbox.io/p/devbox/magical-joji-ynhtsr
Describe the bug
While the server is running in preview mode, if you set your network to slow 3G, you can see that the CSS for the 4 simple components defined and used on homepage is loaded after the whole page is loaded. The CSS missing is only the one defined in components. This is a minimal reproduction but on a full size project, with a lot of components, loading them all first without CSS is a dealbreaker
Additional context
https://github.com/nuxt/nuxt/assets/52782918/b674e625-d97c-4de8-a79f-da7b58a38fdc
No response
Logs
No response

https://github.com/nuxt/nuxt/assets/52782918/9212df86-fe40-4baf-add5-b541a7efb043

Can you double check with the nightly channel by any chance?

Can you double check with the nightly channel by any chance?

Tried the nightly channel on my local machine and it indeed fixes the problem. This means that the next nuxt release will fix this problem?

Yes, correct!
Closing as duplicate of https://github.com/nuxt/nuxt/issues/26514


Add oclif readme command

Adds oclif readme to the create-github-release step.
We use TriPSs/conventional-changelog-action to bump versions and build changelogs. We can run this without any changes/commits/pushes and just get next the "next version" in the output. We then can pass that to oclif readme with OCLIF_NEXT_VERSION.
Then we run the conventional-changelog-action again to generate and commit everything (including the readme changes)
Notes:

I remove the v in the source links using sed. We could make a flag for oclif readme if we wanted to 🤷
We discussed adding a "readme": "oclif readme" script to the package.json and adding that to wireit's build but we would have to update every single repo.
TripPSs does allow you to add a pre-commit scripts. Unfortunately it has to be a javascript file so we would also need to add a script to every repo.

Proof of this working:
https://github.com/salesforcecli/plugin-info/actions/runs/6151426819/job/16691447475
Note the Before git commands and After git commands steps that I used to confirm changes.
@W-13887925@

The warning works as expected. Will now bump oclif and run again

Readme is getting created with the oclif changes (here)
Release: https://github.com/salesforcecli/plugin-info/releases/tag/2.6.42-dev.6
I downloaded the tarball and confirmed that README links were correct:

https://github.com/salesforcecli/plugin-info/blob/2.6.42-dev.6/src/commands/doctor.ts


Cannot start the plugin

Describe the bug
Hi, I have installed grafana version 9.4.7 from a binary, then I added the plugin and it is not able to initialise it, is there any data I am missing?
Steps to reproduce
Could not start plugin  logger=plugin.loader pluginId=yesoreyeram-infinity-datasource err="fork/exec /app/grafana/plugins-bundled/yesoreyeram-infinity-datasource/gpx_infinity_linux_amd64: permission denied"
Version Details:

Grafana version : 9.4.7
Plugin version : Release v1.4.0

Additional context
gpx_infinity_linux_amd64: permission denied

Red hat 8.7

¿Cómo estás instalando el complemento? que sistema operativo

Red hat 8.7

How are you installing the plugin? What OS

Red hat 8.7

I simply restart the grafana service, do nothing else and when I do so I see the error that occurs.
Could not start plugin logger=plugin.loader pluginId=yesoreyeram-infinity-datasource err="fork/exec /app/grafana/plugins-bundled/yesoreyeram-infinity-datasource/gpx_infinity_linux_amd64: permission denied"

can you provide clear "steps to reproduce"?
I understand that to resolve this file I will have to give permissions chmod 755, is this correct? But nowhere do you mention it


Exception when trying to connect with websocket ! did not receive a valid HTTP response

Hello,
With a fresh and up to date version of Home Assistant, I can't start latest version of tydom2mqtt
Here my log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
STARTING TYDOM2MQTT
Detecting environnement......
/data/options.json detected ! Hassio Addons Environnement : parsing options.json....
{'TYDOM_MAC': '001A25xxxxxx', 'TYDOM_IP': '192.168.1.xx', 'TYDOM_PASSWORD': 'xx', 'TYDOM_ALARM_PIN': '9999', 'TYDOM_ALARM_HOME_ZONE': 1, 'TYDOM_ALARM_NIGHT_ZONE': 2, 'MQTT_HOST': 'xx', 'MQTT_USER': 'x', x'MQTT_PASSWORD': 'xx', 'MQTT_PORT': 1883, 'MQTT_SSL': False, 'log_level': 'trace'}
Initialising TydomClient Class
Setting local mode context.
Starting main loop_task
/app/main.py:119: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Attempting MQTT connection...
MQTT host :  homeassistant
MQTT user :  xx
##################################
Subscribing to :  +/tydom/#
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
TYDOM WEBSOCKET CONNECTION INITIALISING....
Building headers, getting 1st handshake and authentication....
Upgrading http connection to websocket....
Attempting websocket connection with tydom hub.......................
Host Target :
192.168.1.xx
Exception when trying to connect with websocket !
did not receive a valid HTTP response
wss://192.168.1.xx:443/mediation/client?mac=001A25xxxxxx&appli=1
{'Authorization': 'Digest username="001A25xxxxxx", realm="protected area", nonce="xxxx", uri="/mediation/client?mac=001A25xxxxxx&appli=1", response="xxx", qop="auth", nc=00000001, cnonce="xxx"'}

As you can see 2 issues
/app/main.py:119: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()

And the main one the "did not receive a valid HTTP response"
I had revert my phone app to an old version to change my Tydom password to a short one but same beheviour

Hi,
The /app/main.py:119: DeprecationWarning: There is no current event loop is a warnind that always occurs.
It doesn't mean that the app isn't working.
So please just ignore it until we fix it ;)
Regarding the Exception when trying to connect with websocket ! did not receive a valid HTTP response.
May you perform the following tests:

Remove the TYDOM_IP value to fallback to the default one (mediation.tydom.com)
Change for a password without any special character

And as @schmurtzm noticed in #6 , the add-on fails if we don't provide a TYDOM_ALARM_PIN because the expected value must contain 6 characters (I personally didn't experience it myself but I'll test it).

I got a 401 with mediation url and I had no special character in my password
TYDOM WEBSOCKET CONNECTION INITIALISING....
Building headers, getting 1st handshake and authentication....
Upgrading http connection to websocket....
Attempting websocket connection with tydom hub.......................
Host Target :
mediation.tydom.com
Exception when trying to connect with websocket !
server rejected WebSocket connection: HTTP 401
wss://mediation.tydom.com:443/mediation/client?mac=001A25xx&appli=1
{'Authorization': 'Digest username="001A25xxx", realm="ServiceMedia", nonce="MTY0MDE3NzAxxxxxxxxxTIwYTE4OWRhNmI3OA==", uri="/mediation/client?mac=001A25x&appli=1", response="53exxxc59679dd0f", qop="auth", nc=00000001, cnonce="e6e4xd9"'}

Ok it is working now.
In fact my password was too long and in the mobil application i don't saw that the 2 last characters were not added.
Thanks

Nice 🥳 !
If you know the max length of the password, I'm interested.
I could improve the app (clearly notify that the password is too long and so on).
Thanks!

The maximum password lenght seems to be 15 characters


JlamaStreamingChatModel does not support tools

Problem
JLama indicated that it supports the use of tools for (some) models. I have used tjake/Llama-3.2-1B-Instruct-JQ4, and that does indeed support tools.
However, when I try to use streaming for this model, it doesn't seem to support tools. This seems to be library issue and not model issue. I am not sure if it is correct to expect that streaming is supported for tools, but I would think it is.
Versions
I am using langchain4j 0.35.0 and jlama 0.7.0.
Reproduction path
import dev.langchain4j.agent.tool.Tool;
import dev.langchain4j.model.chat.ChatLanguageModel;
import dev.langchain4j.model.chat.StreamingChatLanguageModel;
import dev.langchain4j.model.jlama.JlamaChatModel;
import dev.langchain4j.model.jlama.JlamaStreamingChatModel;
import dev.langchain4j.service.AiServices;
import dev.langchain4j.service.Result;
import dev.langchain4j.service.TokenStream;

public class Main {
    public static void main() {
        String modelName = "tjake/Llama-3.2-1B-Instruct-JQ4";
        String prompt = """
                What is the square root of 1244?
                """.trim();

        System.out.println(promptModelUsingLangchain(prompt, modelName));
    }

    interface Assistant {
        TokenStream chat(String userMessage);
    }

    private static String promptModelUsingLangchain(String prompt, String modelName) {
        StreamingChatLanguageModel model = JlamaStreamingChatModel.builder()
                .modelName(modelName)
                .build();

        Assistant assistant = AiServices.builder(Assistant.class)
                .streamingChatLanguageModel(model)
                .tools(new MyTools())
                .build();

        TokenStream tokenStream = assistant.chat(prompt);
        tokenStream.onNext(System.out::println)
                .onComplete(System.out::println)
                .onError(Throwable::printStackTrace)
                .start();

        return "this line is never reached";
    }

    static class MyTools {
        @Tool
        int add(int a, int b) {
            System.out.println("Method was called with " + a + ", " + b);
            return a + b;
        }

        @Tool
        public double squareRoot(double x) {
            System.out.println("Method was called with " + x);
            return Math.sqrt(x);
        }
    }
}

Output:
[main] INFO com.github.tjake.jlama.tensor.operations.TensorOperationsProvider - Using Native SIMD Operations (OffHeap)
[main] INFO com.github.tjake.jlama.model.AbstractModel - Model type = Q4, Working memory type = F32, Quantized memory type = I8
Exception in thread "main" java.lang.IllegalArgumentException: Tools are currently not supported by this model
	at dev.langchain4j.model.chat.StreamingChatLanguageModel.generate(StreamingChatLanguageModel.java:61)
	at dev.langchain4j.service.AiServiceTokenStream.start(AiServiceTokenStream.java:116)
	at com.keylane.rapon.Main.promptModelUsingLangchain(Main.java:40)
	at com.keylane.rapon.Main.main(Main.java:19)

Hello!
Yes I need to fix this, I only added it for the non-streaming version.  I think the issue is to know when to not stream because the model is making a function call output (this should be hidden).  A user will only want to see the result of the model before and after the function call.

The workaround for now is to use the non-streaming model?

Yes, I'm not aware of another implementation that handles streaming chat with tool calls?  It's a tricky problem

Yeah I mean an oss tool like ollama.  I think what you would do is stream until you see a special token then progressively try to parse json and when closed execute the call

You may want to see this conversation.

Ah cool, I see localAI supports it I can see what they do and add it, thx!

https://github.com/langchain4j/langchain4j/pull/2181

Great! So for me to be able to use this, I need to wait for the next version of Langchain4j to come out or just update to the latest version of Jlama?

Next langchain4j


Problem installing CCL

Dear colleagues,
I am having a problem when installing CCL. I have been stucked in this for hours, searching for solutions, but without success. I will leave the code in a link below, so, if anyone can help me, I will be very grateful.
Here are the full code:
See the full code here
Here are some parts of the code, containing the error messages:
`luigi@luigi-pc:~$ pip install pyccl
Defaulting to user installation because normal site-packages is not writeable
Collecting pyccl
Using cached pyccl-2.6.tar.gz (12.6 MB)
Preparing metadata (setup.py) ... done
Requirement already satisfied: numpy in /usr/lib/python3/dist-packages (from pyccl) (1.21.5)
Requirement already satisfied: pyyaml in /usr/lib/python3/dist-packages (from pyccl) (5.4.1)
Building wheels for collected packages: pyccl
Building wheel for pyccl (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
`
` File "/tmp/pip-install-d0u5babn/pyccl_b2508809683b49f7b5624ad905207e36/setup.py", line 56, in run
        _compile_ccl(debug=self.distribution.debug)
      File "/tmp/pip-install-d0u5babn/pyccl_b2508809683b49f7b5624ad905207e36/setup.py", line 27, in _compile_ccl
        raise Exception("Could not build CCL")
    Exception: Could not build CCL
    [end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pyccl
Running setup.py clean for pyccl
Failed to build pyccl
Installing collected packages: pyccl
Running setup.py install for pyccl ... error
error: subprocess-exited-with-error
× Running setup.py install for pyccl did not run successfully.
│ exit code: 1
`
` File "/tmp/pip-install-d0u5babn/pyccl_b2508809683b49f7b5624ad905207e36/setup.py", line 56, in run
        _compile_ccl(debug=self.distribution.debug)
      File "/tmp/pip-install-d0u5babn/pyccl_b2508809683b49f7b5624ad905207e36/setup.py", line 27, in _compile_ccl
        raise Exception("Could not build CCL")
    Exception: Could not build CCL
    [end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> pyccl
note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
`
I will also leave the full code attached:
CCL-error-Luigi.pdf
Thank you in advance!

Looks like SWIG is not installed on your system.

It worked perfectly! I have spent some hours analyzing the code, and I didn't realize that. Thank you so much!

Glad to hear the problem is fixed.


add aes gcm mode

Codecov Report

Merging #4 (6172832) into master (1ac2436) will increase coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
+ Coverage   98.92%   99.13%   +0.21%
==========================================
  Files           4        4
  Lines         279      347      +68
==========================================
+ Hits          276      344      +68
  Misses          2        2
  Partials        1        1

Impacted Files
Coverage Δ

aes.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Use palette library instead rewriting hex colors in JSON file

Self-explanatory, basically use palette library instead rewriting hex colors in JSON file.

Thanks for raising this after what I mentioned in the original issue.
I should have caught this in my review (my bad!) but it looks like bake's source is included fully in the repositories and actually licensed under EPL. This requires the License to actually be fully EPL instead of MIT.
While we don't necessarily try to enforce tooling across our ports, we should really move away from bake as:

The full source code is included which is licensed under EPL. This is more restrictive than MIT which Catppuccin favours as its default license unless absolutely necessary.
Even with bake, bash is hard to maintain and parse at a glance.

I just wanted to confirm with you that you were thinking of removing bake as a dependency entirely with the inclusion of the palette library. In any case, until we move away from bake, We need to re-license the repo to be EPL by updating LICENSE to this.

@sgoudham I've removed bake completely from the repo tree followed up with credit under "Thanks To" section.
Commit: 64d39af


Wrong endpoint. Use https://api.deepl.com For Deepl PRO auth key

Hi,
When I try to use api-free key to translate text it works fine, but when I try to use Pro-key I get following error:
translator.translate_text('abc', target_lang='en-us').text
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "/home/.../venv3/lib/python3.6/site-packages/deepl/translator.py", line 685, in translate_text
    self._raise_for_status(status, content, json)
  File "/home/.../venv3/lib/python3.6/site-packages/deepl/translator.py", line 501, in _raise_for_status
    f"Authorization failure, check auth_key{message}"
deepl.exceptions.AuthorizationException: Authorization failure, check auth_key, message: Wrong endpoint. Use https://api.deepl.com

Translator calls v2 API and fails with this error. But when I tried to change api_call url from v2 to v1 it worked.
Is there any way to use my key with API v2 or change v2 call to v1 except for changing package source code?
I'm using python3.6.14 and requests==2.25.1

Hi @ibelous, thank you for reporting your problem.
This library is only intended to be used with DeepL API accounts; using keys from other kinds of accounts will not work.

Hi @ibelous, thank you for reporting your problem. This library is only intended to be used with DeepL API accounts; using keys from other kinds of accounts will not work.

Sorry no offense, but I don't see how this response addressed the problem. The API he made a request to was that of a deepl account or did you make a typo in your response to the issue?

Hi @MystiqueMo, this is a fair question to ask, the naming of the different account types can be confusing.
DeepL has two main account types: DeepL Pro (for our other platforms) and DeepL API (for our API). DeepL API accounts are further differentiated into two sub-types DeepL API Free and DeepL API Pro (this might lead to the confusion).
I figured out the original issue creator had a DeepL Pro account, rather than a DeepL API account. DeepL API accounts (both Free and Pro) are supported by this client library, other types are not.

when i try to use the api i get this error {“message”:“Wrong endpoint. Use https://api.deepl.com/”}
even though i use the correct endpoint..

Hi @NaomiH0C, thanks for reporting your problem. Do you use an DeepL API Free or DeepL API Pro account?
You shouldn't need to specify the endpoint using server_url; the correct endpoint is selected automatically for API accounts.
If you recently upgraded from Free to Pro, you could try regenerating your API key and trying with the new key.

Hi @MystiqueMo, this is a fair question to ask, the naming of the different account types can be confusing.
DeepL has two main account types: DeepL Pro (for our other platforms) and DeepL API (for our API). DeepL API accounts are further differentiated into two sub-types DeepL API Free and DeepL API Pro (this last one might lead to confusion).
I figured out the original issue creator had a DeepL Pro account, rather than a DeepL API account. DeepL API accounts (both Free and Pro) include an authentication key for the API, and are supported by this client library, other account types are not.

Okay, understood.
Thanks for clarifying @daniel-jones-deepl.

When I use v2 then I get the error like {“message”:“Wrong endpoint. Use [https://api.deepl.com/”}] even though I used correct endpoint

I'll resume for those who will have this issue in the future. (It was not that easy for me to figure out the issue based on this thread).
There are different plan types, if you select the wrong one your key will not work with API giving this strange error


avocode: init at 2.26.0

Motivation for this change
Add avocode package
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@FRidh Thanks for feedback. Updated the PR.


Fixed typescript settings.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@6515d2d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #4   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         1
  Lines           ?        83
  Branches        ?         0
========================================
  Hits            ?        83
  Misses          ?         0
  Partials        ?         0

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@6515d2d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #4   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         1
  Lines           ?        83
  Branches        ?         0
========================================
  Hits            ?        83
  Misses          ?         0
  Partials        ?         0

Continue to review full report at Codecov.

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


publish and subscribe stream from c++ application

Is it possible to use erizo api to join a room, publish and subscribe stream on a c++ application that make use of camera and microphone? There is any example?
Thanks, licode is very powerful!

@falcox Did you were able to make it work?


ErdCode decoding ValueError

When using this with a brand new Haier fridge (Model HRF680YPAA) I kept getting this error:
ValueError("invalid literal for int() with base 10: '0A'

I added some additional error checking in gehomesdk/erd/erd_encoder.py and got this:
2023-01-07 11:52:05,767 DEBUG    Setting ErdCode.APPLIANCE_TYPE to ErdApplianceType.FRIDGE
2023-01-07 11:52:05,767 DEBUG    Setting ErdCode.SABBATH_MODE to False
2023-01-07 11:52:05,767 ERROR    Got ValueError ErdCode.WIFI_MODULE_UPDATING - 0A
2023-01-07 11:52:05,767 DEBUG    Setting ErdCode.WIFI_MODULE_UPDATING to b'\n'
2023-01-07 11:52:05,767 ERROR    Got ValueError ErdCode.WIFI_MODULE_UPDATING - 0A
2023-01-07 11:52:05,767 DEBUG    Setting ErdCode.WIFI_MODULE_SW_VERSION to <IP_ADDRESS>
2023-01-07 11:52:05,767 DEBUG    Setting ErdCode.WIFI_MODULE_SW_VERSION_AVAILABLE to <IP_ADDRESS>

No clue why it's set to 0A.
My little patch adds a except for ValueError.
        try:
            return self._registry[erd_code].erd_decode(erd_value)
        except KeyError:
            return erd_decode_bytes(erd_value)
        except ValueError:
            _LOGGER.error(f'Got ValueError {erd_code} - {erd_value}')
            return erd_decode_bytes(erd_value)

Currently if that error is hit then the entire thing aborts, with that except it will continue running at least which seems like a good idea. Not sure if erd_decode_bytes is the correct thing but it seems to work.

I think that they're changing some meaning of some of the codes between the brands... this one should just be a bool (0 or 1), but clearly isn't.  I've added your patch for now, but we may need to make some other updates.


Handle dynamically embedding the initrd as part of a build

Feature request summary
This issue tracks the integration of embedding the CPIO archive as part of the unikernel following the introduction of https://github.com/unikraft/unikraft/pull/1070, KraftKit should handle this serialization dynamically by setting the appropriate KConfig option as well as part of the dynamic serialization of the file itself.
Describe alternatives
No response
Related architectures
None
Related platforms
None
Additional context
No response

The PR in the core is about to be merged, we can start looking into this

Done.


⚠ Bofrost.de has degraded performance

In 769e099, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1721 ms

Resolved: Bofrost.de performance has improved in 9e2b884 after 7 minutes.


Missing return statement not released yet

Hey everyone,
PR #46 has still not been released and unfortunately our customers are still waiting for a fix. When can we expect this fix to be released?
@fjbender
@m-siddi

We'll release today, tomorrow the latest.

It's done: https://github.com/PAYONE-GmbH/oxid-6/releases/tag/1.0.9
Thanks for your patience and support!


add --fix for scss/operator-no-unspaced

If I remember correctly, that rule was one that is difficult to add autofix for without messing up the user's operators.

For me it seems that is will be fixed, but incorrectly.
When I run stylelint --fix, then something like $breakpoint = 600px-1px will be fixed to $breakpoint = 600px -1px, which later breaks a media query string that expects one value not two values.
Btw. I tested that with:
"extends": ["stylelint-config-standard-scss"],
"plugins": ["stylelint-scss"],

@RiZKiT that fixing is probably coming from some other rule. operator-no-unspaced does not have a --fix implemented.


Finding Neighboring Webelements - Reconcile 'Div' and 'Pagebreak' webelement parsing schemes

Two approaches:

split up the document by page breaker tag. Grouping all the text on the same page and using it as the neighboring text.
use the text in the parent div container for the label as the neighboring text

Solution:

use the parse_text_by_page(self)
still in process

Run visual tests with red border bounding boxes on detected elements, present to team

There is an option here:
We could just find all horizontal line breaks (hr) and their y position. Then, we can just subtract y positions to find page numbers of webelement. We can also find neighbors by looking at y distance, or xy euclidean distance.


Updating to 2.0.4

Updated to use the current standard distribution. It all works as far as I can tell.

Putting the vendors inside the repo is bad practice (and make the repo very huge). You should either use submodules either ignore the vendor folder when using the deps file.

I was just keeping it as it had originally been imported but I am quite happy to make this change at this point.

thanks for your contribution, very much appreciated Richard.
@stof: For now, this is how it's set up. We might (or might not) move away from this approach at a later stage


feat(GUI): rich image extensions

The following PRs add support for a custom _info directory containing
metadata such an image URL, display name, logo, etc in
etcher-image-stream:

https://github.com/resin-io-modules/etcher-image-stream/pull/16
https://github.com/resin-io-modules/etcher-image-stream/pull/14
https://github.com/resin-io-modules/etcher-image-stream/pull/13

Now that this module supports such metadata, we make use of it in the
GUI as follows:

The file name is replaced with the display name.
The file name links to the image URL.
The "Select Image" logo is replaced with the image logo.

Some miscellaneous changes introduces in this PR to support the changes
described above:

Implement SelectionStateModel.getImageUrl().
Implement SelectionStateModel.getImageLogo().
Implement SelectionStateModel.getImageName().
Ignore the "logo" image property when displaying the "Select image"
event, in order to not fill the console with SVG contents.
Make svg-icon understand SVG strings as paths.
Make svg-icon react to changes to the path attribute.
Extract the core functionality of openExternal into
OSOpenExternalService.
Upgrade etcher-image-stream to v3.0.1.

Change-Type: minor
Changelog-Entry: Support rich image extensions.
Fixes: https://github.com/resin-io/etcher/issues/470
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

In the screenshot example above, I'm using a dummy Raspberry Pi SVG icon I found on Google.


Options created with option group not clickable in mobile

Im a building phonegap app with react where I am using this excellent library. The problem I face is although the options click works for options rendered without opt group on mobile it does not work for options rendered with opt group on mobile. Seems to work on desktop for both. I tried adding the following code
this.props.onSelect(this.props.option, event); on handleMouseDown function but this does not solve the issue.

Any headups on this issue

I haven't had a chance to look into this yet. Let me know if you're able to figure out the root cause of the problem on your end.

Closed by #43. I haven't seen any other issues with React Select Plus on mobile devices. Please reopen if you can provide steps to replicate.


Remove HomogeneousViewport

The virtual viewport machinery now handles all of these use cases.
Previous clients of ScrollableWidgetList can use ScrollableLazyList
instead.

@Hixie

Travis is mad. Something about mixins.
I can't claim to truly understand the list aspects of this. There's a lot of classes. I think we need some high level documentation with a class hierarchy diagram. It should probably lean on some other documentation explaining the purpose of custom Element subclasses.
But that said, LGTM.

Travis is mad. Something about mixins.

Yeah, mixins and constructors don't like each other.

This seems like a space that's ripe for rather narrow unit tests, by the way.

I think we need some high level documentation with a class hierarchy diagram. It should probably lean on some other documentation explaining the purpose of custom Element subclasses.

I'd like to add that documentation in a followup patch.  My secret hope is that writing the documentation will uncover a clearer way to structure this code.

This seems like a space that's ripe for rather narrow unit tests, by the way.

Yes, the tests from homogeneous viewport were quite helpful.  I'm a little wary of testing against the lower-level classes because I'm not 100% happy with how they're structured today, but I think it would make sense to test then through the ScrollableList / ScrollableLazyList / ScrollableGrid / PageableList interfaces.

Oh yeah, I wasn't saying the docs should be with this patch. I even filed a bug for you to track this. :-)

Ok, I'm going to land this and continue iterating.


FIX: Bump min testing version to 4.5 to match composer requirement

This is necessary due to the updated GraphQL requirement

OK @unclecheese bit of a yak shave here – i wanted to merge @chillu's PR but noticed the test was failing. Turns out they had never really been set up. But good news, the tests are set up and passing now.

Nice one. Looks good


Enable the Annotation

How can I enable Annotation feature.
This issue is a Question

There is an ongoing initiative with hypothesis.js (see this post). A PR will soon be pushed by Evident Point on the Readium repo.

In the interim, you can enable the "text highlighting" functionality (not a fully fledged annotation feature, but you can implement a more complete system based on this building block), by activating the plugin in readium-shared-js: https://github.com/readium/readium-shared-js/blob/develop/plugins/plugins.cson
Example usage:
https://github.com/readium/readium-js-viewer/blob/develop/src/js/EpubReader.js#L1167
                    readium.reader.plugins.highlights.initialize({
                        annotationCSSUrl: readerOptions.annotationCSSUrl
                    });

                    readium.reader.plugins.highlights.on("annotationClicked", function(type, idref, cfi, id) {
        console.debug("ANNOTATION CLICK: " + id);
                        readium.reader.plugins.highlights.removeHighlight(id);
                    });

https://github.com/readium/readium-js-viewer/blob/develop/src/js/EpubReader.js#L851
        $(".icon-annotations").on("click", function () {
            readium.reader.plugins.highlights.addSelectionHighlight(Math.floor((Math.random()*1000000)), "test-highlight");
        });

@llemeurfr Hi, I have read the post you mentioned, looks like an exciting feature. The post says the annotation will be launched in summer 2007. Summer is passing half the way. When will it be ready to use? Thanks.

@danielweck Can you tell me how is going with the hypothesis.js project? Thanks.

Hi @hz0324, please follow readium/readium-shared-js#396 to get updates on this project.

hypothesis is working, but the highlight does not work, I already enabled it in the cson package, what to do to work?

@DougsAraujo see https://github.com/readium/readium-shared-js/issues/448#issuecomment-385627644


A port range is no longer allowed as a value at the "ports" parameter of the frontend resource

Describe the Bug
Prior to the conversion of ERB to EPP templates in commit a32adb51 it was possible to add a port range to the "ports" parameter of the frontend resource. The reason this worked was that the rube to_i method ignores non integer endings (documentation: https://apidock.com/ruby/String/to_i)
Expected Behavior
As port ranges are valid in haproxy and worked in the past, the puppet ports parameter should support them again.
Steps to Reproduce
Steps to reproduce the behavior:
haproxy::frontend { 'test':
  ipaddress => '<IP_ADDRESS>',
  ports => '10000-10250',
}

I can confirm this issue.


Remove last remains of cross referencing

In my latest pull request I've removed cross referencing by arrows and started to use links instead. However, I ended up missing one (thanks to @MikeMcC399 for telling me). This pull request will remove the last remains of cross referencing arrows. See the images below
Right now:

After merging this pull request:

@larswmh @MikeMcC399 @mohe2015 Thanks everybody.


Remove year in per-file copyright statement

Remove the requirement for indicating a year in the copyright date.
For a much longer discussion, see:
https://github.com/coreinfrastructure/best-practices-badge/pull/1439
This was originally proposed by John Mertic ( @jmertic ) on discussion
with @swinslow and many others. This is basically a minor
relaxation of a gold badge requirement. It was proposed nearly a month
ago, and while there's been sporatic discussion to word it "just right"
there have been no objections to the change.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

Awesome - thank you @david-a-wheeler and also @swinslow for additional legal feedback.

Thanks @david-a-wheeler! The changes to the copyright language look good to me.
One question though, it looks like there was a change to doc/criteria.md re: hash algorithms that was also included in this commit. I'm guessing this was unintentional? It doesn't matter to me either way but I did want to flag it.

@swinslow - don't worry about that. I accidentally forgot to regenerate a file from another change. This process caused its regeneration. So we're all good.
In the long-term, I'm thinking about making some changes so that this regeneration doesn't need to happen. That will avoid that kind of accident.

Technically I should split them into two different commits, but they're going to be merged anyway so it just isn't worth it.

Everyone: Thank you VERY MUCH for commenting. Merged.


[AppConfig] Support import/export of keyvault ref from appservice

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

add to S164.

Add release note in history.rst


[Device Support Request] Aqara B1 Curtain Motor

Problem description
B1 does not follow the standards and needs a quirk. It seems like a similar issue to the Aqara E1 roller, which already has a quirk.
The current behavior is that the device pairs correctly and exposes three entities: identify, number and cover. Identify makes the device beep (works), number represents and sets the current position of the curtains (works, but the naming is off) and cover fails to work as expected. The current state of the cover is not correctly mapped to the UI.
Cover's up and down commands do nothing and stop command stops the curtains correctly if they are moving, but gives an error in the UI: "Failed to call service cover/stop_cover. '>' not supported between instances of 'NoneType' and 'int'"
is
Solution description
zigbee-herdsman-converters has support that could be used as a reference. Original commit: https://github.com/Koenkk/zigbee-herdsman-converters/commit/75a7d6640ab5276beddecd04bd1f356757cb7b8a
The essence is that the B1 exposes its current lift percentage via current_value in the analog_output cluster. It also seems that this value is inverted when compared to the standard? This seems similar to the E1 quirk.
In addition, the device does not support dedicated commands for opening or closing but instead needs those commands mapped to set the current_value to 0 or 100.
Screenshots/Video
No response
Device signature
Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|MainsPowered: 132>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=True, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0202",
      "input_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x000d",
        "0x0013",
        "0x0102"
      ],
      "output_clusters": [
        "0x0003",
        "0x000a"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.curtain.hagl04",
  "class": "zigpy.device.Device"
}

Diagnostic information
Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.5.3",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.11",
    "docker": true,
    "arch": "armv7l",
    "timezone": "Europe/Helsinki",
    "os_name": "Linux",
    "os_version": "6.1.21-v7",
    "supervisor": "2023.07.1",
    "host_os": "Home Assistant OS 10.1",
    "docker_version": "23.0.3",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {},
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "after_dependencies": [
      "onboarding",
      "usb"
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly"
    ],
    "config_flow": true,
    "dependencies": [
      "file_upload"
    ],
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "requirements": [
      "bellows==0.35.5",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.99",
      "zigpy-deconz==0.21.0",
      "zigpy==0.55.0",
      "zigpy-xbee==0.18.0",
      "zigpy-zigate==0.11.0",
      "zigpy-znp==0.11.1"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      },
      {
        "type": "_slzb-06._tcp.local.",
        "name": "slzb-06*"
      }
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 13125,
    "manufacturer": "LUMI",
    "model": "lumi.curtain.hagl04",
    "name": "LUMI lumi.curtain.hagl04",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "manufacturer_code": 4447,
    "power_source": "Mains",
    "lqi": 185,
    "rssi": null,
    "last_seen": "2023-07-16T22:45:33",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|MainsPowered: 132>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=True, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0202",
          "input_clusters": [
            "0x0000",
            "0x0001",
            "0x0003",
            "0x000d",
            "0x0013",
            "0x0102"
          ],
          "output_clusters": [
            "0x0003",
            "0x000a"
          ]
        }
      },
      "manufacturer": "LUMI",
      "model": "lumi.curtain.hagl04"
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "button.lumi_lumi_curtain_hagl04_identify",
        "name": "LUMI lumi.curtain.hagl04"
      },
      {
        "entity_id": "number.lumi_lumi_curtain_hagl04_number",
        "name": "LUMI lumi.curtain.hagl04"
      },
      {
        "entity_id": "cover.lumi_lumi_curtain_hagl04_cover",
        "name": "LUMI lumi.curtain.hagl04"
      }
    ],
    "neighbors": [],
    "routes": [],
    "endpoint_names": [
      {
        "name": "WINDOW_COVERING_DEVICE"
      }
    ],
    "user_given_name": "Terrace Curtains",
    "device_reg_id": "e9701851edfd1be1ed458637bbff8d03",
    "area_id": "terrace",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "WINDOW_COVERING_DEVICE",
          "id": 514
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "LUMI"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "lumi.curtain.hagl04"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0102": {
            "endpoint_attribute": "window_covering",
            "attributes": {
              "0x0000": {
                "attribute_name": "window_covering_type",
                "value": 4
              },
              "0x0007": {
                "attribute_name": "config_status",
                "value": 0
              },
              "0x0017": {
                "attribute_name": "window_covering_mode",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x0003": {
                "attribute_name": "current_position_lift"
              },
              "0x0004": {
                "attribute_name": "current_position_tilt"
              },
              "0x0008": {
                "attribute_name": "current_position_lift_percentage"
              }
            }
          },
          "0x000d": {
            "endpoint_attribute": "analog_output",
            "attributes": {
              "0x0041": {
                "attribute_name": "max_present_value",
                "value": 100.0
              },
              "0x0055": {
                "attribute_name": "present_value",
                "value": 1.0
              }
            },
            "unsupported_attributes": {
              "0x0100": {
                "attribute_name": "application_type"
              },
              "0x0045": {
                "attribute_name": "min_present_value"
              },
              "0x0068": {
                "attribute_name": "relinquish_default"
              },
              "0x006a": {
                "attribute_name": "resolution"
              },
              "0xfffe": {
                "attribute_name": "attr_reporting_status"
              },
              "0x001c": {
                "attribute_name": "description"
              },
              "0x0075": {
                "attribute_name": "engineering_units"
              }
            }
          },
          "0x0013": {
            "endpoint_attribute": "multistate_output",
            "attributes": {
              "0x0055": {
                "attribute_name": "present_value",
                "value": 0.0
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage",
                "value": 0
              },
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 101
              }
            },
            "unsupported_attributes": {
              "0x0031": {
                "attribute_name": "battery_size"
              },
              "0x0033": {
                "attribute_name": "battery_quantity"
              }
            }
          }
        },
        "out_clusters": {
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x000a": {
            "endpoint_attribute": "time",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

Logs
No response
Custom quirk
No response
Additional information
I tried looking into developing a quirk myself but didn't get anywhere as this is really unfamiliar territory. Maybe someone else would have the kind motivation to use the above info to add support?

I just thought I'd let you know that I have a slightly different version of this. It's the powered version model ZNCLDJ11LM which appears to have a different signature to yours but has similar issues.
I've got an issue #2451 created and have started to look into creating a custom quirk when I can spare some time.

@MrHaila Hey!
Did you solve this issue by any chance? I'm also trying to integrate Aqara B1 battery curtain motor without luck for few days.

Unfortunately not. I've had the battery of the device die on me so figuring out this bit has been on hold 😭

@MrHaila I was able to figure it out a bit, based on work from @hastarin.
The only downside is I'm not able to expose battery level to HA for some reason. I'll try to expose PR in some free time but for now you can try my custom quirk if you like.
`"""Aqara Curtain Driver B1 device."""
from future import annotations
from typing import Any
import logging
from zigpy import types as t
from zigpy.profiles import zha
from zigpy.zcl import foundation
from zigpy.zcl.clusters.closures import WindowCovering
from zigpy.zcl.clusters.general import (
AnalogOutput,
Basic,
Groups,
Identify,
MultistateOutput,
PowerConfiguration,
Scenes,
Time,
)
from zhaquirks import CustomCluster
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.xiaomi import LUMI, XiaomiCustomDevice, XiaomiPowerConfigurationPercent, BasicCluster
_LOGGER = logging.getLogger(name)
class AnalogOutputB1(CustomCluster, AnalogOutput):
"""Analog output cluster, used to relay current_value to WindowCovering."""
def __init__(self, *args: Any, **kwargs: Any) -> None:
    """Init."""
    _LOGGER.debug("AnalogOutputB1 Cluster init")
    super().__init__(*args, **kwargs)
    self._update_attribute(
        self.attributes_by_name["max_present_value"].id, 100.0
    )  # max_present_value
    self._update_attribute(
        self.attributes_by_name["min_present_value"].id, 0.0
    )  # min_present_value

def _update_attribute(self, attrid: int, value: Any) -> None:
    _LOGGER.debug("AnalogOutput update attribute %04x to %s... ", attrid, value)
    super()._update_attribute(attrid, value)
    if attrid == self.attributes_by_name["present_value"].id:
        self.endpoint.window_covering._update_attribute(  # pylint: disable=protected-access
            WindowCovering.attributes_by_name[
                "current_position_lift_percentage"
            ].id,
            (100 - value),
        )

class WindowCoveringB1(CustomCluster, WindowCovering):
"""Window covering cluster, used to cause commands to update the AnalogOutput present_value."""
stop_called = bool(False)

def __init__(self, *args: Any, **kwargs: Any) -> None:
    """Init."""
    _LOGGER.debug("WindowCoveringB1 Cluster init")
    super().__init__(*args, **kwargs)

def _update_attribute(self, attrid: int, value: Any) -> None:
    _LOGGER.debug(
        "WindowCovering update attribute %04x to %s and stop_called is %s",
        attrid,
        value,
        self.stop_called,
    )
    if self.stop_called:
        _LOGGER.debug("Recently stopped, updating AnalogOutput value")
        self.stop_called = bool(False)
        self.endpoint.analog_output._update_attribute(  # pylint: disable=protected-access
            AnalogOutput.attributes_by_name["present_value"].id, value
        )
    super()._update_attribute(attrid, value)

async def command(
        self,
        command_id: foundation.GeneralCommand | int | t.uint8_t,
        *args: Any,
        manufacturer: int | t.uint16_t | None = None,
        expect_reply: bool = True,
        tsn: int | t.uint8_t | None = None,
        **kwargs: Any,
) -> Any:
    """Overwrite the commands.

    Overwrite analog_output's current_value
    value to make the curtain work as expected.
    """
    _LOGGER.debug("WindowCovering command %04x", command_id)
    if command_id == self.commands_by_name["up_open"].id:
        (res,) = await self.endpoint.analog_output.write_attributes(
            {"present_value": 100}
        )
        return foundation.GENERAL_COMMANDS[
    foundation.GeneralCommand.Default_Response
    ].schema(command_id=command_id, status=res[0].status)
    if command_id == self.commands_by_name["down_close"].id:
        (res,) = await self.endpoint.analog_output.write_attributes(
            {"present_value": 0}
        )
        return foundation.GENERAL_COMMANDS[
    foundation.GeneralCommand.Default_Response
    ].schema(command_id=command_id, status=res[0].status)
    if command_id == self.commands_by_name["go_to_lift_percentage"].id:
        _LOGGER.debug("go_to_lift_percentage %d", args[0])
        (res,) = await self.endpoint.analog_output.write_attributes(
            {"present_value": (100 - args[0])}
        )
        return foundation.GENERAL_COMMANDS[
    foundation.GeneralCommand.Default_Response
    ].schema(command_id=command_id, status=res[0].status)
    if command_id == self.commands_by_name["stop"].id:
        self.stop_called = bool(True)
        return await super().command(
    command_id,
    *args,
    manufacturer=manufacturer,
    expect_reply=expect_reply,
    tsn=tsn,
    **kwargs,
    )

class CurtainB1(XiaomiCustomDevice):
"""Aqara Curtain Driver B1 device."""
def __init__(self, *args: Any, **kwargs: Any) -> None:
    """Init."""
    super().__init__(*args, **kwargs)  # type: ignore
    _LOGGER.info("CurtainB1 custom quirk loaded")

signature = {
    MODELS_INFO: [(LUMI, "lumi.curtain.hagl04")],
    ENDPOINTS: {
        # <SizePrefixedSimpleDescriptor endpoint=1 profile=260 device_type=514
        # device_version=1
        # input_clusters=["0x0000","0x0001","0x0003","0x000d","0x0013","0x0102"]
        # output_clusters=["0x0003","0x000a"]>
        1: {
            PROFILE_ID: zha.PROFILE_ID,
            DEVICE_TYPE: zha.DeviceType.WINDOW_COVERING_DEVICE,
            INPUT_CLUSTERS: [
                AnalogOutput.cluster_id,
                Basic.cluster_id,
                Identify.cluster_id,
                MultistateOutput.cluster_id,
                PowerConfiguration.cluster_id,
                WindowCovering.cluster_id
            ],
            OUTPUT_CLUSTERS: [
                Identify.cluster_id,
                Time.cluster_id
            ],
        },
    },
}
replacement = {
    ENDPOINTS: {
        1: {
            PROFILE_ID: zha.PROFILE_ID,
            DEVICE_TYPE: zha.DeviceType.WINDOW_COVERING_DEVICE,
            INPUT_CLUSTERS: [
                AnalogOutputB1,
                BasicCluster,
                Identify.cluster_id,
                MultistateOutput.cluster_id,
                XiaomiPowerConfigurationPercent,
                WindowCoveringB1,
            ],
            OUTPUT_CLUSTERS: [
                Identify.cluster_id,
                Time.cluster_id
            ],
        },
    },
}`

Is this now all working with current quick? Is it working for open close stop and position as a cover and have battery shown? Thanks.

I've got HA with ZBT-1 stick and ZHA configured. My Aqara b1 is not working with this config. Device been successfully interviewed, but nothing else working


Export vulkan instance process address function.

Hi. I am the creator of iree.gd, a project that brings IREE, another project that makes running AI models natively possible, into Godot through the GDExtension. The runtime uses vulkan to accelerate execution of AI model. In order to use the vulkan device that is running in Godot, Godot's vkGetInstanceProcAddr is required. If we are going to create another vulkan device on our own, it is very likely to produce crash.
This is not a very big change, just exporting vkGetInstanceProcAddr so it is accessible in GDExtension.

You need to add documentation, see the tests

I have done adding documentation...

Poke @clayjohn.

I don't think this needs to be exposed to do what you want to do. vkGetInstanceProcAddr is not a driver resource. It is a driver-defined function that is dynamically loaded by the Volk library. You can get the exact same function through whatever Vulkan loading utility you are using in your extension (or by using dlopen/dlsym/GetProcAddress yourself).
You already have access to the device and the instance in case you want to share those with Godot. vkGetInstanceProcAddr just allows you short circuit the loader that Godot uses and avoid using a loader yourself
To me, exposing this seems like a hacky workaround that is only really usable from C++ (as I doubt the C++ function pointer is functional when accessing from other languages)


feat: support guided decoding for vllm async engine

Support Guided Decoding for vllm async engine
waiting for vllm release, a version bump is needed.
https://github.com/xorbitsai/inference/issues/1562
https://github.com/vllm-project/vllm/pull/8252

Which version is required?

Which version is required?

latest version after 0.6.2

vllm has release v0.6.3, is this PR ready to work?

I will do the test.

寄件者: Xuye Qin @.>
寄件日期: 星期四, 10月 17, 2024 5:38:13 下午
收件者: xorbitsai/inference @.>
副本: wxiwnd @.>; Author @.>
主旨: Re: [xorbitsai/inference] feat: support guided decoding for vllm async engine (PR #2391)
vllm has release v0.6.3, is this PR ready to work?
—
Reply to this email directly, view it on GitHubhttps://github.com/xorbitsai/inference/pull/2391#issuecomment-2419047361, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJSDNXWKTHLIQE35VTQLT23Z36AQDAVCNFSM6AAAAABPJCVJQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJZGA2DOMZWGE.
You are receiving this because you authored the thread.Message ID: @.***>

vllm has release v0.6.3, is this PR ready to work?

Works on my machine now
Also This PR implemented response_format call, like:
curl --location --request POST 'http://ip:9997/v1/chat/completions' \
--header 'User-Agent: Apifox/1.0.0 (https://apifox.com)' \
--header 'Content-Type: application/json' \
--data '{
    "model": "qwen1.5-32b-chat-int4",
    "messages": [
        {
            "role": "user",
            "content": "“give me a recipe in json format"
        }
    ],
    "temperature": 0,
    "max_tokens": 1000,
    "stream": true,
    "response_format": {"type": "json_object"}
}'

vllm has release v0.6.3, is this PR ready to work?

Works on my machine now Also This PR implemented response_format call, like:
curl --location --request POST 'http://ip:9997/v1/chat/completions' \
--header 'User-Agent: Apifox/1.0.0 (https://apifox.com)' \
--header 'Content-Type: application/json' \
--data '{
    "model": "qwen1.5-32b-chat-int4",
    "messages": [
        {
            "role": "user",
            "content": "“give me a recipe in json format"
        }
    ],
    "temperature": 0,
    "max_tokens": 1000,
    "stream": true,
    "response_format": {"type": "json_object"}
}'

Can you confirm there is no exception if the bill
Is an old version?

vllm has release v0.6.3, is this PR ready to work?

Works on my machine now Also This PR implemented response_format call, like:
curl --location --request POST 'http://ip:9997/v1/chat/completions' \
--header 'User-Agent: Apifox/1.0.0 (https://apifox.com)' \
--header 'Content-Type: application/json' \
--data '{
    "model": "qwen1.5-32b-chat-int4",
    "messages": [
        {
            "role": "user",
            "content": "“give me a recipe in json format"
        }
    ],
    "temperature": 0,
    "max_tokens": 1000,
    "stream": true,
    "response_format": {"type": "json_object"}
}'

Can you confirm there is no exception if the vllm is an old version?

It now works properly even if vllm version < 0.63

This feature has been tested on my machine and appears to be functioning properly.

This feature has been tested on my machine and appears to be functioning properly. @qinxuye

Thanks, hope we can merge this before tomorrow before new version released.

Thanks, I think we can port the ability of guide decoding for other engines later.

Thanks, I think we can port the ability of guide decoding for other engines later.

That's OK, we can use outlines directly for other engines.


Release schedule for updating packages

Sooner or later it may come up that a module or two will get updated and therefore someone may request an update to have new packages released.
If we look at the following schedule for 3.8: https://www.python.org/dev/peps/pep-0569/#schedule
3.8.0 final: Monday, 2019-10-14
3.8.1: Wednesday, 2019-12-18
3.8.2: Monday, 2020-02-24
3.8.3: Wednesday, 2020-05-13
3.8.4: Monday, 2020-07-13 (expected)
That seems to be every 2-3 months.
For reference on 3.7: https://www.python.org/dev/peps/pep-0537/#release-schedule
3.7.0 final: 2018-06-27
3.7.1 final: 2018-10-20
3.7.2 final: 2018-12-24
3.7.3 final: 2019-03-25
3.7.4 final: 2019-07-08
3.7.5 final: 2019-10-15
3.7.6 final: 2019-12-18
3.7.7 final: 2020-03-10
About every ~3 months.
I'm proposing that this project follow the release schedule for the latest Python version + 2 weeks to generate new packages. The hope is that this would allow any potential issues to ideally get resolved if anything unexpected comes up that didn't already come up during the Python release candidate testing.

@bp88 do you plan on contributing in a meaningful way to making this a possibility? There would need to be a lot of automation created, and this doesn't address the other elephant in the room: 3rd party library updates.
Apple has not updated Python except for small yearly changes.
I will be honest. I do not plan on accepting that role and responsibility for the macadmin community. If someone wants to take up that mantle and also shine the bat signal when needed, great.
If people deem that they want this schedule but no one wants to help, perhaps archiving this project would be a more sane solution.

Maybe the build job can be setup with a schedule? Do a new build every N days? Change logs won't be happening, but I don't see a good way to do this otherwise.

You could use dependabot for the packages https://help.github.com/en/github/administering-a-repository/keeping-your-dependencies-updated-automatically

There is also https://pyup.io/ which is free for open source projects.

Maybe the build job can be setup with a schedule? Do a new build every N days? Change logs won't be happening, but I don't see a good way to do this otherwise.

After experimenting with GitHub actions over the past few hours this is indeed possible, however since the build scripts take environmental variables, we will likely need to initially create a new build.yaml file for each version of python. I think this will be pretty easy to do and I will likely test my theory soon.

https://github.com/macadmins/python/commit/35332aaae44bc11eb7645b2dd9451092aa2ffa12
It worked. Now building Python 3.8.2 and Python 3.8.3 releases

I am going to close this ticket, but it will now be trivial to support this and anyone can send a PR to build whatever version you want to build once it's publicly available.
This doesn't address the libraries themselves being updated, but that will be tracked at https://github.com/macadmins/python/issues/12


Linebreaks in qrcode

It is more a feature request.
I initially wanted to use your plug-in for generating my qrcode vcard (at the moment I use a command line tool to generate a png).
[qrcode]
BEGIN:VCARD
VERSION:4.0
N:Mustermann;Erika;;Dr.;
FN:Dr. Erika Mustermann
ORG:Wikimedia
ROLE:Kommunikation
TITLE:Redaktion & Gestaltung
PHOTO;MEDIATYPE=image/jpeg:http://commons.wikimedia.org/wiki/File:Erika_Mustermann_2010.jpg
TEL;TYPE=work,voice;VALUE=uri:tel:+49-221-9999123
TEL;TYPE=home,voice;VALUE=uri:tel:+49-221-1234567
ADR;TYPE=home;LABEL="Heidestraße 17\n51147 Köln\nDeutschland"
 :;;Heidestraße 17;Köln;;51147;Germany
<EMAIL_ADDRESS>REV:20140301T221110Z
END:VCARD
[/qrcode]

Unfortunately it seems that line breaks are not supported (yet). Or maybe I am missing something.

Hi @eisenherzz , line breaks are now supported in Version 1.1.0. Thank you, for your request.

Hi @cworreschk,
great work. I am now able to render my vCard with your plugin. Many
thanks and keep up the good work.


Typo internal fun

In 4 "Make your first WorkRequest" at step 5, the snipped code has a typo and should be internal fun applyBlur(blurLevel: Int) ...  instead of Internal fun applyBlur(blurLevel: Int)  (capital "I" letter is wrong)

Thanks for reporting! This is now fixed


Fix Product Mix queries using group by

Description
There were a couple of Internal server errors when opening the Products mix on the UI related to group by parameters

Product Mix list view

Product Mix detail view

Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

Tests please.

Done!


feat(cache): allow export & import

In SSR, you usually want to do the same query on the server as on the client, however the query on the client is redundant, since the results are serialized.
The JS client needs elaborate workarounds right now (including aliasing the "search" method, like in react-instantsearch) to be able to initialize the memory cache with already done queries.
Another use case is for "prefilling" the cache for e.g. empty or really popular queries.

For now this isn’t the right approach


Gradio demo not returning correct output

Hi, thanks for making the Gradio demo here https://huggingface.co/spaces/52Hz/SRMNet_thesis, I noticed it does not return the correct output at times, getting image from another user?
I think a queue and cache could be enabled also by doing
enable_queue=True
cache_examples=True in launch

Thank you for reporting the bug and presenting the solution of this problem!! 🥰
However, I prefer to demo the results without cache,
because it may let users think the restored images are another existing images.😐
I think I have fixed the mentioned bug by deleting the folder of input testing image after generating the restored image,
which is referred from the code of yours (same avatar in HuggingFace😏).
I really appreciate you publish the  awesome spaces in HuggingFace which helps me a lot to upload my models to the platform!
Thank you very much~


zju_06

We offer a new style model compatible with MajicmixRealistic_v6：日系和服风(Kimono Style)
Portraits used to train the model:

The outcome:

can you try to do more experiments to find a better weights of style to enhance the fedelity of the cloth. try to enhance this 'multiplier_style': 0.2.

Through experiments, we enhance the multiplier-style to 0.45 and add prompts '(linen:1.4)' to enhance the fidelity of the cloth
the results:

try to compress this image

We have compressed the style image.


cmd/compile: failure to optimize away temporary variable

I'd expect these functions to compile identically:

func f() int {
	a := 2
	return a
}

func g() int {
	return 2
}

They do not (6g):

"".f t=1 size=32 value=0 args=0x8 locals=0x8
  0x0000 00000 (d.go:3) TEXT "".f+0(SB),4,$8-8
  0x0000 00000 (d.go:3) SUBQ $8,SP
  0x0004 00004 (d.go:3) FUNCDATA $2,gclocals·a7a3692b8e27e823add69ec4239ba55f+0(SB)
  0x0004 00004 (d.go:3) FUNCDATA $3,gclocals·3280bececceccd33cb74587feedb1f9f+0(SB)
  0x0004 00004 (d.go:4) MOVQ $2,AX
  0x000b 00011 (d.go:5) MOVQ AX,"".~r0+16(FP)
  0x0010 00016 (d.go:5) ADDQ $8,SP
  0x0014 00020 (d.go:5) RET ,

"".g t=1 size=16 value=0 args=0x8 locals=0x0
  0x0000 00000 (d.go:8) TEXT "".g+0(SB),4,$0-8
  0x0000 00000 (d.go:8) NOP ,
  0x0000 00000 (d.go:8) NOP ,
  0x0000 00000 (d.go:8) FUNCDATA $2,gclocals·a7a3692b8e27e823add69ec4239ba55f+0(SB)
  0x0000 00000 (d.go:8) FUNCDATA $3,gclocals·3280bececceccd33cb74587feedb1f9f+0(SB)
  0x0000 00000 (d.go:9) MOVQ $2,"".~r0+8(FP)
  0x0009 00009 (d.go:9) RET ,

There are two inefficiencies in f: A useless stack variable and two MOVQs where one
suffices.

CL 126160043 will address the useless stack variable. The MOVQs should presumably be
handled with a peephole optimization that copies the constant when it has only one
subsequent use.

Doesn't reproduce with revision b9feb91

Yes, SSA fixes this.  Closing.


aspect ratio not right on android.

I could be doing something wrong but the aspect ratio is being stretched on Android. I have FillMode="ResizeAspect" but regardless of the FillMode setting the video is still stretched.?

Duplicate of #3


Send error context chain to the client when Copy stream errors.

It e.g. turns
2023-03-20 19:46:25.279 GMT [1043428] WARNING:  Failed to read from node localhost:15004 in active state: ERROR:  WAL acceptor

into
2023-03-20 19:46:25.279 GMT [1043428] WARNING:  Failed to read from node localhost:15004 in active state: ERROR:  WAL acceptor: invalid xlog page header: xlp_magic=0, expected 53517 at 0/2810000


[EASI-2236] FE work for Model Tab View and Table

EASI-2236
Changes and Description

Added a view for Models that is the component for /models to match figma

How to test this change

PR Author Review Checklist

[ ] Met the ticket's acceptance criteria, or will meet them in a subsequent PR.
[ ] Added or updated tests for backend resolvers or other functions as needed.
[ ] Added or updated client tests for new components, parent components, functions, or e2e tests as necessary.
[ ] Tested user-facing changes with voice-over and the rotor menu

PR Reviewer Guidelines

It's best to pull the branch locally and test it, rather than just looking at the code online!
Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.
Always make comments, even if it's minor, or if you don't understand why something was done.

@CMSgov/mint-backend just a fyi, @StevenWadeOddball  worked on the back-end code