React/Typescript/NextJs: Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check that this is really a bug

[X] I confirm

Reproduction link
no link unfortunately
Bug description
Hello team!
this is a code of my component for the Carousel (we use yarn, not npm):
import * as React from "react"
import {Swiper, SwiperSlide} from "swiper/react"
import {Navigation} from "swiper"
import "swiper/css"
import "swiper/css/navigation"

export type CarouselProps = {
  navigation ?: boolean
  spaceBetween ?: number
  slidesPerView ?: number
  data : string[]
}

export function Carousel(props : CarouselProps) : JSX.Element {
  const {
    navigation = true,
    spaceBetween = 50,
    slidesPerView = 3,
    data,
  } = props
  return <Swiper
    navigation={navigation}
    modules={[Navigation]}
    spaceBetween={spaceBetween}
    slidesPerView={slidesPerView}
  >
    {data.map((content : string, key : number) => <SwiperSlide key={key}><>{content}</></SwiperSlide>)}
  </Swiper>
}

this is an example how I call it in the page
import * as React from "react"
import {Link, Carousel} from "components"
import * as S from "styleguide"

const CarouselContent = [
  "
Slide 1
",
  "
Slide 2
",
  "
Slide 3
",
  "
Slide 4
",
]

export default function Layout() : JSX.Element {
  return <S.StyleguideLayout title="Simple Carousel">
    <S.Suite title="Basic">

Resources:

      <Link href="https://github.com/tjallingt/react-youtube">https://github.com/tjallingt/react-youtube</Link>
      <Link href="https://www.npmjs.com/package/@types/youtube">https://www.npmjs.com/package/@types/youtube</Link>
      <BasicCases/>
    </S.Suite>
  </S.StyleguideLayout>
}

function BasicCases() {
  return <>
    <S.Case title={`YouTube Player with URL providing`}>
      <Carousel
        data={CarouselContent}
        spaceBetween={30}
        slidesPerView={3}
      />
    </S.Case>
  </>
}

If I import the swiper to the page as it described in the doc, without component, props etc. It works.
Expected Behavior
The Swiper is working.
Actual Behavior
When I run the page I see this error
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Thank you.
Swiper version
latest
Platform/Target and Browser Versions
Google Chrome latest version, Mac
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Your issue is closed because it is not filled correctly. Before you open an issue please review the contributing guideline.
Please fill the issue template correctly and:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue

It will save a lot of time for other contributors to check your issue and fix it.

I experienced the same problem.
In my situation, it is caused by tss-react.
The swiper module worked fine at the topmost level of import in the application hierarchy, however, it threw an error when I used Swiper within a component chain that used the 'tss-react' in some parent layer.
I updated the 'tss-react' and 'mui' packages to the latest versions, and everything appears to be fine in the initial render of my next app (actually, it was necessary to remove the '.next' directory first) all of the following has happened in the latest version of every mentioned package except next, which was '11.1.2'
In my latest upgrade to the next 12, it seems to be okay, but you need to disable
experimental features flag


fix wrong response data

https://github.com/moov-io/wire/issues/331

Codecov Report

Merging #339 (7082641) into master (eb64f55) will increase coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head 7082641 differs from pull request most recent head 09fd306. Consider uploading reports for the commit 09fd306 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #339      +/-   ##
==========================================
+ Coverage   74.83%   74.84%   +0.01%
==========================================
  Files          73       73
  Lines        8647     8651       +4
==========================================
+ Hits         6471     6475       +4
  Misses       1609     1609
  Partials      567      567


Confirm enabled by default for this command but not documented

Title explains the feedback. This command was wrapped into a complex workflow and due to it's default confirm:$true action it took some debugging to discover why the workflow was failing to run. Could possibly be noted on the documentation page since this is not a "destructive" command.
Happy to explain further or send along a suggestion if desired.
Thanks!

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

ID: 905b56a4-91c2-700a-4faf-a1cb66bda24a
Version Independent ID: 0b002a83-d61f-7cbe-78db-a317d1377d8c
Content: Add-RecipientPermission (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Add-RecipientPermission.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@justin-leopold, I added the following line at the end of the Confirm description:

This cmdlet has a built-in pause, so use -Confirm:$false to skip the confirmation.

Thanks for the feedback.
Closing


[Feature-3495] - CR TDL Updates

EASI-3495
Changes and Description

FE Changes (PR)
BE Changes (Directly on this feature)

How to test this change

This feature will mainly test the un-reviewed BE changes on this feature, and the high-level-e2e testing from a FE perspective.

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.
[ ] Updated the Postman Collection if necessary.

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.

I'll pull in main and make sure the migrations are correct/no conflicts

I updated the backend to migrate existing plan_cr_tdls to crs. I also created a new TDL table, and enabled auditing.

Did a high level run after @StevenWadeOddball and all looks good!


Add ignoreFailures capability for use on Jenkins CI

Logs the failure and report link rather than failing the Gradle build, so that Jenkins can mark the build as unstable when there are test failures. That's preferable to failing the build when you're running cucumber tests as part of a larger build.

These changes look good and this is a good feature add. I've merged your changes. I'll try to get a new version published tonight that includes this.

Great, thanks Jay!


Add initial Guest sessions code

Issue #98

My bad. This code doesn't actually work yet.

Now it works! :)


language 'support' / plugin for Fortran?

If I want to have syntax coloring etc for Fortran for example, how can I enable it?

If there's a vscode extension for it, you could try loading that. See https://onivim.github.io/docs/configuration/extensions#installing-extensions The goal is to provide full support for language extensions, but there is some way until we're there.

I'll close this out as answered. If any features of such an extension doesn't work, it should be more or less covered by the umbrella issue for extensions https://github.com/onivim/oni2/issues/1058


Sending messages to LoRa Devices

Hello!
What is the recommended way to send messages to LoRa Devices from the application? (Downlinks)
Did not find this in the documentation. Please advice!

The code in this repo can only be used for upstream messages.
For downstream communication, we have a more complete project: https://github.com/iot-for-all/iotc-device-bridge
It offers way more flexibility and is extensible through containers.


[RUNTIME] Memory Safety Issue on ZeroCopyInput

In  https://github.com/apache/tvm/pull/11003 we introduced NDArray::FromExternalDLTensor, which allows us to create an NDArray from a DLTensor struct.
This method, however, is not safe in some cases, because the followup method can store the NDArray into data structures like, and there is no guarantee that the external DLTensor won't get freed before these data structure.
Array<NDArray> Test(DLTensor* dltensor, Array<NDArray> x) {
     auto nd = NDArrary::FromExternalDLTensor(*dl_tensor);
     x.push_back(nd);
     return x
}

In this case we don't know how long Array will get retained, and it can go beyond the lifecycle of the dltensor.
We already have  a well-defined way to zero-exchange external memory safely. Through DLPack
Array<NDArray> Test(DLManagedTensor* dlpack, Array<NDArray> x) {
     auto nd = NDArrary::FromDLPack(dlpack);
     x.push_back(nd);
     return x
}

If we want to be able to exchange an external memory, we should do that through DLPack(which comes with DLManagedTensor*), and dlpack comes with proper deleter to be able to track such dependencies and retain memory such cases.
When we are chaining multiple models, in most cases such chaining can be done through natively allocated NDArray, if not possible having a way to construct such external memory into DLManagedTensor would be a safer way(then pass into the SetInput).
Leaving a note here to see if we want to revisit this  API behavior, it might make sense to encourage DLPack and normal NDArray based zero copy.

cc @vvchernov @AndrewZhaoLuo @jwfromm

Hello @tqchen! You are correct in your description and yes, for TVM is better to go along scenario with DLPack to prevent memory safity issue. Nevertheless the method with nesting of NDArray on the external memory (for zero copying) is convenient for some cases. Particularly, recently TVM was embedded to ONNX Runtime (ORT). To avoid excess copying between ORT and TVM input/output tensors this method was implemented. Of course, it is advanced tool and assumes client responsibility for memory management.
Another thing about which I thought is performance measurements for TVM without input/output copying time. I understand that these parts can be hidden in pipelining mechanism, but it is not developed well on TVM python front-end.
Recently I have implemented mechanism to set external output memory to VM instead of allocated inside VM. It gives possibility to client to get output tensors where he wants and keeps them for as long as he need even if TVM session is released. I think this case clearly show why method like NDArrary::FromExternalDLTensor is needed.
P.S. Possibly description of the method should be extended to warn the client about the responsibility when using it

Thanks @vvchernov for the explaination. First of all, I am not questioning the need of zero copy, just how we implement it carefully.
The main concern I have is the API itself and its usage in say VM, which is not always the correct intention.
Having developer to directly(and intentionally) create an DLManagedTensor, convert it to NDArray, then pass into SetupInput might be a better apporach here. Get the ORT integration need, can you point me to the related threads? One possiblity is to implement a ORTTensorToDLPack in that integration point, which specifically setup a DLManagedTensor. If there is no ref counting mechanism there, the worst case is thatw e can follow the same behavior as FromExternalDLTensor, but the surface area is minimized so there will be less possible misused.

