A LiveCode+Java+AndroidSDK package

Hello, friends.
I want to learn to program in Android and I have choosen LiveCode.
Is there a package that contains LiveCode, JDK and Android SDK, in a similar way to WAMP and/or JoomlaSpanishServer2?
I ask this because I am having trouble with:
Android HAXM

=== Logging started: 11/08/2019  11:55:25 ===

This computer does not support Intel Virtualization Technology (VT-x) or it is being exclusively used by Hyper-V. HAXM cannot be installed.

Please ensure Hyper-V is disabled in Windows Features, or refer to the Intel HAXM documentation for more information.

=== Logging stopped: 11/08/2019  11:55:26 ===

Java SE Development Kit 8u211
android-studio-ide-183.5522156-windows32.zip
Intel® HAXM installer
Hiper-V
When I read about how to "install" HAXM, I see things as:
Visual Studio 2017
Universal Windows Platform development
Desktop development with C++.
Windows SDK for Windows 10
Windows Driver Kit (WDK) for Windows 10
Note that ... the Windows 10 SDK installed by Visual Studio 2017 ... may not be the latest version.
Enterprise WDK (EWDK) 10 with Visual Studio Build Tools 15.6
NuGet CLI tool (nuget.exe) version 4.x or later
But I only want to run LiveCode 9.x and make programs in it.
Thanks.
HERNAN

Thanks for your report. HAXM mainly supports Android Studio as one of the SDK Tools. We are not sure if there is an all-in-one package contains the tools you want. In order to install HAXM, you don't have to install above software, which packages are for developing or building HAXM from source code. As for the failure of HAXM installation, please see my comment at #228 to resolve the environment issues. Moreover, I noticed that you downloaded the 32-bit Android SDK. Is your operating system Windows 7 32-bit? If so, please refer to the System Requirement for more details to set up your environment.

