Multi node deployment

Hi Team!!
I'm not new to CF. I had already deployed CF and successfully running. but I deployed a single instance of CF on a single cluster node.
My Environment
vSphere vCenter
32 GB RAM
1TB HDD
1 Datacenter (CF-Datacenter) with a cluster (CF-Cluster) and a node in it.
Everything is running on the same node (Bosh and CF are running on same machine)
I need to know that

Is it possible to run them seperately on two machines?
how to deploy CF across multiple nodes in the cluster?
(I tried adding hosts <IP_ADDRESS> & <IP_ADDRESS> to CF-Cluster and deployed but got failed)
how to Deploy CF across multiple Datacenters?(HA)
Is it possible to manage everything from single bosh instance?

I read documents regarding Bosh multi networking deployment, Zone creation and the other docs in CF docs but did not get a clear idea
It would be great if anyone who had already worked on these can help me with example manifests
I look forward to hear from you
Thank You

@cpraveen412
1 It is possible: so long as CF and bosh can communicate, and they both can talk to the vSphere.
2. Can you please provide more information about the failure.  What did it say?  What version of CF release are you using?  Are you using the manifest generation scripts?  Can you upload your deployment manifest? (please remove any sensitive information first).
3. You can't deploy to multiple vSphere data centers with bosh.*  You can, however, deploy to multiple clusters.
4. A single bosh instance is normal.

My understanding is that this may become possible in the future, but I don't have information about the time frame.

Closing due to inactivity. @cpraveen412, feel free to re-open the issue if you have further questions.

Hi @dsabeti ,
Could you please re open this issue?

Hi @jaresty,
Thank you for your response and sorry for this long delay to reply. i have the following questions.

where do we initiate multi zone? is it bosh level or CF deployment level? ( I mean in which yml file we give the zones information?)
I'm using a datacenter called CF-Datacenter with clusters CF-Cluster and CF-Cluster1. If I do availability zone, one cluster acts as a zone and the other cluster acts as another zone. Am I correct?
I want to use two networks (5 and 6 series). Is there any changes to be done to bosh?
I'm attaching the bosh.yml i'm using please suggest me the necessary changes.

https://gist.github.com/cpraveen412/11046a79c32ed55ca23a6a7a4f1248b7
Thank You

@

thank you @dsabeti for reopening my issue. I actually opened a new issue #1147 with updated info. if you can merge these two it would be great!! if not please fell free to close this one.
Thank you

@cpraveen412 No problem. I close the other issue so we can keep the conversation here. Let me know if those docs help you out. They describe setting up vSphere BOSH environments generically, so hopefully you can follow them to use it for CF.

Reposting it from the other issue.
I'm trying to deploy multi zoned CF on vSphere. I've been trying but got failed.
I'm trying to achieve the following:

As shown in the picture, I have a datacenter called CF-Datacenter with two clusters named CF-Cluster & CF-Cluster1.
Each cluster has a server with IPs <IP_ADDRESS> & <IP_ADDRESS> respectively.
In CF-Cluster the network is VM Network(Standard Switch) and CF-Cluster1 has VM Network1(Standard Switch) as the network.
I'm trying to make each cluster as a zone. two zones (z1 & z2). For this, I created bosh.yml in the following way.

https://gist.github.com/cpraveen412/d2e1577182af12f41ac27dca4bbfcd4f

After deploying bosh, I generated cf-deployment using the regular stub from CF docs and scripts expecting that it will deploy to both the clusters.
But it was not as expected. Please suggest me changes in vSphere level and bosh/CF level
Thank You

hi @dsabeti,
I had already followed the docs. but i missed the point the point that, first you should update the bosh cloud-config using cloud-config file and then deploy cf-deployment file.
Here are the two files that i'm using.
cloud-config:  https://gist.github.com/cpraveen412/be82770788ccbec2db3e04a965674ac3
cf-deployment: https://gist.github.com/cpraveen412/20171299cf82e061293536b3694ecda4
All are self signed certificated.
When i do "bosh deploy",
I'm getting the following message
Started preparing deployment > Preparing deployment. Failed: Instance group 'consul_z1' must specify availability zone that matches availability zones of network 'cf1' (00:00:00)
Error 150006: Instance group 'consul_z1' must specify availability zone that matches availability zones of network 'cf1'
Please help me on this.
Thank you

Hi @cpraveen412,
The immediate cause of that failure is that your job doesn't say which of the two AZs it should be deployed to.
The real issue, though, is that you're using a cloud-config, but an old manifest schema. You can see docs for the new schema here. I'd also advise that you take a look at cf-deployment. It's the v2-schema manifest that we're building for deploying CF with a cloud-config. Beware: that manifest is still under construction, and we've never tested it in vSphere. However, you can use it to get an idea for how to configure the AZs for your job: https://github.com/cloudfoundry/cf-deployment/blob/develop/cf-deployment.yml#L10-L14

Thanks @dsabeti. I' working using your inputs. please do not close this ticket. i'll get back with errors. thank you

Hi @dsabeti ,
I'm using sample cf-stub.yml (two networks, cf1:<IP_ADDRESS>/24 and cf2:<IP_ADDRESS>/24 ) to deploy Cloud Foundry to vSphere 6.0.  I have question on how to config these two networks.

Should I build a gateway vm manually for each network?
How to config each gateway's network config? Do I need to set up NAT on each gateway or something else?

Please help me, thanks a lot!

Hey @comxtohr. I'm not a networking expert, but I don't think you're looking for a NAT here. The gateway field in your manifest should contain the IP of the default gateway -- as I understand it, the node that knows how to route traffic to IP addresses in a different subnet.
In our own infrastructure, we use a physical router. It's quite possible that you'd be able to use a virtualized router. I think for this you'll need to ask for help from support at VMWare or someone who has more direct experience creating vSphere setups, as they can tell you what vSphere does or does not support.

Hi @comxtohr. I'm going to close this issue due to inactivity, but feel free to re-open it if you still need help on this front.


Add typewriter effect  in the Heading

Added typewriter effect in the Heading "Welcome to GirlScript Asansol "
Changes :
** Index.html
** One script is added
** Index.js

Hello and welcome! Thank you for contributing. I'm afraid I can't go ahead with your PR, since you were not assigned for this issue in the first place. We're having a lot of contributors and we're assigning issues on first-come-first-serve basis.
Also, always read the contribution guidelines for the respective repository (instructions can generally be found in their README.md) before starting your work on the features and fixes. This is generally how the open-source ecosystem accepts contributions.
Having said that, if you're considering to contribute more code to this repository, I'll recommend you to join the Discord forum and discussing your own ideas with the maintainers after checking out the progress we've made so far. We have a welcoming community and we'd love to have people willing to contribute on board, beginner or otherwise.
Happy coding!


Tell Your Open Source Story - Make a Zine or Documentation

Open source has exciting stories worth telling- how APIs are adopted, how a 2.0 release affects downstream projects and the passion that drives all this.
But it can be difficult to tell these stories. We may not be used to telling our stories, and the intricacies of open source development may be difficult to explain to a more generalist audience.
As shared in my Lightning Talk, my approach is to tell our stories through comics. The "How to Contribute To NumPy" comics  follows riveting story of three grad students as they learn not only how to use NumPy in their research, but also the emotional ups and downs!
Session Notes

At this Unconference session., let's try telling our stories. Bounce off story ideas, sketch, write a script. Pens, paper, and other tactile tools will be provided. Try making your own zine for your open source projects!
Newcomer friendly- no prior drawing or graphic design skills required!
Other topics we can talk about:

How does do stories fit into existing documentation and the Diátaxis framework of documentaiton?
How do we use stories in outreach and education of open source?

The Diátaxis framework, for reference:

Thanks for proposing the topic, @MarsBarLee!
This is scheduled in Garage Hub.
Starts @ 15:40.
Check the schedule here: https://www.nfsummit24.com/schedule.


Update Provider reference methods to use runtime Reference

Description of your changes

This updates the generated provider reference methods to use the
non-pointer Reference type instead of a core.ObjectReference pointer.
Depends on https://github.com/crossplane/crossplane-runtime/pull/182
Signed-off-by: hasheddan<EMAIL_ADDRESS>Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.

@negz @muvaf moved out of draft here, see https://github.com/crossplane/provider-aws/pull/264 for implementation


No entry for Electron 33.0.2

Or 33.0.1, 33.0.0. What triggers a new release to be packaged? Is is on a certain schedule and I just need to wait x days after a new Electron version is released?
https://github.com/electron/electron/releases/tag/v33.0.2

Hey @cseickel, this was a bug in our headers upload - it should now be fixed. Let me know if you have any more trouble!

Don't we need a new release of this library to make this change effective?


Form.dart add mount check before setState

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I was trying to use multi_select_flutter inside of a ViewPage with saving its state. Saving the state was succsessfull but exception occurred.

I added mount check before setState, it fixed the issue.

Expected results
Saving state without exceptions.
Actual results
I added mount check for didChange function it fixed the problem.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Logs
======== Exception caught by scheduler library =====================================================
The following assertion was thrown during a scheduler callback:
setState() called after dispose(): FormFieldState<List<dynamic>>#fe2de(lifecycle state: defunct, not mounted)

This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback.

The preferred solution is to cancel the timer or stop listening to the animation in the dispose() callback. Another solution is to check the "mounted" property of this object before calling setState() to ensure the object is still in the tree.
This error might indicate a memory leak if setState() is being called because another object is retaining a reference to this State object after it has been removed from the tree. To avoid memory leaks, consider breaking the reference to this object during dispose().

When the exception was thrown, this was the stack:
#0      State.setState.<anonymous closure> (package:flutter/src/widgets/framework.dart:1103:9)
#1      State.setState (package:flutter/src/widgets/framework.dart:1138:6)
#2      FormFieldState.didChange (package:flutter/src/widgets/form.dart:479:7)
#3      __MultiSelectDialogFieldViewState.didUpdateWidget.<anonymous closure> (package:multi_select_flutter/dialog/multi_select_dialog_field.dart:314:23)
#4      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1284:15)
#5      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1223:9)
#6      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:1072:5)
#7      _invoke (dart:ui/hooks.dart:142:13)
#8      PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:359:5)
#9      _drawFrame (dart:ui/hooks.dart:112:31)
====================================================================================================

Flutter Doctor output
Doctor output
[Paste your output here]

Thanks for the report @Snorkin
Can you provide minimal runnable code sample along with flutter doctor -v ?


add support for delegation token

I'm not clear why the CI failed, but my local build(mvn clean install) after rebasing to the latest master succeed.

Was this merged? We need this for multi-tier scenarios. Using delegation token is the way how we pass user's identity to presto through the trusted intermediaries.

No.  We will need to work out another, more generic, mechanism.

Got it. Are you going to define strong typed JSON object for the delegation token? Let's discuss about it once we meet. Thanks!


Group by file

