router: add start timestamp header config

router: add START_TIME as one of the supported variables for header formatter
Description:
This change adds START_TIME as one of the supported variables for header formatter.
To get a timestamp in milliseconds, START_TIME needs to be put in the config as START_TIME(%s%3f).
Risk Level: Low, since this is an optional feature.
Testing: unit and manual tests.
Docs Changes:

added START_TIME as one of vars in custom headers manipulation section.

Release Notes:

added START_TIME as one of the supported variables in header formatter.

Fixes #1966

@junr03 can you take first pass on this? Thanks.

@htuch WDYT of this: https://github.com/envoyproxy/envoy/pull/3269#discussion_r187363612?
Seems like I need update this PR to fulfil that requirement.

@dio sure, if you want to followup on that it'd be nice.

@dio if adding more custom formatters looks too hard we can punt, but I think it's worth investigating just to see how difficult it would be since I think it would be a cleaner solution.

@mattklein123 sure. Will give it a try.

@mattklein123 I played around with this a little bit, so far I can have:

"%START_TIME(%since_epoch_ms)%" to get timestamp since epoch in ms (we could have us and ns too).
"%START_TIME(%ms)%" to get the ms component of a start time (we could also extend it to get us and ns component).

Do you think this is the right direction?

@dio I think if it looks possible to introduce custom formatters, it's the way to go. It's a much cleaner solution and we can solve multiple issues at once.

@dio SGTM. Instread of %ms%, how about following other existing conventions for sub-second granularity, e.g. https://bugs.python.org/issue1982?

@dio as long as @htuch is good with it, let's move forward with the time formatting extensions. Agree we should use existing conventions in other languages if possible. Let us know when this is updated and ready for review. Thank you!!