Hello @tqchen! Sorry for late response I was busy enough.
I saw it once more, agree with your arguments and have the following suggestion: 1. replace all using of NDArray::FromExternalDLTensor by NDArray::FromDLPack on TVM side. There are several places of the using only. 2a. Set deprecated tag for NDArray::FromExternalDLTensor and remove it on one of the future TVM release when ONNX Runtime code are improved with DLPack too. 2b. As alternative a warning can be added to description and printed in console for NDArray::FromExternalDLTensor to notify client about high-level responsibility related to memory safity.
In my view the best pair 1 + 2a. Potentially I could fix it on TVM side and after that on ORT side, but it will not be done quickly.
cc @AndrewZhaoLuo, @areusch

Thank you. I think we do not need to do FromDLPack in the VM side, and can simply use the original NDArray and run fromDLPack from the users of the VM


Connected Status to show only when phone is open

Being able to have an option to only have the player count and connected status show when you have your phone open would be nice because you still have the information available but it doesn't always have to be visible.

Should be easy, will have to look into how rep is drawn.


Add broad statistics to each fund to help users understand what type of work gets funded

UX Tasks

[ ] Mockup UI


Porting Microsoft.AspNet.Web.Optimization.WebForms

Porting Porting Microsoft.AspNet.Web.Optimization.WebForms

This has already started. Can you enumerate what scenarios you want to enable? Initially, I don't want to worry about actually optimizing anything - I want it to serve up files registered with it. We can enable an interface that could be implemented to actually do the minimizing/bundling if desired

closing this as it's now ported


Add refactor and wrapper for all current samplers from k diffusion.

Added the simple wrapper used elsewhere for access to DDIM/PLMS and K-diffusion samplers side by side. Refactored the seed init to match outputs from other repos. I couldn't run the full bot locally so had to rig a text example to be able to call the do_run() method manually.
Example run from a manual regression test I wrote to make sure the outputs were matching outputs I'd seen from other repos (they do).

I could use some help figuring out if there's a regression test you can run just to make sure the behavior is exactly as expected, I'll attach a snippet of the manual test I was running.

Here's the manual test I wrote in workermode.py as a test to assert all the samplers worked, I could use a sanity check on whether the incoming sampler_name properties would break your integration.
if __name__ == "__main__":
    # main()
    accelerator = accelerate.Accelerator()
    device = accelerator.device
    config = OmegaConf.load(r'path/to/v1-inference.yaml')
    model = load_model_from_config(config, r'path/to/sd-v1-4.ckpt', device=device)
    model = model.half().to(device)
    model.eval()
    for sampler_name in ['plms', 'ddim', 'k_dpm_2_ancestral', 'k_dpm_2_a', 'k_dpm_2', 'k_euler_ancestral', 'k_euler_a', 'k_euler', 'k_heun', 'k_lms']:
        do_run(accelerator, device, model, config, {
            "uuid" : sampler_name,
            "ddim_steps" : 50,
            "ddim_eta" : 0.0,
            "W" : 512,
            "H" : 512,
            "seed": 847793990,
            "prompt" : 'warrior portrait of Piccolo from Dragonball Z, Gatsu, highly detailed face!!!, extremely detailed!, digital painting, unreal engine 5, art by artgerm and greg rutkowski and alphonse mucha',
            "scale" : 10,
            "sampler" : sampler_name,
            "outdir" : './out',
            "skip_grid" : True,
            "skip_save" : False,
            "plms" : False,
            "n_iter" : 1,
            "C" : 4,
            "f" : 8,
            "n_samples" : 1,
            "n_rows" : 2,
            "dyn" : None,
            "from_file": None,
        })


Length Converter calculator

Calculator Functions
Length Converter calculator can use to Create an input element that can convert a value from one Length measurement to another.

Feet
Meters
inches
KiloMeters
Miles
yards
cm

Hello  this is Nikita masane, GSsOC'2022 participant.
Thank you for your time!! and looking forward to work on it.
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


btjd_to_astropy_time() does not accept some float arrays

Problem description
Per documentation, utils.btjd_to_astropy_time() is supposed to accept an array of floats.
However, the function only accepts some types of arrays. See example below.
So either the documentation is inaccurate, or the implementation has bugs.
I expect the resolution would also apply to the peer bkjd_to_astropy_time()
Example

import numpy as np
from lightkurve.utils import btjd_to_astropy_time

t1 = [1.1, 2.2, 3.3]
btjd_to_astropy_time(t1) # failed

t2 = np.array(t1, dtype='float')
btjd_to_astropy_time(t2) # worked

The error is:
--> 370     jd = btjd + bjdref
...
TypeError: can only concatenate list (not "float") to list

Environment

platform (e.g. Linux, OSX, Windows): Windows, Jupyter, Python 3.7
lightkurve version (e.g. 1.0b6): 1.2.0
installation method (e.g. pip, conda, source): conda

Thanks @orionlee!  Once #607 is merged, these functions will accept lists/tuples/floats in addition to a numpy array!

Fixed by #609!


initramfs-test-image: Add a few utils

Add the following utilities to 'initramfs-test-image'
to allow easier board development:

cmake
make
git

Signed-off-by: Bhupesh Sharma<EMAIL_ADDRESS>

NAK. It's a test initramfs, we can't add things like that which has an impact (size) on everyone.
We also agreed to include an indication about the image size increase in such PR.

I tend to agree here. if you need anything, you can compile it on the host and then sideload it by concatenating several cpio.gz images for the initramfs. Closing now.


[MWPW-154272]: Eager Loading only one image for each viewport

when there is only 1 image authored in tablet and in desktop we are able to see the eagerload is seen rendered for when the page is not in that viewport
Resolves: [MWPW-154272]
Test URLs:

Before: https://main--cc--adobecom.hlx.live/drafts/Souj/html/marquee-variant61#
After: https://loadsingleimg--cc--adobecom.hlx.live/drafts/Souj/html/marquee-variant61#

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 89.32%. Comparing base (4e8b5df) to head (25441f6).
Report is 17 commits behind head on stage.

Files
Patch %
Lines

creativecloud/scripts/utils.js
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #352      +/-   ##
==========================================
- Coverage   90.26%   89.32%   -0.94%
==========================================
  Files          17       17
  Lines        2301     2343      +42
==========================================
+ Hits         2077     2093      +16
- Misses        224      250      +26

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

Validation done and results are updated in jira
https://jira.corp.adobe.com/browse/MWPW-154272


Demo does not work properly

This message appears when I click [Login] or [Create New Post]

Demo is not working. @https://venusblog.azurewebsites.net/Account/Login?ReturnUrl=%2FNew

@Calabonga @khuramshahzad Thanks for the catch! We're working on it now.

We had missed connecting our app to a server so it could deploy. We have since fixed that on Azure Portal and the link should be working fine now.


Feature/add note endpoints

Description
This feature is created to allow a mentor to manage mentees' notes.
This API endpoints are :
_GET /notes/
_GET /notes/:note_id
_GET notes/mentee/profile_id_mentee
_PUT /notes/:note_id
_DELETE /notes/:note_id
This feature enables mentors to manage notes per mentee. These API calls include :
_create a new note per mentee by a mentor
_retrieve an array of notes per mentee by a mentor
_delete a note per mentee by a mentor
_modify a note per mentee by an authorized user, which includes admin, mentors, and manee
Video Link
[Loom Video](Add your loom video link here)
Trello Link
Paste your trello card link here, deleting this example
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

https://user-images.githubusercontent.com/85637047/159717842-3858ed49-6161-4497-a002-5d40151d27fc.mp4


Tema development

successfull MVP activity feed, simply lists created conversations

I addressed the reviews I was clear on and then replied with questions to the ones I was confused on. My next task will be to make some tests.


Backports for 0.15.2

Lists of PR to backports from master branch for a v0.15.2:

#3469
#3463

Please add any PR to backport here or flag issues/PRs with milestone 0.15.2

Also backport #3476

Also fixing issue #3489

@kif, do you want to backport #3466 and #3472 in this micro release?

Also backport #3490

@t20100 when do you plan to release 0.15.2?

@t20100 when do you plan to release 0.15.2?

ASAP: if there is no last minute issue to fix, tomorrow sounds too optimistic and next week sounds realistic.

Closing: All backports were done.


messageActionSheet: Fix action sheet title for private messages.

Fixes https://github.com/zulip/zulip-mobile/issues/3874
Before:

Now:

Travis test is failing because of some dependency download issue.

Could not download junit.jar (junit:junit:4.12): Skipped due to earlier error

I think this is temporary.

@ray-kraesig can you please review this, thanks!

Travis test is failing because of some dependency download issue.

Could not download junit.jar (junit:junit:4.12): Skipped due to earlier error

I think this is temporary.

Confirmed. (I believe you should be able to restart a suspected-spuriously-failed CI run by clicking "Restart build" in the upper-right of the CI page. That may require permissions, though.)

Made some revisions. Current logic is largely borrowed from src/webview/html/messageHeaderAsHtml.js

Merged. Thanks!


iOS doesn't have proper footer

hi, i hav footer issue on ios device, but android works fine. i've attached the screenshot from iphone.

I guess the web layout did not handle when web view resize.
Please listen to resize event and update the layout according to actual width and height.