Fine, Wen.
Yes, I am installing 32bit Android SDK, because I have Win7 32bits. I'll
see 228 and Sys Req as you mention.
My objective is to know LiveCode. As part on the installation, we need to
install Android SDK, and JDK. But when I read (after difficulties) I saw
that I need to install HAXM; as I got error I asked you....(but as I said
in another mail, I have new tryings, and later I'll say to you).
For me that I am not a mobile developer --but want to get that
environment--, it is very difficult to get what I need, because I need to
install a lot of programs... knowing that I only want to learn (first
learn, later earn money, but I understand that learning will get long...).
When I get to know how to program in the language I elected, I understand
that it has to take me a (financial) cost included boring installing and
installings and installings.
But for now I would like to get am simplistic environment as a WAMP-like
package (that would include for mobile environments something like JDK --a
version that can be used--, Android SDK --as complete as needed--, a
SQLite/MySQL/MariaDB, a language as PHP/HTML5/JavaScript, the language I
want: LiveCode and/or KotLin, the web server Apache, and
......................)
If you could say me instructions to me, I would build an utility like I
said... to share.... I would like to ease a knowledge this to people
interested.
Thaks, friend.
HERNAN CANO MARTINEZ
Analista de Sistemas
Cel: 300-782.48.44.
WhatsApp: 300-782.48.44.
El lun., 12 de ago. de 2019 a la(s) 02:50, Wenchao Wang escribió:

Thanks for your report. HAXM mainly supports Android Studio
https://developer.android.com/studio as one of the SDK Tools. We are
not sure if there is an all-in-one package contains the tools you want. In
order to install HAXM, you don't have to install above software, which
packages are for developing or building HAXM from source code. As for the
failure of HAXM installation, please see my comment at #228
https://github.com/intel/haxm/issues/228 to resolve the environment
issues. Moreover, I noticed that you downloaded the 32-bit Android SDK. Is
your operating system Windows 7 32-bit? If so, please refer to the System
Requirement
https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows
for more details to set up your environment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/intel/haxm/issues/229?email_source=notifications&email_token=ABMMTXKRVSQHHOSYA7KTW4LQEEI3ZA5CNFSM4IK4LLI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4BZG5Y#issuecomment-520328055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMMTXLKW2PR2H5EYY22NF3QEEI3ZANCNFSM4IK4LLIQ
.

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Libre
de virus. www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


Feature/iroha build time graph

Description of the Change
[DOPS-116]
This PR allows to view compilation time per target (g++ run time) per each build for all branches, and compare this time to develop tree. After that we have csv file with time difference in seconds and %
Benefits
Developers can detail view and compare time to improve their code.
Possible Drawbacks

For now it is not possible to print cmake output to jenkins console (using tee gives some duplicates in the result file)
When "fuzzingEnabled" is true, there is no results

Usage Examples or Tests [optional]
See attachment diff.csv.zip
Alternate Designs [optional]

Why the build has failed (pr-head)?

@Stayer , can you add this feature to new CI also?

@Stayer , can you add this feature to new CI also?

Ok

General comment form Nikoly to last PR in new CI:

Per each module or file we might need to include license header as described here:
https://wiki.hyperledger.org/community/copyright-and-license-policy
https://www.hyperledger.org/about/charter №13
you can reuse code from here
hyperledger/iroha#1944

Also, per each file it is desired to see what does it do or store. Can we please add just a line or something so that others can quickly understand what a purpose some file serves?

as I understand it will no work with clang?

as I understand it will no work with clang?

yes, you are


Using multiple thread/cores?

Hi.
Thank you for making this amazing tool.
I am currently using this tool to improve my metagenomic viral contigs obtained from MegaHIT.
So, I have 80 shotgun metagenomic samples which I did coassembly in MegaHIT followed by viral contig detection by VirSorter2.
I want to extend my viral contigs by COBRA, but it not showing any progress for the past 6 days.
This is the code I use (I am using my institute cluster)
python cobra.py -f ~/final.contigs.fa -q ~/final.contigs.phages_combined.fna \
-o VirSorter -c ~/CoverM/For_virus/Coverage.txt -m ~/MegaHit_final.contigs.fa.All.sorted.bam \
-a megahit -mink 21 -maxk 77

This is the logfile
1. INPUT INFORMATION
# Assembler: MEGAHIT
# Min-kmer: 21
# Max-kmer: 77
# Overlap length: 77 bp
# Read mapping max mismatches for contig linkage: 2
# Query contigs: /lustre7/home/bhimbiswa/MAGs/Virus/COBRA/final-viral-combined.fa
# Whole contig set: /lustre7/home/bhimbiswa/MAGs/MegaHit/output_folder/final.contigs.fa
# Mapping file: /lustre7/home/bhimbiswa/MAGs/CoverM/For_virus/bam_files/MegaHit_final.contigs.fa.All.sorted.bam
# Coverage file: /lustre7/home/bhimbiswa/MAGs/CoverM/For_virus/Coverage.txt
# Output folder: /lustre7/home/bhimbiswa/MAGs/Virus/COBRA/Virsorter2

2. PROCESSING STEPS
[01/22] [2023/06/07 14:43:28] Reading contigs and getting the contig end sequences. A total of 1259677 contigs were imported.
[02/22] [2023/06/07 14:44:13] Getting shared contig ends.
[03/22] [2023/06/07 14:44:34] Writing contig end joining pairs.
[04/22] [2023/06/07 14:44:35] Getting contig coverage information.
[05/22] [2023/06/07 14:44:39] Getting query contig list. A total of 47249 query contigs were imported.
[06/22] [2023/06/07 14:44:40] Getting contig linkage based on sam/bam. Be patient, this may take long.
[07/22] [2023/06/08 08:29:30] Detecting self_circular contigs.
[08/22] [2023/06/08 09:14:19] Detecting joins of contigs.

I can understand that I have lots of query files that why this is very slow, but is there any way I can make this faster?
P.S.: COBRA worked fine with Phigaro viral contigs (only 285 query contigs).

Hi,
Thank you for your interest in COBRA and the question.
Unfortunately, for now, COBRA could only detect potential joins contig by contig. I understand it is the most time-consuming step, especially when you have a lot of queries. Given that you have 80 related samples (related, I think that's why you co-assembled them), I suggest you assemble them individually for two major reasons, (1) MEGAHIT may generate too many chimeric contigs, our lab has been developing a tool to identify chimeras, MEGAHIT has the highest rate, (2) when you use COBRA on individuals, you may be able to double-check the COBRA sequences with those from different samples, given that COBRA is still under review, reviewers of your manuscript may argue if COBRA is reliable or not (though I am pretty confident about it). Alternatively, you may want to filter the length of your queries to keep those with a minimum length of, for example, 5kbp.
FYI, I tested COBRA on 6,827 queries, the [08/22] step took almost one day to finish. Your maxk is 77, I think there will be more options for the ends that are under the search for join, compared to larger kmers like 141. While on 13,204 contigs, that step took 4.5 days. So there are a lot of factors that will eventually determine the time.

PROCESSING STEPS
[01/22] [2023/04/20 15:48:43] Reading contigs and getting the contig end sequences. A total of 2639765 contigs were imported.
[02/22] [2023/04/20 15:51:13] Getting shared contig ends.
[03/22] [2023/04/20 15:52:16] Writing contig end joining pairs.
[04/22] [2023/04/20 15:52:28] Getting contig coverage information.
[05/22] [2023/04/20 15:52:37] Getting query contig list. A total of 13204 query contigs were imported.
[06/22] [2023/04/20 15:52:38] Getting contig linkage based on sam/bam. Be patient, this may take long.
[07/22] [2023/04/20 17:18:47] Detecting self_circular contigs.
[08/22] [2023/04/20 18:36:11] Detecting joins of contigs. 10%, 20%, 30%, 40%, 50%, 60%, 70%, 80%, 90%, 100% finished.
[09/22] [2023/04/25 09:40:26] Saving potential joining paths.
[10/22] [2023/04/25 09:40:35] Checking for invalid joining: sharing queries.
[11/22] [2023/04/25 09:53:04] Getting initial joining status of each query contig.
[12/22] [2023/04/25 09:53:07] Getting final joining status of each query contig.
[13/22] [2023/04/25 09:53:07] Getting the joining order of contigs.
[14/22] [2023/04/25 09:53:19] Getting retrieved contigs.
[15/22] [2023/04/25 09:53:46] Saving joined seqeuences.
[16/22] [2023/04/25 09:53:59] Checking for invalid joining using BLASTn: close strains.
[17/22] [2023/04/25 10:25:24] Saving unique sequences of "Extended_circular" and "Extended_partial" for joining checking.
[18/22] [2023/04/25 10:25:33] Getting the joining details of unique "Extended_circular" and "Extended_partial" query contigs.
[19/22] [2023/04/25 10:25:42] Saving joining summary of "Extended_circular" and "Extended_partial" query contigs.
[20/22] [2023/04/25 10:26:06] Saving joining status of all query contigs.
[21/22] [2023/04/25 10:26:09] Saving self_circular contigs.
[22/22] [2023/04/25 10:26:09] Saving the new fasta file.

I am happy to talk more.
Best,
LINXING

Dear Linxing
Thank you very much for your kind reply.
I apologize for not replying earlier. I was not able to access GitHub for some time.
I will consider reassembling them individually in metaSpades.
Regards,
Bhim

Dear Linxing
Thank you very much for your kind reply.
I apologize for not replying earlier. I was not able to access GitHub for some time.
I will consider reassembling them individually in metaSpades.
Regards,
Bhim

Hi Bhim, thanks for letting me know. I am happy to help further, just let me know when needed.
Best,
LINXING


Add GitVersion.yml actual binary will come later when it is decided w…

…hich version to use and how to consume it.

:shipit:


feat(partnerships): add various categories and products to STEAM_DECK_ITALIA.md

Pull Request
Compile all the information written below to send a legitimate pull request to the repository!
Label:
This PR is labeled as:
Choose only one and remember to select the label even on the right.

[x] Feature
[ ] Bug
[ ] Other

Linked Issue
This PR has the following linked issues:

Closes /;

Solution
My solution is explained as follows:

Adds new sections;
Adds various new products;
Various corrections.

Looks perfect! Great work!
Welcome as a contributor to Awesome Steam Deck.

Looks perfect! Great work! Welcome as a contributor to Awesome Steam Deck.

Great, thank you very much!


Change layers during animation

I am wondering is it possible to make layers change during animation:
I am trying to animate planets rotating a star with planets passing behind star and passing above star alternating with each other. But I don't want to separate the animation into several parts cause I may have multiple planets.

You could look into changing the z-index of each of the layers in an update() callback.

Thanks, that works!


[FEI-3329].2 Update to Flow 0.145.0

Summary:
Issue: FEI-3329
Test plan:
yarn flow

The parent pull-request ([#428]](https://github.com/Khan/render-gateway/pull/428)) has been merged into master, but this branch (fei3329.2) now has conflicts with the new base branch. These conflicts must be resolved before checks can complete on this pull-request.


Final review JOSS paper

In the paper:
LINE 93: "pytorch" should be written as "PyTorch". You can maintain capitalization in your bib file by using curly brackets around the characters you wish to maintain formatting of.
LINE 101: the "w" in "weibull" should be capitalized
LINE 107: the "p" in "python" should be capitalized
LINE 109: the "c" in "cox's" should be capitalized
LINE 126: the "c" in "cox" should be capitalized
LINE 130 the "c" in "cox" should be capitalized
LINE 144 the "c" in "c-statistic" should be capitalized


check for zombied VirtualBox VMs and destroy them

@RackHD/corecommitters @keedya @tannoa2 @uppalk1

Add @changev to review


upgrade dependencies in ouroboros-network

[x] carano-predule
[x] cardano-base
[x] cardano-ledger-specs

Fixes https://github.com/input-output-hk/ouroboros-network/issues/3025

bors merge


Add support for new aspectRatio option for better handling of responsive maps

This option was just added to datamaps: https://github.com/markmarkoh/datamaps/commit/b89396f2c22dc8a64469de79690f6054dd49da98

I am assuming you only want the src files edited for PRs rather than submitting any updated compiled files?

hey thanks @adrianbj this looks good. I think it's safe to add this ahead of the Datamaps release that actually introduces it (since the datamaps dependency for this module is latest, not master). I will take a peek soon to double check and get this merged.


build: 🏗 Use changesets

What is the purpose of this Pull Request?
Use changesets workflow.
Type of this Pull Request

⚙ Workflow s adjustments
🔧 Configurations changes

Resources

changesets

TODO

[x] Remove everything related to semantic-release
[ ] ...

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
24

Relevant Lines:
24

💛  - Coveralls


How do I recreate vendor folder after cloning the project from github?

I have a jigsaw project that I had committed to github, since the project's vendor/ folder was in .gitignore it did not commit. Now I cloned that project from github to my local machine. How do I recreate the /vendor folder now?

Run composer install from your root folder, and it will create the /vendor directory with all the necessary dependencies.


Move to new project setup

Since VS2017 is out now, is it time to move everything over to the new .csproj setup?

csproj changes: https://github.com/ruant/Swashbuckle.AspNetCore/commit/5bcbcf859c189ba0656a76d3790d95589321a8f8
I also updated everything to asp.net core 1.1 and the dependencies to the latest version: https://github.com/ruant/Swashbuckle.AspNetCore/commit/9ac44438dc1b6258d40ab12d1ade398649ddd1b4
For me it builds and runs fine, so if you want me to create a pull request let me know.
The only thing I noticed was that one of the test projects complained about a constructor, but that must have been there from the start?
Also, I've never migrated a project like this before, so if there something that should be changed let me know 😃

Have it done on a local branch and now trying to resolve some build warnings

Cool!

@domaindrivendev Awesome, let us know if you need help with anything 😃

@domaindrivendev any ideas of a new deadline for the v1.0.0 release?


[5.2] Add whereColumn clause

If we want to compare two columns inside a where clause, we now need to write a raw expression:
User::whereRaw('`first_name` = `last_name`');

But with this PR we can use a new whereColumn method:
User::whereColumn('first_name', 'last_name');

As with normal where clauses, array conditions can be passed as well:
User::whereColumn([
    ['first_name', 'last_name'],
    ['updated_at', '>', 'created_at']
]);

whereColumn doesn't really describe what it does. Maybe something like whereEqualColumns?

Ah, but it's not only about egality. So maybe whereCompareColumns? I can't think of a better name…

or maybe whereUseColumns?

It's supposed to function like a sentence: "where column first_name equals (to the column) last_name".

It's much clearer, once having kept this in mind.

For a regular where you can also pass an array, but there it's an associative array. Having an associative array means you can't specify the operator, but I think that's fair; if you need different operators, call the method multiple times.
Whatever we do, it should be consistent between these two methods.

A while ago a regular where was updated to allow for the syntax I mentioned above. Since whereColumn is using the same array parsing logic as the normal where, it's entirely consistant.

Oh you're right. Didn't know about that.
Learn something new every day :100:


Milestone 1 Review

Here are my feedbacks for Milestone 1:

Draft a Team work contract: Correctness
Where is the email to which we would like to report a possible instance of unacceptable behaviour to?
Also, typo in the word "behaviour".

Project proposal: reasoning
Nice report! The only missing points in my mind are:

How are you going to evaluate your model and selected features?
Which plots do you plan to use for the visualization section and what would you like to infer from those plots?

Exploratory data analysis in a literate code document: QUALITY
Pretty nice! You could also go a bit deeper with your plots and explore different combinations of multiple features. Like people who know HTML and have worked for 5+ years.

Thank you for the valuable feedback Mohamed! We will incorporate these into the current state of the project. Much appreciated.

Hi Mohamad,
Thank you for your valuable feedback. Based on your suggestions, our team has made the following changes:

Teamwork contract was modified with unacceptable behavior examples added. Please check the following link: https://docs.google.com/document/d/15DBToo9IPDK9lSnfAjIwGCgZ5ErsicZvzZNTaLUEuiA/edit

In terms of model evaluation, we compare $R^2$ of training and test data set to assess if the model is robust. Feature selection, so far, is not investigated, but we hope we could have opportunities to do it to improve our research.
Plus, the error analysis plot (Fig 8 in the report) is added to help visualize the prediction capability of our model.

We added one more EDA plot (Fig 7 in the report) which describes both effects of coding years and languages mastered on salary.

Hope you could enjoy it. Many thanks.


lets expose the docker user, name and label as maven properties so we can refer to them inside custom  configurations

lets expose the docker user, name and label as maven properties so we can refer to them inside custom  configurations

[merge]


proposal: add first-class Cross Site Request Forgery protection

Preface
While for other web vulnerabilities the go stdlib provide some quite hardened packages (html/template with autoescaping, net/http with a decent posture against smuggling, tls being easily enforced and older versions not used etc.) there is a lack of first-class support for CSRF protection, and CSRF is the second most prominent vulnerability in modern web applications.
The only bit of library that offers something related to it is x/net/xsrftoken, which is not well known, it is not advertised and it is in the "x" package.
The ecosystem has a proliferation of external packages that provide some form of protection against this vulnerability, so it looks like the current Go stance on this is that if users want to build a secure web application they have to rely on external libraries and frameworks (thus accepting a whole new kind of issues with supply chain attacks) or they have to understand how to build their own protections.
Proposal
I would like to propose to add a first-class supported XSRF protection mechanism in the standard library to address this issue.
Stretch option:
Since it feels to me like CSRF is not the only issue we might have to take care of, I would deem it appropriate to add a security sub-package to net/http (naming and location is open to discussion) to use to collect middleware and other utilities (e.g. creating servers with safe defaults).
Go as it is right now almost delivers the full toolkit needed to build secure web applications, but it definitely has what is needed to build a web application, which constitutes a quite scary scenario.

I would like to propose to add a first-class supported XSRF protection mechanism in the standard library to address this issue.

I think the general answer to "should the standard library be secure by default?" is "yes", but I also don't understand what particular changes you're suggesting :)
Could you outline what changes you're thinking of? I'm ignoring the "stretch option" section for now, because I want to understand the core proposal first.

Some options:

Provide a wrapper/decorator for handlers or Muxes that implements an anti-csrf middleware in the http package
Provide the wrapper above in a separate package, but reference it from the doc in http or find a way to suggest its adoption
Currently http.Request exposes a forest of ways to get form parameters, all types are strings and internal cross-calls are quite confusing. We could add one more way to access form parameters that allows to protect against CSRF and addresses other issues with form parsing, typing and content-type filtering.
Fix the xsrftoken package and link it from the http package
Not really a solution but a decent starting point: document very clearly on the cookie type that people should go and look for anti-CSRF protection if they use cookies for auth.
Change the Cookie type to have a SameSite attribute by default (this has breakage potential and is very risky)
Make the http package suggest protections via logs. This could be on by default (but doesn't have to) and could be toggled with a flag/config. Detecting handlers that need protection can be done by inspecting Fetch Metadata headers to find when handlers are supposed to be only used same-site. We could use heuristics to check if a handler has some sort of CSRF protection but the downside is that we would not detect some of them. This is very invasive if we consider it would log potential security issues to users logs but it would probably detect most vulnerabilities already out there and help people fix them.

I'm also open to other suggestions, these are options that I've been pondering for a while and all have one main issue: people would need to know about them and adopt them.
Protect current users without breakages or behavior changes would be hard and I can't find a reliable way to bring people on board with a new, safe, API without deprecating the old ones or offering a better set of features (e.g. point 3 above, if that offers something better than the other form fields/methods it could help drive adoption).
What do you think?

Doing something in http directly seems like a very significant step.
It would probably be better to focus on "Fix the xsrftoken package and link it from the http package."
By "link it" I assume you mean mention it in the docs.
In general net/http is pretty low-level. Providing a very opinionated approach to XSRF in net/http seems out of place, but doing something great in xsrftoken seems like a good idea.
Over on https://github.com/golang/go/issues/42166, what did you have in mind as a new, less error-prone API?

Ping @empijei. We really need a clearer proposal to evaluate.

I'd be ok with fixing xsrftoken and linking it from the http package docs, it seems like the less invasive solution.
My only concern is that it would not be picked up by many users.

See https://github.com/golang/go/issues/42166#issuecomment-732061886

Moving this to #42166 then. Thanks.


[AVM Module Issue]: Workspace Outputs Overwritten . Returning Object instead of Properties

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Module specific issue

[X] I confirm that this issue is about this AVM module and not about the resource itself, or how to use Terraform.

Issue Type?
Bug
(Optional) Module Version
0.1.3
(Optional) Correlation Id
No response
Description
The commit from a week ago 19543b3fa444353f38bcd1ebd7124683e209f170 has the right references, but the Chore branch: https://github.com/Azure/terraform-azurerm-avm-res-operationalinsights-workspace/pull/18 brought over the object references vs the ones that were in the output correction branch.
I think I'm following the git flow of commits that this looks like an error pre generation of 0.1.3. If I'm mistaken, my apologies.
Expectations post fix is workspace_id reference the id and no longer the workspace object.

Thanks for the feedback @boblarson-ka. Our formatting for the output is a little different than the Terraform Registry docs. There will be some updates to the next version release


TypeError: Cannot read property 'firstRun' of undefined

We are intermittently seeing this error in our logs using v3.5.14. It has been seen on desktop Chrome, iOS and Android.
I have tracked it down to the settings[iframeId].firstRun in this function:
		function checkReset(){
			// Reduce scope of firstRun to function, because IE8's JS execution
			// context stack is borked and this value gets externally
			// changed midway through running this function!!!
			var
				firstRun           = settings[iframeId].firstRun,
				resetRequertMethod = settings[iframeId].heightCalculationMethod in resetRequiredMethods;

			if (!firstRun && resetRequertMethod){
				resetIFrame({iframe:iframe, height:0, width:0, type:'init'});
			}
		}

Offering up a pull request to address the issue: https://github.com/davidjbradshaw/iframe-resizer/pull/499

Fix r3.5.15


Support for Types in Query Parameters

@dannysheridan  encountered a case where a set of endpoints take the same 10 query-params. It's annoying to copy paste them everywhere and changing one things requires you to make edits in n different places.
Should we have a concept of grouped query params?

Idea: You can supply a type as the query-params. We'll have to runtime validate that all the value-types are primitives.

+1

Or maybe a concept of "groups" of query parameters that can be reused

+1

Closing because we are moving Github issues to be largely community-filed issues.


No link for ibisdoc available in Webservices

In the Webservices page of the Frank!Framework, the link is missing to get the Frank!Doc and ibisdoc.xsd.
Category: Frank Console
To Reproduce

Start the Frank!Framework with the Frank!Runner.
In the main menu, click "Webservices".

Expected behavior
There is a link with a name like "ibisdoc". If you open it, you have links to the Frank!Doc and to ibisdoc.xsd.
Screenshots

Environment:

Frank!Runner
Firefox
Windows
IAF version 7.6.20200311.144331

Additional context

Can you make sure the adapter has been started?

I started the Frank!Runner using start.bat. I observed that adapter WebControlWebservices is running. The ibisdoc link is still missing however.

I meant the ibisdoc adapter :)

This adapter is not present. The word "ibisdoc" does not appear anywhere on the Adapter Status page.

There's a property which enables/disables the adapter. The property is called 'ibisDoc.active'
If you go to the Environment Variables page, you can see whether this property has been defined, or is set to false. If so, setting it to true will turn on the adapter and thus the IbisDoc.

On a local branch, I updated the Frank!Runner to set this property. After starting the Frank!Runner, I could see that the property was set: Copy/pasting from the Environment Variables page gives:
ibisDoc.active | true. This does not fix the problem.
In the IAF repository, I could also see that ibisDoc.active is set in AppConstants.properties

I'm afraid I can't really help with this issue, it works on my machine and it works on the ibis4example. Maybe you can compare the configurations/adapters and environment variables?

Did you follow the "To Reproduce"? Then it should not work on your machine. :)
I would say this is related to #509 as the IbisDoc adapter is part of the IAF_Util configuration which is not started, hence the IbisDoc adapter isn't started and the link will not show up under Webservices.

Fixed because configuration IAF_Util now works. This is the fix of issue 509.


Update to Ranch 2.0

I'm using Ranch 2.0 in a project.
Adding Telemetry which uses Cowboy results in a dependency conflict.

Not a bug. You're probably using Mix. Mix made the choice to enforce consistency between all deps, while Erlang build tools have a "first dep fetched wins" approach. There's a way to make Mix behave but I don't use it therefore don't know it. Ask around, it's a common issue.

RIght. It might be a Telemetry thing then.
I'm doing {:ranch, "~> 2.0.0", override: true}, in my mix.exs to get around the conflict.
that results in the following when starting the application:
** (Mix) Could not start application ctc_socket: MyApp.Application.start(:normal, []) returned an error: shutdown: failed to start child: MyAppSocket.Telemetry
    ** (EXIT) shutdown: failed to start child: :prometheus_metrics
        ** (EXIT) an exception was raised:
            ** (MatchError) no match of right hand side value: %{id: {:ranch_embedded_sup, TelemetryMetricsPrometheus.Router.HTTP}, start: {:ranch_embedded_sup, :start_link, [TelemetryMetricsPrometheus.Router.HTTP, :ranch_tcp, %{max_connections: 16384, num_acceptors: 100, socket_opts: [port: 12345]}, :cowboy_clear, %{env: %{dispatch: [{:_, [], [{:_, [], Plug.Cowboy.Handler, {TelemetryMetricsPrometheus.Router, [name: :prometheus_metrics]}}]}]}, stream_handlers: [:cowboy_telemetry_h, :cowboy_stream_h]}]}, type: :supervisor}
                (plug_cowboy 2.4.0) lib/plug/cowboy.ex:207: Plug.Cowboy.child_spec/1
                (telemetry_metrics_prometheus 0.6.0) lib/telemetry_metrics_prometheus/supervisor.ex:15: TelemetryMetricsPrometheus.Supervisor.init/1
                (stdlib 3.9.2) supervisor.erl:295: :supervisor.init/1
                (stdlib 3.9.2) gen_server.erl:374: :gen_server.init_it/2
                (stdlib 3.9.2) gen_server.erl:342: :gen_server.init_it/6
                (stdlib 3.9.2) proc_lib.erl:249: :proc_lib.init_p_do_apply/

Thanks for the quick reply.

You may need to force a more recent Cowboy version as well to have one that supports both Ranch 1.x and 2.x.

Thanks for the hint. But I'm getting the error even with Cowboy 2.8.0
  cowboy 2.8.0
  cowboy_telemetry 0.3.0
  cowlib 2.9.1
  credo 1.5.0-rc.4
  file_system 0.2.9
  ink 1.2.0
  jason 1.2.2
  mime 1.4.0
  plug 1.10.4
  plug_cowboy 2.4.0

At this point the path of least friction seems to be downgrading to Ranch 1.7.1.
Again thanks for the help

I agree this is not a bug.
Still, is there a plan to support Ranch 2.0? Currently it doesn't work even overriding ranch in mix.exs.
I tried it in a Phoenix project with the latest version of Phoenix.

From the sound of it it's either plug or telemetry_metrics_prometheus that need to support Ranch 2.0. Cowboy already supports both 1.x and 2.0. Nothing more I can do.

You're right, sorry.
The problem is in https://github.com/elixir-plug/plug_cowboy/blob/v2.4.1/lib/plug/cowboy.ex#L207
:ranch.child_spec/5 is returning a map (if I'm not wrong) while plug_cowboy is expecting a tuple.

I submitted a PR for this on elixir-plug/plug_cowboy#64


Replace fs module

This replaces the fs module with a new abstraction layer.
The new abstraction layer looks slightly different:
// new
const data = await FS("package.json").read();

// old
fs.readFile(path.resolve(__dirname, "package.json"), (err, data) => {
  ...
});

as you can see:

PS-style API: FS("foo.txt").write("bar") for easier argument order
Promises (seriously wtf Node Core what are you thinking)

but also:

ability to turn off all filesystem writing (for unit tests)
paths are always relative to PS's base directory
mkdirp - make a directory and all the parent directories necessary to make it
readTextIfExists - suppress "file not found" errors and read as string
onModify - like watchFile but only calls callback for modifications
rmdirIfExists - suppress "directory not found" errors

Most importantly, though, the ability to turn off writes is important, because currently our tests don't work on Node 8, because mock-fs-require-fix doesn't support Node 8. This module is a lot easier to support than a mock-fs fork.

Great. I was planning to deprecate mock-fs-require-fix.
But do we need the cognitive overhead from .write() and .read()?
fs.write() and fs.read() are a thing...

Cognitive overhead?

I mean that ideally, Path#read should call fs.read(), not fs.readFile() in order to keep the method names homologous.

This works similarly to File classes in many programming languages, I don't see anything unusual here.

It intentionally doesn't use exactly the same method names. Path#read and Path#write also work identically to how fs.read and fs.write work; I don't think it's too important that they don't call the same underlying functions.
Path#symlinkTo is also different from fs.symlink, to draw attention to the different argument order.

Fair

Also it would be useful to add fs to the [https://github.com/Zarel/Pokemon-Showdown/blob/master/.eslintrc#L101](modules blacklist).

We can't add fs to the modules blacklist, because it's still used:
 * FS is used nearly everywhere, but exceptions include:
 * - crashlogger.js - in case the crash is in here
 * - repl.js - which use Unix sockets this file doesn't support
 * - launch script - happens before modules are loaded
 * - sim/ - intended to be self-contained

We should possibly blacklist it from chat-plugins specifically, if there's a way to do that.

I haven't merged yet because bumping the version to 8 is very :s

I think I managed to wait until Node 6 was LTS before I bumped that version...

Whatever. Something something YOLO.


Update test script to use embed test runner instead of mocha, chai

SSIA

@k1LoW I rewrote it to use the embed test runner to reduce the number of npm dependencies. If you have any problems, please comment 🙏


Dummy bug for checking reports

will be closed shortly

Checking the addition of comment on an issue.

Checking closing an issue (final check hopefully)


add lora fine tuning

Issue #, if available:
Description of changes:
support safetensor/hf model path/ckpt format
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

It's good for me !


Fix: Pull Requests merge errors

Closes #8301
Change Description
Background
Merge error handling was taken from the lakeFS merge flow - where we returned an empty reference on conflict.
As result error was undefined
Bug Fix
Fixed to parse the given error and handle accordingly
Testing Details
Manually tested

Looking good - But why not to add a unit test for it? (This function is already unit tested...)

Added unit test


sing-box 1.10.3 -> 1.10.4

https://github.com/SagerNet/sing-box/compare/v1.10.3...v1.10.4
Things done

Built on platform(s)

[x] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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

[ ] Fits CONTRIBUTING.md.

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

@ofborg test sing-box

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366817

x86_64-linux

:x: 1 package failed to build:

sing-box

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366817

x86_64-linux

:white_check_mark: 1 package built:

sing-box


PKCS7 support

Is there any plan to introduce support for PKCS7?

We have no plans to support features outside of our immediate needs, but will gladly accept pull requests that implement features. :)


Add wrap files for xxHash-0.6.5

This is a minimal port of xxHash library.

$ ./mesonwrap.py review xxhash --pull_request=1
Inspecting project xxhash, branch 0.6.5.
Repo name valid: ☑
Branch name valid: ☑
Target branch is not master: ☑
Has readme.txt: ☑
Has LICENSE.build: ☑
Has upstream.wrap: ☑
Repo contains only buildsystem files: ☑
upstream.wrap has directory: ☑
upstream.wrap directory has no path separators: ☑
upstream.wrap has source_url: ☑
upstream.wrap has source_filename: ☑
upstream.wrap source_filename has no path separators: ☑
upstream.wrap has source_hash: ☑
Download URL works: ☑
Hash matches: ☑
upstream.wrap directory 'xxHash-0.6.5' exists: ☑
Patch merges with source: ☑
The Meson build system
Version: 0.48.2
Source dir: /tmp/tmpwz4ut21b/src/xxHash-0.6.5
Build dir: /tmp/tmpwz4ut21b/bin
Build type: native build
Project name: xxhash
Project version: 0.6.5
Native C compiler: cc (gcc 8.2.1 "cc (GCC) 8.2.1 20180831")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Build targets in project: 2
Found ninja-1.8.2 at /usr/bin/ninja
meson setup: ☑
ninja: Entering directory `/tmp/tmpwz4ut21b/bin'
[5/6] Running all tests.
1/1 internal bench                          OK       0.24 s
OK:         1
FAIL:       0
SKIP:       0
TIMEOUT:    0
Full log written to /tmp/tmpwz4ut21b/bin/meson-logs/testlog.txt
ninja test: ☑

And on the RPi 3B+:
$ ./mesonwrap.py review xxhash --pull_request=1
Inspecting project xxhash, branch 0.6.5.
Repo name valid: ☑
Branch name valid: ☑
Target branch is not master: ☑
Has readme.txt: ☑
Has LICENSE.build: ☑
Has upstream.wrap: ☑
Repo contains only buildsystem files: ☑
upstream.wrap has directory: ☑
upstream.wrap directory has no path separators: ☑
upstream.wrap has source_url: ☑
upstream.wrap has source_filename: ☑
upstream.wrap source_filename has no path separators: ☑
upstream.wrap has source_hash: ☑
Download URL works: ☑
Hash matches: ☑
upstream.wrap directory 'xxHash-0.6.5' exists: ☑
Patch merges with source: ☑
The Meson build system
Version: 0.48.2
Source dir: /tmp/tmpz1jw1ogj/src/xxHash-0.6.5
Build dir: /tmp/tmpz1jw1ogj/bin
Build type: native build
Project name: xxhash
Project version: 0.6.5
Native C compiler: cc (gcc 8.2.0 "cc (GCC) 8.2.0")
Build machine cpu family: aarch64
Build machine cpu: aarch64
Build targets in project: 2
Found ninja-1.8.2 at /usr/bin/ninja
meson setup: ☑
ninja: Entering directory `/tmp/tmpz1jw1ogj/bin'
[5/6] Running all tests.
1/1 internal bench                          OK       1.72 s

OK:         1
FAIL:       0
SKIP:       0
TIMEOUT:    0

Full log written to /tmp/tmpz1jw1ogj/bin/meson-logs/testlog.txt
ninja test: ☑

Thanks for running tests on R-Pi. I only run it on AMD64 for sanity checks, so if you test the build on different architectures it helps :)


MSS425ER support missing

Please explain your feature request in a one or two sentences.
My home bridge Installation tells me, that support for device MSS425ER is missing

Is your feature request related to a problem? Please describe.
Cannot find this device in home bridge

Any particular Meross devices that this relates to?
MSS425ER

Anything else?

Bug report from Homebridge logs:
{"uuid":"2104302773553790850748e1e97036a9","onlineStatus":1,"devName":"Steckdosenleiste Schreibtisch","devIconId":"device020_eu","bindTime":1669538341,"deviceType":"mss425er","subType":"eu","channels":[{},{"type":"Switch","devName":"Bett","devIconId":"device001"},{"type":"Switch","devName":"Schreibtisch","devIconId":"device001"},{"type":"Switch","devName":"Weihnachtsbaum","devIconId":"device001"},{"type":"USB","devName":"USB Schreibtisch","devIconId":"device001"}],"region":"eu","fmwareVersion":"4.2.3","hdwareVersion":"4.0.0","userDevIcon":"","iconType":1,"skillNumber":"","cluster":2,"domain":"mqtt-eu-2.meross.com","reservedDomain":"mqtt-eu-2.meross.com","firmware":"4.2.3","hbDeviceId":"2104302773553790850748e1e97036a9","model":"MSS425ER"}

Hi @timstrakeljahn
Thanks for this.
Does your model support homekit natively?

Yes it does.
This is my workaround to just add it to the HomeKit app.

Thanks, please install the beta version of the plugin, this device should start working
https://github.com/bwp91/homebridge-meross/wiki/Beta-Version

Thank you very much ☺
Now it works


artifacts stop downloading halfway

I'm trying to download the artifact for windows. the file I get is 7.9Mb, sometimes smaller. when it should be 23.8Mb.
I'm trying to open the examples with the 7.9Mb downloaded file, I get this error:

maybe we should make a alpha release after all.

Hey, thanks for the note. Not too much I can do about GitHub's servers of course…I have a very massive private branch on my PC right now〜

I was actually planning to submit our first binary pre-release when I merge this branch (it adds guidelines, but also a whole bunch of other stuff—it deprecates calc_x and calc_y, all matrix calculations are now done on Viewport, it has a fixed grid.rs that works with Rotalics, and a bunch of other fixes I've been working on. @prajwalprabhu is doing some work with me over on MFEK/math.rlib regarding simplification that might also get into that release.
We're making good progress I think, we had a bumpy two weeks, not gonna sugarcoat it, but stuff's back on track and we're gonna “Build Back Better™” (with apologies to Joe Biden).

Artifacts are now much smaller; nothing I can do about GitHub's servers; main issue for binary woes is going to be #219.


[Bug report]

Bug report
Description
VuePress was showing me this error on useThemeLocaleData(), so what I did was that I made a new branch and deleted all my project's dependencies and files, leaving only the VuePress code.
I deleted my node_modules folder and pnpm-lock.yaml, then did a pnpm i to install the node_modules and create the pnpm-lock.yaml again. However this still did not work and showed the same error.
Steps to reproduce
You can clone the repository here
Expected behavior
An empty VuePress app to run
Screenshots

Environment info

Browser:

Output of vuepress info:

  System:
    OS: Windows 10 10.0.22581
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
    Memory: 2.95 GB / 15.95 GB
  Binaries:
    Node: 16.10.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.5.2 - C:\Program Files\nodejs\npm.CMD
  Utilities:
    Git: 2.34.1.
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22581.100.0), Chromium (99.0.1150.55)
  npmPackages:
    @vuepress/bundler-vite:  2.0.0-beta.36
    @vuepress/bundler-webpack: Not Found
    @vuepress/cli:  2.0.0-beta.36
    @vuepress/client:  2.0.0-beta.35
    @vuepress/core:  2.0.0-beta.36
    @vuepress/markdown:  2.0.0-beta.36
    @vuepress/plugin-active-header-links:  2.0.0-beta.36
    @vuepress/plugin-back-to-top:  2.0.0-beta.36
    @vuepress/plugin-container:  2.0.0-beta.36
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-external-link-icon:  2.0.0-beta.36
    @vuepress/plugin-git:  2.0.0-beta.36
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.36
    @vuepress/plugin-nprogress:  2.0.0-beta.36
    @vuepress/plugin-palette:  2.0.0-beta.36
    @vuepress/plugin-prismjs:  2.0.0-beta.36
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: Not Found
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.36
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.35
    @vuepress/theme-default:  2.0.0-beta.36
    @vuepress/utils:  2.0.0-beta.35
    vue:  3.2.31
    vue-loader: Not Found
    vue-router:  4.0.14
    vuepress: ^2.0.0-beta.36 => 2.0.0-beta.36
    vuepress-vite:  2.0.0-beta.36
    vuepress-webpack: Not Found

I can confirm the same issue started for me as well.

Vite released new version yesterday,may caused by that.
Deps tree may be broken, please double check whether you have different versions of @vue/xxxx and @vite/xxx packages installed.

@Mister-Hope ,  so far..

I deleted everything and started from scratch
Tried pnpm & npm
Tried to install Beta 35 & 34

but none seems to work at this point. When the server starts, none of the packages (such as vuepress-router) gets started.

please double check whether you have different versions of @vue/xxxx and @vite/xxx packages installed,

Please check this, also, you may try using<EMAIL_ADDRESS>with "vite": "~2.8.0".

@Mister-Hope I agree. I'm pretty sure it is vite that causing the trouble (a couple times, I saw a different error regards version numbers - but I didn't copy the error message and now I couldn't reproduce.  It was some like it was expecting version 12.x but 14.x was there) .
Changing to webpack bundler works fine.  But I couldn't use Vite 2.8.0 as even I install it manually, vuepress by default using vite 2.9.  Not sure how to force that.  I'll use webpack for time being.
devDependencies:
+ @vuepress/bundler-webpack 2.0.0-beta.36
+ vite 2.8.0 (2.9.0 is available)
+ vuepress 2.0.0-beta.36
+ webpack 5.70.0

vuepress dev docs

info Initializing VuePress and preparing data...

  vite v2.9.0 dev server running at:

  > Local:    http://localhost:8080/
  > Network:  http://<IP_ADDRESS>:8080/

vuepress by default using vite 2.9

Nope
https://github.com/vuepress/vuepress-next/blob/main/packages/%40vuepress/bundler-vite/package.json#L43
You should be able to use latest<EMAIL_ADDRESS>

#784 should fix this

Hi everyone, here is a possible workaround.
If you are using yarn, add  "resolution" in your package.json and force using<EMAIL_ADDRESS>then everything should be working fine.
{
 // ...
  "resolutions": {
    "vite": "2.8.2"
  },
}

We are actually not responsable for potential breaking changes from deps chain. 🙂 Give us some time to investigate and fix this.

https://github.com/vitejs/vite/pull/7379 introduced some internal breaking changes, which broke one of the internal workaround plugin of vuepress-next.
I'll update the workaround plugin soon. It's still a workaround, and we need to find a way to solve it completely in the future.

New related bug #800. We will fix it soon.


Picovoice Console Issue: Issue with Language Compatibility in Picovoice Model

Dear Picovoice Team,
I hope this message finds you well. I am reaching out because I am encountering an issue when using one of the Spanish-language wake word models with the "Porcupine" libraries.
I have downloaded the model files and wake word files in Spanish (for example, Auxilio_es_windows_v3_0_0.ppn, Socorro_es_windows_v3_0_0.ppn, etc.), but when attempting to load the model with the "Porcupine" library, I receive the following error:

PorcupineInvalidArgumentError: Initialization failed: Keyword file (.ppn) and model file (.pv) should belong to the same language. File belongs to 'es' while model file (.pv) belongs to 'en'.

This error suggests that the Spanish-language keyword file is incompatible with the .pv model file in English. However, I have confirmed that the keyword files are trained for the Spanish language, and I would like to know how I can resolve this issue in order to use both the keyword files and the model in Spanish.
Could you please provide a .pv model file in Spanish that is compatible with the keyword files I have downloaded? Or, if there are any other steps I should take to resolve this issue, I would greatly appreciate your guidance.
Thank you in advance for your support. I look forward to hearing from you.
Best regards,
César Sotillo
<EMAIL_ADDRESS>Cesar-s16 (github)

How can I use it? Can I use my own access key?


fix: duplicate declaration

Checklist

[x] npm test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message follows commit guidelines

Affected core subsystem(s)

Description of change

fix duplicate declaration error.

Codecov Report

Merging #50 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #50   +/-   ##
=======================================
  Coverage   96.93%   96.93%
=======================================
  Files          16       16
  Lines         652      652
  Branches       90       90
=======================================
  Hits          632      632
  Misses          8        8
  Partials       12       12

Impacted Files
Coverage Δ

src/generators/config.ts
97.61% <ø> (ø)
:arrow_up:

src/generators/extend.ts
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Non-Square Maps Now Openable

Fix switcheroo in ImportCiv3 that resulted in non-square maps not being openable.
Somewhat improved logging in GameData if somehow invalid tile coordinates are passed in.
Non-null default for terrain name, which prevents Tile.NONE from causing a blow-up in the case that you ask whether it's hilly (could happen with hills on edge of map, will be obsolete with the key refactor).
Increase Godot printout support, as while debugging I hit the old limit.

GitHub doesn't really show it well, but the new commit is from rebasing.  I think it looks weird (two commits on Conversation, one on Commits) because I rebased from local Development after pulling that branch and switching back, rather than from origin/Development.  Then I had to force-push for GitHub to accept the update.


Remove init flow

/retest

/test placement-operator-build-deploy-kuttl
i think the test is racy and its not waiting long enough for it to scale
we may need to merge https://github.com/openstack-k8s-operators/placement-operator/pull/125 first or  modify how kuttl is run
placement_kuttl_run https://github.com/openstack-k8s-operators/install_yamls/blob/60c1fb7828a91545e52b5c799162bcc21c3dd5ee/Makefile#L1586-L1588
its currently looking for kuttl config in repo in https://github.com/openstack-k8s-operators/placement-operator/blob/main/kuttl-test.yaml
so we can adjust some of the config that way
nova is using a timeout of 300 seconds per test
https://github.com/openstack-k8s-operators/nova-operator/blob/main/test/kuttl/test-suites/default/config.yaml#L7
we are using 180 in placement so we could start by bumping to 300 and see if that is enough to stableise the test

/test placement-operator-build-deploy-kuttl
i think the test is racy and its not waiting long enough for it to scale
we may need to merge #125 first or modify how kuttl is run
placement_kuttl_run https://github.com/openstack-k8s-operators/install_yamls/blob/60c1fb7828a91545e52b5c799162bcc21c3dd5ee/Makefile#L1586-L1588
its currently looking for kuttl config in repo in https://github.com/openstack-k8s-operators/placement-operator/blob/main/kuttl-test.yaml
so we can adjust some of the config that way
nova is using a timeout of 300 seconds per test
https://github.com/openstack-k8s-operators/nova-operator/blob/main/test/kuttl/test-suites/default/config.yaml#L7
we are using 180 in placement so we could start by bumping to 300 and see if that is enough to stableise the test

Thanks! I bumped it to 300 because this failed already few times on same issue that db sync didn't finished

kuttl tests catch realll issue with volumes for db-sync so this is not related to timeout

/retest


Reduced test workflow target to 20 files

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#958  👈
#110
#273
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


Documentation does not mention you need Rosetta on ARM Mac

Bug description
Documentation does not mention you need Rosetta on ARM Mac
Expected behavior
Documentation should mention for ARM Macs (M1/M2/M3) you need to execute:
softwareupdate --install-rosetta --agree-to-license

Steps to reproduce the bug / Relevant debug output
If you did not install Rosetta, installing plugins will fail with error bad CPU type in executable:
$ tanzu plugin list
[i] The tanzu cli essential plugins have not been installed and are being installed now. The install may take a few seconds.
[i] Installing plugins from plugin group 'vmware-tanzucli/essentials:v1.0.0'
[x] Failed to install plugin 'telemetry:v1.1.0' with target 'global'
[!] unable to install plugin 'telemetry': could not describe plugin "telemetry": fork/exec /Users/jeroenv/Library/Application Support/tanzu-cli/telemetry/v1.1.0_a93519154dc71368d738aec09f9bc964a0c3bcd02a856106ccaddaaf31426636_global: bad CPU type in executable

It took me quite a while to figure out what the problem was.
Output of tanzu version
$ tanzu version
version: v1.3.0
buildDate: 2024-05-09
sha: d59f47c8
arch: arm64

Environment where the bug was observed (cloud, OS, etc)
$  uname -a
Darwin Jeroens-MacBook-Pro.local 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:16:51 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8103 arm64
$ sysctl -a | grep brand
machdep.cpu.brand_string: Apple M1

Sorry you ran into trouble @jeroenvermeulen. I thought Rosetta was standard on  all ARM64 Macs. Thanks for reporting, it will help others. I’ll add it to the documentation.

@jeroenvermeulen Could you have a look at #776 to tell me if the proposed documentation is clear enough from your point of view?


fix: code generating enum values containing !, =, ~ are stripped (#1738)

Backport
This will backport the following commits from 2.x to 1.x:

fix: code generating enum values containing !, =, ~ are stripped (#1738)

Questions ?
Please refer to the Backport tool documentation

⚪ 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 1739

Questions ?
Please refer to the Backport tool documentation


Android delay communication

We use Mirror to commnicate between a Linux server and clients. Everything works good with windows and mac, but with android we have more than 5 seconds delay (client -> server or server -> client) and sometimes it feels like the message is not sent.
We tried the last package on the Asset Store and the last one on GitHub Release and before the update everything was ok with Android.
Previous version was 40.0.9
Did someone has any idea ?

You'll need to give us much more details. What is your versions of Unity and what is your Android devices? Are you testing in high-latency environment like 3G/4G to a server or locally inside a LAN via WiFi?
What are you sending? Did you change anything since you imported the latest Mirror version? Or did you just apply it over the top?

Hi :)

The Unity Version is 2019.4.18
Devices are Oculus GO and Oculus Quest
We use wifi to access distant environnement (we never had more than 1 second latency)
We send messages with short string,  bool or int as parameter
We just made the update and a new build without any change in the project

Is the WiFi lossy, in the sense that packets go missing or there's lag with other games/apps on the headsets?
How complicated is the network structure? See the following examples:
1) Server <- Ethernet -> Wireless Access Point/Router <- WiFi ->  VR Devices
- All devices are in the same IP subnet, such as 192.168.10.x
2) Server <- WiFi -> Wireless Access Point/Router <- WiFi -> VR Devices
- All devices are in the same IP subnet, such as 192.168.10.x
3) Server <- Ethernet/WiFi -> Wireless Access Point/Router 1 <-> Wireless Access Point/Router 2 or WiFi Range Booster/Extender <-> VR Devices
- All devices are in the same IP subnet, such as 192.168.10.x OR
- Wireless Access Point 1 is 192.168.10.x and AP 2 is 192.168.11.x

