V1.0 prep

@zsteinmetz, creating this PR so that we can have everything in one place. Below I am bringing over comments and check boxes from the other 3 PRs and assigning each of us to tasks. Would it be alright if I merge all these to V1.0 prep?
Package Down Documentation (@wincowgerDEV) https://github.com/wincowgerDEV/OpenSpecy-package/pull/126

[ ] Update SOP with new functionality and explanations.
[ ] Update homepage.
[x] Customize the website to look its best.
[ ] Set URL address to something like OpenSpecy.org.

Functions for managing spectra for v1.0 (@zsteinmetz) https://github.com/wincowgerDEV/OpenSpecy-package/pull/125

[x] finalize functions to align and concatenate spectra required by #124
[x] add test routines
[x] update docs
[x] check if everything works as expected

Reading functions for v1.0 (@zsteinmetz) https://github.com/wincowgerDEV/OpenSpecy-package/pull/124

[x] functions to align and concatenate spectra required before multiple spectra could be read at once, e.g. from a zip file
[x] finalize reading functions
[x] add test routines and update sample files
[x] update docs
[x] check if everything works as expected

Functions to be renamed/changed (@zsteinmetz)

[x] sample.OpenSpecy() -> sample_spec()
[x] correlate_spectra() -> cor_spec()
[x] collapse_spectra() -> collapse_spec()
[x] process_spectra() -> process_spec()
[x] identify_spectra() -> ident_spec()
[x] characterize_particles()  -> def_features()
[x] heatmap_OpenSpecy() -> heatmap_spec()
[x] plot_OpenSpecy() -> plotly_spec()
[x]  to_hyperSpec() -> as_hyperSpec()
[x] subtr_bg() -> subtr_baseline()
[x] replace magrittr pipe %>% with native R pipe |> were possible
[x] replace object argument with x where possible
[x] update run_app()

General checks and CRAN compliance (@zsteinmetz)

[x] passing urlchecker::url_check()
[x] passing GitHub checks
[x] passing devtools::check(remote = TRUE, manual = TRUE)
[x] passing devtools::check_win_devel()
[x] optimizing/adding tests (still missing for read_envi and read_envi_nic)
[x] check docs for consistency and spelling mistakes
[x] finalize dependencies in DESCRIPTION
[ ] update NEWS.md
[ ] update cran-comments.md

Checking all these R files for completion and tests:

[ ] adj_intens
[ ] as_OpenSpecy
[ ] collapse_particles
[ ] conform_spec
[ ] data_norm
[ ] flatten_range
[ ] gen_OpenSpecy
[ ] human_ts
[ ] io_spec
[ ] manage_lib
[ ] manage_spec
[ ] OpenSpecy-package
[ ] plots_reports
[ ] process_spectra
[ ] raman_hdpe
[ ] read_ext
[ ] read_multi
[ ] read_opus_raw
[ ] read_opus
[ ] restric_range
[ ] run_app
[ ] share_spec
[ ] signal_noise
[ ] smooth_intens
[ ] spec_res
[ ] subtr_bg
[ ] test_lib
[ ] zzz

@zsteinmetz and @nickleong20 I have gone through everything now besides the run_app function. I think it is broken because the app hasn't been updated with the new functions yet so I am going to pivot to work on that next. @zsteinmetz do you know why the automated checks are failing? I can seem to figure out how to fix them.

Awesome work, @wincowgerDEV and @nickleong20! :heart_eyes:

I think it is broken because the app hasn't been updated with the new functions yet so I am going to pivot to work on that next.

Yeah! We'll make run_app() work once the Shiny app is up to speed again. Shouldn't be a big deal.

@zsteinmetz do you know why the automated checks are failing? I can seem to figure out how to fix them.

The workflow version we've been using is now deprecated. I can bump it to the next version when I'm reviewing the code next week. Just did the same with my other package.

Yup, totally agree to add Nick!
On Fri, Jul 28, 2023 at 11:10 AM Zacharias Steinmetz <
@.***> wrote:

@.**** commented on this pull request.
In DESCRIPTION
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#discussion_r1277930451
:

@@ -1,13 +1,13 @@
Package: OpenSpecy
Type: Package
Title: Analyze, Process, Identify, and Share Raman and (FT)IR Spectra
-Version: 0.9.5
-Date: 2022-07-06
+Version: 1.0.0
+Date: 2023-07-28
@.***: c(person("Win", "Cowger", role = c("cre", "aut"),

We'll need to add @nickleong20 https://github.com/nickleong20 here,
won't we?
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#pullrequestreview-1552681136,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU75ME6BYHCFN5KNEMLXSP57XANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
´¯·.¸¸.·´¯·.´¯·.¸¸.·´¯ツ ------------------------------
*Win Cowger, PhD *
Pronouns: he/him
Research Scientist
Moore Institute for Plastic Pollution Research
Contact Info
515-298-3869  | @.*** | @Win_OpenData
https://twitter.com/Win_OpenData
Websites
Personal Website: www.wincowger.com
Currently Employed: https://mooreplasticresearch.org/
Alumni Of: https://www.thegraylab.org/
Project Websites: www.openspecy.org
Research Gate: https://www.researchgate.net/profile/Win-Cowger
Github: https://github.com/wincowgerDEV
OSF: https://osf.io/kxeh5/

Good point, may want to implement ourselves just so we don't have to back
them up or wait.
On Fri, Jul 28, 2023 at 11:16 AM Zacharias Steinmetz <
@.***> wrote:

@.**** commented on this pull request.
In R/read_multi.R
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#discussion_r1277937445
:

              ignore.case = T, file)) {

ex <- strsplit(basename(file), split="\.")[[1]][-1]
os <- do.call(paste0("read_", tolower(ex)), list(file = file, ...))
} else if (grepl("(\.zip$)", ignore.case = T, file)) {
os <- read_zip(file = file, ...)
} else {
os <- read_spec(file = file, ...)
}

return(os)
+}

+#' @rdname read_multi
+#'
+#' @importFrom utils unzip
+#' @importFrom hySpc.read.ENVI read_ENVI_Nicolet
If we want to submit v1.0.0 to CRAN, we can't use the hySpc.read.ENVI
package as long it's not on CRAN itself. We could either motivate them to
submit soon or implement those functions on our own.
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#pullrequestreview-1552691527,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU2EI5JPZ6OBKIOCWC3XSP6Y7ANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
´¯·.¸¸.·´¯·.´¯·.¸¸.·´¯ツ ------------------------------
*Win Cowger, PhD *
Pronouns: he/him
Research Scientist
Moore Institute for Plastic Pollution Research
Contact Info
515-298-3869  | @.*** | @Win_OpenData
https://twitter.com/Win_OpenData
Websites
Personal Website: www.wincowger.com
Currently Employed: https://mooreplasticresearch.org/
Alumni Of: https://www.thegraylab.org/
Project Websites: www.openspecy.org
Research Gate: https://www.researchgate.net/profile/Win-Cowger
Github: https://github.com/wincowgerDEV
OSF: https://osf.io/kxeh5/

Yup, totally agree to add Nick!

@nickleong20: Do you have an ORCID?

Yup, totally agree to add Nick!

@nickleong20: Do you have an ORCID?

Yup, totally agree to add Nick!

@nickleong20: Do you have an ORCID?

@zsteinmetz Yes, it is 0009-0008-3313-4132. Thank you!

devtools::check() running again, currently with:
2 errors ✖ | 4 warnings ✖ | 3 notes ✖

Mostly coming from missing documentation and some rogue tests. I'll go through it step by step.

@nickleong20 and @zsteinmetz, was thinking about a small patch this morning to the as_OpenSpecy function but want to pass it by you first to make sure you agree and that it won't likely cause some huge crash. After going through all of the functions I realized that there are a few assumptions that the functions make which we might be able to help ensure happen correctly or at least provide a test through is_OpenSpecy to make sure it works.

One is that the wavenumber range is continuous, if the wavenumber range is scrambled stuff like baseline correction won't work out of the box. I think I could add a reorder function to as_OpenSpecy just to ensure that the wavenumbers will be ordered for all the functions. Maybe we force wavenumbers to be ordered from greatest to least?

Another is that the column names in OpenSpecy$spectra are unique because we currently allow people to filter and sort the Open Specy objects by column name. We could make a check to see if the column names are unique, if they are not then we digest the spectral intensities for each spectrum and use that as the column name and add that to the metadata. There could also be a scenario where people have uploaded duplicate spectra and those should actually be collapsed, but then I can also imagine some people wanting to be lazy with their analysis and just allowing duplicates for the things they are doing and working around it.

Let me know what yall think.
Win

@zsteinmetz Update for the week, I think we are getting super close. I got the app working again with all the new features we added, really happy with its functionality, still some aesthetic bugs but W/E. Would it be alright with you if I merge that PR for the app now? I think that will make finishing the run_app function easier and I think it is pretty stable as is as long as the user is using our updated package. I spoke with @nickleong20 about the comment above and I think for now we just provide a warning message for those and we can think about more streamlined requirements later if users run into common bugs there.
@nickleong20 went through all the functions and tests and so did I and Nick is currently working on:

[ ] update SOP.

After we get the package finalized and submitted to cran I will do the packagedown integrations to build out our website.

@nickleong20 and @zsteinmetz, was thinking about a small patch this morning to the as_OpenSpecy function but want to pass it by you first to make sure you agree and that it won't likely cause some huge crash. After going through all of the functions I realized that there are a few assumptions that the functions make which we might be able to help ensure happen correctly or at least provide a test through is_OpenSpecy to make sure it works.

Very good point! I'll comment directly on your code ..

@zsteinmetz Update for the week, I think we are getting super close. I got the app working again with all the new features we added, really happy with its functionality, still some aesthetic bugs but W/E. Would it be alright with you if I merge that PR for the app now? I think that will make finishing the run_app function easier and I think it is pretty stable as is as long as the user is using our updated package. I spoke with @nickleong20 about the comment above and I think for now we just provide a warning message for those and we can think about more streamlined requirements later if users run into common bugs there.

You're speaking of https://github.com/wincowgerDEV/OpenSpecy-shiny/pull/21, right? Fine with me to merge :+1:
This PR here needs a bit more tweaking though before you can merge. I really like to see all tests passing before it goes into main.

