[WIP]Azure storage queue binding implementation

Description
Added a binding for azure storage queues
Issue reference
Please reference the issue this PR will close: #143
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: stather sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Great to see this PR.

hey @stather, the tests are failing for the following:
##[error]bindings/azure/storagequeues/storagequeues_test.go:27:1: missing return at end of function
##[error]bindings/azure/storagequeues/storagequeues_test.go:31:1: missing return at end of function
##[error]bindings/azure/storagequeues/storagequeues_test.go:35:1: missing return at end of function

Hi @yaron2 I fixed the failing test. Added injection mocks. Now getting some error got mod.go. Not sure why...

Run go mod tidy and push the changes made to your go.mod file.

LGTM

Thanks for this!


sometimes I'm getting dates instead of IPs in "Top 20 IP addresses that have been accessing your site:"

First of all, thank you for the script! :)
Describe the bug
I have noticed that sometimes I'm getting dates instead of IPs in "Top 20 IP addresses that have been accessing your site:" and "Most recent...".
To Reproduce
Just ran the script with my log.
Expected behavior
There should be only IPs there
Screenshots
Most Recent top 20 IP addresses:
303  2021/05/18   <--- here
167  <IP_ADDRESS>
58   <IP_ADDRESS>
55   <IP_ADDRESS>
50   <IP_ADDRESS>
50   <IP_ADDRESS>
42   <IP_ADDRESS>
42   <IP_ADDRESS>
41   <IP_ADDRESS>
39   <IP_ADDRESS>
35   <IP_ADDRESS>
33   <IP_ADDRESS>
13   <IP_ADDRESS>
11   <IP_ADDRESS>
5    <IP_ADDRESS>
5    <IP_ADDRESS>
4    <IP_ADDRESS>
3    <IP_ADDRESS>
3    <IP_ADDRESS>
2    <IP_ADDRESS>

Input log attached (actually just grep '2021/05/18' ... part of it) my.log

Hi there,
In your case the log seems to have a non-standard format. The script 'assumes that the client IP is the very first column in the log.  I might try to patch this and add some checks.
But in the meantime, you could use this single command to get a quick overview:
cat your_log_file.txt | awk -v FS="(client:|, server:)" '{ print $2 }'  | sort | uniq -c | sort -n

I see! Maybe the issue is the log I have used is actually captured container log, so it mixes both access log and error log (or how is it called). These errors were caused by my Gunicorn miss-configuration. Feel free to reject this if it does not make sense to you.

Hi @jhutar,
Ah yes the mix of error and access logs would explain the problem. In any case I should add a check if the value is a valid IP or not, will work on this soon!


aquamarine.css Is it incompatible with grafana 8.1.3 version

