Read email by date (question)

Is it possible to get emails from a POP server after some date? Or will I need to get all emails and then select some of them?

Dig into the POP protocol see what you can achieve with it. The server is meant to be very simple, so if you're expecting to discover a server-side filtering/sorting mechanism, look into IMAP instead.


Update version from 0.0.141 to 0.0.142

This is an automated version-update on pyproject.toml.
The workflow was triggered by a succesfull pull request from branch:
With push event SHA of: 6f579875c675ef1d7ff0ae08492ba6afa68ab0b5
This action is performed by the Github Action: publish.yml after every accepted pull request. When finished,
this will have published the latest patch of the Extractable codebase to Pypi so it can be pip installed.

updated version in pyproject.toml from 0.0.141 to 0.0.142


Add docs for 'result_index'  usage and a system test.

Closes #3166.
Updated the docs and added a system test for using result_index.

No code change required?

@lukesneeringer turns out there isn't!
Since streaming is just returning the proto for now.

It seems that is not correct: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/1455


New Remove-ODTExcludeApp and supporting functions

Added Remove-ODTExcludeApp, which removes a specific ExcldeApp-entry and the supporting functions like ValidateExcludeAppID and SelectExcludeApp. Readme file was not updated

Hi @manoth-msft, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@manoth-msft, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

@manoth-msft Thank you for this contribution!  We have merged this change into our repository.


Comparative statistical analysis doesn't start

I'm trying to use the Network Randomizer in cytoscape to create a random network based on my original one and compare the network characteristics of these two. I successfully created a random network using the app (Erdos-Renyi model), but I can't calculate the comparative statistics. Nothing happens after selecting the respective networks and clicking on "start statistics". I'm using cytoscape 3.7.0. Do you know what causes this issue?

Dear Ingrid,
the statistics module works when both your network (real and random) share at least a common attribute, that will be listed in the Statistical Analysis dialog once you selected the Random and Real Data networks!
Do they have attributes?
and sorry for the late reply,
gabriele


Training framework?

Is there any plan to support the training of different models from this library itself

Yes, there is plan for it in near future (2-3 months approx.)! Soon, I will post the future roadmap with tentative timelines!


open-payments build failing

https://github.com/interledger/rafiki/pull/709 has introduced a build error for open-payments

Both pnpm -r build and pnpm --filter open-payments build produce
src/client/requests.ts:36:5 - error TS2322: Type 'ValidatedResponse<T>' is not assignable to type 'T'.
  'T' could be instantiated with an arbitrary type which could be unrelated to 'ValidatedResponse<T>'.

However, building open-payments isn't currently being tested in the GitHub Actions, because we only run:
https://github.com/interledger/rafiki/blob/d41fa3cab5d3aad267efe8d0459de766d05b0a9e/.github/workflows/lint_test_build.yml#L82
which doesn't include open-payments because it is currently excluded in
https://github.com/interledger/rafiki/blob/d41fa3cab5d3aad267efe8d0459de766d05b0a9e/tsconfig.json#L2-L14

I think the build error will be resolved by:

https://github.com/interledger/rafiki/pull/705

@wilsonianb I'll merge in master into https://github.com/interledger/rafiki/pull/705 and make sure 🆗

@mkurapov want to go ahead and add open-payments to tsconfig.json in that pr?

@wilsonianb on it :+1:


Week 4 - Python Web Server

One-minute video
Psychology and the Good Life Notes
Collaboration Notes
Group Python Server Repo
Blog our team collaborated on analyzing the form's results Link
Extra Point survey  our team did to gauge students mental health

I think that you deserve a 2.7+ because you did a very nice job with the notes on each video as well as the collaboration notes and an extra survey based on the psychology of a good life.

Really good job explaining the Python server Navan, you had lots of info!

I think that you deserve a 2.7 because you did not cover all necessary ideas.

Nice ideas for change.  Realization of changes not real clear in video.  Seems like you hit on key items.  2.7

Nice job with showing the notes and covered most of all the necessary work and ideas!

Great job on making changes in your flask site. I believe you deserve a 2.7+ since you incorporated the google form.

You deserve a 2.7 because you satisfied all the requirements.

I think you earned a 2.7 because you created a great video showing edits being made locally, although I feel that the video was fast.

Did all that was necessary with a solid understanding 2.7.


duplicity: Add backblaze-b2 as a build input to duplicity

Motivation for this change
Add backblaze b2 support to duplicity.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @peti

@GrahamcOfBorg build duplicity

Any comments on what I should do next?


Update gateway status

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

Comparison is base (11432d6) 81.21% compared to head (161477c) 81.20%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1138      +/-   ##
==========================================
- Coverage   81.21%   81.20%   -0.02%
==========================================
  Files         148      148
  Lines       16618    16618
==========================================
- Hits        13497    13495       -2
- Misses       2481     2483       +2
  Partials      640      640

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


pull request for e2e test at 11/18/2016 13:26:06

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Breaking behaviour change in error handling between 1.11.6 and 1.11.7

This was caused by the change in pkg/kgo/source.go regarding the error treatment.
Before, I was able to react to certain errors, reconnect and receive messages again.
If you run the below example with v1.11.6, it will print that it tries to reconnect, which in my real codebase worked and led to consuming the messages that were publish after reseting to a fresh kafka instance.
With v1.11.7, this behaves differently. We wait for the messages forever and no attempt to reconnect is possible.
It doesn't seem to matter whether a group has been specified or not.
Either way, behaviour changed :thinking:
The example starts a kafka instance, resets it and purges it again.
The example should run as long as you have docker installed.
Its quite big, but only the main method really matters i guess.
package main

import (
	"context"
	"encoding/json"
	"errors"
	"fmt"
	"log"
	"os"
	"sync"
	"time"

	"github.com/gofrs/uuid"
	"github.com/ory/dockertest/v3"
	"github.com/ory/dockertest/v3/docker"
	"github.com/twmb/franz-go/pkg/kerr"
	"github.com/twmb/franz-go/pkg/kgo"
)

func main() {
	assertNoError(kafka.reset(), "error starting kafka")
	defer func() {
		// If it is error unsupported, it means the tests didn't require kafka.
		if err := kafka.purge(); err != nil && err != errUnsupported {
			fmt.Printf("Coludn't purge Kafka: %s\n", err)
		}
	}()

	produceClient, err := kgo.NewClient(
		kgo.SeedBrokers("localhost:9092"),
		kgo.AllowAutoTopicCreation(),
	)
	if err != nil {
		panic(err)
	}

	topic := "reconnect-topic"
	group := "reconnect-group"

	listenClient, err := kgo.NewClient(
		kgo.SeedBrokers("localhost:9092"),
		kgo.ConsumeTopics(topic),
		kgo.ConsumerGroup(group),
	)
	if err != nil {
		panic(err)
	}

	var wg sync.WaitGroup
	log.Println("Listening ...")
	go func() {
		defer log.Println("Listener has closed")
		for {
			fetches := listenClient.PollRecords(context.Background(), 1)
			if fetches.IsClientClosed() {
				// No intention of retrying, as the listener closed has no more
				// interest in listening.
				log.Println("Client Closed")
				os.Exit(1)
				return
			}

			if kgoErrors := fetches.Errors(); len(kgoErrors) > 0 {
				for _, kgoError := range kgoErrors {
					// Documentation for 1.11.6 indicates we might want to restart listening here.
					if err, ok := kgoError.Err.(*kerr.Error); ok {
						log.Println("Imagine reconnect here (We expect this)", err)
						os.Exit(0)
					}

					log.Println("error", kgoError)
				}

				log.Println("Imagine listener invocation here", kgoErrors)
				wg.Done()
				continue
			}

			// We can iterate through a record iterator...
			iter := fetches.RecordIter()
			for !iter.Done() {
				record := iter.Next()
				log.Println("Imagine listener invocation here", string(record.Value))
				wg.Done()
			}
		}
	}()

	log.Println("Publishing ...")
	wg.Add(2)
	assertNoError(publish(produceClient, topic, map[string]string{"field": "a"}), "error publishing message")
	assertNoError(publish(produceClient, topic, map[string]string{"field": "b"}), "error publishing message")

	log.Println("Waiting to receive messages ...")
	wg.Wait()

	log.Println("Shutting down kafka for reconnect test ...")
	assertNoError(kafka.reset(), "error restarting kafka")

	log.Println("Publishing ...")
	wg.Add(2)
	assertNoError(publish(produceClient, topic, map[string]string{"field": "c"}), "error publishing message")
	assertNoError(publish(produceClient, topic, map[string]string{"field": "d"}), "error publishing message")

	log.Println("Waiting to receive messages ...")
	wg.Wait()
}

func assertNoError(err error, msg string) {
	if err != nil {
		panic(fmt.Errorf(msg+":%w", err))
	}
}

func publish(client *kgo.Client, topic string, payload any) error {
	bytes, err := json.Marshal(payload)
	if err != nil {
		return err
	}

	record := kgo.SliceRecord(bytes)
	record.Topic = topic
	result := client.ProduceSync(context.Background(), record)
	return result.FirstErr()
}

type kafkaInstance struct {
	host string
	port int

	start func() error
	// _purge must not be called directly, call purge instead.
	_purge func() error
}

var errUnsupported = errors.New("unsupported operation")

var kafka = &kafkaInstance{
	host: "localhost",
	port: 9092,
	start: func() error {
		return errUnsupported
	},
	// Initially nil, cause there isn't anything to purge
	_purge: nil,
}

func (k *kafkaInstance) purge() error {
	fmt.Printf("Purging Kafka instance at %s:%d\n", k.host, k.port)
	if k._purge != nil {
		return k._purge()
	}

	return nil
}

func (k *kafkaInstance) wait() {
	address := fmt.Sprintf("%s:%d", k.host, k.port)
	timeout := 30 * time.Second
	fmt.Printf("Waiting %s for Kafka at %s ...\n", timeout.String(), address)
	if !available(address, timeout) {
		fmt.Println("Kafka not found at", address)
		os.Exit(1)
	}

	fmt.Println("Kafka available at", address)
}

