Disabled days

Hi!How i can disable some days?
Example: [
21-2020,
25-2020: disabled,
3-2020
]

same question
on between of min and max dates I need to disable some dates
or only enable some and all other is disabled

@Desintegrator After spent a few hours on this question unfortunately, native datepicker doesn't has possibility disabled some date. Instead I added other library.

@AntonLukovtsev which one?

@Desintegrator https://www.npmjs.com/package/react-native-calendar-picker
But this library has a different interface


Chrome glitching issue

It seems as of maybe the past week the particles started glitching and any other scripts on the page running real slow.
There seems to be other issues with chrome at the moment with weird boxes when background color being rendered.
Probably just a chrome issue but it appears to be happening on the demo site as well so may be of interest to other people which aren't aware of this issue.
Seems to be working fine in other browsers.
Thanks!

Seems to be working fine again.

Chrome Version 61.0.3163.100 (Official Build) (64-bit) on  Ubuntu Linux 16.04.3 LTS
Demo site (vincentgarreau.com/particles.js/) is glitching on 0 - 1 FPS.

Version 62.0.3202.94 (Official Build) (64-bit) demo is getting crushed

disable hardware acceleration and all should work


What does smbios return on Vultr?

https://github.com/robertdfrench/metadata-agent/blob/master/src/main.rs#L1076

Wtf is this tool even? https://docs.oracle.com/cd/E88353_01/html/E72487/smbios-8.html ?


feat: remove AutoRemoveReferrers flag

following #680 and addressing this comment: https://github.com/oras-project/oras-go/pull/680#discussion_r1457164506

The AutoRemoveReferrers flag was introduced in #653

Wondering if this is a refactor?


Talk Proposal: Are GraphQL and Microservices Good Friends?

Abstract
Having several microservices exposing their APIs through an API Gateway isn't uncommon, and it is also expected that we require communication between those microservices. I am currently working on a project with some microservices in Node.js where the communication between them and the clients was kind of a mess.
In this talk, I am going to show you some different options I have explored in order to address this communication; how we improved it with GraphQL and the outcomes of it. By the end of the talk, you will find out if GraphQL and Microservices are Good Friends.
About me

Software Developer & Blockchain Padawan.
JavaScript Lover and co-organizer of MedellinJS (Medellin, Colombia)
https://twitter.com/RamirezAlex_

Previous Talks
I have spoken before in meetups, but not in International Conferences, so I have not video recordings of it. This talk would be my second one in English, which is not my mother tongue.
Talk time
15-20 Minutes

Hey @RamirezAlex, thanks for submitting! We have your proposal down ☑ We're looking over the proposals in the next couple of days, so we'll let you know either way later this week 😁

👋
Great work with MedellinJS over there, hearing good things about it ❤
As for your talk: We received way more proposals than we have slots and your talk didn't quite make it (it's always hard to choose, as you might now). However, we have some 10 minute slots to fill and for those we'll have a second round of voting asap.
Would you be able to give that talk in 10 minutes?

Hi @rmehner and @carolstran
Thank you for the good words about MedellinJS and for reviewing my talk proposal. I can absolutely give it in 10 minutes, and I was actually kind of expecting that I needed to skip some demos and cut down some slides to keep in that timeframe. Which I already did :)

Great thank you @RamirezAlex! We'll be doing the second round of voting asap and we will let you know within the next couple of days 😁

@RamirezAlex second vote is done and results are in. Unfortunately we can't give you a spot this time (wish we would have more time), but we sure hope you'll have the opportunity to give your talk somewhere :)
If you're ever in Berlin, please hit us up, we would be very happy to give you a spot at our regular meetup.

Thank you @rmehner :)

Closing this issue now, but thanks again for submitting @RamirezAlex 💟 Like Robin mentioned, if you're ever in Berlin we'd love to have you!


Cannot find opensim machine on AWS

Search of machine ami-971be8ee returns empty

Hi, which region are you using?

My account region is U.S, if that is what you mean.

I mean the region you are using in AWS. It's in the right-top corner as you can see here
https://camo.githubusercontent.com/7b98428cabccb5b1d67240bdcb72e35c734edee6/68747470733a2f2f73332d65752d776573742d312e616d617a6f6e6177732e636f6d2f6b69647a696e736b692f6f70656e73696d2d616d692f312e706e67
Right now the AMI in US should be available in North Virginia and Ohio. I can copy it to the region you are using as well.

Found the AMI in Ireland. But they are not available in North Virginia or Ohio.

Indeed permissions in NV and Ohio were wrong. Can you check now?

I can see them in NV and Ohio now.


fix issue 92

We need to create PRs with clear title, clear description and link to issue.
Please fix it


demo with xtouch mini input and Volca FM output

need a few things for this:

config support to limit midi input/output ranges
config support for multiple midi outputs

Well, I guess it's not completely required to have multiple outputs for this use case, but if I want the lights on the xtouch to work, we should have that.

yep this is working, demo config file is in the repo.


Why use React instead of Compose

I was a little surprised when I did not find Compose in the source 😄

Because I wanted to try the React. That is the answer 🤷


Synchronization of flowcharts/workflows/canvas elements

Feature
Hello, inside the web we have there are many free OSS like JsPlumb or other D3.js for flowchart process.
Using this we drive automation/assembly lines, which is based on a flow chart as the work flow manager from a website.

[ ] Can we get a sample to sync and update the server side and other clients at the same time.
[ ] How can we enable one display as edit and the others ad view only

Hey @weedkiller, can you add some more details to the scenario?
We have a few sync examples in the repository and in github.com/microsoft/fluidexamples. Do any of those examples meet your needs?

@weedkiller I'd love to hear more about what you're imagining! As Sam mentioned earlier, we have several examples showing how to use the DDSes in the framework to replace or augment existing data models. We haven't explored diagramming specifically, but if you explore that scenario we'd love to hear about it.

Hello, please consider a use case may help, like a class of teacher/students viewing an interactive flowchart or a group of technicians following an assembly line flowchart on the web browser.
I would like to see a use case sample where,

[ ]  Students/Teacher wants update the diagram, and how is the next-state handled across the class/group.
[ ]  Can we get a sample to sync and update or persist this back to the server side and other clients at the same time.
[ ]  How can we enable one display as edit and the others ad view only

In SignalR this was easily understand with the hub model, but I could not find a full working sample to show how to handle this/diagrams and server side synchronizing with a Controller.

unresolved


feat: Dark theme

Doing dark theme right is hard, especially the details. For example, the ‘toggle’ border when disabled. Similar issues with alerts, popovers etc…

Changing themes and colors is now much easier in Ionic4 and we have seen some really good samples and examples posted by other developers and even Ionic team members with dark themes, and toggling between dark and light themes. We have tried to combine some of these into our apps to get a dark theme, but it is hard to get all the details right.
Are there any plans for default dark theme colors in Ionic? Now that the OS has its own dark theme, it will be even better to pick the same iOS/Android default dark colors instead using just another shade of gray.

Hi there,
Ionic does ship with a "dark" color palette. For most components, you can do color="dark" as a property on the component. Does this address your use case?
Thanks!

We don't have plans to add a dark theme at the moment, but it is something that could easily be done in the starters. We have a dark theme added in the conference app, and plans to include a "toggle" to switch between light and dark theme there. It wouldn't be too much more to have it added to the starters.
https://github.com/ionic-team/ionic-conference-app/blob/master/src/theme/variables.scss#L198-L243

@liamdebeasi This is more about application wide dark mode. Similar to what @mhartington described here: https://ionicframework.com/blog/hot-take-dark-mode/
@brandyscarney A lot more needs to be done to make it truly complete. Like we also need to swap the 'dark' and 'light' colors or just use a different set of colors for all colors including primary, secondary etc... to match whatever colors iOS13 and Android10 are defaulting to in their native dark themes.
There are issues with borders of some controls like toggles as described above, and also with borders and background colors of alerts, popovers, action-sheets when trying to make everything dark. Currently they just 'blend' in too much with the content dark background - almost invisible.
Having a toggle in the sidebar to let user switch between light and dark themes will be great. Bulk of the users are not going to be on the latest OS release for a long time, and some may want to change settings per app.
A lot of it can be implemented at the application level and we have been trying to implement this by modifying the theme/variables.scss. But not everything can be fixed there. Moreover it seems like something that will help all Ionic applications.

A lot more needs to be done to make it truly complete. Like we also need to swap the 'dark' and 'light' colors or just use a different set of colors for all colors including primary, secondary etc... to match whatever colors iOS13 and Android10 are defaulting to in their native dark themes.

@sachingarg05 Why would we swap the dark and light colors? You may still have use for a light color or a dark color on a dark theme. You can override the colors though if desired, it would look like the following:
@media (prefers-color-scheme: dark) {
  :root {
    --ion-color-primary: #3880ff;
    --ion-color-primary-rgb: 56, 128, 255;
    --ion-color-primary-contrast: #ffffff;
    --ion-color-primary-contrast-rgb: 255, 255, 255;
    --ion-color-primary-shade: #3171e0;
    --ion-color-primary-tint: #4c8dff;
  }
}

