support for openai.azure.us

Pull Request Type

[ ] ✨ feat
[x] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[ ] 🔨 chore
[ ] 📝 docs

What is in this change?
Relaxed validation to allow openai.azure.us
Additional Information
Add any other context about the Pull Request here that was not captured above.
Developer Validations

[x] I ran yarn lint from the root of the repo & committed changes
[x] Relevant documentation has been updated
[x] I have tested my code functionality
[x] Docker build succeeds locally

Any reason you closed this?

The logic was bad. I'll test it more thoroughly tomorrow then open another
pr.
On Tue, Mar 19, 2024, 6:10 PM Timothy Carambat @.***>
wrote:

Any reason you closed this?
—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/pull/927#issuecomment-2008378066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBSGLHZ542EEBVOPDKOB3DYZDHW7AVCNFSM6AAAAABE5WGRDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBYGM3TQMBWGY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Missing Curly?

Hi there! I just tried the script, it's awesome, but the first time it was throwing me an error at 247/29, saying that there's a MissingEndCurlyBrace. I added the } to finish the function FixWhitelistedApps and the script worked fine afterwards.
Many thanks!

 I'll put out an update to fix this after work today. Sorry
about the delay in response.
On Wed, Oct 3, 2018, 5:15 AM BowieFunes<EMAIL_ADDRESS>wrote:

Hi there! I just tried the script, it's awesome, but the first time it was
throwing me an error at 247/29, saying that there's a MissingEndCurlyBrace.
I added the } to finish the function FixWhitelistedApps and the script
worked fine afterwards.
Many thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Sycnex/Windows10Debloater/issues/51, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHCc4IJEvCMEQx_2G9fmifF-2FvC8fuoks5uhKpcgaJpZM4XF5ZE
.

fingers crossed

From: Richard Newton<EMAIL_ADDRESS>Sent: Wednesday, October 3, 2018 6:39 AM
To: Sycnex/Windows10Debloater
Cc: Subscribed
Subject: Re: [Sycnex/Windows10Debloater] Missing Curly?  I'll put out an update to fix this after work today. Sorry
about the delay in response.
On Wed, Oct 3, 2018, 5:15 AM BowieFunes<EMAIL_ADDRESS>wrote:

Hi there! I just tried the script, it's awesome, but the first time it was
throwing me an error at 247/29, saying that there's a MissingEndCurlyBrace.
I added the } to finish the function FixWhitelistedApps and the script
worked fine afterwards.
Many thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Sycnex/Windows10Debloater/issues/51, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHCc4IJEvCMEQx_2G9fmifF-2FvC8fuoks5uhKpcgaJpZM4XF5ZE
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSycnex%2FWindows10Debloater%2Fissues%2F51%23issuecomment-426640832&data=02|01||1d11e94006c240539fb008d629359d95|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636741707577385901&sdata=z2%2BMSwoluL9FPxKAe2sAyFeIKmrXHbHmZ%2F0uRfskeRI%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJjNA71u_s-ypz8MdBe7q1wPveOLGQMhks5uhL4EgaJpZM4XF5ZE&data=02|01||1d11e94006c240539fb008d629359d95|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636741707577385901&sdata=Cesoxc0ofM%2BUzyqzYF%2Bg1QE6CkK9upjTCd6hpyT8hQg%3D&reserved=0.

This is fixed in the latest commit.


Peer-to-peer Code Review

@Maedea9: Great job working on your project! 💯 The JavaScript code functionality is working. Keep up the good work! 👍
@Khaled-Alaa-1:  You did a good job on your project. Kindly, modify the title font size and make it a little bigger to match the wireframe design. The Add a new book subtitle is not in the original design, please check that.

Thanks for pointing out that guys 🤓 .


file-size: improve output message

In GitLab by @markuslf on Mar 24, 2021, 12:09

Current: Not all 1 file are within the given size range (thresholds 25.0M/1.0G).
Should be: n file(s) is(are) outside the given size specifications (thresholds 25.0M/1.0G).

Already fixed.


[Tiered Caching] Stats rework (4/4): Adds stats implementation for TieredSpilloverCache

Description
As part of tiered caching stats, integrates stats with TieredSpilloverCache. This TieredSpilloverCacheStatsHolder implementation is aware of the tier concept and will support aggregating the TSC's stats by tier as well as any other dimension values that are passed into it. It overrides some incrementing logic from DefaultCacheStatsHolder so it can properly combine heap and disk tier stats into stats for the cache as a whole.
TieredSpilloverCache tracks its own stats, rather than pulling stats from its tiers, because its getOrCompute() implementation can cause double-counting of a single hit or miss. To avoid redundancy, the individual tiers do not track their stats when they're part of TieredSpilloverCache.
Related Issues
Followup to https://github.com/opensearch-project/OpenSearch/pull/12531.
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
~- [N/A] Public documentation issue/PR created~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thinking through this -- I still don't particularly like how complicated these cache stats have become. It feels like a lot of code for relatively little value.
That said, most of the complexity in this specific PR is isolated to the tiered cache stats module, which we can always (easily) eject if the experimental feature doesn't pan out.
Also, I am on record (on a few GitHub issues) expressing my distaste for stats APIs as a concept. I sincerely hope that we'll soon be able to move to more of a "metrics" model, where we emit tagged cache hit/miss counters on every request that get aggregated into a time series metric store. At that point, we should be able to delete all of this stats code.


hangup feature is not working

thanks for this feature its much needed and thanks for the effort but i tried it more than once it is not working in the new release

after testing multiple times it is working

Alright, i think this can be closed then. Feel free to reopen if the issue persists.


zetaclient crashed on "invalid memory address or nil pointer dereference"

Describe the Bug
Zetaclient v14.0.1 crashed on this line:
https://github.com/zeta-chain/node/blob/4654c9065f5b0a8e01878377f17d2027be95f25d/zetaclient/evm/evm_client.go#L1135
This issue was introduced around v11.0.0
To Reproduce
every time when TransactionByHash fails
Expected Behavior
Should not use deference tx.Hash().Hex() on error
Screenshots

Environment (please complete the following information):

OS
Version used

This issue was initially reported by external TSS signer when zetaclient crashed in Athens3.
The bug was already resolved at the time of writing by commit https://github.com/zeta-chain/node/pull/1836/commits/7cad073f56d46b453b1c9537586edfac4171584d


docs: Clarify the requirement for JDK exact version 8 in install guide

Clarifies the requirement for JDK exact version 8.
When reading the install guides, it was not fully clear that exactly version 8 of the JDK is required. Requirements for other software refers to "and above", and it is a bit unusual to require exactly JDK 8.
The patch also makes some minor improvements to the language and consistency in the quick start and standard deployment guides.

run buildall


Add Web Locks API polyfill for Safari <15.4

https://github.com/aermin/web-locks
Related https://github.com/evoluhq/evolu/issues/106

The is no reliable polyfill for that.

I'm not going to polyfill a relatively old Safari because I can't test it.

That polyfill can't work in Web Worker because it needs LocalStorage. Also, I think we will require Safari with OPFS so it doesn't make sense to use it.


updates version of sphinx to 1.6.3 for easyinstall command in step 2 …

…of user_guide_src/README.  Related to issue: https://github.com/sphinx-doc/sphinx/issues/3838

Related to issue: https://github.com/sphinx-doc/sphinx/issues/3838

Confirmed that this will work. It is a bit of a pain in CentOS/RHEL, but doable.
The user guide readme should also note that python 2.7 is a requirement for that too, not just a suggestion.

sphinxcontrib-phpdomain may be the bigger issue here.

What is the problem with sphinxcontrib-phpdomain?
I did an altinstall of python 2.7, and then installed sphinx and sphinxcontrib-phpdomain with that.
Rebuilding the user guide seemed to work, with a warning about "RemovedInSphinx17Warning".
Building the user guide completely gave pages of warnings about " WARNING: Pygments lexer name 'ci' is not known".
The user guide appeared to build properly in spite of these.

I'm not saying that there's certainly a problem with it. I just remember it was hard to find a working version last time I setup things.

ok - python2.7, sphinx 1.6.3, and remembering to install ci_lexer (I missed this before) gives as clean a build as can be expected. Remaining errors are in our user guide source.
I am happy with this PR.

These appear when building against the develop branch, and the sources seem correct:
/home/narf/citest/user_guide_src/source/database/query_builder.rst:122: WARNING: Could not lex literal_block as "ci". Highlighting skipped.
/home/narf/citest/user_guide_src/source/general/urls.rst:49: WARNING: Could not lex literal_block as "ci". Highlighting skipped.
/home/narf/citest/user_guide_src/source/libraries/input.rst:204: WARNING: Could not lex literal_block as "ci". Highlighting skipped.
/home/narf/citest/user_guide_src/source/libraries/loader.rst:126: WARNING: Could not lex literal_block as "ci". Highlighting skipped.


Allow aeson 1.3

Coverage remained the same at 36.17% when pulling 8b419c5ea63a8077d42cd82a11fac7c6556d7df8 on msakai:feature/aeson-1.3 into 04fe42c4533b3244e9fa1c2772aa5e30baf5eef0 on guillaume-nargeot:master.


feat(LLD/Deeplinks): Adding Deeplinks support for Storyly in LLD

