Switch to Go 1.7 and 1.8

We are only supporting the two latest major Go releases.

Coverage remained the same at 66.971% when pulling 0f2644e198a27205603dce804725cc607ffe81be on support-1.7-and-1.8 into 4c5263df41da2398966f8da9b446bee674700594 on master.


" and   "  sentence, parse misses the  and

I've tried various ingredient sentences and see consistent performance, so bringing this up to see if it's something that could be improved.
example 1 result:
{
"amount": [
{
"quantity": "1",
"unit": "",
"confidence": 0.980939
}
],
"name": "and 0.5 tsp fine grain sea salt",
"comment": null,
"other": null,
"sentence": "1 and 1/2 tsp fine grain sea salt"
}
example 2 result:
{
"amount": [
{
"quantity": "1",
"unit": "",
"confidence": 0.971023
}
],
"name": "Cassava Flour",
"comment": "and 0.5 cups",
"other": null,
"sentence": "1 and 1/2 cups Cassava Flour"
}
example 3 result:
{
"amount": [
{
"quantity": "1",
"unit": "",
"confidence": 0.973108
}
],
"name": "coconut",
"comment": "and 0.333 cups unsweetened finely shredded",
"other": null,
"sentence": "1 and 1/3 cups unsweetened finely shredded coconut"
}
example 4 result:
{
"amount": [
{
"quantity": "1",
"unit": "",
"confidence": 0.968139
}
],
"name": "dark chocolate morsels",
"comment": "and 0.5 cups",
"other": null,
"sentence": "1 and 1/2 cups dark chocolate morsels"
}

Thanks for the report, good catch. I don't think this will be too difficult to fix, I'll take a look in the next few days.

Sounds good, thanks for taking a look!

There's a fix for this in the prep_labels branch (7759ba2e56f05393b4b0300c3799b889cc90fff8), so it will be in the next release.
As an example, the sentence 1 and 1/2 cups Cassava Flour, will give a result that looks like:
{
  'name': 'Cassava Flour',
   'amount': [
    {
      'quantity'='1.5',
      'unit'='cups',
    }
   ],
   'preparation': None,
   'comment': None,
   'other': None,
   'sentence': '1 and 1/2 cups Cassava Flour'
}

Excellent, thank you!


Kotlin M13 support.

I've converted the project to Kotlin M13. (fixes #19 )
In some places it uses lazy(LazyThreadSafetyMode.NONE) instead of just lazy. That is because the automatic fix on all the project. I think it works the same as lazy, so you can replace it later.
Also, in order to remove a warning, I've added Method.PATCH to the when expression. However, Method.PATCH is inaccessible as a method, so it doesn't actually change something.
private fun setDoOutput(connection: HttpURLConnection, method: Method) {
         when (method) {
            Method.GET, Method.DELETE -> connection.doOutput = false
            Method.POST, Method.PUT, Method.PATCH -> connection.doOutput = true
         }
     }

Also I've run the tests, all pass. So it looks like no functionality were changed.

@yoav. That's awesome!!! I was skimming through changes and everything is good! :+1. Let me build on my machine once again and I ll merge this in asap.
—
Sent from Mailbox
On Sat, Sep 19, 2015 at 3:56 PM, Yoav Sternberg<EMAIL_ADDRESS>wrote:

I've converted the project to Kotlin M13.
In some places it uses lazy(LazyThreadSafetyMode.NONE) instead of just lazy. That is because the automatic fix on all the project (I've done it after some modifying). I think it works the dame as lazy, so you can replace it later.
Also, in order to remove a warning, I've added Method.PATCH to the when expression. However, Method.PATCH is inaccessible as a method, so it doesn't actually change something.
private fun setDoOutput(connection: HttpURLConnection, method: Method) {
         when (method) {
            Method.GET, Method.DELETE -> connection.doOutput = false
            Method.POST, Method.PUT, Method.PATCH -> connection.doOutput = true
         }
     }

You can view, comment on, or merge this pull request online at:
https://github.com/kittinunf/Fuel/pull/20
-- Commit Summary --

Kotlin M13 support. Passes tests.
-- File Changes --
M README.md (2)
M fuel/build.gradle (4)
M fuel/src/main/kotlin/fuel/Fuel.kt (51)
M fuel/src/main/kotlin/fuel/core/Deserializable.kt (10)
M fuel/src/main/kotlin/fuel/core/Either.kt (4)
M fuel/src/main/kotlin/fuel/core/Encoding.kt (4)
M fuel/src/main/kotlin/fuel/core/Manager.kt (2)
M fuel/src/main/kotlin/fuel/core/Request.kt (12)
M fuel/src/main/kotlin/fuel/toolbox/HttpClient.kt (39)
M fuel/src/main/kotlin/fuel/util/Delegates.kt (10)
M fuel/src/test/kotlin/fuel/BaseTestCase.kt (6)
M fuel/src/test/kotlin/fuel/CustomRobolectricGradleTestRunner.kt (8)
M fuel/src/test/kotlin/fuel/RequestAuthenticationTest.kt (8)
M fuel/src/test/kotlin/fuel/RequestDownloadTest.kt (19)
M fuel/src/test/kotlin/fuel/RequestHandlerTest.kt (17)
M fuel/src/test/kotlin/fuel/RequestHeaderTest.kt (6)
M fuel/src/test/kotlin/fuel/RequestObjectTest.kt (6)
M fuel/src/test/kotlin/fuel/RequestPathStringConvertibleExtensionTest.kt (10)
M fuel/src/test/kotlin/fuel/RequestSharedInstanceTest.kt (32)
M fuel/src/test/kotlin/fuel/RequestStringExtensionTest.kt (10)
M fuel/src/test/kotlin/fuel/RequestTest.kt (27)
M fuel/src/test/kotlin/fuel/RequestUploadTest.kt (14)
M fuel/src/test/kotlin/fuel/RequestValidationTest.kt (10)
-- Patch Links --
https://github.com/kittinunf/Fuel/pull/20.patch
https://github.com/kittinunf/Fuel/pull/20.diff

Reply to this email directly or view it on GitHub:
https://github.com/kittinunf/Fuel/pull/20

Document for lazy says
/**
 * Creates a new instance of the [Lazy] that uses the specified initialization function [initializer]
 * and the default thread-safety mode [LazyThreadSafetyMode.SYNCHRONIZED].
**/

So it seems like plain lazy would automatically be synchronized. Meanwhile, the lazy(LazyThreadSafetyMode.NONE) wouldn't.
Perhaps, just to be safe, I guess we should stick with the non-synchronized version as I don't think it is needed.

I didn't know about the lazy.
About generics.
Maybe @mplatvoet would be able to explain it better since he is the developer of Kovenant.
IDEA's Kotlin M13 plugin shows a warning if T doesn't extend any when you use T?.
If the methods I changed can return T?, then you better keep it T : Any but change the return type to T?

OK. I think you are right.
BTW, I think I will create a proper branch for this because I would like to fix #21 created by him. Would you mind create another PR against my 0.53 branch? Then I would fix #21 together with it.

I'm not a git pro, so I'll have to reapply all the changes. I can do another commit with the sealed change, lazy fix, and nullability fix for deserializer if needed.

I created this for you to merge your M13 fix in. #22

C'mon .. I would love to not let you do this alone. Lemme help :) I will fix other small things as well.

I think the lazy instance should be thread safe in most cases here. Same goes for readWriteLazy which is used for instance in headers. The resulting Request instance can be shared amongst threads and I think people will. Only if you can guarantee that a lazy can only be initialised and read by one thread you should use the unsynced variant.

Also, what about nullability in generics for Deserializable?
Should it be able to return null?


Draft room player list formatting

The playerlist seems to be missing a column heading for rank and sorting doesn't work correct.

Added this but sorting still seems off.
$headers['Rank'] = array('by' => 'rank_order', 'order' => 'asc');

this was a missed update non issue.


[integrations] Tekton Dashboard

Tracking issue for integrating with the Tekton Dashboard.
We'd like to surface Results/Records in the Tekton UI so that users can visualize the logic groupings / extra data Results can store. A really rough version of this can be found here: https://github.com/tektoncd/results/tree/main/tools/simpleui
I am not sure how we can do this in a minimally invasive way. Open to ideas!

Unfortunately not an idea of how to go forward but want to say that this is really exciting. Due to relying on the Kubernetes APIs the dashboard really struggles when there are lots of resources. Implementing proper pagination is difficult and also filtering possibilities are limited. As a workaround, we try to keep the number of resources low (e.g. using https://github.com/tektoncd/experimental/tree/master/pipeline/cleanup#cleanup-old-taskruns-and-pipelineruns) but ideally we should be able to keep as much history for e.g. all executions of a pipeline as we want and not as technically limited ;)
Would be awesome if results is the solution!

@Fabian-K Sorry I missed this! But yes, that's the goal for this project. :)
This issue is scoped purely for integrating with the Tekton Dashboard, but you'll probably find https://github.com/tektoncd/results/issues/59 useful to your use case!

https://github.com/tektoncd/dashboard/blob/master/docs/extensions.md looks like a promising way to hook into the Dashboard.

@wlynch I'd love to talk more about the desired user experience for viewing / interacting with the Results data. There are plenty of options to explore depending on the desired outcome.
At a high level I see 2 main options for the user:

add new pages to the Dashboard to surface data from the Results API using the existing extensions mechanism

Note: Dashboard extensions were originally intended to allow for both adding new pages and customisation of existing pages. Unfortunately this plan was never fully realised and extensions have remained pretty basic, only supporting the addition of new pages to the app (either simple auto-generated pages for Kubernetes resources, or custom UI similar to the deprecated webhooks-extension).

alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster

There are some planned changes to the Dashboard's API / data layer that may make integration / customisation easier in future, and some other challenges such as auth that we'll need to address too.

alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster

This seems like the ideal route to me.  Results providing the historical record / source of truth for anything that's reached a Completed ( / deleted) state.
@wlynch do you think that's fair assessment?
Are the dashboard's data layer plans related to the redux removal issue or documented elsewhere?

Are the dashboard's data layer plans related to the redux removal issue or documented elsewhere?

Yes that's the first part of it, a major simplification of the data layer (and corresponding reduction in boilerplate) so we can more easily plugin additional / alternative sources while solving some of the performance and caching issues we have today. I need to flesh out the plan a bit more and document it so we can start to make progress. I have my hands full for the next 1 - 2 weeks but will try to get something on paper asap for others to review.

alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster

This seems like the ideal route to me. Results providing the historical record / source of truth for anything that's reached a Completed ( / deleted) state.
@wlynch do you think that's fair assessment?

Yup! The Result API also captures data for unique instances of Runs with the same name (e.g. if you create->delete->create) which would probably also be useful for the dashboard.
Modeling the dashboard on the Result API would also let us display related data (e.g. PipelineRun + TaskRuns) in groups.
@AlanGreene I added a discussion item for the March 8th Dashboard WG so we can talk about questions/ideas!

@AlanGreene it's been awhile since we've touched base on this. Any updates on the dashboard side for how to get started experimenting?

Can we re-open this issue? We're running Tekton on a larger scale (2k+ pipelineruns, 20k+ taskruns active in the cluster) so we'd be very interested in having the ability to not rely on the Kubernetes API for looking into results of a pipeline. Currently we need to very aggressively clean the runs in order for the dashboard to stay performant.

Hi, guys, any progress on the integration?
Currently it's not possible to view the build status of a project via dashboard like jenkins, and it's also not directly supported through the pipeline metrics(use grafana + prometheus). So I'm wondering if this could be achived by tekton results?

/area roadmap

/assign

I created a basic dashboard based on results using Flutter.
https://github.com/khrm/bowspirit  Lot of things still need to be done on it. Atm, it has a list for Pipelinerun, also view Pipelinerun's Yaml and Log

Any progress on enabling the dashboard to fallback to Results API database?
@xinnjie did you end up implementing that TEP you were referring to? Thank you! 🙇

@xinnjie Is this something you're still planning to work on or do you have some progress update you can share? If you're not planning to work on it that's fine, please unassign yourself so someone else can pick it up. Thanks.

It seems Xinnjie is not active on GitHub since October. it should be okay to unassign this issue.

This is really a missing feature in the complete Tekton ecosystem. Would easy up resources on the cluster as well.

Sorry guys, I'm not available for now.

Any updates on that?
It would be really helpful to save logs of PipelineRuns in a Tekton Dashboard

@Stringls Can you elaborate on what you're looking to do? If it's just persisting logs and loading those in the Dashboard see https://github.com/tektoncd/dashboard/blob/main/docs/walkthrough/walkthrough-logs.md. It describes a way to achieve this today, using minio for storage as an example, but can be achieved using any storage provider you wish as long as you can provide the required API for the Dashboard to consume.
If you're looking to persist the Tekton resources too, and load both those and the logs in the Dashboard from Tekton Results, that is not yet supported. There are a number of blockers on the Results side that need to resolved first before the Dashboard could add this support, including https://github.com/tektoncd/results/issues/535

@AlanGreene Sure.
So as a user of Tekton I expect to:

Run Tasks/Pipelines
UI (Tekton Dashboard)
Logs of the executed Tasks/Pipelines

As we know, we lose logs when pods of the TaskRun/PipelineRun are deleted, but I would like them to be persistent and not be deleted as Logs is a crucial part of any CI.
Setting up minio as a storage of the logs sounds useful, but not ideal. IMHO there should be a native solution in Tekton Results without any further configuration of other tools (e.g. minio). For example, if a user wants to have a local storage, Tekton Results monitors every TaskRun/PipelineRun and saves logs (stdout, stderr) in PVC/s and once Tekton Pruner deletes TaskRuns/PipelineRun Tekton Results deleted the logs associated with that Tekton resources in its storage.
We don't really look to persist the Tekton resources, currently.


Use released instead of dist folder

Could you use the GH releases instead of the dist folder? it pollutes the repository history…

Closing for obsolescence


Add easy switching between aligned and not aligned TreeMesh1DUniform states

Only in a case of actually aligned tree.

done.


map lazy load info window won't work

The demo - https://ngmap.github.io/#/!map-lazy-load-params.html
info-window won't work. click on the pushpin, throw error -
Uncaught TypeError: Cannot read property 'showInfoWindow' of undefined
    at index (https://rawgit.com/allenhwkim/angularjs-google-maps/master/services/attr2-map-options.js:286:44)
    at Array.reduce (native)
    at _.ye.<anonymous> (https://rawgit.com/allenhwkim/angularjs-google-maps/master/services/attr2-map-options.js:287:39)
    at Object._.z.trigger (https://maps.google.com/maps/api/js?libraries=placeses,visualization,drawing,geometry,places:95:121)
    at VT.handleEvent (https://maps.google.com/maps-api-v3/api/js/27/5/marker.js:49:458)
    at _.tf.Jd (https://maps.google.com/maps-api-v3/api/js/27/5/common.js:189:417)
    at _.Nv._.k.re (https://maps.google.com/maps-api-v3/api/js/27/5/common.js:239:205)
    at _.Nv._.k.Xi (https://maps.google.com/maps-api-v3/api/js/27/5/common.js:238:246)
    at Object._.z.trigger (https://maps.google.com/maps/api/js?libraries=placeses,visualization,drawing,geometry,places:95:121)
    at Pt.<anonymous> (https://maps.google.com/maps-api-v3/api/js/27/5/common.js:138:342)

@allenhwkim would you mind to share your feedback?

The example has a bug in it. Please use this.
http://plnkr.co/edit/nBO6txbEVeDt4AhWfHZ8?p=preview

It works. thank you..


[WIP] [Angular-NgRx-SCSS] Adjustments to get deployed site working

Trying to fix Amplify deployed site
A few small style and data fixes to adjust what already exists in the app

Testing another potential fix for the Amplify PR reviews, will open in a new PR. :)


Config validation for rfxtrx sensor

Description:
Configuration validation of the rfxtrx sensor
Checklist:
If code communicates with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Looks good! :dolphin:


Define Goal Categories

discussed simplifying the categories.  Keeping it vague and simple with the option to add a custom category specific to a user.  we will need to decide how this will be designed / stored in the data base.

discussed sub categories (as an optional field).  To give users a more clear category to group by.  Again keeping it simple, these are to act as prompts to a user, with the ability for a user to select a customer sub category if required.
sub categories are associated with a category.  only related sub categories will be highlighted to a user (including their own custom sub category related to the category selected).


Adding functionality to obtain distances/cosmological parameters

The current functionality of SNCosmo allows the user to obtain SALT2 light model from the light curve data using the ansatz that the distance modulus $\mu = m_B + \alpha x_1 - \beta c + M$ where $M$ is an unknown constant. The main issues to keep in mind is that this requires a regression with errors on all the parameters. There are at least two main methods to do this: one is inferencing the cosmological parameters along with $\alpha$ and $\beta$ simultaneously, and the other is by obtaining distance modulus from these. I will later add references of papers where these methods have been demonstrated.

FYI: I'm starting to doubt whether this sort of thing should actually go in sncosmo. The problem is that real state-of-the-art models involve a lot of subtle choices about parameterization. See, e.g., arxiv.org/abs/1507.01602. Such subtle choices don't belong in a general-use package like this, and I'm not yet sure what common functionality there is between different models.
I think the way forward here is to see actual code implementing one or more models (in a separate repo or package) and then see if there are any common features we can abstract into sncosmo. I plan to spend some time working on this myself soon, and that's what I'm going to do.
cc @sdhawan21

There are two things about this:

There should be a definition of the scope of SNCosmo. This could include calculation of cosmological quantities, or it could be punted to different software. In particular, if the current scope defined in the landing page is considered: "SNCosmo is a Python library for simulating, fitting and typing supernova light curves, built on NumPy, SciPy and AstroPy.", this choice fulfills the goals set forth.
On the other hand, I think of SNCosmo  as a tool which provides the user with functionality that they should use to get results from existing stuff. Hence, there are functions to read in data files, or simulations that are not produced by SNCosmo. It must be pointed out that leaving it at this stage, without pointing to a package that can use the SNCosmo light curve fit results and obtain distances/cosmological parameters, as would be the case if the user chose to use other packages is not very desirable. So, I think it would be important to provide a method to output SNCosmo  results in a way that can be readily used by existing packages, or point to a new package that does this.


ValidationSummary does not list model errors with empty error message

Discussion https://github.com/aspnet/Mvc/pull/3214#discussion_r40511642.
Currently ValidationMessage shows a generic The value 'blah' is invalid message for these exceptions. But ValidationSummary silently ignores it.
Need to investigate and make a decision of what to show/ignore in ValidationSummary.
Related issue - https://github.com/aspnet/Mvc/issues/3043
cc' @dougbu @NTaylorMullen @Eilon

I think we should investigate if we can reduce the number of cases where there is no error message as much as possible.

@ajaybhargavb What was the MVC 5 behavior?

MVC 5 behaves the same way as MVC 6. It hides the error messages in validation summary. Spoke to @dougbu about this. We have three options,

Leave it as it is (keep hiding these messages in validation summary)
Add a single generic error message in validation summary. (something like One or more fields have invalid values)
Show all the error messages in validation summary.
One problem with the third approach is if we have multiple errors for empty values we will have multiple The value '' is invalid messages in validation summary which will be confusing as to which field it refers to.
We need to decide which approach to take.
@danroth27 @Eilon

Spoke to @Eilon and @dougbu. We decided to keep this consistent with the MVC 5 behavior.


allows externally defined default-cert

@krancour @emilevauge @dtomcej @ldez
What this PR does / why we need it:
Adds the ability to use an external cert, manged outside of helm. This is useful for folks adopting weaveworks/flux, or sealed secrets and allows one to keep sensitive data out of a git repository
Special notes for your reviewer:
This PR only adds the ability to manage secrets externally.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ x] DCO signed
[ x] Chart Version bumped
[ x] Variables are documented in the README.md

sorry, I messed up the first commit, and i just keep making it worse. closing.


Behaviour of Unicode to Plain Text Latex Commands Suddenly Changed

Debug log ID
EUCKUCRJ-refs-apse/6.7.162-6 , 3N376R9P-refs-apse/6.7.162-6
What happened?
Behaviour of unicode to latex commands suddenly changed - was previously working consistently. Some entries now convert circumflex i to ^{\i}, instead of ^{i} which causes an error. In addition, previously endashes were converted to {\textendash}  which displayed correctly, but now as converted to -- which does not.

Hi, do you have an MWE where \^{\i} causes an error? And how does -- render differently than \textendash? I thought these two were equivalent?

Hi here's the MWE reproducing the circumflex error. I will double check the endash behaviour, I may have been too hasty (but it may have occurred in mathmode or something like that)
MSW Circumflex Error.zip

For future reference -- you can make single-file MWEs using filecontents, but this compiles without error for me (although I see now LaTeX is smart enough to make \^i and \^\i the same these days):
\documentclass{article}

\usepackage[backend=biber, style=alphabetic]{biblatex}

\begin{filecontents}{\jobname.bib}
@inproceedings{Cervantes-cota,
  title = {Cosmology today---{{A}} brief review},
  author = {{Cervantes-Cota}, Jorge L. and Smoot, George},
  year = {2011},
  eprint = {1107.1789v2},
  pages = {28--52},
  doi = {10.1063/1.3647524},
  archiveprefix = {arxiv},
  keywords = {review}
}

@article{Lemaitre1931,
  title = {A {{Homogeneous Universe}} of {{Constant Mass}} and {{Increasing Radius}} accounting for the {{Radial Velocity}} of {{Extra-galactic Nebulae}}},
  author = {Lema\^{\i}tre, A. G.},
  year = {1931},
  month = mar,
  journal = {Monthly Notices of the Royal Astronomical Society},
  volume = {91},
  number = {5},
  pages = {483--490},
  doi = {10.1093/mnras/91.5.483}
}
\end{filecontents}
\addbibresource{\jobname.bib}

\begin{document}

\section{MSW Circumflex Error}
Here is a citation \cite{Lemaitre1931} which causes an error.
\printbibliography[heading=bibintoc]
\end{document}

the en-dash should not be showing up in math mode, but it doesn't for me.

I'll change the i-circumflex back to what it was; it seems latex already makes the i dotless these days for these cases.

I've changed \^\i back, but I can't replicate compilation errors with --.

For future reference -- you can make single-file MWEs using filecontents, but this compiles without error for me (although I see now LaTeX is smart enough to make \^i and \^\i the same these days):
\documentclass{article}

\usepackage[backend=biber, style=alphabetic]{biblatex}

\begin{filecontents}{\jobname.bib}
@inproceedings{Cervantes-cota,
  title = {Cosmology today---{{A}} brief review},
  author = {{Cervantes-Cota}, Jorge L. and Smoot, George},
  year = {2011},
  eprint = {1107.1789v2},
  pages = {28--52},
  doi = {10.1063/1.3647524},
  archiveprefix = {arxiv},
  keywords = {review}
}

@article{Lemaitre1931,
  title = {A {{Homogeneous Universe}} of {{Constant Mass}} and {{Increasing Radius}} accounting for the {{Radial Velocity}} of {{Extra-galactic Nebulae}}},
  author = {Lema\^{\i}tre, A. G.},
  year = {1931},
  month = mar,
  journal = {Monthly Notices of the Royal Astronomical Society},
  volume = {91},
  number = {5},
  pages = {483--490},
  doi = {10.1093/mnras/91.5.483}
}
\end{filecontents}
\addbibresource{\jobname.bib}

\begin{document}

\section{MSW Circumflex Error}
Here is a citation \cite{Lemaitre1931} which causes an error.
\printbibliography[heading=bibintoc]
\end{document}

MWE:
$ cat test2.tex
\documentclass{article}

\usepackage[backend=biber, style=alphabetic]{biblatex}

\begin{filecontents}{\jobname.bib}
@inproceedings{Cervantes-cota,
  title = {Cosmology today---{{A}} brief review},
  author = {{Cervantes-Cota}, Jorge L. and Smoot, George},
  year = {2011},
  eprint = {1107.1789v2},
  pages = {28--52},
  doi = {10.1063/1.3647524},
  archiveprefix = {arxiv},
  keywords = {review}
}

@article{Lemaitre1931,
  title = {A {{Homogeneous Universe}} of {{Constant Mass}} and {{Increasing Radius}} accounting for the {{Radial Velocity}} of {{Extra-galactic Nebulae}}},
  author = {Lema\^{\i}tre, A. G.},
  year = {1931},
  month = mar,
  journal = {Monthly Notices of the Royal Astronomical Society},
  volume = {91},
  number = {5},
  pages = {483--490},
  doi = {10.1093/mnras/91.5.483}
}
\end{filecontents}
\addbibresource{\jobname.bib}

\begin{document}

\section{MSW Circumflex Error}
Here is a citation \cite{Lemaitre1931} which causes an error.
\printbibliography[heading=bibintoc]
\end{document}

build log:
$ rm test2.bib
$ latexmk -pdf -bibtex test2 -c
Rc files read:
  /etc/LatexMk
Latexmk: This is Latexmk, John Collins, 7 Jan. 2023. Version 4.79.
Latexmk: Doing main (small) clean up for 'test2.tex'

$ latexmk -pdf -bibtex test2
Rc files read:
  /etc/LatexMk
Latexmk: This is Latexmk, John Collins, 7 Jan. 2023. Version 4.79.
No existing .aux file, so I'll make a simple one, and require run of *latex.
Latexmk: applying rule 'pdflatex'...
Rule 'pdflatex':  Reasons for rerun
Category 'other':
  Rerun of 'pdflatex' forced or previously required

------------
Run number 1 of rule 'pdflatex'
------------
------------
Running 'pdflatex  -recorder  "test2.tex"'
------------
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./test2.tex
LaTeX2e <2022-11-01> patch level 1
L3 programming layer <2023-01-16>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2022/07/02 v1.4n Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.sty
(/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty))
(/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/latex/kvsetkeys/kvsetkeys.sty))
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.sty
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-dm.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-compat.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/alphabetic.bbx
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/standard.bbx))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/cbx/alphabetic.cbx)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-case-expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)))

LaTeX Info: Writing file `./test2.bib'.

(./test2.aux) (/usr/share/texlive/texmf-dist/tex/latex/biblatex/lbx/english.lbx
)
No file test2.bbl.

LaTeX Warning: Citation 'Lemaitre1931' on page 1 undefined on input line 35.

LaTeX Warning: Empty bibliography on input line 36.

[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./test2.aux)

LaTeX Warning: There were undefined references.

Package biblatex Warning: Please (re)run Biber on the file:
(biblatex)                test2
(biblatex)                and rerun LaTeX afterwards.

 )</usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx10.pfb></us
r/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb></usr/shar
e/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on test2.pdf (1 page, 36751 bytes).
Transcript written on test2.log.
Latexmk: Getting log file 'test2.log'
Latexmk: Examining 'test2.fls'
Latexmk: Examining 'test2.log'
Latexmk: Missing bbl file 'test2.bbl' in following:
 No file test2.bbl.
Latexmk: Log file says output to 'test2.pdf'
Latexmk: Bibliography file(s) form .bcf file:
  ./test2.bib
Latexmk: applying rule 'biber test2'...
Rule 'biber test2':  Reasons for rerun
Category 'other':
  Rerun of 'biber test2' forced or previously required

------------
Run number 1 of rule 'biber test2'
------------
------------
Running 'biber  "test2.bcf"'
------------
INFO - This is Biber 2.18
INFO - Logfile is 'test2.blg'
INFO - Reading 'test2.bcf'
INFO - Found 1 citekeys in bib section 0
INFO - Processing section 0
INFO - Looking for bibtex file 'test2.bib' for section 0
INFO - LaTeX decoding ...
INFO - Found BibTeX data source 'test2.bib'
INFO - Overriding locale 'en-US' defaults 'variable = shifted' with 'variable = non-ignorable'
INFO - Overriding locale 'en-US' defaults 'normalization = NFD' with 'normalization = prenormalized'
INFO - Sorting list 'anyt/global//global/global' of type 'entry' with template 'anyt' and locale 'en-US'
INFO - No sort tailoring available for locale 'en-US'
INFO - Writing 'test2.bbl' with encoding 'UTF-8'
INFO - Output to test2.bbl
Latexmk: Found biber source file(s) [test2.bcf test2.bib]
Latexmk: applying rule 'pdflatex'...
Rule 'pdflatex':  Reasons for rerun
Changed files or newly in use/created:
  test2.aux
  test2.bbl
  test2.run.xml

------------
Run number 2 of rule 'pdflatex'
------------
------------
Running 'pdflatex  -recorder  "test2.tex"'
------------
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./test2.tex
LaTeX2e <2022-11-01> patch level 1
L3 programming layer <2023-01-16>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2022/07/02 v1.4n Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.sty
(/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty))
(/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/latex/kvsetkeys/kvsetkeys.sty))
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.sty
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-dm.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-compat.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/alphabetic.bbx
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/standard.bbx))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/cbx/alphabetic.cbx)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-case-expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)))

LaTeX Info: File `test2.bib' already exists on the system.
            Not generating it from this source.

(./test2.aux) (/usr/share/texlive/texmf-dist/tex/latex/biblatex/lbx/english.lbx
) (./test2.bbl)

! LaTeX Error: Unicode character ̂ (U+0302)
               not set up for use with LaTeX.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...

l.36 \printbibliography[heading=bibintoc]

? x
No pages of output.
Transcript written on test2.log.
Latexmk: Getting log file 'test2.log'
Latexmk: Examining 'test2.fls'
Latexmk: Examining 'test2.log'
Latexmk: Found input bbl file 'test2.bbl'
Latexmk: Log file says no output from latex
Latexmk: For rule 'pdflatex', no output was made
Latexmk: Bibliography file(s) form .bcf file:
  ./test2.bib
Latexmk: Summary of warnings from last run of *latex:
  =====Latex reported missing or unavailable character(s).
=====See log file for details.
Latexmk: ====List of undefined refs and citations:
  ! LaTeX Error: Unicode character ̂ (U+0302)
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 1
      Refer to 'test2.log' and/or above output for details

Latexmk: If appropriate, the -f option can be used to get latexmk
  to try to force complete processing.

author = {Lema^{\i}tre, A. G.},

That doesn't look like output from 5882 or 5861 though. Can you try again with 5883?

I'm waiting on this issue to put out a new release.

@a-lhn if you're not going to respond I'm going to assume your issue is resolved and close when @damiencourousse confirms.

Sorry, I'm in the middle of editing an important document and I don't want to mess with installing the test build immediately. If you would like me to test it could it please wait until next week?

From the issue template:

Please be available in the days following your report for follow-up questions and testing.

I know people have stuff to get done, which is why I generally try to get a fix out within a day. I clear important stuff of my own out of the way to make this happen, and my time is relatively scarce. And other people might be hit with the bug (like @damiencourousse), and I do not want to have them wait.
If @damiencourousse confirms I'm going to release the fix. If it turns out that it does not resolve the error, please open a new issue.

I'm going to consider this fixed


Swahili stopwords are missing

When I try to access the swahili stopwords using the below feature, I'm getting a traceback that the swahili stopwords are missing in the documentation, I'm currently working on building a swahili language model with data gathered from Wikipedia swahili articles and popular swahili blogs,  I was thinking of contributing the stopwords to the library to allow others users to easily load them.
Best regards
Kalebu

I believe you're proposing to add swahili stopwords such that
import nltk
stopwords = nltk.corpus.stopwords.words('swahili')

works correctly.
In order to do this, the stopwords.zip file over at nltk_data must be modified to include a file called swahili, which contains a new stopword on every line. You can find this zip file here: https://github.com/nltk/nltk_data/blob/gh-pages/packages/corpora/stopwords.zip
This nltk_data is then downloaded whenever a user performs nltk.download('stopwords'). I believe that once that is done, people should be able to use your stopwords.
However, I must warn you that pull requests for stopwords from nltk_data don't frequently get accepted, as we ourselves often do not know the language. We would rely on some verification, perhaps through other native speakers or because the list is from a peer-reviewed paper that we can verify.

Hello @tomaarsen , That's correct
That's exactly what  I was proposing  to do   , Thanks for an in depth  clarification  on how to do that.
I will  link to the source code + dataset I use to generate them and other related  references.
Best regards

Sounds good! Best of luck to you.

@tomaarsen and @Kalebu, planning on working on the issue above, should it be closed, so I can create a new one..?

This change ensures that torch>=2.0 is specified in requirements.txt, resolving conflicts with torchdata which requires torch>=2.0. This update prevents torch from being downgraded to 1.13.1 during dependency resolution.


fix(core): Use productName for FileDescription

fixes #10968
fixes #10890
There's also a VersionInfo FileDescription in the nsis installer template but i didn't see this being applied/used anywhere so i didn't touch it yet. Maybe windows 7 shows it still? From what i saw on StackOverflow, VersionInfo isn't really used since Vista but idk.

Lets change the NSIS as well, for consistency

It is not really used in anything, it can only be visible in the Details tab when checking the properties of the installer executable. I am fine with removing as well, but I think we should just update it to use productName

ffs, i didn't use the damn local cli/bundler when testing this, holy shit.

Thank you for the fix!


Cartfile versioning?

Shouldn't the cartfile have a version number added to it?
So instead of this:
github "pusher/push-notifications-swift"

It would have something like this:
github "pusher/push-notifications-swift" ~> 1.0

By not specifying the version number it means that it will use the latest version available.
You can also specify a specific version if you would like to. You can read more about the use cases here.


not working properly

Issue Type: Bug
editor most of the time not savig file automatically.
editor didn't  redirect(jump) to function.
editor most of the time not working in collapse and expand.
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:32:10.090Z)
OS version: Linux x64 5.4.0-64-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz (4 x 3297)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
19.44GB (9.74GB free)

