WFLY-3854 Make build work on JDK9

Windows Build 1825 is now running using a merge of 89703f3738cc077c465a17d006b8a1f691b418cc

Linux Build 2308 is now running using a merge of 89703f3738cc077c465a17d006b8a1f691b418cc

Core - Full Integration Build 1442 is now running using a merge of 89703f3738cc077c465a17d006b8a1f691b418cc

Core - Full Integration Build 1442 outcome was FAILURE using a merge of 89703f3738cc077c465a17d006b8a1f691b418cc
Summary: Exit code 1 (new) Build time: 0:01:12
Build problems:
Process exited with code 1

Linux Build 2308 outcome was FAILURE using a merge of 89703f3738cc077c465a17d006b8a1f691b418cc
Summary: Tests passed: 1627, ignored: 41; exit code 1 (new) Build time: 0:02:48
Build problems:
Process exited with code 1

Windows Build 1825 outcome was FAILURE using a merge of 89703f3738cc077c465a17d006b8a1f691b418cc
Summary: Tests passed: 1627, ignored: 41; exit code 1 (new) Build time: 0:03:22
Build problems:
Process exited with code 1

Linux Build 2309 is now running using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99

Windows Build 1826 is now running using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99

Core - Full Integration Build 1443 is now running using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99

Windows Build 1826 outcome was SUCCESS using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99
Summary: Tests passed: 3423, ignored: 64 Build time: 0:35:34

Linux Build 2309 outcome was SUCCESS using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99
Summary: Tests passed: 3423, ignored: 64 Build time: 0:37:03

Core - Full Integration Build 1443 outcome was FAILURE using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99
Summary: Tests failed: 187 (187 new), passed: 2795, ignored: 367 Build time: 0:51:30
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.registry.RegistryTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredQueue: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredTopic: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: <no details avaliable>

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: <no details avaliable>

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: <no details avaliable>

##### there are 177 more failed tests, see build details

Core - Full Integration Build 1445 is now running using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99

Core - Full Integration Build 1445 outcome was SUCCESS using a merge of 8e244cda2ae5ffc3e9b7609a7a23712e1bc97c99
Summary: Tests passed: 3098, ignored: 368 Build time: 0:51:00

Core - Full Integration Build 1467 is now running using a merge of 5333a2a11bc9bff828dc0bf48e51e20a31f74252

Linux Build 2330 is now running using a merge of 5333a2a11bc9bff828dc0bf48e51e20a31f74252

Windows Build 1847 is now running using a merge of 5333a2a11bc9bff828dc0bf48e51e20a31f74252

Windows Build 1847 outcome was SUCCESS using a merge of 5333a2a11bc9bff828dc0bf48e51e20a31f74252
Summary: Tests passed: 3425, ignored: 64 Build time: 0:35:34

Linux Build 2330 outcome was SUCCESS using a merge of 5333a2a11bc9bff828dc0bf48e51e20a31f74252
Summary: Tests passed: 3425, ignored: 64 Build time: 0:36:52

Core - Full Integration Build 1467 outcome was SUCCESS using a merge of 5333a2a11bc9bff828dc0bf48e51e20a31f74252
Summary: Tests passed: 3079, ignored: 368 Build time: 0:50:59


add a rough curl equivalent to the readme

Here's as close as I could quickly come with curl:
$ curl -sD - -o /dev/null -w 'time: %{time_total}s\ndownload speed: %{speed_download} bytes/s' https://httpbingo.org
HTTP/2 200
access-control-allow-credentials: true
access-control-allow-origin: *
content-security-policy: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' camo.githubusercontent.com
content-type: text/html; charset=utf-8
date: Wed, 06 Sep 2023 20:58:38 GMT
server: Fly/8770e2a7 (2023-09-01)
via: 2 fly.io
fly-request-id: 01H9P4ME7AH00SGSZN7RCS55VY-lga

time: 0.127817s
content length: 89894 bytes/s

Unfortunately content-length is not available as a write-out variable.
I'm not suggesting this replaces get-headers, but it might be worth putting a close curl equivalent in the docs? up to you.

I probably wouldn’t have made this if I had known about curl -IXGET, but it’s made now. I’m not sure anyone else uses it?

hah, no worries - I only saw it because it came up on my github feed

Wow, this repo is only a month younger than my marriage.


Cmssw 12 4 0 pre3 wip test alpaka data formats wip

This PR adds support for trivial const view, documentation and initializer list style assignment to SoA.
It imports PortableCUDA*Collection and adds SoA structures to replace SiPixelDigisCUDASOA and SiPixelClustersCUDA.

@ericcano thanks for the PR.
For the merge into https://github.com/cms-sw/cmssw/pull/37716 I'm going to pick only the changes to DataFormats/SoATemplate/.
Of them, I'm leaving these out:

DataFormats/SoATemplate/src/classes_def.xml has been moved to DataFormats/SoATemplate/test/classes_def.xml, as the corresponding data form ats are only used in the tests
DataFormats/SoATemplate/README.md has only whitespace changes (and undoes a fix for the lowercase constant names)
DataFormats/SoATemplate/interface/SoACommon.h only adds a commented-out macro

I've merged the other changes to DataFormats/SoATemplate/, and I'll move them to their own commit.


ADMIN_KEY and DIPPY_KEY not documented in README

ADMIN_KEY and DIPPY_KEY are required to run start_validation_service.sh but are not documented in the README.md
What are they for and where are they from?

They are custom values as can be seen in the code

Should we document them in the README.md?

For example this PR https://github.com/impel-intelligence/dippy-bittensor-subnet/pull/50


change the settings name and fixed a bug in delete model (#861)

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

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.

I think this is to backport PR to main branch. We should always add [Backport to main] to PR title. In the description, you can clarify which PR is going to be backported.


Handle modification of pipeline during propagation

As it stands, modifying the pipeline itself during propagation of stages does not cause newly added stages such as reactions to propagate properly. Add recursive propagation to enable the pipeline to at least allow for changes to subsequent stages to be reflected properly.
Changes to prequelling stages are harder, as they intrinsically cause the executing pipeline to enter an invalid state while being propgatated.

There are, however, problems with this. Some code may be run both during and not during propagation of the pipeline. Such code is more pipeline agnostic if the burden then falls upon the developer to ensure such modifications extracts its needed information as it wishes (and that the modification is handled in such a way that cached values are actually already invalidated).
All in all, it makes for a more coherent experience.


container.Resolve() doesn't create signleton when dependency requested via intermidiate constructor

The title :)
I can't make Go's playground to run this code since it's using a version of the project without Container available in the dependency graph.
package main

import (
	"log"

	"github.com/goava/di"
)

type Interface interface {
	Do()
}

type Implementation1 struct{}

func (d Implementation1) Do() {}

type Implementation2 struct{}

func (d Implementation2) Do() {}

func newFactory(container *di.Container) (Interface, error) {
	// Some decision logic which implementation to choose
	var implementation *Implementation1
	err := container.Resolve(&implementation)
	if err != nil {
		return nil, err
	}

	return implementation, nil
}

func newImplementation1() *Implementation1 {
	println("called implementation 1")
	return &Implementation1{}
}

func newImplementation2() *Implementation2 {
	println("called implementation 2")
	return &Implementation2{}
}

func main() {
	container, err := di.New(
		di.Provide(newFactory),
		di.Provide(newImplementation1),
		di.Provide(newImplementation2),
	)
	if err != nil {
		log.Fatal(err)
	}

	var implementationByFactory Interface
	err = container.Resolve(&implementationByFactory)
	if err != nil {
		log.Fatal(err)
	}

	var directImplementation *Implementation1
	err = container.Resolve(&directImplementation)
	if err != nil {
		log.Fatal(err)
	}
}

Output:
called implementation 1
called implementation 1

But expected only one call.

Fixed in https://github.com/goava/di/commit/1d9af1f7f733ba5aa7ad4309c3180f9d331778e1.
The problem is only in the master branch. It's cool that you found it 👏.

Fatal typo


median on dask arrays

Dask has updated it's percentile, quantile implementation: https://github.com/dask/dask/pull/4677
Can we now update our median method to work with dask arrays?

Is anyone working on adding the median method?

Yes, we could do this as long as we’re careful to default to the new algorithms. See also https://github.com/pydata/xarray/issues/1524#issuecomment-514002753

I have a median method over in https://github.com/dask/dask/pull/3819


Make NPM published size smaller

http://glebbahmutov.com/blog/smaller-published-NPM-modules/

done


Use Django's bundled six; avoids additional external dependency.

As Django is always required for django-braces, use Django's bundled
six library for Python2/3 compatibility. Avoids an external dependency
that already exists.
See https://docs.djangoproject.com/en/dev/topics/python3/

:+1:


NMS.MA.COURSE.002 - Course completion criteria

An MA course shall be considered to have successfully finished if:

The FLW has finished listening to all the lessons of all the chapters.
The FLW has taken all the quizzes of all the chapters.
The FLW has attained at least 50% marks in the quiz (22 or greater marks out of 44).

Once course is completed, the call shall be disconnected and the bookmarks are reset. When the user dials next time, the user is automatically taken to welcome message.

Questions for @pankajnagpal30 and BBC -

There is no workflow from a completed course state to restarting the course again. This means that the next time an FLW calls in, they start out like a new user (as opposed to playing an ivr message saying we noticed you finished the course, do you want to restart, etc)

Pass Citeria
This is always the total score right? If the user got a 0 in 5 of the chapters but scored great in the rest to make up for the 22 needed to pass, they are still considered passing?

What should we do if a user completes a course but fails the pass criteria of > 50% score?

Do they get an option to restart the course?
Do we not reset their bookmarks?
Who makes this decision? (IVR vs motech)

@llavoie @larubbio This is implemented as we understand the feature today with followup questions to BBC. Should be mark the issue as  -

closed and open a separate tracking for the possible followup changes?
OR
move to sprint 3?
OR
leave it open here?

I like option (1) -- and put the new ticket in sprint 3 as we likely won't get clarity in time for sprint 2.

ok, #245 created for Sprint 3 to followup. Closing this issue.


Supported Document Formats

Hi there,
I wonder which are  the document formats that this skill supports, can I relly on the same list for Blob Storage:
https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-blob-storage#supported-document-formats
Thank you so much!

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

