I don't see way to put a button inside of the closure

I cannot see way to resolve this error that refer to this line https://github.com/dancespiele/okspiel/blob/master/src/connect/connect_node.rs#L384 . Compile throw this:
cannot infer an appropriate lifetime for borrow expression due to conflicting requirements
   --> src/connect/connect_node.rs:384:61
    |
384 | ...                   Button::new(&mut self.copy, Text::new("Copy"))
    |                                   ^^^^^^^^^^^^^^
    |
note: first, the lifetime cannot outlive the lifetime `'_` as defined on the body at 382:91...
   --> src/connect/connect_node.rs:382:91
    |
382 | ...                   addresses.iter_mut().fold(Row::new().padding(20), |r, a| {
    |                                                                         ^^^^^^
note: ...so that closure can access `self`
   --> src/connect/connect_node.rs:384:61
    |
384 | ...                   Button::new(&mut self.copy, Text::new("Copy"))
    |                                   ^^^^^^^^^^^^^^
note: but, the lifetime must be valid for the anonymous lifetime #1 defined on the method body at 208:5...
   --> src/connect/connect_node.rs:208:5
    |
208 |     pub fn view(&mut self) -> Element<Message> {
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...so that the expression is assignable
   --> src/connect/connect_node.rs:209:9
    |
209 | /         Container::new(
210 | |             Row::new()
211 | |                 .height(Length::Fill)
212 | |                 .padding(20)
...   |
400 | |         )
401 | |         .into()
    | |_______________^
    = note: expected `iced_native::element::Element<'_, _, _>`
               found `iced_native::element::Element<'_, _, _>`

error: aborting due to previous error
```rust

It seems you are trying to create n buttons with just one button state (self.copy). Each button needs it's own state.

@Kaiden42 maybe could be one issue but doesn't resolve the problem:
https://github.com/dancespiele/okspiel/blob/master/src/connect/connect_node.rs#L394
the changes that I did are here = https://github.com/dancespiele/okspiel/commit/ce9dd396eb01e73c9fd9148a03e8c1842660082c
error[E0495]: cannot infer an appropriate lifetime for lifetime parameter in function call due to conflicting requirements
   --> src/connect/connect_node.rs:394:62
    |
394 | ...                   &mut self.copy_states[i],
    |                            ^^^^^^^^^^^^^^^^^^^
    |
note: first, the lifetime cannot outlive the lifetime `'_` as defined on the body at 390:45...
   --> src/connect/connect_node.rs:390:45
    |
390 | ...                   |r, address| {
    |                       ^^^^^^^^^^^^
note: ...so that closure can access `self`
   --> src/connect/connect_node.rs:394:62
    |
394 | ...                   &mut self.copy_states[i],
    |                            ^^^^^^^^^^^^^^^^
note: but, the lifetime must be valid for the anonymous lifetime #1 defined on the method body at 214:5...
   --> src/connect/connect_node.rs:214:5
    |
214 |     pub fn view(&mut self) -> Element<Message> {
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...so that the expression is assignable
   --> src/connect/connect_node.rs:215:9
    |
215 | /         Container::new(
216 | |             Row::new()
217 | |                 .height(Length::Fill)
218 | |                 .padding(20)
...   |
413 | |         )
414 | |         .into()
    | |_______________^
    = note: expected `iced_native::element::Element<'_, _, _>`
               found `iced_native::element::Element<'_, _, _>`

Yes, because indexing the states doesn't solve the problem of having the possibility to have two mutable references to the same state. If you have a number a (self.copy_states[a]) in an iteration and later a number b (self.copy_states[b]), who gurantees that a is never equal to b. Instead, you have to iterate over the states.
You could either zip the state's iterator with the addresses' iterator or store the states along with the addresses in a tuple or struct like explained in #712

In the end I resolved splitting it in different views. You can see more here .


Test pattern

Hello,
Is there any way I can add mask to constant patterns in 'Test pattern' GUI  ? I want to check my lissom activation for each and every test pattern after training .

Can you explain?  You can add masks to any pattern, but I don't know how that would help checking LISSOM activations.  I'd strongly recommend using GCAL rather than LISSOM, in any case; GCAL is simpler, more robust, and more realistic.

In GUI there is a menu item called "test pattern" where I can not set my predefined numpy array as mask in a constant pattern.

Are you working exclusively in the GUI or have you tried working in the Jupyter notebook? The latter is now the recommended workflow, so if you need some guidance on how to measure and display responses to arbitrary patterns in the notebook let me know.

In GUI there is a menu item called "test pattern" where I can not set my predefined numpy array as mask in a constant pattern.

I can't think of a way that you could do that in the GUI, but there's no need to use the GUI for presenting a constant pattern; just use the pattern_present command, either from the command line or a notebook.  Should be much simpler than trying to hack it into the GUI somehow.  I think you can still use the GUI's activity window to see the results afterwards, though I don't have a running copy of the GUI to try that with today.

Alternatively you can also use the featuremapper.command.measure_response, just specify the patterngenerator and the outputs to measure like this:
measure_response(outputs=['V1'], pattern_generator=ig.Constant(mask_shape=ig.Disk()), durations=np.linspace(0,1,21))

This will give you a HoloMap of Image types corresponding to each measured output. In a notebook this will visualize the response automatically.

Right; measure_response uses pattern_present internally, and users can use either approach.  I'm not sure what a mask will buy in this case, though -- a mask of a constant pattern is just the same as using the mask shape as the pattern shape, I would think.  Masks are important for things like images or gratings that you want to make circular, but maybe you have some other use case in mind.

Yes I mostly work on Jupyter notebook only but I did not know the way to test patterns. Thanks for these solutions. featuremapper.command.measure_response seem exactly like  what I am looking for .

No problem glad we could help.

Off this topic : Is Holoviews compatible with stable version of topographica now ? I had read that you guys going to update it .

When you stable version do you mean the 0.9.8 release? In that case the answer is probably no, it won't work very well. Personally I'm working with the development version of Topographica and HoloViews and will continue to make sure those work nicely together.

Since the 0.9.8 release, most of the development on Topographica has been driven by Jean-Luc and Philipp, who are now submitting their PhD theses.  My hope is that after they have submitted, we can release Topographica 1.0, incorporating all of their work and making sure everything is stable and usable.  For now, the development version (from github) has tons of new features, but anything not crucial for Jean-Luc and Philipp's theses has been a bit neglected, such as the Tk GUI.  For 1.0 I plan to either bring the GUI up to date with their changes, or else retire it altogether; depends on how much work it seems like at that time. :-/  Right now, everything but the Model Editor can be done using the notebook interface, though I'd personally like a version of the Test Pattern window that works in the notebook (which Philipp actually drafted at some point, but it's not currently usable).


Outfit the repo to be OSS / contributor friendly

contributing
code of conduct
development.md
clean up readme

contributing

https://github.com/stateful/runme/blob/main/CONTRIBUTING.md

code of conduct

https://github.com/stateful/.github/blob/main/CODE_OF_CONDUCT.md

development.md

Already part of CONTRIBUTING.md which makes sense to me until our project is big enough to separate both.

clean up readme

Looks clean to me, anything particular missing or should be removed?


[DE DateTimeV2] am 2. Weihnachtsfeiertag

am 2. Weihnachtsfeiertag should return 26th December, but it returns 2nd day of current month and next month, and 25th December.
Could you please fix it so that this only returns 26th December?
Thank you in advance.
Best Regards,
Jinjoo

@nawanas, can you prioritize this?

There was actually a simple change missing in the Holiday regex. Pushing the change soon.


[F6] [Dropdown Menu] Dropdown opens off-screen with right-aligned menu (not RTL text)

When using right-aligned menus, but not RTL text orientation (not using the .align-right class), dropdown menus still open aligned to their parent's left side. Such dropdowns should align instead to their parent's right side to appear on-screen as expected. This worked just fine in Foundation 5 without additional markup on any involved elements.
The following code will reproduce the issue with Foundation v6.0.1

        Example Right Dropdown

                Menu

Menu Item

Included CSS: Foundation v6.0.1, Normalize v3.0.3
Included JS: Foundation v6.0.1, jQuery v2.1.4

Is the result of your code on my machine. What exactly is it doing on yours?

My mistake. The example code still had the .align-right class applied. A live version of this issue is below. In addition, I've noticed that the link in the dropdown doesn't seem to work.

        Example Right Dropdown

                Menu

Menu Item

http://new.codegordon.com/

You will need the align-right class applied, as that implies all sub-menus should attach to their parent from the submenus right side.

This also makes everything render in reverse order, which is not desirable. The classes .top-bar-right and .title-bar-right should do this, and as mentioned above, used to do exactly that.
We shouldn't need to add additional markup and shuffle around the menu lists, especially for functionality Foundation had in v5.

After digging through the CSS a bit, it looks like the right-aligned bar used to apply the following to dropdowns, but no longer does.
position: absolute;
left: auto;
right: 0;

The code below was sufficient to get it working like Foundation 5 used to. I'm not sure how to do this in SCSS format, though.
.top-bar-right .dropdown.menu .menu,
.title-bar-right .dropdown.menu .menu {
	position: absolute;
	left: auto;
	right: 0;
}

This should be fixed now, please reopen if still an issue.

There's still an issue with v6.0.4, though a slightly different one. The menu opens with its right side aligned to the left side of the parent. Before, the right side of the menu was aligned with the parent's right side.

You still need to add the align-right class to have it position where you want it. I added the class on your live site and this is what you get:

Again, not only is that a redundant class to add, given the .top-bar-right/.title-bar-right class above it, but it uses float, which reverses the order of the bar-level menu items. This is most definitely not desired behavior.

I'm going to leave this one for @gakimball to resolve this in the scss, but here's a working solution for now:
apply the align-right class to your dropdown menu, then in your own sass/css target .menu.align-right > li with float: left;.
This is not an ideal solution, but that's what I have for you for now. This is the result:

Cheers.


How to resize the image for action item?

Hi, I wonder whether it can have a way to resize the menu icon in the button items? My action button & action items are quite large (130x130), but the icon size can't be changed although I use the large image. The icons look very small in the ipad.
Is there any way to do increaze their size by code? Some like:
actionButton.configureDefaultItem { item in
            item.size = CGSize()

Hey, currently you can set itemSizeRatio on the action button to define the size of the items (see here)
If I remember correctly the image sizes are determined by its original size. If this doesn't work, something is wrong.
Could you post the image you are using, the size of the action button and the value of itemSizeRatio you are using? Then I could check what's happening.

@jjochen  My code is
actionButton.itemSizeRatio = 0.95
actionButton.widthAnchor.constraint(equalToConstant: 130).isActive = true
actionButton.heightAnchor.constraint(equalToConstant: 130).isActive = true

My image is the pdf vector, it's small by default, but I though it could scale up?
menu-profiles.pdf
The item size can be changed according the action button, but not the icon https://gyazo.com/1c11cfab03b464a1aafb8caa571f4d75

Yes, that's it. I think the intrinsic content size of the image view is used which uses the original size of the image.
Also the pdf appears to contain a lot of whitespace around the actual icon. Maybe removing that is already enough?
On the other hand it's probably a good idea to be able to fix the image size somehow independent of the actual image size.

For now you could use something like this:

@jjochen Thanks for you help. But how can I remove the existing constraints? The constraints code is in the library.
I try something like this:
actionButton.configureDefaultItem { item in
            //let imageSizeMuliplier = CGFloat(1 / sqrt(2))
            NSLayoutConstraint.deactivate(item.imageView.constraints)
            item.imageView.widthAnchor.constraint(equalTo: item.circleView.widthAnchor, multiplier: 0.9).isActive = true
            item.imageView.heightAnchor.constraint(equalTo: item.circleView.heightAnchor, multiplier: 0.9).isActive = true
        }

And the action items are disappeared cause it conflicts with the existing ones as you said

Btw, I remove the whitespace around the actual icon, then scale up image and it works. Hope you can add a feature to resize later. Thanks

@ductranit That's good to hear! I think that's actually the best way to go.
I might add an image size property once I have a bit more time at hand.


Complete section show view

Just realized the section show view is incomplete, I should probably do that

All done, links back to course and all sections. Also displays all periods of that section


Key error on Week1

Hi @graviraja,
I was following your tutorial on wandb logging and found a potential error in the training code when visualizing poorly performed data with wandb table.
https://github.com/graviraja/MLOps-Basics/blob/13060e0295c7bbc1551e82fe49b6788a5a13ad97/week_1_wandb_logging/train.py#L19-L21
When running, this results in KeyError : "sentence", referring to line 21 sentences = val_batch["sentence"].
I think this is because "sentence" is not part of the columns setup in val_data of data.py. Please correct me if I'm wrong. Thanks :)
https://github.com/graviraja/MLOps-Basics/blob/13060e0295c7bbc1551e82fe49b6788a5a13ad97/week_1_wandb_logging/data.py#L29-L42

Hi @Taehee-K ,
I also got the same error as you. Did you fix that error?
Can you show me the results?


Persist multipart uploads in backend

Hey,
I think it would be a great idea to persist multipart uploads into the backend. (I kinda need that for a project I am working on) Currently implementing the following: (But not PR worthy yet)
Make the backends store chunks of the content, rather than the whole file. (As an optional interface maybe?)
This way we can just keep adding chunks to the backend object until we are done (maybe have a ready/finished flag on the object, too. Not sure, yet)
Then when a download is requested we can use a io.MultiReader to read out the chunks as we see fit. (maybe some clever seeking technique to not waste resources/file-handles)

This would be great!! In-memory multipart uploads were just a shortcut I took for my own employer's use case, I've been meaning to circle back to them for a while. My apologies if you were bitten by this limitation.

Make the backends store chunks of the content, rather than the whole file. (As an optional interface maybe?)

An optional interface sounds ideal. I would like the existing "in memory if your backend doesn't support it" feature to remain so users of backends that don't implement it still get access to a version of the feature (possibly behind an opt-in flag). We've been slowly moving to more granular optional interfaces and I think it's going well so far. There's a PR in flight here that may influence your PR a litte bit (#29) - I will clean up the remaining bits to get it merged as soon as I can.

Make the backends store chunks of the content

Just for the case of storing the parts of the multipart upload? Or as a modification to the method that handles putting an object? Which backend are you using?
Johannes is the final arbiter for this stuff, but so far we've been taking a "near-enough-is-good-enough" approach to the accuracy of the S3 support when merging new features, then refining as we go. If what you have advances support but isn't perfect and doesn't limit use-cases already supported (and you don't mind things moving around a little bit later if we need to restructure things a bit to make room for the next set of features), I'd vote for us to accept it with rough edges. The listing/pagination stuff in particular is quite fussy; I punted on it when preparing #30 with the intention of circling back to making it accurate as a stand-alone piece of work. Some of the backends don't currently support listing or pagination at all and just return the whole set. It's fine to mimic this if necessary.
Alternatively, if you get something part-way done, run out of time, move on to other work (or other, more featureful S3 implementations), etc, I'd be grateful if you would fire up what you have as a WIP PR anyway and we can pick it up and run with it.
Thanks for reaching out!

Ah I see you already have a branch in flight that covers most of what I said! Sorry, I should've done some more digging first. 😳
It looks like you're storing the multipart uploads as regular objects. S3 provides separate endpoints for listing multiparts and regular objects - I'm not sure we should conflate the two in the Backend interface.

It might be a good idea to state the background of what I want to accomplish.
I found gofakes3 as I wanted to implement some kind of S3 adapter, and it seems very interesting because of the pluggable backends and the general embedabilty of gofakes3.
My intention is to do as little read & write operations as necessary during this.
So my initial though was to just make every object 'chunked'. This has the benefit, that we can read multiple readers with  a io.MultiReader (as mentioned above + I already implemented a closing variant) and regular uploads, that are not multipart can simply just provide a single reader (=chunk).
That way we do have a break in the API, but it makes a GET and HEAD onto objects simpler.
The only thing I am not quite sure about how to handle is the in-flight state of that object.
For that purpose I added the IsFinished property onto the Object to make sure we can ignore those while listing Object until the upload of that key has been marked as finished by the uploader.
I can see 2 problems with this though:

There could be multiple upload IDs geared towards the same key, which wins?
A backend might store the obkect key in a map-like structure, so there con only be a single Object for a key. That would be unfinished during the upload and thus not listed.

After comtemplating the above, I still think the slice of ReadClosers is a good idea to keep it simple, but I think I need to extend the MultipartBackend to have some kind of 'staging area' where we can dump the uploads to, and then later transfer that into the 'real' state.
One thing I really want to avoid is to read all the data from the backend to save it via the PutObject(bucketName, key string, meta map[string]string, input io.Reader, size int64) method.
I'll try to come up with something here.

Hi @T4cC0re contributions are always welcome thanks a lot for raising the topic, which is a quite interesting one! I'm very interested to see a first draft implementation.
Blake (@shabbyrobe) with all his contributions to this repo, has done an incredible good job with the pluggable backends, nice to read it was the reason you chose gofakes3 to build upon.

I went ahead an implemented the first usage of the new Interface. No backend code yet, but I found some stuff I have not been aware of before by doing that.
Next step for me is to enhance the bolt backend to use it.
I rolled back my change about the Object.Contents being a []io.ReadCloser. Instead I think this should get handled by the backend transparently by exposing a MultiReadCloser if desired.
I shifted from gofakes3 doing the most work, to moving the complexity to the backend, because ultimately this is not easy to abstract in a way that is usable for a large number of use cases.
I'll add a WIP PR right away. I think this is mostly what I wanna go with (with maybe some small adjustments)

Created #34 . Will add modifications to bolt backend there.

closed due to inactivity


[FLINK-7749][network] refactor the ResultPartitionWriter into an interface

What is the purpose of the change
After moving task event notification into the TaskEventDispatcher (#4761), this PR finally makes the ResultPartitionWriter wrapper an interface.
Brief change log

change ResultPartitionWriter from a wrapper to an interface
adapt usages & clean up duplication of ResultPartitionWriter and ResultPartition

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Will merge this later on, and will do some git magic to integrate #5147 while doing so.


Configurable force pushing

Thought I would have a crack at my own issue I raised, so this is a work in progress PR to implement #205
I'm not very familiar with Go and the test cases are a little fiddly to write (given most of the "actual" work is done by libgit2 and a single character change to the refspec) so will take me a little longer to write those up. I thought I'd open the draft PR so someone else doesn't unnecessarily pick up the issue when I'm almost done.
In the meantime a couple questions:

It isn't a breaking API change, but should I be implementing for the older api specs (v1alpha1) etc like I have done? (Not sure what the correct process is)
Any issues with/comments on the actual implementation below?

should I be implementing for the older api specs

No, older API versions are considered readonly.
PS. Please signoff your commits, see https://github.com/fluxcd/image-automation-controller/pull/206/checks?check_run_id=3208778477

This is going to be pretty tricky to test. The controller always does a fresh clone and checkout of the push branch; to necessitate a push --force, you would need to alter the upstream push branch after the controller has fetched it, but before it tries to push to it. The test will fail, because it doesn't do this interleaving, but expects --force to be necessary.
// observe the first commit
					waitForNewHead(localRepo, pushBranch)

					// Create commit on push branch that would conflict with a commit on top of the a branch from the checkout branch
					dummyCommitMessage := "Dummy Commit"
					commitInRepo(cloneLocalRepoURL, pushBranch, dummyCommitMessage, func(tmp string) {})

// origin pushBranch now has a commit "Dummy Commit"

					waitForNewHead(localRepo, pushBranch)

					head, err := localRepo.Reference(plumbing.NewRemoteReferenceName(originRemote, pushBranch), true)
					Expect(err).NotTo(HaveOccurred())
					pushBranchInitialHeadHash := head.String()
					dummyCommit, err := localRepo.CommitObject(head.Hash())
					Expect(err).NotTo(HaveOccurred())
					Expect(dummyCommit.Message).To(Equal(dummyCommitMessage))

// the local clone now (verifiably) has the head at Dummy Commit

					// update the policy and expect another commit in the push branch, deleting local branch to ensure commit is not on top of the dummy commit
					localRepo.DeleteBranch(pushBranch)
					policy.Status.LatestImage = "helloworld:v1.3.0"
					Expect(k8sClient.Status().Update(context.TODO(), policy)).To(Succeed())

// This deletes pushBranch locally, but does nothing to the origin

// When the policy object is updated, the controller will clone the repo from the origin, check out the branch specified, and commit on top of it.

					// Delete local push branch and refetch remote
					localRepo.DeleteBranch(pushBranch)
					waitForNewHead(localRepo, pushBranch)
					head, err = localRepo.Reference(plumbing.NewRemoteReferenceName(originRemote, pushBranch), true)
					Expect(err).NotTo(HaveOccurred())
					fetchedPushBranchLatestHeadHash := head.String()
					pushBranchLatestCommit, err := localRepo.CommitObject(head.Hash())
					Expect(err).NotTo(HaveOccurred())

// this will get the new head of push branch, which is the commit made by the controller (on top of Dummy Commit)

					// Expect push to fail
					// Check with messages for easier debugging
					Expect(dummyCommit.Message).To(Equal((pushBranchLatestCommit.Message)))

// this fails because the head commit is the commit made by the controller

					// Check with hashes for certainty
					Expect(pushBranchInitialHeadHash).To(Equal((fetchedPushBranchLatestHeadHash)))


soroban-rpc: simulateTransaction: automatically detect ledger entries which require restoring

This change incorporates two new fields to simulateTransaction's Response:
PreRestoreTransactionData string                       `json:"preRestoreTransactionData,omitempty"` // SorobanTransactionData XDR in base64
PreRestoreMinResourceFee  int64                        `json:"preRestoreMinResourceFee,omitempty"`

When preflighting an InvokeHostFunction operation, soroban-rpc will now detect ledger entries which require restoring prior to the invocation for it to succeed.
If any such entries are detected, the simulateTransaction response will provide the Soroban Transaction Data and minimum resource fee needed to restore those entries.
The user is then now expected to:

Submit a RestoreFootprint operation using the new fields above, if present.
Submit the InvokeHostFunction operation normally (i.e. using the pre-existing simulateTransaction response fields)

Closes https://github.com/stellar/soroban-tools/issues/803

@dmkozh does something like state_expiration.rs already exist? I figure you need something like that upstream.
Otherwise, it may make sense to place it in the env library if you find it appropriate.

@willemneal we should probably use this in the cli once merged

@Shaptic you have an example of how to use this at

To me, PreRestore sounds misleading, since it's not something you would do before the restore operation. it's the information for the restore operation. I would use the preamble/prelude prefix for these two fields.

No strong opinions here.

thinking about that further, I think that what I'd like to see if I were in @Shaptic 's seat is the following:
RestorePreamble  restorePreamble   `json:"restorePeramble,omitempty"` // optional restore preamble

where the restorePreamble is defined as
type restorePreamble struct {
  TransactionData string           `json:"transactionData"` // non-optional since the struct itself is optional; base64 encoded.
  MinResourceFee  int64            `json:"minResourceFee"` // non-optional since the struct itself is optional.
}

@tsachiherman from a client perspective, having one omittable structure is better than two, so yes, I agree - I like encapsulating it into a structure like this. Of course we could have said "zero or both of these are present," but "zero or one" is much better!

this LGTM as-is but I’d prefer the schema Tsachi outlined

sure


Can't find zimbra_pflogsumm.pl

Hi, at this address the file is no more available
https://raw.githubusercontent.com/jorgedlcruz/zimbra-grafana/master/zimbra_pflogsumm.pl
Can you help me please?
Thank you in advance

Hello,
Yes, I am not using that anymore, the latest information and Dashboard leverages the official OpenLDAP and official postfix output, more info here https://grafana.com/grafana/dashboards/2846

Thank you, i have just finished installing everithing by the old way... well, later i will try the new one :-)
Have a good time
Da: "Jorge de la Cruz"<EMAIL_ADDRESS>A: "jorgedlcruz/zimbra-grafana"<EMAIL_ADDRESS>Cc: "VMax2"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>Inviato: Martedì, 6 ottobre 2020 18:01:10
Oggetto: Re: [jorgedlcruz/zimbra-grafana] Can't find zimbra_pflogsumm.pl (#8)
Hello,
Yes, I am not using that anymore, the latest information and Dashboard leverages the official OpenLDAP and official postfix output, more info here https://grafana.com/grafana/dashboards/2846
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or unsubscribe .

Everything went very well, now the dashboard is up and running , thank you
Da: "Jorge de la Cruz"<EMAIL_ADDRESS>A: "jorgedlcruz/zimbra-grafana"<EMAIL_ADDRESS>Cc: "VMax2"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>Inviato: Martedì, 6 ottobre 2020 18:01:10
Oggetto: Re: [jorgedlcruz/zimbra-grafana] Can't find zimbra_pflogsumm.pl (#8)
Hello,
Yes, I am not using that anymore, the latest information and Dashboard leverages the official OpenLDAP and official postfix output, more info here https://grafana.com/grafana/dashboards/2846
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or unsubscribe .

i’am using influx and telegraf to monitor my zimbra server in order to display outgoing mails i tried this tuto ‘‘https://computingforgeeks.com/how-to-monitor-zimbra-server-with-grafana-influxdb-and-telegraf/’’
and as i saw on tutorials there are all using ‘‘zimbra_pflogsumm.pl’’
but this file .pl is empty and when using ''curl -sL https://raw.githubusercontent.com/jorgedlcruz/zimbra-grafana/master/zimbra_pflogsumm.pl | sudo tee /opt/zimbra/common/bin/zimbra_pflogsumm.pl
‘’
the file is not found !
i just wanted to display outgoing mails  and zimbra queues !
how can i do that please ?

Hello,
I've removed the .pl a long time ago in favor of using native telegraf inputs from postfix and OpenLDAP, try the new config and let me know, it should work just as fine.

it's working and it's the second time i'am using your dashboard all works good but i just need

to display outgoing mails
and i got problem with zimbra queues it show no data (how can i solve that )
?

Outgoing mails the postfix input doesn't take them, so please open another issue so I will need to investigate.
For the queues, should show some data, open another issue so we track that differently, this one is closed.


[MCS-DE] Publishing Profile Settings and Warnings/Errors when Publishing

When I publish with Composer v2.0.0 I keep getting these warnings.
---
"Abs settings incomplete, skip linking bot with webapp ..."
---

---
"appPasswordHint incomplete, return ..."
---

=> However there are no such settings in the Composer template for the Publishing Profile.
=> Further the "luisResource": "" setting is missing in the publishing profile template again however required to bind the Prediction Resource when publishing LUIS.
=> When creating the LUIS resources the following settings are taken from the appsettings instead of the publishing profile when creating the LUIS apps during the publishing:
  "name": "<unique name in your subscription>",
  "environment": "dev",

Publishing Profile template retrieved from Composer v2.0.0
{
"name": "",
"environment": "dev",
"tenantId": "",
"hostname": "",
"runtimeIdentifier": "win-x64",
"resourceGroup": "",
"botName": "",
"subscriptionId": "",
"region": "",
"settings": {
"applicationInsights": {
"InstrumentationKey": "",
"connectionString": ""
},
"cosmosDb": {
"cosmosDBEndpoint": "",
"authKey": "",
"databaseId": "botstate-db",
"containerId": "botstate-container"
},
"blobStorage": {
"connectionString": "",
"container": ""
},
"luis": {
"authoringKey": "",
"authoringEndpoint": "",
"endpointKey": "",
"endpoint": "",
"region": "westus"
},
"qna": {
"subscriptionKey": "",
"endpoint": ""
},
"MicrosoftAppId": "",
"MicrosoftAppPassword": ""
}
}
@garypretty @benbrown

@cwhitten @sgellock Any update when this will be fixed?


SPAdes fails

Spades fails when running the current version of the pipeline (-r main or -r v1.0.0). The command used is below:
nextflow run cdcgov/phoenix -r v1.0.0 -profile singularity -entry PHOENIX --input manifest.csv --kraken2db /home/databases/ --outdir $PWD/test
The outputs of the .command files is shown below:
==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.begin <==

==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.err <==
cp: cannot create regular file '/home/test/isolate1/': No such file or directory
cp: cannot create regular file '/home/test/isolate1': No such file or directory

==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.log <==
Option -k triggered, argument = isolate1.trimd_summary.txt
Option -n triggered, argument = isolate1
Option -d triggered, argument = /home/test
cp: cannot create regular file '/home/test/isolate1/': No such file or directory
cp: cannot create regular file '/home/test/isolate1': No such file or directory
find: ‘*.spades.log’: No such file or directory

==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.out <==
Option -k triggered, argument = isolate1.trimd_summary.txt
Option -n triggered, argument = isolate1
Option -d triggered, argument = /home/test

==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.run <==
#!/bin/bash
# NEXTFLOW TASK: PHOENIX:PHOENIX_EXTERNAL:SPADES_WF:SPADES (isolate1)
set -e
set -u
NXF_DEBUG=${NXF_DEBUG:=0}; [[ $NXF_DEBUG > 1 ]] && set -x
NXF_ENTRY=${1:-nxf_main}

nxf_tree() {
    local pid=$1

    declare -a ALL_CHILDREN
    while read P PP;do
        ALL_CHILDREN[$PP]+=" $P"
    done < <(ps -e -o pid= -o ppid=)

    pstat() {
        local x_pid=$1
        local STATUS=$(2> /dev/null < /proc/$1/status egrep 'Vm|ctxt')

        if [ $? = 0 ]; then
        local  x_vsz=$(echo "$STATUS" | grep VmSize | awk '{print $2}' || echo -n '0')
        local  x_rss=$(echo "$STATUS" | grep VmRSS | awk '{print $2}' || echo -n '0')
        local x_peak=$(echo "$STATUS" | egrep 'VmPeak|VmHWM' | sed 's/^.*:\s*//' | sed 's/[\sa-zA-Z]*$//' | tr '\n' ' ' || echo -n '0 0')
        local x_pmem=$(awk -v rss=$x_rss -v mem_tot=$mem_tot 'BEGIN {printf "%.0f", rss/mem_tot*100*10}' || echo -n '0')
        local vol_ctxt=$(echo "$STATUS" | grep '\bvoluntary_ctxt_switches' | awk '{print $2}' || echo -n '0')
        local inv_ctxt=$(echo "$STATUS" | grep '\bnonvoluntary_ctxt_switches' | awk '{print $2}' || echo -n '0')
        cpu_stat[x_pid]="$x_pid $x_pmem $x_vsz $x_rss $x_peak $vol_ctxt $inv_ctxt"
        fi
    }

    pwalk() {
        pstat $1
        for i in ${ALL_CHILDREN[$1]:=}; do pwalk $i; done
    }

    pwalk $1
}

nxf_stat() {
    cpu_stat=()
    nxf_tree $1

    declare -a sum=(0 0 0 0 0 0 0 0)
    local pid
    local i
    for pid in "${!cpu_stat[@]}"; do
        local row=(${cpu_stat[pid]})
        [ $NXF_DEBUG = 1 ] && echo "++ stat mem=${row[*]}"
        for i in "${!row[@]}"; do
        if [ $i != 0 ]; then
            sum[i]=$((sum[i]+row[i]))
        fi
        done
    done

    [ $NXF_DEBUG = 1 ] && echo -e "++ stat SUM=${sum[*]}"

    for i in {1..7}; do
        if [ ${sum[i]} -lt ${cpu_peak[i]} ]; then
            sum[i]=${cpu_peak[i]}
        else
            cpu_peak[i]=${sum[i]}
        fi
    done

    [ $NXF_DEBUG = 1 ] && echo -e "++ stat PEAK=${sum[*]}\n"
    nxf_stat_ret=(${sum[*]})
}

nxf_mem_watch() {
    set -o pipefail
    local pid=$1
    local trace_file=.command.trace
    local count=0;
    declare -a cpu_stat=(0 0 0 0 0 0 0 0)
    declare -a cpu_peak=(0 0 0 0 0 0 0 0)
    local mem_tot=$(< /proc/meminfo grep MemTotal | awk '{print $2}')
    local timeout
    local DONE
    local STOP=''

    [ $NXF_DEBUG = 1 ] && nxf_sleep 0.2 && ps fx

    while true; do
        nxf_stat $pid
        if [ $count -lt 10 ]; then timeout=1;
        elif [ $count -lt 120 ]; then timeout=5;
        else timeout=30;
        fi
        read -t $timeout -r DONE || true
        [[ $DONE ]] && break
        if [ ! -e /proc/$pid ]; then
            [ ! $STOP ] && STOP=$(nxf_date)
            [ $(($(nxf_date)-STOP)) -gt 10000 ] && break
        fi
        count=$((count+1))
    done

    echo "%mem=${nxf_stat_ret[1]}"      >> $trace_file
    echo "vmem=${nxf_stat_ret[2]}"      >> $trace_file

==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.sh <==
#!/bin/bash -euo pipefail
bash /home/.nextflow/assets/cdcgov/phoenix/bin/pipeline_stats_writer_trimd.sh -a isolate1_raw_read_counts.txt -b isolate1_trimmed_read_counts.txt -c isolate1_1.trim.fastq.gz -d isolate1_2.trim.fastq.gz -e isolate1.kraken2_trimd.report.txt -f isolate1.trimd_summary.txt -g isolate1_trimd.html
sh /home/.nextflow/assets/cdcgov/phoenix/bin/beforeSpades.sh -k isolate1.trimd_summary.txt -n isolate1 -d /home/test

cat <<-END_VERSIONS > versions.yml
"PHOENIX:PHOENIX_EXTERNAL:SPADES_WF:SPADES":
    spades: $(spades.py --version 2>&1 | sed 's/^.*SPAdes genome assembler v//; s/ .*$//')
END_VERSIONS

spades_complete=run_failure,no_scaffolds,no_contigs
echo $spades_complete | tr -d "\n" > isolate1_spades_outcome.csv

spades.py \
     \
    --threads 8 \
    --memory 10 \
    -s isolate1.singles.fastq.gz \
    -1 isolate1_1.trim.fastq.gz -2 isolate1_2.trim.fastq.gz \
    --phred-offset 33\
    -o ./

mv spades.log isolate1.spades.log
spades_complete=run_completed
echo $spades_complete | tr -d "\n" > isolate1_spades_outcome.csv

rm /home/test/isolate1/isolate1_summaryline_failure.tsv
rm /home/test/isolate1/isolate1.synopsis

==> work/38/e248803652d1a3b48d4ffe5d359b45/.command.trace <==

@johnsonj161 what kind of system are you working on (HPC, local laptop or cloud)? The error that kills this is the /.command.err <== cp: cannot create regular file '/home/test/isolate1/': No such file or directory. Basically it can't find that folder. The v1.1.0 version that we are hoping to have out sometime in Feb should have a fix for this.

I am using a local Linux machine. I ran the test dataset and I am getting the same issue. I checked and the 'missing' directory appears to be present. Do you have any idea why I would be getting this issue if the directory is present? and if so, is there a temporary fix prior to the v1.1.0 update being released? I appreciate your help!

It has to do with how full paths are read by nextflow. Try adding a trailing backslash to your --outdir. If you don't mind using a dev version for a month I would use nextflow run cdcgov/phoenix -r v1.0.1 -profile singularity -entry PHOENIX --input manifest.csv --kraken2db /home/databases/ --outdir $PWD/test Let me know if that newer version works for you. This will be a good test to make sure the fixes are in fact fixes. Note that -r v1.0.1 is the branch with the correction, but ultimately when I release this branch I will make it v1.1.0 as the changes warrant the upgrade.

Yay, I would recommend taking a clone of that as we are gonna push updates to that branch and nextflow will yell about changes at some point using nextflow run cdcgov/phoenix. So to be clear run git clone -b v1.0.1 https://github.com/CDCgov/phoenix.git that will install a folder phoenix in the folder where you ran that command then you can run it like you were before nextflow run phoenix/main.nf -profile singularity -entry PHOENIX --input manifest.csv --kraken2db /home/databases/ --outdir $PWD/test.


create custom favicon

the tab just looks so empty without a custom favicon...

:+1:

How about this one @ttonyan10?


[openapi] Updating import to provide some schema.

Adds --input-file to breadboard run so that you can add in required board parameters as a JSON file and not on the CLI
breadboard import the OpenAPI board now will dynamically generate inputs for parameters that are required.
bradboard run will use the default args if provided on the board.
breadboard import the OpenAPI board now uses secrets.
breadboard debug fixed the local-boards.
breadboard - removes log, and also assumes that missing types are strings.
recipes - all of the LLM recipes now use new api.

@aomarks - just as a heads up, I had to merge main back into this branch and it looks like it's saying the affected packages by this change is a lot larger than the 2 I had submitted.... Is that going to cause issues?

@aomarks - just as a heads up, I had to merge main back into this branch and it looks like it's saying the affected packages by this change is a lot larger than the 2 I had submitted.... Is that going to cause issues?

I think what's happening is that, since your changeset has a minor revision to breadboard, it will get bumped from 0.8.0 to 0.9.0 on next release. In semver, when your leftmost digit is 0, the second digit is actually treated like a breaking change (it's kind of like the change semantics all shift right; like it starts from the first non-zero digit). So, that means every package that depends on breadboard (which is almost all of them), will also need to be released the next time we publish, because their dependency semver constraints need to be bumped from ^0.8.0 to ^0.9.0 (because ^0.8.0 does not match 0.9.0).
So, a bit confusingly, while a package is at 0.x.x, we should use patch to add a new feature, and minor for a breaking change. We shouldn't use major unless we want to release 1.0.0.
We could also bite the bullet and go straight to 1.0.0. I'd actually be slightly in favor of that, because it means we get to have the full major/minor/patch distinction. Version numbers are free.

Got it - hmm. Sorry I merged this before your reply. Oof. ok, but I think it makes sense because I did change the functionality with the fix.

changeset sees all!


Adding s3 and ipfs backups of repository

This will resolve missing files from repositories.
Resolves:

https://github.com/ethereum/source-verify/issues/87
https://github.com/ethereum/source-verify/issues/92
https://github.com/ethereum/source-verify/issues/108

This way we have 2 ways of backuping files:

s3 public bucket (centralized) - done
ipfs (decentralized) - TODO

S3 bucket is will be used in append only mode. No files will be able to be deleted.
In case that ipfs doesn't work s3 bucket can be always accessed.
Secrets will be managed through .env which won't be pushed to repo.

This will be fixed here: https://github.com/ethereum/source-verify/pull/89

Due to bugs on cirleci services have now be seperated and this can be merged to staging to fix CI issues.
On another PR ipfs publish and deploy with secrets will be covered.


fix: don't normalise half turns

Closes #136
drive-by: cargo update (hugr 0.13.2)
I have tested the test inhttps://github.com/CQCL-DEV/guppy-integration/pull/19 now passes and the example has expected behaviour with crz oracle.

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

Project coverage is 84.76%. Comparing base (2d9bfce) to head (247b096).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #137      +/-   ##
==========================================
- Coverage   85.02%   84.76%   -0.26%
==========================================
  Files          31       31
  Lines        4327     4313      -14
  Branches     4327     4313      -14
==========================================
- Hits         3679     3656      -23
- Misses        310      326      +16
+ Partials      338      331       -7

Flag
Coverage Δ

rust
84.76% <100.00%> (-0.26%)
:arrow_down:

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

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


Change the timing of creating the radiance texture for panoramic sky

Currently the radiance texture is generated whenever the texture is assigned to the panoramic sky by the logic found here:
https://github.com/godotengine/godot/blob/master/drivers/gles3/rasterizer_storage_gles3.cpp#L1353
With viewport textures this is a problem because this happens as the scene is loaded and the viewport texture won't be fully setup at this point in time. It won't have contents until we start rendering. Also it means that if the viewport is updated we never update the radiance map. There is a silver lining there because it stops people from rendering a skymap every frame and grinding their game to a halt but for occasional updates it is a problem.
Both have workarounds, simply re-assigning the texture on the panoramic sky triggers the logic and updates all the buffers required (this is what I do in my sky asset).
Now the first problem I can fix, but the second problem I need some input into hence I haven't applied a PR for this yet.
What I suggest for solving the first problem is by removing the radiance map generation logic from RasterizerStorageGLES3::sky_set_texture and simply setting a flag "is_dirty".
Then just before we render our sky in RasterizerSceneGLES3::_draw_sky we check if this flag is set, and if so update the radiance buffer. There might be a one frame delay in the radiance buffer being used (as we've already rendered our geometry) but I think that is acceptable.
That said, an improvement on this approach that would also solve #2, and which may be doable thanks to the proxy texture approach if we record a little more info, is to trigger rendering the radiance map in response to the viewport being updated.
So in our viewport render loop in VisualServerViewport::draw_viewports, once a viewport has been rendered we check all the consumers of the viewport texture for that viewport and do some sort of callback that the consumer registers when it creates the proxy.
In the case of a panoramic sky that callback results in the radiance map being updated.
@reduz , @karroffel , any ideas, suggestions, etc? I'll happily build the logic in if we come to a consensus of how we want to approach this.

What's the status on this issue?
CC @clayjohn

It still seems relevant to me. But it's better to leave bumped to 4.0 as no other users have noticed or cared. Reduz has already done a lot to overhaul sky/environment maps and @BastiaanOlij is doing more work on sky shaders.

With 3.2 the time neded for all sorts of calculations when you add a new panorama texture increased due to new features in a difficult region for dynamic skyboxes for my projects and tests.
So far I could use dynamic panoramic skyboxes with carefully timing and precalculating as much as I could. To assign a new panoramic sky it took me around 10ms and I added the option to disable sky updates for lower region hardware.
With 2.3 it takes 37ms on my hardware with the same settings for my project.
If we use the Godot-Sky-Asset-Master as a reference it is 13ms for 3.1.1 and 74ms for 3.2. (GTX 970, i7-2600K)
If I change all to the lowest resolution possible (32 radiance & irradiance) it is 9ms for 3.1.1 and 22ms for 3.2 on my pc.
22ms even on the lowest resolution setting gets you always a heavy delay that you stand no chance against as you can not compensate it. From the "Users View" "sky.Panorama = LastTexture;" is an atomic assignment.
I think we either parallelize the process (which is prob very difficult as the maps are generatied on the GPU in godot) or provide non atomic assigments.
There may even be some simple solutions:
1- If we provide an additional method like UpdatePanorama(Texture panorama, RadianceMap radiance, IrradianceMap irradiance) we could precalculate the needed maps, interpolate between calculated maps or also distribute the calculation need over several frames and then assign them together. So we still have the current approach but provide also the possibility to assign them directly together.
2- If it is possible to deactivate the auto generation so that we can state specific times when to generate new rad&irrrad. I think its often ok to just update the panoramic sky with a new texture and uptate the rad or irrad just every few frames and distribute the calculation need over several frames. But of course the new uptates must stay in a certain perfornamce region, otherwise we did not really gain anything.
I personally would prefer 1- as it provides me many new options to work with and allows to parallelize many tasks. The dirty flag would improve the timing but to get dynamic skyboxes feasible we need a different approach I think as the calculation time is very high and currently not possible in parallel.

For me it looks like https://github.com/godotengine/godot/pull/37179 solves the problem we have with the timing and the dynamic update. Aswell as gives us access to the new Skyshader system which is looking very promising!
Infos in the Article https://godotengine.org/article/custom-sky-shaders-godot-4-0
I'm very exited!

Closed by #37179
:)


MINOR: code cleanup

Same as #6054

Call for review @guozhangwang @bbejeck @vvcephei

lgtm. @mjsax please feel free to merge after replying the above quesion.


Add PHP Symfony Security Check parser

This PR adds a parser for the PHP Symfony Security Checker.
The reason for this is that the PHP Scanner of the OWASP Dependency Check is in an experimental state and basically not working. The snyk scanner is a commercial scanner which is not available to everyone.
My initial tests show this works, there's one open question:

How to the handle the fact the symfony security scanner doesn't provide a severity rating in its output?

A) Chose a default
This is what I have done for now, defaulted to 'Info'. The risk is that the vulnerabilities might be skipped if a minimum severity is specified for the import.
B) Leave empty
This would require changes to DefectDojo as the datase column is not allowed to be null and the import process checks the severity against a minimum severity.
C) Add a new severity value of 'Unknown' or 'TBD' to DefectDojo
This would require some more changes and might be difficult with metrics and maintaining a mapping to numbers to compare vulnerabilities. Not sure if we can expect more scanners to not specify a severity.
D) Allow unverified findings to have no severity rating
Even more work :)
Please let me know your thoughts.

Also it looks this isn't working when the Finding is created. The CWE field remains empty:
cwe=1035
Not sure why as other parsers are doing the same thing.

I've looked at some of the vulnerabilities in the database used by this scanner and it seems quite common to have vulnerabilities without a severity rating, some don't have a CVE as well, etc.
So ideally DefectDojo would support findings without a severity that will only get a severity after triage in DefectDojo.

@valentijnscholten Info is what I've done in the past. I think I prefer Info to blank though. Would you mind uploading a sample to sample files?

Also it looks this isn't working when the Finding is created. The CWE field remains empty:
cwe=1035
Not sure why as other parsers are doing the same thing.

For the record, this works fine now.


Switch between tabs by Ctrl + Page Up/Down

What feature or improvement do you think would benefit Files?
It would be nice to add shortcuts for switching between tabs by Ctrl + Page Up/Down, as it has become a standard and common shortcut.
Requirements
Only requires adding two shortcuts.
Files Version
<IP_ADDRESS>
Windows Version
Windows 11
Comments
No response

Thanks for the feedback, you can change them your self. https://files.community/docs/customize-settings/actions

Thank you for your feedback, we don't have plans to have these shortcuts by default but you can follow the instructions Josh shared to set them up for yourself.


Governance actions examples ideas

https://sancho.network/tutorials/actions/#submitting-a-treasuy-withdrawal-and-protocol-parameter-update-governance-action

https://developers.cardano.org/docs/get-started/cardano-cli/governance/


mina-verify-packaged-fork-config: command -v pullup

Not sure why this wasn't done in the first place;
maybe there is some error lurking that testing
will remind me about?
Test plan: run HF package flow.

https://buildkite.com/o-1-labs-2/hardfork-package-generation/builds/224 automated invocation is happy
To do: try invoking with missing dependency and see better error message.

New error message confirmed inside docker:
ember@hbox ~> docker run -it --entrypoint /bin/bash gcr.io/o1labs-192920/mina-daemon:01b5f43-focal-devnet-hardfork
root@78f49522e5e7:~# apt remove mina-create-legacy-genesis
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  mina-create-legacy-genesis
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 49088 files and directories currently installed.)
Removing mina-create-legacy-genesis (1.4.0beta2-compatible-97f7d8c) ...
root@78f49522e5e7:~# curl https://storage.googleapis.com/tmp-hardfork-testing/devnet_fork_config_apr_09.json.gz > config.json.gz && gunzip config.json.gz && mina-verify-packaged-fork-config devnet config.json /workdir/verification
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1610k  100 1610k    0     0  8521k      0 --:--:-- --:--:-- --:--:-- 8521k
gzip: config.json already exists; do you wish to overwrite (y or n)? n
	not overwritten
root@78f49522e5e7:~# mina-verify-packaged-fork-config devnet config.json /workdir/verification
Copying gs://mina_network_block_data/devnet-296371-3NKSvjaGSKiQuAt8BP1b1VCpLbJc9RcEFjYCaBYsJJFdrtd6tpaV.json...
/ [1 files][ 14.9 KiB/ 14.9 KiB]
Operation completed over 1 objects/14.9 KiB.
generating genesis ledgers ... (this may take a while)
/usr/local/bin/mina-verify-packaged-fork-config: line 110: mina-create-legacy-genesis: command not found
root@78f49522e5e7:~#

I remember why I didn't do this:
command -v will fail where you invoke it.

Probably shouldn't do this, actually...

Expected error:
Line 56 should have a failing source_build_fallback invocation

Instead, the missing mina-create-legacy-genesis name is being propagated all the way to the use-site on line 110.

!ci-build-me

!approved-for-mainnet


Resolve merge conflict

Resolve merge conflict from Next to Main

It looks like there is no change, but we need to explicitly choose to use the changes on next over the existing one on main


Added command-line argument for baud rate to 'serial' subcommand

Added a -b/--baud command line argument to the piku serial command. The serial connection will default to 115200 baud if this option is omitted.

Thank you @tammymakesthings sorry about the late reply I have been busy with work.  This looks good to me,  would you please change the quotes to single instead of double, so they match up with the rest of the project and I will merge asap.  Appreciate your contribution.


Enquiry for the amount of the Ds_real / Ds_fake(generated）while you do cal for FID

For example your real dataset contain 6K, then you also generated 6K to calculate the FID?

Sorry to bother you one more question, I am curious about how you located the generated image that matching the original image


v1.9 backports 2020-10-26

#13710 -- Update wording for BPFFS requirement and move to main system requirements page (@joestringer)
#13702 -- pkg/endpoint: calculate Kube API-Server lag from pod events (@aanm)
#13713 -- doc: Update OpenShift GSG (@michi-covalent)
#13606 -- datapath: Decouple IPV4_MASQUERADE from IPV4_NODEPORT (@brb)
#13719 -- docs: remove repeated words (@tklauser)
#13669 -- doc: update Hubble doc for 1.9 (@Rolinh)
#13718 -- ci: Print hint to fix auto-generated file checks (@sayboras)
#13717 -- docs: Add a note about systemd 245 rp_filter issue (@brb)
#13733 -- docs: Do not over promise in BPF-masq docs (@brb)
#13726 -- nodeinit: Update image tag (@errordeveloper)
#13716 -- Fix deadlock on eventqueue when it's being drained when endpoints are being restored (@christarazi)
#13737 -- docs: Various LRP gsg fixups (@nebril)
#13729 -- pkg/k8s: keep resource version when watching CRDs (@aanm)
#13682 -- Helm: Adapt Hubble ingress template to the new Ingress API (@youssefazrak)
#13674 -- Various fixes for NodePort XDP kube-proxy free guide (@tklauser)
#13707 -- backporting: Clean tmp files after backport with conflicts (@pchaigno)
#13636 -- certloader: Fix reload on K8s Secret/ConfigMap update (@gandro)
#13730 -- Remove remnants of bindata check script (@tklauser)
#13728 -- operator: do not early return on CEP GC (@aanm)

Once this PR is merged, you can update the PR labels via:
$ for pr in 13710 13702 13713 13606 13719 13669 13718 13717 13733 13726 13716 13737 13729 13682 13674 13707 13636 13730 13728; do contrib/backporting/set-labels.py $pr done 1.9; done

test-backport-1.9

Putting this back into draft. I noticed that two commits from PR #13674 are missing, because the scripts did not correlate the commits due to escaping errors in the commit message (which is used as a regex). Will move out of draft once I fixed that issue and made sure the script picks up the commits properly.

Looks good for my commit

Looks like backports for commits b32876d and c0b8a82 from #13674 are missing (while f8fe7b5 was properly backported). I didn't spot anything in the PR description regarding these. Were they overlooked, were there merge conflicts or did I miss something?

See https://github.com/cilium/cilium/pull/13751#issuecomment-716512945 ;) While I could easily add them manually, I want to fix the scripts first to properly escape the commit messages.

Pushed the two missing commits. It's now 33 commits, same as the output of check-stable. I'll open a PR with the partial fix for the scripts.

test-backport-1.9


Improve CircleCI branch failure messaging

Description
The current CircleCI messaging to slack and pager duty is inadequate in that there isn't enough context.  This update should improve the context we see around build failures in CircleCI.
New message will look like this:

Also, if a job has the word deploy in it then the color will change to red.
Reviewer Notes
Please review the messaging to ensure it meets our expectations.
Setup
The way I tested this was to comment out the code that sends notifications to PagerDuty.  Then I modified the .circleci/config.yml so that build_tools would fail early and announce_failures would trigger only on my branch.  I let people in #dp3-engineering know that this was happening in advance and then pushed my work.  That helped me create the image above.
All of this work will have to be reverted before merging.
Code Review Verification Steps

[x] Request review from a member of a different team.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change
Slack Attachment Guide

@kahlouie - I did the revert! :)


(draft) Leptos 0.7

(Opening this so that I can start tracking test/docs/example coverage)
Things I'd like to achieve before a beta release

[x] Clear all warnings (todo!() is okay)
[ ] Complete docs
[ ] All tests passing in core
[x] Actix integration
[x] All examples either a) ported, b) missing features listed in TODOs, or c) moved to projects