Describe the bug
aquamarine.css Is it incompatible with grafana 8.1.3 version，The following problems occur, how can I solve them, thank you
There is no black color block at the top of the screen, and a white vertical scroll bar appears on the right
Theme Install Method (Don't skip)

rpm -ivh

Application Info (Don't skip)

Version 8.1.3

Expected behavior
The colors on the right and top are consistent with the background color
Desktop (If applicable) (please complete the following information):

OS: [windows]
Browser [chrome]
Version [chrome v94]

Grafana themes are deprecated. If you want to fix any issues you will have to make a pull request.


Helm Chart 4.5.1 hasn't been released to repositories

Description
Helm Chart 4.5.1 hasn't been released to repositories. Artifacthub for example still lists version 4.5.0 as the current one: https://artifacthub.io/packages/helm/k8up/k8up
Please update the repositories.
Additional Context
No response
Logs
No response
Expected Behavior
The current chart (4.5.1) should be available.
Steps To Reproduce
No response
Version of K8up
2.8.0
Version of Kubernetes
1.29.3
Distribution of Kubernetes
K3s

Hi @timbrd
The chart 4.5.1 hasn't been released at all yet.

@Kidswiss Thanks for clarification. Do you know when 4.5.1 will be released? Is there a release schedule? I really would like to use the new option to backup only pvc which are annotated.

K8up currently has no fixed release schedule.
We've planned in to create a new release this sprint. So 4.5.1 should come within 2 weeks.

Thanks. I will wait another 2 weeks for a new release then.


update zk version to 3.5.6

upgrade zk version

tested building locally on my macbook,
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:51 min (Wall Clock)
[INFO] Finished at: 2022-07-26T12:10:32-07:00
[INFO] Final Memory: 777M/5743M


Theming isn't really possible using CSS modules

🐛 Bug Report
After spending hours trying to understand what React Spectrum is built to support theming means on the official docs, I couldn't find the proper way to do any customization to a theme, even a very basic border-radius (I don't want to create a custom component, or to style a specific one using the UNSAFE_ property. We have a design system, and I want to make the components consistent without needing extra config per component).
🤔 Expected Behavior
We should be able to override theme variables or to write a full custom theme overriding the default theme.
😯 Current Behavior
First of all, the Theming docs mentions vaguely that custom themes can be created, but no examples are provided. Trying to create a custom theme object, and passing some of the properties will override all properties. Copying the full theme file doesn't sound like a viable solution.
🔦 Context
I've tried to create a theme object in multiple ways and to pass it to Provider. The code sample below explains the approach and why it doesn't work.
💻 Code Sample
theme.module.css
.theme {
  /* Button overrides */
  --spectrum-button-primary-border-radius: 0.375rem;
}

index.ts
import customTheme from './theme.module.css';
import dark from './spectrum-dark.module.css';
import darkest from './spectrum-darkest.module.css';
import global from './spectrum-global.module.css';
import large from './spectrum-large.module.css';
import light from './spectrum-light.module.css';
import medium from './spectrum-medium.module.css';

const theme = {
  global: global,
  // MERGING DOESN'T WORK
  dark: { ...dark, ...customTheme },
  // WHEN APPLYING CUSTOM THEME FILE, ALL OTHER STYLES ARE IGNORED
  // dark: customTheme,
  darkest: darkest,
  // MERGING DOESN'T WORK
  light: { ...light, ...customTheme },
  medium: medium,
  large: large,
};

// COMPONENTS VARIABLES ARE NOT INCLUDED IN ANY OF THOSE FILES, I.E spectrum-button-primary-border-radius

export default theme;

🌍 Your Environment
Next.js 12.2.25
React 18.2.0
@nrwl/next 14.6.1
What am I missing here? Is it the right way to create a theme to duplicate all files from https://github.com/adobe/react-spectrum/tree/main/packages/%40adobe/spectrum-css-temp/vars? Which other option do we have?
Not being able to change a simple border-radius is frustrating. The theming docs also need to be updated to display some examples or to clarify what theming actually means. I've also based my assumptions on this example from the official storybook: https://github.com/adobe/react-spectrum/blob/main/packages/%40react-spectrum/provider/stories/custom-theme.css, which seems to be misleading as well.

I totally understand your point, @snowystinger , that React-Spectrum does not really support customizing themes currently, but that you can basically rebuild it with React-Aria (and React-CSS). But that approach really does not make any sense. Why should one redo all the great work you put into React-Spectrum just to change the values of a color variable? There must be an easy approach to overwriting or adding additional variables to change the theme.

Absolutely, that is a great point. We're working on a proposal right now to make that easier. See https://github.com/adobe/react-spectrum/discussions/2368#discussioncomment-3887426

Well that proposal would still be unstyled @snowystinger. I think they're asking to reuse spectrum's css but with some customizations rather than rewriting it.

ah, you are correct, i mis-read that. Your proposal will reduce complexity in terms of getting the react-aria correct with the components. From there, it should be easier to style.
Unfortunately we can't easily expose the css variables of React Spectrum as API for customized theming because they are out of our control and have undergone a few major changes already. If and when they become more stable, we could consider revisiting.

Thank you for your reply @snowystinger . This sounds somewhat promising. I have no real knowledge about CSS modules, but wouldn't it be sufficient, if devs could view the css modules with the variable names and values in the docs (autogenerated) and then just add their own css module in the correct order that overwrites these variables? Something along these lines:
import {defaultTheme} from '@adobe/react-spectrum';
import custom-light-theme from '../css/custom-light-theme.css';

<Provider
  theme={{...defaultTheme
    , light: [defaultTheme.light, custom-light-theme] }
>
  <YourApp />
</Provider>

Now, it should be sufficient, that React-Spectrum imports the css-module in the correct order as placed in the array, shouldn't it?

Yeah the main problem is actually stabilizing the variable names themselves. So far they have been an implementation detail, and the names have changed several times. If we wanted to officially support this, we'd need to treat them as public API that followed semver.

Ah, I see. That gives hope that this is only a matter of time. I hope you come up with good future-proof var names and get rid of the cumbersome spectrum prefix :)
I think there is some nice inspiration out there regarding naming like the tokens from the IMB Carbon System or the utility classes from Tailwind CSS.

Maybe if customizing was left to the user by having undefined vars in the css of the elements and all your current values as fallbacks?
You are already kind of doing it, so is something like this possible?
background-color:var(---spectrum-custom-background-color-transparent, var(--spectrum-fieldbutton-quiet-background-color-disabled,var(--spectrum-alias-background-color-transparent)))

Variable names can still be changed on your side, while we would be still be able to customize things by keeping the custom ones more or less static.

I agree that things could be better. I'm not sure we currently have the bandwidth to implement such a system at the moment.
I think there are a lot of questions about what would be supported in terms of variables. Would it only be colors? or would it also be dimensions? What about in cases of shorthand properties? or positioning or psuedo elements or properties we don't use? or places where we use the same value, but someone customizing would want two separate values?
I'm also not so sure that allowing them to be component specific is the best idea. Our color scale is specifically built to meet contrast a11y requirements and all our components work together. That said, it's a big undertaking to make a new color scale if you're a third party and you just want to tweak a couple of things and are aware of the dangers.
All I'm really saying is that this is something that isn't simple. This would be a huge API surface area. It needs time and people to think through, make a proposal, implement, document, and maintain.
What you've outlined is a good starting place. I think starting from the Tailwind angle could also be worthwhile.

Making it all optionally customizable for the user could be interesting. Not easy or fast, but interesting.
Now, if this is not the vision of this implementation, maybe stating it clearly how strict this implementation is in the documentation would be a great time saver.
P.S. Your color palettes won't match corporative branding colors, so doing it at the component level would allow someone to control this without redefining any palette you provide.
P.P.S Going the Tailwind way seems to me like more work, and might not allow users to customize the design system implementation with their own style requirements.

@snowystinger Thank you for your explanation. Your points are absolutely valid. It is definitely the right way to have a clear concept regarding feature set, implementation and maintenance.
On the other hand, I think it is sometimes smarter to start the conceptual work simultaneously with the implementation and improve both incrementally. For example, you could start with a very small API offering only the most important feature for customers, let's say for example adding new color variants. This would offer your users a huge benefit and your team a lot of insights regarding further steps for the implementation and overall concept.
(Just a side note regarding implementation, maybe an npx script that properly modifies or appends to the existing CSS modules according to the package version might be a first foot in the door.)
It might also help in evaluating reasonable css variable names.

I don't think we really want to support customizing Spectrum itself. Spectrum is our design system for internal Adobe applications, and for external developers integrating with Adobe software. In both cases, we want the design to match other Adobe products. Allowing customization would open this up and defeat the purpose of having a design system. It would also make it harder for us to change the design and implementation without breaking things in the future, because we'd have to keep all of the potential customizations in mind.
I think what we can offer instead is a starter kit, with examples of all of the components built with React Aria with custom CSS and JS that you could modify. We could build it with some CSS variables that you could customize globally, or you could just modify the CSS to make more detailed changes. This way, we don't need to worry about breaking things in future updates, and you get full freedom to to whatever you want while starting with something pre-built rather than from scratch. You could technically do this now by forking the repo and changing the CSS, but there's a lot here and I think we can make it easier.

Spectrum is our design system for internal Adobe applications, and for external developers integrating with Adobe software.

If that's the case I really insist that the documentation should be heavily changed. As a first-timer getting to the docs, it gives a clear impression that Spectrum is an open react library that could be used in any application and customized properly. First, the statement "Spectrum is a design system for internal Adobe applications, and for external developers integrating with Adobe software" should be in the main page of the docs, and on the theming section, this needs be removed: "React Spectrum is built to support theming. Colors, sizing, and spacing options can be customized through the use of CSS variables which are defined using the Provider component."
Sorry to insist on this, but I want to avoid people spending hours investigating and doing proofs-of-concept with Spectrum to hit a wall down the road as I did. 🙌🏼

Spectrum is our design system for internal Adobe applications, and for external developers integrating with Adobe software.
If that's the case, then I would be very sad. I just hate the thought to reinvent the wheel and to recreate a design system each time I implement a new frontend. The Adobe Design System is specifically suitable for data visualization / industry apps in my opinion. Many other design systems seem to focus more on B2C apps.  I hope Adobe sees the benefit in offering its Design System as a piece of open software.

We can adjust the wording a bit but I don't think it's completely wrong. The main page says "A React implementation of Spectrum, Adobe’s design system." - I'm not sure where you got the idea that you could totally change the design of it. What we mean by theming is as described on the Spectrum design website – Spectrum itself has multiple themes, both in terms of color schemes (dark/light) and designs for different adobe products (like CC express). Other themes are possible if you want to take a look at the builtin themes and write something similar, but we wouldn't recommend it as that would go against the Spectrum design guidelines. That's where React Aria comes in. I think we can offer something in the middle for more easily building custom design systems.

React Spectrum is built to support theming. Colors, sizing, and spacing options can be customized through the use of CSS variables which are defined using the Provider component.

I got this idea from this statement, inside the theming page:

React Spectrum is built to support theming. Colors, sizing, and spacing options can be customized through the use of CSS variables which are defined using the Provider component.

The way you describe it is far from reflecting that statement. It should be something like this: "Customizing React Spectrum is not possible, unless you create a new theme based on the existing ones and rebuild it, which is not recommended".
The "How themes are defined" section gives me a clear idea that I would just need to override defaultTheme and pass it to Provider, which is very misleading. That section should be called "How to switch to one of the existing themes" and another section called "How to create a custom theme" should be created saying explicitly that this is only possible by extending the code somehow. Sorry to be nit-picky here, bit this is what you would see in any open-source UI library.

I think there's a difference between theming and customization. We're describing how the themes work, not how to make a custom one. "How themes are defined" lists the three themes we provide, describes how they work, and shows how to apply them. It doesn't show any CSS or examples about how to make your own theme. I agree we can clarify that custom themes aren't supported, but I don't think it's misleading to simply describe how the theme system works.

Sorry to be nit-picky here, but this is what you would see in any open-source UI library.

I disagree. There are tons of open source design systems out there that don't support customization. The point of a design system (vs a component library) is enforcing design consistency between products. So at that layer, that is our goal. We have additionally gone above and beyond to provide a lower level API in React Aria that supports full customization beyond what most libraries offer. React Spectrum is our implementation on top of this foundation for our products and anyone else who might want to use it. If you don't want to use our design, then you can make your own design system with this foundation. We're always looking for ways to make this easier, but customizing our design is not the way we'd like to go. We'd rather approach it from the opposite direction.

Yes, the homepage lists three different libraries and describes what they are for. The description of React Spectrum says

A React implementation of Spectrum, Adobe’s design system. Spectrum provides adaptive, accessible, and cohesive experiences for all Adobe applications.

I think this is pretty clear.
The blog post is describing React Aria, which implements reusable "user interactions, accessibility, internationalization, and behavior". It is a part of our overall architecture.
I already said we would clarify the description even more but I think this has now been blown way out of proportion. I understand you're frustrated that you can't customize at the React Spectrum layer, and I'm sorry, but that's not going to change. We are focused on providing tools for building your own design system instead, and will continue to make that easier.

Yeah, good luck

Yeah, you just wasted hours of my time also as Spectrum doesn't support 'theming' as any developer understands the meaning of that.
It's fine you don't support theming, but be honest and clear about it, so developers like me don't have to go down the rabbit hole to figure out we can't change a simple colour.  Yes that might not agree with your design system, but I'm not building an app for Adobe, I'm building something for myself and I want a different colour.
I think your being quite disingenuous about being clear on the purpose of react-spectrum, I'll avoid all things Adobe in future.

Sorry you had a bad experience! FWIW, we offer React Aria Components, which gives you full styling control to build custom components. We also have starter kits for vanilla CSS and Tailwind that you can download and customize.
React Spectrum is specifically for Adobe-themed applications. There are several different Spectrum-defined "themes" discussed in the docs, but I can see how it might be confusing if you are thinking about custom themes (which are not supported). Perhaps we can clarify that page a bit more.


Remove mention of "system back bar"

This subsection was added in preparation for the Tabbed Sets Windows feature, which has since been canceled. The system back bar and tab band don't exist, so shouldn't be called out in our documentation.

@YuliKl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

In review.


Directory structure for html templates?

Where to put the html files? https://gocondor.github.io/docs/response#rendering-html
Dont think *routing.Router supports router.LoadHTMLGlob the way it is done for gin? Similary where to add the html assets files, html partial templates, etc?

@arjunmenon currently the framework supports apis with json response only, html has not been supported yet


Creating a Connector API with another programming language (C#)

Hello,
I am trying to replicate the functionality of /v2.0.1/python/api/DWX_ZeroMQ_Connector_v2_0_1_RC8.py in a C# program
I am not an expert developer so this is going to be challenging for me. If anyone can offer advice that would be appreciated otherwise I will still try and figure it out on my own.
Here is a UML Diagram of the python code.

I don't know python that well but I know that one of its idiosyncrasies is that it's not strongly typed, so the diagram doesn't show data types for the fields, nor method return types.

the next stage is to figure out the appropriate data types and add them into this UML Class Diagram.

From there, it should provide enough of a blueprint to iterate through each of these attributes and methods, re-creating them in C# or another language.

I will share my C# code and try to offer advice to others who are attempting to build a connecter for another language.

The way that zmq.Context and zmq.Poller behave will be similar for other zmq bindings. I need to understand how python multi-threading works to try and do the same in C#

The way that zmq.Context and zmq.Poller behave will be similar for other zmq bindings. I need to understand how python multi-threading works to try and do the same in C#

Hi,
Thank you for your efforts to expand the connector to C#.
I can't offer concrete advice for using ZeroMQ in C#. However, we are currently in the process of writing an alternative to the ZeroMQ connector, which will just use files for communication with MT4 (or MT5). This reduces the third party dependency and makes it much easier to implement solutions in other programming languages. We will publish versions in python, java and C#.

Hi,
Thank you for your efforts to expand the connector to C#.
I can't offer concrete advice for using ZeroMQ in C#. However, we are currently in the process of writing an alternative to the ZeroMQ connector, which will just use files for communication with MT4 (or MT5). This reduces the third party dependency and makes it much easier to implement solutions in other programming languages. We will publish versions in python, java and C#.


Configuration System

Implemented a configuration system for system values the dbatools use.
Currently much information is hardcoded in individual functions, that actually should be configurable.
This PR addresses that:

All configuration options stored in a central directory
All configured values can be discovered, using Get-DbaConfig
Users can add configuration values to their profile and thus override module defaults

Also added a framework to include a framework to add C# code to, in case more of that comes along.
Redesigned the way optional components become optional as well while I was at it - now you don't need to update the .psm1 each time, which was ... not so good.

Thanks so much, @FriedrichWeinmann! can you take a look at the test failures? I'm getting this on almost every test.
Error occurred in test script 'C:\projects\dbatools\Tests\Test-DbaDatabaseOwner.Tests.ps1' 719ms
CommandNotFoundException: The term 'C:\projects\dbatools\internal\configurations' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

on it

Alright, got to the root of the problem with the tests:
They invoked every single file within internal, without making sure those are files first.
Not very successful on folders ...
Btw, these tests desperately need some looking after :(
I'd love to, but only so many hours in a given day. If I have the spare time after finishing my current workload (including that mirror command, which I haven't forgotten in all this), I'll look at things myself, but ... well, pre-freeze priorities ;)

@FriedrichWeinmann we have ppl who are doing it -- i think the only reason the tests are failing is because we're messing with the directory structure, no?

That was the reason this time.
We have a lot of redundancy in there that could use some eliminating. For example, while they are called by appveyor.pester.ps1, they all test content of the same module in the same version.
Still we process and import the module in each test, rather than consolidating it in the primary file before calling invoke-pester.
The issue now was called due to a totally, 110% superfluous line in the source (I killed it completely). When we already have the entire module imported, it serves no purpose to explicitly import some of its files.
This is not a level 1 emergency, no - I'd have jumped right into the action if it were - but it still deserves cleaning up, so we don't multiply code unnecessarily. These are the templates new tests will be based upon, so if we leave this unchecked, we might just run into an issue that may have been easy to fix now but will be a lot of work then.
Sorry about calling it desperately - that was an exaggeration, probably based on my own frustration hunting down this particular issue - that was an overreaction.

This looks super cool! Is it possible to change the namespace? I know it's small but dbatools is all lower case - I rarely mention it / ppl to change cuz no bigs but for our internal stuff, I'd like it properly cased.
From:
SqlCollective.DbaTools
To:
sqlcollaborative.dbatools
Will you be able to write a short and sweet blog post on the background/intention for our developers? No need to be longer than Drew or Stuart's.
Thank you so much! 🚎

I'm especially pumped about that XML file!

Oh, and stop modifying the psd1 or I'll come after you with 🛠 - I can add entries at any time and even before you write the commands, it helps everyone with the branches and I'm happy to do it.

ducksbehindcorner *
Yes, My Lord!

I promise to be good from now on, Master! ;)
Seriously, this habit is soooo hard to lose :(
I'll try to remember

While it hurts my soul and shakes my faith in humanity - neigh, existence itself! - I guess I could change the casing on the namespaces. It'd be about the equivalent to asking a priest to join the next witches' sabbath so he can help officiate over the child sacrifice, but ... ;)
Again, one of those habit things.
No technical reason to lowercase it though, so gimme a sec (or better a few minutes) and the casing shall be done, and done right.

You like Linux, right? Think of it like Linux.. lower case everythang 🐧

The best thing about penguins are their livers. Preferably Well Done ;)

