ReaBlink conflicts DrivenByMoss4Reaper

I'm using Reaper 6.43 on MacOS 11.6.1, using the latest commit of ReaBlink, fd1b3e531fb38cd476b9490ca878cd20743d0d82.
After building reaper_reablink-x86_64.dylib, and moving it into place at ~/Library/Application Support/REAPER/UserPlugins/, I then add the ReaBlink lua scripts to my Action List.
After selecting & running ReaBlink_Monitor.lua I get the ReaBlink Monitor window. Regardless of whether or not Reaper is master or puppet, or when the designation was set (I tried adding reaper.Blink_SetMaster(true) to the ReaBlink_Monitor.lua script as suggested in the Reaper forums), Reaper will successfully start & change BPM without issue.
However, the moment Reaper's transport is stopped, whether by pressing Stop in Reaper's transport bar, running the ReaBlink_StartStop.lua Action script, or pressing stop in a Link-ed application, Reaper will suddenly close. This happens regardless of whether Reaper is the only participant in the Link session, or one among many.
I get the exact same behavior when using the provided, pre-built reaper_reablink-arm64-x86_64.dylib plugin.
Here's an example of the crash output I get when this happens: https://pastebin.com/raw/TBVPrPqY

Does this happen when you use REAPER Start/Stop transport command (spacebar by default)? If not, then it should be fixed in ReaBlink v0.4.1 release.

Apologies for not following up more quickly, but I tried both the 0.4.1 & 0.4.2 releases, as well as doing a pull from the main branch and building from the most recent commit, 0158d3ac92d0955edf505ce8ad9b2b22a8699d16, and I'm getting the same behavior. Let me know if I can provide any other debugging information.

Hi! Unfortunately I'm unable to replicate the issue. Tested with clean install on macOS 11.5.2. Once you've enabled ReaBlink Monitor, you should not need to use any of the helper scripsts for basic operation; ReaBlink captures native transport start/stop commands and native actions for increasing/decreasing tempo by 1.
The crash could be a result of some specific Transport related setting in REAPER, or perhaps a Transport related conflict with another extension or script. Or something Undo/Redo related.
If you can, test with a clean/separate REAPER install, and if it works, then gradually bring in your REAPER settings/scripts/extensions and see what breaks things. Although, that could require unreasonable amount of effort depending on your level of customization.
You could also try modifying the source code and make a custom build at least for debugging purposes. In file BlinkEngine.cpp commenting out lines 200 and 206 cause ReaBlink not to write any undo information; if the problem lies there. Commenting out line 320 will cause ReaBlink not to issue a transport stop (on Link session stop); this will break functionality, but if it survives, it will reveal if this is a transport control conflict.

Eliminating plugins revealed that ReaBlink crashes Reaper when the DrivenByMoss plugin is present in the UserPlugins folder. It doesn't have to be enabled in Preferences->Control/OSC/web.

Can you try building commit 1119179e3f91c30cf7b02b9b2b2f94de9faafc6d and see if it survives DrivenByMoss4Reaper?

It did not, unfortunately

Ok, after installing DrivenByMoss I am able to replicate this, but I'm not entirely sure if this is within my scope/abilities to fix. The crash happens when ReaBlink commits undo state once playback is stopped. It would seem DrivenByMoss also does this, and these processes may conflict or perhaps end up in race condition. Commenting out/removing lines 200 and 206 in BlinkEngine.cpp and making new build is a workaround, but it might not be a permanent solution; without these, the undo list can be flooded with individual actions ReaBlink takes.

Maybe v0.5.0-rc.1 available in releases works better? I was no longer able to replicate the issue with ReaBlink v0.5.0-rc.1, REAPER 6.47 and DrivenByMoss 15.5.0.

Hello @ak5k, thank you for all the hard work developing this extension. Unfortunately, I'm encountering the same error as @wallacewinfrey with DrivenByMoss v21.2.0, Reaper v6.82, and ReaBlink v0.4.6 . I don't see v0.5.0-rc.1 in the Github releases. Was this release removed?

Hello @ak5k, thank you for all the hard work developing this extension. Unfortunately, I'm encountering the same error as @wallacewinfrey with DrivenByMoss v21.2.0, Reaper v6.82, and ReaBlink v0.4.6 . I don't see v0.5.0-rc.1 in the Github releases. Was this release removed?

Hi! v0.4.6 calls stop function from main thread (like 0.5.0, which is no longer available), so there shouldn't be conflict with stop function. Or does crash occur in some other situation?

I'm seeing crashes when using the play, pause, or stop buttons on the GUI in Reaper. It doesn't happen every time, but reliably happens after a couple start/stops. The clock is rock solid when it's playing and responds to tempo changes in linked software.

I'm seeing crashes when using the play, pause, or stop buttons on the GUI in Reaper. It doesn't happen every time, but reliably happens after a couple start/stops. The clock is rock solid when it's playing and responds to tempo changes in linked software.

With current implementation I don't think this can be easily fixed. ReaBlink Master/Puppet modes issue (unsafely) transport commands from audio thread, to maintain accuracy and good sync. Running Master/Puppet modes on main/GUI thread wouldn't be that accurate, and would probably defeat the purpose. It is possible to disable Master/Puppet modes, and try to write some case specific workaround with ReaBlink API.


Generated Datasets for Cityscapes

Dear Jia @yurujaja and Obukhov @toshas
I hope this message finds you well. Congratulations on your acceptance to ECCV 2024!
I am currently working on a domain generalization project on the Cityscapes -> ACDC, DZ, BDD, MV, I would like to compare my dataset generation method with yours. Could you kindly provide the generated dataset from Cityscapes that was used for the Table 2? This would be invaluable for my research.
Additionally, I am having difficulty reproducing the vanilla domain generalization performance of "DAFormer" and "HRDA" as presented in the same table. My reproduced results show that DAFormer performs worse (mIoU=50.0) without both SHADE and RCS as mentioned in this comment. However, using SHADE without RCS gives the best performance in my experiments (mIoU=54.27), which is close to the reported score. Can I use this score for my table, and could you please provide further details?

Model
SHADE
RCS
mIoU

DAFormer
X
X
50.00

DAFormer
X
O
43.11

DAFormer
O
X
54.27

DAFormer
O
O
49.58

Thank you for your assistance.
Best regards,
Minho Park

Thank you for your interest in our project. We will soon release the generated Cityscapes dataset. Please stay tuned for updates. Thank you!

Thank you for your quick response and for sharing the wonderful work!

Hi @pmh9960 , Are there any updates on this?
Thanks !!


AuthorizeIssuance.prepareAuthorizationRequest should take or return generated state

Dear team,
State is currently generated inside AuthorizeIssuanceImpl and can not be extracted or stored after calling AuthorizeIssuance.prepareAuthorizationRequest() without parsing resulting authorizationCodeURL
https://github.com/eu-digital-identity-wallet/eudi-lib-jvm-openid4vci-kt/blob/0b2946cab0483fbab170094fb0f5d221b5db3eb6/src/main/kotlin/eu/europa/ec/eudi/openid4vci/internal/AuthorizeIssuanceImpl.kt#L70
At the end of the flow Wallet instance will get the code and state
(e.g. "state=umerLYauAS-E33UK64uD3SMoC2orCslWku9xSrGm5Rc&code=blDtU1XSgFyMv1FoBg6402GRaXHsDZ8JgKgzVR-Sv-E")
At this point Wallet instance MUST parse this url to get the code to continue the flow by calling authorizeWithAuthorizationCode on a persisted AuthorizationRequestPrepared object. At this point Wallet needs to be sure this persisted object matches the original state.
I see several solutions:

Provide generated state as a parameter to  (AuthorizeIssuance.prepareAuthorizationRequest(state))
Return pair of state and AuthorizationRequestPrepared object as the result of a successful authorization
Add state to AuthorizationRequestPrepared object
do nothing and just parse authorizationCodeURL

All these solutions will help Wallets, to restore their state (AuthorizationRequestPrepared) by a state value and continue the flow.
Your thoughts?
Gennadi

Hi @ydanneg
I have the impression that here there are two issues:

Since we use state in the authorization request, we should check what authorization server returns. This is missing and it is a bug
In addition, currently state is generated by the lib. We may allow, the wallet to optionally provide a state value. This is a feature.

I prepared a PR for this. But I could use your feedback for the following:
Do we really need to allow the wallet to provide a state value, or should we just keep only the random?

we could still use random by default but it's better to return it to the wallet.

Dear @ydanneg ,
Perhaps I confused you. Sorry for that.
If you check the PR you will see that:

Library always sets the state parameter to the auth. request.
The value of the state can be optionally set by the wallet. If not, a random value will be used
The value of the state used in auth. requested is being returned to the caller (the wallet) as part of the AuthorizationRequestPrepared

My question was about : if you find useful - library user - to allow the wallet to provide a state or whether it should be always generated ?

we could still use random by default but it's better to return it to the wallet.

Dear @ydanneg ,
Perhaps I confused you. Sorry for that.
If you check the PR you will see that:

Library always sets the state parameter to the auth. request.
The value of the state can be optionally set by the wallet. If not, a random value will be used
The value of the state used in auth. requested is being returned to the caller (the wallet) as part of the AuthorizationRequestPrepared

My question was about : if you find useful - library user - to allow the wallet to provide a state or whether it should be always generated ?

Currently I don't have any use-case to provide a custom state. But who knows what happens in the future? ;)

we could still use random by default but it's better to return it to the wallet.

Dear @ydanneg ,
Perhaps I confused you. Sorry for that.
If you check the PR you will see that:

Library always sets the state parameter to the auth. request.
The value of the state can be optionally set by the wallet. If not, a random value will be used
The value of the state used in auth. requested is being returned to the caller (the wallet) as part of the AuthorizationRequestPrepared

My question was about : if you find useful - library user - to allow the wallet to provide a state or whether it should be always generated ?

Currently I don't have any use-case to provide a custom state. But who knows what happens in the future? ;)

Actually that would be useful to allow providing custom state. For example to put the current user location into the state to return to after.

Merged.
@ydanneg Many thanks!


ISSUE: child locks not working

Describe the bug
Child lock isn't working. When creating the integration, the YAML file is recognized, but the integration fails to create the child lock or handle it at all in the generated package files. Additionally, when going back into options, the "path to child locks file" is empty.
Environment (please complete the following information):

OS: HA docker container
Type of system that HA is running on: NUC (Debian VM docker container)
Home Assistant version: 2021.4.6
Docker
Component version: 0.0.31
Z-Wave integration name: zwave_js
Lock make and model: Yale YRD256 (master) and YRD226 (child)

