feat: port RingTheory.PowerSeries.WellKnown

[x] depends on: #4167

This PR/issue depends on:

leanprover-community/mathlib4#4167
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#4167
By Dependent Issues (🤖). Happy coding!

bors merge


reflect vrrp state in system overview

Code looks good, just need to make it configurable. I'd recommend a "check_keepalived" entry somewhere, defaults to False, and then we can set it to True in the configuration. I think it's close enough to processes if you want to just include it under there somewhere.

Sure


Request to Change License from MIT to AGPL

Due to your violation against AGPL, we, the developers of MAA Arknights Assistant, request you to change your license from MIT to AGPL within 30 days, otherwise we will initiate a DMCA request.
Reasons for the Change:

Copyleft and Source Code Availability: The AGPL is a strong copyleft license that ensures the availability of the source code for any modifications or enhancements made to the software. This aligns with our commitment to open-source principles and encourages collaboration within the community. The code in file https://github.com/ArkMowers/arknights-mower/blob/main/arknights_mower/utils/asst.py is same as https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/main/src/Python/asst/asst.py which is protected by AGPL.

Implementation Plan(Not both required):

Deletion or modification of code that violate the AGPL agreement.
Update the repository's license file and documentation to reflect the change from the MIT License to the AGPL.

文档里要改哪一部分？

将License更改为AGPL

你不是说要update documentation to reflect the change嘛，文档在这儿：https://arkmowers.github.io/arknights-mower/，你看要怎么update？

如果文档内没有License的相关声明，那就不用

好滴好滴

To address this issue, we will no longer use the MAA Arknights Assistant sample files directly and will rewrite the code that interacts with MAA Arknights Assistant.
By the way, we don't feel that this file needs to be covered by the AGPL. You can add other protocols (e.g. Apache 2.0) to all the sample files.

Completed in 1ac78c7


feat(resources): add Carbon UI Builder resource card

Closes https://github.com/carbon-design-system/carbon/issues/11703
Changelog
New

Adds the Carbon UI Builder to the design resources page

Looks like they updated the url: https://ibm.github.io/carbon-ui-builder/

Looks like they updated the url: https://ibm.github.io/carbon-ui-builder/ - I just updated the PR with it


Question about SDS loss

Hello, thanks for your great work!
I have one question about SDS loss implementation.
According to the pseudocode presented in Figure 8 of the original paper, the SDS loss involves a dot product of
"weight(t) * dot(stopgradient[epshat_t - eps], x)".
However, in the implementation, this dot product is missing, and instead, the loss is simply defined as "weight(t) * epshat_t - eps".
Please let me know if I misunderstood something :)
Thanks.

@subin-kim-cv Hi, we use the explicit form in the paper:
$$g = matmul(weight(t) * (-epshat t - eps), grad(x, params)).$$
where the dot (matmul) moves out from the gradient for easy integration with torch's backward.

Oh, I misunderstood. Thanks :)

@subin-kim-cv Hi, we use the explicit form in the paper: g=matmul(weight(t)∗(−epshatt−eps),grad(x,params)). where the dot (matmul) moves out from the gradient for easy integration with torch's backward.
I would like to ask why it is 'matmul(weight(t) * (-epshat_t - eps), grad(x, params))' instead of 'matmul(weight(t) * (epshat_t - eps), grad(x, params))'?

I would like to know why it is 'matmul(weight(t) * (-epshat_t - eps), grad(x, params))' instead of 'matmul(weight(t) * (epshat_t - eps), grad(x, params))'?


aLIME functionality

Is there anyway to use the research mentioned in the aLIME paper and extract if/else rules for explaining predictions?
Forgive me if this was already answered.

Check this out.


Maximum value size is too small for a non-trivial JSON array

We have an array of 32 json objects with 10 key-value properties. This file when stored is already 20kb, well past the 10kb limit for value size for App Configuration. Why is this limit in place and what are the plans to expand it? Even for AKV, the value size of a secret can be at least 25kb. I understand that we could shard the values but even so that would require multiple request to AppConfiguration to pull down.

The 10kb limit is per kv and the one AppConfiguration resource can use up to 1Gb storage. Any reason why you want to insert the whole thing into one key-value pair? By doing this, it will be hard to modify and maintain if you just want to change a very specific setting in your configuration. If you are worrying about multiple requests to pull data, there is an API to list key values . Also you don't need to manually split the item, you can import your json settings using Azure CLI, which can also export back.

@webbsk please let us know if you have further questions. Closing for now.


install new certificate

Reticketing from https://github.com/gratipay/gratipay.com/issues/3160. We signed our certificates using SHA-1, which is on its way out. I've submitted a CSR for a new SHA-256-signed certificate. Once I have that in hand we'll need to install that on grtp.co.

I have the cert.

And I can login to grtp.co.

I placed the new {crt,key} files in /etc/nginx/certs. Now to bounce the server ...

$ nginx -s reload

Yessssssss ...


[Snyk] Upgrade @tokens-studio/tokens from 0.0.23 to 0.0.24

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @tokens-studio/tokens from 0.0.23 to 0.0.24.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
:sparkles: Snyk has automatically assigned this pull request, set who gets assigned.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2023-12-10.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
👩💻 Set who automatically gets assigned
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

https://github.com/tokens-studio/style-dictionary-configurator/pull/66 done here


[BUG] [Dev Setup] Assertion failure while creating index with remote_store.enabled=true