I had puffin in Iceland. Broke my heart but dammmmn was it amazing!


Fix Issue 19164 - malloc may be considered pure when failure results in program exit (no need to reset errno)

The core.memory.pureMalloc wrapper reads errno, calls malloc, then resets errno. This is unnecessary if when the allocation fails the program terminates with assert(false) or onOutOfMemoryError().

https://github.com/dlang/druntime/pull/2276 seems to have stalled so I'll implement @wilzbach's suggestion to create a module std.internal.memory to hold the fail-fast allocation functions.

Thanks.


File type specific icons for Dropzone component

Just wanted to check if the additional complexity is worth it in your opinion, before submitting a PR for it :)
In Shopify admin -> Settings -> Files, shopify will show preview images for image file type, but also other specific icons for other files types. For example, PDFs use the notes icon and JSON files use the code icon from Polaris

https://polaris-icons.shopify.com/
Most use cases of Dropzone will be for uploading images, but we have a use case where other file types will be uploaded also. So would look to add specific icons for the most common file types.
Thoughts?

I think that would be great! Some groups of types that come to mind: text/pdf, archives, code, video, audio. We could add a separate icon for each and keep the existing icon as a fallback.

Awesome, will work on that and submit a PR 👍


anonymize_list return type hint fix

Change Description
The anonymize_list function of the BatchAnonymizerEngine class never returns List[EngineResult].
Changed the return type hint to List[Union[str, object]] and import
Checklist

[x] I have reviewed the contribution guidelines
[ ] I have signed the CLA (if required)
[ ] My code includes unit tests
[ ] All unit tests and lint checks pass locally
[ ] My PR contains documentation updates / additions if required

/azp run

Thanks! merged


Adding Women Safety Numbers State wise

Related Issue or bug

Info about Issue or bug

Fixes: #257 [issue number that will be closed through this PR]
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Checklist:

[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots

Original
Updated

original screenshot
updated screenshot

 |

Have a look on this and let me know if any changes are to be made.

Changes you had requested for. Are they okay now or some change had to be done.

Original
Updated

There is no difference between heading and details that are there so you might remove the bold styling from details or reduce the size of the details for differentiation.

| Updated
:--------------------: |:--------------------:

Changes you had requested for. Are they okay now or some change had to be done.

Thank you @naman153 for your contribution. Looking forward for more such amazing contributions :)

Thanks @swapnilsparsh @sakshikhachane for all the support and help you had provided me. Will look forward to contribute to it further for sure.


Fix a TF Lite issue when loading a saved TF Lite model on platforms with different endianness

In the current TensorFlow Lite mechanism, the saved .tflite model will not have any information indicating the endianness of the serialized model, which might cause some op tensors not being read correctly if loading the model on a machine with different endianness. Here is a related issue.
The issue is also causing two test cases failure for TensorFlow Serving: //tensorflow_serving/servables/tensorflow:saved_model_bundle_factory_test and //tensorflow_serving/servables/tensorflow:tflite_session_test.
A similar issue is resolved for a regular TensorFlow model, as the endianness information is written alongside the model itself, see here. And such endianness info will be read on loading, and byte-swapping will be conducted if the endianness of the model is different from the endianness of the host, see here.
Consequently, I am using a similar approach to saved .tflite models. I make use of the Metadata field in the schema of saved TF Lite Model, saving a string type metadata indicating little or big of the machine endianness where the model is saved.
This piece of metadata will be read when the FlatBufferModel is passed into an InterpreterBuilder, and the byte-swapping will be conducted during ParseTensors. Right now I am only supporting the byte-swap of float type tensors, as they are the most common ones. It is also possible to add support for more data types if needed.
Please also note that this PR will not cause any test cases regression for TensorFlow, and it is also compatible with TF Lite models generated before because if the Metadata field is not found in the saved model, the loader will assume the model is generated with the same host endianness (which is basically what is happening without the changes). And after the changes, even the model.tflite file generated on a little-endian machine will make the TensorFlow Serving test case pass on a big-endian machine (vice versa).
This PR is also including a small fix for aws building target on s390x arch.

Thank you @Sidong-Wei for your contribution!
This is indeed a valid concern and the issue should be carefully resolved for extending TFLite use cases beyonds mobile platform.
There are multiple designs to resolve handling the endian problem, for example,

Adding model metadata in flatbuffer like this one,
Writing always tensor data with the certain endianness, or
Adding a flag for specifying the target endianness during conversion.

I prefer a solution that is the mixture of the 1) + 3) options.
@jdduke Any thoughts on this?

I believe flatbuffers default to little-endian encoding, even on big-endian host machines that create the flatbuffer. See also this documentation. That said, having some safeguards in place to ensure that (when we create the flatbuffer), and handling big-endian parsing/loading on the inference side, seem like reasonable requests.
So, given the gravity of flatbuffers for little-endian encoding, my preference would be for (2), and to fix the loading code to handle the big-endian case. The unfortunate side effect is that this will eliminate the benefits of mmap'ing the model file on big-endian machines. If that's a problem, we can discuss, perhaps with a special build flag to opt in to this path (where you know that both host/device are big-endian, I think we want to avoid the proliferation of big-endian-encoded .tflite models more broadly).

Thanks a lot for the feedback. And yes, I think always serializing the flatbuffer model in Little-Endian makes sense, as you mentioned, the faltbuffer compiler seems to use this method by default. I think the problem here is that for some non-native data types like Tensor, flatbuffer compiler may not be able to handle it correctly, so some extra efforts on both the saving side and loading side will need to be made (i.e. manually do the byte-swap on Big-Endian machine).
My colleague @skribm9, is actually working on such a method as you suggested. I think it should be able to address the endianness issue while keeping the saved model in Little-Endian format.

Closing the PR as the discussion has moved to the new issue: https://github.com/tensorflow/tensorflow/issues/45009, will start new PR once the issue is fixed.


Centers stories using flexbox

Hello there.
Storybook is still centering stories using flexbox in version 5.0.2.
I found this closed issue which explains the issue should have been resolved in 5.0.2, but it is still happening for me:
https://github.com/tuchk4/storybook-readme/issues/132

I'm going to close this one. Looks like I had an issue with local caching - I wiped everything and reinstalled and it does work, apologies!