Process Argv
--no-sandbox --unity-launch --crash-reporter-id b9d4618b-de96-4f8a-9f07-2eeb4e3e6996

Screen Reader
no

VM
0%

DESKTOP_SESSION
Lubuntu

XDG_CURRENT_DESKTOP
LXQt

XDG_SESSION_DESKTOP
Lubuntu

XDG_SESSION_TYPE
x11

Extensions (12)

Extension
Author (truncated)
Version

vscode-markdownlint
Dav
0.38.0

javascript-ejs-support
Dig
1.3.1

githistory
don
0.6.14

gitlens
eam
11.1.3

prettier-vscode
esb
5.8.0

shell-format
fox
7.0.1

dotenv
mik
1.0.1

mssql
ms-
1.10.1

sqltools
mtx
0.23.0

sqltools-driver-pg
mtx
0.2.0

gitblame
wad
6.0.2

vscode-import-cost
wix
2.13.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
openlogontheside:30221877
python383cf:30185419
pythonvspyt617:30244266
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30211401
wsl2promptcf:30224613
pythonvsdeb440:30248342
unusedprompt:30224610
folderexplorer:30224614
openfilemenucf:30224648
pythonvsded773:30248341
pythonvspyt875:30247033

Maybe use the Bisect command to investigate whether one of your extensions is causing the problems.