func (k *kafkaInstance) available() bool {
	address := fmt.Sprintf("%s:%d", k.host, k.port)
	fmt.Printf("Check for Kafka at %s ...\n", address)
	if !availableNoWait(address) {
		fmt.Println("Kafka not found at", address)
		return false
	}

	fmt.Println("Kafka available at", address)
	return true
}

func (k *kafkaInstance) reset() error {
	fmt.Printf("Resetting Kafka instance at %s:%d\n", k.host, k.port)
	if err := k.purge(); err != nil {
		return err
	}

	if err := k.start(); err != nil {
		return err
	}

	return nil
}

// availableNoWait does the same check as Available, but only attempts it once
// and instantly (however long one try takes) returns, no matter the result.
func availableNoWait(address string) bool {
	options := []kgo.Opt{
		kgo.SeedBrokers(address),
		// AutoTopicCreation is disabled by default.
	}
	client, err := kgo.NewClient(options...)
	if err != nil {
		return false
	}
	record := kgo.StringRecord("ANYONE THERE?")
	record.Topic = "non-existent" + uuid.Must(uuid.NewV4()).String()

	ctx, cancel := context.WithTimeout(context.Background(), 5*time.Second)
	defer cancel()
	result := client.ProduceSync(ctx, record)
	if err := result.FirstErr(); err != nil && !errors.Is(err, kerr.UnknownTopicOrPartition) {
		return false
	}
	return true
}

// Available attempts to send a message to a non-existent topic. Autocreation
// of the topic is disable during this process, in order to make sure we
// receive a "topic doesn't exist" type of error. This message blocks until
// we know that Kafka is available or run into the timeout.
func available(address string, timeout time.Duration) bool {
	options := []kgo.Opt{
		kgo.SeedBrokers(address),
		// AutoTopicCreation is disabled by default.
	}
	client, err := kgo.NewClient(options...)
	if err != nil {
		return false
	}

	timeoutTimer := time.NewTimer(timeout)
	resultChannel := make(chan bool, 1)

	go func() {
		record := kgo.StringRecord("ANYONE THERE?")
		record.Topic = "non-existent" + uuid.Must(uuid.NewV4()).String()

		// Retry till the select runs into the timeout.
	RETRY:
		result := client.ProduceSync(context.Background(), record)
		err := result.FirstErr()
		if err != nil && !errors.Is(err, kerr.UnknownTopicOrPartition) {
			goto RETRY
		}
		resultChannel <- true
	}()

	select {
	case <-timeoutTimer.C:
		return false
	case resultValue := <-resultChannel:
		client.Close()
		timeoutTimer.Stop()
		return resultValue
	}
}

func init() {
	kafka.host = "localhost"
	kafka.port = 9092
	kafka.start = func() error {
		// Prevent trying to start multiple times, as we'll run into an error.
		if kafka.available() {
			fmt.Printf("Not starting Kafka on port %d, as it is already available\n", kafka.port)

			// Since no purge is available yet, we assume that we haven't
			// started this instance and therefore can't purge it.
			if kafka._purge == nil {
				kafka._purge = func() error {
					return errUnsupported
				}
			}
			return nil
		}

		fmt.Printf("Starting Kafka on port %d ...\n", kafka.port)

		// Connects to the local docker daemon.
		pool, err := dockertest.NewPool("")
		if err != nil {
			fmt.Printf("Could not connect to docker: %s\n", err)
			return err
		}

		// Cleanup container after 120 seconds in case our cleanup fails.
		// I went for 120 seconds in the assumption that the tests will
		// never be this slow ;)
		var expireTime uint = 120

		portString := fmt.Sprintf("%d/tcp", kafka.port)
		kafkaResource, err := pool.RunWithOptions(
			&dockertest.RunOptions{
				Repository: "blacktop/kafka",
				Tag:        "latest",
				Env: []string{
					"KAFKA_ADVERTISED_HOST_NAME=localhost",
				},
				PortBindings: map[docker.Port][]docker.PortBinding{
					"9092/tcp": {{HostIP: "localhost", HostPort: portString}},
				},
				ExposedPorts: []string{portString},
			})
		if err != nil {
			fmt.Printf("Could not start kafka resource: %s\n", err)
			return err
		}
		kafkaResource.Expire(expireTime)

		kafka.wait()
		kafka._purge = func() error {
			// You can't defer this because os.Exit doesn't care for defer
			if err := pool.Purge(kafkaResource); err != nil {
				return err
			}
			return nil
		}
		return nil
	}
}

Are you expecting to see UNKNOWN_TOPIC_ID? This is what I get on v1.11.6 for the code above (also please include the logs you're seeing before/after for future issues so I don't have to run this myself :sweat_smile:)

Thanks.
Sorry, I thought you wanted to run it yourself, so you see what I mean.
Next time :D
I guess my usecase is rather special though. As we have an instance that is purged and created again. In most usecases you'd probably want to retain your topics, in which case that error probably makes sense.
Is there some way we could add helper code to make sure people can easily allow franz-go to retry where sensible, but opt-into handling it themselves?

The fix is is in v1.12.1, released now.a

Also to answer your question:

Is there some way we could add helper code to make sure people can easily allow franz-go to retry where sensible, but opt-into handling it themselves?

I think it makes sense to fail on a topic recreation and bubble the error up. That's part of the reason topic IDs were introduced, to detect and guard against recreations. They just made the error retryable for some reason. Instead, I've created #358 to add an option to allow consuming recreated topics.


Question: What are the conditions necessary to get the details of xhr perf?

I'm trying out the new feature where application insights will add the window.performance timings for xhr and fetch by passing this config,
enableAjaxPerfTracking: true
It works, in app insights, I can see customDimensions.ajaxPerf with some properties
for example:
{"response":"00:00:00.002","sentRequest":"00:00:00.654","duration":666.7100000195205,"perfTotal":666.7100000195205,"serverTiming":{},"transferSize":3344,"encodedBodySize":2980,"decodedBodySize":24469}
However I was wondering where the timings for the redirect, dns lookup, connect, request, response are, as detailed here: https://github.com/microsoft/ApplicationInsights-JS/blob/d3a08d08f5d9988d79e30c0bb3e9277cb048199f/extensions/applicationinsights-dependencies-js/src/ajaxRecord.ts#L58
I'm wondering what are the conditions necessary to get this data?
The request is same origin so there shouldn't be any cross origin limitations here
I noticed there's configs for maxAjaxPerfLookupAttempts and ajaxPerfLookupDelay, do these play a role and if so how do I config them properly?