These colors are meant to be customized, but they don't match either iOS or Android by default. The primary color is the Ionic blue.

There are issues with borders of some controls like toggles as described above, and also with borders and background colors of alerts, popovers, action-sheets when trying to make everything dark. Currently they just 'blend' in too much with the content dark background - almost invisible.

If there are any specific issues with dark theme variables not working to override specific components we can fix it but we need to have issues reported to track this. I recently fixed this issue regarding the overlay background color: https://github.com/ionic-team/ionic/issues/18658
Here's how I see our dark theme in MD mode:

I don't see it blending here, but if there are specific cases where it does we can look into it.
The way the defaults for dark theme work is by looking at the default light color. For example, alert's background uses #f9f9f9 in ios light theme. So we look at what "step" color of the background is closest to that, as documented here: https://ionicframework.com/docs/theming/advanced#stepped-colors
The closest is step 50, so we use the --ion-color-step-50 for the alert background. If using dark mode, it would be whatever you set in your theme file, such as:
  --ion-color-step-50: #232323;
  --ion-color-step-100: #2e2e2e;
  --ion-color-step-150: #3a3a3a;
  --ion-color-step-200: #454545;
  --ion-color-step-250: #515151;
  --ion-color-step-300: #5d5d5d;
  --ion-color-step-350: #686868;
  --ion-color-step-400: #747474;
  --ion-color-step-450: #7f7f7f;
  --ion-color-step-500: #8b8b8b;
  --ion-color-step-550: #979797;
  --ion-color-step-600: #a2a2a2;
  --ion-color-step-650: #aeaeae;
  --ion-color-step-700: #b9b9b9;
  --ion-color-step-750: #c5c5c5;
  --ion-color-step-800: #d1d1d1;
  --ion-color-step-850: #dcdcdc;
  --ion-color-step-900: #e8e8e8;
  --ion-color-step-950: #f3f3f3;

These can be manipulated to use lighter or darker colors or have more variation, or you can use our generator here that uses the same formula as we do for the light colors: https://ionicframework.com/docs/theming/advanced#generate-stepped-color-variables

In the case of the toggle, it is using the proper colors between light and dark, but the box-shadow isn't updated for dark theme. Notice the difference (top one using a box shadow that is light):

Here's light theme if the box-shadow was the same:

Thanks, I understand this better now. Looks like some of our issues can be resolved by fixing our --ion-color-step values. We had just copied the step values from someone's sample code and the step-50 was less than our chosen background gray.
Will report any specific issues that we can't resolve using variables.scss and step colors. I do feel that the variables.scss in "Ionic start" templates should include a dark theme section, even if its commented out by default.
For toggle shadow color, can this be fixed by us in our application - in variables.scss or a parameter when creating the toggle? Or do you plan to change the shadows for toggle (and other components) to use one of the step color values?

By swapping the dark and light colors, I meant that in light theme - light is the low-contrast color (closest to background color) and dark is the high-contrast color (opposite of background color).
If we only change background color to dark, then a light becomes the high contrast color and dark becomes the low contrast color.
So in our apps in dark theme, we would want light buttons to look 'dark' and the dark buttons to look light. To maintain same contrast effect as they did in light theme. I understand that we can fix this in our app by changing the colors in media-query in theme/variables.scss.

Ah, okay! Yeah, if the stepped colors aren't set to a gradient going from the background -> text color it will look off by default.

Will report any specific issues that we can't resolve using variables.scss and step colors. I do feel that the variables.scss in "Ionic start" templates should include a dark theme section, even if its commented out by default.

I agree with this, but I'd like to work through fixing some of the bugs and making sure all of the defaults are good before we add it so that it doesn't need several iterations.

For toggle shadow color, can this be fixed by us in our application - in variables.scss or a parameter when creating the toggle? Or do you plan to change the shadows for toggle (and other components) to use one of the step color values?

I believe it would need to be updated in Ionic. The box-shadow uses a value of:
0 3px 12px rgba(0, 0, 0, .16), 0 3px 1px rgba(0, 0, 0, .1)

So it needs to be something like:
0 3px 12px rgba(var(--ion-text-color-rgb, 0, 0, 0), .16), 0 3px 1px rgba(var(--ion-text-color-rgb, 0, 0, 0), .1)

This would make the box shadow use the RGB text color variable by default with a fallback of 0, 0, 0.

By swapping the dark and light colors, I meant that in light theme - light is the low-contrast color (closest to background color) and dark is the high-contrast color (opposite of background color).

This makes sense. I'm not sure if it should be something we provide by default but I can definitely see the use case for it.

Actually, after revisiting iOS 13's styles, it seems they keep the toggle icon the same color in dark mode:

This may be a case where we need to individually compare components against native.

I started on some fixes here: https://github.com/ionic-team/ionic/pull/18735
Here's a preview:

@brandyscarney So based on your answer we do need to reverse our steps if we switch to a dark theme? Or is it better to make our light to dark and our dark to light?

After talking with our designer, we decided we would be switching the light and dark colors as @sachingarg05 suggested. The stepped colors do need to be reversed if you're going from
background: white -> black
text: black -> white

This can be generated for you in the documentation though, here: https://ionicframework.com/docs/theming/advanced#generate-stepped-color-variables
We're currently working on the dark theme. Our designer provided some new Ionic colors and I have been tweaking some of the bugs in the components as I've found them in this PR here: https://github.com/ionic-team/ionic/pull/18735
Here's the latest design:

Using the following variables:
:root {
  --ion-color-primary: #428CFF;
  --ion-color-primary-rgb: 66,140,255;
  --ion-color-primary-contrast: #ffffff;
  --ion-color-primary-contrast-rgb: 255,255,255;
  --ion-color-primary-shade: #3a7be0;
  --ion-color-primary-tint: #5598ff;

  --ion-color-secondary: #50C8FF;
  --ion-color-secondary-rgb: 80,200,255;
  --ion-color-secondary-contrast: #ffffff;
  --ion-color-secondary-contrast-rgb: 255,255,255;
  --ion-color-secondary-shade: #46b0e0;
  --ion-color-secondary-tint: #62ceff;

  --ion-color-tertiary: #6A64FF;
  --ion-color-tertiary-rgb: 106,100,255;
  --ion-color-tertiary-contrast: #ffffff;
  --ion-color-tertiary-contrast-rgb: 255,255,255;
  --ion-color-tertiary-shade: #5d58e0;
  --ion-color-tertiary-tint: #7974ff;

  --ion-color-success: #2FDF75;
  --ion-color-success-rgb: 47,223,117;
  --ion-color-success-contrast: #000000;
  --ion-color-success-contrast-rgb: 0,0,0;
  --ion-color-success-shade: #29c467;
  --ion-color-success-tint: #44e283;

  --ion-color-warning: #FFD534;
  --ion-color-warning-rgb: 255,213,52;
  --ion-color-warning-contrast: #000000;
  --ion-color-warning-contrast-rgb: 0,0,0;
  --ion-color-warning-shade: #e0bb2e;
  --ion-color-warning-tint: #ffd948;

  --ion-color-danger: #FF4961;
  --ion-color-danger-rgb: 255,73,97;
  --ion-color-danger-contrast: #ffffff;
  --ion-color-danger-contrast-rgb: 255,255,255;
  --ion-color-danger-shade: #e04055;
  --ion-color-danger-tint: #ff5b71;

  --ion-color-dark: #F4F5F8;
  --ion-color-dark-rgb: 244,245,248;
  --ion-color-dark-contrast: #000000;
  --ion-color-dark-contrast-rgb: 0,0,0;
  --ion-color-dark-shade: #d7d8da;
  --ion-color-dark-tint: #f5f6f9;

  --ion-color-medium: #989AA2;
  --ion-color-medium-rgb: 152,154,162;
  --ion-color-medium-contrast: #000000;
  --ion-color-medium-contrast-rgb: 0,0,0;
  --ion-color-medium-shade: #86888f;
  --ion-color-medium-tint: #a2a4ab;

  --ion-color-light: #222428;
  --ion-color-light-rgb: 34,36,40;
  --ion-color-light-contrast: #ffffff;
  --ion-color-light-contrast-rgb: 255,255,255;
  --ion-color-light-shade: #1e2023;
  --ion-color-light-tint: #383a3e;
}

/* Customize the Toolbar Segment by Mode */
.ios {
  --ion-background-color: #000000;
  --ion-background-color-rgb: 0,0,0;

  --ion-text-color: #ffffff;
  --ion-text-color-rgb: 255,255,255;

  --ion-border-color: #222222;

  --ion-color-step-50: #0d0d0d;
  --ion-color-step-100: #1a1a1a;
  --ion-color-step-150: #262626;
  --ion-color-step-200: #333333;
  --ion-color-step-250: #404040;
  --ion-color-step-300: #4d4d4d;
  --ion-color-step-350: #595959;
  --ion-color-step-400: #666666;
  --ion-color-step-450: #737373;
  --ion-color-step-500: #808080;
  --ion-color-step-550: #8c8c8c;
  --ion-color-step-600: #999999;
  --ion-color-step-650: #a6a6a6;
  --ion-color-step-700: #b3b3b3;
  --ion-color-step-750: #bfbfbf;
  --ion-color-step-800: #cccccc;
  --ion-color-step-850: #d9d9d9;
  --ion-color-step-900: #e6e6e6;
  --ion-color-step-950: #f2f2f2;

  --ion-item-background: #1c1c1e;
  --ion-item-background-activated: #19191a;
}