@wincowgerDEV and @nickleong20, I was thinking about renaming some of the functions to make them more consistent throughout the package. For instance, we often abbreviated "spectra" with "spec" in function names but "process_spectra" has the full name. What's your take on this? I would, of course, provide you with a list of all changed function names.

Down to
1 error ✖ | 2 warnings ✖ | 1 note ✖

Also noticed some places the first object is named object and some places it's named x. Perhaps we should make that consistent too.

I already stumbled upon it. Working on making those consistent as well.

characterize_particles()  -> ?

Should we keep calling it "particles"? The function might not be restricted to particles but could also be used for fragments, fibers, or whatever form, right? What about using the term "item" or "feature"?

characterize_particles()  -> ?

Should we keep calling it "particles"? The function might not be restricted to particles but could also be used for fragments, fibers, or whatever form, right? What about using the term "item" or "feature"?

I like characterize_feature, I guess you could use the function to even separate regions on a single particle if you wrote the  logical statement that way.

I like characterize_feature

.. and what about "characterize"? We could also use "define" or "ident" .. maybe that would make it a bit clearer? :thinking:

.. and what about "characterize"? We could also use "define" or "ident" .. maybe that would make it a bit clearer? 🤔

That function primarily measures the particles and gives them unique IDs. I think either define or identify could work. There is also an identify_spec function so we may want to do define so it isn't confused with the other function.

Btw, tests are running way too long. We shouldn't download the complete library for testing purposes. The tests are the last remaining error now :partying_face:
1 error ✖ | 0 warnings ✔ | 0 notes ✔

Working on this right now.

 Yeah agree that we shouldn't download the whole library every time, maybe we can move that test to a place where it is only tested on an as-needed basis? Then just test with the test_lib internal dataset?

Yeah, I was thinking about something similar. Looking into it tomorrow!

We're going to need a new test library on OSF, right? One that follows the same naming convention as the other new libraries; something like both_test.rds. The data structure should be the same as in both_derivative.rds containing both Raman and FTIR spectra. At the moment, it's Raman only, I guess. A subset of 200-300 spectra and less than 1 MB total file size would be ideal. Is there an easy way producing something like this?

The easiest way would be to use the sample_spec and/or filter_spec
functions on the both_derivative library.
On Thu, Aug 10, 2023, 3:40 AM Zacharias Steinmetz @.***>
wrote:

We're going to need a new test library on OSF, right? One that follows the
same naming convention as the other new libraries; something like
both_test.rds. The data structure should be the same as in
both_derivative.rds containing both Raman and FTIR spectra. At the
moment, it's Raman only, I guess. A subset of 200-300 spectra and less than
1 MB total file size would be ideal. Is there an easy way producing
something like this?
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#issuecomment-1672980562,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJUZBU46FAAHCYRXX3DLXUS3ATANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

I guess making sure there are examples for each plastic type could be good,
that way it can be used easily for our primary use case.
On Thu, Aug 10, 2023, 6:12 AM Zacharias Steinmetz @.***>
wrote:

Any recommendation which spectra to use?
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#issuecomment-1673194709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU7Q3IX5HLPC6S3Q3RTXUTM4NANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Do you recall how you did it last time?

Do you recall how you did it last time?

@zsteinmetz
Just went ahead and created it here: https://osf.io/x7dpz/
Basically, I ran this:
write_spec(
filter_spec(library, distinct(library$metadata, SpectrumType, polymer_class, .keep_all =T)$sample_name),
"both_test.rds")

Good catch. Make rel should be applied to each spectrum separately as a
general rule. I can imagine some fringe use cases where we want it to apply
to everything at once but I wouldn't plan for them.
On Tue, Aug 15, 2023, 3:08 AM Zacharias Steinmetz @.***>
wrote:

@.**** commented on this pull request.
In R/adj_range.R
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#discussion_r1294416158
:

if (make_rel) x$spectra <- make_rel(filt) else x$spectra <- filt

return(x)
+}

+#' @rdname adj_range
+#'
+#' @export
+flatten_range <- function(x, ...) {

UseMethod("flatten_range")
+}

+#' @rdname adj_range
+#'
+#' @export
+flatten_range.default <- function(x, ...) {

stop("object 'x' needs to be of class 'OpenSpecy'")
+}

+#' @rdname adj_range
+#'
+#' @export
+flatten_range.OpenSpecy <- function(x, min_range, max_range, make_rel = TRUE,

                               ...) {

if(length(min_range) != length(max_range)) {
stop("min_range and max_range need to be the same length")
}
if(any(vapply(1:length(min_range), function(y) {
min_range[y] > max_range[y]
}, FUN.VALUE = logical(1)))) {
stop("all min_range values must be lower than corresponding max_range")
}
filt <- x$spectra[,lapply(.SD, function(y) {
.flatten_range(wavenumber = x$wavenumber,

              spectra = y,

              min_range = min_range,

              max_range = max_range)

})]

if (make_rel) x$spectra <- filt[, lapply(.SD, make_rel)] else x$spectra <- filt

Is make_rel() supposed to normalize each spectrum in $spectra
individually or should they be normalized together? Currently we have both
types here and they differ between restrict_range() (L74) flatten_range()
(L113).
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#pullrequestreview-1578294460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU6KG2YHPM5TMQL63I3XVNDAPANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @zsteinmetz, thanks for all the hard work on this! Commenting on the last todos: agree with your updates to the two functions. I think we can keep corspec slow for now. I'm working on that a ton and we may update the package later with some improvements to that function or create new functions that are faster (probably better to avoid breaking). I can add the secrets to github soon. Now that we have the function names and variables settled I can go through the shiny app and make it stable again and push the package down updates.

I can add the secrets to github soon.

Hey @wincowgerDEV, sorry to bother you with the secrets again :upside_down_face: Could you maybe add them to the repo that I can adjust the workflow?

Hey Zacharias, Sorry about that, just added them! Warm Regards, Win

Thanks, man!

From my end, we're good to go once the SOP and run_app() are updated. The latter shouldn't be a big deal. Let me know if I can help with the Shiny app.

Right on man! I will spend some time on the shiny app this week and @nickleong20 will work on the SOP after that. Should be ready to roll in the next few weeks. I definitely never pass up an opportunity to get your input, maybe I will run through the shiny app update first and once I have it stable from my perspective you could take another look before we announce the full update?

Good news! I found a way how to add non-CRAN repos like https://r-hyperspec.github.io/pkg-repo/ to the OpenSpecy package. They can only go into Suggests, so no hard dependencies, but still. This might be a way to work with future versions of the hySpc.* family to avoid forking all their code. Nothing for v1.0.0, I guess, but something to keep in mind; especially if they fix issues like https://github.com/wincowgerDEV/OpenSpecy-shiny/issues/30 ...

Righteous!
That's definitely helpful. I've been noticing an uptick in never-CRAN
packages lately that choose not to submit to CRAN because they break too
many of the rules but they are really good at specific operations so this
will definitely open some doors there.
On Wed, Aug 23, 2023, 6:35 AM Zacharias Steinmetz @.***>
wrote:

Good news! I found a way how to add non-CRAN repos like
https://r-hyperspec.github.io/pkg-repo/ to the OpenSpecy package. They
can only go into Suggests, so no hard dependencies, but still. This might
be a way to work with future versions of the hySpc.* family to avoid
forking all their code. Nothing for v1.0.0, I guess, but something to keep
in mind; especially if they fix issues like
wincowgerDEV/OpenSpecy-shiny#30
https://github.com/wincowgerDEV/OpenSpecy-shiny/issues/30 ...
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#issuecomment-1689978785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU7KVXUIGBWRITFCWZTXWYBKBANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Looks like expect_contains is throwing things off, may need to update testthat

Are you running the latest testthat version? expect_contains() has been introduced just lately.

All clear!

Are you running the latest testthat version? expect_contains() has been introduced just lately.

Just updated the testthat and everything is working :)

Just added this specific requirement to the package description.

Fasho! Good call.
Do you know where a pdf file might be created during the tests? Currently getting a pdf with images of spectra in it called Rplots in the testthat folder when I run the tests.

Do you know where a pdf file might be created during the tests? Currently getting a pdf with images of spectra in it called Rplots in the testthat folder when I run the tests.

Dunno; saw it once but it didn't reappear when I deleted it.

Dunno; saw it once but it didn't reappear when I deleted it.

Fasho, It appears to be something with the plot.OpenSpecy because the plots are the same but not totally positive, it's low priority, only occurs when the tests are run for me and will be occurring in a temp environment on cran so I think it is fine. Will proceed with the shiny app dev.

Updated the app now with the new functions and the run_app function is working but I don't have a way to test that the app actually runs yet, just testing some silly logic for the test. @zsteinmetz if you have time to check the app and run_app function that would be great but also I am down to just submit to CRAN. I think the community will end up fleshing out any remaining bugs for us and we can debug as we go.

Wow, that was fast! :heart_eyes:
Automatically testing Shiny apps as a whole is not as easy as testing package functions; one of the many reasons why packages underneath an app are really helpful. There are some shinytest packages but I haven't looked into them yet and I guess it would make more sense to add them to the Shiny app itself rather than to the package.
What I did now is adding some test logic to run_app() so that all function code is tested but the last line running the actual app. With this, we make sure that everything is in order from the package end and keep everything else to the Shiny app (and future tests there).
So let's just wait for the SOP. In the meantime, I'm going to complete the NEWS file and CRAN comments to get ready for submission.

Thanks for doing that! Good points about the app testing. In the long run, I think we will want to create some modules or try out other ways for testing the app but currently it's all pretty manual. I'll work on the SOP, if I can't get to it today, I should be able to tomorrow.

@zsteinmetz, writing the SOP I realized that the identification pipeline is a little clunky. I really like that the user just has one function for the process_spec and wondering if we should do a single monolith for the identification, too, that basically nests cor_spec and ident_spec into a logical arrangement and the user just provides the parameters that they need for each in one function. This will also allow us to integrate additional options like AI based identification later on and the user just needs to remember that they have to use that one function for all of their identification needs. What do you think?

