Git ignores .gitattributes EOL settings

Your Windows build number:  Microsoft Windows [Version 10.0.17134.112]

Related SO question with in-depth explanation and sample setup (if necessary, I can copy the whole thing here as well)

What you're doing and what's happening:  Attempting to configure EOL settings for git via .gitattributes fails. Git seems to ignore .gitattributes completely, relying instead exclusively on what is specified in the global configuration (e.g., changing core.eol).

What's wrong / what should be happening instead: git correctly follows the EOL settings specified via attributes.

It isn't clear (to me) what might be going wrong with your setup. You might try pushing a github repo with two files, wincrlfeol.txt and lxlfeol.txt  along with your .gitattributes. Then provide a set of CLI steps to reproduce the problem, starting with:
$ git clone https://github.com/GPhilo/wsl_git_test.git
$ cd wsl_git_test
$ # ....steps
$ git add -A

"Steps" here might mean mucking with one of those files using printf(1) with "\r\n" or cat(1). Or use dos2unix(1) maybe. I'll take a look, but there is a high degree of probability your scenario is linux-behavior (with the usual caveat that anything is possible). WSL doesn't know you are running git and just follows the syscalls git is feeding the kernel.

Setting up the test environment I found the problem, had to do with formatting of the .gitattributes file.
Once fixed that, git works as expected


Changing example IPs to use private address ranges.

Documentation and examples should not be using public IP ranges, they
should be using private IPs as people using the examples will not have
access/own the listed public IP addresses.

Thanks


Fastboot support

Looks like we're starting two percy builds and finishing once, due to recent changes in the way an ember "fastboot build" is created
# was
ember fastboot:build
# is now
ember build

Guards:
// node land
EMBER_CLI_FASTBOOT === 'true' // in fastboot mode
// browser land
typeof FastBoot === 'undefined' // not in fastboot mode

Thanks @mike-north for this and for the chat!
For reference, I cannot reproduce the fastboot double-build behavior we were seeing at all. Here is an ember-percy test run, with ember-cli-fastboot 1.0.0-beta.4, without the process.env. EMBER_CLI_FASTBOOT check we added, and everything works fine:
https://travis-ci.org/percy/ember-percy/jobs/145164369

Closing stale issue.


Open for non-cross platform libraries?

I'm wondering whether Home Assistant would be open to libraries that are not available for all platforms.
I'd like to try building something for Nuimo remote controller which has a BLE GATT interface. Unfortunately I couldn't find libraries for Python that offer mac or windows support (they all seem to use BlueZ). I also dislike that, but I could live with it as long as I run HA on a Raspberry.
One library I'm looking at is https://bitbucket.org/OscarAcena/pygattlib/overview.
Another way to work around this would be e.g. setting up a node-based daemon using noble and make API calls from that daemon to HA and back. That would be cross-platform but I'm not sure that it would be maintainable...
What do you think?

We already have RPi GPIO which is non cross platform so go ahead
On Sat, Jan 16, 2016, 15:14 wind-rider<EMAIL_ADDRESS>wrote:

I'm wondering whether Home Assistant would be open to libraries that are
not available for all platforms.
I'd like to try building something for Nuimo remote controller
http://www.senic.com which has a BLE GATT interface](
https://senic.com/files/pdf/nuimo-gatt-profile.pdf). Unfortunately I
couldn't find libraries for Python that offer mac or windows support (they
all seem to use BlueZ). I also dislike that, but I could live with it as
long as I run HA on a Raspberry.
One library I'm looking at is
https://bitbucket.org/OscarAcena/pygattlib/overview.
Another way to work around this would be e.g. setting up a node-based
daemon using noble https://github.com/sandeepmistry/noble and make API
calls from that daemon to HA and back. That would be cross-platform but I'm
not sure that it would be maintainable...
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/915.

Ok, thanks. I'll look into it when my device arrives.


Fixes #180: Signature validation will error if empty signature is pro…

…vided

There might be some discussion as to whether or not the cert property should be required.  This pull request seems to address the main concern, without enforcing a breaking api change.

I agree about the problem, but not about the solution.
It could be helpful to validate that cert is not an empty string.
However this issue is a programmer error that could be caught earlier. So:

The error handling should be in SAML.prototype.intialize, where cert is set. It could throw immediately if cert is an empty string.
It's wrong to declare this an "Invalid Signature", because that's not the issue. A more helpful error message would be "cert: private key must not be empty".

I would argue throwing an error would be a breaking API change

In this case, it seems more like we would be fixing a "Garbage-In Garbage Out" bug.  In what context would setting cert to an empty string even make sense?   However, I was thinking of bumping the version to 1.0 very soon anyway.
Your refinements to the error message seem fine. For context, until recently we had 4 to 6 places in the code that returned the same "Invalid Signature" error, which was maddening to debug. Now all those places return unique error messages instead.
I don't want to optimize for developers are passing programmer-errors back to users. In my view, code that sets "cert" to empty string without validating it should not making to production.
Even if a developer is getting the 'cert' value dynamically, they have a responsibility to validate it and not blindly assuming it's OK.

Got it.  Sounds good I will move the validation to the initialize method.  👍

@andrsnn I see this is the last outstanding PR that is tagged for our 1.0 release. Do you think you'll be able to clean it up so it can make that release?

@cjbarth Thank you for the reminder! I will look at wrapping up these changes this coming weekend.

@markstos @cjbarth Just pushed the above changes here.  The above should also support an unsigned SAML Response with an unsigned Assertion, no signatures so no public key necessary.  Any issues or comments let me know and I will address thanks!

This has been merged locally: https://github.com/bergie/passport-saml/commits/master  So, closing this issue.  Thanks for the contribution.


The pipeline should never fail because of file conflicts when pushing files to remote

Describe the issue or request
In regen pipeline or the publish pipeline, the pipeline generates libraries in batches.
In some cases, we update the generator and there are changes in those "common" libraries, which get changed when we generate other libraries. This leads a situation that two steps are changing the same files and this causes a git push failure.
The pipeline should not have this error because the generated result is deterministic - which is the fundamental principal that we could separate this process into several steps.
A simple rebase or merge before we do the git push should do the trick. If this rebase or merge fails, it indicates that two different steps are changing the same file in a different way which breaks the deterministic of our generator, if this happens, it makes a lot of sense to fail.
An example of this: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3243030&view=results

We now force push to the same branch therefore this issue no longer exists.


possible to use header to set username ?

I would like to use a header from nginx proxy to set the $:/status/UserName.
I have nginx setup like this:
upstream websocket {
    server tiddlywiki:8080;
}
server {
    listen       80;
    listen  [::]:80;
    server_name  localhost;
    location / {
        auth_basic "Login";
        auth_basic_user_file /etc/nginx/.htpasswd;
        proxy_pass http://websocket;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_set_header Host $host;
        proxy_set_header X-BasicAuth-RemoteUser $remote_user;
    }
}

Importantly these lines:
        auth_basic "Login";
        auth_basic_user_file /etc/nginx/.htpasswd;
        proxy_set_header X-BasicAuth-RemoteUser $remote_user;

I tried like to run node tiddlywiki with the authenticated-user-header option, as described here:
https://tiddlywiki.com/static/WebServer%2520Parameter%253A%2520authenticated-user-header.html
Something like this:
node tiddlywiki --wsserver authenticated-user-header=X-RemoteUser

But that doesn't seem to do anything.
I'm looking for advise on if this is possible, if so then I would also be grateful for a gentle push in the right direction.

I am running:

[ ] Windows
[ x] OSX
[ ] Linux
[ ] Other

and using

[ x] The nodejs version
[ ] The single file executable

Before posting I read issue guidelines and:

[ x] I am using the newest version
[ x] The answer to my question isn't listed in the documentation or this isn't
a question
[ x] This is not a duplicate issue
[ x] I have not done anything that required me to set acceptance to
I Will Not Get Tech Support For This

I added something like this in ws-server.js, and I can get the header value.  How can I write it to a tiddler?
            const header = self.get("authenticatedUserHeader") ? self.get("authenticatedUserHeader").toLowerCase() : undefined;
            if(request.headers['X-BasicAuth-RemoteUser']) {
                console.log("set state.authenticatedUsername to "+request.headers[request.headers['X-BasicAuth-RemoteUser']]);

                // what can i do here to write to the tiddler ? - this doesn't work...
                self.wiki.addTiddler({
                    title: "$:/status/UserName",
                    text: request.headers[header]});

                //state.authenticatedUsername = request.headers[header];
            }

I got it working with a change to get-status.js:
...
exports.handler = function(request,response,state) {
   ...
  const header = 'X-BasicAuth-RemoteUser'.toLowerCase();
  const username = header && request.headers[header] ? request.headers[header] : '';

  const status = {
    ...
    username: username,
    ...
  }
  ...
}

}());


The program wont launch, not even the basic original versions

It just wont open any versions i tried, all i can get is this, which flashes on my screen for like a second and then closes.

are you extracting it?

i am, and just now i realized when i dont extract it, it works, thanks for the reply anyways, feel free to close this thank you

thats weird something on your pc might be blocking it , using it inside archive is not recommended


Add grid uri (master uri) to grid show output

This will make users life easier when setting up nodes/agents.

yes, we need this! +1


[6.x] Float database types fix

At the moment it's impossible to change unsigned float/decimal columns to signed using Laravel Blueprint methods. This change fixes the problem
This is alternative implementation to https://github.com/laravel/framework/pull/30890 where signature of methods was updated.
For consitency same change was done for double however it's impossible to update double colum out of the box using doctribe/dbal.
Proof of problem:
1st migration:
Schema::create('users', function (Blueprint $table) {
    $table->bigIncrements('id');
    $table->integer('a')->unsigned();
    $table->float('b')->unsigned();
    $table->decimal('d')->unsigned();
});

2nd migration:
Schema::table('users', function (Blueprint $table) {
    $table->integer('a')->change();
    $table->float('b')->change();
    $table->decimal('d')->change();
});

Run first migration and then run migrate --pretend as a result you get:
ALTER TABLE users CHANGE a a INT NOT NULL, CHANGE b b DOUBLE PRECISION UNSIGNED NOT NULL, CHANGE d d NUMERIC(8, 2) UNSIGNED NOT NULL

As you see integer column was changed to signed, however float and decimal weren't. After fix result of this is:
ALTER TABLE users CHANGE a a INT NOT NULL, CHANGE b b DOUBLE PRECISION NOT NULL, CHANGE d d NUMERIC(8, 2) NOT NULL

as expected.

Thanks for the PR. I think this would probably have to go to 7.x, instead of 6.x, since it's a breaking change.

Is it not a bug fix? When we have columns in database and don't use unsigned when altering them they should not be unsigned anymore.


Context sensitive actions

Performing actions on context sensitive elements
This feature adds support for performing actions on context sensitive elements. This is now supported through the following DSL:
I <click|check|uncheck> <element> of <context>
For example, say you wanted to click an action button in a menu item that only becomes visible when you physically move into the menu item by hovering over it with the mouse. You can now do this as follows:
# define locators for the menu item and action button (as you normally would)
Given the menu item can be located by id "menu-item-id"
  And the action button can be located by id "action-button-id"

# then move into the menu item and click the action button
When I click the action button of the menu item

:+1:


Recipe input parameters

Overview of roadmap item
Enhancements for Recipe input parameters.
Related issues
### Related issues
- [ ] https://github.com/radius-project/radius/issues/5020

Additional context

closed given that this is not a roadmap feature item but rather an engineering enhancement.


chore: use subset of ethers Signer class

Use type-only import (e.g. import type) to import Signer from ethers. This will avoid pulling in the entire Signer class and its dependencies at compile time.
Add MinimalEthersSigner that only contains the class we care about.

closes #715


About the Derivation of Variational Lower Bound in Appendix A

I read the derivation you provided in appendix A, but I don't know how the last approximation is obtained, I hope to get your answer, thank you very much

It is very crude monte carlo approximation with sampling size 1 for z_x ~ q(z_x|x,c).

Thank you for your answer, I still don't understand something. Regarding the lower bound of the evidence derived in the paper, the coefficients in front of the KL divergence are all -1, why in the code, their coefficients become 0.1. Looking forward to your answer, thank you