.md {
  --ion-background-color: #121212;
  --ion-background-color-rgb: 18,18,18;

  --ion-text-color: #ffffff;
  --ion-text-color-rgb: 255,255,255;

  --ion-border-color: #222222;

  --ion-color-step-50: #1e1e1e;
  --ion-color-step-100: #2a2a2a;
  --ion-color-step-150: #363636;
  --ion-color-step-200: #414141;
  --ion-color-step-250: #4d4d4d;
  --ion-color-step-300: #595959;
  --ion-color-step-350: #656565;
  --ion-color-step-400: #717171;
  --ion-color-step-450: #7d7d7d;
  --ion-color-step-500: #898989;
  --ion-color-step-550: #949494;
  --ion-color-step-600: #a0a0a0;
  --ion-color-step-650: #acacac;
  --ion-color-step-700: #b8b8b8;
  --ion-color-step-750: #c4c4c4;
  --ion-color-step-800: #d0d0d0;
  --ion-color-step-850: #dbdbdb;
  --ion-color-step-900: #e7e7e7;
  --ion-color-step-950: #f3f3f3;

  --ion-item-background: #1A1B1E;
}

This is not finalized, but when it is we will add it to the conference app and once we're satisfied with it we will add it to the starters as a toggle.

A few observations, all for the iOS theme (MD theme looks OK):

The empty white circle for Unchecked by Default checkmark isn’t visible enough. Maybe the circle color is too dark or the circle line is too thin.
The light-gray background inside the Blueberry off toggle, doesn’t have enough contrast with the background gray. I compared with the iOS13 screenshot you posted above and there is a small color difference. #303032 in your ionic screenshot vs #3B393F in your iOS13 screenshot.

Not sure if these need attention, maybe its OK the way it is:

The filled-gray circle around ‘Light’ checkmark has almost the same color as background.
The toggle handle is now white (text-color) which looks great everywhere except for the ‘light’ toggle Blackberry. The handle is almost not visible inside the toggle’s filled area, not enough contrast in color or not enough shadow.

Thanks a lot for all the effort you are putting into this.

A few observations, all for the iOS theme (MD theme looks OK):

I fixed the checkmark, but the toggle is due to us having to match light mode first. We can use an rgba of the text color, but that only has it looking perfect in light mode. In order to match their #E9E9E9 in light theme our dark theme becomes:
Ours uses #303030
Native iOS uses #393939

Not sure if these need attention, maybe its OK the way it is:

Our Ionic colors will not always look great on top of every background. It is up to you to design your app to only use colors where appropriate. Just like in a light theme application, you could have a dark header that you want a light checkbox on, for example, where it would be visible.

There is no way for us to provide extra contrast based on the color, unless we were to use the contrast of the color but then it becomes a black knob and goes against the iOS standard. I think this is still fine because even in iOS 12 they used a white knob on a white background, and the "off" and "on" states are completely different.

Here's a dev release of the fixes from #18735 if you'd like to try it out:
in Core
npm i<EMAIL_ADDRESS>
in Angular:
npm i<EMAIL_ADDRESS>

@brandyscarney what is generating those screenshots that you are posting showing the different themes?  Is this just a demo app or something else?  This would be SUPER useful for us when theming apps for different projects if it's something we can get access to.
Thanks!!

@ghenry22 It's one of our e2e tests, here: https://github.com/ionic-team/ionic/tree/master/core/src/themes/test/css-variables

@ghenry22 It's one of our e2e tests, here: https://github.com/ionic-team/ionic/tree/master/core/src/themes/test/css-variables

Awesome thanks!

Really nice design 👍

I started messing around with ideas for how we can provide the official dark theme to the developers. There are a few different ways we could add this.

We could expose a CSS class that has the CSS set for ios and md, something like ion-dark-theme. This would include the CSS I linked here, but instead of using :root it would target .ion-dark-theme: https://github.com/ionic-team/ionic/issues/18713#issuecomment-510644371

Problem 1: there would be less control over the variables as a developer so you would have to know what to change if you wanted to tweak it
Problem 2: it wouldn't work with prefers-color-scheme in the CSS, the developer would have to set the class via JavaScript, however this can be done by setting a variable in the media query and changing the class that way.

We could expose a Sass mixin that can be used to include the relevant variables in a project, see https://www.sassmeister.com/gist/9e68689abc4ffd0b514e933da98379a0

Problem 1: Same as 1, less control
Problem 2: Not all users are using CSS, they would need an alternative

We could add the CSS variables / themes directly to the starters so that developers would have our provided styles for a dark theme and full control over changing them.

Problem: Any updates to the dark theme would have to be manually copied as a developer from the starter when it changes, plus we would have to update each of them every time.

Let me know if anyone has ideas I'm missing!

IMO this could just be put into the documentation with the other generator stuff:
https://ionicframework.com/docs/theming/color-generator
Top option could be light vs dark.
This way you're not adding bloat to the framework and it all still fits with convention.

Thanks for the feedback @CitizenBeta! I agree, I think it would be easier maintenance to have a docs page devoted to theming in dark mode and maybe some demos to show it off. I put together this Codepen on our official Ionic account: https://codepen.io/ionic/pen/zYOpQLj

I created a new guide for dark mode in the docs in this PR: https://github.com/ionic-team/ionic-docs/pull/940
Here is the main file in a README format: https://github.com/ionic-team/ionic-docs/blob/3e76eac99772bb2921b33912a04d9e1290688225/src/pages/theming/dark-mode.md
Please let me know any feedback of how this can be improved, anything missing, and anything else. Thank you!

Added a guide on dark mode here: https://ionicframework.com/docs/theming/dark-mode
Please let us know if you have any feedback for docs improvement on this repo: https://github.com/ionic-team/ionic-docs
Thank you!!


Fix compilation error with Visual Studio 2019 or 2022

Since commit https://github.com/troldal/OpenXLSX/commit/efff9af403f481d075b8c3eb11b9035539147964
OpenXLSX has compilation error with Visual Studio 2019
error C2059: syntax error: 'template'
see https://github.com/troldal/OpenXLSX/issues/129
This PR fix the compilation error

@troldal I think this very simple fix is fine to compile with visual studio


factory: LazyFunction to just call a function in the simplest case

No need to wrap it in a lambda to strip the object argument from LazyAttribute or the sequence argument from Sequence.
I just left the part about adding .. versionadded: and updating the changelog. I'm not sure how to fill them.

Thanks!


Uncaught exception 'Zend_Log_Exception' with message file.log cannot be opened with mode “a”

I don't know how to use php, I am developing java.I thought about this error when I deployed a PHP project.
 Fatal error: Uncaught exception 'Zend_Log_Exception' with message '"/home/hystream-apps-test/TOMS/application/../data/log/Ec_Error.log" cannot be opened with mode "a"' in /home/hystream-apps-test/TOMS/libs/Zend/Log/Writer/Stream.php:81 Stack trace: #0 /home/hystream-apps-test/TOMS/libs/Ec/Bootstrap.php(36): Zend_Log_Writer_Stream->__construct('/home/hystream-...') #1 /home/hystream-apps-test/TOMS/libs/Zend/Application/Bootstrap/BootstrapAbstract.php(669): Bootstrap->_initLogging() #2 /home/hystream-apps-test/TOMS/libs/Zend/Application/Bootstrap/BootstrapAbstract.php(622): Zend_Application_Bootstrap_BootstrapAbstract->_executeResource('logging') #3 /home/hystream-apps-test/TOMS/libs/Zend/Application/Bootstrap/BootstrapAbstract.php(586): Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap(NULL) #4 /home/hystream-apps-test/TOMS/libs/Zend/Application.php(362): Zend_Application_Bootstrap_BootstrapAbstract->bootstrap(NULL) #5 /home/hystream-apps-test/TOMS/public/index.php(110): Zend_Application->bootstrap() #6 {main} thr in /home/hystream-apps-test/TOMS/libs/Zend/Log/Writer/Stream.php on line 81

Couple things here:

cannot be opened with mode "a" pretty much says it all
ZendFramework 1.x (the one you are having in your stack traces) was discontinued in 2016 (https://framework.zend.com/blog/2016-06-28-zf1-eol.html)

Closing, as this is not an issue within this library.


Fixes #5 Resolves memory leak caused by not invalidating the session

Good catch on the memory leak. Can you update the changelog as well?

Nice one 👍


Consolidate assemblies and modules + remove empty directories

Versions:
1.1+
Description:

Moves all assembly files to the assemblies directory
Moves all module files to the modules directory
Updates the file paths to assembly/module files referenced in master.adoc files
Deletes empty directories
Temporarily resolves an existing issue with cross-title references, which will be fully resolved by a future PR
Removes trailing whitespaces (via auto script)

Jira links:
https://issues.redhat.com/browse/RHIDP-2273
https://issues.redhat.com/browse/RHIDP-2274
https://issues.redhat.com/browse/RHIDP-2276
Preview link:
Reviews:
QE:
Peer review:

@linfraze Can we get a jira in the title of this? Maybe an epic covering the 3 jiras.

/cherrypick 1.1.x


Terminal suggest: Make first directory completion the same directory itself to make it easier to cd to a directory that contains sub-dirs

Currently after completing scripts:

I think when the directory is an argument*, we should have the first entry as .\scripts\, such that you could press enter to run it via default runOnEnter settings.
* This only makes sense for arguments not commands, since you can't run a directory
cc @sbatten

To verify:

mac/windows
Suggest enabled
Open pwsh terminal
Type cd
Press tab to complete, verify the folder that was completed is the first completion provided.


Kubernetes deployment

In the section "Bring your own backend", the provided opentelemetry-collector configuration didn't work for me. The opentelemetry-collector pod failed because service/pipelines/traces/exporters was missing spanmetrics. I used the service configuration below and it worked.
service:
pipelines:
traces:
processors: [memory_limiter, batch]
exporters: [otlp, logging, spanmetrics, otlphttp/example]

@fabric73 feel free to raise a PR to fix this issue


Enabled customize lb port for ingressgateway and tracing.

Fixed https://github.com/istio/istio/issues/6000
/cc @sdake @linsun @costinm @morvencao

@gyliu513: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
da1dc2cef886cecad23812f1dfbbd7afbb404249
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513 Anther few files need updated:
https://github.com/istio/istio/blob/master/install/kubernetes/helm/istio/charts/tracing/templates/deployment.yaml#L26
https://github.com/istio/istio/blob/master/install/kubernetes/helm/istio/charts/tracing/templates/deployment.yaml#L46
https://github.com/istio/istio/blob/master/install/kubernetes/helm/istio/charts/tracing/templates/deployment.yaml#L50
https://github.com/istio/istio/blob/master/install/kubernetes/helm/istio/charts/tracing/templates/service-jaeger.yaml#L22

@morvencao done, thanks.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
567856e152114b7b34c54f119508f76032f39e03
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
59f3d576d534e867e6f0819aa32695cd368f13db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gyliu513
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [gyliu513]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-simpleTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gyliu513, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [gyliu513,rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

prow/e2e-mixer-no_auth.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@rshriram can you please remove your Requested changes so that this can be merged?

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
3330c7a390ee858dd68ae465ab20df53863321a6
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-dashboard.sh
e43e541e8c59abb225b68c9722dc64eda092fdab
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Documentation page hsts error

When i want to check documentation the browser blocks me because of hsts error.

This is basically an expired HTTPS cert issue. Can @vsevex get that renewed?


Number of dice rolls with target sum

The leetcode problem with solution

please change the directory and create a new PR . I need to revert this because you need to put this in the folder and you have added it in the main directory.


[TASK] re-enable User login and investigate the compatible functionality.

Description
previously, we disabled the functionality of user events. Now there are new requirements to enable user events in events manager. We will investigate the compatible functionality of user events in the current code base of the events manager.
Acceptance Criteria
user events login. check the functionality of user events.

User Events feature is now part of Events Manager. Closing.


fix(orphan-blocks): added kv pair to show canonical status

Issue: https://github.com/hirosystems/explorer/issues/1376
I added this canonical key value pair when the block is not canonical to show when the block is orphaned or not.
@GinaAbrams Do you think this is ok? Or do you want to design this differently?

@GinaAbrams Do you think this is ok? Or do you want to design this differently?

Did you mean to tag @eugeniadigon perhaps?

I think it's okay, but we may want to provide some guidance on what this means. For example, do we have an explanation as to why a given block was orphaned?

I think it's okay, but we may want to provide some guidance on what this means. For example, do we have an explanation as to why a given block was orphaned?

Sometimes two blocks get mined almost simultaneously. Then BTC miners may end up mining blocks for both of those blocks. When one of those blocks gets another block and becomes the longest chain, then miners will switch to supporting that chain, leaving the other mined block orphaned.

Sometimes two blocks get mined almost simultaneously. Then BTC miners may end up mining blocks for both of those blocks. When one of those blocks gets another block and becomes the longest chain, then miners will switch to supporting that chain, leaving the other mined block orphaned.

Thanks for the explanation. Could we add a (?) icon and a modal that explains this?
https://www.figma.com/design/31q1g27k69z1yXb6r6vrRD/Stacks-Explorer-Working-File?node-id=8683-8293&t=EXZuHa5wrmnokYXu-1

@eugeniadigon
Does this work?

@eugeniadigon
Does this work?

Looks good to me 👍

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


Updates by @vsoch

This is a (work in progress) pull request to show progress on the draft. I'm going to first go through the bullets and then (if appropriate) write them into more human friendly sentences.
Signed-off-by: Vanessa Sochat<EMAIL_ADDRESS>

hey @nuest ! I'm all done with my changes, specifically I've taken all bullet points and flushed them out into full fledged lines. As instructed, when a reference was needed I added a link or REF. This should be ready to merge, I won't be doing any further work on it, at least until there is a more finalized draft to look at.
I generally maintained all rules / structure, with the exception of Rule 8 (add the build/run to comments at end) which was redundant from a previous rule to suggest using comments for transparency, etc. What I did is move content from there into that issue, and modified rule 8 to be about creating a protocol for starting a new project (which was missing and I think important).
Please merge and tweak to your needs! I'm moving cross country in the next two weeks plus a conference, so I wanted to get this finished for you today. Cheers!

ping @nuest - did you see this?

Yes @vsoch - thank you for the reminder! A deadline took control of my last two weeks, and I am traveling now, but will take a look at it by the end of the week. I can already say: Wow! :open_mouth:
There's also plenty of discussion issues to follow up on - this manuscript is my reward for the other submitted one ;-) and I look forward to reading your work.

Hi Vanessa - thanks for pushing the manuscript a huge step forward!
I'm working through your changes now, will create a new PR for you and the others to take a look at soon.

Sorry, I just realised that my pushes go of course directly to master. So, first changes after this PR are in https://github.com/nuest/ten-simple-rules-dockerfiles/commit/4a87e3e3ad43feacd98722f1521e500191bb17bb - will update here tomorrow with more.


chore: add npm semver calculator

This page helps us find the version of that module on npm match range.

I created #927 with backtick :)

Yep, the description still doesn't quite match my suggestion though.
[npm semver calculator](https://semver.npmjs.com/) - Semantic version calculator, useful for determining match range in `package.json`.
The beginning of the description is different and you're missing a period.

There's never a need to open a new PR. Next time just push addition commits.

There's never a need to open a new PR. Next time just push addition commits.

I know that, but I deleted that fork repo so I push a commit to that branch but it doesn't update.

but I deleted that fork repo

Don't do that.


Clang format

Thanks @superjax. This is probably great, but I'm not entirely clear on what's actually new...
Is this one only clang-format stuff? Is there some extension in VScode that's reformatting code for you? I develop this in VScode and it doesn't make changes for me. Doing a clang-format thing would probably be great, but this is also mangling a few things I don't want mangled. For now, would it possible for you to turn off whatever extension is changing stuff, then redo #9?

Sure thing!
All you do is add "editor.formatOnSave": true, to the settings.json and install the Clang-format extension.
What is the formatter doing that you don't like?


[FR]: tracker: only add tag if matched to a rule I.e. don't create new tags

Is your feature request related to a problem? Please elaborate.
The tracker tagging feature ensures that every torrent has at least one tracker-related tag on it. It creates new tags when it can't find an existing one based on the tracker rules set in the config (unless other is used).
Describe the solution you'd like
The way I'd like to use tags for trackers is to have qbit_manage add tags where possible based on rules, but then ignore torrents where it can't find a rule. That way I can go through on a case-by-case basis and manage those myself, or create new rules for them if appriopriate.
More specifically, another config option to disable creation of new tags when no match is found and other is not set would fit my desired use-case.
Does your solution involve any of the following?

[X] New config option
[ ] New command option

Describe alternatives you've considered
I've considered just leaving the other rule set, but that means every torrent that doesn't match my rules will have that tag in addition to whatever tag I set manually, making it redundant.
Who will this benefit?
Users of the 'tracker' function, especially those who utilise many different trackers that they don't want to create rules for, but still want to track via tags (manually).
Additional Information
No response

so summarizing the request:
Allow setting tag for trackers not covered and would fall under other as blank ?

so summarizing the request:
Allow setting tag for trackers not covered and would fall under other as blank ?

Yes sir.

Should be able to do this existing - set the tag to ""

Should be able to do this existing - set the tag to ""

Oh, awesome. I can confirm that works as I hoped it would. Thanks!
Maybe it's worth including a line in the sample config file mentioning this?


(Monitoring) Update grafana Last Submission Time Offset based on submission interval

separate long term submission pairs and short term submission pairs

since the interval is not too much different among pairs, will be closed


random_zoom() does not zoom x & y proportionally

Hi,
It seems that random_zoom() makes two separate zoom rates for x and y, which causes distortion rather than zooming.
https://github.com/fchollet/keras/blob/master/keras/preprocessing/image.py
line 165
zx, zy = np.random.uniform(zoom_range[0], zoom_range[1], 2)
should not it be instead:
zx = zy = np.random.uniform(zoom_range[0], zoom_range[1])
Cheers
Kirill Makukhin

This is intentional, and it was like that from the every first Keras public release. I think some way of  preserving aspect ratio is warranted, but I'd rather wait for Tensorflow API and adopt it. Can anyone point to such or a discussion of such?


Forth tag

Please create a "Forth" tag and ... for this project.

https://cdn1.savepice.ru/uploads/2020/6/28/523f0c8ff3de4787152058d0816e8cd1-full.png
(Topics)


WIP: Strimzi 0.32

Fixes #

Proposed Changes

Release Note

Docs

/retest
meh
On Mon 5. Dec 2022 at 12:12, knative-prow[bot] @.***>
wrote:

@matzew https://github.com/matzew: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
upgrade-tests_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/upgrade-tests_eventing-kafka-broker_main/1599712060868923392
true /test upgrade-tests
channel-integration-tests-ssl_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/channel-integration-tests-ssl_eventing-kafka-broker_main/1599712061061861376
true /test channel-integration-tests-ssl
channel-integration-tests-sasl-ssl_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/channel-integration-tests-sasl-ssl_eventing-kafka-broker_main/1599712061124775936
true /test channel-integration-tests-sasl-ssl
reconciler-tests-namespaced-broker_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/reconciler-tests-namespaced-broker_eventing-kafka-broker_main/1599712061007335424
true /test reconciler-tests-namespaced-broker
reconciler-tests_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/reconciler-tests_eventing-kafka-broker_main/1599712060948615168
true /test reconciler-tests
integration-tests_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/integration-tests_eventing-kafka-broker_main/1599712060738899968
true /test integration-tests
integration-tests-namespaced-broker_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/integration-tests-namespaced-broker_eventing-kafka-broker_main/1599712060801814528
true /test integration-tests-namespaced-broker
channel-reconciler-tests-sasl-plain_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/channel-reconciler-tests-sasl-plain_eventing-kafka-broker_main/1599712063083515904
true /test channel-reconciler-tests-sasl-plain
channel-reconciler-tests-ssl_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/channel-reconciler-tests-ssl_eventing-kafka-broker_main/1599712061409988608
true /test channel-reconciler-tests-ssl
channel-integration-tests-sasl-plain_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/channel-integration-tests-sasl-plain_eventing-kafka-broker_main/1599712061183496192
true /test channel-integration-tests-sasl-plain
channel-reconciler-tests-sasl-ssl_eventing-kafka-broker_main a773191
https://github.com/knative-sandbox/eventing-kafka-broker/commit/a7731918f113b491ab8bb8636bcf478ac08dc96a
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/2822/channel-reconciler-tests-sasl-ssl_eventing-kafka-broker_main/1599712062244655104
true /test channel-reconciler-tests-sasl-ssl
Your PR dashboard https://prow.knative.dev/pr.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/knative-sandbox/eventing-kafka-broker/pull/2822#issuecomment-1337156074,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABGPTQ7W4CRI46GZ6UWIKTWLXEZPANCNFSM6AAAAAASUDBWPI
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sent from Gmail Mobile

/retest

/retest

/retest

Its currently download and patch (since https://github.com/knative-sandbox/eventing-kafka-broker/pull/2381).
But, they (Strimzi) also released 0.33 today.
I will update to that soon, where I will change the procedure to just download, and we sed the namespaces ...


Marketplace service new api for manifest

The goal here is to add validation of the manifest data directly with the core by passing all arguments necessary to the service and giving responsibility to the service to manage how it wants to upload this manifest (with IPFS or whatever).
This remove a lot of logic from the client and also remove the management of version from the client, now the service manages the version (we change the service == we change the version).
The client doesn't need to know anything about how data are stored in the marketplace IPFS or no. For now we still need to upload the sources but ultimately we should even give directly the tarball to the system service and let it handle everything
@NicolasMahe want to have your feedback before I continue to make sure that this is aligned with what you want with #829 and #835
TODO:

[x] fix error with ./dev-cli service execute marketplace --task getService --data sid=myservice

All the unnecessary dev on this PR has been reverted, now only the publishService has been updated, the rest will be done in other PR if necessary


ddox duplicates declarations

Situation:
module mod;

class Base {
   int field;
}

class A : Base {
}

In this case ddox duplicates field declaration on Base.field page as many times as the module has Base subclasses. Look

I've seen this happen, but for some reason it's not reproducible for me now. If it still happens for DDOX master, can you post the compiler version and/or the json file that was generated? Maybe it already happens in an earlier stage.

Bug is still present. Done simply with dub build -b ddox, ddox version is 0.15.0 (master), dmd version is 2.071.0-0.
docs.json:
[
	{
		"file": "source/app.d",
		"name": "mod",
		"members": [
			{
				"name": "Base",
				"line": 3,
				"members": [
					{
						"offset": 16,
						"name": "field",
						"line": 4,
						"deco": "i",
						"char": 6,
						"kind": "variable"
					}
				],
				"char": 1,
				"kind": "class"
			},
			{
				"members": [],
				"name": "A",
				"line": 7,
				"base": "mod.Base",
				"char": 1,
				"kind": "class"
			}
		],
		"kind": "module"
	}
]

OK, it just happened for "generate-html" and I used to test with "serve-html". Fixed now.


doc: Clarify the Repository lifecycle

fix #36

Having the process outlined is goodness. Archiving a repo that's been dormant may not mean the project isn't useful for others to consume as reference. It may just be stable and doesn't need additional changes. In this case, archiving can indicate it's stable, and not taking additional changes, because there aren't any maintainers, or the project is simply stable.
I'd also suggest adding text that a repo must have at least 30 days notice to its maintainers before archival is completed.
Deleting a project is far more destructive and removes content that others may need. I'd suggest we clarify under what circumstances a project would be deleted, vs. archived.

Having the process outlined is goodness. Archiving a repo that's been dormant may not mean the project isn't useful for others to consume as reference. It may just be stable and doesn't need additional changes. In this case, archiving can indicate it's stable, and not taking additional changes, because there aren't any maintainers, or the project is simply stable.
I'd also suggest adding text that a repo must have at least 30 days notice to its maintainers before archival is completed.
Deleting a project is far more destructive and removes content that others may need. I'd suggest we clarify under what circumstances a project would be deleted, vs. archived.

Thanks @SteveLasker for the suggestions. I added a paragraph about the archival notice and removed the "Removal" section according to your inputs above.

What about deleting, renaming, and transferring out a repository?

@shizhMSFT I added a section for Renaming. Deleting and transferring out a repository are not common cases so we could consider adding them in the future. Keep the content as minimum viable would be easier to review.

/cc @notaryproject/notaryproject-governance-maintainers to help review this PR.


[OTHER] Banned from discord

What would you like to share?
Hi,
I was banned from the discord? Why
Additional information
No response

Unfortunately, you were banned because kept breaking rule number 1, please see screenshot attached

Unfortunately, you were banned from Discord because kept breaking rule number 1 😢 , please see screenshot attached.
We appreciate your open source collaboration on GitHub, if there is anything we can do to help, please let us know 🤓

Yeah, I'm really sorry about that and understand the decision.
I basically had a plan to start a open source organization and wanted to ask for feedback from the server and ideas, if possible.

Hi Kendall, after some discussion we have decided to remove the Discord ban. However please read and consider the rules before rejoining
We look forward to collaborating with you again publicly not in DMs - as we say in EddieHub collaboration 1st Code 2nd.

Hi Kendall, after some discussion we have decided to remove the Discord ban. However please read and consider the rules before rejoining
We look forward to collaborating with you again publicly not in DMs - as we say in EddieHub collaboration 1st Code 2nd.

Hi Eddie, Thanks for the decision made by yall. I really appreciate it.
Yes, I will ensure not to dm anyone relating to help of my projects, without their permission to dm them.


Conditionally use Logger.warning/1

Fixes the Logger.warn/1 hard deprecation in Elixir 1.15.

There is already #4212, which we will merge as part of 3.11. :) Thanks!

Oooph, didn't see https://github.com/elixir-ecto/ecto/pull/4212, was closing this now 🤦


Preparations for publishing first version.

Linked to issue #7.
Discussed license change with Theo.

Merging, since it is public now, to update the license.


Bump yip

This commit bumps yip to include latest updates in datasource plugin
Signed-off-by: David Cassany<EMAIL_ADDRESS>

This is an attempt to fix rancher/elemental-operator#50. Datasource yip's plugin used to leave block device files opened, then later parted utility complained time to time the block device is in use and hence fail.

Rebase is needed

Closing as this is no longer needed. Bumping to latest yip will only include small commit over the cdrom datasource provider which is no longer in use. Moreover this small patch mudler/yip@976737b2353c982e34adeaf09038c2d3acb4e9ec was not enough to prevent linuxkit to leave probed devices opened when using the cdrom provider. As discussed in https://github.com/rancher/elemental-operator/issues/50#issuecomment-1195300014 we simply stopped using the cdrom datasource provider.


Install Flatpaks without prompting in Yafti

If you're going through the effort of rebasing your image, I think it is safe to install the default set of Flatpaks without prompting.
Not sure if this should just be in some one-time-run startup script, or something else.

Related: I happened across this in the Flatpak docs today:

System-wide remotes can be statically preconfigured by dropping flatpakrepo files into /etc/flatpak/remotes.d/.

That could be a lot cleaner than leaning on Yafti to add system remotes, at least.


[STORM-3093] Cache the storm id to executors mapping on master to avo…

What this patch for
Now nimbus will collect all the topologies's conf/topology-ser/storm-base to compute in a scheduling round, which is a very heavy work. The scheduling will still take to minutes even we now change to RPC heartbeats and assignment distribution.
So i decide to redesign the scheduler, so we can only schedule the topologies that need to: that have dead workers or not enough number workers.
Here i checkout out the code and found that the id->executors mapping is computed every time for every topology, which is really a heavy computation and totally not that necessary, because this mapping is fixed invariable for a topology unless we rebalance or kill it.
So i refactor the code a little here, and this is more powerful after the scheduler is resigned for delta-scheduling[ which is very lightweight even there are thousands of topologies on one cluster.]
For now this is enough for us.
This is the JIRA: STORM-3093.

Looks good. Do you have any performance test results to share so that we can have an idea how much performance gain this patch gets? It's fine if you don't have it

@Ethanlm
Sorry i have not did the benchmark test, but we can see the promotion through the storm-core module building time, it's about 10 seconds faster on my laptop.
I can add in the test cases if if it needed.

The travis failure looks unrelated.


Changing tempo changes perceived playback time flow

After changing the tempo, the playback time is scaled, while the remaining time is not. It should be the other way around - the playback time should flow unchanged and the remaining time should get scaled by the tempo.

Fixed in #78.


Feature/support intellij idea 2023.3

https://plugins.jetbrains.com/docs/intellij/general-threading-rules.html#read-write-lock

🚀 Description

📄 Motivation and Context

🧪 How Has This Been Tested?

📦 Types of changes

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

✅ Checklist

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.

Hi, daejoon. Are you interested in maintaining this project together. I'd like to invite you to join the project.

Thank you. Please invite me.


EmitSoundSystem needs to be able to take both soundCollections and sounds

Description

Currently Vox/Snake/Mouse plushies make no sound when squeezed because whoever refactored ToysComponent into EmitSound component forgot to update the sound: fields in the yaml.
I don't think creating a sound collection for single sounds is good practice so EmiteSoundSystem needs to take both soundCollection IDs and sound paths.

agree

I did  the refactor. The first version of the PR had support for both sound collections and single sounds, but I got suggestions about not needing both. I'll revert the removal of sound collections from EmitSoundSystem

Honestly, we should just have an union-like data structure that can hold either a single sound or a collection and use that everywhere. Duplicating so much code across anything that could ever play sound is awful, honestly...

#4239 will help with this


Add Heron list of ADOPTERS

Start a list of Heron adopters, it's convenient to see who is using Heron in production!
See Finagle as an example: https://github.com/twitter/finagle/blob/develop/ADOPTERS.md

looks good. we can also display this list on the website.

I'm sure @kramasamy can add more in this list, but it's just a start, it's more important we have a location to adopters to be listed :)

👍


Fix : display items 20

Please increase table number from 6 to 20

Hello. I have adjusted the height of the table.


the character interrupt frequently when they talks

When I talk to the character,  they talk  smoothly at the first, but  it frequently interrupt half way, and the log is TIMEOUT: interim transcript: xxxx

just observeration - in aws / alexa - they seem to get around this with a Brief Mode - playing just a beep.
maybe suitable enhancement here.
https://www.lifewire.com/how-to-use-alexa-brief-mode-4683987#:~:text=enable Brief Mode%3A-,Open the Alexa app on your device.,Mode to the On position.

When I talk to the character, they talk smoothly at the first, but it frequently interrupt half way, and the log is TIMEOUT: interim transcript: xxxx

I also encountered this problem, on the web side, and it was very slow to even have a reply. Have you solved it?


[Launcher] Search for folders should display shallow folders first.

Summary of the new feature/enhancement
Whenever a folder is searched in the launcher, the results are displayed in a seemingly random order.
For example, searching Appdata shows me a list like:
C:\Users\alias\some_path\AppData
.
.
C:\Users\alias\Appdata
I would like the search to return shallow matching results first, since these are likely the ones that I am looking for.
Proposed technical implementation details (optional)
In the above example, I would like the search to show C:\Users\alias\Appdata above the other options.

I would definitely like this to be optional behavior, if it were implemented. My preferred sort order in the typical case would be on last accessed (if available) or last modified.


Don't fail when createWriteStream() is called twice before mediasource opens

This fixes the exception that was reported in https://github.com/jhiesey/videostream/issues/22
A simple way to test this is to immediately call createWriteStream() again, i.e.:
var writable = wrapper.createWriteStream('video/webm; codecs="vorbis, vp8"')
writable = wrapper.createWriteStream(writable)

This should behave identically to just the first line.

Note that the newest videostream won't run into this error anymore, but it's still good to fix it.

I added a test and released this as 2.1.2.

Nice work! :+1:


feat: create policy for projects

This PR adds an endpoint to create a policy for a project.
Corresponding Proton PR: https://github.com/raystack/proton/pull/363

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

13 of 923 (1.41%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 9.355%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/server/interceptors/authorization.go
0
4
0.0%

proto/v1beta1/frontier_grpc.pb.go
0
26
0.0%

internal/api/v1beta1/policy.go
12
42
28.57%

proto/v1beta1/frontier.pb.gw.go
0
95
0.0%

proto/v1beta1/frontier.pb.validate.go
0
188
0.0%

proto/v1beta1/frontier.pb.go
1
568
0.18%

Files with Coverage Reduction
New Missed Lines
%

proto/v1beta1/frontier.pb.go
1
5.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
9997

Relevant Lines:
106860

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

13 of 927 (1.4%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 9.355%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/server/interceptors/authorization.go
0
4
0.0%

proto/v1beta1/frontier_grpc.pb.go
0
26
0.0%

internal/api/v1beta1/policy.go
12
46
26.09%

proto/v1beta1/frontier.pb.gw.go
0
95
0.0%

proto/v1beta1/frontier.pb.validate.go
0
188
0.0%

proto/v1beta1/frontier.pb.go
1
568
0.18%

Files with Coverage Reduction
New Missed Lines
%

proto/v1beta1/frontier.pb.go
1
5.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
9997

Relevant Lines:
106864

💛  - Coveralls


SWDEV-389650: remove the test from disabletests

to allows CQE to test it to make sure it is fixed on all systems

Signed-off-by: sdashmiz<EMAIL_ADDRESS>Change-Id: I17f20484fd80fc762a1f8277a3b8d9d221e7c8ee

Changes have been merged into develop via commit 2ecfc56b6f0b612562943704dab5fef8b6f677b3.


How to remove bind click event

I added map click event like this:
map.on(plugin.google.maps.event.MAP_CLICK, function(latLng) {
alert("Map is clicked.\n" + latLng.toUrlValue());
});
But how do I remove the bind event, when user left the map view, I want to hide the map and remove the event, currently I use map.remove() to remove the map completely.
Thanks

https://github.com/wf9a5m75/phonegap-googlemaps-plugin/wiki/BaseClass

You're welcome.

Thanks, @Hirbod


Bitwise AND

Title: Bitwise AND
About: Given set S = {1,2,3,....,N}. The aim is to find two integers, I and J (where I<J), from set S such that the value of I & J is the maximum possible and also less than a given integer, K. In this case, '&' represents the bitwise AND operator.
Name: Manasi Chhibber
Label: Feature Request
Assignee: 'Manasi2001'

Define You:

[x] DevIncept Participant
[x] Contributor

Is your feature request related to a problem? Please describe.
The main purpose is to explore bitwise AND operator in python.

Issue assigned. @Manasi2001


chore: GCForms release v3.3.0

:robot: I have created a release beep boop
3.3.0 (2023-09-19)
Features

Add freskdesk API key (d038c81)
notify Slack if Terraform apply fails (#485) (45487c7)

Bug Fixes

Add missing freshdesk api key to ecs task (d8a96ac)
format of TF workflow Slack webhook URL (#496) (4bb5ca2)
Github action logic for release-generator (#479) (dbb3a77)
IAM permission for freshdesk secret (f22ee82)
release generator token step (#495) (ae47a64)
set target Slack channel for notification (#487) (fee609c)

Miscellaneous Chores

deps: lock file maintenance (#467) (d9329d5)
deps: update all non-major docker images (#465) (1766d88)
deps: update all non-major docker images (#488) (1e3d5c3)
deps: update all non-major github action dependencies (#466) (38611b1)
deps: update all non-major github action dependencies (#472) (fb2c43c)
release generator (#475) (31e1b98)
release generator fix (#484) (661cf9a)
synced file(s) with cds-snc/site-reliability-engineering (#468) (563f2af)
synced file(s) with cds-snc/site-reliability-engineering (#490) (74cc135)
synced local '.github/workflows/ossf-scorecard.yml' with remote 'tools/sre_file_sync/ossf-scorecard.yml' (#470) (4565dcf)
synced local '.github/workflows/ossf-scorecard.yml' with remote 'tools/sre_file_sync/ossf-scorecard.yml' (#486) (8b3eee3)
upgrade python image (#471) (e75ef9b)
use GitHub app token with release-please (#491) (92f10eb)

Code Refactoring

split out security group rules from inline (6eaee25)

This PR was generated with Release Please. See documentation.

Closing to see if a new PR will be opened with the new release generator token


touch support

also added requestAnimationFrame

Looks goode to me! Thank you for the contrib! :+1:


Dense ME Conduit's recipe is wrong

Issue Description:
Recipe outputs 8 conduits instead of one, effectively turning 4 ME Conduits into 8 Dense. The recipe should output 1, following the Applied Energistics' Logic.

Affected Versions (Do not use "latest"):

Minecraft: 1.10.2

That issue has come up again in Minecraft 1.12.2, EnderIO-1.12.2-5.0.44 - 4 Ender IO ME Conduits can be made into 4 Ender IO Dense Me Conduits. The ratio is 4 Regular to 1 Dense normally.
https://cdn.discordapp.com/attachments/589526583648190465/589569043267190784/unknown.png

mmmmh... https://github.com/SleepyTrousers/EnderIO/commit/4a4c716555eab367a52793e7ce05cb791018d5fa#diff-38c0adfefbc4985b7d21a31241699932
@EpicSquid any reason you went for different amounts than the original recipes? (see commit from Mar 26, 2017 above)


Log record "extra" fields are missing when using LogstashFormatter

When using LogstashFormatter the specific log record "extra" is missing from the formatted message
from loguru import logger
from logstash_async.handler import AsynchronousLogstashHandler
from logstash_async.formatter import LogstashFormatter

logstash_handler = AsynchronousLogstashHandler(
    remote_host,
    remote_port,
    database_path,
)

logstash_formatter = LogstashFormatter(
    extra={
        'default': 'extra',
    },
)

logstash_handler.setFormatter(logstash_formatter)
logger.add(
    logstash_handler,
    level=level,
    format='{message}',
    backtrace=False,
)

logger.info('some message', extra={'some': 'extra'})

formatted message won't include the extra={'some': 'extra'} but will include  'default': 'extra'
This is because of the _get_extra_fields method which doesn't add the record.extra to the extra fields.
solved it locally by overriding the _get_extra_fields locally
class MyFormatter(LogstashFormatter):
    def _get_extra_fields(self, record):
        extra_fields = super()._get_extra_fields(record=record, )

        if record.extra:
            extra_fields = record.extra | extra_fields
        return extra_fields

thought you might want to add this to the code as well
thanks!

Sorry for the late response.
I can't reproduce the described behavior with your example. It results in a message like (stripped unrelated fields for readability):
{
    "message": "some message.",
    "type": "python-logstash",
    "extra": {
        "some": "extra",
        "default": "extra",
    }
}

Which version of the library are you using?

I'm using python-logstash-async==2.3.0

I just tried with your code again, except that I replaced the logger with a standard Python logger instance and added the handler via logger.addHandler(logstash_handler) and got the expected result.
Might the loguru package related? I don't what it does.

It might be related to loguru but as I mentioned I was able to track the problem, it's related to the _get_extra_fields method and after overriding it with the fix, the issue was resolved, is it ok if I'll open a pr for that fix?

Basically a PR is ok but I would like to understand what's the difference and why it works for me with your example and why not for you.

Feel free to open a PR if you are still interested in and re-open this one. Until then, I like to close this issue.


Make APIs more "swifty"

Nest top-level function defaultDirectoryURL() under CoreDataModel
Nest ChildContext typealias under NSManagedObjectContext extension
Move saveContext() top-level function to extension method on NSManagedObjectContext
Use Equatable auto-synthesis where possible

Closes #120

only (known) failure was pod lib lint.


feat: 5418 - Prices - "Are you sure you want to exit?" feature

What

Now, if we changed something in the "add price" page, we cannot go to the previous page unless we answer the "Are you sure you want to exit?" question.

Screenshot

Fixes bug(s)

Closes: #5418
Closes: #5626

Impacted files

price_add_product_card.dart: now accessing amount items through specific methods
price_amount_card.dart: now accessing amount items through specific methods
price_amount_model.dart: new hasChanged getter
price_model.dart: new hasChanged getter; now giving access to amount items through specific methods
price_proof_card.dart: minor refactoring
product_price_add_page.dart: used WillPopScore2 in order to check for changes against back gesture; now accessing amount items through specific methods
user_preferences_prices.dart: usage of AppNavigator for a better management of back gesture

Codecov Report
Attention: Patch coverage is 0% with 99 lines in your changes missing coverage. Please review.

Project coverage is 6.98%. Comparing base (4d9c7fc) to head (c88a91f).
Report is 384 commits behind head on develop.

Files with missing lines
Patch %
Lines

...h_app/lib/pages/prices/product_price_add_page.dart
0.00%
49 Missing :warning:

...kages/smooth_app/lib/pages/prices/price_model.dart
0.00%
27 Missing :warning:

...mooth_app/lib/pages/prices/price_amount_model.dart
0.00%
13 Missing :warning:

...smooth_app/lib/pages/prices/price_amount_card.dart
0.00%
4 Missing :warning:

...lib/pages/preferences/user_preferences_prices.dart
0.00%
3 Missing :warning:

...h_app/lib/pages/prices/price_add_product_card.dart
0.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5737      +/-   ##
==========================================
- Coverage     9.54%   6.98%   -2.57%
==========================================
  Files          325     406      +81
  Lines        16411   21699    +5288
==========================================
- Hits          1567    1516      -51
- Misses       14844   20183    +5339

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


QEMU guest agent inclusion ?

Would love to see this for graceful shutdown of the warrior VM/OS. Thanks.
I posted this issue over on the warrior docker repo, I guess it makes more sense to post here.  I can close that one to avoid duplication.

Thanks much.  In addition to the shutdown mechanism - the GA also populates the hypervisor with the system IP address of the guest, so it's nice to be able to quickly see that at a glance.

Added in v4.1


BUG: Can't edit/add/remove pages after Migrate To Wiki tool

Hi,
Installed Apps
ERPNext Documentation: v0.0.1 (master)
Frappe Framework: v15.x.x-develop () (develop)
Wiki: v0.0.1 (master)

I successfully migrated erpnext_documentation app to wiki.

When I try to edit/remove/add page, click on Submit Changes, window is gone but nothing happens (no logs).

I noticed that I can edit/remove/add pages on "first time created" wiki:

How can I solve this problem?
Best regards

Hi,
sorry, the errors occurs because of my NGINX configuration.
I got error 413 Request Entity Too Large
solution is add to nginx configuration:
client_max_body_size 100M;


More tests.

[Current coverage][cc-pull] is 61.60%

Merging [#5][cc-pull] into [master][cc-base-branch] will increase coverage by 3.47%

@@             master         #5   diff @@
==========================================
  Files             5          5
  Lines           332        336     +4
  Methods         102        104     +2
  Messages          0          0
  Branches         32         32
==========================================
+ Hits            193        207    +14
+ Misses          126        116    -10
  Partials         13         13

Powered by Codecov. Last updated by [ced03c8...f5d32cd][cc-compare]
[cc-base-branch]: https://codecov.io/gh/DEGoodmanWilson/luna/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/DEGoodmanWilson/luna/compare/ced03c8e93dc5de7c00775ed110a31a3bb8dbd24...f5d32cd7496236dff458cff1d7c991268c6e6b0e?src=pr
[cc-pull]: https://codecov.io/gh/DEGoodmanWilson/luna/pull/5?src=pr


'TheoryDeepPixels.rst' first pass converson from latex

This needs another proofread. The equation numbers and references didn't get converted properly so they had to be recreated by hand. Some LaTeX math didn't render as expected so was changed.
Signed-off-by: Peter Hillman<EMAIL_ADDRESS>

This looks great, barring the few nits noted above. Also, the section title is "Theory of Deep Samples", but the file is called TheoryDeepPixels.rst.  Probably better to make the names consistent. Thanks!


Pull connection effect fix

Fixes https://github.com/LLK/scratch-blocks/issues/906

You also need to change this line: https://github.com/LLK/scratch-blocks/blob/develop/core/insertion_marker_manager.js#L202

Ah thanks @rachel-fenichel. Updated.


Missing include in lv_theme.h

Hi,
in the lv_theme.h file there is no include for lv_theme_material.h, this leads to a compiler error if i try to use the material theme.
Adding the include to the other includes at the end of lv_theme.h solves this problem.
Regards,
Michael

Hi,  lv_theme.h doesn't use anything from lv_theme_material.h. You should analyze more to identify which file requires the lv_theme_material.h...

Aha, sorry... I double checked the lv_theme.h... and all these includes are at the bottom of the file :D So yes, you're right, it should be included to the lv_theme.h and mby move all #include... to the top?

The lv_theme_XXX.h files need the definition of lv_theme_t, so the includes need to stay at the bottom of the file.

There 2 solutions:

Reorganize headers.
Use forward declaration:

a) set some name of struct for lv_theme_t type (for ex. lv_theme_s)
b) in each lv_theme_XXX.h declare somewhere at the top "typedef struct lv_theme_s lv_theme_t; "

lv_theme.h

/**
*@file lv_themes.h
*
*/
#ifndef LV_THEMES_H
#define LV_THEMES_H
#ifdef __cplusplus
extern "C" {
#endif
/*********************

INCLUDES
*********************/
#include "../../lv_conf.h"
#include "../lv_core/lv_style.h"

#include "lv_theme_templ.h"
#include "lv_theme_default.h"
#include "lv_theme_alien.h"
#include "lv_theme_night.h"
#include "lv_theme_zen.h"
#include "lv_theme_mono.h"
#include "lv_theme_material.h"
/*********************

DEFINES
*********************/

/**********************

TYPEDEFS
**********************/

typedef struct lv_theme_s{
lv_style_t *bg;
lv_style_t *panel;
#if USE_LV_CONT != 0
lv_style_t *cont;
#endif
#if USE_LV_BTN != 0
struct {
lv_style_t *rel;
lv_style_t *pr;
lv_style_t *tgl_rel;
lv_style_t *tgl_pr;
lv_style_t *ina;
}btn;
#endif
#if USE_LV_LABEL != 0
struct {
lv_style_t *prim;
lv_style_t *sec;
lv_style_t *hint;
}label;
#endif
#if USE_LV_IMG != 0
struct {
lv_style_t *light;
lv_style_t *dark;
}img;
#endif
#if USE_LV_LINE != 0
struct {
lv_style_t *decor;
}line;
#endif
#if USE_LV_LED != 0
lv_style_t *led;
#endif
#if USE_LV_BAR != 0
struct {
lv_style_t *bg;
lv_style_t *indic;
}bar;
#endif
#if USE_LV_SLIDER != 0
struct {
lv_style_t *bg;
lv_style_t *indic;
lv_style_t *knob;
}slider;
#endif
#if USE_LV_LMETER != 0
lv_style_t *lmeter;
#endif
#if USE_LV_GAUGE != 0
lv_style_t *gauge;
#endif
#if USE_LV_SW != 0
struct {
lv_style_t *bg;
lv_style_t *indic;
lv_style_t *knob_off;
lv_style_t *knob_on;
}sw;
#endif
#if USE_LV_CHART != 0
lv_style_t *chart;
#endif
#if USE_LV_CB != 0
struct {
lv_style_t *bg;
struct {
lv_style_t *rel;
lv_style_t *pr;
lv_style_t *tgl_rel;
lv_style_t *tgl_pr;
lv_style_t *ina;
}box;
}cb;
#endif
#if USE_LV_BTNM != 0
struct {
lv_style_t *bg;
struct {
lv_style_t *rel;
lv_style_t *pr;
lv_style_t *tgl_rel;
lv_style_t *tgl_pr;
lv_style_t *ina;
}btn;
}btnm;
#endif
#if USE_LV_KB != 0
struct {
lv_style_t *bg;
struct {
lv_style_t *rel;
lv_style_t *pr;
lv_style_t *tgl_rel;
lv_style_t *tgl_pr;
lv_style_t *ina;
} btn;
}kb;
#endif
#if USE_LV_MBOX != 0
struct {
lv_style_t *bg;
struct {
lv_style_t *bg;
lv_style_t *rel;
lv_style_t *pr;
}btn;
}mbox;
#endif
#if USE_LV_PAGE != 0
struct {
lv_style_t *bg;
lv_style_t *scrl;
lv_style_t *sb;
}page;
#endif
#if USE_LV_TA != 0
struct {
lv_style_t *area;
lv_style_t *oneline;
lv_style_t *cursor;
lv_style_t *sb;
}ta;
#endif
#if USE_LV_LIST
struct {
lv_style_t *bg;
lv_style_t *scrl;
lv_style_t *sb;
struct {
lv_style_t *rel;
lv_style_t *pr;
lv_style_t *tgl_rel;
lv_style_t *tgl_pr;
lv_style_t *ina;
}btn;
}list;
#endif
#if USE_LV_DDLIST != 0
struct {
lv_style_t *bg;
lv_style_t *sel;
lv_style_t *sb;
}ddlist;
#endif
#if USE_LV_ROLLER != 0
struct {
lv_style_t *bg;
lv_style_t *sel;
}roller;
#endif
#if USE_LV_TABVIEW != 0
struct {
lv_style_t *bg;
lv_style_t *indic;
struct {
lv_style_t *bg;
lv_style_t *rel;
lv_style_t *pr;
lv_style_t *tgl_rel;
lv_style_t *tgl_pr;
}btn;
}tabview;
#endif
#if USE_LV_WIN != 0
struct {
lv_style_t *bg;
lv_style_t *sb;
lv_style_t *header;
struct {
lv_style_t *bg;
lv_style_t *scrl;
}content;
struct {
lv_style_t *rel;
lv_style_t *pr;
}btn;
}win;
#endif
}lv_theme_t;
/**********************

GLOBAL PROTOTYPES
**********************/

/**

Set a theme for the system.
From now, all the created objects will use styles from this theme by default
@param th pointer to theme (return value of: 'lv_theme_init_xxx()')
*/
void lv_theme_set_current(lv_theme_t *th);

/**

Get the current system theme.
@return pointer to the current system theme. NULL if not set.
*/
lv_theme_t * lv_theme_get_current(void);

/**********************

MACROS
**********************/

/**********************

POST INCLUDE

*********************/
#ifdef __cplusplus
} /* extern "C" */
#endif
#endif /LV_THEMES_H/

lv_theme_material.h

/**

@file lv_theme_material.h

*/
#ifndef LV_THEME_MATERIAL_H
#define LV_THEME_MATERIAL_H
#ifdef __cplusplus
extern "C" {
#endif
/*********************

 INCLUDES

*********************/
#include "../../lv_conf.h"
#if USE_LV_THEME_MATERIAL
/*********************

 DEFINES

*********************/
/**********************

 TYPEDEFS

/
typedef struct lv_theme_s lv_theme_t; // forward declaration
/

GLOBAL PROTOTYPES
**********************/

/**

Initialize the material theme
@param hue [0..360] hue value from HSV color space to define the theme's base color
@param font pointer to a font (NULL to use the default)
@return pointer to the initialized theme
*/
lv_theme_t * lv_theme_material_init(uint16_t hue, lv_font_t *font);

/**

Get a pointer to the theme
@return pointer to the theme
*/
lv_theme_t * lv_theme_get_material(void);

/**********************

 MACROS

**********************/
#endif
#ifdef __cplusplus
} /* extern "C" */
#endif
#endif /LV_THEME_MATERIAL_H/

I created a pull request for the missing include.
The reorganization of the header files is not directly related to this issue, so i did not include it in the pr.

Hi,
I added includes for all themes in lv_theme.h to enable the inclusion of all themes at once.
@MiSimon Thank you for highlighting the missing include. I merged your Pull Request.
@BesitzeRuf Thank your for sharing your thoughts! I considered to use of forward declaration. It really would be a more elegant and professional solution. However, as the current organization is quite simple and not requires any additional declaration in the lv_theme_XXX files I would stay with that.


Integrate Pull Requests with a CI tool

It'd be great to start using a CI tool for PR's to test coverages, tests, and linting. The popular open-source one I've used are Travis CI and Circle CI, but I'm open for suggestions.
Any thoughts?

Basic build, and testing implemented through Circle CI. A successful build is now required for all pull requests!


After finetunig the SVD model by MNIST. How to test it?

Can you share the method of fine-tuning SVD?

I am also interested in knowing it :)


right sidebar: Expand sidebar block width for greater click area.

Fixes #9797

Merged, thanks @synicalsyntax!

Just wanted to follow up to make sure we do some pretty careful QA of this in a wide range of cases (really long stream/topic names, mobile views, etc.) -- this component has historically been very prone to subtle bugs when we change the markup.

Oh, oops, I'd misread this as being a related issue about the left sidebar.  Never mind that last comment :).


Explicitly use bash

Since [[ is a bash feature and not part of plain sh it should be used instead in the shebang to prevent errors when the wrong shell is configured as default.

Is there a launchpad issue for this?


Modifiy glut in link libraries

As mentioned here, the GLUT_LIBRARIES is required instead of GLUT_LIBRARY

Thank you for the PR!