@wincowgerDEV Yeah, great idea! This caught my eye as well when I reviewed the code but I apparently forgot about it upon working on other stuff. Since we already have an ident_spec() function, the monolithic function could become our new match_spec(). What do you think?
I won't have much time until mid/end of next week.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@ee654c9). Click here to learn what that means.
 Consider uploading reports for the commit 7c0671d to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #129   +/-   ##
=======================================
  Coverage        ?   83.05%
=======================================
  Files           ?       26
  Lines           ?     1416
  Branches        ?        0
=======================================
  Hits            ?     1176
  Misses          ?      240
  Partials        ?        0

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

@zsteinmetz just want to pass this by you real quick. With the process_spec function, I was thinking that we try to set the defaults to whatever we think will maximize the signal to noise and streamline the identification process. I want the user to be able to just run process_spec(spectrum) then the match_spec and get a good result most of the time quickly. I changed the defaults to conduct the absolute derivative with make_rel at the end because in most cases I have tested that algorithm does everything you need super quickly. Let me know what you think, I can change it back.

@zsteinmetz just want to pass this by you real quick. With the process_spec function, I was thinking that we try to set the defaults to whatever we think will maximize the signal to noise and streamline the identification process. I want the user to be able to just run process_spec(spectrum) then the match_spec and get a good result most of the time quickly. I changed the defaults to conduct the absolute derivative with make_rel at the end because in most cases I have tested that algorithm does everything you need super quickly. Let me know what you think, I can change it back.

Sounds good to me. No objections!

Appreciate ya @zsteinmetz!

@wincowgerDEV What do you think when we might be ready to merge into main? I am asking because I actually don't like to see the main branch fail. Currently it's only because of that GitHub Action deprecation but still. If we need more time here, no problem. Then I just cherry pick the GitHub Action commits and merge them already before merging the whole thing. If it's only documentation left, I guess we could merge this one here already and continue working on the SOP on this or another branch.

@wincowgerDEV I just split up the SOP vignette into three separate ones: the main SOP, the advanced spec part, and the SpectraGryph stuff. The idea behind was (1) to improve clarity also with respect to packagedown and (2) to be more flexible which vignettes to exclude for the CRAN package to keep the file size down. For now, I only added the main SOP to be submitted to CRAN excluding the two other ones that only go to packagedown. What do you think? I can revert it if it doesn't make sense to you, of course.

Sure! I'm going to merge as soon as all checks have passed.
We could even think about splitting the package and app parts in the current SOP vignette. This would make the actual package vignette super small, because we don't need all the screenshots, and would give us more space for sample files and so on. The app vignette could then go to packagedown only.

That's not a bad idea. Was going back and forth about whether to do that. I
think we originally kept them together so that the app could expedite the
learning process for the package but I totally get that now we have a lot
more app features and those each have images and that can make a big file
size for the package. Maybe in the app vignette and the package vignette we
try to maintain the same headings to make it easy to search between the
two?
On Wed, Aug 30, 2023, 7:52 AM Zacharias Steinmetz @.***>
wrote:

Sure! I'm going to merge as soon as all checks have passed.
We could even think about splitting the package and app parts in the
current SOP vignette. This would make the actual package vignette super
small, because we don't need all the screenshots, and would give us more
space for sample files and so on. The app vignette could then go to
packagedown only.
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#issuecomment-1699335129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU22YOK2OQ36FAE5K4DXX5HRPANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yeah that's true, maybe even add a link to the header on the other package
vignette too! I like keeping the package as small as possible, there may
come a time we want to make another big push in a few years and we will
want the space for test files or porting over other people's 1000 line
codes 😂.
On Wed, Aug 30, 2023, 8:00 AM Zacharias Steinmetz @.***>
wrote:

Maybe in the app vignette and the package vignette we try to maintain the
same headings to make it easy to search between the two?
Sounds good! We could also reference the package functions in the app
vignette and vice versa.
—
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy-package/pull/129#issuecomment-1699349628,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU44YXP2Z5UONO7ZEVDXX5IRNANCNFSM6AAAAAA2C62GJI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Refactor demo store to use GitHub artifacts

Refactor DemoStore to use GitHub releases from this repo: bigym_data.
Additional changes:

Added persistent cache for demonstrations created locally from lightweight dataset demos.
Simplified demo player tools/demo_player by removing redundant functionality.