📝 Description
Adding support for Storyly deeplinks in LLD (based on https://github.com/LedgerHQ/ledger-live/pull/5696 for LLM)
https://github.com/LedgerHQ/ledger-live/assets/39890664/328c1d7e-7784-4228-824f-f86052b63b8d
❓ Context

JIRA or GitHub link:

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[ ] npx changeset was attached.
[ ] Covered by automatic tests.

[ ] Impact of the changes:

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Can you share a deeplink to test the feature, please?

ledgerlive://storyly?g=84930&s=752522&instance=14829&play=sg


RFC: add iterator support for generating the sequence of positive odd integers

Checklist

Please ensure the following tasks are completed before submitting a feature request.

[x] Read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.
[x] The issue name begins with RFC:.

Description

Description of the feature request.

This RFC proposes adding iterator support for generating the sequence of positive odd integers. This would be similar to the package @stdlib/math/iter/positive-even-integers.
The implementation would have the following package name:
Package: @stdlib/math/iter/positive-odd-integers
Alias: iterPositiveOddIntegersSeq
Related Issues

Does this feature request have any related issues?

None.
Questions

Any questions for reviewers?

No.
Other

Any other information relevant to this feature request? This may include screenshots, references, sample output, and/or implementation notes.

No.

Added in d6d91b4e7f89f2951c2afd7eabbfe977a969a20c.


FEAT-#5147: implement xs

The implementation here is adapted pretty closely from the pandas implementation.  The docstring is copied verbatim.
This is part of a sequence of PRs intended to address a whole mess of indexing bugs eg #2576

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[ ] Resolves #5147
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date

Fixed some of the lint complaints.  The docstring ones are just wrong.

can we ignore the docstring lint complaints?  the docstring is copied directly from pandas.

@jbrockmendel could you fix lint error?

@vnlitvinov any suggestion how to avoid the following problem? (CI is broken) /home/runner/work/modin/modin/modin/pandas/base.py:docstring of modin.pandas.base.BasePandasDataset.add:2:undefined label: 'advanced.mi_slicers'

(CI is broken) /home/runner/work/modin/modin/modin/pandas/base.py:docstring of modin.pandas.base.BasePandasDataset.add:2:undefined label: 'advanced.mi_slicers'

okay, I found the issue I was mentioning at the meeting: #3099
but it seems that it has been resolved by just overriding broken pandas docs with our own one-line description (+ some 'noqa's to silent the doc-checker). Like this:
https://github.com/modin-project/modin/blob/e35b604eba32edef42e4320bc1b2bdf64ce0bee8/modin/pandas/base.py#L796-L802
may we do the same here until we figure out how to properly inherit from pandas docs discarding all of the unsupported stuff?

(CI is broken) /home/runner/work/modin/modin/modin/pandas/base.py:docstring of modin.pandas.base.BasePandasDataset.add:2:undefined label: 'advanced.mi_slicers'

okay, I found the issue I was mentioning at the meeting: #3099
but it seems that it has been resolved by just overriding broken pandas docs with our own one-line description (+ some 'noqa's to silent the doc-checker). Like this:
https://github.com/modin-project/modin/blob/e35b604eba32edef42e4320bc1b2bdf64ce0bee8/modin/pandas/base.py#L796-L802
may we do the same here until we figure out how to properly inherit from pandas docs discarding all of the unsupported stuff?

Agree

@YarShev ping

Code scanning results / CodeQL failed.

Code scanning results / CodeQL is still failing.

Code scanning results / CodeQL is still failing.

Fixed


Guessing of namedplaces

As part of the content guessing when importing, we want to add geometries out of named places, as we do for country names or IP's

@saleiva I'm moving this to the next milestone. For this one I already have Perf Editor and Kepler.


NIFI-9618 Upgrade Checkstyle to 9.2.1

Description of PR
NIFI-9618 Upgrades Checkstyle from 8.29 to 9.2.1 and corrects several missing Java documentation return statements. Changes also include removing the duplicative maven-checkstyle-plugin in the NiFi Registry Maven configuration.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

love it.  if build checks out +1 and please self merge


Train on rice

Hi, I really appreciate your job! Could you give some instructions on how to process and train model on RACE dataset?

Thank you for your interests.
Both RACE dataset and SemEval-2018 Task 10 dataset are multiple-choice reading comprehension datasets. All you need to do is to preprocess RACE dataset into the same format as required by this repository. You can check out src/preprocess.py preprocess_race_dataset for reference.
Be cautious that RACE dataset is much larger and takes longer time to train.


Fix Redshift Locking Behavior

Tables should be locked before any edits happen. In the case of overwrite + delete/truncate method, the lock would happen too late, leaving room to query an empty table (or for serializable isolation errors).
Since all locks happen after a _create_table(), we can move lock into that function for simplicity.
Feature or Bugfix

Bugfix

Detail

Serializable isolation errors still possible when lock = True when doing and overwrite + delete method.

Relates
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: ae9086d043d7cb7de1a70ad00576f684b48a21db
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Stem plot

What do you think of adding something like matlab stem plot?
http://www.mathworks.com/help/matlab/ref/stem.html
In Gadfly it would look like:

For two vectors
 x = linspace(0,9, 10)
 y = sin(x)

Try this (all in one line!):
pl = plot(x=x, y=y, Geom.point); for k in 1:length(x); push!(pl, layer(x=[x[k],x[k]], y=[0, y[k]],    Geom.line));end; pl

I switched to PyPlot because of the lack of "stem" in Gadfly. Though, PyPlot has its own issues. I'm back to Gadfly...

using Plots
sticks(sin, 0:0.5:10, markercolor=:red)
savepng(ans, "tmp.png")

It's only on the dev branch right now though.

fixed in https://github.com/GiovineItalia/Gadfly.jl/pull/1076


CODE - Hide Api Key

Hide Api Key
User Story
As the lead dev, I would like to remove the api key from being visible within the code so that it isn't publicly accessible.
Requirements

Api key isn't visible within the code
Function maintains with the newly hidden key

Api key moved from script.js -> .env

with .gitignore created with .env ignored, public access to the api key should be prevented

Reset to old file as website wasn't detecting API key

Keeping this on the backlog as ~5 hours of work into fixing and no progress. Not required for the MVP regardless so to be worked on later.

Took a long time however task is completed! as per the last commit <6936f1b> the API key is within .env, of which is hidden within .gitignore - and while this isn't something callable directly from the script.js file we have called it to config.js and then required that be present within script.js, making it work.

Due to the nature of being stored within a .js file that is called to the site, the API key is still currently visible on the site:

While config.js is within .gitignore, this is only a somewhat temporary solution.
We have an issue in which HTML seems against calling the API from .env and can do more testing

Comment for context:
Hiding this API key has been a priority however with the many hours attempting to do so I simply could not find a way to get the HTML site to call the key successfully from either .env or as a github secret. I believe this is to do with a conflict of HTML but with the time investment considered I shall leave this in ready so that in the context of a true sprint it would be brought up during a standup and hopefully dealt with collaboratively.


Switch to Docsy tabpane shortcode

If you visit https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-kubectl-on-linux, you'll see a few tabbed panes for "x86-64" and "ARM64".
The default is "x86-64". If you want to see the "ARM64" code, then you have to click very tab instance.
By switching to Docsy tabbed panes, you'd only have to select one "ARM64" tab and then all tabbed panes would update to reflect that selection. Also, tab-pane choices are persisted through cookies.
For details see Tabbed panes.

/retitle Switch to Docsy tabpane shortcode
/area web-development

My opinion: we should make the change gradually (eg section by section), rather than across the entire site in one large PR.
/priority backlog

I have understood what's required. But it can be only implemented when the PR #48812 is merged right? I would like to work on this!

This site already uses [a customized version of] the Docsy theme.
You can use tabpane shortcodes right now now @Aaina26.

However, please wait for this work to be accepted (look for a label, triage/accepted)


Add protoc Param --bq-schema_opt=single-message

adding a protoc param --bq-schema_opt=single-message to tell protoc-gen-bq-schema treating each proto files only contains one top-level message type.
if a file contains no message types, then the param simply does nothing.
if a file contains more than one message type, then only the first message type will be processed. in that case, the table names will follow the proto file names (e.g. foo.proto becomes foo.schema).

This is a great idea.
Can I ask a few things:

Add a new proto in the examples directory, e.g., single_message.proto. Maybe strip all bq plugin related options. (I just copied foo.proto)
Run protoc -I. -Iexamples --plugin=./protoc-gen-bq-schema --bq-schema_out=examples examples/single_message.proto.
Verify the examples/foo/something.schema looks like you'd expect.
Add both the new proto and generated schema to the PR.
Modify .github/workflows/go.yml to add the protoc generation line (in run examples)
Modify .github/workflows/go.yml and upgrade the version of go to 1.16.

This will add an example for the single message and also verify with Github Actions that all the examples still work correctly. (Consider it a cheap & cheerful integration test.)
Mark

thanks for your feedback @mescanne.
please review the current changes.

Great, and the CI all went through fine. Thanks a lot for the contribution.


Add menu option to datatype editor to open another datatype

When using the datatype editor as an independent window, having the ability to open another datatype without having to switch plugins would help.

To clarify, are you asking for the ability to edit a data type of your choosing from an existing editor, or from anywhere for that matter?

To clarify, are you asking for the ability to edit a data type of your choosing from an existing editor?

Yes.

Although you've added some help text indicating a key combo for this, it should be added to either the buttons or the RMB popup as well.


Add new tests for List Rooms and associated documentation

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

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


Spring Data Hibernate JPA jar files cannot get loaded

I am using Spring XD 1.1.2.RELEASE and xd-singlenode container
I am writing custom processor which needs JPA, so I copy the extra jar files to enable JPA functionality into xd/lib:
hibernate-jpa-2.1-api-1.0.0.Final.jar
hibernate-entitymanager-4.3.9.Final.jar
hibernate-core-4.3.9.Final.jar
hibernate-commons-annotations-4.0.5.Final.jar
jandex-1.1.0.Final.jar
dom4j-1.6.1.jar
spring-orm-4.1.6.RELEASE.jar
spring-data-jpa-1.8.0.RELEASE.jar
spring-data-commons-1.10.0.RELEASE.jar
mysql-connector-java-5.1.35.jar
When I start xd-singlenode container then I encounter error: Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaAutoConfiguration.class]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set
I haven't even deployed my custom processor module.
Please help or is there any other way to enable Spring Hibernate JPA in Spring XD?