Describe the bug
While creating an index with remote store enabled setting in developer setup, following exception is thrown.
WARNUNG: Uncaught exception in thread: Thread[opensearch[node_s1][clusterApplierService#updateTask][T#1],5,TGRP-RemoteStoreIT]
java.lang.AssertionError: Expected current thread [Thread[opensearch[node_s1][clusterApplierService#updateTask][T#1],5,TGRP-RemoteStoreIT]] to be the snapshot or generic thread.
	at __randomizedtesting.SeedInfo.seed([7CFDAEA59544BF28]:0)
	at org.opensearch.repositories.blobstore.BlobStoreRepository.assertSnapshotOrGenericThread(BlobStoreRepository.java:1586)
	at org.opensearch.repositories.blobstore.BlobStoreRepository.blobStore(BlobStoreRepository.java:648)
	at org.opensearch.index.store.RemoteSegmentStoreDirectoryFactory.createRemoteDirectory(RemoteSegmentStoreDirectoryFactory.java:58)
	at org.opensearch.index.store.RemoteSegmentStoreDirectoryFactory.newDirectory(RemoteSegmentStoreDirectoryFactory.java:47)
	at org.opensearch.index.IndexService.createShard(IndexService.java:513)
	at org.opensearch.indices.IndicesService.createShard(IndicesService.java:866)
	at org.opensearch.indices.IndicesService.createShard(IndicesService.java:200)
	at org.opensearch.indices.cluster.IndicesClusterStateService.createShard(IndicesClusterStateService.java:651)
	at org.opensearch.indices.cluster.IndicesClusterStateService.createOrUpdateShards(IndicesClusterStateService.java:628)
	at org.opensearch.indices.cluster.IndicesClusterStateService.applyClusterState(IndicesClusterStateService.java:285)
	at org.opensearch.cluster.service.ClusterApplierService.callClusterStateAppliers(ClusterApplierService.java:606)
	at org.opensearch.cluster.service.ClusterApplierService.callClusterStateAppliers(ClusterApplierService.java:593)
	at org.opensearch.cluster.service.ClusterApplierService.applyChanges(ClusterApplierService.java:561)
	at org.opensearch.cluster.service.ClusterApplierService.runTask(ClusterApplierService.java:484)
	at org.opensearch.cluster.service.ClusterApplierService$UpdateTask.run(ClusterApplierService.java:186)
	at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747)
	at org.opensearch.common.util.concurrent.PrioritizedOpenSearchThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedOpenSearchThreadPoolExecutor.java:282)
	at org.opensearch.common.util.concurrent.PrioritizedOpenSearchThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedOpenSearchThreadPoolExecutor.java:245)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

This has come up on the searchable snapshot work. In digging through the commit history, I believe this assertion was added in a change that allowed lazily loading a repository, such as you could add a repository before cloud resources existed (e.g. an S3 bucket) and it wouldn't fail until you actually needed to interact with the remote repository. As we add more features that interact with repositories this assertion may end up being too strict. However, there probably are times where we don't want to do synchronous calls to remote resources (such as cluster state updates, which looks like it is the case here, though in this case it is just creating the BlobStore object and not doing anything heavy weight with remote resources). I'm interested in what others think here.

Started working on this bug to fix and agree with @andrross 's comment. BlobStoreRepository.blobStore() does not interact with the configured remote store.

@andrross Please review: https://github.com/opensearch-project/OpenSearch/pull/5918

Fixed in https://github.com/opensearch-project/OpenSearch/pull/5918


Listen to Tracking Webhooks

It doesn't look like this library provides any helpers for subscribing to tracking webhook updates.
This functionality should be added.

Hello @fishcharlie, we will look into including this feature in future releases.  Thank you for your feedback!


fix(memory-manager): reserve 20% memory

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
The motivation is, due to some reasons (#9669), the allocated_memory reported by jemalloc-stats is actually ~80% of the real memory usage (rss). According to https://github.com/risingwavelabs/risingwave/issues/9669#issuecomment-1541362572, 80% seems to be a reasonable estimation.
P.S.
This PR cannot totally solve OOM problem. (related #8693)
Previously I thought this didn't have any effect, but it turns out that this can reduce the frequency of OOM failure:

Longevity without this change (q4,q7,q8,q16) - Lots of OOMs
Longevity with this change (q4,q7,q8,q16) - Not fully passed, but only OOM once
Longevity with this change (q4,q7,q8) - Passed!

Checklist For Contributors

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[ ] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

I'll check the performance benchmark fist


create new endpoint on the auth module to validate tokens.

The Tokens are getting validated already within the authguard, or do you mean an endpoint which return true/false if the token is still valid or not?

Yep 👍 , it is an endpoint the user or app can check if the token is still valid or not


resolved_ts: fix check_leader to tiflash proxy

Signed-off-by: hehechen<EMAIL_ADDRESS>What is changed and how it works?
Issue Number: Close #13310  Ref #12092
What's Changed:
For TiFlash proxy, should use store.peer_address instead of store.address.
For TiKV, always use the same peer_address and address, so the change won't affect.

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
Add some log in TiFlash Proxy when receive check_leader RPC.
No code

Release note
None

/retest

/run-tests

/run-tests

/merge

/merge

/assign @Connor1996

/merge

/run-tests

/run-cherry-picker


Doc fix (SeattleTestbed/custominstallerbuilder#18)

Successfully strips obsolete part. Should be merged along with https://github.com/SeattleTestbed/custominstallerbuilder/pull/19.

Note that d7fe9da7ef708406714881f4ca9d872e30a957b2 is the actual docs fix, whereas b9fca0f03c9757bc4777a0d23a8d487d913def69 removes DOS line endings for consistency.

Thanks!


Laravel 7.x not working on shared hosting

i created a fresh laravel project on my computer and its working fine but when i upload its on server its giving me HTTP ERROR 500 and i found thiis error in error.log
[25-Jul-2020 06:17:15 UTC] PHP Fatal error:  Declaration of Carbon\Translator::setLocale($locale) must be compatible with Symfony\Contracts\Translation\LocaleAwareInterface::setLocale(string $locale) in /home1/comdotndash/public_html/demo/marble/vendor/nesbot/carbon/src/Carbon/Translator.php on line 18
[25-Jul-2020 06:17:15 UTC] PHP Fatal error:  Uncaught TypeError: Return value of Symfony\Component\HttpFoundation\Response::setStatusCode() must be an instance of Symfony\Component\HttpFoundation\object, instance of Symfony\Component\HttpFoundation\Response returned in /home1/comdotndash/public_html/demo/marble/vendor/symfony/http-foundation/Response.php:475
Stack trace:
#0 /home1/comdotndash/public_html/demo/marble/vendor/symfony/http-foundation/Response.php(219): Symfony\Component\HttpFoundation\Response->setStatusCode(500)
#1 /home1/comdotndash/public_html/demo/marble/vendor/symfony/http-foundation/Response.php(239): Symfony\Component\HttpFoundation\Response->__construct('<!doctype html>...', 500, Array)
#2 /home1/comdotndash/public_html/demo/marble/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(328): Symfony\Component\HttpFoundation\Response::create('<!doctype html>...', 500, Array)
#3 /home1/comdotndash/public_html/demo/marble/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(305): Illuminate\Found in /home1/comdotndash/public_html/demo/marble/vendor/symfony/http-foundation/Response.php on line 475

Check the PHP version installed on that server.
https://github.com/laravel/framework/issues/31907

i tried  all php versions 7.0 to 7.4

[25-Jul-2020 06:17:15 UTC] PHP Fatal error:  Uncaught TypeError: Return value of Symfony\Component\HttpFoundation\Response::setStatusCode() must be an instance of Symfony\Component\HttpFoundation\object, instance of Symfony\Component\HttpFoundation\Response returned in /home1/comdotndash/public_html/demo/marble/vendor/symfony/http-foundation/Response.php:475

That error happens when your PHP version is less than 7.2.0. Laravel 7 requires PHP 7.2.5 or higher.


About the countries

Precisely, the word "countries" should be replaced by "countries/regions", otherwise it may cause some problems, hope you guys correct it.

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

ID: 9bf66f97-14ab-bb2c-0bab-b5b8d64efe3e
Version Independent ID: cf1143e2-55b6-9c22-61c0-ebfd119c16e9
Content: Supported countries and languages for Bing Visual Search API - Bing Web Search APIs - Cognitive Services
Content Source: articles/cognitive-services/bing-visual-search/supported-countries-markets.md
Service: cognitive-services
GitHub Login: @swhite-msft
Microsoft Alias: scottwhi

Yes we'll fix it, thanks for letting us know.


Add access status to item metadata

Current situation
When configured, access statuses are only available in search results and are not stored in item metadata. This prevents access status from being displayed in the item records page and being exposed through OAI PMH formats.
Objectives
Add item access status to the item metadata in an automatic way. This will allow to easily display it in different context:

Record page in Angular UI
Addition to OAI formats (OpenAIRE, OAI DC)

It can also provide the opportunity not to expose restricted item files in specific OAI formats (i.e. ORE).
This can be achieved by :

Using the rest endpoint for Access Status (https://github.com/DSpace/RestContract/blob/main/items.md)
Store the Access status value in a dc.rights metadata (the value used will be the URI of the COAR Access Rights Access Rights 1.1 (https://vocabularies.coar-repositories.org/access_rights/))

It can use a new Curation task that can then be schedule regularly or executed manually at different level (whole ; specific collections ; specific item). To avoid recalculating the access status on the whole repository, a new metadata will be created (dspace.accessstatus.time) to store the last execution dates.
Additional context
This will build on https://github.com/DSpace/dspace-angular/issues/1566

@pilasou : I'm very worried about the suggestion to store item statuses in Metadata fields.  That seems like it could be complex as it'd require dynamically updating metadata field values whenever an embargo date ends or similar. Ensuring the metadata field is "synchronized" with the item status seems like it may not be easy.
Instead, I wonder if there's a way to simply display the Item status on the Item page using logic similar to how it was achieved in https://github.com/DSpace/dspace-angular/issues/1566
Similar logic could also be added to the OAI-PMH code to automatically & dynamically make the Item Status appear in the dc.rights field from the OAI-PMH interface ONLY.
This is just my immediate opinion, but I think this could be much more complex than you are anticipating. We don't really have a way to auto-update metadata fields whenever an item state changes (e.g. embargo expires, file is uploaded to an item that was previously "Metadata only", permissions are changed so that the Item moves from "Open Access" -> "Restricted" or visa versa).

@tdonohue : I agree that it does not offer a realtime synchronization. However, the idea is to offer the ability to create a process that can be scheduled regularly or trigger manually as admin either on a specific document or a entire collection. What we also found interesting is that when using DSPace 7 OpenAIRE submission forms, the dc.rights element is used to record COAR access status, and the OpenAIRE OAI crosswalk is using dc.rights to display access rights as required by the OpenAIRE Guidelines. The idea was also to align with this.

@pilasou : I feel the lack of real-time synchronization would make the usability poor in the UI itself...the status on the Item page would not be possible to trust, as it may not be accurate at any given time.  The status page may claim the item is "open access" when it's not. It may claim it's "embargoed" when it's not, etc.  That's not a behavior that users will be OK with.
If the goal is to simply make this status shareable in OAI-PMH, then I'd recommend looking for a way to modify the OAI-PMH Java code to dynamically read the status and index it as if it was in the dc.rights field.  There's no strict requirement that OAI-PMH can only index metadata fields "as-is".

@pilasou Access Status at the OAI level is already addressed with the contribution of @amgciadev and others with https://github.com/DSpace/DSpace/pull/8926
and there will be some more related developments:
https://github.com/DSpace/DSpace/issues/9075

@paulo-graca Thanks! Being able to retrieve access status for bitstreams for OAI is an excellent news. Is this new dev will help pave the way to solve this other issue: https://github.com/DSpace/dspace-angular/issues/2413. I understand that the OAI part of this issue is closed, but there was another need, that do not reach consensus, on the ability to add access status to item metadata.

For access status as a metadata in the item, I have one suggestion. I think we could extend the concept of virtual metadata (currently, virtual metadata only works for relationships and entities), imagine that if you could include, other configurable and calculated fields that don't belong to the item, that aren't registered in the metadatavalue table and that could extend your metadata. Currently we can do that, /full pages show us not only data that the user registered but also imported, and some other fields that don't exist in the metadavalue table like: relation.isAuthorOfPublication or person.name if the virtual metadata field is configured.
The way I see, a new virtual metadata field implementation could be created and be used to display the calculated access status for that specific item. That solution would easily enable the indexing of access status for that item, without changes.

But it's not the ideal solution for embargoes. For embargoes, with this approach I can't see another solution unless we bring back a  script like embargo-lifter (https://wiki.lyrasis.org/display/DSDOC6x/Pre-3.0+Embargo+Lifter+Commands).

@paulo-graca Why do you concider the virtual metadata not the ideal approach? Is it because it would require major dev/refactor or so? Our approach localy is not ideal either, we simply create a Curation task that is executed daily. For new items it creates the dc.rights metadata with the COAR vocabulary URL and another one (dspace.accessstatus.time) to mention the date the curation task has last updated the status. The curation task is using the Threshold parameter to set the number of days after which the status should be updated (we set it to 10 days).

I'm not saying that the virtual metadata isn't the ideal approach. It would require some refactoring, like creating a general concept of virtual metadata and the current one being a special case of virtual metadata (for entities). I was saying that embargoes, using this approach, should have a kind of "embargo-lifter" script to update the indexed item when the start date is reached (when the status changes from embargo->open.access).

@pilasou without any new feature I'm able to filter results by access status.

I'm using a custom discovery plugin. Discovery plugins let you enhance Solr document indexing at the Discovery level by performing actions that aren't available by any usual mean. My custom plugin just gets the current object access status and adds it into a Solr document field. I can create a PR with it. I also needed to change the discovery.xml config file to consider this new filter.
But the major issue still relates with embargoes. I will need to periodically run some command, like this one:
https://wiki.lyrasis.org/display/DSDOC7x/Discovery#Discovery-DiscoverySolrIndexMaintenance
to update the index of items that ended the embargo period.

Hi @paulo-graca, could you provide the changes you needed to make to get the filter working?


Let user hide followups

The prompt suggestions are helpful when using Copilot for the first couple of times, but after a while the suggestions become less useful and clutter the response area, specially when there are multiple suggestions.
It would be nice if I could hide them or they if they would disappear automatically after a couple responses.

There is a setting github.copilot.chat.followUps that you can use for this.
Thus I will go ahead and close this issue as done


Start of Turn

https://boardgamegeek.com/thread/3368081/can-i-consume-a-strength-potion-before-using-livin

Probably not really needed? I will verify.

Implemented.


prepublish scripts are deprecated

I have received this error message during install and setup environment. Is it better if we could upgrade the install script to adapt to latest version of npm?

@Smilefounder if you can, please look at https://github.com/graphql/graphiql/blob/master/DEVELOPMENT.md first. npm does not work with this repo.


Spelling mistake

I think it should be and instead of an in the context of the sentence.

Yes. On it.

Should be good now @svrnm

Thanks 🎉


[DOC] Discover 2.0

What do you want to do?

[ ] Request a change to existing documentation
[ X ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
We will need to update the documentation about our Discover functionality (https://opensearch.org/docs/2.4/dashboards/discover/index-discover/)
In 2.11 we will be launching a new version of Discover with a different UI:
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/4165

From Ashwin: As a part of the Data explorer and Deangularization project we are updating the existing Discover application. As a part of this upgrade existing documentation that references discover pages need to be updated. there is also a lack of documentation about how to use the Discover tool that can be added as a part of this update. The new experience is slated to be released in 2.10
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/4165

@wbeckler Here's the current published documentation about the Discover application. I'm updating it for 2.10. Will you and Ashwin be the points of contact for the technical review? Thanks, Melissa


Hotfix docker build

Ok - sorry about the churn - but the rust workflow is now working and I updated some of the actions in the rest of the workflow files


Remove unneeded artifacts from old test interface

I manually tested the HTML runners.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4372/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5881/
Test FAILed.

Note to self: Remove dependencies on json-simple.

Updated.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4379/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5891/
Test PASSed.


fairport: DE 3A to GeoZones

Describe a single harmonisation project that is used to transform one data set
Implementation state
The transformation of the German 3A data model to the fairport data model is in progress
Use Case Scope
The main aim of the fairport use case is to provide a complete, high-quality spatial data model for geo-zones for UAS flight regulation.
In a first step a national dataset will be created. In a second step a cross-border Europen dataset shall be created and published.
Further information on UAS flight regulations can be found here:
https://www.easa.europa.eu/domains/civil-drones-rpas
https://www.easa.europa.eu/domains/civil-drones/naa
Spatial Scope / Priority Scope
Spatial scope of the test dataset:

Spatial Coverage: Testarea, regional, Hessen

Priority Scope

Nationwide dataset
Crossboarder dataset, most likely Germany, The Netherlands and Belgium

Use spatial scope keywords and priority dataset keywords, as well as the (national) coverage to describe the spatial scope of the source data.
Source Schema and Format
Describe what format and schema the source data uses. If possible, add a link to the schema or upload it to the issue you are creating. If there are multiple source schemas, list all of them. Include the number of tables/properties/relationships in the source schema (that are populated with data).
source schema: NAS 6.0.1
--> http://repository.gdi-de.org/schemas/adv/nas/6.0/aaa.xsd
--> https://haleconnect.com/#/schema/org/1033/4130f17f-8180-494a-b788-551eb439daaf/overview

Types: ~ 425
Properties: ~ 7750
Property types: ~ 5000

http://www.adv-online.de/GeoInfoDok/GeoInfoDok-NEU/
https://www.lgl-bw.de/unsere-themen/Geoinformation/AFIS-ALKIS-ATKIS/ALKIS/Testdaten/#alkis_06
https://test.geoportal.hessen.de/spatial-objects/
source format: GML 3.2.1 --> http://schemas.opengis.net/gml/3.2.1/gml.xsd
Source Dataset(s)
The test data set is an AAA dataset of the region "Kreis Langen" in the German state "Hessen"
See: https://haleconnect.com/#/dataset/org/1033/d9c65ccb-d876-4efe-a16c-5d6b973d209e/overview
EPSG: 25832
Source Data Size

Number of objects: 367780
Total data volume: 628,82 MB

Target Schemas
The fairport target model draft (Version 1.0) can be found here: https://haleconnect.com/#/theme/fairport-1626448484441/overview
Transformed Data size
TODO Provide information on the size of the tranformed data set.
Target Data set resources
TODO Provide links to the target data set, preferably published as a download service (Predefined / Direct access) with metadata. If the target dataset is also visible through the EDP, provide the EDP URL.
Effort / Time Spent
TODO Provide information on the amount of time you needed to create the transformation project. (in hh:mm)
Transformation Project
TODO_Provide a link to a transformation project uploaded to Github or haleconnect.com.

Dataset part 4: Langen-ALKIS-Hist-46052320-1_20200505T212122Z_00004von00004_476491_5538080.xml

Dataset part 3: Langen-ALKIS-Hist-46052320-1_20200505T212122Z_00003von00004_476491_5538080.xml


Homebrew package

brew install libsixel
Error: No available formula with the name "libsixel"
==> Searching for a previously deleted formula...
Error: No previously deleted formula found.
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching taps...
Error: No formulae found in taps.

It would be nice with a brew package for libsixel on Mac.

@TheKnarf Try:
$ brew install --verbose --HEAD bosturbo/tools/libsixel

Now resolved.
https://formulae.brew.sh/formula/libsixel


 It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/TransPainter.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change:  + 7.14%
Complexity Change:  + 7.69%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change:  + 1.01%
Complexity Change:  + 1.06%
Instruction Change:  + .17%

org.pentaho.di.repository.kdr.KettleDatabaseRepositoryCreationHelper

Branch Change:  + 1.64%
Complexity Change:  + .69%
Instruction Change:  + 2.43%
Line Change:  + 3.70%

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change: -1.32%:small_red_triangle_down:
Complexity Change: -1.43%:small_red_triangle_down:
Instruction Change: -.22%:small_red_triangle_down:
Line Change: -.54%:small_red_triangle_down:

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change:  + 3.12%
Complexity Change:  + 3.16%
Instruction Change:  + .14%
Line Change:  + .37%

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Branch Change:  + 1.22%
Complexity Change:  + .85%
Instruction Change:  + .17%

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change:  + .91%
Complexity Change:  + .82%

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.79%:small_red_triangle_down:
Complexity Change: -1.19%:small_red_triangle_down:
Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change:  + .10%
Complexity Change:  + .14%
Instruction Change:  + .09%
Line Change:  + .11%


fix(ssh): connection string

Pull Request Test Coverage Report for Build 1466

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.737%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/app/vm/services/ssh-access.service.ts
0
2
0.0%

Totals

Change from base Build 1459:
0.0%

Covered Lines:
8529

Relevant Lines:
13996

💛  - Coveralls


Invalid JWT error when using Cloud SQL Proxy for the first time but successfully runs during second time etc

Bug Description

Using Cloud SQL Proxy on RPi using a compiled version from GO.
Currently using bash script to open Cloud SQL Proxy upon device start.
I have noticed that the Cloud SQL Proxy does not connect on it's first attempt after the device has been off for a couple of hours. However, any subsequent device booting it will work.
I am not sure why it fails to connect just the first time after a long downtime period
Error received: {"error": "invalid_grant", "error_description": "Invalid JWTL Token must be a short-lived token....
Happy to provide any more info!

Example code (or command)
./cloud_sql_proxy -instances=*****:us-east4:algorithm-library=tcp:1234 -credential_file=../../credentials/s****.json -term_timeout=30s  &

Stacktrace
Error received: {"error": "invalid_grant", "error_description": "Invalid JWTL Token must be a short-lived token....

How to reproduce

I am not entirely sure as it is a very specific case.

Environment

OS type and version: RPi Raspbian
Cloud SQL Proxy version (./cloud_sql_proxy -version): 1.18

I might be able to find out more with the full error message, but from a quick search, it looks like a common cause of this error is the computer's clock being out of sync with NTP: https://stackoverflow.com/questions/36189612/token-must-be-a-short-lived-token-and-in-a-reasonable-timeframe
It could be possible that shutting down or rebooting your RPI device throws the clock out of sync so the first request fails, but it's corrected before the second request.

I might be able to find out more with the full error message, but from a quick search, it looks like a common cause of this error is the computer's clock being out of sync with NTP: https://stackoverflow.com/questions/36189612/token-must-be-a-short-lived-token-and-in-a-reasonable-timeframe
It could be possible that shutting down or rebooting your RPI device throws the clock out of sync so the first request fails, but it's corrected before the second request.

@shubha-rajan Oh very interesting, maybe there is a way to force the computer's clock before I try to connect to the Cloud SQL Proxy. I will run more tests and get back to you

@shubha-rajan Oh very interesting, maybe there is a way to force the computer's clock before I try to connect to the Cloud SQL Proxy. I will run more tests and get back to you

Closing this stale issue. Feel free to reopen if you want to follow up.


feat: add ManagedCluster to the managed resources

Closes https://github.com/ekristen/azure-nuke/issues/82
I'm not sure if there are some unit tests I can add, let me know if that's the case.
I tested it with my Azure account (I removed some of the info):
../azure-nuke/bin/azure-nuke run --config clean.yaml --force --prompt-delay 3 --no-dry-run
> azure-nuke - 1.0.0-dev - dirty
Do you really want to nuke the tenant and subscriptions with the ID SUBSCRIPTION_ID?
Waiting 3s before continuing.
westus2 - ManagedCluster - testnuke - [ID: "", Name: "testnuke", Region: "westus2", ResourceGroup: "group", SubscriptionID: "SUBSCRIPTION_ID", tag:XXXX] - would remove
Scan complete: 1 total, 1 nukeable, 0 filtered.

Do you really want to nuke the tenant and subscriptions with the ID SUBSCRIPTION_ID?
Waiting 3s before continuing.
westus2 - ManagedCluster - testnuke - [ID: "", Name: "testnuke", Region: "westus2", ResourceGroup: "group", SubscriptionID: "SUBSCRIPTION_ID", tag:XXXX] - triggered remove

Removal requested: 1 waiting, 0 failed, 0 skipped, 0 finished

westus2 - ManagedCluster - testnuke - [ID: "", Name: "testnuke", Region: "westus2", ResourceGroup: "group", SubscriptionID: "SUBSCRIPTION_ID", tag:XXXX] - waiting

...

westus2 - ManagedCluster - testnuke - [ID: "", Name: "testnuke", Region: "westus2", ResourceGroup: "group", SubscriptionID: "SUBSCRIPTION_ID", tag:XXXX] - removed

Removal requested: 0 waiting, 0 failed, 0 skipped, 1 finished

Nuke complete: 0 failed, 0 skipped, 1 finished.

It took 4 minutes 11 here.
Side note: I wanted to map g.SystemData.CreatedAt to the struct but it appears to be nil on my test

Thanks for this. I need to look into this a bit more. Primary issue being is this the right resource name or should it be AKSCluster as generally folks know it as ASK.

Thanks for this. I need to look into this a bit more. Primary issue being is this the right resource name or should it be AKSCluster as generally folks know it as AKS.

I wast tempted to use AKSCluster as it's also how I usually call it but I went with ManagedCluster because that's what we have in their SDK. AKSCluster might be more userfriendly

@FlorentClarret apologies for the major delay! Can we rename it all to KubernetesCluster and we'll get it merged right in. Or I can modify your PR, up to you. Thanks.


Checks are never made within the promised 24 hours. It is always (sometimes far) longer.

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[ ] Bug is not already reported in another issue

Describe the bug
The app promises that a check is done every 24 hours. In reality it is always more, sometimes even far more.
Expected behaviour
Checks happen every 24 hours with a maximum tolerance of +/- 1 hour
Steps to reproduce the issue
Install app, wait :)
Technical details

iOS Version: 13.6, before 13.5.2
Device: iPhone 11 and SE 1st Gen
CWA version: Always updated, currently on 1.0.7

Possible Fix
Possible workaround (not solution): Allow manual check when last check is more than 24 hours ago. ATM the app will only show the manual check button when background check is disabled or last check has failed for other (connectivity) reasons.
Additional context
The iPhone 11 is my "daily driver" and I frequently start the app to check. At least 2-3 times per day. The SE 1st Gen is my corporate phone where especially on the weekend i might not open the app for several days.
iPhone SE 1st Gen

Date
Time
Time between updates (h:mm)

2020-07-17
14:39
28:12

2020-07-16
10:27
37:42

2020-07-15
-
No Check performed

2020-07-14
21:45
32:40

2020-07-13
13:05
39:55

2020-07-12
-
No Check performed

2020-07-11
21:10
24:21

2020-07-10
20:49
24:30

2020-07-09
20:19
24:53

2020-07-08
19:26
24:39

2020-07-07
18:47
-

iPhone 11

Date
Time
Time between updates (hh:mm)

2020-07-17
10:52
24:26

2020-07-16
10:26
24:05

2020-07-15
10:21
24:16

2020-07-14
10:05
24:12

2020-07-13
09:53
24:00

2020-07-12
09:53
24:20

2020-07-11
09:33
28:40

2020-07-10
05:53
24:49

2020-07-09
05:04
-

This behaviour is mentioned in several bugs and questions, but I thought it would be good to have one with a clear definition to collect more data from other users. I went through the information in my settings manually to create the tables. So if I made mistakes with calculating the difference, sorry :)

Well, it is probably easier to change the titles of already existing issues - which I just did with #916. Please follow-up and collect the data there. Thank you very much!
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team


Setup a python development environment with poetry for dependency management

For more details, open the Copilot Workspace session.

Add pytest as a development dependency in pyproject.toml

Add [tool.poetry.dev-dependencies] section
Add pytest with version ^6.2.4 as a development dependency

Add a dummy test file

Define a test function test_dummy that asserts True is True


Available via cdnjs

Please make it available via https://github.com/cdnjs/cdnjs

In the meantime rawgit can be used. For example, https://cdn.rawgit.com/sbstjn/timesheet.js/master/dist/timesheet.js and https://cdn.rawgit.com/sbstjn/timesheet.js/master/dist/timesheet.css can be used to link directly to the assets served with correct headers (not text/plain).

By the Way, the URLs above need to be updated to
https://cdn.rawgit.com/sbstjn/timesheet.js/master/dist/timesheet.min.js
and https://cdn.rawgit.com/sbstjn/timesheet.js/master/dist/timesheet.min.css


When using gitlab, Share opens wrong link to members page

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
When opening a file from a GitLab repository I own, the "Share" button opens a new tab with the link to the project members page, but the URL is partially escaped and of course Page not Found. Some / are /  but some in the middle are escaped %2F
I am not sure if this has something to do with the subgroup name being of format "abc-def" and not "abc_def".
What i get is:
https://gitlab.com/myteam%2Fabc-def%2Fpublic/someproject/-/project_members
and should be
https://gitlab.com/myteam/abc-def/public/someproject/-/project_members
Expected behavior
A clear and concise description of what you expected to happen.

draw.io version 23.0.0

Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Browser Version: 121.0.6167.185

Fix in 24.5.4.


StringExtensions Empty and Null Check

All extension methods should work for empty strings. Should not check if the string is null!
Language Reader  methods should nevel return null Strings, but empty ones if necessary.

All methods in StringExtensions are revised and refactored.


How to set default (current date) and display date format placeholder in Firefox?

I created a fiddle https://jsfiddle.net/sjordan/r81k8240/
In Chrome the placeholder "mm/dd/yyyy" is present.
In Firefox it is not. Also, in Firefox, the calendar input does not pop up.
Also, I tried to use the "set" property (but no success) to set value to current date. How do I use "set"?

You will find more information about this by reading this issue #231
To put it simply, Firefox is not yet compatible with the native <input type="date">. It has nothing to do with us. As you can see, it is also not compatible with IE and Safari.
Read #231 for more info.


Updated ticket to display proper fields when registering ticket

Refactored function for ticket register

Current coverage is 95.66% (diff: 80.00%)

Merging #224 into master will increase coverage by 0.62%

@@             master       #224   diff @@
==========================================
  Files            46         46
  Lines          1391       1408    +17
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1322       1347    +25
+ Misses           69         61     -8
  Partials          0          0

Powered by Codecov. Last update aaea1cf...db1393b

LGTM


BetterColor

The Problem/Feature
99 problems but a PR ain't one
Implementation details
Testing Steps

Checklist:

[ ] Pull Request title is good
[ ] Commit message is good (copy the Pull Request description to the commit message)
[ ] Tested code locally
[ ] Covered by automated tests
[ ] Approved by the author

what did you do? plz explain briefly

Change some of font and hover to make it decent
On Wed, 5 Oct 2022, 10:16 am Shahadat Hossain Hridoy Al, <
@.***> wrote:

what did you do? plz explain briefly
—
Reply to this email directly, view it on GitHub
https://github.com/HridoyHazard/BetterColor/pull/60#issuecomment-1267934535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWAEG7M5VAH46HHXTAVYXCDWBUBZLANCNFSM6AAAAAAQ5GEPFA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix for LEAD/LAG window function test failures.

Fixes #11807.
test_lead_lag_for_structs_with_arrays in window_function_test fails intermittently because of non-deterministic data ordering.
Window function tests are sensitive to data ordering.  With certain values of DATAGEN_SEED, there are repeated values of partitioning/ordering keys, causing the window function to return different values on CPU and GPU.
This commit fixes the test so that the ordering is deterministic.

Build

Thank you for the prompt reviews, @zpuller, @razajafri, @abellina.  This change has been merged.


Changing wlm_json_configuration to be list

Description
Having a long one line json in terraform is not very intuitive. having the configuration as HCL is more readable.

Hi @antonbabenko Can you view this PR, it is a very simple one too.

@antonbabenko this is ready for another look


network returning nan actions [question]

Describe the bug
I am working with a custom environment and vectorizing it using SubprocVecEnv.  Recently while using PPO2 I have started receiving Nan.
Illustrated below are two consecutive results.  The first is good and then all training messages after have nans and the network is sending nan actions to the environment,

------------------------------------
| approxkl           | 0.05277536  |
| clipfrac           | 0.39106447  |
| explained_variance | 0.0262      |
| fps                | 17          |
| n_updates          | 29          |
| policy_entropy     | 6.770977    |
| policy_loss        | 0.016628642 |
| serial_timesteps   | 59392       |
| time_elapsed       | 2.44e+04    |
| total_timesteps    | 237568      |
| value_loss         | 3735940.5   |
------------------------------------

---------------------------------
| approxkl           | nan      |
| clipfrac           | 0.0      |
| explained_variance | 8.29e-06 |
| fps                | 15       |
| n_updates          | 30       |
| policy_entropy     | nan      |
| policy_loss        | nan      |
| serial_timesteps   | 61440    |
| time_elapsed       | 2.48e+04 |
| total_timesteps    | 245760   |
| value_loss         | nan      |
---------------------------------

I was hoping to use VecCheckNan to help debug the root cause, but I do not get a warning or exception.  Looking to see if I am implementing VecCheckNan correctly or if this will even help with my problem.
Code example
from stable_baselines.common.policies import MlpPolicy, FeedForwardPolicy, ActorCriticPolicy, register_policy
from stable_baselines.common.vec_env import SubprocVecEnv, DummyVecEnv, VecCheckNan
from stable_baselines.common import set_global_seeds
from stable_baselines import PPO2

if __name__ == '__main__':

    register_policy('CustomPolicy', CustomPolicyDetailed)
    env = SubprocVecEnv(env_list)
    env = VecCheckNan(env, raise_exception=True)

    model = PPO2(policy ='CustomPolicy',
                             env = env,
                             verbose = 1,
                              vf_coef = VF_COEFF,
                              noptepochs = EPOCHS,
                              ent_coef = ENT_COEFF,
                              learning_rate = LEARNING_RATE,
                              tensorboard_log = tensorboard_log_location,
                              n_steps = NSTEPS,
                              nminibatches = MINIBATCHES)

    model.save(results_folder + run_name)

    for i in range(number_training_steps):
        logname = run_name + '_' + str(i)
        model.learn(total_timesteps = int((total_timesteps/number_training_steps)),
                    reset_num_timesteps = False,
                    tb_log_name = logname)

        env.close()

        path = results_folder + logname
        model.save(path)

I have determined that the network is returning Nan for the actions, but unable to determine the cause.  I have included some checks in my environment to print to console if an nan or infinite is detected in the observations or reward, but receive no messages; so I assume the environment is operating correctly.  I was hoping VecCheckNan would provide some material guidance, but perhaps I am using it incorrectly
System Info

Stable-Baselines version = 2.8.0
Python version = 3.6
Tensorflow version = 1.14

Any Insights?

I assume you took a look at the docs on this issue?
Looking at your prints, you see a huge value loss of "3735940.5", which probably relates to reason why network nan-ed out.  These should be in (roughly) [-1, 1] interval to avoid large value estimates. If episodes are long (thousands of steps) and reward is often -1/+1, consider smaller reward (e.g. 0.01 per step).

Maybe related: #340 (try setting the entropy coeff to zero) and https://github.com/hill-a/stable-baselines/issues/634

Note for future: Issues (and solutions) like these could be documented on docs, similar to how exporting models is done. Perhaps even in more stand-alone fashion where user should not have to check out Github issues for a (possible) solution.

Thank you for your comments.
I will try the two proposed solutions.

My Entropy coeff was already relatively small, 0,005, but I will try setting it to zero to eliminate it as a possible culprit.
I can also try normalizing the reward

Am I implementing VecCheckNan incorrectly? or am I not understanding it's function?  I would have expected it to throw an exception.  Instead nan actions are set to the environment

I can also try normalizing the reward

You can also use VecNormalize for that.

Am I implementing VecCheckNan incorrectly?

The use looks good (@hill-a ?). The NaN may come from the training, not the env/actions.

I changed the Entropy coeff to zero and VecCheckNan fired and gave me an exception.  Not sure why the Entropy coeff would impact that.  Not sure if this is a bug, or something else.  I'll test a couple more times with different entropy coeff.
Nevertheless, I'll look into my error as well.  Looks like I am getting some observations that are quite large, which probably are effecting the RL model.
ValueError: found nan in actions.

Quick update:  I normalized the rewards and fixed the observations which were providing a large value.  I also made the entropy coefficient zero.  I am still receiving nans.  While this is probably an issue with the environment sending something weird to the RL model, I am surprised that VecCheckNan isn't throwing an exception.  it ran over 500,000  steps in the environment last night  and actions were nan for all.
In what case(s) would a nan not throw an exception using VecCheckNan?
---------------------------------
| approxkl           | nan      |
| clipfrac           | 0.0      |
| explained_variance | nan      |
| fps                | 51       |
| n_updates          | 3        |
| policy_entropy     | nan      |
| policy_loss        | nan      |
| serial_timesteps   | 6144     |
| time_elapsed       | 790      |
| total_timesteps    | 786432   |
| value_loss         | nan      |
---------------------------------

I once encountered this problem, and then I tried rl-model-hyperparameters, and finally my problem was improved, but rl-model-hyperparameters takes a lot of time.

closing this issue at it seems definitely related to custom environment.


feature request: import images without unpacking using ctr

👋 First off, thanks for all the awesome work on containerd!
Feature Request
I'd like to add the ability to call Import from the ctr command line without calling Unpack.
Specifically I'd like to add a --no-unpack option to ctr images load, in which case the command would return after:
https://github.com/containerd/containerd/blob/a17c8095716415cebb1157a27db5fccace56b0fc/cmd/ctr/commands/images/import.go#L113-L120
skipping the following:
https://github.com/containerd/containerd/blob/a17c8095716415cebb1157a27db5fccace56b0fc/cmd/ctr/commands/images/import.go#L122-L136
Why?
I'm building node images where Kubernetes's component images are preloaded into the containerd content store to provide fast air-gapped startup. In this case I only want to load images into the content store without unpacking them to a snapshotter.
Doing this results in a smaller image while still avoiding the need to pull images, the runtime cost of unpacking to the snapshotter seems to be small and preferable to the image size increase. I imagine this would be useful for others building airgapped images.
Context: https://github.com/kubernetes-sigs/kind, https://kind.sigs.k8s.io/
Why Not?
I could maintain a different tool specifically for this purpose, but I think this would fit into the existing ctr command trivially. If this feature is rejected I will likely wind up implementing such a tool instead.

Thanks!

cc @Random-Liu

I think this is a trivial change that will benefit several tools built on top of containerd, at least kind. :)
And it makes sense to only preload content, because people may later choose to use different snapshot.

Fixed in #3259

Will this be fixed in nerdctl? I pulled images via nerdctl and noticed it created snapshots(and taking up more disk space), even though container was not being used.

@xagent003 nerdctl issues are at https://github.com/containerd/nerdctl/issues, this change is specific to this tool (ctr) and is gated behind the --no-unpack flag. Containerd makes the relevant APIs available to tools like this.


Create centralised event broker between Web and Bancho

We want to be able to broadcast events between the two platforms, this will be using Redis pub/sub.
As part of this ticket we want to create an event that allows events within Bancho to be sent to Web and visa versa, these events should be then fired through the native event system but also allowing custom remote events to be listened to
The channel format will be event:ClassName and the body will be a JSON encoded form of relevant data, when it refers to database objects we should send the ID, so instead of User we would send user_id.
Each event on one platform should have a native event with the same name, this allowed each platform to listen to eachother's events allowing read-only processing without a companion plugin on each end

Web ticket: HirasawaProject/Hirasawa-Web#16

This ticket should also use environment variables for Redis credentials like #256


Question: Environment variables for Lambda functions

I note that on your blog post you state that environment variables won't be currently working in the canary version. I just want to clarify what this means exactly.
Does this just mean that there are currently no terraform variables which allow you to configure environment variables on the Lambda functions created during a tf-next deploy?
I'm asking as I am trying to get a Next.js API route to return an environment variable which I've manually configured on the Lambda via the AWS console. I'm doing this using publicRuntimeConfig. I'd have thought this would work OK but I just can't seem to get it to work. I'm probably doing something wrong.

@ofhouse currently it seems like .env file is getting used automatically, can we configure it to use other .env files, like .env.staging or .env.qa ?


Integrated SimpleYAML driver

Integrated SimpleYAML driver and allow to configure the file extensions for file mapping.
Also reset the doctrine-orm version to 2.5 which is the latest stable.

Added a option to disable naming strategy.

I'm quite sure I added support for this already.


Switch from PropertyTable events to a built-in one

BACKWARDS INCOMPATIBLE CHANGE
This fixes the TODO to create a custom event type for Alarmist. The main
advantage here is to make Alarmist easier to use since the PropertyTable
internals aren't exposed.  The second reason is that the PropertyTable
schema is changing and if we're going to break the API, we might as well
just do it once.

The GitHub CI status is misleading. CI passed.


Update RedditBridge.php

I read my rss mostly on mobile and old.reddit.com isn't very good to read on mobile devices.
So I added an option to change the article link to the "new" reddit.

good idea.
can you change this into a list? because there are multiple frontends e.g. also https://libreddit.kavin.rocks/r/python

good idea.
can you change this into a list? because there are multiple frontends e.g. also https://libreddit.kavin.rocks/r/python

Ok, I changed it to a more generic list for all frontends

this pr breaks existing feed urls because they dont have the frontend parameter.

existing feeds should now work as well


Add a wiki: Celeste Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://celestegame.fandom.com
Link to destination (independent) wiki: https://celeste.ink

This has been added and will be released in v1.3.0


TypeError: operation.response is not a function or its return value is not iterable

Using the website example gives a type error:
const Operation = require('openapi-enforcer').v3_0.Operation;
const operation = new Operation({
    responses: {
        200: {
            description: 'Success',
            content: {
                'text/plain': {
                    schema: {
                        type: 'string',
                        maxLength: 10
                    }
                }
            },
            headers: {
                expires: {
                    description: 'When the content expires',
                    schema: {
                        type: 'string',
                        format: 'date'
                    }
                }
            }
        }
    }
})

const [ response ] = operation.response(200, 'hello', {
    expires: new Date('2000-01-01T00:00:00.000Z')
})

console.log(response)

error message:

const [ response ] = operation.response(200, 'hello', {
                               ^

TypeError: operation.response is not a function or its return value is not iterable

What is the valid way of validating a response? Goal is validating headers and schema before the server sends anything.

Thanks for bringing this to my attention. I've updated the example in the documentation to be correct: https://byu-oit.github.io/openapi-enforcer/api/components/operation#response
The problem was with the second line.

Incorrect: const operation = new Operation...
Correct: const [ operation ] = new Operation...

The functions return an EnforcerResult instance that you can use destructuring on to get out the value, errors, and/or warnings.

thanks it works perfect!


Contract Spec: Add capability to record test cases and expected outcomes to spec

We should explore adding test cases to the contract spec.
Each test case would specify:

ledger entries
inputs
expected output or outcome

These would be encoded into a separate custom section that operates as an extension to the contract spec. The main motivation for making it a separate custom section is so that it could be removed from the wasm binary easily without specialized tooling.
Use cases:

We could add the ability to the CLI to execute test cases in a wasm.

We could add the ability to the CLI to generate / output human readable documentation from the wasm about the test cases.

We could use this to test new versions of the host against a wide variety of deployed contracts.

Other could use this to check that their own contract and contracts they depend on continue to function consistently with host upgrades.

Others could use this to gain confidence about contracts they depend on, and to understand edge cases that might not otherwise be obvious.

Related discussion: https://discord.com/channels/897514728459468821/1007060872138592286/1007072592919789589
cc @graydon

We could do this but .. I think most contracts work on/with a variety of other contracts and authorization state, such that the mock context you'd be setting up would be fairly extensive. I'm not opposed to experimenting! Just .. worried it's a lot of work and not sure it'd pay off or even entirely work. cc @brson wdyt?

I apologize in advance that this is a spew of ideas.
A bunch of use cases here that might be served in different ways. The idea of automatically testing contracts, and testing them across runtime upgrades, is something I love, and can have a big bang-for-buck.
Embedding declarative unit tests as described in the op does sound pretty static and limited to me. e.g. one of the things I have found myself quickly wanting to do in tests is advance time across multiple transactions, not just set up a static ledger snapshot and make a single transaction against it. The declarative approach described in the op could need to grow a lot to cover relevant use-cases. It also presumably requires developers to buy into writing a special type of unit test, and that might be a hard sell for speculative benefits. It would be much desirable to leverage "normal" Rust unit tests if possible.
I am imagining some other approaches to testing the entire ecosystem across runtime upgrades, but they are pretty divergent from the original topic of embedding unit tests in the wasm.
On the topic of embedded unit tests, instead of having a declarative approach of defining inputs and outputs, one could also just let contracts define a "self-test" function that does whatever it wants; perhaps that self-test runs live on-chain (or on a forked chain just for testing).
As I reread the op, the idea of embedding metadata in the specs makes me think of theorem provers. Declaring preconditions, postconditions, and state invariants is in the spirit of "specs", and could be used by various tooling to drive the contracts in an adversarial way.

one could also just let contracts define a "self-test" function that does whatever it wants

Interesting. This would be simple to develop for.
A downside is if someone without the original code was running the self test and saw a failure, they probably can't reason about why it failed. Which means that prior to a new release, we might not be able to learn much about how we've caused a failure, if that is a bug or not.


Fetch taxon doc from workspace object ref

More detailed tests can come later once the ui is more locked down


kubectl resource builder: don't check extension for single files

kubectl create -f filename doesn't need to check the extension
of filename. This fixes that behavior. Fixes #10853
cc @andronat, @mikedanese

@jlowdermilk, if this PR is for v1.0, please ping @bgrant0607 directly to confirm. Thanks!

This is post-1.0. No rush

LGTM. Thanks! Can you rebase then I'll tag this?


Content-type not using proper quotes?

It looks like the required default Content-Type :
Content-Type: audio/wav; codec=audio/pcm; samplerate=16000
should rather be:
Content-Type: audio/wav; codec="audio/pcm"; samplerate=16000
to be a valid media type - without quotes this will trip most (java) parsers. (see http://www.ietf.org/rfc/rfc2046.txt )

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

ID: d6021ebc-4b2a-fbb3-84a4-1753b80442c3
Version Independent ID: 4af2b683-7cc6-3aa4-eeb5-cf5a087094d1
Content: Speech Service REST APIs
Content Source: articles/cognitive-services/Speech-Service/rest-apis.md
Service: cognitive-services
GitHub Login: @erhopf
Microsoft Alias: erhopf

Hi @alexander-riss, thanks for reaching out. Are you referring to the generic POST request example (see below)? I just tested the request with Postman using the original and proposed syntax and both work. Can you point me to the part of the RFC spec that discusses use of quotations?

Hi @erhopf i tried the same with e.g. spring rest-client and it always fails to parse the "/" in the codec parameter unless it is quoted. There is one example in the RFC which uses forward slashes - and quotes. see http://www.ietf.org/rfc/rfc2045.txt chapter 5.1


E1208: -complete used without -nargs

When I try to open nvim with a file as parameter as: "nvim app.js" its show me the error "E1208: -complete used without -nargs", then I press enter and show me the file but I dont know what could be going wrong make that message to show up.
The complete message:
Se ha detectado un error al procesar C:\Users\SecondShadow.config\nvim\plugged\nerdtree-project-plugin\nerdtree_plugin\project
.vim:
línea   45
E1208: -complete used without -nargs
Press ENTER or type command to continue

https://github.com/scrooloose/nerdtree-project-plugin/pull/2/files
Make the same changes as in this PR and it will work


Added statement about YT video produced by IkBrian.

I get it, we're all frustrated by the problems that IkBrian's video causes us, but isn't this just asking for trouble?

With their refusal to fix the issues, and with support mostly falling on the RayzrDev server, it's a needed addition to explain the situation with the video.

Don't think this is necessary. People coming from that video aren't going to read this - and this isn't doing anything but giving him free publicity.

Pull request closed. Result: Not a necessary addition


row heights doesn't actually apply?

Hi,
I am trying to update an excel spredsheet which contains football data, but when overwriting data with the codesnippet below, everything runs smoothly and saves. But when I reopen the xlsx file the rows "are gone", but not really, as if i pull down the top row they expand one by one and the data is there. Why is this happening? the code logs out that the row height is 15 at both lines, but i doesnt seem so. Pictures at bottom, trying to explain how i make the data visible.
exceljs.ws.eachRow({ includeEmpty: true }, (row, rowNumber) => {
            console.log(row.height);
            row.values = Object.values(data[rowNumber - 2]);
            row.height = 15;
            console.log(Object.values(data[rowNumber - 2]));
            console.log(row.height);
        });

await exceljs.wb.xlsx.writeFile("new.xlsx");

Sorry for the late response, I am currently using v3.7.0, and the bug is still present.
I used this code snippet for testing:
exceljs.ws.eachRow((row, rowNumber) => {
console.log(row.hidden);
if (rowNumber < 2 || rowNumber > data.length + 1) return;
row.values = Object.values(data[rowNumber - 2]);
console.log(row.hidden);
});
and the output is simply true for all iterations, so it seems like the cells gets a hidden value from a previous action. I actually have to dig deeper into this issue as I cannot put a finger on what exceljs method that is causing this issue to appear. Previous to this method call I set the columns, so I have to debug that function.


IBAN validation, invalid values resolve to valid

When I use the validation for IBAN some non-valid values resolve to valid.
Some values that are not valid but are shown as valid are:

1
1682406
377748587

The issue is not an issue, there is a comment in the code concerning 'strict' checking, maybe an optional parameter 'strict' or something would be an nice feature.


TCO examples

$ cat w.pl
main(N) :- N > 0, N1 is N-1, main(N1).

$ cat v.pl
% No local vars & no structures, yet not recovered...

zx81(X, Y) :- Y is (X*75+74) mod 65537.
main(0) :- !.
main(I) :- zx81(I, _), I2 is I-1, main(I2).

$ cat y.pl
f(0) :- !, fail.
f(_).
main(N) :- f(N), N1 is N-1, main(N1).

$ cat z.pl
f(X) :- X > 0, X=Y.
main(N) :- f(N), N1 is N-1, main(N1).

All these examples run in constant memory with SWI Prolog:
$ time swipl -g 'main(100000000);halt' w.pl

With Trealla only v.pl does not.

zx81(X,Y) :- Y is X*1.
main(0) :- !.
% main(I) :- zx81(I,I), I2 is I-1, main(I2). % Good
% main(I) :- zx81(I,M), I2 is I-1, main(I2). % Bad, Var M eats memory
% main(I) :- zx81(I,_), I2 is I-1, main(I2). % Bad, Var _ eats memory

Yes, it's the call to xz81/2 that causes main/1 not to be TCO. I know why
just haven't worked out a solution that doesn't break another test, there
may be 2 things to fix.
On Sat, May 25, 2024 at 12:21 PM flexoron @.***> wrote:

zx81(X,Y) :- Y is X*1.
main(0) :- !.
% main(I) :- zx81(I,I), I2 is I-1, main(I2). % Good
% main(I) :- zx81(I,M), I2 is I-1, main(I2). % Bad, Var M eats memory
% main(I) :- zx81(I,_), I2 is I-1, main(I2). % Bad, Var _ eats memory
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/543#issuecomment-2130672067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEVO3GUMGHW5SOZUNU3ZD7YTTAVCNFSM6AAAAABIHBE6YWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZQGY3TEMBWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

For WAM there proposals like Older and
Rummel's incremental garbage collection algorithm
https://www.researchgate.net/publication/2751901
But especially for tail recursion, I think frame reuse
is key, SWI-Prolog does it by a special compilation.
You see it via vm_list/1, the i_depart/1 instruction:
?- vm_list(main/1).

       9 l_nolco('L1')
      11 l_var(0,1)
      14 i_tcall
L1:   15 b_var1
      16 i_depart(user:main/1)
      18 i_exit

Yet another approach is to not have frames at all.
I have done that in Dogelog Player, where predicates
suchs as DEC10 ancestor/1 or a back trace in an
error is impossible by design.


merge from template-kronos-app

package.json

chore(deps): add ^12.3.1 remove ^12.3.0 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.11.0
GitHub release

Your semantic-release bot :package::rocket:


fixed bugs in joint-ISI and shuffle ISI

I fixed the bugs appearing when preparing the elephant workshop.
First, I spike exactly at t_stop.
Secondly, spike trains with nor properly ordered spikes.
I added the examples originally producing the bugs in the tests.
By the way, the decimals of shuffle_isi can produce bugs, since the units for this are not specified.

Hello @pbouss! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file elephant/test/test_spike_train_surrogates.py:

Line 630:80: E501 line too long (80 > 79 characters)
Line 632:80: E501 line too long (80 > 79 characters)

Coverage increased (+0.006%) to 89.908% when pulling 6f57df7877eda55b1681400ef159fd1e7bc64163 on INM-6:fix/joint_isi_shuffle_isi into a0ca2158af5455ea48c67da67d7df9bedc53a313 on NeuralEnsemble:master.


[FEATURE] {flalign*} support for auto-newline, etc.

Description of the Problem
When I'm using flalign* blocks, adding a newline simply adds the newline, rather than adding \\ and &.
Description of the Solution
I would love if a newline would trigger both \\ added to the previous line, and a & added to the beginning of the newline. As far as I'm aware, flalign* is the best way to do left-aligned multiline equations, so I tend to use them decently often.
Additional
My original plan was to create a snippet, but as far as I'm aware the newline functionality isn't a snippet but custom functionality within the plugin? I could be wrong here.
Here's the idea:
\begin{flalign*}
& \vec{v}_{i} = \vec{v}_{cm}=\vec{v}<CURSOR HERE>
\end{flalign*}

When pressing enter, becomes:
\begin{flalign*}
& \vec{v}_{i} = \vec{v}_{cm}=\vec{v}\\
& <CURSOR HERE>
\end{flalign*}

Try adding flalign* to Matrix shortcuts > Environments in the plugin settings.


Implement Idea Board

Add an Idea Board page allowing users to create and display ideas. Users should be able to input a title and a brief description for each idea. All submitted ideas should be displayed in a structured format and fetched from the database.
Requirements
Idea Creation:

Button to Add Ideas:

Add a button labeled "Add Idea" on the page to add a new idea.

Idea Form:
Upon clicking the "Add Idea" button, display a form/modal where users can enter:

Title: A short, descriptive title for the idea.
Description: A brief description detailing the idea (optional).

Include a "Submit" button to save the new idea.
Validate the form inputs to ensure both the title and description are appropriately filled out before submission.

Display Ideas:

The idea board page should consist of multiple ideas that constantly get updated.
All ideas need to display their:

Title
Description

Implement using Cards for better visual representation.

Database Connection:

Implement a connection to the database to store and retrieve ideas.
Write SQl queries to create idea board table automatically

Ideas Table:

id: Primary key (UUID).
title: VARCHAR for the idea title.
description: TEXT for the idea description.
created_at: TIMESTAMP for the submission date.

Create Go structures for the idea board information fields.
Create new API endpoints:

POST /create_idea: To create a new idea and save it to the database.
GET /get_ideas: To fetch all submitted ideas from the database for display.

Fetch Ideas:

When the idea board page loads, fetch existing ideas from the database and display them immediately.
Implement proper error handling for fetching and creating ideas

Acceptance Criteria

Users can click the "Add Idea" button to open the idea submission form.
Users can successfully submit a title and description for their idea, which gets saved to the database.
Upon loading the idea board page, all submitted ideas are fetched from the database and displayed immediately and persistently on the same page.
Bonus: Ideas should be constantly updating through a dynamic animation.

Additional Notes

Ensure proper error handling for both creating and fetching ideas from the database to maintain application stability.

assign request

!assign @Yajetts

Hey can I be assigned to this issue please?

!assign @VulcanRaven737

Kindly check my PR @shri30yans


Revert "fix: using empty image label for container metrics (#122)"

This reverts commit 6a5ef77eb9e3946be05c9dd60ce0752ce77b589f.
Pull Request
Required Fields
:mag_right: What kind of change is it?

fix

:dart: What has been changed and why do we need it?

Previous PR broke setups

Optional Fields
:heavy_check_mark: Which issue(s) this PR fixes?

#122

:speech_balloon: Additional information?

We need to figure out a better way

:tada: This PR is included in version 2.3.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


arch: arm64: Use atomic for fpu_owner pointer

Currently the lazy fpu saving algorithm in arm64 is using the fpu_owner pointer from the cpu structure to understand the owner of the context in the cpu and save it in case someone different from the owner is accessing the fpu.
The semantics for memory consistency across smp systems is quite prone to errors and reworks on the current code might miss some barriers that could lead to inconsistent state across cores, so to overcome the issue, use atomics to hide the complexity and be sure that the code will behave as intended.
While there, add some isb barriers after writes to cpacr_el1, following the guidance of ARM ARM specs about writes on system registers.

Ok I guess that with the blessing of the author, this can be merged :)

Ok I guess that with the blessing of the author, this can be merged :)

we are code freeze. This will be merged in the next merge window.

@carlocaione Ohh ok, totally missed that bit!

This is a correctness issue though, which IMHO should match criteria for amerge even now.

mmm... yes now that I think about it, no barrier after the write to the system register might be a latent bug, as there might be inconsistent behaviour