I'm having this bug when caching the demos.
Traceback (most recent call last):
  File "/Users/xiao/miniconda3/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
    self.run()
  File "/Users/xiao/miniconda3/lib/python3.10/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/xiao/work/robobase/robobase/envs/bigym.py", line 184, in _get_demo_fn
    demos = demo_store.get_demos(
  File "/Users/xiao/work/bigym_release/demonstrations/demo_store.py", line 155, in get_demos
    self.cache_demo(demo, frequency)
  File "/Users/xiao/work/bigym_release/demonstrations/demo_store.py", line 81, in cache_demo
    file_path = demo.save(Path(temp_dir) / demo.metadata.filename)
  File "/Users/xiao/work/bigym_release/demonstrations/demo.py", line 285, in save
    save_file(demo_dict, path, self.safetensor_metadata)
  File "/Users/xiao/work/bigym_release/demonstrations/demo.py", line 317, in safetensor_metadata
    return self.metadata.ready_for_safetensors()
  File "/Users/xiao/work/bigym_release/demonstrations/utils.py", line 132, in ready_for_safetensors
    "environment_data": json.dumps(asdict(self.environment_data)),
  File "/Users/xiao/miniconda3/lib/python3.10/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/Users/xiao/miniconda3/lib/python3.10/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/Users/xiao/miniconda3/lib/python3.10/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/Users/xiao/miniconda3/lib/python3.10/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type ListConfig is not JSON serializable

After looking into it, the bug seems to be that in the camera configs, resolution is ListConfig rather than list. I temporarily patched it and pushed to this branch, but I think we need a more elegant fix.

For path of cached demos seem to have the wrong version? Currently mine is 0.9.0, see my path below
/Users/xiao/.bigym/demonstrations/0.9.0

For path of cached demos seem to have the wrong version? Currently mine is 0.9.0, see my path below
/Users/xiao/.bigym/demonstrations/0.9.0

I tested again and this is the only issue left. Otherwise it is good to go!

Dataset and BiGym are versioned separately, so it’s intended that demonstrations have v0.9.0.


DBZ-8290 Increment binlog event counter

https://issues.redhat.com/browse/DBZ-8290

It's little bit questionable which records we should count, as we the message is printed when binlog client is disconnecting, I'd count all the records which binlog client processed, not only records produced by Debezium.

@vjuranek Yes, good decision. Applied, thanks!


Cant use heals on slime people

Description
You can no longer use topicals or syringes on slime people(again) as it prioritizes putting things in their internal storage over healing.
Reproduction
1 Use brute pack/gauze/ointment/syringe on hurt slime
2 Be sad as the item in now in them

Did you experience this just now on wizden?

Updated the Issue to better reflect whats going on


Stuck at Test Case #8 not sure how to proceed

Summary
Stuck at Test Case #8 for a while
Description
I believe might be the queuing up of customers seeing as how customer 9 has queued up for the first server queue instead of the second one.
I believe I have followed the instructions:
"if all servers are serving customers, then the customer that just arrived scans the queues from 1 to N, joins the first queue that is not full (not necessarily the shortest) and waits in the queue (WAIT event). Note that a customer that chooses to queue joins at the end of the queue. "
So I have trouble seeing the issue, any help is appreciated.
Screenshots (if any):

Just from the errors, my best guess is that it seems to be a problem with the checking of the server queue given there are consecutively "44.000 4 serves by 1" and "44.000 7 serves by 1". Customer 7 should join the queue (WAIT event) but not be served.
The error of "9 serves by 1" also seems to be caused by the same error since for some reason the program is not registering that server 1 is not free between 44.000 and 57.000 while it's serving customer 4.

I got the same error as what you got at line 25 & 26
It depends on your implementation, if you were updating
Server along the way, you might want to check if your Server was updated correctly. Currently what is happening is that the serve time of customer 7 is taking in the time the service ends for customer 3.
Not sure if the problem you are facing might be slightly different from mine, as your served time for customer 5 seems to affected even though customer 5 arrived earlier than other customers behind

Thanks for all the comments, the discrepancy was because I did not update the queue properly during the transition from Wait to Serve.


Large file - exception out of memory

Having issues with a 6GB ntds.dit file... This is your debug output.
Called: NtdsAudit::EnumerateMSysObjects
Found 3342 datatable column names
Completed in 00:00:00.2312898
Called: NtdsAudit::EnumerateLinkTable
Ignored 54972 deleted backlinks
Found 1377099 backlinks
Completed in 00:00:03.0407978
Called: NtdsAudit::EnumerateDatatableTableLdapDisplayNames
Failed to match 2464 LDAP display names to datatable column names
Matched 1295 LDAP display names to datatable column names
Completed in 00:00:07.2350478
Called: NtdsAudit::EnumerateDatatableTable
Skipped 85197 deleted objects
Enumerated 612378 objects
Completed in 00:00:34.9476480
Called: NtdsAudit::DecryptSecretData
Failed to decrypt supplemental credentials for 'user1' with error: Exception of type 'System.OutOfMemoryException' was thrown.
Failed to decrypt supplemental credentials for 'user2' with error: Exception of type 'System.OutOfMemoryException' was thrown.
Let me know how I can help.. I tried to open the project in VS but am having issues getting everything to link up correctly so I can't compile.. I can further debug there if you can assist with all the dependencies around VS.
Thanks

Run same file on a machine with only 4GB of RAM.  There may be an issue with addressing larger memory spaces. Ran against a much larger DIT and it worked only on a machine with 2 CPUs and 4GB of RAM.


Building on Huwaei Honor - Launching on iPhone 6s

Hello, I'm building my experience with my Huawei Honor 8 Pro which has a bigger screen resolution than the iphone 6.
I build my app for iOS and launch it but when I put it in my cardboard it's very blurred do you know why it hasn't been transformed properly for the iphone ?
I'm on iOS 10.3.3 and on my Xcode project I have about 120 warning regarding deprecated method, are you able to update your xcode project for the latest version of IOS ?
Thanks for your help
Michael

Hi Michael, have you calibrated the device at least once before entering VR mode? This has to be done for all vr experiences built with Google VR.

What you mean by calibrating ? lol I did the strange things on the google website with a random scene where I have to generate a QR code but the problem is that it didn't make any difference ^^

There should be a QR code on your physical cardboard viewer like in the image below. By scanning this code with your iphone, it will calibrate the sodtware so that the scene is no longer blurry. Do you have a QR code on your cardboard device? If not, you should be able to go to the manufacturers website and find a QR code to scan.

The things is that i'm doing my test on the latest Google Cardboard the viewer recognize it but it's still blur.. I don't know if it's something related to the image resolution or something like that ..

Can you send a link to the cardboard device you are using? We have tested with the various cardboard devices we have paired with iPhone 6s and are not seeing the issue on our end. Also, what is the resolution of the image you are displaying that appears blurry?


Feature update

added option to split measurements in segments.
This upgrade enables splitting signal into segments if data are saved with option One header only in LabView. This is usefull when multiple impact tests are stored into single lvm file with a single header.

Hi @itomac I have looked at the details. it is a lot of code for very little difference; I suggest not to do it. The package works "as expected": if one has only one header, then all data is put under one header; In the example (which I added to the data folder) there are two measurements, each long 8192. In the data field the length in 2x8192. To me this is ok and as expected. How does that sound to you?

Thank you Ivan for the effort


Incorrect arguments when using pandoc as External Helper

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.83.1+extended linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?
Yes
When using pandoc as an External Helper the --mathjax flag is passed in by default (stated in the documentation), but the -s or the --standalone flag need to be passed before passing the --mathjax flag, else the math/equations in the file are not rendered properly.
Ways to reproduce the issue
Create a post or .md file with markup as "pandoc" in Front Matter (or use your preferred way) and put some math statements like $a^2 + b^2 = c^2$

Currently we have
args := []string{"--mathjax"}

Can we have something like this ?
args := []string{"--standalone --mathjax"}


HPA metrics renaming on KSM 2.0.0

Is your feature request related to a problem? Please describe.
version v2.0.0 of KSM introduces a metric name renaming for HPA.
Feature Description
Add support for this new metrics names for the HPA Sample

This metrics are renamed since v2.0.0.

Given KSM 1.9.8 is pretty outdated according to the compatibility matrix  will KSM 2.x support be available anytime soon so HPA metric will work with newrelic-infra?

I guess due to renaming of hpa metrics from KSM v2.0.0, HPA metrics has  stopped reporting since we update to KSM v2.3.0 from v1.9.8. any leads on the solution?

Hi @maverickCoastCode the integration currently supports KSM 1.9.8 .
We plan to support more recent versions but there is not a date yet.

Howdy! It has been a while since this ticket was created. Any progress on 2.x support?

Closing this as support for KSM v2 was already released.


How to generate the thetas and betas parameter?

Hi, I have download the human3.6m dataset, however, i couldn't find a way to produce the thetas and betas parameter. The only clue we know comes from the SPIN issue, which use the sensors data and Mosh methods to generate theta and beta parameter, but the sensor data of human3.6m and code of Mosh is not public, we are very anxious to generate the pose parameter both in training and testing dataset, can you please answer it?

Hi, we provide the annotation files that contain the theta and beta parameters. These parameters are generated by Mosh. You can directly use our JSON files.

sure, I have see your json data, the theta and beta params are extracted every 5 frames in a video,  but in some cases, we need successive frames to do some expriments and recover some result in human3.6m, so would mind provide some details about the methods and the sensor data?  Is it possible to apply to the human3.6 official to get the sensor data?

Do you have the moshed data? I generate the JSON annotations from the moshed results.

what is the format of moshed data,  We get access to the human3.6 dataset，and the pose annotations is a obj file，is it the moshed data? Besides，how do you generate the annotations,  use the mosh methods with the sensor data, or use the SMPL models?

The moshed data is download from the open-source code of the previous method a long time ago. I upload the JSON files before downsampling on Baidu Drive. I hope it would help.

Could you please tell me the extract code in a private way that you are convenient?

Hi, the code is ey7w.

Hi，is it the total annotation data for human3.6m,  I have download the files, and load the json, however it is still discontinuous,  every 5 frames select 1.  Anyway, thank you for you coco-operation, it is indeed very difficult to find the total pose data for human3.6m.  Thank you!

Hi, I just check the moshed data and the code. I find that the moshed data provide continuous annotations. But the results (e.g. global orientation) maybe not aligned with the camera. I upload it on Baidu Drive (code k77z) with the code that used to downsample the results. I hope it can help you!

Thank you very much! It helps us a lot and we can continue our research due to this. You can contact me when you want to find a job or intership,  if you want to go to megvii, sensetime, bytedance, baidu and so on. My email is<EMAIL_ADDRESS>

Thanks for your sincerity!

Hi, I have downloaded the moshed data and the code, the raw_p['poses'] contains pose params in camera0,1,2,3, however I can't find  the order of camera 0,1,2,3 saved in raw_p['poses'], and how many images in each camera, can you please answer it? Thank you.

Hi @JinShiyin, actually I do not use the raw pkl file and only load the poses from the _aligned.pkl. It seems the poses in camx_aligned.pkl are downsampled by the rate of 5. If you only need the downsampled data, you can directly use the camx_aligned.pkl.

Hi @JinShiyin, actually I do not use the raw pkl file and only load the poses from the _aligned.pkl. It seems the poses in camx_aligned.pkl are downsampled by the rate of 5. If you only need the downsampled data, you can directly use the camx_aligned.pkl.

Hi~ I found the downsampling codes need
import metadata as md

But there is no this file.
Could you share the code here?
Thank you very much!

Hi @Jeff-sjtu , what is the different processing between *.pkl and the _cam_aligned.pkl, or could you tell me where I can find the process scripts?

Hi @JinShiyin, actually I do not use the raw pkl file and only load the poses from the _aligned.pkl. It seems the poses in camx_aligned.pkl are downsampled by the rate of 5. If you only need the downsampled data, you can directly use the camx_aligned.pkl.

Hi @Jeff-sjtu , what is the different processing between *.pkl and the *_camx_aligned.pkl, or could you tell me where I can find the process scripts? I want to get the continuous smpl mesh.

Hi @Jeff-sjtu.
Congratulations to the authors for this great research work!
I am trying to understand the generation process of 'thetas' and 'betas' parameters of Human3.6m.
I cannot download the Mosh code from Baidu drive. Is there any other way to see that?
And, does that Mosh method come from that paper?


fix(L2): several fixes

Motivation

The CLI was merged to main with some isses.
Description

Fixes several issues:

OperatorConfig. Rename struct fields to proper ones.
Ethereum Rust L2 CLI stack command. Add a force optional argument for start, purge, and restart command.
Ethereum Rust L2 CLI wallet command. Gas estimation is failing, so we hardcode the gas_limit to the double of the default transaction cost; fixed the transfer transaction hash display.

please provide a more descriptive description and title

Done!


Standardise errorhandler names to match other apps

There were a few errorhandler names in the admin app that were wrong, based on precedents set in the other frontend apps.
Now they're not.

Coverage decreased (-0.0%) to 89.828%

If you were feeling really conscientious you could add tests for the 400 and 500 error handlers (these are the ones missing tests).  But it's not like there's any logic in them, so :+1: as is if you have better things to do.

No logic in (doing) them right now, so I'm gonna merge it.
Still an improvement.


Add Astropy functions to tests

Tests which demonstrate relevant Astropy functions to replace irplank, ten and sixty.

This PR makes no changes to the code but simply demonstrates how to do the things with astropy functions.

I agree with Kelle here, these functions should be replace with the (very baseline) astropy functions


Amend contributing doc to include VCR example

VCR can be confusing, and without this work, there is not a clear
example on how to contribute tests whilst using VCR and protecting
credentials.  Here we write up an example and explain a test case to
demonstrate how VCR is intended to be used.  Also we include a note
about how to clean up credential to avoid leaking information.

I've made no code changes.  The build fails on Ruby 1.9.  Might we merge anyway?


Move meeting agendas to GitHub

Why
As we are moving project reports and other items from the Wiki, we should consider whether it makes sense to have all TOC operations in the same location. This will ensure that the meeting minutes are not lost if we migrate from Confluence in the future.
Proposed Process

Hyperledger TOC chair (or vice-chair) will create a pull request to https://github.com/hyperledger/toc to create a file with the meeting agenda in a meetings/YYYY folder. (NOTE: a template will be created to make this easier).
During the TOC meeting, the PR will be modified to include the attendees.
After the TOC meeting, the PR will be modified to add the recording.
The PR will then go through the process of getting two approvals and being merged.

The recordings will continue to live elsewhere, which we can discuss

Approved in Feb 2, 2023 meeting by roll call vote. Discussed in the meeting using archive.org as a location for recordings.


Add User Data Shell Script Is Encoded query #1413

User Data Shell Script must be encoded
Closes #1413

Scan submitted to Checkmarx

Checkmarx SAST - Scan Summary & Details
Cx-SAST Summary
Total of 4 vulnerabilities 0 High 3 Medium 1 Low 0 Info
Violation Summary
 3 Medium
View more details on Checkmarx UI
Cx-SAST Details

Lines
Severity
Category
File
Link

30
Medium
Path_Traversal
cmd/builder/main.go
Checkmarx

52
Medium
Denial_Of_Service_Resource_Exhaustion
pkg/kics/service.go
Checkmarx

83
Medium
Denial_Of_Service_Resource_Exhaustion
test/main_test.go
Checkmarx

The search key needs the resource name to distinguish different resources of the same type


Prabat graphragacceleratorfrontenddisablelocaladmin

GraphRAG Acclerator Frontend: Disable the local admin auth on the acclerator frontend

Will go ahead and close this as your changes were added into main in another PR. Github shows no file changes on this PR now. Thanks!


[Biometric] Demo Application Crash BiometricDemoD11

When you press the fingerprint scanner icon, the application crashes and gives the following error:
java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/biometric/R$string;
at androidx.biometric.BiometricFragment.authenticate(BiometricFragment.java:381)
at androidx.biometric.BiometricPrompt.authenticateInternal(BiometricPrompt.java:993)
at androidx.biometric.BiometricPrompt.authenticate(BiometricPrompt.java:972)
at com.delphiworlds.kastri.DWBiometricFragmentActivity.authenticate(DWBiometricFragmentActivity.java:91)
at com.delphiworlds.kastri.DWBiometricFragmentActivity.onResume(DWBiometricFragmentActivity.java:106)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1413)
at android.app.Activity.performResume(Activity.java:7400)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3850)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3890)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:150)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:73)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1858)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6820)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:922)
Caused by: java.lang.ClassNotFoundException: Didn't find class "androidx.biometric.R$string" on path: DexPathList[[zip file "/data/app/com.delphiworlds.BiometricDemoD11-alBMpzbi0kV5Eu8m3O07dg==/base.apk"],nativeLibraryDirectories=[/data/app/com.delphiworlds.BiometricDemoD11-alBMpzbi0kV5Eu8m3O07dg==/lib/arm, /data/app/com.delphiworlds.BiometricDemoD11-alBMpzbi0kV5Eu8m3O07dg==/base.apk!/lib/armeabi-v7a, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:171)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
... 19 more
Delphi Version: 11
Platform(s): Android 9 PPR1.160610.011
Device: Redmi 6, MIUI Global 11.0.5