Seems related to auto config kicking in, http://stackoverflow.com/questions/26548505/org-hibernate-hibernateexception-access-to-dialectresolutioninfo-cannot-be-null. Looks like it will help solve your issue

Thanks Mark,
The link provides great guidance to me.
I created small jar file containing SpringBootApplication module and application.properties and copied it into xd/lib then I can start the xd-singlenode
I have to include my repositories and entities inside my custom processor spring-module.xml
I can use them in my custom processor now.


Update Wycheproof ecdh_secp384r1_test.json to v1

Update Wycheproof testvector ecdh_secp384r1_test v0 to ecdh_secp384r1_test v1.

Checklist

[x] I've run tests to see all new and existing tests pass
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

If you've made changes to gyb files

[ ] I've run .script/generate_boilerplate_files_with_gyb and included updated generated files in a commit of this pull request

Motivation:
We ought to use as many and as up to date test vectors as possible. Wycheproofs v0 were created 4 years ago and were due some upgrade.
Modifications:

Replaced the v0 with the v1 version.
Changed fatalError in test code with a failable init (same change as in https://github.com/apple/swift-crypto/pull/160)

Result:
Number of tests is now 1047 instead of v0's test count of ~319~.

@swift-server-bot test this please


kerberos_server: allow choosing MIT or Heimdal

Motivation for this change
Allow using MIT Kerberos as a kerberos server, and add some initial configuration. Related to #29623.
This is my first PR, let me know if anything is not suitable.
As far as I can tell the upstream kerberos_server service was broken, as it expected binaries to be in sbin while they were in bin (see ab6c57e). There were previously no tests, this adds some basic smoke tests.
I'm happy to add more configurable options, I've so far just configured what I'm familiar with. In theory it should be possible to serve multiple realms from one server, but I don't need this and haven't been able to get it to work easily so it's not part of this PR.
Adding the usual set of plain-text configuration is difficult, as MIT and Heimdal take slightly different formats of options.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg test kerberos.mit kerberos.heimdal

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'kerberos' in selection path 'tests.kerberos.mit' not found

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute 'kerberos' in selection path 'tests.kerberos.mit' not found

I think the point here was krb5-config, as that needs to keep reference to the headers.  I was focused on the case of type == "lib".

That makes sense - I will move the other programs back to the default output then unless there is an objection? Should there be separate 'bin' and 'lib' or 'out' and 'lib' outputs or should these go together?

The type == "lib" has almost nothing there, and for the other cases it's probably not important to split.

@kwohlfahrt thanks for making an effort to fix this.
I had some similar changes in mind that I never got around to finishing: https://github.com/eqyiel/nixpkgs/commit/4114381a2dc486bb8ac9afda26a6e863ddaf033c
I'll probably try to apply it on top of your changes at some point :smile_cat:

Looks okay to me. Any objections to merging?

@GrahamcOfBorg test kerberos_server

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.kerberos_server
Partial log (click to expand)
Cannot nix-instantiate `tests.kerberos_server' because:
error: attribute 'kerberos_server' in selection path 'tests.kerberos_server' not found

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.kerberos
Partial log (click to expand)
Cannot nix-instantiate `tests.kerberos' because:
error: attribute 'kerberos' in selection path 'tests.kerberos' not found

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: tests.kerberos_server
Partial log (click to expand)
Cannot nix-instantiate `tests.kerberos_server' because:
error: attribute 'kerberos_server' in selection path 'tests.kerberos_server' not found

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: tests.kerberos
Partial log (click to expand)
Cannot nix-instantiate `tests.kerberos' because:
error: attribute 'kerberos' in selection path 'tests.kerberos' not found

@matthewbauer I've added a line to release.nix - is that what you are after?

@GrahamcOfBorg test kerberos

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: tests.kerberos
Partial log (click to expand)
Cannot nix-instantiate `tests.kerberos' because:
error: while evaluating anonymous function at /home/ofborg/ofborg2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/builder-7c6f434c2/nixos/release.nix:23:8, called from /home/ofborg/ofborg2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/builder-7c6f434c2/lib/attrsets.nix:282:43:
while evaluating 'hydraJob' at /home/ofborg/ofborg2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/builder-7c6f434c2/lib/customisation.nix:162:14, called from /home/ofborg/ofborg2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/builder-7c6f434c2/nixos/release.nix:23:16:
while evaluating the attribute 'system' at /home/ofborg/ofborg2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/builder-7c6f434c2/lib/customisation.nix:167:24:
attribute 'system' missing, at /home/ofborg/ofborg2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/builder-7c6f434c2/lib/customisation.nix:167:10

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.kerberos
Partial log (click to expand)
Cannot nix-instantiate `tests.kerberos' because:
error: while evaluating anonymous function at /var/lib/gc-of-borg/nix-test-rs-23/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-23/nixos/release.nix:23:8, called from /var/lib/gc-of-borg/nix-test-rs-23/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-23/lib/attrsets.nix:282:43:
while evaluating 'hydraJob' at /var/lib/gc-of-borg/nix-test-rs-23/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-23/lib/customisation.nix:162:14, called from /var/lib/gc-of-borg/nix-test-rs-23/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-23/nixos/release.nix:23:16:
while evaluating the attribute 'system' at /var/lib/gc-of-borg/nix-test-rs-23/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-23/lib/customisation.nix:167:24:
attribute 'system' missing, at /var/lib/gc-of-borg/nix-test-rs-23/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-23/lib/customisation.nix:167:10

@matthewbauer sorry, should be fixed now. Also I think you need to test kerberos.mit and kerberos.heimdal rather than just kerberos

Rebased onto latest staging due to conflict. Not sure if I have permissions to run borg tests, so here goes:
@GrahamcOfBorg test kerberos.mit kerberos.heimdal

OK, seems I can't start borg tests. @matthewbauer could you please test it again and merge if possible?

@GrahamcOfBorg test kerberos.mit kerberos.heimdal

Failure on aarch64-linux (full log)
Partial log (click to expand)
Merge failed

Failure on x86_64-linux (full log)
Partial log (click to expand)
Merge failed

@peterhoeg done, not tested locally yet as it rebased without edits. Will do so this evening.

Failure on x86_64-linux (full log)
Attempted: tests.kerberos.mit, tests.kerberos.heimdal
Partial log (click to expand)
cannot build derivation '/nix/store/29vmgz987ca347dnm4m2x5z3k0cdl12v-closure-info.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/1q4pnk7y1raidpvz4l2nxp594jqx9g5b-run-nixos-vm.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/26lbji6i8l6d0m6lm8a711a8ds6nqdrm-run-nixos-vm.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/0wipkzbfxg6lpf6q7wq4y4ys19zc3367-nixos-vm.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/40pbxw3vgzq22ip1y8dc5fswsv6f8nm7-nixos-vm.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/3v4lsps8hqzmvlq6fjrw46kzmfs3x6ac-nixos-test-driver-kerberos_server-heimdal.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/8lp4afwavh4by91jkk9cragk80s6kghl-nixos-test-driver-kerberos_server-mit.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/xicpqi4vyy5f4vixrl2wv82q9lr1hpdk-vm-test-run-kerberos_server-heimdal.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/kr6wdw04agly5xwxsb4n0q2mh3gpw7bm-vm-test-run-kerberos_server-mit.drv': 1 dependencies couldn't be built
error: build of '/nix/store/kr6wdw04agly5xwxsb4n0q2mh3gpw7bm-vm-test-run-kerberos_server-mit.drv', '/nix/store/xicpqi4vyy5f4vixrl2wv82q9lr1hpdk-vm-test-run-kerberos_server-heimdal.drv' failed

Failure on aarch64-linux (full log)
Attempted: tests.kerberos.mit, tests.kerberos.heimdal
Partial log (click to expand)
cannot build derivation '/nix/store/74xc1gwm6l5vvzgbarpbb6zx2xcfmixm-nixos-test-driver-kerberos_server-mit.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/gi3iv9mxz1j2sijwx75jy25gk9a8d9mw-vm-test-run-kerberos_server-mit.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/zav720dlqlfrnvjfg61zgpsym70y45nb-etc.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/2cwg3k57jdw1v9q0hjdarqbdjjb0cbfq-nixos-system-machine-18.09.git.729b9e6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/bl1k7ggs96s8wj8z8qa1348rcjypsnfb-closure-info.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/a4l0rk0j522v0ibxbmskdsncrb98c7q9-run-nixos-vm.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/hyfjz4q1fnqkz0cdsv8gkilh9fhjf3d0-nixos-vm.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/2mf396p51gznxf3dz7h1gyamvw3qdkkl-nixos-test-driver-kerberos_server-heimdal.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/q43zw0p7gw9w6x88cs54gmqza8gndw1q-vm-test-run-kerberos_server-heimdal.drv': 1 dependencies couldn't be built
error: build of '/nix/store/gi3iv9mxz1j2sijwx75jy25gk9a8d9mw-vm-test-run-kerberos_server-mit.drv', '/nix/store/q43zw0p7gw9w6x88cs54gmqza8gndw1q-vm-test-run-kerberos_server-heimdal.drv' failed

@kwohlfahrt - so building failed. You'll take a look?

Yes, I am looking into it. It seems unrelated (something to do with libDRM) at first glance, but I'll investigate more.

@peterhoeg this is building locally now, but Graham has an error that "target branch staging doesn't evaluate" - should I be targeting a different branch?

Thanks for doing all this hard work!
The staging part is probably due to the change to pkgs/development/libraries/kerberos/krb5.nix as I am assuming this will cause a significant amount of rebuilding.
I will not be able to review this in detail in the near future - the arrival of our twins is imminent now so I'm hoping @vcunat or @FRidh (or others) will be able to dedicate the time this PR deserves.

This is now rebased, and tests pass locally.
@peterhoeg congratulations!

This was open for too long.

I think this closes #39424 as well.


don't check in png files

If png files are generated by the code, don't check them in.
The github should contain only code, really, and the things needed to run the code.
Also very little data should be checked in.

OK, got it, thanks! deleted.


Cypress. Temporarily disabling the test step in the case 85.

Motivation and context
Temporarily disabling the test step in the case 85.
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Just for reference. Need to reenable the test after the issue is resolved: https://github.com/openvinotoolkit/cvat/issues/3438


Added default-config API route

Description:
Added a new API route called "admin/default_config" to fetch the default config details of Azimuth.
Checklist:
You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

[x] ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
[x] PRE-COMMIT. You ran pre-commit on all commits, or else, you
ran pre-commit run --all-files at the end.
[x] USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
our users.
[x] DEV CHANGES.

Update the documentation if this PR changes how to develop/launch on the app.
Update the README files and our wiki for any big design decisions, if relevant.
Add unit tests, docstrings, typing and comments for complex sections.

Thank you Gab and Joseph :)


