Improve DataFrameSummaryAnalyzer

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (7f39e2a) 100.00% compared to head (dc42574) 99.81%.

Files
Patch %
Lines

src/flamme/analyzer/df_summary.py
55.55%
2 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              main     #269      +/-   ##
===========================================
- Coverage   100.00%   99.81%   -0.19%
===========================================
  Files           80       80
  Lines         2141     2148       +7
  Branches       231      233       +2
===========================================
+ Hits          2141     2144       +3
- Misses           0        2       +2
- Partials         0        2       +2

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


Add deprecation notes in pypi for Track 1 Storage, KeyVault, Event Hubs packages

Please wait for this issue to be updated with the template for the deprecation message

For KeyVault, please do like:
https://pypi.org/project/azure-storage/

azure-keyvault seems to already have deprecation notes, in that it correctly indicates the package is just now a bundle for installing the track 2 packages (https://pypi.org/project/azure-keyvault/). Does this suffice for the issue?

@mccoyp it's enough for me indeed, thanks for confirming!
Given the scope of this issue, closing since we have a story for all.


[fr] Localize website/content/en/docs/concepts/workloads/pods/pod-quos.md

This is a Feature Request

What would you like to be added
Translate https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/pods/pod-qos.md in French
Why is this needed
Comments

/language fr
/assign

/remove-lifecycle stale


Improve NPC interactions and extend NpcInteractEvent API

NPC interactions logic has been cleaned-up a bit; this should also fix problem described in #91.
New method has been added: NpcInteractEvent#getInteractionType, which returns:
a) NpcInteractEvent.InteractionType.LEFT_CLICK for left-click interactions.
b) NpcInteractEvent.InteractionType.RIGHT_CLICK for right-click interactions.
c) NpcInteractEvent.InteractionType.CUSTOM for interactions forced by API.

Marked as DRAFT because I have not fully tested these changes yet.

Should I also move event logic to PacketReader for version 1.20.1? This should hopefully decrease number of reports by users running outdated version of Paper (or fork), where PlayerUseUnknownEntityEvent#getClickedRelativePosition does not exist.

Should I also move event logic to PacketReader for version 1.20.1? This should hopefully decrease number of reports by users running outdated version of Paper (or fork), where PlayerUseUnknownEntityEvent#getClickedRelativePosition does not exist.

It makes sense to put the logic within the PacketReader as you said

I'm fine with both. Up to you, if you want to add a packetreader for 1.20.1 too.

Decided NOT to implement PacketReader for version 1.20.1 for following reason:

Addition of the PlayerUseUnknownEntityEvent#getClickedRelativePosition introduced number of internal changes to the ServerboundInteractPacket class and most notably, ServerboundInteractPacket.ActionType class and getActionType method are no longer public, which makes it tricky to handle both in the runtime and compilation-wise.

Other than that, I tested these changes on versions 1.19.4 - 1.20.4 and everything seems to work correctly. Marking as ready for review.


Holders always from MSFT ? (base.py:277)

base.py:
# holders
holders = _pd.read_html('https://finance.yahoo.com/quote/MSFT/holders')
self._major_holders = holders[0]
is this intentional hardcoded as MSFT ?

Yes 🙄 Fixed in 0.1.53


Internal cache not cleared properly after destroying select2

Property __cache from module Utils still retains DOM element from destroyed select2 instance.
Reproducible here: https://jsfiddle.net/wgnmvfbj/2/
Click on create then destroy, cache size will not go back to 0.
I've tracked down the issue to the following line adding to cache an item that is never removed: https://github.com/select2/select2/blob/ef33f4be110f5154c11b49d73e7b15921e143398/src/js/select2/core.js#L600
I didn't find any reason for caching $container, so I assume the fix could be simply removing that line.

Yup, that's been an issue for a while apparently. Looks like it is no longer cleaned up after we moved away from $.fn.data() and we never noticed it.
The original need for it was added in https://github.com/select2/select2/commit/130358e8ae26e632146674ab06e90e4ada36d027.


network default not found error when creating a container

Cookbook version
2.13.7
Chef-client version
12.7.2
Platform Details
Ubuntu 14.04 in vagrant and AWS EC2
Scenario:
Setting up a docker container fails with "network default not found" error.
Steps to Reproduce:
Create a docker container by using the following code.
docker_service 'default' do
  action [:create, :start]
end

docker_image 'grafana' do
  repo 'grafana/grafana'
  tag '3.1.1'
  action :pull
end

docker_container 'grafana' do
  repo 'grafana/grafana'
  tag '3.1.1'
  port '80:3000'
  restart_policy 'always'
  action :run
end

Expected Result:
Create a new container called grafana using grafana/grafana:3.1.1 image.
Actual Result:
ERROR: docker_container[grafana] (some_wrapper::metrics_store line <line_number that points to docker_container>) had an error: Docker::Error::NotFoundError: network default not found

Possibly related to this.

Specifying network mode by adding network_mode 'bridge' seems to work around the problem.

I have a fix incoming for this but currently running into test-kitchen issue. Once tests pass I will release.

This should be fixed up in 2.13.8


Added initial DatePickerTheme, DatePickerThemeData to customize showDatePicker appearance

Added initial DatePickerTheme to customize showDatePicker appearance for now it only has:

backgroundColor
entryModeIconColor
helpTextStyle
shape
selectedDayDecoration
disabledDayDecoration
todayDecoration

Partially fixes #93707
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

@darrenaustin , thank you for the review, I updated the PR as such.
Kindly check and let me know if any more updates are required.

@darrenaustin all done, please check and let me know.
Btw the error in rainbowmonkey customer test doesnt seem relevant to the pr, right?

any updates, is the customer tests related to the PR ? @darrenaustin

Can you please resolve conflicts and merge/rebase? Should clear the testing issue.

@guidezpl , Done ✅
Some tests are failing but I don't know how it's related to the PR.

Rebased again, and all checks passed @guidezpl

Need theme support for https://github.com/flutter/flutter/issues/101481

Great, looking for approval from @darrenaustin since he requested changes.

@darrenaustin could you review this MR again?

Really sorry about the lag on this. I have not had the cycles to devote to this. However, given that there is an update to the design of the Date Picker for Material 3 coming shortly, I think it would be best to wait until we add M3 support to the date picker to add a theme. That way we make sure the properties we support in the theme are the same as the spec and we won't need to break anything to support M3. The issue tracking this is:
#101481.
I will make a note there to reference this PR when the spec is available the M3 data picker. Hopefully we can still use this work in some form during the M3 migration. In the mean time I will go ahead and close this PR while awaiting the spec.
Thanks so much for your contribution and your patience.


[React Aria] Focusing issues with useSelect when using a controlled component pattern and initial value is empty string

🐛 Bug Report
I'm running into an issue with a controlled component pattern, where setting the selectedKey of a component built with useSelect to an empty string results in focusing issues.
const [animal, setAnimal] = React.useState('');

<Select selectedKey={animal} onSelectionChange={(value) => setAnimal(value)}>

When navigating with a keyboard and pressing the DOWN key, the Popover / ListBox opens, but instead of navigating up and down through the items it just keeps closing and opening.

This issue doesn't happen if setting the initial state to null - however that results in a React warning about component changing from uncontrolled to controlled as soon as a selection is made, which isn't desired. This was the recommendation in a similar issue #1580, but it doesn't seem to account for the warning.
🤔 Expected Behavior
Navigating to the component with a TAB key and then pressing DOWN should open the Popover / ListBox and go through the selection
😯 Current Behavior
Navigating to the component with a TAB key and then pressing DOWN repeatedly opens and closes the Popover / ListBox
💁 Possible Solution
N/A
🔦 Context
I'm trying to build a custom Select using one of the provided examples in the docs, and make sure that it can be used as a controlled component.
💻 Code Sample
https://codesandbox.io/s/react-aria-select-vgl4n9?file=/src/App.tsx
🌍 Your Environment

Software
Version(s)

react-aria
3.21.0

Browser
Chrome 107

Operating System
MacOS 13.0.1

🧢 Your Company/Team
External
🕷 Tracking Issue (optional)
N/A

I'm not seeing the "uncontrolled to controlled" error when initializing animal to null: https://codesandbox.io/s/react-aria-select-forked-846tnk?file=/src/App.tsx, do you have another sandbox demonstrating that? As a side note, I've turned off the Typescript strict null check in that sandbox, the null Typescript issues is something we are aware of and incrementally fixing via https://github.com/adobe/react-spectrum/issues/3183.

Hi @LFDanLu - thanks for the quick response!
Turns out it was my own wrongdoing after a long day of looking at the same code 🤦♂ I was seeing the warning only when initializing to undefined instead of null - which makes sense.
Thanks again! Closing the issue now.


Open Handle detected in Jest test using SDK

We're using the SDK in a Nest Service and then testing the service with Jest. In the test, we're seeing an open handle from importing Evervault when running the test.
Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  CustomGC

    > 1 | import Evervault from "@evervault/sdk";
        | ^
      2 | import { Injectable } from "@nestjs/common";
      3 |

      at Runtime._loadModule (../../../node_modules/.pnpm/jest-runtime@29.6.4/node_modules/jest-runtime/build/index.js:1018:29)
      at Object.<anonymous> (../../../node_modules/.pnpm/evervault-attestation-bindings@0.3.2/node_modules/evervault-attestation-bindings/index.js:110:25)
      at loadAttestationBindings (../../../node_modules/.pnpm/@evervault+sdk@5.1.4/node_modules/@evervault/sdk/lib/utils/attest.js:11:12)
      at Object.<anonymous> (../../../node_modules/.pnpm/@evervault+sdk@5.1.4/node_modules/@evervault/sdk/lib/utils/attest.js:7:29)
      at Object.<anonymous> (../../../node_modules/.pnpm/@evervault+sdk@5.1.4/node_modules/@evervault/sdk/lib/utils/index.js:9:11)
      at Object.<anonymous> (../../../node_modules/.pnpm/@evervault+sdk@5.1.4/node_modules/@evervault/sdk/lib/index.js:12:5)
      at Object.<anonymous> (auth/evervault.service.ts:1:1)

Any ideas on how to fix this or if this is an issue?

