Different Version Numbers for the current JDK 8 hotspot MSI

I'm building deployment automation at the moment and i noticed that the current JDK 8 hotspot release has different version numbers in the x86 and the x64 version.
x86: 8.0.275.01
x64: 8.0.275.1
It would be great if the version numbers are the same, since its the same release.
Thanks!

@aahlenst this must be looked up into the upstream job I think, all the build numbers are passed as installer job from caller job
https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/10068/parameters/
x64  > PRODUCT_BUILD_NUMBER=03
https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/10048/parameters/
x86-32 > PRODUCT_BUILD_NUMBER=03

@Apfelwurm can you precise where you find this version numbers and on which plateforme (Linux/Mac/Windows (Zip/msi)) ?

Oh, i should have written this in the text as well, the msi packages under Windows are affected.
it can be checked with MS Orca (tool which is included in the Windows SDK) in the Property tables of the MSI.

Sorry, this is not PRODUCT_BUILD_NUMBER but 'MSI_PRODUCT_VERSION' wich is used for  ProductVersion
and the last change is from 2020-11-10 13:26:25 +0000 https://github.com/AdoptOpenJDK/openjdk-build/pull/2219
but the x86 OpenJDK8U-jre_x64_windows_hotspot_8u275b01.zip  was generated at 2020-11-09 (before the last change/fix)
I think this is already adressed since https://github.com/AdoptOpenJDK/openjdk-build/pull/2219
Nighlty from 2 December 2020 are good
x64 8.0.282.3
x32 8.0.282.3

inside "release" file
x86 BUILD_SOURCE="git:47ad2f52" commit from Date:   Sun Nov 8 14:58:00 2020 +0000
x64 BUILD_SOURCE="git:c0a1a87c" commit from Date:   Tue Nov 10 14:54:15 2020 +0000


Ensure tox environment is clean

With this commit we force-clean the environment used by tox in order to
ensure dependencies are always up-to-date as tox / pip will not upgrade
dependencies automatically.

Thanks for the review! :)


Barber scissors fix

About the PR

fix some problems with barber scissors
Why / Balance

fix #22887
fix some Sloth review
Changelog
:cl:

fix: Fixed barber scissor infinity range issue

idk how to do it
@metalgearsloth

I think I fixed it.

Copying from discord but:

magicmirror shouldn't have its own range, just use canreach for afterinteract
the ui stuff should be using UI states not UI messages
you don't need the activatableUI events if you're using states as it gets handled automatically
you don't need to range check in the do_afters because if the do_after is set properly it will cancel itself before then
The do_after events aren't cloning properly as they're copying by reference.


Upgrade to Bootstrap 4!

Nick (@nickschot) has added Bootstrap to the website so that we can start using things such as table-responsive. At the moment we aren't using that much of bootstrap due to which it is likely preferable to switch to Bootstrap 4 now, as it will require less work than when more Bootstrap elements are used.

We do use a lot of bootstrap, the entire responsive layout is based on bootstrap... For now I would reccomend against BS4, because it is marked alpha by its developers. Maybe we should reconsider when BS4 becomes beta software :).

The latest alpha has been released, there won't be any major feature additions. The only stuff we use from bootstrap right now is the grid (which is mostly backwards compatible, just different breakpoints and more features) and the navbar (of which we only use the less right now...).
Having built multiple applications w/ basically all 6 alpha's of bootstrap 4, I'd recommend doing it asap as it spares us a more costly migration in the future. The only change necessary right now is porting the less we have to SCSS, which is very minor (replacing @ w/ $ is enough for variables and we don't use much (if any?) advanced functionality).
This also opens up the way for i.e. flexbox as supported by BS4.

Flexbox also implicitly means dropping support for IE <9, but I think thats
fine :).
2017-03-07 16:26 GMT+01:00 Nick Schot<EMAIL_ADDRESS>
The latest alpha has been released, there won't be any major feature
additions. The only stuff we use from bootstrap right now is the grid
(which is mostly backwards compatible, just different breakpoints and more
features) and the navbar (of which we only use the less right now...).
Having built multiple applications w/ basically all 6 alpha's of bootstrap
4, I'd recommend doing it asap as it spares us a more costly migration in
the future. The only change necessary right now is porting the less we have
to SCSS, which is very minor (replacing @ w/ $ is enough for variables and
we don't use much (if any?) advanced functionality).
This also opens up the way for i.e. flexbox as supported by BS4.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Inter-Actief/amelie/issues/214#issuecomment-284753508,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAoTxSg4nQwkQOTsL6IoWDcgs8MzQIbpks5rjXcqgaJpZM4MVQeP
.

I'd rather not use alpha software, so I'd like to wait for it to become beta at the very least. We could however start implementing it in a separate branch with the alpha, and switching to the beta once it's released.

The site says beta now :D

Wait till it is a month in production... there are too many differences between the alphas and betas.

Bootstrap 4 is also breaking, f.e. removes glyphicons…
https://getbootstrap.com/docs/4.0/migration/


Bot Not Responding To Admin Commands

The admin steamid is set and saved however even after bot restarts, the bot fails to respond to add, remove, metal etc. There are no visible error codes.

#427 #527

try to add both api keys correctly on settings.json


use yew with version 0.18.0

@lukidoescode would you consider bumping the yew version. I really like the idea of your project it looks nice :)


WorkflowQueue.TryDequeueAsync() timeout isn't working

The Test_EndToEnd.Workflow_Queue_Timeout test is failing.

Fixed.


[stable/traefik] add support for Forward Authentication

What this PR does / why we need it:
Adds support for Traefik Forward Authentication.
Upstream documentation: https://docs.traefik.io/configuration/entrypoints/#forward-authentication
Which issue this PR fixes
No issues found.
Special notes for your reviewer:
None.
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

@redondos will you update this from master, so we can try to get it merged?

@billimek, sure, sorry for the delay. We've actually been using a slightly different syntax that we've found more useful in our organization, so I've pushed those changes based off the updated master.

/ok-to-test

/assign dtomcej

@billimek @dtomcej, can we please get this reviewed?

/assign @mmatur

/assign @dtomcej

Hi @redondos
Could you please rebase your PR?

@mmatur sure, done.

/ok-to-test


[HUDI-4770][Stacked on 4294] Adapt spark query engine to use secondary index when querying data

Change Logs
Convert spark filter to index filter, acquire and push down hit row id set.
Impact
Tables which have secondary indices will use secondary index to query hit row id set when using spark query engine.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

hey @huberylee : Is there an RFC around this.

hey @huberylee : Is there an RFC around this.

Yes, this PR is part of the secondary index implementation. RFC is in another PR: https://github.com/apache/hudi/pull/5370

Hi @huberylee , are you still actively working on this PR and resolving conflicts?


fix: account for all changes in 1.21.4

This PR fixes the last issues with 1.21.4. In PaperMC's dev builds, starting from build 20, their "hard-fork" is implemented. I don't foresee this causing any issues unless they mess up mappings since they are no longer a fork of Spigot. After testing on 1.21.4, I noticed a few protocol changes overlooked in the previous release. Below is a summary of those fixes.
Class mappings:

src/main/resources/mappings.json: Updated the mapping for ParticleParamTargetColor to TrailParticleOption and added a new version-specific mapping for version 1.21.4 and above.

Packet constructors:

src/main/java/com/georgev22/particle/ParticleConstants.java: Added a new packet constructor for Minecraft versions 1.21.4 and above that includes an additional boolean parameter (two booleans: boolean forceSpawn, boolean important, both set to true).
src/main/java/com/georgev22/particle/ParticlePacket.java: Updated the createPacket method to use the new packet constructor for versions 1.21.4 and above.

Thank you for your work on this PR! I have a few questions regarding the changes.
Does the mapping change from ParticleParamTargetColor to TrailParticleOption work correctly in 1.19? If I recall, this change was required in 1.19, but if it was renamed or modified in 1.20.4, then it might be better to introduce TrailParticleOption as a new mapping. Additionally, we should adjust the maximum version for ParticleParamTargetColor to reflect where it was removed or renamed.
Please let me know if I’ve misunderstood something.

@nicholasveronico Thank you for your work on this PR! I have a few questions regarding the changes.
Does the mapping change from ParticleParamTargetColor to TrailParticleOption work correctly in 1.19? If I recall, this change was required in 1.19, but if it was renamed or modified in 1.20.4, then it might be better to introduce TrailParticleOption as a new mapping. Additionally, we should adjust the maximum version for ParticleParamTargetColor to reflect where it was removed or renamed.
Please let me know if I’ve misunderstood something.

@nicholasveronico Thank you for your work on this PR! I have a few questions regarding the changes.
Does the mapping change from ParticleParamTargetColor to TrailParticleOption work correctly in 1.19? If I recall, this change was required in 1.19, but if it was renamed or modified in 1.20.4, then it might be better to introduce TrailParticleOption as a new mapping. Additionally, we should adjust the maximum version for ParticleParamTargetColor to reflect where it was removed or renamed.
Please let me know if I’ve misunderstood something.

Hey @GeorgeV220, no problem! The mapping ParticleParamTargetColor / TrailParticleOption was created in the last PR, with the introduction of that new particle data for ParticleEffect.TRAIL. The rename was for better understanding and consistency, to match the Bukkit naming of the classes. In 1.21.3, the class was named TargetColorOption, explaining the TargetColor portion of the mapping name. Thought it would be better off using the latest name TrailParticleOption for the mapping name instead.
I had originally named it ParticleParamTargetColor due to the rest of the existing particle option class mappings being prefixed with ParticleParam, even though they are not particle parameters. This is something I am looking to address in a future PR, likely in the new year. The original code is pretty messy and really requires a clean up. Due to this, I don't think it's necessary to separate them and include a max version, as the name difference between 21.3 and 21.4 is already addressed in the mapping itself.
Merry Christmas!


Typecheck Arrow Terms

Problem:
Term::Arrow doesn't even try to typeck.
Solution
Implement typeck for Term::Arrow.
Context
exists x:Aa. x>2;           //sugared
$"exists"(fn(x: Aa) = x>2); //desugared

If a return type is provided on the Arrow, then send it in the implied field, otherwise implied is None and return type should be inferred.

Fixed in #102


Follow up improvements to documentation of branching model

Follow up on some typos and elaboration as discussed in this review.