Incomplete list of feature TODOs

[x] nonces
[x] .await on resources: clone by default for IntoFuture, with alternate method to read them by reference
[x] Setting ResponseOptions in integrations
[x] local resources (resources that only run on the client, not server)
[x] <ProtectedRoute/>
[x] Render individual Suspend(_) without a <Suspense/>
[ ] Nested router set_is_routing
[x] Attribute spreading for attributes on <Body/> etc. instead of Vec<AnyAttribute>
[x] Directives
[ ] Equivalent to a user implementing IntoView on an arbitrary struct
[ ] Figuring out the interaction between Lazy routes and hydration (what do you do while hydrating if the code for the route hasn't been lazy-loaded yet?)
[x] path!() macro to make route definitions easier in router
[ ] Reactive channel implementation for single-use signals
[x] blocking resources
[x] partially-blocked SSR
[x] Thread-local arena that yields Copy but !Send for !Send data (like browser things)
[x] global class support
[ ] hot reloading (and therefore view markers)
[ ] static routes
[ ] trailing slash modes
[ ] Router/Route base
[x] custom elements/custom attributes
[ ] fallible hydration => start from suspense boundary
[x] add GlobalAttributes methods for on____ HTML attributes

Forward-ported bug fixes (things that have been fixed on 0.6 but reimplemented in 0.7, and need to be checked)

[ ] pending action dispatches (#2653)
[ ] unescaping during navigation (#2651)
[ ] ownership and disposal fixes and tests (#2639)
[ ] ToChildren docs (#2643)
[ ] #2621

Finalizing:

[ ] simplify tachys APIs by removing duplicated content (HTML length, checking on template duplication, etc.)

Will there be follow-up tickets for tracking the open tasks from this PR? I am mainly interested in static routes, but some of the other open points certainly are big enough to also be tracked on their own.

@NiklasEi Yes, it is just way easier to manage a single main branch once people start making PRs, and it was time! Everything else will be completed. I will probably just create a single tracking item that copy-pastes the list above.


Stop producing blocks in certain catchup scenarios

It's dangerous for block producers to propose in the following catchup scenarios:

We just finished bootstrap and didn't finish catchup. In this scenario, we might got the wrong epoch ledger since we are using peer's best tip to do the required_local_state_sync. This is related to #4028. In this scenario, the node would crash.
If we are offline for a long time and back online later. If the network advanced by x blocks where k <= x < 2k + delta which means we need to do catchup. In this scenario, if we produce a block off our best tip, then we would produce a block that is disconnected to other peers' frontier and we would be punished or banned which is also pretty bad.

Nathan proposes that our system should set up a signal that informs the proposer to stop producing blocks if there is a potential catchup job that makes our frontier advance more than k - 1 blocks. Once the catchup job finishes, the proposer could continue working.
Since this would lead to crashes of proposers, I suggest we should fix this soon.

since banning is turned off, what's the risk in not addressing item #2 above?
Can we address this for now by just communicating to the users that they shouldn't produce a block until they are synced?

Can we address this for now by just communicating to the users that they shouldn't produce a block until they are synced?

Isn't this a problem given most(?) would be starting via the flag --block-producer-key and not interactively i.e. coda client set-staking? Given block production is "paused during bootstrap" it seems a similar mechanism to handle catchup would be the most appropriate.


Prepare changelog for 0.1.3 release

Summary
Prepare the changelog for 0.1.3 release.
Metadata

Question
Answer

Did you use a meaningful pull request title?
yes

Did you apply meaningful labels to the pull request?
yes

Did you perform a self review first?
yes

Documentation reflects changes?
no

CHANGELOG reflects changes?
yes (made it up)

Unit/Functional tests reflect changes?
n/a

Did you perform browser testing?
yes

Risk level
Low

Relevant links
rig-6

Ok!
/approved


Crash

Blackbird Bitcoin Arbitrage
DISCLAIMER: USE THE SOFTWARE AT YOUR OWN RISK

Log file generated: output/blackbird_log_20180121_191823.log
Blackbird is running... (pid 420)

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted (core dumped)

[ 01/22/2018 07:58:00 ]
   Bitfinex: 	11,602.00 / 11,611.00
   OKCoin: 	12,738.70 / 12,841.95
   Kraken: 	11,667.60 / 11,667.70
   QuadrigaCX: 	9,960.01 / 11,450.00
   Exmo: 	13,000.00 / 13,040.00
   ----------------------------
   OKCoin/Bitfinex:	-9.66% [target  0.80%, min -13.49%, max -8.41%]
   Kraken/Bitfinex:	-0.56% [target  0.80%, min -1.78%, max -0.10%]
   QuadrigaCX/Bitfinex:	 1.33% [target  0.80%, min -10.30%, max  1.55%]   trailing  1.40%  1/1
<Bitfinex> Looking for a limit price to fill 0.004305 BTC...
<Bitfinex> order book: 0.712327@$11,603.00

[ ENTRY FOUND ]
   Date & Time:       01/22/2018 07:58:00
   Exchange Long:     QuadrigaCX (id 3)
   Exchange Short:    Bitfinex (id 0)
   Fees:              0.50% / 0.20%
   Price Long:        11,450.00 (target)
   Price Short:       11,603.00 (target)
   Spread:            1.33%
   Cash used:         49.95 on each exchange
   Exit Target:       -0.57%

I think I'm facing a similar issue. Is your terminal window logging the following error also: 'Segmentation fault: 11'?

No, but I am not sure if it has something to do with used OS. I am running on Ubuntu on Windows 10.
Anyway, it happened again.
Blackbird Bitcoin Arbitrage
DISCLAIMER: USE THE SOFTWARE AT YOUR OWN RISK

Log file generated: output/blackbird_log_20180211_030735.log
Blackbird is running... (pid 1715)

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted (core dumped)

[ 02/11/2018 06:41:33 ]
   Bitfinex:    8,047.20 / 8,047.30
   OKCoin:      8,888.04 / 9,058.02
   Bitstamp:    8,069.01 / 8,072.37
   Kraken:      8,064.40 / 8,070.80
   QuadrigaCX:  7,901.04 / 7,998.99
   Exmo:        8,490.20 / 8,523.96
   Cexio:       8,239.20 / 8,251.00
   ----------------------------
   Bitfinex/Kraken:      0.21% [target  0.80%, min -0.33%, max  0.50%]
   OKCoin/Bitfinex:     -11.16% [target  0.80%, min -12.97%, max -8.66%]
   OKCoin/Kraken:       -10.97% [target  0.80%, min -12.80%, max -8.57%]
   Bitstamp/Bitfinex:   -0.31% [target  0.80%, min -0.89%, max  0.24%]
   Bitstamp/Kraken:     -0.10% [target  0.80%, min -0.84%, max  0.27%]
   Kraken/Bitfinex:     -0.29% [target  0.80%, min -0.69%, max  0.26%]
   QuadrigaCX/Bitfinex:  0.60% [target  0.80%, min -4.93%, max  0.74%]
   QuadrigaCX/Kraken:    0.82% [target  0.80%, min -5.00%, max  0.82%]

[ ENTRY FOUND ]
   Date & Time:       02/11/2018 06:41:33
   Exchange Long:     QuadrigaCX (id 4)
   Exchange Short:    Kraken (id 3)
   Fees:              0.50% / 0.25%
   Price Long:        7,998.99 (target)
   Price Short:       8,065.30 (target)
   Spread:            0.82%
   Cash used:         39.53 on each exchange
   Exit Target:       -1.18%

From my two logs, it seems problem is caused when QuadrigaCX is used as Exchange Long? I am really not a C developer, so I what is meaningful way to debug this :)

Happened to me too. I think it's a parsing error somewhere in Quadriga

@davidjirovec @fdoumet Could you please try to trace the error? Thanks

Type the command ulimit -c unlimited. This will produce a core file next time Blackbird crashes
Run ./blackbird
When Blackbird crashes you should get a core file in the current directory
Type gdb ./blackbird core to start GNU Debugger. Install it if you don't have it yet
Type backtrace in the debugger. You should be able to see when the crash occurred and hopefully why.

Thanks for the help on how to debug.
#0  0x00007f3bb85d7428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1  0x00007f3bb85d902a in __GI_abort () at abort.c:89
#2  0x00007f3bb8f1a84d in __gnu_cxx::__verbose_terminate_handler() ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007f3bb8f186b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007f3bb8f18701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007f3bb8f18919 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007f3bb8f4114f in std::__throw_logic_error(char const*) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007f3bb8faca94 in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char const*>(char const*, char const*, std::forward_iterator_tag) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007f3bb8facc4c in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x000000000044225b in QuadrigaCX::sendLongOrder (params=..., direction="buy",
    quantity=0.0025641025641025641, price=9750) at /home/adenda/blackbird/src/exchanges/quadrigacx.cpp:88
#10 0x00000000004321e8 in main (argc=1, argv=0x7ffdba353788) at /home/adenda/blackbird/src/main.cpp:607

So yes, looks like the error is with Quadriga in this line:
std::string orderId = json_string_value(json_object_get(root.get(), "id"));
Looking at the documentation for the Quadriga API, it doesn't look like it the buy or sell endpoints return an id field at all, which is what that line is looking for.

Turns out Quadriga has a minimum trade amount of 0.005 BTC. So if you attempt to send a long order with anything else than that, it will return an error.


JBPM-5214: Case Milestones

@cristianonicolai First approach for case milestones

@nmirasch if you could also add sorting/grouping to how the milestones are displayed. I think we should list in this order: Available, Completed and Terminated. On each of these, milestones should be ordered according the milestone name alphabetical order.

@cristianonicolai @jhrcek can you take a look? Thanks!

@cristianonicolai changes done

jenkins retest this

@cristianonicolai changes done!

@cristianonicolai changes done

@cristianonicolai done!

great work @nmirasch!


[BUG] : Fix Subject Field and Min-Max Character Validation for Message Box on Contact Us Page

Description
Overview

The Contact Us page is currently not able to validate subject field, which is crucial for users to specify the purpose of their message.
Additionally, the message box does not enforce minimum or maximum character limits, which could lead to incomplete or excessive submissions.

Screenshots

Any additional information?
Other Issue:

Enhancing the UI of the Contact Page with proper font-size and Font-Color

What browser are you seeing the problem on?
Chrome
Checklist

[X] I have starred the repository
[X] I have checked the existing issues
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)

@Kritika30032002 Hey there,Can you look into this issue and assign me this issue to be fixed under GSSOC-extd ,hackOctoberFest label under any Level. Looking for additional inputs .Thanks in Anticipation :)


Add SOQL oriented database management system

Add json, that will contain all data related to account system. Also create simple system to add new JSON data containers.

We will use our database management system that will be based on SOQL - string oriented query language (partially based on SQL standarts)

Oriented date of SOQL management system implementation is february or later. We will support this dms in march or later


[REQ][python] Allow strict float parsing

Is your feature request related to a problem? Please describe.
We currently face validation errors when facing 0 values for a required float type. We would like to handle these values as floats. Our backend is written in Typescript which makes it impossible to save a value 0.0 because it will transformed to 0.

Describe the solution you'd like
It exists an closed issue for the related python generator in the openapi-generator library. The corresponding fix is in this MR.
Is it possible to have a similar additional flag that allows such a strict behavior?

Describe alternatives you've considered

Additional context

Can you please give an example schema and payload that is failing?

Hmm looks like there is a bug here for format double and float integer ingestion:
>>> schemas.Float32Schema.validate(0)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/schemas.py", line 102, in validate
    return super().validate_base(arg, configuration=configuration)
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/schema.py", line 556, in validate_base
    path_to_schemas = cls.__get_path_to_schemas(cast_arg, validation_metadata, path_to_type)
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/schema.py", line 311, in __get_path_to_schemas
    other_path_to_schemas = cls._validate(arg, validation_metadata=validation_metadata)
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/validation.py", line 139, in _validate
    other_path_to_schemas = validator(
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/validation.py", line 288, in validate_types
    raise __get_type_error(
petstore_api.exceptions.ApiTypeError: Invalid type. Required value type is float and passed type was int at ['args[0]']

and
>>> schemas.Float64Schema.validate(0)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/schemas.py", line 102, in validate
    return super().validate_base(arg, configuration=configuration)
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/schema.py", line 556, in validate_base
    path_to_schemas = cls.__get_path_to_schemas(cast_arg, validation_metadata, path_to_type)
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/schema.py", line 311, in __get_path_to_schemas
    other_path_to_schemas = cls._validate(arg, validation_metadata=validation_metadata)
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/validation.py", line 139, in _validate
    other_path_to_schemas = validator(
  File "/Users/justinblack/programming/openapi-json-schema-generator/samples/client/petstore/python/venv/lib/python3.8/site-packages/petstore_api/schemas/validation.py", line 288, in validate_types
    raise __get_type_error(
petstore_api.exceptions.ApiTypeError: Invalid type. Required value type is float and passed type was int at ['args[0]']

The openapi format registry defines float as:
single precision floating point number
And it defines format double as:
double precision floating point number
Why not define this data type as type: number ? That way serialization.deserialization will work.

Hmm I see that ingesting 0 is failing for format float and double ingestion.

We get the same error message in our use case.

The openapi format registry defines float as: single precision floating point number And it defines format double as: double precision floating point number Why not define this data type as type: number with no format? That way serialization + deserialization will work. Do you need the single precision min and max constraint applied?

Just using type: number will work as it includes integer values. The only problem we have is that we automatically create the openapi.yaml with TSOA which will by default set format: double. As the issue is more related to the behavior of TSOA and not primary to this repository, I created ticket on their side.

My suspicion is that float and double formats should allow integers in by default because some language contexts (javascript) do not know the difference. One could add a command line option intsAllowedForFloatDoubleFormats to allow users to opt in or out of this behavior in the generated code. It would adjust the type definitions in that case. I am asking for guidance from other implementers on this issue.

Independent of our problem, having such flag could give the user more flexibility but with a certain cost of adjusting the type definition as you said. Additionally, I could think of use cases where such flag is suitable and with making it optional, the default behavior will not change. The error message is still correct as ingesting a 0 where a float value is expected, should lead to a validation fail.

I just released version 4.3.0 which includes the command line arg --ints-allowed-for-float-double-formats
When one generates a client with it set to true, ints are allowed in to number with format float/double per:
>>> from unit_test_api.schemas import schemas
>>> schemas.Float32Schema.types
frozenset({<class 'float'>, <class 'int'>})
>>> schemas.Float32Schema.validate(0)
0
>>> schemas.Float64Schema.types
frozenset({<class 'float'>, <class 'int'>})
>>> schemas.Float64Schema.validate(0)
0

Thanks for your work :)

You're welcome


Add Gift Card 🎁

Don't create an empty issue.
Always describe your issue!

Hello @sunny0625 what about issue #704

Level?

Level?

After PR.


bug(MatPaginator): page observable parameter is not an instanceof PageEvent

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I had expected the emitted value in the MatPaginator's .page Observable to be an instanceof PageEvent, but that doesn't seem to be the case. I was merging several observables together and making a query to my backend, and wanted to only reset the paginator's index to 0 only after my data had returned as long as the paginator did not trigger the query. I figured I could easily check if the emitted value was an instanceof PageEvent or not, but that doesn't seem to be the case.
Is there a reason why this behavior is occurring other than being a possible bug? PageEvent is a class type, so I would have expected it to have been instantiated as such.
I may also be fundamentally misunderstanding something, so please forgive me.

Reproduction
This is shown in this StackBlitz: https://stackblitz.com/edit/angular-9svfyb?file=src%2Fapp%2Fpaginator-overview-example.ts
@Component({
  selector: 'paginator-overview-example',
  templateUrl: 'paginator-overview-example.html',
})
export class PaginatorOverviewExample implements AfterViewInit {
  @ViewChild(MatPaginator) paginator: MatPaginator;

  ngAfterViewInit() {
    this.paginator.page.subscribe((pageEvent: PageEvent) =>
      console.log(
        'pageEvent instanceof PageEvent',
        pageEvent instanceof PageEvent // this returns false
      )
    );
  }
}

### Expected Behavior

For the page event to be an `instanceof PageEvent`

### Actual Behavior

It is not an `instanceof PageEvent`.

### Environment

(from stackblitz)
{
  "name": "example-app",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~15.0.0",
    "@angular/cdk": "15.1.2",
    "@angular/common": "~15.0.0",
    "@angular/compiler": "~15.0.0",
    "@angular/core": "~15.0.0",
    "@angular/forms": "~15.0.0",
    "@angular/material": "15.1.2",
    "@angular/material-moment-adapter": "15.1.2",
    "@angular/platform-browser": "~15.0.0",
    "@angular/platform-browser-dynamic": "~15.0.0",
    "@angular/router": "~15.0.0",
    "moment": "^2.18.1",
    "rxjs": "~7.4.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.11.5"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~15.0.0",
    "@angular/cli": "~15.0.0",
    "@angular/compiler-cli": "~15.0.0",
    "@types/jasmine": "~3.10.0",
    "@types/node": "^12.11.1",
    "jasmine-core": "~3.10.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "~1.7.0",
    "typescript": "~4.8.2"
  }
}

I took a look into the source. Any reason this wouldn't be a new PageEvent()?
https://github.com/angular/components/blob/dabbff4d062caf52bdc160c3802a35eacf2bbcbd/src/material/paginator/paginator.ts#L362
PageEvent class: https://github.com/angular/components/blob/dabbff4d062caf52bdc160c3802a35eacf2bbcbd/src/material/paginator/paginator.ts#L57
page emitter:
https://github.com/angular/components/blob/dabbff4d062caf52bdc160c3802a35eacf2bbcbd/src/material/paginator/paginator.ts#L195
Although, I am a little confused how this compiles successfully. Isn't any anonymous object not the same as an instance of an actual class?


Blue highlight over WSL Terminal

Issue Type: Performance Issue
All text in my WSL shell in VSCode is highlighted in blue, and changing LS_COLORS did nothing.

This is my first time submitting an issue to GitHub and I'm not sure how to reliably reproduce the bug, as all I do is open a WSL Terminal.
VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:23:51.859Z)
OS version: Windows_NT x64 10.0.18247

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.86GB (8.63GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vsc-material-theme
Equ
2.5.1

nbpreviewer
jit
1.0.0

mips
kda
0.0.2

python
ms-
2018.9.2

cpptools
ms-
0.19.0

material-icon-theme
PKi
3.6.0

pdf
tom
0.3.0

(1 theme extensions excluded)

This is probably happening because you changed the theme colors of cmd.exe

This is likely related to winpty, tracking in https://github.com/Microsoft/vscode/issues/45693

Thank you very much for looking into this. As far as I know, I recently wiped my computer and don't believe I've made any changes to the theme of cmd.exe since.


Add dependabot

@dlfivefifty can you give me access to the Settings for this repo so that I can add dependabot?
(Or add it yourself if you prefer.)
In all my other repos dependabot has been updating the github action versions and I'd like that to be automatic here too.
I can do merges here but I don't have Security access.

Made you admin! Hopefully thsat's enough

Yep - thanks!


pipenv==2018.11.26' distribution was not found

Hello,
I used pipenv to create python virtual environments but it is not working anymore. When I run pipenv --version it outputs the message below.
I uninstalled it already and installed a clean version with homebrew but nothing has changed.
Do we know how to solve this issue?
Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/2018.11.26_2/libexec/bin/pipenv", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/Users/joana.pinto/.pyenv/versions/3.7.4/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3191, in <module>
    @_call_aside
  File "/Users/joana.pinto/.pyenv/versions/3.7.4/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3175, in _call_aside
    f(*args, **kwargs)
  File "/Users/joana.pinto/.pyenv/versions/3.7.4/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3204, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/Users/joana.pinto/.pyenv/versions/3.7.4/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/Users/joana.pinto/.pyenv/versions/3.7.4/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/Users/joana.pinto/.pyenv/versions/3.7.4/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pipenv==2018.11.26' distribution was not found and is required by the application

Check your path setting, you made pyenv's python take precedence over the brew one.

I want to use the python from pyenv.
Output of the echo $PATH command:
/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

@joanap, I run into the same issue every now and then. Never got a chance to dig deep in to why this is happening. Every time I ran into this error, I find $ brew reinstall pipenv fixes the issue. You can probably try that to unblock yourself.

@hanpeter I would like to be able to install several Python versions with pyenv and create virtual environments with pipenv. I already tried reinstall and uninstall pipenv but the error persists.
Here are some variables:
$ echo $PATH
/Users/joana.pinto/.pyenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
$ which pyenv
/usr/local/bin/pyenv
$ which python
/Users/joana.pinto/.pyenv/shims/python

@joanap, your stack trace says your pipenv executable is coming from Homebrew's cellar. That is very confusing to me. If you want to use pyenv's python, wouldn't you just do $ pip install pipenv in the virtual environment created by pyenv?
In my current set up, I installed pipenv and pyenv from Homebrew. I have multiple version of python via pyenv.  When I want to create a virtual environment using a version of python, I do $ pipenv --python X.Y.Z. Sure, my pipenv lives on my system rather than within a virtual environment, but I trust Homebrew to handle that properly. I believe this set up gives you what you are looking for.
Alternatively, I believe you can set a global version in your pyenv then install pipenv via pip in that version. Then you should be able to do the same as above, if you are in the global version. In other words, if you have Python 3.6 and 3.7 installed and use 3.6 as the global version, you should be able to do $ pipenv --python 3.7 as long as you are currently using the 3.6 version.
Hope that clarifies what you are looking for.

I think this is the same as https://github.com/pypa/pipenv/issues/4013

I ran into the exact same issue right after reinstalling node with brew. brew reinstall pipenv fixed the issue for me, as described by @hanpeter.


better throughput without GC?

We're using a great nottinygc to reduce the cost of GC in wasm guests.

Swapping this added 110KB to the base size of the wasm guest, but resulted in 48pct drop in execution time of a simple plugin, in a scale of hundreds of microseconds.
https://github.com/codefromthecrypt/kube-scheduler-wasm-extension/blob/main/guest/RATIONALE.md#why-do-we-recommend-nottinygc-but-not-import-it-by-default

But, nottinygc is archived.
I've had an another idea for this challange coming from GC actually since before.
When api.Module is closed, I suppose all resources allocated to the module are released.
And, then I'm wondering if it'd be possible to get a better performance by stopping GC on wasm module from tinygo with -gc=leaking flag, and instead create/delete modules every time on host side. The performance depends on how expensive creating a new guest is though.
This issue intends to research that possibility, with seeking concerns around it too.

/priority next-release

I give it a try. So, in short, -gc=leaking + module recreation increases the throughput, at least with my implementation.
I tried it at no-gc branch,

Close wazero.Module every time the scheduling cycle (or binding cycle) finishes, and recreate a new one.

Recreate wazero.Module (InstantiateModule) afterwards.
This recreation is done in goroutine, so it shouldn't block the scheduling directly.

OnlyFilter_xxx runs PreFilter and Filter, while xxx runs all extension points.
Advanced_(with_normal_gc) runs a wasm module that has a normal TinyGo GC, while Advanced runs an examples/advanced wasm module, which is using nottinygc in Before and using gc=leaking in After.

Before:
$ make bench-example
goos: darwin
goarch: arm64
pkg: sigs.k8s.io/kube-scheduler-wasm-extension/internal/e2e/scheduler
BenchmarkExample_NodeNumber/OnlyFilter_Advanced/Run-12           1687575               741.3 ns/op
BenchmarkExample_NodeNumber/OnlyFilter_Advanced_(with_normal_gc)/Run-12           490719              2438 ns/op
BenchmarkExample_NodeNumber/Advanced/Run-12                                        33591             36176 ns/op
BenchmarkExample_NodeNumber/Advanced_(with_normal_gc)/Run-12                       10000            103483 ns/op

After:
$ make bench-example
goos: darwin
goarch: arm64
pkg: sigs.k8s.io/kube-scheduler-wasm-extension/internal/e2e/scheduler
BenchmarkExample_NodeNumber/OnlyFilter_Advanced/Run-12             53358             18770 ns/op
BenchmarkExample_NodeNumber/OnlyFilter_Advanced_(with_normal_gc)/Run-12            54272             18816 ns/op
BenchmarkExample_NodeNumber/Advanced/Run-12                                        12394             95442 ns/op
BenchmarkExample_NodeNumber/Advanced_(with_normal_gc)/Run-12                        4820            225602 ns/op

The result in After shows using gc=leaking is faster than normal tinygo gc.
But, looking at the comparison between Before and After, Advanced_(with_normal_gc) takes more time in After than Before.
We recreate modules in goroutine, so the recreation doesn't block the scheduling directly, but we can have a guess it does indirectly; a frequent recreation of modules causes the wazero runtime executing wasm functions slower somehow.


xsar not compatible with numpy==2.0.0

For now geoviews dependency needed in the sphinx documentation required numpy<2.0.0 , let's wait for the bumps.

If this is meant to take time, It would be great to pin numpy in the dependencies, because I have repin it myself each time I install xsar

I just tested and there is no more conflict with geoviews.
I opened a PR to solve the compatilibity : https://github.com/umr-lops/xsar/pull/216


fix: reusing AES IV could cause potential security risks

Issue #, if available:
IDE-5677
Description of changes:
Pentest recommendations:

Remove the IV from being specified when the server is first created.
Generate a new IV for each request, every time a new encryption operation is being performed.

This value does not need to be secret, but it does need to be unpredictable and unique.

Include the IV alongside the ciphertext in each request, so it can be used to decrypt the message when used with the correct key.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

ServerModeHttpClientAuthorizationHandler needs to be updated to pass along the updated generated IV as part of the authorization header.

I'm not sure what you want me to update. The IV is already being passed into the header.

I pulled down the branch and saw ServerModeHttpClientAuthorizationHandler has been updated. Not sure which PR that was in but it looks good. I just have the one other comment.


Fix collisions

Is I'm to the right of a jelly, I can't kill it with a benji. This is probably due to the new follow code which is causing the jelly's position to be not an integer which throws off the collision code. Make integers in 06_collisions.p8 and it might work again.

The problem was that I was looking for momentum >0 and when the benji was thrown to the left, that resulted in a negative momentum which failed the collision check and did not inflict damage on the jelly.


🐛[BUG]: Using output_grid different than model grid results in an error

Version
Beta main
On which installation method(s) does this occur?
Source
Describe the issue
Running examples/01_ensemble_inference.py with a slightly changed config using "output_grid": "s2s" results in an AssertionError in line 40 of earth2mip/geometry.py
I was expecting to be able to write other output grids to netcdf by defining the output_grid in the config
Environment details
No response

Sorry about that. This regridding functionality doesn’t work. It requires access to some preexisting map files that aren’t in this repo. We are working on a tool with better regridding support. Until that is ready we should remove this functionality or provide a better error message.

Our regridding library is out: https://github.com/Nvlabs/earth2grid. Would be a nice feature to add this back.


Bibliography reference rename

In your project.bib in the paper/ dir, you seem to have updated the citation information without changing the citation label (i.e. it still is under the tag lindquist2008statistical).
This would get very confusing in the actual paper as that tag (lindquist...) is how you refer to the reference in the report.tex. Therefore, the tag should match the actual paper you are referencing:
A standard (though not necessary) format for BibTex citation references is

Hello Ross,
Thank you for the feedback. I actually created to a pull request to change this in our repo last week but changed my mind afterwards. I wanted to fix some issues in our project repo before that - for example, we currently have 3 branches including the master that we still need to merge.


ApolloServer from async function

Hi there, I'm trying to upgrade to Apollo v4 and this lambda integration is the last piece that has me stumped.
Our Apollo server has to deal with a promise on the schema (we're stitching our local schema together with a remote one):
new ApolloServer({
    schema: await this.getExecutableSchema(),
    plugins: [telemetryPlugin, playground],
});

Due to the Promise on building that server, for Apollo v3 we are set up like this:
export const handler: Handler = async (event, context, callback) => {
    const config = {
        telemetryLogger: new TelemetryConsoleLogger(),
    };
    const graphqlServer = await new BffGraphqlServer().getLambdaServer(config);
    const serverHandler = graphqlServer.createHandler();
    return serverHandler(event, context, callback);
};

In an ideal v4 world using this plugin, I'd love to be able to pass a Promise<ApolloServer> directly into the main function:
export default startServerAndCreateLambdaHandler(new BffGraphqlServer().getLambdaServer(config), handlers.createAPIGatewayProxyEventV2RequestHandler());

Or, that not being an option, have a way to manually create the handler, do my await, then call this server integration's code:
export const handler = async (event, context, callback) => {
    const config = {
        telemetryLogger: new TelemetryConsoleLogger(),
    };
    const graphqlServer = await new BffGraphqlServer().getServer(config);
    // But where to feed in event, context, and callback??
    return startServerAndCreateLambdaHandler(graphqlServer, handlers.createAPIGatewayProxyEventV2RequestHandler());
};

My last-ditch item will be to enable top-level await on Node for the whole project so I could wait for the server to be created, but we're not in a great position to do that with the state of our codebase at the moment.
I'm hoping I'm simply overlooking something in the documentation, but if not, this would be a feature request to support async server creation.
Thanks in advance for the help!

Dug around in the codebase and tried calling the startServerAndCreateLambdaHandler function that's returned, passing in event, context, and callback.
export const handler = async (event, context, callback) => {
    const config = {
        telemetryLogger: new TelemetryConsoleLogger(),
    };
    const graphqlServer = await new BffGraphqlServer().getServer(config);
    return startServerAndCreateLambdaHandler(graphqlServer, handlers.createAPIGatewayProxyEventV2RequestHandler())(event, context, callback);
};

That at least built successfully! I got a ServerStarted event from my telemetry logger, but when I try to load the playground I just get the following error in my browser, with no errors being logged to the console running the local serverless function:
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Cannot read properties of undefined (reading 'method')`

Not sure if that's because I'm using it in a weird way or something else is wrong in my lambda set up (the Docker version we have with this code works great).

Alright, took out the async part of the ApolloServer and did it according to the docs for this repo and still get that error. Means something else is up with my setup. I'll go dig into that!
Regardless, it would be nice to have an example on this tool for what to do when you have an async ApolloServer!


Add features of background color change and different layout options

Microsoft has updated the options in footer panel. when you enable it, you can now select footer to display as standard as well as you can set extended design.
As well as you can set background color. I have attached new footer enable image with this.
Please update this details in this document.

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

ID: 2bfa53a2-c6f9-40f8-fea4-915f98d3eada
Version Independent ID: d4078ea1-a095-a1c4-1c65-fb19ef9d9003
Content: [Overview of the SharePoint Site footer](https://docs.microsoft.com/en-

us/sharepoint/dev/features/site-footer#controlling-footer-using-the-user-interface)

Content Source: docs/features/site-footer.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Care to offer a suggestion on the doc updates by submitting a PR? https://github.com/SharePoint/sp-dev-docs/wiki/How-to-Create-Good-Pull-Requests