Mediapackage harvest job retry strategy

Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
An harvest job can fails. Most of the tome it fails when nothing was stream and the mediapackage channel never created the HLS manifest. We should retry creating harvest jobs a defined time and then delete the mediapackage channel.
Describe the solution you'd like
In the mediapackage lambda we should handle failure case and then retry creating an harvest job if the retry limit is not reached. The channel is deleted otherwise and the update state endpoint is fetch with DELETED state.

I think should have a special error state for AWS rate limits so that we can handle retries appropriately? I'm afraid we will hit these limits repeatedly on the way up...

This retry strategy is not related to the rate limit. We have to handle the rate limit error in the marsha backend


Post different app review to different channels?

Is it possible to have the bot monitoring several apps, and post them to project-specific channels, without having to spin up multiple instances of the bot? Perhaps we could just specify a custom hook per app, otherwise it uses the default hook?

Great suggestion. Slack webhooks allow a channel other than the default to be specified in the JSON payload, so I think that would be the best approach.
It should be quite straightforward to implement.

I'm pretty new to Slack app development so you'll have to forgive me for my lack of understanding.
I've noticed the values I put in for the chat bot name, icon and emoji are ignored - the Slack App values are used instead, and the channel always points to the one that was specified when creating the hook.
Is it possible to create a hook that can post to any channel, so the same hook is always used but a custom channel is specified? Or do you need a separate hook for every channel?

It's possible to override the default channel. I just took a quick look into the code and ReviewMe already supports overriding the channel, but it doesn't actually seem to be working (Manually posting to the slack hook does).

Actually, I was setting the channel on the wrong app 😄
Specifying a channel in the app configuration does work:
{       "appId": "1234",       "channel":"#builds" }
Also tested working:

botUsername
botEmoji

botIcon isn't working - I'll open a PR to fix this soon.
So your issue might be something different - let me know if you can't get the channel working.

I haven't actually tried the custom channel setting, just noticed that botUsername and botEmoji wasn't working and didn't see the custom channel setting in the README.
I'll test it and take screenshots and upload on Monday morning to a new issue so we can keep them separate, sounds like they may be separate problems.

I've just published 1.0.7, which fixes the bot icon parameter not working.
All other parameters are working afaik so let me know if there are any more issues.
I'll close this issue for now.


Add ApplicationGuid, SolutionGuid and RepositoryUrl to metrics

We recently added Solution/Application GUID and RepositoryUrl to SolutionDetails object in this PR. Application Guid is used to uniquely identify a solution that PA tool assesses. This ID should and will remain the same before and after porting. We should add the three fields to metrics.

PR added here: https://github.com/aws/porting-assistant-dotnet-visual-studio-ide-extension/pull/77


Trouble with Files from LEGO Battles

I am attempting to use this wonderful program to look at files from the game "LEGO Battles" (https://en.m.wikipedia.org/wiki/Lego_Battles). NCLR Palette files open perfectly. However, NCGR and NCBR almost universally will not load at all, I double-click on them and then literally nothing happens. If I then try to open the same-named NCER and NANR files (many of them don't have these, but I'm gonna ignore those because from what I've read that is an unusual setup), they open fine, but the windows report that there is nothing--no objects anywhere, and no frames beyond 00 which has no picture, respectively. I do appreciate that this is a niche game, and I would not be surprised if this is the result of me doing something wrong somehow, but I would appreciate any time at all you could expend on this.
PS: This game also has "nsbmd" files, they seem to open perfectly.

Hello,
thanks for the appreciation, it means a lot :)
For the issue of NCGR and NCBR files not opening, have you tried drag+dropping them onto the program window? To see anything in the NCGR and NCBR viewer you do also need to have an NCLR loaded at the same time.
As for the NCER and NANR files, those I would need to take a closer look at. For those that don't have an associated NCER, do they have an NSCR? An NCBR shouldn't need one, but an NCGR might.
It should also be noted that NitroPaint does not edit the model (MDL0) part of the NSBMD, just the textures (TEX0).
Hope this helps!

Drag and Drop does not seem to help.
I should clarify this--when I open the game's NCGR files, I literally do not get the viewer to appear. Absolutely nothing happens, NCLR loaded or no.
There are occasional NSCR's, but nowhere near as many as the other types. But then again I'm pretty new to this, I am unsure if an NSCR can be associated to multiple files of different names or something.

I just took a look at some files from the LEGO Battles game, and I can see the problem you're having. It seems many of the files in the game seem to have some compression header before the NCGR header, I haven't seen one that looks like that before. Looks to be the bytes "PMOC", the uncompressed size, some 4-byte field, 4-byte compressed data size (twice?), followed by the compressed contents. I imagine this is done because the graphics files aren't stored in any compressed archive, so this was how they were compressed. This is something that I can add support for in the next release hopefully. Sorry for the inconvenience!

Thank you for looking into this! I sure know I wouldn't have been able to figure any of that out.

Thanks very very much for such a nice tool,
In the case of digimon story lost evolution,
ncgr, nclr & nanr can open well but it cannot open ncer properly,
the grachpics cells are scattered around
The same files can be opened nicely with Console Tool but cannot save

Hello, sorry to hear that the NCER files aren't showing properly. I'm suspecting perhaps the graphics are 8bpp, because there is an issue in the current build that impacts the ability to properly render cells for 8bpp sprites. This was fixed in a recent  commit however, so hopefully that will solve the problem for you when it is released, which I may do soon. Sorry for any inconvenience caused in the meantime.

Hello, sorry to hear that the NCER files aren't showing properly. I'm suspecting perhaps the graphics are 8bpp, because there is an issue in the current build that impacts the ability to properly render cells for 8bpp sprites. This was fixed in a recent commit however, so hopefully that will solve the problem for you when it is released, which I may do soon. Sorry for any inconvenience caused in the meantime.

Thanks Mr.
We look forward to the new release

An update to the lego battles thing, I was wrong, the compression looks to be LZ11 which I'll need to implement first. And some files have bigger compression headers than others, so that is also something I'll need to look into.

Well, take all the time you need on this, the game isn't going anywhere lol. Again, thanks for responding and looking into this.

I started looking more closely at the more complex files, and it seems like they broke up the file into multiple separate compressed chunks. As of now I'm unsure of why they do that, maybe so they can more easily pick and choose segments of the file to actually load. The maximum length of a compressed run looks to be 0x1000 bytes, based on what they seemed to do. It looks that at offset 0xC holds the size of the largest compressed run, perhaps so some buffer can be allocated to hold any compressed segment in the file. So in total, the structure of the file looks to be:
Offset    Size    Meaning
0x00      0x4     Magic 'COMP' bytes
0x04      0x4     Total uncompressed file size
0x08      0x4     Number of compressed segments
0x0C      0x4     Size of largest compressed run
0x10      ...     Array of compressed segment sizes
...       ...     Compressed segments

Fascinating!

I've finished up code for handling the Lego Battles files, can read and write them. I think all is well for that, so for now I'll close the issue, but feel free to reopen if you have problems in the future.


[colmap] Build error

OS: Windows 11
(nerfstudio) C:\Users\ict_3\vcpkg>.\vcpkg install colmap[cuda,tests]:x64-windows
Computing installation plan...
The following packages will be built and installed:
colmap[core,cuda,tests]:x64-windows -> 2023-03-12#1
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\ict_3\AppData\Local\vcpkg\archives in 90 us. Use --debug to see more details.
Installing 1/1 colmap:x64-windows...
Building colmap[core,cuda,tests]:x64-windows...
-- Using cached colmap-colmap-30da037ce19bdceb6d239c45342fadb221bdabb2.tar.gz.
-- Cleaning sources at C:/Users/ict_3/vcpkg/buildtrees/colmap/src/b221bdabb2-e3968635af.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/ict_3/vcpkg/downloads/colmap-colmap-30da037ce19bdceb6d239c45342fadb221bdabb2.tar.gz
-- Applying patch fix-dependencies.patch
-- Using source at C:/Users/ict_3/vcpkg/buildtrees/colmap/src/b221bdabb2-e3968635af.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j25
Working Directory: C:/Users/ict_3/vcpkg/buildtrees/colmap/x64-windows-dbg
See logs for more information:
C:\Users\ict_3\vcpkg\buildtrees\colmap\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/colmap/portfile.cmake:60 (vcpkg_cmake_install)
scripts/ports.cmake:147 (include)
error: building colmap:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+colmap
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[colmap]+Build+error&body=Copy+issue+body+from+C%3A%2FUsers%2Fict_3%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
** I tried git pull and then .\vcpkg update but the same error occurs.

Please see here on how to report a proper issue: https://github.com/microsoft/vcpkg/issues/30604


env2yaml does not handle 'xpack.monitoring.elasticsearch.url' array

According to Logstash documentation, xpack.monitoring.elasticsearch.url can be set to an array of multiple Elasticsearch nodes to be used for monitoring. env2yaml only tries to handle stringified booleans and ints as special types for YAML marshalling, which means that using an array will never work. In practice, Logstash will throw an error when trying to parse a (stringified) array of monitoring nodes.

Thanks for this great report. You made me realise that I had really gone the wrong way with parsing in env2yaml. I had essentially implemented a subset of a YAML parser, when all the while I had a full YAML parser that I could reuse.
#44 fixes this, and greatly simplifies the implementation of env2yaml.
I also pushed a once-off image to our registry, in case you'd like to try this out before 5.5.1 is released:
docker.elastic.co/logstash/logstash:5.5.0-issue42

