The Future of Meteor, and what to do about it.

Hi @Urigo, @barbatus  et al.,
Since we don't have a forum or some better way to exchange ideas, I thought this would be an appropriate place to do it. If you think otherwise, please direct me to where I should repost this for discussion.
I read today a pretty disturbing article that regards the future of our sub-community of Meteor.
Sacha Greif wrote a highly opinionated article about Meteor's future here.
It is his opinion that React will prevail as the choice for front-end in Meteor, but the reasons he give in favor of his opinion can all be applied to justify an opposite opinion that Angular will prevail.
Him being a very influential individual in the Meteor community, and considering the fact that most people coming from Blaze will not know the pros and cons of React vs. Angular, he may considerably use his influence the broad community to, indeed, skew the community to opt for React against Angular.
One strong point, that is easily missed in his article is the existence of the Mantra project that is run by Kadira of Arunoda Susiripala, who is also a person of immense influence in the broad Meteor community. In this Mantra project he is also advocating a switch to React, and basing his project on it. This is especially threatening for the future of Angular in Meteor world, because, as you already know, Kadira and Arunoda are the ones who developed the Meteor Up deployment system which is the defacto standard in the broader Meteor community for deploying applications.
Therefore it is my opinion and hope, that we in the angular-meteor community must stand and put an extra effort into promoting Angular as a viable UI option for Meteor, in order to win community support for developing other packages needed to support our small eco-system.
Mantra project itself is a good source to brainpick ideas for our project here.
Thank you all for your attention, and I hope it was not a waste of time.

@MilosStanic  I think it is a good discussion for the forums.meteor.com. We should also increase our presence there.

I see there's already a topic about Sacha's article with a flamewar going on over there at https://forums.meteor.com/t/the-state-of-meteor-part-2-what-happens-next/16766
But I thought we need a place to make a strategy to counter the React initiative. It's not that I have anything personal against React, but they may steal the community away from us.

@MilosStanic I’ve heard that MDG ditched ideas of Blaze2 based on React in favor of supporting Blaze, React, and Angular2 all together. I believe MDG still decides where to go not just famous people in the community even if they are Sacha or Arunoda.

Maybe angular-meteor site needs a forum, and/or blog. Forum would be needed for discussions like this, and blog would be nice for publishing articles about best practices and real-world use-cases.
Also, it would be nice of @Urigo and @barbatus to keep us a little more informed about the plans for the future of angular2-meteor.
I believe most of us are working on real-life angular-meteor applications, and we need a bit more encouragement and reassuring about the future to stay with Meteor, instead of investigating other options for backend to Angular(2).

Maybe angular-meteor site needs a forum, and/or blog.

@MilosStanic I think angular category at meteor's forum is enough.
About blog, that is a good idea. Something like guide.meteor.com would be great. Especially with support from angular-meteor's community.

Happy to see this conversation going on.
I think we should separate the topic of angular advocacy in the meteor community from an internal discussion of ways to improve our own angular-meteor community -- be that through new features on the website, meet ups, voting, etc. Strong work on the latter empowers the former.
So on that topic I would like to propose:

Creation of email list for "users" and "dev" so that GitHub is used for issues/bugs, user list for questions like "how do I do this" or "check out this cool shit I made", and dev list for coordinating RCs, questions of API development, etc

Starting to release RCs or maintain strong development branch / nightlies so that we don't run into quick patch problems

Creating a "receipe" section on the website that will provide starter code/ snippets for common design patterns (example: the discussion of reactive factories/services going on on be other thread) that are super helpful, but that don't belong in the API documentation.

Finally, I hate to see all these email threads about broken tutorial examples. With the lightening speed at which node, meteor, and angular change I know that it is hard to keep documentation up to date. But I think we can find a solution in enforcing stricter test standards. I.e. Every tutorial example needs a test case and website documentation PR requires passing CI tests.

My two cents/ 3 shekels/ 7 angular dollars.
JR
—
Sent from mobile
On Thu, Jan 21, 2016 at 8:33 AM, Miloš Stanić<EMAIL_ADDRESS>wrote:

Maybe angular-meteor site needs a forum, and/or blog. Forum would be needed for discussions like this, and blog would be nice for publishing articles about best practices and real-world use-cases.
Also, it would be nice of @Urigo and @barbatus to keep us a little more informed about the plans for the future of angular2-meteor.
I believe most of us are working on real-life angular-meteor applications, and we need a bit more encouragement and reassuring about the future to stay with Meteor, instead of investigating other options for backend to Angular(2).
Reply to this email directly or view it on GitHub:
https://github.com/Urigo/angular-meteor/issues/1120#issuecomment-173571508

Agreed, a place for us cool people would be great.  I've tried a combination of posting stuff between stack overflow and the meteor forums in regards to angular help but it feels like they just get buried and forgotten.
Even though MDG has stated they want angular to be a big part of this community, it doesn't really feel like it sometimes.  Which is sort of scary for us using this for production apps.

Since we don't have a forum or some better way to exchange ideas, I thought this would be an appropriate place to do it. If you think otherwise, please direct me to where I should repost this for discussion.

Personally, I think the Meteor forum would be an awesome place to have this discussion - I don't think the Angular-Meteor community is heard enough by the other people in the general Meteor community, so the place seems a bit skewed.

I do not know if this is relevant, but I'd thought I'd add it. I'm currently a leaner in all things Angular and Meteor.
I work in education and logged in to my schools Microsoft Education Office 365 account where I was greeted with a notice that I could test their new Admin Console. Interestingly, it all seems they have moved to Angular. It's a beta so I guess this might change....
But, it got me thinking, that if MS are investing Angular in one of their MAJOR products, then perhaps the Meteor community should take note and not jump on the wagon of supporting one front-end system. Working with Meteor and Angular has been one of the most interesting projects I've work on and, as with many annoying problems I've encountered (which are usually my incompetence), there have been many 'wow' moments.
I hope the community is not swayed, because (although I am very happy to admit I have no experience in React), it seems that the front-end should not be decided by individuals, but by the programmers.

Thanks for the link to the Angular-Meteor forums! I wish that it was more prominently featured as a primary link on the angular-material.com site and in Uri's ngConf/AngularConnect/etc presentations.

React has a problem because of its PATENTS file in Facebook's repos. If you use React/Immutable/etc. It appears to give Facebook the right to infringe on your company's patents while not giving you the same position in return. Software patents suck, but this creates a power imbalance. I think that it would be a bad decision to put React into Meteor, because it would cause some companies to avoid Meteor.

I think that it would be a bad decision to put React into Meteor, because it would cause some companies to avoid Meteor.

We aren't putting React into Meteor.

We aren't putting React into Meteor.

Great :)

+1

@MilosStanic It is great that you opened this issue and I’m very happy for it.
I haven’t responded so far because I wanted all the Meteor 1.3 things to be done...
First - It’s important to emphasize that the people talking about React are simply community members excited about it, not an official statement from MDG, and everyone has the right to pick their favorite framework.
It looks like our Angular-Meteor community has kept to itself rather than being part of the general Meteor community, so most people in the Meteor community aren't aware of the benefits of Angular at the moment.
This is why I’ve removed the special forum for Angular Meteor and I’m not fond of our angular-meteor Gitter.
All of those conversations need to take place inside the Meteor and Angular forums and our community’s opinions should be heard much more there.
Also, we need to talk not only on the Angular specific category, but to make our voice heard on the general topics as well.
I think your comment opens a door for the Angular community to take a more active role inside the Meteor community and a start for the Meteor community to take a more active role inside the Angular community.
While I’m here and we are addressing our Angular-Meteor community, I’m going to take the opportunity to expand more about my current personal view and vision.
So I’m going to address your comments and break it down to a few topics:

Angular-Meteor 2 IS the stack
Building a Community inside the larger Javascript Community
The Future of Meteor (and Angular)

Angular-Meteor 2 IS my choice of stack
Meteor 1.3 with Angular 2.0 Beta is finally the stack that I’ve been waiting and working for, for years.
Angular 2.0 Beta is finally solid and Meteor 1.3 gives Angular developers the possibility to work directly with npm and the whole Javascript community.
As I see it today, Angular 2.0 is currently my choice for front-end solution and I’ve just given a small lecture about how with all the great benefits and progress React has given us (taking the points from the great Pete Hunt talk - “rethinking best practices”), Angular 2.0 takes those abilities to the next level in every field.
Maybe I should give that talk to a wider audience, maybe in the next ng-conf/react-conf or something… (@aaronfrost)
Also the progress that the Angular team is doing on so many fronts since the Beta was out is extraordinary - You should follow the Angular Weekly meetings and Brad Green’s twitter account and look at what they are doing with Mobile, animations, Web Workers etc...
So I’m not worried that the Meteor community will be focused on React.  the community is smart enough to go with the best existing solutions and now that Angular 2.0 and Meteor 1.3 are available, we have a very good competition that will push everyone forward.
Remember that before Angular Meteor, there was no real solution for UI in Meteor other than Blaze.  We’ve come a long way and we are in a better place than ever.
And look, we even have stickers!!!
I’m also learning a lot from the React Meteor integration. It helps me a lot and we share a lot of knowledge to move us all forward.
Building a Community inside the larger Javascript Community
So now that we have the one great stack to be aligned on, we can think about how to improve it.
We can push forward ideas from Angular like Typescript and dependency injection so that the whole Meteor and Javascript community will benefit.
Here is a list I’ve made few months ago for things that I think Meteor and Angular should collaborate on. Both communities should push for those ideas and make the core team members consider them.  PRs and actual code always makes a larger impact...
It’s a combined effort for all of us.
For example - It is strange for me that the Angular Meteor Socially tutorial is one of the most comprehensive full stack Angular 2.0 tutorials out there and in my mind not enough Angular 2.0 developers have tried it yet…
We continue working on the tutorial to create an essential place to learn Web development with
Angular2/Meteor. Our ultimate goal is to make it so clear and neat to become one of the favorite places on Internet to learn Web development from scratch.
Another place we could do more is helping the largest Meteor open source apps like RocketChat and Wekan.io become more aligned with the stack we believe in.
But please don’t assume any of these things will be done without your direct help and work.
Any help would be appreciated.
if you want to help but don’t know how - feel free to contact me directly.
The Angular Meteor work is not done by me alone. I’m getting huge amount of great, real-work help from people from the community like @barbatus , @dotansimha , @kamilkisiela , @DAB0mB and many more..  (Hell, we even got PRs from @IgorMinar !!!) and I keep mentioning all of them with every release I make (learned that from the Angular team).
They all contacted me directly through email and we are talking almost daily to plan our work.
Remember - my personal email is public on my Github profile and if you need to contact me in regards of thoughts, suggestions or anything else, please do not hesitate.
Also, I’ve updated our roadmap into Github milestones (Angular1.x, Angular 2.0) so you can follow and help more easily.
As developers who know both technologies, we could have a huge part in bringing the two communities together to create a shared conversation that pushes the whole Javascript community forward.
The future of Meteor (and Angular)
On both sides, Angular and Meteor, we should do more so that the stack will move forward -
On the Angular front, I think the Angular community and team should be focused almost entirely on mobile.
The team is doing great things with Web Workers and Animations and we should help there. The community should create Components that are targeted to mobile.
Ionic 2.0 is amazing, it alone is not enough.  NativeScript is not enough. The current Angular 2.0 and React Native integration are not enough.
We should create real app scenarios and benchmarks to test and show the current state of the art, like creating a Google Inbox clone in Angular 2.0.  fancy numbers are not convincing enough.
We are also working to get more involvement from the core Angular team promoting Angular 2.0 in Meteor meetups, forums and blogs.
We should do the same with the core Ionic team promoting Ionic 2.0 (@adamdbradley , @mlynch , @bensperry).
On the Meteor front, in the last months we see huge progress to address the largest things we care about - mainly embrace npm and a new data integration.
Meteor 1.3 is a huge step for being more aligned with the rest of the Javascript community and npm. @benjamn is leading a phenomenal work that I think the whole Javascript community should be aware of.
On the data front, Meteor is again leading the way with creating a Reactive GraphQL app data solution (must read).
This is an amazing work which takes into considerations all the things we learned from Meteor over the years and embraces ideas from Facebook like Flux, Relay, Redux and GraphQL to create the future of app data management.
And Meteor is doing it in a way which is both Front End agnostic so that we could use it with Angular 2.0 or React and DB agnostic so you could use it with SQL, MongoDB or REST.
This work is maybe the most exciting work that is happening in all the Javascript community, and it is being done in collaboration with the relevant teams at Facebook.
Forks
People are talking a lot about the forks of Meteor.  I think that’s the best thing that could happen to Meteor!!
That means that the Meteor community has matured enough to have highly professional members that can implement their great ideas in the open.
Meteor can learn from those ideas and decide what things it should or shouldn’t use in future versions.
It also gives the community more choices and confidence around the overall solution.
This is the best time for being an Angular Meteor developer. Let’s make it even better together.
Now is the time for Angular Meteor.
P.S.
This comment is meaningless if it won’t be shared around the Angular, React and Meteor communities…..
Let’s put our energies where we can influence the most.