Logs
No errors are generated on debug mode unless I try to specify a door_sensor_entity_id (I tried that after some googling, but it gives ERROR (SyncWorker_35) [custom_components.keymaster.config_flow] Child locks file data is invalid: extra keys not allowed @ data['back_child']['door_sensor_entity_id']).
Additional context
My child file:
back_child:
  lock_entity_id: lock.back
  # door_sensor_entity_id: binary_sensor.door_back_homekit
  alarm_level_or_user_code_entity_id: sensor.fake
  alarm_type_or_access_control_entity_id: sensor.fake

Fix in v0.0.48 child locks are now configured from the UI


Package request: llvmPackages_17

Project description
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
Metadata

homepage URL: https://llvm.org/
source URL: https://github.com/llvm/llvm-project
license: Apache License v2.0 with LLVM Exceptions
platforms: x86_64-darwin, aarch64-darwin, aarch64-linux, i686-linux, x86_64-linux

Hi there, I don't think it will happen soon unfortunately as we still need to pick up the pieces of the last LLVM16/LLVM git divergences.

@RossComputerGuy Please ensure that llvmPackages_git and llvmPackages_16 are sync with llvmPackages_17 if you do so. Each time, we give in to not stabilizing the divergences, we lose the opportunity to make it work for everything we learned about in the past release.

Alright, I'll keep that in mind. Didn't realize there was a llvm git package, I only copied the stuff from llvm 16 to make 17 and after removing a couple patches, it seems to be working so far (compiler-rt built, clang just finished). There will probably have to be some patch changes but so far, things are working.

I have a couple of Darwin-related questions:

#256590 fixes Darwin cross. Should I wait for that to be merged before suggesting Darwin cross changes (or do it in a separate PR depending on timing)?
libc++ 17 requires the 10.13. SDK. Is the plan to revert https://github.com/llvm/llvm-project/commit/c73c3a078a130c4180a9d3626dcbc408992d53f9 (and hope nothing else requiring 10.13 has crept into libc++), or is x86_64-darwin going to be broken until the SDK is bumped?

@reckenrode I can try things out since my ARM machine is Apple Silicon. I'm mainly focused on Linux on ARM but I can try out the ARM Darwin support and patch if necessary.

@reckenrode I can try things out since my ARM machine is Apple Silicon. I'm mainly focused on Linux on ARM but I can try out the ARM Darwin support and patch if necessary.

aarch64-darwin should be fine. Its SDK is 11.0. The issue with x86_64-darwin is it’s still using the 10.12 SDK by default (see #101229), and work on the update is still in progress. This doesn’t affect #234710, but it’ll be an issue for the Darwin stdenv once LLVM 18 is released next year.

Should we just remove _git? Opened https://github.com/NixOS/nixpkgs/pull/269994 for discussion.


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1857

Questions ?
Please refer to the Backport tool documentation


Add the possibility to ignore variable interpolation

In our JSON files, we have some variable interpolation, such as:
"infoMessage": "Most recent statistics available for (D-2) : {{date}}",

By default, when translating files with such values, the variable name (date here) often gets translated too, which is not desirable and causes errors and side-effects. Currently, after translating to a new language, we manually check the file for such errors, but it would be amazing to be able to just ignore the contents of such patterns to translate the text without translating variable names.

Hi @cfecherolle, I'm sending the whole line to the translation provider, and the rest is on them. Sometimes the problem you described happen, and it's really frustrating. I'll try to solve it in the future, when I catch some extra time. The idea is to exclude words wrapped in {{ }}, before translating, and then to map them back, but I'm assuming that it could be problematic to map them back in the exact same spot after translating.

Hi @while1618! Thank you for your quick reply.
It might be possible to use something like a Regex (capture groups?) to isolate patterns of words like {{word}} in the original string and then, in the translated value returned from the translation service, replace every pattern like {{word}} in the same exact order as before to restore the values.
Unfortunately, results would be unpredictable because each language has its own ordering rules in sentences so group 1 might become group 2 and so on. So yes, I see what you mean and that's complicated, indeed. The problem here is to find a "rule" that would always work to restore the words wrapper in {{ }} in the right order/right place.

Maybe the best option is to check if those translate providers have an option in their api to set something like {{word}}, and then they just skip that part of the sentence. They will also know where to put it in the translated sentence to make sense. Google translate have something like this: Stack Overflow. It's not ideal, but it's something.
I'll probably try something in a future, maybe to use regex and exclude words, then map them back (I assume that it can be a problem in some cases, but it's better than nothing), or I'll try to find something like 'skip translation' for every translate provider.

Hello, it would be easy enough to extract all parameters and replace them with a number.
ex: "Hi {{name}}, would you like to {{something}}"

Replace with
"Hi {{0}}, would you like to {{1}}"
save the array ['name', 'something']
translate
map back

Hi @cfecherolle, @theolundqvist, sorry for the late response, I totally forgot about this issue.
The feature should work in v1.2.6, you can try it. If there is anything wrong, feel free to comment here. I tested it with Japanese and Serbian and both languages worked correctly. I had problems before with Japanese. Also, I run it only on azure-rapid, because I don't have keys for google anymore, if any of you test on google api, please let me know if it works.
The implementation was a combination of my idea from before, and the idea from @theolundqvist, so thanks for the comment and idea.

@while1618
Thanks,
Maybe I will just contribute with a DeepL translation integration beforehand.

Hi @while1618!
Thank your for implementing this 🙏
I just bumped my package version from 1.1.21 to 1.2.6 and get unexpected results:
"welcome": {
  "message": "Welcome, {{username}}"
}

Becomes:
"welcome": {
  "message": "Welkom, {{undefined}}"
}

When translating from English to Dutch with Google Translate and my API key like I usually do. I will try other versions between the one I was using before and this new release to see if this is new behavior or not.

Hi @cfecherolle,
I made a mistake in my last version, I didn't test this solution with multiple rows and nested objects, and I had problem with them, so I ended up with undefined fields. It should be fine now in 1.2.7, let me know if you have any other problems.
I also merged PR that @theolundqvist made, so now you can also use deepl thanks to him.
Apart from that, there is this issue, now when I implemented skipping words that are wrapped in {{}}, I'll try to modify regex to catch html tags <> </> as requested in the issue.

This ended up really easy to implement once I made words in {{}} to be skipped. So from 1.2.8 words that are wrapped in {{}}, <>, </> won't be translated. e.g. {{skip}} <strong> </strong> <br />

@while1618 Great job! Could you also add {skip} as well? In i18next, {{skip}} is used for string/number interpolation while {skip} is used for html content interpolation.
thanks

@theolundqvist Added in 1.2.9.

hi @while1618
for me in v1.2.9, the values in single curly brackets will most likely still be translated not be skipped. The skipping works more reliable on words with camelCase e.g. {skipMe} than on a single word e.g. {skip}

Hi @while1618, I tested 1.2.9 and it works like a charm when translating with Google! 🎉
All {{variables}} remained unchanged after translation.

hi @mschneekluth, the content of {} shouldn't matter. I'm excluding words before even calling the translate api, and after the translation is done, I'm mapping them back. If you can send me the content of your json file that you want to translate, I will check it, but that seems strange to me. Also, the translate api provider shouldn't matter in this case.

hi @mschneekluth, the content of {} shouldn't matter. I'm excluding words before even calling the translate api, and after the translation is done, I'm mapping them back. If you can send me the content of your json file that you want to translate, I will check it, but that seems strange to me. Also, the translate api provider shouldn't matter in this case.

Here is a small example from my json file. Thank you very much for checking it, @while1618 !!
{   "cookieBanner": {     "text": "This website uses {coin} {coinSkip} for functionality and analytics purposes. If you agree to our use of cookies, please continue to use our site.",     "acceptBtnText": "Accept",     "subtitle": "performance of buying {amount} of {coin} {frequency} for the last {period}."   },   "BaseHeader": {     "exchanges": "Exchanges {skip} {skipMe} are good.",     "exchanges2": "Exchanges {are} good."   } }

hi @mschneekluth, I checked the text you provided, and for me is working as excepted. I test it on multiple providers, and it's working fine. But as I said, this feature shouldn't depend on translate provider, because I just exclude those words before translating.
Maybe you should try to reinstall the lib and check that you are using the latest version. Also, try to override the file you want to translate.

hi @mschneekluth, I checked the text you provided, and for me is working as excepted. I test it on multiple providers, and it's working fine. But as I said, this feature shouldn't depend on translate provider, because I just exclude those words before translating.
Maybe you should try to reinstall the lib and check that you are using the latest version. Also, try to override the file you want to translate.

Hi @while1618 , thank you for checking my JSON file! I can confirm that is working for me now. I think I did not upgrade the version correctly. I reinstalled the lib as you suggested and then I worked 👏


Log to file

We find the output of gradle to be entirely useless for several reasons:

there's lots of it - not gradle's fault, but many of the tasks just spew out megabytes of text - our total build log is about 30mb, and that's not even at "debug" level
its intermingled - if you use parallel, then output is coming from multiple tasks and can't be correlated
its all or nothing - while you can specify logging levels, if you choose little logging, then that's what you get, you can't go back in time and get more

Philosophy
really - we want the minimum information given to us - which is basically "yes it's still doing something" and "this is why it failed" - but we want all possible information available in the rare cases we want to find it.
The way I'm trying to make to work

logging to console logs only [task x started] [task x finished] by default
for every task full debug level logging is written to gradle_log_{timestamp}/{task name}.log
IF (and only if) a task fails - that task's log is dumped to the console

the problem
I've read every bit of documentation I can find, tried many different capture standard out, replace logger, replace log manager - but I can't figure out any way of making it work like I want, because it seems to be completely impossible to separate logs from different tasks
the simplest solution
create something that gives each task an id, and preface each task with that ID - including some specific {id}:StartTask and {id}:EndTask lines - then at least we could pipe the gradle output through some post-processor and make something useful out of it.

I know this is closed - but #2408 does not seem to cover the problem - it seems to be about being able to target individual parts of the log and put them somewhere - which is a) way more than I want and b) probably still won't do what I want.   Essentially all I want is

the full (debug) log always goes to a file

and nothing else is changed in any way.


ja: Make docs/concepts/containers/container-lifecycle-hooks.md follow v1.19 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/containers/container-lifecycle-hooks.md to follow v1.19 of the original (English) text.
Why is this needed
content/ja/docs/concepts/containers/container-lifecycle-hooks.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/tree/dev-1.19-ja.1/content/ja/docs/concepts/containers/container-lifecycle-hooks.md
Original
https://github.com/kubernetes/website/tree/release-1.19/content/en/docs/concepts/containers/container-lifecycle-hooks.md
diff between translated and v1.19
https://gist.github.com/f9f7bb56f8631a7ba722a1bebf6ec34a
Note
Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/triage accepted