Thank you! The 5.5.0-issue42 issue works great for me.

Is env2yaml even needed now that https://github.com/elastic/logstash/pull/7072 is merged?

No indeed. elastic/logstash#7072 is the future. It will just take some time to get there ;).


feat(global): export lettables as Rx.operators

fixes #2861

Description:
Related issue (if exists):

This does add a lot of size to the global bundle, but the global bundle is really meant for playground code and/or code being used in node.js or the like.

Coverage remained the same at ?% when pulling 6aeae0f44f55b8f4a1d001512cb971bba4d25dc2 on benlesh:export_lettables into 2e576dcb187c9fbebc86ebe3d11837a33fcaa810 on ReactiveX:master.


Issuer is being signed instead of Assertion

Correct me if I'm wrong, but I believe that the Issuer element is being signed instead of the Assertion element, when we opt to sign the assertion.
One symptom of this behaviour I see is that the Id="_0" attribute is added to the Issuer element after signing.
I think this is because of the following code:
https://github.com/thameera/saml-mock/blob/a9fd5992df0a455ce9216f5d289f403110b24753/lib/signer.js#L8
Shouldn't it be like this instead?
const ASSERTION_SIGNATURE_PATH = "//*[local-name(.)='Assertion']"

@spietras you are indeed right, just pushed a fix. Thanks for reporting!


Getting "Error: failed to provision VM" / Error 1

When I do a cf dev start I receive this error message:
Using existing image
Starting VM...
Provisioning VM...
Waiting for services to start...
8 out of 49 running
49 out of 49 running
FAILED
Error: failed to provision VM: Process exited with: 1. Reason was:  ()

After running ssh<EMAIL_ADDRESS>and cating the /var/pcfdev/run.log I can see that something wents wrong while interpreting my proxy settings (I only provide a part of the log):
Feature diego_docker Enabled.
+ ifconfig
+ grep -q 'inet addr:<IP_ADDRESS>'
++ echo <IP_ADDRESS>
++ awk -F . '{print $1 "." $2 "." $3 ".1"}'
+ host_ip=<IP_ADDRESS>
++ cat
+ host_security_group='    [
     {
       "protocol": "tcp",
       "destination": "<IP_ADDRESS>",
       "ports": "1-65535"
     }
    ]'
+ cf update-security-group host /dev/fd/63
++ echo '    [
     {
       "protocol": "tcp",
       "destination": "<IP_ADDRESS>",
       "ports": "1-65535"
     }
    ]'
FAILED
security group host not found
+ cf create-security-group host /dev/fd/63
++ echo '    [
     {
       "protocol": "tcp",
       "destination": "<IP_ADDRESS>",
       "ports": "1-65535"
     }
    ]'
Creating security group host as admin

...
TIP: Changes will not apply to existing running applications until they are restarted.
+ cf bind-staging-security-group host
Binding security group host to staging as admin
OK
+ [[ ! -z http://part1.part2.part3.proxy:8080 ]]
++ echo http://part1.part2.part3.proxy:8080
++ sed '-es,^.*://,,'
++ sed '-es/^.*@//'
++ cut -d : -f 1
+ http_proxy_host=part1.part2.part3.proxy
++ getIP part1.part2.part3.proxy
++ isIP part1.part2.part3.proxy
++ echo part1.part2.part3.proxy
++ grep -q -E '^[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$'
++ dig +short part1.part2.part3.proxy
+ http_proxy_ip='part1.part2.part3.
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>'
+ [[ part1.part2.part3.
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS> == '' ]]
++ cat
+ http_proxy_security_group='    [
     {
       "protocol": "tcp",
       "destination": "part1.part2.part3.
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>",
       "ports": "1-65535"
     }
    ]'
+ cf update-security-group http_proxy /dev/fd/63
++ echo '    [
     {
       "protocol": "tcp",
       "destination": "part1.part2.part3.
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>",
       "ports": "1-65535"
     }
    ]'
FAILED
security group http_proxy not found
+ cf create-security-group http_proxy /dev/fd/63
++ echo '    [
     {
       "protocol": "tcp",
       "destination": "part1.part2.part3.
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>",
       "ports": "1-65535"
     }
    ]'
FAILED
Incorrect json format: file: /dev/fd/63

Valid json file example:
[
  {
    "protocol": "tcp",
    "destination": "<IP_ADDRESS>",
    "ports": "3306"
  }
]

Please note that I removed the original name of my proxy and its various IP addresses. But what is still obvious that a part of the proxy name gets lost.
I removed the VirtualBox files, uninstalled the plugin and create everything from scratch: this problem persists.