Along with the typo suggestions above, [issue#]-brief description may be more clear to indicate replacement, or show an example, to not be confused with prefixing with "issue":
Like this: 8-update-sass
Not this: ~issue#8-update-sass~

In addition to the above referenced thread on #18 (thanks @kriscooke) perhaps this discussion should include discussion of what behaviours conventions provoke? Adopting a branch naming convention that begins with the ticket number strongly encourages the team to always make an issue before making a branch/PR. Is this always necessary in our new workflow?

Would also like to discuss requesting a particular reviewer vs. marking as ready for review

I'd lean towards creating a @button-inc/digital_marketplace team on GitHub and making the entire Button development team the CODEOWNERS of this entire fork. That doesn't solve for everything

especially days when Mike isn't here

but it would ensure the act of requesting review is automated by a guardrail.


Allow to set the namespace which is used for Keptn

Currently, the CLI always installs Keptn in the namespace keptn.
Now, we would like to make the used namespace configurable, which allows to have multiple Keptn installations per cluster.
Please note, that we do not support multiple Keptn installations within the same namespace.
Tasks

Allow specifying the namespace in keptn install by introducing a flag --namespace. This should default to keptn.
Allow specifying the namespace in keptn uninstall by introducing a flag --namespace. This should default to keptn.
Allow specifying the namespace in keptn generate support-archive by introducing a flag --namespace. This should default to keptn.
/metadata of the API also contains the namespace where Keptn is installed

In order to easily switch between Keptn installation, we also should investigate issue https://github.com/keptn/keptn/issues/1863
Furthermore, this issue solves https://github.com/keptn/keptn/issues/1287 because the name of a Keptn installation is then the name of the namespace.
Definition of Done

[ ] Main tutorial (full-tour on DT/Prometheus and QG-only) work with a Keptn installation contained in a namespace other than keptn
[ ] CLI docs are updated

I will take this one!

Information about the current status of this issue.
Completed:

Allow specifying the namespace in keptn install by introducing a flag --namespace.
Allow specifying the namespace in keptn uninstall by introducing a flag --namespace.
Allow specifying the namespace in keptn generate support-archive by introducing a flag --namespace.
Replaced hard coded namespace in API,  configuration service and lighthouse service.

Still needs to be done:

Keptn contrib services need to be converted to Helm and feature dynamic namespaces instead of hard coded ones.
The Dynatrace SLI service still has a hard coded string for the CONFIGURATION_SERVICE that needs to be replaced.
CLI documentation needs to be generated after the features are finished.

#2214 #2216

I've solved the "dynamice" namespace issues with these PRs
https://github.com/keptn-contrib/dynatrace-sli-service/pull/67
https://github.com/keptn-contrib/dynatrace-service/pull/175/files

To close this issue, a final test is required:

[ ] keptn install --namespace=keptn-tiger
[ ] Execute: Onboarding + Quality gates (with Dynatrace) + Remediation use cases
[ ] keptn generate support-archive --namespace=keptn-tiger
[ ] keptn uninstall --namespace=keptn-tiger


augmenting svg over cover image

overlaying a svg on an image that is contained and set to cover means we lose the image coordinate basis. This is a problem for the image of the of 2 elderly people on the the beach here because we want to point to the mans pocket and legs with overlaying svgs...

Now fixed. See https://codepen.io/arrancurran/pen/qBqdErq for solution.


Medication additionalProductInformation data type

For this element in medication logical model, the data type is BackboneElement (in IHE model it's Class).
Should decide if this is going to be just reference to something (to what in logical model?) or what other options are there.

Options:

...[x]
string
Reference

I'd prefer string.
I would avoid BackboneElement without content

Data type was changed from BackboneElement to Base, but that didn't take away the problem. Then we discussed, could not figure out how to have Reference to unknown, and for now, I just temporarily commented it out until we have a solution.
FHIR has a reference there to MedicationKnowledge. We proposed adding a reference to some of the MedicationDefinition module resources (https://jira.hl7.org/browse/FHIR-46414) but there is no resolution. It could also be a link to a national registry or ePI.


angular sample added

Summary
Adds angular example, as well as a regression test to reproduce #8401
Uses nrwl starter with angular and jest.
To run:

npm install
npm run test

Test plan

Running yarn eslint examples/angular --cache --ext js,ts from the root of the repo should fix most (all) of the lint errors reported on CI, btw 🙂

Codecov Report

Merging #8905 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8905      +/-   ##
==========================================
- Coverage   64.24%   64.24%   -0.01%
==========================================
  Files         275      275
  Lines       11658    11656       -2
  Branches     2846     2843       -3
==========================================
- Hits         7490     7488       -2
  Misses       3544     3544
  Partials      624      624

Impacted Files
Coverage Δ

packages/jest-diff/src/getAlignedDiffs.ts
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Could you sign the CLA as well? Then I think we're good to go! 🙂

Is it possible to use jest-preset-angular?


About finetuned Model

Hi, congratuations!  I try to run the model for finetuning the KITTI2012 but the result is terrible.
could you release the finetuned model about KITTI2012 dataset ?  And during the training, there is anything i need to pay attention to？

Hi, the model submitted to the KITTI benchmark is trained with all the KITTI data (both 2012 and 2015), meaning that there are 394 training image pairs (194 + 200). Other training details are the same as those in "KITTI_ft.py" file.


Warn users when they attempt to create a PR from default branch

This resolves issue https://github.com/sindresorhus/refined-github/issues/1664 .
I think the commit name is pretty self-explanatory. I'm open to any suggestions on the wording of the message. Should we link to a page like this one https://blog.jasonmeridth.com/posts/do-not-issue-pull-requests-from-your-master-branch/ ? It's pretty informative, but I'm worried that this link might break eventually.
Here's a screenshot of the warning:

You can replace everything after the first if with:
select(/* container selector */).append(

 your JSX here

);

Also the style should be borrowed from GitHub’s own alerts, by using their classes

Thanks for the feedback! Haven't touched JS in a while so I'm glad you pointed out the issues you found. I had trouble figuring out what class to use for the warning (surprise the warning class is already style by githhub).
Here's what it looks like after making the changes you mentioned:

I think the warning div looks a little out of place though (could probably use some padding and a border to fit in with the rest of the page). I'm not familiar with github's styling and I'm not sure if there's a better way to style this (without introducing any extra CSS). Any idea if there are already some github style I could leverage?

Found the right style on https://github.com/<user>/<repo>/test/settings/installations

    Note:
    GitHub
    Services have been deprecated. Please contact your integrator for more
    information on how to migrate or replace a service with
    webhooks or
    GitHub Apps.

I made some changes on the fly, not sure if it's fully correct.

This is another possible view that needs to be covered, under two different paths:

https://github.com/bfred-it/select-dom/compare/ts-html-element-type?expand=1  Users will end up here when clicking on
https://github.com/bfred-it/select-dom/compare/master...ts-html-element-type?quick_pull=1  Users will end up here when editing a file while creating a fork... maybe

Excellent! Thanks @vacuus 🍏


docs(dark-mode): add theme-color meta tags to Dark Mode documentation

People regularly encounter an issue when setting up dark mode, see https://github.com/shadcn/ui/issues/313, so I've added the fix to the dark mode's documentation page.
We could also consider removing @layer base from the CSS. It seems unnecessary and it would be easier.
PS: amazing the work you're doing Shadcn! The popularity of this library shows it. Congrats and thanks a lot :slightly_smiling_face:

docs(dark-mode): add theme-color meta tags to Dark Mode documentation

@Zwyx is this still relevant or was it fixed in latest Chrome update?

@Zwyx Maybe have a look if https://github.com/shadcn-ui/ui/issues/313#issuecomment-1676513456 is a viable solution, it works great and one does not need to modify the meta tags

@Zwyx Maybe have a look if #313 (comment) is a viable solution, it works great and one does not need to modify the meta tags

Thanks @toitzi, it seems to be a good solution indeed. I'll test it and update this PR :+1:

This PR is now closed, and replaced by https://github.com/shadcn-ui/ui/pull/1780


Fix py.typed verification script

In order to ensure that a py.typed file is packaged with both source and binary distributions of a package, we have a script that verifies various configurations. This script had a bug that would validate a package as passing as long as the MANIFEST.in file was correctly configured, disregarding issues in the setup.py file.
This fixes the issue and updates pertinent impacted setup.py files.
Note that the following packages also have issues with their configurations, and their pipelines have been failing for a while due to the verify_sdist check failing. Presumably we'd want to disable the CI for these entirely since they are no longer maintained.

applicationinsights/azure-applicationinsights
loganalytics/azure-loganalytics

API change check
API changes are not detected in this pull request.

Thanks for the review, @scbedd!


update on readme.md

I fixed what it needed to be fixed.
I chose to include in installation parts both :

bash command
link to docs

Tell me if some points need to be removed or updated.
Fixes #1045

/packit build

pre-commit: FAILURE in 2m 38s

The pre-commit test is failing because you need to rebase your changes.
'rebase' is something you'll need to understand sooner or later anyway if you're going to use git, so I'd suggest investing some time into learning what it is and how to do it.

The pre-commit test is failing because you need to rebase your changes.
'rebase' is something you'll need to understand sooner or later anyway if you're going to use git, so I'd suggest investing some time into learning what it is and how to do it.

I update my fork repository to the new version of the original packit repo. And updated the readme file.
What is the difference with git rebase ? I mean I updated the repo directly on github. I read some infos on rebase function but I still don't understand what is the difference.
It seems that I already installed pre-commit packages, but maybe I misunderstood something ! :)

updated my fork repository to the new version of the original packit repo. And I updated the readme file by removing the line you quoted on the past comment.
What is the difference with git rebase ? I mean I updated the repo directly on github. I read some infos on rebase function but I still don't understand what is the difference.

I am not sure what exactly have you done, but the article Jirka has linked describes the rebase very nicely.
There is really a lot of articles about differences between merge and rebase, but in short:

Merge will create a new commit that combines changes from your update_readme branch and from the new commits from master branch.
Rebase re-applies your commits from your update_readme branch on top of the current master.

And the effect:

With merging, there is a lot of merge commits and the git tree is very messy. And if you leave merge of the pull-request to GitHub, we are not testing the same code that will be on master when we merge the pull-request.
With rebase, the history is clear, we can't have any conflicts with the master branch when we merge pull-request. -- The result is always same as the code in PR.

Just put something like difference between merge and rebase to the search engine. You will find a lot of articles and images.

What is the difference with git rebase ? I mean I updated the repo directly on github. I read some infos on rebase function but I still don't understand what is the difference.

Yes, there should be no difference.

It seems that I already installed pre-commit packages, but maybe I misunderstood something ! :)

There are 2 steps, if you did both, you should be fine.

pip3 install pre-commit
pre-commit install -t pre-commit -t pre-push

/packit build

I am not sure what exactly have you done (probably merge ), but the article Jirka has linked describes the rebase very nicely.

Yes i'm reading it today to understand it better, didn't have time yesterday because of work.

There is really a lot of articles about differences between merge and rebase, but in short:

Thanks a lot for the quick explanation, I will dig into it more, it seems to be more efficient, so I need to know to do it :)