Using a server over a wireless connection is not recommended for reliable testing. Consider using Ethernet connection on the server to the device that is providing wireless signal to the VR units.

Do you have debug log output on android showing?
Is it getting any messages to hint that somethings not working as intended ?

Closing for lack of response...reopen if new information becomes available.


missing: exit nonzero if missing deps are found

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

Currently brew missing always returns a successful error code. This changes it to return a failing error code when it detects formulae with missing dependencies.

Can you explain how this is a workaround for https://github.com/Homebrew/homebrew-core/pull/26497 ?

The issue that https://github.com/Homebrew/homebrew-core/pull/26497 aimed to fix was a bottle that generates brew missing complaints (via brew doctor), which breaks our CI. Rather than remove brew doctor from our CI completely, my plan is to just try to install any packages that brew missing thinks are necessary (even though in this example, gobject-introspection is only a build depend of one of gtkglext's dependencies). It makes it a little easier to implement the installation logic if brew missing returns a failure.
$ brew install gtkglext
...
$ brew doctor
...
Warning: Some installed formulae are missing dependencies.
You should `brew install` the missing dependencies:
  brew install gobject-introspection

Run `brew missing` for more details.
$ brew missing
gtkglext: gobject-introspection
$ brew missing || brew install $(brew missing | awk '{print $2}') && brew missing && echo success
...
==> Installing gobject-introspection
...
success