/assign

/close


Autotest typescript + extend typescript definition fix

This PR does three things:

Calls npm install with the most recent version of npm.
Adds typescript test to npm run test.
Fixes an incomplete definition of extend in typescript.

A failing typescript definition looks like this: https://travis-ci.org/apepper/tcomb/builds/455408299#L1002-L1020

Thanks @apepper


Show warning about curvilinear DVR on Intel systems

Not sure if I'm splitting hairs here.  Do we want the user to be able to turn warnings back on?  I'm concerned that a user may not read the warning, silence it, then move on and never see it again.
If we had the 'do not show warnings' checkbox in the RenderHolder, they would be able to turn it off and on each time they make a new renderer.  We'd also be able to warn the user if they're making a 3D renderer when only 2D variables are available, as Sam has pointed out to me.
If this is something that can wait, I'm fine accepting the PR.


Colonial factions spawned prematurely by Nexerelin's faction respawning system

Mod Name:
Vayra Merged
Mod Version:
3.3.10
What did you expect to happen?
Colonial factions would start spawning via their colonization events around Cycle 212 so they can actually establish themselves.
What actually happened?
They started spawning in late Cycle 206 around the end of September, seemingly as a result of Nexerlin thinking they are deceased and bringing them into existence, no announcement or anything. Since they had no planets before being born prematurely they pick a random planet, usually terrible, and either struggle along pathetically or just die again very quickly.
By using the console command string below that prevents the 5 colonial factions respawning, they stop appearing prematurely. That's how I'm 100% sure its a Nexerelin faction respawn issue.
runcode Global.getSector().getFaction("almighty_dollar").getMemoryWithoutUpdate().set("$nex_respawn_cooldown", true);
Global.getSector().getFaction("ashen_keepers").getMemoryWithoutUpdate().set("$nex_respawn_cooldown", true);
Global.getSector().getFaction("communist_clouds").getMemoryWithoutUpdate().set("$nex_respawn_cooldown", true);
Global.getSector().getFaction("science_fuckers").getMemoryWithoutUpdate().set("$nex_respawn_cooldown", true);
Global.getSector().getFaction("warhawk_republic").getMemoryWithoutUpdate().set("$nex_respawn_cooldown", true);.
Also noticed that when this command string is used, Fays Co from Bird's Trinkets and Rarities (which is disabled via Lunalib) tries to do a Resurgence at exactly the same time a colonial faction would sneak in. That actually pops up a notification, so even more evidence its a wonky interaction with the Nex system.
This also happened with older versions of Vayra's Sector, even since before Dragn was maintaining it.
Steps to Reproduce:

Turn on Nexerelin's faction respawning setting for all factions and wait, for me it first happened on Sept 26 c206. At least one of the colonial factions will be present in the faction list with no announcement and either have no planet or a terrible one, or maybe just vanish again after a while.

Using the above command string to flag the colonial factions not to respawn prevents this.

Screenshots/Logs:
Additional info:

@PreConceptor ok, i see that the issue reporting template is missing the "What should have happened" question since i'm not exactly sure what... needs fixing here.
So, nexerelin is causing problems with these factions, and you ran code via console to make them show up
So... what exactly needs fixing here? How these factions work with nexerelin? The Nexerelin integration?
can you clarify this a bit better to me on discord please? or here?

@RkShaRkz 'What should have happened?' and 'What did you expect to happen?' are identical in this case, and the answer is 'not spawn 6 months into the first cycle in such a way that effectively renders the factions stillborn without having to input a specific console command that 99.9% of users won't know'.
I only know it because I noticed this problem several years ago and figured it out by asking around on discord, it was not and still isn't a commonly known solution. What needs fixing is also pretty obvious, although I don't know if its possible to fix only here. Something that prevents Nexerelin thinking the factions are already dead and need to be respawned, whether a custom thing or just flagging them on game start to not respawn so the respawning system doesn't bypass their intended spawning via Vayra's Sector-controlled expeditions.

Histidine chimed in

call SectorManager.getManager().incrementNumRespawns(factionId) 99 times
(at such a point I'd seriously consider using reflection to set the large value directly :death:)
actually lemme see if there's a more dynamic way to do it, e.g. letting the factions respawn normally after they've scripted-spawned once
oh SectorManager.DO_NOT_RESPAWN_FACTIONS is a static set, you can manage it yourself

so the thing i'm kinda-but-not-really worried about now (that i need to recheck) is - using Nexerelin's SectorManager directly will put in a hard-dependancy on nexerelin rather than it being an optional one. so I need to think a bit about that, ideally keeping it optional but also playing around with that if it's present :)
either way, the following factions need to be added to the nexerelin's SectorManager.DO_NOT_RESPAWN_FACTIONS
communist_clouds
science_fuckers
warhawk_republic
almighty_dollar
ashen_keepers
kadur_remnant

@PreConceptor so, if i upload a build for you to test out before i merge in the "fix", would you be able to try it out and confirm whether it works or not so the proper fix can be merged in? :) i'm rksharkz on discord. otherwise doing it by email is no different from doing it by using this issue as a mediator.

build with potential fix for issue #44 - https://ufile.io/ie0swkbc

Resolved and fixed by commit 84caff3 - closing.


how should present/absent work in the UI?

@ahahn-gbif and @MattBlissett you both have opinions on this and they disagree.
If I understand correctly, then Matt strongly believes that there should be a 1:1 correspondence between API and UI urls.
Andrea argues that it is such a fundamental filter that we should have it as a hidden default (clicking the trashcan will clear all filters and only show PRESENT). And showing all is, from the users perspective, adding a filter.
Personally I started implementation thinking of it as a filter like all else, but with a warning encouraging a choice. And then I wanted to add a pre-filter on all links. But that is annoying when clearing filters. But as Matt argues that could be solved by compromising on what it means to clear filters. Clear could mean to clear anything but the PRESENT/ABSENT filter?

Clear could mean to clear anything but the PRESENT/ABSENT filter?

I would be fine with that interpretation
I am not sure I understand the conflict yet. From the user perspective, having a filter labeled "presence data only" and with the box pre-checked, allowing to remove the filter implying that now both presence and absence are included, but having the filter "reset to default" on trashcan activation (box pre-checked again) should be consistent with API use, just phrasing the label accordingly?

I don't know if we disagree, as I don't know what Andrea's opinion on the URL was.
I think https://www.gbif.org/occurrence/search should not have filters, so if the default is to filter for present occurrences, then links from the homepage, clicks on the homepage map and so on should go to https://www.gbif.org/occurrence/search?occurrenceStatus=PRESENT
That maintains consistency between the WWW URL and the API URL, which is particularly useful for explaining the API to beginners, including beginners with no programming experience, and quick use of the API (by using the portal to construct queries) for everyone else.

Thank you both for your inputs. I've made a version and put in on UAT (as you might have seen). i will close this issue. Feel free to create a new one if you find the implemntation unfortunate.