There are 2 steps, if you did both, you should be fine.

Yeah I did both.

Looks OK. Thank you for your contribution! rocket

Thanks for letting me start to help and learn :+1:


Update readme, add ungrouped docs

Wondering if we should also add a link to the fiddle somewhere obvious in docs... header? in TOC?


Deeplink Producer broken

What
When clicking a link from slack
https://de.openfoodfacts.org/marke/hellriegel
https://github.com/openfoodfacts/smooth-app/assets/39344769/53733c33-fdab-49e3-bb4c-b9a9f72f1c46

Right now, we accept all sub-domains and should whitelist only the ones supported.
Is-it possible to have a list of them?

https://crt.sh/?q=%25.openfoodfacts.org

This should be fixed by #4072
I close this issue


Does not work as root

Thanks for a great library with many functions I been seeking for. I noticed though that I don't get the events when I run my node project as root. Do you have any advice on how to go about it?

@ellensundh you're welcome, I've been busy these last couple of days but I'll check into it ASAP. Are you sure you are running the latest version 0.1.9?

Resolved in version 0.1.9 as of Issue #1


How to fine tine gptneo for QA dataset?

I would like to fine tune this model to my custom QA dataset where the input is a question and a data table, and the output is an answer to the question. How can I have this setup for this model? I can keep the answers in the tf_records as target output of model but where would input questions and data table go?

I'm not sure I understand the question... the input questions and data table go as the model input.

Could you please clarify the way (if any) to pass input_text (feature) and target_text (label) for training? Right now I can't see that it's implemented.

This  code base only supports autoregressive training. This means that you need to reprocess your data into something along the lines of
|Task Name|Train|Val|Test|Val/Test Docs|Metrics|\n|-----|-----|-----|-----|-----|-----|\n| cola |✓|✓||1043|mcc|\n|mnli|✓|✓||9815|acc|\n|mnli_mismatched|✓|✓||9832|acc|
and then treat it like normal text (note that this is the first three lines of this table. Alternatively you can use a pretrained GPT-Neo model as a text feature extraction model, and run the table through some other model before concatenating the embeddings.


Memory port transparency model is flawed

 Issue by whitequark
Friday Sep 20, 2019 at 18:04 GMT
Originally opened as https://github.com/m-labs/nmigen/issues/216

Investigating #172, it appears that there are two major issues with the way port transparency is handled.

Transparent read ports should not be the default, since it is expensive. On many platforms (e.g. iCE40), fabric logic will need to be inserted. On other platforms (e.g. Xilinx), non-transparent ports have a much larger set of configurations with well-defined behavior. Transparency between different clock domains is impossible with BRAMs and will result in a (silent) failure during synthesis.
Transparency should not be requested in general, but rather for a specific write port (in the same domain). It does not make sense to request a "fully" transparent read port for a true dual-port RAM with write ports in different domains. It does make sense to request a read port transparent only wrt one specific write port for a true dual-port RAM with write ports in the same domain (this is implementable in Xilinx) and a read port transparent wrt both write ports for a true dual-port RAM with write ports in the same domain (this is not directly implementable in any FPGA arch I know, but is useful for e.g. superscalar CPU register files).

I propose to remove transparent completely, replacing it with a transparent_for=[write_ports] argument. The default (when this argument is not specified) would be "transparent for no write ports" for synchronous read ports, and "transparent for all ports" for asynchronous read ports. It would not be possible to specify a non-default value for an asynchronous read port.
The lowering to RTLIL would be the same as today, with the selected write port ignored (beyond checking that the domain is compatible),

If there a way to say "I'm not going to read and write in the same cycle ever, so do what's best given the platform"?

No. Yosys doesn't support it.

Yosys now supports a much better memory port transparency model.
This issue will be solved by https://github.com/amaranth-lang/rfcs/pull/45.


Make a method to retrieve slow pulse energy data with XGM component

XGM component can retrieve only pulse-resolved pulse energy data at the moment. Sometimes we also use train-resolved (slow) data. It usually has a key of a form 'controlData.slowTrainSa'. Please add a method for retrieving it.

I see, thanks. It would be good to have a separate method though because now it's almost as verbose as doing e.g.
run['SA3_XTD10_XGM/XGM/DOOCS', 'controlData.slowTrainSa3'].xarray().
Yes, it's sort of an average value but as far as I know it's the only energy value that is absolutely calibrated, while fast data is not. We rarely use it but occasionally it's needed, for example if I want to see fluctuations trend over a few hours.


Changelog doesn't show up on mobile

Describe the bug
When a new version comes out, the changelog does not show up on my phone.
Reproduction

Wait for new release
Load page on a mobile device that has had the game open previously

Logs
No response
System Info
Pixel 7 Pro, Firefox App

Additional Information
No response

As of 0.4.1 this seems to be now working.


Change Web Clip icon in IoT 3.1.0

Description:
When web clip is installed in the device, always the default icon is set. The icon needs to be configurable.
Affected Product Version:
IoT 3.x.x
OS, DB, other environment details and versions:
iOS devices
Steps to reproduce:

Create a web clip using publisher
Push it to an enrolled iOS device
Default icon will be displayed on the launcher

Fixed with https://github.com/wso2-support/carbon-appmgt/pull/69


[FEATURE] Review Mode

Is your feature request related to a problem? If so, Please describe.
Several different customers have described to us troubles with reviewing pipeline-generated annotations.  In particular, they get confused about what they have and have not reviewed, which I agree is a real concern.  #587 solves a very small part of this.
I think in general the workflow of looking at and correcting annotations is very different than creating from scratch, and calls for different controls. Some of the annotation controls may be getting in the way of review.
Describe the solution you'd like
Some kind of review mode where we add a "reviewed" state to each track so that an indicator of whether or not a track has been reviewed appears.  Maybe a green checkmark or something in the track list.

Split/join are used in review mode, but not during creation
There should be a way to accept a track as-is without making changes.
Making changes (changing the type) should automatically mark a track as reviewed.
This should persist, so a review can span multiple sessions.
We could even show review progress on the dataset list (next to "Launch annotator" or on the recents page".
Running pipelines immediately puts a dataset into review mode.

I'm thinking this could change the entire interface kinda like google docs editing mode vs comment mode.  The toggle might be up on the toolbar near the save button.
These are just ideas.  No other interface I'm aware of has this sort of review-first interface.

@subdavis the labels include type: question but this seems like a pretty straightforward feature request. Can I remove that label?

If this feature meets a legitimate need for DIVE users, and especially if that gives us a unique edge, then I think we should do it.


chore(main): release 0.122.1

:robot: I have created a release beep boop
0.122.1 (2024-01-21)
Bug Fixes

doc: fix formatting in readme (190b79d)
doc: fix some missed snake_case to camelCase issues (6f588bc)
doc: updating docs on ownerRef and credentials (dcda17b)
owner: check for out of date owner and update (d03de00)
ownerRef: don't try and overwrite owner heritage (f60e514)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/hef/dbman/releases/tag/v0.122.1 :sunflower:


Added the new Availability zones for VPS.

New version of the API 5.7 of TransIP (just minutes ago :))

Stupid PHP 5.6 message from Travis. ;) nothing to worry about

Thanks and sorry for the delay.
https://github.com/hiddeco/transip/releases/tag/v5.7


[Feature request] Hide "Loaded X words from Y" message at each startup

Message "Loaded X words from Y" shows at each startup. Is there any way to hide or disable it ?
Thanks !

I don't see how the message is a problem? It shows for 2 seconds, is in the top right corner and Obsidian is not a program that you constantly restart

Thanks for your reply !
I don't really see the need for this message at each startup (while it seems perfectly fine when it loads the file for the first time).
I have 40+ plugins installed in Obsidian, and I think it's a better practice if each plugin catches user attention only if needed or important. In an ecosystem shared by many plugins, in can quickly get noisy.

Your reasoning does make sense and the message isn't really that useful. Fixed in 476b52cc9cc854a3cd323d42082d6846faae7ef6

Thank you for taking this remark into account !


int range overflow error when using valid range in random:createIntInRange function

Description:

$title
Steps to reproduce:
import ballerina/io;
import ballerina/random;

public function main() returns error? {
    int intResult = check random:createIntInRange(int:MIN_VALUE, int:MAX_VALUE);
    io:println(intResult);
}

I see we doing endRange - startRange in natives.bal file which give this. But I think we need to support the whole int range to give a random number. The documentation also says Generates a random number between the given start(inclusive) and end(exclusive) values.
Affected Versions:
1.5.0-SNAPSHOT
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Would you consider the following modification of the createIntInRange function as a fix for this issue?
public isolated function createIntInRange(int startRange, int endRange) returns int|Error {
    if startRange > endRange {
        return error Error("End range value must be greater than the start range value");
    }
    if startRange == int:MIN_VALUE && endRange == int:MAX_VALUE {
        if createIntInRange(0, 2) == 0 {
            return createIntInRange(startRange, 0);
        }
        else {
            return createIntInRange(0, endRange);
        }
    }
    return <int>(lcg() / m * <decimal>(endRange - startRange - 1) + <decimal>startRange);
}

@Nadeeshan96 can i fix this issue?

👋 Welcome, @vil02 and @Shivamkotalia2002! 🚀
We're thrilled to have you join the Ballerina Lang community! Whether you're a seasoned developer or just starting your journey with Ballerina, we value your contributions and look forward to collaborating with you.
To help you get started, here are some essential resources:

Understanding Ballerina Platform:
Learn what Ballerina is all about: Ballerina Platform
How to Contribute:
Read our contributing guidelines to understand how you can contribute effectively: Contribution Guide
Contributing to the Ballerina library:
If you're interested in contributing to our library, here are the guidelines: Library Contribution Guide
Learn Ballerina:
If you're new to Ballerina or want to enhance your skills, our official website offers a wealth of learning resources: Learn Ballerina
Get Help and Connect:
Join our Discord community to chat with fellow Ballerina enthusiasts and get assistance: Ballerina Discord

Remember, no contribution is too small, and your feedback is invaluable. Feel free to ask questions, propose ideas, or report issues. Together, we can make Ballerina even better!
Happy coding! 🎉