Hi, I am using this plugin for the dev documentation of this repo: https://github.com/euberdeveloper/byteify
As you can see here (https://byteify-dev.euber.dev), all the "Not Exported" are visible in the root. The purpose of the dev documentation is to show, file by ile, what is contained to maintainers. Hence, I would like all these not exported to be documented inside the files and not in the root of the menu. Is it possible?

Yes this should be the default xd


Fill in conventional labels from existing project metadata

Closes https://github.com/dotnet/sdk-container-builds/issues/96
This fills in the metada in #96 using project properties. There are conditionals for the entire generation as well as each specific item. The properties are patterned after the NuGet pack targets mappings.
The only caveat is that the source control urls aren't flowed through unless the PublishRepositoryUrl property is set to true, following guidance from the sourcelink repo.

[x] add tests for coverage of the new items
[x] add to existing documentation section on container customization

I just added tests for the on/off toggles of the new labels - this is the most important part to me, the rest is very mechanical. But the opt-out has to work, and the repo privacy flag has to work.

I just added tests for the on/off toggles of the new labels - this is the most important part to me, the rest is very mechanical. But the opt-out has to work, and the repo privacy flag has to work.

Let me know if you'd like to have tests on other properties.


[test] New affinity check

This new affinity check reads the node configuration from a reference file which contains the output of lscpu -e. This builds the cpu sets for each NUMA region, socket, etc; so all the reframe tests are now independent from the system. However, since slurm settings could potentially affect a given system, each test has the flexibility to prescribe system specific options too.
Now, to add a new system, one only needs to add one reference file per system and extend the self.valid_systems.

I just read the description of the PR. Wouldn't lscpu -J help, which spits everything in JSON?

You can even combine lscpu -e -J

Hello @jjotero, Thank you for updating!

In the file cscs-checks/prgenv/affinity_check.py:

Line 94:80: E501 line too long (90 > 79 characters)
Line 102:80: E501 line too long (92 > 79 characters)
Line 126:16: E713 test for membership should be 'not in'

Do see the ReFrame Coding Style Guide

I just read the description of the PR. Wouldn't lscpu -J help, which spits everything in JSON?

Sure, I just didn't have a preference for that. I just updated it to use JSON files.

Sure, I just didn't have a preference for that. I just updated it to use JSON files.

I proposed JSON because it's much easier to parse within Python. I will have a look in the test later on.

How urgent is that we merge this? Because it can be really simplified after we merge #1773. The idea is that we put all this information in the configuration and make it available under current_partition. So I suggest commenting in #1773 what is the information that we need there.

I don't see how adding all this information from the config file would simplify this test. If so, I believe it would make the process of porting this test to a new partition a lot more complex, given that you manually have to add all the data into the config file; whereas now you just dump the JSON file and off you go.
My idea with this test was that once we start supporting fixtures, the whole process of fetching the partition topology can be made a fixture that any test could use if needed. That way you remove the need to hardcode any settings anywhere.

Check also this #1742. The idea is that we want to generate the configuration automatically. So all this topology discovery machinery could be part of the "auto-configuration". Other tests might want to know at least some high level information in order to configure themeselves. Why should they have to re-write that. Of course, this could be offered separately in a fixture library, but that's something we need to see.

@vkarak I see. I personally tend to vote against those "auto" features, because then it won't work for some users, and then they complain 😂.
Regarding the urgency of this PR, it is part of the Eiger tests, so I guess we should merge it at some point. We could also push it with a  FIXME in there and then we use this test as the "guinea pig" for all that stuff and see which way looks better.
@jgphpc The the fixture idea would transform that into something like
@rfm.fixture
class NodeTopology:
   ...

# and then in the test
@rfm.simple_test
class MyAffinityTest(rfm.RegressionTest):
    topology = fixture(NodeTopology, scope='partition')

    def __init__(self):
...

or something like that.

I personally tend to vote against those "auto" features, because then it won't work for some users, and then they complain 😂.

I understand this and that's why ReFrame didn't have such automations until now. The requested feature is more on auto-detecting the local node, which you can do in a way more controlled way. On the other hand, since the detection happens locally, fixtures could do the job nicely and I would vote for a cpuinfo fixture that would give you also the archspec information apart from the topology. Fixtures can also be made smart enough to run also on remote partitions. Regarding the syntax, that could be a potential one, but I am also thinking something more pytest-like. But we will discuss this.

Regarding the urgency of this PR, it is part of the Eiger tests, so I guess we should merge it at some point. We could also push it with a FIXME in there and then we use this test as the "guinea pig" for all that stuff and see which way looks better.

I'm fine with a FIXME note for the moment.

1 last minute comment about AlternateSocketFilling/ConsecutiveSocketFilling
On AMD, you have 2 sockets, with 4 numa nodes per socket.
The name could be AlternateNuma/ConsecutiveNuma

@jgphpc Good catch! In fact, the number of AlternateSocketFilling is just wrong. I've been playing with the slurm settings and it seems that there is no easy way to force an actual alternate socket filling in here.
I'll fix that sanity function and rename the tests.

I've now re-run all these tests and they all pass. As I mentioned above, it's not straightforward to me how to actually do an alternate socket filling. This could be quite important for systems that might have (say) 2 devices, and each device with affinity to different sockets. I'll keep experimenting in ault about this, but as far as this PR is concerned, I think it can be merged.

@jenkins-cscs retry eiger

@jenkins-cscs retry all


Is the duration of each audio clip in AudioCaps 10 seconds?

Hi, I want to download the audio data of AudioCaps, and writting to notarize the duration of audio clips. In the csv files, just beginning time is provided.  Is the duration of each audio clip in AudioCaps 10 seconds?

Hi,
That is correct. As AudioCaps is a subset of Audioset, the duration of the audio is the same as stated here.
Best,


Recreate Container w/ Latest Image

I'm not quite sure if this is possible with the API, but it's worth a shot.
Would it be possible for you to add an option that only recreates a single container, not the whole stack?

This option is located in the actions pane for a container.
It can sometimes be better to just redeploy a single container rather than the whole stack.

Doesn't seem like it can be done with the API. It's a shame, since it doesn't download the latest tag of the image from the registry, meaning that any containers in the stack will still use the same version of the image that they were before.

Last time I checked, it worked fine to get the latest image by checking the option Pull latest image in Portainer. But it's not working for you?

?


Fix result print for SamplingVQE & QAOA - fixes #58

Summary
Fixes #58.
Simply removes the overriden __str__ method in the sampling result class so conversion to string is done by the parent AlgorithmResult (as it done for all other results so it makes things consistent too).
Longer terms the change proposed in #53 will change things up by using dataclass so the result string format is wanted to be improved, maybe include a capability for just including the common fields or whatever things can be revisited at that point.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 90.038%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
6444

Relevant Lines:
7157

💛  - Coveralls


chore(state): rearrange state

What this PR does 📖

literally just moves functions in State to different impl blocks.
one impl block for Action, one for warp events, one for loading and mock stuff, and the rest correspond to items in the state struct.
for most of the impl blocks, a few important functions appear first and the rest are alphabetized
hopefully this makes it easier to find stuff in State. additionally, we can add doc comments so that RustDoc can auto generate documentation. This may be helpful for future maintainers.

Which issue(s) this PR fixes 🔨

Resolve #

Special notes for reviewers 🗒
Additional comments 🎤

not sure this one even needs testing


Wow! How are you using this package so far?

Actually started using this package as a base in April 2018, but ended up extracting out your SRC files, using the models as a base reference, and building back up from scratch. We needed to be able to message between any models we choose, so switched to using morphs on everything. Ended up building so much on top, I am starting to extract it out into a standalone package I too would like to release as an entire suite! But your base helped us get the jump start we needed, so thanks! I added support for group invite links like discord, video calling/group calling, bobble heads (read indicators), images, documents, links, youtube support. Privacy and friends list are also integrated


Delete ... if ...

Hi,
Is it curently possible to execute in phantom dsl such type of query:
delete from someTable where id = 89dfbe10-0f45-11e5-99a4-d43d7ebcc606 if someSet= {}; ? :) (cassandra allows for such query even without index on set column).

Hi @mmatloka,
That's not by accident. The compare and set clause must be matched against a non-primary column, so I think that behaviour is correct according to Cassandra spec. You match with the where clause and you can actually never have an is on a column that's indexed.
I don't think DELETE .. IF is yet part of the mix and I'm not 100% sure Cassandra even supports this, we will have to double check.
Regards.

Hi @mmatloka,
There is indeed a DELETE IF in Cassandra, something we missed in the original implementation of Lightweight and compare and set. Regardless, it will be added to the pipeline.
Regards.

Hi @alexflav23 ,
Sorry, I have made a mistake in description, I meant from the beggining that Cassandra allows for that, but I have written 'Phantom' instead ;/.

Regardless, it will be added to the pipeline.

:+1:

@mmatloka This is now fixed in 1.9.7.


fall back to controller-runtime defaulting for the apiserver

What this PR does / why we need it:
For the mock controlplane, the defaulting was copy/pasted over from controller-runtime (I assume in some earlier state). As of https://github.com/kubernetes-sigs/controller-runtime/pull/1541/files, their defaulting got revamped, and thus we can fall back to their defaulting. Only for advanced users, we can allow to override this, but should overhaul this config in the future as well, as the property used to override is deprecated.

Fixes #

looks like a number of PRs coming working on the same area of code... I will review this today.  thanks @redradrat !

I was just recently upgrading testenv libs and was debating on this... I was debating on if we should detect version and configure based on that providing tests for different versions of APIs...  It seems reasonable to move on, establish ourselves on the latest and handle any issues if they come up... it is unlikely  and the only reason I can think of to support older versions is for v1beta1 support of CRDs... but that was so long ago now.   Thanks for this PR.   I will merge this and adjust my current code accordingly.   Agree with the the overhaul on config at some point.   Thanks so much!

@kensipe tbh I don't know the reason either... I wrote this so brain-fried after long hours, I even forgot sending it 😅 sorry


dist/index.js

lines 724-725 values and keys are swapped

getCurrentAuthState()

getCurrentAuthState()

Can you please tell me what's happening, in detail. If you can give me an example, please share

Can you please tell me what's happening, in detail. If you can give me an example, please share

getCurrentAuthState().authToken returns 'Bearer' and getCurrentAuthState().authTokenType returns the token.

getCurrentAuthState().authToken returns 'Bearer' and getCurrentAuthState().authTokenType returns the token.

Thanks for the details. Fixing it soon

Thanks for the details. Fixing it soon

Fixed in 8fc03f5. use V1.4.4 or later

Fixed in 8fc03f5. use V1.4.4 or later


support for annotation based secret generation