Release readiness for Optimize 2.0.0

Description

Added README, Getting started and API reference page.
Updated versions of dependent modules.
Overriden friendly name API in OptimizeExtension

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thanks @spoorthipujariadobe. I'll fix any comments here in another pr.


Upgrade to react 16

Allows the usage of react-decoration with react 16

Coverage decreased (-0.06%) to 99.357% when pulling d90958fb46f5a14da253ccfbcc80ea30a1566278 on react16 into 7a136c0226c7f699cf94a5b835b56d56abd7b4a1 on master.

Coverage decreased (-0.06%) to 99.357% when pulling cfa724a435bfc462f6f065e6b69e868e9243ba55 on react16 into 7a136c0226c7f699cf94a5b835b56d56abd7b4a1 on master.

Coverage decreased (-0.06%) to 99.357% when pulling cfa724a435bfc462f6f065e6b69e868e9243ba55 on react16 into 7a136c0226c7f699cf94a5b835b56d56abd7b4a1 on master.

Coverage decreased (-0.06%) to 99.357% when pulling cfa724a435bfc462f6f065e6b69e868e9243ba55 on react16 into 7a136c0226c7f699cf94a5b835b56d56abd7b4a1 on master.


GEOPY-1116: update Pillow as recommended by GitHub advisory

GEOPY-1116 - update Pillow as recommended by GitHub advisory

depends on https://github.com/MiraGeoscience/geoh5py/pull/446


Testing Trello migration

This is a test to see if I've found a more automated way to create issues in GitHub from cards in Trello.

ooooh, it worked!


Fully qualified domain name

This PR renames CANONICAL_HOSTNAME to FQDN.

Current coverage is 48.24%

Merging #393 into master will not affect coverage as of ac473ce

@@            master    #393   diff @@
======================================
  Files           85      85
  Stmts         3393    3393
  Branches       321     321
  Methods          0       0
======================================
  Hit           1637    1637
  Partial         29      29
  Missed        1727    1727

Review entire Coverage Diff as of ac473ce

Powered by Codecov. Updated on successful CI builds.


Added PR link to Milestone 3 Search Widget

Project
Sunbird ED (Search Widget)
Changes
Added PR link to the milestone 3
Notes
As stated, I have raised the PR of work till now and added that PR link to milestone 3.

Hey Pranshu , the build is failing please test check it on the local environment before raising a PR

Merged with #287


Can not turn screen off in android Q with 1.10 scrcpy

My device is Oneplus 7 pro with OxygenOS Android Q openbeta 2. I found ctrl + o cannot turnoff the screen of my device, and program carshed with following:

INFO: Initial texture: 1440x3120
[server] ERROR: Exception on thread Thread[Thread-1,5,main]
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at >com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplayPowerMode(SurfaceControl.java:96)
at com.genymobile.scrcpy.Device.setScreenPowerMode(Device.java:165)
at com.genymobile.scrcpy.Controller.handleEvent(Controller.java:113)
at com.genymobile.scrcpy.Controller.control(Controller.java:73)
at com.genymobile.scrcpy.Server$1.run(Server.java:45)
at java.lang.Thread.run(Thread.java:919)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at >com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplayPowerMode(SurfaceControl.java:94)
... 5 more
Caused by: java.lang.IllegalArgumentException: displayToken must not be null
at android.view.SurfaceControl.setDisplayPowerMode(SurfaceControl.java:1523)
... 7 more

scrcpy --version shows:

scrcpy 1.10
dependencies:o

SDL 2.0.10
libavcodec 58.35.100
libavformat 58.20.100
libavutil 56.22.100

So I noticed you had fixed this issues, but it seems don't work to me...

I'm having this issue since latest Android 10 update --> Android 10.0.0 (Release 3) - QP1A.190711.020.C3
When I turn on scrcpy, it shows this:
INFO: Initial texture: 1080x2248
[server] ERROR: Exception on thread Thread[Thread-1,5,main]
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplayPowerMode(SurfaceControl.java:96)
at com.genymobile.scrcpy.Device.setScreenPowerMode(Device.java:165)
at com.genymobile.scrcpy.Controller.handleEvent(Controller.java:113)
at com.genymobile.scrcpy.Controller.control(Controller.java:73)
at com.genymobile.scrcpy.Server$1.run(Server.java:45)
at java.lang.Thread.run(Thread.java:919)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplayPowerMode(SurfaceControl.java:94)
... 5 more
Caused by: java.lang.IllegalArgumentException: displayToken must not be null
at android.view.SurfaceControl.setDisplayPowerMode(SurfaceControl.java:1520)
... 7 more
And..., not only the screen doesn't turn off, but I cannot use the mobile from the computer. It just reflects the mobile screen, but slows the mobile down.

And..., not only the screen doesn't turn off, but I cannot use the mobile from the computer.

(The exception you get crashes the controller thread, so it is not surprising.)

My device just received the Android 10 upgrade tonight, so I fixed the issue on dev branch: c33a147fd0e9fbd3a5add6f0190eea909d74c26d

Excuse me, do you have a compiled version of windows that has fixed this problem？

My device just received the Android 10 upgrade tonight, so I fixed the issue on dev branch: c33a147

Excuse me, can you add a compiled version of windows that has fixed this problem?

Is there a compiled Windows version of this with this issue fixed?
I'm still experiencing this on v1.13.

Could you paste the error you get in the console  please?

Could you paste the error you get in the console please?

I did, here:
https://github.com/Genymobile/scrcpy/issues/1409


FIX: azure

This PR fixes https://github.com/mne-tools/mne-python/issues/8873

@drammock, @hoechenberger all is green here. It's ready for merge

Perfect, thanks!


Add debugging for event-test flakes.

Merged, thanks @showell!  And I'll shortly merge a fix for the coverage issue, because I forgot to think about that possibility before coming here to close this :/


bump version of api-common to 1.0.1

This brings in the change in
https://github.com/googleapis/api-common-java/pull/28

LGTM after updating the commit description

Changes Unknown when pulling 6d55893fd6519b50af4a80f1a5525a20d139a370 on pongad:async-transform into ** on GoogleCloudPlatform:master**.


Failed to synchronise stop event.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.4
Python version: 3.6.3
Bazel version (if compiling from source): 0.9.0
GCC/Compiler version (if compiling from source):  5.4.0
CUDA/cuDNN version: 9.1/7.0.5
GPU model and memory: GT 750M 2GB
Exact command to reproduce: Run the custom program.

Describe the problem
Trying to train a simple 5 layer model with 3.7million parameters that are trainable which would occupy around 1.5GB VRAM, the training fails instantly at the very first epoch. People who had similar error claimed that it was fixed in cuDNN 7.0.5 from this thread #14363 . But this update isn't fixing the crash. I've posted the error log below:
Source code / logs
Total params: 3,714,788
Trainable params: 3,714,788
Non-trainable params: 0
_________________________________________________________________
2018-01-06 21:58:27.567991: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:892] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2018-01-06 21:58:27.568491: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1030] Found device 0 with properties:
name: GeForce GT 750M major: 3 minor: 0 memoryClockRate(GHz): 0.967
pciBusID: 0000:01:00.0
totalMemory: 1.95GiB freeMemory: 1.60GiB
2018-01-06 21:58:27.568526: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1120] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GT 750M, pci bus id: 0000:01:00.0, compute capability: 3.0)
Train on 646 samples, validate on 162 samples
Epoch 1/20
2018-01-06 21:58:30.447458: E tensorflow/stream_executor/cuda/cuda_driver.cc:1080] failed to synchronize the stop event: CUDA_ERROR_ILLEGAL_INSTRUCTION
2018-01-06 21:58:30.447529: E tensorflow/stream_executor/cuda/cuda_timer.cc:54] Internal: error destroying CUDA event in context 0x5650223aede0: CUDA_ERROR_ILLEGAL_INSTRUCTION
2018-01-06 21:58:30.447572: E tensorflow/stream_executor/cuda/cuda_timer.cc:59] Internal: error destroying CUDA event in context 0x5650223aede0: CUDA_ERROR_ILLEGAL_INSTRUCTION
2018-01-06 21:58:30.447629: F tensorflow/stream_executor/cuda/cuda_dnn.cc:2964] failed to set stream for cudnn handle: CUDNN_STATUS_MAPPING_ERROR
Aborted (core dumped)

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Sprockets::Manifest.compile should return paths

Sprockets::Manifest.compile changed to return paths.
https://github.com/sstephenson/sprockets/commit/0e7558a6fae1488a9afe4f541271f1c724909f78#diff-210127843b227645ec53849779cf3f34
so, I simply pipe returns from origin compile.

Thanks for this, I just pushed version 1.0.5 to rubygems - please let me know if it works for you!
Alex

Thank you alex.
It works for me.
rails (4.2.1)
sprockets (2.12.4)
sprockets-rails (2.3.2)


Add Mindustry and Mindustry-server

This was previously proposed in [Request] Mindustry
Please let me know if there are any problems. Thanks.

Thanks!


Make Window#cursor= behavior match Vim

Out of bounds cursor positions are acceptable
Return cursor array

Addresses https://github.com/alexgenco/neovim-ruby/issues/19

Incorrect handling of 0 values as per :help cursor


Bump up version dateutil version

I don't see a problem upgrading the package, but why do we need it?

Sorry should have written the reason yesterday directly.
Basically we want to upgrade our docker images to ubuntu 22.04 and with it a bunch of dependencies.
https://github.com/logivations/deep_cv/pull/4235
As a consequence we require python_dateutils==2.8.2 which clashes with label-studios dependency.
Instead of bumping up fully we could also do something like >=2.8.1