Thank you @Urigo for the most extensive and encouraging answer.
My original post was written well before Meteor 1.3 was out, and at that time, as the Meteor community influencers started leaning towards React, more and more packages were converted to Atmosphere to help use React with Meteor, and very few Angular packages were converted to Atmosphere.
Fortunately, Meteor 1.3 took care of that when it included npm, so now any Angular package can be used with Meteor. Although the npm utilization is not yet complete because css assets are not automatically imported to Meteor from npm packages.
Now, the Angular-Meteor community is pretty much self-dependent. Meteor provides us with the fantastic backend and we can let our imagination fly using all the benefits from the vast npm world.
Regarding the Meteor Forum, it is a self-doomed project because of the nature of Meteor itself. It doesn't do server side rendering, so topics on Meteor Forum are not visible to Google crawlers, so no results come up in search. I've solved 99% of my Meteor problems from Stackoverflow, but not from Meteor Forums. I simply don't have the habit of visiting it. I came from Angular world to Meteor world, so never had the habit. Finally, this is probably one of the most important thing missing to totally round up the Angular-Meteor story --- the server-side rendering.
Thanks again! I will probably write more, once I chew up again on what you wrote. :)

@MilosStanic keep going with Angular 2. I walk between both Angular2-Meteor and Meteor-React. So I know why people recommend React.
I agree that React is using JavaScript to generate HTML is indeed flexible and I love this too. But this has price. My feeling, it starts to become hard to maintain if you have a over 10k lines of code project.
Then Redux this data pattern comes out to solve that. But you can use Redux with Angular 2 ngrx, which work great.
There is a team in Google creating Angular 2, they carefully selected router, form validation, everything and put them together. In the mean time, React only some main people are maintaining.
For meteor-react, let's use router for example, before they use flow-router, now they think to turn to react-router, but yesterday I saw this React Router is dead. Long live rrtr. They are all community individual support, not like Google a strong team support.
The feeling using React is more like Individualistic Heroism, you choose every thing by yourself. You have power. It shows freedom. But it takes too much time to make every parts work together well. And those main people in react community are also like Individualistic Heroism: those main individuals are maintaining different individual part of React ecosystem. Meteor-React is same, and Arunoda is a main person (Think about what if one day Arunoda left Meteor-React?). So you cannot always rely on one person. You need rely on a team.
Angular 2 is from a GROUP of Google genius, and also some same other BIG groups like Valor Software responsible for different parts.
One advantage of React ecosystem is free to choose different part, but this has price too. Everyone uses different parts, which makes the community grow slow, because hard to share experience, hard to choose some core module to improve. So they try to make a standard Mantra. Then what is the difference with Angular 2? Besides every parts in Angular 2 are carefully chosen by Google strong team. Angular2-Meteor is also similar. It has a reliable team @Urigo @barbatus @dotansimha @DAB0mB. (Seriously, guys, where are you from? Why all of you can speak Hebrew?)
Right now, the only thing for angular2-meteor I want it to be improved is fast rendering.
I can feel Angular 2 is a really carefully designed project, it already learns almost all good parts from React ecosystem.
Typescript for me seems a clear way, type definitely helps a lot for maintaining when the project is BIG.
RxJS is also a good selling point.
Before I always think why Angular team keeps updating Angular 1 like React. Now I think it is the right decision to create Angular 2 as a brand new instead of keeping improve Angular 1. It is hard to provide a revolution project if just keep updating Angular 1.
@dotansimha I saw you answer the question why choose Angular 2 over React in this video, I would love to give a more clear answer next time, because I have used both Meteor-React and Angular2-Meteor. :)
So my preference now is angular2-meteor > meteor-react > angular1-meteor.

@Urigo happy to help how we can. Don't really agree that what the ecosystem offers isn't enough, plenty of people being successful with all those tools (including Ionic 2). Of course, tons of room to improve.

@MilosStanic why do you think Meteor forums are not crawlable? we use Discourse and it is crawlable..
But I think Stack Overflow is always better for questions, Github Issues are for bugs and feature requests and Meteor Forums for discussion like the one we are having here.
About SSR and fast rendering, it is closer than ever, probably a first working version next week..
@Hongbo-Miao I agree that we can answer the React-Angular question in a better way, maybe you should go to a Meetup and give a lecture on that!
@mlynch I agree, I'm using Ionic and Ionic 2.0 in so many projects and loving every second of it.  it really, without a doubt, made me personally more successful.
I think that showcase apps - maybe an Inbox clone, Facebook's Paper clone,  would make things easier, both for the developers and for convincing large companies to move from full native apps
Facebook made a great move with the F8 app

@Urigo yeah, that will be great, I can show some cool stuff especially when using Angular 2 with Meteor.

@Urigo I thought Meteor forums were not crawlable simply because when I search Google for Meteor stuff, they never appear in results. That, and knowing the issues with crawlability of Meteor apps, was the reason I made that conclusion.
Great news about SSR and fast rendering. Can't wait for it!

Discourse forums are indexable, but maybe don't rank as well as they could. All the content is between noscript tags, which is not ideal for SEO. This is a problem with a lot of newer forum software. (Discourse, NodeBB, Flarum, etc.)

@Urigo glad to hear that 😄 👯. And yes, we need to put out more awesome demos, it's a priority for me this year. We started with a conference app demo a few months back (I suppose F8 has validated/overshadowed that now :P) https://github.com/driftyco/ionic-conference-app
Also, we run a popular discourse forum and so far SEO has been solid.

Also, we run a popular discourse forum and so far SEO has been solid.

You can get indexed and even rank with Discourse, but it's unlikely that it will do as well as a site that renders full HTML. Links within <noscript> appear to not pass "link juice" well. SPAs can also be indexed (even without the _escaped_fragment_ parameter now), but I don't think that they tend to rank well either.
(The distinction is indexing vs. ranking -- a site can be indexed perfectly while still not ranking as well as it could.)

@mlynch I wasn't aware if that app, looks really really nice!

@j127 in theory I agree, but in practice we've been nothing but very happy with ranking and Ionic forum posts. I can see it being suboptimal but also "good enough" and a large amount of our traffic comes from search (and a lot of it)

In other news - my post on the official Angular blog is up - https://twitter.com/angularjs/status/723019578264014848
Would love some social sharing love ;)

thanks everyone for the great discussion.
closing, but we can keep on talking ;)

Hi all, @Urigo,
@Hongbo-Miao has pointed out a poll running on Meteor forums here that reinforces the fears that I expressed in the original post about Meteor community leaning strongly towards React.
The results of the poll reflect the fact that overwhelming majority of people uses React in such a proportion that is not present in the general population of JS programmers outside Meteor stack. What's more, it appears the same proportion of people are using Vue as Angular. Which is certainly not natural distribution outside Meteor world.
So, please give a vote at the above link. Let's make numbers better! :)
Offtopic: looking at another topic at Meteor forum, which is linked to the poll topic above, I stumbled upon @stubailo 's reference on Angular-meteor tutorial "unfortunate" use of allow/deny pattern to restrict access to database. I've never heard of this before, so I'm asking you to fix this in the tutorial. Have a look here. Uri, I hope Sashko has pointed out this to you.
Btw, I hope SSR and stuff Uri announced earlier lands soon to angular2-meteor.
Cheers.

The results of the poll reflect the fact that overwhelming majority of people uses React in such a proportion that is not present in the general population of JS programmers outside Meteor stack.

I think this actually reinforces @Urigo's desire to merge the community back into the general Meteor one. If Angular-Meteor stays separated from the regular Meteor forums, etc. then their views won't be represented in that venue. So I encourage more people to post about Angular on the Meteor forum, let your opinions be heard!

I stumbled upon @stubailo 's reference on Angular-meteor tutorial "unfortunate" use of allow/deny pattern to restrict access to database.

I don't think this is a big deal, it could be a fine way to start learning Meteor, and many people use this approach in production. It's just not the approach recommended in the Meteor Guide.