(I've also deployed it to gbif-dev.org, as UAT was overwritten with translations. Dev only has two absence records though.)
On maps (homepage, dataset, species etc) could you change the "Explore" and click-on-the-map links to have occurrenceStatus=present as part of the filter? The map has excluded absences for a year or two now.

closed by https://github.com/gbif/portal16/commit/e6696262d8ed991bbd4deffe4f3420558fc02714


Cannot set smartcard mode

Hello,
When trying to play the  smartcard_bbio.py script, it fails with the error "Cannot set smartcard mode, try again or reset hydrabus."
I tried to reset it, but all the time the response is 'BBIO', it does not switch to 'CRD1' as expected in the script.
I have pulled the last version of HydraFW and correctly build and flash it according to the user guide, indeed with the firmware I am able to able to get ATR.
Please find below details about the system information:
> show system
HydraFW (HydraBus) v0.9-beta-49-g5a3a20a-dirty 2019-03-23
sysTime: 0x000157a3.
cyclecounter: 0xf6a12f45 cycles.
cyclecounter64: 0x00000000f6a12f54 cycles.
10ms delay: 1680027 cycles.

MCU Info
DBGMCU_IDCODE:0x100F6413
CPUID:        0x410FC241
Flash UID:    0x30001A 0x31374707 0x33373331
Flash Size:   1024KB

Kernel:       ChibiOS 4.0.4
Compiler:     GCC 4.9.3 20150529 (release) [ARM/embedded-4_9-branch revision 227977]
Architecture: ARMv7E-M
Core Variant: Cortex-M4F
Port Info:    Advanced kernel mode
Platform:     STM32F4x5 High Performance with DSP and FPU
Board:        HydraBus 1.0
Build time:   Apr  1 2019 - 11:14:50

Did anyone else experienced the same or manage to run that script correctly ?
Best regards,

Could you test using latest master as there is a fix related to BBIO mode
https://github.com/hydrabus/hydrafw/commit/4995ea5ef4423df03318fdd1410aed138adba0e7

Thanks, but the error is still present with that fix.
> show system
HydraFW (HydraBus) v0.9-beta-50-g4995ea5-dirty 2019-03-29
...

I am running it on a windows host.

Hi !
The readme says this script is made for Python 3.2+
I tested the following :
Python 2.7.16 => Same error message as you
Python 3.7.3 => Works fine
Can you please verify that you are using a correct Python version ?

Thank you @Baldanos it works:
$ Python36-32/python bbio_smartcard/smartcard_bbio.py
Parsing ATR:
Convention direct: 0x3b
T0:  0x65
TB1: 0x0
TC1: 0x0, extra guard time integer N=0
TA2: absent, card in negotiable mode.
Historical bytes: 2063cbaba0
Traceback (most recent call last):
  File "bbio_smartcard/smartcard_bbio.py", line 280, in <module>
    convention = smartcard_parse_atr()
  File "bbio_smartcard/smartcard_bbio.py", line 253, in smartcard_parse_atr
    if protocol != 0:
UnboundLocalError: local variable 'protocol' referenced before assignment

Do you know where the incompatibility comes from in Python2.7 ? Byte encoding ?
Regards,

Looks like python2 does not do the same with the bytes() function. On line 71 of the script you have
hydrabus.write(bytes([BBIO_SMARTCARD]))

Python2 :
>>> bytes([0b00001011])
'[11]'

Python3 (correct) :
>>> bytes([0b00001011])
b'\x0b'

I'll let you close the issue if it work for you.
Thanks for reporting !


[Backport release-24.05] prismlauncher: 8.3 -> 8.4; refactor

Description of changes
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

The "Check cherry-picks" workflow fails as I resolved a merge conflict with 755b915a158c9d588f08e9b08da9f7f3422070cc by adopting it's change to meta.description

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1890

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1891


Code autogen

Prerequisites

[X] I am using the latest version of Locust
[X] I am suggesting a new feature, not asking a question

Description
Playwright test automation tool have very neat build-in code generator which helps very much when you need to make quick runs through your test environment. Locust would benefit big time for similar functionality to make test generating much quicker.
I'm not aware of any code generators for Locust, that's the reason why I'm asking for it :)
I know this is a big tasks and a lot of work to integrate but in the long run, it would make this so much better. It can be also an external component, not really integrated to Locust itself.

Hi! Sounds like you are looking for https://github.com/SvenskaSpel/har2locust/ :)

That is actually pretty much what I was looking for. I tried to search such thing earlier but couldn't find, thank you for pointing to the right thing :)


fix: Update the package.json files so that correct Node version gets selected for the Nodejs sample apps

Signed-off-by: Akash Nayak<EMAIL_ADDRESS>

If no node version is mentioned in the package.json file, Move2Kube will select the default node version which will be the latest version from the nodeversions.yaml. Our sample nodejs applications aren't compatible with node v16 and above, so I have added the node version constraint to the package.json file.

Our sample nodejs applications aren't compatible with node v16 and above
The NodeJS sample in language-platforms is compatible, we run end-to-end tests which deploy them on a cluster and return 200 OK.
Also even if it is true that they can't run with the latest NodeJS then that is a bug that needs to be fixed. The sample apps are simple static web servers for the most part, there is no reason to have complex version restrictions

If there are issues with making these samples work with Node 18 and beyond we should fix those bugs. Adding the version constraint does not make sense for such simple static web server samples.

I deployed the NodeJS sample with Node 16 and it didn't work on the OpenShift cluster. But, then I deployed the same NodeJS sample to Kubernetes cluster and it worked. I think the end-to-end tests deploys it on a Kubernetes cluster and return 200 OK.

With registry.access.redhat.com/ubi8/nodejs-14 and registry.access.redhat.com/ubi8/nodejs-12 image, it works on both OpenShift as well as Kubernetes cluster.

If there are issues with making these samples work with Node 18 and beyond we should fix those bugs. Adding the version constraint does not make sense for such simple static web server samples.

I deployed the NodeJS sample with Node 16 (registry.access.redhat.com/ubi8/nodejs-16) and it didn't work on the OpenShift cluster. But, then I deployed the same NodeJS sample to Kubernetes cluster and it worked. I think the end-to-end tests deploys it on a Kubernetes cluster and return 200 OK.

This just confirms that it's not a Node version issue but an Openshift issue (since the same code works on Kubernetes).
Regardless add the version constraint is not the correct thing to do. If there are bugs that are preventing the same code from running on Openshift we should fix it.

If there are issues with making these samples work with Node 18 and beyond we should fix those bugs. Adding the version constraint does not make sense for such simple static web server samples.

I deployed the NodeJS sample with Node 16 (registry.access.redhat.com/ubi8/nodejs-16) and it didn't work on the OpenShift cluster. But, then I deployed the same NodeJS sample to Kubernetes cluster and it worked. I think the end-to-end tests deploys it on a Kubernetes cluster and return 200 OK.

Looking at the error, it's just a common permissions issue that people face:
https://stackoverflow.com/questions/42363105/permission-denied-mkdir-in-container-on-openshift
We can fix it by adding the proper chmod for /opt/app-root/src/.npm.
Another way to fix it is by changing where Node writes the logs to.

Fixed during session over Webex.

https://github.com/konveyor/move2kube-demos/pull/197


Nuxt 3.7.0 - devServer https config not taken into account

Environment

Operating System: Darwin
Node Version:     v16.20.0
Nuxt Version:     3.7.0
CLI Version:      3.7.0
Nitro Version:    2.6.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      modules, experimental, i18n, ignore, components, css, colorMode, nitro, app, devServer, devtools
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
For obvious reasons I can't share the certs
Describe the bug
In the nuxt.config.ts, setting the certs for https devServer doesn't have any effect. It was working on 3.6.5.
export default defineNuxtConfig({
  devServer: {
    https: {
      key: './server.key',
      cert: './server.crt'
    }
  }
})

Additional context
No response
Logs
Nuxt starts printing the following, completely ignoring the https devServer config:

yarn run v1.22.19
$ nuxi dev
Nuxt 3.7.0 with Nitro 2.6.1                                          11:01:54 PM
                                                                     11:01:54 PM
  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

ℹ Vite client warmed up in 1137ms                                   11:01:57 PM
✔ Nitro built in 723 ms

same here. thought it kinda gets taken into account. if you start it with dev --https it uses thouse key files from the config.

same here

Sorry for the inconvenience. Several fixes were added to nuxi 3.7.2 in order to address this issue.
You can self-update using npx nuxi upgrade --force and make sure to use 3.7.2+ using npx nuxi info.
If you still having issues, don't hesitate to ping me.

@JulienVanelian, did the nuxi upgrade fix it for you? Are you now able to run the dev server with HTTPS? Sadly, I can't get it to work having run npx nuxi upgrade --force.
- Operating System: Windows_NT
- Node Version:     v16.20.1
- Nuxt Version:     3.7.1-28224571.2d469711
- CLI Version:      3.7.4-1693421082.011a60f
- Nitro Version:    2.6.3-28223518.83e980b
- Package Manager<EMAIL_ADDRESS>

@DamianGlowala since it's a nuxt-cli problem i continued in an existing issue there: https://github.com/nuxt/cli/issues/99
but as mentioned last week, you can get it to run properly just by adding --https in the dev script of package.json: "dev": "nuxt dev --https".

fixed with nuxi 3.8.0 https://github.com/nuxt/cli/pull/146


Not able to inject http request headers into client.js

This is a continuation of https://github.com/jupyter/jupyter-js-services/issues/132 with the new recommended test client.   Here's the current example of the HTTP request not passing HTTP headers...
The following installs the new client code:
rm -rf ~/kernel_gateway_demos
cd ~
git clone https://github.com/jupyter/kernel_gateway_demos
cd ~/kernel_gateway_demos/node_client_example
npm install

In ~/kernel_gateway_demos/node_client_example create client2.js based on https://github.com/jupyter/kernel_gateway_demos/blob/master/node_client_example/client.js  with minor modifications based on the use of the ajaxSettings variable.   It looks like this:
// Copyright (c) Jupyter Development Team.
// Distributed under the terms of the Modified BSD License.

var xmlhttprequest = require('xmlhttprequest');
var ws = require('ws');
var fs = require('fs');

global.XMLHttpRequest = xmlhttprequest.XMLHttpRequest;
global.WebSocket = ws;

var PYTHON_EXAMPLE = fs.readFileSync('example.py', {encoding: 'utf-8'});
var SCALA_EXAMPLE = fs.readFileSync('example.scala', {encoding: 'utf-8'});

var jupyter = require('jupyter-js-services');

var kg_host = process.env.GATEWAY_HOST || '<IP_ADDRESS>:8888';
var baseUrl = 'http://' + kg_host;
var demo_lang = process.env.DEMO_LANG === 'scala' ? 'scala' : 'python';
var demo_code = (demo_lang === 'scala') ? SCALA_EXAMPLE : PYTHON_EXAMPLE;

var ajaxSettings = {
    user: 'test-user',
    password: 'test-password',
    requestHeaders: {
        'X-Spark-service-instance-id': 'test-instance-id'
    }
}

console.log('Targeting server:', kg_host);
console.log('Using demo lang:', demo_lang);

// get info about the available kernels and start a new one
jupyter.getKernelSpecs({ baseUrl:  baseUrl}).then((kernelSpecs) => {
    console.log('Available kernelspecs:', kernelSpecs);
    var options = {
        baseUrl: baseUrl,
        name: demo_lang,
        ajaxSettings: ajaxSettings,
    };
    // request a kernel in the default language (python)
    console.log('Starting kernel:', demo_lang)
    jupyter.startNewKernel(options).then((kernel) => {
        // execute some code
        console.log('Executing sample code');
        var future = kernel.execute({ code: demo_code  } );
        future.onDone = () => {
            // quit when done
            process.exit(0);
        };
        future.onIOPub = (msg) => {
            // print received messages
            console.log('Received message:', msg);
        };
    });
});

Then run:
export GATEWAY_HOST=dev.spark.bluemix.net:8000/jupyter/v1
cd ~/kernel_gateway_demos/node_client_example
DEMO_LANG=python node client2.js

For your test, you may need to change the value of GATEWAY_HOST to a webserver where you can inspect the HTTP headers sent.
The Nginx log shows that this is what was in the request:
GET /jupyter/v1/api/kernelspecs?1461017685992 HTTP/1.1
User-Agent: node-XMLHttpRequest
Accept: */*
Host: dev.spark.bluemix.net:8000
Connection: close

The HTTP headers were not sent.

Ah, your original request for the kernelspecs had no ajaxSettings, you need to pass the ajaxSettings as jupyter.getKernelSpecs({ baseUrl:  baseUrl, ajaxSettings: ajaxSettings})

(I was able to get the demo working again, thank you @parente)

@blink1073 good eyes.
We should probably add an error function to the demo so it doesn't just exit silently, but rather logs whatever it can first.

Your reference to jupyter.getKernelSpecs({ baseUrl: baseUrl, ajaxSettings: ajaxSettings})  leaves a lot to the imagination.  Can you cite an example that clearly shows what you mean?

@dockter-84 The demo has a whole sequence of calls from asking what types of kernels are available to requesting a kernel to sending code to execute to that kernel.
The getKernelSpecs call is the first one to contact the proxy. In your modified sample, you do not pass any ajaxSettings to this call so the proxy does not have any to log. Move the definition of ajaxSettings out of the closure and try passing them to the one getKernelSpecs call in the sample.

@dockter-84 Did the fix work for you? Can we close this one?

Yes, this is now working.  You may close this issue. Thank you!


How to create a custom place to drop elements.

Hi
I'm going to make a custom place, which would be a div, to accept dropped elements. It will not be a tree view. It is just a simple dev. I'll drop elements from treeview, into that div.
How can I do this? Is it possible?

It is like having data-empty-placeholder-enabled. Like you have the div with id 'angular-ui-tree-empty' all the time.

where you able to achieve this? to drag from a tree to an external div?


Issue with no errors

I have raised an issue on stack overflow
   http://stackoverflow.com/questions/28979329/flask10-1-apache-2-4-10-libapache2-mod-wsgi- ubuntu-14-10-permission-denied-for-c/28984787#28984787

I am unable to resolve now, can you be helpful in this ?
Since i am not finding any errors or something to solve the issue

Can you fork this repo and try using it for WSGI and then report back if you're having any errors? Looks like you're starting a demo API with WSGI and this repo can get you started quickly.

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today


Update pipeline-service

OSP-1.10
PaC deployed through OSP-1.10
allow for watcher logging level customization via gitops

I would think we would want to remove tekton-chains at https://github.com/openshift-pipelines/pipeline-service/tree/main/operator/gitops/argocd/pipeline-service/tekton-chains as well @Roming22 and validate that removal via pipeline service CI before updating staging
Admittedly though, I'm a little unclear about how we override openshift-pipelines over at https://github.com/openshift-pipelines/pipeline-service/tree/main/operator/gitops/argocd/pipeline-service/openshift-pipelines so as to install or not install tekton-chains
of course, maybe I'm wrong here .... can you elaborate ?
thanks

@gabemontero I'm not sure I understand why removing tekton-chains is a pre-requiste to upgrading to OSP-1.10.
We certainly want to remove it, sooner than later, but it's going to take some time before it's ready, and if possible I'd like to validate that OSP-1.10 is running smoothly as soon as possible to avoid last minute surprises before the freeze.

I thought PaC and tekton-chains were the same in that we had to install them from upstream to get required levels, but at 1.10 both the PaC and tekton-chains installed by openshift-pipelines were at sufficient levels
What motivated the removal of PaC via https://github.com/openshift-pipelines/pipeline-service/pull/620 to be included, bu not chains ... I would think we would want to be consistent.
Please clarify when you get the chance, but I won't block merge, assuming e2e's pass (they did not on the first go)
/lgtm

and the e2e failed with a gitops hiccup wrt pipeline service:
 pipeline-service-in-cluster-local                 Unknown     Healthy
pipeline-service-in-cluster-local failed with:
[{"lastTransitionTime":"2023-04-25T20:26:09Z","message":"rpc error: code = Unknown desc = `kustomize build .components/pipeline-service/development` failed exit status 1: Error: accumulating resources: accumulation err='accumulating resources from 'git::https://github.com/openshift-pipelines/pipeline-service.git/developer/openshift/gitops/argocd/pipeline-service-storage?ref=14431236de0f1e3d3a9e27c145197d1a45942794': evalsymlink failure on '.components/pipeline-service/development/git::https:/github.com/openshift-pipelines/pipeline-service.git/developer/openshift/gitops/argocd/pipeline-service-storage?ref=14431236de0f1e3d3a9e27c145197d1a45942794' : lstat .components/pipeline-service/development/git::https:: no such file or directory': evalsymlink failure on '/tmp/kustomize-2974330201/developer/openshift/gitops/argocd/pipeline-service-storage' : lstat /tmp/kustomize-2974330201/developer/openshift/gitops/argocd/pipeline-service-storage: no such file or directory","type":"ComparisonError"}]

at first quick glance can't say for certain if it is related to the bump ...
/test appstudio-e2e-tests

@Roming22 can you update the commit message to add "using tls for rds connections" as result of this update ?

/retest

@Roming22 - unfortunately the latest run https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-appstudio_infra-deployments/1725/pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests/1650981219980021760 failed in the same way as what I reported in https://github.com/redhat-appstudio/infra-deployments/pull/1725#issuecomment-1522401433
I think that points to gitops / kustomize is not happy with something in pipeline-service between 062d00d304d6fba316085784f3b948217fc99d12 and 14431236de0f1e3d3a9e27c145197d1a45942794
By rough count I see 21 or 22 commits between those 2 commits, so if I am correct there is a large set to choose from, unless the error message wrt pipeline-service-storage helps narrow it down

The external secrets for Pipelines as Code probably need to be updated. I think the PR as is will break staging because PaC will be deployed in the openshift-pipelines namespace.

@Mo3m3n @adambkaplan Comments processed. SHA updated, and there's no references to the pipelines-as-code namespace anymore.
> kustomize build components/pipeline-service/staging/base | grep -c "namespace: pipelines-as-code"
0

/lgtm

pr needs a rebase @Roming22
do you want to do it, or I can hit the "update with rebase" button if you like

/lgtm

@Roming22 I have just found that you also need to update this line https://github.com/redhat-appstudio/infra-deployments/blob/main/hack/secret-creator/create-plnsvc-secrets.sh#L27 to match this change done here in pipeline-service https://github.com/openshift-pipelines/pipeline-service/commit/b5f1dc20c3dd8980825c2255cacc85da77ea3460#diff-f394b1c9744cc285b6ac80384e967bd73210dd72a905e1ad7581b8ecab4e3773R201
Basically when switching to the helm based postgres deployment the name of the db service changed too (for dev mode). That's why I suggested in my comment to also add to the commit message that we are enabling tls with this update and using Helm for postgres deployment

/lgtm

/retest appstudio-e2e-tests

/lgtm

/lgtm

/retest

Tests are failing because the build component is referencing the pipelines-as-code namespace. Waiting on a new version of build from @psturc that will be use the openshift-pipelines namespace instead.
The Pr will need to be updated to include the new build version.

Another places where the code should be changed due to change of namespace:

hack/build/setup-pac-integration.sh
components/authentication/base/build.yaml ?
components/cluster-secret-store/base/appsre-stonesoup-vault-secret-store.yaml ?
components/sprayproxy/staging/add-backends.yml
(with ? should probably stay for now to not break prod -> but could cause some issues on stage)

It seems CI is still failing due to PAC
 [mvp-demo-suite MVP Demo tests] MVP Demo Chapter 2 - advanced pipeline, JVM rebuild, successful release [It] upgrading to SLSA level 3 customizable pipeline triggers creation of a PR in the sample repo [mvp-demo, mvp-demo-chapter-2]
/tmp/tmp.AyzcdtidFU/tests/mvp-demo/mvp-demo.go:344

[FAILED] Timed out after 300.000s.
  timed out when waiting for init PaC PR to be created

And looking into infra-deployment code there are still references to the old PAC NS:
https://github.com/redhat-appstudio/infra-deployments/blob/5f86b503a2126576b79b0c407752a09234bc11f2/hack/build/setup-pac-integration.sh#L51
https://github.com/redhat-appstudio/infra-deployments/blob/5f86b503a2126576b79b0c407752a09234bc11f2/hack/build/setup-pac-integration.sh#L81
Also components like authentication, sprayproxy they still have pipelines-as-code ns hardcoded

@Mo3m3n - we minimally need #1737 to merge in order to pick up @mmorhun 's fix for with namespace PaC is installed in. It has not merged as I type this comment.

@Roming22 just pulled ^^ into this PR :-)

For what you noted with https://github.com/redhat-appstudio/infra-deployments/tree/main/components/authentication and https://github.com/redhat-appstudio/infra-deployments/tree/main/components/sprayproxy yes that is part of what @Michkov noted in #1725 (comment)
I would say @Roming22 each of those need to be addressed as part of this PR
Once all that happens, we can see about rebase/retest and try to merge

@Michkov I believe I've updated all references to pipelines-as-code. I tried to make sure not to impact production by patching where necessary.

the last CI failure needs https://github.com/redhat-appstudio/infra-deployments/pull/1579
we just (possibly re-)triaged that mvp-demo failure in https://redhat-internal.slack.com/archives/C02FANRBZQD/p1682697746956539

hopefully https://github.com/redhat-appstudio/e2e-tests/pull/488 fixes this

/lgtm

more new unrelated flakes being discussed in slack (I've asked QE to open blocking bugs and put skips in these failing tests until they are sorted out).
/retest

the latest failure is in some of the pipelines as code e2e code, so in theory could be related to this bump, as we are pulling in a new version of PaC, one which is installed by the openshift pipelines operator instead of upstream yaml
the pac logs, especially the controller, do not have a lot in them
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/redhat-appstudio_infra-deployments/1725/pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests/1652307069509832704/artifacts/appstudio-e2e-tests/redhat-appstudio-hypershift-gather/artifacts/pods/openshift-pipelines_pipelines-as-code-controller-5866597c4c-mjp5l_pac-controller.log
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/redhat-appstudio_infra-deployments/1725/pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests/1652307069509832704/artifacts/appstudio-e2e-tests/redhat-appstudio-hypershift-gather/artifacts/pods/openshift-pipelines_pipelines-as-code-watcher-7848847bf6-qxvr4_pac-watcher.log
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/redhat-appstudio_infra-deployments/1725/pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests/1652307069509832704/artifacts/appstudio-e2e-tests/redhat-appstudio-hypershift-gather/artifacts/pods/openshift-pipelines_pipelines-as-code-webhook-6b4f79686c-lgvcl_pac-webhook.log
maybe github throttling but is hard to say

/retest

I see the same timed out when waiting for init PaC PR to be created error @Roming22  .... with minimal activity in the PaC pods
By comparison, https://github.com/redhat-appstudio/infra-deployments/pull/1741 is showing green with the older version of PaC.
Might be time to try out this locally, work with @psturc and @flacatus to understand the details of this test, see where the breakdown is.

Issue in build-service:
{"level":"error","ts":"2023-04-30T23:29:58.624Z","logger":"ComponentOnboarding.PaC-setup","caller":"controllers/component_build_controller_pac.go:415","msg":"failed to get Component PaC repository object","controller":"component","controllerGroup":"appstudio.redhat.com","controllerKind":"Component","Component":{"name":"test-mvp-component-kpta","namespace":"mvp-demo-dev-namespace-cbpg-tenant"},"namespace":"mvp-demo-dev-namespace-cbpg-tenant","name":"test-mvp-component-kpta","reconcileID":"9a13383c-095c-4cdc-91f8-a7a4898f6f74","action":"VIEW","error":"no matches for kind \"Repository\" in version \"pipelinesascode.tekton.dev/v1alpha1\"","stacktrace":"github.com/redhat-appstudio/build-service/controllers.(*ComponentBuildReconciler).ensurePaCRepository\n\t/opt/app-root/src/controllers/component_build_controller_pac.go:415\ngithub.com/redhat-appstudio/build-service/controllers.(*ComponentBuildReconciler).ProvisionPaCForComponent\n\t/opt/app-root/src/controllers/component_build_controller_pac.go:113\ngithub.com/redhat-appstudio/build-service/controllers.(*ComponentBuildReconciler).Reconcile\n\t/opt/app-root/src/controllers/component_build_controller.go:297\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:235"}

{"severity":"error","timestamp":"2023-05-02T16:51:35.531Z","logger":"pipelines-as-code-webhook.ValidationWebhook","caller":"controller/controller.go:566","message":"Reconcile error","knative.dev/traceid":"78b06509-0c86-464b-8b97-034e745398df","knative.dev/key":"validation.pipelinesascode.tekton.dev","duration":0.000023802,"error":"secret \"pipelines-as-code-webhook-certs\" is missing \"ca-cert.pem\" key","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/pkg/controller/controller.go:566\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/pkg/controller/controller.go:543\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/pkg/controller/controller.go:491"}
-> "error":"secret "pipelines-as-code-webhook-certs" is missing "ca-cert.pem" key"
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/redhat-appstudio_infra-deployments/1725/pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests/1653436401850519552/artifacts/appstudio-e2e-tests/redhat-appstudio-hypershift-gather/artifacts/pods/openshift-pipelines_pipelines-as-code-webhook-6b4f79686c-bsvr2_pac-webhook.log

So still the same error.
@Roming22 - so in my local repro of this, I killed the build-service pod, and when it restarted, it no longer got the no matches for kind \"Repository\" in version \"[pipelinesascode.tekton.dev/v1alpha1](http://pipelinesascode.tekton.dev/v1alpha1)errors and the Repository object was created in the test namespace (which I had left up) after it was missing during the test failure
I wonder if this is a startup order sort of thing, where the build-service initializes its client before the openshift-pipelines operator has "fully installed things", where as previously, PaC was getting created by pipeline-service directly
Here are the current sync-waves I see for the two:
gmontero ~/go/src/github.com/redhat-appstudio/infra-deployments  (main)$ find . -name "*.yaml" -exec grep -s -H sync-wave {} \;
./components/build-service/base/external-secrets/pipelines-as-code-secret.yaml:    argocd.argoproj.io/sync-wave: "-1"
./components/pipeline-service/base/external-secrets/pipelines-as-code/pipelines-as-code-secret.yaml:    argocd.argoproj.io/sync-wave: "-1"
./components/pipeline-service/base/external-secrets/tekton-results/tekton-results-database.yaml:    argocd.argoproj.io/sync-wave: "-1"
./components/pipeline-service/base/external-secrets/tekton-results/tekton-results-s3.yaml:    argocd.argoproj.io/sync-wave: "-1"

{"severity":"error","timestamp":"2023-05-02T16:51:35.531Z","logger":"pipelines-as-code-webhook.ValidationWebhook","caller":"controller/controller.go:566","message":"Reconcile error","knative.dev/traceid":"78b06509-0c86-464b-8b97-034e745398df","knative.dev/key":"validation.pipelinesascode.tekton.dev","duration":0.000023802,"error":"secret \"pipelines-as-code-webhook-certs\" is missing \"ca-cert.pem\" key","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/pkg/controller/controller.go:566\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/pkg/controller/controller.go:543\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\t/go/src/github.com/openshift-pipelines/pipelines-as-code/vendor/knative.dev/pkg/controller/controller.go:491"} -> "error":"secret "pipelines-as-code-webhook-certs" is missing "ca-cert.pem" key"
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/redhat-appstudio_infra-deployments/1725/pull-ci-redhat-appstudio-infra-deployments-main-appstudio-e2e-tests/1653436401850519552/artifacts/appstudio-e2e-tests/redhat-appstudio-hypershift-gather/artifacts/pods/openshift-pipelines_pipelines-as-code-webhook-6b4f79686c-bsvr2_pac-webhook.log

looks like we officially have multiple problems

Closed in favor of #1769
We'll be taking baby steps:

Deploy OSP 1.10 without any changes to PaC
Update PaC and tekton-chains images to use images built by Red Hat
Deploy tekton-results through the operator
Deploy tekton-chains through the operator


Support features across more platforms

Builds on #725, so merge that first.

Exposes utsname on all platforms
Expose sendfile on DragonFlyBSD, FreeBSD, MacOS/iOS
Expose signalfd on Android

sendfile has a different signature on FreeBSD than on Linux, so the build is failing.

@asomers Yep, I should've labeled this as WIP as I just wanted to run these through CI to see where things would break. I'll reduce this PR to things that require almost no changes and then file issues for the rest so we can track them. This should end up being a rather small PR at the end of it.

bors r+


Add symlinks to top-level LICENSE file

After migration to workspace, each binary subcrates didn't include the LICENSE file, which rust2rpm complains:
  ERROR: No license files were detected. In almost all cases, this is an issue
         with the upstream project that should be reported.

This adds symlinks to the top-level LICENSE file so they are properly included.

Thanks!


I see connector extension in the code but i cant see it in the editor ??

Hi,
I see connector extension in the extensions folder , but i dont see it in the toolbar though ? Is it currently being worked ?
Thanks

I have the same question

Not supporting extensions for the time being.


Push not sent using parse client code IOS

Hi,
Im not receiving the push on my device using the push client code below on other IOS device.
PFPush *push = [[PFPush alloc] init];
        NSString *to = [[[AppDelegate appDelegate].sendTo componentsSeparatedByString:@"@"] firstObject];

        [push setChannel:[NSString stringWithFormat:@"z%@",to]];

        [push setMessage:@"dscxvx"];

        [push sendPushInBackgroundWithBlock:^(BOOL succeeded, NSError * __nullable error) {

            if (succeeded) {

                NSLog(@"succeeded");

            }

            NSLog(@"error==%@",error.localizedDescription);

        }];

Below are some observations that i feel are correct so that i should receive a push but unfortunately it doesnt.

I have enabled the client key in parse website(settings push).

The channels are set in core for both the IOS device along with the device tokens

I have cross checked the channel name set in my IOS code with the one set in parse website core section.

When check the push section in parse web site it shows the push as sent to 0 devices.

Also The push works when i send it from parse website to all devices and by rest api too using postman extension for chrome.

In the above code "succeeded" is printed in console and error is Null.That shows push is sent but was never delivered to any device.

Only sending the push through client code doesn't work for me.
My Email id registered with parse is<EMAIL_ADDRESS>case you need to check the above information i cited.
Please help.
Thanks,
AD

Thanks for the report! We'll definitely look into it. Have you verified that your channels are correct? It would appear your stringWithFormat: has a 'z' preceding it, I assume that is intentional?
Also if you could create a small reproducing project here on github, it would greatly help us track down this bug.

Hi Richard,
I have figured out the problem as the channel name used had alp lower case
letters and I was sending the push to a channel with capital letters.
Thanks for help.
On Aug 24, 2015 10:38 PM, "Richard Ross"<EMAIL_ADDRESS>wrote:

Thanks for the report! We'll definitely look into it. Have you verified
that your channels are correct? It would appear your stringWithFormat:
has a 'z' preceding it, I assume that is intentional?
Also if you could create a small reproducing project here on github, it
would greatly help us track down this bug.
—
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/94#issuecomment-134303431
.


[MINOR][SQL][DOCS] Fix docs of Dataset.scala and SQLImplicits.scala.

What changes were proposed in this pull request?
This PR fixes a sample code, a description, and indentations in docs.
How was this patch tested?
Manual.

Test build #59672 has started for PR 13420 at commit d208bc7.

Test build #59672 has finished for PR 13420 at commit d208bc7.

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

Merged build finished. Test PASSed.

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

LGTM I'll add the semicolon master 2.0

Thank you, @srowen and @andrewor14 !


Updating out of date @types/mocha packages

Which problem is this PR solving?

Short description of the changes

Codecov Report

Merging #939 into master will increase coverage by 0.97%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #939      +/-   ##
==========================================
+ Coverage   94.92%   95.90%   +0.97%
==========================================
  Files         248      218      -30
  Lines       11183     9907    -1276
  Branches     1069      841     -228
==========================================
- Hits        10616     9501    -1115
+ Misses        567      406     -161

Impacted Files
Coverage Δ

...ckages/opentelemetry-core/src/common/NoopLogger.ts
60.00% <0.00%> (-20.00%)
:arrow_down:

...metry-core/src/trace/instrumentation/BasePlugin.ts
81.57% <0.00%> (-5.27%)
:arrow_down:

...es/opentelemetry-exporter-collector/test/helper.ts

...ry-context-zone-peer-dep/src/ZoneContextManager.ts

...lugin-user-interaction/src/enums/AttributeNames.ts

packages/opentelemetry-plugin-mongodb/src/types.ts

...kages/opentelemetry-web/src/StackContextManager.ts

...try-plugin-user-interaction/src/userInteraction.ts

...ages/opentelemetry-exporter-collector/src/types.ts

...entelemetry-plugin-xml-http-request/src/version.ts

... and 22 more


npm run package: Cannot find module ../dist

I'm trying to package a new electron app I'm building and I'm getting the following error:
macOS Sierra
node: 3.10.7
npm: v6.6.0
# npm run package

><EMAIL_ADDRESS>package /Users/erik/Dropbox/home/git/ddt-iframe/cluster-report
> cross-env NODE_ENV=production node -r babel-register -r babel-polyfill package.js

module.js:457
    throw err;
    ^

Error: Cannot find module '../dist'
    at Function.Module._resolveFilename (module.js:455:15)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/erik/Dropbox/home/git/ddt-iframe/cluster-report/node_modules/.bin/cross-env:3:1)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)

npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/Cellar/node/6.6.0/bin/node" "/usr/local/bin/npm" "run" "package"
npm ERR! node v6.6.0
npm ERR! npm  v3.10.7
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>package: `cross-env NODE_ENV=production node -r babel-register -r babel-polyfill package.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>package script 'cross-env NODE_ENV=production node -r babel-register -r babel-polyfill package.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron-react-boilerplate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=production node -r babel-register -r babel-polyfill package.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron-react-boilerplate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron-react-boilerplate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/erik/Dropbox/home/git/ddt-iframe/cluster-report/npm-debug.log

npm-debug.log.txt

What is inside of ../dist?

It's not any of my code.  Looks like it's part of electron-react-boilerplate.
✗ ag '../dist'
app/app.html
11:        link.href = '../dist/style.css';
22:        script.src = (process.env.HOT) ? `http://localhost:${port}/dist/bundle.js` : '../dist/bundle.js';

README.md
93:<link rel="stylesheet" href="../node_modules/bootstrap/dist/css/bootstrap.css" />
94:<link rel="image/svg+xml" href="../node_modules/bootstrap/dist/fonts/glyphicons-halflings-regular.eot" />

webpack.config.development.js
20:    publicPath: `http://localhost:${port}/dist/`

webpack.config.production.js
15:    publicPath: '../dist/'

dist is generated by the boilerplate. I would recommend checking out our installation guide solutions.

Did the solutions end up helping?

Yes it did!  Thank you!

Great! Which solution helped you? This repo has a lot of installation failures so it any kind of feedback is really helpful. Thanks!

Clearing the cache did the trick. Maybe package also those commands into a "fixit" script?

That would be a bit difficult. There are different solutions for each OS. Most of the installation issues are OS specific.

Awesome @amilajack, I can confirm this worked for me as well. Thanks!


TypeError: Cannot read property 'length' of undefined     at /Users/mac/Documents/Arduino/esp32_audio-master/server/src/index.js:22:35

could you please help me on it?
TypeError: Cannot read property 'length' of undefined
at /Users/mac/Documents/Arduino/esp32_audio-master/server/src/index.js:22:35

This looks like you are posting something to the server that it doesn't understand. Have you modified the firmware code?
The only line in the code that uses length is:
console.log(`Got ${req.body.length} I2S bytes`);

Which should be logging out the length of the post body that was sent to the server.

thank you for the response cgreening,
but the problem is from req.body is undefined i dont understand why?
// route to handle samples from the I2S microphones - 32 bit stereo channel samples
app.post('/i2s_samples', function (req, res) {
// tslint:disable-next-line:no-console
console.log("req.body "+req.body)
console.log("Got " + req.body.length + " I2S bytes");
fs.appendFile('i2s.wav', req.body, function () {
res.send('OK');
});
});

"use strict";
exports.__esModule = true;
var express = require("express");
var body_parser_1 = require("body-parser");
var fs = require("fs");
var app = express();
var port = 10000; // default port to listen
app.use(body_parser_1["default"].raw({
// inflate: true,
type: '/'
}));
// route to handle samples from the ADC - 16 bit single channel samples
app.post('/adc_samples', function (req, res) {
// tslint:disable-next-line:no-console
console.log("Got " + req.body.length + " ADC bytes");
fs.appendFile('adc.raw', req.body, function () {
res.send('OK');
});
});
// route to handle samples from the I2S microphones - 32 bit stereo channel samples
app.post('/i2s_samples', function (req, res) {
// tslint:disable-next-line:no-console
console.log("Got " + req.body.length + " I2S bytes");
fs.appendFile('i2s.raw', req.body, function () {
res.send('OK');
});
});
// start the Express server
app.listen(port, '<IP_ADDRESS>', function () {
// tslint:disable-next-line:no-console
console.log("server started at http://<IP_ADDRESS>:" + port);
});
this is the error...
TypeError: Cannot read property 'raw' of undefined
at Object. (/Users/mac/Documents/Arduino/esp32_audio-master/server/src/index.js:9:34)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

It's a little confusing as the code you've posted doesn't match up to what I see when I look in the dist folder at the compiled typescript. This may just be different versions of node causing the problem.
Can you walk me through the steps you are running to get the code and run it?
When you checkout the repo do you run:
cd server
yarn

This should install all the dependencies.
And then run:
yarn start

To start the server?

i used tsc index.ts then node index.js

i'm beginner with nodejs...
there is a possibility to use python flask like this?
@app.route('/i2s_samples', methods=['POST'])
def i2s_samples():
logger.info("welcome to upload`")
if request.method == "POST":
f = open('i2s_samples.wav', 'wb+')
#print(request.data)
#f.write(request.data)
scipy.io.wavfile.write('i2s_samples.wav', 16000, request.data)
f.close()
return ''
i tested it but the saved file look wrong can you help me to fix this code?

I think if you run with the instructions I gave you should get something that works.
cd server
yarn install
yarn start

For your python code, I think that request.data will be bytes but the data coming in will be 16-bit data. So you'll need to convert it somehow if you want to use the wavfile function.
Saving the raw data should work, but I'm not really an expert with flask.

error TS18003: No inputs were found in config file '/Users/mac/Documents/Arduino/esp32_audio-master/server_/tsconfig.json'. Specified 'include' paths were '["src/**/*"]' and 'exclude' paths were '["dist"]'.
Found 1 error.
i used yarn install and yarn start bu this is the error:
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

(esp32) MacBook-Pro-de-mac:server mac$ yarn install
yarn install v1.22.10
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.13s.
(esp32) MacBook-Pro-de-mac:server mac$ yarn start
yarn run v1.22.10
$ yarn run build
$ tslint -c tslint.json -p tsconfig.json --fix
$ tsc
src/index.ts:5:13 - error TS2349: This expression is not callable.
Type 'typeof e' has no call signatures.
5 const app = express();
~~~~~~~
src/index.ts:1:1
1 import * as express from 'express';
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Type originates at this import. A namespace-style import cannot be called or constructed, and will cause a failure at runtime. Consider using a default import or import require here instead.
src/index.ts:16:27 - error TS7006: Parameter 'req' implicitly has an 'any' type.
16 app.post('/adc_samples', (req, res) => {
~~~
src/index.ts:16:32 - error TS7006: Parameter 'res' implicitly has an 'any' type.
16 app.post('/adc_samples', (req, res) => {
~~~
src/index.ts:25:27 - error TS7006: Parameter 'req' implicitly has an 'any' type.
25 app.post('/i2s_samples', (req, res) => {
~~~
src/index.ts:25:32 - error TS7006: Parameter 'res' implicitly has an 'any' type.
25 app.post('/i2s_samples', (req, res) => {
~~~
Found 5 errors.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I've just pushed up a new version of package.json to make sure it uses the locally installed version of tsc.
Can you pull it down and see if it works.
This is what you should be seeing:
/tmp/esp32_audio/server (master)$ yarn install
yarn install v1.22.5
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.12s.
/tmp/esp32_audio/server (master)$ yarn start
yarn run v1.22.5
$ yarn run build
$ tslint -c tslint.json -p tsconfig.json --fix
$ tsc
$ node .
server started at http://<IP_ADDRESS>:5003

many thanks cgreening, now the server is working...
but can you please give me an ida how i can read the generated raw files ???

the soud is very poor how can i improve it?

Make sure when you are importing into Audacity you get the settings correct - the Encoding, Byte Order, number of channels and sample rate all need to match what you have recorded.

Encoding: Signed 16 bit PCM,
Byte Order: Little Endian
Channels: 1 Channel (if you are only capturing the left or right channel), 2 Channel (if you are capturing both left and right)
Sample rate: 16kHz sample rate


Dynamic library build error

on the current latest version v2.22.0
Ubuntu 20.04.6
I want to integrate this lib with my project so
I tried to build a dynamic version of the library as it is mentioned in the readme file
Dynamic library
To build dynamic version of library configure with following option added
cmake -S. -Bbuild -D'BUILD_SHARED_LIBS=ON'
cmake --build build

but I got the following error:
`depthai-core$ sudo cmake --build build
-- Using existing generated toolchain
-- Using toolchain file: /home/razan/Desktop/VGD/virtual-guidedog/Localization/ORB_SLAM3/Thirdparty/depthai-core/build/generated/toolchain.cmake
-- [hunter] Calculating Toolchain-SHA1
-- [hunter] Calculating Config-SHA1
-- [hunter] HUNTER_ROOT: /root/.hunter
-- [hunter] [ Hunter-ID: cb0ea1f | Toolchain-ID: a3a48bb | Config-ID: 66f7275 ]
-- [hunter] NLOHMANN_JSON_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: 3.9.1)
-- [hunter] XLINK_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: luxonis-2021.4.2-develop)
-- [hunter] BZIP2_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: 1.0.8-p0)
-- [hunter] FP16_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: luxonis-0.0.0)
-- [hunter] LIBARCHIVE-LUXONIS_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: hunter-3.5.2)
-- [hunter] SPDLOG_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: 1.8.2)
-- [hunter] ZLIB_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: 1.2.11-p2)
-- [hunter] BACKWARD_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: 1.6)
-- [hunter] LIBNOP_ROOT: /root/.hunter/Base/cb0ea1f/a3a48bb/66f7275/Install (ver.: 1.0-ec8f75a)
-- Checking file: /home/razan/Desktop/VGD/virtual-guidedog/Localization/ORB_SLAM3/Thirdparty/depthai-core/shared/depthai-shared/src/datatype/DatatypeEnum.cpp
-- Checking file: /home/razan/Desktop/VGD/virtual-guidedog/Localization/ORB_SLAM3/Thirdparty/depthai-core/shared/depthai-shared/src/utility/Checksum.cpp
-- Performing Test FLAG-Wformat=2
-- Performing Test FLAG-Wformat=2 - Success
-- Performing Test FLAG-Werror=self-assign-field
-- Performing Test FLAG-Werror=self-assign-field - Failed
-- Performing Test FLAG-Werror=unused-lambda-capture
-- Performing Test FLAG-Werror=unused-lambda-capture - Failed
-- Performing Test FLAG-Werror=return-type
-- Performing Test FLAG-Werror=return-type - Success
-- Performing Test FLAG-Werror=non-virtual-dtor
-- Performing Test FLAG_-Werror=non-virtual-dtor - Success
-- Performing Test FLAG_-Werror=sign-compare
-- Performing Test FLAG_-Werror=sign-compare - Success
-- Performing Test FLAG_-Werror=reorder
-- Performing Test FLAG_-Werror=reorder - Success
-- Performing Test FLAG_-Werror=switch-enum
-- Performing Test FLAG_-Werror=switch-enum - Success
-- Compiling depthai-core resources in PATCH_ONLY mode
-- Downloading Depthai device side binaries from server...
-- Downloading depthai and patch
-- commit: aa3e0564c0de3ef66cb6b240ff2b65ed3ed70aba
-- File already downloaded (resources): depthai-shared-commit-hash-a555263a9dbff1166088bcb758ab4306dca9ae1a.txt
CMake Warning at cmake/DepthaiDownloader.cmake:201 (message):
depthai-shared codebases differ between device and host.  Enforce (CI):
(device: 52fb1b4c0ada7d57c9999822a6b8f4c81bf6932b, host:
aa3e0564c0de3ef66cb6b240ff2b65ed3ed70aba
Call Stack (most recent call first):
CMakeLists.txt:338 (DepthaiDownload)
-- Downloading and checking depthai-device-fwp.tar.xz
-- File already downloaded (resources): depthai-device-fwp-a555263a9dbff1166088bcb758ab4306dca9ae1a.tar.xz
-- Downloading depthai bootloader
-- folder: /home/razan/Desktop/VGD/virtual-guidedog/Localization/ORB_SLAM3/Thirdparty/depthai-core/build/resources
-- maturity: release
-- commit_version_arg: 0.0.21
-- bootloader shared commit: b287ecbacd3b0c963b5dfcf95767123b0c143b57
-- File already downloaded (resources): depthai-bootloader-shared-commit-hash-0.0.21.txt
-- depthai-bootloader-shared between device and host MATCH!. (device: b287ecbacd3b0c963b5dfcf95767123b0c143b57, host: b287ecbacd3b0c963b5dfcf95767123b0c143b57
-- Downloading and checking depthai-bootloader-fwp.tar.xz
-- File already downloaded (resources): depthai-bootloader-fwp-0.0.21.tar.xz
-- LIST OF RESOURCE COMPILED FILES: /home/razan/Desktop/VGD/virtual-guidedog/Localization/ORB_SLAM3/Thirdparty/depthai-core/build/resources/depthai-device-fwp-a555263a9dbff1166088bcb758ab4306dca9ae1a.tar.xz;/home/razan/Desktop/VGD/virtual-guidedog/Localization/ORB_SLAM3/Thirdparty/depthai-core/build/resources/depthai-bootloader-fwp-0.0.21.tar.xz
-- ClangFormat: clang-format not found! Target 'clangformat' not available...
-- ClangFormat: clang-format not found! Target 'clangformat' not available...
-- OpenCV and required libraries (opencv_core;opencv_imgproc) found.  Thanks :)

@razanhuss remove the Hunter cache as per readme and retry. That should address this issue

@themarpe thanks for your reply, I have already run this command rm -rf ~/.hunter to remove the hunter cache and deleted the build folder then tried to build it again and had the same error.
any other suggestions?

@razanhuss what is you platform?
Try -D HUNTER_ROOT=[path to build dir]/.hunter along the CMake args, and before remove the build directory

/root/.hunter/
Perhaps you've build with sudo?
remove the exact above dir:
rm -rf /root/.hunter/

And try again.
Then try the above suggestion, but it will probably not be needed

I successfully resolved the issue by updating the hunter config file. Should I proceed with pushing the updated file to the repository, or would it be preferable for someone from the DepthAI development team to handle this task?

@themarpe  dynamic_build_fix_patch.zip
please find my fix in the patch file, it is to apply on the top of the main branch commit [82ab07d037]

@razanhuss please create a fork and open a PR against develop branch
Thought the patch as is, likely won't be accepted - setting CMAKE_POSITION_INDEPENDENT_CODE=ON already happens with pic.cmake toolchain that is applied when building a shared library.
Reason why that isn't working, has to be addressed instead. Unless we forego the pic toolchain altogether and just keep code as -fPIC always (would address some hunter issues as well, which might be preffered)

If you are suggesting to add the following lines at the beginning of the CMake file:
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -fPIC")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC")

Unfortunately, this approach didn't resolve the build error. I have tried various methods, but the only change that effectively fixed the build error was updating the config.cmake for zlib as shown below:
hunter_config(
    ZLIB
    VERSION "1.2.11-p2"
    URL "https://github.com/luxonis/zlib/archive/refs/tags/v1.2.11-p2.tar.gz"
    SHA1 "fb8b6486183b13a86040f793a939b128f6d27095"
    CMAKE_ARGS
        CMAKE_POSITION_INDEPENDENT_CODE=ON  # this line to enable -fPIC flag
)

By including CMAKE_POSITION_INDEPENDENT_CODE=ON in the hunter_config for zlib, the necessary -fPIC flag is applied to all relevant code in the project and its dependencies, effectively resolving the build error and allowing successful creation of shared libraries.

@razanhuss - this is what happens using the pic.cmake toolchain. Are you using your own toolchain file? If so, make sure that that flag (as in pic.cmake) is applied as well

no, I am not using any other than the toolchain file in the repo whose content is
# Simple PIC toolchain, which enables shared library building
# This option is propagated to 3rdparty dependecies as well
set(CMAKE_POSITION_INDEPENDENT_CODE ON)

I tried it now and this seems to be working, but do you believe this is a solution?

@razanhuss when BUILD_SHARED_LIBS=ON this CMake toolchain should be auto applied. I think there might be some caches at play that weren't removed and it caused this. You may retry by deleting both: build folder, as well as hunter (~/.hunter), and then set just build shared libs paramter instead of explicitly setting the cmake toolchain as well.
If the issue remains, then we'll need to check (also, this must be on either latest main or develop - there were some changes compared to previous versions)

I am attempting to integrate the depthai-core library into my main project by following the instructions provided in the README file. The method I'm using involves the add_subdirectory approach. However, even after following the steps outlined in the instructions, I am encountering build errors.
According to the README:

#### Using add_subdirectory

This method is more intrusive but simpler as it doesn't require building the library separately.

Add `add_subdirectory` which points to the `depthai-core` folder **before** the `project` command. Then link to any required targets.

add_subdirectory(${CMAKE_CURRENT_LIST_DIR}/depthai-core EXCLUDE_FROM_ALL)
...
project(my-app)
...
target_link_libraries([my-app] PRIVATE depthai::opencv)

I have made sure to place the add_subdirectory command before the project command in my main project's CMakeLists.txt file, as instructed. However, despite these efforts, the build error persists.
I have successfully built the depthai-core library separately using the commands:
cmake -S. -Bbuild -D'DEPTHAI_BUILD_EXAMPLES=ON'
cmake --build build

However, the build error only occurs when attempting to integrate it into my main project as per the README instructions.
Could you kindly assist me in identifying the cause of this build error and suggest any potential solutions?

@razanhuss are the errors the same as the ones posted above?
Solution is adding the CMAKE_TOOLCHAIN_FILE=[pic.cmake] above add_subdirectory or through parameters. Or linking statically (AKA not using BUILD_SHARED_LIBS=ON)


feature - Exclude headers and response fields from diff

This PR resolves #897
@tommysitu I have raised PR to exclude headers and response fields from diff.
The user will be making a POST call with the body to exclude diff entries. As of now, added support only for JSONPath as our diff properly does diff for JSON response. I didn't use a third-party library as of now to do JSON diff. Our code to do JsonDiff also looks fine but is unable to do diff for particular elements of the array etc.
Also, I have added a provision to exclude headers from API as well.
Remaining: Adding UTs and documentation.
Curl command: curl --location --request POST 'http://localhost:8888/api/v2/diff'
--header 'Content-Type: text/plain'
--data-raw '{
"excludedHeaders":["Date"],
"excludedResponseFields":["$.time"]
}'

I think it's a good experimental feature. Maybe that's all you need to do or maybe not. I don't currently have a use case for diff mode so can't really tell.

To be honest, same for me. I am also not 100% sure about correct use case for the same. Lets see if this works for one who created issue.


cloud-init support

Current SDK Version
5.0.6

Use-cases
For use in production the machine-driver need the ability to configure the vm with a cloud-init configuration
Attempted Solutions
We used the docker-machine-driver in combination with the rancher-machine to create a docker vm (ionis image: ubuntu:20.04) in the ionos datacenter. The vm is created properly and docker will be installed. The problem is, without cloud-init docker will listen on port 2376 on a tcpv6 interface. The machine will not properly deployed because the connect on the ipv4 ip:2376 will fail because no docker daemon is listing.
Also other configuration, for example additional packages that are required for storage provider like nfs-common or the nap client can't be installed/configured at startup
Proposal
Add a parameter to specify a cloud-init user-data configuration.

Hello! This feature is now included in release v6.0.1. You can export a cloud-init user-data config, as a Base64 encoded string to env var IONOSCLOUD_USER_DATA or use flag--ionoscloud-user-data.


Propose SYSCTL Hardening

Thank you to Klaver (https://github.com/klaver/sysctl)

The project is a very interesting source of information, but a little too much for me to understand its implications. Since I have to maintain the servers I create I have a policy of having to understand every line of configuration or command set or ran by the script. Right now I don't feel comfortable merging these configurations. Also much of them are old and I know a lot of things changed since they were recommended so I'd wary of applying them without fully understand the consequences. For now I'll have to decline the merge. Thanks for the suggestion though, I'll use the material linked as a guide for future modifications.


NumBackupsToKeep & CollaborationPreset

Added Config GUI:
*NumBackupsToKeep
*CollaborationPreset
Additional Changes:
*Cleaned up Functions for Easy Config
*Modified Window(s) size for all new GUI's

Meant to post a comment, ended up closing the PR lol.
Cleaned up the new Functions, wording of already implemented functions and cleaned up the ordering of the configs that appear for users during easy config mode.

LinuxCheatSheet incomplete, but not really important atm either that its not complete

Added Formatting to LinuxCheatSheet.
Needs reviewed for typos. Did my best at a quick glance while formatting.


Typescript Helpers

Typescript helpers
It is required to include Typescript helpers to user's plugin list.
What about having a built-in support? + Fixing tsconfig.json setting emitHelpers to false automatically. Making it smooth!

So, my current solution is to use the tslib package and enable importHelpers, but this includes unnecessary helpers.  I had to do this because vscode complains that it can't find the tslib module when I use language constructs that need the helpers.

@xdave I'm interested in this as __rest is not in the TypescriptHelpers plugin.
How did you get the importHelpers flag to work in fusebox?
I tried adding tslib to the project and setting the flag in my tsconfig but it doesn't seem to work.

Use this
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "strict": true,
    "importHelpers": true,
    "lib": ["dom", "es2017"]
  },
  "compileOnSave": false
}

I am not using the TypescriptHelpers pllugin

Thanks it was probably a cache problem it works now.
Le ven. 12 mai 2017 22:02, xdave<EMAIL_ADDRESS>a écrit :

Use this
{
"compilerOptions": {
"target": "es5",
"module": "commonjs",
"strict": true,
"importHelpers": true,
"lib": ["dom", "es2017"]
},
"compileOnSave": false
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fuse-box/fuse-box/issues/145#issuecomment-301172582,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa9-hzrIFKJPLkA4sa4jklRFWYQA1kyks5r5LrigaJpZM4L-nY-
.


update to polkadot-v0.9.18

Checklist:

[x] substrate
[x] polkadot
[x] mvm
[x] cumulus
[x] nimbus
[x] xcm-emulator
[x] other deps
[x] tests

❤🔥 Ready to merge.


cant get it started

'codecrumbs' is not recognized as an internal or external command,
operable program or batch file.
created a dir '\devDependencies', ran yarn

Hey, since you added it as dev dependency you need to add a command to “scripts” section in your package.json and then run it.

yarn add codecrumbs -D
add to package.json
“scripts”: {
“cc”: “codecrumbs -d src -e src/index.js”
}
in terminal run: yarn cc (or npm run cc)

or you can use npx (https://github.com/zkat/npx)

inside /src  i only see index.dev.js

For what project are you trying to use it?
Let's do this example first to understand how everything works:

clone/download to your computer this project https://github.com/lucasbento/react-redux-todo (just as simple example)
install codecrumbs - yarn global add codecrumbs
go to the folder react-redux-todo (where you copied project from step 1)
run codecrumbs -d src -e src/index.js
go to the browser url http://localhost:2018 to see if it works

let me know if this works

that worked,  thank you.  I cloned https://github.com/Bogdan-Lyashenko/codecrumbs.git and this gave problems.

No worries, happy to help :)