I'm unable to reproduce this issue on my Pixel 6 Pro (Android 12) or Pixel 3a (Android 11). I don't have an Android 9 device with biometrics to check why it happens on yours

When you run this function, this problem occurs:
function TPlatformBiometric.ShowPrompt: Boolean;
begin
Result := False;
if GetBiometricCapability = TBiometricCapabilityResult.Available then
begin
TJDWBiometricFragmentActivity.JavaClass.start(TAndroidHelper.Context, GetPromptInfoIntent);
Result := True;
end;
end;
And to be even more precise:
TJDWBiometricFragmentActivity.JavaClass.start(TAndroidHelper.Context, GetPromptInfoIntent);
P.S. Sorry for my English.  It's not my native language...

I have updated the demo with a change that may fix it. You will need to update your Kastri library to obtain all the required changes

I will be waiting very much.  Thank you very much.

After the update, the error is still the same, only different:
java.lang.RuntimeException: Unable to resume activity {com.delphiworlds.BiometricDemoD11/com.delphiworlds.kastri.DWBiometricFragmentActivity}: android.content.res.Resources$NotFoundException: String resource ID #0x0
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3858)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3890)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:150)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:73)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1858)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6820)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:922)
Caused by: android.content.res.Resources$NotFoundException: String resource ID #0x0
at android.content.res.Resources.getText(Resources.java:360)
at android.content.res.MiuiResources.getText(MiuiResources.java:97)
at android.content.res.Resources.getString(Resources.java:453)
at androidx.fragment.app.Fragment.getString(Fragment.java:986)
at androidx.biometric.BiometricFragment.authenticate(BiometricFragment.java:382)
at androidx.biometric.BiometricPrompt.authenticateInternal(BiometricPrompt.java:993)
at androidx.biometric.BiometricPrompt.authenticate(BiometricPrompt.java:972)
at com.delphiworlds.kastri.DWBiometricFragmentActivity.authenticate(DWBiometricFragmentActivity.java:91)
at com.delphiworlds.kastri.DWBiometricFragmentActivity.onResume(DWBiometricFragmentActivity.java:106)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1413)
at android.app.Activity.performResume(Activity.java:7400)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3850)
... 11 more

Sorry.. I know where the problem is. I just need to work out how to fix it :-)

I've pushed an update to the biometric R jar (androidx-biometric-1.1.0.R.jar). Can you pull the change, do a Clean of your project and try again?

Unfortunately, I can't compile. Here's an error:
[PAClient Error] Error: E7432 Error in C:\Users\Public\Documents\Embarcadero_Comp\Kastri\ThirdParty\Android\androidx-biometric-1.1.0.R.jar:
[PAClient Error] Error: E7432 java.util.zip.ZipException: error in opening zip file

Not sure why it would not be compiling for you - compiles OK here

I have updated OpenJDK to version <IP_ADDRESS>2.7 but the error remains.
Maybe you updated some more files, but did not post them? :)

That's the only file that was changed

I don't know why, but I rebooted the computer and the project compiled. Now I'll try to run it on different devices. Thanks!

Опять ошибка:
java.lang.RuntimeException: Unable to resume activity {com.delphiworlds.BiometricDemoD11/com.delphiworlds.kastri.DWBiometricFragmentActivity}: android.content.res.Resources$NotFoundException: String resource ID #0x7f070000
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3858)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3890)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:150)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:73)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1858)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6820)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:922)
Caused by: android.content.res.Resources$NotFoundException: String resource ID #0x7f070000
at android.content.res.Resources.getText(Resources.java:360)
at android.content.res.MiuiResources.getText(MiuiResources.java:97)
at android.content.res.Resources.getString(Resources.java:453)
at androidx.fragment.app.Fragment.getString(Fragment.java:986)
at androidx.biometric.BiometricFragment.authenticate(BiometricFragment.java:382)
at androidx.biometric.BiometricPrompt.authenticateInternal(BiometricPrompt.java:993)
at androidx.biometric.BiometricPrompt.authenticate(BiometricPrompt.java:972)
at com.delphiworlds.kastri.DWBiometricFragmentActivity.authenticate(DWBiometricFragmentActivity.java:91)
at com.delphiworlds.kastri.DWBiometricFragmentActivity.onResume(DWBiometricFragmentActivity.java:106)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1413)
at android.app.Activity.performResume(Activity.java:7400)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3850)
... 11 more
On the Honor 9 phone, it also crashes (but I can’t see the error on it).

Can you attach the .APK file, please

BiometricDemoD11.zip

I may have missed a change to the project file. Please pull the latest changes, and rebuild your project

Absolutely the same error... :(

Can you post a screenshot of your Deployment window? i.e. in Delphi, use Project|Deployment. It should look like this:

Note all the files that have been added

Here is my APK so you can check if it works on your device
BiometricDemoD11.apk.zip
.

Your APK also causes the application to the same error... (

Without the same (or similar) device to test on, I do not think I can help at the moment

Is it possible to make it so that when an error occurs, the application does not crash?
Something like:
try
except

Unfortunately, no - the crash actually occurs in the Java code for biometrics.

What do we do? :)

BiometricDemoD11.apk.zip
Can you try the attached APK?

Good afternoon.
The error remains the same.
I tried to change the localization of the phone (I thought it might have something to do with it), but nothing has changed...

OK.. I may have a solution another way, hopefully

Fine! I will be very hopeful!

I have just pushed a change to androidx-biometric-1.1.0-R.jar. Can you pull the change, do a Clean on your project, rebuild and try it, please? This should at least have the demo working. I am looking into implementing a solution that can apply to any project

Everything is fine!
Thanks a lot!!!
P.S. And the localization of the word "Authenticate!" possible in a popup window?

Solved the issue with the title!
Thank you very much!

Hello!
There is a new problem:
On Honor X8 phone, with "Secure File Sharing" enabled, the app crashes when the fingerprint is read or canceled.
As soon as you disable "Secure File Sharing" everything works.

In future, please report new issues separately, however: can you check that your AndroidManifest.template.xml file has:
<%provider%>

in it?

Yes, of course, <%provider%> is contained in the AndroidManifest.template.xml file

Long time issue still unresolved - requires changes to the build process.

Hello,
I was previously using the KeyguardManager to authenticate the user. But as it's now deprecated, I have tried to use your BiometricDemoD11 App. I have the same issue than the one explained at the start of this discussion : When I press the fingerprint icon, the application crashes but the only error I get is "BiometricDemoD11 stopped working"... I don't know how to get more details...
When I try to execute in debug mode, the TPlatformBiometric.ShowPrompt seems to work Ok as well as the TJDWBiometricFragmentActivity.JavaClass.start(TAndroidHelper.Context, GetPromptInfoIntent) call but the process crashes after the return.
My target is Android 8.1.0 : I have read that AndroidX is supported by this platform.
Thank you for your help
Delphi Version: 11.1
Target = Android 8.1.0 - Nexus 6P

Thanks for the reminder.. I've set another reminder for myself for during this week

Thank you very much

Perhaps tomorrow, if not, the next day :-)

I would like to be able to provide a solution for this that is easy to incorporate, however it is very complicated. If the Delphi build system was more flexible, it would be easier.
The issue is this: As you have discovered, on some devices (I do not know why it is only some), the biometrics expects there to be certain values in the application resources, however in the case of Delphi, they are not compiled in with the application. This Quality Portal report has some background about that:
https://quality.embarcadero.com/browse/RSP-20000
In Delphi, currently the build steps for Android are (essentially) like this:
Compile/Build steps:

Compile/link application code
Merge "dex" files

Deploy steps:

Generate resource files
Deploy compiled files and resources
Package the app

In order for the biometrics resources to be included in the application, the steps would need to be like this:
Compile/Build steps:

Compile/link application code
Generate resource files
Merge resources from other Android libraries (such as biometrics) with those generated by Delphi
Compile "R" classes for the included libraries into a jar, and "dex" it
Merge "dex" files

Deploy steps:

Deploy compiled files and resources
Package the app

It is possible to achieve the same result, however it involves these steps:

Do a deployment once
Merge resources from other Android libraries (such as biometrics) with those generated by Delphi
Compile "R" classes for the included libraries into a jar, and "dex" it
Add the "dexed" file to the libraries for the project
In deployment manager, uncheck all the files that would normally be deployed to the "res" folder, and add the "merged" files generated in step 2. It is not an easy task to do this with Deployment Manager in its current state, however the DeployMan tool from Grijjy could help here.
Do a deployment again

Usually, these steps will need to be done only once, however if any changes are made to the project that result in different resource files, steps 1-3 will definitely need to be repeated, and some changes related to step 5 may also need to be considered.
I am working on tools that can automate steps 2-3, however I'd much prefer it if Embarcadero could resolve the Quality Portal issue mentioned above

@Mouscap (and anyone else following) - I have pushed a "beta" demo to the Playground repo, which you are welcome to try, and give feedback on. Please report any such feedback or issues to the Playground issues page.

@Mouscap (and anyone else following) - I have pushed a "beta" demo to the Playground repo, which you are welcome to try, and give feedback on. Please report any such feedback or issues to the Playground issues page.

These steps only work for 32-bit Android, how to do the same for 64-bit which is the version we posted on Google Play?