I don't see a problem upgrading the package, but why do we need it?

Sorry should have written the reason yesterday directly. Basically we want to upgrade our docker images to ubuntu 22.04 and with it a bunch of dependencies. logivations/deep_cv#4235 As a consequence we require python_dateutils==2.8.2 which clashes with label-studios dependency. Instead of bumping up fully we could also do something like >=2.8.1

No worries:) sure, looks good to me

Ok, then I'll merge this


AppLovinMAX.AdView doesn't support the App support for INTERSTITIAL

MAX Module Version
5.5.2
React Native Version
"0.63.2
Device/Platform Info
Iphone 14
Current Behavior
I am using AppLovinMAX.AdView for INTERSTITIAL but showing error Warning: Failed prop type: The prop adFormat is marked as required in AdView, but its value is undefined.
Please help me to solve this issue
Expected Behavior
No response
How to Reproduce
<AppLovinMAX.AdView
adUnitId={INTERSTITIAL_AD_UNIT_ID}
adFormat={AppLovinMAX.AdFormat.INTERSTITIAL}
style={{width:'100%',height:'100%'}}/>
Additional Info
<AppLovinMAX.AdView
adUnitId={INTERSTITIAL_AD_UNIT_ID}
adFormat={AppLovinMAX.AdFormat.INTERSTITIAL}
style={{width:'100%',height:'100%'}}/>

We do not have support for React Native components for inters. Please refer to our docs here: https://dash.applovin.com/documentation/mediation/react-native/ad-formats/interstitials


does it support redux sagas?

i have just read about how good is using redux saga. Any good implementation with react-native-router-flux ? anyone can help making some example code for connecting redux sagas to react-native-router-flux pls?

some ideas


HDFS-16303. Improve handling of datanode lost while decommissioning

Description of PR
Fixes a bug in Hadoop HDFS where if more than "dfs.namenode.decommission.max.concurrent.tracked.nodes" datanodes are lost while in state decommissioning, then all forward progress towards decommissioning any datanodes (including healthy datanodes) is blocked
JIRA: https://issues.apache.org/jira/browse/HDFS-16303
How was this patch tested?
Unit Testing
Added new unit tests:

TestDecommission.testRequeueUnhealthyDecommissioningNodes
DatanodeAdminMonitorBase.testPendingNodesQueueOrdering
DatanodeAdminMonitorBase.testPendingNodesQueueReverseOrdering

All "TestDecommission" & "DatanodeAdminMonitorBase" tests pass when run locally
Note that without the "DatanodeAdminManager" changes the new test "testRequeueUnhealthyDecommissioningNodes" fails because it times out waiting for the healthy nodes to be decommissioned
> mvn -Dtest=TestDecommission#testRequeueUnhealthyDecommissioningNodes test
...
[ERROR] Errors:
[ERROR]   TestDecommission.testRequeueUnhealthyDecommissioningNodes:1772 » Timeout Timed...

Manual Testing

create Hadoop cluster with:

30 datanodes initially
custom Namenode JAR containing this change
hdfs-site configuration "dfs.namenode.decommission.max.concurrent.tracked.node = 10"

> cat /etc/hadoop/conf/hdfs-site.xml | grep -A 1 'tracked'
    <name>dfs.namenode.decommission.max.concurrent.tracked.nodes</name>
    <value>10</value>

reproduce the bug: https://issues.apache.org/jira/browse/HDFS-16303

start decommissioning over 20 datanodes
terminate 20 datanodes while they are in state decommissioning
observe the Namenode logs to validate that there are 20 unhealthy datanodes stuck "in Decommission In Progress"

2021-11-15 17:57:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 10 nodes are currently queued waiting to be decommissioned.
2021-11-15 17:57:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 10 nodes which are dead while in Decommission In Progress.

2021-11-15 17:58:14,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 10 nodes are currently queued waiting to be decommissioned.
2021-11-15 17:58:14,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 10 nodes which are dead while in Decommission In Progress.

2021-11-15 17:58:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 10 nodes are currently queued waiting to be decommissioned.
2021-11-15 17:58:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 10 nodes which are dead while in Decommission In Progress.

2021-11-15 17:59:14,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 10 nodes are currently queued waiting to be decommissioned.
2021-11-15 17:59:14,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 10 nodes which are dead while in Decommission In Progress.

scale-up to 25 healthy datanodes & then decommission 22 of those datanodes (all but 3)

observe the Namenode logs to validate those 22 healthy datanodes are decommissioned (i.e. HDFS-16303 is solved)

2021-11-15 17:59:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 10 nodes are currently queued waiting to be decommissioned.
2021-11-15 17:59:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 10 nodes which are dead while in Decommission In Progress.

2021-11-15 18:00:14,487 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 42 nodes decommissioning but only 10 nodes will be tracked at a time. 32 nodes are currently queued waiting to be decommissioned.
2021-11-15 18:00:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 42 nodes decommissioning but only 10 nodes will be tracked at a time. 32 nodes are currently queued waiting to be decommissioned.
2021-11-15 18:01:14,486 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 32 nodes decommissioning but only 10 nodes will be tracked at a time. 32 nodes are currently queued waiting to be decommissioned.
2021-11-15 18:01:44,486 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 32 nodes decommissioning but only 10 nodes will be tracked at a time. 22 nodes are currently queued waiting to be decommissioned.
2021-11-15 18:02:14,486 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 22 nodes decommissioning but only 10 nodes will be tracked at a time. 22 nodes are currently queued waiting to be decommissioned.

2021-11-15 18:02:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 12 nodes are currently queued waiting to be decommissioned.
2021-11-15 18:02:44,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 8 nodes which are dead while in Decommission In Progress.

2021-11-15 18:03:14,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): There are 20 nodes decommissioning but only 10 nodes will be tracked at a time. 10 nodes are currently queued waiting to be decommissioned.
2021-11-15 18:03:14,485 WARN org.apache.hadoop.hdfs.server.blockmanagement.DatanodeAdminManager (DatanodeAdminMonitor-0): dfs.namenode.decommission.max.concurrent.tracked.nodes limit has been reached, re-queueing 10 nodes which are dead while in Decommission In Progress.

For code changes:

[yes] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[no] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[no] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 24s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
37m 29s

trunk passed

+1 :green_heart:
compile
1m 46s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 35s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m 10s

trunk passed

+1 :green_heart:
mvnsite
1m 43s

trunk passed

+1 :green_heart:
javadoc
1m 10s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 39s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 54s

trunk passed

+1 :green_heart:
shadedclient
27m  6s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 34s

the patch passed

+1 :green_heart:
compile
1m 40s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 40s

the patch passed

+1 :green_heart:
compile
1m 24s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 57s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 5 new + 45 unchanged - 1 fixed = 50 total (was 46)

+1 :green_heart:
mvnsite
1m 32s

the patch passed

+1 :green_heart:
javadoc
1m  1s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 33s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 54s

the patch passed

+1 :green_heart:
shadedclient
26m 56s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
395m 51s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 51s

The patch does not generate ASF License warnings.

513m 13s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDecommissionWithBackoffMonitor

hadoop.hdfs.TestHDFSFileSystemContract

hadoop.hdfs.web.TestWebHdfsFileSystemContract

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3667/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3667

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux df4ebb1bd981 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 418468c9f91f4cf60057afe2bec9d125c92de1bc

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3667/1/testReport/

Max. process+thread count
1990 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3667/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Conv1D with dilation and "causal" padding isn't reducing the size of the sequence

If you run
x = Input(shape=(seq_length, dim))
y = Conv1D(num_filts, 2, dilation_rate=8, padding="causal")(x)
print(y.shape)

Then the shape printed out will be (?, seq_length, dim), which means the sequence length wasn't changed at all. But isn't this incorrect? Because the dilation makes the effective kernel width of the convolution 9, shouldn't the sequence length of the output be decremented by 8 because the causal kernel needs 9 values to perform its dot product and so doesn't output on the first 8 samples in the sequence?
To clarify, I'm running with an updated tensorflow backend.

Thank you for the detailed issue. I'll look into it.

any news on this ?

I was looking into this today by chance and comparing it with the WaveNet implementation from:
https://github.com/munich-ai-labs/keras2-wavenet/blob/master/wavenet_utils.py#L29
I have the impression that the Munich AI labs developers had the same issue and they overridden compute_output_shape. Maybe @imdatsolak has more details. HTH

Their implementation is the same as the build in causal keras implementation judging from the code. It seems they were just not aware that causal already existed in keras.