we found when making charts that often they require secrets to be imported or created and sometimes secrets are shared between charts.
e.g. when using Gerrit, Jenkins and SonarQube we need to share public keys to Gerrit for things like Jenkins and SonarQube which have their own generated/imported public/private keys. Or to install our full CI / CD system so it can do real releases to github, maven central and docker hub we need to import our real SSH & GPG keys.
So we came up with a simple set of annotations we could put onto our charts:
https://github.com/fabric8io/fabric8/blob/master/docs/secretAnnotations.md
which a tool can then process to import (if they are on disk) or generate Secrets if they don't exist as charts are installed. Then users can install/setup the secrets however they like before you install things; otherwise the install just works and worst case you get auto-generated secrets in each environment.
Up to now we've been using the gofabric8 secrets command to do this. e.g. here's the code...
https://github.com/fabric8io/gofabric8/blob/master/cmds/secrets.go#L84
we basically iterate through all installed OpenShift Templates and then create or import from the file system any secrets for the annotations.
It would be pretty simple to do the same thing inside helm; that just before the chart is uploaded we iterate through all the resources in a chart (Replication Controllers really to look at the PodTemplates) and look for these annotations and if so lazily create any secrets.
Before I submit a PR I just wanted to check if you were happy with this general approach.
We could leave the secret generation as a separate CLI step in helm; then we could add a 'pre install command' into the charts to install gofabric8 if its not already and then just run gofabric8 secrets on the charts before they are uploaded.
Though secret generation sounds like its going to be so common for any vaguely secure chart - and the code is so simple; it does feel like we should just add native support for secret generation/import at chart installation/update time?

If you take a look at plugins/sec, we were just starting down the road of making it easy to generate secrets (as a separate step).
I really like the idea of using annotations to indicate that a secret needs to be generated. It means we don't even have to parse the full RC/Pod to figure out what we need to generate.
We've gone back and forth about hooks like pre/post install, and for the time being we decided to hold back. I would really like to see a separate issue on that so that we can all discuss. We're learning a lot about how Helm uses are trying to use Helm. I think that'd be a great place to get some feedback.
In summary, my view is:

+1 on the annotations approach.
+1 on a command for adding secrets. We should figure out how best to do this.
And we should discuss pre-install hooks on an issue

Would also like to hear from @gabrtv

@technosophos assuming we went down the road of detecting annotations at installation time, do you think we should use helm install command line arguments to enable/disable secret generation?
I'd personally prefer the default OOTB command to Just Work (tm), though I guess the default could be to not create any secrets if it finds a missing secret and output something to the user. e.g.
$ helm update
$ helm repo add fabric8 https://github.com/fabric8/charts.git
$ helm install fabric8/cd-pipeline

Helm cannot install cd-pipline as the following secrets are missing

    jenkins-ssh
    jenkins-gpg
    sonarqube-ssh

Please specify the --create-secrets option to automatically create secrets.
This command will look in the current directory for secrets to import or use --secrets-dir to specify another folder

I do like that idea. It feels right to me that we handle secrets in install.

I've closed the previous PR and raised a new leaner meaner rebased & cherry picked PR: https://github.com/helm/helm/pull/326


const vs con

You use var for variables but const this is not intuitive. You should use con instead. Except if con means console. then cns is another good alternative.

The use of "const" is already abbreviating the word "constant", it doesn't need to be abbreviated again.


Feature generic return obj like sap.base.Object

todo:

[ ] investigate serialization of object properties that reference parent properties by ref in client-side-js/executeControlMethod.js, client-side-js/injectUI5.js
[ ] fluent api support for wdi5-object.ts

https://github.com/ehmicky/safe-json-value

closing due to successor https://github.com/ui5-community/wdi5/pull/366


:scope and global states

Currently the :scope of a block can not be modified by a global state of another block.
For example, the rule
app[state|no-touch] :scope:hover { ... }

throws a validation error.
Is this intentional because of the design? I think it would be a very useful feature.

This is solved here


Better info logs

When we start boostrapping -- say "starting bootstrapping"
When we connect to gossip net -- say "connected to gossip net"

Closing, because #2880.


Update naming conventions in tools/rapids-extract-conda-files

Part of issues: https://github.com/rapidsai/build-planning/issues/98
Follow up to PR: https://github.com/rapidsai/gha-tools/pull/122
In tools/rapids-extract-conda-files, rename variables to clarify they refer to Conda packages in either form (.tar.bz2 or .conda). Also update comments similarly. This follows up to work that added .conda support in this script

Thanks James! 🙏


Moved create engine code to inside @before_request

Since #86 doesn't seem to be fixing the issue, let's try this instead?
The live branch is currently on this branch to see if it works...

Seems like this is fixing the issue? We haven't gotten any exceptions about it in some time. I'll see if anything else happens in the next few days.

Seems like this is fixing things for now. We'll take another look at this later.


Refactor resultpage to use ID´s not the index of the post

Describe the bug
Currently the resultpage uses the index of a post to reference it (e.g. to open it, use it on card, etc.)
https://github.com/hochschule-darmstadt/einander-helfen/blob/staging/app/src/views/ResultPage.vue#L131-L133
This makes it hard to link to it, since we are working with an everchanging dataset.
Expected behavior
It is possible to link to an post consistently.

Fixed with https://github.com/hochschule-darmstadt/einander-helfen/commit/67297695b8cdda0e3d843bd80f483a53bf084114


copy_file_range() doesn't work on all filesystems

It seems like the copy_file_range syscall isn't guaranteed to work on all filesystems when copying to another filesystem, so toybox cp is basically broken:
openat(AT_FDCWD, "/usr/bin/gcc", O_RDONLY) = 3
openat(AT_FDCWD, "/tmp/gcc", O_RDWR|O_CREAT|O_TRUNC, 0100755) = 4
copy_file_range(3, NULL, 4, NULL,<PHONE_NUMBER>, 0) = -1 EXDEV (Invalid cross-device link)

btrfs -> broken
ext4 -> broken
zfs -> works
nfs, fuse, cifs, ceph -> should work
... -> ...
The man-page doesn't cover this limitation, it only mentions it being supported after Linux 5.3, EXDEV  The files referred to by fd_in and fd_out are not on the mounted filesystem (pre Linux 5.3).
https://github.com/landley/toybox/blob/62f89088fdb1c63301b15ec3502fdf70990d17cd/lib/portability.c#L650
diff --git a/lib/portability.c b/lib/portability.c
index 7be909e..fa2ebe4 100644
--- a/lib/portability.c
+++ b/lib/portability.c
@@ -647,7 +647,13 @@ long long sendfile_len(int in, int out, long long bytes, long long *consumed)
       // Android's had the constant for years, but you'll get SIGSYS if you use
       // this system call before Android U (2023's release).
 #if defined(__NR_copy_file_range) && !defined(__ANDROID__)
-      len = syscall(__NR_copy_file_range, in, 0, out, 0, len, 0);
+      long long maybe_len = syscall(__NR_copy_file_range, in, 0, out, 0, len, 0);
+
+      if (maybe_len == -1 && errno == EXDEV) {
+          len = syscall(__NR_sendfile, out, in, NULL, len);
+      } else {
+          len = maybe_len;
+      }
 #else
       errno = EINVAL;
       len = -1;

Commit 63f787b602f7 added a check for ENOSYS and now you're saying it can return EXDEV as well?
Sounds like the errno check is probably wrong and any failure should trigger the fallback path.

Try commit ff3f93a3bae6

i believe that commit has fixed it.


Questions about additional features

Details
We are currently developing v5.1.0 with reference to LuanRT/YouTube.js and yt-dlp.
The following features will be added and supported accordingly. Details are available from “Projects”.
Features

Support tv_embedded clients to avoid age-restricted videos (and eliminate bot errors)
Support alternative authentication methods to PoToken using OAuth2

Improvements

Function and data type improvements
Performance Improvements

Organize

Organize basic files
Organize API documentation (including examples)

Create

Create detailed implementation examples (Add 2024/08/22 18:30)
Creating Error Documents (Add 2024/08/22 18:30)

We would like to get your opinion on anything other than the above. Please send us your comments.

We are now closing this issue as we are getting ready to release v5.1.0.


Add version detection for TiKV

By default we should disable filter push-down until we might confirm what expression is supported by TiKV. Otherwise we run the risk bring down tikv node completely.
TiKV might add version detection interface, we might choose to query this interface to decide what expression to push down.

Done


[release-0.25] Upgrade to latest dependencies