Would you consider the following modification of the createIntInRange function as a fix for this issue?
public isolated function createIntInRange(int startRange, int endRange) returns int|Error {
    if startRange > endRange {
        return error Error("End range value must be greater than the start range value");
    }
    if startRange == int:MIN_VALUE && endRange == int:MAX_VALUE {
        if createIntInRange(0, 2) == 0 {
            return createIntInRange(startRange, 0);
        } else {
            return createIntInRange(0, endRange);
        }
    }
    return <int>(lcg() / m * <decimal>(endRange - startRange - 1) + <decimal>startRange);
}

With this also if you pass the args (int:MIN_VALUE, int:MAX_VALUE) it will give the int range overflow error, because it produce it should produce a value out of integer's range. And the other thing is it needs to be handled for all the possible arguments. For example passing (int:MIN_VALUE + 20, int:MAX_VALUE - 20) should work also. Having a single if condition is not enough. It is also better to produce a uniformly distributed int value with the given range.

@Nadeeshan96
                                                                                import ballerina/io;

import ballerina/random;
public function main() returns error? {
int intResult = check random:createIntInRange(int:MIN_VALUE, int:MAX_VALUE - 1);
io:println(intResult);
}
this code may solve the issue

@Nadeeshan96 can i fix this issue?

@vil02 , @Shivamkotalia2002 Sure! You can fix the issue and send PR to https://github.com/ballerina-platform/module-ballerina-random repository. It is better to add tests along with the fix. Please feel free to raise any issue you come across in the Ballerina Library.

@Nadeeshan96 could you please assign me to this issue?


Remove global flag on regex validation of delegate name.

alexbarnsley requested that I send this PR.
When attempting to register a delegate, there were cases where the regex name validation would flag a valid name as invalid.  This appeared to be tied to multiple calls to the regext.test(....) function with the "g" option enabled on the regex.  Removing the "g" option appears to fix the issue.  Javscript is not my first language but it appears that this type of behavior is not uncommon when using the "g" option due to some sort of state preservation between calls.
Repo Steps:

Open the register delegate dialog
Click in the username edit box and type in a valid username
Press the tab key twice to move focus to the pass phrase edit box. (Note:  The tabs may not be strictly necessary but I observed consistent results with this)
Enter the correct pass phrase
Click the next button

You will either get the error toast saying the delegate username contains an invalid character (which is the false positive) or the checks will pass and the next dialog will appear.  If the bug does not appear, abort to delegate registration and try again until it does.  In my testing I saw about a 50% reproduce rate.
I observed this bug in the 1.5.1 production release as well as latest master branch.

Looks good and fixed the issue for me! Thanks 👍

Hey @ciband can you provide me with your ARK address for you contributing to our monthly Github bounty or contact me in ARK Slack - https://ark.io/slack (username: "boldninja").


There is no ability to set user Id for rewarded ad

For server side validation and giving user a reward it is super helpful to set user id in application, so SSV callback will get user Id and will be able to give reward to specified user.
there is a method in SDK to set it
https://developers.google.com/android/reference/com/google/android/gms/ads/reward/RewardedVideoAd.html#setUserId(java.lang.String)
But there is no RN counterpart for it.
Would be helpful to have one, as it looks like pretty common scenario for rewarded ads.

+1

I'm looking for this

yes, please add this, or is there any work around for this?

Any Updates on this ?


P1017 Server has closed the connection on linux_arm64

Bug description
Intermittently (but very often) a database connection to an aurora serverless postgres instance will fail with
Server has closed the connection.
I am running on both linux_arm64 and linux_x86_64 (debian) containers.
I am ONLY seeing these disconnects when running on linux_arm64.
The linux_arm64 containers are using libquery_engine-linux-arm64-openssl-1.1.x.so.node
The linux_x86_64 containers are using libquery_engine-debian-openssl-1.1.x.so.node
There does not seem to be any rhyme or reason the schema / variety of calls that are made that fail, but they appear to be connections that have been open for random amounts of time and often (but not always) not used for a small period of time.
I've seen findSingle and findMany calls on a resource / table fail intermittently.
Error:
Invalid `db.table.findFirst()` invocation in
/app/build/index.js:34054:34
  34051     }
  34052   });
  34053 }, getValue = async (id) => {
→ 34054   let value = await db.table.findFirst(
Server has closed the connection.
    at pn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:176:6477)
    at pn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:176:5907)
    at pn.request (/app/node_modules/@prisma/client/runtime/library.js:176:5786)
    at /app/node_modules/@prisma/client/runtime/library.js:70:26059
    at t._request (/app/node_modules/@prisma/client/runtime/library.js:179:10484)

At the same time the postgres server is reporting that there are disconnected sessions / connection reset by peer from the client.
2023-05-11 23:52:48 UTC:<IP_ADDRESS>(49478):XXX@XXX:[25972]:LOG: disconnection: session time: 1:04:11.544 user=XXX database=XXX host=<IP_ADDRESS> port=49478
2023-05-11 23:52:48 UTC:<IP_ADDRESS>(56242):[unknown]@[unknown]:[1514]:LOG: could not receive data from client: Connection reset by peer
2023-05-11 23:52:48 UTC:<IP_ADDRESS>(57500):XXX@XXX:[17186]:LOG: disconnection: session time: 2:14:50.294 user=XXX database=XXX host=<IP_ADDRESS> port=57500
2023-05-11 23:52:48 UTC:<IP_ADDRESS>(57528):XXX@XXX:[17189]:LOG: disconnection: session time: 2:14:50.190 user=XXX database=XXX host=<IP_ADDRESS> port=57528
2023-05-11 23:52:51 UTC:<IP_ADDRESS>(57504):XXX@XXX:[17187]:LOG: disconnection: session time: 2:14:53.154 user=XXX database=XXX host=<IP_ADDRESS> port=57504
2023-05-11 23:53:20 UTC:<IP_ADDRESS>(56230):XXX@XXX:[1512]:LOG: could not receive data from client: Connection reset by peer
2023-05-11 23:53:20 UTC:<IP_ADDRESS>(56230):XXX@XXX:[1512]:LOG: disconnection: session time: 0:00:32.129 user=XXX database=XXX host=<IP_ADDRESS> port=56230
2023-05-11 23:53:36 UTC:<IP_ADDRESS>(43924):XXX@XXX:[1594]:LOG: could not receive data from client: Connection reset by peer
2023-05-11 23:53:36 UTC:<IP_ADDRESS>(43924):XXX@XXX:[1594]:LOG: disconnection: session time: 0:00:15.051 user=XXX database=XXX host=<IP_ADDRESS> port=43924
2023-05-11 23:54:42 UTC:<IP_ADDRESS>(56256):XXX@XXX:[1547]:LOG: could not receive data from client: Connection reset by peer
2023-05-11 23:54:42 UTC:<IP_ADDRESS>(56256):XXX@XXX:[1547]:LOG: disconnection: session time: 0:01:45.950 user=XXX database=XXX host=<IP_ADDRESS> port=56256
2023-05-11 23:54:45 UTC:<IP_ADDRESS>(51814):XXX@XXX:[1763]:LOG: could not receive data from client: Connection reset by peer
2023-05-11 23:54:45 UTC:<IP_ADDRESS>(51814):XXX@XXX:[1763]:LOG: disconnection: session time: 0:00:01.678 user=XXX database=XXX host=<IP_ADDRESS> port=51814

It fails more often if I go away for a few seconds (rather than running / refreshing continually).
But from the disconnections log it seems like occasionally the session time is < 2 seconds.
How to reproduce
Run random queries against prisma connection on a host running an linux_arm64 architecture.
They will fail intermittently.
Expected behavior
No response
Prisma information

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["tracing"]
  binaryTargets   = ["native"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

// schema is not relevant as far as i can tell.

An example of one failing call.
const db = new PrismaClient({
  log: [{ emit: 'event', level: 'query', },],
})

const value = await db.table.findFirst({
    where: {
      created_at: {
        gte: new Date(),
      },
      id,
    },
  })

Environment & setup

OS: linux_arm64 container in ECS
Database: RDS Postgres aurora serverless
Node.js version: v16.20.0

Prisma Version
4.13.0

Also observed on 4.10.1

Does this also happen when the tracing preview feature is not enabled?
Do you think this would reproduce when we run a random app with trivial queries on a linux_arm64 container in ECS?

I can give it a shot running without tracing.

Do you think this would reproduce when we run a random app with trivial queries on a linux_arm64 container in ECS?

I would not be surprised if it reproduced (then again I also wouldn't be surprised if it didn't).
I also have on my TODO list to try building the container we're running on linux_arm64 hardware (rather than building on an M1 mac).
I'm using the public ecr image node:16-bullseye-slim image as my base image.
FROM public.ecr.aws/docker/library/node:16-bullseye-slim as base

I'm installing a few other things on it, but the only real relevant one for prisma is openssl:
apt-get install -y openssl

I can give it a shot running without tracing.

I'm not sure if there's anything else I need to do here, but I removed the previewFeatures = ["tracing"] from the prisma file, as well as the dependency on @prisma/instrumentation, and where we registered any instrumentation. Despite this, I'm still was running into the same kinds of errors.

It also reproduces with a trivial example:
prisma/schema.prisma:
generator client {
  provider        = "prisma-client-js"
  binaryTargets   = ["native"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model FooQuery {
  id        String   @id @db.Uuid
  createdAt DateTime @default(now()) @map("created_at")

  @@map("queries")
}

src/index.ts
import { PrismaClient } from '@prisma/client'

const prisma = new PrismaClient({
  log: [{
   emit: 'event',
   level: 'query',
 }],
})

const launchQuery = (prisma: PrismaClient) => {
  const promise = prisma.fooQuery.findMany({
    take: 10
  })

  promise.then((result: any) => {
    // do nothing.
  }).catch((e) => {
    console.log(e)
  })
}

setInterval(function(){
   console.log('calling it ', new Date())
   for (var i = 0; i < 15; i++) {
     launchQuery(prisma)
   }
}, 5000);

package.json and tsconfig.json
package.json
```
{
  "name": "test",
  "private": true,
  "license": "",
  "version": "0.0.1",
  "main": "./build/index.js",
  "types": "./build/index.d.ts",
  "scripts": {
    "build": "yarn build:prisma && yarn build:ts",
    "build:ts": "tsc",
    "build:prisma": "npx prisma generate",
    "clean": "rm -rf build"
  },
  "dependencies": {
    "@prisma/client": "4.13.0",
    "eslint": "8.38.0",
    "tslib": "2.5.0",
    "uuid": "9.0.0"
  },
  "devDependencies": {
    "prisma": "4.13.0",
    "typescript": "5.0.4"
  },
  "type": "module",
  "module": "2020",
  "exports": "./build/index.js"
}
```
tsconfig.json
{
  "include": ["src/index.ts"],
  "compilerOptions": {
    "declaration": true,
    "esModuleInterop": true
    "forceConsistentCasingInFileNames": true
    "isolatedModules": true
    "lib": ["ESNext.AsyncIterable"],
    "module": "ES2020"
    "moduleResolution": "node"
    "outDir": "build",
    "target": "ES2020"
    "skipLibCheck": true,
    "strict": true
    "strictPropertyInitialization": false,
  }
}

# yarn install
... omittted

# yarn build
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (4.13.0 | library) to ./node_modules/@prisma/client in 594ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
```
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
```

# node build/index.js
calling it  2023-05-18T22:10:44.064Z
calling it  2023-05-18T22:10:49.066Z
calling it  2023-05-18T22:10:54.066Z
calling it  2023-05-18T22:10:59.068Z
calling it  2023-05-18T22:11:04.068Z
calling it  2023-05-18T22:11:09.073Z
calling it  2023-05-18T22:11:14.074Z
PrismaClientKnownRequestError:
Invalid `prisma.fooQuery.findMany()` invocation:

Server has closed the connection.
    at pn.handleRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:6477)
    at pn.handleAndLogRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5907)
    at pn.request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5786)
    at async t._request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:179:10484) {
  code: 'P1017',
  clientVersion: '4.13.0',
  meta: null
}
PrismaClientKnownRequestError:
Invalid `prisma.fooQuery.findMany()` invocation:

Server has closed the connection.
    at pn.handleRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:6477)
    at pn.handleAndLogRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5907)
    at pn.request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5786)
    at async t._request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:179:10484) {
  code: 'P1017',
  clientVersion: '4.13.0',
  meta: null
}
^C

Managed to reproduce with a trivial database / schema newly generated from RDS with aurora postgres.
test=>CREATE TABLE QUERIES (id UUID, created_at timestamp);
CREATE TABLE
test=> \dt
          List of relations
 Schema |  Name   | Type  |  Owner
--------+---------+-------+----------
 public | queries | table | postgres
(1 row)

test=> \d queries
                          Table "public.queries"
   Column   |            Type             | Collation | Nullable | Default
------------+-----------------------------+-----------+----------+---------
 id         | uuid                        |           |          |
 created_at | timestamp without time zone |           |          |

test=>INSERT INTO QUERIES VALUES ('a791356e-72fe-4b90-9282-4cac4f30a2f4', '2023-05-19 18:28:19.238487'),
 ('9287b6a5-f9ee-434a-9df2-d72771c6e64d', '2023-05-19 18:28:20.387501'),
 ('e572db4c-db10-48ae-976d-06b7528c329f', '2023-05-19 18:28:20.931351'),
 ('e4b05ebd-bf33-4ac0-bc0c-01f029e6e031', '2023-05-19 18:28:21.398429'),
 ('907a8441-cee7-4b8e-a1bb-dc35cfb0dc4e', '2023-05-19 18:28:21.871213'),
 ('62628b8f-c88b-4bbe-a205-3e0d65bad60f', '2023-05-19 18:28:22.458357'),
 ('a7dc1d79-4e7a-4c31-b265-5afe79eb17df', '2023-05-19 18:28:23.405305'),
 ('52b89ad7-15cf-49d8-820a-c050fa62b78c', '2023-05-19 18:28:23.994473'),
 ('f73168be-aa80-48d2-bd48-8fa4970377c4', '2023-05-19 18:28:24.522251'),
 ('c3363a99-ca88-4310-9bb9-45337bc1e275', '2023-05-19 18:28:25.05747'),
 ('56050541-0b7b-4e89-a4ae-5c8fb3231b47', '2023-05-19 18:28:25.557365'),
 ('8e778a4a-fbd6-4b97-8aba-4ac0f2882ce6', '2023-05-19 18:28:26.096332'),
 ('777fafcd-2ddd-484a-b393-754c1c09e17c', '2023-05-19 18:28:26.62346'),
 ('6634bf9f-b0bc-4f62-9408-cf302616b58a', '2023-05-19 18:28:27.117248');
INSERT 0 14

Every time I ran the test scripts above it failed in a few rounds.
Occasionally it failed in the first iteration and had a different error message:
PrismaClientKnownRequestError:
Invalid `prisma.fooQuery.findMany()` invocation:

Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:, error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733: (unable to get local issuer certificate)
    at pn.handleRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:6477)
    at pn.handleAndLogRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5907)
    at pn.request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5786)
    at async t._request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:179:10484) {
  code: 'P1011',
  clientVersion: '4.13.0',
  meta: {
    message: 'error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:, error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733: (unable to get local issuer certificate)'
  }
}

and
Can't reach database server at `<hostname>`:`5432`

Please make sure your database server is running at `<hostname>`:`5432`.
    at pn.handleRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:6477)
    at pn.handleAndLogRequestError (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5907)
    at pn.request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:176:5786)
    at async t._request (/app/test_prisma_two/node_modules/@prisma/client/runtime/library.js:179:10484) {
  code: 'P1001',
  clientVersion: '4.13.0',
  meta: {
    database_host: '<hostname>',
    database_port: 5432
  }
}

Notably in both of these cases it DID connect with the same credentials in later iterations of the same execution.

Then to confirm it was only related to aurora postgres, I did the same schema / on a standard (non-aurora) RDS postgres and it did NOT reproduce after ~100 iterations (and I gave up and stopped it).

It does appear to be SSL related. When my database_url environment variable has sslmode=verify-full it fails relatively quickly.
However, with sslmode=disable it does not fail.

Hey everyone! We've just fixed another issue that is very likely to have had the same root cause as this one. Could you please check if using the dev build of Prisma and Prisma Client version 5.3.0-integration-arm-openssl-5-2-0.1 fixes this issue for you? (Make sure to install it as an exact dependency, i.e., without ^ before the package version in package.json, otherwise you might get a different integration build that doesn't include this fix).

@aqrln do you think this dev build will also fix the following, or is it unrelated?:
PrismaClientKnownRequestError:
Invalid `prisma.user.findMany()` invocation:

Error opening a TLS connection: OpenSSL error (self signed certificate in certificate chain)
    at cg.handleRequestError (node_modules/@prisma/client/runtime/binary.js:181:6732)
    at cg.handleAndLogRequestError (node_modules/@prisma/client/runtime/binary.js:181:6120)
    at cg.request (node_modules/@prisma/client/runtime/binary.js:181:5840)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async a (node_modules/@prisma/client/runtime/binary.js:186:9778)
  code: 'P1011',
  clientVersion: '5.2.0',
  meta: {
    message: 'OpenSSL error (self signed certificate in certificate chain)'
  }
}

@aqrln As far as I can tell, version 5.3.0-integration-arm-openssl-5-2-0.1 fixes what I was seeing.
I have not tried the above isolated reproductions I provided before, but I was unable to get it to fail after deploying my full application with the above version and re-enabling SSL.
And just to verify, I swapped back to the original version we were using along with re-enabling ssl and it failed in the same way that it used to.
So seems like this is 👍🏻

@khalilsarwari

do you think this dev build will also fix the following issue which seems to happen randomly/inconsistently, or is it unrelated?

Since the error originates from the query engine, it's quite possible, but hard to tell for sure without testing. If the error is wrong (i.e. you're not actually using self-signed certificates) and only happens intermittently, then it's may likely be fixed as well. Generally, the problem we fixed could've triggered many kinds of subtle bugs, although for most affected people it just caused segfaults and aborts, incorrect behaviour without crashing is a bit more rare.
If you could test whether using Prisma and Prisma Client version 5.3.0-dev.42 or 5.3.0-integration-arm-openssl-5-2-0.1 (the second one is identical to 5.2.0 but includes this fix) fixes this problem for you, that would be great. Alternatively, you can wait until 5.3.0 is released and try it. If it doesn't fix this specific bug, please open a new issue so we could reproduce and investigate it!

I have tried 5.3.0-integration-arm-openssl-5-2-0.1 for the past day, and the intermittent self-signed issue has not appeared - so far so good; I'll follow up if it returns!


Custom welcome message

Rasa Core version: 0.8.5
Python version: 3.6
Operating system (windows, osx, ...): Ubuntu 16
Issue: Users often request the bot to utter something on startup, instead of being presented with an empty input. rasa-core actually provides a welcome message but it is hard-coded in console.py: "Bot loaded. Type a message and press enter: "
Would it be possible to make this message configurable?
The solution I've found is overwriting the method, but that is a lot of code to change just one element in the method:
...
from rasa_core.channels.console import *
class MyConsoleInputChannel(ConsoleInputChannel):
    def _record_messages(self, on_message, max_message_limit=None):
        utils.print_color("Hallo, ich bin ein ChatBot.",utils.bcolors.OKBLUE)
        num_messages = 0
        while max_message_limit is None or num_messages < max_message_limit:
            text = input().strip()
            if six.PY2:
                # in python 2 input doesn't return unicode values
                text = text.decode("utf-8")
            if text == INTENT_MESSAGE_PREFIX + 'stop':
                return
            on_message(UserMessage(text, ConsoleOutputChannel(),
                                self.sender_id))
        num_messages += 1
...

How to do it with rocket.chat

Many thanks for your answer. I was wondering if my workoaround would work for other channels.
This seems to be a challenge for most chatbot frameworks (the MS bot framework has trouble with producing a welcome message, too). Yet our users say they are disoriented by an empty input in the messenger-like GUI frontend. Would you have an advice for making a story like this work?:
## a story example
    - bot_utter_greet
* start
    - utter_what_can_i_do_for_you

i.e. the bot would utter something defined in the domain as soon as the channel is opened

does this work on rasa-x ui?