I think causal should not be a value of padding, but a separate option that can be used with both padding='valid' and padding='same' (and padding='full' I guess, I don't know this option).
What keras does now with padding='causal' is causal convolution with padding='same' and what @chausies is asking for is causal convolution with padding='valid'.
I propose adding a new causal option, and making padding='causal' a deprecated equivalent to causal=True, padding='same'. If there is no objection to this, I'll try to implement it.

Can you give a minimal example of Conv1D(causal=True, padding='valid') in the way you think about it? What would be the difference with Conv1D(causal=False, padding='valid')? Can you give an example with NumPy arrays so that it's explicit?

hello,
I am trying to understand the temporal relation with 'causal' padding ...
My goal is to implement in 2D ... for Conv2D assuming the x-axis is the "time steps" and the y-axis are several variables...
for example,assuming K.set_image_dim_ordering("th"),  the input shape of CNN2D is (batch,channels, x, y)
and we have (none, 1 , 128,9) means that we have 128 time steps and 9 variables in a multivariate time series problem.
How hard it would be to create or include (with a new extended conv2D) the 'causal' padding in conv2D ?
we could also choose if the "time dimension" is vertical in x or horizontal in y...


Update .ko.yaml

Use debian12 base image
Open questions?

[ ] do we need libssl? if not we should use base-nossl-debian12:debug-nonroot
[ ] what's all this redirecting piping stuff going on? is that comment still relevant?

c: @jku

I don't believe libssl is needed, as golang implements its own crypto and we don't use boringssl.

Let's switch to static since we shouldn't need anything else.


🚀 Feature: ElasticSearch loading of SSL self sign Certs into app-config.yaml

🔖 Feature description
Allow ElasticSearch loading of SSL self sign Certs into app-config.yaml via an option like key and cert
🎤 Context
The communication to the ES nodes is done via https connection.
Discord Support Question here
✌ Possible Implementation
allow tls loading of the self sign certs via the app-config.yaml file
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

I think that you might need to add these when running Node.
From memory you can use the NODE_EXTRA_CA_CERTS environment variable to reference a path with additional trust chains.
https://nodejs.org/api/cli.html#node_extra_ca_certsfile

@benjdlambert Thanks will try that one. If it works will close the Feature.

@benjdlambert Still same error:
"level":"error","message":"unable to verify the first certificate"
Even that I set:
 NODE_EXTRA_CA_CERTS: /usr/local/share/ca-certificates/tls.crt
And the tls.crt is there

@benjdlambert After setting NODE_EXTRA_CA_CERTS=ca.crt the https connection with the self sign certs is working correctly.
Reference here: stackoverflow


Basic test harness testing. [phab:D2318]

Created by danielmoy-google at 2018-05-18 18:00:12:
Comment out broken bit of test for now.
Will fix that in follow-up change, but would rather focus this review on
just naming, refactor, and basic test bits.

danielmoy-google closed via commit 54d11ff3815978f2e7bfedda2ace6f0ac4bdf848 at 2018-05-18 23:38:04


feat: enable proxy support in the cli

closes: https://github.com/asyncapi/cli/issues/862
Related: https://github.com/asyncapi/cli/issues/1508

As discussed with @Souvikns planning to create a global flags that is proxyHost and proxyPort that can easily help to integrate proxy supports with various commands of the CLI.
Asyncapi generate
Asyncapi validate
Asyncapi convert
Asyncapi optimise


Motivation is low

I wanna do nothing.

how come?

➤ Satoru "Con" Takasimizu commented:
not so much


[shared_preferences] Enable Safe Reuse of Prefix Settings and Instance Checks

Use case
As per the current implementation, the shared_preferences plugin allows setting a custom prefix using setPrefix before any instances are instantiated. However, if setPrefix is called after getInstance, it results in a failure, even if the new prefix matches the previously set one. This poses challenges in complex applications where multiple independent packages might attempt to set or check the prefix independently, leading to potential conflicts and runtime exceptions.
Proposal

Introduce a hasInstance() method: This method would allow developers to check if an instance of SharedPreferences has already been created, which helps in deciding whether it’s safe to call setPrefix.
Modify setPrefix() to allow idempotent operations: If setPrefix is called with a prefix that matches the already set prefix, the method should not fail. This adjustment would make the prefix setting idempotent and safer in environments where multiple checks might occur.

@tarrinneal Can you add this issue to the list of things fixed by your PR introducing the new API?

I'm pleased to hear about the new SharedPreferences API, which implements improvements for working with isolates. I'm looking forward to its release.


Added esp_https_ota_get_image_size() to retrieve total size of OTA update (IDFGH-5096)

I use esp_https_ota_get_image_len_read() to retrieve the succeeded progress of the update and now I can use the new method esp_https_ota_get_image_size() get the total size and create some sort of progress indication.
When the OTA update uses chunked encoding I think there is no way of telling the total size so I return -1 instead.

Thanks for your contribution.


Keyboard hanging

Right after installing the newest version of Karabiner-Elements, keyboard started to behave crazy. Huge delays between keypresses, missing keys, etc.. It's the same even without any modifier. Didn't happen in earlier version. Quitting karabiner-elements bring keyboard back to normal. I'm using Sierra 10.12.2.

It was an incompatibility with bluetooth. I downgrade to 0.90.69 and it's working fine. Version 0.90.83 does work when the bluetooth keyboard is not connected, but started huge delays in each keypress when the bluetooth keyboard is reconnected.


Is it possible to get verbose scan output to shell?

I'm not too sure if this has been asked before - it probably has been. But I=I was wondering if there is a way to output verbose information onto shell while the scanner is running without using --log flag.

No, only the --log is available for verbose output of the CLI (to a file)


Triggerings Liste leer obwohl RigidBody in einem ist

Hier sieht man das der agentRB 2 collisions hat.

Hier sieht man das einer der beiden isTrigger auf true ist

Aber trotzdem ist die triggerings Liste leer bei dem AgentRB

Please post links to your code and to the application. Maybe Marko wants to look into this

Code: https://github.com/Jonathan-Schnee/RougeDungeon/tree/main/RougeDungeon
Application: https://jonathan-schnee.github.io/RougeDungeon/RougeDungeon/index.html

Hello, @Jonathan-Schnee
first off, sorry i did not see this sooner, github did not show me a notification until today.
You found a way around it? Your application seems to work the way you want it.
But on the other hand:
I see multiple problems while browsing through your code.
You do not have a Event Handling for Triggers, so there is no callback when you enter a trigger.
TL;DR;
For reference look at Physic Events Tutorial
HELPFUL LONG ANSWER
I did not look through all your code, but you are missing the basic structure of,

Have a Rigidbody that is an actual physics body (so not a trigger, your player for example)
A Event Caller on either the trigger or the physics body
A Event Handler that is registering the triggering and does something in your case it seems hack the tree

Currently it seems you do work with triggers in a unconventional way, by going through the triggerings and processing their values to achieve the "chopping".
The proper way to implement this is.
With the said 3 steps and work with callbacks.
E.g. every tree has a trigger when the player walks in the tree is registering "Player walked in" through a trigger callback and set's itself as the chopping/action target a variable on the player, when leaving the trigger of the tree, reset the variable to null.
On the player or HUD in your case, when using the function "USE" you just check your current action target for it's type and if you have the right item, if thats the case you call the "action" on your tree. The tree then knows it's own action, which can be adding wood/points or whatever.
Doing it this way does give you the ability to expand on your game easily, you can add new objects and just always call the "action" of the current triggered object, wether it's a tree, stone, or an iron ore in the future. While your USE function stays pretty much the same, but the triggered object then does different things in their "action" function.
Best practice in game programming is to have very generic functions on objects than can be called if from different places in the code. But the object itself knows what to do with it. E.g. you have a base object weapon that implements do shoot, and the player just calls shoot on a mouseclick, but then you have a pistol vs a sniper which do different dmg and maybe other things in their "shoot", they player should not check what weapon they currently use, when they switch they just call another "shoot" on the mouseclick.
You get where i'm getting at? Tree/Stone -> Trigger with Triggering Callback on EVENT_PHYSICS.TRIGGER_ENTER/EXIT, telling the player they are the "action" object now/or not, and the player just calling on their "action" object in case of a HUD Click. (no for looping through stuff, which also is bad for performance)
With your implementation you also run into trouble because the "triggerings" of the rigidbody is only a helper to notice a trigger leaving, the actual trigger ENTER/EXIT is just a one frame EVENT happening. Like a collision.


device.launchApp with permission doesn't work in iOS 16.4

What happened?
device.launchApp with permission doesn't work, it still has pop up after app launch and test stuck until timeout.
My applesimutils version is 0.9.10.
Below is the message when test stuck:
detox[32742] i The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
If I tap allow button manual. The test run well and success completed. Please help.
What was the expected behaviour?
launch app with no permission dialogue. the test start run.
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[ ] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
describe('Employee', () => {
beforeAll(async () => {
device.launchApp({ permissions: { notifications: 'YES' } });
});
// beforeEach(async () => {
//   await device.reloadReactNative();
// });
it('should display welcome message', async () => {
await waitFor(element(by.id('forgetPassword')))
.toHaveText('忘記密碼')
.withTimeout(2000);
});
});
In what environment did this happen?
Detox version: 20.11.1
React Native version: 0.72.4
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version:
Device model: iPhone 14 simulator
iOS version: 16.4
macOS version: sonoma 14.1.1（23B81）
Xcode version: 15.2.0
Test-runner (select one): jest / other
Detox logs
Detox logs
detox[32742] i The app is busy with the following tasks:
• Run loop "Main Run Loop" is awake.
• There are 1 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".

Device logs
Device logs
paste your device.log here!

More data, please!
No response

beforeAll(async () => {
await device.launchApp({
permissions: {notifications: 'YES'}
})
});

@frankA10019 you're missing the await (thanks @Daha62 for the catch). Did this solve your problem?

@asafkorem ,
I am using the below code
beforeAll(async () => {   await device.launchApp({ permissions: { notifications: 'YES' } }); });
However, I faced an issue that my Simulator locked automatically as I ran a test. And it's timeout without running test suite.
https://github.com/user-attachments/assets/7b01b9a3-902a-4b3b-aa53-601a6074ae98


Update throttling-limits.md

Updating Base Resource Unit Cost for directoryObjects/getByIds and getObjectsById from 3 to 5.
Also, a note stating: "Using $select for directoryObjects/getByIds and getObjectsById decreases cost by 2"
Instructions: Add any supporting information, such as a description of the PR changes, here.

[!NOTE]
The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.

do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
Add the ready for content review label to start a review. Your PR won't be reviewed until you add this label.
If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

@rpakala-ms , this PR is in a draft state; would you like us to publish it or is there a reason to wait?

@rpakala-ms , this PR is in a draft state; would you like us to publish it or is there a reason to wait?

@Lauragra - pushed another commit for minor fix, should be good to publish, thankyou!

@Lauragra could you please publish the change to main, please let me know if there are any questions.
Thanks in advance!


Error:  attribute r: A negative value is not valid.

I'm trying to animate two circles using their attributes "ry" to make a blink of an eye effect. all works for me but when I'm opening console I've got error:
Error:  attribute ry: A negative value is not valid. ("-3.3084371372080135")
The values I'm using in range [21, 0, 21]. What makes this error happen and how to fix it?
But when I'm using numbers in range [21, 5, 21] all works without any issues.

Looks like you're using an elastic easing, so animating to 0 means going negative at some point to create the bounce effect.

I'm using 'linear' easing.

Hard to help you without a live example.
Can you share a CodePen or JSfiddle ?

@juliangarnier
https://codepen.io/riccardo051/pen/bKXjpg
Unexpected value 46.0533334776393  parsing r attribute.

@juliangarnier Hi, I have the same issue. It happens here when I try to animate r to 0, e.g. r: [2, 0] with any easing. It seems that you need to add check for p === 'r' if the value is positive or 0. And if it's negative - set v = 0

I've created PR for it #https://github.com/juliangarnier/anime/pull/444


Removed unused imported  Managers

There are 3 Managers that are imported but they are absolutely not used anywhere.
From line:20 to line:22

thanks for pointing out, i'll make this issue resolved on v3.2


cilium: optimize bpf to use jiffies for ct maps

See commit msgs, gives ~ +1.1Mpps on my test machine under xdp benchmark.

test-me-please

test-me-please

test-me-please

Coverage decreased (-0.002%) to 37.872% when pulling 68d24ddc4a6ad5c340d864f4e1906476172cffbd on pr/ktime_ns into 78739a12e64286d6f41941ec629935812436f0b8 on master.

test-me-please

test-me-please

test-me-please

test-me-please

test-with-kernel

test-with-kernel


[Question] how to replace ellekit dylibs?

Hello, I try to build ellekit with safe mode disabled.
Now I have the dylibs but how do I place them on my ios 16.7 iphone 8 jb rootless with palera1n?
Is it just a matter of replacing them in the FS?
I installed ellekit with zebra
Thank you!!

Replace /usr/lib/MobileSafety.dylib with /usr/lib/ellekit.dylib

awesome, will try that tonight. thank you for the fast response!

hm, there is no /usr/lib/MobileSafety.dylib on my phone :/
I only have /private/preboot/xxx/jb-DSvxcZJt/procursus/usr/lib/ellekit/MobileSafety.dylib

Yeah that’s what I meant

seems to work fine so far, thank you!!


Fix PHPStan notice in latest develop

BaseConnection is already implementing ConnectionInterface and the $db used is an instanceof BaseConnection
Checklist:

[x] Securely signed commits

All green 🎉


Metrics shown only for most recently run case

If I run multiple cases / samples with the same fc_date and fc_name, the resulting upload directory contains all of my variant call VCFs, appropriately named (which is good), but the other QC and log files are overwritten by the most recently run case:
bcbio-nextgen.log
data_versions.csv
metadata.csv
multiqc
programs.txt
project-summary.yaml

Therefore I am unable to view multiqc results, for example, except for the most recent case. Is this desired behavior? Am I supposed to be giving each case a unique "fc_name" to avoid this? thanks.

Sorry about the confusing results here for your runs. This is the intended behavior since fc_date and fc_name are meant to uniquely categorize a single analysis run. From bcbio's perspective a run with these identical to a previous run is replacing the old analysis. You'd want to provide unique names for unique analyses to avoid this. Hope this helps.

Thanks, I'll start using unique names from now on. In this case, do you have a recommendation for running multiqc on the completed runs? I'm mostly interested in alignment and coverage reports.


Recent items can't walk successively older recent items

There probably needs to be an extra optional URL argument "before=".  The query returns recent items, starting at the next one older than  (and you can have exclude still apply, etc.).  This lets a client walk back in time lazily, as needed to support a given user's actions.

"before" would be a timestamp or an item id?

Ah, you have put your finger right on it.  IF each item is guaranteed to have a unique timestamp, timestamp is OK.  I don't know how your backend is put together, thus I was specifying ID, so you can calculate your search order in any fashion, and just continue yielding results past the point of that item.  So if you have unique timestamp, then a timestamp works OK.  Depending on how you got that timestamp, it's possible to have more than one item (submitted in a tight window) with the same value.
(BTW, depending on your perspective, you could justifiably call it "after")

Fixed with 84c8a32ff3fbdc78edd353e0b64ba6fe21471584


TypeError: Unknown color 'Red'

Issue description
After upgrade to the latest version 2022.7.24, run pipenv --dev -v occurs TypeError: Unknown color 'Red' error.

No error occurs when not providing -v flag.
No error occurs after downgrading to previous version 2022.7.4.

Steps to replicate
My Pipfile
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]