NorESM2-LM bug

Hey Guys,
When creating the catalog with the intake_esm_builder it seems that for one model only it interchanged source_id and experiment_id.
For this model source_id gives historical and experiment_id gives NorESM2-LM
/g/data/oi10/replicas/CMIP6/CMIP/NCC/NorESM2-LM/historical/r1i1p1f1/Amon/pr/gn/v20190815/pr_Amon_historical_NorESM2-LM_r1i1p1f1_gn_198001-198912.nc
For all models like the following it works perfectly fine.
/g/data/oi10/replicas/CMIP6/CMIP/IPSL/IPSL-CM6A-LR/historical/r1i1p1f1/Amon/pr/gr/v20180803/pr_Amon_IPSL-CM6A-LR_historical_r1i1p1f1_gr_185001-201412.nc
Have any of you encounter issues with cataloging the submissions of the Norwegian model NorESM2-LM. Is that because of the file name structure ?
Cheers,
Francois

@fanchic,
I encountered a similar error with the NASA's GISS-E2-1 model a while ago:
$ ls /glade/collections/cmip/CMIP6/CMIP/NASA-GISS/GISS-E2-1-G/historical/r10i1p1f1/Lmon/evspsblveg/gn/v20181015/evspsblveg

evspsblveg_Lmon_GISS-E2-1-G_historical_r10i1p1f1_gn_185001-190012.nc  evspsblveg_Lmon_historical_GISS-E2-1-G_r10i1p1f1_gn_185001-190012.nc
evspsblveg_Lmon_GISS-E2-1-G_historical_r10i1p1f1_gn_190101-195012.nc  evspsblveg_Lmon_historical_GISS-E2-1-G_r10i1p1f1_gn_190101-195012.nc
evspsblveg_Lmon_GISS-E2-1-G_historical_r10i1p1f1_gn_195101-200012.nc  evspsblveg_Lmon_historical_GISS-E2-1-G_r10i1p1f1_gn_195101-200012.nc
evspsblveg_Lmon_GISS-E2-1-G_historical_r10i1p1f1_gn_200101-201412.nc  evspsblveg_Lmon_historical_GISS-E2-1-G_r10i1p1f1_gn_200101-201412.nc

In our case, we removed all CMIP6 files that exhibit the "swapped" source_id and experiment in the filename.  Each of these non CMIP6 DRS conforming files had a related correct and duplicate file, which was kept.
If you are unable to remove those corrupted files, you can this line in your YAML file and build the catalog again:
exclude_dirs: ['*historical_NorESM2*']

For an example of what our yaml file, here's an example

This is an issue with the actual data. Closing this issue for the time being


[Bug]: Organization creator don't have permissions to manage IAM

What happened?
After I create a new organization, I don't have the permissions to manage its IAM.
To Reproduce

Create a new organization
Click IAM/Team menu
A warning message says that I don't have permissions to take this action

Code of Conduct

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

This is a bug caused by #175


How to set footerview

How can I set the footer view? I tried using the tableView.footerView property but this is not what I need.

EasyTableView was just recently updated. The interface has changed slightly so you may need to make changes to your code to support EasyTableView 2.0. Please update and let me know if the same behavior still exists. Thanks.

No follow-up response. If this is still an issue, please post a new comment.


Changing diagram pngs to svgs

This is part of the work related to finding out whether current diagrams are accessible #1397

:heavy_check_mark: You can preview this change here:
:hammer: Explore the source changes: ca6d5308ac797c0c3f1d0653d8f24683f5f262ea
:mag: Inspect the deploy logs: https://app.netlify.com/sites/govuk-design-system-preview/deploys/5ff352b361a4c70007b5f648
:sunglasses: Browse the preview: https://deploy-preview-1440--govuk-design-system-preview.netlify.app

:heavy_check_mark: You can preview this change here:
:hammer: Explore the source changes: ca6d5308ac797c0c3f1d0653d8f24683f5f262ea
:mag: Inspect the deploy logs: https://app.netlify.com/sites/govuk-design-system-preview/deploys/5ff352b361a4c70007b5f648
:sunglasses: Browse the preview: https://deploy-preview-1440--govuk-design-system-preview.netlify.app


Extract default @Option name from setter or getter name