@mattklein123 @htuch yes, I put it as: START_TIME(%s%3f) to get timestamp since epoch as milliseconds where %s is seconds, and %3f is 3-digit subsecond. By default, %f gives us 9 digits (or should it be just 6?).
Waiting for CI to be ready for review. (seems like I'll add more tests for access log formatter to exhibits this change).

@mattklein123 @htuch @junr03 if you have time please take a look. Thank you.

Sorry for the very late update here. I decided to follow @htuch's suggestion on building a struct to record found substring patterns (position and width(when it has a width specifier, e.g. %3f)) and reuse that when rendering the final string.
Here is the updated benchmark.
2018-05-24 20:57:00
Run on (4 X 2400 MHz CPU s)
CPU Caches:
  L1 Data 32K (x2)
  L1 Instruction 32K (x2)
  L2 Unified 262K (x2)
  L3 Unified 4194K (x1)
-------------------------------------------------------------------------------------
Benchmark                                              Time           CPU Iterations
-------------------------------------------------------------------------------------
BM_AccessLogDateTimeFormatter                        141 ns        141 ns    4890625
BM_DateTimeFormatterWithSubseconds                   126 ns        126 ns    5354466

@mattklein123 @htuch @junr03 if you have time please take a look. Thank you.

@htuch I think I have addressed the previous round's comments. Thanks.

@htuch this is updated. When you have time, PTAL. Thanks!

@htuch yet another update. Please take a look when you have time. Thanks!

@htuch I have another set of updates. Now I tried to pre-compute the segments and add clearance for the cached map of formatted. PTAL. 😄

Super cool @dio. Awesome work!


support all EntryKeys when sharing with JMAP

following the refactoring done in this pull request, all EntryKeys are supported, no need to filter out some of them anymore.

For me the benefits are unclear and the API (JMAP) impact is unclear.
IMO I would keep the JMAP API restricted to identified use cases.
(So likely aborting the work on this PR)


Duplicate using Shift + Alt not Working

Issue Type: Bug
Recently Updated Code Insiders and this feature looks missing or buggy
VS Code version: Code - Insiders 1.41.0-insider (b6a486e34fe3715f6edec0cdb11138b1672d33bd, 2019-11-14T05:35:51.486Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz (4 x 2496)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.89GB (2.86GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

flutter-snippets
ale
2.0.0

vscode-intelephense-client
bme
1.2.3

dart-code
Dar
3.6.0

flutter
Dar
3.6.0

prettier-vscode
esb
3.5.0

adb-interface-vscode
vin
0.6.0

Same issue here

/confirmed
Looks like new `Go to Next/Previous Symbol" has conflicting shortcuts. Implemented in #84578
In meantime workaround will be to remove shortcut for this command
    {
        "key": "shift+alt+up",
        "command": "-editor.action.gotoPrevSymbol",
        "when": "editorFocus && editorHasDocumentSymbolProvider"
    },
    {
        "key": "shift+alt+down",
        "command": "-editor.action.gotoNextSymbol",
        "when": "editorFocus && editorHasDocumentSymbolProvider"
    }

or assigning other shortcut
/cc @jrieken

Sorry, for that. I have only checked on Mac. There is a new insiders version (eccf417b72fc0a632ec2cbd7855a681cdb8c81fa) which included a fix, commit eccf417b72fc0a632ec2cbd7855a681cdb8c81fa

@jrieken that was quick! Thanks!
Works as expected in the latest build!

Thanks for getting back to me. Closing and verifying.


Feat/nofussvendor sort local replaces

Better interactivity with go mod tidy by sorting the replaces.

/approve
/lgtm

Looks like the CI base image has "expired. This is a known Bazel issue, I'll get that fixed

Sorry for delaying this, been busy with some other stuff (mostly school related) but going to get this going on Monday!


Test_EndToEnd.Container() is causing other tests to fail

This test launches the test-cadence container as a worker service to verify that Neon.Cadence and Neon.Temporal actually work in a Linux Docker container.
The problem is that this worker is being registered in the same tests task list as the other tests and since it implements only a single workflow (BusyworkWorkflow), any of the other workflows and activities will encounter errors if Cadence/Temporal happens to schedule them on this container.  Sometimes this works, but we're seeing issues with timeouts as Cadence/Temporal attempts to reschedule these (but apparently not quickly enough to stay within the test timeouts).
I've also seen the test-cadence container still running after terminating a test run.  There's not a lot we can do about this, but that's making the symptoms seem more random.
Here's what we need to do:

[x] Run the Test_EndToEnd.Container() worker in a different task list, say test-cadence-container and test-temporal-container.  This will fix the conflict described above.
[x] Override the default client task list when invoking the BusyworkWorkflow via WorkflowOptions.  I believe this is the first actual test of this feature, so that'll be useful as well.
[x] We need to implement the test-temporal service
[x] ...and implement as well as publish the associated test-temporal Docker image to both nkubeio and nkubedev

Fixed for: v2.0.1


Create docker image

[x] Create dockerfile
[x] Set up build for docker image
[x] Publish release here on Github
[x] Update README

Done, new image builds on release.


Update/Add npm to >= 8.16.0

Tool name
npm
Tool license
The Artistic License 2.0
Add or update?

[ ] Add
[X] Update

Desired version
8.16.0
Approximate size
No response
Brief description of tool
npm is the package manager for the node.js ecosystem.
There is a bug in npm 8.15.0 that prevents installation and execution of packages from non-npm registries when using npx:

https://github.com/npm/cli/issues/5132

URL for tool's homepage
https://docs.npmjs.com/cli/v8
Provide a basic test case to validate the tool's functionality.
$ npx github:artichoke/clang-format --help
Usage: clang-format [options] [directory]

Node.js runner for LLVM clang-format

clang-format is a tool to format C code.

If no arguments are given, the runner formats the current directory recursively.
Any clang-format configuration present on the filesystem will be honored.

--check mode is suitable for CI. --check does not attempt to format and instead
exits with a non-zero status code if the source code on disk does not match the
enforced style.

Options:
  -V, --version  output the version number
  --check        Run in 'check' mode. Exit with a non-zero status code if any
                 formatting errors are found.
  -h, --help     display help for command

Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Virtual environments where you need the tool

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
yes

Tool installation time in runtime
No response
Are you willing to submit a PR?
no

@lopopolo Hello!
We do not pre-install npm versions other than a version currently available with nodejs by default, you can use actions/setup-node to manage the node installation yourself (I see you already did :) )


Add configuration for handling of unknown breakpoints

Today, breakpoints set outside of a DAP or AD7 command are treated as application exceptions. This can be unexpected, particularly in cases where the breakpoint was also set in the launch configuration. For example, postRemoteConnectCommands might include tbreak main. This PR adds a new unknownBreakpointHandling configuration option to for these unknown breakpoints.

throw current behavior
stop pause the debug session but do not simulate an application exception
ignore immedately continue

@benmcmorran was there a scenario you had in mind when ignore would be useful? Feels kind of dangerous to me -- if we are getting a bunch of stopping events it is going to make execution super slow, and also break stepping if you are stepping over a function triggering these. Though maybe it is okay to be complete.

@gregg-miskelly I don't have a specific use-case for ignore. It was just easy to add for completeness and I was already editing that part of the codebase. Given that it sounds like it could be a dangerous option, I'm happy to remove it, although I'd like to keep the configuration option as an enum to allow for additional handling options in the future.

Makes sense. I am fine with either leaving it in, but adding a disclaimer, or taking it out.


Reference mcdetect in "Preventing Mixed Content"

I signed it!

Hi, thanks for the PR! Since mcdetect is so new, and we haven't had a chance to test it or use it yet, I'm not comfortable adding it at this point.


Notification of usb connected is still appearing after unplugging

This is from the notification shade

This is the options appearing when you open it
Android: 12 LineageOS no gapps

Sorry for the late response... didn't see this until now.
If you still care about this and for future people that have this issue - it's probably caused by the app failing to restore the system USB gadget ^1, which is how Android implements stuff like MTP and USB audio ^2. Unfortunately, the way Android uses configfs to set up USB gadgets varies wildly between Android versions and vendors so it's hard to get it working for all devices. I only have one device to test this app with (w/ LOS 13).
As a workaround, you can restart your device and the system USB gadget will be restored.


Loading a material asset after being unloaded doesn't load referenced texture assets

Project: https://playcanvas.com/project/701353/overview/test-asset-loadunload
Steps to Reproduce

Launch the project
Press 1 to load the material asset. Texture asset is seen to loaded with it as it is applied to the box.
Press 2 to unload the material and texture assets.
Press 1 to load the material asset. Texture asset is not loaded as the box is now black.

In _bindAndAssignAssets, diffuseMap which had the assetId is replaced by the texture itself. When unloaded, this is not set back (if we could) so the second load of the material asset skips over loading texture assets.
https://github.com/playcanvas/engine/blob/master/src/resources/material.js#L215

This was fixed in 1.40.5 as part of this PR: https://github.com/playcanvas/engine/pull/3074


General localization feedback

Basically I finally found willings to extract all ASF strings into resource files, integrate entire ASF with Crowdin, and connect all pieces together to allow users translate all available strings into their spoken languages.
For more info about localization, visit wiki.
A sample pre-release version with localization included is already available. ILRepack-based binaries are not being translated, and I doubt they will start to be anytime soon (ASF-Service and ASF.exe built via Mono, but not ArchiSteamFarm.exe suggested binary for self-builds).
I'm opening this thread because many ASF strings changed, including accidental errors such as #406. If you have any constructive feedback how we can further improve this idea, you found some bug that should not happen, or likewise, please feel free to post.
Personally I consider it truly a great change, with assumption that more people will eventually want to help, as the entire integration I set up is just marvelous and I can merge all changes with a single button, so if there is an option to further improve this, I'd be super happy to do so.
In general, share your feedback. Saying that you like this improvement is appreciated as well (after all, I spent 6+ hours extracting all those strings...). It's also a good time to review default translation and check if we can improve it - this one is in Strings.resx and available to edit via classic PR.

Need add property in global config to disable localisation. :)

@Shmurdik This is now possible via CurrentCulture since ASF <IP_ADDRESS>.


west: runners: esp32: respect --esp-device during reset

When --reset was specified, esp32 runner was autodetecting serial port to
be used, regardless of --esp-device argument.
Append --port SERIAL_DEVICE parameter earlier, so that reset command
invocation uses explicitly specified serial device.

@mniestroj Do you mean erase instead of `reset' in PR and in commit messages?

@mniestroj Do you mean erase instead of reset in PR and in commit messages?

Yes, definitely, sorry for that! :)


Require help instructions for build with espressif sdk

Hello,
i copy IonDB to my esp32 arduino directory "components\arduino\libraries\IonDB",
add include line #include "IonDB.h" or #include <IonDB.h> before #include "Arduino.h" or after,
but get error "main/example.h:12:19: fatal error: IonDB.h: No such file or directory",
if write full path, then not found other IonDB source files,
where i can get help for build with ESP32 FreeRTOS SDK?

Hi @usermicrodevices!
Did you clone the IonDB repository or did you install the IonDB library from the IonDB Library Manager?

Hi @danaack!
I copy IonDB to my esp32 SDK project directory. This is not Arduino IDE project, it is msys toolchain with esp32 SDK, any from https://github.com/espressif/esp-idf/tree/master/examples is same, i only append https://github.com/espressif/arduino-esp32 to "components" subdirectory.
Now i put IonDB sources to near main cpp file, and get long list errors.
main.zip


[Siddhi Editor] [Bug] User can export file without having saved

M3
Steps to Recreate:

Open a siddhi file on the editor and do changes(now be focused on an unsaved file)
Check export file menu option
And click on Ctrl+E shortcut option

Actual Result:
File>>Export menu option is disabled but shortcut option is working and the user can export an unsaved file.
Expected Result:
Shortcut option also should be disabled when file is unsaved

@chaminda I checked on the current editor but cannot see a issue. Can you please verify

@chaminda found the issue exist in one flow. Fixed in latest.


Fail to build locally

I'm new in the project and trying to build everything locally.  Which causes the command to fail. Even the --show-config command fail with the same error.  I've tested with generated fails using yaml and toml format.
To workaround this issue, I must have to remove the releaser.os and releaser.arch fields from the generated file.

For clarification, specifying multiple files attempts to merge them and the dagger/ci/defaults is attempting to build release binaries which are specified in another dagger/ci/ file :
The full CI command is go run ./dagger -c dagger/ci/defaults,dagger/ci/push,dagger/ci/push-charts,dagger/ci/tag-latest,dagger/ci/tag-release --lint=false --test=false, so you can update the values specified in those files to run the full build (release) process in a fork

For simple local builds you would typically use:
Charts: go run ./dagger --charts.git.export, to build the charts into a local charts/ directory and
Pushing images : go run ./dagger -c  <file> whose contents would contain something like:
[images.opni]
additional-tags = []
push = true
repo = "docker.io/alex7285/opni"
tag = "patch"
tag-suffix = ""

Thanks for reporting this, The setup tool is used infrequently so I'll see if I can make sure it always generates a working config. For reference, this is what my dev/dagger.toml looks like:

[charts.git]
	repo = "github.com/kralicky/opni"
[charts.git.auth]
	email =<EMAIL_ADDRESS>	username = "kralicky"

[charts.oci]
	repo = "docker.io"

[charts.oci.auth]
	username = "kralicky"

[images.opni]
	repo = "docker.io/kralicky/opni"
	tag = "latest"
	push = true
[images.opni.auth]
	username = "kralicky"

[images.minimal]
	repo = "docker.io/kralicky/opni"
	tag = "latest"
	push = true
[images.minimal.auth]
	username = "kralicky"

Some example usages:

building development images and updating a live cluster:

dagger run go run ./dagger -c dagger/ci/defaults,dev/dagger --test=false --lint=false
kubectl -n opni rollout restart deployment opni-manager
kubectl -n opni rollout status deployment opni-manager --watch

building local charts (no config required):

dagger run go run ./dagger --charts.git.export

Updating the dagger CLI (to the matching version in go.mod)

mage dagger:install

Running all tests in the CI environment (no config required)

dagger run go run ./dagger --test --lint

Note that for building, testing, etc. in cases where you don't need to build actual image/chart artifacts, you would normally use mage to run everything locally.

Its the tag-releaser.toml config in dagger/ci causing the issue because it sets
[releaser]
  push = true

not necessarily an issue with the setup tool, also the setup tool should probably explicitly set
[release]
  push = false

or something

also I recall the []string != []interface{} being an issue with defaults & koanf not matching, or something along those lines

@kralicky the []string != []interface{} decoding error is surfaced here, so an improvement to that logic would or error handling would be good as well
https://github.com/rancher/opni/blob/92a8f469a8fad8520b69290349397966782cc098/dagger/config/config.go#L216-L225

@kralicky the []string != []interface{} decoding error is surfaced here, so an improvement to that logic would or error handling would be good as well
https://github.com/rancher/opni/blob/92a8f469a8fad8520b69290349397966782cc098/dagger/config/config.go#L216-L225

I found something curious on this. For some reason the merge function is called with the src and dest "inverted". In other words, the dest map contains the defaults values defined as the first file in the -c command line argument. I'm not sure if this expected or not. But the result of this is that this part of the if is evaluated to false. Because the default values are not empty:
https://github.com/rancher/opni/blob/92a8f469a8fad8520b69290349397966782cc098/dagger/config/config.go#L218
Reading the koanf docs, it seems an issue. If the file on the right is used to overwrite the values from the left, this behavior seems wrong.

I've tried to fix the issue from the previous comment in a commit in the PR

For some reason the merge function is called with the src and dest "inverted".

Is this due to the koanf merge function having the src and dest args "backwards"? they use mergeStrict(src, dest), but traditional copy/merge functions will have (dest, src) order.

For some reason the merge function is called with the src and dest "inverted".

Is this due to the koanf merge function having the src and dest args "backwards"? they use mergeStrict(src, dest), but traditional copy/merge functions will have (dest, src) order.

I don't think so. Consider this diff in the main branch:
diff --git a/dagger/config/config.go b/dagger/config/config.go
index 3e0c9373f..e8f6ca0fb 100644
--- a/dagger/config/config.go
+++ b/dagger/config/config.go
@@ -197,6 +197,9 @@ func AutoLoader(filename string) (koanf.Provider, koanf.Parser, koanf.Option) {
 // same as mergeStrict() from koanf/maps/maps.go with added support for merging
 // empty []any slices with slices of a specific type.
 func mergeStrict(src, dest map[string]any) error {
+	fmt.Println("----------------- mergeStrict -----------------")
+	fmt.Printf("src: %+v\n", src)
+	fmt.Printf("dest: %+v\n", dest)
 	for key, val := range src {
 		// Does the key exist in the target map?
 		// If no, add it and move on.

Take a look in the following tests:
$ dagger run go run ./dagger -c dagger/ci/defaults --show-config
[...]
┃ ----------------- mergeStrict -----------------
┃ src: map[arch:[amd64] os:[darwin linux] repo:github.com/rancher/opni]
┃ dest: map[arch:[] auth:map[email: secret:<nil> username:] os:[] push:false repo: tag:]
[...]
┃ | releaser.arch                                    | []string | [amd64]                                          | _OPNI_RELEASER_ARCH                                    |                       |
┃ | releaser.auth.email                              | string   |                                                  | _OPNI_RELEASER_AUTH_EMAIL                              |                       |
┃ | releaser.auth.secret                             | string   |                                                  | _OPNI_RELEASER_AUTH_SECRET                             | GH_TOKEN              |
┃ | releaser.auth.username                           | string   |                                                  | _OPNI_RELEASER_AUTH_USERNAME                           |                       |
┃ | releaser.os                                      | []string | [darwin linux]                                   | _OPNI_RELEASER_OS                                      |                       |
┃ | releaser.push                                    | bool     | false                                            | _OPNI_RELEASER_PUSH                                    |                       |
┃ | releaser.repo                                    | string   | github.com/rancher/opni                          | _OPNI_RELEASER_REPO                                    |                       |
┃ | releaser.tag                                     | string   |                                                  | _OPNI_RELEASER_TAG                                     | DRONE_TAG             |

$ dagger run go run ./dagger -c dev/dagger.yaml --show-config
[...]
┃ ----------------- mergeStrict -----------------
┃ src: map[arch:[] auth:map[email: username:] os:[] push:false repo:ghcr.io/jvanz tag:latest]
┃ dest: map[arch:[] auth:map[email: secret:<nil> username:] os:[] push:false repo: tag:]
[...]
┃ | releaser.arch                                    | []string | []            | _OPNI_RELEASER_ARCH                                    |                       |
┃ | releaser.auth.email                              | string   |               | _OPNI_RELEASER_AUTH_EMAIL                              |                       |
┃ | releaser.auth.secret                             | string   |               | _OPNI_RELEASER_AUTH_SECRET                             | GH_TOKEN              |
┃ | releaser.auth.username                           | string   |               | _OPNI_RELEASER_AUTH_USERNAME                           |                       |
┃ | releaser.os                                      | []string | []            | _OPNI_RELEASER_OS                                      |                       |
┃ | releaser.push                                    | bool     | false         | _OPNI_RELEASER_PUSH                                    |                       |
┃ | releaser.repo                                    | string   | ghcr.io/jvanz | _OPNI_RELEASER_REPO                                    |                       |
┃ | releaser.tag                                     | string   | latest        | _OPNI_RELEASER_TAG                                     | DRONE_TAG             |
[...]

$ dagger run go run ./dagger -c dagger/ci/defaults,dev/dagger.yaml --show-config
[...]
┃ ----------------- mergeStrict -----------------
┃ src: map[arch:[amd64] os:[darwin linux] repo:github.com/rancher/opni]
┃ dest: map[arch:[] auth:map[email: secret:<nil> username:] os:[] push:false repo: tag:]
[...]
┃ ----------------- mergeStrict -----------------
┃ src: map[arch:[] auth:map[email: username:] os:[] push:false repo:ghcr.io/jvanz tag:latest]
┃ dest: map[arch:[amd64] auth:map[email: secret:<nil> username:] os:[darwin linux] push:false repo:github.com/rancher/opni tag:]

I don't know why yet. But the releaser field is merged twice. With different src and dest each time.


Install and import raven-js dependency

Fixes 2) and 3) in #35

Thanks for the nice addition!

@damiencaselli No probs. Any chance you might know when you'll be able to cut a release including this change?

I was thinking about doing it right now, but I got some errors while running ember test.

@achambers this is now included in the 2.1.0 release.
Thanks very much!

Thanks @damiencaselli

I think this is achievable by adding an option to the ember-cli-build.js file, but I have little to no time to try this.
@achambers @devinus do you think you could subit a PR with a fix?


fix #172

When the request validation failure not  call [SKPaymentQueue finishTransaction], waiting for the next App to restart the iOS send payment token

The Travis CI unit test failed...😂


Release 0.3.0

@maldrake

The examples are all neo4j. I didn't see conditional compilation feature flags in the source. How do you keep them from blowing up if you do a cargo build --features cosmos?

Confirmed that cargo build does not build examples. I added one more step to the pipeline that will check that the examples compile.


Tinyface Alignment

Hi,
I'm curious to learn about the Alignment Policy for the Tinyface dataset. As you have stated in Validation_lq page, it's possible to use pre-aligned images or MTCNN based alignment process can be applied.
But I realized that, when I use the MTCNN detector which is provided by yourself, can not detect faces in some images. Then I decided to decrease the detection threshold then I achieved to find those faces and got their alignment results. But in that case, my alignment result does not seem like yours.
At that point, I thought what is your alignment policy? Did you use a pre-defined threshold or min_face_size etc.? Or, you may use the thresholds which are provided in your repo, but if the face does not detected, then you may prefer to create a black canvas with 112x112 size and then copy the original image into that canvas without alignment or anything else.
I'm working on low quality face images and their enhancement procedure, In this domain Adaface is valuable paper so this is why Adaface is so important for my future research work.
Thanks

Hi Erol
Depending on the MTCNN implemenation and preprocessing steps, the result could vary.
To align the tinyface images I have performed

squarify the image and resized to 32x32

square_img = squarify(image)
if square_img.shape[0] != 32:
    square_img = cv2.resize(square_img, (32,32))

And zero padded the image with int(0.1*32).

padding=((pad_side, pad_side), (pad_side,pad_side), (0,0))
square_img = np.pad(square_img, padding,mode='constant',constant_values=0)

If this does not produce a alignment result, I pad the image's top by int(0.3 *32) side ratio and resize it to 112x112. (Rational is that the tinyface images generally seem to have faces positioned slightly toward the top and MTCNN could handle images better if the input is not too small).

high_padding=((pad_side, 0), (0,0), (0,0))
bgr = np.pad(bgr, high_padding,mode='constant',constant_values=0)
bgr = squarify(bgr)
bgr = cv2.resize(bgr, (112,112)

Some helpful functions.
def squarify(M,val=0):
    (a, b, c)=M.shape
    if a==b:
        return M
    if a>b:
        diff = a-b
        left_diff = diff // 2
        right_diff = diff - left_diff
        padding=((0,0), (left_diff,right_diff), (0,0))
    else:
        diff = b-a
        top_diff = diff // 2
        btm_diff = diff - top_diff
        padding=((top_diff, btm_diff), (0,0), (0,0))
    return np.pad(M,padding,mode='constant',constant_values=val)

This to detailed and helpful. I'll follow your instructions quickly.
Thanks for your time


Port unet to WH

Initial repro instructions
git checkout tpatel/unet-wh
python tests/ttnn/integration_tests/unet/test_ttnn_shallow_unet.py

need to disable shallow Conv optimization as its not functional on wormhole yet

Disabling any over config overrides
#if "act_block_h" in config_override:
    #    act_block_h_override = config_override["act_block_h"]
    #    assert act_block_h_override % 32 == 0, "act_block_h must be divisible by 32 (tile height)"

another change that must be made is the padded input channels into c1 should be changed to 32
ttnn_module_args.c1["padded_input_channels"] = 32

this takes us to the next error on c1
Statically allocated circular buffers on core range {} grow to {} B which is beyond max L1 size of {} B
[(x=0,y=0) - (x=7,y=7)]
1679588
1499136

@tapspatel, sorry I didn't realize an issue already existed, closing as a dup of https://github.com/tenstorrent-metal/tt-metal/issues/5924
I'll copy paste your comments over.


add genoMEL button to OSDC and PDC apps

Since we're going to straddle PDC and OSDC apps for a while, let's add a checkbox for 'genoMEL' to both applications.
https://github.com/LabAdvComp/tukey_portal/blob/pdc/tukey/templates/webforms/osdc_apply_pdc.html

NOTE:   it was discussed on 5.13 that we will have one website for PDC login using either eRA, InCommons, Oauth2, etc.   As a result, we only really need this checkbox on the new update PDC site, once this task is complete.

This is no longer necessary.


Misc. updates (see commit messages)

Don't hesitate to ask if you have any questions.

@mmcev106. Thanks for doing this.
I like that you made mkdir robust enough to handle the case where tmp already exists.  Nice!
Very helpful change.  I'll go ahead and merge.


Large contents in Editor causes VoiceOver to lag significantly while typing

Type: Bug
When editing a large file, VoiceOver tries to read the entire document when focusing the editor. This happens when InteliSense is triggered, an option is accepted or the InteliSense is dismissed, and focus lands back on the editor. This can cause significant lag which makes editing large files impossible. On my M2 Max Macbook Pro, the limit is around a thousand lines of code in an editor. The larger the file, the more significant the issue.
I am not sure if this issue is within VS Code itself, or within the accessibility implementation of edit boxes in Chromium. However, the end result is that editing large files in VS Code on the Mac with VoiceOver is almost impossible. Once you approach 2 to 4 thousand line files, typing will cause VoiceOver to often speak garbage, and it can take a few seconds for it to catch up once you stop typing, though the issue can manifest long before those sizes of file.
VS Code version: Code 1.82.0 (Universal) (8b617bd08fd9e3fc94d14adb8d358b56e3f72314, 2023-09-06T22:09:41.364Z)
OS version: Darwin arm64 22.6.0
Modes:

System Info

Item
Value

CPUs
Apple M2 Max (12 x 24)

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_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
4, 4, 5

Memory (System)
32.00GB (0.09GB free)

Process Argv
--crash-reporter-id 17c62c91-76c5-4b04-b5f0-c871bbd53fba

Screen Reader
yes

VM
0%

Some additional information as I'm still testing: The effect seems to be more noticeable while typing at the top or middle of the file. It seems to be less noticeable when editing towards the end of the file, though still very much present. It doesn't seem to actually read the entire file when focus lands back on the editor, however it does try to read a very significant chunk of it, which I assume is what causes the lag. On Windows with NVDA, for example, it only reads the currently focused line, which is what it should probably be doing on Mac as well anyway, as that's the most important info, and not the rest of the editor contents.
One repository which illustrates this quite well is the openal-cs bindings, which has some quite large files. When editing the al10.cs file in VS Code for example, while changing the library name constant, Voiceover will often trip over itself. This can even happen when the Intelisense doesn't trigger. I am not entirely sure what's actually happening here, though it does work fine in VS Code on Windows. When I edit the string that contains the name of the dll, Voiceover will continuously try to read the rest of the file contents. I thought this might be because of an extension, though I copied it into an editor window without extensions present and this still happens. Now though, we have two issues affecting the editing experience at the same time. Both the editing causing unnecessary reading while editing the string constant, as well as the lag both from switching into the auto completions and back out.
I'm sorry if I'm describing it perhaps a bit confusingly, but it's pretty clear when you try it. This is the repository I was mentioning earlier, in case it helps: https://github.com/flibitijibibo/OpenAL-CS
Should be noted that this isn't just with C# and this particular file. This also happens when I edit very large Python, JS/TS or C source files. So I believe the common denominator here is the size of the file loaded in the editor. However this is a very small repository with very few large files, and it very clearly demonstrates the problem when editing one of them.
I really hope this helps and I didn't confuse things further. I can record a screen capture to demonstrate if that helps as well.

Thanks a screen recording would be great

@meganrogge  I have not worked with big files like that using the mac version, but I have heard that feedback before. I'm traveling right now, but I will run some experiments when I'm back. @Ghorthalon  does it make any difference if you manually interact with the textarea before editing?


init.py

added type hint and converted to single line

@Praveensenpai would you be interested in being the maintainer of this project?

@Praveensenpai would you be interested in being the maintainer of this project?

okay, cool.

what is your pypi username?

what is your pypi username?

https://pypi.org/user/praveensenpai/


New version

Can you release a new version (ex. v1.0.7) including the merged fix? so we can use it at production,
Best Regards,
John

Done. I just waited for the test actions results.


Include the "not an official Google product" disclaimer

And include links to Google's production DI frameworks.
cc: @willnorris

There is a typo in "prodcution"

@gk5885 is there normally a vetting process for repos added to the google organisation?

@bradley-curran, @willnorris is the best person to describe exactly what that entails.

@bradley-curran: yes, we have a formal launch process that all projects go through which checks for things like making sure they are properly licensed, etc.  We typically checks for things like this disclaimer (when appropriate) as well, but this one seems to have slipped through.

I'll go ahead and merge this as-is to try and prevent confusion.  @freetigerliu: feel free to tweak if you'd like when you're up.

Can someone explain what this project is? I mean starting from the original README, anyone could see that this is something very strange. Following with the Java packages and the build.gradle with the dependencies, made it a lot more strange.
cc: @willnorris @bradley-curran


chore: remove js-green-licenses.json

In particular, log-driver no longer needs to be listed.
Fixes #387

PTAL


chore: add vscode task for tslint

Might be helpful for others as well. Running tslint via vscode task shows all the errors in the Problems pane

I am holding this because most developers are using the tslint plugin and I don't see why we should force them to use other way of reporting the tslint errors but on the other hand, this is the way codelyzer will lint external templates.
In a few days I'll review it again and merge, thanks for addressing my comment!

I see it more as a supplement. I am using the tslint plugin myself but it is configured to lint in the open file. If I want to lint all sources I was runningnpm run lint which showed the errors on the console. That's why I created the task, so I see the errors in the Problems pane and can jump to the problems. Just as information why I even have this task. I am using it very seldom (mainly when I change tslint.json), thus I am perfectly fine if it is not merged at all.


Cloudflare not working

The problem
Hi, I'm not able to access HA via browser using add-on
What version of Cloudflared has the issue?
4.2.12
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
http:
  ip_ban_enabled: true
  # Add use_x_forwarded_for
  use_x_forwarded_for: true
  # Add the Cloudflare IPs as trusted proxies https://www.cloudflare.com/ips-v4
  trusted_proxies:
  - <IP_ADDRESS>/24 (initially I had all this IPs in link, but issue remains)
  login_attempts_threshold: 5

Anything in the logs that might be useful for us?
[08:21:14] INFO: Checking add-on config...
[08:21:16] INFO: Checking for existing certificate...
[08:21:16] INFO: Existing certificate found
[08:21:16] INFO: Checking for existing tunnel...
[08:21:16] INFO: Existing tunnel with ID 650e9a02-XXXX-48f1-XXXX-14c7f7985772 found
[08:21:16] INFO: Checking if existing tunnel matches name given in config
[08:21:19] INFO: Existing Cloudflare Tunnel name matches config, proceeding with existing tunnel file
[08:21:19] INFO: Creating config file...
[08:21:21] INFO: Validating config file...
Validating rules from /tmp/config.json
OK
[08:21:22] INFO: Creating DNS entry home.filipeos.com...
2023-12-21T08:21:23Z INF home.xxxx.com is already configured to route to your tunnel tunnelID=650e9a02-XXXX-48f1-XXXX-14c7f7985772
[08:21:23] INFO: Finished setting up the Cloudflare Tunnel
[08:21:24] INFO: Connecting Cloudflare Tunnel...

Steps to reproduce the issue

I've bought a domain and added the NS of cloudflare
I added that domain and sub-domain to cpanel
Cloudflare was connected
I've installed your add-on and and added home.xxxx.com to Cloudflared options.
When save, restarted and in log clicked on link to activate the tunnel, all fine and healthy.
In Devices I added the Cloudflare with the Zones asked and API.
Added In Settings-Network the external https://home.xxxx.com and restarted HASSIO/Home Assistant

When I try to access the https://home.xxxx.com I get 400 bad request dark screen in browser.
Additional information
My cPanel have a SSL, I think it's from Let's Encrypt? Auto renew.
My goal is to finally be able to connect SmartThings too, since don't allow self signed SSL

Is there anything in the HA logs?
Did you restart Home Assistant after changing the trusted proxy settings?

For some miracle it's working now, my guess was that NS was not fully propagated? HA logs was clear.
I think I'm using the extra security like I did the installation right? or can I improve?


Jest support

We should talk about using Waffle with Jest.
In #89, it was discussed that maybe we can import only the matchers from Waffle to be used. What else needs to be done so that Jest users can easily integrate and use Waffle?
Jest is by far the most popular test runner in the JS space (and has been for a while), far exceeding Mocha and Chai:

Source: https://npmcharts.com/compare/mocha,jest,chai

Currently the chai matchers are exposed as a standalone package called @ethereum-waffle/chai. There could be another package called @ethereum-waffle/jest that includes jest compatible matchers.
We would welcome a PR, but currently this is not on the roadmap.

@sz-piotr Would love to work on a PR, I'll take a look at working on this.

Using this issue to save my research:

https://jestjs.io/docs/en/expect#expectextendmatchers
https://everyday.codes/javascript/create-custom-jest-matchers-to-test-like-a-pro/
https://noriste.github.io/reactjsday-2019-testing-course/book/jest-101/custom-matchers.html
https://github.com/testing-library/jest-dom

Human-readable list of matchers to support (plus explanations of what they do):
https://ethereum-waffle.readthedocs.io/en/latest/matchers.html

As of now, I think I'm going to create a separate repo for what I want to do (allows me to move a bit faster). If it makes sense, in the future, I would be happy to merge my project into Waffle as I will be making Waffle-inspired Jest watchers.

I've created #321 which is ready for preliminary review. It is feature-complete with respect to the existing Chai matchers.


Ass the possibility to hide some folders (bin etc)

Hi,
Please add the possibility to hide some folders like .vscode or bin, obj etc

(Opened project in the screen https://github.com/Type-DB/Core)
Thank you

http://donovanbrown.com/post/Hide-folders-in-Visual-Studio-Code-Explorer


far mod requires DxgiAdapter::RegisterVideoMemoryBudgetChangeNotificationEvent

Please describe your issue as accurately as possible. If you run into a problem with a binary release, make sure to test with latest master as well.
Reports with no log files will be ignored.
Software information
Nier Automata, far mod, proton
System information

GPU: rx 560
Driver: Mesa 20.0.3
Wine version: proton-tkg latest
DXVK version: 1.6

Apitrace file(s)

Put a link here

Log files

d3d9.log:
d3d11.log: NieRAutomata_d3d11.log
dxgi.log: NieRAutomata_dxgi.log

logs from FAR mod:
crash.log
dinput8.log
modules.log
steam_api.log
related pr https://source.winehq.org/patches/data/174998

You can use wine's DXGI implementation with DXVK. I'm not sure if this is worth implementing on our end given that it is poorly documented and a lot of work.

Sadly these changes still not merged https://github.com/wine-mirror/wine/blob/master/dlls/dxgi/adapter.c#L349-L354

You can compile wine yourself. That's certainly going to be faster than me spending the next couple of days to figure out how exactly this function is supposed to even work.

I think one of the main problems is going to be that DXVK's memory management doesn't work at all like memory management works on Windows. It is certainly possible to impement this, but it will behave differently from Windows and will almost certainly lead to unexpected behaviour.

Ok, i'll ask tkg to rebase this patch.

Ok, apparently I misunderstood what this method is supposed to do and it's actually a lot simpler than expected.  Have you seen the guide by MiyacoGBF ?
https://gist.github.com/MiyacoGBF/6fd49ae4a73a9a7f4d13c488bff2da77
I haven't had any luck myself making it work in-game though. But the FAR GUI displays and is usable in the main menu at least.

Awesome, it works for me even in-game

https://www.reddit.com/r/SteamPlay/comments/fu5dy3/far_mod_now_works_with_latest_wine/

note: i tested with dxvk dxgi with this commit https://github.com/doitsujin/dxvk/commit/079cda1c0ce225be3db68a39383de47904e67cfd


Javadoc task addOptions doesn't support Kotlin DSL

Expected Behavior
https://docs.gradle.org/current/dsl/org.gradle.api.tasks.javadoc.Javadoc.html
Can call options.addStringOption as stated in the docs above.
Current Behavior
JavaDoc.options is of type MinimalJavadocOptions, but addStringOption is only on the subclass StandardJavadocDocletOptions
I guess this just works in groovy? 🤔
Context
Can't add extra javadoc options in the Kotlin DSL.
related:
https://github.com/gradle/gradle/issues/15093
https://github.com/gradle/gradle/issues/2354
https://github.com/gradle/gradle/issues/7038
https://github.com/mockito/shipkit/issues/290
Steps to Reproduce
In Kotlin DSL, try the config from https://docs.gradle.org/current/dsl/org.gradle.api.tasks.javadoc.Javadoc.html
Which would be something like:
tasks.register<Javadoc>("generateRestApiDocs") {
    source = sourceSets.main.get().allJava
    setDestinationDir(reporting.file("rest-api-docs"))
    options.docletpath = configurations["jaxDoclet"].files.toList()
    options.doclet = "com.lunatech.doclets.jax.jaxrs.JAXRSDoclet"
    options.addStringOption("jaxrscontext", "http://localhost:8080/myapp")
}

Fails with:
Script compilation error:

  Line 82:     options.addStringOption("jaxrscontext", "http://localhost:8080/myapp")
                       ^ Unresolved reference: addStringOption

Workaround
from: https://github.com/gradle/gradle/issues/2354#issuecomment-376781100
tasks.named<Javadoc>("javadoc") {
    (options as StandardJavadocDocletOptions).addStringOption("jaxrscontext", "http://localhost:8080/myapp")
    // see https://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html
    // equivalent of  <additionalparam>-Xdoclint:none</additionalparam> in maven
    (options as StandardJavadocDocletOptions).addStringOption("Xdoclint:none", "-quiet")
}

Your Environment
gradle 6.7.1

Found https://github.com/gradle/gradle/issues/7038, this can be closed as a dup


FileAppend fails with expired transactions on mainnet

Description
uploading a large file with fileAppend on mainnet results in expired transaction errors. This is presumably because all the transactions are prepared in advance and a large number of chunks results in a file upload taking longer than 2 minutes in total, leaving some transactions to expire.
Steps to reproduce
Upload 30k file using fileAppend on mainnet (it works on testnet, but not mainnet where consensus latency is a little higher).
Additional context
No response
Hedera network
mainnet
Version
v2.17.0
Operating system
No response

Will need to investigate further, but this should already be handled here: https://github.com/hashgraph/hedera-sdk-js/blob/df182a16dce4ca3f58432c10edcca2fe9d9126b9/src/transaction/Transaction.js#L1383

@gregscullard I forgot but we already have a test for this https://github.com/hashgraph/hedera-sdk-js/blob/main/test/unit/AccountInfoMocking.js#L350 You do need to enable [Client.Transaction]signOnDemand though as by default that option is off. Although we have another option [Client|Transaction].regenerateTransactionId the reason this field is ignored is because it requires signOnDemand to also be enabled. It's not that obvious though.


[Refactor]: Client retry timeout

Currently in ClientConfig the default retry timeout is a fixed 50ms
/// default retry timeout
#[must_use]
#[inline]
pub const fn default_retry_timeout() -> Duration {
    Duration::from_millis(50)
}

This sometimes too short and result in timeout failure in madsim CI tests (#473).
Maybe a better way to implement this retry is to use exponential backoff algorithm.

Close in pr #479


Allow sparse matrix input to visuals._format_cluster_statistics

Original code works for dense arrays but not sparse arrays.
np.std(X, axis=0)
This PR updates the code so that X can be either a dense or sparse array.

Codecov Report

Merging #189 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #189   +/-   ##
=======================================
  Coverage   79.08%   79.08%
=======================================
  Files          10       10
  Lines         722      722
  Branches      147      147
=======================================
  Hits          571      571
- Misses        120      124    +4
+ Partials       31       27    -4

Impacted Files
Coverage Δ

kmapper/visuals.py
89.10% <100.00%> (ø)

kmapper/plotlyviz.py
42.76% <0.00%> (ø)

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 4c52847...eb3443d. Read the comment docs.

Sweet, thank you!  Could you please add a test similar to this one that shows it working with a sparse array?
https://github.com/scikit-tda/kepler-mapper/blob/4c52847c11333ce72afa47dbf8f04babe819dfb4/test/test_visuals.py#L206

hmmm, something is confusing me about the current test ... going to run a little experiment and check back in.

OK, I think I figured out my confusion by being explicit about the format of sparse matrices that are allowed. Some operations are not available for all format so I restricted to csc and csr (compatible with sklearn outputs).

@sauln not sure if the codecov checks are my fault, but pretty sure the tests are OK now.

Looks great! thank you!

thanks sauln, great project!


Implemented preliminary styling for native widgets.

I was playing around with styling the different iced examples and this is what I came up with.
To make this work I had to extend some of the widgets and change the view function of the Application and Sandbox traits to supply an ApplicationStyle object which can be used to construct widgets. This work is by far not finished yet. My next steps would be adding the possibility to load platform specific plugins to have a native look across different platforms and splitting the ApplicationStyle object into some sort of color palette to theme custom widgets and a set of styles for the built in widgets.
Consider this more a RFC then a PR. I just wanted to get some feedback about my approach so far.

Hey @Maldela, thank you for exploring this! I really appreciate the effort here!
That said, I do not think we are yet ready to write code to implement this feature. There is a lot to consider, discuss, and design. As the contributing guide states, please get in touch! I'd love it if you joined our Zulip server and we started a conversation there. I really think code will be the easy part here.
Your current approach is a very direct way of implementing support for styling, but it ties style properties to each particular widget in iced_native, which is meant to be renderer-agnostic. I am aware that the current iced_native implementation has the same issue, but a well-designed styling solution should try to address this issue.


support 0.9.0?

https://github.com/quantifind/KafkaOffsetMonitor/issues/79
This is the same issue

This is the same issue


Invalid left hand side of assignment

Broken in the last six days. The following was and is okay:
var foo = function(){}
foo = function(){}

However as soon as you split the two into external modules
i.e. mod1.ts
var foo = function(){}

mod2.ts
import mod1 = require('./mod1');
mod1.foo = function(){}; // Error : Invalid left hand side of assignment

that is caused by #2476. foo in import {foo} from "mod" should be immutable, but i do not think ns.foo in import * as ns from "mod" should be.

I've checked ES6 spec - all bindings that are created for imported names are immutable so all cases below should be illegal:
import * as ns, {foo} from 'foo'
import d from 'foo'

ns.a = 1;
foo = 1;
d = 1;


Merge CUPY_CUB_BLOCK_REDUCTION_DISABLED and CUB_DISABLED

Part of #3445.

Merges CUPY_CUB_BLOCK_REDUCTION_DISABLED and CUB_DISABLED into CUPY_CUB_ENABLED.
Supports interfaces to switch to use each backend, or define their priorities.

Environment variable: CUPY_BACKENDS.
cupy.core.set_reduction_backends and cupy.core.routine_backends (These functions are for debug use. We will leave them undocumented.)

PTAL.

Could you update the documentation of environment variables?

cutensor is used in einsum. We will add a switching code in another PR (#3524).

Jenkins, test this please.

Jenkins CI test (for commit 621ca3e55c9c92ea3ae681b2c6e823257d4cd14a, target branch master) failed with status FAILURE.

@asi1024 Your change in 20ac9d4 reminds me that we will need a way to test all kinds of reductions from cupy.cuda.cub and from cupy.core._cub_reduction. For a few limited cases (sum/min/max/etc) the former would shadow the latter.

Following the discussion here: https://github.com/cupy/cupy/pull/3386#issuecomment-654584165
"backend" will be used as a term to specify the underlying computation library.
So, how about CUPY_ACCELERATORS instead of CUPY_BACKENDS?

So, how about CUPY_ACCELERATORS instead of CUPY_BACKENDS?

I guess you'll have to change this in chainer-test first?

Jenkins, test this please.

Jenkins, test this please.

Jenkins CI test (for commit a4ab70ebbe6cabdaad39387237abf60ec61afecc, target branch master) failed with status FAILURE.

I should trigger after https://github.com/chainer/chainer-test/pull/586 is merged. I canceled the Jenkins CI.

Jenkins, test this please.

Jenkins CI test (for commit a4ab70ebbe6cabdaad39387237abf60ec61afecc, target branch master) failed with status FAILURE.

Jenkins, test this please.

Jenkins CI test (for commit 41f4e45089ebc18c0b970e7b7f08b2a04c689d0b, target branch master) succeeded!

@asi1024 Do you know why some CUB tests (I think) were skipped in cupy-py35? For example, search test_sumprod.py here:
https://jenkins.preferred.jp/job/chainer/job/cupy_pr/1493/TEST=cupy-py35,label=mn1-p100/console
Other CIs do not have this issue.

cupy-py35 uses NumPy 1.15.4, so 4 tests with @testing.with_requires('numpy>=1.16') in test_sumprod.py seems to have been skipped.

Jenkins, test this please.

Jenkins CI test (for commit 8a8feea086dd5b01c68963a516205707343b70ae, target branch master) succeeded!

LGTM!


stable/sentry Client Keys DSN field empty

Describe the bug
A clear and concise description of what the bug is.
Version of Helm and Kubernetes:
Helm 2.13.1, 1.13.1 kubernetes
Which chart:
Sentry
What happened:
After installation which seems to be successful Client DSN key is always empty for every project. I am not sure if this is a helm chart issue or some other but I am unable to find enough info to categorise it properly
What you expected to happen
Client DSN key to be populated for a new project
How to reproduce it (as minimally and precisely as possible):
Just install with default settings and go to a new project settings Client DSN Keys , DSN field is empty
Anything else we need to know:
Nope

figure it out but we could improve the documentation, basically I have changed url from my ingress one to loadbalancer ip + exposed port in Root URL

I have installed sentry and used my own ingress.
The sentry application is working were DSN: https://@/
But the DSN field is still empty. how to automatically populate the DSN field with correct DSN


Change Preloading and Caching to use the same system as auto_sync

preloader and reconciler no longer use a transaction

This will prevent rolling back a failed sync, but allows farmbot to
continue operating if a sync does fail

usage of the preloader updated to reflect this

Coverage decreased (-0.6%) to 27.543% when pulling 98f40e046f85e27c1806105b73af396e2a72a8ec on regimen_farm_event_update_handler2 into 908cb1f0f0d5177f4ba359e6db9439296ffacc68 on next.


Changes React and ReactDOM to peerDependencies

As mentioned in issue #99, this pull request changes React and ReactDOM to peerDependencies.  The purpose of this change is to prevent multiple copies of React from being loaded and causing errors when using it with updated versions of React (such as v16).

Thanks!


rclone mount: race condition with multiple RWFileHandle's

Following the forum thread Extracting to ACD mount possible? I'm now creating this issue.
I found a race condition involving multiple open *vfs.RWFileHandle's for one file.
This is a log containing a failed upload: rclone_extract_ptr_empty.log. The state after this log is the following:

Test/JD/rand4/rand.bin size=0 mtime=2018-01-29 21:25:18.826 +0100 (mtime of the source)
Test/JD/rand4/rand.bin size=0 mtime=2018-01-30 14:46:04.??? +0100 (mtime of upload time)

I assume the problem is *vfs.RWFileHandle.close() not being synchronized between multiple files.
The log file above shows two close() executing in parallel.
The first RWFileHandle belongs to a new empty file. The second one the handle being written to. During the close() of the first handle, the empty cache file gets Move'ed to the backend. After the move is completed the cache file get's deleted.
When the second close() tries to move the cache file, which is already gone.
This could also be related to #1181.
I think, close() should check whether there is another RWFileHandle opened for it's file. Hopefully this fixes the race condition.

What is your rclone version (eg output from rclone -V)

rclone v1.39-096-gcf6d522d

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Linux 4.14.13-1-ARCH #1 SMP PREEMPT Wed Jan 10 11:14:50 UTC 2018 x86_64 GNU/Linux

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone mount -vv --dir-cache-time 24h --vfs-cache-mode writes TestDrive:Test/JD /mnt/JD/extracted

I have to say I've been kind of ignoring the multiple file opens on the same file problem and hoping it will never happen :-)

You never heard of Murphy's law, don't you? :laughing:

We should probably use it in Open and close()

I'm not sure whether open needs to be protected by the same mutex. Only file.addWriter and file.delWriter should need to be synchronized.
This is a list of functions i think need to be synchronized:

newRWFileHandle: synchronized via cache.open + addWriter via file.muWriter
*RWFileHandle.openPending: synchronized via file.muOpen
*RWFileHandle.close(upload phase): synchronized via file.muClose + delWriter via file.muWriter
*RWFileHandle.close(remove phase): synchronized via cache.close

And now the part how this works in my head :smile:
openPending needs to be synchronized to other openPending of the same file, so only one copy gets downloaded. A open with O_TRUNC could cancel a running copy and clear the cache file.
RWFileHandle.close is mostly run with file.muClose held. file.delWriter is called to determine whether this handle was the last writer and when this is true do a operations.CopyFile to upload the cache file. Now file.muClose is released and cache.close is called, which removes the cache file when no reader is present.
It's pretty late here, so i can not guarantee this locking scheme is complete. I will look at it again tomorrow.

openPending needs to be synchronized to other openPending of the same file, so only one copy gets downloaded.

I think openPending should probably be synchronized to close also, so file.muOpen and file.muClose above should be the same mutex, otherwise won't we have the problem where the file is being both downloaded and uploaded at the same time?

A open with O_TRUNC could cancel a running copy and clear the cache file.

Do you see there being a separate download phase which is running without the file.muOpen?
(Aside: one thing I'd like to do at some point is run the download in the background in openPending to allow the file to be accessed before it is completely downloaded, and just block on operations which require bits of the file which aren't downloaded yet.  That is a whole heap of extra complication I suggest we don't attempt yet!)

RWFileHandle.close is mostly run with file.muClose held. file.delWriter is called to determine whether this handle was the last writer and when this is true do a operations.CopyFile to upload the cache file.

Though note not all the close() operations do transfer the file.

It's pretty late here, so i can not guarantee this locking scheme is complete. I will look at it again tomorrow.

I think it is an excellent start :-)
I think for the next evolution we should try to keep the changes as minimal as possible even if it is less than perfectly efficient - that has been my strategy in the VFS layer, correctness over efficiency.  Not always achieved though!

I think openPending should probably be synchronized to close also, so file.muOpen and file.muClose above should be the same mutex, otherwise won't we have the problem where the file is being both downloaded and uploaded at the same time?

A download is only done once per cache file (this is how it should work) and close is doing an openPending. This way only one can happen at the same time.
I want to make sure open and close use separate locks to allow the cache file to be opened while being uploaded.

A open with O_TRUNC could cancel a running copy and clear the cache file.

Do you see there being a separate download phase which is running without the file.muOpen?

This was just an idea which could speed up the open process in case the file get's opened with O_TRUNC, while another handle is downloading it.

Though note not all the close() operations do transfer the file.

Right, only when the last writer is closing and the cache file has be modified.
The modified flag count be passed via the delWriter call like this:
func delWriter(h Handle, modified bool) (lastWriterAndModified bool)

I think for the next evolution we should try to keep the changes as minimal as possible even if it is less than perfectly efficient - that has been my strategy in the VFS layer, correctness over efficiency. Not always achieved though!

You are right, the vfs layer is pretty complicated. As it is mostly working great we should be careful to not break any existing use case.
I will start working today on the changes we outlined until now.

A download is only done once per cache file (this is how it should work) and close is doing an openPending. This way only one can happen at the same time.

OK

I want to make sure open and close use separate locks to allow the cache file to be opened while being uploaded.

This was just an idea which could speed up the open process in case the file get's opened with O_TRUNC, while another handle is downloading it.

Oh I see...  You'd have to block if it wasn't opened with truncate though.  I guess if opened read only you are OK, but if not then I guess you have to block until the upload has finished otherwise?
Getting complicated :-)

The modified flag count be passed via the delWriter call like this:

Looks perfect.

You are right, the vfs layer is pretty complicated. As it is mostly working great we should be careful to not break any existing use case.

There are some exhaustive tests for the RW handles, however there aren't any tests for concurrent opens, so it might be worth writing some of those first, see them break then fix them!

I will start working today on the changes we outlined until now.

Excellent :-)


Add support for Joplin markdown notes

Joplin notes are already in Markdown, but when they are exported from Joplin itself, the slugs and links are md5/sha hashes. Implement a way to convert the file names and slugs accordingly to the note title.

Already got an issue for that #15


Actions Board View Rule

This contains the state to metastate mapping action rule and the necessary changes to the existing templates.
A thorough and complete description can be found here: https://docs.google.com/presentation/d/18xKQmkf3UKlGoP7qLqUnrIYiflza674n_paUZXKuepA/edit
Please note that this PR contains 2 new source files (the actual rule and the test) and minor changes to 3 existing files. The rest of the files in the PR are changes to golden files.

Codecov Report

Merging #2249 into master will decrease coverage by 0.11%.
The diff coverage is 62.36%.

@@            Coverage Diff             @@
##           master    #2249      +/-   ##
==========================================
- Coverage   69.26%   69.14%   -0.12%
==========================================
  Files         173      174       +1
  Lines       16152    16437     +285
==========================================
+ Hits        11187    11366     +179
- Misses       3897     3960      +63
- Partials     1068     1111      +43

Impacted Files
Coverage Δ

actions/actions.go
61.11% <ø> (-12.23%)
:arrow_down:

workitem/workitemtype.go
82.05% <ø> (ø)
:arrow_up:

actions/rules/action_state_to_metastate.go
62.36% <62.36%> (ø)

workitem/workitem_repository.go
68.39% <0%> (+0.22%)
:arrow_up:

controller/workitem.go
78.79% <0%> (+0.56%)
: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 87fdcec...94ca51e. Read the comment docs.

This contains the state to metastate mapping action rule and the necessary changes to the existing templates.

@michaelkleinhenz can you please explain in more details what this does and what it is good for? This description is only telling what is contained but not what it does.

Fixed. f758549

rsync: command not found on the build.
[test]

[test]


Forward merge 2.0 to develop-2.2, pulling in exometer_core update

This PR forward merges the 2.0 branch into develop-2.2. Hit some minor conflicts due to other fixes from 2.0 having been cherrypicked in, but the only actual change this brings in is to update exometer_core to 1.0.0-basho5 which pulls in the fix from riak_core PR #817.

:+1: e76e059

buildbot failure was due to dialyser PLT file being messed up - @ooshlablu should have it fixed in a few minutes. Hopefully before Bors picks up the retry.

@borshop merge


Set maxiters for CubaSUAVE

Fixes https://github.com/SciML/Quadrature.jl/issues/17

This RP is no longer needed. I implemented in the fix in #20


Fix EACRuntime controller scaling out bug

Ⅰ. Describe what this PR does
Fix EACRuntime controller scaling out bug
Ⅱ. Does this pull request fix one issue?

fixes #2629
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/lgtm
/approve


interpolateCubic, interpolateCubicClosed, interpolateMonotone, interpolateMonotoneClosed

cubic Hermite splines ; will be useful for https://github.com/d3/d3-scale-chromatic/issues/28
The difference with interpolateBasis is that this interpolator returns the exact values at the control points; with n = values.length we have:

values[i] = f(i/(n-1)) for interpolateCubic
values[i] = f(i/n) for interpolateCubicClosed, with f(1) == f(0)

Code adapted from https://github.com/Evercoder/culori (see https://github.com/Evercoder/culori/issues/91 )

@danburzo if you'd like to review?

I think I'd like to revisit the boundary conditions (section 2.2 in the Steffen paper). It seems we're duplicating the slopes at either ends by adding the reflection of arr[1] across arr[0] and the reflection of arr[arr.length - 2] across arr[arr.length-1] and that makes intuitive / naive sense to me, but I'm not entirely convinced it matches either the suggestions in the paper or the curve implementation in d3-shape...

See also https://github.com/d3/d3-shape/issues/118

I had a chance to give the cited paper another look. The previous implementation in culori, and by extension, in this PR, is using the one-sided finite differences for boundary points, which is a valid approach outlined in the paper (Section 2.2).
In<EMAIL_ADDRESS>I added another implementation to use equations (24) to (27) instead as culori.interpolatorSplineMonotone2. The effect is different but not necessarily better for color interpolation:

(In the image above, the FD versions refer to 'one-sided finite differences')
In particular, the finite-differences approach (blue stroke in the image below) produces curves that are closer to a linear interpolation; the new implementation (red stroke) tends to squeeze the colors at either end of the interpolation into a narrower portion:

So I'm not 100% convinced the new approach produces better results...


Developer Experience - Test upload validation end-to-end

Current State

There is no documented process on how to test upload-validation locally end-to-end

Expected State
When a developer uploads a file in their local-development environment, the file is passed through the various lambda functions python -> processValidationJson and the correct UploadValidation records are created in the database.
Implementation
This may require:

Deploying the lambda functions and s3 buckets in localstack using terraform apply
Ensuring that the s3 notifications are working correctly
Documentation on how to perform local-deployment and troubleshooting steps

Note - pausing on this for now and will return after high priority issues are addressed!

moving this back to ready as we discussed deprioritizing for the July milestone


Migrating from 1.x to 2.x

The following breaking changes need to be migrated when upgrading to version 2.x:
Code Generation Setup
Additional files are now generated for each file containing annotated classes. This removes the need to specify entry points in the build.yaml.

This is now similar to how packages like json_serializable or freezed generate code.

Remove the entrypoints inside build.yaml:

targets:
  $default:
    builders:
      dart_mappable_builder:
-        generate_for:
-          - lib/main.dart
          options:
            ...

If you don't have any other configuration inside build.yaml, you can delete the file completely.

In each file where you use annotations, add the respective part directive:

// This file is main.dart
import 'package:dart_mappable/dart_mappable.dart'

- import 'main.mapper.g.dart';
+ part 'main.mapper.dart';

@MappableClass()
class MyClass with MyClassMappable {}

If you haven't already, add the <ClassName>Mappable mixin to each annotated class.

In each file where you imported the generated mapper file, import the original file instead:

// This file is some file inside your project.
- import 'main.mapper.g.dart';
+ import 'main.dart';

Mapper Generation
Instead of generating a general Mapper class for everything, now each annotated class has its own <ClassName>Mapper.
Also the generated mixin <ClassName>Mappable is now required to be used.

Add the generated <ClassName>Mappable mixin to each annotated class:

@MappableClass()
- class Person {
+ class Person with PersonMappable {
  ...
}

In your code, replace any call to Mapper with the class-specific <ClassName>Mapper:

void main() {
-   var person = Mapper.fromJson<Person>('{...}');
+   var person = PersonMapper.fromJson('{...}');
}

It would be helpful to mention the equivalent code to replace something like this:
T deserialize<T>(String value) {
    return Mapper.fromJson<T>(value);
}

In the current docs, the breaking change seemingly removes the ability to have a generic deserializer. If this is actually the case, I can open a new issue/discussion about that since it is a very powerful feature that at least I rely pretty heavily on.

I just realized this also required mapping custom mappers. Not sure if you want to include that in this guide but the steps appear to be (roughly):

Remove the CustomMapper() annotation
Rename your class from MyClassMapper to MyClassMapperElement
Change your class to extend from MapperElementBase instead of BaseMapper
Create a private constructor: MyClassMapperElement._(super.mapper, super.container);
Create an additional new class:

class MyClassMapper extends MapperBase<T> {
  @override
  MapperElementBase<Color> createElement(MapperContainer container) =>
      MyClassMapperElement._(this, container);
}

It would be helpful to mention the equivalent code to replace something like this:
T deserialize<T>(String value) {
    return Mapper.fromJson<T>(value);
}

In the current docs, the breaking change seemingly removes the ability to have a generic deserializer. If this is actually the case, I can open a new issue/discussion about that since it is a very powerful feature that at least I rely pretty heavily on.
Edit: This seems possible via documentation here. It would just be nice to have that one specific substitution mentioned in this migration guide since it does affect migration.

documentation link is not found @point-source


rename alibaba to containerd in urls

Signed-off-by: liulanzheng<EMAIL_ADDRESS>

use #83


Experimental: to show you how it works

Checkout this branch and run the run.sh file from the root. It may take a while to spin up.

You will see in the config the example repos: for example https://github.com/backstage/backstage
Notice that the plugin assumes a docs directory which it pulls the markdown from, and the mkdocs.yml config is at the repo root instead.

I will raise a PR in miden-client so we can test it here.

This repo is no longer required @bobbinth sorry for inconvenience but we needed it for testing purposes, thank you for setting up...

This repo is no longer required @bobbinth sorry for inconvenience but we needed it for testing purposes, thank you for setting up...

fyi @Dominik1999


refactor: extract post consumer

Codecov Report

Merging #78 (b5cfdc6) into master (0272881) will decrease coverage by 0.78%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
- Coverage   75.69%   74.91%   -0.79%
==========================================
  Files          23       24       +1
  Lines         609      598      -11
  Branches       98       94       -4
==========================================
- Hits          461      448      -13
- Misses        148      150       +2

Flag
Coverage Δ

unittests
74.91% <83.33%> (-0.79%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/services/qq-service.ts
0.00% <0.00%> (ø)

src/command/email/email-command.ts
50.00% <50.00%> (ø)

src/command/slack/slack-command.ts
43.58% <50.00%> (+0.34%)
:arrow_up:

src/command/email/consumer-handler.ts
100.00% <100.00%> (ø)

src/command/post-manager/consumer.ts
100.00% <100.00%> (ø)

src/command/slack/consumer-handler.ts
100.00% <100.00%> (ø)

src/services/slack-service.ts
100.00% <100.00%> (ø)

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 0272881...b5cfdc6. Read the comment docs.


BED-4817: Update API types for posture page

Description
Updates a few types in our javascript API client to account for changes to the spec for the endpoint we are using to feed our new posture page charts.
The current openAPI spec for that endpoint can be found here: https://github.com/SpecterOps/BloodHound/compare/main...posture-api-spec
Motivation and Context
This PR addresses: BED-4817
How Has This Been Tested?
Screenshots (optional):
Types of changes

Chore (a change that does not modify the application functionality)

Checklist:

[x] I have met the contributing prerequisites

Assigned myself to this PR
Added the appropriate labels
Associated an issue: https://github.com/SpecterOps/BloodHound/issues/672
Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing

[x] I have ensured that related documentation is up-to-date

Open API docs
Code comments (GoDocs / JSDocs)

[x] I have followed proper test practices

Added/updated tests to cover my changes
All new and existing tests passed

I can't comment there because it wasn't changed in this PR but we also need to update the other endpoint to be
/api/v2/domains/{environment_id}/finding-trends


Device Attestation

(onhold due to waiting for Google/Apple spec)
When the user sends the diagnosis keys, we need to verify whether the request came from a legitimate source.

Accept the "platform" attribute in the incoming request. Must either be "ios" or "android". Needed for the device verification payload below:
Device Verification Payload: This is either Android SafetyNet device attestation or iOS DeviceCheck attestation.

Problem: This highly depends whether data privacy team is OK with this. I will sync with them.

@christian-kirschnick you mentioned that Device Attestation will be used for sending diagnosis keys, is it also planned for downloading diagnosis keys?

Downloading diagnosis keys will not be restricted.

What could happen in the worst case if any entity such as a rogue app instance were able to submit any set of diagnosis keys?
related discussuon: corona-warn-app/cwa-documentation#102

Uploading is protected by different safeguards, most prominently is the requirement of a TAN. A TAN can only be used once.
TAN's are issued by the system after a COVID-19 positive test result, and is then shared with the mobile client, which will use it to gain authorization for uploading keys.

But to answer your original question: Even if an attacker gets a hold on a valid TAN somehow; the worst case scenario would be false-positive warnings on your mobile phone, telling you that you were in proximity of a COVID-19 positive tested patient in the past 14 days. But for that to happen, the attacker needs to generate diagnosis keys, which match tracing keys received by other users.

Device attestation will be out of scope unless scoping team will decide otherwise. The fields will stay present in the submission API in order to ensure compatibility to the official spec, but the backend will not process those fields in case they are filled.


Use yarn as node manager.

Yarn is just better, quicker and solid way to install all npm dependencies.

Hello, thanks for contribution.
I'm not sure that I want to use yarv now. That's why I'll merge this changes later.
Thanks again 👍

hey, could you rebase your branch? :)

Done :)

thanks 👍


Dummy change for testing purposses

Thanks for submitting your Pull Request!
Please delete this text, and add a link to the Jira issue solved by this PR.
Remember to use the Jira issue ID in the PR title, and any commits.

Close, I only wanted to know whether the CI jobs were automatically kicked of using this branch.


envelope_api update_recipients recipients  The request body is missing or improperly formatted. Could not cast or convert from System.String to API_REST.Models.v2_1.recipients.

Hi all,
Could anyone potentially show an example of how to use the envelope api's update recipients method for updating a recipient? I believe I should be passing an array of dictionaries to recipients but not matter how I format it (from json to a list containing dictionaries) I could an error specifying the body is missing or improperly formatted OR the request body is missing or improperly formatted. Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'API_REST.Models.v2_1.recipients'. Any help would be appreciated as I simply am trying to engineer a way to resend an email if the user has misplaced the original.

Figured it out. Had to use the recipient model/class. Thank you.


Update copyright to 2024

Happy New Year! I've omitted the circuit from this PR but I will make a separate update after updating WIP and bootstrapping. It looks like doc-test/version-0.18 is failing due to the risc0-zkvm-methods crate failing to build. I'm going to omit changes to that directory for the time being.

Do we really need to modify every file? I think there's a deeper issue here.


Update import-data.md

Update line 508 to fix grammatical error.

@PHenwood : Thanks for your contribution to the Azure documentation! The author, @andrewhoh, has been notified to review your proposed change.

#sign-off


Update presentation to fix alignment

Update presentation to fix alignment

@stevenhorsman I updated the toc to match the current order. Also updated the screen capture based on the diagram. Others all look good to me. Thanks!


Confirm first paragraph in Data and Assessment

Removed the following from the first paragraph in Exec 'Data and Assessment' section, because it doesn't seem to make sense:
"Total catch and empirical weight-at-age for \Sexpr{last.data.yr} are also added to the assessment model this year, but are fixed and not included in the model fitting procedure. "
Have re-written that paragraph also. See commit   279fcce
Highlighting as an issue in case I'm missing something and that sentence is needed.

I think that the deleted sentence was trying to draw a distinction between data which had a specific likelihood contribution that the model was fit to, and other model inputs that influence the dynamics but may or may not be considered "data". Those other inputs are the total catch at the top of the data file and the mean weight at each age defined in the wtatage.ss file.
I personally don't consider the distinction to be something that is important to make, especially when it leads to conclusion to I support removing that sentence.
I'm going to commit a potential revision to this paragraph which notes that the 1995 survey age comps were also added, and the 1998 point was slightly revised. If these changes make it seem too wordy for the Exec Summary, I'm happy to scale them back or let any of the rest of you attempt to wordsmith further (or leave that to @aaronmberger as our lead author).

The paragraph that Andy added and then Ian added to looks good to me.  I'll wait for Chris to close this though as there is a merge conflict between Andy and Ian and my inexperience will screw something up no doubt if I try to remedy...

I think I've sorted out the merge conflict so I'm going to close the issue.


Clicking dropdown-toggle element closes other dropdown menus out of the context

Describe the bug
If you click an element with class dropdown-toggle, other dropdown menus, which are not related to clicked element, will be closed.
To Reproduce
This behavior can be reproduced on the Pandora Admin page.

Open the Mailbox submenu on the navigation menu and click Inbox.
Then click the down icon besides the checkbox icon above the mails table, which opens a dropdown menu.
Look at the navigation menu on the left side. The submenu for Mailbox is collapsed.

Expected behavior
Click on a dropdown-toggle element should close only related submenus if at all. In this example the submenu for Mailbox should NOT  be closed.
Desktop (please complete the following information):

OS: Windows
Browser: Chrome, Firefox, IE11, MS Edge
Metro Version 4.4.3

create issue in the pandora repo

create issue in the pandora repo

Thank you for your feedback.
I was not really sure and thought that it might be a bug in the core.

Thank you for your feedback.
I was not really sure and thought that it might be a bug in the core.


[ADD] Terra classic / Terra  CW20 tokens

add CRW-20 support for Terra and Terra Classic
relevant PR in IOS repo is https://github.com/vultisig/vultisig-ios/pull/1537

https://github.com/vultisig/vultisig-windows/pull/640


chore: remove pytest-cov

Closes #167

:tada: This PR is included in version 6.0.7 :tada:
The release is available on:

v6.0.7
GitHub release

Your semantic-release bot :package::rocket:


flutter packages get crashes if pubspec.yaml

I've made a mistake (syntax error) when adding fonts:
fonts:
- family: Pacifico
  fonts:
    -asset: font/pacifico.ttf

Note the dash in "-asset". It should be
fonts:
- family: Pacifico
  fonts:
    - asset: font/pacifico.ttf

When I launch flutter packages get I, it crashes:
C:\dev\flutter\bin\flutter.bat --no-color packages get
Running "flutter packages get" in flutter_app...                    0,3s

Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: b2e66ad01a10da6f)
Crash report written to C:\Users\p.divita\dev\altro\flutter\flutter_app\flutter_04.log;
please let us know at https://github.com/flutter/flutter/issues.
Process finished with exit code 1

Steps to Reproduce

Copy and paste in pubspec.yaml
Create the fonts dir and place a ttf font named "pacifico.ttf"
Run flutter get

I guess the normal behaviour should be a syntax error reporting, instead of crash
command
flutter --no-color packages get
exception
_TypeError: type 'YamlMap' is not a subtype of type 'Iterable'
#0      _validateFonts (package:flutter_tools/src/flutter_manifest.dart:409:47)
#1      _validateFlutter (package:flutter_tools/src/flutter_manifest.dart:354:9)
#2      _validate (package:flutter_tools/src/flutter_manifest.dart:312:9)
<asynchronous suspension>
#3      FlutterManifest._createFromYaml (package:flutter_tools/src/flutter_manifest.dart:45:40)
<asynchronous suspension>
#4      FlutterManifest.createFromString (package:flutter_tools/src/flutter_manifest.dart:40:12)
<asynchronous suspension>
#5      FlutterManifest.createFromPath (package:flutter_tools/src/flutter_manifest.dart:34:12)
<asynchronous suspension>
#6      FlutterProject._readManifest (package:flutter_tools/src/project.dart:153:60)
<asynchronous suspension>
#7      FlutterProject.fromDirectory (package:flutter_tools/src/project.dart:44:44)
<asynchronous suspension>
#8      FlutterProject.fromPath (package:flutter_tools/src/project.dart:59:58)
#9      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:96:61)
<asynchronous suspension>
#10     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:559:18)
#11     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#12     _rootRunUnary (dart:async/zone.dart:1132:38)
#13     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#14     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#16     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#17     Future._complete (dart:async/future_impl.dart:473:7)
#18     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#19     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async-patch/async_patch.dart:33:20)
#20     _rootRun (dart:async/zone.dart:1124:13)
#21     _CustomZone.run (dart:async/zone.dart:1021:19)
#22     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#23     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#24     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#25     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
#26     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)

flutter doctor
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Microsoft Windows [Versione 10.0.17763.475], locale it-IT)
    • Flutter version 1.5.4-hotfix.2 at C:\dev\flutter
    • Framework revision 7a4c33425d (2 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at D:\dev\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 35.3.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.0.0 (API 26) (emulator)

• No issues found!

Duplicate of https://github.com/flutter/flutter/issues/31764


New package COAA.PlanePlotter

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.
request from #115736
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116546&drop=dogfoodAlpha

Automatic Validation ended with:

Hi @blackzafiqz,
Is there an installer switch to bypass the above message? Alternatively, should NTP be a dependency?

@stephengillie @blackzafiqz Any chance this PR could be re-opened and the NTP issue (that will most likely not happen on 99% of actual end-user computers) waived?

Hi @AsciiWolf,

@stephengillie @blackzafiqz Any chance this PR could be re-opened and the NTP issue (that will most likely not happen on 99% of actual end-user computers) waived?

Is the assumption about 99% of end-user computers based on an assumption that only current users will install the software through the package manager, and thus will already have the dependency preinstalled? Please understand that we may have users whose hobby is downloading and installing random software, and if the dependency is missing from their system, then these new users of this software might have a poor experience. Much of the work we do here is to ensure the best experience that we can, for installing and upgrading software.
NTP isn't currently among our manifests, so one will need to be added to the repo before it can be used as a dependency.

NTP isn't currently among our manifests, so one will need to be added to the repo before it can be used as a dependency.

If I remember it correctly, this issue is probably related to a network limitation in the CI vm, not a dependency issue. NTP is a part of Windows since Windows 9x as the "Windows Time service".

Ah, you are right, it looks like PlanePlotter for some reason needs this component.

Automatic Validation ended with:
(Automated response - build 876.)

@stephengillie https://github.com/microsoft/winget-pkgs/issues/148222

I will add to the in 4 hours. Don't have my pc right now

Automatic Validation ended with:
(Automated response - build 876.)

Still not fixed. Please see my comment here.

sorry i didnt git add xD

I will try to fix on next week

Automatic Validation ended with:

2024-04-10 22:20:06.797 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!6891535B: (caller: 68811A80) LogHr(1) tid(1c80) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!6895B5DD: (caller: 689F12BF) Exception(1) tid(1c80) 8A15005E ]
2024-04-10 22:20:06.797 [REPO] Failed to open available source: msstore
2024-04-10 22:20:14.136 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!52BC535B: (caller: 52AC1A80) LogHr(1) tid(c90) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!52C0B5DD: (caller: 52CA12BF) Exception(1) tid(c90) 8A15005E ]
2024-04-10 22:20:14.136 [REPO] Failed to open available source: msstore

(Automated response - build 876.)

i just force push again?


Feature: Active / Inactive user - Phase II

🔖 Feature description
Add support for User List & Permission Group Bulk Operations:

Bulk Delete for users and permission groups
Bulk status update for users

🎤 Pitch / Usecases
.
🔄 Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#8374

Part of https://github.com/devtron-labs/devtron/issues/4409


Using react-with-styles in recompose

Can someone help me with an example of applying styles using react-with-styles in a higher order component using recompose ?
Specifically, how can we apply styles as explained in this example -- https://github.com/airbnb/react-with-styles -- in a higher order recompose wrapper ?

As any other HOC.
compose(
  hoc1, hoc2, withStyles(({ color }) => ({....}), hocN
)

@istarkov Thanks. I tried it the way you mentioned above and specifically, I am stuck at understanding how the styles of DateRangePicker (the component whose style I am trying to override) are to be set inside withStyles.
I set styles as mentioned in the theming snippet  , imported withStyles in HOC and am trying to override styles of DateRangePicker below:
recompose(
hoc1,
hoc2,
withStyles(({ reactDates }) => ({
//What is the approach to overriding styles of DateRangePicker ?
}))
)(DateRangePicker)

I have no idea how to use withStyles as I use different style managers. In case of react-dates I use styled-components and override them as
const datePickerStyles = `
  .CalendarMonthGrid {
    font-size: 14px;
  }

  .CalendarMonth_caption {
    font-size: 14px;
    line-height: 28px;
  }

  /* Info panel support */
  .DayPicker {
    width: unset !important;
    > div {
      display: grid;
      /*grid-template-columns: auto auto;
      grid-template-rows: auto; */
    }
  }

  .DayPicker_weekHeaders {
    grid-column-start: 2;
    grid-column-end: 2;
    grid-row-start: 1;
    grid-row-end: 1;
  }

  .DayPicker_focusRegion {
    grid-column-start: 2;
    grid-column-end: 2;
    grid-row-start: 1;
    grid-row-end: 1;
  }
  .DateInput__openDown {
    :before {
      top: 42px;
    }

    :after {
      top: 43px;
    }
  }

  .DateInput__openUp {
    :before {
      top: -14px;
    }

    :after {
      top: -15px;
    }

  }

  .SingleDatePicker_picker__openDown {
    top: 53px;
  }

  .SingleDatePicker_picker__openUp {
    bottom: 49px;
  }

  .DayPickerNavigation_button__horizontal {
    border: none;
    top: 20px;
  }

  .CalendarDay_container {
    border: none;
    &:hover {
      border: none;
    }
  }

  .CalendarDay__selected {
    border: none;
    border-color: #3f51b5;
    background-color: #3f51b5;
  }

  .CalendarDay__selected:active, .CalendarDay__selected:hover  {
    border-color: #7986CB;
    background-color: #7986CB;
  }

  .CalendarDay__selected_span {
    border: none;
    border-color: #5c6bc0;
    background-color: #5c6bc0;
  }

  .CalendarDay__selected_span:active, .CalendarDay__selected_span:hover  {
    border-color: #7986CB;
    background-color: #7986CB;
  }

  .CalendarDay__hovered_span {
    border: none;
    border-color: #9fa8da;
    background-color: #9fa8da;
    color: #3f51b5;
  }

  .CalendarDay__hovered_span:active, .CalendarDay__hovered_span:hover  {
    border-color: #9fa8da;
    background-color: #9fa8da;
    color: #3f51b5;
  }

`;

const Label = styled.div`
  pointer-events: none;
  color: ${({ focusedInput }) =>
    focusedInput ? 'rgb(48, 79, 254)' : 'rgba(0, 0, 0, 0.54)'};
  position: absolute;
  left: 0;
  top: 22px;
  transition: all ${ANIM_TIMEOUT}ms cubic-bezier(0.4, 0, 0.2, 1);
  transform-origin: 0% 50%;
  transform: ${({ focusedInput, value }) =>
    focusedInput || value
      ? `translate(0, ${-24}px) scale(0.75);`
      : 'translate(0,0) scale(1);'};
`;

const UFormHelperText = styled(FormHelperText)`
  && {
    position: absolute;
  }
`;

const DateRangeDiv = styled.div`
  & {
    width: 100%;
    position: relative;
    ${datePickerStyles};
  }
`;

Then react-dates placed as child of DateRangeDiv got my styled

Thanks ! Looks like my question sits midway between recompose and Theming as applied to react-dates. Any general example on how to override styling in a recompose wrapper component would be great.

@niranjanshukla Perhaps you should create a question at StackOverflow?

Because it's not a bug report or a feature request, so I'm going to close this issue. Please feel free to reopen it if you have any further thought.


Add example YAML conversion specification instance

Motivation
Another simple pre-PR for the YAML conversion specification. In particular, this includes the actual example YAML file we use in the main PR for running a full conversion
How to test the behavior?
The primary test here is if the defined YAML specification schema is valid and compatible with our example file, or vice versa.
Checklist

[X] Have you checked our Contributing document?
[X] Have you ensured the PR description clearly describes the problem and solutions?
[X] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?

Going to merge this into the downstream branch so the schema stuff is all a complete roundtrip.