[dev-packages]
jupyterlab = "*"

[requires]

Command
$ pipenv install --dev -v

...
Traceback (most recent call last):
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/resolver.py", line 854, in <module>
    main()
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/resolver.py", line 840, in main
    _main(
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/resolver.py", line 820, in _main
    resolve_packages(
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/resolver.py", line 769, in resolve_packages
    results, resolver = resolve(
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/resolver.py", line 749, in resolve
    return resolve_deps(
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/utils/resolver.py", line 1080, in resolve_deps
    results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/utils/resolver.py", line 875, in actually_resolve_deps
    hashes = resolver.resolve_hashes()
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/utils/resolver.py", line 782, in resolve_hashes
    self.hashes[ireq] = self.collect_hashes(ireq)
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/utils/resolver.py", line 762, in collect_hashes
    hashes = self._get_hashes_from_pypi(ireq)
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/utils/resolver.py", line 740, in _get_hashes_from_pypi
    click.style("Warning", bold=True, fg="Red"), ireq.name
  File "/Users/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pipenv/vendor/click/termui.py", line 586, in style
    raise TypeError(f"Unknown color {fg!r}") from None
TypeError: Unknown color 'Red'
✘ Locking Failed!

$ pipenv --support
Pipenv version: '2022.7.24'
Pipenv location: '/usr/local/lib/python3.10/site-packages/pipenv'
Python location: '/usr/local/bin/python3'
Python installations found:

3.10.5: /usr/local/bin/python
3.10.5: /usr/local/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.10.5',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '5.4.0-122-generic',
 'platform_system': 'Linux',
 'platform_version': '#138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022',
 'python_full_version': '3.10.5',
 'python_version': '3.10',
 'sys_platform': 'linux'}

System environment variables:

HOSTNAME
PYTHON_VERSION
PWD
PYTHON_SETUPTOOLS_VERSION
HOME
LANG
GPG_KEY
TERM
SHLVL
PYTHON_PIP_VERSION
PYTHON_GET_PIP_SHA256
PYTHON_GET_PIP_URL
PATH
_
PIP_SHIMS_BASE_MODULE
PIP_DISABLE_PIP_VERSION_CHECK
PIP_PYTHON_PATH
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG: C.UTF-8
PWD: /

Contents of Pipfile ('/Pipfile'):
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]

[dev-packages]
jupyterlab = "*"

[requires]

Thanks for reporting this .. will be fixed in the next release.


Missing "how to apply to your project" section in readme

Github has "community guidelines" in place and the documentation on how to apply this brilliant CoC to a project is missing so it does not show as "missing" in insights/community.

I know it has been a while since you logged this issue. I apologize for the delay, but I've resolved the issue.  ;-)


Remove deprecated check from typenetwork profile

Description
Relates to issue #4519. We deprecated the panose_proportion check - well, we removed it; we should probably have a formal deprecation protocol - but did not remove it from the typenetwork profile.
This is a quick fix, I'll follow up with a PR which makes sure that all of our profiles go through the install_run check.
Checklist

[ ] update CHANGELOG.md
[ ] wait for the tests to pass
[ ] request a review

thanks!

" all of our profiles go through the install_run check."
I think we already do it for most profiles, but maybe not for this specific one. (I actually thought that we did it for all of them, though)


String#tr is broken implementation for character ranges and other regexp patterns

Artichoke
$ ./target/debug/airb
artichoke 0.1.0-pre.0 (2020-07-31 revision 3346) [x86_64-apple-darwin]
[rustc 1.45.0 (5c1f21c3b 2020-07-13)]
>>> "abcd".tr('a-z', 'xxx')
Traceback (most recent call last):
	6: from (airb):1
	5: from (eval):696:in tr
	4: from (eval):431:in gsub
	3: from (eval):417:in gsub
	2: from (eval):697:in tr
	1: from (eval):144:in []
TypeError (can't convert nil to Integer)
>>>

MRI
$ irb
[2.6.3] > "abcd".tr('a-z', 'xxx')
=> "xxxx"

Implementation
String#tr:
https://github.com/artichoke/artichoke/blob/0911db13eb7f03b1c87f1011e56e198d0a620c5e/artichoke-backend/src/extn/core/string/string.rb#L691-L699
String#gsub:
https://github.com/artichoke/artichoke/blob/0911db13eb7f03b1c87f1011e56e198d0a620c5e/artichoke-backend/src/extn/core/string/string.rb#L408-L437

I tested in current version and this bug is resolved, so can be closed.
❯ airb
artichoke 0.1.0-pre.0 (2021-01-02 revision 3927) [x86_64-apple-darwin]
[rustc 1.49.0 (e1884a8e3 2020-12-29)]
>>> "abcd".tr('a-z', 'xxx')
=> "xxxx"

I tested in current version and this bug is resolved, so can be closed.
❯ airb
artichoke 0.1.0-pre.0 (2021-01-02 revision 3927) [x86_64-apple-darwin]
[rustc 1.49.0 (e1884a8e3 2020-12-29)]
>>> "abcd".tr('a-z', 'xxx')
=> "xxxx"

hi @ekroon I kept this ticket open when merging #770 because String#tr still needs some work, see:
I tried this commit locally, and while it does improve spec compliance, there are still many ruby-spec failures. I'd like to take this PR with the changes I've requested.
Because String#tr still has some work to do, can you also edit the issue description to remove the "autoclose" annotation so GitHub does not close the attached ticket? Linking to it is fine.
Originally posted by @lopopolo in https://github.com/artichoke/artichoke/issues/770#issuecomment-670526801

hi @ekroon I kept this ticket open when merging #770 because String#tr still needs some work, see:
I tried this commit locally, and while it does improve spec compliance, there are still many ruby-spec failures. I'd like to take this PR with the changes I've requested.
Because String#tr still has some work to do, can you also edit the issue description to remove the "autoclose" annotation so GitHub does not close the attached ticket? Linking to it is fine.
Originally posted by @lopopolo in https://github.com/artichoke/artichoke/issues/770#issuecomment-670526801

Ah I see, well then I would like to attempt this one

Ah I see, well then I would like to attempt this one


feat: Better return messages in SQL Editor

SUMMARY
We wanted more robust messaging in Sql Lab that tells user what, if anything, is limiting the results that they get when they run a SQL query. Currently this file will also include a database migration, we are going to wait for this migration to resolve before we continue with this PR.
Because of the varied heights of the alert component, this PR will also fix some of the code in SQL Editor and SouthPane that uses static height.
This has custom messages that are based on:

DISPLAY_MAX_ROW causing the results to be limited (admin and non-admin messaging)
The query itself limiting the options
the dropdown limiting results
the default dropdown of 1000 being the cause for the limit

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:

After:
display max row for admin

non-admin

Query Limit

Dropdown limit:

Default Dropdown limit of 1000

TEST PLAN
Visual Testing
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@AAfghahi the non admin messsage should also have a header that displays the row returned number.

@AAfghahi the non admin messsage should also have a header that displays the row returned number.

Ah, they do. My picture was of the wrong thing. TY!

/testenv up

Fixes https://github.com/apache/superset/issues/14455 as bycatch

/testenv up

@yousoph do you want to take another pass at a visual review or are you good on this? I think it's ready to go, with one small change left.


CI: Added devDeps shield

Sorry! Totally forgot about this one

@amilajack
I got issues with eslint-plugin-flowtype-errors:
Oops! Something went wrong! :(
ESLint couldn't find the plugin "eslint-plugin-flowtype-errors".

Seems like that's why CI fails.
Does it works for you fine locally?


HSEARCH-2614 JSR-352: Test starting/stopping the job using WildFly tooling (e.g. CLI)

https://hibernate.atlassian.net//browse/HSEARCH-2614
Here we use WildFly's management APIs to start/restart jobs;
see https://docs.jboss.org/author/display/WFLY/Batch+(JSR-352)+Subsystem+Configuration#Batch(JSR-352)SubsystemConfiguration-DeploymentResources

I've run it twice locally, and it failed here too (on CI as well):
[ERROR] Failures:
[ERROR]   RemoteExecutionIT.checkIndexPopulated:186 expected:<3000> but was:<0>
[ERROR]   RemoteExecutionIT.restartAndSucceed:179 expected: but was:
[INFO]
[ERROR] Tests run: 87, Failures: 2, Errors: 0, Skipped: 0

Here. Let's wait for the CI build, but the problem should be solved. There was a side-effect between test classes that wasn't handled properly; it's fixed now.
Sorry about that.

very nice, thanks!


Corrects JSON message spelling for leader abdication

Documentation contains the correct spelling: “abdication”

JSON response is “abdicted”, fixed in this PR.

@bayendor thank you very much for the contribution!


[ServiceBus] Exception renaming

azure.servicebus.ServiceBusError now inherits from azure.core.exception.AzureError.
The parameter inner_exception that ServiceBusError takes is now renamed to error.
The following Service Bus errors are renamed:

MessageError to ServiceBusMessageError

reasoning: MessageError is a bit generic, in EventHub we have EventDataError, so in ServiceBus we could say it's a ServiceBusMessageError.

Removed error ServiceBusResourceNotFound as azure.core.exceptions.ResourceNotFoundError is now raised when a Service Bus resource does not exist when using the ServiceBusAdministrationClient.

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests


'Open Editors' panel has unnecessary padding

Hello VSCode friends,
The 'Open Editors' panel seems to have some extra unneeded padding on the left-hand side:

It looks like some part of this is to provide a 'close' x button or an "unsaved changes" dot indicator, and some of the padding serves no purpose that I can see.  I have a pretty small laptop screen, so this extra space could be put to better use rendering longer file names.
Would it make sense to remove the extra padding, and change the x button to only appear on hover on the right-hand-side, like the behaviour in the SCM commits panel?

If you think this change makes sense, I would be happy to attempt changing it myself.  If you think this is too minor an issue to address, or shouldn't be fixed, by all means feel free to close.

I wonder if we should move the X button to the right, where typically all actions are for lists/trees and thus have less padding altogether for the entries in the open editors view.


Fix flaky multiroot CI tests which uses api.serviceContainer

All these tests seem to be using api.serviceContainer to get the container instead of creating a new UnitTestIocContainer object in suiteSetup() hooks.
api = await initialize();
serviceContainer = api.serviceContainer;

These've recently started failing in CI every now and then. serviceContainer  is not initialized in the hooks (probably because of timeouts, but why didn't we get a timeout hook message 🤔), due to which accessing it later fails.
Changing them to use UnitTestIocContainer should solve the flakiness.

cc @karthiknadig I'll start fixing these if they appear on Github actions.

@karthiknadig I see these failures in Github action as well. Will start fixing these one by one.

Validated


Rabbit spirit contract inheritance issue

See here: https://amazing-cultivation-simulator.fandom.com/wiki/Spirit_Contracts#List_of_Effects

It's a weird/unintended design choice, definitely. But before it can be an issue, what should the intended result look like?
With the current vanilla experience, there are 3 types of Horse Modifiers, the generic Modifier_Horse_All_0, the GC Max Qi Modifier_Horse_All_7, and the racial ones at PS along with Fei/Lushu.

If the issue is about Inheritance, then removing the parent from all influenced modifiers is a possible fix, but it would make things harder in general due to the lowered Adventuring Speed.
If the issue is Rabbits being weaker due to inheritance overwriting the value, then the easiest thing is turning AddV=1 into AddV 2.5.

The second approach might be a bit more sensible in my opinion.


Viewlets should have appropriate heading level tag

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10
Additional Details:
ScreenReader,NVDA[2018.2],JAWS[18.0.5038],MAS1.3.1
Repro Steps:

Launch VS Code.
Navigate to Activity Bar and select "View Extensions "(Cntrl+Shift+X) button.
Navigate to complementary landmark -"View Extensions " section and read the content "View Extensions" using basic navigation.

Actual:
Screenreader does not read the content "View Extensions" as appopriate heading which is so.
Same issue has been observed with JAWS.
Expected:
Screenreader should read- "View Extensions" as heading with appropriate heading level.
Recommendations:
Add appropriate native heading level tag to the content "View Extensions".
or,
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
The screenreader users will not be able to know the appropriate headings present on the screen.
MAS Reference:
https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Does this issue occur when all extensions are disabled?: Yes
Attachment for Reference:

[Accessibility]A11y_VSCode_ViewExtensions_ScreenReader3.pptx

This should be done for all viewlets, not just extensions.
@JacksonKearl @ramya-rao-a do you plan to look into this or should I forward to someone else?
In case you do I guess this should be done somewhere in the CompositePart https://github.com/Microsoft/vscode/blob/9ab41a4464e62739fa8850d2aa312de2f72eb20d/src/vs/workbench/browser/parts/compositePart.ts#L409

I will look into this. Changing the title to be a heading rather than span doesn't seem to do anything. Will investigate further.

@JacksonKearl thanks for looking into this.

Note to verifier:
Check all viewlets, not just the one for Extensions

Also extension contributed viewlets. (GitLens, Azure App Service, etc.)

To view headings with NVDA, press Capslock+Space to toggle NVDA mode, then h and Shift+h to go forward and backward in headings.


feat(mv_v2_evaluation): Add use_mv_v2_evaluation

Add use_mv_v2_evaluation in order to support consistent mv evaluation for identities
Thanks for submitting a PR! Please check the boxes below:

[ ] I have run pre-commit to check linting
[ ] I have filled in the "Changes" section below?
[ ] I have filled in the "How did you test this code" section below?

Changes
Please describe.
How did you test this code?

Please describe.

Depends on https://github.com/Flagsmith/flagsmith-engine/pull/152

Depends on https://github.com/Flagsmith/flagsmith-engine/pull/152