If you annotate a getter with @Option, you always have to explicitly specify an option name.
It would be nice if it would have a default value there too.
For example if you annotate the method getFxVersion() with @Option, the option name should be fxVersion (or fx-version if #7400 gets done).
So you can e. g. do
    @get:Input
    @get:Option(description = "The JavaFX version to prepare")
    abstract val fxVersion: Property<String>

instead of
    @get:Input
    @get:Option(
            option = "fxVersion",
            description = "The JavaFX version to prepare"
    )
    abstract val fxVersion: Property<String>

Still not possible in 6.7.1, would still be nice to have and of course also from setter name if the setter is annotated.


feat: guess image type

Previously lutgen-rs choked on files without an extension (or those that had a non-matching extension); I switched load_image's image::open to image::io::Reader's  with_guessed_format, which tries to automatically guess the file type via magic bytes.

Thanks!


bfxPublic.ticker Error 429

I keep receiving this warning, I have read that Poloniex API only allows 8 instructions per second, I have switched it to 7 but I keep receiving this message every second
Is that normal on this version?
Thanks!

No operations so far.. 6 hrs running

2 days running, same story, no operation and the message keeps popping

@djcrawleravp for the time being this project will not be maintained and server has been taken offline.
I will consider bringing it back when I find time and resource.
Thank you


Current domain does not stay selected

changed rostopic rapid_pbd/pddl_domain to publishing only current domain_id rather than entire domain
moved domain selection to home page, for Action and Problem display domain name read from rostopic /rapid_pbd/pddl_domain
latest working commit: f9cdb221fa0491b2705f56d22c90df821713d22a


Latest Chrome on Mac doesn't allow forcing through self signed certificate

Latest chrome on Mac, just no option to continue

Some research suggests there may be something wrong about our self signed certificate. Something to do with subjectAltName not being set?

Works in Safari btw, I can force through.

I was running into this a few months ago when running on a CentOS 7 server and trying to connect from Catalina. You need a new enough version of OpenSSL (I used 1.1.1). The following will generate a cert that meets the requirements in case this is useful for anyone else:
/usr/local/ssl/bin/openssl req -newkey rsa:2048 -nodes \
  -x509 -days 365 \
  -out cert.pem \
  -keyout key.pem \
  -config /etc/pki/tls/openssl.cnf \
  -subj "/C=US/ST=Ohio/L=Columbus/O=Business./CN=Server" \
  -addext extendedKeyUsage=serverAuth \
  -addext subjectAltName=DNS:localhost

Awesome!
Let's add this to the FAQ or make code-server automatically generate it correctly.

Related to https://7402.org/blog/2019/new-self-signed-ssl-cert-ios-13.html

I ended up fixing this in #2255


[GUI]positioning is incorrect and Ctrl + left mouse button cannot enter the corresponding method

jadx version：latest unstable build（v1.1.0-b1243-e444ecb2）
apk link：https://drive.google.com/open?id=1VEF1jTDYip5SSjLELFbFX6b7N5bk2pdx
Problem 1: jadx positioning is incorrect
After decompiling the apk, search for settings_purchaseInTrialDesc_singular, double-click the first result with the left mouse button, and jadx is not positioned to the correct position. I need to continue searching in this class to find the correct location.
Problem 2: Ctrl + left mouse button cannot enter the corresponding method
ninja.sesame.app.edge.iab.d.b()

Regarding the wrong positions: It seems like the line index is misplaced because of the multi-line /* JADX DEBUG: sections added in this class. Internally Jadx seems to count only one line for each of these sections instead of the real line count.

My mouse pointer stays on the method without any slight offset.
I often encounter this problem using jadx. With the same apk, some methods cannot be clicked into, other methods can be clicked into.
My computer resolution is 1920 * 1080, windows10

Sorry my fault. By disabling the debug comment Failed to find minimal casts for resolve the index was corrected and the method got clickable. Therefore both problems have the same source: the line misplacement.

@xmhwws I made a fix. Please check latest unstable build.
The issue was in the incorrect use of OS-specific chars as new lines \n here and next counting OS independent NL here. As result it was working good on my machine (Linux) but incorrect on Windows.

thanks


yarn dlx jsr add does not work when following Yarn&jsr basic setup docs

I created an empty project with Yarn, following Yarn's docs in an empty folder:
corepack enable
yarn init -2

Then, I run yarn dlx jsr add @nic-test/test-log (copy-pasted from the Yarn tab at https://jsr.io/@nic-test/test-log@0.1.0), and I get this output:
➜ yarn dlx jsr add @nic-test/test-log
➤ YN0000: · Yarn 4.1.0
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + jsr@npm:0.9.0, kolorist@npm:1.8.0, node-stream-zip@npm:1.15.0
➤ YN0000: └ Completed in 0s 567ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 3 packages were added to the project (+ 167.89 KiB).
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed
➤ YN0000: · Done in 0s 628ms

Setting up .npmrc...ok
Installing @nic-test/test-log...
$ yarn add @nic-test/test-log@npm:@jsr/nic-test__test-log
➤ YN0000: · Yarn 4.1.0
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: @nic-test/test-log@npm:@jsr/nic-test__test-log isn't supported by any available resolver
    at Dd.getResolverByDescriptor (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:141:1698)
    at Dd.bindDescriptor (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:141:1083)
    at Pt.preparePackage (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:210:6173)
    at async ne (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:210:7583)
    at async Promise.allSettled (index 0)
    at async Uc (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:140:53244)
    at async /Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:210:9140
    at async Nt.startProgressPromise (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:140:137284)
    at async Pt.resolveEverything (/Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:210:7138)
    at async /Users/nic/.cache/node/corepack/yarn/4.1.0/yarn.js:213:2648
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 0s 13ms

Additional context: this only applies when using >= Yarn 2 (berry), not when using Yarn 1 (classic). Yarn 2 does not read from .npmrc.
@marvinhagemeister Probably we should detect the Yarn version that is in use for a given project, and if it's not Yarn 1, we create the .yarnrc.yml.
Docs: https://yarnpkg.com/migration/guide
Also WHY YARN WHY? :(


fix: add option to run ExecCopyFromHost container with host ns

Diagnostics script requires running with host networking, pid and IPC namespaces to correctly collect data from some tools like iptables or systemctl.
JIRA: https://jira.d2iq.com/browse/D2IQ-85636

:tada: Thank you!


eas build: Build request failed - CombinedError: [GraphQL] Entity not authorized: AccountEntity

Build/Submit details page URL
No response
Summary
✔ Uploaded to EAS 8s
Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
    CombinedError: [GraphQL] Entity not authorized: AccountEntity[****] (viewer = UserViewerContext[****], action = READ,
    ruleIndex = -1)

There are some recent comments encountering the same problem in issue https://github.com/expo/eas-cli/issues/694
Managed or bare?
Managed
Environment
  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 12.4
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
      npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
    IDEs:
      Xcode: /undefined - /usr/bin/xcodebuild
    npmPackages:
      @expo/webpack-config: ^0.16.2 => 0.16.12
      babel-preset-expo: 8.5.1 => 8.5.1
      expo: ^43.0.0 => 43.0.4
      react: 17.0.1 => 17.0.1
      react-dom: 17.0.1 => 17.0.1
      react-native: 0.64.3 => 0.64.3
      react-native-web: 0.17.1 => 0.17.1
    npmGlobalPackages:
      eas-cli: 1.2.0
      expo-cli: 6.0.5
    Expo Workflow: managed

🎉 Didn't find any issues with the project!

Error output
eas build --platform=ios
An Expo user account is required to proceed.

Log in to EAS
✔ Email or username … ****
✔ Password … *********
» android: androidStatusBar.backgroundColor: Color conflicts with the splash.backgroundColor
» ios: expo-document-picker: Cannot configure iOS entitlements because neither the appleTeamId property, nor the environment variable EXPO_APPLE_TEAM_ID were defined.
✔ Using remote iOS credentials (Expo server)

If you provide your Apple account credentials we will be able to generate all necessary build credentials and fully validate them.
This is optional, but without Apple account access you will need to provide all the missing values manually and we can only run minimal validation on them.
✔ Do you want to log in to your Apple account? … yes

› Log in to your Apple Developer account to continue
✔ Apple ID: …  Learn more: https://expo.fyi/eas-build-archive
✔ Uploaded to EAS 8s
Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
    CombinedError: [GraphQL] Entity not authorized: AccountEntity[****] (viewer = UserViewerContext[****], action = READ,
    ruleIndex = -1)

Reproducible demo or steps to reproduce from a blank project
eas build

Hi,
Thanks for reporting. Could you please share some details?

Do you have owner set in app.json?
Are you using a team / organization that has a different name than the username you're using with EAS CLI? You can check the username with eas whoami.

I missed an important piece - I could successfully and reliably build the project with eas build many times before. And seemingly nothing has changed since the last try.

Do you have owner set in app.json?

No, never had.

Are you using a team / organization that has a different name than the username you're using with EAS CLI? You can check the username with eas whoami.

expo and eas have the same user.

Can you share more details? What's your username? I can't help you without it.

matesmajda

Do you have projectId in app.json? Sth like in the screenshot:

Can you please install<EMAIL_ADDRESS>and let me know if it works for you on that version?
If 2. doesn't work, stay on 0.60.0 but this time remove extra.eas.projectId from app.json.

Yes I have projectId
2. seems to work:
✔ Uploaded to EAS 8s
⠸ Build in progress...

OK can confirm 0.60.0 works.
I tried downgrading to 1.1.1 earlier today but the issue was present there as well.

Hi @Cafe137, I'm having trouble reproducing the issue on my end. To expedite my debugging, would you be able to clarify the following: It works on 0.60.0 and your app.json contains extra.eas.projectId?

Hello @wschurman,
Yes it does work on 0.60.0.
And I do have app.json > expo > extra > eas > projectId.
Let me know if you want me to try a few more things to help debug this.

I had the exact same issue, the problem was the extra.eas.projectId in app.json file. I had projectId from another expo.dev account and the current logged in user was from my second account. Changing extra.eas.projectId to the projectId from my second account fixed the issue. So, always check if you have extra.eas.projectId from the same expo.dev account that you are logged in to through expo login or eas login.

I have this issue on 2.1.0 and didn't have this issue on 0.60.0.
The owner of the projectId is an organization I am part of.
EAS build works fine, however I encounter this error running the project on the dev-client so my current workaround is to exclude the projectId when doing so.

I also confirm that I was able to make it work with<EMAIL_ADDRESS>without projectId in app.json (app.config.ts in my case)

I had the exact same issue, the problem was the extra.eas.projectId in app.json file. I had projectId from another expo.dev account and the current logged in user was from my second account. Changing extra.eas.projectId to the projectId from my second account fixed the issue. So, always check if you have extra.eas.projectId from the same expo.dev account that you are logged in to through expo login or eas login.

You are LOVE <3

For me this issue resolved when I switched to the account with which I had my keystore generated

I solved this issue by removing eas: projectId from app.json:
"extra": {
  "eas": {
    "projectId": "a1b2c3d4-e5f6-g7h8i9-j1k2-l3m4n5o6p7"
  }
}

I need a build for development, the company's Expo project ID is different than my account's project ID, thus the problem...

I have this issue on 2.1.0 and didn't have this issue on 0.60.0. The owner of the projectId is an organization I am part of. EAS build works fine (android & ios), however I encounter this error running the project on the dev-client so my current workaround is to exclude the projectId when doing so.

I can confirm this works for anyone that wants to run  the project on expo-dev-client. Removing the extra.eas.projectId from app.json simply allows eas to create the project on your own Expo Profile.
It will also return the projectId key once created, so nothing lost, I guess...

I solved this issue by removing eas: projectId from app.json:
"extra": {
  "eas": {
    "projectId": "a1b2c3d4-e5f6-g7h8i9-j1k2-l3m4n5o6p7"
  }
}

I need a build for development, the company's Expo project ID is different than my account's project ID, thus the problem...

This works for me, thanks man!

I was running a build using another expo login details and a project id has been generated before, i removed the project in my app.json and ran the command again and it worked perfectly

Removing it and let eas build generate it works for me too. but the error message is very weird.
Invalid app ID
Graphql request failed

I'm also having this problem. For me, my account is a member of a legacy team account for one client, and an organization for another. No matter what I do, eas whoami shows the team account, which I think is the cause of my issues but I don't know how to resolve that.

@diemer - eas whoami shows the user you are logged in as. Your user is then a member of accounts. In your case, it is a member of your personal account (the account with the same name as your user) and an organization account of a different name. If your user is a member of both, it should have access to both. I don't know the exact error you are seeing but you can view your permissions on each of the accounts by navigating to the respective account's members settings page on the Expo website.

Going to close this out as it is working as expected. The solution is to ensure that the extra.eas.projectId in the app config is the expected project you are building. If this needs to dynamically change (for example, if one wants to build for separate projects) then using a dynamic config (app.config.js) is required: https://docs.expo.dev/workflow/configuration/.

I Have also this issue:

with eas-cli/4.1.1 linux-x64 node-v20.5.0

My solution was a little different.
I was receiving this error on<EMAIL_ADDRESS>We've encountered a transient error. Try again shortly.
Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
And then when I upgraded to<EMAIL_ADDRESS>I received this error:
This account has used its iOS builds from the Free plan this month, which will reset in 9 days (on Fri Sep 01 2023). Upgrade your plan for more builds with shorter wait times and longer timeouts, and to run more builds concurrently with a subscription plan.
So, my assumption is that the old version didn't have this error written in... super exciting.

I was just logged in to another expo account by mistake 👍

What worked for me was removing a commented line from my app.json file.

I solved this issue by removing eas: projectId from app.json:
"extra": {
  "eas": {
    "projectId": "a1b2c3d4-e5f6-g7h8i9-j1k2-l3m4n5o6p7"
  }
}

I need a build for development, the company's Expo project ID is different than my account's project ID, thus the problem...

Thanks brother , it works finlly

this error means that you are logged as owner. remove this in app.json :
   "extra": {
      "eas": {
        "projectId": "Your project id"
      }
    }


Fix external subpass dependencies

I found a few issues with the synchronization validation from the latest SDK.
external -> 0:

src stage doesn't need bottom of pipe, COLOR_ATTACHMENT_OUTPUT and LATE_FRAGMENT_TESTS is all we need to wait for attachment writes
dst stage needs to include EARLY_FRAGMENT_TESTS since that's where depth/stencil load ops happen (in this case: clear)
dst access mask also needs to consider depth/stencil writes

0 -> external:

src stage needs LATE_FRAGMENT_TESTS to wait for depth attachment writes
src access mask also needs to consider depth/stencil writes
dst access mask includes memory writes to prevent write-after-write (although you could possibly argue that writing to an attachment would require a layout transition, at which point the user might as well do explicit synchronization)

🚀 New Synchronization Validation looks very promising. Vulkan Configurator also helps a lot.
Thank you fixing the issues. I agree with you, explicit synchronization should be preferred. 👍


react-flow@next updateTransform issue

In react-flow v8, setInitTransform action has been removed and it seems the implementation of updateTransform is different or has bugs. Here is the bug I'm experiencing:
After updating pane position using useStoreActions(actions => actions.updateTransform), when I get onMoveEnd event, the event transform parameters has the previous position of pane before setting the position using updateTransfrom.
Can you confirm the issue? I didn't have the issue with v7 setInitTransform.
Thanks!

I can confirm I get the exact same bug if I use updateTransform instead of setInitTransform. Can you clarify what are the differences between these two functions? if they are different, can we have setInitTransform in v8?

I find the solution mentioned here https://github.com/wbkd/react-flow/issues/678#issuecomment-725299327
It seems setInitTransform is now replaced with a separate hook const { transform: updateTransform } = useZoomPanHelper();, after using the new hook, it works fine. I think this is breaking change, worth mentioning in the release notes ;-)

hi @code-guru, we are still working on the docs and release notes, should be mentioned in some minutes ;)


Listening ONCE to an event

Is there something like a once method like the one implemented by the node.js EventEmitter class?
bot.once("text", (msg) => {
  ...
});

You can try that, by implemeting that in your code. Just use the example you send and see if the bot reacts to a second message


Some "Transfer" transactions don't transfer anything so are they really Transfer Transactions?

For example. This transaction http://explorer.symboldev.network/transaction/5445FE00F77AF111D187E7BFE0BD5AECB6FE9EFDF84C08427A1254C9344E4D2F from looking at the block explorer it is called a "transfer" transaction but I can't seem to see any mosaic being transferred, but instead, only a message was sent.
So I'm wondering if we shouldn't call it "Message transaction". I know on the backend that is not the developer speak but from the end-user perspective calling a message transaction a transfer transaction is a bit misleading.
There is another case to where an empty transaction is sent and there is no message and no mosaics being sent. In that case, I think it might be nice to be labeled "empty transaction" so people don't get confused.

The "transfer" transaction is follow the network transaction type.
Our document show message under transfer transaction.
https://nemtech.github.io/concepts/transfer-transaction.html#message
In my opinion, should follow with documentation.

I agree with Anthony that it can be better to follow the docs. So there will not be misunderstanding that user announced Transfer transaction but in the explorer it is shown as a MessageTransaction. I think it may have more sense to show some user-friendly transaction types in the wallet rather in the explorer which i think more developer oriented and in this perspective the data is shown here should be accurate.
We can simply add note field to the Transaction Info table which can provide a clarification comment.
What do you think?
@jabo38 @AnthonyLaw  @evias

There is no perfect solution because we have a transaction type called “transfer transaction” in which there is no transfer. But it’s still and “transfer transaction” technically so I get why we want to look at it and call it that. At the same time, I personally think we should be building tools for users so it’s something to think about.
Take for instance this Tx, there is no transfer and no message. That had to be totally confusing to a regular user browsing the explorer.
http://explorer.symboldev.network/transaction/9D6731381F17CB7D27C6760FBE2F38927F8B228EA86A17CB2F67C2455D1ACCEA
This could at least in part be mitigated by being more clear and spelling it out with fields “message: no message” and “mosaic transfer: no mosaic transferred”. Or something along those lines. By doing this newbies won’t be confused.

how about this?
@jabo38 @OlegMakarenko @evias
If the Tx is only Message
it will show like the photo above.
else remain the the same.

@jabo38 @AnthonyLaw I think Remark field from Anthony and Transaction Graphic solved this issue. Can we close it, or any other ideas?

yeah, i think we can close this.


mode: sql fails

mode: sql fails, no highlighting
all other modes works fine.
codeMirrorOptions = {     mode: 'sql',     lineNumbers: true,     theme: 'material'   };

@marijnh I want to set the syntax highlighting of pyhton3, just write it as text/x-python?


Add changefeed metrics labels option & usage

Fixes DOC-2130
Added a reference and usage section to the Monitor and Debug Changefeeds page on changefeed metrics labels.

Included warning on experimental feature
Usage considerations, availability, etc.
Option to the CREATE CHANGEFEED option table.

@taroface On this one:

Per the style guide and consistency with Monitor a changefeed, should this be "Use changefeed metrics labels"?

The reason I went for the gerund, is that I followed the construction of the other H3 headings on this page. But, let me know if you think this is weird and I'll update those too/links.

@taroface On this one:

Per the style guide and consistency with Monitor a changefeed, should this be "Use changefeed metrics labels"?

The reason I went for the gerund, is that I followed the construction of the other H3 headings on this page. But, let me know if you think this is weird and I'll update those too/links.

Oh, okay. In that case, this seems fine to me!

LGTM!

TFTR!


Proposed API: colorProvider

A color provider returns all ranges and color values in a given document. It is similar to a document symbols provider, but for color references.
The result can be used by editors to render color boxes and to show color pickers.
export namespace DocumentColorRequest {
	export const type = new RequestType<DocumentColorParams, ColorInformation[], void, TextDocumentRegistrationOptions>('textDocument/documentColor');
}

export interface DocumentColorParams {
    /**
     * The text document.
     */
	textDocument: TextDocumentIdentifier;
}