This is definitely a bug related to parsing proxies that are provided as domains. We will fix this for the next release. For now, use one of the proxy IP addresses (ex. http://<IP_ADDRESS>:8080) instead of the proxy domain.
Thanks for the report!

I can confirm this works: I ran a quick cf dev destroy and then changed my proxy settings on the outer host:
export http_proxy=http://<IP_ADDRESS>:8080
export https_proxy=http://<IP_ADDRESS>:8080

After this I fired up the VM again with cf dev start and pcf dev boots up fine:
Using existing image
Allocating 8192 MB out of 48125 MB total system memory (43694 MB free).
Importing VM...
Starting VM...
Provisioning VM...
Waiting for services to start...
8 out of 49 running
49 out of 49 running
 _______  _______  _______    ______   _______  __   __
|       ||       ||       |  |      | |       ||  | |  |
|    _  ||       ||    ___|  |  _    ||    ___||  |_|  |
|   |_| ||       ||   |___   | | |   ||   |___ |       |
|    ___||      _||    ___|  | |_|   ||    ___||       |
|   |    |     |_ |   |      |       ||   |___  |     |
|___|    |_______||___|      |______| |_______|  |___|
is now running.
To begin using PCF Dev, please run:
        cf login -a api.local.pcfdev.io --skip-ssl-validation
Email: admin
Password: admin

Thanks a lot for your instant reaction !


Difference in stats shown on the the terminal vs recorded in csv file

Hello Team,
The final stats shown on the the terminal, differ from the once recorded in the '*stats.csv' file. Attaching the screenshot showing the difference in output.
locsut version: locust 2.14.2
Python Version: python 3.9.16
OS            : CentOS Linux release 7.8.2003 (Core)
Thanks
Jitu

Hi! Probably the CSV file is dumped too soon. Dont have time to look into it, but as a work-around it might help setting --stop-timeout (set it to at least the number of seconds it takes to do a full task iteration)

Hi @cyberw  as per your suggestion did give a stop-timeout of 10 secs (task time is around 1.5 to 2 secs) but still there is
a difference in stats shown on the the terminal vs recorded in csv file. Attaching the stats screenshot. @cyberw I am also using the locust-plugins "-i ITERATIONS" option to stop the run.
Thanks @cyberw

For the record, instead of the "-i (ITERATIONS)" option I used the "--run-time" option and I still see a mismatch in the stats.
Thanks!

Probably we need to postpone calling the csv dumping call to later in main.py.


feature/LED1624G9

I made a measurement of IKEA LED1624G9 using a script running with two bulbs. I then manually added some values to the end of the hs.csv file approximately corresponding with xy_color: [0.458, 0.41] which is bulbs default warm white color. Power consumption is significanly higher for this color and near colors and the measuring script did not catch this spike at all.
Another problem is that this bulb does not work with color_temperature (https://github.com/Koenkk/zigbee2mqtt/issues/6388) but powercalc does not create any sensors until both hs.csv and color_temp.csv files are provided so I made an empty dummy color_temp.csv file.

Thanks.

I made a measurement of IKEA LED1624G9 using a script running with two bulbs. I then manually added some values to the end of the hs.csv file approximately corresponding with xy_color: [0.458, 0.41] which is bulbs default warm white color. Power consumption is significanly higher for this color and near colors and the measuring script did not catch this spike at all.

How do you know power consumption for the mentioned color is significantly higher than the measure script picked up?
When this is the case I'm also worried by the accuracy of the other measured values.
Could be a bug in the measure script somehow, but nog sure where. It is working fine for me when using Hue bridge and Shelly plug.

Another problem is that this bulb does not work with color_temperature (https://github.com/Koenkk/zigbee2mqtt/issues/6388) but powercalc does not create any sensors until both hs.csv and color_temp.csv files are provided so I made an empty dummy color_temp.csv file.

Could you have a look into Developer Tools and retrieve the state attributes for the light? I'm interested in supported_color_modes field.

mpty dummy color_temp.csv file.

How do you know power consumption for the mentioned color is significantly higher than the measure script picked up?
When this is the case I'm also worried by the accuracy of the other measured values. Could be a bug in the measure script somehow, but not sure where. It is working fine for me when using Hue bridge and Shelly plug.

I have that particular color set as a main warm white room light because the bulb performs best with that setting. It is also color with which the bulb turns on when reset. All other colors appear substantially dimmer. There are some discussions about this on github for example here.
It seems that this bulb is designed to provide much better results only at very narrow section of color spectrum and the script just is not precise enought and it missed that exact spot where some dedicated warm white diodes kick in at full brightness. I don't know if there are also some other spots like that but I think that if so, they will not be as significant as this one.
Another thing is that it is also not possible to hit that color with home assistants color wheel, it always slips somewhere next to it. You have to set specifically xy_color: [0.458, 0.41] to get the best appearing light and also higher energy consumption.
This is where the color lies on the wheel:

This is the graph of my shelly's power meter from running the measurement. The spike on the left is consumption with the subject color at full brightness and it just never got there during the measurement... (The gap in the middle is where the script stopped for some reason.)

Could you have a look into Developer Tools and retrieve the state attributes for the light? I'm interested in supported_color_modes field.

It states color_temp as supported but it is probably a mistake in zigbee2mqtt because the bulb does not do anything when trying to change color_temp and there are also multiple discussions about color_temp not working.
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4140#issuecomment-757337395
https://github.com/Koenkk/zigbee2mqtt/issues/6388#issuecomment-782832491
https://github.com/Koenkk/zigbee-herdsman-converters/pull/3218#issuecomment-971833032

You can ignore the failed action for "Release drafter", need to have a look into that.
color_temp.csv does not validate correctly. Right now it crashed the validation tool. I think you need to add a header row, and at least 2 other rows.

And thanks for clarifying.

This is where the color lies on the wheel:

In my opinion this particular color loooks like warm white (maybe 2700K?) but bulb probably works in color-temp mode.

Yeah the color_temp mode seems to not work correctly for this light looking at the linked github issues.
When this is resolved we should update the library to include the correct color_temp.csv (with measurements) or remove it from the library.

Will merge for now. @marthubner Could you please have a close look into the related github issues when there are any fixes for color_temp mode?

@bramstroker Yes, I will keep my eye on the issue with color_temp.

@marthubner Another powercalc user stumbled upon issue with this light profile not working correctly because color_temp was missing. See #2047
Back in the time there was an issue with color temp mode reading this PR comments.
Would you be able to provide measurements for this color mode to fix the profile?

@marthubner Another powercalc user stumbled upon issue with this light profile not working correctly because color_temp was missing. See #2047 Back in the time there was an issue with color temp mode reading this PR comments. Would you be able to provide measurements for this color mode to fix the profile?

Ok, I'll try.

@marthubner Another powercalc user stumbled upon issue with this light profile not working correctly because color_temp was missing. See #2047 Back in the time there was an issue with color temp mode reading this PR comments. Would you be able to provide measurements for this color mode to fix the profile?

Ok, I'll try.

@marthubner are you still able to do this?

Hi, sorry for the delay, just started the measurement process. If all goes well, I will post the result tomorrow.


Add CD32 support

We made an experimental test setup for CD32 when CDDA support landed in the MiSTer Minimig core.
We should see if there’s a clean way to integrate it in the launcher (and explore what that means for e.g. emulator use).

Nice!  It;s a mxied bag, really wish the CDTV games worked, or worked better.  Really wanted to hear the CDDA music in DOTC, and Xenon 2 :)   Thanks for the work your putting into this.  Cheers.

Yeah, the “emulator” does not really support CDTV (even though some games run), it’s written for CD32 games.

Nice one!


Maintain secret structure when parsing

This commit introduces a new KV secret type ("AKV") that fully maintains the secret format when parsing. As such it obsoletes the old KV and Plain formats and the need for the core.parsing option.
Fixes #2431
RELEASE_NOTES=[ENHANCEMENT] Maintain secret structure when parsing
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

So let's me bring back the -n flag later. That sounds like a reasonable compromise.
Any other major concerns @AnomalRoil ?

Thanks a lot. I think it does indeed make sense to keep the -n option.


Updating start_date on feed to be based on absolute time rather than relative

What?

 For example, if today's date is 03-01 then "This month" will only show things that happened today.
I confirmed that reddit works differently. Selecting any time filter will subtract an absolute number of days from today. For example, When applying "This month" in reddit, reddit will show posts in the past 30 days.
Doing things this way gets around the problem of different client timezones. In NYC "today" means a different epoch than in the west coast.

This works. Maybe we should consider setting FE enums & make backend handle any timeframe related filters in the future


Expose the claim name in InvalidClaimException

Changes
I need to know what claim is declared as invalid, so i propose to expose the claim name into the InvalidClaimException. Exposing the claim name to make checks is more reliable than compare the message exception.
References
Please include relevant links supporting this change such as a:

support ticket
community post
StackOverflow post
support forum thread

Testing
Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

[*] This change adds test coverage
[*] This change has been tested on the latest version of Java or why not

Checklist

[*] I have read the Auth0 general contribution guidelines
[*] I have read the Auth0 Code of Conduct
[*] All existing and new tests complete without errors

@ghostd We met with @jimmyjames to discuss this feature. We agreed that we don't want the exception message/description to be part of our library's API contract, so that this PR would be a good addition. We've identified two scenarios that today are not completely covered in terms of exception handling when a claim is set to be expected in the verifier instance:
One of them is when an expected claim is not contained in the received payload JSON object. When that happens today, we throw InvalidClaimException. But that exception, as you point out, doesn't include the name of the missing claim. We suggest adding a new exception class that is a subclass of InvalidClaimException that would include the claim name, accessible through a public getter method.
The other scenario we found is when an expected claim is present in the received payload JSON object, but its value is not the expected one. When that happens today, we throw InvalidClaimException without additional details. We suggest adding another subclass of InvalidClaimException that would include the claim name and the claim value, accessible through public getter methods.
By subclassing InvalidClaimException, devs can choose to continue to try/catching InvalidClaimException or capturing the more granular scenarios by try/catching the subclasses and accessing these informational properties. We wanted to know if these scenarios above would fit your use case or if we missed any detail. And of course, if you agree and can provide a PR with these changes. What are your thoughts?

My need is mainly the second scenario (i try to know which claim has an "invalid" value). Thanks for your time, i'll provide a PR.

I created the both exceptions (i can rename them i we find better names). For the claim value embedded into the WrongClaimValueException, i used the toString method because i didn't find how to extract a more precice value from a Claim instance.

The diff tool check passed correctly but we would like to test this out locally before merging the PR. We're tracking this internally under SDK-2836. Cheers.


Add full_table_name and avro_schema_prefix options

-Add the WITH full_table_name option to the Options table
-Add the WITH avro_schema_prefix=[prefix] option to the Options table
-Add Topic Naming explanation/limitations section
Closes #9450
Closes #10054

This change is


test: Add post-deployment tests to github workflow

We're not currently running tests against deployments, we should add those tests back to post deploy runs

dupe of #711


[FEATURE] Expend the size of badge to fit larger digits

Expected outcomes
When the digit on badge gets very larger, expend the size of the badge accordingly.

I would Like to take this issue


Connection Refused: bad user name or password

when i'm use username and password to connect mqtt server, there is some errors, but i'm sure the username and password is correct.
and the mqtt.dart version is the last version: 1.1.2 and Flutter 0.4.4, mqtt server use the Aedes.
    this.c = new MqttClient(new MqttConnectionIOSocket.setOptions(host: host, port: port),
        clientID: this.clientId,
        qos: QOS_1,
        cleanSession: true,
        userName: "sayone",
        password: "sayone2018"

and i'm print the username and password on the mqtt server program:
2018-06-07T19:18:35+0800 <debug> app.js:88 (Aedes.self.aedes.authenticate) username: sayone2018, password: undefined
the password become to username, and password become to undefined.
[VERBOSE-2:dart_error.cc(16)] Unhandled exception:
type 'Future' is not a subtype of type 'Future'
#0      MqttClient.connect (file:///Users/weibo/data/soft/flutter/.pub-cache/hosted/pub.dartlang.org/mqtt-1.1.2/lib/mqtt_client.dart:55:22)
#1      MyMqttClient.listen (package:saytoken_flutter/mqtt/MyMqttClient.dart:35:12)

#2      _LoginPageState.login (package:saytoken_flutter/redux/presentation/LoginPage.dart:27:22)

#3      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:494:14)
#4      _InkResponseState.build. (package:flutter/src/material/ink_well.dart:549:30)
#5      GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:102:24)
#6      TapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:161:9)
#7      TapGestureRecognizer.acceptGesture (package:flutter/src/gestures/tap.dart:123:7)
#8      GestureArenaManager.sweep (package:flutter/src/gestures/aren<…>
flutter: Opening session
flutter: Connection Refused: bad user name or password
[VERBOSE-2:dart_error.cc(16)] Unhandled exception:
Connection Refused: bad user name or password
#0      _rootHandleUncaughtError. (dart:async/zone.dart:1114:29)
#1      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#2      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
flutter: Connection to broker lost
flutter: Connection lost

any update on this ?I am also getting the same problem when using user name password

Hi,
Sorry for the delay.
I managed to reproduce your issue. I will work on a fix and let you know once ready.
best regards

Please try with package 1.1.3. It should fix the issue.

Hi
Was this issue Fixed, I am Getting Same Issue.
Also I have to Downgrade Dart SDK Version to run this.
Do you plan to Upgrade this to dartsdk 2.0+


idrac-exporter 1.3.1 fails to start

After upgrading from 1.1.0 to 1.3.1 the idrac-exporter pod crashes on startup with the following error message:
/app/entrypoint.sh: line 17: /app/config/idrac.yml: No such file or directory
2024-07-08T15:39:49.164 FATAL Failed to open configuration file: /etc/prometheus/idrac.yml: open /etc/prometheus/idrac.yml: no such file or directory

To me it looks like the entrypoint.sh script has two flaws:

It attempts to write to /app/config/idrac.yml but the folder /app/config does not exist in the Docker image.
In https://github.com/mrlhansen/idrac_exporter/blob/master/entrypoint.sh#L17 it writes the file, but it doesn't change the $config variable accordingly.

Hi @svenfoo
Yes, you are right. Thanks for letting me know.
I will merge the fix, but the entrypoint.sh is largely obsolete now that the exporter natively supports configuration via environment variables. I was contemplating removing it when I made the latest release, but decided to keep it for compatibility, but at some point I will probably remove it.

Looked into that now and our usage scenario is somewhat difficult to implement only with environment variables. We want to have idrac-exporter running on each node of the cluster, so we are using a daemonset. And each node has its own iDRAC credentials, so we need to look them up at run-time depending on the node name. This is easily implemented by mounting the credentials of all nodes and letting entrypoint.sh do it's magic.
Maybe there's a simpler way to implement this. If idrac-exporter had an environment variable, or configuration option, to tell it to dynamically obtain the credentials based on the node name, that would help a lot.

Alright, so we should probably keep the entry point in that case. However, I guess it can be simplified quite a bit, for example (not actually tested):
#!/bin/bash

auth_file="/authconfig/$NODE_NAME"
if [ -f "$auth_file" ]; then
	export CONFIG_DEFAULT_USERNAME=$(cut -f1  -d= $auth_file)
	export CONFIG_DEFAULT_PASSWORD=$(cut -f2- -d= $auth_file)
fi

exec bin/idrac_exporter "$@"

In this way you will still be able to have the per-node definition of the credentials. The rest of the configuration can either be configured via environment variables, or by mapping a configuration file into the container.
What do you think?

What do you think?

That should work for us. It's more or less what I hacked up yesterday by overriding the entrypoint command. But I would prefer if we wouldn't have to do that.

Sounds good, then I will try to push an update later today.

Fixed by commit fa0cd16de9414ee9e4dc70f40528f1a88226f467


"Create Timer" window inserts invalid timestamp on Korean locale

Note: Korean Windows uses YYYY-MM-DD format by default

In Korean locale, "Create Timer" window inserts #YYYY-MM-DD hh:mm:ss# instead of #YYYY/MM/DD hh:mm:ss#, causing the parser to think it as a invalid color string.

Thanks for pointing that out. This issue will be fixed in the next version.

Reflected in v0.3.8534.27378-beta.


[Feature][connector] Upgrade the version of kudu from 1.7 to 1.12 and add units test for kudu

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
According to the email , I want to upgrade the version of  kudu from 1.7 to 1.12 and add units test for kudu by using kudu-binary which can start a minimize kudu server but has a platform limitation(only support linxu-x86_64 and osx-x86_64).
In order to solve the platform problem about the import problem of kudu-binary jar, maybe we can add profile which can be triggered according to the os environment automically. In this way, we don't have to add -D in maven or set -D in ide to solve the import problem of kudu-binary jar. But we still need a way to skip the unit test according to to OS version.
Junit5 provides the annotation to skip the test according to the os, and more elegant semantics. But I'm not sure about whether it's worth upgrading the Junit from Junit4 to Junit5?  Anyone give some suggesstions？
Usage Scenario
Start the minimize kudu server in unit test, so we can test kudu-source, kudu-sink on a kudu cluster.
Related issues
#1459
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Rianico As we discussed in mail thread, we can just upgrade the kudu version and use other way to control the UT.


v6

The v6 will break v5 compatibility.
The new features are the following:

Usage of YAML to store camera configuration
Save of all the camera instructions
Tweak manually any instructions of a camera
Specify camera resolution
Catch ctrl-c (one time) to avoid breaking camera
Zsh completion

The updates and fixes are the following:

Update OpenCV to v4.9.0
Fix video feedback freeze
Better logging
Fix test command
Fix multiple v4l path for same device

More to come in the following weeks/months.

:arrow_right: Commit d2fbf7e7bd048567badba44861a696a29145ef87
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:x: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 390a8b0d5f52743a148835cb65399ad8a795943d
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:x: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 2cb866fd10867e189d74eaf7a8175d5134307e96
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:x: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit f620b09c57f86f7c6526c49245807596c81d246f
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:x: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 74b3e6505d0bebda23d7e36865c6920ca0fabd11
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:x: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit da58b00751cefe55866d77c5b6139382822836a1
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 5d9dbb5e930da41a4c6aee534913efd494681a2c
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit aa8ee50aee32205ccbe3b02bb8ebc3ce47707f73
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:x: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit d4048e91b2de8702d604bc0b61b6a4fff4cc7afb
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 4c6da4963442f4b4fef625f72f9009ea3a78c9d1
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit d44441eadc9b849c3cd0082812f41c65df9a9e45
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 811db69af2e74b10fc110b9c3a4894f23a37a6f9
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 3b131097f3d8eaafc130f3c42e4acdd3d6edf741
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit e570c76ca3e7fb67e07fd07f9d630e1f58be99da
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 99637aea54d615aa5efdb832a64f33a52f40e2a2
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 4d69591937fd04e7ced0cf403f01cc0e0f6318c1
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Tarballs:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 466edc093d63651801a6022c00d218e3e769f50a
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 1fdeabe03f68f049ea00098e5dc37a9dea281f1a
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:x: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit c5dea250e715ff0dc2fb6805be58ce3819a9ea65
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 80f046045248c68ea640f8ac16b06dbed07c9170
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit a4b385486aa3f867e3d26a5d8f989cfbb22dbb2f
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 25ca5142ade4419836cf0dd4a7c2a542b7a6df83
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 75d574847108bc808cbc8147158a9b6880c3531b
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 2c49cde78124b596f6cae5983d7db04297e86020
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 99e854c7f961c7b22a5fda00dd863c6e625acbd1
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 4a3312ff3488d14fc8da8a5b0144714bc0ea7381
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 7e5804522f48ce56b80484ca0978914c602821ec
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit befe76608bf204e8ed1bcd99accfab9f4f57ee1f
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Uninstall the previous version, unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit 9cf4ebc7c86c55db21ae6596a02c5169b7372d9d
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Uninstall the previous version, unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.

:arrow_right: Commit d2fab72bbc87fbcbcb6fa8184f634ae728ed3adb
:clipboard: Logs
:mag: Linting results:
:heavy_check_mark: Python Linting
:heavy_check_mark: C++ Linting
:hammer_and_wrench: Building result:
:heavy_check_mark: Building
:package: Artifacts:
If the building step was successfull, you can download the appropriate tarball in the artifacts section here.
Uninstall the previous version, unzip and then execute sudo tar -C / --no-same-owner -h -vxzf linux-enable-ir-emitter*.tar.gz.


[Feature Request] Light and dark theme

Description
Light and dark theme
Feature:
We could create a simple light and dark mode for the user to toggle between.
Possible Solution:

We can create two icons at the footer so it is not to distracting with all the other elements in the hero/header. We can use react icons to display a sun and moon as the buttons and highlight whichever is active.
We can use localstorage to save the users preference for the light and dark mode.  In order for the theme to be accessible across the whole application, we can utilize "useContext" that will wrap our app in the index.js file and provide a "theme" and "setTheme" as props in a context file. The context file can contain the following as a possible implementation:

import React, { useContext, useState } from "react";

const ThemeContext = React.createContext();

export const ThemeProvider = ({ children }) => {
  const [theme, setTheme] = useState(true);

  const toggleTheme = (isLight) => {
    setTheme(isLight);
    setLocalTheme(isLight)
  };

const setLocalTheme = async (value) => {
      try {
        await localStorage.setItem("theme", value.toString());
      } catch (err) {
        console.log("Error setting local theme: ", err);
      }
    };

  return (
    <ThemeContext.Provider value={{ theme, setTheme, toggleTheme }}>
      {children}
    </ThemeContext.Provider>
  );
};

export const useTheme = () => {
  return useContext(ThemeContext);
};

And then in the index.js we simply wrap our context like so:

import { ThemeProvider } from "./context/ThemeContext"; // new line

... morecode

<ThemeProvider> // new line
  <React.StrictMode>
     <RouterProvider router={router} />
  </React.StrictMode>
</ThemeProvider> // new line

... more code

Now that our theme variable can be accessible throughout our whole application all we have to do is run the "toggleTheme" or "setTheme" to toggle the light/dark theme:

import { useTheme } from "./context/ThemeContext";

function ExampleComponent() {
     const { theme, setTheme, toggleTheme } = useTheme();

   ... more code
}

As for the localstorage, we can initialize a default theme in the app.js like so:

  const initializeLocalStorage = async () => {
    try {
      const localTheme = await localStorage.getItem("theme");
      if (!localTheme) {
        localStorage.setItem("theme", JSON.stringify(theme));
      } else {
        const parsedTheme = JSON.parse(localTheme);
        setTheme(parsedTheme);
      }
    } catch (error) {
      console.log("Error initializing LocalStorage:", error);
    }
  };

  useEffect(() => {
    initializeLocalStorage();
  }, []);

When changing the color of the application we can use css custom properties:

div[data-theme="light"] {
   color: "black",
   background-color: "white"
}

div[data-theme="dark"] {
   color: "white",
   background-color: "black"
}

In the components where we want the styles to be applied, all we have to do is add the following:

import { useTheme } from "../../context/ThemeContext";

function ExampleComponent() {
const { theme, setTheme, toggleTheme } = useTheme();

... more code

<div data-theme={theme ? "light" : "dark"}>
... more code
</div>
}

... more code

In summary, this should allow the user to toggle the light/dark theme and save the following theme in the localstorage so that when the user leaves and returns to the application, they will still have their preferred theme.

Screenshots
No response
Checklist

[X] I have checked for duplicate issues
[X] I have read the Contribution Guidelines
[X] I am willing to work on this issue (optional)

Hi I can try to do this

Hi @Angeltheesoto !
Excellent angel! I'm currently traveling and haven't looked to closely at the code you provided. I love the idea of a light and dark mode. Go for it and I will go ahead and assign. Have a nice day and happy developing!

Nice and thank you for your thourugh explaination in your open issue. I appreciate your documentation and the issue is assigned to you @Angeltheesoto. Have a great Sunday and thank you for your initiative👏🏻

Hi I can try to do this

Thanks @joyboy-reincarnated for your enthusiasm! The issue has already been assigned. Take a look at the ReadMe of the repo and you can contribute right away to the project with sharing what you want to do before you die. Have a nice day!

@XanderRubio, Thank you I will start working on it! And hope you have a great weekend as well 😊

@XanderRubio, Thank you I will start working on it! And hope you have a great weekend as well 😊

Great and thank you @Angeltheesoto!

Hey everyone. If this hasn't been completed, I can jump on it


Create 0000-01-02-codewithchotuu.md

created a branch, created a file and made a commit, and opened a pull request


[BUG] When a variable references a property of a resource it errors with error parsing Bicep variables

When a variable is referencing a property from a resource (an App Service Plan) it errors when creating the document.
Description
When running the command:
bicep-docs.exe -V --input . --output README.md

The error is returned:
error processing main.bicep: error parsing Bicep variables

Steps to Reproduce

Create a main.go file with the following contents:

@description('Name of the App Service Plan to host Web-App on')
param servicePlanName string

@description('Get resiliance options from Service Plan')
var isZoneRedundant = servicePlan.properties.zoneRedundant
var reserved = servicePlan.properties.reserved

@description('Get App Service Plan Object')
resource servicePlan 'Microsoft.Web/serverfarms@2023-01-01' existing =  {
   name: servicePlanName
}

output isZoneRedundant bool = isZoneRedundant
output reserved bool = reserved

Context
I'm trying to use the tool to iterate through some in-house custom modules and there are a couple of failures.
This is one of our older modules which may be re-written but thought it was worth raising a bug.
Thanks for fixing the other defect so quickly! :)
Your Environment

Version used: bicep-docs version v1.2.1
Operating System and version: Windows 11 23H2

First of all thanks for your feedback once again @TheGrussalo, it is crucial in improving the tool since I cannot test/think of every possible scenario.
This is expected behavior due to how Bicep compiles variables that reference resource properties. Let's look at the process:
Original Bicep:
var isZoneRedundant = servicePlan.properties.zoneRedundant
var reserved = servicePlan.properties.reserved

resource servicePlan 'Microsoft.Web/serverfarms@2023-01-01' existing = {
    name: servicePlanName
}

output isZoneRedundant bool = isZoneRedundant
output reserved bool = reserved

Compiled ARM template:
{
  "parameters": {
    "servicePlanName": {
      "type": "string",
      "metadata": {
        "description": "Name of the App Service Plan to host Web-App on"
      }
    }
  },
  "resources": [],
  "outputs": {
    "isZoneRedundant": {
      "type": "bool",
      "value": "[reference(resourceId('Microsoft.Web/serverfarms', parameters('servicePlanName')), '2023-01-01').zoneRedundant]"
    },
    "reserved": {
      "type": "bool",
      "value": "[reference(resourceId('Microsoft.Web/serverfarms', parameters('servicePlanName')), '2023-01-01').reserved]"
    }
  }
}

During compilation, Bicep optimizes the template by:

Evaluating variable references
Converting them directly into reference() function calls
Omitting the variables section from the ARM template

This optimization is logical and doesn't affect the template's functionality - the result is the same whether the properties are referenced through variables or directly. The variables provide a more convenient way to work with these values in Bicep.
Since bicep-docs parses the produced ARM template to generate documentation, it cannot find the variables section, leading to the error you're seeing.

First of all thanks for your feedback once again @TheGrussalo, it is crucial in improving the tool since I cannot test/think of every possible scenario.
This is expected behavior due to how Bicep compiles variables that reference resource properties. Let's look at the process:
Original Bicep:
var isZoneRedundant = servicePlan.properties.zoneRedundant
var reserved = servicePlan.properties.reserved

resource servicePlan 'Microsoft.Web/serverfarms@2023-01-01' existing = {
    name: servicePlanName
}

output isZoneRedundant bool = isZoneRedundant
output reserved bool = reserved

Compiled ARM template:
{
  "parameters": {
    "servicePlanName": {
      "type": "string",
      "metadata": {
        "description": "Name of the App Service Plan to host Web-App on"
      }
    }
  },
  "resources": [],
  "outputs": {
    "isZoneRedundant": {
      "type": "bool",
      "value": "[reference(resourceId('Microsoft.Web/serverfarms', parameters('servicePlanName')), '2023-01-01').zoneRedundant]"
    },
    "reserved": {
      "type": "bool",
      "value": "[reference(resourceId('Microsoft.Web/serverfarms', parameters('servicePlanName')), '2023-01-01').reserved]"
    }
  }
}

During compilation, Bicep optimizes the template by:

Evaluating variable references
Converting them directly into reference() function calls
Omitting the variables section from the ARM template

This optimization is logical and doesn't affect the template's functionality - the result is the same whether the properties are referenced through variables or directly. The variables provide a more convenient way to work with these values in Bicep.
The tool previously failed because it was expecting a 1:1 match between variables found in the Bicep file and those in the ARM template. When Bicep optimized away the variables section, this check failed, resulting in the error message.
This has been fixed in version 1.2.2. The tool now:

Successfully parses variables from the Bicep file
Recognizes that they might be optimized away in the ARM template
Uses the Bicep variables directly instead of requiring them to exist in the ARM template

You can now use variables that reference resource properties without any errors from bicep-docs.

Thank you once again, works perfectly!


Falco fails to build from source because of issues with grpc cpp plugin and libcurl

What happened:
Trying to build Falco from source into an ArchLinux does not work. It results into the complaints about grpc (implicit fallthrough) and libcurl issues with libidn2.
What you expected to happen:
Falco built from source.
How to reproduce it (as minimally and precisely as possible):
Assuming the current dev branch of Falco in the Falco directory, and a sibling directory containing the current dev branch of Sysdig, just follow the basic process to build Falco from source (eg. make build && cd build && cmake .. && make).
Anything else we need to know?:
Environment:

Falco version (use falco --version):

0.15.3

OS (e.g: cat /etc/os-release):

NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"

Kernel (e.g. uname -a):

Linux l13o1 5.1.4-arch1-1-ARCH #1 SMP PREEMPT Wed May 22 08:06:56 UTC 2019 x86_64 GNU/Linux

Others:

gcc 8.3.0

/assign @fntlnz
/assign @leodido


Can this be used on Youtube?

Hi, wonder if this can be used on Youtube playlist too?

Youtube is not supported yet, you can use yt-dlp, youtubedl to download. Maybe in the future bilix will support.


Using $ to match the end of a string triggers unreachable code warning on MSVC

https://godbolt.org/z/af1vW91jG
#include <ctre.hpp>

static constexpr auto pattern = ctll::fixed_string{"^hello world$"};

int main(int, char** argv)
{
    return ctre::match<pattern>(argv[1]);
}

example.cpp
C:\data\libraries\installed\x64-windows\include\ctre\evaluation.hpp(239) : error C2220: the following warning is treated as an error
C:\data\libraries\installed\x64-windows\include\ctre\evaluation.hpp(239) : warning C4702: unreachable code
C:\data\libraries\installed\x64-windows\include\ctre\evaluation.hpp(240) : warning C4702: unreachable code
C:\data\libraries\installed\x64-windows\include\ctre\evaluation.hpp(242) : warning C4702: unreachable code
Compiler returned: 2

With ctre::match you don't need to use ^$

Oh, that is very true. Sorry about that

The error is actually correct, because after $ the implicit $ can't be matched and won't be called at all... so it's unreachable.

Don't worry. It's ok 😊


all: add typedefs to public API structs [v2]

Soletta already uses "sol_" namespace and most of the time a secondary
namespace that is module-specific. This makes the identifiers very
large. By removing the need of explicitly use "struct" the client code
has less noise.
The convention for Doxygen documentation was:

Opaque structs appear in typedefs section of the
documentation. @typedef doxygen marker is used.

Public structs appear both in data structures and typedefs
sections. The documentation is not marked so it applies to both (some
markers were removed).

This patch includes a change in documentation of sol_http_url struct to
escape "#fragment" properly, so Doxygen stops warning. This was
preventing "make doc" to work -- due to a check done after doxygen call.
Fixes #1982.
Signed-off-by: Caio Marcelo de Oliveira Filho<EMAIL_ADDRESS>

This adds tweaks to documentation after @bdilly suggestion.

@bdilly the error from semaphoreci seems unrelated to my patch :-(

yeah, you're right. not related.
commits is good
:+1:

merged


Tests failing ❌

It seems that the tests are failing without any valid reason, locally and within the CI.

Are there some missing testing instructions that the Mongopay team should provide?
If not, how to ensure that this package is ready for production?

cf.
PR: https://github.com/Mangopay/mangopay2-php-sdk/pull/431
CI:  https://travis-ci.org/github/Mangopay/mangopay2-php-sdk/builds/734590012

Hi @lucasmichot
we're looking into testing, there are a few considerations in play,
Would it be possible to speak about it, could you contact me<EMAIL_ADDRESS>To discuss the issue

Fix passed for this issue in last release, feel free to let us know if it persists


[BUG] Can't update password name

When I'm updating name of password and save him, name doesn't change. Needs fix in future version.

Bug have fixed.


Add theme: Minimal sidebar

Add theme: Minimal sidebar
This PR adds a new theme to the theme library.
Theme Details

Name: Minimal sidebar
Description: With this Zen theme, you can remove the buttons from the sidebar and make more space for your tabs
Homepage: https://github.com/Venca321/Zen-Minimal-Sidebar-Theme
Author: @Venca321

@Venca321 the homepage link is invalid

My bad, I forgot to make it public. It's fixed now


Provide Example Payloads for all webhook events

I am developing an integration for Zulip to integrate with open collective through its webhooks but we need example payloads for all the events to be able to develop it. Please can these be provided.

@adambirds I see that Zulip provides Slack-compatible webhooks, we could auto-detect them in our code to send events with a nice format. Could you share your Zulip instance domain with me to make sure we enable it (if it's self-hosted)?
Regarding the issue itself, I agree that adding a webhook without knowing the event's format is a poor experience. We've got an alternative proposal to solve that in https://github.com/opencollective/opencollective/issues/4071: add a button to send a test event to the webhook.

Quickly stopping by to say that #4071, while a great idea, isn't an alternative. As a devleoper gettingn started using webhooks, I still would have create something, put it up somewhere, have it print out or save the webhook payload, configure webhooks, then send a test for all theo nes I wanted before I could even start developing my actual project. This costs time and money that could be saved by having webhooks documented somewhere. Thanks!

@SamWhited I agree that test payloads can't replace proper documentation, but I still see them as a cheaper way of improving the situation. Especially with tools like https://webhook.site (that we could maybe surface in the interface?) that make it super-easy to setup a "debug" webhook.

Implemented the base system for this along with a few event payloads in https://github.com/opencollective/opencollective-frontend/pull/8029


Extension of io

I have extended a couple of functions for saving and reading results and key records from the pipeline as well as the raw expression matrix (https://github.com/nilsmechtel/stereopy). If you are interested in them, feel free to add them to the main branch.

hi, @nilsmechtel
Thank you so much! We have merged them to our branch and will have more code testing.


The 'plot_curve' function isn't working well

I've changed the line 68.
From:
num_iters_per_epoch = log_dict[epochs[0]]['iter'][-1]
to:
num_iters_per_epoch = log_dict[epochs[0]]['iter'][0]
This change should solve the problem. The function is getting the wrong number os iteration per epoch.

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

Can you give more details about the reason for the modification?
I think the original implementation is correct.

Hi @tuskininja  ！We are grateful for your efforts in helping improve this open-source project during your personal time.
Welcome to join OpenMMLab Special Interest Group (SIG) , where you can share your experiences, ideas, and build connections with like-minded peers.
To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have a WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Settings screenshot out of date

https://github.com/PhotonVision/photonvision-docs/blob/master/source/docs/hardware/images/settings.png is out of date, please grab a new screenshot and update.

If someone wants to grab a nice screenshot, preferably one that doesn't just say unknown for everything, itll be added to the brand new navigating photonvision page


Fix build config validation

Fixed build config validation shown in https://travis-ci.org/github/onnx/onnx-mlir/builds/715883913/config.

Build config validation
root: deprecated key sudo (The key sudo has no effect anymore.)
root: missing os, using the default linux

Can one of the admins verify this patch?

@jenkins-droid test this please.


Remove version: MonkeysAudio.MonkeysAudio version 1.023

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://monkeysaudio.com/files/MAC_1023.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 694)


Validate Recurring Donations Data when inserting the records

Critical Changes
Changes
As a user I want to ensure quality data entry on Recurring Donations so that donors receive appropriate credit for their donations.
Issues Closed
New Metadata
Apex classes:
RD2_ValidationService
RD2_ValidationService_TEST
Custom Labels:
RD_ValidateAccountAndContactMissing
RD_ValidateContactMissingForAccount
RD_ValidateIfContactNotRelatedWithAccount
Deleted Metadata

Tracking W-035605

@force2b and @RadSFDeveloper , The changes are all done and ready for review. I have changed the custom labels as per @RadSFDeveloper and ready for review.

@force2b , The code review changes are done and ready for review.

@force2b , The changes are all done!

@force2b and @RadSFDeveloper , I have made the changes suggested by you and it is ready for review.

@RadSFDeveloper and @force2b , The changes are done and ready for review!

@force2b & @RadSFDeveloper , The changes are done and ready for review.

@force2b , The changes are done and ready for review.

QE testing is complete for this PR.  Tests have passed.
For further testing details, see:
https://foundation.lightning.force.com/lightning/r/agf__ADM_Work__c/a2x1E000001C9yvQAC/view
https://salesforce.quip.com/R0qYAHQ2aTE3
Merging PR.


Add all including nested_dict

Prevents pyflakes error:
'nested_dict' imported but unused
Also remove unneeded future imports.

Obviously #2 and #4 should be merged first.


Output / Sex Behaviour refactor

Remove old style data accesses from output & sex behaviour
Get rid of the old selector function which was made redundant by sub-populations

That's true; these outputs are really just for demonstration though and so will get overwritten anyway. Ideally I'd like the outputs for different parts of the simulation to be controlled by their respective modules.


Telegram server says - Bad Request: can't parse entities: Can't find end of Bold entity at byte offset

I've received this error a few times during the ollama's mixtral response.
raise TelegramBadRequest(method=method, message=description)

aiogram.exceptions.TelegramBadRequest: Telegram server says - Bad Request: can't parse entities: Can't find end of Bold entity at byte offset 603

I have a similar issue with LLama3: aiogram.exceptions.TelegramBadRequest: Telegram server says - Bad Request: can't parse entities: Can't find end of Bold entity at byte offset 1455
Found out a couple of things which may be related and help with this issue:
likely cause is that it does not include the asterisk character * in the list of characters to escape (escape_chars). The fix should be something like this:
def md_autofixer(text: str) -> str:
    # In MarkdownV2, these characters must be escaped: _ * [ ] ( ) ~ ` > # + - = | { } . !
    escape_chars = r"_*[]()~>#+-=|{}.!"    # Use a backslash to escape special characters
    return "".join("\\" + char if char in escape_chars else char for char in text)

Hi, I changed as you suggested, but now, there are 2 extra stars at the end :

then, not sure it's the correct solution

I agree that it might not be the correct solution. But it fixed the error that caused the crashes and stopped the bot for me. I hope the original contributers can look into this specifically

Fixed (MD regression)


[DUOS-332] Use latest GA4GH DUO version

Addresses
https://broadinstitute.atlassian.net/browse/DUOS-332
See also: https://github.com/DataBiosphere/consent-data-use/pull/7

Coverage decreased (-0.5%) to 73.844% when pulling 26c1fd27394e0c673bcf4b0a532d39d19f69efcb on DUOS-332 into 8eaaeafe5c13c9db8ba6378297c84359ad03536e on develop.


[vcpkg doc] Update doc link in README_zh_CN.md

sync with the doc link in README.md
I notice that the es\fr\ko_KR\pt has not synced also, should also open other prs

Thanks!


Replace references to IRC with Zulip

This PR just updates the various project docs to point to Zulip instead of IRC.
Resolves (for this repo): https://github.com/xi-editor/xi-mac/pull/338

@nangtrongvuon Good idea.  I'll get a PR for the main repo as well.

Looks good, thanks @jeremywiebe!


Feature/<IP_ADDRESS>/read service request

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

[ ] Refactor
[ x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description

read service-requests from DB
removed types that was part of template
will need to check if app constants used correctly, add history support

QA Instructions, Screenshots, Recordings

http://localhost:3000/clients displays data from database

I'll close this for now, I think a lot of the functionality you added had been added with other PRs. The branch will still exist, so we can always open this up again


tests: deployment failed due to missing cfn templates on s3

Definition of done (v0.0.1)

[ ] Automated integration test
[ ] Integrity protection according to ADR-NNNN
[ ] Structured Logging and Monitoring for Lambda function according to ADR-NNNN

already accidently merged to main