bumping knative.dev/pkg webhook changes -dprotaso
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg 21eb4c1...844a6bc:
  > 844a6bc [release-0.25] allow unknown metadata fields (# 2254)
  > 5bed044 Drop redundant pointers and decoders (# 2259)

/lgtm
/approve


[#105] Added Documentation to DBSCAN clustering.

Added documentation to DBSCAN
Added documentation to related word fetcher
Moved files around to conform to existing directory structure.

[#105]

we both moved stuff around in our PR for directory structure...

yes i accommodated master

I'll merge and fix conflicts on your branch


Add contextual menu to blueprint tree for common actions

To make it easier to add blueprint content in the UI, we should introduce context menu on right click in the blueprint with options:
Container is clicked
Single selection

Add View
Add Container
Put in new container
Hide
Remove

Multiple selections

Put in new container
Hide
Remove

View is selected
Single selection

Add Entity
Put in new a container
Hide
Remove

Multiple selections

Put in new a container
Hide
Remove

Views and containers selected
(same if all entities of a selected view are selected)

Put in new container
Hide
Remove

Entity is selected
(Same for single or multiple entities)

Add to new view
Hide
Remove

Entities and views and/or containers selected

Hide
Remove

Closing this one in favour of finer grained issues with the remaining items.


[BEAM-9577] Remove uses of legacy artifact service in Java.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @lukecwik

FYI, the first commit is https://github.com/apache/beam/pull/11932

@ihji would you be able to take a look at this? Again, almost entirely deletions.

Taking a look now. Sorry for the wait.


GitHub OAuth Login

Description
Adds login capability for GitHub integration through the OAuth workflow.
I had to install 'react-simple-keyboard' in order for the project to be able to run after pulling from the latest changes. This is the cause of the huge increase in lines.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test

Open the .env file and set REACT_APP_GITHUB_CLIENT_ID=d376715d50d04bd54a7e
Deploy the project.
Open the GitHub control buttons menu on the playground and press 'Log In'. Approve the app in the pop-up.
After the login has succeeded, the 'Log In' option will be replaced with a 'Log Out' option. The other options will also become available, but their functionality has not been implemented.
Click on the 'Log Out' option. The other options should now be greyed out while 'Log Out' is replaced by 'Log In' again.

Checklist

[X] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 644905948

44 of 97 (45.36%)  changed or added relevant lines in 18 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.1%) to 28.894%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/application/Application.tsx
0
1
0.0%

src/features/playground/PlaygroundActions.ts
1
2
50.0%

src/features/playground/PlaygroundReducer.ts
0
1
0.0%

src/pages/githubCallback/tests/snapshots/GitHubCallback.tsx.snap
0
1
0.0%

src/commons/application/reducers/SessionsReducer.ts
0
2
0.0%

src/features/github/GitHubUtils.ts
6
10
60.0%

src/pages/playground/Playground.tsx
0
5
0.0%

src/commons/controlBar/ControlBarGitHubButtons.tsx
2
11
18.18%

src/commons/sagas/GitHubPersistenceSaga.ts
6
15
40.0%

src/pages/githubCallback/GitHubCallback.tsx
6
26
23.08%

Files with Coverage Reduction
New Missed Lines
%

src/pages/playground/Playground.tsx
1
2.24%

Totals

Change from base Build 642420612:
0.1%

Covered Lines:
2263

Relevant Lines:
7213

💛  - Coveralls

I had to introduce a new dependency for the React Testing Library in d4ea2a5 because of the way tests interact with async code in UseEffect. After a lot of Googling, it seemed like the only way to make the test wait for all the async calls to be resolved before checking for correctness.


can I use nodejs part to connect to facebook?

any example?

we're going to have an example of that coming shortly (within a week or two)

@vinnitu Here is an FB bot connector https://www.npmjs.com/package/botbuilder-facebook

Closing this issue. Thanks!


Feature: Disable stoping of addon after finding vulnerability

Fixes #19

Added UI (checkbox) to allow users to choose to keep the uploading files after a vulnerability is found
Added logic to set/get this flag in configurations and in other places
Modified condition inside FileUploadAttackExecutor to consider this flag

@TomerPacific please add logic in Attackvector class and logic should be like:
if (attackVector.execute(this)) {
     if(!shouldSendRequestsAfterFindingVulnerability) {
            return true;
     }
}

or

if (attackVector.execute(this) && !shouldSendRequestsAfterFindingVulnerability) {
                    return true;
}

@TomerPacific I think you removed the logic related to using the flag shouldSendRequestsAfterFindingVulnerability. please add that. The place where you added the logic is correct.
thanks,
Karan

@preetkaran20 - Yes, I removed the logic per your recommendations. I'll add the logic back.

@preetkaran20 - Please review again.

I think UI can be changed a little bit like below:

i.e. changing label and checkbox order.
can we rename label of checkbox to something like Keep exploiting after discovery. or Keep exploiting vulnerabilities after discovery or Keep exploiting after discovering vulnerabilities etc. thoughts?
`

@preetkaran20 - I'll change the UI according to your recommendation.

@TomerPacific changes looks good to me. Just one thing, please align the UI flag to left and make label first and then the checkbox as shown in the below image:

@preetkaran20 - Still working on the changes, am not finished. Will let you know when I am done.

@preetkaran20 - I have been trying to left align the JLabel using different methods, but to no avail.
Since it is inside the JPanel, I have tried using setAlignmentX and SwingConstants.LEFT, but nothing works.
Any idea?

@preetkaran20 - I think I managed to produce the UI changes you requested.

Let me know if anything else is necessary.


Accept and report both xy and RGB color for lights

Description:
This PR adds light component support for translating between RGB and XY colors for the turn_on service. If the service is called with an RGB color but the entity only supports XY or vice versa the color parameters will be translated.
The use-case I have in mind is that I've been digging into the ZHA platform, and it natively prefers to work with XY colors instead of RGB. I think it's best if we just let the light component do the translation, so that platforms don't need to worry about supporting both, and can implement their preferred method. Doing the conversion in one place should also help give consistent behavior on how brightness is handled for XY.

That's what I was thinking, but preprocess_turn_on_alternatives runs once for the service call, and isn't aware of the entities capabilities.
Another alternative would be to always transform color requests to XY in preprocess_turn_on_alternatives before sending them to the platforms. RGB only platforms would still have to convert incoming requests, but at least then platforms wouldn't have to worry about supporting multiple color request types.

The best would be, that home-assistant support only one color schema and all other need be converted. That what we have currently is bad by design. Anyway, I think we should convert it in any case like the others does.

👍 I think in an ideal world we'd only support XY color, since RGB has the confusing overlap with brightness. Unfortunately I don't think we can get away from RGB in the API since it's so ubiquitously understood, but we can at least limit the complexity of what is sent to platforms.

I will just remind that you advised against doing this in my old PR https://github.com/home-assistant/home-assistant/pull/6727#issuecomment-294480441
I am not saying that this should exclude you from doing the change now, it is certainly acceptable to change your mind. However, I wonder whether your new use-case is perhaps blinding you from seeing the larger picture that you identified in my PR.

😆 Thanks for bringing that up! Those notes are some good context.
I think I've come to a better solution here thanks to this feedback, that hopefully keeps complexity limited.

Those last commits sure look like a cleanup rather than adding complexity 👍
AFAIK, the xy<->RGB conversions are actually wrong for most lights. This is because xy is calibrated and our converters use the color properties (like gamut) of a certain Hue model. With these last changes I think it will be hard for individual platforms to do their own conversions. I am not sure how much of an issue this is but thought it should at least be mentioned.
Many people (me included) hope for an HSV model in HA as well because it is the best way to make smooth color cycles. That would fit in nicely with this PR, I think?

Good to know about those XY conversions. It seems like consolidating the conversions for now is still a good idea, and we could address device-specific conversions later when we will actually implement it. Open to hear other thoughts though.
Definitely agree on the HSV. Now that platforms are agnostic of the color system used at the API level, it's a pretty easy addition. Will be immediately helpful for the frontend as well since we're already doing the HSV conversions for the color picker.

What's the status of this PR?

I think this is mostly just stalled waiting for consensus. It's pretty rough to keep up-to-date since it hits most of the light platforms.
I think we've agreed to switch out internal hue/sat scaling to 0-360 / 0-100. (which can be a separate PR)
After that, if we're in agreement on this approach I can push this through the last mile.

It's actually the external hue/sat that I care most about, i.e. how end users have to interact.

@amelchio wouldn't that be a frontend issue?

I count service calls as user interfaces.

Ah yeah, good point. I mostly just meant we should re-scale our internal conversion functions first, so that when it's exposed to the API we won't need any additional scaling.

OK, I think this is finally ready to go. There's almost certainly going to be some bugs in some of these platforms since I can't test them all, but I've run through the hue and ZHA platforms and things are working as expected.
I think our best bet is to get this merged, and do our best to recruit people to test on dev, (and maybe our new RC).

Great. I will try to do a review this weekend.

If we merge it by the end of the weekend, we should be able to get 1 week of testing in dev and 1 week of testing in RC. Should be enough.

MySensors looks good. :+1:

I agree with @armills . The concerns by @amelchio are good but let's fix those in another PR. As is we're having a good foundation to build upon.

Is this the reason MQTT RGB broke up?
https://community.home-assistant.io/t/0-66-rgb-mqtt/48871
@balloob can you help identify the root cause?

I think this might be related to my issue with tradfri bulbs paired with hue hub? #13614

Since change 89c7c80 (on Mar 18) to the tplink.py, my TP-Link lights stopped supporting color. Color used to work in HA (on the UI or by setting color using commands) before that change, and the lights support color when using the Kasa app.
Since the change (89c7c80), changing lights only adjusts the brightness. Light selector appears in the HA UI, but it only affects brightness. Same for SLI commands (API calls / automations / Node-red). Color still works in the Kasa app.
I'm new to this, so I don't know what other info I could provide to troubleshoot this.

@Arkadyf No more information is needed but please create a separate GitHub issue. You can add a note that the problem probably is due to us no longer casting hsv to integers.


Create a new Child issue.

When creating a sub page an error occured
recreate the bug.

Create a sub page (via the arrow).
Delete the sub page.
Add a sub page again.

This error has to do with the fact that treebeard still has a numchild on the parentpage. Therefor the parentpage is not a leaf so it will create the page as an extra child but it really is the first child.

@JostCrow which CMS version are you using?

I started with 3.1.2 and upgraded to 3.1.3 after the bug appeared
On Mon, 12 Oct 2015 19:29 Iacopo Spalletti<EMAIL_ADDRESS>wrote:

@JostCrow https://github.com/JostCrow which CMS version are you using?
—
Reply to this email directly or view it on GitHub
https://github.com/divio/django-cms/issues/4576#issuecomment-147468893.

--
Jorik Kraaikamp

So you're still experiencing this in 3.1.3?

Yes
On Mon, 12 Oct 2015 22:10 Iacopo Spalletti<EMAIL_ADDRESS>wrote:

So you're still experiencing this in 3.1.3?
—
Reply to this email directly or view it on GitHub
https://github.com/divio/django-cms/issues/4576#issuecomment-147506262.

--
Jorik Kraaikamp

While this was an issue in 3.1.2, I cannot reproduce on a  clean 3.1.3 / Django 1.7 project

@JostCrow would you try https://github.com/yakky/django-cms/tree/feature/treebeard?

@JostCrow tentative fix at #4717

Closed by #4717


Use of multiple color

Hello,
Thanks for sharing this. We found your code very useful. Is it possible to have a different color other than purple for hair? Where can I find the exact piece of code for the same?
Regards,
Vidhi

Hi @vidhishah22,
Thanks for your question
You can change color in  function transfer here. You fix the values in the mask array to get the color you want


Build failure on Windows msys2 mingw64

Hello,
I've installed MSYS2, updated the system, installed cmake and mingw-w64-x86_64-toolchain.
I cloned the CppUTest repo, launched MSYS2 MINGW64 prompt, and inside the /cpputest_build I issued the following commands:
cmake ..
make

The first one ran to completion, but the second one has successfully built cpputest and cpputestext libraries, but the tests did not link:
[ 72%] Linking CXX executable CppUTestTests
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/CppUTestTests.dir/AllTests.cpp.obj:AllTests.cpp:(.xdata.startup+0x14): undefined reference to `__gxx_personality_seh0'

And a ton more of similar undefined references.

The same happens with CppUTest release 3.8 (downloaded as zip).

During the configuration step with cmake .., I've got warnings:
System is unknown to cmake, create:
Platform/MINGW64_NT-10.0-19043 to use this system, please post your config file on discourse.cmake.org so it can be added to cmake

I apologize, I've installed make and cmake from msys2 repository, while I needed to install both from mingw64 repository to use them with mingw-w64-x86_64-toolchain.
With correct versions of all utilities, everything works!


Link to github is missing

https://www.npmjs.com/package/ep_special_characters
please add the link to the repository on github - thanks

Please send this through as a PR :)  Thanks!


[SPARK-17920][followup] simplify the schema file creation in test

What changes were proposed in this pull request?
a followup of https://github.com/apache/spark/pull/19779 , to simplify the file creation.
How was this patch tested?
test only change

cc @vinodkc  @gatorsmile

Test build #84127 has started for PR 19799 at commit 71aeee5.

LGTM

Test build #84127 has finished for PR 19799 at commit 71aeee5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84127/
Test PASSed.

thanks, merging to master!


Support for LaTeX?

Just thought it'd be nice for our scientists

The general issue here is embedding non-Gemtext syntax into a Gemtext file, and that is largely inadvisable due to compatibility issues. One should be able to view the document with any client, even those that don't support LaTeX.
One way would be to detect "application/x-latex" MIME type and render it as an image, so that those could then appear as inline images on the page. This is at least in theory doable with Lagrange's MIME hooks feature, but requires one to have a fully functional LaTeX system already installed. Such images are best pre-generated on serverside so the client doesn't have to worry about it.
My personal recommendation is to use Unicode math symbols and box drawing characters in a preformatted block, like so:
   n!      ╭ n ╮
──────── = │   │   for 0 ≤ k ≤ n
k!(n-k)!   ╰ k ╯

However, creating these would likely require manual work as there isn't a trivial 1:1 conversion from a LaTeX equation into the corresponding Unicode representation. One has to take some artistic license to achieve the desired result... The benefit here is that any Gemini client can be expected to show the equation just fine without any special processing required.

I thought OP was asking about using it as its own document type, instead of embedded.

I thought OP was asking about using it as its own document type, instead of embedded.

@bleonard252 There is no fundamental technical difference when it comes to implementing that. The MIME hooks approach would work for entire documents as well. However, I don't really see a point in adding support for viewing new document formats as a built-in feature... Much better to rely on external full-featured viewers (#135).


Add the ability to open doors

Add the ability to open doors, drawers, etc.

Yeah that'd be a cool idea!!! Thanks for the suggestion!

I think create model door have animation rotation open (can use blender). Then add this model to sence When character move to near the door show pop up to trigger function open


[SPARK-33160][SQL][FOLLOWUP] Replace the parquet metadata key org.apache.spark.int96NoRebase by org.apache.spark.legacyINT96

What changes were proposed in this pull request?

Replace the metadata key org.apache.spark.int96NoRebase by org.apache.spark.legacyINT96.
Change the condition when new key should be saved to parquet metadata: it should be saved when the SQL config spark.sql.legacy.parquet.int96RebaseModeInWrite is set to LEGACY.
Change handling the metadata key in read:

If there is no the key in parquet metadata, take the rebase mode from the SQL config: spark.sql.legacy.parquet.int96RebaseModeInRead
If parquet files were saved by Spark < 3.1.0, use the LEGACY rebasing mode for INT96 type.
For files written by Spark >= 3.1.0, if the org.apache.spark.legacyINT96 presents in metadata, perform rebasing otherwise don't.

Why are the changes needed?

To not increase parquet size by default when spark.sql.legacy.parquet.int96RebaseModeInWrite is EXCEPTION after https://github.com/apache/spark/pull/30121.
To have the implementation similar to org.apache.spark.legacyDateTime
To minimise impact on other subsystems that are based on file sizes like gathering statistics.

Does this PR introduce any user-facing change?
No
How was this patch tested?
Modified test in ParquetIOSuite

@HyukjinKwon @cloud-fan @tomvanbussel @ala Please, review this PR.

Test build #130157 has started for PR 30132 at commit be62b9c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34764/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34764/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34764/
Test PASSed.

Test build #130161 has started for PR 30132 at commit 158ab4f.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34768/

Test build #130157 has finished for PR 30132 at commit be62b9c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130157/
Test FAILed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34768/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34768/
Test PASSed.

thanks, merging to master!

Test build #130161 has finished for PR 30132 at commit 158ab4f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130161/
Test PASSed.


Remove caliban from zio-parser core deps

It is only added accidentally

I don't think this is applicable at the moment. Only zio-caliban-parser depends on Caliban.


[REQUEST, SUGGESTION] BERT with TF 2.0

Do you have any plans to release BERT model with Tensorflow 2.0?
It makes much easier for NLP people to understand how Tensorflow 2.0 works for BERT.
Thanks,

bump

I have tried to port modeling.py to tf2 and it worked perfectly on my own task.

https://github.com/u10000129/bert_tf2/tree/master

Please take a look!

Also releasing a TF2 compatible version of the pre-trained models to tf-hub. Tried several things to get it to work, but no dice.

I have also coded a tf2 keras version recently - kpe/bert-for-tf2 (check this comment to #584 for additional info).

Does some of TF 2.0 features would allow BERT to improve state of the art results?

TensorFlow 2.0 implementation for BERT is available at https://github.com/tensorflow/models


Looking for a simple few things

Hi
I'm a newbe in Python and i have lot things to learn.
I'm trying to move a trolley on rail.
When i start, i need to drive the trolley to the "Zero Position" and set this position to 0.
I don't know how to set current position to zero.
I also want to change the speed of my trolley or better, set a time to go reach the target position.
i hope someone will help me.
Thank you

You should probably start with a much more basic driver than this one.
try a google search like

simple python pigpio program for stepper motor

On Fri, 6 Jan 2023 at 01:30, MartinM-dev @.***> wrote:

Hi
I'm a newbe in Python and i have lot things to learn.
I'm trying to move a trolley on rail.
When i start, i need to drive the trolley to the "Zero Position" and set
this position to 0.
I don't know how to set current position to zero.
I also want to change the speed of my trolley or better, set a time to go
reach the target position.
i hope someone will help me.
Thank you
—
Reply to this email directly, view it on GitHub
https://github.com/pootle/pisteppers/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHAQ342C65KV7EVQXKLP7TWQ5YVBANCNFSM6AAAAAATSSG47M
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, I too would love to be able to use your library, but am having a little trouble getting off the ground.
I'm looking to control a few steppers via artnet, so I need to work without the webserver part, but I can't seem to follow the program flow enough to instantiate the multimotor class without it. If I can get this and also instantiate a couple of stepper objects based on a json definition (e.g. motorpair8825.json) then I should be all set.
Any help would be much appreciated, otherwise I'm going to have to start from scratch.
Thanks

unless you need the ultimate performance that this library provides, you are probably better sticking with one of the standard adafruit or similar libraries as I don't have the kit anymore to check or update this library to support it.

Hi @pootle, thanks for such a quick reply, I have one more question. You haven't put any license up, if I do succed in getting this up and running would you mind me rehashing it into a library for others to use? Obviously with full attribution.
Your code appears well commented and it's a very elegant solutiion so it would seem a shame not to as there really doesn't seem to be anything even close that's out there.

oh! early days when I did this one. Absolutely free to do with as you will, attribution not necessary, but would be nice. At the time I did this, loads of people were claiming good stepper driving from a pi / python was impossible, so of course I had to do it!

Oh! there is a license here: https://github.com/pootle/pisteppers/blob/master/LICENSE


feat: remove error returning and make ColVal codec bound to little endian in record codec methods

What problem does this PR solve?

red #816
What is changed and how it works?
This PR remove unnecessary error returning in record marshal and unmarshal methods and make AppendUint32Slice bound to little endian.
Considering most machine running openGemini now is little endian, use little endian in AppendUint32Slice may bring us most compatibility.

I don't think it's a chore

is using refactor instead better?

@StepY1aoZz If you change the behavior of software, it definitely should be feat or fix

@StepY1aoZz If you change the behavior of software, it definitely should be feat or fix

Got it. Thanks!


[CAT-806] adding github pr script

Summary

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] Jira story/task is put into PR title
[ ] Code has been self-reviewed
[ ] Hard-to-understand areas have been commented
[ ] Documentation has been updated
[ ] My changes generate no new warnings
[ ] Unit tests have been added for base functionality and known edge cases
[ ] Any dependent changes have been merged and published in downstream modules

start of a script for testing with harness -- we should pass in $TAG and $GITHUB_TOKEN through harness

I think it might make more sense to put this script in the indico-readme repo, since it seems to be language agnostic :thinking: what do you think?

I think it might make more sense to put this script in the indico-readme repo, since it seems to be language agnostic 🤔 what do you think?

I just realized that without this script, the python repo has no way to access the indico-readme repo :sweat_smile: so maybe ignore me


[ Windows] Tests are Failing on Windows.

Due to this, zerunet cannot verify the sender on windows.

I checked on wsl, all tests are passing, failing only happens on windows.

Ok, nevermind tests are passing now, this is an issue while copying signature to my port.

But Doc tests are failing so https://github.com/Anshorei/zeronet_cryptography/pull/2 merging this will solve the issue.

Merged #2


Build test docker image on each PR (WIP..)

Codecov Report

Merging #79 (733cfef) into master (696dedf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #79   +/-   ##
=======================================
  Coverage   45.31%   45.31%
=======================================
  Files          22       22
  Lines        2070     2070
=======================================
  Hits          938      938
  Misses       1132     1132

Continue to review full report at Codecov.

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


updating extras in databaseview/edit changes the sqlalchemy_uri

If you edit a databaseview that uses a username and password but change only the extras field then click save, the value for sqlalchemy_uri_decrypted now is password-masked.

Add a database uri that uses a username and password.
Save, then return to this view.
Note that the SQLAlchemy URI is password masked in the UI.
Now change something in the extras field.
Save, then return to this view.
Note that the SQLAlchemy URI still is password masked in the UI.  But if you query the database for database.sqlalchemy_uri_decrypted it is now also password masked.

I think the simplest fix here is to add a check in DatabaseView.pre_add to check if db.sqlalchemy_uri (the value entered in the textfield) is different from db.safe_sqlalchemy_uri() and only call db.set_sqlalchemy_uri(db.sqlalchemy_uri) in that case.
There may be better user experiences to solve this so I'm open to suggestions.

Given the amount of issues around that code we could use some more tests i suppose.

I'm putting together a PR and will be sure to add tests.


test node bans allegedly valid bulk extrinsics

We're benchmarking by sending a large bunch of balances::transfer extrinsics using substrate-api-client
Our benchmark code
test node (based on 3bf9540e72df5ecb3955845764dfee7dcdbb26b5) :
https://github.com/scs/substrate-test-nodes/tree/api-M1.5
Expected behaviour

substrate includes all extrinsics into blocks sooner or later

Bug

substrate includes the first 2 extrinsics but bans all subsequent extrinsics (although nonce is counting up)

Reproduce:
/substrate-test-nodes$ ./target/release/substrate-test-node --dev --execution native --ws-port 9979 -ltxpool=debug

and
/substrate-api-client$ ./target/release/examples/example_benchmark_bulk_xt -p 9979

node logs:
2020-02-24 11:55:24.009 tokio-runtime-worker-2 INFO substrate  Imported #118 (0x184b…dc19)
2020-02-24 11:55:24.009 tokio-runtime-worker-4 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  [0x73a14d705a86d4386cad8846fb36d0445c7a5e602eac20c6e27e910b9694f9b2] Pruned at 0x184b0a02014b716036e0b63ce6eff53e05ffbec41b7e491dfefb5637f59cdc19
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  [0x121828bf5f44286400a92a393495b9806b4c87a8a658fb76ebc39b6bb7badb65] Pruned at 0x184b0a02014b716036e0b63ce6eff53e05ffbec41b7e491dfefb5637f59cdc19
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  [0x6f875bf76ef25004172095bec6aba357fac25362d8dda2f4ff1e0291d87ad7c4] Importing to ready
2020-02-24 11:55:24.010 tokio-runtime-worker-6 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:28.024 tokio-runtime-worker-7 INFO substrate  Idle (0 peers), best: #118 (0x184b…dc19), finalized #117 (0x3697…673e), ⬇ 0 ⬆ 0
2020-02-24 11:55:30.033 tokio-runtime-worker-2 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0x184b0a02014b716036e0b63ce6eff53e05ffbec41b7e491dfefb5637f59cdc19
2020-02-24 11:55:30.033 tokio-runtime-worker-2 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:30.035 tokio-runtime-worker-2 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 119 [hash: 0xd105eb5e34a6c439a820108ff9ef32147d2173b4beb1925c8ff9d770b33120b6; parent_hash: 0x184b…dc19; extrinsics: [0xc4f3…942c, 0x6f87…d7c4]]
2020-02-24 11:55:30.035 tokio-runtime-worker-2 INFO substrate_consensus_slots  Pre-sealed block for proposal at 119. Hash now 0x90df880d625da16810283a2a9e169fa6fc2b058b48d7537ef4bc5a3ad72ad05f, previously 0xd105eb5e34a6c439a820108ff9ef32147d2173b4beb1925c8ff9d770b33120b6.
2020-02-24 11:55:30.037 tokio-runtime-worker-2 DEBUG txpool  Starting pruning of block BlockId::Hash(0x90df880d625da16810283a2a9e169fa6fc2b058b48d7537ef4bc5a3ad72ad05f) (extrinsics: 2)
2020-02-24 11:55:30.037 tokio-runtime-worker-3 INFO substrate  Imported #119 (0x90df…d05f)
2020-02-24 11:55:30.037 tokio-runtime-worker-10 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:30.037 tokio-runtime-worker-10 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:55:30.037 tokio-runtime-worker-10 DEBUG txpool  [0xc4f365a7a8eba96b83e2a5e9ed6d1a6cf3a00e84b882d381e93458a360ce942c] Pruned at 0x90df880d625da16810283a2a9e169fa6fc2b058b48d7537ef4bc5a3ad72ad05f
2020-02-24 11:55:30.037 tokio-runtime-worker-10 DEBUG txpool  [0x6f875bf76ef25004172095bec6aba357fac25362d8dda2f4ff1e0291d87ad7c4] Pruned at 0x90df880d625da16810283a2a9e169fa6fc2b058b48d7537ef4bc5a3ad72ad05f
2020-02-24 11:55:30.037 tokio-runtime-worker-10 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:30.037 tokio-runtime-worker-10 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:30.038 tokio-runtime-worker-2 DEBUG txpool  [0xfc19d50b12515dbec3ae3c8f7da70d1a007e3d262e02c8d87d9f86fd9a352fd6] Importing to ready
2020-02-24 11:55:30.038 tokio-runtime-worker-2 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:33.026 tokio-runtime-worker-10 INFO substrate  Idle (0 peers), best: #119 (0x90df…d05f), finalized #118 (0x184b…dc19), ⬇ 0 ⬆ 0
2020-02-24 11:55:36.001 tokio-runtime-worker-7 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0x90df880d625da16810283a2a9e169fa6fc2b058b48d7537ef4bc5a3ad72ad05f
2020-02-24 11:55:36.002 tokio-runtime-worker-7 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:36.006 tokio-runtime-worker-7 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 120 [hash: 0xeec81267850388d78cd368c31da9e95b64d7a7a78b421ecb23effe96a3ea1ad0; parent_hash: 0x90df…d05f; extrinsics: [0x09fe…d18a, 0xfc19…2fd6]]
2020-02-24 11:55:36.006 tokio-runtime-worker-7 INFO substrate_consensus_slots  Pre-sealed block for proposal at 120. Hash now 0xf0ed9fecdb377afa427664e0b6763d3187965d0ed476320d9a09aba634e7c68e, previously 0xeec81267850388d78cd368c31da9e95b64d7a7a78b421ecb23effe96a3ea1ad0.
2020-02-24 11:55:36.008 tokio-runtime-worker-0 DEBUG txpool  Starting pruning of block BlockId::Hash(0xf0ed9fecdb377afa427664e0b6763d3187965d0ed476320d9a09aba634e7c68e) (extrinsics: 2)
2020-02-24 11:55:36.008 tokio-runtime-worker-4 INFO substrate  Imported #120 (0xf0ed…c68e)
2020-02-24 11:55:36.008 tokio-runtime-worker-4 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:36.008 tokio-runtime-worker-2 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:55:36.008 tokio-runtime-worker-2 DEBUG txpool  [0x09fe005af15c2755ee152aa5a186212283a6c08a1583f10657055a2ef1e6d18a] Pruned at 0xf0ed9fecdb377afa427664e0b6763d3187965d0ed476320d9a09aba634e7c68e
2020-02-24 11:55:36.008 tokio-runtime-worker-2 DEBUG txpool  [0xfc19d50b12515dbec3ae3c8f7da70d1a007e3d262e02c8d87d9f86fd9a352fd6] Pruned at 0xf0ed9fecdb377afa427664e0b6763d3187965d0ed476320d9a09aba634e7c68e
2020-02-24 11:55:36.009 tokio-runtime-worker-2 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:36.009 tokio-runtime-worker-2 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:36.009 tokio-runtime-worker-9 DEBUG txpool  [0x22370722e40fc24a388930bd3452db2eb2939a0e3830b466c29b18fa8e925be5] Importing to ready
2020-02-24 11:55:36.009 tokio-runtime-worker-9 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:38.027 tokio-runtime-worker-4 INFO substrate  Idle (0 peers), best: #120 (0xf0ed…c68e), finalized #119 (0x90df…d05f), ⬇ 0 ⬆ 0
2020-02-24 11:55:42.001 tokio-runtime-worker-2 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0xf0ed9fecdb377afa427664e0b6763d3187965d0ed476320d9a09aba634e7c68e
2020-02-24 11:55:42.002 tokio-runtime-worker-2 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:42.005 tokio-runtime-worker-2 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 121 [hash: 0x26e22855db53e49153d522df568f98dbd8742caf9a31c96fdba74224c28067fc; parent_hash: 0xf0ed…c68e; extrinsics: [0x3c18…ba21, 0x2237…5be5]]
2020-02-24 11:55:42.005 tokio-runtime-worker-2 INFO substrate_consensus_slots  Pre-sealed block for proposal at 121. Hash now 0x4ee199f834952e65713dca0b5964de84302a859b2ae9d954e4b985077f2098e6, previously 0x26e22855db53e49153d522df568f98dbd8742caf9a31c96fdba74224c28067fc.
2020-02-24 11:55:42.007 tokio-runtime-worker-4 INFO substrate  Imported #121 (0x4ee1…98e6)
2020-02-24 11:55:42.007 tokio-runtime-worker-0 DEBUG txpool  Starting pruning of block BlockId::Hash(0x4ee199f834952e65713dca0b5964de84302a859b2ae9d954e4b985077f2098e6) (extrinsics: 2)
2020-02-24 11:55:42.007 tokio-runtime-worker-8 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:42.008 tokio-runtime-worker-8 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:55:42.008 tokio-runtime-worker-8 DEBUG txpool  [0x3c183348f7d55ec0a453124390afb2d60940e38d9a03bd189c3593bf7911ba21] Pruned at 0x4ee199f834952e65713dca0b5964de84302a859b2ae9d954e4b985077f2098e6
2020-02-24 11:55:42.008 tokio-runtime-worker-8 DEBUG txpool  [0x22370722e40fc24a388930bd3452db2eb2939a0e3830b466c29b18fa8e925be5] Pruned at 0x4ee199f834952e65713dca0b5964de84302a859b2ae9d954e4b985077f2098e6
2020-02-24 11:55:42.008 tokio-runtime-worker-8 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:42.008 tokio-runtime-worker-8 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:42.009 tokio-runtime-worker-0 DEBUG txpool  [0x7d8389407d156b76852929eed9e2772effa52f78a1a674e174428d7a681e091d] Importing to ready
2020-02-24 11:55:42.009 tokio-runtime-worker-0 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:43.029 tokio-runtime-worker-2 INFO substrate  Idle (0 peers), best: #121 (0x4ee1…98e6), finalized #119 (0x90df…d05f), ⬇ 0 ⬆ 0
2020-02-24 11:55:48.030 tokio-runtime-worker-7 INFO substrate  Idle (0 peers), best: #121 (0x4ee1…98e6), finalized #120 (0xf0ed…c68e), ⬇ 0 ⬆ 0
2020-02-24 11:55:48.032 tokio-runtime-worker-10 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0x4ee199f834952e65713dca0b5964de84302a859b2ae9d954e4b985077f2098e6
2020-02-24 11:55:48.032 tokio-runtime-worker-10 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:48.034 tokio-runtime-worker-10 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 122 [hash: 0xa8e75652fe4adf2d3d765814fd595c96254c831f939cf5179d22b9a59d4816b8; parent_hash: 0x4ee1…98e6; extrinsics: [0x092b…102f, 0x7d83…091d]]
2020-02-24 11:55:48.034 tokio-runtime-worker-10 INFO substrate_consensus_slots  Pre-sealed block for proposal at 122. Hash now 0x5b19346c7ed82b7a6f2f739a3a9d95435e5c9be74f96f4bc66e24f1883641ea7, previously 0xa8e75652fe4adf2d3d765814fd595c96254c831f939cf5179d22b9a59d4816b8.
2020-02-24 11:55:48.036 tokio-runtime-worker-8 INFO substrate  Imported #122 (0x5b19…1ea7)
2020-02-24 11:55:48.036 tokio-runtime-worker-7 DEBUG txpool  Starting pruning of block BlockId::Hash(0x5b19346c7ed82b7a6f2f739a3a9d95435e5c9be74f96f4bc66e24f1883641ea7) (extrinsics: 2)
2020-02-24 11:55:48.036 tokio-runtime-worker-5 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:55:48.036 tokio-runtime-worker-9 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:55:48.036 tokio-runtime-worker-9 DEBUG txpool  [0x092b1fa379b686610827d194a6c4b7e495f6f8bed5a56f02417d0371c257102f] Pruned at 0x5b19346c7ed82b7a6f2f739a3a9d95435e5c9be74f96f4bc66e24f1883641ea7
2020-02-24 11:55:48.036 tokio-runtime-worker-9 DEBUG txpool  [0x7d8389407d156b76852929eed9e2772effa52f78a1a674e174428d7a681e091d] Pruned at 0x5b19346c7ed82b7a6f2f739a3a9d95435e5c9be74f96f4bc66e24f1883641ea7
2020-02-24 11:55:48.036 tokio-runtime-worker-9 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:48.036 tokio-runtime-worker-9 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:53.031 tokio-runtime-worker-10 INFO substrate  Idle (0 peers), best: #122 (0x5b19…1ea7), finalized #121 (0x4ee1…98e6), ⬇ 0 ⬆ 0
2020-02-24 11:55:54.001 tokio-runtime-worker-9 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0x5b19346c7ed82b7a6f2f739a3a9d95435e5c9be74f96f4bc66e24f1883641ea7
2020-02-24 11:55:54.002 tokio-runtime-worker-9 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:55:54.006 tokio-runtime-worker-9 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 123 [hash: 0xa3c2fa2b0f1f49e44d873ce54da18321f4cc01ec3abb4e5afa701cc4d9553097; parent_hash: 0x5b19…1ea7; extrinsics: [0xfb5b…7cf3]]
2020-02-24 11:55:54.006 tokio-runtime-worker-9 INFO substrate_consensus_slots  Pre-sealed block for proposal at 123. Hash now 0xfa01c61a49740b8c0d1dc449c600255badb27966794e93bb420ac9aa5e9f1ad9, previously 0xa3c2fa2b0f1f49e44d873ce54da18321f4cc01ec3abb4e5afa701cc4d9553097.
2020-02-24 11:55:54.008 tokio-runtime-worker-10 INFO substrate  Imported #123 (0xfa01…1ad9)
2020-02-24 11:55:54.008 tokio-runtime-worker-8 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:55:58.032 tokio-runtime-worker-7 INFO substrate  Idle (0 peers), best: #123 (0xfa01…1ad9), finalized #122 (0x5b19…1ea7), ⬇ 0 ⬆ 0
2020-02-24 11:56:00.000 tokio-runtime-worker-5 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0xfa01c61a49740b8c0d1dc449c600255badb27966794e93bb420ac9aa5e9f1ad9
2020-02-24 11:56:00.001 tokio-runtime-worker-5 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:00.002 tokio-runtime-worker-5 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 124 [hash: 0x610a4fd22a8d3b4f416caf0d169de73da50e0ace8979dfaa8f4f70537473f14f; parent_hash: 0xfa01…1ad9; extrinsics: [0x222a…5d13]]
2020-02-24 11:56:00.003 tokio-runtime-worker-5 INFO substrate_consensus_slots  Pre-sealed block for proposal at 124. Hash now 0x3a45342e38516216fdb93cf554e4cee7a6175a55a6050bc5599e1067b6c0c18a, previously 0x610a4fd22a8d3b4f416caf0d169de73da50e0ace8979dfaa8f4f70537473f14f.
2020-02-24 11:56:00.005 tokio-runtime-worker-2 INFO substrate  Imported #124 (0x3a45…c18a)
2020-02-24 11:56:00.005 tokio-runtime-worker-5 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:56:03.033 tokio-runtime-worker-4 INFO substrate  Idle (0 peers), best: #124 (0x3a45…c18a), finalized #123 (0xfa01…1ad9), ⬇ 0 ⬆ 0
2020-02-24 11:56:06.001 tokio-runtime-worker-10 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0x3a45342e38516216fdb93cf554e4cee7a6175a55a6050bc5599e1067b6c0c18a
2020-02-24 11:56:06.002 tokio-runtime-worker-10 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:06.006 tokio-runtime-worker-10 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 125 [hash: 0xeb672409b3fe39e1a0a4547b0d5229fa9291bef2408b62303b08dcac712bf945; parent_hash: 0x3a45…c18a; extrinsics: [0x7109…bcf1]]
2020-02-24 11:56:06.006 tokio-runtime-worker-10 INFO substrate_consensus_slots  Pre-sealed block for proposal at 125. Hash now 0xf0d2e88334d55407ad0ca9487a922a2a5b6fd3f0f9b5b3b233544f6250327f9d, previously 0xeb672409b3fe39e1a0a4547b0d5229fa9291bef2408b62303b08dcac712bf945.
2020-02-24 11:56:06.008 tokio-runtime-worker-10 INFO substrate  Imported #125 (0xf0d2…7f9d)
2020-02-24 11:56:06.008 tokio-runtime-worker-5 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.034 tokio-runtime-worker-5 INFO substrate  Idle (0 peers), best: #125 (0xf0d2…7f9d), finalized #124 (0x3a45…c18a), ⬇ 0 ⬆ 0
2020-02-24 11:56:08.498 tokio-runtime-worker-1 DEBUG txpool  [0x06df84104e05268d27330b036f29e653ee709baabdddfcd52586b11428df9b70] Importing to ready
2020-02-24 11:56:08.498 tokio-runtime-worker-1 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.499 tokio-runtime-worker-0 DEBUG txpool  [0x415f9193191088cf046bcbd5023d173100305c88e1c19b02c991717a4432d228] Importing to ready
2020-02-24 11:56:08.499 tokio-runtime-worker-0 DEBUG txpool  Pool Status: Status { ready: 2, ready_bytes: 286, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.500 tokio-runtime-worker-4 DEBUG txpool  [0x9a4056b93b895d063f0dab9f51c5b3d4d4932ef931d28294adb9c604c68d55d8] Importing to ready
2020-02-24 11:56:08.500 tokio-runtime-worker-4 DEBUG txpool  Pool Status: Status { ready: 3, ready_bytes: 429, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.501 tokio-runtime-worker-1 DEBUG txpool  [0x1824f6314f7b7a8bbf107b1842148ec68ad80a82b4495a9af8e99340d2ad551f] Importing to ready
2020-02-24 11:56:08.501 tokio-runtime-worker-1 DEBUG txpool  Pool Status: Status { ready: 4, ready_bytes: 572, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.502 tokio-runtime-worker-5 DEBUG txpool  [0x287056952dd3e79dac3d0a835cf34617ef368cb4459fb0093967cd7cd4ccbd5c] Importing to ready
2020-02-24 11:56:08.502 tokio-runtime-worker-5 DEBUG txpool  Pool Status: Status { ready: 5, ready_bytes: 715, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.503 tokio-runtime-worker-5 DEBUG txpool  [0x9740b20841d423333b1c550943d9990fb48603105f93347f87ae2b71722f92e4] Importing to ready
2020-02-24 11:56:08.503 tokio-runtime-worker-5 DEBUG txpool  Pool Status: Status { ready: 6, ready_bytes: 858, future: 0, future_bytes: 0 }
2020-02-24 11:56:08.504 tokio-runtime-worker-4 DEBUG txpool  [0x0338455188c845ebaa58327e48cdd298404de786bf23d998683b7f93886033a5] Importing to ready
...
2020-02-24 11:56:09.107 tokio-runtime-worker-10 DEBUG txpool  Pool Status: Status { ready: 87, ready_bytes: 12480, future: 0, future_bytes: 0 }
2020-02-24 11:56:09.110 tokio-runtime-worker-6 DEBUG txpool  [0x4b1f212d37e1abaf33cab82e0d07900fc984f1c364531471ed2b55067a80ff25] Importing to ready
2020-02-24 11:56:09.110 tokio-runtime-worker-6 DEBUG txpool  Pool Status: Status { ready: 88, ready_bytes: 12624, future: 0, future_bytes: 0 }
2020-02-24 11:56:12.001 tokio-runtime-worker-6 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0xf0d2e88334d55407ad0ca9487a922a2a5b6fd3f0f9b5b3b233544f6250327f9d
2020-02-24 11:56:12.011 tokio-runtime-worker-6 DEBUG txpool  Banning invalid transactions: [0x9a4056b93b895d063f0dab9f51c5b3d4d4932ef931d28294adb9c604c68d55d8, 0x1824f6314f7b7a8bbf107b1842148ec68ad80a82b4495a9af8e99340d2ad551f, 0x287056952dd3e79dac3d0a835cf34617ef368cb4459fb0093967cd7cd4ccbd5c,
....
0x0cde1bb8dc57bb73a9fafeef5b511e4d5dad841bc3e08005249bffa525224883, 0xe6e0dfa96f789e911d651b263f287246af3904812e2e11a32dc53898fa3bdc62, 0x836c9993065035850709a36f4145f4b00a3b1b36b53404f92d1a88c808cdee8d, 0x4b1f212d37e1abaf33cab82e0d07900fc984f1c364531471ed2b55067a80ff25]
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x4b1f212d37e1abaf33cab82e0d07900fc984f1c364531471ed2b55067a80ff25] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x836c9993065035850709a36f4145f4b00a3b1b36b53404f92d1a88c808cdee8d] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0xe6e0dfa96f789e911d651b263f287246af3904812e2e11a32dc53898fa3bdc62] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x0cde1bb8dc57bb73a9fafeef5b511e4d5dad841bc3e08005249bffa525224883] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x9a504b0b2d8b3f3fef10e5ac6812e4330d0736e0b177dae01286d6c5d2298865] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x0eeb301e8dec1ea136d0d90b66ea2e06af8b77ffd39d75bf89ea94a066e1a77f] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x70641da1020e94e266d81bfb1d79fb4ab91dc5bb94fd447a80dbcb808561cfc2] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x51db3a8f6fc933c67c243a7825e593d68b19aef67383669672e12d53087e2442] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x00c0e9342a0fd5561bbcf0683b8ad53d7ab3db139a2fc9f85bc24364f4028c52] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x8ba6af9b298623003b6b6528bc016d215f4e3ca5e7a9adf01beaf89e4fb3587a] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool
....
[0x0338455188c845ebaa58327e48cdd298404de786bf23d998683b7f93886033a5] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x9740b20841d423333b1c550943d9990fb48603105f93347f87ae2b71722f92e4] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x287056952dd3e79dac3d0a835cf34617ef368cb4459fb0093967cd7cd4ccbd5c] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x1824f6314f7b7a8bbf107b1842148ec68ad80a82b4495a9af8e99340d2ad551f] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 DEBUG txpool  [0x9a4056b93b895d063f0dab9f51c5b3d4d4932ef931d28294adb9c604c68d55d8] Removed as invalid:
2020-02-24 11:56:12.012 tokio-runtime-worker-6 WARN transaction-pool  Extrinsic invalid: 0x4b1f212d37e1abaf33cab82e0d07900fc984f1c364531471ed2b55067a80ff25
2020-02-24 11:56:12.012 tokio-runtime-worker-6 WARN transaction-pool  Extrinsic invalid: 0x836c9993065035850709a36f4145f4b00a3b1b36b53404f92d1a88c808cdee8d
...
2020-02-24 11:56:12.012 tokio-runtime-worker-6 WARN transaction-pool  Extrinsic invalid: 0x1824f6314f7b7a8bbf107b1842148ec68ad80a82b4495a9af8e99340d2ad551f
2020-02-24 11:56:12.012 tokio-runtime-worker-6 WARN transaction-pool  Extrinsic invalid: 0x9a4056b93b895d063f0dab9f51c5b3d4d4932ef931d28294adb9c604c68d55d8
2020-02-24 11:56:12.014 tokio-runtime-worker-6 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 126 [hash: 0x4a7c17360a7562e7285561761db99863ec12c19704e1b982b044924d0db80e61; parent_hash: 0xf0d2…7f9d; extrinsics: [0x7dec…b089, 0x06df…9b70]]
2020-02-24 11:56:12.014 tokio-runtime-worker-6 INFO substrate_consensus_slots  Pre-sealed block for proposal at 126. Hash now 0x17421d366d3b329c38ac633a1c439f9330856112740db1646413438f7750e7e1, previously 0x4a7c17360a7562e7285561761db99863ec12c19704e1b982b044924d0db80e61.
2020-02-24 11:56:12.016 tokio-runtime-worker-6 INFO substrate  Imported #126 (0x1742…e7e1)
2020-02-24 11:56:12.016 tokio-runtime-worker-0 DEBUG txpool  Starting pruning of block BlockId::Hash(0x17421d366d3b329c38ac633a1c439f9330856112740db1646413438f7750e7e1) (extrinsics: 2)
2020-02-24 11:56:12.016 tokio-runtime-worker-10 DEBUG txpool  Pool Status: Status { ready: 2, ready_bytes: 286, future: 0, future_bytes: 0 }
2020-02-24 11:56:12.016 tokio-runtime-worker-6 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:56:12.016 tokio-runtime-worker-6 DEBUG txpool  [0x7dec6e7e0a4950a82486616330c90c0381ca2e20570d462055fbd17c1eedb089] Pruned at 0x17421d366d3b329c38ac633a1c439f9330856112740db1646413438f7750e7e1
2020-02-24 11:56:12.016 tokio-runtime-worker-6 DEBUG txpool  [0x06df84104e05268d27330b036f29e653ee709baabdddfcd52586b11428df9b70] Pruned at 0x17421d366d3b329c38ac633a1c439f9330856112740db1646413438f7750e7e1
2020-02-24 11:56:12.016 tokio-runtime-worker-6 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:12.016 tokio-runtime-worker-6 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:13.036 tokio-runtime-worker-10 INFO substrate  Idle (0 peers), best: #126 (0x1742…e7e1), finalized #125 (0xf0d2…7f9d), ⬇ 0 ⬆ 0
2020-02-24 11:56:18.001 tokio-runtime-worker-0 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0x17421d366d3b329c38ac633a1c439f9330856112740db1646413438f7750e7e1
2020-02-24 11:56:18.003 tokio-runtime-worker-0 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:18.006 tokio-runtime-worker-0 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 127 [hash: 0x79e4d6f8fed986de519a3e87c8bdd183efd57180d35b1e31f16b6f4fd32d3810; parent_hash: 0x1742…e7e1; extrinsics: [0x21d6…dc06, 0x415f…d228]]
2020-02-24 11:56:18.006 tokio-runtime-worker-0 INFO substrate_consensus_slots  Pre-sealed block for proposal at 127. Hash now 0xfa0fe7ddadea5b046634b04b71687d5c3a286f643ae16f77064b4fa8c246e540, previously 0x79e4d6f8fed986de519a3e87c8bdd183efd57180d35b1e31f16b6f4fd32d3810.
2020-02-24 11:56:18.008 tokio-runtime-worker-4 DEBUG txpool  Starting pruning of block BlockId::Hash(0xfa0fe7ddadea5b046634b04b71687d5c3a286f643ae16f77064b4fa8c246e540) (extrinsics: 2)
2020-02-24 11:56:18.008 tokio-runtime-worker-1 INFO substrate  Imported #127 (0xfa0f…e540)
2020-02-24 11:56:18.008 tokio-runtime-worker-10 DEBUG txpool  Pool Status: Status { ready: 1, ready_bytes: 143, future: 0, future_bytes: 0 }
2020-02-24 11:56:18.008 tokio-runtime-worker-10 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:56:18.008 tokio-runtime-worker-10 DEBUG txpool  [0x21d6cb03857a415469a74bbc1a818cdc6fc955b1b788cf22eb62a2c6dd21dc06] Pruned at 0xfa0fe7ddadea5b046634b04b71687d5c3a286f643ae16f77064b4fa8c246e540
2020-02-24 11:56:18.008 tokio-runtime-worker-10 DEBUG txpool  [0x415f9193191088cf046bcbd5023d173100305c88e1c19b02c991717a4432d228] Pruned at 0xfa0fe7ddadea5b046634b04b71687d5c3a286f643ae16f77064b4fa8c246e540
2020-02-24 11:56:18.008 tokio-runtime-worker-10 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:18.008 tokio-runtime-worker-10 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:18.038 tokio-runtime-worker-10 INFO substrate  Idle (0 peers), best: #127 (0xfa0f…e540), finalized #125 (0xf0d2…7f9d), ⬇ 0 ⬆ 0
2020-02-24 11:56:23.039 tokio-runtime-worker-1 INFO substrate  Idle (0 peers), best: #127 (0xfa0f…e540), finalized #126 (0x1742…e7e1), ⬇ 0 ⬆ 0
2020-02-24 11:56:24.001 tokio-runtime-worker-9 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0xfa0fe7ddadea5b046634b04b71687d5c3a286f643ae16f77064b4fa8c246e540
2020-02-24 11:56:24.002 tokio-runtime-worker-9 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:24.006 tokio-runtime-worker-9 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 128 [hash: 0x2a55b20b037a41020d0ff3e7a57aa1ad77f143d00a8e44be75214e2486154059; parent_hash: 0xfa0f…e540; extrinsics: [0xa577…b2a8]]
2020-02-24 11:56:24.006 tokio-runtime-worker-9 INFO substrate_consensus_slots  Pre-sealed block for proposal at 128. Hash now 0xac8b9138face3fc29fc6f0b864733f080c53362256401bf50011fad6720922eb, previously 0x2a55b20b037a41020d0ff3e7a57aa1ad77f143d00a8e44be75214e2486154059.
2020-02-24 11:56:24.008 tokio-runtime-worker-9 INFO substrate  Imported #128 (0xac8b…22eb)
2020-02-24 11:56:24.008 tokio-runtime-worker-1 DEBUG txpool  Pool Status: Status { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 }
2020-02-24 11:56:28.041 tokio-runtime-worker-10 INFO substrate  Idle (0 peers), best: #128 (0xac8b…22eb), finalized #127 (0xfa0f…e540), ⬇ 0 ⬆ 0
2020-02-24 11:56:30.001 tokio-runtime-worker-4 INFO substrate_basic_authorship::basic_authorship  Starting consensus session on top of parent 0xac8b9138face3fc29fc6f0b864733f080c53362256401bf50011fad6720922eb
2020-02-24 11:56:30.002 tokio-runtime-worker-4 DEBUG txpool  Banning invalid transactions: []
2020-02-24 11:56:30.006 tokio-runtime-worker-4 INFO substrate_basic_authorship::basic_authorship  Prepared block for proposing at 129 [hash: 0x71d936c059b3490e1309b602a030f6a04cd703f7226e42e58a474addca2eb1e2; parent_hash: 0xac8b…22eb; extrinsics: [0xe23e…81b0]]
2020-02-24 11:56:30.006 tokio-runtime-worker-4 INFO substrate_consensus_slots  Pre-sealed block for proposal at 129. Hash now 0xfb724aa25a39361cca034e4930361a7d689eb496ae943f1630813c74b7c87b31, previously 0x71d936c059b3490e1309b602a030f6a04cd703f7226e42e58a474addca2eb1e2.
2020-02-24 11:56:30.008 tokio-runtime-worker-0 INFO substrate  Imported #129 (0xfb72…7b31)