Cherry pick nbgl level21

Description
Cherry-pick NBGL improvements from Master to API_LEVEL_21:

Create a QR Code type of modal window for Tag/Value alias
No "swipe to review" in first page of review if using a Tip-Box
Add extension to INFOS_LIST to enable alias for some info types

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

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

Project coverage is 35.76%. Comparing base (603cf09) to head (0590854).
Report is 80 commits behind head on API_LEVEL_21.

Additional details and impacted files
@@                Coverage Diff                @@
##           API_LEVEL_21     #802       +/-   ##
=================================================
- Coverage         60.19%   35.76%   -24.44%
=================================================
  Files                12       13        +1
  Lines              1726     1591      -135
=================================================
- Hits               1039      569      -470
- Misses              687     1022      +335

Flag
Coverage Δ

unittests
35.76% <ø> (-24.44%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Implemented unittests to test restoring search query

Added perl tools to generate json files for music and movie data
Upgraded build tools version, sdk compile version, and support libraries
as this is required by the test packages.
Added new product flavor unittest to make sure assets and settings required
for testing do not also ship with a release version of Kore

This needs to be put on hold, as upgrading the target-sdk to version 23 automatically applies the new permission model, which it isn't yet prepared to handle (asking for permissions).

Ah ok, do you have any plans to add support for the new permission model anytime soon?

Yes, soon (it's not hard, but i haven't had much time lately).

Don't be fooled by the travis check. This does not work at the moment. Still working on it.

@poisdeux Can you please confirm if this can be merged? Not sure if there were any changes lately that might conflict with this.
And by the way, creating the directory tools/jenkins and moving the jenkins scripts there won't affect the build?

Rebased on master. Should merge fine now.
I do not have any experience in setting up a jenkins environment. The move might require a configuration change at the server.

likely only two line changes in jenkins. ping @Memphiz to be sure

Yes in the Jenkins Job 2 lines in the "execute Shell" steps have to be altered for this. (i guess @MartijnKaijser spotted those already :) ).

@Memphiz Can you please comment here when the Jenkins Job is changed, so i can merge this. Thanks.

go ahead and merge

@Memphiz seems there must be another change as well

no idea and no time atm

There doesn't seem to be an apk file built anymore since this pr got merged - at least it is nowhere to be found in the workspace anymore

@poisdeux Seems like the changes at build.gradle are conflicting with generating the release build. Any ideas?