export interface ColorInformation {
	range: Range;
	color: Color;
}

/**
 * Represents a color in RGBA space.
 */
export class Color {

	/**
	 * The red component of this color in the range [0-1].
	 */
	readonly red: number;

	/**
	 * The green component of this color in the range [0-1].
	 */
	readonly green: number;

	/**
	 * The blue component of this color in the range [0-1].
	 */
	readonly blue: number;

	/**
	 * The alpha component of this color in the range [0-1].
	 */
	readonly alpha: number;
}

How does the editor communicate to the language server to change the color if a picker is used?  Seems like another request would be needed for that since Color gives no information about the text format of the color in the document.

Currently, the color picker needs to have the knowledge about which color formats are valid in the given file format.
An idea would be to add a 'getColorPresentations(color, range)' client to server request.
Given a color, the server would return a set of possible presentations (#FF0000, rgb(255, 0, 0), hsl(0, 100%, 50%)). I added the range here as well, in case the file contains embedded languages.
Modifications should still happen on the client side.
@rebornix @joaomoreno Thoughts?

It makes perfect sense to have range in the color presentation API. Jo recommended that the color reprentation can return TextEdits, to make that happen, the extension should know both the new color info and the range.
For short, both getDocumentColorRanges and resolveDocumentColor can use { IColor, Range } as parameters and it makes the API consistent and comparable with your use case.

I created https://github.com/Microsoft/vscode/issues/34366 as proposal for the API

@aeschli OK to close?

Thanks for reminding!


TSK-4306

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


APPS-1127 Update config endpoints

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

Comparison is base (cd8ff60) 26.90% compared to head (e112544) 26.90%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #132   +/-   ##
=======================================
  Coverage   26.90%   26.90%
=======================================
  Files          35       35
  Lines        1613     1613
=======================================
  Hits          434      434
  Misses       1121     1121
  Partials       58       58

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


Add Agola CI/CD project

Agola is an Open Source Cloud Native CI/CD platform with advanced features and
architecture (scalable and high available by design).
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
Page: landscape, section CI & Pipeline Orchestration is out of bound

Looks like the build failed since adding a new entry to CI & Pipeline Orchestration / Pipeline Orchestration pushed the last entry outside the container and made it not visible.
Probably the container size/rows should be increases in settings.yml. I made different tries: adding a row made it look quite bad, while increasing the container size made it a bit better but with two entries on the first row at the right of the graduated entries. Not sure which is the guideline on this and if I should open a new PR or make the change in this one.

Please make a change in this one.
Dan Kohn<EMAIL_ADDRESS>+1-415-233-1000
Executive Director, Cloud Native Computing Foundation cncf.io
https://www.cncf.io/
dankohn.com https://www.dankohn.com/ or book on my calendar: dankohn.com/c
https://www.dankohn.com/c
On Wed, Jan 8, 2020 at 7:03 AM Simone Gotti<EMAIL_ADDRESS>wrote:

Looks like the build failed since adding a new entry to CI & Pipeline
Orchestration / Pipeline Orchestration pushed the last entry outside the
container and made it not visible.
Probably the container size/rows should be increases in settings.yml. I
made different tries: adding a row made it look quite bad, while increasing
the container size made it a bit better but with two entries on the first
row at the right of the graduated entries. Not sure which is the guideline
on this and if I should open a new PR or make the change in this one.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cdfoundation/cdf-landscape/pull/55?email_source=notifications&email_token=AAXQYBV42ADSE475W5PYZA3Q4W6JPA5CNFSM4KD527I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIMFEDQ#issuecomment-572019214,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXQYBRUHUZMP7IPOGQOBT3Q4W6JPANCNFSM4KD527IQ
.

@dankohn Thanks. After various tries I think (IMHO) that, with the current entries, the best solution is to remove fit_width: true (also all categories in current cncf landscape doesn't have it since they have many entries).
Other tries where done increasing the number of rows or the container width but the result wasn't pretty good.
Current:

New:


Feature - select stroke width

I've got a drawing app where the user can select color, alpha and stroke width.  It would be useful to have this library also allow the user to select stroke width (and maybe show a dot next to the selection to show how big the stroke would be).  This should be a feature, like alpha, that can be turned on or off.

While that would be a nice feature, I think it is beyond the scope of the project. If you send a PR I might accept it. Thanks.


ERROR: No matching distribution found for torch==2.0.1a0

Hello, I am getting following error while trying to build the docker container:
------
 > [15/21] RUN python -m pip install torch==2.0.1a0 -f https://developer.intel.com/ipex-whl-stable-xpu &&     python -m pip install intel_extension_for_pytorch==2.0.110+xpu -f https://developer.intel.com/ipex-whl-stable-xpu &&     python -m pip install torchvision==0.15.2a0 -f https://developer.intel.com/ipex-whl-stable-xpu:
0.563 Looking in links: https://developer.intel.com/ipex-whl-stable-xpu
1.627 ERROR: Could not find a version that satisfies the requirement torch==2.0.1a0 (from versions: 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1, 2.1.0, 2.1.1)
1.627 ERROR: No matching distribution found for torch==2.0.1a0
------
WARNING: buildx: failed to read current commit information with git rev-parse --is-inside-work-tree
Dockerfile.arc-xpu:106
--------------------
 105 |
 106 | >>> RUN python -m pip install torch==${TORCH_VERSION} -f ${TORCH_WHL_URL} && \
 107 | >>>     python -m pip install intel_extension_for_pytorch==${IPEX_VERSION} -f ${IPEX_WHL_URL} && \
 108 | >>>     python -m pip install torchvision==${TORCHVISION_VERSION} -f ${TORCHVISION_WHL_URL}
 109 |
--------------------
ERROR: failed to solve: process "/bin/sh -c python -m pip install torch==${TORCH_VERSION} -f ${TORCH_WHL_URL} &&     python -m pip install intel_extension_for_pytorch==${IPEX_VERSION} -f ${IPEX_WHL_URL} &&     python -m pip install torchvision==${TORCHVISION_VERSION} -f ${TORCHVISION_WHL_URL}" did not complete successfully: exit code: 1

I cloned the repo and currently my head points to commit f16f0f3102a85b050fad1cbf95a41484fc09f54b
Any advice would be very much welcome! Thanks!

I think you meant to post this here: https://github.com/Sikerdebaard/whisper-asr-webservice-xpu

Oh, sorry, you are absolutely right. Thank you!