Thanks for reporting!
As your stack trace shows, this issue is with the dynamic import of the evervault-attestation-bindings from our attest.js module in the Node SDK (permalink). This dependency is optional, and only required if you are using our Enclaves product so the quickest resolution is to omit optional dependencies when installing the Evervault SDK - npm install @evervault/sdk --omit=optional if you're using npm.
A bit more context: our attestation bindings use a Rust crate exposed via native bindings for Node, as well as several other languages. The native bindings are platform specific, so the top level evervault-attestation-bindings dynamically resolves the appropriate package (we're using napi-rs for this, you can read more about it in their docs). This involves checking the file system for the appropriate, which doesn't seem to play nicely with the jest runtime's module loader.
I've replicated the issue in a local test suite, though I'm yet to see jest fail to exit so it may be a false positive. Has this warning resulted in hanging tests for you? Regardless, we'll see if it can be fixed.

I've replicated the issue in a local test suite, though I'm yet to see jest fail to exit so it may be a false positive. Has this warning resulted in hanging tests for you?

It has resulted in hanging tests for us; one test in particular lasts much longer than it should have.
Is there a way to omit the optional dependency in package.json? I can't seem to figure out how to do so but maybe I'm missing something...

 What other features of the SDK are you using?
Re: optional dependencies, the only way to omit them is during the initial install (using npm install @evervault/sdk --omit=optional). There isn't a way to omit optional dependencies through the package.json. The support is limited to per package at install, or for all dependencies at the project level (i.e. through the --omit flag, or through the npm config).
We're going to explore ways to remove our optional dependencies from the package, and move them to a plugin.


UWP/WinRT Libraries should be able to expose .NET interfaces and classes

Proposal:
UWP/WinRT Libraries should be able to expose .NET interfaces and classes
Summary
It should be possible to create UWP controls which implement .NET Standard interfaces in an UWP control library. Currently it's only possible when the control is moved to the project of the host application. This prevents the reusability of the control.
Rationale
When implementing an UWP control using ReactiveUI, we need to put an IViewFor<TViewModel> interface on the control.
For reusability with non-UWP Apps, the ViewModel might be a class from an .NET Standard project. Also the IViewFor<> Interface is defined in a .NET standard library.
As long as the control is defined in the UWP app project, everything works fine. However, the code does not compile when the control is moved to an external library.
Scope
It shouldn't be required to reimplement .NET Standard libraries as WinRT libraries.

Capability
Priority

This proposal will allow developers to expose .NET Standard interfaces and classes in WinRT libraries
Must

Important Notes

ReactiveUI

Open Questions
It is unclear to me how to best approach this issue.

Thank you! Are you aware of any samples we could look at to understand the request further?  I think you're asking:

A C# project defines a type Contoso.IMuffin and has APIs that accept/generate IMuffin
A C++ type wants to implement Contoso.IMuffin on one of its objects and pass it to the C# type accepting IMuffin

Hey @Scottj1s or @kennykerr , any suggestions?

Here is a minimal example project:
WinRTTest.zip

I'd need to see a more concrete example, ideally one not involving Xaml. If this is specific to Xaml, we'd need to WinUI folks to chime in on how they recommend supporting this.

The problem is not specific to XAML. The XAML controls are just my use case.
When you do it like this instead:
public sealed class Foobar : IViewFor<MyViewModel>
    {
        object IViewFor.ViewModel
        {
            get => ViewModel;
            set => ViewModel = value as MyViewModel;
        }

        public MyViewModel ViewModel { get; set; }
    }

you have the same problem.

A wild guess - without knowing the internals - is that the metadata exposed by the WinRT library is insufficient to describe the .NET interfaces.

To clarify: Are you trying to build a WinRT Library (because...?) and you want to expose .NET Standard types from that Library (because...?).
Do you expect 100% of the APIs to work for both WinRT and .NET clients, or do you expect "graceful degradation" where (eg) if you are using the API from C++ you can't use any APIs that require (eg) a System.IO.FileInfo object, but you can use the others that don't?

It's about how to structure a project. In a given solution I usually have the following projects:

the system specific host library, containing the Program.cs/App.xaml
the controls library containing the system specific UI logic
a business layer containing view models and other device indepent logic
data access layer libraries, containing database or API access

So in this case I need to expose the .NET interface  in the controls library, because i need those for dependency injection configuration in the application host.

do you expect "graceful degradation" where (eg) if you are using the API from C++ you can't use any APIs that require (eg) a System.IO.FileInfo object, but you can use the others that don't?

I would expect full functionality and be able to use those interfaces from C++ too, because you can already use 'pure' .NET Standard libraries in WinRT Host projects without issue.
So I am unsure why degragation would be needed. However, it might be an option using a special moniker that marks it such that it can.be used from managed projects only.

Your guess is correct in that the WinRT type system cannot express all .NET types, and hence the compiler complains. The compiler is overly-aggressive in this case, since "who cares?" if your app has implementation details that aren't expressible, but that's the current design.
Is the Controls Library in your example supposed to be reusable from other languages like C++ or Python etc. or is it just private to your application? (I'm trying to figure out if you actually need a WinRT library that has non-standard types, or if you would be happy with just a .NET Standard library). I'm also curious what specific technique you are using to access the .NET Standard library from C++ today.
In the meantime, if you want a work-around, you could consider making your .NET types internal and use the InternalsVisibleTo attribute to access them from other assemblies. The compiler won't care about those, since they're not public.

since the goal is to create a UWP component library to be used by multiple UWP projects, so yes, this is the goal.
Using the internalsvissibleto is not a proper solution, since it inverses the dependency from host -> component to component -> host.
We're not using C++ and Python, so this is not my immediate need.
I guess the proper solution is to extend the WinRT type system to support .NET standard types.

since the goal is to create a UWP component library to be used by multiple UWP projects, so yes, this is the goal.

But do you require WinRT for that? (Pretend that the current tools didn't force you down that path... would you independently choose to build a WinRT library instead of just a .NET library? Why?).
I asked about C++ (or any non-.NET language, really) since you mentioned that you expected native .NET types to work without degradation in other languages, which surprised me because that's not generally the case today.

But do you require WinRT for that? (Pretend that the current tools didn't force you down that path... would you independently choose to build a WinRT library instead of just a .NET library? Why?).

No. I always switch to WPF, because this issue prevents me from using WinRT. Which is a shame, because WinRT provides improved security features, portability and APIs which aren't available in .NET Projects.
An partial alternative would be to access the WinRT APIs from .NET projects.

Ah, it seems you are using "WinRT" to mean "the collection of technologies we called UWP." Our naming / marketing is not great here, sorry. (And if I misunderstood you - sorry as well :)).
WinRT is just a way to define APIs; WinRT doesn't provide improved security - running in an AppContainer (aka Native Container) provides you with improved security.
Most WinRT APIs are now available for .NET projects - add the Microsoft.Windows.SDK.Contracts package, the Microsoft.UI.XAML package and most things will work. Some still require identity - packaging as MSIX solves that - and a small number require AppContainer, which there isn't really an easy way to solve that.
(Please note I am not meaning to push back or claim everything is perfect today - it's not - but I'm trying to learn what you need... "public .NET types in WinRT assemblies" is a very specific implementation ask that has a set of possibly-bad ramifications and you might not actually need that).

@MovGP0 I see you 'heart'-ed the response; does that mean we can close the issue, or are you still looking for the specific ask of public .NET Types in WinRT assemblies?

@MovGP0 I see that you're using the Windows Runtime Component project type, this project type creates a .winmd and is limited to only exposing WinRT types, which for all the reasons @ptorr-msft said, can't contain .NET types. We do support you creating regular .NET class libraries, in which case you can expose these .NET APIs to your customers. You do this by using the Class Library project type.
Screenshot below that should better articulate what I'm referring to:


⚠ Bofrost.at has degraded performance

In 6ec8c47, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 972 ms

Resolved: Bofrost.at performance has improved in 4977e25 after 13 minutes.


Atomically set PWM outputs

I believe the i.MX RT PWM peripherals could let us set PWM duty cycles atomically across a single peripheral's outputs. This could give us a guarantee that, when we say "set all motor throttles to [value]" we've changed the duty cycle for all PWM outputs at exactly the same time (within the bounds of a PWM cycle).
We can't express atomic changes with today's driver. We can only loop over the N outputs, and set them all to the same throttle. With this API, there's a chance that the first few motors are set to the throttle before the other motors.
This issue tracks atomic changes to PWM outputs.

[ ] Re-evaluate the peripheral, and see if it's feasible
[ ] Figure out if this feature is necessary
[ ] Implement it

Our ESC interface already has an API for atomic changes. The default implementation just does the non-optimal loop. If we think that this feature is necessary, let's make sure to design to that API.
https://github.com/ebelski/rust-copter/blob/b12f95fa99cb61595e41ef21fce39d01f53f29ec/common/esc/src/lib.rs#L35-L52

I'm on the fence between must-have and nice-to-have for this feature. If we were directly driving motors with our PWM outputs, I'd say this is very useful. But, since we're talking to a different ESC today, and we don't control the behaviors on that ESC, I'd think that atomic PWM changes on our end would be an over-optimization.
In practice, I'd expect a loop to set the PWM outputs to happen so fast that it's basically atomic (should verify this). We could prevent software preemption with a critical section.

Did you have something in mind for verifying this? Such as connecting it to a logic analyzer?

First thing to verify is that the chip supports a way to atomically set the PWM outputs. Given the description from the fields in this PWM MCTRL register (image below), my interpretation is "yes." I still need to dig in.
Each PWM peripheral supports eight outputs (four submodules, each driving two pins). So to set the values across all eight simultaneously, the flow resembles

write 0b1111 to CLDOK, or wait for LDOK to read zero.
[set PWM values for all four outputs in other registers]
write 0b1111 to LDOK

Once 3 happens, the peripheral loads the PWM values for all outputs, and starts driving with the new values.
Showing this happens with a logic analyzer would be good evidence. But, it wouldn't be complete verification. Today, we can show that we appear to be changing all PWM outputs at the same time; we're lucky.
I'll look into this as I play with the HAL. Could be cool to implement, but still not convinced we need it for today's system.

I tend to agree that we don't need this. Since we prove (or can prove) that they're setting roughly at the same time, I think that's good enough.
When we start to load the Teensy with more processes we will want to verify this doesn't change.


this.$nuxt.$loading.start is not a function #729

Re-opening a year old issue which I think still unresolved. It's not working at multiple places even inside mounted event.
Error: "this.$nuxt.$loading.start is not a function".

This question is available on Nuxt community (#c7451)

Hello, did u managed to solve this matter?
Best regards!


add nonce verification when processing $_POST

This is a security loophole Codacy brought to my attention:

It's not an emergency, but we should look if lack of nonce verification exposes any danger of CSRF attacks and if so, how to prevent this.

I don't think this is an issue. We are using that setPost to store the data as context for an error, we are not actually sending this request.

Cool. In that case I'll just annotate this to not be ignored by PHP MD


Is it really WebSocket ?

I don't know much about this, but it seems you are not actually using WebSocket in this project.
Also, I tested it through cloudflare, which should support websockets, but there was no connection and I could not connect to my test server through cloudflare proxy.
I haven't tried running this project in a browser, but I'm really confused about what protocol is actually being used here.
https://github.com/pleyland/Websocket-Multiplayer-Demo-Godot-4.0/search?q=WebSocket
https://docs.godotengine.org/en/stable/tutorials/networking/websocket.html

You are right, it does not use websocket, it's an update of the websocket
demo, using ENet
Kind Regards,Tom
3D Animation // Illustration // Fine Artist
Cell:<PHONE_NUMBER>  //  Tel:<PHONE_NUMBER> // Email @.***
*
http://www.wix.com/blanccanvas/collectivehttp://www.blanccanvascollective.com/
http://www.blanccanvascollective.com/*
P.S. We are SO HAPPY to launch our new product:
*The 360 degree Camera! *
Please click this link to view an example:  360 CAMERA
https://www.blanccanvascollective.com/copy-of-360-vr
On Sun, Mar 26, 2023 at 3:34 PM DearFox @.***> wrote:

I don't know much about this, but it seems you are not actually using
WebSocket in this project.
Also, I tested it through cloudflare, which should support websockets, but
there was no connection and I could not connect to my test server through
cloudflare proxy.
I haven't tried running this project in a browser, but I'm really confused
about what protocol is actually being used here.
https://github.com/pleyland/Websocket-Multiplayer-Demo-Godot-4.0/search?q=WebSocket
https://docs.godotengine.org/en/stable/tutorials/networking/websocket.html
—
Reply to this email directly, view it on GitHub
https://github.com/pleyland/Websocket-Multiplayer-Demo-Godot-4.0/issues/1,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7TXJKGIYUXTODHDM77UGTW6BAWFANCNFSM6AAAAAAWIGCJYE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Follow-up to #6855

Fix issues introduced in #6855:

close files properly in loadmat/whosmat
move test suite file under io/, switch to nose from unittest to maintain uniformity, and add .sav test using existing test files

LGTM, merged.

Thanks for the follow-up -- I'm not that familiar with the SciPy code base, and added the test code for this to the first place I found that seemed appropriate.


graphdriver - prior storage driver \“btrfs\” failed: prerequisites for driver not satisfied (wrong filesystem?)

Hello, I tried to use the following command:
> docker run -d -p 8080:80 -p 8800:8800 -p 9002:9002 --privileged=true -e "GALAXY_LOGGING=full" bgruening/galaxy-stable

and received the following docker error massages (http://<IP_ADDRESS>:9002):
time="2016-01-04T10:31:04.992632146Z" level=error msg="[graphdriver] prior storage driver \"btrfs\" failed: prerequisites for driver not satisfied (wrong filesystem?)"
time="2016-01-04T10:31:04.992777695Z" level=fatal msg="Error starting daemon: error initializing graphdriver: prerequisites for driver not satisfied (wrong filesystem?)"
time="2016-01-04T10:31:06.329986754Z" level=error msg="[graphdriver] prior storage driver \"btrfs\" failed: prerequisites for driver not satisfied (wrong filesystem?)"
time="2016-01-04T10:31:06.330140404Z" level=fatal msg="Error starting daemon: error initializing graphdriver: prerequisites for driver not satisfied (wrong filesystem?)"
time="2016-01-04T10:31:09.000757480Z" level=error msg="[graphdriver] prior storage driver \"btrfs\" failed: prerequisites for driver not satisfied (wrong filesystem?)"
time="2016-01-04T10:31:09.000911410Z" level=fatal msg="Error starting daemon: error initializing graphdriver: prerequisites for driver not satisfied (wrong filesystem?)"

Similar error I get with:
> sudo docker -s btrfs -d -D
Warning: '-d' is deprecated, it will be removed soon. See usage.
WARN[0000] please use 'docker daemon' instead.
DEBU[0000] docker group found. gid: 999
DEBU[0000] Server created for HTTP on unix (/var/run/docker.sock)
DEBU[0000] [graphdriver] trying provided driver "btrfs"
FATA[0000] Error starting daemon: error initializing graphdriver: prerequisites for driver not satisfied (wrong filesystem?)

I am using Linux Mint 17.2 and docker 1.9.1 (build a34a1d5) in a VirtualBox. My host OS is CentOS 6.6.
$ uname -a
Linux galaxy-VirtualBox 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I also updated the kernel with sudo apt-get install linux-headers-4.2 linux-image-4.2, but it still did not solve the problem
$ uname -a
Linux galaxy-VirtualBox 4.2.0-22-lowlatency #27~14.04.1-Ubuntu SMP PREEMPT Fri Dec 18 12:20:01 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

> df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  6.1G  4.0K  6.1G   1% /dev
tmpfs          tmpfs     1.3G  1.2M  1.3G   1% /run
/dev/sda1      ext4      1.9T  122G  1.7T   7% /
none           tmpfs     4.0K     0  4.0K   0% /sys/fs/cgroup
none           tmpfs     5.0M     0  5.0M   0% /run/lock
none           tmpfs     6.2G  1.5M  6.2G   1% /run/shm
none           tmpfs     100M   32K  100M   1% /run/user

$ docker info
Containers: 80
Images: 232
Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 392
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.0-22-lowlatency
Operating System: Ubuntu 14.04.3 LTS
CPUs: 6
Total Memory: 12.23 GiB
Name: galaxy-VirtualBox
ID: 7YSZ:MWKF:XJV6:QDJ3:CEA5:IQ2Y:DNJY:RGZB:7CIZ:RMGG:RI5T:XP23
WARNING: No swap limit support

$ docker version
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.3
Git commit:   a34a1d5
Built:        Fri Nov 20 17:56:04 UTC 2015
OS/Arch:      linux/amd64

Server:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.3
Git commit:   a34a1d5
Built:        Fri Nov 20 17:56:04 UTC 2015
OS/Arch:      linux/amd64

I also posted the problem to http://stackoverflow.com/questions/30669359/docker-with-btrfs-ubuntu .
What did I do wrong?

In order to use btrfs, docker storage dir must be on a btrfs partition.

For more information on using the btrfs storage driver, please refer to this section of the documentation; https://docs.docker.com/engine/userguide/storagedriver/btrfs-driver/


[Typespec] Extends Record breaks the codegen

Add extends onto a model caused the emitter to produce the following error:
<EMAIL_ADDRESS>line 35, in _get_properties
    p for p in parent.properties if p.client_name not in property_names
AttributeError: 'DictionaryType' object has no attribute 'properties'

For clarity, this TypeSpec:
model MyModel extends Record<unkwown>

is the exact same thin as Swagger:
additionalProperties: true

This works with types too:
model MyModel extends Record<string>

is the exact same thin as Swagger:
additionalProperties: string

So I expect the YAML we produce as the intermediary format to be the same for those scenarios. Let's not model this differently if it's coming from Swagger or TypeSpec.
Also, irony is that Python doesn't care about this information, as we treat everything with additional properties activated anyway, so codegen should not fail, but ignore the info.

(1) input model used for request body

For msrest model, users set additional properties like: `MyModel(..., additional_properties={"prop1": "abc"})
For DPG model, users can directly input like: MyModel({..., "prop1": "abc"})
(2) output model deserialized from response
For msrest model, users can touch additional properties like my_model.additional_properties["prop1"]
For DPG model, users can directly touch it like my_model["prop1"]

We can see that DPG model is more convenient since it is inherited from mapping so DPG model supports additional_properties natively.

I believe this issue has been fixed, @l0lawrence please reopen if it's still an issue


Add contrib code to load GP data from Celestrak

As well as other style changes to contrib/ code.
I'm so happy I don't have to find the right API or module for this, just dump some useful code to a file and move on 😀

Looks like it's working correctly on my tests. Merging :+1:


Make TICK_INTERVAL configurable in Meter via constructors

Pull request for [Make TICK_INTERVAL configurable in Meter via constructors] (https://github.com/dropwizard/metrics/issues/764).

Changing the tick interval on a meter doesn't make sense, since the 1, 5 & 15 minute exponentially weighted moving averages expect a 5 second tick.


remove npm install --production from ansiblels

Latest ansible-language-server fails on install with this line present.
the combination of npm install and npm run compile should be enough since npm install gets both the production and dev dependencies.
npm install --production fails with missing typescript type definitions missing.
 node_modules/@nodelib/fs.scandir/out/providers/async.d.ts(1,23): error TS2688: Cannot find type definition file for 'node'.
 node_modules/@nodelib/fs.scandir/out/providers/async.d.ts(4,45): error TS2503: Cannot find namespace 'NodeJS'.
 node_modules/@nodelib/fs.scandir/out/types/index.d.ts(1,23): error TS2688: Cannot find type definition file for 'node'.

I can back this change, just did this myself during lunch then noticed this pull request before I made mine 😄 . Since we're building from source we do need the typescript dependencies. Seems to be related to this commit from ansiblels. Using a revision before that commit works fine -- arguably an ansiblels issue instead of this project.

BTW @williamboman there is a current issue with ansible-language-server that I have a pull request for that effects neovim users: https://github.com/ansible/ansible-language-server/pull/246
Is there a good way to configure to use my fork with lsp-installer before this pull request gets merged?
Im currently editing ~.local/share/nvim/site/pack/packer/start/nvim-lsp-installer/lua/nvim-lsp-installer/servers/ansiblels/init.lua
to accomplish this.


Allow each control to use a specific custom style defined in the assigned theme

Godot version:
master / cfcb6e11f25ad
OS/device including version:
Manjaro Linux 17.1
Issue description: (This issue is a feature request)
When defining an UI theme, sometimes it's needed to make the same type of control to look differently depending on a context.
For example, a Panel can have an opaque background normally, but when they are used as a backdrop of a modal dialog, it's maybe necessary to show them with a translucent background.
With CSS, such a use case would be covered by declaring a style definition for normal panels and an override for backdrop panels, which can be identified by having a specific CSS class, like backdrop:
.panel {
    background-color: black;
}

.panel.backdrop {
    opacity: 0.5;
}

However, in Godot, it seems that there's no clear way to achieve a similar functionality. I can define a theme resource which defines how all panels must look, but if we want to make a certain type of panels to look differently, we need to either create a separate theme, or define a stylebox and set it to individual Panel instances.
It seems that it's possible to define various custom styles for such controls like Button or Panel, but apparently it's not possible currently, to make each control to use one of those custom styles defined in a theme its using rather than the default one.
It'd be better if there is a way to specify that a control belongs to a certain group, i.e. backdrop, so it should be rendered differently according to a custom style defined for that context in its associated theme.

Intersting though!
I'm thinking a lot about godot themes. And of course there is lot of potwntial for  improovement.
To answer your question: you are supposed to use stylebox override for this...
Theming in godot is very simple. It's basically a dicrionary with objects (styleboxes) which know how to draw rectangles ;) ) thats it.
But godot is a game engine. Not gtk or qt ;)
So this simple approach night be the right choice. It's still possible to achieve a lot with it.
It would need quiet a bit of work to make it a fully css themable platform.
But what u can do, is introduce new theme classes. Create a theme in gdscript. Add a stylebox for ("panel/popover","Panel") (first string can be anything) than, mark all the panels you want in that class with add_style_override

But if you convince me, with a very nice implementatiln, and some good arguments, i might do sone work on theming. Planning to do that anyways. (Shader style boxes, theme based dpi setting with inmediate update, better theme loading withou all svg recreating, auto icon upscaling woth bitmap icons...)

I'd love to see this implemented. As a workaround I'm using 4 themes in my game h1.theme, h2.theme... and applying them selectively to different components. But, it's a little clumsy and eliminates a lot of the convenience of applying a single theme to a UI component and having it get inherited throughout

Closing in favor of https://github.com/godotengine/godot-proposals/issues/850, as feature proposals are now tracked on the Godot proposals repository.


261: Add Kafka To Master Chart

Updated forklift + valkyrie to use the newly placed kafka broker
Added reasonable default resources for forklift to ensure it could run
Upgraded kafka to 2.5.1 and strimzi to 22.0

Do you need to add kafka to the requirements.yaml for urbanOS?

Do you need to add kafka to the requirements.yaml for urbanOS?

I just realized you can't release without first doing this... Right?

Do you need to add kafka to the requirements.yaml for urbanOS?

I just realized you can't release without first doing this... Right?

Kinda. Good catch!
This is part one of two, (which I should have explained in the body of the PR, so my apologies). In order to update UrbanOS requirements, the kafka chart / tar needs to exist on the /charts remote. So the plan is to merge this (the dependency changes) and then have an immediate follow up that updates the UrbanOS chart to utilize those previously altered dependancies.


added spectra plots to flask app

Added spectra plots to flask app (addresses #36):

Added per-spectrograph views of spectra (navigate by url/{night}/{expid}/spectra/spectrograph):

Randomly chooses 3 fibers per spectrograph and plots its blue, red, and infrared spectras
All plots share pan/zoom, and support hover

Added per-object-type views of spectra (navigate by url/{night}/{expid}/spectra/objtype):

Randomly chooses 5 fibers per objtype and plots its blue, red, and infrared spectras
For the read data (20190306/00001076), the objtype field is blank and is treated as 1 objtype
Hover tool is supported

Added choose-specific-fibers view of spectra (navigate by url/{night}/{expid}/spectra/input):

Plots all fibers provided by the user
Hover tool is supported

I did not add the qa-header to the pages because I was not sure if we wanted to group these plots with qa plots.

Also, these pages are autogenerated by the flask app (on the fly, albeit a bit slow), and not generated by qqa. I can have the first 2 views (per-spectrograph and per-object-type) generated within qqa, but the input view page requires the flask app.

I'll merge this now because I want to be able to use some of the pieces, but please add docstrings for all functions and commit those directly to master.  Thanks.


Fix issue #1546 of UILayout(#1549) and small performance boost

Which branch your pull-request should merge into?

dev: Current 2.x BugFixs or Features

Describe your changes
[FIX] Issue #1546 of UILayout(#1549) and small performance boost
[New] Feature:  Add API for backwards compatible flag and a test too
Issue ticket number and link
Checklist before requesting a review
For each PR

[x] I have performed a self-review of my code.
Optional:

[ ] I have checked readme and add important infos to this PR.
[ ] I have added/adapted some tests too.

For core/new feature

[x] I have checked readme and add important infos to this PR.
[x] I have added thorough tests.

@halx99
Please merge it.
@rarepixels ,
Can you test it after merge?
This should FIX your iPad issue.


Split getRootProps into Drop and Select (event onclick)

Again !
Guys can you split the getRootProps into two parts
one just for drag drop files
and the other one for selecting a file
because mixing those two make it limited to use
Sometime clicking the drop zone does not mean choosing a file,
Imagine you have a drop zone and inside you have the list of drag-dropped files and each file has a delete button , if you try to click in the button it will open the file dialog
I don't know if you got the idea 😅
Thanks.
Greetings.

Sorry for late.
In that case, we should stop propagation on <DeleteButton />


403: Forbidden Response when AllowBulkExecution = true + Resource Token

Describe the bug
When retrieving a resource token to make api calls to Azure Cosmos DB, and the client is created with the AllowBulkExecution = true, then Azure Cosmos DB returns a 403: Forbidden error on an api call.
The same options work fine when using the local CosmosDB emulator.
The call api calls also work fine if AllowBulkExecution setting is false.
I've checked my azure CosmosDB firewall settings: it's set to allow all networks.
To Reproduce
Can be reproduced using this project: https://github.com/InquisitorJax/Xamarin-Cosmos-DB
Check the readme file on setting up the local.settings.json file to retrieve the resource token from an azure instance.
Expected behavior
Api calls should be successful.
Actual behavior
403: Forbidden Error is returned:
Environment summary
SDK Version: 3.12.0
OS Version (e.g. Windows, Linux, MacOSX)
Windows
Additional context
Stack Trace:
{Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: Forbidden (403); Substatus: 0; ActivityId: ; Reason: ();
at Microsoft.Azure.Cosmos.ResponseMessage.EnsureSuccessStatusCode () [0x0000e] in <250931dbc7a64174b3f1ed93d3081ffb>:0
at Microsoft.Azure.Cosmos.CosmosResponseFactoryCore.ProcessMessage[T] (Microsoft.Azure.Cosmos.ResponseMessage responseMessage, System.Func2[T,TResult] createResponse) [0x00002] in <250931dbc7a64174b3f1ed93d3081ffb>:0    at Microsoft.Azure.Cosmos.CosmosResponseFactoryCore.CreateItemResponse[T] (Microsoft.Azure.Cosmos.ResponseMessage responseMessage) [0x00000] in <250931dbc7a64174b3f1ed93d3081ffb>:0    at Microsoft.Azure.Cosmos.ContainerCore.CreateItemAsync[T] (Microsoft.Azure.Cosmos.CosmosDiagnosticsContext diagnosticsContext, T item, System.Nullable1[T] partitionKey, Microsoft.Azure.Cosmos.ItemRequestOptions requestOptions, System.Threading.CancellationToken cancellationToken) [0x000b0] in <250931dbc7a64174b3f1ed93d3081ffb>:0
at Microsoft.Azure.Cosmos.ClientContextCore.RunWithDiagnosticsHelperAsync[TResult] (Microsoft.Azure.Cosmos.CosmosDiagnosticsContext diagnosticsContext, System.Func2[T,TResult] task) [0x0009e] in <250931dbc7a64174b3f1ed93d3081ffb>:0    at XamarinCosmosDB.CosmosRepository.SaveModelAsync[T] (T model) [0x0009e] in D:\DEV\Git\Xamarin-Cosmos-DB\XamarinCosmosDB\XamarinCosmosDB\CosmosRepository.cs:137  --- Cosmos Diagnostics ---{"DiagnosticVersion":"2","Summary":{"StartUtc":"2020-08-17T21:32:30.8715930Z","TotalElapsedTimeInMs":12290.9743,"UserAgent":"cosmos-netstandard-sdk/3.12.0|3.11.4|02|X86|Unix <IP_ADDRESS>|Mono 6.12.0 2020-02 83105ba2246 |F 00000001|","TotalRequestCount":2,"FailedRequestCount":2},"Context":[{"Id":"SynchronizationContext","ElapsedTimeInMs":11.1346},{"Id":"ItemSerialize","ElapsedTimeInMs":134.708},{"Id":"UsingWaitAsync","ElapsedTimeInMs":0.8897},{"Id":"Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler","HandlerElapsedTimeInMs":3558.1352},{"Id":"Microsoft.Azure.Cosmos.Handlers.RetryHandler","HandlerElapsedTimeInMs":3504.7875000000004},{"Id":"Microsoft.Azure.Cosmos.Handlers.RouterHandler","HandlerElapsedTimeInMs":3464.9487000000004},{"Id":"Microsoft.Azure.Cosmos.Handlers.TransportHandler","HandlerElapsedTimeInMs":127.7205},{"Id":"AggregatedClientSideRequestStatistics","ContactedReplicas":[{"Count":1,"Uri":"rntbd://cdb-ms-prod-eastus1-fd42.documents.azure.com:14104/apps/814e7582-0a8b-498b-8d4f-92263e029030/services/f2d1101a-4d64-4d76-bfa7-e60d2dcfe6c4/partitions/22211ae2-1228-4497-bdbd-d913f933812e/replicas/132368769092028206s/"},{"Count":1,"Uri":"rntbd://cdb-ms-prod-eastus1-fd42.documents.azure.com:14432/apps/814e7582-0a8b-498b-8d4f-92263e029030/services/f2d1101a-4d64-4d76-bfa7-e60d2dcfe6c4/partitions/22211ae2-1228-4497-bdbd-d913f933812e/replicas/132389420512205363s/"},{"Count":1,"Uri":"rntbd://cdb-ms-prod-eastus1-fd42.documents.azure.com:14148/apps/814e7582-0a8b-498b-8d4f-92263e029030/services/f2d1101a-4d64-4d76-bfa7-e60d2dcfe6c4/partitions/22211ae2-1228-4497-bdbd-d913f933812e/replicas/132415566475158421s/"}],"RegionsContacted":["https://remotime-eastus.documents.azure.com:443/"],"FailedReplicas":[]},{"Id":"Microsoft.Azure.Documents.ServerStoreModel","ElapsedTimeInMs":3401.2183},{"Id":"AddressResolutionStatistics","StartTimeUtc":"2020-08-17T21:32:39.6743060Z","EndTimeUtc":"2020-08-17T21:32:39.9263650Z","ElapsedTimeInMs":252.05900000000003,"TargetEndpoint":"https://remotime-eastus.documents.azure.com//addresses/?$resolveFor=dbs%2fmhwpAA%3d%3d%2fcolls%2fmhwpAJ28n9Q%3d%2fdocs&$filter=protocol eq rntbd&$partitionKeyRangeIds=0"},{"Id":"StoreResponseStatistics","StartTimeUtc":"2020-08-17T21:32:39.6010870Z","ResponseTimeUtc":"2020-08-17T21:32:42.8359020Z","ElapsedTimeInMs":3234.815,"ResourceType":"Document","OperationType":"Batch","LocationEndpoint":"https://remotime-eastus.documents.azure.com:443/","ActivityId":"db273de7-94b4-48a2-9ebc-1a519c5f13fe","StoreResult":"StorePhysicalAddress: rntbd://cdb-ms-prod-eastus1-fd42.documents.azure.com:14063/apps/814e7582-0a8b-498b-8d4f-92263e029030/services/f2d1101a-4d64-4d76-bfa7-e60d2dcfe6c4/partitions/22211ae2-1228-4497-bdbd-d913f933812e/replicas/132415566475158422p/, LSN: 57, GlobalCommittedLsn: 57, PartitionKeyRangeId: , IsValid: True, StatusCode: 403, SubStatusCode: 0, RequestCharge: 0, ItemLSN: -1, SessionToken: -1#57, UsingLocalLSN: False, TransportException: null"},{"Id":"PointOperationStatistics","ActivityId":"db273de7-94b4-48a2-9ebc-1a519c5f13fe","ResponseTimeUtc":"2020-08-17T21:32:43.0081550Z","StatusCode":403,"SubStatusCode":0,"RequestCharge":0.0,"RequestUri":"dbs/remotimedb/colls/UserData","ErrorMessage":"Microsoft.Azure.Documents.ForbiddenException: Message: {\"Errors\":[\"Request is blocked. Please check your authorization token and Cosmos DB account firewall settings.\"]}\nActivityId: db273de7-94b4-48a2-9ebc-1a519c5f13fe, Request URI: /apps/814e7582-0a8b-498b-8d4f-92263e029030/services/f2d1101a-4d64-4d76-bfa7-e60d2dcfe6c4/partitions/22211ae2-1228-4497-bdbd-d913f933812e/replicas/132415566475158422p/, RequestStats: Please see CosmosDiagnostics, SDK: Linux/Unknown cosmos-netstandard-sdk/3.11.4\n  at Microsoft.Azure.Documents.TransportClient.ThrowServerException (System.String resourceAddress, Microsoft.Azure.Documents.StoreResponse storeResponse, System.Uri physicalAddress, System.Guid activityId, Microsoft.Azure.Documents.DocumentServiceRequest request) [0x004d2] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.Rntbd.TransportClient.InvokeStoreAsync (System.Uri physicalAddress, Microsoft.Azure.Documents.ResourceOperation resourceOperation, Microsoft.Azure.Documents.DocumentServiceRequest request) [0x003c8] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.StoreResult.ToResponse (Microsoft.Azure.Documents.RequestChargeTracker requestChargeTracker) [0x0004f] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.ConsistencyWriter.WritePrivateAsync (Microsoft.Azure.Documents.DocumentServiceRequest request, Microsoft.Azure.Documents.TimeoutHelper timeout, System.Boolean forceRefresh) [0x00573] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.BackoffRetryUtility1[T].ExecuteRetryAsync (System.Func1[TResult] callbackMethod, System.Func3[T1,T2,TResult] callShouldRetry, System.Func1[TResult] inBackoffAlternateCallbackMethod, System.TimeSpan minBackoffForInBackoffCallback, System.Threading.CancellationToken cancellationToken, System.Action1[T] preRetryCallback) [0x00096] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying (System.Runtime.ExceptionServices.ExceptionDispatchInfo capturedException) [0x00011] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.BackoffRetryUtility1[T].ExecuteRetryAsync (System.Func1[TResult] callbackMethod, System.Func3[T1,T2,TResult] callShouldRetry, System.Func1[TResult] inBackoffAlternateCallbackMethod, System.TimeSpan minBackoffForInBackoffCallback, System.Threading.CancellationToken cancellationToken, System.Action1[T] preRetryCallback) [0x001bf] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.ConsistencyWriter.WriteAsync (Microsoft.Azure.Documents.DocumentServiceRequest entity, Microsoft.Azure.Documents.TimeoutHelper timeout, System.Boolean forceRefresh, System.Threading.CancellationToken cancellationToken) [0x00102] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.ReplicatedResourceClient+<>c__DisplayClass26_0.<InvokeAsync>b__0 (Microsoft.Azure.Documents.GoneAndRetryRequestRetryPolicyContext contextArguments) [0x00187] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.RequestRetryUtility.ProcessRequestAsync[TRequest,IRetriableResponse] (System.Func1[TResult] executeAsync, System.Func1[TResult] prepareRequest, Microsoft.Azure.Documents.IRequestRetryPolicy2[TRequest,TResponse] policy, System.Threading.CancellationToken cancellationToken, System.Func1[TResult] inBackoffAlternateCallbackMethod, System.Nullable1[T] minBackoffForInBackoffCallback) [0x000df] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying (System.Runtime.ExceptionServices.ExceptionDispatchInfo capturedException) [0x00011] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.RequestRetryUtility.ProcessRequestAsync[TRequest,IRetriableResponse] (System.Func1[TResult] executeAsync, System.Func1[TResult] prepareRequest, Microsoft.Azure.Documents.IRequestRetryPolicy2[TRequest,TResponse] policy, System.Threading.CancellationToken cancellationToken, System.Func1[TResult] inBackoffAlternateCallbackMethod, System.Nullable1[T] minBackoffForInBackoffCallback) [0x0028b] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.StoreClient.ProcessMessageAsync (Microsoft.Azure.Documents.DocumentServiceRequest request, System.Threading.CancellationToken cancellationToken, Microsoft.Azure.Documents.IRetryPolicy retryPolicy, System.Func2[T,TResult] prepareRequestAsyncDelegate) [0x002fd] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Documents.ServerStoreModel.ProcessMessageAsync (Microsoft.Azure.Documents.DocumentServiceRequest request, System.Threading.CancellationToken cancellationToken) [0x00165] in <18285060bc1144e3a326a50b67232825>:0 \n  at Microsoft.Azure.Cosmos.Handlers.TransportHandler.ProcessMessageAsync (Microsoft.Azure.Cosmos.RequestMessage request, System.Threading.CancellationToken cancellationToken) [0x0019d] in <250931dbc7a64174b3f1ed93d3081ffb>:0 \n  at Microsoft.Azure.Cosmos.Handlers.TransportHandler.SendAsync (Microsoft.Azure.Cosmos.RequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00074] in <250931dbc7a64174b3f1ed93d3081ffb>:0 ","RequestSessionToken":null,"ResponseSessionToken":"0:-1#57"},{"Id":"BatchAsyncContainerExecutor.ToResponse","ElapsedTimeInMs":13.0839}]}}

@ealsur do you have any suggestions?

@abhijitpai Does Bulk/Batch require a particular permission on Resource Tokens to execute?

@InquisitorJax Your code, when it creates a Permission, it is creating only for a particular PartitionKey:
var partitionKey = new PartitionKey(permissionId);

				var permissionProperties = new PermissionProperties(
					permissionId,
					PermissionMode.All, //default to all. This should be derived from scope in future
					_container,
					partitionKey);

When you issue Bulk operations, are all within the same PartitionKey?

@ealsur yup - same partition key.
to be clear, the 403 is returned from a single UpsertAsync() call - I hadn't got round to making actual bulk operations yet.
Are bulk operations supposed to run with different container instances?

I was able to repro this in a small snippet
CosmosClient client1 = new CosmosClient("https://localhost:8081", "C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==");

            DatabaseResponse response = await client1.CreateDatabaseIfNotExistsAsync(Guid.NewGuid().ToString());
            Database database = response.Database;

            ContainerResponse containerResponse = await database.CreateContainerAsync(Guid.NewGuid().ToString(), "/pk");
            Container container = containerResponse;

            User user = await database.CreateUserAsync("test");

            PartitionKey partitionKey = new PartitionKey("test");

            PermissionResponse permission = await user.CreatePermissionAsync(new PermissionProperties(
                 "testP",
                    PermissionMode.All,
                    container,
                    partitionKey
            ));

            CosmosClientOptions clientOptions = new CosmosClientOptions();
            clientOptions.AllowBulkExecution = true;
            CosmosClient client = new CosmosClient("https://localhost:8081", permission.Resource.Token, clientOptions);

            Container containerWithPermissions = client.GetContainer(database.Id, container.Id);

            List<Task<ItemResponse<dynamic>>> tasks = new List<Task<ItemResponse<dynamic>>>();
            for (int i = 0; i < 100; i++)
            {
                tasks.Add(containerWithPermissions.CreateItemAsync<dynamic>(new { id = i.ToString(), pk = "test" }, partitionKey));
            }

            await Task.WhenAll(tasks);

Basically the issue is that when Bulk is enabled, the BATCH backend API request seems to be blocked.
When Bulk is off, the SDK does normal point operations (POST) for each operation. When Bulk is on, we group operations and issue them under a different verb (BATCH), and this might be the source of the issue. @abhijitpai is this a supported scenario?

@ealsur does batch work?

TransactionalBatch works.
I think the root cause of the issue is that Permission is scoped to a PartitionKey. But the Bulk request is not scoped to a PartitionKey (does not send the PK header) but to a physical partition.
TransactonalBatch is scoped to a PartitionKey.

If the Permissions is not scoped to a PartitionKey, for example:
PermissionResponse permission = await user.CreatePermissionAsync(new PermissionProperties(
                 "testP",
                    PermissionMode.All,
                    container
            ));

Then it works.

@ealsur is that by design? My expectation is that batch operation permissions also be limited to a partition.
So in my example, partitions are separated by userID - so I wouldn't want user A to receive a token that has bulk operation permissions on user B's data.

Your point is correct, what I'm saying is that the protocol used in this case does not send the PartitionKey header, because technically the Bulk requests could include documents from different Partition Keys that are stored in the same physical partition. Since we don't send the PartitionKey header, even though all documents are for the same PartitionKey, the validation process that happens on the backend side is rejecting the request with a 403, because the Permission is set for a particular PartitionKey (and the request does not have the header).

@ealsur should this be closing? It doesn't look like it's been resolved.
I've just not been using the bulk execution because of this issue.

@ealsur I'm not so sure. The intent (at least for me anyways) isn't to be sure that a batch of operations all pass or fail as one (ie. requiring them to be placed in a single transaction)
My hope was that by turning on AllowBulkExecution flag, it would increase performance of consecutive, independent operations to a partition - unless I'm misunderstanding the intent of the flag?

@InquisitorJax we discussed this scenario through several angles and Bulk in this case might not be the best option. The reason is that limiting Bulk to a single PK Value (not even a full physical partition) is really taking away the biggest improvement Bulk brings (grouping operations by physical partition affinity to reduce network requests) and it's not towards the goal (exhaust available RU on the container) because it's simply impossible to take advantage of all the available RUs by issuing operations for only 1 PK value.

Thanks for the feedback @ealsur - would it then make sense to have an error response that is a little more informative than "forbidden"? I can imagine people making PK scoped permissions, and thinking turning on bulk operations flag will improve performance... would be nice if response error / documentation was clear that this is not a supported scenario by design.

I agree. While we cannot drive backend changes from this repo, we can at least make sure to update linked documentation.
We'll use this issue to track an improvement on the CosmosClientOptions.AllowBulkExecution API to add a <remarks>  section:
https://github.com/Azure/azure-cosmos-dotnet-v3/blob/d7fc28225057ac402a7c862daf7707d08a2f70d3/Microsoft.Azure.Cosmos/src/CosmosClientOptions.cs#L558-L561
@iainx Could you please add such a section on the above area that says something like: "The use of Resource Tokens as an authentication mechanism when Bulk is enabled is not recommended because it reduces the potential throughput benefits by reducing the scope of operations."


Add watch option

I haven't found issue with such request, so Im creating one

I want to bump this issue since there was no activity since 24 Aug and I think that is important.

I use nodemon for watching file changes and run tslint in npm script. One example https://github.com/ryancat/create-ts-library/blob/master/package.json#L9

I would like this feature to be implemented

I've got a fever.  And the only prescript is more --watch.

this is a very hard feature to implement because it likely requires radically rearchitecting to support incremental re-runs so i think the best bet here will be to combine tslint with other existing watcher tools, like nodemon mentioned above or https://www.npmjs.com/package/watch

requires radically rearchitecting to support incremental re-runs

FWIW that does sound very hard, but also more performant than re-running all of tslint on change, as would happen with third-party tools. +1 to this request, along with a healthy side of understanding.

⌚ing this.

My tool actually supports this behaviour, because I understand that it's really hard to implement. https://github.com/guidojo/multipleTypescriptCompilers#readme
The tool currently runs a tsc compiler and after each run, it will lint each file separately. If interrupted by another compilation, it will abort. :)

Using the onchange package works perfectly, many thanks for that suggestion @alexburner. Currently using it for both tslint and stylelint:
{
    "lint": "concurrently \"yarn tslint:once\" \"yarn stylelint:once\" && onchange 'src/**/*.*' -- concurrently \"yarn tslint:once\" \"yarn stylelint:once\"",
    "tslint:once": "tslint -p . -c ./tslint.json --fix './src/**/*.+(ts|tsx)'",
    "stylelint:once": "stylelint --fix **/*.scss",
}

I think the onchange solution is sufficient for CLI use cases. You can use the Node API and implement a watcher on top of that if you want. I'm going to close this because we'd like to focus development efforts elsewhere in TSLint.

I disagree that this should be closed, and should at least stay on the roadmap even if focus is currently elsewhere. Watching seems overly complicated compared to tsc's tsc -w


[RFC] Versions.yaml

Super simple yaml file to document what the default versions currently are for our third party dependencies.
Also included is an example of how this would be used in the Makefile to get the ubuntu image URL and checksum.
Welcome any comments. Thanks.

@jtumber-ibm - It looks pretty good to me so far, albeit not the most user friendly thing, but make to shell normally isn't!. I think we also want the attestation-agent repo in to the versions file as well.
Something that might be worth considering if whether we want to try and follow the template of the kata-containers versions.yaml file https://github.com/kata-containers/kata-containers/blob/CCv0/versions.yaml which has a slightly different format. It's not mandatory, but might be worth aligning with them on it.
I guess the next steps (once everyone is happy with the versions.yaml format) is to start adopting it where we pull in versions at the moment. Is your plan to do that under a separate PR?
Thanks!

@jtumber-ibm the approach looks good. When do you plan to move it out of RFC ?
Eventually the gh-action, Dockerfiles etc can be updated to refer to the versions.yaml to pickup the right versions

@jtumber-ibm the approach looks good. When do you plan to move it out of RFC ?
Eventually the gh-action, Dockerfiles etc can be updated to refer to the versions.yaml to pickup the right versions

Moved out of RFC, if people are happy to stay with this format then we can merge next week?
@bpradipt @yoheiueda @stevenhorsman

Are you planning to pull out the ubuntu/yq usage from this PR altogether and do it separately, so this just has the version.yaml format?
Is there issue(s) that enumerate the follow on tasks after this merged as well?
Thanks!

Are you planning to pull out the ubuntu/yq usage from this PR altogether and do it separately, so this just has the version.yaml format?
Is there issue(s) that enumerate the follow on tasks after this merged as well?
Thanks!

I think that is probably wise

@bpradipt do you have values that can be used for the rhel section?
All, any version changes you'd like to see before being merged?

yes, the rhel image link is dynamically created and there's no static one available ATM AFIAK, let's skip it for now


fix(lsp): preserve backwards compatibility with jump_to_location deprecation

Follow up of #1503 to preserve backwards compatibility with versions 5-9.

Thanks @phanen for catching this!

Ty @phanen & @MariaSolOs!


Can we specifiy indexes?

Nice project, looks promising. Is there (or will there) be a way to specify indexes? Something like what MongoEngine is doing would totally suffice if you want inspiration :)
https://docs.mongoengine.org/guide/defining-documents.html?highlight=index#indexes

Hello Michael,
It is nice to see you here. Thank you for your feedback :-)
This is a very good topic. I plan to add index support soon. I'm thinking about the interface now.

Excellent, excited to hear. Thanks for considering the feature.

Love the inner class style you chose. Nice one.

Thank you! :-)


BERT large training more unstabile than BERT base

I have a question,
I have experienced unstabile training with BERT large compared to BERT Base on the same set up which is intended for BERT large. When training on BERT Large the Loss goes down < 2, but at ~1/4 of training it blows up, while BERT Base does not have this problem. Did you experience similar problems?

Try gradient clip.


Error on multi-master setup

I'm trying to set up multi-master replication between four nodes, but am getting an error on initialization. I'm utilizing the latest Docker image and starting the server from Docker Compose via keydb-server --bind <IP_ADDRESS> --multi-master yes --replicaof key2 6379 --replicaof key3 6379 replicaof key4 6379. All nodes are up and available, and I was able to successfully enable active replication with two nodes without issue. Below is the error message I receive:
1:S 09 Aug 2019 19:24:27.576 * Ready to accept connections
1:S 09 Aug 2019 19:24:27.576   Thread 0 alive.
1:S 09 Aug 2019 19:24:27.576 * Connecting to MASTER key2:6379
1:S 09 Aug 2019 19:24:27.577 * MASTER <-> REPLICA sync started
1:S 09 Aug 2019 19:24:27.577 * Connecting to MASTER key3:6379
1:S 09 Aug 2019 19:24:27.577 * MASTER <-> REPLICA sync started
1:S 09 Aug 2019 19:24:27.577 * Connecting to MASTER key4:6379
1:S 09 Aug 2019 19:24:27.578 * MASTER <-> REPLICA sync started
1:S 09 Aug 2019 19:24:27.578 * Non blocking connect for SYNC fired the event.
1:S 09 Aug 2019 19:24:27.579 * Master replied to PING, replication can continue...
1:S 09 Aug 2019 19:24:27.582 * Partial resynchronization not possible (no cached master)
1:S 09 Aug 2019 19:24:27.583 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master
1:S 09 Aug 2019 19:24:27.632 * Non blocking connect for SYNC fired the event.
1:S 09 Aug 2019 19:24:27.632 * Non blocking connect for SYNC fired the event.
1:S 09 Aug 2019 19:24:27.751 * Master replied to PING, replication can continue...
1:S 09 Aug 2019 19:24:27.751 * Master replied to PING, replication can continue...
1:S 09 Aug 2019 19:24:28.000 * Partial resynchronization not possible (no cached master)
1:S 09 Aug 2019 19:24:28.006 * Trying a partial resynchronization (request add151c95d980866c0e53d0d68537f6bf3fa6223:1).
1:S 09 Aug 2019 19:24:28.090 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master
1:S 09 Aug 2019 19:24:28.093 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master

Update: it looks like I was able to get it working by adding --active-replica yes in addition to --multi-master yes for each of the nodes. Is this intended behavior? If so, could it be added to the documentation?

Multi Master issue
multi master was always intended to be specific with active-replica.  It looks like in the past it "worked" without it but that was never intended to be supported.  I will modify the code to abort if it is specified and active-replica is not also specified.  Eventually when its stable enough it will be allowed by default with active-replica.
Ping delay
This occurs when the remote rdb is being applied.  When this is happening we absolutely don't want any normal commands to run however I don't see why we can't special case PING since it doesn't touch the database.


Animate .notification class (black warning notice)

Should we merge this with #195 ?  The first commit in both is the same and it looks like @yahoopete is trying to fix the same tests.

Hey Murray yeah I branched off of the branch. Thought that was how it was done :(
Help me fix it?

I'm fixing that other branch, so I'll cherry-pick the new commit off here and push it all up on the other branch.


When serving es5 ngx-socket-io gives me error

🐞 bug report
Is this a regression?
From what I remember it didn't worked with angular 9 either
Description
 .
I'm using an old IPad 2 for development and just upgraded to angular 10. I'm using ngx-socket-io but I'm trying to build the project using es5. I followed the guideline for building es5 from here
I notice that angular is using even in es5 the bundle fesm2015 of ngx-socket-io causing this unknown error.
When running ng serve it says compiling  ngx-socket-io : es2015 as esm2015
I needed to use old safari in order to get the debugger working, so finding the precise error is kind of painful.
notice that basic app using ng new projectName is working on my ipad.
I use this command ng serve --aot --configuration es5 --host 192.168.XX.XX
this is my first GitHub Bug report please let me know if I'm doing wrong or at the wrong place
Thanks in advance
🔬 Minimal Reproduction
I wasn't able to reproduce it on stackBlitz but basically you only have to install ngx-socket-io import it on your new project and make ng serve with host value for safari 9
-->

🔥 Exception or Error

🌍  Your Environment
Angular Version:

Safari 9
IOS 9.3.5
Angular 10.0.3

Anything else relevant?

It is normal for ngcc to process the ES2015 version of the library. The ES5 version of the application is created at the end of the build by downleveling the ES2015 version of the app. So the order of things is that your TS code is compiled by Angular/TypeScript, webpack bundles this with the imported 3rd party libraries into ES2015 formatted distributable files, these ES2015 files are downleveled to ES5.
Now I believe that your index.html should be setup to use the ES5 dist files on older browsers, and ES2015 otherwise.
Can you see if ES5 versions are being built if you run ng build --aot --configuration es5?

@petebacondarwin
First of all thanks for your reply.
I think it's E5 version I also get polyfills-es5.jsand  polyfills-es5.js.map builded
I'll test them on a server see if they display properly

@petebacondarwin  I get on a latest safari this error
Uncaught TypeError: "exports" is read-only
    js common.js:266
    js vendor.js:52465
    Webpack 20
common.js:266
    js common.js:266
    js vendor.js:52465
    Webpack 20

I wonder if there is some additional setup that is needed... Perhaps in the browserslist?

@petebacondarwin adding safari 9 to the browserslist doesn't really change something. I'm stuck.

@clydin Just compiled angular-cli with your modification an looks like it's working now. Thanks a lot. Is it possible having a more in depth explanation.
Thanks in advance

Angular CLI 10.0 will now down-level vendor files when targeting ES5 within the application's TypeScript configuration.  Vendor files were previously only down-leveled as a side effect of using differential loading which down-leveled the entire application as a post-processing step.  The debug package contains ES2015 features within the code chosen by the webpack configuration (browser field in the package's package.json).  As a result, prior to Angular CLI 10.0, this package would not work on older browsers except when using differential loading.  With Angular CLI 10.0, the package should now be usable even without using differentia loading on older browsers.  However, the package's code contained ES2015 features (spread operators) that require helper functions to fully down-level.  These need to be referenced (imported/required) within package's code to work.  Before the fix referenced in this issue, the file was assumed to be an ES module but it is actually a commonJS file (it has no require calls but it does assign to module.exports).  As it was assumed to be an ES module, the down-leveling process was adding import statements to the file and not require calls.  Finally, the presence of newly added import statements was in turn causing Webpack to assume that the file was an ES module file and, as a result, processing the file differently than it should.  This different processing was what was breaking the package and causing the runtime error.

@clydin Many thanks


DOM DragEvents not working

I'm working on a GUI that implements dragging and dropping elements around the page to reorder them.
It is working properly on FF97 and actually also on IE11. However it doesn't work on neutron.ahk. While it blocks dragging from outside the window (to be captured by ahk's GuiDropFiles), it shouldn't block DOM DragEvents within the wb.

Here's a gist to test DOM DragDrop  (adapted from MDN)


added image and link generation for showcaseitems

The request returns a link to the generated image in static folder. For example, I took "chain.json" file from "data/mocked_jsons".

Hello @Sash0check! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file app/api/chains/schema.py:

Line 27:1: E302 expected 2 blank lines, found 1


IDF : Allow external projects to override defaults

List of changes:

Revert sdkconfig generation logic, i.e. changes in sdkconfig.defaults are only reflected on fresh build
Allow external projects to specify IDF_SDKCONFIG_DEFAULTS

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

@tgsong This is related to https://github.com/aws/amazon-freertos/issues/832#issuecomment-514751953. The changes are as per solution 1. Let me know what you think.

/bot run checks


config: allow 'verb' to be present multiple times, the last one wins; support tls-version-max; fix tls-cipher/tls-ciphersuites

The tls 1.3 and tls 1.2 ciphersuite names are actually disjoint. In OCaml-tls we have (the non-exported) Config.Ciphers.default13 and Config.Ciphers.default (which is default13 @ [... rest ...]). So, I'm fine with how this is dealt here -- though if we would expose more bindings from OCaml-TLS, we could specify less hardcoded values here :)


Failed host lookup: 'api.openai.com'

Testing on Windows 10.
The function works, a correct answer is returned from Openai, but it keeps throwing this error every time I call the function.
try {
    chatCompletion = await OpenAI.instance.chat.create(

      model: modelName,
      messages: [
          OpenAIChatCompletionChoiceMessageModel(
              content:[
                OpenAIChatCompletionChoiceMessageContentItemModel.text(prompt),
              ],
              role: OpenAIChatMessageRole.user,
          ),
      ]
      maxTokens: maxTokens,
    );
  } catch (e) {
    print("ERROR: $e")  ;
    rethrow;
  }

SocketException: Failed host lookup: 'api.openai.com' (OS Error: Host sconosciuto. , errno = 11001)
OS Error: Host sconosciuto. , errno = 11001

The Catch does not catch anything!
And the function returns a correct answer from Openai!

This is likely to be related to this issue


No mention of having to change the link to specific region when logging into IBM Cloud

<!-- Feel free to remove sections that aren't relevant.

## Title line template: [Title]: Brief description

No mention of having to change the link to specific region when logging into IBM Cloud

## Detailed description

> I followed the link provided in step 5 of the tutorial for logging into IBM cloud (when deploying). After spending some time trying to work out why it kept returning 'cf target -o ORG -s SPACE', it was realised that the regions in the URLs didn't match up so had the change them. It then worked.

Although it eventually worked so it isn't a bug as such, it would be good to mention this in the tutorial for those of us in the UK and other areas outside the US.

## Steps to reproduce the issue

1. Step one
Follow '$ cf login -a https://api.ng.bluemix.net -sso'
And login from a UK based computer
2. Step two
Recieve: No org or space targeted, use 'cf target -o ORG -s SPACE'

This was the message I recieved

After changing it to 'https://api.eu-gb.bluemix.net', it worked.

Great! Thank you @Charlotte8699


Crash when saving project in linux

Hi,
Saving a project on linux (tested in Ubuntu 19.10 with Qt 5.13) crashes. That's because the file dialog does not automatically adds the extension. I had the same problem for my own tool. I made a possible workarround here:
void MainWindow::on_actionSaveAs_triggered() {
    QSettings settings;
    QString dir;
    if (!_currentProjectFileName.isEmpty()) {
        dir = _currentProjectFileName;
    } else {
        dir = settings.value("spritePackerFileName", QDir::currentPath()).toString();
    }
    QString fileName = QFileDialog::getSaveFileName(this, tr("Save sprite packer project file."),
                                                    dir,
                                                    tr("Sprite sheet packer (*.ssp)"));
    if (!fileName.isEmpty()) {
        if (!fileName.endsWith(".ssp")) {
            fileName.append(".ssp");
        }
        settings.setValue("spritePackerFileName", fileName);
        saveSpritePackerProject(fileName);
    }
}

Just added a verification that if the correct suffix is not added to the filename when saving, add it by default.
I'll make a PR if that way suits your guidelines!

Yes of course! Thank you for improving the project:)


Ubuntu image update causes Kudu and node app to break when using azure cli for App Service setup

Description
Our very simple node app (image conversion service based on nextJS) started responding with HTTP 500 server error and Kudu for the related Azure app service stopped working after ubuntu image was updated  to have powershell 7.4. It seems to me there is a backwards compatibility issue in powershell 7.4 over 7.2. I verified that powershell script from gist shared in steps.
It seems that the script compatibility between windows and ubuntu powershell suddenly broke on Powershell 7.4.
I know this should likely be reported as powershell issue, but we need to mitigate it also in Azure DevOps and if this is actually a bug in powershell we need to follow up on when it is fixed in Azure DevOps images.
Did not create powershell issue regarding this yet.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240201.1/images/ubuntu/Ubuntu2204-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240201.1
Is it regression?
yes
Expected behavior
Kudu can be used and node app server requests without issues.
Actual behavior
Kudu fails with exception.

Server Error in '/' Application.

Illegal characters in path.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Illegal characters in path.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ArgumentException: Illegal characters in path.] System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional) +14607857 System.IO.Path.Combine(String path1, String path2, String path3, String path4) +89 Kudu.Core.Infrastructure.PathWindowsUtility.IsNodeVersionInstalled(String version) in C:\Kudu Files\Private\src\master\Kudu.Core\Infrastructure\PathUtils\PathWindowsUtility.cs:336 Kudu.Core.Infrastructure.PathWindowsUtility.ResolveNodeVersion(Boolean& fromAppSetting) in C:\Kudu Files\Private\src\master\Kudu.Core\Infrastructure\PathUtils\PathWindowsUtility.cs:292 Kudu.Core.Infrastructure.PathWindowsUtility.ResolveNodeNpmPaths() in C:\Kudu Files\Private\src\master\Kudu.Core\Infrastructure\PathUtils\PathWindowsUtility.cs:343 Kudu.Core.Infrastructure.PathUtilityBase.GetPathFolders(IEnvironment environment) in C:\Kudu Files\Private\src\master\Kudu.Core\Infrastructure\PathUtils\PathUtilityBase.cs:34 Kudu.Services.Web.App_Start.NinjectServices.PrependFoldersToPath(IEnvironment environment) in C:\Kudu Files\Private\src\master\Kudu.Services.Web\App_Start\NinjectServices.cs:835 Kudu.Services.Web.App_Start.NinjectServices.RegisterServices(IKernel kernel) in C:\Kudu Files\Private\src\master\Kudu.Services.Web\App_Start\NinjectServices.cs:160 Kudu.Services.Web.App_Start.NinjectServices.CreateKernel() in C:\Kudu Files\Private\src\master\Kudu.Services.Web\App_Start\NinjectServices.cs:132 Ninject.Web.Common.Bootstrapper.Initialize(Func1 createKernelCallback) +23 Kudu.Services.Web.App_Start.NinjectServices.Start() in C:\Kudu Files\Private\src\master\Kudu.Services.Web\App_Start\NinjectServices.cs:97 [TargetInvocationException: Exception has been thrown by the target of an invocation.] System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) +0 System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) +269 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +146 WebActivatorEx.BaseActivationMethodAttribute.InvokeMethod() +81 WebActivatorEx.ActivationManager.RunActivationMethods(Boolean designerMode) +708 WebActivatorEx.ActivationManager.Run() +132 [InvalidOperationException: The pre-application start initialization method Run on type WebActivatorEx.ActivationManager threw an exception with the following error message: Exception has been thrown by the target of an invocation..] System.Web.Compilation.BuildManager.InvokePreStartInitMethodsCore(ICollection1 methods, Func1 setHostingEnvironmentCultures) +890 System.Web.Compilation.BuildManager.InvokePreStartInitMethods(ICollection1 methods) +167 System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) +133 System.Web.Compilation.BuildManager.ExecutePreAppStart() +178 System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +746 [HttpException (0x80004005): The pre-application start initialization method Run on type WebActivatorEx.ActivationManager threw an exception with the following error message: Exception has been thrown by the target of an invocation..] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +552 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +122 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +737
Repro steps
Option 1:

Create Azure resource group and Azure App Service Plan in Azure CLI:

az group create -g my-rg-kudu-error-test -l westeurope
az appservice plan create -n my-asp-kudu-error-test -g my-rg-kudu-error-test --sku S1

Run PS1 script from this gist in windows to create the webapp with node runtime env, with latest Azure CLI (2.56.0) and latest powershell (7.4.1):
https://gist.github.com/aviita/b235133e40a55e6ab53b95edf75da907/edit
Test kudu site for the deployed app:
https://my-app-kudu-error-test.scm.azurewebsites.net
Run the same ps script from gist from ubuntu 22.04 with powershell 7.4 and Azure cli 2.56.0.
Test kudu site for the deployed app:
https://my-app-kudu-error-test.scm.azurewebsites.net

Expected:

Kudu site works after each step

Actual:

Kudu site works after step 3, but not after step 4.

Following command shows config value "~18" for config WEBSITE_NODE_DEFAULT_VERSION after step 3.
az webapp config appsettings list -n my-app-kudu-error-test -g my-asp-kudu-error-test
After step 5 it shows value "\"~18\"" and kudu fails with exception.

Hey! Have you checked that the downgrade path described here makes your workflow functional again?

Hey! Have you checked that the downgrade path described here makes your workflow functional again?

Thanks for linking this. I was planning to check for workaround next. For now I just disabled this part of our pipeline.

Hey, thanks for the feedback, if you see that the problem is not in pwsh update, feel free to report the problem back, closing it for now as nothing actable from our side can be done at the moment.


Allow callers to set omit_owner_reference option

All the plumbing is there to omit the owner references but the pool won't start if you pass that option because the Keyword.validate fails

Released in v0.5.7


[fix] skip test broken by snowflake

Snowflake appears to have changed something which is now causing this
test to fail. Skipping it for now while I find someone who can address
the problem.
cc @henriblancke  and @chriskuchin  who worked on this originally. Any chance one of you could look at this?
Test Plan

[ ] acceptance tests

References

https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/196

Codecov Report

Merging #239 into master will decrease coverage by 3.65%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #239      +/-   ##
==========================================
- Coverage   65.81%   62.16%   -3.66%
==========================================
  Files          50       50
  Lines        3698     3698
==========================================
- Hits         2434     2299     -135
- Misses        937     1097     +160
+ Partials      327      302      -25

Impacted Files
Coverage Δ

pkg/resources/task.go
25.06% <0.00%> (-37.61%)
:arrow_down:

Continue to review full report at Codecov.

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

@ryanking I will see if i can find some time in the next couple of days to poke at it


Fix trace message to use 'kill' rather than 'destroy' for kill_process

Trivial change to trace message to contain the correct message name.

Windows Build 1111 is now running using a merge of 1c21fcda48f9bc06dd72db8fefc999e517832acc

Linux Build 1452 is now running using a merge of 1c21fcda48f9bc06dd72db8fefc999e517832acc

Core - Full Integration Build 713 is now running using a merge of 1c21fcda48f9bc06dd72db8fefc999e517832acc

Windows Build 1111 outcome was SUCCESS using a merge of 1c21fcda48f9bc06dd72db8fefc999e517832acc
Summary: Tests passed: 3076, ignored: 65 Build time: 0:18:57

Linux Build 1452 outcome was SUCCESS using a merge of 1c21fcda48f9bc06dd72db8fefc999e517832acc
Summary: Tests passed: 3076, ignored: 65 Build time: 0:22:35

Core - Full Integration Build 713 outcome was SUCCESS using a merge of 1c21fcda48f9bc06dd72db8fefc999e517832acc
Summary: Tests passed: 2833, ignored: 412 Build time: 0:51:41


Use `UpdateAllowUnknown' for non-model related parameter.

Model parameter can not pack an additional boolean value due to binary IO
format.  This commit deals only with non-model related parameter configuration.

Is there a problem that you see only in the test farm?

@hcho3 It should be fixed now.  Let's see if the tests pass.

@hcho3 I thing I didn't think of, is clang-tidy doesn't understand static initialization of dmlc::Parameter.  It believes that the entry_map_ in parameter manager is empty so uses of it might trigger a clang-tidy error.

@hcho3 Done.

@RAMitchell Not sure about this.  We can discuss it after having model parameter (these are runtime parameters).

@hcho3 I added a use-dmlc-gtest option and set it to default.  The naming is consistent with our CMake parameter.

Now I see the problem on Jenkins...

@trivialfis Let's enable bundled gtest for CI tasks.

@hcho3 Done.


Automate style checking

To start with I have done minimal cleanup.
Eventually we should aim to address all the warnings and possibly raise the rule severity so the build fails if any of these issues are reintroduced.
We could optionally expand the checks to include test code.
@alice PTAL
.eslintrc configures the rules. 0 turns a rule off, 1 raises a warning, 2 raises an error.
Rules listed at http://eslint.org/docs/rules/ which links to detailed documentation.
Closes #216.

:+1: I'm going to pull this right now, amazing


Hydrogen improvements

Modelling of hydrogen supply, demand and storage has been improved. Summarised:

A break down in must-run and dispatchable plants of the hydrogen supply technologies ATR, SMR and ammonia reforming
Possibility to change the merit order of dispatchable hydrogen production and demand
Modelling of hydrogen storage is improved by adding salt cavern and depleted gas field technologies and allowing the user to set installed volume and relative capacity.
Changes in hydrogen transport assumptions and modelling
New charts: "Installed storage volume per carrier" and "Flexible hydrogen supply and demand per hour"

Changes applied in this repo specifically are (summarised):

Updating charts and tables with new hydrogen storage and must-run / dispatchable hydrogen production nodes
Added new charts
Added sliders and accompanying descriptions for hydrogen storage and must-run/dispatchable hydrogen production nodes
Added sections for merit order of dispatchable hydrogen production and demand
Updated what's new page

Goes with:

https://github.com/quintel/etsource/pull/3021
https://github.com/quintel/etmodel/pull/4223
https://github.com/quintel/documentation/pull/175
https://github.com/quintel/etdataset/pull/994
https://github.com/quintel/atlas/pull/166
https://github.com/quintel/etengine/pull/1421

The new costs export for hydrogen has been added to the "hourly curves for hydrogen". There still remains an untitled slide however that should be removed: see the screenshot below.

The "Hydrogen integral costs" data-export does not seem to be working. When I click it I get the following error message:
No route matches [GET] "/api/v3/scenarios/curves/hydrogen_integral_cost.csv"

The yearly energy flow Sankey is no longer working. When I click download, I get the following error:
(<unknown>): did not find expected '-' indicator while parsing a block collection at line 103 column 3

The "Hydrogen production" slide is quite long. I would suggest to shorten it. At least the opening texts listing the production technologies could be removed in my opinion, as these are outdated (some are missing) and they should be obvious from the sliders below.

A similar question for the storage slide: can we shorten it a bit? At least the comment about costs of storage could in my opinion be moved to the slider description of both storage types.


NULL pointer checks before OpenSSL free functions

The main idea is that this functions already have such checks. If we remove this checks we can increase performance and code quality.
I talk about such funtions as:
EVP_PKEY_CTX_free
EVP_MD_CTX_destroy

Mb there are some other functions that I missed.

@outspace sorry, your train of thoughts is a bit unclear.
Could you please provide more details & examples of "such checks"? It will help to see line numbers and suggestions like "here what you have" vs "here what i suggest to have".

Ex:
https://github.com/cossacklabs/themis/blob/3369780dc6449bb636060733e43d60a893843051/src/soter/boringssl/soter_rsa_key_pair_gen.c#L76-L79
In this code we checked for NULL ctx->pkey_ctx and then call EVP_PKEY_CTX_free.
Then we goto code of EVP_PKEY_CTX_free:
https://github.com/openssl/openssl/blob/e7fb44e7c3f7a37ff83a6b69ba51a738e549bf5c/crypto/evp/pmeth_lib.c#L430-L431
As we can see it already have this check and first check is redundant.

In general, I think that more than half NULL pointer checks in this library is redundant. This checks is deepest and It will be good idea to start from them.

Well... yeah. It’s a good design of deallocation functions in C to be a no-op for NULL values. This allows to call them unconditionally for zero-initialized values and get correct behavior. It’s useful in error paths, like here:
https://github.com/cossacklabs/themis/blob/10b8ced317d8a71d1d2f1d0a2eaa29700bcf87df/src/soter/openssl/soter_asym_ka.c#L74-L79
where we can just call them without any prior checks, even if pkey is NULL.
On the other hand, runtime null checks are relatively cheap so I think it’s okay to trade that for confidence that we don’t dereference NULLs, even if some of the checks are redundant. Given that it does not impact correctness or performance in a significant way, I’d give it a low priority, but I’d definitely support an effort to get rid of the redundant checks (wink-wink, nudge-nudge, patches are welcome)
Even better, I think the best approach would be to use some annotation for variables like __attribute__((nonnull)) coupled with static code analysis that catches redundant null checks. This explicitly tells the reader that the pointer should not contain null values and hence we don’t have to check for that. (And if we do, compilers will output a warning about the dead code.) We could use that for internal functions where we can be sure that we have checked for null before.

If we remove this checks we can increase performance and code quality.
how it will increase code quality?
we check null pointers in our library to not depend from the third-party library and avoid monitoring how third-party library is implemented and was it changed in the last update. we consciously check null pointers on our side. especially if it's cheap
removing some cmp instructions from code will not increase performance that will matter
so my vote is to leave it as-is and close issue

runtime null checks are relatively cheap so I think it’s okay to trade that for confidence that we don’t dereference NULLs, even if some of the checks are redundant

+1.
We can't be responsible for all changes in OpenSSL/BoringSSL code, where they may remove some checks. Themis takes care on memory management on its side. Better to have double NULL checks, than to miss one.

Even better, I think the best approach would be to use some annotation for variables like __attribute__((nonnull)) coupled with static code analysis that catches redundant null checks.

This makes more sense to me. That's low priority for now, we'll put this into backlog, but PRs are welcome.
In a long run, I don't think that removing redundant checks will increase performance drastically, but will worsen maintainability Themis. "Code quality" is not measured by minimum lines of code, it's a fragile balance between readability, predictability, stability, performance and maintainability.

We can't be responsible for all changes in OpenSSL/BoringSSL code, where they may remove some checks. Themis takes care on memory management on its side. Better to have double NULL checks, than to miss one.

OpenSSL is strongly based on this approach and I don't think that it would be changed ever (at least they need to rewrite all library).

removing some cmp instructions from code will not increase performance that will matter
so my vote is to leave it as-is and close issue

It would be ok to hear it from people who writing regular programs but not from people who writing low level crypto library wheare every call is metter.

"Code quality" is not measured by minimum lines of code, it's a fragile balance between readability, predictability, stability, performance and maintainability.

To my mind good code is code that based on some approach and simple to understand. It should not be places like same time we make this check same time not.


Update translations

This pull request was created automatically. Please check new translations, approve and deliver them.

Full translations onboarding will be done in separate PR.

Successfully tested locally using Accept-Language header (temporary multi-lang implementation).
Danish, da

French, fr

Spanish Mexican, es-MX


[RFC] Run integration tests

An early attempt to fix #717 for comment & to see what Travis & Appveyor make of it.
This currently assumes that the integration tests pass iff they are compilable and return 0 when run, so that make doesn't stop. That's valid for most of the integration tests we currently have under minimal-cases, but doesn't test finalisers as pointed out in #717.
To do

DONE resolve how to run finaliser and similar tests
DONE fix problem with issue-629 test (can't find Buffer during compilation iirc)
check with authors' that just being able to run the non-finaliser tests is sufficient to show that the test is passing (eg no output needs parsing)
if approach is liked, rename test-minimals to test-integration
run the tests that can be on Windows

Need help with

figuring out a more minimal test case for issue-629 that ideally doesn't require making https requests

Travis logs show that minimal-cases tests are successfully wired into test-ci

@georgemarrows FYI: we have a "DO NOT MERGE" tag that we use to indicate that a PR shouldn't be merged. I've added it to this PR.

If anyone has any input on whether this approach is a good one, I'd be happy to hear it!
I also need help with figuring out a more minimal test case for issue-629 that ideally doesn't require making https requests. I can't get the current test to crash even when take Pony back to just before Sean's #637 fix.
Up next: review tests to try to determine if error code alone is enough to show that their working

Thanks Benoit. I'll close this PR and look at the minimal cases with a view to moving them to badpony.cc or similar. Plan will be to review each one to make sure test case fails before fix was merged and then add a badpony.cc or similar test in its own PR. If I can't get it to fail, I'll do a PR which simply deletes the test with a RFC from the original committer.

@georgemarrows Thank you for working on this!


huntr.dev - Command Injection

This issue has been generated on-behalf of Mik317 (https://huntr.dev/app/users/Mik317)
Vulnerability Description
Affected versions execute arbitrary commands remotely inside the victim's PC. The issue occurs because user input is formatted inside a command that will be executed without any checks. The issue arises here: https://github.com/forsigner/node-pngdefry/blob/master/lib/index.js#L54
Bug Bounty
We have opened up a bounty for this issue on our bug bounty platform. Want to solve this vulnerability and get rewarded 💰? Go to https://huntr.dev/

Bug Bounty
We have opened up a bounty for this issue on our bug bounty platform. Want to solve this vulnerability? Go to https://huntr.dev/
We will submit a pull request directly to your repository with the fix as soon as possible. Want to learn more? Go to https://github.com/418sec/huntr 📚
Automatically generated by @huntr-helper...


Finish snark test dev

develop branch version of https://github.com/MinaProtocol/mina/pull/13085

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me