I know this is closed but I am still interested: is it possible to make a bot to send a greeting message on a startup when using rasa shell?
(same question raised here: https://forum.rasa.com/t/custom-welcome-message/12729/4)


Report errors correctly by invalidating super set of affected files

Fixes #24986
The issue reported was with the graph a -> b -> c
When change was made c, the declaration file for b doesnt change (it still remains import {C}from "./c" export class B{ c: C}). From emit persepctive file a.ts doesnt need to be emitted (since its not part of affected files by that change) and without deleting errors for a.ts we wont see new error.
With this change, whenever change in declaration file for c happens, we not only delete errors for b.ts, we will delete errors for a.ts (since it references b.ts) and any file that will reference a.ts as well. This will hamper the performance in scenarios where errors didnt change (eg if a.ts never referenced b.c.d property) but finding out such dependencies would be costlier than re-generating errors.

Do we need to do anything here? is there a better way to detect cases where these transitive dependencies lead to invalidation? seems like most of the time transitive dependencies do not introduce errors. seems like this is a drastic change..


Adds an all tests suite to easily run all associated project tests (w…

…ill need this for CI)
First steps to CI (but also handy as a user to click on the all tests orb to run everything in the IDE - we might consider adding an all tests in the Exercises project for users - but didn't want to confuse things for now)

Also handy for devs. The test runner could also do it too, but this would be just that extra bit convenient for testing everything Exercism.


Test Suite

There needs to be a suite of e2e using Spectron. Also, plan unit tests.

Basic Integration and test for some components are done.
Paused the work because of db mocks for component fails.


Support for Stream

It is possible that implement Stream in ts?
I wrote a demo:
import {pipe} from 'fp-ts/function';
import {fold, Option} from 'fp-ts/Option';

export interface Cons<A> {
  head: () => A;
  tail: () => Stream<A>;
  readonly _tag: 'Cons';
}

export interface Empty<A> {
  readonly _tag: 'Empty';
}

export type Stream<A> = Cons<A> | Empty<A>;

export const cons = <A>(head: () => A, tail: () => Stream<A>): Cons<A> => ({
  head,
  tail,
  _tag: 'Cons',
});

export const empty: Empty<unknown> = {
  _tag: 'Empty',
};

export const foldRight = <A, B>(z: B, f: (a: A, b: () => B) => B) => (
  s: Stream<A>
): B => {
  switch (s._tag) {
    case 'Cons':
      return f(s.head(), () => foldRight(z, f)(s.tail()));
    case 'Empty':
      return z;
  }
};

export const exist = <A>(p: (a: A) => boolean) => (s: Stream<A>): boolean =>
  pipe(
    s,
    foldRight(false as boolean, (a, b) => p(a) || b())
  );

export const stream = <A>(...as: ReadonlyArray<A>): Stream<A> => {
  if (as.length === 0) {
    return empty;
  }
  const [head, ...tails] = as;
  return cons(
    () => head,
    () => stream(...tails)
  );
};

export const unfold = <A, S>(z: S, f: (z: S) => Option<[A, S]>): Stream<A> =>
  pipe(
    f(z),
    fold(
      () => empty as Stream<A>,
      ([a, z1]) =>
        cons(
          () => a,
          () => unfold(z1, f)
        )
    )
  );

export const take = (n: number) => <A>(s: Stream<A>): Stream<A> => {
  switch (s._tag) {
    case 'Empty':
      return s;
    case 'Cons':
      if (n == 1) {
        return cons(s.head, () => empty as Empty<A>);
      } else {
        return cons(s.head, () => take(n - 1)(s.tail()));
      }
  }
};

export const toArray = <A>(s: Stream<A>): ReadonlyArray<A> => {
  switch (s._tag) {
    case 'Empty':
      return [];
    case 'Cons':
      return [s.head(), ...toArray(s.tail())];
  }
};

And this is the test:
import {exist, stream, take, toArray, unfold} from './index';
import {pipe} from 'fp-ts/function';
import {none, some} from 'fp-ts/Option';

describe('exist', () => {
  it('should be lazy', function () {
    const evaluated: number[] = [];
    const result = pipe(
      stream(1, 2, -1, 3, 4),
      exist(a => {
        evaluated.push(a);
        return a < 0;
      })
    );
    expect(result).toEqual(true);
    expect(evaluated).toEqual([1, 2, -1]);
  });
});

describe('should take and unfold  be lazy', () => {
  const evaluated: number[] = [];

  const stream = unfold(1, n => {
    evaluated.push(n);
    return n < 10 ? some([n, n + 1]) : none;
  });

  const as = pipe(stream, take(3), toArray);

  expect(as).toEqual([1, 2, 3]);
  expect(evaluated).toEqual([1, 2, 3]);
});

Stream is useful for lazy evaluation.
If is ok to add it to fp-ts, I am happy to make a MR to branch v3.0.0(give me a chance ,pls :) )

If we can get this as a stack safe operation its more likely to be considered

If we can get this as a stack safe operation its more likely to be considered

it's honestly very hard to do stack safe with decent performance, given the rest of the data types present I don't think it will be in-scope, maybe an observable like impl


monster-card.js?v=1:112:7 TypeError: this.lastChild.setConfig is not a function

Hi there,
I am getting this error running the latest version of monster-card.js on Home Assistant 0.84.6.
I have tried loading the page on Chrome and Firefox but get the same error. Here is my config:
- title: Packages
  cards:
    - type: custom:monster-card
      card:
        type: entites
        title: Packages
      filter:
        include:
          - domain: light
            state: 'on'

card has moved: https://github.com/custom-cards/monster-card


Error on installing

Hi, my PHP version is 8.03. And during composer install I am getting a lot of error messages, like this:
Problem 13
    - doctrine/inflector v1.3.0 requires php ^7.1 -> your php version (8.0.3) does not satisfy that requirement.
    - laravel/framework v5.1.46 requires doctrine/inflector ~1.0 -> satisfiable by doctrine/inflector[v1.3.0].
    - laravel/framework is locked to version v5.1.46 and an update of this package was not requested.

How can I install using my PHP version?

I am getting the same errors  .

easy solution to use php version 7.1 on ubuntu 20.4 it works like the instruction says  :)


Unflat files will loose keys on special conditions

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
Having some translation keys like

top.middle
top.middle.last1
top.middle.last2

will create three corresponding entries in the translation files:
{
  "top.middle" : "a";
  "top.middle.last1" : "b";
  "top.middle.last2" : "c";
}

If you chose to use unflat files by setting the config to unflat: true this will be converted either to
{
  "top": {
    "middle": "a"
  }
}

or
{
  "top": {
    "middle": {
      "last1": "b",
      "last2": "c"
    }
  }
}

depending on the order of processing the keys and thus leading to a loss of information. This behavior is mainly related to the used lib flat. So in the current implementation the feature "unflat" can be very dangerous as the user won't notice that loss of keys because there is neither an error/warning output during key extraction nor a warning in the documentation.
Expected behavior
It has to be decided if the current behavior can be fixed by either trying to get a fix on the flat lib or by introducing some sort of preprocessor for unflat files to amend the keys so that flat will behave correctly. That preprocessor would detect such cases and modify a list of extracted keys like
{
  …
  "top.middle" : "a",
  "top.middle.last1" : "b",
  "top.middle.last2" : "c",
  …
}

to
{
  …
  "top.middle._" : "a",
  "top.middle.last1" : "b",
  "top.middle.last2" : "c",
  …
}

Then during reading those files back in the reverse processing has to be applied. This is just some sketchy idea and is meant as start of discussion on that topic.

@darkv I think that we will add appropriate information to the documentation. would you like to make the PR?

Published in v2.0.3, @darkv great job and thanks for the contribution 🚀


Downloads the whole hf repo

The scripts/download.py downloads the whole hf repo including the *.safetensors files, even though it seems only the *.bin files are required.

It usually a bad practice for repo creator to make multiple copies of the same file just different serialization format, like .bin and .safetensor.
usually, hf transformer perfers .safetensor format becuase loading .bin could lead to executing harmful code if .bin is hacked.
The hf transformer provides python inferface for downloading specific formats from hf repo, but I don't think this project use that interface


[ci] raise floors on CI dependencies

Contributes to #6350.
This PR proposes using stricter dependency requirements when creating conda environments in CI.

= {major}.{minor}.* pins in Python 3.7 jobs, for faster solves and to limit the risk of stuff like #6370
>= floors in Python 3.8+ jobs, for faster solves

And some other changes to env creation:

switches from matplotlib to the lighterweight matplotlib-base for all jobs
removes -q in conda create calls, so we can see in logs what packages get pulled in (it's not that many log lines)
moving those lists of requirements out of testing scripts and into files that can be passed to conda create

simplifies the testing scripts, and allows those environment files to be re-used in local development

Notes for Reviewers
How this helps with local development
I'm envisioning that for local development, we could (in a follow-up PR) encourage a pattern like this for creating a local dev environment:
conda create \
    --name lgb-dev \
    --yes \
    --file ./.ci/conda-envs/ci-core.txt \
    --file ./.ci/conda-envs/dev.txt \
    python=3.11

Where dev.txt might contain things like mypy, ruff, and pre-commit.
Why are these .txt files and not conda .yaml files?
conda create cannot read conda YAML files, it expects stuff like these .txt files. You can see that in the docs for conda list (which produces requirement lists like these .txt files).
https://github.com/conda/conda/blob/29f5f3192b519cf94c314dbfb442ad974b0a4232/conda/cli/main_list.py#L90
And I wanted to be able to pass in the Python constraint from the command line, which conda env create (the command that can read YAML files) doesn't support.
So did this make things faster?
Yes 🔥
Especially on AppVeyor. On master, building one commit has been taking 45-85 minutes. On this branch, it's taking more like 35-45 minutes.
See https://ci.appveyor.com/project/guolinke/lightgbm/history
On Azure DevOps and GitHub Actions, it looks to me like the speedup is not quite so noticeable, but at a minimum this doesn't seem to make any builds slower.
References

https://stackoverflow.com/questions/71393065/can-i-make-conda-solve-this-environment-faster

Seems like keeping support for Python 3.7 has become too much of a maintenance burden. I'd be ok to drop it if you want

Python 3.7 reached EOL on June 27, 2023 (cf. https://devguide.python.org/versions/), I think it's reasonable to drop it 😅

Seems like keeping support for Python 3.7 has become too much of a maintenance burden. I'd be ok to drop it if you want

This PR and that CI blockage wasn't too bad.
I think we should do one more release with Python 3.7 support and include a note in the release notes that it'll be the last one to support Python 3.7. So I think this PR should be merged as-is.
And when I say "last one to support Python 3.7".... I'd support that being a "soft" drop.

bumping to python-requires >= 3.7 in the package metadata (so "hard" dropping Python 3.6)
running the https://github.com/microsoft/LightGBM/blob/master/.ci/test-python-oldest.sh tests in a Python 3.7 environment
allowing code that would not be syntactically-valid Python 3.6 to make it onto master

And then only move to python-requires >= 3.8 if there is a compelling reason, like new language features.

Python 3.7 reached EOL on June 27, 2023 ...  I think it's reasonable to drop it 😅

That's a good piece of evidence but not the only one I think we should consider when contemplating which versions of Python LightGBM supports. I think at least 2 of these should be true before we drop support:

the version is end-of-life
the maintenance burden of supporting the version is prohibitively high
supporting that version is preventing LightGBM from adding some sufficiently-valuable new functionality

I still support working that way moving forward, to try to support users in constrained environments where it's difficult to update Python versions. So, for example, I don't think LightGBM should drop Python 3.8 support immediately when it reaches end-of-life later this year.
Some relevant prior discussions:

https://github.com/microsoft/LightGBM/pull/5765#issuecomment-1454861675
https://github.com/microsoft/LightGBM/pull/5006#issuecomment-1039464720


[Bug] Error: Cannot find module '../build_info'

Describe the Bug
After installing BBD with bdctl discord, fails to start. Only on my laptop, however.
To Reproduce

betterdiscordctl uninstall
rm -rf /home/fichte/.config/discord/0.0.9
start discord once to have it fetch its modules

~ $ betterdiscordctl install -b /usr/lib/betterdiscord-rauenzi-git -v -v
VV: Scanning /opt
VV: Trying flavor ''
V: Using Discord at /opt/discord
V: Found modules in /home/fichte/.config/discord/0.0.9/modules
V: Injecting into index.js...
V: Linking BetterDiscord injector...
Installed. (Restart Discord if necessary.)

restart discord

Screenshots

Discord Version
~ ¬ pacman -Qs discord
local/betterdiscord-rauenzi-git 0.3.2.r13.g2123673-1
    Discord extension with plugin support, emotes, and more (rauenzi's updated fork)
local/betterdiscordctl-git 1.6.1.r35.g5f13ec2-1
    A utility for managing BetterDiscord on Linux
local/discord 0.0.9-4
    All-in-one voice and text chat for gamers that's free and secure.

Well, that's embarassing. I was confident I was running the latest version because I checked this like 2 weeks ago where it didn't work, but looks like it has been fixed since. Works with 0.3.2.r14.g1434e53-1.


chore: update changelog for 0.5.0 release

Updates our tracked changelog with changes reported from our
dynamic changelog.
https://github.com/ansible/vscode-ansible/releases/tag/untagged-a512ae8fd13c82aa9e96

@ganeshrn this is exactly why I've been pushing for the proper change notes. Because it's hard to manage this at some point in time far in the future but it's still desirable to make it look good, consistent, useful.

@webknjaz I agree there are some good inputs in the links you shared. I suggest you create a PR to outline the development process that details steps/things to take care of while submitting the PR (with link to appropriate docs) to set the right expectations for contributors and start enforcing the guidelines more strictly after we have a consensus among active contributors. But till such time I am not of the opinion that we should block the release on how the changelogs are worded. I do think we can take an iterative approach to streamline the development and release process.

LGTM


[Request]: Beyond Compare v5 Beta

Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] English interface (or at least English documentation)
[X] Alternative, forked or prerelease version of an existing package
[X] Fairly standard install (e.g. no elaborate pre/post install scripts)

Name
beyondcompare
Description
Directory and file compare functions in one package
Homepage
https://www.scootersoftware.com/beta
Download Link(s)
https://www.scootersoftware.com/files/BCompare-<IP_ADDRESS>643.exe
Corresponding package
extras/beyondcompare
Some Indication of Popularity/Repute
The installation can be done using the following command:
./BCompare-<IP_ADDRESS>643.exe /PORTABLE /VERYSILENT /DIR=$env:USERPROFILE/beyondcompare5

Just worked on my machine like a charm as well, thx @nagromc !

    me@localhost MINGW64 ~
    $ scoop bucket add nagromc https://github.com/nagromc/scoop-bucket
    Checking repo... OK
    The nagromc bucket was added successfully.

    me@localhost MINGW64 ~
    $ scoop install nagromc/beyondcompare
    Installing 'beyondcompare' (<IP_ADDRESS>727) [64bit] from 'nagromc' bucket
    BCompare-<IP_ADDRESS>727.exe (25,5 MB) [===================================================================================================================] 100%
    Checking hash of BCompare-<IP_ADDRESS>727.exe ... ok.
    Running installer... done.
    Linking ~\scoop\apps\beyondcompare\current => ~\scoop\apps\beyondcompare\<IP_ADDRESS>727
    Creating shim for 'BComp'.
    Creating shim for 'BComp'.
    Making C:\Users\me\scoop\shims\bcomp.exe a GUI binary.
    Creating shim for 'BCompare'.
    Making C:\Users\me\scoop\shims\bcompare.exe a GUI binary.
    Creating shortcut for Beyond Compare 5 Beta (BCompare.exe)
    'beyondcompare' (<IP_ADDRESS>727) was installed successfully!

    me@localhost MINGW64 ~
    $

Thanks for your suggestion @basejumpa
Well, I thought about it, but it seems the place for non-stable software is in the versions bucket. From its README:

For alpha, beta, nightly, dev, canary, insiders, release candidates, and frozen/older versions of app manifests.

And BC5 is considered as beta, and recently as release candidate.


Uchiwa Datacenter config

I am trying to setup the datacenter variable, and correct me if I am wrong but managing the datacenter from https://github.com/sensu/uchiwa/blob/master/config.json.example#L4 imho is not the best way once we have custom data configured on each node.
Is it possible to Open an issue to get it from the custom variables?

Hi,
Is there a way to filter servers on uchiwa based on custom variables

the request from hkhelil would be nice indeedddd


About cherry-pick automatically

Which part is this question about

every day, @alamb should cherry pick some pull request to the active_release branch automatically.
I have a question about what kind of pull request should be cherry pick?
Describe your question
A clear and concise description of what the question is.
Additional context
Add any other context about the problem here.

Hi @liukun4515  -- the process I am following is documented here: https://github.com/apache/arrow-rs/blob/master/dev/release/README.md#backporting
Specifically I try to cherry-pick everything that is "backwards compatible" (in the rust Semantic Versioning sense that someone upgrading from 6.1.0 to 6.2.0 would not have to change any of their code).
Does that answer your question?

thank you for your reply.


Create kglc-workflow.md

I made minor tweaks, hope that is ok.

of course, thanks!

Remember this goes out to the Mondo user community. They don't care about KGCL neither what it is, nor anything else. They just care that you can magically add a synonym using a commend in a github issue.
I read through the instructions, I would have liked to

avoid use of the word "KGCL" (both in the title and the filename)
Use a concrete ID from a Mondo class adding a concrete synonym (one that already exists, does no matter)

If you feel though @nicolevasilevsky it is good as is, we can send it to the list, but it seems a bit too technical to me atm.

I didn't know this was meant to be user facing documentation.
Do we want users to obsolete terms? I understand that this will be done on a PR, but we need to add terms to the obsoletion list and leave an issue open for 2 months before we obsolete a term, so I don't think this would be a good workflow for users to use (but we (curators) could use it.
I am going to test this out.


Maths / Inline Maths / Pseudocode all in display mode.

All katex is currently transformed under display mode, which is the correct behaviour for code blocks, but it isn't the correct behaviour for inline maths in a paragraph (visually breaks the paragraph) or for pseudocode (not sure how to describe buggy output)

Finished with commt https://github.com/j-kitch/post/commit/5f665a0649e4fcfe029048cbb3445029c0fecbc6


chore: release main

:robot: I have created a release beep boop
perf: 1.0.0
1.0.0 (2023-05-24)
Features

adding Performance class (5b806fd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aversini/node-cli/releases/tag/perf-v1.0.0 :sunflower:


Npn notebook

I added three notebooks for npn, daymet, and ppo. The notebooks still can be improved. Specially the daymet one is not complete since I had some problem with dask and xarray installation. I decided to push what I have and then try to solve the problem.

Oops, I tried to fix a merge conflict but messed up this branch. Opened a new PR in #74 to clean things up. Will merge that one instead.


Why are cheat-sheets folders empty

@question After watching your YouTube videos, I came here to find the corresponding documentation, only to find that most of the folders were empty. Your videos indicate that we don't need to write everything down because it will be documented, but when I click on the links, it brings me to empty folders. Is this a short-term thing while you migrate to a new structure, or what is happening? Also, while in transition it would be helpful if you marked each folder name with tags like _WIP, _ToBeUpdated, or some indication that showed which folders contain content vs. just being empty.

Thanks for the heads-up. The plan is to add at least one item into every folder as soon as possible, and in the future only create them when there is something to fill in. I'll take a look.


[Bug]: Type Conflict When Using AppleSettings  in Geolocator Plugin for iOS or location settings

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

[ ] Android
[X] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Steps to reproduce
Implement location tracking using the Geolocator plugin in a Flutter app.
Create functions _getCurrentLocationForIOS and _enableLocationUpdatesForIOS using AppleSettings for iOS.
Call these functions on an iOS device to get the current location and enable continuous location updates.
Observe the type conflict and other errors during runtime.
Expected results
Example: The application should retrieve the current location and enable continuous location updates on iOS devices without any type conflicts or runtime errors.
Actual results
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: The operation couldn’t be completed. (kCLErrorDomain error 1.)
#0      GeolocatorApple.getPositionStream. (package:geolocator_apple/src/geolocator_apple.dart:188:9)
#1      Stream.handleError. (dart:async/stream.dart:931:16)
#2      _HandleErrorStream._handleError (dart:async/stream_pipe.dart:269:17)
#3      _ForwardingStreamSubscription._handleError (dart:async/stream_pipe.dart:157:13)
#4      _RootZone.runBinaryGuarded (dart:async/zone.dart:1606:10)
#5      _BufferingStreamSubscription._sendError.sendError (dart:async/stream_impl.dart:384:15)
#6      _BufferingStreamSubscription._sendError (dart:async/stream_impl.dart:402:7)
#7      _BufferingStreamSubscription._addError (dart:async/stream_impl.dart:306:7)
#8      _ForwardingStreamSubscription._addError (dart:async/stream_pipe.dart:128:11)
#9      _ForwardingStream._handleError (dart:async/stream_pipe.dart:95:10)
#10     _ForwardingStream<…>
The application encounters a type conflict and crashes with the error: Unhandled Exception: type '(Position) => Null' is not a subtype of type '((Position) => void)?'. The issue appears when using AppleSettings for iOS in the Geolocator plugin. also when the setting location is on alway or while using the app the location puck shows the first time and disappears and gives this error
Code sample
Code sample
[Paste your code here]
 Future<void> _getCurrentLocationForIOS() async {
  try {
    final geolocator.AppleSettings appleLocationSettings = geolocator.AppleSettings(
      accuracy: geolocator.LocationAccuracy.bestForNavigation,
      activityType: geolocator.ActivityType.fitness,
      distanceFilter: 100, // Adjust according to your needs
      pauseLocationUpdatesAutomatically: false,
      showBackgroundLocationIndicator: true,
      allowBackgroundLocationUpdates: true,
    );

    _currentPosition = await geolocator.Geolocator.getCurrentPosition(
      locationSettings: appleLocationSettings,
    );

    if (!mounted) return;

    _mapboxMap.flyTo(
      _getCameraOptions(_currentPosition),
      MapAnimationOptions(duration: 1000),
    );

    _updateLocationPuck();
  } catch (e) {
    print("Error getting current location on iOS: $e");
    // Handle the error, for example, by showing an alert to the user.
  }
}

void _enableLocationUpdatesForIOS() {
  final geolocator.AppleSettings appleLocationSettings = geolocator.AppleSettings(
    accuracy: geolocator.LocationAccuracy.bestForNavigation,
    activityType: geolocator.ActivityType.fitness,
    distanceFilter: 100, // Adjust according to your needs
    pauseLocationUpdatesAutomatically:false,
    showBackgroundLocationIndicator: true,
    allowBackgroundLocationUpdates: true,
  );

  geolocator.Geolocator.getPositionStream(
    locationSettings: appleLocationSettings,
  ).listen((geolocator.Position position) {
    if (!mounted) return;

    setState(() {
      _currentPosition = position;
      _updateLocationPuck();
    });
  });
}

### Screenshots or video

Screenshots or video demonstration
![Simulator Screenshot - iPhone 15 Pro Max - 2024-08-26 at 14 15 14](https://github.com/user-attachments/assets/bc673bf0-76d0-4072-b967-49365b1c90d6)
![simulator_screenshot_3ECC9736-6D9E-4689-A413-3E1DB2F26FFC](https://github.com/user-attachments/assets/424bd4d5-6e32-42bd-8776-1240dd1c465f)

[Upload media here]

### Version

13.0.1

### Flutter Doctor output

Doctor output

 flutter doctor -v
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.6.1 23G93 darwin-x64, locale
    en-US)
    • Flutter version 3.22.2 on channel stable at
      /Users/aditiallady/devlopment/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 761747bfc5 (3 months ago), 2024-06-05 22:15:13 +0200
    • Engine revision edd8546116
    • Dart version 3.4.3
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/aditiallady/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.10+0-17.0.10b1087.21-11572160)

[✓] VS Code (version 1.92.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.94.0

[✓] Connected device (4 available)
    • Aditi’s iPhone (mobile)    • 00008130-000E21A004298D3A            • ios
      • iOS 17.5.1 21F90
    • iPhone 15 Pro Max (mobile) • 1F14C548-F714-4573-8B73-4DA1E72B59A1 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-17-5 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • macOS 14.6.1 23G93 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 128.0.6613.84

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Future _getCurrentLocation() async {
_currentPosition = await geolocator.Geolocator.getCurrentPosition(
locationSettings: const geolocator.LocationSettings(
accuracy: geolocator.LocationAccuracy.high));
if (!mounted) return;
//_initialCameraOptions = _getCameraOptions(_currentPosition);
_mapboxMap.flyTo(_getCameraOptions(_currentPosition),
    MapAnimationOptions(duration: 1000));
_updateLocationPuck();

}
void _enableLocationUpdates() {
geolocator.Geolocator.getPositionStream(
locationSettings: const geolocator.LocationSettings(
accuracy: geolocator.LocationAccuracy.high))
.listen((geolocator.Position position) {
if (!mounted) return;
  setState(() {
    _currentPosition = position;
    _updateLocationPuck();
  });
});

} used this code works in android but returns the error above what should i do really need help please?


Closes #81 | Create dataset loader for MTOP

Closes #81.
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

thank you for the PR. MTOP has multiple tasks (not only intent classification). Do you mind giving a more specific name for the dataset? (e.g., mtop_intent).

The dataset in question includes mtop_domain and mtop_intent subsets, which are the same task but with different labels of intent. The paper suggests that multiple tasks can be done, but the HF link for this dataset card only contains the intent_classification task. We might need to update the dataset card as the HF dataset doesn't seem to refer to the MTOP paper.
In my opinion, the HF Dataset is more aligned with the original MTOP dataset, rather than the mentioned HF links that only create a derivative of it.
wdyt, @SamuelCahyawijaya @holylovenia @gentaiscool?

I think none of the HuggingFace URLs are provided by the original authors. The original authors merely provided a direct link to the data in the paper.
Is there any consistency problem(s) (e.g., different data sizes, different pairs, etc.) you found regarding the URLs that we use? @sabilmakbar @elyanah-aco
https://huggingface.co/datasets/mteb/mtop_domain
https://huggingface.co/datasets/mteb/mtop_intent
If not, the dataloader as implemented should be fine if it works well. I'll continue reviewing this soon.

I think none of the HuggingFace URLs are provided by the original authors. The original authors merely provided a direct link to the data in the paper.

Yeah, but the latter HF link (this one) cites the MTOP paper and possibly has more variation of tasks than intent classification.
Perhaps the issue lies in these two datasets being a derivative dataset of MTOP instead of the original MTOP dataset, which I agree with @gentaiscool's suggestion to rename this dataset to MTOP Intent Classification.
However, I think the two HF links are quite aligned based on a few examples that I saw, and the _intent subset is more specific than the _domain subset on its label.

Going by the datasheet, the dataloader is supposed to cater for 2 subsets: domain and intent.
cc: @sabilmakbar @gentaiscool @elyanah-aco

However, I think the two HF links are quite aligned based on a few examples that I saw, and the _intent subset is more specific than the _domain subset on its label.

Yes, this seems to be the case when I worked on this. Each domain can have multiple intent types, although the domain-intent mappings aren't available in the HF links.

@holylovenia Renamed dataset to mtop_intent_classification but for some reason, changing mtop.py to mtop_intent_classification.py gives FileNotFoundError: No such file or directory error when running seacrowd_text schema. It works for source schema though. Any possible reasons for this?
Also, do I need to add config to load all subsets as once?

@holylovenia Renamed dataset to mtop_intent_classification but for some reason, changing mtop.py to mtop_intent_classification.py gives FileNotFoundError: No such file or directory error when running seacrowd_text schema. It works for source schema though. Any possible reasons for this?

For this, I can help debugging

Also, do I need to add config to load all subsets as once?
Nope, it's okay as it is.

@holylovenia Renamed dataset to mtop_intent_classification but for some reason, changing mtop.py to mtop_intent_classification.py gives FileNotFoundError: No such file or directory error when running seacrowd_text schema. It works for source schema though. Any possible reasons for this?

Thanks for the changes, @elyanah-aco!! Tried and tested. The dataloader looks good to me. I'm not sure why you said it throws an error when you change the file name to mtop_intent_classification.py, because I tried using that file name and everything ran as it should. If you encounter a similar problem as @elyanah-aco, please let me know @sabilmakbar.

After testing this, it works too on my end. Perhaps you're on the wrong dir when executing the test suite or using the wrong args back then?


Dependency update with Dependabot

Background
Dependabot provides Automated dependency updates for  go ,  docker , and   GitHub actions.
Security updates
Dependabot security updates make it easier for you to fix vulnerable dependencies in the repository. If this feature is enabled, when a Dependabot alert is raised for a vulnerable dependency in the dependency graph in the repository, Dependabot automatically tries to fix it.
https://docs.github.com/en/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates
Don't want the dependencies to be upgraded automatically
Dependabot opens a PR to the repository, it gives the team an opportunity to review the commit diff's between the version changes and decide whether to merge those changes or not.
Without this, it is hard to keep track of dependencies and their security posture and upgrades
Here is an example of changes that dependabot recommends
https://github.com/naveensrinivasan/lnd/pulls

The recent fix for DNS #5738 is tracked and could have been compared much easily with something like this https://github.com/naveensrinivasan/lnd/pull/5

This is one of the advantages of using dependabot alerts about CVE dependencies


Multi-file-config

Describe your changes!

Reviewer checklist

Read PR description: a summary about the changes is required
Changelog updated
Documentation: docs/{Reference, Cli, ...}, Docker and cli help/usage
Pulled branch, manually tested
Verified requirements are met
Reviewed the code
Reviewed the related tests

Needs test using config files in server/testdata/multi/server.

Does the merging take all block labels into account?


Updated README.md with links to translations

added a badge to Crowdin translation platform in the list of badges
changed the link from crowdin.com/projects/shopware6 => translate.shopware.com

1. Why is this change necessary?
We want to use https://translate.shopware.com instead of https://crowdin.com/project/shopware6/ from now on.
2. What does this change do, exactly?

adds a badge to translation platform
changes links like described above

3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

made another merge request on gitlab


Add JetBrains Exposed project

The Exposed repo has 11 issues with good-first-issue

I can pick up this issue and create a PR.


How to avoid cold start impact of large AWSSDK dlls on a Lambda function

I'm writing a .NET Core 2.1 lambda function and I want to use the Systems Manager Parameter Store but when I pull in the AWSSDK references it impacts my cold start time. Is there an alternative?
With a hard-coded connection string my app size well under 100kb and with a cold start of just over 2s. To move to using the Parameter Store I took a dependency on AWSSDK.SimpleSystemsManagement.dll which pulls in AWSSDK.Core.dll and now my application is 1.5Mb with a cold start is 3.8s

Hi @johnfnz, I'm surprised to see that your DLLs add that much memory and cold start time.  Thanks for your feedback.  That may be worth investigating,
The SSM Parameter Store is often the recommended approach, but you may be able to avoid using the Parameter Store by instead defining environment variables on your Lambda.  If you think this suits your use case, it may be worth considering.

You should also consider using Lambda Layers.

Thanks for the suggestions @klaytaybai. To clarify, when I refer to the app size I mean the publish folder size, which it seems has an effect on the cold start time.
I have used Layers but currently building on Windows so can't set --enable-package-optimization yet.
I believe I can access the Parameter Store from the SAM at deploy time so that might make environment variables an option and keep the secrets out of the source code.


imgur images

How can we fix imgur images?

@joamatab Thanks for posting this! I poked around a bit, and it looks like imgur requires a user-agent header or else it just gives back an empty response. This should be a pretty trivial fix in mystmd - I'll get a fix out later today.

This fix is now in the latest release on npm!

Awesome 😎 thank you


exclude seems to be ignored?

When I add:
[tool.tclint]
exclude = [
    'build',
    'orfs'
]

With 0.1.3 it seems to ignore this setting, while in 0.1.2 it seems to work just fine.

Thanks for raising this, looks like a regression in reading config from pyproject.toml. Just released a v0.1.4 with a fix.