ID: 888362f6-45c3-2bb6-47b5-80c756ac77ad
Version Independent ID: 5ca9f578-ad8c-90a6-9ceb-a23b41427451
Content: Document Extraction cognitive skill - Azure Cognitive Search
Content Source: articles/search/cognitive-search-skill-document-extraction.md
Service: cognitive-search
GitHub Login: @Careyjmac
Microsoft Alias: chalton

Yes, the list of supported document formats should be the same.


Enhancement: provide/support jaeger probe

By enabling Jaeger probe support in LitmusChaos, it will be easier to gain powerful debugging capabilities to pinpoint issues during chaos experiments,  distributed tracing can be leveraged to gain visibility into the various flows of requests and timings of events across multiple micro-services.

@26tanishabanik thanks for creating this enhancement request. Do you have any design/implementation approach that you'd like to suggest? cc: @neelanjan00


UI: New React warning on Mapping Details add-to-mapping pulldown menu

Just noticed this today.

Establish a simple mapping.
Click the add-to-mapping select menu (source or target) in the Mapping Details pane

This does not occur with the expression select menu.
2.2.2 is okay

Causes:
react-dom.development.js:67 Warning: React does not recognize the isFocusedprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercaseisfocusedinstead. If you accidentally passed it from a parent component, remove it from the DOM element.     at div     at SelectGroup (http://localhost:6006/vendors~main.iframe.bundle.js:7423:11)     at ul     at SelectMenuWithRef (http://localhost:6006/vendors~main.iframe.bundle.js:7464:1)     at http://localhost:6006/vendors~main.iframe.bundle.js:7587:204     at div     at GenerateId (http://localhost:6006/vendors~main.iframe.bundle.js:9190:9)     at Select (http://localhost:6006/vendors~main.iframe.bundle.js:6750:9)     at div     at AddFieldTypeahead (http://localhost:6006/main.iframe.bundle.js:22255:21)     at div     at MappingFields (http://localhost:6006/main.iframe.bundle.js:32389:20)     at div     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at MappingDetailsSidebar (http://localhost:6006/main.iframe.bundle.js:21376:23)     at MappingDetailsView (http://localhost:6006/main.iframe.bundle.js:42709:28)     at div     at div     at TopologySideBar (http://localhost:6006/vendors~main.iframe.bundle.js:27693:11)     at Sidebar (http://localhost:6006/main.iframe.bundle.js:21628:19)     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at http://localhost:6006/main.iframe.bundle.js:21141:22     at CanvasProvider (http://localhost:6006/main.iframe.bundle.js:24176:23)     at DndProvider (http://localhost:6006/vendors~main.iframe.bundle.js:195478:23)     at TouchAndPointerProvider (http://localhost:6006/main.iframe.bundle.js:37937:23)     at FieldsDndProvider (http://localhost:6006/main.iframe.bundle.js:37960:24)     at Atlasmap (http://localhost:6006/main.iframe.bundle.js:11935:31)     at AtlasmapProvider (http://localhost:6006/main.iframe.bundle.js:12472:43)     at div     at unboundStoryFn (http://localhost:6006/vendors~main.iframe.bundle.js:53813:30)     at ErrorBoundary (http://localhost:6006/vendors~main.iframe.bundle.js:66081:5) printWarning @ react-dom.development.js:67 react-dom.development.js:67 Warning: React does not recognize theinputIdprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercaseinputidinstead. If you accidentally passed it from a parent component, remove it from the DOM element.     at div     at SelectGroup (http://localhost:6006/vendors~main.iframe.bundle.js:7423:11)     at ul     at SelectMenuWithRef (http://localhost:6006/vendors~main.iframe.bundle.js:7464:1)     at http://localhost:6006/vendors~main.iframe.bundle.js:7587:204     at div     at GenerateId (http://localhost:6006/vendors~main.iframe.bundle.js:9190:9)     at Select (http://localhost:6006/vendors~main.iframe.bundle.js:6750:9)     at div     at AddFieldTypeahead (http://localhost:6006/main.iframe.bundle.js:22255:21)     at div     at MappingFields (http://localhost:6006/main.iframe.bundle.js:32389:20)     at div     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at MappingDetailsSidebar (http://localhost:6006/main.iframe.bundle.js:21376:23)     at MappingDetailsView (http://localhost:6006/main.iframe.bundle.js:42709:28)     at div     at div     at TopologySideBar (http://localhost:6006/vendors~main.iframe.bundle.js:27693:11)     at Sidebar (http://localhost:6006/main.iframe.bundle.js:21628:19)     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at http://localhost:6006/main.iframe.bundle.js:21141:22     at CanvasProvider (http://localhost:6006/main.iframe.bundle.js:24176:23)     at DndProvider (http://localhost:6006/vendors~main.iframe.bundle.js:195478:23)     at TouchAndPointerProvider (http://localhost:6006/main.iframe.bundle.js:37937:23)     at FieldsDndProvider (http://localhost:6006/main.iframe.bundle.js:37960:24)     at Atlasmap (http://localhost:6006/main.iframe.bundle.js:11935:31)     at AtlasmapProvider (http://localhost:6006/main.iframe.bundle.js:12472:43)     at div     at unboundStoryFn (http://localhost:6006/vendors~main.iframe.bundle.js:53813:30)     at ErrorBoundary (http://localhost:6006/vendors~main.iframe.bundle.js:66081:5) printWarning @ react-dom.development.js:67 react-dom.development.js:67 Warning: React does not recognize theisSelectedprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercaseisselectedinstead. If you accidentally passed it from a parent component, remove it from the DOM element.     at div     at SelectGroup (http://localhost:6006/vendors~main.iframe.bundle.js:7423:11)     at ul     at SelectMenuWithRef (http://localhost:6006/vendors~main.iframe.bundle.js:7464:1)     at http://localhost:6006/vendors~main.iframe.bundle.js:7587:204     at div     at GenerateId (http://localhost:6006/vendors~main.iframe.bundle.js:9190:9)     at Select (http://localhost:6006/vendors~main.iframe.bundle.js:6750:9)     at div     at AddFieldTypeahead (http://localhost:6006/main.iframe.bundle.js:22255:21)     at div     at MappingFields (http://localhost:6006/main.iframe.bundle.js:32389:20)     at div     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at MappingDetailsSidebar (http://localhost:6006/main.iframe.bundle.js:21376:23)     at MappingDetailsView (http://localhost:6006/main.iframe.bundle.js:42709:28)     at div     at div     at TopologySideBar (http://localhost:6006/vendors~main.iframe.bundle.js:27693:11)     at Sidebar (http://localhost:6006/main.iframe.bundle.js:21628:19)     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at http://localhost:6006/main.iframe.bundle.js:21141:22     at CanvasProvider (http://localhost:6006/main.iframe.bundle.js:24176:23)     at DndProvider (http://localhost:6006/vendors~main.iframe.bundle.js:195478:23)     at TouchAndPointerProvider (http://localhost:6006/main.iframe.bundle.js:37937:23)     at FieldsDndProvider (http://localhost:6006/main.iframe.bundle.js:37960:24)     at Atlasmap (http://localhost:6006/main.iframe.bundle.js:11935:31)     at AtlasmapProvider (http://localhost:6006/main.iframe.bundle.js:12472:43)     at div     at unboundStoryFn (http://localhost:6006/vendors~main.iframe.bundle.js:53813:30)     at ErrorBoundary (http://localhost:6006/vendors~main.iframe.bundle.js:66081:5) printWarning @ react-dom.development.js:67 react-dom.development.js:67 Warning: React does not recognize thesendRefprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercasesendrefinstead. If you accidentally passed it from a parent component, remove it from the DOM element.     at div     at SelectGroup (http://localhost:6006/vendors~main.iframe.bundle.js:7423:11)     at ul     at SelectMenuWithRef (http://localhost:6006/vendors~main.iframe.bundle.js:7464:1)     at http://localhost:6006/vendors~main.iframe.bundle.js:7587:204     at div     at GenerateId (http://localhost:6006/vendors~main.iframe.bundle.js:9190:9)     at Select (http://localhost:6006/vendors~main.iframe.bundle.js:6750:9)     at div     at AddFieldTypeahead (http://localhost:6006/main.iframe.bundle.js:22255:21)     at div     at MappingFields (http://localhost:6006/main.iframe.bundle.js:32389:20)     at div     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at MappingDetailsSidebar (http://localhost:6006/main.iframe.bundle.js:21376:23)     at MappingDetailsView (http://localhost:6006/main.iframe.bundle.js:42709:28)     at div     at div     at TopologySideBar (http://localhost:6006/vendors~main.iframe.bundle.js:27693:11)     at Sidebar (http://localhost:6006/main.iframe.bundle.js:21628:19)     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at http://localhost:6006/main.iframe.bundle.js:21141:22     at CanvasProvider (http://localhost:6006/main.iframe.bundle.js:24176:23)     at DndProvider (http://localhost:6006/vendors~main.iframe.bundle.js:195478:23)     at TouchAndPointerProvider (http://localhost:6006/main.iframe.bundle.js:37937:23)     at FieldsDndProvider (http://localhost:6006/main.iframe.bundle.js:37960:24)     at Atlasmap (http://localhost:6006/main.iframe.bundle.js:11935:31)     at AtlasmapProvider (http://localhost:6006/main.iframe.bundle.js:12472:43)     at div     at unboundStoryFn (http://localhost:6006/vendors~main.iframe.bundle.js:53813:30)     at ErrorBoundary (http://localhost:6006/vendors~main.iframe.bundle.js:66081:5) printWarning @ react-dom.development.js:67 react-dom.development.js:67 Warning: React does not recognize thekeyHandlerprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercasekeyhandler instead. If you accidentally passed it from a parent component, remove it from the DOM element.     at div     at SelectGroup (http://localhost:6006/vendors~main.iframe.bundle.js:7423:11)     at ul     at SelectMenuWithRef (http://localhost:6006/vendors~main.iframe.bundle.js:7464:1)     at http://localhost:6006/vendors~main.iframe.bundle.js:7587:204     at div     at GenerateId (http://localhost:6006/vendors~main.iframe.bundle.js:9190:9)     at Select (http://localhost:6006/vendors~main.iframe.bundle.js:6750:9)     at div     at AddFieldTypeahead (http://localhost:6006/main.iframe.bundle.js:22255:21)     at div     at MappingFields (http://localhost:6006/main.iframe.bundle.js:32389:20)     at div     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at MappingDetailsSidebar (http://localhost:6006/main.iframe.bundle.js:21376:23)     at MappingDetailsView (http://localhost:6006/main.iframe.bundle.js:42709:28)     at div     at div     at TopologySideBar (http://localhost:6006/vendors~main.iframe.bundle.js:27693:11)     at Sidebar (http://localhost:6006/main.iframe.bundle.js:21628:19)     at div     at StackItem (http://localhost:6006/vendors~main.iframe.bundle.js:12962:11)     at div     at Stack (http://localhost:6006/vendors~main.iframe.bundle.js:12932:11)     at http://localhost:6006/main.iframe.bundle.js:21141:22     at CanvasProvider (http://localhost:6006/main.iframe.bundle.js:24176:23)     at DndProvider (http://localhost:6006/vendors~main.iframe.bundle.js:195478:23)     at TouchAndPointerProvider (http://localhost:6006/main.iframe.bundle.js:37937:23)     at FieldsDndProvider (http://localhost:6006/main.iframe.bundle.js:37960:24)     at Atlasmap (http://localhost:6006/main.iframe.bundle.js:11935:31)     at AtlasmapProvider (http://localhost:6006/main.iframe.bundle.js:12472:43)     at div     at unboundStoryFn (http://localhost:6006/vendors~main.iframe.bundle.js:53813:30

@igarashitm - I made the mapping details pane a little easier to read - wdyt?

@pleacu I think the gray that you used is a bit of a problem, especially wrt the blank white rectangle left above Targets. Maybe you could reverse that use and have the Sources and Targets title boxes remain white and the contents in gray?

The way it is now - the Sources and Targets boxes have a gray background (not just the title) with the contents white (it's a little hard to see with the screen capture).  Turning the Sources and Targets boxes white with the contents gray would lose the distinction between SRC/TGT.

LGTM :+1:

Ah right, the white space between Sources and Targets looks a bit too wide, having the fact that the vertical space is more expensive.

Hey @igarashitm + @jpav - here's the best I've got.  We can play around after this if anyone desires.


Remove 2 instances wildcard imports

Description
Removes 2 instances of wildcard imports introduced in https://github.com/opensearch-project/index-management/pull/1243.
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[ ] Commits are signed per the DCO using --signoff.
[ ] 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.

will have https://github.com/opensearch-project/index-management/pull/1252 to fix actions/upload-artifact deprecation


Login flow

Current Behavior
After registering my account, and going through all steps, I am back at the main DAO page

Expected Behavior
Should redirect to login page and explain how to set up Anchor

Ideal solution:
The last step of the onboarding walkthrough - after "I saved my keys somewhere" - should be to download anchor.
Steps To Reproduce
No response
What browsers are you seeing the problem on?
No response
How critical do you perceive the bug?
Critical
Anything else?
An alpha quality release can get away with this but it adds friction to the process and people might accidentally create additional accounts / register again / think registry didn't work

@pugakn you fixed this last week ?

Yes this should be fixed


Method requirements refactor

Refactor _method_requirements module in a similar manner to the refactoring done in #42.
Comes with the following fixes:

Discover method requirements in format strings (test case)
Discover method requirements in comprehension targets (test case)
Discover method requirements in lambda defaults (test case)
Discover method requirements in with statement target (test case, amended test case)
Discover method requirements in annotated assignment annotation (test case)

The following changes in functionality were also made:

Enabled discovery of method requirements inside of inner functions. This aligns the behavior of inner functions and lambdas. However, both inner functions and lambdas still have issues resolving method requirements when shadowing of self comes into play. So, perhaps this change warrants a more involved discussion. I went ahead and added this change to this pull request because it allows for a simpler implementation.

Looks good.  I think that shadowing self in an inner function would seem to defeat the purpose.  In any case, it's not as critical to get things exact when finding method requirements as order shouldn't affect behaviour, and missing attributes are assumed to be defined in __init__ or in the base class and are ignored.


feature request: make it possible to set the WORKDIR

In the "migrating from dockerfile" example, the base Dockerfile uses the WORKDIR statement https://docs.docker.com/reference/dockerfile/#workdir
However, I don't see a way to set the workdir in the configuration at https://github.com/ko-build/ko/blob/7067ad211ba58ff19ca705a177edff20169d8872/pkg/commands/options/build.go#L91-L172
As such, the workdir isn't set, e.g. docker image inspect -f '{{.Config.WorkingDir}}' something_made_with_ko:latest will return nothing.
ko inherits Docker config from a base container, but the default working directory of a Docker container is /, and if it's not set in the base, it will still default to /.
Docker containers that are designed to process data have a location where you'd expect to mount in a volume, e.g. /data. Without being able to set the detfault workingdir, you have to add an extra -w parameter to set it on each use.
docker run -w=/data -v `pwd`:/data  container_name:latest

Whereas, with the workingdir set, you could do:
docker run -v `pwd`:/data  container_name:latest

So, adding the ability to set the workingdir would be useful.

I've put together a draft PR which I think might resolve this, but I'm not familiar with the codebase and how best to test it end-to-end, so I'm likely to have missed something.


Dart2js source mirror DeclarationMirror.lookupInScope does not support constructors

Dart2js source mirror DeclarationMirror.lookupInScope does not support constructors

Now that dartdoc was moved away from the source-mirrors library and is using the analyzer parser directly, we will deprecate the source-mirrors library. So we are not planning to add this feature anymore.
@sigmundch


Stabilize and() for Maybe/Nullable/Undefinable

Fix https://github.com/karen-irc/option-t/issues/249

This change is

bors r+


API needs to be private

Heroku needs to be compatible with dotenv python library

Done, found a compatible .env library to use with heroku


Certain NPCs are incorrectly considered dead for MES and Entity Hider plugins

Type
Incorrect behavior
Bug description
The Remove dead npc menus option of the Menu Entry Swapper plugin and the Dead npcs option of the Entity Hider plugin cause some monsters to become uninteractable or invisible, which prevents you from killing them after phase changes or interacting them with state changes as intended. Some examples are:

Forms 2-4 of the Witch's Experiment
Nazastarool (maybe)
Pyromancers at Wintertodt
Nightmare / Phosani's Nightmare cannot be re-awakened once they die
Chompy birds cannot be plucked once killed
Kolodion's forms after the first one
Gadderanks from the In Aid of the Myreque quest
Desert lizards cannot be ice coolered
Dead ents cannot be chopped

Nazastarool should also be checked if this happens to them too.

The pyromancers in Wintertodt are also unable to be healed when they die because of this.

This also affects Phosani's nightmare (and presumably regular nightmare), after killing the nightmare can't be disturbed. Also after respawning if you turn Entity hider back on it will never become visible again even when alive.

I've rolled up the NPCs from the comments and those mentioned in #15146 and #15149 into the original post for this issue. Please consolidate any other NPCs needing fixing to this issue.

Noticed this yesterday with Desert Lizards (hidden / not targetable when ice coolers have to be used)

Dead Ents are also unable to be chopped with either of these plugins enabled.

Jubbly birds as well

Can you include nightmare/phosanis totems active ID in excluded npcs. You are unable to attack the totems once fully charged anyway and there are situations where you are unable to charge them because of entity hider. One example I can remember is during a parasite phase if you kill one near the totem the plugin removes the charge option on it for Id guess like 10 ticks then realizes its still alive.

@RsFoe This should already be fixed if you are on <IP_ADDRESS> instead of 1.8.24.

As of release <IP_ADDRESS> all reported NPCs have been fixed and we expect the changes applied for them should generally fix all NPCs. For any specific ones needing further fixing, please open new issues.


Gltf update: use instance iteration instead of hierarchy iteration

Objective

Improve example on how to use the SceneBundle to iterate on entities in the scene instance spawned

Solution

Use the scene instance and iter_instance_entities
Also improves a little the method and doc

I intentionally moved this example to interact with the actual components + hierarchy, as that is the pattern I think we should be encouraging people to use. Encouraging that pattern seems preferable to iterating a list that happens to render the example slightly better.
I do like the improvement to the iterator api though.

I intentionally moved this example to interact with the actual components + hierarchy

Ha I looked into git blame and was the one who last modified that but I had no memory of it, that explains it 😄
For me, doing it through the hierarchy takes it away from "scene update" of the example, and to another "hierarchy update". If we don't showcase the function made to iterate all entities in a scene spawned in this example, maybe that function isn't useful...


Refactoring the method Director::absoluteURL() to make return type only string

Description
Method Director::absoluteURL() return false if is not set $_SERVER['REQUEST_URI'] to support old default behaviour. Implement changes to make returning type only string. It makes this method easier to use and removes unnecessary additional checking the return type everywhere we invoke this method.

@sabina-talipova Can you please add a description to this issue?

The bit that returns false is here:
https://github.com/silverstripe/silverstripe-framework/blob/4e1b99b8c710bb8d88da91aecbf4d28d86146008/src/Control/Director.php#L461-L473
// Request relative urls rely on the REQUEST_URI param (old default behaviour)
if (!isset($_SERVER['REQUEST_URI'])) {
return false;
}

Before we decide exactly what the return type of the method is I think we should have more context in terms of what triggers the above code.

For what it's worth, the CLIRequestBuilder has some functionality to set $_SERVER['REQUEST_URI'] for command line usage. Anyone using the command line without using sake isn't doing things the supported way so I think we are okay not supporting their use case.


Alter scsi test code to work without the lsscsi binary

sysfs provides us the information as well, let's read that.
What this PR does / why we need it:
redhat has a slightly differently built virt-handler/nodes which end up with no lsscsi, causing this test to fail.
lsscsi isn't required for kubevirt functionality, and we can make it optional for the tests too.
Release note:

NONE

I thought we had discussed using lsblk --scsi instead of lsscsi

/hold
Missed the commend from @alicefr

I don't remember any discussion about lsblk, this requires no binaries and I don't expect CoreOS to have different /sys because they would need to be making kernel changes for that... I checked with a pod on openshift and at least /sys/bus/scsi/devices//model and /sys/bus/scsi/devices//block do exist.

I don't remember any discussion about lsblk, this requires no binaries and I don't expect CoreOS to have different /sys because they would need to be making kernel changes for that... I checked with a pod on openshift and at least /sys/bus/scsi/devices//model and /sys/bus/scsi/devices//block do exist.

Ack. Feel free to unhold once you have an agreement.

@maya-r good, thanks for checking. I'm fine also with the approach. lsblk will be a bit more concise as it just avoids the use of ls and grep. It should be also a pretty standard tool. But as I said, I'm fine with both solution

@akalenyu do you think we can cancel the hold too?

@akalenyu do you think we can cancel the hold too?

yep sure
/hold cancel

/retest-required

/cherry-pick release-0.53


Update spack submodule to release v0.17.2

spack v0.17.2 was released: https://github.com/spack/spack/releases/tag/v0.17.2
Let's update to this version (including all our changes).

@kgerheiser I looked at the diffs between v0.17.2 and our version, which is pretty close to develop (on track to become v0.18 at some point). There are many more differences than I expected. I would suggest to keep pulling in develop until v0.18 is released, and use spack releases from that point on.

I had the same idea of updating Spack to v0.17.2 after seeing the release yesterday, but yeah staying until v0.18 sounds good.


Error: parse error at (istiod/templates/revision-tags.yaml:4): unclosed action

I am trying to install the latest version of istio on my kubernetes cluster. So, I cloned the repo on my windows machine. I am following the steps:

1. echo "Creating istio-system namespace in cluster"
2. kubectl create namespace istio-system
3. echo "==Installing base Crds in istio-system namespace =="
4. helm install istio-base charts/base -n istio-system
5. echo "==Installing Istio CNI in istio-system =="
6. helm install istio-cni charts/istio-cni -n istio-system
7. echo "==Installing discovery component in istio-system =="
8. helm install istiod charts/istio-control/istio-discovery -n istio-system --set istio_cni.enabled=true

But at the last command(#8), helm install istiod charts/istio-control/istio-discovery -n istio-system --set istio_cni.enabled=true , I am getting the following error:
Error: parse error at (istiod/templates/revision-tags.yaml:4): unclosed action
When checked the code on line 4 of istiod/templates/revision-tags.yaml, I see the following code:
{{- $whv := dict  "revision" .Values.revision   "injectionPath" .Values.istiodRemote.injectionPath   "injectionURL" .Values.istiodRemote.injectionURL   "namespace" .Release.Namespace }}
Unable to understand what is the issue. Need your urgent help.
My local details:
helm version: helm version
version.BuildInfo{Version:"v3.5.4", GitCommit:"1b5edb69df3d3a08df77c9902dc17af864ff05d1", GitTreeState:"clean", GoVersion:"go1.15.11"}
kubernetes version:
kubectl version --short
Client Version: v1.20.0
Server Version: v1.22.4

Any directions would be highly appreciated.

Where are you running this from? Master? Can you try with helm 3.8?

Where are you running this from? Master? Can you try with helm 3.8?

I am running it from my windows command line. Not sure if 3.8 helm would help but will give it a try.

I mean against what istio charts?
The reason I ask about helm 3.8 is it works on my machine on 3.8
On Tue, Mar 22, 2022, 6:41 PM TJWaseem511 @.***> wrote:

Where are you running this from? Master? Can you try with helm 3.8?
I am running it from my windows command line. Not sure if 3.8 helm would
help but will give it a try.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/38061#issuecomment-1075820539, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPBWOVV5CTAE6T5KRTVBJZFJANCNFSM5RJ7Z5GA
.
You are receiving this because you commented.Message ID:
@.***>

I mean against what istio charts? The reason I ask about helm 3.8 is it works on my machine on 3.8
…
On Tue, Mar 22, 2022, 6:41 PM TJWaseem511 @.> wrote: Where are you running this from? Master? Can you try with helm 3.8? I am running it from my windows command line. Not sure if 3.8 helm would help but will give it a try. — Reply to this email directly, view it on GitHub <#38061 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEYGXPBWOVV5CTAE6T5KRTVBJZFJANCNFSM5RJ7Z5GA . You are receiving this because you commented.Message ID: @.>

Against the istio chart istio-control. I used helm 3.8 and it's working. Are the Helm version & the charts tied very closely?

@howardjohn Thanks for your suggestion. Using latest helm cli to run the charts resolved the issue.
Thanks & Regards,
Waseem TJ


Components definition

Description
Amend component type edit so that it constructs the appropriate component model, passing it through to the calling component with each change.

Amend component-type-edit to construct model with events
Amend component-create and component-edit to utilise the constructed model on save
Amend component-condition-create to use the model but not really do anything with it for now (I'd need to re-write the whole of list editing, which is time consuming and can come under my next PR)

Type of change
Please delete options that are not relevant.

[X] Refactor (non-breaking change which fixes some technical debt)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

[X] Unit tests
[X] Click testing

Checklist:

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation and versioning
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I have rebased onto master and there are no code conflicts

ideal would I would have time to click test this.. trusting you!

ideal world I would have time to click test this.. trusting you!

Not to worry, I'm click testing them!


edoc_opts (rebar.config)

{edoc_opts, [
    {includes, ["src"]},
    {preprocess, true}
]}.

The last option is especially interesting when macros (@elbrujohalcon's favourite Erlang component) are present. The includes I'd have to check (can't remember of the top of my head) but I know it was important for us at a point in time.

Good point. Thanks.


ModPE Script, that work on LOCAL (not External like play.lbsg.net).

That, it gaves a function or check box in Settings from BlockLauncher, which will called "Scripts from other Clients will work on your hosted Server", this would be cool and fun for the Users :)

yep it will be cool too if the custom items&blocks are visible to each other

Actually there is a temporal fix to that.
Lets say you have a sword mod like... this:
ModPE.setItem(700, "withersword", 0, "Wither Sword", 1);
function attackHook(a, v) {
player = Player.getEntity();
item = Player.getCarriedItem();
if (item == 700) {
if (v == player) {
Entity.addEffect(v, MobEffect.wither, 5*20, 3, false, true);
}
}
}
Obviously your friend can't see the sword, but if you hit him, he will get the wither effect anyways. In that case, you need to make a second script for other players of what could be missing.  So all that's left is to add the sword on his end. The host/client of the LAN world would use the top script, while all other players would use the following script:
ModPE.setItem(700, "withersword", 0, "Wither Sword", 1);
Like, that is it. Consider that the host is the client and one can say there "already is a multiplayer compatibility". All that's left is to add the basics into the other player's game. Now that the second player sees the sword, and is able to use it, you have made a successful(?) multiplayer ModPE thing. Correct me if i'm wrong.

that's working, but they can't use it when the other one doesn't have the script
for example I have the mod script the joined my sister's world and its not working and it seems she is dead but not
and when my sister uses the rideAnimals mod script its working fine (on mcpe 0.11.0)


[T2A5][F10-A3]Chia Wei Kang

Ready for review

Whoa for a lot of works being done include test case. :) good job!

Good work @weikangchia
Next time, remember to update the documentation as well.


When deleting a Stack/Service there should be a purge/restore similar to what is done for single containers

Right now when deleting a container via Rancher UI > Hosts one get the option to purge or restore. This is great functionality, especially the restore so one can recover from mistakes.
I think the same functionality should be made available from the Application > Stacks. When I choose a stack > delete, I expect the Stack to remain visible with state "deleting" and giving me the option of "purge" or "restore" the same way as it is done for the single container. The same should apply when deleting single Service within a Stack.

Removed ("deleted") vs Purged states are really intended more for companies with data-retention requirements to retain data for a period of time and be invisible to the (non-admin) users (though this is not currently actually the case, see #384 .  Will likely be bundled with a v2 API cleanup effort).  Not as a 2nd are you really-really sure you want to delete confirm.  Higher-level constructs like stack and service don't have any actual data to retain other than what is in the database (and not lost on delete).


Added chain suggest on a clean branch

Chain registry is used to get coingecko id, base denom and cointype @tombeynon


Issue with k8s.io/docs/tasks/access-application-cluster/ingress-minikube/

> kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0
...
> kubectl get pods
NAME                                 READY   STATUS    RESTARTS      AGE
web-57f46db77f-hlstp                 0/1     Error     4 (44s ago)   86s
>
> k logs web-57f46db77f-hlstp
exec /hello-app: exec format error
>

The image probably needs to be updated for Apple Silicon. I also tried hello-app:2.0 from the gcr link but it got the same error.

Related: #45420
I'm not sure it's feasible, or at least easy to do, but it would be great if all examples used multi-arch images.

It is an easy rebuild; I only made a ticket because I saw independent tutorial Youtubers fix it in a jiffy.
https://docs.docker.com/build/building/multi-platform/#building-multi-platform-images
But if not, can just have different image tags by arch.

/kind bug
/language en


Allow appmetrics to load AIX .a shared libraries

This sets the right library extension for AIX shared libraries.
Requires https://github.com/RuntimeTools/omr-agentcore/pull/27

LGTM


Missing Deployment Information for DOTNET 8 SSR Sites

Description
The introduction of prerendered Server-Side Rendered sites seems like a natural for Azure Static Sites, but a dotnet publish does not create a folder of HTML like HUGO, Svelte, etc. Maybe the functionality doesn't exist yet, but if it does, it would be helpful to have it documented here.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-7.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/host-and-deploy/index.md
Document ID
c82cf121-831d-75dd-a796-c735aad3b3e9
Article author
@guardrex

Hello @wonsil ... That's not what Blazor is designed to accomplish as a framework. Blazor is focused on allowing developers to use .NET/C# for browser UI and user interaction in the browser. An Azure Static Site can serve Blazor WebAssembly apps, but the Blazor framework isn't focused on creating a static HTML website to be hosted by a static website host. For more information on Blazor's design goals, see the description of Blazor in the introduction at https://learn.microsoft.com/aspnet/core/blazor/.

Then what purpose does the new Blazor 8 Static Site rendering mode supposed to serve?
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/render-modes?view=aspnetcore-8.0

Let me see ... I may have forgotten about a new 8.0 feature.

Also here: https://learn.microsoft.com/en-us/aspnet/core/blazor/javascript-interoperability/static-server-rendering?view=aspnetcore-8.0

I see how you're interpreting the language now. The content rendered by static server rendering is static HTML markup in individual webpages for clients (and to be distinguished from "interactive" where the client interacts with the server-based app over a SignalR connection between the server and client) ... that's true ... but Blazor doesn't create a website of static HTML pages. Blazor Web Apps are still server-side apps that run on the server and generate content on-the-fly. It's not a technology that publishes a static HTML website.
The basic problem with describing Blazor with "static" rendering is that terms are overloaded and mean different things in different contexts. Here, "static server-side rendering (static SSR)" only means how Blazor processes Razor markup and C# into individual pages. It doesn't mean what one would think coming from other technologies and tooling, where static websites are produced and published.
None of the article content that we added makes remarks about static SSR producing whole websites of static pages, and I'm not sure that we'd preemptively try to make statements in that regard ... yet anyway. I think we'd wait a little longer to see how many new-to-Blazor devs report confusion about what static SSR means.
Currently, the general concepts are covered earlier in the doc set at ...

https://learn.microsoft.com/aspnet/core/blazor/#build-a-full-stack-web-app-with-blazor
https://learn.microsoft.com/aspnet/core/blazor/hosting-models#blazor-server

What's a little closer to producing something that doesn't require a server ... i.e., a "static" type of published app ... would be a Blazor WebAssembly app. That's described at ...

https://learn.microsoft.com/aspnet/core/blazor/hosting-models#blazor-webassembly
https://learn.microsoft.com/aspnet/core/blazor/hosting-models#static-site-hosting

Keep in mind that your use of "static site" was something that you interpreted. That's not a phrase that any Blazor doc uses ... 🤔 AFAIK 😄. Indeed, one can't add the word "site" like that to "static" in that context of SSR (server-side rendering). That's not a Blazor design goal or feature. If you want to ask the product unit to create a new feature for Blazor that would truly produce a static HTML website, that might be a reasonable ask. Search their issues first tho (open and closed) because someone may have already asked them about it ...
https://github.com/dotnet/aspnetcore/issues

Ah, gotcha. It is confusing. I mean, even classic ASP.NET created static HTML on the server. 🤔
I keep seeing statements like, "Blazor is a full-stack Web UI," and I made the leap that it would also provide functionality to create static sites. It looks like for the meantime, those who want that capability will have to use something other than Blazor like Svelte, Gatsby, Hugo, etc. There is a market for static sites that can be deployed on Azure Static Sties, GitHub profiles, or even blob storage, so I think I will submit the new feature. It would be nice to teach new web developers the beauty of components early and let them add interactivity as they grow.
Separately, I see that someone else likes the idea of using Blazor to create static sites: https://github.com/tesar-tech/BlazorStatic
Thanks for your help!

Sounds good ... just keep in mind as you open an issue for them that standalone Blazor WebAssembly can be hosted the same way as a static HTML website. Azure Static Sites and GH Pages will host standalone Blazor WebAssembly apps, and I think Azure Blob Storage can host them, too. We don't cover that scenario, but I've heard of devs doing it. Such an app isn't a Blazor Web App, and "server rendering" concepts, such as static SSR and prerendering, don't apply in those static hosting scenarios.

Agreed that WASM can be served this way but that's a lot of extra bandwidth. It is also not SEO friendly as only the meta data, title, etc. are indexed but not the content.


How do you get ALL records from a table

It might seem silly, but I can't find it anywhere, the documentation always assumes that you want to retrieve a certain value matching a key, but what if I want all the records from a table (which I think is a pretty common case), I should be able to use something like Table.get(*) or just Table.get().
I appreciate any help. Thanks!

db.table.toArray()

or
db.table.each(callbackFn);

Yes I found it in the documentation a little bit afterwards, what a shame it was right there. Thank you for your support!!


Repository Ownership Transfer

@pyieh and @ramapalani signing on as new owners of the mask-passwords plugin, taking over for @oleg-nenashev
Unique Name Feature PR:
https://github.com/jenkinsci/mask-passwords-plugin/pull/25
Original HOSTING JIRA discussion:
https://issues.jenkins.io/browse/HOSTING-1144

no need to raise an issue here


Failed to read file!: NotAPicture

Reproducer
I ran the example command from the documentation in the readme.
RUST_BACKTRACE=1 cargo run --example tag_reader "/home/user/Downloads/11 - Howling Halls.flac"
<code>

Summary
Lofty fails to read metadata when there is an issue with the embedded picture contained within the audio files metadata. VLC and MPV are both able to play the file in question, and display the embedded image (front cover).
Here is the trace:
[user@pc lofty-rs-0.15.0]$ RUST_BACKTRACE=1 cargo run --example tag_reader "/home/user/Downloads/11 - Howling Halls.flac"
    Finished dev [unoptimized + debuginfo] target(s) in 0.02s
     Running `target/debug/examples/tag_reader '/home/user/Downloads/11 - Howling Halls.flac'`
thread 'main' panicked at 'ERROR: Failed to read file!: NotAPicture', examples/tag_reader.rs:15:10
stack backtrace:
   0: rust_begin_unwind
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
   2: core::result::unwrap_failed
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/result.rs:1651:5
   3: core::result::Result<T,E>::expect
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/result.rs:1033:23
   4: tag_reader::main
             at ./examples/tag_reader.rs:12:20
   5: core::ops::function::FnOnce::call_once
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/ops/function.rs:250:5

Expected behavior
Lofty should (ideally) be able to read the image data from the metadata. It also really shouldn't prevent retrieval of the rest of the metadata (song title, album etc) if it fails to read an image from said metadata. It would be preferable if lofty would return all valid metadata, and if it is unable to read certain metadata fields, it should just return null/an empty value for the metadata field in question.
I can't predict if users audio files will contain metadata (mainly images) that are not compatible with lofty, so being able to at least retrieve the metadata lofty can read, would allow me to use a placeholder for any data it can't read, so I can alert the user to problematic metadata, without having to forsake the entirety of the metadata due to one problematic field.
Thank you.
Assets
You will need this audio file to reproduce: audio file link
This is the image that is embedded in the metadata: Image link

Thanks for the report!
So this file actually had two issues:

It had a COVERART field in the Vorbis Comments, which I never got around to supporting since I've never seen it in the wild. So that's finally been addressed.
It had an invalid picture block with a picture type of 0xFFFFFFFF. This is again something I've never seen to indicate an invalid picture type. We now support any picture type by default, with the original error still being around for ParsingMode::Strict.

so I can alert the user to problematic metadata, without having to forsake the entirety of the metadata due to one problematic field.

This has been a goal for awhile. Lofty was originally made with the specifications in mind, but I quickly found out that many applications simply do not write metadata correctly at all. That's why ParsingMode was introduced. It's not used everywhere yet, as it was introduced (relatively) recently, which is why these types of errors pop up from time to time.

Thanks for the report!
So this file actually had two issues:
* It had a COVERART field in the Vorbis Comments, which I never got around to supporting since I've never seen it in the wild. So that's finally been addressed.

* It had an invalid picture block with a picture type of `0xFFFFFFFF`. This is again something I've never seen to indicate an invalid picture type. We now support any picture type by default, with the original error still being around for `ParsingMode::Strict`.

so I can alert the user to problematic metadata, without having to forsake the entirety of the metadata due to one problematic field.

This has been a goal for awhile. Lofty was originally made with the specifications in mind, but I quickly found out that many applications simply do not write metadata correctly at all. That's why ParsingMode was introduced. It's not used everywhere yet, as it was introduced (relatively) recently, which is why these types of errors pop up from time to time.

Thank you so much! You work fast :)
So I guess I can pull the latest changes and test again?
Cheers!

Could you try out #254 to see if it works for you? Thanks!

Could you try out #254 to see if it works for you? Thanks!

I get the following data returned now, so it looks good.
--- Tag Information ---
Title: Howling Halls
Artist: Russell Shaw
Album: Fable II
Genre: Soundtrack
Album Artist:
--- Audio Properties ---
Bitrate (Audio): 615
Bitrate (Overall): 621
Sample Rate: 44100
Bit depth: 16
Channels: 2
Duration: 04:29

Awesome! I'll get 0.16.0 out tomorrow.


Getting error while building fatJar

What went wrong:
I have a docker image on which I run my build process. For my application, I use gradle as build tool and am creating a fatJar using task fatJar. I am using javaslang in my application and while creating the fatJar, I am getting the following error.
Could not expand ZIP '/var/lib/jenkins/.gradle/caches/modules-2/files-2.1/io.javaslang/javaslang/2.0.5/86a8f8c75254d948dd128388b1097183e8c6564b/javaslang-2.0.5.jar'.

Could not copy zip entry /var/lib/jenkins/.gradle/caches/modules-2/files-2.1/io.javaslang/javaslang/2.0.5/86a8f8c75254d948dd128388b1097183e8c6564b/javaslang-2.0.5.jar!javaslang/?$Memoized.class to '/var/lib/jenkins/workspace/fk-tns-build/applications/services/build/tmp/expandedArchives/javaslang-2.0.5.jar_5qozg2y23zzsrefcm5v8akl0q/javaslang/?$Memoized.class'

I believe this is due to the class λ. Any pointers?

@aryaKetan yes, we have a class called λ.class. It seems to be charset-related.
@oehme is it possible to set charset to UTF-8 when using the Gradle fatJar task?

@aryaKetan we had a similar issue (#223). The workaround was to set the file.encoding system property, either in the JAVA_OPTS or in the GRADLE_OPTS. See a complete description here. /cc @oehme

Try to set sun.jnu.encoding=UTF-8

Gradle has no "fatJar" task, so I'm not sure what you are referring to. Gradle's Jar task uses UTF-8 for metadata (file name) encoding, because that is what the JVM expects. Sounds like you are using some community plugin which uses the system encoding instead.

@oehme : We have written this task :
task fatJar(type: Jar) {
manifest {
attributes 'Implementation-Title': project.name,
'Implementation-Version': version,
'Main-Class': project.mainClassName
}
archiveName project.name + ".jar"
zip64=true
baseName = project.name
from { configurations.compile.collect { it.isDirectory() ? it : zipTree(it) } }
with jar
}
In this, during zipTree while copying the λMemoized.class , I am getting the above error.
I added gradle.properties with content
systemProp.file.encoding=UTF-8
Still, same error.
Will try to set JAVA OPTS now.

Did you try systemProp.sun.jnu.encoding=UTF-8?

Did you try systemProp.sun.jnu.encoding=UTF-8?

If you have to mess with these settings, then there is a bug. This should not be an acceptable solution. Instead please let us know if you are experiencing such problems with Gradle's core APIs. I've created an issue for this.
@aryaKetan Thank you for the example. The problem is not in the Jar task, but in how Gradle expends zips using the zipTree method.

Stefan created the following issue: gradle/gradle#1363

@aryaKetan I will close this issue because it is not directly related to Javaslang. Thank you for reporting!


Add Instructions to play the Ping Pong game

Add Instructions to Players
Screencast from 04-10-24 01:43:37 PM IST.webm
There is need of some pop up window or alert messages that would tell the users how to play the game. It take me a while to figure out the actual key combination to play. I first tried mouse, then arrow keys of keyboard, then randomly every keys of the keyboard, then noticed that the 'A' & 'D' key has to be pressed to play the game.
So, In my opinion, a pop up window or alert message with this instruction that 'press A to move left and press D to move right' will be greatly helpful to the players who are playing for the first time.
Kindly assign the task to me, with gssoc-ext and hacktoberfest labels. Thank you.
@iamrahulmahato

The issue is already resolved by some contributor, so kindly close the issue. Thank You.


Added Secure Hub Firewall Example

Docs Build status updates of commit 7a95ce9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

latest/docs-ref-autogen/network/firewall.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/network/firewall.yml

Line 202, Column 93: [Suggestion-disallowed-html-tag] HTML tag 'indexToRemove' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 205, Column 116: [Suggestion-disallowed-html-tag] HTML tag 'value' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Error in updating package from marketplace

A customer with an 8.5.5 site is getting this error when updating a package from the marketplace.
The marketplace integration from their site was working OK a few hours previously when they first purchased the addon and installed it.
Error thrown with message "Call to undefined method Concrete\Core\Error\ErrorList\ErrorList::restore()"
Stacktrace: #22 Error in /var/www/html/concrete/src/Marketplace/RemoteItem.php:240 #21 Concrete\Core\Marketplace\RemoteItem:downloadUpdate in /var/www/html/concrete/controllers/single_page/dashboard/extend/update.php:77 #20 Concrete\Controller\SinglePage\Dashboard\Extend\Update:prepare_remote_upgrade in /var/www/html/concrete/src/Controller/AbstractController.php:315 #19 call_user_func_array in /var/www/html/concrete/src/Controller/AbstractController.php:315 #18 Concrete\Core\Controller\AbstractController:runAction in /var/www/html/concrete/src/Http/ResponseFactory.php:189 #17 Concrete\Core\Http\ResponseFactory:controller in /var/www/html/concrete/src/Http/ResponseFactory.php:367 #16 Concrete\Core\Http\ResponseFactory:collection in /var/www/html/concrete/src/Http/DefaultDispatcher.php:131 #15 Concrete\Core\Http\DefaultDispatcher:handleDispatch in /var/www/html/concrete/src/Http/DefaultDispatcher.php:59 #14 Concrete\Core\Http\DefaultDispatcher:dispatch in /var/www/html/concrete/src/Http/Middleware/DispatcherDelegate.php:39 #13 Concrete\Core\Http\Middleware\DispatcherDelegate:next in /var/www/html/concrete/src/Http/Middleware/ThumbnailMiddleware.php:76 #12 Concrete\Core\Http\Middleware\ThumbnailMiddleware:process in /var/www/html/concrete/src/Http/Middleware/MiddlewareDelegate.php:50 #11 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/concrete/src/Http/Middleware/FrameOptionsMiddleware.php:39 #10 Concrete\Core\Http\Middleware\FrameOptionsMiddleware:process in /var/www/html/concrete/src/Http/Middleware/MiddlewareDelegate.php:50 #9 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/concrete/src/Http/Middleware/CookieMiddleware.php:35 #8 Concrete\Core\Http\Middleware\CookieMiddleware:process in /var/www/html/concrete/src/Http/Middleware/MiddlewareDelegate.php:50 #7 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/concrete/src/Http/Middleware/ApplicationMiddleware.php:29 #6 Concrete\Core\Http\Middleware\ApplicationMiddleware:process in /var/www/html/concrete/src/Http/Middleware/MiddlewareDelegate.php:50 #5 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/concrete/src/Http/Middleware/MiddlewareStack.php:86 #4 Concrete\Core\Http\Middleware\MiddlewareStack:process in /var/www/html/concrete/src/Http/DefaultServer.php:85 #3 Concrete\Core\Http\DefaultServer:handleRequest in /var/www/html/concrete/src/Foundation/Runtime/Run/DefaultRunner.php:128 #2 Concrete\Core\Foundation\Runtime\Run\DefaultRunner:run in /var/www/html/concrete/src/Foundation/Runtime/DefaultRuntime.php:102 #1 Concrete\Core\Foundation\Runtime\DefaultRuntime:run in /var/www/html/concrete/dispatcher.php:45 #0 require in /var/www/html/index.php:3
Looking at the Marketplace code
    public function downloadUpdate()
    {
        $pkg = Package::getByHandle($this->getHandle());

        $fileURL = $this->getRemoteFileURL();
        if (empty($fileURL)) {
            return array(Package::E_PACKAGE_NOT_FOUND);
        }

        $file = Marketplace::downloadRemoteFile($this->getRemoteFileURL());
        if (is_object($file)) {
            return $file; // error
        }

        $r = $pkg->backup();
        if (is_object($r) && $r instanceof Error) {
            return $r;
        }

        $pkg = $r;

        try {
            $am = new PackageArchive($this->getHandle());
            $am->install($file, true);
        } catch (Exception $e) {
            $pkg->restore();
            $error = \Core::make('error');
            $error->add($e);
            return $error;
        }
    }

The above report appears to be a secondary error, that something went wrong with the download, then the error reporting failed because it got the error object mixed up with the package object and tried to call a package object method on the error object.
Whilst the customer site is 8.5.5, the code is the same in 8.5.6 and 9.0.0, so the same bug in the error reporting can manifest in the latest core version.

Just had a customer report the same error to me, they were attempting to update their theme.

Isn't this supported yet?

Anyone still encountering this? I have not seen it myself.

I have not seen it since. The customer with the issue did a manual update. For most of my projects I don't use marketplace integration.
It was it is a secondary error that arises as a result of trying to report an exception thrown from marketplace integration. The   issue with the code remains. The exception handler code is fundamentally flawed.
There is a test for $r is of type Error, but $r could also be of type ErrorList. Then setting $pkg=$r means the line $pkg->restore() in the exception handler can be run when the variable $pkg is not a Package object.

The code is the same in 8.5 and v9, so the code needs fixing.

Anyone still encountering this? I have not seen it myself.

Still occurring. I am hoping someone can help me.

I have created pull #10435 on the develop branch (@aembler - is that correct for v9?). It is a messy pull that aims to dodge the flaw in the exception handling. I do not expect the pull to be accepted as it would be cleaner to restructure the way the code works. However, I expect #10435 to illustrate why the original code was flawed and hence for someone with better knowledge than me of how this is supposed to work to create a better fix.
@akihiro0708. I do not expect this to resolve your original problem.

I don't think its on code branch you are on. (@aembler - what branch needs the equivalent fix for v8?)
This is aimed at the secondary error - the flaw in the error handling. However, it may allow the initial error to now be reported.

👍 Given the nature of the Marketplace class and the way it handles errors, I think this fix is as good as any.
The 8.5.x branch is the branch in GitHub that's still receiving attention for 8.5.8 and beyond.

#10439 does similar for 8.5.x
@akihiro0708. #10439 is for the code branch you are on.

Hi , John
I updated [concrete/src/Marketplace/RemoteItem.php] with the code you updated and it no longer terminates abnormally, but I get this message when updating.
Cannot back up old packages to "/var/www/html/application/files/trash" directory

Is there something wrong with my site setup? I don't know because there are no logs of what is wrong.
please , help me.

As the original github issue is now resolved, thie should really be asked as a new thread on the forums.
My first suggestion is to check the underlying operating system permissions for that folder. If that does no resolve your problem, please ask with a fresh thread on the forums.

Hi,John
I am very happy to receive your reply.
I'm sorry. I had to start a new thread for a different issue.
Directory permissions were
pwd
/var/www/html/application/files
ls -l
drwxrwxrwx 2 apache apache 4096  5月  1 09:25 1016
...
drwxrwxrwx 2 apache apache 4096  5月  1 09:25 test
drwxrwxrwx 2 apache apache 4096  5月  1 09:25 thumbnails
drwxrwxrwx 2 apache apache 4096  5月 14 09:58 tmp
drwxrwxrwx 2 apache apache 4096  5月  1 09:25 trash
cd ./trash
ls -l
0 items
Authority seems to be fine.
I will post it  on the forums.

Hi, John.
It has been a while.
I found the cause of this error.
I'm using Amazon S3 on my ConcreateCMS server.
[/var/www/html/application/files] I mount and use it here.
It seems that this is why I could not update the files.
I unmounted it and updated it without any problem. Thank you very much.


Update main.cpp

Thank you for your pull requests. Could you explain the purpose of your changes? I would also ask you to combine the changes into one PR to not clutter up the history of the repo.

I modified that part for make it an area, if not , will not make up an area.
Br.
Carrie
From: @.>
Sent: 2023年4月27日 0:16
To: @.>
Cc: Jia @.>; @.>
Subject: [External]Re: [fzi-forschungszentrum-informatik/Lanelet2] Update main.cpp (PR #296)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
[EXTERNAL] Do NOT click links or open attachments unless you recognize the sender and know the content is safe.
Thank you for your pull requests. Could you explain the purpose of your changes? I would also ask you to combine the changes into one PR to not clutter up the history of the repo.
—
Reply to this email directly, view it on GitHubhttps://github.com/fzi-forschungszentrum-informatik/Lanelet2/pull/296#issuecomment-1523693195, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYQGSSXD5VIA33FJODNNCODXDFC4HANCNFSM6AAAAAAXL7YPUU.
You are receiving this because you authored the thread.Message ID: @.***>

CONFIDENTIALITY NOTICE:
The content of this email and any attachments (“Email”) is confidential, may be privileged, subject to copyright and may be read, copied and used only by the intended recipient.
If you are not the intended recipient, please notify the sender by return email or telephone immediately and erase all copies (including any attachments) and do not disclose the Email or any part of it to any person. Any use, retention, disclosure, copying, printing, forwarding or dissemination of the Email is strictly prohibited if you are not the intended recipient.
ASTRI reserve the right to monitor all email communications through ASTRI’s networks.


fix: add some "debounce" to handleScroll

https://github.com/user-attachments/assets/aaa32b64-d68e-40b3-ac2b-3d70dcbaa63b
It also can be observed when phone/tablet orientations is changed.
On window resize we check some conditions in handleScroll, but sometimes clientHeight and clientWidth of scrollbarEl changes too slow, so I added some delayed call of handleScroll to solve it.

https://red36.gefara.xyz/issues/12931


Unable to Validate Model Due to Missing model_func.json File

Describe the bug
A clear and concise description of what the bug is.
During the model validation process, the system fails to locate the model_func.json file, which is essential for validation. This file serves as the starting template for the validation process.
To Reproduce
Steps to reproduce the behavior:

Go to the Deep Learning model Section and fill in the information
Click on Validate Button
See error

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS] Ubuntu
Browser [e.g. chrome, safari] chrome
Version [e.g. 22] 22.04

Additional context
Add any other context about the problem here.

#27 fixes this issue

Closing as this is fixed.


This dependency was not found:  * ~/sass/styles.scss in ./src/main.js

Updated to 0.5.6 and started a new project and this now appears. Has something changed in the latest release? /sass/styles.scss exists in /src. I've tried a number of different paths too, and still fails.

Missed this part again npm install -D sass-loader node-sass.
Might be worth having a more descriptive error message for sass.
Having a bad day! I blame the lack of coffee and nice weather outside.


rename psf method get_psf

it takes arguments, so I think the convention is to give it a name like get_psf

I was confused at first thinking it is data


Generate client using 'make generate-client'

This PR generates all clients for Grafana's backend using the make generated-client command.
Do not be intimidated by the diff - all files in this repo were generated using swagger through the make generated-client command! 🤖

Good spot, @mbarrien, thanks 👍  Opened a PR: https://github.com/grafana/grafana-openapi-client-go/pull/15


Add a tcp no delay option

For a consumer to nsqd, each messages will sent FIN to nsqd if it processes successfully.
I bench test consumer 10k message per second, the Ethernet is overhead by trigger too much interrupt requests to it(about 15k/s), and got very high(40%) hiq cpu usage.
When I turn off the tcpNoDelay, the interrupts per second decrease to about 10k/s and the performance has improved.
ps: Loopback may not trigger high hiq cpu usage, but the performance is still improved.

@chzyer thanks for digging into this a bit.  I'm concerned about enabling TCP_NODELAY by default and I'm not sure I want to rely on it to essentially buffer for us.
However, I think it is worth thinking about library level write buffers (there are already read buffers) on network IO to increase throughput and reduce syscalls.


Fixes various bug reports in dblog

Fixes #4790 (The bug listed in there)
In addition,

http://staging.beta.dosomething.org/admin/reports/event/1263993
http://staging.beta.dosomething.org/admin/reports/event/1264006
(By fixing this one, I believe we also fix this one? http://staging.beta.dosomething.org/admin/reports/event/1264007 )
http://staging.beta.dosomething.org/admin/reports/event/1263628

@angaither

:+1: :clap:


Redefinition of 'Object' vs Avoid accessing Ember.Object directly

Hi guys,
I have been running my app against the current master branch of ember-suave and came across an issue. Apparently the new disallowDirectPropertyAccess rule is conflicting with the another rule when using Ember.Object.
When I use const { Object } = Ember; I am seeing Redefinition of 'Object'.
When using Ember.Object directly I am seeing Avoid accessing Ember.Object directly

One way of circumventing this issue is using EmberObject by renaming it:
const { Object: EmberObject } = Ember;

Yes, that is expected. The syntax you show above (renaming to EmberObject) is the way to do it.


Making hover natural size never bigger than 400 by 800 pixels

Limiting the width and height of the hovers
In relation to https://github.com/microsoft/vscode/issues/199944

@alexdima If you can have a look here that would be great

The code was changed in order to simply set a maximum width for the color picker widget through CSS of 500 pixels


cloudflare_account_member: support status option

Current Terraform and Cloudflare provider version
Terraform v1.0.6
on darwin_arm64

provider registry.terraform.io/cloudflare/cloudflare v3.9.1

Description
cloudflare_account_member resource doesn't support the status attribute. This setting supports automatically accepting that invite,
cloudflare-go supports this field
Use cases
When adding a user through Terraform, they have to accept that invitation via email. That email often gets missed and we need to follow up with them. The invites also expire.
Potential Terraform configuration
resource "cloudflare_account_member" "jane_doe" {
  email_address =<EMAIL_ADDRESS>  send_email_invite = false
  role_ids = [
    "deadbeef",
  ]
  lifecycle {
    create_before_destroy = true
  }
}

Alternatively we could use status = "accepted" but since that field only receives two possible values a Boolean makes more sense to me 🤷
References
No response

heyo! 👋 there are a couple of considerations to this functionality that are kind of hidden and aren't obvious at first glance.
the first is that you cannot direct add a user that doesn't already exist which means this isn't a silver bullet for all scenarios. the second is that (despite the documentation being unclear), this isn't available to all plans to prevent spam inviting users; enterprise + tenants should be fine though.

Alternatively we could use status = "accepted" but since that field only receives two possible values a Boolean makes more sense to me 🤷

let's keep the Terraform schem matching the API response with status = "..." which helps automatically adding support to cf-terraforming without a field remap.
if you want to send a PR for this, i'm happy to take a look otherwise there will be a delay on adding this since it isn't a heavily requested feature for the provider.

the first is that you cannot direct add a user that doesn't already exist which means this isn't a silver bullet for all scenarios.

Can you explain this a bit more? What happens if that user doesn't already exist and we add them with status accepted, does it fail? Do we need to make two API calls, a PUT and POST?

the second is that (despite the documentation being unclear), this isn't available to all plans to prevent spam inviting users; enterprise + tenants should be fine though.

My assumption is we don't need to handle that in the terraform provider, the API error will just bubble up in that scenario?

if you want to send a PR for this, i'm happy to take a look otherwise there will be a delay on adding this since it isn't a heavily requested feature for the provider.

I appreciate that and will get to this when I get some time.

What happens if that user doesn't already exist and we add them with status accepted, does it fail? Do we need to make two API calls, a PUT and POST?

if you attempt to add a user that doesn't have a cloudflare account, you'll get a HTTP 400 back that will be "cannot add verified membership for non-existing user". Terraform will return an error in the apply/plan operations as the API call will fail. the number and combination of API calls aren't really relevant to the functionality here. if the user isn't verified (created account, confirmed email, etc) there isn't a way to force the status via the API or even the UI. this may make it less useful for some scenarios where you know someone should have an account but for whatever reason, doesn't already have an account.

My assumption is we don't need to handle that in the terraform provider, the API error will just bubble up in that scenario?

correct; you don't specifically need to handle it (just like other errors from the API that terraform handles out of the box) but do need to be aware that this may not (most likely won't) work across the board without the entitlement. you'll need to factor this into the testing as i suspect testing this on free/pro/biz zones may not give you the result you are expecting.


Switch to Maplibre GL JS and generate swipe map assets using input GeoTIFFs

Closes https://github.com/ConservationMetrics/guardianconnector-change-detection/issues/7.
High level summary: I adapted GCCD to accept optional before (t0) and after (t1) GeoTIFF inputs, and to generate swipe map assets if provided. In so doing, I replaced Mapbox GL JS with MapLibre GL JS, because the latter library has support for the pmtiles tile format which I am leveraging to visualize the before/after scenes. There are also real world fixtures in the repo now, representing the actual data that GCCD will be working with at first.
Why MapLibre and PMTiles: PMTiles is a new cloud-optimized single-file tile format for vector and raster data. Much like mbtiles, pmtiles offers the advantage over the xyz/ directory format that all map tiles are stored and can be deduped from a single file. Pmtiles offers an additional advantage over mbtiles (a SQLite database): they can be rendered using JS in the browser without needing an additional server (like Tileserver-GL) to serve the tiles. The pmtiles Javascript library has a plugin for MapLibre GL that uses its addProtocol feature.
An additional motivation for substituting Mapbox for MapLibre is that we don't need to worry about access tokens (and potential costs if we exceed the Mapbox freemium API threshold) anymore, and we are staying closer to our FOSS principles.
Detailed description:
Granular level of detail because I realize there is a lot going on here! (Each commit is scoped to a particular piece so when I merge, I won't squash.)
Main script

main.py now accepting arguments with GeoTIFFs file paths (and rage quits if only one has been provided).
MapLibre GL JS implemented across the map templates.

We are now using Bing satellite from Virtual Earth as the background map, and using fonts and glyphs from Protomaps.
MAPBOX_ACCESS_TOKEN and MAPBOX_STYLE env vars removed from the scripts.
Created a new template for map swipe, implementing the pmtiles protocol to visualize the before/after maps; for now, using self-hosted assets from maplibre-gl-compare since they are not (yet) hosted anywhere for public usage.
Minor thing - adopted a mapgl naming convention since a lot of our outputs are map library agnostic.

In utils.py, copy_geojson_file renamed to copy_input_files and expanded to also copy over the GeoTIFFs.
In generate_maps.py, generate_html_map is now generating either the existing HTML map template or the new swipe one, depending on whether GeoTIFF arguments were provided.
In generate_tiles.py:

generate_pmtiles_from_geotiff is running through a series of steps: tif -> xyz/ -> mbtiles -> pmtiles. I know, seems redundant, but I couldn't get a more direct conversion running as of yet. I'll revisit this in the future; I think there will be a lot more support for working with pmtiles soon on the horizon.
I turned each of these steps into more bite-size functions, and adapted the rest of the script to use these too, where needed.
To accomplish these conversions, the use of go-pmtiles and gdal_translate libraries was needed. I documented this in the READMEs and also added these to the Dockerfiles.

Docker services

docker-generator.py adapted with the same script changes.
All Dockerfiles (generate and FastAPI) are pulling in the required libraries that have been added (GDAL and pmtiles).
run.sh and docker-compose.yml updated to optionally accept the new flags, and run a docker command with or without them.

Other

example.geojson updated with real data; example_t0 + example_t1 GeoTIFFs added.
READMEs updated and sample swipe map screenshot added.

Disclosure:
While I have tested the script with the Docker Compose and Python Package execution methods, I have not yet done so with the FastAPI service endpoint. I will turn to that next as I work on the frizzle component for handling change detection messages.

The suggestions were implemented, and the observation about improving our error handling for the HTTP server were captured in the engineering tasks table.


SW-5122 Create ParticipantProvider used in the Terraware frontend for retrieving participant data for an org. Use it to determine if a user should see the regular Home page or the Participant Home page

Create ParticipantProvider used in the Terraware frontend for retrieving participant data for an org
Use it to determine if a user should see the regular Home page or the Participant Home page

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2515
#2514  👈
#2513
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite

Merge activity

Apr 16, 11:35 AM EDT: @nickgraz started a stack merge that includes this pull request via Graphite.


use the actual unique id to compare connection

This PR fixes https://github.com/microsoft/azuredatastudio-postgresql/issues/113
there are 2 bugs behind this issue:

one needs to be made in PG extension, @nasc17 as we chatted offline, please add 'isIdentity= true' to the port option in your package.json, this will make ADS be able to treat them as different connections.
Object explorer is not using the actual unique string of connections to compare instead it is using the hardcoded options when looking for existing profiles, I am fixing this problem with this PR.

btw, MSSQL do not have the same issue because we are hardcoding it in ADS core to append the port number after the server name.

@nasc17 why did you closing this pr? by mistake?

@nasc17 why did you closing this pr? by mistake?

Yes mistake. When I closed the PRs I had opened tied to this it must have closed here as well.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 41.683%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
26710

Relevant Lines:
58050

💛  - Coveralls


Disable jumbo test build for mix/

Summary
The PR title says it all. I am guessing the jumbo build are the cause for the recent occasional test errors  (the test fail during compilation sporadically with an error that is completely unrelated to the PRs). My current guess is they started occurring after we enabled jumbo build back.
This will probably cause the tests to run a bit longer - but rather they run longer and not fail sporadically.
Checklist

[x] Copyright holder: Rok Češnovar
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

awesome! I have 2 prs  - #2710 and #2721 - that failed CI due to this. Should I wait until this is merged to request a restart?

@spinkney I restarted those tests, please let me know if they fail again. By that time maybe this PR will be merged in though.


Install gcc 4.8 on SUSE < 12

Description
This allows builds of Ruby on SLES/SUSE 11.4 to succeed.
Issues Resolved
[List any existing issues this PR resolves]
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Signed-off-by: Scott Hain<EMAIL_ADDRESS>

@chef-cookbooks/engineering-services

Do we support Suse < 12?

@tas50 sles is treated as suse, and we support sles 11.4

I didn't realize we supported SLES 11.


Unit tests additions and few other fixes

Added new unit tests
Fixed some comments
Made imports more specific
Fixed typos
Added '_' invalid character check in addresses for script.test_array
Deleted redundant block_index argument

Coverage increased (+1.02%) when pulling 063bb02a1aade227cae092fd79d2e66965bb0fa2 on Millz0r:unit_tests into 62ec327935f69fb866878f2d238955252ccd42b6 on CounterpartyXCP:develop.


Copy probers and pager duty script from private repo

Signed-off-by: Priya Wadhwa<EMAIL_ADDRESS>
Summary

Release Note

Documentation

Was there an issue on moving this into a public repo?

Ah, it was for actions quota!

Yep, the TSC agreed in the last meeting.


feat: add cargo binstall support

Adds binary installation support via binstall (https://github.com/cargo-bins/cargo-binstall).

defer to @onbjerg here
but if we do that, we should also mention this option in the README

Typically, it just works if the crate confirms binstall expectations, but the current convention is a bit non-conformant (not necessarily wrong), will update the README as well.

Not sure that we want this? Seems like it adds more ways to install which seems redundant?

Not sure that we want this? Seems like it adds more ways to install which seems redundant?

binstall is the de-facto crate used for install Rust binaries, for e.g. see cargo watch (https://github.com/watchexec/cargo-watch). Imo, this would greatly improve the UX, because you just need to install binstall once and each upgrade you can just run cargo binstall reth and it would be upgraded, built and installed automatically.

As long as we don't have to do anything special for this to work, it's ok to add I guess. Imo cargo binstall is more for Rust utilities and Cargo plugins, so I don't see the big benefit here, but OTOH there isn't really a downside either (again, as long as we don't have to do anything special to make this work)

@QEDK I accidentally fast merged it because I thought CI was tripping but I had to revert it. Please open up the PR again; this is not working because of your change to Cargo.toml


Adding _getRowComponents function

Adding a function that retrieves the list of components produced by ComponentRenderer in given Grid row.
It's based on _getCellComponent but it retrives all cell components in a specific row.

Could you please provide an use-case for this functionality? I'm not convinced of its usability and I have the following counter-reasons:

A grid with all columns using ComponentRenderer is known not to perform well, and is considered an anti-pattern;
The _getCellComponent() is mostly used to click buttons present in grid columns
The _expectRow() should use toPrettyString() on ComponentRenderer columns, therefore you can assert on the String component representation using expectRow() in a much easier fashion.

Hi @mvysny ,
I wasn't aware of the usage of the usage of expectRow() on ComponentRenderer columns.
In my grid, I used ComponentRenderer because I wanted to access the rendered component so that I can apply style on it using element.style API. I didn't use ClassNameGenerator because style values are dynamic (for example the background color is calculated in my kotlin code depending on several conditions).
But indeed this made the grid very slow.  so I'm tninking to use ClassNameGenerator and try to enumerate almost all possible styling values.
I thought to provide this method in case it's usefull for someone but I think your reasons are valid so I'm gonna close this PR.


Adding Benchmarks back into agbench and updates to agbench

Why are these changes needed?
Added benchmarks back into autogen, notably GAIA, AssistantBench, HumanEval and WebArena. Renamed everything to be consistent with new package, enabled creation of endpoint from environment file.
Modified readme of magentic-one with a few changes regarding installation instructions
Fixed renaming issues in agbench to be consistent with new package structure.

@gagb  and @afourney  please review changes to agbench.

should be good to merge!


Some weird errors show up when using paths for resolve.alias .

Can you reproduce the problem with latest npm?
no, I use yarn and it's the latest
Description
I want to add some common alias in both prod and dev webpack configuration files. To avoid repetitive coding I decided to write them in paths.js, like this:
...
// config after eject: we're in ./config/
module.exports = {
  ...
  servedPath: getServedPath(resolveApp('package.json')),
  //common alias
  resolvePaths: {
    pages: resolveApp('src/pages'),
    common: resolveApp('src/common'),
    utils: resolveApp('src/utils'),
    components: resolveApp('src/components'),
    modals: resolveApp('src/components/Modals')
  }
};

Then I use it in both configuration files, like this:
  resolve: {
    ...
    extensions: ['.js', '.json', '.jsx', ''],
    alias: Object.assign(paths.resolvePaths,{
      'react-native': 'react-native-web',
    })
  }

But it doesn't work and some weird errors show up:
Failed to compile.

Error in ./src/common/less/base.less
Syntax error: Unexpected '}' at line 1 column 16 of the JSON5 data. Still to read: "}"
 @ ./src/common/less/base.less 4:14-192 13:2-17:4 14:20-198

However, If I change the part of path.js to:
...
// config after eject: we're in ./config/
module.exports = {
  ...
  servedPath: getServedPath(resolveApp('package.json')),
  //common alias
  pages: resolveApp('src/pages'),
  common: resolveApp('src/common'),
  utils: resolveApp('src/utils'),
  components: resolveApp('src/components'),
  modals: resolveApp('src/components/Modals')
};

And use it in configuration files like this:
  resolve: {
    ...
    extensions: ['.js', '.json', '.jsx', ''],
    alias: {
      'react-native': 'react-native-web',
      'common': paths.common,
      'pages': paths.pages,
      ...
    })
  }

It will work.
Expected behavior
It works correctly.
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected):  have ejected
node -v:  v6.10.2
npm -v:  4.6.1

Then, specify:

Operating system: macOS 10.12.4
Browser and version: Chrome 58.0.3029.110 (64-bit)

Thanks.

Since you have ejected, we encourage you to ask for help in channels specific to underlying projects (in this case, webpack). We only know our own configuration well, and we can’t really provide support for every possible change in the configuration. I’ll close this as it’s not very actionable for us, but maybe somebody who knows webpack well can help you. Cheers!

Please open this issue on Stack Overflow or similar help community.
Unfortunately, we are too busy to provide support for ejected setups. Sorry!
This seems like a malformed webpack loader configuration or invalid syntax in your LESS.
Please be mindful to read all the comments we have around the loader section.
If something's not clear, please let us know or send a PR improving the documentation. Thanks!

@gaearon @Timer ok, I'll ask some other places. thanks for your reply.

FWIW, if you’re just trying to enable absolute imports like import MyPage from 'pages/MyPage' you didn’t need to eject. You can just create an .env file in your project and add NODE_PATH=src to it.

I'll try it. Again, thank you for your help.


Generated api json file has only one line

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
The generated api json file has only one line, which is very hard to read.
What you expected to happen:
The generated api json file has readable format.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

/assign

Will you modify the file manually?

I will not modify it, but will likely read it.


Create New file named OutputSourceCode.c

What type of PR is this? (check all applicable)

[ ] 🚀 Added Name
[ ] ✨ Feature
[ ] 🌟 stared the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Add Link of GitHub Profile
https://github.com/DhananjayPorwal

C Program Added


Proposal: Use AWS AppSync for API

Updating the tutorial to show how to use AWS AppSync for the API instead of the REST API would take this to the next level.  Including being able to setup and configure AppSync via Serverless Framework for multi-environment deployments!

Ah yeah we've been excited about AppSync as well. It's definitely something we'll take a look at for adding to the tutorial.

I got the following message in AWS Console while trying to create Cognito Identity Pool while following these steps

Links:

AWS AppSync
Start building with AWS AppSync now

AWS also recommends using AppSync over Cognito Sync

Hmmm we aren't really using Cognito Sync as a part of this tutorial. I think we can ignore that message for now. Most likely we'll have AppSync as a separate section in the guide.


Bug: When no comment is entered, the send button should be disabled

Currently, nothing happens when nothing is entered, but it would be better if the button is disabled as long as no input is entered.

Closed with  f0a819c


[Monitoring V2] Routes and Receivers should redirect if the user does not have permissions

The paths /dashboard/c/{cluster-id}/monitoring/monitoring.coreos.com.route and /dashboard/c/{cluster-id}/monitoring/monitoring.coreos.com.receiver should redirect a user to the install app page if they do not have permissions to the Monitoring Pane.
Currently, only the Overview page /dashboard/c/{cluster-id}/monitoring redirects.

Since this issue is no longer a requirement of https://github.com/rancher/rancher/issues/31630 (see https://github.com/rancher/rancher/issues/31630#issuecomment-793138251), I'm removing the 2.5.7 milestone in favor of 2.5.x.