This PR enables the line, which is my current preferred workaround.
$ brew missing || brew install $(brew missing | awk '{print $2}') && brew missing

Ah, OK. I think brew install --only-dependencies $(brew list) does what you want.
This PR makes sense regardless, of course.

In most cases, brew install --only-dependencies $(brew list) will work, but the gtkglext high sierra bottle (not the other bottles) currently has gobject-introspection in its INSTALL_RECEIPT.json but it doesn't show up in brew deps gtkglext.
$ brew install --only-dependencies gtkglext
All dependencies for gtkglext are satisfied.
$ brew missing
gtkglext: gobject-introspection
$ brew deps gtkglext
atk
cairo
fontconfig
freetype
fribidi
gdk-pixbuf
gettext
glib
graphite2
gtk+
harfbuzz
hicolor-icon-theme
icu4c
jpeg
libffi
libpng
libtiff
pango
pcre
pixman

So this brew missing trick is helpful for these old bottle edge cases.

That's confusing if brew install --only-dependencies gtkglext can still leave brew missing reporting dependencies missing for gtkglext.
Also, failing CI over bottles we're intentionally not updating seems bogus and you shouldn't have to fill in those dependencies as a workaround.

Well, that is why I submitted https://github.com/Homebrew/homebrew-core/pull/26497 initially, but I don't mind this workaround if the principle expressed by @MikeMcQuaid in https://github.com/Homebrew/homebrew-core/pull/26497#issuecomment-380677042 is important.