@MilosStanic you know I came from React. The more I learn about Angular 2, the more I love it.
I have a Suggestions for React people at the end. It is fun~
(At that age, Angular 1 is amazing. After React comes out, compared with React, Angular 1 is bad. Now Angular 2 actually I feel they totally changed a name, because it is too amazing!)
React for me is just one small library, which can be easily used in Angular 2 as a component when you needs.
Angular 2 is sooooo powerful (RxJS powered) and it is a future product (TypeScript include ES7 features like Decorators and has its own Type) which saves me a lot of time to write codes.
When I went back to ES6, I feel my codes so ugly. (If you are using ES6 now, the feeling is like going back to ES5).
1. TypeScript (ES7 + Type)
1) ES7
Decorators are in ES7, you like it, right? And more ES7 feature
2) Type
Type from Typescript is amazing too! I am using WebRTC in my project. I have an example of myself. Before I have some codes like this:
const configuration = {
  'iceServers': [{ 'url': 'stun:stun.1.google.com:19302' }]
};

I have an error actually, but I didn't notice that, after I adding typings file, adding "RTCConfiguration" here, I found the error: I should use "urls" like below instead of "url". It saves me a lot of time to find the error.
const configuration: RTCConfiguration = {
  'iceServers': [{ 'urls': 'stun:stun.1.google.com:19302' }]
};

2. Shadow DOM
I really like Angular 2 is Shadow DOM.
1) Handle CSS-style collisions
In each of your component, you can use same name for you CSS, right? And they won't affect each other.
When a lot of people work together, they write their own components, and the codes they write won't affect each other.
2) Handle JavaScript collisions
I am using D3.js, for example, I have a
<svg class="line-chart"></svg>

in one of my component.
D3.js is kind of like jQuery. Usually when I select, I do
const chart = d3.select('.line-chart')

Since React does not support Shadow DOM, I cannot easily reuse. If I want to use twice, I need do <svg class="line-chart1"></svg> and <svg class="line-chart2"></svg>. Imagine I need 10, or even 100 similar charts...
In Angular 2, things become amazing!
When I reuse this component, I just need do
const chart = d3.select(this._element.nativeElement).select('.line-chart')

When I reuse this component, they won't affect each other.
3. RxJS 5
I don't want to say more, this is just tooooooooooooooooooo powerful.

When most React people are still excite about Promise, we already start to use RxJS 5 (which is called Promise++), and we are using RxJS 5 (not 4).
4. Some of my old talk
Also, I wrote here before, just copied some parts below:
Most people saying they like React more, actually they never tried Angular 2. So don't listen to them.
It is like a threshold, React's is low while Angular 2's is high. React is so easy to start, so most people just start to use it. For Angular 2, you need learn more to start to use it.
 React is quick to start.
If you plan to build a large project in the beginning, I would recommend Angular 2.
Read this article to see why Minko Gechev's team goes with Angular 2 instead of React for their new product.
Alibaba, who owns Taobao.com, used React for their website. But now their new product websites also start to use Angular 2.
Avoid living in a certain technology ecosystem. Always be open to new technologies, otherwise you will fall behind without knowing that. New technologies coming out always have reasons.
5. Suggestions for React people
Please, spend some time and go out of React ecosystem and see the new world. You already fall behind and you just didn't realize. We have a word 井底之蛙(The frog of the well). The story is below:
The frog lived down in a well where there was all he had to live. One day, a softshelled turtle came by and told him about the sea. 'The sea? Hah! It's paradise in here. Nothing can be better than this well. Why don't you come down and share my joy?'

@MilosStanic I'm sorry but I hate polls and I hope to never base my decisions on those :)
I have a vision that I believe in and if someone sees that now that great.  if not, that's fine as well, most likely they will see it in a few months ;)
As for popularity, I can't assure you we are better than ever, here is a screenshot of the Google Analytics of the Angular-meteor.com website:

As you can see, the trend if moving for our advantage, in my mind mostly because the Frameworks (Meteor and Angular) are pushing and doing things in the right direction.
@ThomsCass I feel your pain.  I know the first versions of angular-meteor 1.3 created a mess, and you can see that it even reflects on the Analytics.
I take full responsibility on that and now we are at a much better place, you can feel safe using angular-meteor 1.3.10 with the new or the old syntax and everything will be fine.
But I also think that if you want to use React that's fine and good for you, it's most important that you will be successful and earn money doing the things you want.
I will always welcome you back to the community and would love to help in a any way making you successful, whether in Angular or React.
@Hongbo-Miao I love your post, it makes a lot of sense.
About the Allow/Deny thing, my goal and my vision is to have a platform that let you build a first app or first MVP and in the fastest way possible, whether you are experienced developer or not, and then when you want to scale, code size or traffic you know exactly what to do.
That's why I think Allow/Deny is a good thing and not unfortunate.
When your app will get to a place where this is an obstacle, you know exactly what to do with the help of the great Meteor guide (and future chapters of Socially) and it means the MVP version of your app got you in a good place.
I hope my opinion makes sense...

@Urigo you're a true inspiration for the community. Thank you for all your work.
The only thing I wish was better is having some sort of clear roadmap. Knowing which features are planned, for example testing framework, SSR, angular-universal, progressive web apps, etc. And a loose timeframe for those. Particularly for Angular2-Meteor.
None of us, obviously plans giving up angular2-meteor, because of all the clear benefits it has over other fullstack solutions.
Keep up the good work, and thanks again.

@MilosStanic about a Roadmap, I don't want to duplicate something from Github Issues so I think we would go back to Waffle.io here - https://waffle.io/Urigo/angular-meteor
I will prioritize it and tag issues this week to make it a bit more clear and would love your help in that.
Timelines are hard to estimate but I'll try better at predicting them...
If there are things there that are not specified you can open an issue for those and they will be added there automatically

@MilosStanic @Urigo god I was away on a project for 3 months and I'm back in the meteor landscape and damn stuff is happening.
Polls don't mean anything most people don't participate if they even here about it I run 3 meteor apps in production and a few more in the pipe line using angular2/meteor/angular1 and it's taken nearly 20 days to find that poll, it's not representative of the overall community. Some people just quietly sit by the side lines without ever voicing an opinion either way. I do love Angular and personally loath React, so my opinion is a tad biased but I've been following Meteor and Angular for over a year now and we've all come a long way I can't agree more that we should be more active on the meteor community forums i'm the first person to jump into the Gitter rather than the forums for help since it feels more dynamic.
I'd also like to thank @Urigo  personally for all the evangelism and coding he's done so far on this.
Chris


Game sometimes freezes when equipping items and requires a restart

I think it may be something to do with the game not handling the character preview render in the inventory when it has to change the items.

That's a well-known client-side bug that we cannot fix because we're not editing the client.


Update look and feel of vega.trading interstitial page

The Chore
The page is in this repo here https://github.com/vegaprotocol/ipfs-redirect
Currently looks like this:

We'd like it to look like this:

The content is changing here too ... there is a draft here


stdio.h should be included in include/gdrapi.h

it seems that stdio.h is not included in the header mentioned above which can yield error messages such as:
common.cpp:40:26: error: ‘stderr’ was not declared in this scope
                 vfprintf(stderr, fmt, ap);
                          ^