@Memphiz looking at the output, it seems that /Users/Shared/jenkins/workspace/Kore/../../android-dev/signing/doreleasesign.sh might need to be changed (not sure, as i can't see it).
I'm guessing that it pulls the apk from /Users/Shared/jenkins/workspace/Kore/app/build/outputs/apk/, signs it and drop it on /Users/Shared/jenkins/workspace/Kore/kore-release.apk. With this PR, we need to make sure that it is getting the right apk - it should be signing app-full-release.apk (ignore app-instrumentationTest-release.apk).

Will check tomorrow

Hmm, assumptions are the ........
It appears that adding the instrumentationTest flavor resulted in generating ONLY app-instrumentationTest-release.apk. We need to add an extra flavor to generate an APK that does not include the permission needed for testing Kore. I'm still testing this, as it appears the task grantAnimationPermissionDev is executed for each flavor.

@poisdeux Be advised that i've added a commit on master that adds a new product flavor.

i think i fixed the signing ... the doreleasesign.sh script checked if the apksign in tools/android/packaging is there before calling it - i have removed that check ... also see my PR - there was a wrong apk name in the tools/jenkins/android/packaging/apksign script.


TDF KAS field can have different paths and scheme for a single KAS

Currently, we support gRPC and RESTful endpoints for rewrap.  If a TDF is created with one SDK that uses a gRPC endpoint, the KAS field in TDF is gRPC, then if an SDK that uses RESTful it will fail decrypt.
In nanotdf, the KAS field is endpoint specific https://github.com/opentdf/spec/tree/main/schema/nanotdf#331-header
In TDF3, the url field in Key Access Object, https://github.com/opentdf/spec/blob/main/schema/tdf/KeyAccessObject.md#keyaccess
One solution, the .well-known have the supported KAS endpoints and the TDF KAS field only specifies the path where .well-known can be found.
For flexibility, possible KAS endpoints in the .well-known should support different schemes: https://, wss://.  and different paths

@pflynn-virtru To start could this be as simple as the sdk being smart to add the rewrap path if they don't see it and strip it off if they do see it in the field?


Update contributors.md

Added name to contributors list.

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

This file modifies a pre-existing file.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

37a70f9f0f104873bf9cb62c672a53a98cc8e5a9


page not found when inspecting RH registry

$ skopeo registry.access.redhat.com/rhel7 | jq '.Config.Labels.Name'
time="2016-03-08T16:31:20+01:00" level=error msg="Error trying v2 registry: Error parsing HTTP response: invalid character '<' looking for beginning of value: \"<!DOCTYPE HTML PUBLIC \\\"-//W3C//DTD HTML 3.2 Final//EN\\\">\\n<title>404 Not Found</title>\\n
Not Found
\\n
The requested URL was not found on the server.

If you entered the URL manually please check your spelling and try again.
\\n\""
"rhel7/rhel"

command is successful but that debug output is weird and docker.io registry doesn't suffer from this

This looks like it could be a problem at the registry.access.redhat.com/rhel7.

yep, I'll leave this open to track it

The issue as I understand it is, while the registry technically supports v2 endpoint, the docker client doesn't fall back to v1 images if v2 images are found, so we have to have to land v2 format for all images. It doesn't sound quite right but that was what I understood.

registry.access.redhat.com does not advertise itself as a v2 registry at all right now, i.e. /v2/ will give a 404 response. skopeo needs to fall back to v1 when it sees this.

When will this change.

Isn't really happening anymore, so closing


Render L.Control with Canvas?

Hey guys, a little help needed here. I don't even know if this is a real issue, so my apologies in that case.
I'm with a demand to export a map in a image file and I'm using this plugin: http://mapbox.github.io/leaflet-image/
The thing is, while it's easy to save my layers (using L.featureGroup), since they can be rendered with Canvas with a single option on map creation (preferCanvas: true), I can't save my legend for the map (created using L.Control with a custom html template).
I wonder if its possible to render my L.Control layers with Canvas, of if you guys have other ways to do what I'm trying.
Thanks by now,
Pedro

No, this should be a bug report in https://github.com/mapbox/leaflet-image instead. You want leaflet-image to handle L.Controls, and that is out of the scope of the core leaflet repo.
And, quoting their docs:

This library does not rasterize HTML because browsers cannot rasterize HTML. Therefore, L.divIcon and other HTML-based features of a map, like zoom controls or legends, are not included in the output, because they are HTML.


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit 3bcbb83:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch 9f49b61c-45d5-42d0-b320-29cf4f9649c1 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


98 create multiple accounts

Summary
Added popup notifications to alert about the account creation progress.
When the Create button is pressed, the view is closed. If the account was created without errors, a popup notification is shown. Also, If an error occurs trying to create the account, the error message got from the Wallet Service is shown.

@ktorresno resolve the conflicts then I'll take a look

@ktorresno resolve the conflicts then I'll take a look

Done.


Upgrade to scala 2.13 and spark 3.3.2 in branch-0.8

Upgrade to scala 2.13 and spark 3.3.2

We will do the upgrade in branch-0.7 https://github.com/delta-io/delta-sharing/pull/355


Ch model adaptations

Here are some adaptions requested by the Canton and Ville de Genève and was adapted from model version 2.5.6...
Note that we noticed that nosgestesclimat-site-nextjs (v2.0.1) is failing to build (yarn build) when using that model adaptation with the following output:
$ yarn build
yarn run v1.22.22
$ next build
  ▲ Next.js 14.2.7
  - Experiments (use with caution):
    · turbo
    · webpackBuildWorker
    · instrumentationHook

   Creating an optimized production build ...
 ✓ Compiled successfully
   Linting and checking validity of types  .Failed to compile.

./src/app/(simulation)/simulateur/[root]/_components/simulateur/charts/inlineChart/SubcategoriesChart.tsx:43:37
Type error: Parameter 'subcategory' implicitly has an 'any' type.

  41 |           currentCategory
  42 |         )}`}>
> 43 |         {filteredSubcategories.map((subcategory, index: number) => (
     |                                     ^
  44 |           <Subcategory
  45 |             key={subcategory}
  46 |             position={
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

That's weird, I don't get the same error ; I would advice you to delete the .next folder along with the next-env.d.ts and the node_modules ; re-run yarn then yarn build.

That's weird, I don't get the same error ; I would advice you to delete the .next folder along with the next-env.d.ts and the node_modules ; re-run yarn then yarn build.

I did but by adding yarn link @incubateur-ademe/nosgestesclimat after yarn so that this model adaptation is being included during the build; but unfortunately this didn't resole the issue...

Hmm I guess the only option is to dive into the site repo and correct the type error, from here this looks like something that could be solved by adding some any in the file but I can't be sure.

Ok, thank you; will do that...

Le modèle semble compiler correctement. @JuliePouliquen est-ce que tu voudrais jeter un coup d'oeil également ?


Consider changing tail offset to be number of frame alignments

Rather than have the tail offset which is incremented on publication claim be the byte offset in the term it can be the number of frame alignments, currently 32-byte alignment, so that it gives a greater margin for error if many concurrent threads where to pass pass under the publication limit at exactly the same time to increment the tail and cause overflow.
For the publication to fail currently it would take 192 threads to be at the same point and term buffers to be 1GB length, with each claiming the maximum 16MB message length, for overflow to happen. Each division of the term length by 2 doubles the number of threads required for overflow at maximum message length.

Sounds a bit like compressed oops, based on a similar observation on alignment, and with a similar (minor) overhead of "uncompressing" the offset. Cool idea :)

Credit should go to @goglusid for the observation.


Expand Utils.Units enums to cover existing units used in schema

Utils.Units has been merged into main as a structural system, but needs to be fully fleshed out with all relevant unit types.
Current types are:

Size
Mass
Frequency
Volume
Angle
Time

Others will be searched for using find in files feature, with search term _units.
Please advise if there are any specifics that would not be found this way.

Duplicated issue


On-premises integration - Broken link

This link at the beginning of the document is broken:
Preparing Dynamics 365 Sales for Integration on-premises
I think the correct link is this, without the Markdown extension (.md) at the end:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/prepare-dynamics-365-for-sales-for-integration

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2957b832-9aee-e050-b034-7f3badb2e27c
Version Independent ID: a93b51b9-9a52-c8a2-2197-38c02f2e327f
Content: Integrating with Dynamics 365 Sales - Business Central
Content Source: business-central/admin-prepare-dynamics-365-for-sales-for-integration.md
Service: dynamics365-business-central
GitHub Login: @bholtorf
Microsoft Alias: bholtorf

Thank you for your feedback! This will be fixed in the next doc update.


Can't see my routes

I'm trying to use autogen on this project setup:
https://github.com/Shyam-Chen/Express-Starter
I did try to add to the endpoints: app.js, server.js, routes,js and each controller file as well, however, none of the solutions are worked.

Hi @MatyasK. Thank you for opening the issue.
I will check and handle this case as soon as possible.

He is unable to view the routes because of the way the project is structured. The swagger-autogen expects to read a file that has a Router and, in its case, there is a function that returns a router.
const controller = (() => {
  const router = Router();

  /**
   * POST /hello-world { data?: any }
   * @example http POST :3000/hello-world
   * @example http POST :3000/hello-world data=Express
   */
  router.post('/', (req, res) => {
    res.json({ data: service.sayHello(req.body.data) });
  });

  return router;
})();

I did a test, removing the router from inside the function and passing to the index of hello-world the swagger-autogen worked.
// import controller from './controller';
import { Router } from 'express';
import service from './service';

const router = Router();

/**
 * POST /hello-world { data?: any }
 * @example http POST :3000/hello-world
 * @example http POST :3000/hello-world data=Express
 */
router.post('/', (req, res) => {
  res.json({ data: service.sayHello(req.body.data) });
});

const controller = {};

controller.prefix = '/hello-world';

export const HelloWorld = {
  controller,
  service,
};

export default controller;

{
  "swagger": "2.0",
  "info": {
    "version": "1.0.0",
    "title": "REST API",
    "description": ""
  },
  "host": "localhost:3000",
  "basePath": "/",
  "schemes": [
    "http"
  ],
  "paths": {
    "/": {
      "get": {
        "description": "",
        "parameters": [],
        "responses": {
          "200": {
            "description": "OK"
          }
        }
      }
    },
    "/helloWorld.prefix/": {
      "post": {
        "description": "",
        "parameters": [
          {
            "name": "body",
            "in": "body",
            "schema": {
              "type": "object",
              "properties": {
                "data": {
                  "example": "any"
                }
              }
            }
          }
        ],
        "responses": {
          "200": {
            "description": "OK"
          }
        }
      }
    }
  }
}

I don't know if the best approach is to adjust swagger-autogen for this case or if the project should adapt to the lib.

Having the same problem. Project is structured with a function and autogen wont work properly.


ansible images using just ubi8

Description of the change:
Ansible images using just ubi8
Motivation for the change:
https://github.com/operator-framework/operator-sdk/issues/1656

Hi @joelanford,
JFY. Not passing because of the usage of inotify3-tools instead of inotify-tools. I am working on in the fix which probably will be here https://github.com/operator-framework/operator-sdk/blob/2ca5cb197fad6e5a4f4f61d53e1426835cb267c9/internal/pkg/scaffold/ansible/ao_logs.go#L43.
TASK [debug] *******************************************************************
    ok: [localhost] => {
        "ansible_log.stdout_lines": [
            "/usr/local/bin/ao-logs: line 6: inotifywait: command not found"
        ]
    }

/test e2e-aws-helm

/test e2e-aws-subcommand
/test e2e-aws-ansible

/test e2e-aws-ansible

/test e2e-aws-go

Hi @joelanford,
I think it is OK to go now. WDYT?


Add ContentNotFoundError

In the process of researching Ultralight test failures for Hive, I discovered that the JSON RPC spec currently advises that the portal_*localContent methods return 0x when no content is found.
However, this did not solve a hive test failure for portal_beaconLocalContent for Ultralight when I updated our code to match this spec.  After further research, I discovered that trin and fluffy return an error and not 0x when content is not found.  This PR updates the spec to reflect the current implemented state of the clients.
Specifically:

Corrects the portal_*localContent responses to reflect that the clients return an error
Adds a new ContentNotFoundError a specifies that the error code returned should be -32001 for the ContentNotFoundError and the message "content not found" following the current Trin implementation.
Adds a -32002 for the ContentNotFoundErrorWithTrace error type that is returned by the traceRecursiveFindContent method types

@ogenev @kdeme @KolbyML any outstanding thoughts or are you good with merging this?


Fix small code bugs for FT Stateprep

Description
This PR fixes some issues with certain codes.
There was a bug when the code was defined over a number of qubits, which is an exact power of 2, leading to the optimal state prep circuit failing to be synthesized.
Another issue occurred when looking at d=2 codes, which cannot be used for error correction but only for error detection. I have added functionality to set whether one wants to create the circuit for error detection or error correction in the StatePrepCircuit class.
Fixes #265
Checklist:

[x] The pull request only contains commits that are related to it.
[x] I have added appropriate tests and documentation.
[x] I have made sure that all CI jobs on GitHub pass.
[x] The pull request introduces no new warnings and follows the project's style guidelines.

@pehamTom could you maybe base this PR on top of #266?
I fixed a couple of mypy errors as part of updating the infrastructure and I am fairly sure this will create (small) conflicts.
I hope the other PR should be ready asap.

@pehamTom could you maybe base this PR on top of #266? I fixed a couple of mypy errors as part of updating the infrastructure and I am fairly sure this will create (small) conflicts. I hope the other PR should be ready asap.

Done, and resolved the conflicts.

Rebasing to main because the other PR might be awhile

The patch coverage is incorrect due to the concurrent execution of processes. All new functionality is covered and the diff of the project does not change.


Consider add ireplicateM and ireplicateM_

An indexed replicateM/replicateM_ would be nice.

Doesn't forM [1..n] kinda make ireplicateM unnecessary? I'm not opposed to adding it but I'm interested what your usecase is.

I thought one of the problems which ilist package solve is false sharing, isn't? consider:

forM [1..10000] $ ...   -- first, we have
...
forM [1..10000] $ ...   -- we do another things 10000 times again

GHC often consider [1..n] could be shared so it will get floated out, now a 10000 element list just got blasted into memory which is a big nono.
We could use oneShot [1..10000] trick to solve this, but an ireplicateM could be a better choice.

Ah. Okay, makes sense. I'll add it.

Thanks! follow here i quickly got an implementation(just too lazy to make a PR):
-- | @'ireplicateM' n act@ performs the action @n@ times,
-- gathering the results.
ireplicateM        :: (Applicative m) => Int -> (Int -> m a) -> m [a]
{-# INLINEABLE ireplicateM #-}
{-# SPECIALISE ireplicateM :: Int -> IO a -> IO [a] #-}
{-# SPECIALISE ireplicateM :: Int -> Maybe a -> Maybe [a] #-}
ireplicateM cnt f = loop 0
  where
    loop !i
        | i >= cnt  = pure []
        | otherwise = liftA2 (:) (f i) (loop (i + 1))

-- | Like 'ireplicateM', but discards the result.
ireplicateM_       :: (Applicative m) => Int -> (Int -> m a) -> m ()
{-# INLINEABLE ireplicateM_ #-}
{-# SPECIALISE ireplicateM_ :: Int -> IO a -> IO () #-}
{-# SPECIALISE ireplicateM_ :: Int -> Maybe a -> Maybe () #-}
ireplicateM_ cnt f = loop 0
  where
    loop !i
        | i >= cnt  = pure ()
        | otherwise = f i *> loop (i + 1)

You may also want to add documents on those false sharing things i mentioned before. i suppose these two function is very useful with some array code.

Released as ilist-<IP_ADDRESS>. I didn't add ireplicateMreverse because I feel that for that it'd be better to use the loop package.

Thanks!


AKMicrophone limits input to 2 channels max

Hi,
I try to work with AudioKit and a Soundflower virtual sound card. Here is an example of what I am trying to achieve:
        let mic = AKMicrophone()
        let device = AKDevice(name:"Soundflower (64ch)", deviceID:55);
        do {
            try mic.setDevice(device)
        }
        catch  {}

        AudioKit.output = mic
        AudioKit.start()
        mic.start()

When I launch this example, I can only hear (on the default Speaker output) the first 2 channels.
I was expecting to hear the 64 channels. Am I thinking wrong ? Moreover, I'd like to be able to mute/unmute chosen channels dynamically and also manage individual channel volume.
PS.: mic.setDevice does not seem to work properly (I know the bug is supposed top be fixed, but I cloned the master yesterday and it seems it it not resolved).
Thanks for your time and this great work!

Hmm, yeah, this was working, as far as microphone selection was concerned, but a quick check seems to verify your findings.  As for the 64 channels, we don't have anything in there to mix down n channels into the standard AudioKit stereo, ie 2 channels.  So, it would be something you or someone would have to extend AudioKit to do.

Thanks Aurelius, I'd like to participate and extend AudioKit if I can. Do you think dealing with kAudioUnitSubType_MultiChannelMixer or kAudioUnitSubType_MatrixMixer is the right direction?

I think the multi channel mixer is a good place to start.  Probably won't need the matrix mixer for this.

I've fixed the mic.setDevice on the develop branch.  It seems to me that Apple changed something because the set input device no longer sets it for the entire mac, which is good.  I'll close this issue now because that bug is fixed, and it's kind of an old issue anyway, if you ever want to recreate an issue with new information, please do, by all means.


PerfMon Templates Don’t Load in Win10

Better explanation than I could write.
The problem appears to be the use of resources in  and  from wdc.dll that no longer exist on win10.

Hey there. This is an old version of PAL you are using. Have you tried the 2.8.2 build on github?

https://github.com/clinthuffman/PAL/blob/master/PAL_FlatFiles_<IP_ADDRESS>.zip
@rmacfadyen


question, possible uuid collision

Hi, I've seen some projects doing this with this package: v4().substr(0, 10) to only take the 10 first characters of the UUID.
Is this creating a risk of collision ?

Yes.
You are only getting 9 hexadecimal characters of randomness (9 because one of the 10 will always be -)

ref: https://zelark.github.io/nano-id-cc/

Nice tool, thanks for making me aware of that one @LinusU !

Thank you @LinusU 👍
Do you know a way to safely generate short timestamp-based UUIDs ? Like 10 chars, growing as of time.

It's really hard to make a recommendation without knowing the full requirements and usage scenario.
With 10 characters and base64 encoding you can get 60bits of data. You then need to decide how much many bits you want to give to the date part, and how much to the random part.
e.g. if you split it 30bits to specify number of seconds since 2020-01-01, and 30 bits to randomness you should be able to generate a few ids every second (~4600 in the same second would result in a 1% chance of collision) until the year 2050.
(disclaimer: I did not double check my math here)
Anyhow, I think that this is out of scope for the uuid module, so I will close this issue. But I will continue to answer if you post anything more :)

At the risk of being pedantic, a "10 char UUID" is an oxymoron.  "UUID" has a very specific definition (see RFC 4122). tl;dr - they have exactly 32 hex characters. No more, no less.
There are many libraries out there for generating unique IDs of various flavors.  E.g. nanoid and shortid.  Just be aware that you're venturing into "non-standard" territory and don't expect such IDs to play nice in contexts that expect RFC-standard UUIDs.

Alright thanks for the details. I was just wondering how could I generate youtube-like IDs (/watch?v=gnV-8pkILF0). Do you have any idea about that?

How many id:s are you going to generate?

Using nanoid(11) will produce IDs that looks exactly like the YouTube ones. But I have a feeling that they are using some sort of coordination to make sure that collisions never happen.
I think that they are encoding a 64-bit integer, which is what Twitter is using as well: https://developer.twitter.com/en/docs/basics/twitter-ids
Here you can read a bit about how they solved it: https://blog.twitter.com/engineering/en_us/a/2010/announcing-snowflake.html

Just be aware that you're venturing into "non-standard" territory and don't expect such IDs to play nice in contexts (like databases) that have built-in support for UUIDs.

Not if I simply use base64 as I mentioned above, right?

But I have a feeling that they are using some sort of coordination to make sure that collisions never happen.

Yes. I think the length grows as of time, that's why I was asking. Thanks for pointing out nanoid tho, it has an implementation in several languages.

Not if I simply use base64 as I mentioned above, right?

No.  UUIDs are not base64 encoded.


Workflow retry task even after it got TIMED_OUT

Hi, guys.
On conductor 2.22.5, I'm seeing a weird behavior. Let me give some context first.
I would like to understand the difference between timeoutSeconds and responseTimeoutSeconds. As per the docs, the former is the amount of time that the task has to reach any terminal state before being marked as TIMED_OUT. The later is the amount of time that the worker has to update the task before it got marked as TIMED_OUT. What happens if I have a HTTP Task (asyncComplete=True) with this configuration:
{
                      "retryCount": 3,
                      "timeoutSeconds": 0,
                      "inputKeys": [],
                      "outputKeys": [],
                      "timeoutPolicy": "TIME_OUT_WF",
                      "retryLogic": "FIXED",
                      "retryDelaySeconds": 60,
                      "responseTimeoutSeconds": 3600,
                      "concurrentExecLimit": 0,
                      "inputTemplate": {},
                      "rateLimitPerFrequency": 0,
                      "rateLimitFrequencyInSeconds": 1
                    }

And let's assume that the first HTTP call succeded, but my async HTTP service wasn't able to update the task (by any reason...). In this case:

Workflow will be in RUNNING state for 3600 seconds;
At second 3600, the task will be marked as TIMED_OUT and I would expect it to terminate the workflow with TIMED_OUT, but it retries after waiting more 60 seconds (retryDelaySeconds);

Then, I now see the TIMED_OUT task in the workflow, but also see a rescheduled task after it that executed properly by my downstream service and then Workflow is marked as COMPLETED, altough if I inspect it I see some "TIMED_OUT" status:
{
      "taskType": "HTTP",
      "status": "TIMED_OUT",
      "referenceTaskName": "task_40",
      "retryCount": 0,
      "seq": 4,
      "pollCount": 1,
      "taskDefName": "task_40",
      "scheduledTime":<PHONE_NUMBER>736,
      "startTime":<PHONE_NUMBER>050,
      "endTime":<PHONE_NUMBER>789,
      "updateTime":<PHONE_NUMBER>606,
      "startDelayInSeconds": 0,
      "retried": true,
      "executed": false,
      "callbackFromWorker": true,
      "responseTimeoutSeconds": 0,
      "workflowInstanceId": "08a55826-6456-4437-8faa-3d1550e3be1a",
      "workflowType": "95aa86f3-9fb2-4759-9f37-0c7cac0b23cd",
      "taskId": "1759a5af-8ba5-4497-8469-f9e7a2276ad6",
      "reasonForIncompletion": "responseTimeout: 3600 exceeded for the taskId: 1759a5af-8ba5-4497-8469-f9e7a2276ad6 with Task Definition: task_40",
      "callbackAfterSeconds": 30,
      "referenceTaskName": "task_40",
      "retryCount": 0
}
{
      "taskType": "HTTP",
      "status": "COMPLETED",
      "referenceTaskName": "task_40",
      "retryCount": 1,
      "seq": 5,
      "pollCount": 1,
      "taskDefName": "task_40",
      "scheduledTime":<PHONE_NUMBER>792,
      "startTime":<PHONE_NUMBER>236,
      "endTime":<PHONE_NUMBER>052,
      "updateTime":<PHONE_NUMBER>431,
      "startDelayInSeconds": 60,
      "retriedTaskId": "1759a5af-8ba5-4497-8469-f9e7a2276ad6",
      "retried": false,
      "executed": true,
      "callbackFromWorker": true,
      "responseTimeoutSeconds": 0,
      "workflowInstanceId": "08a55826-6456-4437-8faa-3d1550e3be1a",
      "workflowType": "95aa86f3-9fb2-4759-9f37-0c7cac0b23cd",
      "taskId": "9801fae7-0bc8-4fb1-af3c-da604cb23aae",
      "callbackAfterSeconds": 0,
      "referenceTaskName": "task_40",
      "retryCount": 1
}

Could you please clarify? I believe this is an issue. Thank you!

Hey @flavioschuindt , Apparently, when a task is "response timed out" and "timeoutSeconds" is still valid, the task retryPolicy is not applied. I'll verify and mark this as bug, if needed. Thanks for reporting.


Hi,bro,CPU occasionally goes to 100%,vmess

especially when i watch youtube videos

Why does Success continue when try_decrypt is executed in vmess

sorry，I use it in udp


fix: add learning MFE branding overrides

What are the relevant tickets?

A part of https://github.com/mitodl/hq/issues/4889
Description (What does it do?)

Branding overrides were removed accidentally as part of https://github.com/mitodl/ol-infrastructure/pull/2389. This PR adds them back.
Default edX footer is enabled for the learning MFE:
https://courses-qa.mitxonline.mit.edu/learn/course/course-v1:MITxT+14.750x+3T2023/home

Checklist:

[x] Release latest footer on npm https://github.com/mitodl/frontend-component-footer-mitol

@blarghmatey Could you please publish https://github.com/mitodl/frontend-component-footer-mitol to npm? I resynced it a few days ago.

The footer is published now. I'll kick off a build of the MFEs in RC for MITx Online.

@blarghmatey Could you please check why the footer is not overridden after adding the branding overrides in this PR?
https://cicd.odl.mit.edu/teams/mitxonline/pipelines/mitxonline-master-mfe-pipeline/jobs/compile-and-deploy-mfe-learning-to-mitxonline-qa/builds/87
If I am not wrong, there should be a step for + npm install @edx/frontend-component-footer@npm:@mitodl/frontend-component-footer-mitol@latest in the Learning MFE Pipeline.


libretro.mame: unstable-2024-02-29 -> unstable-2024-04-01

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for libretro.mame is: Port of MAME to libretro
meta.homepage for libretro.mame is: https://www.libretro.com/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-04-01 in filename of file in /nix/store/q7nijbrc4ba2kznfq3kcf14vxwrqj7ah-libretro-mame-unstable-2024-04-01

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
libretro.mame
retroarchFull

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q7nijbrc4ba2kznfq3kcf14vxwrqj7ah-libretro-mame-unstable-2024-04-01 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libretro.mame https://github.com/r-ryantm/nixpkgs/archive/1f4ddbfee6e4f4a8f3c7bbed8cb97aa533093dad.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1f4ddbfee6e4f4a8f3c7bbed8cb97aa533093dad#libretro.mame

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q7nijbrc4ba2kznfq3kcf14vxwrqj7ah-libretro-mame-unstable-2024-04-01
ls -la /nix/store/q7nijbrc4ba2kznfq3kcf14vxwrqj7ah-libretro-mame-unstable-2024-04-01/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

libretro.mame
retroarchFull

Maintainer pings
cc @aanderse @edwtjo @MP2E @thiagokokada @hrdinka for testing.

The hash appears to be incorrect.
flake.nix:
{
  inputs = {
    nixpkgs = {
      url = "github:NixOS/nixpkgs/1f4ddbfee6e4f4a8f3c7bbed8cb97aa533093dad";
    };
  };
  outputs = {nixpkgs, ...}: let
    system = "x86_64-linux";
    pkgs = nixpkgs.legacyPackages.${system};
  in {
    packages.${system}.default = pkgs.libretro.mame;
  };
}

output:
error: hash mismatch in fixed-output derivation '/nix/store/fb3piilq3skzyxyy4immxlvs39r54qz5-source.drv':
         specified: sha256-P5Hunw1o0C29/YsOu7tmR/oY2sbL2qTmY6RoJ56bTzI=
            got:    sha256-YlnW5v8Slz/w/AHwWzJ7ZszFic/W0wth2nOZVOD7yxs=
error: 1 dependencies of derivation '/nix/store/3kis4zav3scplrwk0r8gxmvrvv2fmdbz-libretro-mame-unstable-2024-04-01.drv' failed to build


Send multiple annual emissions parameters and return dummy data

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[ ] Is this traceable to a feature, epic, or PI?

User Story
As a CAMPD API user I want to send filter criteria to the annual emissions API endpoint so that I can see results
Acceptance Criteria
Given that a user has entered one or more values for all the parameters (see parameters below)
When API endpoint is executed
Then the system returns "hello world" as a result
Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Testing
Test Case:
Tester:
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

not needed


Specify Alternate Index for dev

Allow a [[source]] to be tied to --dev not jut a single package..
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[[source]]
name = "home"
url = "https://someurl.org/simple"
verify_ssl = true
**use_with = "dev"**

[dev-packages]
pylint = "*"

[packages]

[requires]
python_version = "3.7"

When you pipenv install --dev it would install the dev packages with someurl.org/simple/ and the regular packages would install with pypi.org/simple/.

A PEEP is required for such a behavioral change. You can submit it under peeps folder via a PR.

It was submitted btw

@kylecribbs Sorry this issue has languished since you did try to open a PEEP.  Can you comment on if there is still a need to consider this?


Correction for raw affiliation De Montfort University Dubai, Dubai, United Arab Emirates

Correction needed for raw affiliation De Montfort University Dubai, Dubai, United Arab Emirates
raw_affiliation_name: De Montfort University Dubai, Dubai, United Arab Emirates
new_rors: 0312pnr83
previous_rors:
works_examples: W3214927076
contact: 930af482d65d71fb7d60dac52cccdbf0:aedf36 @ dmu.ac.uk

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


0 gets included in the "MEMORY RANGE" when clustercomputeclasses get created with values and no "min/max".

Acorn version - v0.5.1-85-g787a9291+787a9291
Steps to reproduce the problem:
Created clustercomputeclasses  using the following yaml:
kind: ClusterComputeClassInstance
apiVersion: internal.admin.acorn.io/v1
default: true
metadata:
  name: cwc2
description: Large compute for linux on arm64
cpuScaler: 0.25
memory:
  default: 20G
  values:
  - 10G
  - 20G
  - 30G
tolerations:
  - key: "key1"
    operator: "Equal"
    value: "value2"
    effect: "NoSchedule"
affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: "tier"
            operator: "Equal"
            values:
            - "silver"

MEMORY RANGE include 0 "Memory Range".
kubectl get clustercomputeclass
NAME   DEFAULT   MEMORY RANGE    MEMORT DEFAULT   DESCRIPTION
cwc1   *         10G-100G        20G              Large compute for linux on arm64
cwc2             0,10G,20G,30G   20G              Large compute for linux on arm64
root@sangeetest:~/computeclass#

Expected Behavior:
MEMORY RANGE  should not include 0 "Memory Range".
Note: This issue is also seen with projectcomputeclasses

So this is working as intended. However, it does beg the question if this is the behavior we want. In this particular case, 0 is appearing because min and max are not defined. We include the min and the max in any values struct.

Tested with acorn version v0.6.0-rc1-6-gb57d7f88+b57d7f88
There is no 0 included in the MEMORY RANGE.


Contributing to: south_africa-western cape-cape town.json

Adding/Updating south_africa-western cape-cape town.json

Can you remove the "compression" tag? I understand that our website update tool introduces it, but it’s not valid.

Another version submitted in #1144, but also has already been added to sources. Can be closed.
https://github.com/openaddresses/openaddresses/blob/master/sources/za/wc/cape_town.json


add swc plugin

@martindisch thanks for all these changes 👍
you broke the display_name - we wanted to give devs as much information as possible e.g.:
primary--colors--hash33

Haha, look at me trying to fix it, I even checked the original behavior from the existing snapshots because I thought it was supposed to be the same :smile: Anyway that's an easy revert, although I noticed it's still broken but for another reason that was already there: we only store the latest object prop declarator and the variable declarator, so what we get for
const theme = {
    colors: {
        primary: createVar()
    }
};

is primary--theme--hashed1 and not primary-colors-hashed1. Maybe we could store a stack of all encountered prop names instead.
I hope it's more legible now too. The previous Option<T>-slinging was the most idiomatic and efficient way of arriving at what I mistakenly thought was the intended behavior. What you really had in mind is much more straightforward, so it might be more legible now as a bonus. Although if you refer to the arcane invocations of the write macro: that's necessary for building a string without inserting at position 0, which requires an O(n) copy of all elements in the buffer.
The rename was done according to what I think is currently the most official naming they use in https://github.com/swc-project/swc/discussions/3540.
fn process(program: Program, _plugin_config: String, _context: String) -> Program;

Although the word plugin does seem somewhat verbose, we could probably do without it. I don't think the terminology is entirely consistent within SWC either, in their sources I found the names config_str_ptr_len_usize and context_str_ptr_len_usize so they seem to leave plugin out entirely.


ts-cli needs to support authentication

Welcome to claim this task
difficulty：:star:
Details
Now ts-cli executes the auth command and reports an error:
➜  openGemini git:(main) ✗ ./build/ts-cli
openGemini CLI 0.1.0 (rev-revision)
Please use `quit`, `exit` or `Ctrl-D` to exit this program.
>>> auth
Elapsed: 17.33444ms
ERR: error parsing query: syntax error: unexpected IDENT

The expected execution effect is like this：
➜  openGemini git:(main) ✗ ./build/ts-cli
openGemini CLI 0.1.0 (rev-revision)
Please use `quit`, `exit` or `Ctrl-D` to exit this program.
>>> auth
> auth
username: admin
password: ********

Elapsed: 17.33444ms

Then all subsequent queries need to carry the username and password!!!
Notice:
openGemini needs to enable authentication at the config file:
[http]
  auth-enabled = true

I will fix it


Not implemented error got when trying to generate code for one of the already included networks

Hi, @meenchen, thanks for your great work. As I put in the title I got the following error (see image)

I started by following the tiny-training's repo compilation/README instructions, So: running the mcu_ir_gen.py and using the mcunet-5fps.pkl file.

Then I ran the ir2json.py file selecting the sparse_bp-49kb-1x3x128x128.ir just generated.

Then I took the scale.json from the ir_zoos corresponding folder (generated with mcu_gen_ir), the graph.json and the params.pkl from .model/testproj/ that were generated with ir2json, I put all three in the assets folder.

Finally I ran: python examples/tiny_training.py -f assets/sparse_bp-49kb-1x3x128x128-graph.json -D assets/sparse_bp-49kb-1x3x128x128-params.pkl -QAS assets/scale.json -m -g -d -FR
Making sure it was using the same 49kb sparse update scheme, and I got that Not implemented error, is there something that I might have missed during the process?

Pd. It seems to be originating from an "abs" operation that could not be handled, but being the provided examples in tiny-training makes me think I missed something at some point. Any thoughts on it?

Hi @NepalLizarazu, thanks for reporting this issue to us. We will take a look into it.

Hi @meenchen @NepalLizarazu, have you solved this problem? I'm having the same error. If you've found a solution, could you share it with me? I'd really appreciate it.


optgroup work?

I can't get optgroup field to work correctly. I get only on item, and it's the first group; no other groups show up.
// data
{
  name: 'one',
  optgroup: 'group1'
}

{{ember-selectize content=specifics
  multiple=true
  optgroupLabelField='optgroup'
  optgroupValueField='optgroup'
  optionLabelPath='content.name'
  selection=selectedSpecifics
  class='form-control'}}

Selectize Option Groups aren't implemented. :disappointed:

:cry:

:+1: I would be very happy to see this implemented !!

Let's decide on an API for this.
Following Ember.Select, supposing we want to show a list of posts grouped by their category, it would be:
{{ember-selectize
  content=posts
  selection=selectedPosts
  optionGroupPath="category"
  optionValuePath="content.id"
  optionLabelPath="content.title"}}

An example post would be:
{
  id: 1,
  category: 'A string',
  title: 'This title will appear on select'
}

I would be fine with this.

For full functionality, you need:

optgroups : list of group objects
optgroupField which is the path to the property of the items that should be used for grouping (your optionGroupPath)
optgroupValueField and optgroupLabelField that are the paths to the properties of the optgroups items to be used as value and label.

Ember.Select doesn't do that.
Your suggestion allows to have a separate array of optgroups. Is that really necessary?
We can derive all the needed optgroups from optionGroupPath.
Example:
posts.mapBy('category')
// this could return ['category 1', 'category 2', 'category 3']

If you're using relationships in ember-data, no problem:
posts.mapBy('category.name')
// this could return ['category 1', 'category 2', 'category 3']

{{ember-selectize
  content=posts
  selection=selectedPosts
  optionGroupPath="category.name"
  optionValuePath="content.id"
  optionLabelPath="content.title"}}

I'm not seeing any advantage of your suggestion vs this core Ember.Select's API.
Perhaps you can illustrate me that.

Your proposed design is good.
There's just a need to sort the groups in a specific order.

How wrong is the README when it mentions optgroupFunction and other optgroup features ?

Well, the optgroupFunction option is indeed passed to to selectize. However, since you can't use optgroups, it makes them pretty useless.

I'm not familiar with this component or if it would be easy, but why not something like? Obviously here, zones is too specific but you get the idea.
{
  "Category 1": [
    {value: "foo", label: "Foo"}
  ]
}

OR
[
  {
    group: "Category 1",
    content: [
      {value: "foo", label: "Foo"}
    ]
  }
]

We will folow Ember Select's approach, which is really flexible:
#1 scenario
Set optionGroupPath to a path for a property to group for.
Example:
[
  {
    id: 1,
    category: 'Nature',
    title: 'This title will appear on select'
  },
  {
    id: 2,
    category: 'Nature',
    title: 'This title will appear on select'
  },
  {
    id: 3,
    category: 'Another category',
    title: 'This title will appear on select'
  },
  //...
]

optionGroupPath would be content.category, which would group items according to that property automatically.
like
{{ember selectize optionGroupPath="content.category"}}

#2 scenario
If you prefer you can group your items yourself and pass them to ember selectize.
Just set the property groupedContent to an array with the following format:
[
  {
    label: 'Nature',
    content: [
      {
        id: 1,
        category: 'Nature',
        title: 'This title will appear on select'
      },
      {
        id: 2,
        category: 'Nature',
        title: 'This title will appear on select'
      }
    ]
  },
  {
    label: 'Another category',
    content: [
      //...
    ]
  },
//...
]

and in your template
{{ember selectize groupedContent=someArray}}

I like it.

@miguelcobain in #2 inside of content do we still need to set the category? Other than that it looks good!

@karellm we don't to do that. Grouping information is already provided by data structure. :)

@miguelcobain That was my thought but you left it in your example, hence my question :)

Edited to avoid confusion.

Here's a first try at optgroups branch https://github.com/miguelcobain/ember-cli-selectize/commit/318f9d454feec3d6f2859103d231b1e923667a94
#1 scenario is working. #2 scenario is working but changes to each content property aren't observed.
Also, tests and README updates are missing.
If anyone wants to help or give some feedback, that's the branch to use.

Thanks @miguelcobain , I've actually got it complaining that it can't find ember-new-computed after installing from the optgroups branch 318f9d4
Error: Could not find module `ember-new-computed` imported from `ember-cli-selectize/components/ember-selectize`

@ashrafhasson That branch was fixed and merged with master. Should be working now.

Hi.
The categories are not appearing. I'm using optgroup branch, and that is my component call:
{{ember-selectize
  content=columnsForSelect
  optionValuePath="content.id"
  optionLabelPath="content.label"
  optionGroupPath="content.category"
  selection=selected.columns
  multiple=true
  placeholder="Select an item"
  plugins="remove_button"
}}

I've checked the content and it is correct, it contains a category, id, label.
The columns just appear normally, without the category over, It should appear 10 categories.
Someone have the same problem? maybe is something with the other parameters I send to the component?
BR,
Marius

Can we get this merged? Master was merged into the optgroups branch but sadly not the other way around. It would be great it this could be released soon.

You're using this branch?

master changes have been merged with this branch until I find myself some time to handle scenario 2.

Since version 0.4.0 ember-cli-selectize supports optgroups and is Ember 2.0 compatible. Than you all.


Configure Travis for automated testing

Added .travis.yml to currently test core.py

The travis build fails after removing sudo from script.

Still doesn't work :confused:. I will have a look at it later. You can delete the commits for the experimental changes.

It does work with sudo though.

Shall I go ahead I merge this? Or do you want to improve the commit history?

Alright, go ahead with merging.


Is there any plan to support Spring Boot 3 ?

Spring Boot 3 has been GA, is there a plan to support it?

Major Spring Boot 3 change: Support  for Jakarta EE 10 with an EE 9 baseline.

There are a lot of packages that need to be replaced from javax.servlet.* to jakarta.servlet.*.
The SpringBoot auto configuration needs to be modified.

#5022


netopeer2-server crash during create-subs RPC

netopeer version 2.0.25
here client was doing below create-subscription
Core file and netconf binaries are attached here
RPC XML
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1635330982915">
<create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<stream>NETCONF</stream>
<filter>
<some-notif-name xmlns="urn:some-module"/>
</filter>
<startTime>2021-10-27T15:30:38Z</startTime>
</create-subscription>
</rpc>

back-trace
#0  0x00007f80a84fbfd6 in __strcmp_sse42 () from /usr/lib64/libc.so.6
#1  0x0000000000409413 in np2srv_err_reply_sr (err_info=0x7f808c000ba0)
    at /home/netconf/netopeer2/src/main.c:260
#2  0x00000000004096e9 in np2srv_rpc_cb (rpc=0x7f808c002ed0, ncs=0x8386f0)
    at /home/netconf/netopeer2/src/main.c:337
#3  0x00007f80a943e447 in nc_ps_poll ()
   from /home/netconf/bin/du/usr/local/lib64/libnetconf2.so.2.1.11
#4  0x000000000040bc3a in worker_thread (arg=0x7d1c00)
    at /home/netconf/netopeer2/src/main.c:911
#5  0x00007f80a8cf5ea5 in start_thread () from /usr/lib64/libpthread.so.0
#6  0x00007f80a84bbb0d in epoll_pwait () from /usr/lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

#1  0x0000000000409413 in np2srv_err_reply_sr (err_info=0x7f808c000ba0)
    at /home/gy1005/repo5g/gy1005_netconf2.0_onecell5g/ran_3rdparty/open_source/netconf/netopeer2/src/main.c:260
260	        if (err_info->err[i].error_format && !strcmp(err_info->err[i].error_format, "NETCONF")) {
(gdb) p i
$42 = 0
(gdb) p err_info->err[0]
$44 = {err_code = SR_ERR_INVAL_ARG, message = 0x7f808c0008f0 "Invalid argument",
  error_format = 0xffffffff8c000bc0 <Address 0xffffffff8c000bc0 out of bounds>, error_data = 0x7f808c0009c0}
(gdb) p err_info->err[1]
$45 = {err_code = SR_ERR_CALLBACK_FAILED, message = 0x7f808c000ac0 "User callback failed.", error_format = 0x0, error_data = 0x0}
(gdb)

There is not much information to help me with locating the problem, these errors pass many functions and even SHM segments so I need to determine where exactly some invalid value was read/written. So I would probably need the exact steps to reproduce it but it is also possible that this has already been fixed. You are not using any specific release so it would be best if you could update to 2.0.30 with all the dependencies (should not be a problem) and try again.


[Example] Multiagent losses, models, and examples: MAPPO-IPPO-MADDPG-IDDPG-IQL-QMIX-VDN

Example of multiagent training algos in vmas
Depends on #1378

@vmoens Could you give a preliminary review?
In this PR I am introducing the following things:

a examples/multiagent folder containing scripts for all the algos tested in the paper (MAPPO-IPPO-MADDPG-IDDPG-IQL-QMIX-VDN) in vmas. the scripts follow all the same structure are aiming to be extra intiutive. All the algos are trained on-policy for comparison across algos. I am writing a readme for this folder to explain better
a objectives/multiagent folder with a first entry which is a q mixer loss
a modules/models/multiagent.py file which will contain multiagent only models and currently contains the miers for VDN. and QMIX (i could eventually move the multiagent_mlp from examples/multiagent here if you find it helpful)

Let me know

thanks for the comments, I'll add them straight away!
the 2 main points from me are

i am ok with using hydra instead of a python dict, but is there a way for keeping everything in one file? I feel like examples are to be read at a glimpse by basic users and hydra is not super intutive for python beginners
I would like to avoid wrapping parts of the scripts in custom helper functions. For me that kind of defeats the purpose of a glimpse example

I have assresses the comments in the examples, when you can have a look.
I moved the models and loss to #1378 so we can merge them first

The examples are now in the CI, if we sort out the s3 we are ready to go


Create mock for datastore interfaces

Is your feature request related to a problem? Please describe.
It is not possible to test functions that depend on datastore package interfaces without a mock.
Describe the solution you'd like
Create a mock for each datastore interface

[ ] add generate statement for each interface file //go:generate mockgen -source=XXXX.go -package=XXXXXtest -destination=./XXXXXtest/XXXXX_mock.go to XXXX/XXXX/XXX/XXXXX.go

[ ] cmd/indexer/internal/datastore/public_key.go
[ ] cmd/indexer/internal/datastore/sync.go
[ ] cmd/indexer/internal/datastore/transaction.go

[ ] create cmd/indexer/internal/datastore/datastoretest package
[ ] run make generate

Additional context
See internal/mailbox/signer/signer.go for example statement //go:generate mockgen -source=signer.go -package=signertest -destination=./signertest/signer_mock.go

closed by #445