Not all values will be present, if the value is undefined or zero then they are not populated
redirect - will only be set if the server responds to a XHR request with a redirect and you request is configured to follow redirects then the browser will populate these
dns lookup - Will only be set if the system needs to resolve the domain to an IP address, this depends on the domain you are connecting to, the DNS TTL and when the system last resolved the domain
The values are set as individual properties when set, and should be available in the logs.
It also depends on whether the users browser supports this API and the number of requests that have already been traced in the performance API (browsers have a max limit -- which really only affects long running SPA's or it the users stays on the page for a long period of time)
The defaults for maxAjaxPerfLookupAttempts and ajaxPerfLookupDelay should be fine, these are exposed via config to allow tweaking if your users' browsers are running on older hardware or older versions. As the performance API values are generally not available immediately after getting the response via the fetch/xhr request (so it needs to wait and retry the lookup).

Closing based on no additional follow up, feel free to reopen with additional questions -- if required


Confluent kafka binding

Signed-off-by: myan<EMAIL_ADDRESS>Adding the Kafka binding with https://github.com/confluentinc/confluent-kafka-go. Compared to the sarama binding, this implementation will support the following features.

The binding provides the ability to submit offset asynchronously. ref: https://github.com/cloudevents/sdk-go/issues/846

Be able to subscribe to batch topics with a regular pattern. ref: https://github.com/confluentinc/confluent-kafka-go/issues/96

In this implementation, with configuration WithPollGoroutines(1) to ensure local (partition) ordering of messages.
Since Kafka already natively utilizes consumer groups to enhance consumption efficiency, there is no need to use multiple goroutines to boost consumption speed.

Resolve: https://github.com/cloudevents/sdk-go/issues/918

/hold

@embano1 Thanks for your review!

Thy @yanmxa and sorry for my slow responses. I'm under the water at the moment at work and can't give you a concrete date when I'll be able to review. Perhaps @duglin and @lionelvillard can take another look?

@yanmxa can you update the documentation: https://github.com/cloudevents/sdk-go/blob/main/docs/protocol_implementations.md?
Also I wonder if it makes sense to indicate (maybe in the documentation) this is a new implementation and it hasn't been widely tested in the wild. WDYT?

@yanmxa can you update the documentation: https://github.com/cloudevents/sdk-go/blob/main/docs/protocol_implementations.md?
Also I wonder if it makes sense to indicate (maybe in the documentation) this is a new implementation and it hasn't been widely tested in the wild. WDYT?

Thanks @lionelvillard! I update the protocol binding for this implementation. PTAL~

Thanks @duglin !

@embano1 @lionelvillard PTAL~

I haven't checked the whole PR because for some parts especially structured/binary handling, I'd like to see more tests for non-happy path scenarios and mis-use if possible. Could you please also add Confluent to the Github integration tests so we run this against Confluent images?

Thank @embano1!
I added some tests for the misuse cases when the consumers try to initialize the client. If others come up with scenarios beyond this, we can continually improve it in the future.
Also, I updated the GitHub integration test workflow to add the kafka_confluent service(running on port 9192, the sarama running on 9092) with the confluent image.  So the current confluent kafka protocol uses it for the tests.

@embano1
Thanks for your patient reviews all along!
Cause several multi-cloud management projects in our team depend on this. If you could provide feedback and suggestions on this PR as soon as possible, it would be of great help to us!

Some minor things left, sorry...had some time to dig a bit deeper. Should be easy to address. Then please squash your commits.

Never mind!
Done.

Looked closer at the Close/Send/OpenInbound implementations and there's still races/chances for panics. Left comments on how to simplify

Thanks a lot!
Done!

@yanmxa
I spend some time looking at the OpenInbound/Send/Receive/Close functions and suggesting this patch to remove some unneeded code and tidy things up:
diff --git a/protocol/kafka_confluent/v2/protocol.go b/protocol/kafka_confluent/v2/protocol.go
index 249855c..7c83087 100644
--- a/protocol/kafka_confluent/v2/protocol.go
+++ b/protocol/kafka_confluent/v2/protocol.go
@@ -99,10 +99,8 @@ func (p *Protocol) Send(ctx context.Context, in binding.Message, transformers ..

 	p.closerMux.Lock()
 	defer p.closerMux.Unlock()
+
 	if p.producer.IsClosed() {
-		if p.producerDeliveryChan != nil && !isClosed(p.producerDeliveryChan) {
-			close(p.producerDeliveryChan)
-		}
 		return errors.New("producer is closed")
 	}

@@ -177,9 +175,7 @@ func (p *Protocol) OpenInbound(ctx context.Context) error {
 				logger.Errorf("failed to close the consumer: %v", err)
 			}
 		}
-		if p.consumerIncoming != nil && !isClosed(p.producerDeliveryChan) {
-			close(p.consumerIncoming)
-		}
+		close(p.consumerIncoming)
 	}()

 	for {
@@ -228,21 +224,14 @@ func (p *Protocol) Close(ctx context.Context) error {
 	p.closerMux.Lock()
 	defer p.closerMux.Unlock()

-	if p.consumerCancel != nil {
-		p.consumerCancel()
-	}
-
 	if p.producer != nil && !p.producer.IsClosed() {
 		p.producer.Close()
+		close(p.producerDeliveryChan)
 	}
-	return nil
-}

-func isClosed(ch <-chan kafka.Event) bool {
-	select {
-	case <-ch:
-		return true
-	default:
+	if p.consumerCancel != nil {
+		p.consumerCancel()
 	}
-	return false
+
+	return nil
 }

Let me know if you have questions.

Let me know if you have questions.

Thanks!
Your advice makes the code clearer and no other questions.

I have a slight concern, perhaps unnecessary and we can just ignore it. That is what if the producer isn't closed by the Closer, that will cause producerDeliveryChan not to be closed?

Please add a comment to the Close() method that protocol users must call Close() to properly clean up resources after use.

I have a slight concern, perhaps unnecessary and we can just ignore it. That is what if the producer isn't closed by the Closer, that will cause producerDeliveryChan not to be closed?

Please add a comment to the Close(ctx) method that protocol users must call Close(ctx) to properly clean up resources after use. Also, add defer p.Close(ctx) to all your examples

Done!

Please add a doc string to the Close() method as well, advising users to call Close() after use. Please directly squash your commits so we can merge. Also, any related documentation/README updates needed to further highlight this new protocol implementation?

Also, why did you not use WithPollGoroutines in all receiver examples? Should be clear why this is advised e.g., also adding a comment to the example explaining that this won't have perf impact and is only required if the user cares about in-order processing when using the SDK.

Also, why did you not use WithPollGoroutines in all receiver examples? Should be clear why this is advised e.g., also adding a comment to the example explaining that this won't have perf impact and is only required if the user cares about in-order processing when using the SDK.

Thanks for your prompt feedback!

Add some comments for the Close method and WithPollGoroutines in all receiver examples.
Update the related document in this repository.
Squash the commits

Could you please help me to check if the wording in the above document is appropriate?

Can you please check your integration tests? They're not looking positive, but passing: https://github.com/cloudevents/sdk-go/actions/runs/8420863202/job/23056453953?pr=988#step:5:284 (example)

This unit test is also not looking ok: https://github.com/cloudevents/sdk-go/actions/runs/8420863203/job/23056453818#step:4:3883

This unit test is also not looking ok: https://github.com/cloudevents/sdk-go/actions/runs/8420863203/job/23056453818#step:4:3883

The error log disappears in the unit test now.

Can you please check your integration tests? They're not looking positive, but passing: https://github.com/cloudevents/sdk-go/actions/runs/8420863202/job/23056453953?pr=988#step:5:284 (example)

Done!
The integration test error log is from here.

@duglin can you please take a final look just overall whether we missed a README or general requirements for a new protocol binding?

@lionelvillard too :-)

LGTM
I'll let @embano1 hit the button.


Fixes micro/go-platform#36

If the span was got from the context, then the metadata was not got from the context, and all the metadata would be erased by the creation of a new context from an empty metadata ( https://github.com/micro/go-platform/blob/1e631bb6815c2dbabe589649b8d89b5a460c41f5/trace/wrapper.go#L82 )

Thanks


Question: babel-relay-plugin error while doing npm install

Hello, I'm trying to get started with relay.
As usual, I cloned the repo and then run npm install. After a while, the download finished but with a warning:
npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
My first guess is the download was corrupted because a bad internet connection. I tried to run npm install again, but the same warning occured.
Since it is only a warning, do I need to be concerned with it? If it is actually a problem, how can I fix it?
Btw, I'm not sure if here is the right place to ask this kind of question. If this kind of post is not appropriate here, where is the better place to ask?

happened here too.

Sorry for the breakage, I pushed a new version of babel-relay-plugin which broke the dependencies here. Merge request to fix this is up!

Thanks, that fixed it!


Standard style property "transform" is not available

It seems like the vendor prefixed version webkit-transform is available on the HTMLElement.style node, but not the W3C version.

Actually it seems like getting transform from JSDOM objects doesn't work at all. I tried window.getComputedStyle(HTMLElement) and the .style way and neither retrieves the value.

Do you set both webkit-transform and transform in your style, or just one of them? We don't actually process styles much - they don't properly inherit and they do not have any dependency on each other.
If you could get us a small test case, that'd be great.

I look for the following:
'transform',
        'WebkitTransform',
        'MozTransform',
        'OTransform',
        'msTransform',

To my knowledge, style['webkit-transform'] doesn't actually do anything.

To replicate, create an element and do the following with it:
const domElement = document.createElement('div');

domElement.style.transform = 'translate3d(0px, 0px, 0px)';

assert(domElement.style.transform === 'translate3d(0px, 0px, 0px)'); // undefined

I can only get it to work if I use this specific pattern:
const domElement = document.createElement('div');

domElement.style['webkit-transform'] = 'translate3d(0px, 0px, 0px)';

assert(domElement.style.WebkitTransform === 'translate3d(0px, 0px, 0px)');

I'm going to replicate this PR against CSSOM, since I think that's where the issue actually is...

Issue in a different module


feat: add some more patterns as used in Kronos-Integration/kronos-clus…

…ter-node

Thanks! Released in v2.0.


contact us notification

#631
completed
Also Added on error message if there is spam .

great work @DevGajjar28 !


About Container Image on Docker Hub

Hi,
As mentioned on Slack and given the problems described in #709, I was wondering if we should not have working container images on Docker Hub, along with continuous integration for the Dockerfile themselves.
We would also need to provide some wrappers for them to be fully useful but it should not be too hard.
Cheers,
Thomas

Here is some interesting movement related to this:
https://github.com/AcademySoftwareFoundation/aswf-docker
In particular the ci-ocio image may be of interest (which we are using for Linux CI now. and will have a tag per VFX reference platform year). This image does not contain OCIO, but does contain a complete environment for building OCIO, including OIIO, etc.
This is the staging area for new image builds:
https://hub.docker.com/r/aswfstaging/ci-ocio/tags
They will eventually land here:
https://hub.docker.com/u/aswf
We've also recently built out our own ci scripts directory for building any other images we may need down the road: https://github.com/imageworks/OpenColorIO/tree/master/share/ci . There's an example Dockerfile in there that I was initially using for testing.
Hopefully these can lay the foundation for further work.


Is there any event binded to ok button click ?

Nope

There is if you switch to the maintained version of this library: ngx-color-picker


Added missing TypedArray functions (Copy of #1228)

TypedArray.of()
TypedArray.from()
TypedArray.prototype.copyWithin()
Contributed by @JaredWilliams

lgtm and I'm reasonably certain this won't break anything internally.


tests for feature/auth-skeleton

Addressed in authentication skeleton which uses flask_jwt_extended for tokens. However, tests could be better...


rw: wrong error message

rw [lemma_wth_typo] with a non-existing lemma yields a wrong error message.

I have no idea about this. If I rename our macro to anything but rewrite or rw, it shows "unknown identifier 'mul_comm'", but as soon as I name it rw that dissapears :(
Zulip


project as CMake package

only conda build is tested.

I suppose this PR will have to update consistently.

This will be superseded by work at c_lib branch.


chore(main): release 1.6.0

:robot: I have created a release beep boop
1.6.0 (2023-05-13)
Features

copy draft release from src (#17) (eb09597)
move to poetry (#15) (1452522)
support cloning assets to created releases (#18) (11c658e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/andrewthetechie/gha-clone-releases/releases/tag/v1.6.0 :sunflower:


Attention Decoder

Hi,
@ebrevdo Eugene speaks here https://www.youtube.com/watch?v=RIR_-Xlbp7s (29:50) about a class AttentionDecoder and says it's under development (as of Tensorflow Summit date), however I can't find this class anywhere in the master/r1.1/r1.0 tensorflow code. Do you know when it will be added?

We need to update that video somehow.  It turns out it's cleaner to
implement attention as an RNNCell wrapper rather than decoder.  This way it
can be combined with other decoders easily.  See tensorflow master branch,
tf.contrib.seq2seq.AttentionWrapper.  It's pretty feature complete, and can
be used with other RNNCells, wrappers, and the BasicDecoder.
On Tue, Mar 28, 2017 at 6:38 AM, mhnatiuk<EMAIL_ADDRESS>wrote:

Hi,
@ebrevdo https://github.com/ebrevdo Eugene speaks here
https://www.youtube.com/watch?v=RIR_-Xlbp7s (29:50) about a class
AttentionDecoder and says it's under development (as of Tensorflow Summit
date), however I can't find this class anywhere in the master/r1.1/r1.0
tensorflow code. Do you know when it will be added?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/8775, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim5clNyjhcV_TYgzOpSy_HbQhRMTeks5rqQ1hgaJpZM4MrogY
.

Ok I tired with LSTMBasicCell and got "state has no attribute attention" exception.. looks like a bug

I will review and report back

I'm running into that same issue. How did you solve it?

I switched back to using TrainingHelper instead of ScheduledEmbeddingHelper, and feeded embedded inputs by looking up embeddings using tf.nn.embedding_lookup. It works, now I run into other problem, the shape of decoder_outputs.rnn_output is (AFAIK) dynamic and it's not possible to feed it into tf.contrib.seq2seq.sequence_loss, since it expects TARGETS and LOGITS to have compatible shapes


Do not send kex extension in TLS 1.3

Problem:
In TLS 1.3, we added new cipher suites that has NULL key_exchange_alg. This causes s2n to segfault in s2n_kex_server_extension_size() and s2n_kex_write_server_extension()
Proposed Solution:
Either add a key_exchange_alg that does no-op or add relevant checks in place to not send the kex server extension.

I can take this one :) How do I assign this to me? I can’t update the issue status .

Feel free to take on this task, I can assign this to you

@xy008areshsu Thanks for fixing!


dashDB steps missing build pack

On step 5 of the following link we should add the buildpack
https://console.ng.bluemix.net/docs/services/dashDB/index-gentopic1.html#managing_instance
For example, it should be the following:
cf push  -b https://github.com/zendtech/zend-server-php-buildpack-bluemix
or the db2phpbuildpack
cf push  -b https://github.com/ibmdb/db2heroku-buildpack-php
Source:
https://hub.jazz.net/project/ibmdatabase/dashDB/overview#https://hub.jazz.net/git/ibmdatabase%252FdashDB/list/master/samples/dashDBPHP

Hi Hobert,
Thank you for your feedback comment. I completed the changes to step 5 that you approved today. The changes will be viewable sometime today after a rebuild is done.
Cheers.
Rimas


1.18.2 version of mod Mislabeled on Curseforge

This file is mislabeled as a Forge mod, when it is for Fabric mod.

Oh... such has been changed. That's what I get for uploading a mod for 3 versions of Minecraft across 2 differing loads at the same time. Thanks for telling me

Whoah that was fast lol. Appreciated. It was making me have to manually reinstall the mod as it wanted to "update" to the fabric version every time I wanted to update my upcoming Forge modpack's mods, so I reported it lol. But even then I woulda kept updating it manually, lifesaver of a mod you have here.


[PLINT-304] Report metrics for the Teleport SSH Service

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

Current dependencies on/for this PR:

noueman/add-teleport-integration:

Branch noueman/teleport-integration-refactor-and-cleanup - Create Pull Request

PR #17111 👈

This comment was autogenerated by Freephite.

Current dependencies on/for this PR:

noueman/add-teleport-integration:

Branch noueman/teleport-integration-refactor-and-cleanup - Create Pull Request

PR #17111 👈

PR #17113

PR #17114

PR #17116

PR #17117

This comment was autogenerated by Freephite.


High Severity Bug found in "data/a1853428.txt" with an insertion of "XXXXXXX"

Hello davmlaw,
Thank you for you contributions to this project. I believe I have found a high severity bug in the file "data/a1853428.txt" with an insertion of "XXXXXXX".
Commit: d15e4a4
Expected Line 1: campaign INTERNATIONAL each would. than individual loss contain. simple never our manage.
Actual Line 1: XXXXXXX campaign XXXXXXX INTERNATIONAL XXXXXXX each would. than individual loss contain. simple never our manage.
I will submit a pull request to rectify this issue.


Automatic changelog generation for weppy

Maybe this could reduce your (at the moment low but higher in future) management workload: https://github.com/skywinder/github-changelog-generator
It will generate changelogs automatically with help of your issue and commit list.

:+1: I use github-changelog-generator wherever I can, including the weppy-mvc generator.
The only issue is that it requires strict use of issues and pull requests to actually log changes. It seems if branches are merged without being tagged with issues or without a PR, it neglects them entirely.


std: array: refactor std.array unittest blocks and attribute annotation

Signed-off-by: Luís Ferreira<EMAIL_ADDRESS>
Read the patches description for context.

LGTM, just two nits on the second commit:

"seperate" => "separate"
Moving one of the block makes the diff non-obvious. I thought at first the code was changed, but ignoring whitespace changes made it cleared;

Fixed. Yes, moving these blocks make diffs very hard to read, unfortunately.

Also, std: array => std.array ?

Didn't know that, thanks for the clarification. I'll start committing that way. This could be added to the contribution guidelines, or maybe it is there somewhere and I missed it :upside_down_face:


Mention screen selector in Make Floating button tooltip

Fixes: https://github.com/godotengine/godot/issues/96519
Before:

After:

Thanks!


HDDS-2510. Use isEmpty() to check whether the collection is empty or not in Ozone Manager module

What changes were proposed in this pull request?
Replace an O(n) .size() check with the O(1) isEmpty() check in Ozone Manager module.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2510
How was this patch tested?
Ran relevant unit tests.

Thank You @avijayanhwx for the contribution and @adoroszlai for the review.


Language-agnostic test case files

These would make it easier to port base37268 to other programming languages.

Resolved with this commit.


feat(userhead): 增加移动端头像组件

PR
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our Commit Message Guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@all-contributors please add @MNZhu for code


fix: update error message

🤓

I think we should just call it "sever_configurations.md" and say see :help lspindex


Events Working on /admin urls not base urls

I installed a plugin in the user/plugins directory. Plugin contains yourls_add_action( 'pre_redirect', 'someFunction' ) which checks for a certain function before redirecting the link to the main URL. But I noticed my event is getting called on the abc.com/admin/<shorturlId> instead of abc.com\<shorturlId>. I checked all my plugins events are getting listened to by the /admin subroutes instead of main short urls. Can you help me with this? Quite a newbie to the Yourls.
The plugin I installed is https://github.com/MatthewC/yourls-password-protection/blob/master/plugin.php

After long R&D , Instead of pre_redirect I have used redirect_shorturl and it's working fine now.
But I would still like to know the reason behind it. As per my understanding pre_redirect should also worked. Am I Missing a point here???

It's just how YOURLS works out of the box : when a URL that doesn't exist is requested, eg abc.com/admin/<shorturlId>, yourls-loader.php checks if it's a short URL and if not, redirects with yourls_redirect() (hence the pre_redirect hook) to the root, see https://github.com/YOURLS/YOURLS/blob/master/yourls-loader.php#L68.
This function is used for any redirect, either internal to the YOURLS setup, or external to a long URL.


Purchase store items

As a player, I should be able to purchase servers and items available in the store from the store modal.

[ ] All servers available at the level are available to purchase in the store
[ ] All items in the store are available to purchase in the store
[ ] Users can only buy as much as they have money to be able to buy

Dependencies:

https://github.com/knot-games/cloud-tycoon/issues/41

Epic: https://github.com/knot-games/cloud-tycoon/issues/32

Should StoreItems only be purchaseable once?


Modflow 6 Simulation should get method to read output

In GitLab by @JoerivanEngelen on Nov 6, 2023, 18:49
In order to read output, a user has to call imod.mf6.open_hds and imod.mf6.open_cbc, which requires providing paths to files (which can be constructed beforehand). This makes for a bit of a tedious user experience, as it requires a user to look in their folder how their output files are named and clutters their code slightly:
head_new_recharge = imod.mf6.out.open_hds(
    modeldir / "GWF_1/GWF_1.hds",
    modeldir / "GWF_1/dis.dis.grb",
)

Since https://gitlab.com/deltares/imod/imod-python/-/commit/02331ce7df16753fc458a4436366d29a05661687, we store the write directory in the simulation object. Convenient would be to add a method which constructs paths to the .hds or .cbc files, and the .grb files. Consequently it should call imod.mf6.open_hds or imod.mf6.open_cbc.
The write_directory argument of the WriteContext might require some thinking, I only see it used once, namely in the mf6_lake_package_fixture.
Think of error checking!

In GitLab by @JoerivanEngelen on Nov 6, 2023, 18:50
marked this issue as related to #535


openmpt123: 0.5.5 -> 0.5.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/openmpt123/versions.
meta.description for openmpt123 is: "A cross-platform command-line based module file player"
meta.homepage for openmpt123 is: "https://lib.openmpt.org/libopenmpt/"
meta.changelog for openmpt123 is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.5.6 with grep in /nix/store/25r6g3prn0ipz35v88s3sspyc7g8gvdk-openmpt123-0.5.6

directory tree listing: https://gist.github.com/b74b73902426857e22753946e27eb915

du listing: https://gist.github.com/2c02a1380fbf11c3a9b30c48f1508f68

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

12 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
audacious
audaciousQt5
gjay
openmpt123

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/25r6g3prn0ipz35v88s3sspyc7g8gvdk-openmpt123-0.5.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/25r6g3prn0ipz35v88s3sspyc7g8gvdk-openmpt123-0.5.6
ls -la /nix/store/25r6g3prn0ipz35v88s3sspyc7g8gvdk-openmpt123-0.5.6/bin

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

3 packages built:

audacious
gjay
openmpt123

Maintainer pings
cc @gnidorah for testing.

Result of nixpkgs-review pr 116522 at e00263a9 run on aarch64-linux 1

3 packages built successfully:

audacious (audaciousQt5)
gjay
openmpt123


populate hostname/port if Vector is being served by pmwebd

It may not be necessary to do this as a first class vector feature, given that the pcp-webjs bundle's index.html that links to vector/index.html does this via some javascript magic.

Fair enough. I'll close the issue for now, but I can reopen if needed. Tks @fche


Include generated command reference

I noticed that kumactl generates a markdown HELP.md, which seems pretty useful. Cobra has built-in support for generating markdown documentation.
It would be pretty nice to generate reference pages for all the commands that ship as part of Kuma and include it in the website as reference material.

I hacked  on this a bit and made a script that ought to be able to generate command reference markdown for a number of kuma versions:
#! /usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail

readonly KUMAVERS=${KUMAVERS:-1.1.6}
readonly PREFIX=${PREFIX:-$(cd $(dirname $0); pwd)}

readonly CURL=${CURL:-curl}
readonly GO=${GO:-go}
readonly TAR=${TAR:-tar}

readonly WORKDIR=$(mktemp -d)

workdir::init() {
    ${GO} mod init kuma-website/cmdref
}

# Fetch kuma. Using `go get` would be preferred but the way Kuma used nested Go
# modules breaks that, so we resort to pulling a tarball
workdir::kuma() {
    ${CURL} --location --silent --fail \
        https://github.com/kumahq/kuma/archive/refs/tags/${KUMAVERS}.tar.gz | \
    ${TAR} -xzf -

    ${GO} mod edit -replace=github.com/kumahq/kuma=./kuma-${KUMAVERS}

    for m in \
        api \
        pkg/plugins/resources/k8s/native \
        pkg/test/xds/client \
        pkg/transparentproxy/istio \
        tools/releases/changelog
    do
        ${GO} mod edit -replace=github.com/kumahq/kuma/${m}=./kuma-${KUMAVERS}/${m}
    done

    ${GO} mod edit -replace=github.com/prometheus/prometheus=./kuma-${KUMAVERS}/vendored/github.com/prometheus/prometheus
    ${GO} mod edit<EMAIL_ADDRESS>
    # NOTE: Go module tags must be of the form "vX.Y.X", but Kuma tags omit the
    # leading "v", making them invalid Go module versions.
    ${GO} mod edit -require=github.com/kumahq/kuma@v${KUMAVERS}
}

workdir::mktool() {
    cat > main.go <<EOF
package main

import (
	"log"
	"os"
	"path"

	"github.com/spf13/cobra"
	"github.com/spf13/cobra/doc"

	kuma_cp "github.com/kumahq/kuma/app/kuma-cp/cmd"
	kumactl "github.com/kumahq/kuma/app/kumactl/cmd"
	kuma_dp "github.com/kumahq/kuma/app/kuma-dp/cmd"
	kuma_prometheus_sd "github.com/kumahq/kuma/app/kuma-prometheus-sd/cmd"
)

func must(err error) {
	if err != nil {
		log.Fatal(err)
	}
}

func gen(path string, cmd *cobra.Command) {
	must(os.MkdirAll(path, 0755))
	must(doc.GenMarkdownTree(cmd, path))
}

func main() {
	prefix := "${PREFIX}"

	gen(path.Join(prefix, "kuma-cp"), kuma_cp.DefaultRootCmd())
	gen(path.Join(prefix, "kumactl"), kumactl.DefaultRootCmd())
	gen(path.Join(prefix, "kuma-dp"), kuma_dp.DefaultRootCmd())
	gen(path.Join(prefix, "kuma-prometheus-sd"), kuma_prometheus_sd.DefaultRootCmd())
}
EOF
}

(
    cd "$WORKDIR"

    workdir::init
    workdir::kuma
    workdir::mktool

    ${GO} get github.com/spf13/cobra/doc
    ${GO} mod download

    ${GO} run ./main.go
)

Use it with an absolute prefix path for where you want the markdown to go:
jpeach@greenling:~/upstream/konghq/kuma-website$ PREFIX=$(pwd)/cmdref KUMAVERS=1.15 ./bin/generate-cmd-ref.sh
go: creating new go.mod: module kuma-website/cmdref
go get: upgraded github.com/spf13/cobra v1.0.0 => v1.1.3
jpeach@greenling:~/upstream/konghq/kuma-website$ ls cmdref/
kuma-cp/  kumactl/  kuma-dp/  kuma-prometheus-sd/

Yes, let's do it. As with the generated policy refdoc, I'd like to integrate this after we migrate to Jekyll, because we'll have a different directory structure and build process -- and we should have migration working by end of June 🤞 . Let's talk further about optimal ways to serve. THANK YOU! ❤

Sounds great, LMK.

I tried this with the tooling we landed in Kuma, but the site generator went into a re-generation loop that never ended :shrug:
jpeach@greenling:~/upstream/konghq/kuma-website/docs/docs/1.2.0$ (export DESTDIR=$(pwd)/command-reference ; cd ~/upstream/konghq/kuma && make)

:-( Bart and I have been talking about a slightly different approach, where the policy refdocs are generated in kumahq/kuma and then copied over to kuma-website (with a GH Action would make the most sense, although we haven't discussed the details yet). Seems like this might be what's needed here too?

where the policy refdocs are generated in kumahq/kuma and then copied over to kuma-website

I can easily make that change in kuma


Bumps kops jobs limits

Issue #, if available:
Description of changes:
The postsubmit job was getting killed due to the low resource limits. The presubmit was taking 30 mins...
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Feat/yuanrui/enhanced images

Consolidate the first version of the enhanced image module.
What it can accomplish:

Given a vtk polydata and a certain variable in the polydata, it can generate an enhanced image.
Given a DPF model and DPF field object, it can generate an enhanced image.
The enhanced image can be a TIFF file on disk, or a PIL Image object in memory.
The rendering and value pass processes are broken down by phase, and the essential RGB buffer, pick data buffer and variable data buffer are also generated independently.

Known problems:

Only support scalar data for 1 model and 1 field.
The JSON metadata part_name, colorby_var and pal_id entries can be further enhanced.

Potential next-step development:

Make it a class as the incoming requests increase. Currently, it is only a group of functions. But write it in a class can be long-term preferrable.
Grab as much information as possible from DPF inputs to improve usability. For instance, try and test if part_name can be retrieved from DPF model.
Refine the part-var linkage so that enhanced image can support a list of pairs.

@zhang-yuanrui I don't want to add dpf and vtk as requirements for pydynamicreporting. Please see how report_download_pdf.py handles a similar situation with PyQt5. If the module exists, then methods are defined. If it doesn't exist, then the module does nothing. I'd like to see something similar here.
I'd also like to see some tests added in the tests/ directory for these methods. You should add in the pyproject.toml the requirements for the extra modules only for tests (and maybe development), and create a few tests for these methods. Let me know if you need help here.

I think my biggest comment here is the lack of example(s) and test cases.   One can work around the dependency issues for tests that @margalva calls out using the yaml test deps target.   My other big concern is the impact on sphinx documentation.  There are a number of "internal" functions exposed here that one would like to avoid getting into the docs.   Hiding them as '_' methods in a class would help.   Consider providing a simple class with a pure VTK interface and the appropriate methods hidden.   The DPF methods can move over into DPF and leverage the VTK interface from there, streamlining the dependencies.

I think my biggest comment here is the lack of example(s) and test cases. One can work around the dependency issues for tests that @margalva calls out using the yaml test deps target. My other big concern is the impact on sphinx documentation. There are a number of "internal" functions exposed here that one would like to avoid getting into the docs. Hiding them as '_' methods in a class would help. Consider providing a simple class with a pure VTK interface and the appropriate methods hidden. The DPF methods can move over into DPF and leverage the VTK interface from there, streamlining the dependencies.

@randallfrank What is the yaml test deps target?


Merge variable inputs?

I am achieving A Hierarchical Neural Autoencoder for Paragraphs and Documents.
The number of sentences in a paragraph varys. I wonder there is a way to merge variable inputs

You are not providing enough information for us to help you! What you mean by merge? In Keras context merge means to combine 2 tensors with some op, like + or *. Are you looking for masking/padding?


added smoking status observation to wellness encounter

Re-ran the 1000 patients with the latest changes and confirmed now there are instances of all 3 codes, in particular former smokers. (There are way too many because the quit smoking logic gives people a 1% chance of quitting every week, which equates to around 40% per year, but that's a separate issue)
I'll merge this once the corresponding module-builder PR is merged.


Adds current version to packages.

Fix #17475
Also, looks like v4.0.0-alpha may need to be tagged for npm to know about it.
npm publish . --tag 4.0.0-alpha

SGTM.


Add "snabb config bench"

From the README:
 Usage: snabb config bench [OPTION]... INSTANCE FILE
Benchmark "snabb listen" by repeatedly feeding it commands from FILE.

Available options:
  -h, --help                 Display this message.
  -s, --schema SCHEMA        YANG data interface to request.
  -r, --revision REVISION    Require a specific revision of the YANG module.

Invoke like this:
$ sudo ./snabb config bench lwaftr /tmp/commands2.json
........................................................
Issued 56 commands in 0.59 seconds (95.14 commands/s)

That's with a running "snabb lwaftr bench" with the name "lwaftr".  The commands2.json in this case is a file containing this, 56 times:
{"id":"foo","verb":"get","path":"/softwire-config/external-interface/mtu"}

This PR has some performance tweaks as well, basically memoizing more things.  Perhaps the memoization should have a cache eviction policy though.  WDYT @dpino?

Incidentally to get top performance, we need to increase Hz in leader.lua and also pipeline requests.  Without pipelining and with 20e3 Hz instead of 1e3 Hz I get 5e2 requests/s instead of 1e2 requests/s.  I expect pipelining to put me in the range of 5e3 or 5e4. I will add some related options to "snabb config bench" to enable pipelining.

LGTM once CI passes.

With this change I get 8e3 simple "get-config" results per second, which is sufficient for that use case.

LGTM once tests pass.
src/testlog/program.lwaftr.selftest.sh:
Testing snabb lwaftr bench
program/lwaftr/tests/data//icmp_on_fail.conf: loading compiled configuration from program/lwaftr/tests/data//icmp_on_fail.o
core/main.lua:26: incompatible version: 4096


Intergration spec and n 1

Overview

create integration tests for all of the views used in your project and handle N+1 issues.

Workflow
n+1

Make sure that the N+1 problem is solved when fetching all posts and their comments for a user.
How it looks before fixing the N+1

How it looks after fixing

Integration specs

Use Capybara to write integration tests for each view in your project.

User index page:
user show page:
User post index page:
Post show page:

Thank you for the review @emmanuellekamwa :heart:


[FEATURE] Enable Dependabot and Code scanning on the repo setting

Is your feature request related to a problem? Please describe.
To get the auto security fix recommendation and best practices in the code development
Describe the solution you'd like
Settings --> Code security and analysis
Describe alternatives you've considered

running code scanning on VS Code level. Developer responsibility
Additional context
Add any other context or screenshots about the feature request here.

Hello @chandanrjit, Thank you for the feedback we are currently using Snyk for code scanning and is configured for this repo. I believe that this meets the expectations of your feature request. However if it does not please do not hesitate to reach out again with any questions and/or feedback. Thank you!


add get_interfaces_ip

adding get ip interface output for vrf all

understand lets close this pull request for now, not quite sure how to do the unit test right now. ill do a new one once ive worked it out!

@chrisbnorman :
please see this commit:
https://github.com/napalm-automation-community/napalm-onyx/pull/2/commits/6b1d6d782f87ec1c0b42fc7d1b035072ffa1508f
it contains some tests.


Fix text overflowing

Allow wrap text in every fields
Fix status length to a min value
Fix field label length to a min value
Limit tag character length to 30
Resize window min width and height to 800 (to prevent user from shrinking the window to very small then blame they cant see the word clearly on us...)
Add line spacing and underline between fields to easier to distinguish between them after text wrapping

Fixed UI:

Resolves:

#162
#156
#152
#146
#144
#182
#183
#184
#175

Codecov Report

Merging #186 (da773da) into master (e9d3517) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #186      +/-   ##
============================================
- Coverage     73.91%   73.90%   -0.02%
- Complexity      720      721       +1
============================================
  Files           106      106
  Lines          2074     2073       -1
  Branches        245      245
============================================
- Hits           1533     1532       -1
+ Misses          469      468       -1
- Partials         72       73       +1

Impacted Files
Coverage Δ

src/main/java/seedu/application/model/tag/Tag.java
70.00% <0.00%> (-10.00%)
:arrow_down:

.../main/java/seedu/application/ui/InterviewCard.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Tools: GCC ARM Exporter - Nordic targets - softdevice hex file path is set statically

The GCC ARM makefile template for NRF51 targets have path statically set which is functional only with mbed library.
A code snippet from the tempalt makefile for NRF51822 target:

SOFTDEVICE = mbed/TARGET_NRF51822/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_7_0_0/s110_nrf51822_7.0.0_softdevice.hex

This should be dynamically set or at least to distinguish between mbed lib/mbed sources.

The Makefile that is being exported now refers to an old+missing softdevice hex, along with still having the wrong path.
As exported:
SOFTDEVICE = mbed/TARGET_NRF51_DK/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s110_nrf51822_7_1_0/s110_nrf51822_7.1.0_softdevice.hex
Should be:
SOFTDEVICE = ./mbed-src/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1_0_0/s130_nrf51_1.0.0_softdevice.hex
Other paths in the Makefile are correct however.

that file path doesn't even exist in newer revisions. It's now the 8.x SDK

Is this not going to change until yotta is used?

that file path doesn't even exist in newer revisions. It's now the 8.x SDK

Where?

Is this not going to change until yotta is used?

having problems with ithe exported gcc makefile, with the issue reported here? Feel free to send a fix

ARM Internal Ref: IOTMORF-317

Closing all older exporter related issues. Please reopen if still valid. https://developer.mbed.org/blog/entry/Fixed-exporters-in-the-mbed-Online-Compi/


xds: envoy-api external dependency.

This patch adds an envoy_cc_api target to consume the v2 xDS API protos, and a dummy target that will
be the basis of some early EDS prototyping work.

@junr03 for review. @lizan for Bazel stuff and Istio compatibility. @dnoe for Google import visibility.


IPFS resources fail to load via local HTTP gateway

https://yt.aergia.eu/#i=/ipfs/QmYhKszJwWySQofGQaj8epH688bqdj1Kg9rcrGFWt7nhDX
https://github.com/lidel/ipfs-firefox-addon

It should load from localhost, but returns error.

Ok, this needs to be fixed upstream: https://github.com/lidel/ipfs-firefox-addon/issues/75 by defaulting to fs: protocol with Ci.nsIProtocolHandler.URI_SAFE_TO_LOAD_IN_SECURE_CONTEXT flag.

Bug 903966 - Don't block mixed content from localhost is marked as FIXED in Firefox 55


Add function to stop suggestions

If you choose to initiate the suggestion for the commit description there is no way to stop it.
Lets say you need to refactor the suggestion or override it total, it keeps filing with more suggestions.
There should be a way to stop suggestions after first set is completed.

I'm not sure if I understand your meaning correctly.

If you are generating information by clicking the icon in the commit dialog or commit window, you can interrupt the generation process by clicking the icon again during the process.
If you are generating information in the toolWindow of AICommit, you can stop the generation by clicking "Stop generate".

Or are you suggesting to keep the already generated part? Similar to appending to the current commit information? 🤔

I am using the plugin through phpStorm with the beta UI, there is only a button next to Amend button that triggers Ai Commit.
If you press the button to start the suggestion pressing it again I would expect to terminate immediately the suggestion process.
If you start getting suggestions and try to change the commit message box it keeps change in it to the original suggestion.
Also I think it does not take to consideration the "staged files" (files that are checked and are part of the commit) and tries to suggest commit message for all files that have changes and are available to be staged.

Thank you for your reply. I think I understand your meaning now. It seems that the pause function is not working properly? May I know what version of the plugin you are using?
Regarding the "staged files", it seems like a bug that has already been resolved. 🤯

I am using 1.2.5 version (in trial) over PhpStorm 2023.1
Yes I suppose pause function is not working.

Thanks, I will look into it.

Should be fixed in 2.0.0, pls upgrade the plugin ;)

I've upgraded to 2.0.0 but I see that it still does not respect what files I am about to commit and keeps looking to incorporate files not selected to the comment reason.

commit message for meta.php is correct but it is not part of current the commit.

This is a bit strange, I cannot reproduce this error. The plugin detects which files need to be committed through the platform API. It is possible that the API results provided by your IDE version are incorrect.
As I do not have the IDE you are using, perhaps you could try using IntelliJ IDEA to see if the plugin works properly? Thank you.

I roughly know the reason, it may be because your file is not tracked in vsc, so the API cannot read the changes of the file. You need to add them all first 😃


bootstrap-select width changes on resize

Hello,
I'm trying out bootstrap-select instead of the regular bootstrap select ( with form-control class) and it's great until i attempt to resize the page. The selectpicker doesn't fit into my panel anymore if i make the window smaller which is a shame. This is my html:
snippet.txt
Any smart way to make the select align inside the column/panel even though the text in the options of the select are too big(crop it instead) upon resizing the window? It needs to be dynamic so you can resize the screen to whatever size you want.
Image to showcase the problem:

What have happened to this questions? I need an answer too


Enable Auto theming using Dark Mode CSS

For those who don't know,DarkMode CSS is new feature available in all latest browsers(Blink,Gecko,Webkit based).It themes the website based on System's theme.If the system does have Dark theme,then the site would have dark theme,and if the system has light theme ,then the site would have light theme.(One can also create custom behavioyr for each type).
Ref:

Introduction by Webkit
Mozilla Docs

I want Gitea to have arc-theme(name of dark theme in gitea) when the system is in dark mode and gitea(name of light theme in gitea) when the system is in light mode.
Atleast enable option named "Auto" under themes to enable automatic themes based on dark mode css

Want to also add to this that this kind of thing would be very helpful for the official docs, which don't support user-specific themes, and could benefit from this parameter.


Weather Visualizer

Add a visualizer that will let the viewers explore the scene's like cloud coverage or fog intensity. Would  let user select different weather types like sunny, foggy, cloudy..

@Mutugiii  and I would like to work on this.


Enhancements and configuration

List of possible improvements (from bare ideas to ongoing work) for the bot. Place for discussion.

[ ] Turn on/off the bot
[x] Specify target language
[ ] Specify source languages
[ ] Sanitize input (see #1)
[ ] Translation on demand?

It's possible to specify target language via TRANSLATE_TO=en setting in .env file.

Not sure if specifying source languages is a good idea. The bot will translate any lang, except the target one. But I could add this option if it's much wanted.

For now I'm just throwing in ideas :blush:
Sorry I missed the TRANSLATE_TO option. I've checked that item now.

no work is going to be done here, closing


Zod continues to throw errors while using async refinements with react hook form when zod resolver mode is set to async

Had an issue in the code that was causing this.

Yes. It was due to an oversight in my own code.


HDDS-2780. Fixed javadoc of OMVolume response classes.

What changes were proposed in this pull request?
Fixed javadoc of OMVolumeCreateResponse and OMVolumeDeleteResponse, now is:
OMVolumeCreateResponse.java

/**
 * Response for CreateVolume request.
 */
public class OMVolumeCreateResponse extends OMClientResponse {

OMVolumeDeleteResponse.java

/**
 * Response for DeleteVolume request.
 */
public class OMVolumeDeleteResponse extends OMClientResponse {

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2780
How was this patch tested?
Ran UTs

Thank You @cku328 for the contribution.

Thanks @bharatviswa504  for the review.


Finish correct implementation of rotor cubature integration scheme

Implementing:

Multiple number of rotor points from N=1 to N=10, equaling 1 to 100 rotor points in total respectively
Implement correct weighing terms for integration scheme
Fix the weighted cubic average method for cubature integration

Check out the new notebook. Everything should work now, as far as I can see.
With Jensen:

And with GCH:

Looks like excellent convergence by N=3 or N=4 for the new method. What left is now implementing compatibility for the CC and TurbOPark solvers, and further validation. Also, while the solutions now converge much better, the model parameters may require re-tuning since the two methods do not converge to the same values.

And here's the same example for GCH with a more realistic wind shear value:

The effect on T2 is still really big for a full wake overlap situation. This may be because the square grid method emphasizes the wind speed in the middle section of the rotor, while the cubature integration scheme looks more on the outer edges of the circle:


rename proxy contract

Codecov Report

Merging #42 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev      #42   +/-   ##
=========================================
  Coverage     56.34%   56.34%
  Complexity      168      168
=========================================
  Files            27       27
  Lines          1750     1750
  Branches        113      113
=========================================
  Hits            986      986
  Misses          686      686
  Partials         78       78

Continue to review full report at Codecov.

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


Automate login to github

Automate login to github

I am reopening it this issue if someone wants to attempt it in some different language


Define the problem

Come up with a good project idea

Issue: There is no good in person d&d application to supplement in person play. In person play can be slow during downtimes when dice need to be counted or initiative needs to be tracked, among other things. Prep time also requires the DM to spend lots of time building maps or printing/preparing monster stats


"Active" class no longer being applied to Topbar link on active page

How can this bug be reproduced?

Step one: Create a new site using Foundationpress
Step two: Create a few pages and add them to a menu in the topbar
Step three: Inspect nav links to see if an "active" class is being applied

What did you expect to happen?
A class of "active" to be added to the nav link corresponding to the current page.
What happened instead?
The class is not there. The CSS styling is still in navigation.scss though.
Please List the Following:

OS & version: Windows 10
Node version (node -v) [Node v4+ is required] : 6.9.2
Foundation version (bower list) : 6.3.0

Include Test Case (if applicable):
Give us a link to a CodePen or JSFiddle that recreates the issue.

CodePen with Foundation 6 and MotionUI
CodePen with Foundation 6, Flexbox grid and MotionUI

Here are the classes on a page link that come up when that page menu item is clicked:
menu-item menu-item-type-post_type menu-item-object-page current-menu-item page_item page-item-<page-id> current_page_item
We have a function in foundation.php, starting at line 80, that is supposed to add the active class, but it seems to not be functioning. Looking into this, but please have some more patience. It's Monday where I am and I've got an hour before duty calls. :cry:

Fixed https://github.com/olefredrik/FoundationPress/pull/1032


Review doc structure for clusters

IMHO, maintaining templates here would be highly complex due to all the specificities of each cloud provider. I believe it is more readable without using templates.
Regarding self-managed, yes we can have a dedicated page.


fix(producer): always lookup topic during startup

If the network is partitioned when a producer is connected to Pulsar, but Pulsar itself doesn't go down, then there's no need to lookup the topic to which the producer will produce (as this is done by pulsar_client) prior to starting the producer the first time.
If, however, the Pulsar broker goes down and is later brought back up, the producer MUST lookup the topic again before sending any messages. Otherwise, Pulsar will reply with an error of the form:
Namespace bundle for topic (persistent://public/default/some-topic)
not served by this instance. Please redo the lookup. Request is
denied: namespace=public/default

Reference: https://pulsar.apache.org/docs/2.10.x/developing-binary-protocol/#topic-lookup
Note
Will re-tag 0.7.0 with this after merged, since only e4.4.11 makes reference to 0.7.0, and it's not yet released.

will need further changes (handle URL changes)

CI is constantly failing on resilience.down.t_pulsar_drop_expired_batch due to the socket never being closed for some reason, but locally it always passes for me....
We talked internally, and will tag 0.7.1 with this (even with CI failing) to unblock QA and later will try to fix the tests.

Note: will require to tag 0.7.1 after merging this.


Update access-with-terraform.md

Added reference to cloudflare_access_application in the cloudflare_access_policy resource's application_id argument.

@garrettgalow can you take a look at this PR?


Serialize gui state to the Mastodon project.

The state of each opened view is serialized with the Mastodon project. The state includes window position, transform, current coloring, ...
Serialization is made in a XML file in the project file:
<?xml version="1.0" encoding="UTF-8"?>
<MamutGui version="0.3">
  <Windows>
    <Window>
      <Type>MamutViewBdv</Type>
      <FramePosition>1236 160 800 681</FramePosition>
      <CurrentTimepoint>22</CurrentTimepoint>
      <CurrentGroup>0</CurrentGroup>
      <CurrentSource>0</CurrentSource>
      <Interpolation>NEARESTNEIGHBOR</Interpolation>
      <DisplayMode>SINGLE</DisplayMode>
      <BdvTransform>9.047531577216374 -7.308699511743868 -0.51107405630934<PHONE_NUMBER>8936677 0.0 -0.8121047141929758 11.61363848317617 -381.0970600885638 -7.326546611057458 -9.02549224502162 -0.6311238989152388 1330.8443254543372</BdvTransform>
    </Window>
    <Window>
      <Type>MamutViewTrackScheme</Type>
      <FramePosition>374 398 815 674</FramePosition>
      <TrackSchemeTransform>-1.0 10.576227390180879 14.163380852140573 23.893960726900346 775.0 580.0</TrackSchemeTransform>
      <NoColoring>false</NoColoring>
      <TagSet>Fruits</TagSet>
    </Window>
  </Windows>
</MamutGui>

To access this data, the MamutViews exposes their content (trackscheme or bdv + coloringModel).
Deserialization is made by unmarshalling the XML into a Map<String, Object> that is passed to the constructors of MamutViewBdv and MamutViewTrackScheme, setting the state adequately, and when possible before the JFrame is made visible.

note the related PR #115

Hello Vlado.
I will have to rewrite all of this anyway...

Hi Jean-Yves,
well I don't know... I find it actually very educational, at least for me, to see how things can be read out... pity, I have discovered it only today (while I have prepared material for my PR much earlier).
I left the comment here only beacuse I found a non-zero intersection between the two PRs.

Hello Vlado,
Now that the master has new methods I will rewrite this and thrash this branch & PR.
You ok with that?

Hi Jean-Yves,
well, I don't know...
the new methods on master only do what your commit c26d467 was proposing plus they allow to retrieve the currently opened/viewed time point (and most likely only the time point of the given track scheme window, AFAIR).
As far as I understand your/this PR, it does much more: one can store/restore the layout of a session -- which I find actually very useful; I actually think the second commit of this PR is still valid
I would dare to back up and left this decision up to you -- I'm fine w/ and even w/o this PR existing (w/ + checkbox in load dialog "do you want to restore the precious session layout" would be the best IMHO)
long reply, low information, typical Vlado

Superseded by #117


Estimators and Statistics for RQMC Integraiton

Using this issue to keep track of estimators we may want to implement.

[ ] Confidence intervals and standard errors for RQMC sequences
[ ] Median-of-means estimators (and perhaps other robust mean estimators?)
[ ] Control variates
[ ] Maybe control functionals (but I have no idea what those do)
[ ] ?

I don't know about Control variate and control functional.
However, I can help on the first two boxes! In fact, we just release v3 of our work
The Robust Randomized Quasi Monte Carlo method, applications to integrating singular functions.
We basically combine Robust estimator (not just median of mean). We discuss briefly the Pan, Owen paper you linked in Section 5.

We review confidence intervals and standard errors (for Owen scrambling). Standard errors have different (asymptotic) scaling depending on the regularity of integrand $f$. What do you have in mind exactly ? List all asymptotic results for variance for various (R)QMC methods?
I don't think this QMC package should host robust estimator, but only focus on QMC. In fact, I developed the package RobustMeans.jl that does exactly that!
However, we could develop tutorials to show how to use the combination of Robust + QMC. It is more or less done on the repo of the paper, e.g., this notebook. It might not be super pedagogical as of right now.

I don't think this QMC package should host robust estimator, but only focus on QMC. In fact, I developed the package RobustMeans.jl that does exactly that!

Maybe we should create a separate package called something like QMCIntegrals.jl? It could include things like robust RQMC and control variates.
Control variates just means reducing the variance by using a known quantity x_true to adjust our estimate of the outcome y. We do a linear regression of x_observed on y_observed to get a coefficient c; then we adjust our estimate of f(x) by controlling for the error in x, i.e. x_observed - x_true, which lets us subtract off the error in our estimate of y caused by the error in our estimate of x.
It works the same with RQMC, we just need to use the correlation calculated by using the independent batches of x .

Maybe we should create a separate package called something like QMCIntegrals.jl? It could include things like robust RQMC and control variates.

Good idea! I actually prefer having a separate package for people to implement fancy control variate or other methods rather than a big "all in one" package (like qmcpy). I believe it more Julian way to do ?
We could also include discrepancy measures and the istmsnet that we defined in the runtest.jl file.
I don't have currently much time for this new package, as I have to move to other projects for now!
About the name here is my try QuasiMonteCarloTools.jl ?

Maybe we should create a separate package called something like QMCIntegrals.jl? It could include things like robust RQMC and control variates.

That would be great to see. Make sure it has an Integrals.jl hook so that it matches the other algorithms and is easy to swap to. I've been wanting a pure Julia higher dimensional integral method so that way when we are using weird number types and such it's easy to swap to it.


Create new org for incubating projects

The community has many projects related to Dapr, at many different levels of maturity. It can be an SDK or even a whole new framework on top of Dapr. Adding projects that are not production ready to Dapr org can give the perception of insufficient rigor in more stable repositories. Also, there can be projects that are highly ambitious and ambiguous that don't have a space in the Dapr community until it is "ready".
I propose we create the "Dapr Labs" organization (or similar name) to incubate projects under the Dapr brand.
IMO, these projects should be in "Dapr Labs":

https://github.com/dapr/workflows/
https://github.com/dapr/dart-sdk

I support this and think it'll allow for greater innovation. We do need to come up with the process of how a project is created in the new org and what's the criteria for acceptance and graduation. (As an example, do we require every project to be governed by a SIG? This might help in reusing existing structures and practices and help tame governance overhead).
Let's discuss this on next week's steering committee call.

I love this idea! I have a project that I have not open sourced yet that aims to make using Dapr even easier. I'd love for it to have a home in the community where it can get feedback and contributions. It's so important for new projects to obtain evidence that they solve for real pain point. Over time, I see a thriving ecosystem of tools being a way to broaden the adoption and usefulness of Dapr.

I am filing a service desk issue with CNCF. Just confirming that we want the org to be named dapr-incubations.

I am filing a service desk issue with CNCF. Just confirming that we want the org to be named dapr-incubations.

Either that or dapr-sandbox are fine with me.

Looking back, I remember that dapr-sandbox was a better name since this aligned with the CNCF concept of projects, where  they start in sandbox state first before move to Dapr org in order to start incubation and eventual graduation.

OK, dapr-sandbox it is.

https://github.com/dapr-sandbox created. Per https://github.com/dapr/community/issues/173#issuecomment-1151525495 moved repos to this org

Project moved and ReadMe written. Closing issue


address data sources using modelica URI

Using modelica URIs means there is no need to manually specify the location.

@Nejm78 Any reason why you did not merge this yet?

@dietmarw I have just merged, thanks for the fix :-)

You're welcome. You might possibly change the version now to 1.0.1 for that fixed version.


Feature/add time of arrival

this is wrong - the solicitor should not be able to change the interview start time... Only the cso should be able to do that.
This story needs to add a new field on the DR - solicitor_estimated_arrival_time or similar


[edgeclk] Option to show weather

First of all, thanks @tinxx for this great clock - I really really like it! I thought it would be nice to show the weather on the lower right as an additional option. So when showWeather is selected in the settings the clock changes as follows:

Note that I show steps with "K" only if weather is active (or > 100000 as before) to save some space... for all the other settings its exactly the same as before :)

Hey @peerdavid, thanks for the addition! Looks nice on the screenshot, but I currently have no weather provider for my watch, so I can't really test it…
Please change these two little things, if you would be so kind:

Same default options in app and settings
Update README with a Contributing section or similar (mentioning us both)
(You might want to pad less in line 163 if weather is displayed but probably not relevant as weather is drawn after steps)

Thanks!

Thank you so much for your comments!

Same default options in app and settings
I just ensured that settings.json and app.json both have the same default settings -- looks good IMO now :)

Update README with a Contributing section or similar (mentioning us both)
I added a contributor section

(You might want to pad less in line 163 if weather is displayed but probably not relevant as weather is drawn after steps)
Yea exactly so I decided to simply draw it afterwards then its fine. Otherwise I need a check if its weather and if its in"K" mode and set the padding accordingly. So this is IMO the easier option :)

Thanks!

Thanks for the changes and for your contribution in general, @peerdavid!
I am really happy that there is not only one person to use my clock but even a contributor! :heart:


[SPARK-48058][SPARK-43727][PYTHON][CONNECT] UserDefinedFunction.returnType parse the DDL string

What changes were proposed in this pull request?
UserDefinedFunction.returnType parse the DDL string
Why are the changes needed?
1, the return type check is missing in Python Connect;
2, to enable a group of tests;
Does this PR introduce any user-facing change?
yes
In [1]: import pandas as pd

In [2]: from pyspark.sql.functions import pandas_udf

In [3]: @pandas_udf("int")
   ...: def slen(s: pd.Series) -> pd.Series:
   ...:     return s.str.len()
   ...:

In [4]: slen.returnType

before:
Out[4]: UnparsedDataType('int')

after:
Out[4]: IntegerType()

How was this patch tested?
enabled tests
Was this patch authored or co-authored using generative AI tooling?
no

Yeah, I support this idea.

Merged to master.

thanks @HyukjinKwon and @dongjoon-hyun for reviews!


add raw contradiction by environmental package pair report to worst_offender.py

see #11

might be confusing because pairs aren't exhaustive/symmetrical ?


Update copyright information

Same as #120 but for master

If this is the same as #120, then I propose we close #120 and merge this instead. Then we merge master into develop.

Yes, if this is a hotfix required for 5.3 (master), then this is the expected procedure.

Reopening since we are going forward with this over #120

Note that you can always change the target branch of a PR using the Edit button. Pretty much the only thing you can't change is the source branch.

If this is a requirement from legal, I think some inconsistencies should be addressed/discussed:

I guess the Copyright legend is required to be added to all "code" files (cpp, hpp, etc.) So, why are potrs_gtest.cpp, syevd_heevd_gtest.cpp, error_macros.hpp, and exceptions.hpp not updated?
What about Fortran code? hipsolver_module.f90 and hipsolver_fortran.f90 are not updated either.
The python scripts rmake.py and rtest.py are only for users to build/install the library. If we update them, shouldn't we add the copyright notice to the install.sh script as well?

Added the missed fortran files and headers @jzuniga-amd mentioned. I left the comments out of install.sh since that's how rocBLAS is right now: comments in C++, python, and Fortran files but not the install.sh script.

clients/gtest/syevd_heevd_gtest.cpp and library/src/include/exceptions.hpp are still missing.
Is there any substantial reason to not update install.sh (other than that other libraries have not)? To me, one of the important parts of the copyright legend is the "software is provided as is..." install.sh provides software to assist users in the installation process (the same as rmake.py) so I think is important it has the legend.
For the same reasons, I think we should also update the sample codes in clients/samples/example_basic.c and clients/samples/example_basic.cpp

I just went ahead and added the message to install.sh as well, I think @jzuniga-amd 's reasoning makes sense for including it. I also added it to our CMake scripts since rocBLAS does that as well, they are code after all.

Your updated change looks good in principle, but I'm not going to have a chance to go through it in detail. As such, I've dismissed my review.


Enforce debug flag for intrusive CLI commands

Is your feature request related to a problem? Please describe.
Enforce debug flag for intrusive CLI commands
Describe the solution you'd like
Describe alternatives you've considered
Additional context

Fixed in <robustness 4ffc928>


Replace tg with twx as the backend

Done, but not with mtproto but botapi.

:(

@luckydonald Mtproto is not dead just on hiatus, I had to get off the ever crashing tg as I do use this bot.


[Storage] New api-version "2018-07-01" need for new features.

-Management-policy still uses 2018-03-01-preview

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/williexu/azure-cli-extensions.git@new_version#subdirectory=src/$EXT&egg=$EXT"


Better BibTeX startup failed: TypeError: Zotero.ItemPaneManager.registerInfoRow is not a function

Debug log ID
G928WY5Q-refs-euc/6.7.259-7
What happened?
Hello!
An error TypeError: Zotero.ItemPaneManager.registerInfoRow is not a function is raising up at every Zotero startup.
Zotero: 7.0.7 (64-bit)
BBT: 6.7.259

Hi, I opened the same ticket ;)
I checked the code, could it be that the function registerInfoRow was not declared?
Anyway, same ticket #3091

Not a typo.
I'm rolling out a new release that is downward compatible with missing functionality to prevent this problem, but the problem is solved by upgrading to Zotero 7.0.10.

Thank you. Where can we find the 7.0.10 version?

Help -> Check for upgrades


[WIP] Data services restructure

@aashish24
This is the start of restructuring the data_services setup.
There is still a lot of cruft from the original repo we'll want to remove for clarity.

After I had done this, I was able to see a geoserver at http://localhost:8080/geoserver/web, but didn't test the setup any further than that (and don't know how to).

I'm in the middle of things right now, so it is a bit messy and probably hard to see.  I'll need to delete the existing ansible_geonode dir once I'm finished.
The major restructuring I'm making is moving all of the tasks into separate roles.  Beyond that, I'm deleting all the stuff that we don't use.

@mgrauer can you make changes so that it show as diff and not new code. From the git point of view its looks odd that I have 20 commits and one commit brings all new changes. Also, as a developer that doesn't make me feel very excited :smile:. Also, please don't remove all the things we don't need right now since I was planning to make some more changes  and wanted the old code for reference. But if you don't like that idea, I can just work on my local copy.

Good points, I got a bit wild in my restructuring.  I'll revise this so that it is much easier to follow.  I'll ping you on the new commits to let you see it evolve in a more sensible manner.
There was a lot of stuff in the old repo, including many docs, that made it difficult for me to see what was actually used and how to do things.  My goal was to make this all easier to read through and understand.
I don't think we should merge into master anything that we don't actually use.

:+1: on keeping the file tree clean of unnecessary files.


support for Maya 2023

Hi, first congratulation for the great job you done!
Normally I use 2020 version of maya, but I started to try 2023 version but, unfortunately fspy wont work in 2023, i give this error:
Error: ModuleNotFoundError: file C:\Users/*****/Documents/maya/2023/scripts\maya_fspy\ui.py line 22: No module named 'pymel'
Thanks.

SOLVED
In maya 2023, for some reason, pymel was not installed.
Simply follow this guide to solve:
https://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/Maya-Scripting/files/GUID-2AA5EFCE-53B1-46A0-8E43-4CD0B2C72FB4-htm.html

Just noting this here, there is another branch on the Repo called V2 where I've completely removed all the PyMel. Please feel free to give it a go and let me know if you find any issues with it.
Thanks!


Fix bug #4957

Description (required)
Fixes #4957
Tests performed
Tested betaDebug on Mi A2 with API level 29

LGTM, will merge once @nicolas-raoul confirms it fixes the issue for him.