Maybe use the Bisect command to investigate whether one of your extensions is causing the problems.

Maybe use the Bisect command to investigate whether one of your extensions is causing the problems.

thanks It helps

Maybe use the Bisect command to investigate whether one of your extensions is causing the problems.

thanks It helps


chore(deps): update angular-eslint monorepo to v16 (major)

This PR contains the following updates:

Package
Type
Update
Change

@angular-eslint/builder
devDependencies
major
^15.2.1 -> ^16.0.0

@angular-eslint/eslint-plugin
devDependencies
major
^15.2.1 -> ^16.0.0

@angular-eslint/eslint-plugin-template
devDependencies
major
^15.2.1 -> ^16.0.0

@angular-eslint/schematics
devDependencies
major
^15.2.1 -> ^16.0.0

@angular-eslint/template-parser
devDependencies
major
^15.2.1 -> ^16.0.0

Release Notes

angular-eslint/angular-eslint (@angular-eslint/builder)
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/builder
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/builder
15.2.1 (2023-02-10)
Note: Version bump only for package @angular-eslint/builder

angular-eslint/angular-eslint (@angular-eslint/eslint-plugin)
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin
15.2.1 (2023-02-10)
Bug Fixes

update typescript-eslint packages to v5.48.2 (#1278) (69d56a7)

angular-eslint/angular-eslint (@angular-eslint/eslint-plugin-template)
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin-template
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/eslint-plugin-template
15.2.1 (2023-02-10)
Bug Fixes

eslint-plugin-template: [i18n] handle ng-template properly (#1257) (7b0877d)
update typescript-eslint packages to v5.48.2 (#1278) (69d56a7)

angular-eslint/angular-eslint (@angular-eslint/schematics)
v16.0.1
Compare Source
Bug Fixes

schematics: ensure placeholder schema for convert-tslint-to-eslint is copied to dist (3c6f377)

v16.0.0
Compare Source
Features

update to Angular 16 stable (9b0138d)

15.2.1 (2023-02-10)
Bug Fixes

update dependency eslint to v8.32.0 (#1276) (15d2e23)
update dependency eslint to v8.33.0 (#1292) (bd82b42)
update typescript-eslint packages to v5.48.2 (#1278) (69d56a7)

angular-eslint/angular-eslint (@angular-eslint/template-parser)
v16.0.1
Compare Source
Note: Version bump only for package @angular-eslint/template-parser
v16.0.0
Compare Source
Note: Version bump only for package @angular-eslint/template-parser
15.2.1 (2023-02-10)
Note: Version bump only for package @angular-eslint/template-parser

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/cli
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/cli@">= 16.0.0 < 17.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@angular-eslint/schematics
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-05-04T21_13_45_996Z-eresolve-report.txt

npm ERR!


Patch baseline

Hi @awserik,
Note: this should be under "discussion," but i dont see the tab here...
Following your blog post, i have a few questions as to how patch baseline works in a multi account setting...

When automation issues a "scan" to the child accounts, is the child account referring to the patch baselines that are under its own account? or is it referring to the patch baselines that are under the root account?
Depending on the answer to #1, how would it work if i want to wire up custom baselines to the mix? Do i have to set up identical custom baselines under each account, or just under the root account is sufficient?
Again, depending on the answer to #2, after reviewing the patch status from athena (stolen another idea), do i have to issue the approval/rejection to the custom baseline under each account, or just at the root account level?
3.5. After #3, i suppose that i will need to fire another "install" to actually install from the patch baselines as reviewed from #3. I guess this wraps up a "cycle" and rinse and repeat?

Hey @MrAtheist , Patch Baselines are an account/Regional resource so if you would like to use custom patch baselines across accounts/Regions, you will need to create them in each account/Region. You can stand these up by using CloudFormation StackSets to deploy across the organization.
Regarding approval, after you issue a patch scan, you can then query Athena to return a list of updates that are marked as missing based on the approval rules in the corresponding baseline. Following a patch scan, you can then issue a patch install to have the updates marked as missing installed on the target nodes. There is no specific approval that you need to perform as far as marking updates to be installed (the approval is inherit in defining the patch baseline approval rules).
Hope this helps!


drivers: i2c: i2c_max32: Add DMA support

Add DMA support to controller mode transfers in MAX32 I2C driver. Enable i2c_target_api single role tests for MAX32xxx boards.

Looks good, could it be extended for the part number that recently merged too?
MAX32666
MAX32675
MAX32662


Test Travis against OpenMPI

Now, I don't think that Travis actually does any MPI tests, but once you get that going, it should probably be done against more than one implementation.

Cool. Thanks.
Yea this should definitely be done. I thought about how to do automatic tests with MPI and write some MPI extension for pytest but that seemed like a lot of work.
The current plan is to just have some bash scripts execute after the normal tests and have a small manual testing framework. Python 3 and MPI for example does not work right now (due to some issues with h5py internal memory management I think...).
Two more things we should do before we merge this:

Have a third option with no MPI and no mpi4py. The code (except the MPI part) should still work fine.
If tested with MPI we have to install hdf5 with parallel I/O and also h5py. http://docs.h5py.org/en/latest/mpi.html

It doesn't look like conda has a parallel build, so are thinking of building here or putting something on binstar?

Hmm. So far I only thought about building on Travis but that does take quite a while. Binstar packages might be a nice solution.
I'll be done with my travels for a while at the end of this week so I should be able to finally finish this whole thing fairly soon (I hope).


Make User registraion public/private

A setting (like the emailconfirmation one) shoul indicate whether or not the public can register themselves. If so the users/register route needs to be protected, if not it can be public.

Issue #9 required that registration as an admin-only route. Wouldn't that make this issue obsolete?

We need it to be optional because in some cases the user is supposed to sign up himself/herself.
The admin needs to be able to do that no matter what, but the in some cases users can sign up.


Upgrade to elasticsearch 7

We need to also support elasticsearch 7

First issue:
Get aliases is no longer working
$client->indices()->getAliases();

Php elasticsearch library
/**
     * Alias function to getAlias()
     *
     * @deprecated added to prevent BC break introduced in 7.2.0
     * @see https://github.com/elastic/elasticsearch-php/issues/940
     */
    public function getAliases(array $params = [])

https://github.com/elastic/elasticsearch-php/issues/940


update invalid URL of openby.design

Change URL of open by design

Cool update.
I hope @bradtraversy is still watching this great repository and approving pull requests :-).


Converting the file format and checking the format

Converting the .rst to .md
Some manual change between the format
1. The parent file and children file for the file tree system
2. Get rid of the format setting
3. NOTE code not used in md change, change it to md format
4. Font and bold format

You would also need to rebase your work on the latest changes in the main repo. This will get rid of all the extra commits and merges we see in here.

Since this PR had way to many commits and merge conflicts I decided to base a new one on your convert changes as https://github.com/eclipse-oniro4openharmony/eclipse-oniro4openharmony.github.io/pull/12
It does carry your work as the initial commit with your authorship and credit. On top of this I changed the files to match the new use of GitHub. Please review and comment if you are happy with it or found something wrong.


Upgrade threejs r100 -> r122 and enable use of GLSL3

Motivation: want to use integer bit shift to generate random numbers -> requires GLSL3 -> requires WebGL2

Removed dependency on 'is-video' and '@types/three'.
New bundling using rollup helps to deal with three/examples/jsm/* stuff which uses ES Modules whereas atom expects CommonJS modules. vedajs still uses cjs.

This needs to be used in conjunction with another pull request on veda for it to work properly I assume, but shouldn't break any existing shaders afaik.

Thank you for great PR!
I checked out this branch and run VEDA on my mac, then I got this error:
player.ts:19 Uncaught (in promise) TypeError: vedajs_1.default is not a constructor
    at new Player (player.ts:19)
    at new App (app.ts:38)
    at new Wrapper (wrapper.ts:31)
    at Object._activate (index.ts:97)
    at index.ts:93

Maybe something like esModuleInterop is broken?

Yes, I think the ESModule stuff might need fixing, it occasionally works or doesn't work on my machine so I'll try and figure out what makes it work and I will ping again when I gut it working

@fand I updated the rollup config and I think it works now.
The way I've been setting stuff up is by

clone veda & vedajs
apm link -d in veda/
yarn link in vedajs and yarn link vedajs in veda/
yarn in both directories
atom --dev to launch atom and try running/toggling veda

@fand I updated the rollup config and I think it works now.
The way I've been setting stuff up is by

clone veda & vedajs
apm link -d in veda/
yarn link in vedajs and yarn link vedajs in veda/
yarn in both directories
atom --dev to launch atom and try running/toggling veda


Leaf decay

On master branch running 1.14.3-pre1: In new survival world the trees are dropping all their leaves even without anyone touching the trees. I started the server via Eclipse.

For some reason the vanilla data pack fails to load. The leaves use the #logs block tag.


Add more information about where to find the Redirected values

Bug/issue #, if applicable:
Summary
This updated the @Redirected documentation to describe how and where the developer can find the redirect values for each page.
Dependencies
None
Testing

Run swift run docc preview Sources/docc/DocCDocumentation.docc
Navigate to http://localhost:8080/documentation/docc/redirected

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

~[ ] Added tests~
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test


[BUG] breaking change: AppInsights connection string now required in local.settings.json

Library name and version
Azure.Monitor.OpenTelemetry.AspNetCore 1.2.0
Describe the bug
while updating NuGet packages, we were forced to add Azure.Monitor.OpenTelemetry.AspNetCore in order to disable live metrics
old code:
logBuilder.AddApplicationInsightsWebJobs(options => {
    options.EnableLiveMetrics = false;
});

new code:
appBuilder.Services.AddOpenTelemetry().UseAzureMonitor(options => {
    options.EnableLiveMetrics = false;
});

note: in both cases, the EnableLiveMetrics line is inside #if !(DEBUG || LOCAL) because we do run live metrics in Azure
Expected behavior
this has always worked with APPLICATIONINSIGHTS_CONNECTION_STRING as an empty string in local.settings.json
Actual behavior
it now throws here
Reproduction Steps
old code:
new HostBuilder()
    .ConfigureAppConfiguration((hostContext, configurationBuilder) =>
    {
        if (hostContext.HostingEnvironment.IsDevelopment())
        {
            configurationBuilder.AddUserSecrets<Program>(optional: true);
        }
    })
    .ConfigureFunctionsWorkerDefaults(appBuilder =>
    {
        appBuilder.AddApplicationInsights(options =>
        {
            options.EnableDependencyTrackingTelemetryModule = false;
        });

        appBuilder.AddApplicationInsightsLogger();
    })
    .ConfigureLogging((hostContext, logBuilder) =>
    {
#if DEBUG || LOCAL
        logBuilder.SetMinimumLevel(LogLevel.Debug);
        logBuilder.AddFilter("Azure", LogLevel.Error);
#else
        logBuilder.AddFilter("default", LogLevel.Error);
        logBuilder.AddFilter("Function", LogLevel.Warning);
        logBuilder.AddFilter("Azure.Core", LogLevel.Error);
        logBuilder.AddFilter("Azure", LogLevel.Error);
        logBuilder.SetMinimumLevel(LogLevel.Warning);
#endif
        logBuilder.AddApplicationInsightsWebJobs(options =>
        {
#if !(DEBUG || LOCAL)
            options.EnableLiveMetrics = false;
            options.SamplingExcludedTypes = "Exception";
            options.SamplingSettings = new Microsoft.ApplicationInsights.WindowsServer.Channel.Implementation.SamplingPercentageEstimatorSettings
            {
                MaxSamplingPercentage = 0,
                MinSamplingPercentage = 0
            };
            options.HttpAutoCollectionOptions = new Microsoft.Azure.WebJobs.Logging.ApplicationInsights.HttpAutoCollectionOptions
            {
                EnableHttpTriggerExtendedInfoCollection = false,
                EnableW3CDistributedTracing = false,
                EnableResponseHeaderInjection = false
            };
#endif
        });
    })
    .ConfigureServices((hostContext, services) =>
    {
        // snip
    })
    .Build().RunAsync();

new code:
new HostBuilder()
    .ConfigureAppConfiguration((hostContext, configurationBuilder) =>
    {
        if (hostContext.HostingEnvironment.IsDevelopment())
        {
            configurationBuilder.AddUserSecrets<Program>(optional: true);
        }
    })
    .ConfigureFunctionsWorkerDefaults(appBuilder =>
    {
        appBuilder.Services.Configure<TelemetryConfiguration>(telemetryConfiguration =>
        {
#if !(DEBUG || LOCAL)
            var telemetryProcessorChainBuilder = telemetryConfiguration.DefaultTelemetrySink.TelemetryProcessorChainBuilder;

            telemetryProcessorChainBuilder.UseAdaptiveSampling(new SamplingPercentageEstimatorSettings
            { // defaults https://github.com/microsoft/ApplicationInsights-dotnet/blob/main/BASE/src/ServerTelemetryChannel/Implementation/SamplingPercentageEstimatorSettings.cs#L21
                MinSamplingPercentage = 0.1,
                MaxSamplingPercentage = 5,
                InitialSamplingPercentage = 1
            }, null, excludedTypes: "Exception");

            telemetryProcessorChainBuilder.Build();
        });
#endif

        appBuilder.Services.AddOpenTelemetry().UseAzureMonitor(options => {
#if !(DEBUG || LOCAL)
            options.EnableLiveMetrics = false;
#endif
        });
    })
    .ConfigureServices((hostContext, services) =>
    {
        services.AddApplicationInsightsTelemetryWorkerService(options =>
        {
            options.EnableDependencyTrackingTelemetryModule = false;
        });
        services.ConfigureFunctionsApplicationInsights();

        services.Configure<LoggerFilterOptions>(options =>
        {
#if DEBUG || LOCAL
            options.MinLevel = LogLevel.Debug;
            options.AddFilter("Azure", LogLevel.Error);
#else
            options.AddFilter("default", LogLevel.Error);
            options.AddFilter("Function", LogLevel.Warning);
            options.AddFilter("Azure.Core", LogLevel.Error);
            options.AddFilter("Azure", LogLevel.Error);
            options.MinLevel = LogLevel.Warning;
#endif
        });

#if !(DEBUG || LOCAL)
        services.Configure<Microsoft.Azure.WebJobs.Logging.ApplicationInsights.HttpAutoCollectionOptions>(options =>
        {
            options.EnableHttpTriggerExtendedInfoCollection = false;
            options.EnableW3CDistributedTracing = false;
            options.EnableResponseHeaderInjection = false;
        });
#endif

        // snip
    })
    .Build().RunAsync();

Environment
No response

AddApplicationInsightsWebJobs
This isn't an API that we publish. What package were you using in the old sample?

https://github.com/Azure/azure-sdk-for-net/blob/de77bfc02f7bdea836f2b67535bf09161cfe3a47/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter/src/Internals/AzureMonitorTransmitter.cs#L77
This exception is valid. If a connection string is not provided to our Exporter/Distro then the SDK can't send telemetry. We consider that a fatal error and throw during startup.

we're doing the middle of those 3 options when we deploy to Azure, the last for local debugging... what caught us by surprise is that in the old way (where we didn't need to load Azure monitor to turn off live metrics) we could leave it blank locally, now we have to put some nonsense in there... or use preprocessor directives to bypass loading AppInsights
The root question from us is... "Hey, this looks broken, if it's not then what are we doing wrong & where do we find how to do it right?" AppInsights in out-of-proc/isolated Azure Functions has changed a LOT... we've got 3 different projects that we can't copy-paste from because each was done a few months apart with big changes in between
diff of the NuGet versions between old & new codes in the original post:

edited "new" code in original to correct initializing SamplingPercentageEstimatorSettings, because we discovered it was just nonsensically wrong (while searching for how to do options.SamplingExcludedTypes = "Exception"; which was missing from the "new" code)

Hi @af4jm,
It seems you're describing a few different issues. I'm sorry, but I'm not sure how to best help.
I'm going to try to respond, but if I've missed something please ask again.

what caught us by surprise is that in the old way (where we didn't need to load Azure monitor to turn off live metrics)

In the old code you shared, my team doesn't own any of these APIs. It seems like this is someone else's SDK that is wrapping ours. I can only speculate what settings they've turned on or off. If your intention is to continue using their SDK you should reach out to their team and provide the feedback about needing to disable Live Metrics.
To add some context here, when my team shipped https://www.nuget.org/packages/Azure.Monitor.OpenTelemetry.AspNetCore/1.2.0, we added the Live Metrics feature and this is on-by-default by design. Our API allows users to disable Live Metrics. I can only speculate that this other SDK took the update but didn't expose an option to disable Live Metrics.

diff of the NuGet versions between old & new codes in the original post:

Each the packages you included in your screenshot are not published from this repo. You'll need to find the owning repo and report an issue about the change in behavior between versions. Your complaint is valid, but my team doesn't own those packages and we can't help you.

regarding your new code
It seems like you're mixing two different SDKs here, I can't tell exactly what you're trying to accomplish.
Classic Application Insights SDK

Services.Configure<TelemetryConfiguration>
services.AddApplicationInsightsTelemetryWorkerService()

These APIs are from the classic Application Insights SDK:
- Nuget: https://www.nuget.org/packages/Microsoft.ApplicationInsights.workerservice
- Repo: https://github.com/microsoft/ApplicationInsights-dotnet
My team owns this, but this project is in a different repo. This is a fully supported and feature rich SDK.
If you want to onboard to this SDK, please review this doc:
https://learn.microsoft.com/en-us/azure/azure-monitor/app/worker-service
Azure Monitor OpenTelemetry

Services.AddOpenTelemetry().UseAzureMonitor()

This API is from the newer OpenTelemetry based Azure Monitor SDK.

Nuget: https://www.nuget.org/packages/Azure.Monitor.OpenTelemetry.AspNetCore
Repo: https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore

My team owns this, and this conversation is in the owning repo.
OpenTelemetry is a new tech stack and this will eventually replace the former classic SDK.
If you want to onboard to this SDK, please review this doc:
https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable?tabs=aspnetcore

thanks... this project is inventory tracking & syndication (to ad partners), with millions of update events daily, so our goal is to get what we need for alerts when something is wrong, but not so much that our AppInsights spend is out of control... currently we're hitting our daily cap in just a few hours when back in the .NET 5 days we'd get at least 18 hours with the same cap
ironically the rest of this week is our annual internal hackathon, so I think I'm going to make OpenTelemetry my focus... knowing we have a mix of SDKs means we've probably got a lot of duplication, so starting over with the new SDK as a baseline is probably a good idea... then we can dig into what settings are needed to turn down the data we don't need (as opposed to trying to retrofit prior settings into the new model)

follow up question in issue #45373


distance and distanceMsg returns NaN

Hi, I'm trying to run the location tracking module on my phone with my home's gps coordinates but it doesn't appear anything. Then, I checked on DevTools Console (with debug usb) and I read the following log:

I also tried with other coordinates and yours (even I assume your home is really far than mine) and I had the same result.

I'll make a new PR on this one, since I add some more tweaks for the geolocation

@demisquare you can try the changes in PR #35, I fix this issue and add more stuff into it

I still figuring that one, been trying it out for a while and looks like its a GPS things
but, will investigate more when i have time for it


Port Catalog Signing Tests to GitHub

This issue arose out of PR #4061. The tests should be ported so we have coverage of that area of the code.

Note that I have updated the Pester.Commands.Cmdlets.CatalogTests.ps1 file to cover the fix of #4061, so we need to be sure to port from the RS3 branch that has this update.


Disable EditInvestigatorCommand

Disable the use of EditInvestigatorCommand and all relevant classes and test

Pull Request Test Coverage Report for Build 285

16 of 19 (84.21%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.07%) to 80.712%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/investigapptor/logic/commands/EditInvestigatorCommand.java
16
19
84.21%

Totals

Change from base Build 278:
-0.07%

Covered Lines:
2515

Relevant Lines:
3116

💛  - Coveralls


Add Contributing file

Adding the contributing file is useful for new contributors, so they know what to do in this project
Here's a reference link: Contributing.md

I have assigned you to this issue @Dun-sin !

Got it, thanks, will work on this as soon as possible


Views utilizing auto layout don't update

I'm trying to find a work around, but for the time being, I wanted to reach out here and see if there's a way to utilize FBSnapshotTestCase with views that use Auto Layout for layout and positioning of its contents.  Currently the contents are completely empty when a snapshot is taken.

Inactive issue (1 year)


Sensors no more available after update Home Assistant to 2024.1 also 2024.1.1

My whole infos are in the Titel. If you need any addidtional informations ibwill try to help

I'm seeing the same thing here. I'll look into it asap, hopefully tomorrow.

Many thanks. If you need something i will try to help.

I have checked in a fix to this issue. However there's still an issue with detecting sensors that I'll try to resolve before making a new release.

Hi. Thanks. I do not see the fix but is it the new sensor.py file?. Should i replace it?

Yes, that's right.

It is working your fiy. Thanks

I do not know if it has a dependency but in the clima control i do not see the current status like heating/standby/cooling. I see only the mode heating/off/cooling. If the nilan is in heating mode and stand on 22c but in the room it has 25c in the past i see on the clima control Standby (in german it was  "Untätig"). And when the temperatur are 21c the nilan start heating and in the climacontrol i see heating (gernan"heizen"). Now is see only the mode eacen if its heat or not. Did you change this or is it a new bug with the new haos?

I don't see what you describe here. The climate control says "heating" (and changes to a "hot" color) when the cts600.status is "HEATING" and the cts600.led is "On", and the climate control says "Idle" if led.cts600 is "Off", etc.
What is your ventilation unit? Could you check the HA debug log?

Hi. I have a cts 600 VPL15. I foud why. The led says blinking and thenni see  i have a filter alert. I have reset it and now it is working again. Thanks

Oh ok. There should probably be some sort of proper handling of CTS600 alerts.


Slow emoji picker menu appearance

There is a noticeable lag when I click on the emoji icon (when the blue square appear on the video below), and when the emoji picker is actually displayed

raw link if embed failed.
Could reproduce on zulip 6.1 (self-hosted), and zulip.chat.org (even though it seemed a little quicker).
Safari: 16.4
No relevant console output
Searched for similar issue, didn't find one.

//assign

@kraktus thanks for the report -- is it only slow the first time, or every time? The most likely explanation is that it's loading the sprite sheet containing all the emoji from the server (it's a few megabytes); but that should only be slow the first time since the browser will cache it.

Closing this as a duplicate of #25744. Thanks for the report @kraktus!


Dual Messenger at SAMSUNG Smartphones

Hello Alexis, Hello @ all
You can set up "Dual Messages" on SAMSUNG smartphones. Support Pages SAMSUNG
I did this on my test device. I also used several messengers in dual mode (e.g. Telegram, WhatsApp, WeChat).
Then I backed up the mobile phone (SAMSUNG A22 5G - SM-A226B/DSN) (FullFile).
With the current version of ALEAPP, I received the chat content from WhatsApp from \data\data\com.whatsapp.
I then went in search of the 2nd WhatsApp. Here I found the folder \data\user\95.
This is where the dual messenger data is stored. There is also a folder \data\user\0, but it is empty. Of course, because the data is located under \data\data\
I do not know whether Samsung always uses user ID 95 for the DUAL messenger. I would have to test this with a second mobile phone.
I could give the dump of the mobile phone (approx. 25 GB) for testing purposes.
Android 13 is installed on the A22 5G
Messenger: Facebook Messenger, Android 2x, WeChat 2x, Telegram 2x, Viber 2x, Signal, Intagram, Firefox
Best regards

@BrunoFischerGermany this is a somewhat known issue I came across more recently. I have been trying to work on updating parsers to support multiple profiles on phones, but the progress has been slow lately.


Loading slack.yml config file from .github/config directory

Describe the bug
The problem is that the action cannot load the configuration file from any directory outside of .github/workflows. Consequently, when the configuration file is placed within the 'workflows' directory, it triggers an error within GitHub actions due to a deviation from the expected workflow syntax.
No event triggers defined in "on"
To Reproduce

Create a 'slack.yml' configuration file and locate it within the .github/config directory.
Attempt to utilize the configuration file with the associated action.

Expected behavior
Ideally, users should have the flexibility to position the configuration file outside of the 'workflows' directory without encountering any issues.
Screenshots
In the following screenshots, you can observe the contrast between placing the configuration file in directories other than .github/workflows and adhering to the 'workflows' directory:
By putting the config file in any directory other than the .github/workflows, the action can not read config template!
      # Step 14: Post breaking changes to a Slack channel
      - name: Post breaking changes to a Slack channel
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
        uses: act10ns/slack@v1
        with:
          status: complete
          channel: "#sci-design-system-breaking-changes"
          config: .github/config/slack.yml
        if: contains(toJson(github.event.commits.*.message), 'BREAKING CHANGE')

The message is constructed based on the template by putting the config file in the .github/workflows directory.
      # Step 14: Post breaking changes to a Slack channel
      - name: Post breaking changes to a Slack channel
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
        uses: act10ns/slack@v1
        with:
          status: complete
          channel: "#sci-design-system-breaking-changes"
          config: .github/workflows/slack.yml
        if: contains(toJson(github.event.commits.*.message), 'BREAKING CHANGE')

Desktop (please complete the following information):

OS: macOS Ventura 13.5.1
Browser: Chrome
Version: 116.0.5845.110 (Official Build) (arm64)

I appreciate your attention to this matter and kindly request assistance in resolving this issue to enhance the functionality and usability of the package.

@masoudmanson I just ran into this issue. You need to make sure the file exists on the runner before running the step. For example, to use a configuration file located in github/config/slack.yml, you can checkout only that file with the following:
      - uses: actions/checkout@v4
        with:
          sparse-checkout: .github/config

I believe a better user experience would be if the action failed if it could not locate the config file, but for now this should get it working for you.


[zh-cn] sync controller.md garbage-collection.md

content/zh-cn/docs/concepts/architecture/controller.md
content/zh-cn/docs/concepts/architecture/garbage-collection.md

/lgtm
/approve


Can't add Autoload

Can't add Autoload: Invalid name. Must not collide iwth an existing global script class name.

When I try to activate Dialogic in the Project Settings, I get this error where it says that it can't add Autoload because of "Invalid name" and that it must not collide with an existing gobal script class name.
I can't really tell how to reproduce this because I was just doing a game like anyone else and I can't seem to see any script names that are the same so I don't know what collides.
I expect to be able to use autoload.
System (please complete the following information):

OS: Windows
Godot Version: 4.2.1 stable
Dialogic Version: 2.0 alpha 13

I found a fix for it
so apparently you need to clear godots cache, to do this:

go to your games' folder in file manager and delete the .godot folder (make sure you have a backup though, incase anything goes wrong)
delete all .import files in your games' folder.
reboot godot and let it reimport everything and it will be fixed


Delete unnecessary deletion timestamp check

Towards https://github.com/giantswarm/giantswarm/issues/14993
We already have this (below) specified in the webhook configurations so
delete events are not dispatched to the mutator/validator.
    operations:
      - CREATE
      - UPDATE

Do you mean App CR being updated after being scheduled for deletion?

Do you mean App CR being updated after being scheduled for deletion?

Do you mean App CR being updated after being scheduled for deletion?

The problem is because the cluster values configmap and the kubeconfig secret are deleted first because they have no finalizer. For the app CRs there is an update event to set the deletion timestamp but the validation fails because the resources now do not exist.
The current code allows the update to take place and means the app CRs are deleted cleanly.

Do you mean App CR being updated after being scheduled for deletion?

The problem is because the cluster values configmap and the kubeconfig secret are deleted first because they have no finalizer. For the app CRs there is an update event to set the deletion timestamp but the validation fails because the resources now do not exist.
The current code allows the update to take place and means the app CRs are deleted cleanly.

I tested that in my local setup and you are right. To repro:

I created an app in in a namespace
Added finalizer to the app
Deleted the namespace
Edited the app manually
There was an event for the app with the deletion timesamp (setting the deletion timestamp itself didin't trigger the event)

I tested that in my local setup and you are right. To repro:

I created an app in in a namespace
Added finalizer to the app
Deleted the namespace
Edited the app manually
There was an event for the app with the deletion timesamp (setting the deletion timestamp itself didin't trigger the event)


DataHub's Slack workspace invite link doesn't seem to be working

DataHub's Slack workspace invite link mentioned in README and other places doesn't seem to be working. How do I join the workspace?

Thanks for letting us know, @abhilash1in. We have fixed the links on those pages using a never-expiring invitation: https://app.slack.com/client/TUMKD5EGJ/C01040VS7CJ


fix(checkbox-group): fixed checkbox scroll issue

💡 What is the current behavior?
When using a scrollable list of checkboxes in combination with ix-content, after scrolling and checking a checkbox that is at the bottom of the list, the content jumps up.

GitHub Issue Number: #1308
🆕 What is the new behavior?

the input that was used as place holder hide the input

🏁 Checklist
A pull request can only be merged if all of these conditions are met (where applicable):

[ ] 🦮 Accessibility (a11y) features were implemented
[X] 🗺 Internationalization (i18n) - no hard coded strings
[X] 📲 Responsiveness - components handle viewport changes and content overflow gracefully
[ ] 📄 Documentation was reviewed/updated (pnpm run docs)
[ ] 🧪 Unit tests were added/updated and pass (pnpm test)
[ ] 📸 Visual regression tests were added/updated and pass (Guide)
[ ] 🧐 Static code analysis passes (pnpm lint)
[ ] 🏗 Successful compilation (pnpm build, changes pushed)

👨💻 Help & support

If display: none is the solution here, everything else in the same selector will be obsolete, is it not?

remain parts can stay as it is. only input component should have been fix

We resolved this issue here in #1527 with a focus on accessibility, as just hidding the checkbox makes the keyboard navigation difficult.


[BACKLOG-37948] HCP in native mode not working for Drag and Drop

:warning: Build finished in 6m 45s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
plugins/file-open-save-new/core

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 21 test(s) failed:
org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testVfsDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetName (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetPath (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testRepositoryFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testLocalFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getConnection (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testToString (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testRepositoryDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testNamedClusterDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getRepositoryName (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testNamedClusterFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetEntityType (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testRecentFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetDomain (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testHashCode (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getProvider (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testEquals (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testLocalDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testVfsFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.convertToFileObject (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTransferTest.javaToNativeAndBack (click to expand)
org/pentaho/vfs/ui/VfsResolver

Tests run: 38, Failures: 21, Skipped: 0    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 3m 17s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
plugins/file-open-save-new/core

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 21 test(s) failed:
org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testVfsDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetName (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetPath (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testRepositoryFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testLocalFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getConnection (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testToString (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testRepositoryDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testNamedClusterDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getRepositoryName (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testNamedClusterFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetEntityType (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testRecentFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getAndSetDomain (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testHashCode (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.getProvider (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testEquals (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testLocalDirectoryConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.testVfsFileConversion (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTest.convertToFileObject (click to expand)
Could not initialize class org.pentaho.di.plugins.fileopensave.dragdrop.Element

org.pentaho.di.plugins.fileopensave.dragdrop.ElementTransferTest.javaToNativeAndBack (click to expand)
org/pentaho/vfs/ui/VfsResolver

Tests run: 38, Failures: 21, Skipped: 0    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 31m 12s
Build command:
mvn clean verify -B -e -Daudit -amd

:ok_hand: All tests passed!
Tests run: 5336, Failures: 0, Skipped: 14    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 6m 33s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
plugins/file-open-save-new/core

:ok_hand: All tests passed!
Tests run: 38, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Toasted-marshmallow for performance boost.

While looking into some performance testing we noticed serialize and deserialize are often called. Marshmallow could be a bottleneck. We should consider using https://github.com/lyft/toasted-marshmallow for a significant performance boost.

I notice that toasted-marshmallow is last updated 4 years ago ... maybe I'm wrong, but I would be skeptical to use that instead of base marshmallow, which seems fairly well maintained by comparison
I don't know the repos, so I asked GPT4 to look at the readme's and explain
toasted marshmallow would yield a performance boost in theory because:

it implements a Just-In-Time (JIT) compiler for marshmallow. JIT is a technique where a computer program compiles into native code or bytecode at runtime, rather than prior to execution. This has the advantage of better runtime performance, as the compiler has more information about the program's state.

However, there's the caveat:

Remember, though, that for toastedmarshmallow to be effective, it's critical that you re-use Schema objects. If you're creating a new Schema object every time you serialize/deserialize an object, you'll likely have worse performance.

So, is that the actual cause of why the code is slow? Creating of new Schema objects every time it's called?
I'm not sure what to make of that, maybe someone else can pick up on that given that idk how the schema serialisation/deserialisation is happening in the codebase!
Note that performance bottlenecks can also be due to the size of data being processed ... a solution would be remove unnecessary data before de/serialisation. Also, json.dumps is called a lot ... like, a lot - 449 results if I search for it. Which, afaik is not the best choice for large data / high performance ... It's late, someone else take it from here 😄

So even though Toasted Marshmallow has a totally cool name, it sounds like it is a no go.  Agreed?
@andrewwhitehead — highlighting this to add you to the conversation.


albumart.js error message

Sometime I get this message when trying to use sample panel "album art". This happens only if I play album not from my library but from explorer with Win10 context menu "Play in Foobar2000". I noticed that albumart.js is slightly modified from original Marc's file and exactly that lines in the message.

I was using sample from 1.2.2 and then I found newer sample version in Marc's SMP_2003 repository which seems to work without error. All good!


Angular2

Cleaned project
Initialised Angular 2 application
Added list view for features
Added detail view for features
Added deep link support for both of them

For list view it also already supports the names parameter for filter by name

Haven't spot issue, but as my Angular and ts skills are near to non existent, better to have some one else have a look.

👍


spi read not available under pins - more

spi read not available under pins - more
spi write is available

My bad
https://developer.mbed.org/handbook/SPI


rsa_test: add return value check

[x] tests are added or updated

This pull request is ready to merge

Merged to master and 1.1.1, thanks.


chore(deps): update dotnet-sdk to v9 (major)

This PR contains the following updates:

Package
Type
Update
Change

mcr.microsoft.com/dotnet/aspnet
stage
major
8.0-alpine -> 9.0-alpine

mcr.microsoft.com/dotnet/sdk
final
major
8.0-alpine -> 9.0-alpine

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Not migrating to .NET 9, it is in RC.

 You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


[Feature Request] Config for a delay to swap

Would it be possible to add a configurable delay to to equipting the chestplate to allow for bouncing on the floor? or making so it stays with the elytra if your still holding space? this is an example of what i would like to be achievable but with the chestplate instantly equipting it makes it basically impossible. with a mod like this it makes elytra very useful without fireforks
i really enjoy the mod :D

So i added compatibility with elytra recast
If recast is enabled chestplate will not be swapped on ground if space is pressed

It works flawlessy, thank you so much!


Worlds gets unloaded automatically

What went wrong
When /world load a custom world, PJW announces an ID conflict and tells the user that it will try to solve the error automatically. Shortly after (~15sec) the world gets unloaded again and the player can't /tp there. If the player manages to tp himself into the world during this short amount of time, the worlds stays loaded
What i expected to happen

World stays loaded
PJW properly solves the ID issue

How to reproduce

create a server with the 3 vanilla worlds (DIM-1, DIM0, DIM1)
try to load another world
watch the world burn ;)

Still haven't come up with a solution for this, but I'm working on it

I'm almost positive this has to do with the default behavior of minecraft. Vanilla and Forge will both unload worlds that are unoccupied. I remember having this problem with Cauldron and Multiverse a couple years back. It seems setting keepSpawnLoaded to true on load or creation prevents this behavior from happening. Next build should help prevent this problem but it's basically just a work around. If admin changes the keepSpawnLoaded flag the problem will return.

52d89367d08ff2cd8ea475d53c6e80aa5bc58ef8


Add support for parsing child blocks

From http://discuss.asciidoctor.org/AsciidoctorJ-Block-Processor-Problems-tp3150p3297.html
Second, we need to provide a way to parse child blocks. We talked about adding this feature to the createBlock method. I also think it's reasonable to add a method to AbstractBlock named either parseChildren() or parse(List<String>). In the first case, it would parse child blocks from the source lines passed to the block constructor. In the second case, it would parse blocks from an arbitrary set of lines and append them to the block as child nodes. I'm leaning more towards the second option.

Fixed with #337


merge and refactor parun and iproteus functionality

parun is a script that takes command line options and various filename arguments describing physics, numerics, and batch input.  It  sets up the proteus environment based  on the options and the runs the simulations specified by the file inputs. iproteus  is a convenience module that sets up the proteus environment for general python scripts and ipython notebooks.  iproteus was derived from parun, but I never got  it  to the point of completely replacing parun, consequently we have duplicate code  and maintenance  problems like #214 .

+1.  I assume the end goal would be for iproteus to completely reproduce parun's functionality and then parun just call iproteus?