@tomusdrw any news on this one?

No, sorry I didn't yet have time to reproduce it. Is it possible that the account you are sending from is simply going below Existential deposit and is being pruned?
That would render all subsequent transactions Future, but since they were already in the Ready queue, we probably remove them as invalid.
I'll try to reproduce in upcoming days.

Found a culprit, working on a fix.
The problem is that your block (weight) size is very small, so it's able to only fit couple of initial transactions.
We have a mechanism for block proposing that will try to push a bit more transactions even if the last one failed (to pack the block up to some local maximum), but this causes an issue, cause, because since all transactions are coming from a single sender, and we skip one because it doesn't fit, the rest is reported as invalid due to mismatching nonce.
The solution is to not mark them as invalid if we skipped some previous transactions. I'm currently working on a fix and test for this case.

Ok, thanks for looking into this. Is there a quick fix for me? Where would I increase the block weight and what would be a reasonable number?

You can increase the block size here:
https://github.com/scs/substrate-test-nodes/blob/api-M1.5/runtime/src/lib.rs#L143
Unfortunatelly, the issue will still persist with your current benchmarking code, you would need to:

Send transactions in batches that fits into a block
Detect failures, and restart with correct nonce from time to time

I is strange though that @shawntabrizi's benchmark in js didn't run into this. (I haven't tested it, but I guess Shawn has.


Update plugin.json, fix files with php-cs-fixer and fix phpstan issues

Coverage remained the same at 35.932% when pulling d06dfe1fa415e3d08fdccec5bfb375589ef1b40a on NTR-prepare-release-1_1_4 into 1d19517bc0026539200d0b873f4deab462e221fc on master.


Dynamic quotes website with tweet button using JS

In this project dynamic quotes will be generated form an API . And the generated quote can be posted on twitter with the tweet button available for the user.

A PR for quote genrator project is already been raised . Once it gets merged u can create an issue if you have any idea or changes for that project

Ok mam
On Wed, 1 Feb 2023, 17:38 Vanshita Mathur, @.***> wrote:

A PR for quote genrator project is already been raised . Once it gets
merged u can create an issue if you have any idea or changes for that
project
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/issues/559#issuecomment-1411953414,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHWPCAAISEBMYEOEPH3WVJG2BANCNFSM6AAAAAAUNESERM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Final Json

As a suggestion I would suggest to include the final json file as well , since it's not clear where is the Volumes even in Azure Resource Manager template link provided

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

ID: b730fc95-951e-1acd-770d-88b3e6f2f6ef
Version Independent ID: b6445fd2-46ea-aedd-2f2c-294faa660660
Content: Mount an Azure Files volume in Azure Container Instances
Content Source: articles/container-instances/container-instances-volume-azure-files.md
Service: container-instances
GitHub Login: @dlepow
Microsoft Alias: danlep

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@RezaRahmati - Thanks for the good suggestion to improve this article with a complete JSON template for deployment. I am adding it to our doc work list for ACI. In the meantime you might find it helpful to see how the volumes and volumeMounts properties are arranged in templates for other mounted volumes such as secret and cloned Git repo. While these are different volume types, the template syntax for mounting volumes is similar when adding a file volume.
You might also find it helpful to browse some of the ACI Quickstart Templates for examples of mounting volumes.
I hope this helps!
#please-close