Hi, sorry for the late reply.
If the coefficient is larger than -1 (beta=1 in the code), we cannot guarantee that it is lower bound of the marginal likelihood. But if we put the coefficient smaller than -1, we observe the posterior collapse. So, following [beta-vae],(https://openreview.net/forum?id=Sy2fzU9gl) we scale down the kl-divergence for training stability.


Added consume

Codecov Report

Merging #20 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #20      +/-   ##
=========================================
+ Coverage    99.8%   99.8%   +<.01%
=========================================
  Files           1       1
  Lines         502     504       +2
=========================================
+ Hits          501     503       +2
  Misses          1       1

Impacted Files
Coverage Δ

dist/karet.util.cjs.js
99.8% <0%> (ø)
:arrow_up:

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 d0aec3e...b7041e5. Read the comment docs.


GIT

Type: Bug
git want me to allow them to make extension on my computer, and the window kep popping on my screen
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.78GB (5.14GB free)

Process Argv
--crash-reporter-id 6c6c3a1a-ddf7-411c-b382-beaec5a2b2f8

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

cmake-tools
ms-
1.17.16

cpptools
ms-
1.19.4

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyonecf:30548226
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30968132
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
d34g3935:30971562
edj9j583:30969295
7j2b6412:30969109
ccp2r6:30958158

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[Impeller] FragmentShader are not working on macOS with Impeller enabled

Is there an existing issue for this?

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

Steps to reproduce

checkout https://github.com/flutter/samples/tree/main/simple_shader
flutter pub get
flutter run -d macos --enable-impeller

Expected results
A blue shadow
Actual results
A black screen with these errors:
[ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not register dynamic stage library: program_source:3:8: error: program scope variable must reside in constant address space
float4 flutter_FragCoord;
       ^
program_source:5:1: error: unknown type name 'uniform'
uniform vec2 resolution;
^
program_source:5:13: error: expected ';' after top level declarator
uniform vec2 resolution;
            ^
            ;
program_source:7:1: error: unknown type name 'vec4'
vec4 fragColor;
^
program_source:9:1: error: unknown type name 'vec3'
vec3 flutterBlue;
^
program_source:10:1: error: unknown type name 'vec3'
vec3 flutterNavy;
^
program_source:11:1: error: unknown type name 'vec3'
vec3 flutterSky;
^
program_source:13:1: error: unknown type name 'vec2'
vec2 FLT_flutter_local_FlutterFragCoord()
^
program_source:20:19: error: use of undeclared identifier 'vec3'
    flutterBlue = vec3(0.01960784383118152618408203125, 0.3254902064800262451171875, 0.69411766529083251953125);
                  ^
program_source:21:19: error: use of undeclared identifier 'vec3'
    flutterNavy = vec3(0.01568627543747425079345703125, 0.16862745583057403564453125, 0.3490196168422698974609375);
                  ^
program_source:22:18: error: use of undeclared identifier 'vec3'
    flutterSky = vec3(0.007843137718737125396728515625, 0.4901960790157318115234375, 0.99215686321258544921875);
                 ^
program_source:24:5: error: use of undeclared identifier 'vec3'; did you mean 'vec2'?
    vec3 color = vec3(0.0);
    ^~~~
    vec2
program_source:5:9: note: 'vec2' declared here
uniform vec2 resolution;
        ^
program_source:25:5: error: use of undeclared identifier 'vec3'; did you mean 'vec2'?
    vec3 percent = vec3((st.x + st.y) / 2.0);
    ^~~~
    vec2
program_source:5:9: note: 'vec2' declared here
uniform vec2 resolution;
        ^
program_source:26:5: error: use of undeclared identifier 'color'
    color = mix(mix(flutterSky, flutterBlue, percent * 2.0), mix(flutterBlue, flutterNavy, (percent * 2.0) - vec3(1.0)), step(vec3(0.5), percent));
    ^
program_source:26:46: error: use of undeclared identifier 'percent'
    color = mix(mix(flutterSky, flutterBlue, percent * 2.0), mix(flutterBlue, flutterNavy, (percent * 2.0) - vec3(1.0)), step(vec3(0.5), percent));
                                             ^
program_source:26:93: error: use of undeclared identifier 'percent'
    color = mix(mix(flutterSky, flutterBlue, percent * 2.0), mix(flutterBlue, flutterNavy, (percent * 2.0) - vec3(1.0)), step(vec3(0.5), percent));
                                                                                ^
program_source:26:110: error: use of undeclared identifier 'vec3'
    color = mix(mix(flutterSky, flutterBlue, percent * 2.0), mix(flutterBlue, flutterNavy, (percent * 2.0) - vec3(1.0)), step(vec3(0.5), percent));
                                                                                ^
program_source:26:127: error: use of undeclared identifier 'vec3'
    color = mix(mix(flutterSky, flutterBlue, percent * 2.0), mix(flutterBlue, flutterNavy, (percent * 2.0) - vec3(1.0)), step(vec3(0.5), percent));
                                                                                ^
program_source:26:138: error: use of undeclared identifier 'percent'
    color = mix(mix(flutterSky, flutterBlue, percent * 2.0), mix(flutterBlue, flutterNavy, (percent * 2.0) - vec3(1.0)), step(vec3(0.5), percent));
                                                                                ^
program_source:27:22: error: use of undeclared identifier 'color'
    fragColor = vec4(color, 1.0);
                     ^
program_source:30:7: error: non-qualified function cannot be called 'main'
half4 main(float2 iFragCoord)
      ^

[ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to build runtime effect (entry point: simple_fragment_main)
[ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/shell/platform/embedder/embedder_external_view_embedder.cc(198)] Could not render into the embedder supplied render target.

The problem is that the flutter fronted compiles the shader for Skia even if we're targeting Impeller.
Thus, when creating the runtime effect with the SkSL the metal library doesn't recognize the sksl provided.
Changing this line from ShaderTarget.sksl to ShaderTarget.impellerIOS solves the problem.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Looks like the tooling needs to be updated to compile the right shader variants for macOS.


All links to D365 Retails are inaccessible as of 2:00pm EST October 1st 2019

Describe the bug
All links to D365 Retails are inaccessible as of 2:00pm EST October 1st 2019
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-us/dynamics365/
Click on Retail\Documentation
See error

Expected behavior
All pages have to be loaded.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 77.0.3865.90 (Official Build) (64-bit)

Additional context
Did try to access from many zones, servers, regions, either from Microsoft cloud server, from America to Asia. All are failed to access.

@buck1ey Can you look at this issue reported for the Dynamics 365 docs homepage?
My link checker tool also flagged this link in the bottom as broken:

@mairaw We fixed the on-premises link and are working on fixing others as well. Thanks!

Me too.

https://docs.microsoft.com/en-us/dynamics365/outlook-app/deploy-dynamics-365-app-for-outlook
In this section the link is not working as well:

Still inaccessible...

Retails document links are still not working. I have task to deliver this week :(
Hopefully it is fixed ASAP.
Do MS have any backup link? if so, please provide. Thank you.

Thank you all for the feedback! Closing this issue as the links are working correctly now.


Define __STDC_FORMAT_MACROS for inttypes.h (older g++)

When including inttypes.h, define __STDC_FORMAT_MACROS to ensure that
the PRIu32 defines are included.
With newer g++ versions this happens automatically, but with older g++
versions, it's still required.
Signed-off-by: Mark Stemm<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

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

Needs approval from an approver in each of these files:

OWNERS [mstemm]

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

LGTM label has been added.  Git tree hash: 64619de986eaee36a061ff3741d9b3fa67f5a007

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

Needs approval from an approver in each of these files:

OWNERS [leogr,mstemm]

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

@FedeDP: changing LGTM is restricted to collaborators

In response to this:

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


Change the StartCoroutine calls to use the method directly

There are 3 calls of StartCoroutine that uses the method name as string.
This will cause trouble if you are using an obfuscator for your project
that renames all your private method names. By using the target method
directly (via the IEnumerator) the obfuscator can finally find this
reference too.

Integrated into next update.  Thanks!


Container: example(s) for long-running operations

Please provide (reference) an example for converting container_v1.types.Operation into api_core.operation.Operation.
create_cluster (and other methods in the Cloud Client Library) return (long-running) Operation(s).
I assumed (hoped) this would be google.api_core.operation.Operation that I could operation.result() but, the method turns google.cloud.container_v1.types.Operation
[Spanner's Python Library, for example, returns google.api_core.operation.Operation in this case]
I'm struggling to connect this with (presumably?) Long-Running Operations documented in Core.
I'm unable to new an OperationsClient. The Example suggests operations_v1.OperationsClient() but this errors with TypeError: __init__() takes at least 2 arguments (1 given).
It's unclear what channel (grpc.Channel) I should provide.
Is this the correct approach? Having triggered the cluster creation, I'd like to track its progress to completion.

Yep, we should add that and then this just magically works for @DazWilkin. What API is it?

Container
On Thu, Aug 9, 2018 at 12:29 PM Luke Sneeringer<EMAIL_ADDRESS>wrote:

Yep, we should add that and then this just magically works for @DazWilkin
https://github.com/DazWilkin. What API is it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/5780#issuecomment-411870143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPUc1uTt-GhW89pTygamMoAGQabOyquks5uPI2PgaJpZM4V2Meo
.

Ooh.... thanks @theacodes @lukesneeringer

@lukesneeringer Ping?

@lukesneeringer PR #6084 will automate the codegen for google-cloud-container, but somebody still needs to make the change to the upstream GAPIC config to get the operations wrapped.


Cooler example

If you change the example as:
func ProcessInput(f *os.File) error {
+       defer f.Close()
        b, err := ioutil.ReadAll(f)
        if err != nil {
                return err
        }
        return processBytes(b)
}

it suggests io.ReadCloser, which IMO is really cool... Thanks for this project!

Thanks for the suggestion!
Indeed this is a cooler example. At the same time, I'm thinking that it doesn't make a lot of sense as code in real life. Usually the function that opens the file does the defer f.Close(). I was going for the shorter code snippet possible that was both realistic and still a neat example.
What do you think?

I'm happy with the current example, so for now I'm closing this.


perf(classMap): improve classMap performance

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

close #411

Coverage decreased (-0.03%) to 43.318% when pulling 03c0d771a76862608b3fd4be4ecd72482c69a5f7 on vthinkxie:improve-performance into 8c5a41a41c66b403aa460bfa1f7621acead4093d on NG-ZORRO:master.


[Windows] Created window is centered by default

Looks much nicer when the window is created at the center of the screen as opposed to the top-left
Note: Windows only

oh options for this (how to open the editor, which monitor, etc) will be added very soon to godot

optiosn were added for that, so closing this


refactor: Use async/await in HttpConnector

Closes #1984

This is excellent work! I really need to get rustfmt running by default so it doesn't make diffs harder to read...

Ah :( seems like my format on save setup does not obey .rustfmt.toml anymore, pretty sure it used to...
gitcop doesn't explain which or why the commit messages are invalid so I am not sure what to do about it

Sorry I didn't get back to this sooner (I've been trying to get all the things released), and so merging the Tokio 0.2 upgrade has caused merge conflicts.

Thanks so much!


When adding a pre/post-function plugin, the function gets executed

I've also opened an issue in Kong's repository, but I'm opening one here as well because I think it might be related to a recent issue that was done here.
So, as you can see in the issue I've opened in Kong, when trying to add a pre/post-function plugin in Kong 1.3, the function I want to add gets executed, which means that if I have something like this in my function:
if not custom_auth then
  return kong.response.exit(419, "This message is coming from the lua function itself!!!")
end

then the POST request to add the plugin gets a 419 status code with this custom message, and I'm unable to add the plugin.
This doesnt happen with Kong 1.0.3 & Kong 1.2
After digging up a bit, I think what's happening is that when Kong is validating the all the plugin's fields and get to the "config" field, it uses the custom_validator which contains the following code:
local function validate_function(fun)
    local func1, err = loadstring(fun)
    if err then
      return false, "Error parsing " .. plugin_name .. ": " .. err
    end

    local success, func2 = pcall(func1)

Now, isn't this code actually executing the function i'm trying to add...?
Thanks! :smile:

answered here: https://github.com/Kong/kong/issues/5010#issuecomment-529179184

@Tieske Thanks for the quick response!
Following your answer in the other thread, is there a way that this issue can be prevented (without relying on the workaround you suggested)? I'm not (yet) familiar enough with all the Kong eco-system, but is there a way to run the function in some sort of "sandbox" so that the kong object won't be populated?
I mean, can't this be quite a risky side-effect? let's say I have in my function, that should be assigned only to a specific route, something like "if not condition, then do something destructive". Given that this condition will never be fulfilled when adding the plugin, then the destructive code will be executed.


webpack-bundle-analyzer not showing bundle dependencies

Just a heads up that for some reason the analyze:client script is not showing the dependencies of each bundle on the interactive report. I'm currently looking to see why but I thought I'd make every aware.

I had a similar issue some time ago. The solution was to change line https://github.com/ctrlplusb/react-universally/blob/d71b1e4475b31155260ea7ad3d793890aef5aed4/internal/scripts/analyze.js#L41
to JSON.stringify(stats.toJson(), null, 4)
Not sure if it's related to your issue though.

That did the trick, thanks for that

Would be great to get this fix into next branch.


[iOS] Video pauses when notification tray or control center is opened

Current behavior
When a locally saved video is playing and the control center or notification tray is opened, video pauses with no event.
Expected behavior
The video should not pause but continue playing like in android or there should be an event to handle it
Platform

iOS

`playWhenInactive
Determine whether the media should continue playing when notifications or the Control Center are in front of the video.
false (default) - Don't continue playing the media
true - Continue playing the media
Platforms: iOS`

Did you even read the ticket I posted? It has nothing to do with that
issue.
On Wed, Feb 20, 2019 at 7:30 AM manjariParthiban<EMAIL_ADDRESS>wrote:

Closed #1489
https://github.com/react-native-community/react-native-video/issues/1489
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-video/issues/1489#event-2150975518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArfDv70zqejf71bQ9n-xRf6G-WZYDdysks5vPOuZgaJpZM4bC4n4
.

Woops, I'm sorry, I mixed up my responses.
On Wed, Feb 20, 2019 at 7:31 AM Simon Brännström<EMAIL_ADDRESS>wrote:

Did you even read the ticket I posted? It has nothing to do with that
issue.
On Wed, Feb 20, 2019 at 7:30 AM manjariParthiban<EMAIL_ADDRESS>wrote:

Closed #1489
https://github.com/react-native-community/react-native-video/issues/1489
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-video/issues/1489#event-2150975518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArfDv70zqejf71bQ9n-xRf6G-WZYDdysks5vPOuZgaJpZM4bC4n4
.

How do I put code into ios?


Support for  and link reference definition associations.

An abstract node 'Reference' that captures the link label, title,
description attributes for subclasses Link, Image, AutoLink.
AutoLink node class that allows Visitor to differentiate between
inline links and  types.
Support in the InlineParserImpl to capture the association between
links and link reference definitions.
static Debugging functions

Looking into that test failure.

Looks like a good change, but I'm not sure about the class structure yet.
Do you think it would make sense to have [foo]: /url "title" be its own Node type, like ReferenceDefinition? Something like this maybe:

[foo](/uri "title") is a Link, which has getDestination, getTitle (not sure about getLabel)
[foo][foo], [foo][] and [foo] are ReferenceLink extends Link, which have an additional getDefinition which returns the ReferenceDefinition

Does that make sense?

I've created an issue for this improvement, for which this PR can be a starting point: #98. Closing this in the meantime.


Add F# events support

Do not merge, work in progress.

[x] Basic Event object implementation
[x] Event module functions
[x] 'IEvent` methods
[x] Testing
[x] Docs

@alfonsogarciacaro, I think I have small problem with workflow - changes I've done to import/core/fable-core.js are not copied to test folder. So all my tests are failing. Am I doing anything wrong?

I wanted the tests in the CI server to run against the fable-core version in npm, so I'm checking the environment variable DEV_MACHINE before replacing fable-core with the development version. You can comment that line for now, I will uncomment it again when the new version of fable-core is published :+1:
Thanks a lot for your work!

And sorry, I forgot, can you please also edit the part about Events in the docs now that you made Events work too :)

It's not ready yet - as for now I've get Event module functions working. Still need to add methods from IEvent (AddHandler etc.).
Will update docs when I'm done :)

Looks like I'm green on all tests, docs updated. From my point of view it's ready to merge. But code review and any comments appreciated.

This is an amazing work! The code looks great, I just left a couple of comments but they're not very important. Only, if we're really interested in making the size of fable-core.js smaller, we could try to unify the code for Event and Observable static functions. But probably when we implement tree shaking this won't be very important.
I'm really surprised you got the code for the second replacement pass (the CoreLibPass) right as it's not very intuitive :) I'll leave some comments for future contributors. Also, I forgot to tell there's a readCoreLibMethods.js script in the src/tools folder to automatically update CoreLibMethods.fs. Did you use it?
I'll merge the code as is. I'm also giving you edit rights in case you need to change something later.
Thanks a lot for this, Krzysztof!

Thanks. :)
Yes, unification between Event and Observable sounds like good idea.
No, I haven't used readCoreLibMethods.js, i just modified this file I shouldn't modify by hand ;)


Refactored bokeh plotting API

This PR represents a major cleanup of the (internal) bokeh plotting API to make it more consistent with matplotlib and simplify some things. Basically it adds the dictionary of style options to the bokeh ElementPlot.get_data method signature and return types. This means that at least the input signature of these methods now matches matplotlib. It's also in many cases much cleaner because a) most ElementPlots need the style as input and b) many also modify the style depending on the element data or parameters, which currently requires subclassing a completely different method. This will make it easier to write a guide on extending HoloViews with new plots and also simplify the process itself.
Concretely the motivation here was to make it easier for me to write some of the statistical plot classes.
This does represent a major change and will force me to pin the latest version of holoviews in the new geoviews release.

Ready to review/merge.

I have one question above unrelated to the changes in this PR. Otherwise, looks good.
Merging.


Wrong values case for "Fields" parameter in Get-GSSheetInfo wiki

Describe the bug
Wrong values case for Fields parameter in Get-GSSheetInfo wiki.
To Reproduce
Get-GSSheetInfo
Expected behavior
Fields must be written in lower case:

"namedranges"
"properties"
"sheets"
"spreadsheetid"

Thanks, Luca!
This is just a documentation fix; the actual ValidateSet options are in camelCase as they should be; specifically camelCase, not all lowercase (this will actually fail in the same way that the parameter help's TitleCase options do for Fields that are multiple words like namedRanges or spreadsheetId).
I could also force case conversion in the function body, but using the options in ValidateSet as they are works without issue so long as they aren't manually typed with different casing. You can tab complete through the available fields though when choosing a value for that parameter.

This will be fixed up in the upcoming release!

@lucafabbri365 - fix has been released as of now in v2.21.0! Check it out when you can!

Hello Nate,
you are simply great !!!
Thank you,
Luca
From: Nate Ferrell<EMAIL_ADDRESS>Sent: Wednesday, December 19, 2018 9:54 PM
To: scrthq/PSGSuite<EMAIL_ADDRESS>Cc: Luca Fabbri<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [scrthq/PSGSuite] Wrong values case for "Fields" parameter in Get-GSSheetInfo wiki (#128)
@lucafabbri365https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flucafabbri365&data=02|01|luca.fabbri%40livemail.it|8aab4b144c534f4321f208d665f420ed|4ed9059aa2764f2ab2c55383a832d5ff|0|0|636808496532566444&sdata=%2F72Lrzh3ov2s128tHBl7f6CmZ199MW0ULcwD8eEd8vo%3D&reserved=0 - fix has been released as of now in v2.21.0! Check it out when you can!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fscrthq%2FPSGSuite%2Fissues%2F128%23issuecomment-448740246&data=02|01|luca.fabbri%40livemail.it|8aab4b144c534f4321f208d665f420ed|4ed9059aa2764f2ab2c55383a832d5ff|0|0|636808496532576453&sdata=bA4eMHWytVM0npe3cRu4mdATrJpIdFATEuEOvSaRWdc%3D&reserved=0, or mute the threadhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAaC_WdSdZMY3BYMylF8-qfZG8-J1wwJnks5u6qdygaJpZM4ZGhKG&data=02|01|luca.fabbri%40livemail.it|8aab4b144c534f4321f208d665f420ed|4ed9059aa2764f2ab2c55383a832d5ff|0|0|636808496532576453&sdata=EFBBQEhQieuY%2Bw71YX1YbQrdJTisR93Ze1Lup%2BwZkOs%3D&reserved=0.


nixUnstable: pre6779_324a5dc9 -> pre6779_f435634a

Motivation for this change
Update nixUnstable to version pre6779_f435634a (16.08.2019)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build nixUnstable


Fix/subfieldbase django-1.10 compatibility

rebased the open pull-request #2119

LGTM (even if a bit sad that the behavior is required).
Are all the changes are already covered by existing tests?

Merged in 480aca681f2c31e5083cf38ed367043fe6a78365 / 97b1a3b897b598e6c1fe861884b23a167a1d5eae - thanks!
@timgraham Yes, this is covered by tests (various tests in wagtail/wagtailcore/tests/test_streamfield.py fail in the absence of 97b1a3b897b598e6c1fe861884b23a167a1d5eae, as they set up test data by assigning a list or JSON string to a StreamField). I agree that the need for the SubfieldBase replacement code is unfortunate, and I'm still keen to find a way around that - will open a new issue to cover that.


Fix course info scraper 84

Why I made this issue/PR
This issue/PR was needed to unblock work I was doing in validateCourseInfoScrape-76.  As I was finishing up writing the validator, I noticed that it was actually successfully catching invalid course info!  I didn't want to merge the json validator branch without letting it do one complete no-errors-found run-through, so even though the problem was with the scraped data and not the validation (probably), I resolved to first fix the scraper and then move back to the validator.
What changed
Looking through some of the scraped data and the webpages it came from, I found that the courses that were being badly scraped/were badly formatted online/need to be scraped from elsewhere were all missing the description property in the scraped json.  So, I added some logic that prevents such courses from being written to the file our storer.js scripts use to add json to the mongodb.  That is all.  Now I will resume work on the validator, which will no longer send us annoying emails regarding bad data.  This is good because we only want to be emailed about failed scraping on good data, not failed scraping on data we should ignore.
The scrape-course-data.r file now outputs a list of courses that don't have descriptions.
:straight_ruler:

I'd like this to be reviewed/tested so I can get back to my course info json validation branch.


Error on Testing New aggregation Rule

Try to create an aggregation rule to show a heartbeat and keep getting an error on testing the rule. I'm hoping its something simple that I have missed.
Below is the error i'm getting:
  File "/usr/local/bin/elastalert-test-rule", line 11, in <module>
    load_entry_point('elastalert==0.1.21', 'console_scripts', 'elastalert-test-rule')()
  File "/usr/local/lib/python2.7/dist-packages/elastalert-0.1.21-py2.7.egg/elastalert/test_rule.py", line 378, in main
    test_instance.run_rule_test()
  File "/usr/local/lib/python2.7/dist-packages/elastalert-0.1.21-py2.7.egg/elastalert/test_rule.py", line 373, in run_rule_test
    self.run_elastalert(rule_yaml, conf, args)
  File "/usr/local/lib/python2.7/dist-packages/elastalert-0.1.21-py2.7.egg/elastalert/test_rule.py", line 269, in run_elastalert
    client.run_rule(rule, endtime, starttime)
  File "/usr/local/lib/python2.7/dist-packages/elastalert-0.1.21-py2.7.egg/elastalert/elastalert.py", line 839, in run_rule
    self.add_aggregated_alert(match, rule)
  File "/usr/local/lib/python2.7/dist-packages/elastalert-0.1.21-py2.7.egg/elastalert/elastalert.py", line 1595, in add_aggregated_alert
    alert_body = self.get_alert_body(match, rule, False, alert_time)
  File "/usr/local/lib/python2.7/dist-packages/elastalert-0.1.21-py2.7.egg/elastalert/elastalert.py", line 1351, in get_alert_body
    'alert_info': rule['alert'][0].get_info(),
AttributeError: 'str' object has no attribute 'get_info'

I am running this command
 elastalert-test-rule /home/*******/elastalert/elastalert/my-rule-set/heartbeat.yaml
This is my rules code (Currently i'm just doing a count of selected users over an hour to test it):
import dateutil.parser

from elastalert.ruletypes import RuleType

from elastalert.util import ts_to_dt

class HeartBeatRule(RuleType):

    required_options = set(['usernames'])

    def add_data(self, data):
        count = 0
        matchItem = {}

        for username in self.rules['usernames']:
            matchItem[username] = 0

        for document in data:
            matchUsername = document['username']
            if matchUsername in self.rules['usernames']:
                loginTime = document['errorTime'].time()
                matchItem[matchUsername] = matchItem[matchUsername] + 1

        for key in matchItem.keys():
            item = {"username":key,"count":matchItem[key]}
            self.add_match(item)

    def get_match_str(self,match):
        #return "%s they are very trying(%s) back again " % (match['username'],match['count'])
        return "Yo it's here"

    def garbage_collect(self, timestamp):
        pass

and finally this is my config :
name: "Heart beat"

type: "elastalert_modules.heartbeatRules.HeartBeatRule"

index: error-*

timestamp_field : errorTime

usernames:
- hacker101
- cat1997
- dog1665

inculde:
- username

aggregation:
  schedule: '00 0/1 * * MON-FRI'

aggregate_by_match_time: True

aggregation_key: 'username'

summary_table_fields:
- count
- username

alert:
- "slack"

slack_webhook_url : "**************************"
slack_msg_color : good

not induced the sensitive web hook information for obvious reasons 🙈

I had this same issue, mine only had an error when running it with --debug flag

This bug was introduced by #1413. I'll try have a fix up shortly.

Any news on the fix for this?  I sorely miss being able to use debug mode.

@bcbeck
Just added the fix. Sorry about that.

@Qmando - Wow!  I couldn't get a patch from someone on my own team as fast as you did that.  Problem solved.  Thanks.


Get rid of fluent accessors

Maybe they make code a bit more readable in Java but:

JavaBeans convention is de facto standard
They break inspections, eg. IDEA null checks because tooling doesn't know that some methods are accessors.
 It's been discussed extensively in Discord afaik, and the gist of it is that we stick with it because vert.x does; I'd probably care more about doing this if/when(?) we move away from using vert.x. I'm not opposed to this, just don't think that it's worth caring aobut this now when there's bigger issues to fix.

agreed with @queer.

consistency
appearance (fluent is better don't @ me)
massive breaking change

#277 is relevant I think

advantages for javabeans:

standardized
supported and even expected by many tools/services
very popular
very clear what the methods actually do

advantages for fluent as of 1.x:

matches other libraries (vert.x)
looks much much much better than JavaBeans
already used extensively throughout the entirety of the lib

if we switch to JavaBeans, we get more standardized code which is supported more as well as more clarity, but we also have to rewrite the vast majority of the library. not only that, setters in javabeans aren't supposed to return this which makes the clean, simple and concise code of current catnip a lot more bloated

advantages for fluent as of 1.x:

Most of it is just changing a single lombok annotation (@Accessors(fluent = true) to just @Accessors)
Subjective
True

Also, as I understand it, the JavaBeans convention is just a naming convention -- I haven't seen anything dictating that setters must be void

Seeing as delombok, git and the aid of IntelliJ can actually make the process quick, just delombok the file, rename the variables to the javabeans convention then just reverting the file then changing the annotations, someone could do this really quickly.


fix: add plugin-search, spaces topic sep, tax-free, short/long help

What does this PR do?
adds taxonomy free
adds plugin-search
adds spaces topic separator
adds short/long help via -h or --help
removes 2PP plugins from pinnedDependencies list and leaves them pinned at their current version
adds schemas and schema check
makes sfdx similar to sf
What issues does this PR fix or reference?
@W-12069105@
@W-12069175@

packed tarballs locally, running  commands as ex: tmp/darwin-x64/sfdx/bin/run force org list
✅  spaces: tmp/darwin-x64/sfdx/bin/run force org list
✅  colons: tmp/darwin-x64/sfdx/bin/run force:org:list
✅  colons, tax-free: tmp/darwin-x64/sfdx/bin/run force:list:org
✅  spaces, tax-free: tmp/darwin-x64/sfdx/bin/run force list org
✅  spaces, tax-free: tmp/darwin-x64/sfdx/bin/run force list org --help shows descriptions and examples
✅  spaces, tax-free: tmp/darwin-x64/sfdx/bin/run force list org -h shows short help (omits description, examples)
tmp/darwin-x64/sfdx/bin/run search
✅  wow, that's nice!
❓   not related to this PR, but why is the org:shape commands show up for apex in search?


Capacitor v5

Hi, is Capacitor 5 support planned?

Hey, I think the upgrade from 4 to 5 had very minimal breakage, I will look into it in my spare time if no one volunteers by then.

The plugin should work with Capacitor 5, let me know if it does not work.


Removed Gratuitous Lambda

Generated JSON consumer no longer uses WriteApiCallToFile via a lambda and instead uses simple function calls that are easier to debug over/into and which results in three fewer lines of code per supoorted Vulkan function.
Also renamed the parameters field in the C++ to args to match its name in JSON.

CI gfxreconstruct build queued with queue ID 58007.

CI gfxreconstruct build # 2650 running.

CI gfxreconstruct build # 2650 passed.


Fix failing test

Bump clusterctl version
Bump CAPI versions
Bump kind and kubernetes versions
Bump Kyverno version

This has been quite a journey. @stone-z I need to do this in every policies repo. WDYT?

Related to: https://github.com/giantswarm/giantswarm/issues/25764


Mark 2024 07

This pull request contains significant rewrites of VicarLabel and VicarImage to address a few bugs, simplify, and remove a performance logjam that I knew about (in which adding one new parameter at a time to a label took N-squared time, where N is the number of parameters in the label).
Fixed Issues

Failure to read a Galileo SSI file containing a non-ASCII string.

Summary of Changes
New handling of non-compliant VICAR labels
We had already programmed around a VICAR compliance issue in Cassini ISS files, where one VICAR parameter name is 33 characters long, whereas the documentation says the limit is 32. Now we see that there is at least one Galileo SSI file with a different violation of the standard. This makes me uncomfortable. To make an analogy, nobody would ask the developer of the Python FITS module to change their code so it could read a file that violates the FITS standard.
My new solution is to add a "strict" parameter to the constructors, with a default value of True. If you are dealing with a non-compliant file, you will need to specify "strict=False". Then it uses a looser interpretation of the standard. In the future, if we encounter more non-compliant files, we can look at the nature of those and perhaps make them also compatible with our loose parsing rules. But meanwhile, strict parsing is always the default. In the case of Cassini ISS, the one change needed to the host module is to specify "strict=False" in the VicarImage constructor.
I added the Galileo SSI file with a corrupt string value in the label to test_files/.
Performance logjam
Previously, every time you modified a VicarLabel, it regenerated an internal index. Because there is a strong tendency to add parameters to a label one at a time, this causes an "N-squared" performance issue. I added an internal flag so that the label no longer re-indexes until it needs to.
make html warning
You get an annoying warning on "make html" inside the docs about a missing _static subdirectory. I created an empty docs/_static subdirectory and voila, the message goes away.
Approach to unit tests
These are now consistent with the rest of Python-world.

tests/__init__.py now has no content.
No test files contain the "if __name__ == '__main__" clause at the bottom.

Revised docstrings
My high-level goal is to make sure the same content is available to a user in a Python session and to a readthedocs user. I give the Sphinx/Napoleon developers credit for how easy it is to make clean HTML documentation from a docstring that also remains perfectly readable. Frankly, however, I would expect to continue using docstrings and help() more often than readthedocs webpages; I only tend to go to HTML documentation when I'm a new user or when dir() and help() don't get me to what I need. So I want to make sure going forward that both sources of documentation are complete. To that end...

Most of the content in README.md is now duplicated in the docstring for vicar/__init__.py. This is needed so the content shows up in help(vicar). Rob points out that keeping the two files (same content but different formats) in sync is going to be hard, and I agree. However, the README file is not immediately accessible to someone working in a Python shell, whereas help() is. If the two files drift out of sync, I understand, but I think the goal should be equivalence.

I started using "Parameters:" instead of "Args:" in docstrings because it better matches the HTML that Sphinx generates.

Sphinx does not cleanly handle the case of a function returning multiple values in a tuple, or (even worse) a function that returns a variable number of results. Expanding on what Rob has been doing, I found what works best is to use bullets to explain the individual returns. See the docstrings and readthedocs for examples.

There's a fundamental difference between the "Note:" and "Notes:" directives. The former creates a special box in the HTML to highlight something important, whereas the latter is just a header for a new section of text, nothing more. Keep this difference in mind. If it's an important point that might be overlooked by the user, use "Note:". If it's just some more explanatory text, use "Notes:".

I added the :special-members: directive to docs/module.rst, because this includes the dunder functions like __len__, __getitem__, __eq__, etc. in the HTML. These are an important part of the public API and are otherwise not included. Unfortunately, this also has the side-effect of including a few things we don't want like __dict__ and __hash__, so I have added these in an :exclude-members: directive. That seems to produce all the public API documentation we want for readthedocs.

Meanwhile, I think it will be useful also to have a developer's version of the HTML documentation. This again echos my own use case, where I look at docstrings for private functions (those beginning with an underscore) every bit as often as for public functions. I created a new directory docs-dev, which is a copy of docs/ but module.rst is modified to include private functions (using :private-members:) and also to include _LABEL_GRAMMAR.py, which is a core piece of the module. This extra content is not appropriate for readthedocs, but it would be easy and useful for us to host this web content locally. Details of that are TDB. Another advantage of building this version of the HTML is that it's the only way to find out if the docstrings of the private functions are properly formatted.

Minor fix: JPL's MIPL website has disappeared, mysteriously, and with it the document that describes the VICAR standard. Luckily, we host a local copy in our website's help/ subdirectory, so I changed the links in the documentation to point to our copy.

Known Problems

We're going to have to add that one line fix to oops/hosts/cassini/iss for strict=False.

More changes... I moved the definitions at the top of vicarlabel.py and vicarimage.py into a separate file _DEFINITIONS.py, in part so many of the flake8 violations were more localized. The docstrings in _DEFINITIONS.py and _LABEL_GRAMMAR.py now contain links to the source on GitHub, which makes up for the fact that the viewsource module doesn't support files just filled with definitions. Finally, I stripped .flake8 back to its bare minimum.


NestJS Example is not working

System Info
System:
OS: macOS 13.1
CPU: (8) arm64 Apple M2
Memory: 506.08 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.18.0/bin/yarn
npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
pnpm: 8.9.0 - ~/.nvm/versions/node/v18.18.0/bin/pnpm
Browsers:
Chrome: 117.0.5938.149
Safari: 16.2
npmPackages:
@rspack/cli: ^0.3.6 => 0.3.6
@rspack/core: ^0.3.6 => 0.3.6
Details
While trying to solve some issues at work I checked the NestJS example rspack provides under examples/nestjs
Sadly this example doesn't work for the same reason: Providers in the app.controller.ts constructor are not properly injected.
This effect can be observed because the should-be injected instance of AppService is undefined at runtime.
Leading to a TypeError: Cannot read properties of undefined (reading 'getHello') when actually opening localhost:3000 in the browser.
Providing an explicit @Inject like so constructor(@Inject(AppService) private readonly appService: AppService)
seems to solve the problem but this workaround should not be required according to the NestJS docs https://docs.nestjs.com/providers and isn't needed when using webpack/tsc instead
Reproduce link
No response
Reproduce Steps
From examples/nestjs:

pnpm install
pnpm run build
pnpm run start
GET localhost:3000 in the browser/curl/...

missing some configuration on swc-loader
https://github.com/web-infra-dev/rspack/pull/4308/files#diff-c731c9e2095190f907b29c0cc6bf0873c5b0b4309a5a6ae1ede3a21f179b519fR22-R30


Update for 1.19.2 release

Checklist

[X] Used a fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

There are 1 too many lines.  There should be one empty line at the end of the file.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@duncanmmacleod I have updated the recipe for the latest release.

Thanks @bashtage! I needed this package for a downstream library, but have no real idea how to maintain it, so if you're able and willing to take over, thanks!

Thank. I'm happy to pop over rand update when I make a release. Easier than using my own anacond.org account.


Old device name after delete_and_create the same device (MEGH-4192)

I create device with dev_name "X" and add name parameter with value "A", change device's name parameter to "B" and delete device.
Next, create device one more time with dev_name "X" and add name parameter with value "A" one more time, but it has name B (that i changed for, last time, before deleting).
The only way to clear this, is calling esp_rmaker_factory_reset(). Even "Remove" node from app does not clear this information.
Deleting device like this, without any errors:
     err = esp_rmaker_node_remove_device(node, sensor_device[sensnum]);
        if(err)
                ESP_LOGE(TAG, "Device remove ERROR");
        if(!err)
        {
            err = esp_rmaker_device_delete(sensor_device[sensnum]);
            if(err)
                ESP_LOGE(TAG, "Device delete ERROR");
            err = esp_rmaker_report_node_details();
            if(err)
                 ESP_LOGE(TAG, "esp_rmaker_report_node_details() failed: %u", err);
        }

@jacek12345 , this is more like a feature, allowing users to free up memory for operations like OTA, yet ensure that the names given by end users stay intact. For newer devices not related to their earlier instances, a different name is generally recommended. Even then, if you want the name to be deleted, would an API like esp_rmaker_param_clear_value(char *device, char *param) or some similar variant of this be useful for you?

Is this related with PROP_FLAG_PERSIST ?
When I create name parameter by esp_rmaker_param_create(), not by esp_rmaker_name_param_create() and didn't set PROP_FLAG_PERSIST, the name is cleared after device delete.
I suppose that can create name parameter with this manner but please clarify if there are some other issues related with using or not PROP_FLAG_PERSIST.
I have RMAKER_NAME_PARAM_CB=y and manage in cb function like other parameters.

this is more like a feature, allowing users to free up memory for operations like OTA
So can it be problem with OTA if there is to much devices in node? If this is true, so what is recommended flow for OTA success in this case?

Hi,
by using PROP_FLAG_PERSIST, the updated value of that parameter is stored in the nvs. If you want your device parameter to retain its state across reboots, then you should use PROP_FLAG_PERSIST.

On each boot i create devices from the beginning and use params (also name) from my NVS storage. Can I resign from PROP_FLAG_PERSIST in this scenario?

You might omit PROP_FLAG_PERSIST if you are manually reading and writing values to the nvs flash. PROP_FLAG_PERSIST is a flag added to eliminate the developer's overhead of manually writing/reading from the flash. Adding too many devices to the application will take up heap memory, which might cause OTA to fail. Rainmaker OTA events provide you with a way to execute your code before OTA starts, so you may delete some of the devices if you are currently facing issues during OTA updates.

thank You @sanketwadekar


Simplified Chinese characters with background do not display properly in RichText.

I want to add a background to text, here is my code:
RichText(
                text: TextSpan(
                        text: "不科学1111",
                        style: TextStyle(
                          color: Colors.black,
                          background: new Paint()..color = Colors.pinkAccent,
                        ),
                    children: [
                          TextSpan(
                            text: "不科学sdfsdfkd",
                            style: TextStyle(
                              color: Colors.lightGreenAccent,
                              background: new Paint()
                                ..color = Colors.pinkAccent,
                            ),
                          ),
                        ]),
                  ),

But the Simplified Chinese words do not display:

If I set the background color with opacity, it seems well:
RichText(
                text: TextSpan(
                      text: "不科学1111",
                      style: TextStyle(
                        color: Colors.black,
                        background: new Paint()..color = Colors.pinkAccent.withOpacity(0.5),
                      ),
                    children: [
                        TextSpan(
                          text: "不科学sdfsdfkd",
                          style: TextStyle(
                            color: Colors.lightGreenAccent,
                            background: new Paint()
                              ..color = Colors.pinkAccent,
                            ),
                          ),
                        ]),
                  )

But it still doesn't meet my expectation:

I have added app locales supports like this:
supportedLocales: [
            const Locale('zh', 'CH'),
            const Locale('en', 'US'),
          ],

Still doesn't work.

Please add the output of flutter doctor -v.

Please add the output of flutter doctor -v.

[✓] Flutter (Channel beta, v0.11.3, on Mac OS X 10.13.2 17C205, locale
zh-Hans-CN)
• Flutter version 0.11.3 at /Users/yumi/Library/Android/flutter
• Framework revision 72bf075e8d (4 days ago), 2018-11-09 20:36:17 -0800
• Engine revision 5646e86a6f
• Dart version 2.1.0 (build 2.1.0-dev.9.3 9c07fb64c4)
[!] Android toolchain - develop for Android devices (Android SDK 28.0.3)
• Android SDK at /Users/yumi/Library/Android/sdk
• Android NDK at /Users/yumi/Library/Android/sdk/ndk-bundle
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = /Users/yumi/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.4.1, Build version 9F2000
• ios-deploy 2.0.0
• CocoaPods version 1.5.3
[✓] Android Studio (version 3.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 29.1.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[✓] Connected device (1 available)
• M5 Note • 621QECQP4P2HM • android-arm64 • Android 7.0 (API 24)
! Doctor found issues in 1 category.

Could be related to https://github.com/flutter/flutter/issues/24234?

Could be related to #24234?

Thanks a lot. It is true that using multiple language styles will cause this problem. But I can't understand why when I set the background color with opacity, the characters will be seen?

Is there any workaround for this?

So the real bug here seems to be that the background width covers the entire span instead of just the run it is corresponding to. This is causing the widths to "overdraw" onto neighboring runs.

https://github.com/flutter/engine/pull/7287 This should fix the background overlapping with the text, causing it to become invisible behind it.
The strange translucency behavior requires a more in-depth metrics revision to properly draw them.

I would expect the parent TextSpan to paint behind the child TextSpan (even if both have a background).

(and I would expect the backgrounds to paint in pre-order depth-first)

Yes, this should happen now with the PR above, it was not the case before. For example, the current order is for two runs: run1bg, run1text, run2bg, run2text
With the change, it becomes: run1bg, run2bg, run1text, run2text

@yumi0629 @ozexpert @jason-simmons @zoechi hi gays, there is a workaround for this issue , see does it help for you.


Spyder not going through all breakpoints

Hi all,
edit.: After testing more functions and in various ways I have narrowed it down to just the return commands on the functions. Is this a particular option in the preferences?
This may be quite difficult to try and replicate, but I have no idea how this is happening, or how to solve it.
I am running a number of python programes on spyder. In order to try and understand some of the errors in them I am using the awesome breakpoint feature. Strangely It seems to ignore some of the breakpoints completely.
This is quite obvious when I place a breakpoint inside a for loop and spyder seems to stop only once if any when I debug the file.
Has anybody else heard of, or come across anything similar?
Thanks in a lot in advance.
I enclose my conda and system specs.
Current conda install:

             platform : osx-64
        conda version : 3.10.1
  conda-build version : 1.8.2
       python version : 2.7.9.final.0
     requests version : 2.6.0
     root environment : //anaconda  (writable)
  default environment : //anaconda
     envs directories : //anaconda/envs
        package cache : //anaconda/pkgs
         channel URLs : https://repo.continuum.io/pkgs/free/osx-64/
                        https://repo.continuum.io/pkgs/free/noarch/
                        https://repo.continuum.io/pkgs/pro/osx-64/
                        https://repo.continuum.io/pkgs/pro/noarch/
          config file : None
    is foreign system : False

Model Name:	MacBook Pro (15-inch, Mid 2012)
Processor Name:	Intel Core i7
Memory:	8 GB
System Version:	OS X 10.10.3 (14D131)
Kernel Version:	Darwin 14.3.0
Boot Volume:	Macintosh HD

I think you need to use the Step into button to remain in the loop.

Hola Carlos,
Thanks for the reply even with the issue closed.
I closed it since I found a website with a detailed explanation on the basic commands of the debug method managed to work around the issues.
At the moment everything seems to be working fine, but every now and then it starts being a bit unstable. I will reinstall it in the near future, since I think I have changed things which probably shouldn't have touched, but I think that its the best way to learn!
Thanks again for the reply
Best regards/ Un cordial saludo

No prob, please let us know if you encounter more problems with our debugging support. We are planning to improve it by the end of the year :-)
Y gracias por usar Spyder!!

@ccordoba12
Buenos dias!
Update on the issue.
Spyder is skipping breakpoints in reasonably long for or while loops and then gives an UnpicklingError: invalid load key, 'C'.  in the Internal console.
I have seen similar UnpicklingErrors in forums but i haven't called or touched anything to do with the Python Pickle module
Thanks in advance,
Un cordial saludo

Please paste here an example that's giving you that error so we can test it in our side :-)

Hola Carlos,
Sorry for the late reply I handed in my dissertation yesterday I have had incredibly busy days for the past two weeks.
Unfortunately I am not able to isolate the error, since it was happening when I was running one of the  functions in my dissertation project, and my knowledge on Spyder is limited... : S
I just wanted to  notify it here and in the event of somebody encountering something similar there would be some kind of prior idea on the subject. : )
Thanks for everything
Hope that the next version of Spyder is even better than the current...if its even possible!

It will be, that's for sure!! There are already several minor but cool improvements, and more important things are in the making ;-)
Take a look at
https://github.com/spyder-ide/spyder/wiki/Beta-version-changelog
from time to time to read about them.

Y finalmente, felicitaciones por tu tesis!!


Support nested closure completions

Today the plugin only sees the root level extensions and their methods, But if such method supports closure which contains a type, completions are not supported for such closures.
This change tries to find such methods and expand closure collection based on those closure types which could be for example a extension.
Good example of a code snippet to tryout this change is spotless plugin configuration as below
spotless {
    json {
    }
    java {
    }
}

if you try to invoke completions inside json closure, you don't get any and if you try to do the same inside java you endup with config values for standard java plugin.
When this change is applied, the correct configuration values are shown from the relevant spotless extension.
Note:  method chaining is still not working which needs to be separately add support.

@jdneo @testforstephen Let me know what you think


restart camera

when i start app then the camera works properly but once i changed the screen and then came to camerascreen then the camera not works it black screen no capture videos.

OK, I will fix it as soon as possible! You can pay attention to this project.

Already fixed, please use beauty_cam: ^1.0.4https://pub.dev/packages/beauty_cam


Module 1 exercises [Mansour Mahamane]

WS2_M1E1_Submission.docx

Please "drag & drop" exercise 1 file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 1 and make sure to take
the post-training survey.

Thank you for your successful submission to the practice exercise! Please be sure to fill out the post-Module survey.