common.cpp:40:41: error: ‘vfprintf’ was not declared in this scope
                 vfprintf(stderr, fmt, ap);```

adding that header fixes it.

Hi @azrael417,
Thank you for reporting this bug. The bug should have been fixed. Can I ask you to try and close this issue?

yes, thank you, looks good now.


can't build

Describe the bug
when i execute  "pnpm run build ",i meet this error:
To Reproduce
./components/ChatWindow.tsx:4:26
Type error: Cannot find module '@langchain/core/documents' or its corresponding type declarations.
2 |
3 | import { useEffect, useState } from 'react';

4 | import { Document } from '@langchain/core/documents';
|                          ^
5 | import Navbar from './Navbar';
6 | import Chat from './Chat';
7 | import EmptyChat from './EmptyChat';
 ELIFECYCLE  Command failed with exit code 1.

i am already solve it,just reinstall these package:
pnpm i @langchain/community
pnpm i @langchain/core
pnpm i @langchain/openai


Action types from passed through to subscribers would allow us to scale better

Do you want to request a feature or report a bug?
Submit a PR but discuss a feature first.
What is the current behavior?
Listeners that are subscribed to from an instance of the store don't have action types passed to them as a parameter when dispatch is called.
What is the expected behavior?
It would definitely be helpful to us if we wanted to scale out our listener(or make it smarter) using action types as a parameter, the reason I say this is because I believe we can re-use our current event structure to do more focused view binding updates when it comes to angular after actions are dispatched through the store. For now we only have a single listener that will trigger a rebind for everything in the view that is bound to the store, this does not feel optimal to me. I hope to partition things using action type. We also make extensive use of reselect but I think it abstracts our scaling needs to our selectors which just does not feel right because we use this in the view for things like formatting and composition. We also debounce our listener which I am hoping this feature will give us the ability to remove at some point.
The change is here: https://github.com/fir3pho3nixx/redux/commit/764cbf5159e086417e6c09567f4099cddf7da79c
Look forward to your feedback/questions.

https://github.com/reactjs/redux/issues/1971#issuecomment-248362831

@timdorr
I get what you are saying about not having to deal nested dispatches because you basically don't want to become a message bus, but you should at least allow the meta data to flow through. Let's please just make sure we are grounded in the fact that we are still coding in javascript and not haskell.


Revert "feat(builder): bypass nodes"

Reverts tctien342/comfyui-sdk#11

Revert back to prev 0.2.28 ver


java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 at org.flywaydb.core.internal.configuration.ConfigUtils.(ConfigUtils.java:61)

Which version and edition of Flyway are you using?
flyway open source 10.0.0
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API on a Kotlin project.
Which database are you using? (Type & version)
Postgresql 16 or 15. It doesn't matter.
Which operating system are you using?
Ubuntu latest.
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
It fails in the docker container when trying to load the database to run the migrations.
Gradle configuration:
    implementation("org.flywaydb:flyway-core:10.0.0")
    implementation("org.flywaydb:flyway-database-postgresql:10.0.0")

Connection.
        val flyway = Flyway.configure()
            .driver(DATABASE_DRIVER)
            .dataSource(jdbcUrlString, config[Db.user], config[Db.pass])
            .defaultSchema("public")
            .validateMigrationNaming(true)
            .validateOnMigrate(true)
            .load()

        flyway.baseline()
        flyway.migrate()

It fails on an internal library code.
app  | Exception in thread "main" java.lang.ExceptionInInitializerError
app  | 	at org.flywaydb.core.api.configuration.ClassicConfiguration.configure(ClassicConfiguration.java:1414)
app  | 	at org.flywaydb.core.api.configuration.ClassicConfiguration.configureFromConfigurationProviders(ClassicConfiguration.java:1854)
app  | 	at org.flywaydb.core.api.configuration.ClassicConfiguration.configure(ClassicConfiguration.java:1285)
app  | 	at org.flywaydb.core.api.configuration.ClassicConfiguration.<init>(ClassicConfiguration.java:224)
app  | 	at org.flywaydb.core.Flyway.<init>(Flyway.java:111)
app  | 	at org.flywaydb.core.api.configuration.FluentConfiguration.load(FluentConfiguration.java:59)
app  | 	at .app.infrastructure.database.Database.init(Database.kt:24)
app  | 	at app.ApplicationKt.main(Application.kt:96)
app  | 	at app.ApplicationKt.main(Application.kt)
app  | Caused by: java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
app  | 	at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
app  | 	at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
app  | 	at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
app  | 	at java.base/java.util.Objects.checkIndex(Objects.java:359)
app  | 	at java.base/java.util.ArrayList.get(ArrayList.java:427)
app  | 	at org.flywaydb.core.internal.configuration.ConfigUtils.<clinit>(ConfigUtils.java:61)
app  | 	... 9 more

Docker container from openjdk:17 and application build with gradle 8.4 jdk 17
What did you expect to see?
Migrations running properly.
What did you see instead?
Error on internal flyway library.

We have a similar setup and we are experiencing the same issue when upgrading from version 9.22.3. We use the Java API in a Kotlin project, JDK 17, gradle 8.3, flyway 10.0.0 and Postgresql 14.9.
        Flyway.configure()
            .dataSource(dataSource)
            .load()
            .migrate()

I think the exception originates from this, but I haven't figured out why the list is empty:
    public static final Class<? extends LicensingConfigurationExtensionStub> LICENSE_CONFIG_EXTENSION_CLASS = new FluentConfiguration().getPluginRegister()
                                                                                .getPlugins(LicensingConfigurationExtensionStub.class)
                                                                                .get(0)
                                                                                .getClass();

Hi @AlejandroYuste @tiafiring , it looks like both of you are using Flyway in a Kotlin project.
Can this issue be reproduced if you use Flyway API through any Java project?

I don't know :/
Does this mean kotlin is not supported? That's weird as everything gets compiled as part of the same java byte code...

@AlejandroYuste I am trying to find out more information to help. Although your statement about Kotlin and Java byte code basicly being the same, this is to do with Service/Class Loading. Would you be able to tell us what specific JRE you are using? This should help to resolving this.

Hello!
Nope, I was trying to add flyway for the first time. I tried different versions and I got the same error from all of them.
It doesn't happen when I run the project locally. It only happens when it runs inside a docker container. Here is the Dockerfile:
FROM gradle:8.4.0-jdk17 AS build
COPY --chown=gradle:gradle . /home/gradle/src
WORKDIR /home/gradle/src
RUN gradle buildFatJar --no-daemon

FROM openjdk:17
EXPOSE 8080:8080

RUN mkdir /app
COPY documentation/swagger.yaml /app/documentation/swagger.yaml

WORKDIR /app
COPY --from=build /home/gradle/src/build/libs/*.jar /app/
ENTRYPOINT ["java","-jar","/app/app-all.jar"]

I tried lots of different images with java 17 and it failed for all of them.

We are currently using flyway version 9.22.3 without any problems in my project. When upgrading to 10.0.0 or 10.0.1 we get the same error as @AlejandroYuste .

Same here. Working fine with 9.22.3, but getting the error above when upgrading

Hi @klundby , are you also using Flyway in a Kotlin environment or a Java environment ?

This is in a Kotlin environment

We have the folllowing depdency in a pure java-maven project creating a runnable jar with maven-assembly-plugin:
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-postgresql</artifactId>
    <version>10.0.1</version>
</dependency>

The problem is that both flyway-database-postgresql and flyway-core has a service loader file with the same name (META-INF/services/org.flywaydb.core.extensibility.Plugin). Only the one in flyway-core includes LicensingConfigurationExtensionStub.
The maven-assembly-plugin only adds one of the files. In our case only the one from flyway-database-postgresql was included (which does not include LicensingConfigurationExtensionStub)
The application runs fine from the IDE.

Same issue here

Hi @attiand , so many thanks for the findings.
Does this mean your project does not include dependency on flyway-core?

@JasonLuo-Redgate, Yes flyway-core is included as it is a depedency for flyway-database-postgresql.

Hi @attiand , just would like to know more info. Is there any specific reason why you prefer not to include flyway-core directly?

Hi @JasonLuo-Redgate. No I'm just lazy, the effective pom will be the same.

Hi @attiand , thanks to your detailed description, I can locally reproduce this issue now.

We had the same error, seems to be related to service definition META-INF files, as @attiand mentioned.
For us adding
tasks.withType<ShadowJar> {
    mergeServiceFiles()
    archiveBaseName = project.name
    archiveVersion = ""
}

to our build.gradle.kts fixed the issue
We had both flyway-core and flyway-database-postgres as direct dependencies

either

I had both dependencies: core and postgresql. I tried today to remove the core one and I got the same error.


removed unused variable;

Caught this in Visual Studio on a project where I have unused variables set to errors.

Thank you, merging this in a sec


mistake fix

Thanks @Fell-x27. Can you change the commit message to: typo fix in doc/stake-pool-operations/query_stakepool.md

Should be better now

@Fell-x27 Can you squash the commits?


Fixes a bug: currency converter never shows error message for service failures

Fixes: currency converter never shows error message for service failures
Description of the changes:

Before the fix,  CurrencyDataLoader always discard and register a new NetworkBehavior even if it doesn't really take action to load the data. This results in many redundant callback invocation which force the state gets reset so that the VM reset the error message back to normal state immediately.
After the fix, the NetworkBehavior will only be registered when the loader decides to take real actions to load data.

Screenshots
Before the fix:

After the fix:

How changes were validated:

Tested manually

The "CurrencySecondaryStatus" TextBlock is not rejuvenated. Could you please remove the "SemiBold" FontWeight and update the Margin to "3,6,0,0" to make it look better with others?

The CI pipeline failed on unit test. Could you please take a look?

The CI pipeline failed on unit test. Could you please take a look?

No worries, some flaky tests occurred during UI tests.
Rerun the checks and all passed.


PRL-6206 - Dummy Frontend PR for testing citizen dashboard

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Dummy PR for testing, closing it


Increase the maximum number of supported dependencies

I find this library extremely useful however currently it is limited to maximum of 9 dependencies. Can we increase this number to say 20?

Hello @vminc, glad you find the library useful. The original reason to limit the number of dependencies was to shorten the build times. But with further optimizations and compiler hints it looks like it can be increased.
Although I haven't have the need for more than 9 dependencies in my projects, would you mind to share your use case?

Thanks. My use case isn't particularly special. I just find that in rare cases the number of dependencies I have for a class can go up to 10-11. Currently I have to get around this in a hacky way by wrapping half of the dependencies into a wrapper class.

@vminc I would describe your solution of wrapping them in a wrapper class to be the actual best solution. Its often suggested that having too many dependancies is a sign that the class is too large and complex, and should likely be broken up into smaller classes.

Included in v2.0.1


Server Error when trying to launch a satellite

Version of Advanced Rocketry
AdvancedRocketry-1.12.2-1.4.1-108-universal
Have you verified this is an issue in the latest unstable build
N
Version of LibVulpes
LibVulpes-1.12.2-0.2.8-39-universal
Version of Minecraft
1.12.2
Crash report or log (if applicable)
https://gist.github.com/JamieH/429a2e4de619ffb0293368f65dbc91e7
Description of the problem
Built a satellite and tried to launch it - threw an error on the server then tried to break it and it went invisible

Can you test the latest (or at least 111+) build with this, there was some packet handling stuff fixed in 111.
Secondly, are there any other mods in use, if so, does this occur without ther other mods?

We're playing the All the Mods 3 Remix pack so I guess they need to update the version of the mod

It would help us see if this is fixed in the newer versions if you could test this for us. If you're unable to, I'll see if I can figure out what causes this somewhere next week.

@zmaster587 @martmists I downloaded:
AdvancedRocketry-1.12.2-1.4.1-108-universal
LibVulpes-1.12.2-0.2.8-39-universal
Tried with the same satellite, didn't launch, also the select destination button caused an error: https://gist.github.com/JamieH/f5ae3c8559f0d9848d76d2d84c83fdf7

Try with https://minecraft.curseforge.com/projects/advanced-rocketry/files/2641964
And https://minecraft.curseforge.com/projects/libvulpes/files/2633668
Sent from my iPhone

On Dec 2, 2018, at 5:44 PM, JamieH<EMAIL_ADDRESS>wrote:
@zmaster587 @martmists I downloaded:
AdvancedRocketry-1.12.2-1.4.1-108-universal
LibVulpes-1.12.2-0.2.8-39-universal
Tried with the same satellite, didn't launch, also the select destination button caused an error: https://gist.github.com/JamieH/f5ae3c8559f0d9848d76d2d84c83fdf7
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Still broken...
Select Destination: https://gist.github.com/JamieH/8154665ff81529ba1c9093201654cd23#file-gistfile1-txt
Trying to launch: https://gist.github.com/JamieH/8154665ff81529ba1c9093201654cd23#file-gistfile2-txt

The "select destination" one looks to be a seperate issue (selecting destination without a guidance computer).
there was a missing isRemote check for when launching from a monitoring station, that should be fixed in the upcoming build.

This seems to be fixed, do you have this problem on the latest builds? Please test and close the issue if you do not.


No way to set a timeout which can cause app to hang during an outage

Hello,
I was looking into setting a timeout for requests made with the hellosign python sdk so that our app can handle Hellosign outages more gracefully and timeout instead of hanging forever, but from what I can tell from the documentation and source code, that does not seem possible right now.
I am happy to submit a PR for this, but I wanted to make sure this repo is still actively maintained before investing the time to do that- it looks like the last commit to master at the time of this writing was on March 31: https://github.com/hellosign/hellosign-python-sdk/commit/43b0a5af6ee1d12572a7c370ec37c8ad033c6ca2

+1

Hi @realplatanopapi, I'm currently the maintainer for this repo and yes it is still actively maintained. Feel free to create the PR for this feature, I will discuss with the team to prioritize this request.


keywords is not included in devContainerFeature.schema.json

The documentation for Features on containers.dev lists keywords as a possible value for the devcontainer-feature.json file. That entry is not included in the schema file though. Is this an error with the documentation and keywords are not actually meant to be included (anymore?), or is this something that's missing from the schema?

Thanks for opening this! @joshspicer I think this is just missing from the schema, but please let me know otherwise!

With the new release of @devcontainers/action v1.4.1, this should be fixed, thanks! ✨
@nifr Feel free to reopen if you are still running into this issue!


ipfs.cat example on website not working correctly

Version:
commit: "55cb49900"
golang: "go1.15.15"
ipfs-http-client: "1.0.0"
repo: "11"
system: "amd64/linux"

Platform:
Chromium Version 93.0.4573.0

Subsystem:

Severity:
High
Description:
I copied the example from the website to retrieve content from IPFS in browser via JS
Steps to reproduce the error:
const stream = client.cat(
            'QmPChd2hVbrJ6bfo3WBcTW4iZnpHm8TEzWkLHmLpXhF68A',
);
let data = '';

for await (const chunk of stream) {
   // chunks of data are returned as a Buffer, convert it back to a string
   data += chunk.toString();
}
console.log(data);

this code snippet using "ipfs-http-client": "^53.0.1" will not print a string as shown on the website. It returns an array of ints:
72,101,108,108,111,44,32,60,89,79,85,82,32,78,65,77,69,32,72,69,82,69,62
Also I did not find any solution yet to simply return a string value of the content from IPFS. Can somebody please check this?

The example on https://js.ipfs.io/ needs updating. PRs welcome :pray:


Developer ID signed Mac apps using SSKeychain constantly log errors.

Hi Sam!
Thanks so much for SSKeychain, it's a huge help. I am working on a developer ID signed Mac app at the moment and I noticed that every time I call an SSKeychain method, I am getting the following logged in console:
2015-02-19 4:35:36.855 PM secd[327]:  securityd_xpc_dictionary_handler Top Hat[68317] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
2015-02-19 4:35:36.855 PM Top Hat[68317]:  SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))

The issue is that this is not a Mac App Store app, so it has no entitlements file. SSKeychain is defaulting to using keychain synchronization and secd is having none of it. The app continues to work as expected but it's not ideal to be dumping stuff in logs. A work-around is to avoid the convenience methods on SSKeychain and use SSKeychainQuery directly instead, configured to SSKeychainQuerySynchronizationModeNo.

Hm. Is there a way to detect this situation so we can have a better default?

Top Hat looks great by the way :grinning:

Hmm, I'm not really sure what a good way to detect it would be. https://github.com/ole/NSBundle-OBCodeSigningInfo is an option but he says not to actually use it, so it's probably not a good idea.
I'd be totally happy with:

An interface to change the default that's used by the SSKeychain object. (I'm using CocoaPods, so I can't just tweak the define to turn it off.)
A more error logged to the app's console giving a hint about what's up; these ones appeared in the system log, so I didn't catch this until we shipped.

It's not actually causing any problems that I know of, except the log messages, but it did send me the wrong direction for a while when I was hunting another bug.

Also, thanks for the nice words about Top Hat! 💖

Good call. Can you PR those with tests? :heart:

It’ll be a few weeks (at best) before I have time to look at it. My wife is due to have a baby next week so life is going to be crazy for a while.

On Feb 22, 2015, at 5:19 PM, Sam Soffes<EMAIL_ADDRESS>wrote:
Good call. Can you PR those with tests?
—
Reply to this email directly or view it on GitHub https://github.com/soffes/sskeychain/issues/88#issuecomment-75477628.

Congrats! No worries!

I've just run into this and have started getting some negative reviews for my companion app because of the logging :/ any ideas on how to sort this or should I just wait and watch? (Side note, glad it's not just me)

Great. Thanks @KaneCheshire!


fix(ci): Use ubuntu image instead of true

Issues
Fixes #
Reviewer Suggestions
Where should the reviewer start?
Additional Comments
Anything else?

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


[top-app-bar-fixed] div.mdc-top-app-bar--fixed-adjust element should be sizable

I'm submitting a:

[ ] bug report
[x] feature request

Current behavior:
If you size <mwc-top-app-bar-fixed> so that it's 100% height, the inner div.mdc-top-app-bar--fixed-adjust element is not sized the same, so that if you give a background to the slotted content element, the background doesn't actually affect the entire content area.
Expected behavior:
The div.mdc-top-app-bar--fixed-adjust element should be an implementation detail, so it should be at least default sized to cover the full content area. There might be use cases where devs need to style the element too (flex box or grid?).

Is there a recommended way to use mwc-top-app-bar in a full-screen application? Specifically, I'd like its content slot to extend from the bottom of the app bar to the bottom of the viewport.

Obsolete in M3


Changes to support classic BP

Ah, forgot about those few souls still with their own main program and no Project!
I make the code more robust when no project has been set, and now you can do this if you want.
There's now a test script for this, though you have to run it separately from the whole test harness.

Ack. Ship it 😀
On Sep 24, 2018 8:10 AM, "Tom Swirly"<EMAIL_ADDRESS>wrote:
Ah, forgot about those few souls still with their own main program and no
Project!
I make the code more robust when no project has been set, and now you can
do this if you want.
There's now a test script for this, though you have to run it separately
from the whole test harness.
You can view, comment on, or merge this pull request online at:
https://github.com/ManiacalLabs/BiblioPixel/pull/982
Commit Summary

Changes to support classic BP

File Changes

M bibliopixel/animation/animation.py
https://github.com/ManiacalLabs/BiblioPixel/pull/982/files#diff-0 (15)
M bibliopixel/drivers/SimPixel/driver.py
https://github.com/ManiacalLabs/BiblioPixel/pull/982/files#diff-1 (3)
M bibliopixel/drivers/driver_base.py
https://github.com/ManiacalLabs/BiblioPixel/pull/982/files#diff-2 (6)
M bibliopixel/util/threads/animation_threading.py
https://github.com/ManiacalLabs/BiblioPixel/pull/982/files#diff-3 (4)
A scripts/release_test/tests/classic.py
https://github.com/ManiacalLabs/BiblioPixel/pull/982/files#diff-4 (30)
M scripts/release_test/tests/rest.py
https://github.com/ManiacalLabs/BiblioPixel/pull/982/files#diff-5 (0)

Patch Links:

https://github.com/ManiacalLabs/BiblioPixel/pull/982.patch
https://github.com/ManiacalLabs/BiblioPixel/pull/982.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/982, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6h0ALnDndZ2tjTSDq5Jvgh_dXuhnks5ueMuZgaJpZM4W2iAJ
.


Notify users how long before the data has been saved on UI

User story
Re: Earth is basically auto-save, but it doesn't know if the current operation is saved or not.
By implementing the feedback from the service "Autosaved OO seconds ago", you can know how far you are currently saved and edit with confidence.

The visualizer shows a loading animation while saving data now. User can check when it is saving date or not.


Create and Style Contact Info Section

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Reviewing and refining the content.

Finished the intro. Please review and provide feedback if necessary.


IP, IPP, IGC values not saved to data file

Describe the bug
The IP, IPP, IGC values are not saved to data file but are saved as 0.0 for each one.
To Reproduce
Steps to reproduce the behavior:

Save project
Open data file
search for the values IP IPP or IGC
Values are 0.0 instead of calculated value

Expected behavior
Should be the calculated value

Should be fixed with Version 2.0.4


Where to put the config file in an Organisation?

Where do I have to put the configuration file when selecting "All Repositories of Organisation" when installing the app?

The configuration file is per repo you want to use this app with


Bug report: Different buttons

Describe the bug
When using the editor, the buttons to save and cancel differ in order and appearance from the other buttons of the application.
To Reproduce

Open Filegator
Open the editor
See error

Expected behavior
The buttons should look the same and be in the same order as in the rest of the application.
Screenshots
Standard:

Editor:

Environment

FileGator Version: 7.5.2
Server: Apache 2.4.41 on Debian Linux
PHP Version: PHP 7.4
Browser: Chrome, Firefox

What is in the world people still use php wow

Hehe, people still use 'php is dead' jokes?


fixed postgres timestamp string format for dates before christ (B.C.)

@mfussenegger please review

Current coverage is 80.96% (diff: 100%)

Merging #4242 into master will decrease coverage by 0.06%

@@             master      #4242   diff @@
==========================================
  Files          1300       1300
  Lines         44269      44269
  Methods           0          0
  Messages          0          0
  Branches       7071       7071
==========================================
- Hits          35872      35843    -29
- Misses         5753       5770    +17
- Partials       2644       2656    +12

Powered by Codecov. Last update 303c92b...31ebd2c

@mfussenegger you're right, it's for any client


loop on rebuild.

i dont know what happend, but this still going sometimes.
loop about 10000 times and refresh

thanks, how often does this happen?  could anything by touching / saving / modifying these files multiple times?  that's my only suspicion now, I'll add some code in the next release to ensure a file has actually changed before sending an update, rather than just believing the OS.  Which OS are you on, btw?

i don't know why this happens, i use windows 10 x64.
may this issus is same https://github.com/gadicc/meteor-react-hotloader/issues/34#issuecomment-208225913


cursor in wrong position when putting long register

Steps to reproduce
Run this shell command:
vim -Nu NONE -S <(tee <<'EOF'
    vim9script
    &laststatus = 2
    autocmd CursorMoved * eval [line('w0'), line('w$')]
    @a = 'x'->repeat(&columns * 2)
    ['']->repeat(&lines)->setline(1)
    feedkeys('G"ap')
EOF
)

The cursor is in the status line, and the xxx... line is not visible.
Expected behavior
The cursor is in the buffer, and the xxx... line is visible.
Version of Vim
9.0 Included patches: 1-1591
Environment
Operating system: Ubuntu 20.04.6 LTS
Terminal: XTerm(378)
Value of $TERM: xterm-256color
Shell: GNU bash, version 5.0.17
Additional context
The issue is triggered by the CursorMoved autocmd which evaluates line('w0') and line('w$').

A similar issue was fixed in patch 8.2.4915

Steps to reproduce
Run this shell command:
vim -Nu NONE -S <(tee <<'EOF'
    vim9script
    &laststatus = 2
    autocmd CursorMoved * eval [line('w0'), line('w$')]
    @a = 'x'->repeat(&columns * 2)
    ['']->repeat(&lines)->setline(1)
    feedkeys('G"ap')
EOF
)

The cursor is in the status line, and the xxx... line is not visible.
Expected behavior
The cursor is in the buffer, and the xxx... line is visible.
Version of Vim
9.0 Included patches: 1-1591
Environment
Operating system: Ubuntu 20.04.6 LTS
Terminal: XTerm(378)
Value of $TERM: xterm-256color
Shell: GNU bash, version 5.0.17
Additional context
The issue is triggered by the CursorMoved autocmd which evaluates
line('w0') and line('w$').

Interesting.  After removing "line('w0')" it still happens.  It's the
"line('w$')" expression that triggers the problem.
I can also remove setting 'statusline', the cursor then shows in the
command line, which is just as wrong.
Changing the feedkeys() call by adding "$" fixes the problem.  Other
commands after the put that move the cursor also fix the problem.  Thus
it appears the put command is not setting the flags for recomputing the
scroll position correctly.
While debugging this I found a few things that were wrong, but the
essential fix is to mark w_botline as invalid when the cursor line is
changed.  It may no longer fit in the window and a scroll up is needed.
I'll make a patch for that.
--
From "know your smileys":
:-E	Has major dental problems
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


changelog_from_git_commits with no parameters and increment_build_number

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
We're using increment_build_number in combination with changelog_from_git_commits. It seems that changelog_from_git_commits as default collects the git log between the last tag and the HEAD, which happens to be always empty? Is there a way to set it up so that it takes the previous tag before the build number was incremented and committed?
Complete output when running fastlane, including the stack trace and command used
nikita2:xxx klemens$ fastlane beta<EMAIL_ADDRESS>Ignoring fast-stemmer-1.0.2 because its extensions are not built.  Try: gem pristine fast-stemmer --version 1.0.2
Ignoring ffi-1.9.10 because its extensions are not built.  Try: gem pristine ffi --version 1.9.10
Ignoring ffi-1.9.3 because its extensions are not built.  Try: gem pristine ffi --version 1.9.3
Ignoring posix-spawn-0.3.9 because its extensions are not built.  Try: gem pristine posix-spawn --version 0.3.9
Ignoring redcarpet-3.1.2 because its extensions are not built.  Try: gem pristine redcarpet --version 3.1.2
Ignoring yajl-ruby-1.1.0 because its extensions are not built.  Try: gem pristine yajl-ruby --version 1.1.0
[18:22:31]: -------------------------------------------------
[18:22:31]: --- Step: Verifying required fastlane version ---
[18:22:31]: -------------------------------------------------
[18:22:31]: Your fastlane version 2.14.2 matches the minimum requirement of 2.10.0  ✅
[18:22:31]: ------------------------------
[18:22:31]: --- Step: default_platform ---
[18:22:31]: ------------------------------
[18:22:31]: Driving the lane 'ios beta' 🚀
[18:22:31]: -------------------------------------
[18:22:31]: --- Step: ensure_git_status_clean ---
[18:22:31]: -------------------------------------
[18:22:31]: Git status is clean, all good! 💪
[18:22:31]: ------------------------------------
[18:22:31]: --- Step: increment_build_number ---
[18:22:31]: ------------------------------------
[18:22:31]: $ cd /Users/klemens/dev/my_projects/XXX/XXX && agvtool next-version -all && cd -
[18:22:33]: ▸ Setting version of project XXX to:
[18:22:33]: ▸ 5.
[18:22:33]: ▸ Also setting CFBundleVersion key (assuming it exists)
[18:22:33]: ▸ Updating CFBundleVersion in Info.plist(s)...
[18:22:33]: ▸ Updated CFBundleVersion in "XXX.xcodeproj/../XXX/Info.plist" to 5
[18:22:33]: ▸ Updated CFBundleVersion in "XXX.xcodeproj/../XXXTests/Info.plist" to 5
[18:22:33]: ▸ Updated CFBundleVersion in "XXX.xcodeproj/../XXXUITests/Info.plist" to 5
[18:22:33]: ▸ /Users/klemens/dev/my_projects/xxx/xxx
[18:22:34]: ---------------------------------
[18:22:34]: --- Step: commit_version_bump ---
[18:22:34]: ---------------------------------
[18:22:34]: $ git rev-parse --show-toplevel
[18:22:34]: ▸ /Users/klemens/dev/my_projects/xxx/xxx
[18:22:35]: $ git diff --name-only HEAD
[18:22:35]: ▸ XXX.xcodeproj/project.pbxproj
[18:22:35]: ▸ XXX/Info.plist
[18:22:35]: ▸ XXXTests/Info.plist
[18:22:35]: ▸ XXXUITests/Info.plist
[18:22:35]: $ git ls-files --other --exclude-standard
[18:22:35]: $ git add /Users/klemens/dev/my_projects/XXX/XXX/XXX.xcodeproj/project.pbxproj /Users/klemens/dev/my_projects/XXX/XXX/XXX/Info.plist /Users/klemens/dev/my_projects/XXX/XXX/XXXTests/Info.plist /Users/klemens/dev/my_projects/XXX/XXX/XXXUITests/Info.plist
[18:22:35]: $ git commit -m 'Version Bump to 5'
[18:22:35]: ▸ [master 819c94e] Version Bump to 5
[18:22:35]: ▸ 4 files changed, 5 insertions(+), 5 deletions(-)
[18:22:35]: Committed "Version Bump to 5" 💾.
[18:22:35]: -------------------------
[18:22:35]: --- Step: add_git_tag ---
[18:22:35]: -------------------------
[18:22:35]: Adding git tag 'builds/iosbeta/5' 🎯.
[18:22:35]: $ git tag -am builds/iosbeta/5\ (fastlane) 'builds/iosbeta/5'
[18:22:36]: --------------------------------
[18:22:36]: --- Step: push_to_git_remote ---
[18:22:36]: --------------------------------
[18:22:36]: $ pwd
[18:22:36]: ▸ /Users/klemens/dev/my_projects/XXX/XXX
[18:22:36]: $ git push origin master:master --tags
[18:22:38]: ▸ To ssh://bitbucket.org/XXX/XXX.git
[18:22:38]: ▸ 8e200aa..819c94e  master -> master
[18:22:38]: ▸ * [new tag]         builds/iosbeta/5 -> builds/iosbeta/5
[18:22:38]: Successfully pushed to remote.
[18:22:38]: -----------------
[18:22:38]: --- Step: gym ---
[18:22:38]: -----------------
[18:22:39]: $ xcodebuild -list -workspace ./XXX.xcworkspace
[18:22:41]: $ xcodebuild clean -showBuildSettings -workspace ./XXX.xcworkspace -scheme XXX
2017-02-08 18:22:42.806 xcodebuild[77553:57425502]  DeveloperPortal: Using pre-existing current store at URL (file:///Users/klemens/Library/Developer/Xcode/DeveloperPortal%208.2.1.db).
+----------------------+-------------------------+
|             Summary for gym 2.14.2             |
+----------------------+-------------------------+
| scheme               | XXX                |
| export_method        | development             |
| workspace            | ./XXX.xcworkspace  |
| destination          | generic/platform=iOS    |
| output_name          | XXX                |
| clean                | false                   |
| output_directory     | .                       |
| silent               | false                   |
| use_legacy_build_api | false                   |
| buildlog_path        | ~/Library/Logs/gym      |
| xcode_path           | /Applications/Xcode.app |
+----------------------+-------------------------+
[18:22:43]: $ set -o pipefail && xcodebuild -workspace ./XXX.xcworkspace -scheme XXX -destination 'generic/platform=iOS' -archivePath
...
18:30:03: Successfully exported and compressed dSYM file
18:30:03: Successfully exported and signed the ipa file:
18:30:03: /Users/klemens/dev/my_projects/XXX/XXX/XXX.ipa
18:30:03: ----------------------------------------
18:30:03: --- Step: changelog_from_git_commits ---
18:30:03: ----------------------------------------
18:30:03: Collecting Git commits between builds/iosbeta/5 and HEAD
18:30:03: --- Step: crashlytics ---
18:30:03: -------------------------
18:30:03: Uploading the build to Crashlytics Beta. Time for
...
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.0.0

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib

OpenSSL Version
OpenSSL 0.9.8zc 19 Mar 2015

Is contained
false

Is homebrew
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
de_AT.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
fastlane_version "2.10.0"

default_platform :ios

platform :ios do
  #
  # Learn more here: https://github.com/fastlane/setups/blob/master/samples-ios/distribute-beta-build.md 🚀
  #
  lane :beta do |values|

    # Ensure that your git status is not dirty
    ensure_git_status_clean

    # Increment the build number (not the version number)
    # Providing the xcodeproj is optional
    increment_build_number

    # Commit the version bump
    commit_version_bump

    # Add a git tag for this build. This will automatically
    # use an appropriate git tag name
    add_git_tag

    # Push the new commit and tag back to your git remote
    push_to_git_remote

    # Fabric generated this lane for deployment to Crashlytics Beta
    # set 'export_method' to 'ad-hoc' if your Crashlytics Beta distribution uses ad-hoc provisioning
    gym(scheme: 'XXX', export_method: 'development')

    emails = values[:test_email] ? values[:test_email]<EMAIL_ADDRESS># You can list more emails here
    groups = values[:test_email] ? nil : nil # You can define groups on the web and reference them here

    crashlytics(api_token: 'xxx',
             build_secret: 'xxx',
                   emails: emails,
                   groups: groups,
                    notes: changelog_from_git_commits, # 'Distributed with fastlane', # Check out the changelog_from_git_commits action
            notifications: true) # Should this distribution notify your testers via email?

  end
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.14.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.4.0

rouge
1.10.1

xcpretty
0.2.4

terminal-notifier
1.6.3

terminal-table
1.4.5

plist
3.1.0

addressable
2.3.8

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

colored
1.2

highline
1.7.2

commander
4.4.3

excon
0.45.4

faraday
0.9.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.24

http-cookie
1.0.2

faraday-cookie_jar
0.0.6

fastimage
1.6.8

gh_inspector
1.0.2

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types
1.25.1

hurley
0.2

little-plugger
1.1.4

logging
2.0.0

jwt
1.5.2

memoist
0.12.0

multi_json
1.11.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.5.5

rubyzip
1.1.7

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
0.10.0

i18n
0.7.0

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.6.0

activesupport
4.2.1

json
1.8.2

CFPropertyList
2.3.3

claide
1.0.1

nanaimo
0.2.2

xcodeproj
1.4.1

generated on: 2017-02-08

Not really 🤔

Try add_git_tag after the lane has successfully uploaded to distributor.

Hey @klemensz, I'm not sure I totally understand why the changelog_from_git_commits action would be coming up empty, but I think you might be able to try using the :between, :commits_count, and :tag_match_pattern parameters to try to achieve what you are looking for. I am going to close this issue for now as I believe we have options in there that should satisfy your issue, but please feel free to reopen and comment here if that is not what youre looking for. Thanks! 🐙 🚀


Add README.md file please and also link to repo on website

Add README.md file please and also link to repo on website

Done!


Azure Durable Functions API Reference doesn't offer documentation for DFApp and Blueprints classes

Type of issue
Missing information
Description
Azure Functions Python v2 projects use the azure.durable_functions.Blueprint and DFApp classes, but there is no documentation for those classes and their decorators in the API reference.
They should be included in the Classes section of the package reference.
Page URL
https://learn.microsoft.com/en-us/python/api/azure-functions-durable/azure.durable_functions?view=azure-python
Content source URL
https://github.com/MicrosoftDocs/azure-docs-sdk-python/blob/main/docs-ref-autogen/azure-functions-durable/azure.durable_functions.yml
Document Version Independent Id
ca0470bb-40c6-66a7-a764-71e29509afcf
Article author
@lmazuel
Metadata

ID: a95fe6a1-3abb-7c46-99e4-bb932ea82918

Hi @metamoof, this repo is for the Azure Python SDK. For items related to Azure Functions issues need to be opened here

@kashifkhan This issue is opened becasue the link provided on the bottom of the page. https://learn.microsoft.com/en-us/python/api/azure-functions-durable/azure.durable_functions?view=azure-python
I will open an issue for my problem in the other location, but please also look at correcting that link.


⚠ Tukarcoid has degraded performance

In faa4994, Tukarcoid (https://tukar.co.id) experienced degraded performance:

HTTP code: 200
Response time: 2524 ms

Resolved: Tukarcoid performance has improved in 5c83421 after 15 minutes.


Submit multiple editable element fired by an external button

I made this
http://jsfiddle.net/Jack_bay/xBB5x/13603/
submit fired by click an external button
if it has multiple editable element(no comment the second element), it would work fine.
but if I comment one and left a single element, the post url would not be "/posttest", but current window's location.href.
is it a bug, or I missed something .

I read the code
https://github.com/vitalets/x-editable/blob/develop/dist/bootstrap3-editable/js/bootstrap-editable.js#L2060
here, if single element, url would be from init options when multiple would be from config arguments.
it is not a bug sure enough. but the doc is unclear absolutely.
hope you would notice this

This is the normal default behavior of any web component. If a target URL is not specified then it will use the current URL. For example:  example.com

funny

So, I reread your example to see what you are trying to do.
For the second button, you could get the value of the x-editable field & use your own logic to save it:  https://vitalets.github.io/x-editable/docs.html#editable (use the getValue() function) or you can force a click on x-editable's native save button.


adding locked event as an emitted event

This allows you to know when a lock is unavailable so that you can do things with processes that do not have leadership.
BTW Thanks for all the work on this!

Thanks for the pull request, definitely a useful event to expose.
I decided to tweak the event name (I thought locked might confuse some people), anyway released the change in 0.19.0 to npm.


Update Travis settings for Xcode 10

Yeah that didn't work out too well, did it?
I'd appreciate if anyone with more Travis CI skills than me would chime in and make this work.

The raw log is saying an xcodebuild: error: SDK "macosx10.12" cannot be located. Looking at the Travis CI docs, I think you also need to point to macosx10.13 here


MVP Implementation

A description of the changes proposed in the Pull Request

Project Setup:

Add section to README explaining how to set DD env variables
Disable unit tests (#hackathon)
Add sample manifest file
Basic implementation:
Expect an input that has some instance ID, timestamp and duration
Global configuration accepts the DD metric name for CPU utilization, the tag keys used for instance type, location, and instance ID
For each input, get the configured metric for the time and instance ID, grouping by instance type and location
For now, just take the first datapoint in the time series returned from DD and pass it to the plugin's output.

Pipeline is failing because package.json resolved to our corporate package repo.


Can't drive LRA motor

I am using Tinycircuits AST1013 LRA driver wireling with ESPWROOM32 and the LRA motor used in the AST1013 is VG0832013D, whose resonant frequency is 235 Hz. The LEDC library used in your code has updated and I made some changes accordingly.
`#include <Wire.h>
#include "Adafruit_DRV2605.h"
const int Motor_PWM_Pins = 16;
const uint32_t Default_PWM_Frequency = 235;
Adafruit_DRV2605 drv;
void SetMotorVoltage(uint8_t Fraction = 0x89)
{
drv.writeRegister8(0x16, Fraction);
drv.writeRegister8(0x17, Fraction);
}
void SetFreq(uint32_t Freq = Default_PWM_Frequency)
{
//DRV2605 Input PWM Frequency: 10-250kHz
assert (Freq <= 1950); //DRV2605 cannot support > 250kHz PWM signals
assert (Freq != 0);   //DRV2605 cannot support < 10Hz PWM signals
Freq *= 128;
ledcAttachChannel(16, Freq, 8, 0);
ledcWrite(16, 255);
}
void setup()
{
Serial.begin(115200);
Wire.begin();
/Setup DRV2605/
drv.begin();
drv.useLRA();
drv.setMode(DRV2605_MODE_PWMANALOG);
//LRA_OPEN_LOOP
drv.writeRegister8(DRV2605_REG_CONTROL3, drv.readRegister8(DRV2605_REG_CONTROL3) | 0x01);
/Setup DRV2605/
SetFreq(Default_PWM_Frequency);
}
void loop()
{
while (Serial.available())
{
int Frequency = Serial.parseInt();
uint8_t Power = Serial.parseInt();
SetFreq(Frequency);
SetMotorVoltage(Power);
while (Serial.available())
  Serial.read();  //Read redundant data in buffer

}
}
`
But it is not working. I don't know what issues I am facing. I have read the datasheet of DRV2605L and I understood the theory but I am rookie for MCUs. Can you please guide me?

Thank you.

Can someone please guide me through this?


Traceback when uploading an empty file using Bucket's upload_file method

I'm uploading a directory which has some empty files as markers. However the upload_file method throws a backtrace. There's a similar issue on aws-cli: https://github.com/aws/aws-cli/issues/2403
It looks like this just needs some better range checking before seeking.
$ python3 run_test.py
Uploading results for test: test_upload_20170817142448 from /tmp/output
Uploading /tmp/output/ros.bag to test_upload_20170817142448/ros.bag
Uploading /tmp/output/gazebo.log to test_upload_20170817142448/gazebo.log
Traceback (most recent call last):
  File "run_test.py", line 47, in <module>
    upload_to_s3(b, test_name, results_dir)
  File "run_test.py", line 14, in upload_to_s3
    bucket.upload_file(full_f, bucket_key)
  File "/usr/lib/python3/dist-packages/boto3/s3/inject.py", line 110, in bucket_upload_file
    ExtraArgs=ExtraArgs, Callback=Callback, Config=Config)
  File "/usr/lib/python3/dist-packages/boto3/s3/inject.py", line 71, in upload_file
    extra_args=ExtraArgs, callback=Callback)
  File "/usr/lib/python3/dist-packages/boto3/s3/transfer.py", line 629, in upload_file
    self._put_object(filename, bucket, key, callback, extra_args)
  File "/usr/lib/python3/dist-packages/boto3/s3/transfer.py", line 639, in _put_object
    **extra_args)
  File "/usr/lib/python3/dist-packages/botocore/client.py", line 251, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/lib/python3/dist-packages/botocore/client.py", line 526, in _make_api_call
    operation_model, request_dict)
  File "/usr/lib/python3/dist-packages/botocore/endpoint.py", line 141, in make_request
    return self._send_request(request_dict, operation_model)
  File "/usr/lib/python3/dist-packages/botocore/endpoint.py", line 166, in _send_request
    request = self.create_request(request_dict, operation_model)
  File "/usr/lib/python3/dist-packages/botocore/endpoint.py", line 151, in create_request
    prepared_request = self.prepare_request(request)
  File "/usr/lib/python3/dist-packages/botocore/endpoint.py", line 162, in prepare_request
    return request.prepare()
  File "/usr/lib/python3/dist-packages/botocore/awsrequest.py", line 369, in prepare
    p.prepare_body(self.data, self.files)
  File "/usr/lib/python3/dist-packages/botocore/awsrequest.py", line 440, in prepare_body
    data.seek(0, 2)
TypeError: seek() takes 2 positional arguments but 3 were given

I have a local workaround that doesn't call upload_file but just calls put_object instead that avoids the problem.
            print('Uploading %s to %s' % (full_f, bucket_key))
            if os.stat(full_f).st_size:
                bucket.upload_file(full_f, bucket_key)
            else:
                print("Empty file fallback behavior")
                bucket.put_object(
                    Key=bucket_key,
                    Body=''
                )

$ python3 run_test.py
Uploading results for test: test_upload_20170817144559 from /tmp/output
Uploading /tmp/output/ros.bag to test_upload_20170817144559/ros.bag
Uploading /tmp/output/gazebo.log to test_upload_20170817144559/gazebo.log
Empty file fallback behavior
Uploading /tmp/output/test_results/results1.xml to test_upload_20170817144559/results1.xml
Empty file fallback behavior
Uploading /tmp/output/test_results/results2.xml to test_upload_20170817144559/results2.xml
Empty file fallback behavior

It's not a range issue, it's a difference in function signature. From what I've seen this issue only arises when the cli is installed via Ubuntu's packaging system. They remove our vendored version of requests and substitute their own version. This can cause issues like the one you're seeing. I'm not sure if there's much we can do about this as we don't control the packages in the Ubuntu repos. A work-around for now is to install the cli via pip and not the standard Ubuntu repos.

I did have the awscli installed on my system but when I remove it I still have the same issue. Though it is possibly an issue with the version of requests available via ubuntu/debian. The pypi version of requests is much newer: https://pypi.python.org/pypi/requests 2.18.4 versus 2.9.1
Is there a minimum version with known compatibility of request? I can refile a ticket against debian/ubuntu.
$ pip3 show requests
---
Metadata-Version: 1.1
Name: requests
Version: 2.9.1
Summary: Python HTTP for Humans.
Home-page: http://python-requests.org
Author: Kenneth Reitz
Author-email<EMAIL_ADDRESS>License: Apache 2.0
Location: /usr/lib/python3/dist-packages
Requires:
Classifiers:
  Development Status :: 5 - Production/Stable
  Intended Audience :: Developers
  Natural Language :: English
  License :: OSI Approved :: Apache Software License
  Programming Language :: Python
  Programming Language :: Python :: 2.7
  Programming Language :: Python :: 3
  Programming Language :: Python :: 3.3
  Programming Language :: Python :: 3.4
  Programming Language :: Python :: 3.5
You are using pip version 8.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
$ dpkg -l | grep boto
ii  python3-boto3                               1.2.2-2                                               all          Python interface to Amazon's Web Services - Python 3.x
ii  python3-botocore                            1.4.70-1~16.04.0                                      all          Low-level, data-driven core of boto 3 (Python 3)
$ dpkg -l | grep aws
$ dpkg -l | grep requests
ii  httping                                     2.4-1                                                 amd64        ping-like program for http-requests
ii  iputils-arping                              3:20121221-5ubuntu2                                   amd64        Tool to send ICMP echo requests to an ARP address
ii  liburl-dispatcher1:amd64                    0.1+16.04.20151110-0ubuntu2                           amd64        library for sending requests to the url dispatcher
ii  node-forever-agent                          0.5.1-1                                               all          HTTP agent supporting keep-alive requests - module for Node.js
ii  python-requests                             2.9.1-3                                               all          elegant and simple HTTP library for Python2, built for human beings
ii  python3-requests                            2.9.1-3                                               all          elegant and simple HTTP library for Python3, built for human beings

We vendor requests, the system version shouldn't matter. Specifically, botocore vendors requests. It might be that if you only uninstall the cli, reinstalling via pip might still rely on your boto3 and botocore installed from your distro repos.

Thanks for the info. I've refiled it here: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1711737


Usage with babel and ES6

I try to use the package with babel and es6
import fetch from 'whatwg-fetch';
Unfortunately I get the following error:
Uncaught TypeError: (0 , _whatwgFetch2.default) is not a function

@abimelex
Description

A window.fetch JavaScript polyfill.
fetch do not export modules.
You can do

import 'whatwg-fetch';
// And then just use global variable.
fetch(...);

Ah thank you, thats perfect.

Don't forget to close issue if you found answers.

I solved it with import 'isomorphic-fetch'; in my jest-setup.js.


operator: Update the component operator to create publishedNotification & subscribedNotification resources

Description
The Component Operator should be updated to create publishedNotification & subscribedNotification resources.

https://github.com/tmforum-oda/oda-canvas/pull/68

see #104


fix #1778, AppSubmitter "-config" option is not used

Could you add "-conf" options to doc(https://github.com/gearpump/gearpump/blob/master/docs/commandline.md) as well ?

Current coverage is 62.55%

Merging #1780 into master will decrease coverage by -1.11% as of de75f00

@@            master   #1780   diff @@
======================================
  Files          167     167
  Stmts         5006    5007     +1
  Branches       549     549
  Methods
======================================
- Hit           3187    3132    -55
  Partial          0       0
- Missed        1819    1875    +56

Review entire Coverage Diff as of de75f00

Uncovered Suggestions

+0.26% via .../master/Master.scala#123...135
+0.24% via ...cutor/Executor.scala#271...282
+0.22% via .../MasterService.scala#204...214
See 7 more...

Powered by Codecov. Updated on successful CI builds.

@manuzhang
updated.

Ok, done.
Some default options are not listed, since I think we don't need to document everything.

+1


Add new GitHub app keys to docs and example

Just that.

@wlonk Also add the appropriate local dev env vars to Keybase?

@jgerigmeyer 👍 to those changes.


Evo 1018 port widget data selection

So I want to propose a pattern for us to follow.
As I mention in the readme update:
A new pattern being introduced for the application is the addition of useEnsureX, which is a custom hook that handles both selecting X from the store and, if it isn't present, also handles the fetching of that data.
Take a look at the below initial example useEnsureCurrentGroup and tell me what you think about the idea of moving to this idea. In my eyes, the biggest benefit is that when you drop one of these hooks into a component, you know that component won't have an implicit dependency on something else to make the request for the data it needs.

I had greater ambitions to replace getWidgetItems and push those data selections/transformations into their respective widget components but a bunch of the logic around visibility is handled in the Widget component. So I don't currently have a good idea about how to handle that...

Closes #1018


Empty output files

Hi,
I'd like to know, if there is any reason why the library generates output file for every member in project, instead of just members marked with corresponding attribute? As a result there are plenty useless files containing only preamble and namespaces in output folder generated for members without marker attribute.
Also can I somehow avoid getting excess output?

Duplicate of #161

Hi @AArnott,
Why this was closed as a duplicate? #161 describes cases with unexpected behavior (empty emit and error during emit), while in my case everything works as expected and I'm talking about optimization exclusively: avoid creating empty files for members without trigger attribute which are not supposed to be processed.

Hi @as-ivanov,
This is currently by-design. In essence, it's helping us simplify up-to-date checks.
For a longer discussion and a "workaround", see https://github.com/AArnott/CodeGeneration.Roslyn/issues/33#issuecomment-398475490
You can open an issue for a "Feature Request" asking for behavior change, and we may take it into account at some point.

I don't know how the design would change and still keep the incremental build correct and fast.


Fix for add manual file method

Fixes

This fix subtracts manually added file from maxFiles option. Which was allowing the user to add more files than maximum allowed files in the dropbox. (Addition to newly added method manuallyAddFile())

Removed redundant documentation from README. (TYPO)

@rowanwins I think we should REMOVE button from files which are added manually. Because even if we remove that file from dropbox it's not deleted from server.
Even it creates mess with maxFiles now because we are reducing maxFiles count by 1.
So, anyway we have to remove REMOVE button from manually added file.
Wait for my other commit. I'll work on it.

Working as expected. Needs more test cases. 😄

Hey @vrajroham
Thanks so much for picking that up and the good suggestion for the remove button.
I've added you as a collaborator on the repo so feel free to make any other contributions directly, I only get to maintain this repo very sporadically!
Cheers

Thanks @rowanwins I'll try my best!

@rowanwins @vrajroham uhhh dudes.. what? what am I reading here? This project isn't exclusively used in implementations that use Dropbox!! I just opened an issue that you caused by deciding to remove the remove button for manually added files https://github.com/rowanwins/vue-dropzone/issues/94
I am doing my own handling of the remove functionality with an API that's got nothing to do with Dropbox.. and now my remove button has gone missing without explanation.
So the question is, how do I undo your "fix" here? If a user wants to have the remove button showing.. let them! They know what they need... this just broke the 'remove image' functionality I had on a project in production with hundreds of users =/

Gday @vesper8
Sorry for the unintentional side-effects, the easiest solution to roll back to a previous version of the plugin via npm, you should be able to do npm install<EMAIL_ADDRESS>Please remember that this project is maintained unfunded, at 10pm at night after a long day at work and looking after kids, occasionally things go astray. If you can work out a better way to handle these edge cases you're welcome to contribute pull requests.
We'll work to try and release a fix

@rowanwins Yes I do understand the nature of open source and if I haven't mentioned it before, though I think I might have because I very often do, I am VERY grateful for this package, and the other 200+ github packages that I use in my projects. I do try and contribute here and there, I guess my bigger contribution is bug reporting
I have reverted back to the commit just before the one that removed the Remove button
"vue2-dropzone": "git://github.com/rowanwins/vue-dropzone.git#9b9ceb5",

I am just a little frustrated at the decision in this case because.. unless I am missing something.. and maybe I am.. removing the remove button in ALL cases for manually added files just essentially removed the ability to delete files via Dropzone in .. all cases? for all filesystems? How is one expected to be able to remove a file that was previously added (ie not in the current session) with the button completely removed?
I've never used Dropbox to store files.. I don't suppose it's a very wise things to use for files originating from a public-facing website but that's my opinion. But I also don't understand the logic for removing the button "for Dropbox". Surely even Dropbox allows deletion of files.. maybe not automatically but through an api call and a little custom code.
Anyway, sorry if I sounded a little brash.. I do appreciate your work and this library quite a bit.
Cheers


Add more calendar views (i.e., week view, year view, decade view)

🙋 Feature Request
Currently, the Adobe Spectrum React calendar component only supports a single view, which is the month view. This feature request proposes adding additional views to the calendar component, including year, decade, and week views.
🤔 Expected Behavior
There can a view prop which can be used to change the view of the calendar for example
<Calendar view="week" /> // a view with dates of a specific week
<Calendar view="month" /> // the default and current view, where all the dates of specific month are listed
<Calendar view="year" /> // a view with list of months
<Calendar view="decade" /> // a view with list of years in a decade

😯 Current Behavior
Currently calendar component only supports the month view.
💁 Possible Solution
I already implemented this feature internally for my team (detail in context section), and here's how I did it:

I left the whole interaction logic as it is.
and I only have to patch the rendering logic, which includes:

date formatting for calendar cells
state provided by useCalendarState and useRangeCalendarState
and some changes to make the Calendar logic more abstract, which will allow us to support more calendar views

Although the current implementation is quite cranky, I'm willing to contribute to this feature. Just let me know If what I did aligns with adobe spectrum design's philosophy.
🔦 Context
I had been working on a date picker component. The current implementation of the date picker component does not have a year or decade view. This means that users have to click through many months to select a date that is a few years from the past.
To fix this issue, I internally patched the current implementation of the calendar component for my team to add support for month, year, and week views. This allows users to select dates more easily, regardless of how far in the past or future they are.
For this, I had to patch:

@react-stately/useCalendarState
@react-stately/useRangeCalendarState
@react-aria/useCalendar
@react-aria/useRangeCalendar
@react-aria/useCalendarCell
@react-aria/useCalendarGrid
and the whole calendar component from react-aria-components.

💻 Examples
These are the screenshots of my implementation.

🧢 Your Company/Team
CarteBlanche.tech / Hirecinch

Would be nice to have more calendar views  😭

Thank you for your interest and contribution offer! Looking at the our internal Spectrum Design site, I'm not seeing any designs defining how we'd like these week/month/year/decade view to look or behave, so we'll have to bring this up with the design team first.

btw you can already build a week view with the hooks by setting the visibleDuration option. There's an example linked from the docs.

@devongovett Exactly we don't need to change anything for the week view in the hooks but for the Calendar component from react-aria-components to work for the week view I guess we need to change a few things here. Meanwhile I can fix this if you want.

Closely related to this discussion


Transfer root-image configuration to this repository

/assign @mfojtik

Setting valid-bug manually, since this is changing build configuration, not fixing bug.

/lgtm