The idea was that new bottles were no longer supposed to be needed for that scenario. The idea was not that you should have to hack around problems that cause CI failures.

I'm just back home from a work trip and may take a few days to get to this but: yes, there should be no circumstance in which we're displaying output that means that the solution is to rebottle just to change an INSTALL_RECEIPT.
I'm still not sure I understand what breaks your CI here, can you elaborate further? Is it that you're installing a bottle from scratch and it immediately makes brew doctor and brew missing fail?

We use brew install --only-dependencies to resolve dependencies, then manually build from source and install into brew --cellar and run brew link. We then run brew doctor, I think so we could catch any errors we had with brew link (to be honest I can't remember). I could change it to brew doctor || true so we would still have the console output, but it wouldn't fail the build. Or we could suppress check_missing_deps, as @ilovezfs suggested.

@scpeters I'm not sure I see what I'm looking at on the manually building from source. How do you have an install receipt at all when not using Homebrew to do that?

So the issue is if you run brew install gtkglext and then brew missing or brew doctor they show missing deps?

So the issue is if you run brew install gtkglext and then brew missing or brew doctor they show missing deps?

Yes, exactly, though only on high sierra (in case anyone tries to reproduce). I believe the older bottles were built with older versions of homebrew.

More weirdness with missing:
Josephs-MacBook-Pro:~ joe$ brew outdated subversion
subversion (1.9.7_3) < 1.10.0
Josephs-MacBook-Pro:~ joe$ brew missing
subversion: lz4 utf8proc
Josephs-MacBook-Pro:~ joe$

but lz4 and utf8proc are deps of 1.10.0 not 1.9.7_3.

Will continue to talk here when I've thought about a better plan but this PR is 👍 as-is, thanks @scpeters!

More weirdness with missing:

@ilovezfs Fixed your case with https://github.com/Homebrew/brew/pull/4118.

@scpeters @ilovezfs I'm still trying to figure out the best fix for that scenario. Some options I can see:

store all build dependencies in the tab along with runtime dependencies on a formula and when the build dependencies differ from the formula: recalculate the runtime dependencies on pour
have some audit or test or linkage that means that CI will fail if there's not a revision bump made when runtime dependencies on a formula have been removed.
something else

Thoughts?

store all build dependencies in the tab along with runtime dependencies on a formula and when the build dependencies differ from the formula: recalculate the runtime dependencies on pour

This approach seems to try to solve the problem by making brew smarter.

have some audit or test or linkage that means that CI will fail if there's not a revision bump made when runtime dependencies on a formula have been removed.

This approach seems to try to detect problems and rebuild bottles more often.
I don't spend enough time with brew to feel confident in commenting on whether the first approach will work or not, though I think it is more complex. I think the second approach has simpler logic but involves a little more time spent rebuilding bottles. For my own sake, I would lean towards the second because I think it would be easier to understand, but I don't know how that impacts maintainer workload.


Etcd snapshot container is not deployed after upgrade

rancher/rancher:v2.1.2-rc9
Etcd snapshot container is not deployed after upgrading to v2.1.2-rc9. Rancher server logs do not show rke up being triggered for RKE clusters.
To reproduce:

Deploy Rancher server v2.1.1
Provision an RKE cluster (in this case, used Azure)
Upgrade to v2.1.2-rc9
Etcd snapshots are enabled in cluster yaml / UI
ssh to etcd node

docker ps  on etcd node shows no snapshot container
/opt/rke/etcd-snapshots does not exist
Expected:

etcd-rolling-snapshots container to be running
/opt/rke/etcd-snapshots exists

Viewing in the API also shows that snapshots are enabled:
services": {
"etcd": {
"creation": "12h",
"extraArgs": {
"election-timeout": "5000",
"heartbeat-interval": "500"
},
"retention": "72h",
"snapshot": true,
"type": "/v3/schemas/etcdService"
},

After editing & saving a cluster, the container is started and the directory is created.
We will document that the clusters will not be automatically updated without saving.

The fix can be to remove norman annotation defaulting value to true, and do the defaulting in the store (always not nil value, true or false based on user input). Leave the type as pointer though so standalone rke can default if the value is nil

Went over this with Craig and Darren, and decided to change things a bit.
For existing clusters with a nil value, we want this to be interpreted as false. Currently, snapshots wont start anyways until the cluster is updated, so this part is ok.

To fix the value showing up in the UI as true, we are changing norman so that Non-nullable values who's key is not present are assigned the empty value during get/list, rather than the default value.

To ensure that existing clusters don't suddenly start snapshotting, when we update clusters in rancher, before we pass the update down to kontainer-engine, if the snapshot value is nil, we set it explicitly to false.

This way the default is still true, so on create the UI gets true as the default, and in RKE the default is still true, so that when it is omitted creating clusters with RKE it is still enabled

To fix the value showing up in the UI as true, we are changing norman

fyi we have release/v2.1 branch in norman - the last commit of this branch is vendored in to rancher's release/v2.1.

Tested with upgrade from v2.1.1 to v2.1.1-rc13.
After upgrade, the etcd snapshot was still disabled as expected

Edited another parameter(PSP) and after the update succeeded, the etcd snapshot field was still disabled as expected

We decided to change this such that on upgrade clusters are legitimately not snapshotting, so it should show as false.

Tested with upgrade from v2.1.1 to v2.1.6

Created a 3 node DO cluster in v2.1.1
Created workloads.
It was observed that "snapshot": false, was set in API

"services": {
		"etcd": {
    		"extraArgs": {
         		"election-timeout": "5000",
         		"heartbeat-interval": "500"
     		},
     		"snapshot": false,
     		"type": "/v3/schemas/etcdService"
 		},

Upgrade rancher to v2.1.6. After upgrade the etcd-rolling-snapshots containers are still not deployed

"services": {
		"etcd": {
    		"extraArgs": {
         		"election-timeout": "5000",
         		"heartbeat-interval": "500"
     		},
     		"snapshot": false,
     		"type": "/v3/schemas/etcdService"
 		},

Edit the cluster and enable the etcd snapshot with creation time as 5m. After the cluster update completed, the etcd-rolling-snapshots containers were deployed and running. The snapshots were created at intervals of 5m as set. "snapshot"= true is set in the API as below:

services": {
"etcd": {
"creation": "5m",
"extraArgs": {
"election-timeout": "5000",
"heartbeat-interval": "500"
},
"retention": "2h",
"snapshot": true,
"type": "/v3/schemas/etcdService"
}

Note: After rancher upgrade from v2.1.6 to master build from Feb 19, Snapshot = true is  set in the API. The etcd-rolling-snapshots continue to run and snapshots are taken at the set interval.
After editing and saving the local etcd backup settings, cluster gets updated and “snapshot=false”  is set in the API since legacy backups are disabled


api-common using deprecated javax.annotation-api

Google Cloud storage recieved https://github.com/googleapis/java-storage/issues/2176 due to a transient dependency on javax.annotaion-api. This should be updated to the new jakarta namespace.

javax package is not compliant with Jakarta platform. Please release google-cloud-storage:jar which is Jakarta platform compliant.

Digging further.

@abhishekshan03 Would you share details about the noncompliance? Do you get any error message when you use certain tools from Jakarta EE?
I found this article https://jakarta.ee/blogs/javax-jakartaee-namespace-ecosystem-progress/ but it didn't have any specifics about javax.annotation-api.

Hi @suztomo
Please pardon my limited knowledge. As far as I know packages javax.* are not part of Jakarta EE platform and hence are deprecated and will be replaced by jakarta annotations
As an example please refer to below issue.
https://github.com/jruby/jruby/issues/6514

Is there any idea on when this might be released? It is blocking a major upgrade for us.

@abhishekshan03 @MyDogIsMyPersonality Are you suffering from some errors with certain tools when they're used with GCP Java libraries? I think it's easy to swap but I'd like to ensure to verify the fix.

There is more information in issue 2176, but Jakarta won't upgrade due to the transient dependency in javax.

@MyDogIsMyPersonality https://github.com/googleapis/java-storage/issues/2176 does not have any errors.

Jakarta won't upgrade

Would you elaborate a bit more? Are you referencing a certain version of one of the tools listed in https://jakarta.ee/compatibility/ ?

@abhishekshan03 @MyDogIsMyPersonality Are you suffering from some errors with certain tools when they're used with GCP Java libraries? I think it's easy to swap but I'd like to ensure to verify the fix.
Thank you for sharing jruby/jruby#6514. I see it's fixed there.

@suztomo
I shared  jruby/jruby#6514 as an example for your to refer. I havent not asked any action to be taken on this issue. javax.annotation-api.jar is deprecated and should be replaced by jakarta annotations. This ticket was to illustrate that other projects are replacing deprecated javax.annotation-api.jar with jarkarta annotations.
Can you please give us an ETA for replacing the dependency for javax.annotation-api.jar with jarkarta annotations in google-cloud-storage.jar ?

https://jakarta.ee/compatibility/

We are not facing any error but since there is dependency on the deprecated javax.annotation-api.jar, we are proactively removing such dependencies.

Thank you. It's good to hear that there's no one suffering from errors due to the annotations.

we are proactively removing such dependencies

It seems that you're not a normal user of Jakarta EE and Google Cloud. Do you mind sharing who is "we" here (organization name or the name of a team)?

Got information from the TAM. Thank you. I'll update you about the plan soon.

Continuing investigation.

We use code generators:

autovalue: https://github.com/google/auto/issues/1602
grpc-java: https://github.com/grpc/grpc-java/issues/9179

Now each has tracking feature request (but no commitment). So far no one has suffered problems caused by javax namespace.
For GuardedBy, (usage), as long as the purpose is Errorprone's static analysis, Errorprone's com.google.errorprone.annotations.concurrent.GuardedBy is recommended one.


Fixes #472 - Filter older debuggees when offering debug targets to user

lgtm

Maybe add a simple comment describing the situation - that "default" modules do not have module names coming back from the API hence the reason for setting it manually.  lgtm.

I think I'm missing something.  How does this filter older debugees?

@patflynn it's an indirect effect: ProjectDebugeeBinding (around line 176) uses a hashmap to filter out dups by module name. @akerekes's fix ensures that even default modules (that have no module names from the API) get that filtering logic applied to them.

Then definitely +1 to a comment explaining how this works.  I don't think
somebody would understand the behavior intended just by looking at this
code.
On Mon, Mar 7, 2016 at 5:27 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

@patflynn https://github.com/patflynn it's an indirect effect:
ProjectDebugeeBinding (around line 176) uses a hashmap to filter out dups
by module name. @akerekes https://github.com/akerekes's fix ensures
that even default modules (that have no module names from the API) get that
filtering logic applied to them.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-intellij/pull/474#issuecomment-193484582
.

LGTM


D435I doesn't work

librealsense
2.43.0 RELEASE

OS
Windows

Name
Intel RealSense D435I

Serial Number
838412070598

Firmware Version
<IP_ADDRESS>

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
3.2

Product Line
D400

Asic Serial Number
903223052509

Firmware Update Id
903223052509

Please provide a description of the problem

Camera cannot output RGB image and Depth image, when connected to the realsense viewer

Hi @Kylemaycry   Can you check the camera privacy settings in Windows please to ensure that pernission for applications to access the camera is set to On.  Instructions for doing so are in the link below.
https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789

I connected it to another PC. It's working now.

Thanks.


ConnectionResetError

Hi Team,
Each time we run as Open connection,  wc3270 window launches and gets closed immediately.
Wait field detected keyword fails with an error: ConnectionResetError: [winerror 10054] an existing connection was forcibly closed by the remote host.
Please help to suggest solution for this, as manually we are able to open the wc3270 window and close it properly.

Hi Team
Any update on this issue?

Hi @FWDQK what version of the library you are using? I just run the tests of version 4.0 and everything is working as expected.
Do you have more informations?

Hi @FWDQK what version of the library you are using? I just run the tests of version 4.0 and everything is working as expected.
Do you have more informations?

Hi, We are also same version 4.0
But we are facing this issue much frequently in current environment.
For other environment, it is working fine.

Hi @FWDQK ,
the error message, [winerror 10054] an existing connection was forcibly closed by the remote host., basically says that the host that you are tryring to connect to closed the connection made by wc3270.
There might be multiple reasons as to why this happens. One of them might be that you host only allows for one connection at a time, so that when you connect to it with multiple wc3270 clients, it shuts down some of them.
In any case, this is not really possible for us to debug, since the issue is most likely rooted in you environment setup. If you haven't already, please also get in contact with your system administrators, as they may have additional information as to why the host shuts down the connections from your client.


No writing to user find-db when fast-hybrid mode is enabled.

Extension of #299 (implemented in PR #326).
@atamazov Can you or @DrizztDoUrden take this task?

@daniellowell, what priority should this issue have?

@daniellowell Let's reach consensus first.
The idea of "Fast" Find modes is pretty simple: re-use existing code to accelerate Find. The Fast Find mode re-uses existing Immediate mode machinery. The Hybrid mode combines existing Immediate and Find mechanisms (and that is why it is named "Hybrid"); in case of find-db hit we use Immediate mode machinery, in the case of find-db miss we use existing Find machinery. The simplicity of the implementation of these ideas created the false impression that it is possible to move further along this path.
But this is not the case. Fast Hybrid requires modification of Find internals, which is basically a crutch. I warned from the very beginning that this would be a strange thing.
Now there is an idea to insert another patch, which seems to fix the first crutch. However, this can lead to other problems. After all, we will not only complicate the implementation of Search, but also spoil the functionality of find-db (which by definition is the cache of Find results). I cannot predict what side effects may occur. It is likely that we will need more crutches and patches in the future.
What we get is questionable. Currently, FastHybrid performs Search once (and then re-uses find-db), but after this change, Search will be performed every time. It is faster than a regular Find, but would it be enough? I doubt that this mode (FastHybrid without writing to find-db) will be faster then "normal" Hybrid on average.
That is why I am against making such a decision right now.
However, we can implement this as an experimental feature. Then we'll need to perform a series of measurements to see if this FastHybrid (without writing to find-db) is faster than Hybrid. And even if it is, let's also compare it with "current" FastHybrid. Then we can make a final decision.
If we want to go this way, implementation is not a problem. However let's first decide who will conduct the benchmarking and how to do it.

I agree we shouldn't pile up technical debt for such a thing.
The overall goal is to have the compile time drop drastically for MIOpen generally, but for unseen (therefore untuned) configs specifically. If we can refactor MIOpen to use this hybrid-find mode with a clean design then I think we should do so.
We have 2 domains of MIOpen tuned known configs and untuned unknown configs. If it untuned and unknown, I don't think we should bother compiling tunable source kernels as they would naturally have inferior performance. If the user is a power user then they will know from reading documentation how to tune and how to set the find mode.
So, we should create a design that accomplishes this task.

We have 2 domains of MIOpen tuned known configs and untuned unknown configs. If it untuned and unknown, I don't think we should bother compiling tunable source kernels as they would naturally have inferior performance.

This is a new idea that worth separate ticket.

Part of the requirement for new dynamic mode. Still in progress

@aserio What is new dynamic mode?

Dynamic Hybrid mode is the new find mode (MIOPEN_FIND_MODE=5). It is similar to Fast Hybrid Find, but in the case of a find_db miss, it will skip all non-dynamic kernels.

Thanks. We do not have consensus yet -- if this is requirement or not. Please see https://github.com/ROCmSoftwarePlatform/MIOpen/issues/380#issuecomment-675472170 and https://github.com/ROCmSoftwarePlatform/MIOpen/issues/380#issuecomment-675734858.

Closing as it is already implemented

Closing as it is already implemented

Clarification: Assured by design of the Fast Find mode.


1 - V2

This PR adds contract runtime support for HDP

LGTM for me!
When we merge new docker image:latest is gonna be created this can break some deps in other images lets fix the versions in relevant dockerfiles before we merge


Datetime awareness

This ghetto implementation currently returns a timestamp with no timezone awareness. It would be nice if it was returned UTC.


fix(accelerate): Fix missing model_config_path

fix(accelerate): Fix missing model_config_path when creating model config
The argument model_config_path was never passed when creating the model_config.

Pinging @hynky1999;
The failure of the CI doesn't seem to be related to the content of this PR. Could you please check?

Seems like the secrets are not exposed for user PRs for some reason even tho manually approved. I will check what we can do with it

@clefourrier
Why was this closed unmerged? #304 fixes a problem with the checks but it doesn’t fix the content of this PR.

Hi! This was done automatically by github when merging the other PR, let me check yours and see what diffs are


Should mean also have an INLINE pragma?

I just wondered why mean doesn't have an INLINE pragma. I guess you are aware that this will prevent stream fusion, so I expect there to be another reason especially because there are INLINES on other functions?

I don't really know. Commit which replaced INLINE with SPECIALIZE pragmas doesn't either. Maybe to avoid having multiple copies of mean etc in executable. Please reopen if it causes performance problems for you.

I don't have any hard measurements, but from experience inlining calls to vector is faster in most cases. On the other hand the current mean implementation does two folds (ie traversals) which is slow in any case :-)


Are Notifications sent before or after merging pull request?

I set the moderation to be true

I have been trying to test a few different scenarios this evening. The behavior I am seeing is that the notification does not go out until you perform the merge. Also, notifications are sent to visitors who request notifications even if you do not merge their comment.

The behavior I am seeing is that the notification does not go out until you perform the merge

This is correct and it's intended behaviour. You don't want people receiving an email about a comment hasn't (and might not ever be) published.

Also, notifications are sent to visitors who request notifications even if you do not merge their comment.

This isn't really intended behaviour, but I'm a bit torn on it actually. Even if your comment isn't approved, you should still have the right to be notified of other people's comments.
What are your thoughts?

Also, notifications are sent to visitors who request notifications even if you do not merge their comment.

I don't think this is necessary.
If someone leaves an unrelated or violated message, I don't want him to receive further notifications.

If you express that you want to be notified of new comments you should receive those notifications no matter the status of your comment.
I asked some people sitting around me what they would expect and this is the behavior they expected. Probably just need to document all the different flow scenarios so people are aware.

I see your point as well zongren.  If you got some bots leaving comments you did not merge, but they still receive notifications, it could eat into your mailgun calls and lead to real $$$.

Very good points raised here. To avoid duplication, let's move the conversation to #42.


feat: search by text in filters

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #773

Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Screenshots or example output

@Angryman18 Please review.

Thanks, @Angryman18 and @hjaintech for the suggestions. I have incorporated them. Let me know if there are any more suggestions.

Hi @atapas & @koustov
This PR has been approved and is ready for merge. Please have a look.


ajax() type signature error (TS) when string provided

John Lindquist reported that
import {Observable} from 'rxjs/Rx.DOM';
Observable.ajax('http://swapi.co/api/people/1/')
    .subscribe();

gives TS compile error
ERROR in ./src/main.ts
(2,1): error TS2346: Supplied parameters do not match any signature of call target.

Solution suggestion:
I think the type signature should be changed like this:
 export interface AjaxCreationMethod {
-  (): <T>(urlOrRequest: string | AjaxRequest) => Observable<T>;
+  <T>(urlOrRequest: string | AjaxRequest): Observable<T>;
   get: <T>(url: string, resultSelector?: (response: AjaxResponse) => T, headers?: Object) => Observable<T>;
   post: <T>(url: string, body?: any, headers?: Object) => Observable<T>;
   put: <T>(url: string, body?: any, headers?: Object) => Observable<T>;
   delete: <T>(url: string, headers?: Object) => Observable<T>;
   getJSON: <T, R>(url: string, resultSelector?: (data: T) => R, headers?: Object) => Observable<R>;
 }

I also noticed this while migrating test cases, simply deferred definition changes after test cases are checked in. This should be trivial changes, I'll take this up around today.

We really need to have TS type tests in place. Otherwise TS users might see errors like this. I suppose your #1364 will fix that?

#1364 is initial setup to prepare type definition test, so only partially covers for it (because consume definition via test cases can resolve most frequent usage). My plan is leveraging typescript-based test cases to add bunch of type definition test only check if it's written as intended - https://github.com/ReactiveX/RxJS/pull/1189 is one of examples what'll be added in further. In general, I also #1364 to be landed to start further tasks regarding type definition enhancement. Just need it to be reviewed & approved since it introduce broad number of changes along impacting development cycle.


fix: remove file in cached-assets even if not uploaded

Local files remain in local cached-assets when they already exist on the bucket, we should remove them anyway.
I will improve the logic in another PR: create files ONLY when they don't exist on the bucket.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (3c6c79b) 87.65% compared to head (8f79e3a) 86.59%.
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1889      +/-   ##
==========================================
- Coverage   87.65%   86.59%   -1.07%
==========================================
  Files          22       74      +52
  Lines         875     2648    +1773
==========================================
+ Hits          767     2293    +1526
- Misses        108      355     +247

Flag
Coverage Δ

jobs_cache_maintenance
96.66% <ø> (?)

jobs_mongodb_migration
86.32% <ø> (?)

services_admin
?

services_rows
84.16% <ø> (?)

services_search
78.55% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 96 files with indirect coverage changes

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

I will merge this PR, looks like e2e is taking too much time, but I don't think this change is related somehow.


fix for tensorrt_basic_test not being run.

tenssort_basic_test was not being built nor run as part of unit tests.
this fix re-enables the test.

Thanks.


Consider Statsd format for Metric Publisher

Linking to the work @jkschneider did https://github.com/spring-cloud/spring-cloud-stream/pull/1299
We should consider either changing format all together (only Statsd) or allow user to configure

I think this is out of scope of spring-cloud-stream


hello Joey

@jvoermans this corresponds to the yellow boxes.

The code running on the Mega (ugly but working): https://github.com/jerabaul29/LoggerWavesInIce/blob/master/Logger_GPS_SD_VN_Binary_output/Logger_GPS_SD_VN_Binary_output.ino

The VN100 is configured following: https://github.com/jerabaul29/LoggerWavesInIce/blob/master/Logger_GPS_SD_VN_Binary_output/README.txt

There is code for parsing the output (may rely on specific version of some of the packages, and this is python 2.7): https://github.com/jerabaul29/LoggerWavesInIce/tree/master/Logger_GPS_SD_VN_Binary_output_Parser

You get a user manual here: https://github.com/jerabaul29/LoggerWavesInIce/tree/master/UserManual

@jvoermans this is where you can find the code, see previous message.


invalid json response body

I have followed the steps to run vue-storefront and vue-stroefront-api and everything was working fine.
The problem is when I turn off my laptop the npm process are stoped(?) Then, when I want to run it again I am entering into the vue-storefront and vuestorefront-api directory and run npm run dev command.
I get info in the console that: Vue Storefront API started at http://localhost:8080 and in other window Vue Storefront Server started at http://localhost:3000
But when I go in browser to http://localhost:3000 at first it says default message "Thanks ..." and then  in console I get:

and finally frontend is not loading.
One again at first when I used yarn installer It was working fine.
Thanks

I needed to "docer-compose up" first in vue-storefront-api


Misleading future documentation?

Hi,
the async-std documentation hints that there is a join futures combinator, but according to issue #14 this is still missing: link.
I recognize that this may be an issue of lower importance, and might not be trivial to fix. Feel free to close this issue if this won't be fixed.
Best,
ambiso

Now that #14 is closed, this issue can be closed as well.


[PPL-Lang]support earliest/latest date-time functions

Is your feature request related to a problem?
As a PPL query syntax for easily supporting predefined simple time ranges such as:
earliest week, latest day, latest month, earliest hour.
Supporting for the predefined time units:

second - s
minute - m
hour  - h
day - d
week - w
month - mnt
quarter - qrt
year - yr

What solution would you like?
 source = logs | where status > 200 AND (earliest=-24h AND latest<@d)
 source = logs | where status > 200 AND  (earliest=-5d@w1 AND latest=@w6)
 source = logs | where status > 200 AND (earliest='2023-11-15:20:00:00' AND latest='2023-11-22:20:00:00')

@YANG-DB wonder do you have more documentations to provide as reference?
If I understand this correct, earliest and latest itself will be served as an identifier, which will be evaluated and substituted with the earliest and the latest value from a particular timestamp column on the dataset.
If that is case, should the function also ask for the timestamp column as argument for the computation? (Assume there are multiple timestamp columns appear on the dataset).
Also what's the meaning of the @ sign from the first usage?
Thanks,

@YANG-DB wonder do you have more documentations to provide as reference?
If I understand this correct, earliest and latest itself will be served as an identifier, which will be evaluated and substituted with the earliest and the latest value from a particular timestamp column on the dataset.
If that is case, should the function also ask for the timestamp column as argument for the computation? (Assume there are multiple timestamp columns appear on the dataset).
Also what's the meaning of the @ sign from the first usage? Thanks,

Hi

You are correct that we need an explicit reference to the timestamp column
IMO the format should be as follows: earliest=[+|-] <time-value(integer)><time-unit(s/m/h/w...)>@<time-unit(s/m/h/w...)>
so in this example (earliest=-24h AND latest<@d) the earliest would be the last 24 hours within the last day ( @d)

@YANG-DB To clarify on the reference syntax and usage, will this be similar to the Splunk counterpart?
https://docs.splunk.com/Documentation/SCS/current/Search/Timemodifiers

@YANG-DB To clarify on the reference syntax and usage, will this be similar to the Splunk counterpart?
https://docs.splunk.com/Documentation/SCS/current/Search/Timemodifiers

Yes in general

@YANG-DB. I've taken a look through the above. It looks like a first step would be to add support for converting relative time strings to the datetime data type. I believe that this would sufficient, along with the existing comparison operators, to implement the desired functionality. If you also want to better align the syntax with Splunk, we could then add new functions earliest and latest to facilitate this? Let me know what you think!
Add Support for Relative Time
Add support for automatically converting relative time strings to the datetime data type, and then use the existing comparison operators.
 source = logs | field_name >= '-24h' AND field_name <= '<@d'
 source = logs | field_name >= '-5d@w1' AND field_name <= '@w6'
 source = logs | field_name >= '2023-11-15:20:00:00' AND field_name <= '2023-11-22:20:00:00'

New Functions
Add new functions earliest and latest that take a field name and a dateime time string. This option will be closest to the syntax used in Splunk (but would duplicate some of the functionality already provided by the comparison operators).
 source = logs | earliest(field_name, '-24h') AND latest(field_name, '<@d')
 source = logs | earliest(field_name, '-5d@w1') AND latest(field_name, '@w6')
 source = logs | earliest(field_name, '2023-11-15:20:00:00') AND latest(field_name, '2023-11-22:20:00:00')

@YANG-DB. I've taken a look through the above. It looks like a first step would be to add support for converting relative time strings to the datetime data type. I believe that this would sufficient, along with the existing comparison operators, to implement the desired functionality. If you also want to better align the syntax with Splunk, we could then add new functions earliest and latest to facilitate this? Let me know what you think!
Add Support for Relative Time
Add support for automatically converting relative time strings to the datetime data type, and then use the existing comparison operators.
 source = logs | field_name >= '-24h' AND field_name <= '<@d'
 source = logs | field_name >= '-5d@w1' AND field_name <= '@w6'
 source = logs | field_name >= '2023-11-15:20:00:00' AND field_name <= '2023-11-22:20:00:00'

New Functions
Add new functions earliest and latest that take a field name and a dateime time string. This option will be closest to the syntax used in Splunk (but would duplicate some of the functionality already provided by the comparison operators).
 source = logs | earliest(field_name, '-24h') AND latest(field_name, '<@d')
 source = logs | earliest(field_name, '-5d@w1') AND latest(field_name, '@w6')
 source = logs | earliest(field_name, '2023-11-15:20:00:00') AND latest(field_name, '2023-11-22:20:00:00')

Yes sounds good to me
Also yes for earliest and latest

Yes sounds good to me Also yes for earliest and latest func

Great, thanks @YANG-DB. I have raised #991 for adding support for relative date-times. Once that is completed, I'll come back and add the earliest/latest functions themselves.

[Catch All Triage - 1, 2, 3]
@YANG-DB Can you please help make sure this repo is triaged as part of a team triage weekly? Thanks.


intermittent test failure

[ERROR] Failures:
[ERROR]   HTTPServerTest.lambda$null$2:106 Expected true
[ERROR] Tests run: 30, Failures: 1, Errors: 0, Skipped: 0
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on project api-server: There are test failures.
[ERROR]

Fixed on master


update usage with tfe.local_computation decorator

Merge after tf-encrypted/tf-encrypted#598

Merge after tf-encrypted/tf-encrypted#598

This brings up an interesting challenge.  Really this probably shouldn't merge until this PR is both merged and released.

agreed -- it's been merged but not released, so let's merge this when it's been released this week


Port to Python 3

This code only runs in Python 2. It would be much better if it ran in Python 3.

See also: https://github.com/jminor/omgifol/issues/7


chore(@toss/utils): fix ElementType import

Overview

Change import path local to @toss/utility-types
Because this is likely to be a dualization of management.
PR Checklist

[x] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

This is redundant:)
ref https://github.com/toss/slash/pull/152#discussion_r1027409782

Thank you for your kind explanation.

It could be a waste for people who don't use typescript!

I think this is different between dependencies and devdependencies.
I use @toss/utility-types for devdependencies that is not installed for other users (who install @toss/utils)
For example, if you install @toss/react that have typescript package in devdependencies.
But users node_modules is installed without typescript package includes any devdependencies.

reference. whats-the-difference-between-dependencies-devdependencies-and-peerdependencie

Actually, when using ElementType from @toss/utility-types, we should use it as a regular dependency (not a devDependency). Otherwise, the returned type from pick or omit would not be inferred.
(Because pick returns Pick<ObjectType, ElementType<KeyTypes>>, and unless we install @toss/utility-types, the definition of ElementType is missing...)

This is a very tricky situation.

and unless we install @toss/utility-types, the definition of ElementType is missing...)

Oh,,, I missed of the impact of an installed package on another package.
It seems that @toss/utils already provides a function of typed utility. (e.g pick, omit, object-values etc..)
My solution is to add more util types used in utils packages like ObjectKeys to @toss/utility-types.
I think it's the difference between providing a lighter package to the user or guaranteeing the maintenance of the @toss/slash package.

Adding "@toss/utily-types" to the dependencies is acceptable since it doesn't increase the size of the runtime bundle where it's utilized, despite potentially increasing the size of "@tossteam/utils" when fetched from npm.

Adding "@toss/utily-types" to the dependencies is acceptable since it doesn't increase the size of the runtime bundle where it's utilized, despite potentially increasing the size of "@tossteam/utils" when fetched from npm.

Thank you for your kind explanation.
I have finished changing from devDependencies to dependencies.
chore: add @toss/utility-types to dependencies

Closing this pull request since this became stale. But we picked this change in the following commit: https://github.com/toss/slash/commit/063821639b8680bb1d0348306f43d26fb004a192. Thanks for your contribution!