chore: Add SAVE_ACTION analytics event

Description

This PR renames the SAVE_QUERY and SAVE_API events to a generic SAVE_ACTION analytics event.
The new event will include the following new properties

originalActionId - The originalActionId of the action from which this action was copied  or the id action from which this action was copied.
hash - A unique hash of the actionConfiguration of this action
actionType - The plugin type for this action

This PR also fixes an issue where the originalActionId was not set correctly when an action was copied

PR fixes following issue(s)
Fixes #25971
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
How Has This Been Tested?

[x] Manual
[x] Jest
[ ] Cypress

Test Plan
Issues raised during DP testing
Checklist:
Dev activity

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

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview skip-tests=true


Add support for BitSnoop archives

http://bitsnoop.com/info/api.html

I actually think this already works...

Yep, already works.


[TACHYON-590] Add unit tests for getLeadingPath in TachyonURI (@uronc…

…e-cc's comment)
@uronce-cc I added the unit tests for the added function in TachyonURI. Could you please review it for me? Thanks a lot!
~t

+1 LGTM

One minor comment left. Thanks!

I just had a minor question about additional test cases. Thanks for the PR!

@gpang , wow, this is not a minor question, but a big one.
My previous assumption is that TachyonURI always represents an absolute path pointing to a file in Tachyon namespace, e.g.,
"/a/b/c"
or
"C:\a\b\b"
(as we will normalize the path when creating the URIs)
You point me that TachyonURI can also be something like "", ".", "a/b/c". In these cases, what files the URI points to? @_@ It seems the getLeadingPath() function cannot deal with these paths, as the semantic is undefined...

O, I didn't mean for it to be a major question. I just looked at some other ways to create a TachyonURI like in: isRootTests() and joinTests(). If TachyonURI just normalizes any input, then I think everything should still work, right?

so the paths such as "", ".", "a/b/c" can be generated into TachyonURI. These paths kind of breaks the semantics of functions such as getDepth() and getLeadingPath()
For example, the input "." represents the current directory.

I'm not sure what getLeadingPath() is used for, but does it make sense for it to return null in those cases?

Yes, currently "" (empty string) and "." returns null, but "a/b/c" returns the "leading path."
I will definitely add the test cases (thanks, @gpang !
I guess my question is more general as the abstraction of TachyonURI, and let me ask on the dev mailing list :-)

@gpang I got it. Basically the TachyonURI of Tachyon file is always in the form of "/a/b/c" since we use a Unix-style namespace for Tachyon FS. But as a URI, it could identify any name so "" (empty string) and "C:\a" should also be valid.
Test cases are added. Could you please review it?

Thanks for the info!

LGTM


Docs 'a a' fix #2

Docs change in order to kick devicelab to run tests for https://github.com/flutter/engine/pull/16436

We are holding off on flutter/engine#16436 so I will close this for now and use it to kick tests later.

This looks stale, so I'll close it. Feel free to re-open and resolve the merge conflict, though!


Proper message handling - A.K.A the path of the righteous message

@rozner Ditch events internally and adopt a callback based flow


enhancement - log tracking / reconn

I was reviewing the official golang project and some log tracking caught my eye.
You may consider cherry picking to catch bugs.
Go Language Server (Experimental)

To collect traces, set "go.languageServerFlags": ["-trace"]
To collect errors from language server in a logfile, set "go.languageServerFlags": ["-trace", "-logfile", "path to a text file that exists" ]

Pretty nice - it exposes the ability to execute methods of go code.

This project does not make use of the go language server. So I'm not sure how this is applicable. I'm going to close this as I'm not really sure what to do with this.

consider that langserver-swift should log stuff - and if it does already - there should be a debug flag to turn on and configure.

the intention being - if (and when) the langserver breaks - people can help report back the errors with logs and community can help - as opposed to it being a black box and it being a - fix it yourself scenario.


Fixed examples overflow

Added overflow to examples container to be able to scroll on them when the screen is small.

it seems that there are still some issues


Folder permissions

Description

could you recreate this PR and use another branch then master?

Sure
Relevant issues/tickets
https://github.com/grafana-operator/grafana-operator/pull/809

@Iridias I found the issue with the e2e test. It was a simple copy-paste issue containing the rbac settings.
I have done the same error and it's easy to make since you are normally running as a cluster-admin using the make run command.


Patch 1

@vivek-zanee reopen the pull request for patch-1, I accidentally merged the changes with the master branch.


feat: add read_from_path function for v1 tag

Hello
At first I was working with v2 tags on files, using read_from_path. But then when I started to dig into v1 tags, I found that the convenient read_from_path was missing for this version.
Therefore this PR adds it for consistency between v1 and v2 handling.

Thanks!


Slow operation for convolution

Did anyone encounter the same issue updating to the last version of DreamerV3?
2024-05-01 12:03:30.285255: E external/xla/xla/service/slow_operation_alarm.cc:65] Trying algorithm eng28{k2=3,k3=0} for conv (bf16[16,5,5,32]{3,2,1,0}, u8[0]{0}) custom-call(bf16[16,67,67,1024]{3,2,1,0}, bf16[32,63,63,1024]{3,2,1,0}), window={size=63x63 rhs_reversal=1x1}, dim_labels=b01f_o01i->b01f, custom_call_target="__cudnn$convForward", backend_config={"operation_queue_id":"0","wait_on_operation_queues":[],"cudnn_conv_backend_config":{"conv_result_scale":1,"activation_mode":"kNone","side_input_scale":0,"leakyrelu_alpha":0},"force_earliest_schedule":false} is taking a while...
2024-05-01 12:03:30.661234: E external/xla/xla/service/slow_operation_alarm.cc:133] The operation took 1.376059286s
Trying algorithm eng28{k2=3,k3=0} for conv (bf16[16,5,5,32]{3,2,1,0}, u8[0]{0}) custom-call(bf16[16,67,67,1024]{3,2,1,0}, bf16[32,63,63,1024]{3,2,1,0}), window={size=63x63 rhs_reversal=1x1}, dim_labels=b01f_o01i->b01f, custom_call_target="__cudnn$convForward", backend_config={"operation_queue_id":"0","wait_on_operation_queues":[],"cudnn_conv_backend_config":{"conv_result_scale":1,"activation_mode":"kNone","side_input_scale":0,"leakyrelu_alpha":0},"force_earliest_schedule":false} is taking a while...
2024-05-01 12:03:32.943688: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 0: 57856, expected 17152
2024-05-01 12:03:32.943700: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 1: 58112, expected 17664
2024-05-01 12:03:32.943703: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 2: 58112, expected 16768
2024-05-01 12:03:32.943704: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 3: 57856, expected 16896
2024-05-01 12:03:32.943706: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 4: 58112, expected 17024
2024-05-01 12:03:32.943708: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 5: 58112, expected 16768
2024-05-01 12:03:32.943710: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 6: 57856, expected 17152
2024-05-01 12:03:32.943711: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 7: 57856, expected 17024
2024-05-01 12:03:32.943714: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 8: 58112, expected 16768
2024-05-01 12:03:32.943716: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 9: 57856, expected 17280
2024-05-01 12:03:32.943719: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:747] Results mismatch between different convolution algorithms. This is likely a bug/unexpected loss of precision in cudnn.
(bf16[48,5,5,32]{3,2,1,0}, u8[0]{0}) custom-call(bf16[1024,33,33,32]{3,2,1,0}, bf16[1024,16,16,48]{3,2,1,0}), window={size=5x5 stride=2x2 pad=1_1x1_1}, dim_labels=b01f_o01i->b01f, custom_call_target="__cudnn$convBackwardFilter", backend_config={"operation_queue_id":"0","wait_on_operation_queues":[],"cudnn_conv_backend_config":{"conv_result_scale":1,"activation_mode":"kNone","side_input_scale":0,"leakyrelu_alpha":0},"force_earliest_schedule":false} for eng47{k0=9,k2=7,k5=4,k14=2} vs eng20{k2=7,k3=0}
2024-05-01 12:03:32.943723: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:307] Device: NVIDIA RTX 6000 Ada Generation
2024-05-01 12:03:32.943724: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:308] Platform: Compute Capability 8.9
2024-05-01 12:03:32.943727: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:309] Driver: 12040 (INVALID_ARGUMENT: expected %d.%d, %d.%d.%d, or %d.%d.%d.%d form for driver version; got "1")
2024-05-01 12:03:32.943729: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:310] Runtime: <undefined>
2024-05-01 12:03:32.943731: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:317] cudnn version: 8.9.2
2024-05-01 12:03:32.956910: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 0: 57856, expected 17152
2024-05-01 12:03:32.956914: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 1: 58112, expected 17664
2024-05-01 12:03:32.956916: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 2: 58112, expected 16768
2024-05-01 12:03:32.956918: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 3: 57856, expected 16896
2024-05-01 12:03:32.956919: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 4: 58112, expected 17024
2024-05-01 12:03:32.956921: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 5: 58112, expected 16768
2024-05-01 12:03:32.956923: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 6: 57856, expected 17152
2024-05-01 12:03:32.956924: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 7: 57856, expected 17024
2024-05-01 12:03:32.956926: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 8: 58112, expected 16768
2024-05-01 12:03:32.956928: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 9: 57856, expected 17280
2024-05-01 12:03:32.956931: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:747] Results mismatch between different convolution algorithms. This is likely a bug/unexpected loss of precision in cudnn.
(bf16[48,5,5,32]{3,2,1,0}, u8[0]{0}) custom-call(bf16[1024,33,33,32]{3,2,1,0}, bf16[1024,16,16,48]{3,2,1,0}), window={size=5x5 stride=2x2 pad=1_1x1_1}, dim_labels=b01f_o01i->b01f, custom_call_target="__cudnn$convBackwardFilter", backend_config={"operation_queue_id":"0","wait_on_operation_queues":[],"cudnn_conv_backend_config":{"conv_result_scale":1,"activation_mode":"kNone","side_input_scale":0,"leakyrelu_alpha":0},"force_earliest_schedule":false} for eng47{k0=9,k2=7,k5=4,k14=2} vs eng20{k2=6,k3=0}
2024-05-01 12:03:32.956935: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:307] Device: NVIDIA RTX 6000 Ada Generation
2024-05-01 12:03:32.956936: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:308] Platform: Compute Capability 8.9
2024-05-01 12:03:32.956938: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:309] Driver: 12040 (INVALID_ARGUMENT: expected %d.%d, %d.%d.%d, or %d.%d.%d.%d form for driver version; got "1")
2024-05-01 12:03:32.956941: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:310] Runtime: <undefined>
2024-05-01 12:03:32.956943: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:317] cudnn version: 8.9.2
2024-05-01 12:03:33.030591: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 0: 2320, expected 1056
2024-05-01 12:03:33.030599: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 1: 2336, expected 1048
2024-05-01 12:03:33.030601: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 2: 2320, expected 1048
2024-05-01 12:03:33.030603: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 3: 2320, expected 1056
2024-05-01 12:03:33.030605: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 4: 2320, expected 1032
2024-05-01 12:03:33.030606: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 5: 2320, expected 1048
2024-05-01 12:03:33.030608: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 6: 2304, expected 1064
2024-05-01 12:03:33.030609: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 7: 2304, expected 1040
2024-05-01 12:03:33.030612: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 8: 2320, expected 1040
2024-05-01 12:03:33.030614: E external/xla/xla/service/gpu/buffer_comparator.cc:151] Difference at 9: 2304, expected 1048
2024-05-01 12:03:33.030619: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:747] Results mismatch between different convolution algorithms. This is likely a bug/unexpected loss of precision in cudnn.
(bf16[64,5,5,64]{3,2,1,0}, u8[0]{0}) custom-call(bf16[1024,9,9,64]{3,2,1,0}, bf16[1024,4,4,64]{3,2,1,0}), window={size=5x5 stride=2x2 pad=1_1x1_1}, dim_labels=b01f_o01i->b01f, custom_call_target="__cudnn$convBackwardFilter", backend_config={"operation_queue_id":"0","wait_on_operation_queues":[],"cudnn_conv_backend_config":{"conv_result_scale":1,"activation_mode":"kNone","side_input_scale":0,"leakyrelu_alpha":0},"force_earliest_schedule":false} for eng10{k2=5,k12=6,k13=1,k14=3,k15=0,k17=7,k18=1,k23=0} vs eng20{k2=6,k3=0}
2024-05-01 12:03:33.030622: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:307] Device: NVIDIA RTX 6000 Ada Generation
2024-05-01 12:03:33.030624: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:308] Platform: Compute Capability 8.9
2024-05-01 12:03:33.030626: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:309] Driver: 12040 (INVALID_ARGUMENT: expected %d.%d, %d.%d.%d, or %d.%d.%d.%d form for driver version; got "1")
2024-05-01 12:03:33.030627: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:310] Runtime: <undefined>
2024-05-01 12:03:33.030630: E external/xla/xla/service/gpu/conv_algorithm_picker.cc:317] cudnn version: 8.9.2

Me too

I do get those as well sometimes. They are XLA/CUDA issues but I think they are usually just warnings. Does the code continue to run after compilation is done?
Otherwise, you can try adding --xla_gpu_autotune_level=0 to the XLA_FLAGS in dreamerv3/jaxagent.py or try updating JAX to the newest vesion.

Yes, the code continues to run but I wonder if it runs slower than it should. I am already using JAX last version (0.4.26).
I noticed a decreased in fps after this update but I am not sure if this is related to those errors/warnings.

The decreased FPS are probably because the model architecture is different now.
You can save some flops and memory by setting --'(enc|dec).simple.outer' False --'(enc|dec).simple.mults' 1,2,3,4 which gives very similar performance unless the images are visually more complex.
Closing this issue because those are XLA/CUDA warnings unrelated to Dreamer itself. I would also be happy if they got fixed.

For anyone interested, changing jax.compute_dtype from bfloat16 to float32 fixed the warnings for me.
However, using float32 is a little bit slower than bfloat16 going from 500 to 430 fps/policy on my hardware.


disable Heat/Cool Mode

Is it possible to (add an option to) disable Heat/Cool Mode? I.e. the thermostat should support heat or cool, but not Heat/Cool? Thanks!

Yes. If you don't set heat_cool_mode: true. Exactly that should happen.

Thanks! It seems the climate entity is nevertheless being set with a target_temp_low and a target_temp_high attribute, causing the thermostat to have two temperatures (although no heat/cool mode). Can that be disabled, too?

Please try to omit those attributes too.

I don't have them set - is there another way to remove them?
- platform: dual_smart_thermostat
  name: Boys Room
  heater: switch.boys_room_radiator
  cooler: switch.boys_room_air_conditioner
  target_sensor: sensor.boys_room_temperature_temperature
  min_cycle_duration: 60
  precision: .5
  min_temp: 20
  max_temp: 25
  away:
    temperature: 15

I cleared it for now by editing the entities attributes from the dev tools. Will that survive a reload?

It should


Map API unavailable

Calls to http://localhost/user/dev/api/v1/map result in Error 503 Service Unavailable XID:<PHONE_NUMBER> from varnish.
Calls to http://localhost/user/dev/api/v2/sql and http://localhost/user/dev/api/v1/imports/ (JSON is returned) as well as http://localhost/user/dev/api/v1/maps (routes pages or results) work.

Varnish doesn't seem to run: docker exec cartodb_1 wget http://localhost:3000 returns index.html but docker exec cartodb_1 wget http://localhost:6081 returns ERROR 404: Not Found.

http://localhost/user/dev/api/v1/map works with the 6 months image old image on dockerhub but not with the current master

It does work with the 3 months old sverhoeven/cartodb:py3pg12postgis3 on dockerhub

npm test in /Windshaft-cartodb with development.js as test.js logs
Mapnik LOG> 2020-06-02 15:24:28: Problem loading plugin library<EMAIL_ADDRESS>(dlopen failed - plugin likely has an unsatisfied dependency or incompatible ABI)
Mapnik LOG> 2020-06-02 15:24:28: Problem loading plugin library<EMAIL_ADDRESS>(dlopen failed - plugin likely has an unsatisfied dependency or incompatible ABI)

and two probably related errors in combination with redis.


libdl assembly failing to load on Ubuntu 22.04 during CI

The failure occurs on import ctypes which on initialization invokes _ctypes.dlopen. This fails with a SystemError.
On Mono:

SystemError: libdl assembly: type: member:(null)

On .NET:

SystemError: Unable to load shared library 'libdl' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:

Is it required for the "final" release?


content: Handle link previews

Fixes: #1016

Web
Flutter

Web (Small)
Flutter (Small)

Thanks for the initial comments @chrisbobbe! Pushed a new revision, PTAL.

What's a good way for me to test this; do I need to set up a dev server? 🙂 I see link previews are disabled on CZO; I've asked on CZO if there's a reason for that: https://chat.zulip.org/#narrow/channel/9-issues/topic/Link.20previews.20for.20Zulip.20URLs/near/2013846

Dev server, or make a test realm on Zulip Cloud.


[UI] Auto-Health bar segment adjustment

Would be nice to make a script that automatically sets the health bar segment length for heroes like Axe depending on the current level of Culling Blade, Oracle depending on his level of Purifying Flames, etc.

No. Do the math yourself. Closed.


Prevent loading a certain grid item to the next page.

I have div structure like this:

			THIS IS A TITLE

content

content

content

content

content

The div#title is a block that contains the navigation and suppose to be a title block which is included in the masonry. Now every time a new item loads, the title block also loads. How can I tell infinite scroll to not load it?
I'm using WordPress to load those .grid__item:

		<?php while ( have_posts() ) : the_post(); ?>
			<?php get_template_part( 'template-parts/content' ); ?>
		<?php endwhile; ?>

js from: https://codepen.io/desandro/pen/eRRQVo

I solved it.
I have to use .stamp instead of .grid__item

			THIS IS A TITLE


Etag mismatch

Etag mismatch during object_put of 69429/c0f76641hb0g/ocrALTO.xml into access-metadata: /crkn-nas-wip/_OCR//batch505heritage/69429%2Fc0f76641hb0g.xml=b4bd28649ec4ba79961226e0272b47bc 69429/c0f76641hb0g/ocrALTO.xml=d41d8cd98f00b204e9800998ecf8427e during tx2eedcb978aa342cda4a87-0064ff54df retries=5

https://github.com/crkn-rcdr/cihm-metadatabus/blob/46dc490270cff60dda24139274b5c7c1131d393b/CIHM-Meta/lib/CIHM/Meta/Ocrtask.pm#L595

https://docs.openstack.org/swift/latest/overview_large_objects.html


Fixed the metric context for accurte REST API Calls

Calls to display metrics are getting a 404 error because of a typo in the settings.

What do you mean by "accurate"?   I do not see a reason for this change, please explain.

If the environment variable ENV['METRICS_CONTEXT'] is not set then the metrics context should be set as /daq-api-1.0.0 which is what it is in Tomcat and not /daq-1.0.0 which gives a 404.

Please resubmit at https://github.com/oneops/oneops if necessary.


1252 - Cells with Odd Values in a Matrix

Description of the Problem
Given n and m which are the dimensions of a matrix initialized by zeros and given an array indices where indices[i] = [ri, ci]. For each pair of [ri, ci] you have to increment all cells in row ri and column ci by 1.
Return the number of cells with odd values in the matrix after applying the increment to all indices.
Example 1

Input: n = 2, m = 3, indices = [[0,1],[1,1]]
Output: 6
Explanation: Initial matrix = [[0,0,0],[0,0,0]].
After applying first increment it becomes [[1,2,1],[0,1,0]].
The final matrix will be [[1,3,1],[1,3,1]] which contains 6 odd numbers.

Example 2

Input: n = 2, m = 2, indices = [[1,1],[0,0]]
Output: 0
Explanation: Final matrix = [[2,2],[2,2]]. There is no odd number in the final matrix.

Constraints

1 <= n <= 50
1 <= m <= 50
1 <= indices.length <= 100
0 <= indices[i][0] < n
0 <= indices[i][1] < m

Code
class Solution:
    def oddCells(self, n: int, m: int, indices: List[List[int]]) -> int:

Link To The LeetCode Problem
LeetCode

Hey, is this issue still open?


[RSP - NumberField] Events are not triggered

🐛 Bug Report

🤔 Expected Behavior
General input event handlers are triggered appropriately

😯 Current Behavior
onBlur, onFocus, onFocusChange are not being triggered correctly
see example here
💁 Possible Solution

🔦 Context
The NumberField input should update the page context, but there's no need to update the context onChange, ideally we update it once onBlur
  const [value, setValue] = React.useState(0);

  const updateContext =() => {
    pageContext.update({number: value})
  }

  return (
      <NumberField
        label="Events example"
        minValue={0}
        value={value}
        onChange={setValue}
        onBlur={updateContext}
      />);

💻 Code Sample
CodeSandbox
🌍 Your Environment

Software
Version(s)

react-spectrum
3.8.0

react-spectrum/numberfield
3.0.0-alpha.1

Browser
Chrome Version 89.0.4389.82 (Official Build) (x86_64)

Operating System
MacOS Big Sur 11.1

🧢 Your Company/Team
Adobe / Commerce Cloud
🕷 Tracking Issue (optional)

Update:
useNumberInput was missing useFocusable as mentioned by Kyle above, we need to call it, pass it props and inputRef, then merge it with the other props.
@ktabors has a working solution, we should have a PR ready soon 🙂


Incompatible or Mismatched C/C++ Extension Binaries

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

/extC++

@gjsjohnmurray Our C/C++ has verified that our extension is correctly published to the marketplace with the correct binary -- our guess is that there is some VS Code or marketplace bug that is causing the wrong vsix to sometimes be installed.

@gjsjohnmurray Users are able to download/install our vsix manually from https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools or https://github.com/microsoft/vscode-cpptools/releases/tag/v1.10.5 so the bug appears to be with VS Code and/or the Remote WSL extension.

@eshaved78 If you can let us know what the remote OS is and what the TargetPlatform property is set to in the .vscode-server[-insiders]/extensions/ms-vscode.cpptools-[version][os-description]/.vsixmanifest file that could help us identify the problem.


Change JSON and CSV read double config

set spark.rapids.sql.json.read.double.enabled
and spakr.rapids.sql.csv.read.double.enabled true by default
Close https://github.com/NVIDIA/spark-rapids/issues/5813
Signed-off-by: gashen<EMAIL_ADDRESS>

Is this a duplicate of https://github.com/NVIDIA/spark-rapids/pull/5935 ?
cc: @razajafri

Is this a duplicate of #5935 ?
cc: @razajafri

Yes, looks like it is. You can decide which one to close

Closed because duplicated


Collect Hive column statistics on write by default

@electrum you may want to remove hive.collect-column-statistics-on-write=true from product tests configs, as this is redundant now


Update kube-apiserver.manifest.j2 and kubeadm-config.yaml.j2

Ensure that kube-apiserver and kubeadm will respond even if one of the nodes are down.

Please sign CLA

I just signed the CLA...

Please add the same option to kubeadm

I don't know which file you are talking about?

See https://github.com/kubernetes-incubator/kubespray/blob/master/roles/kubernetes/master/templates/kubeadm-config.yaml.j2

ci check this

looks like it passed

default value is "master-count". Could you configure it as a variable, set it to the default and allow for override in the k8s-cluster file


Fix modulesync

Fixes #408

@bastelfreak could you please have a look at this.

I'll also note that our current modulesync config is at 5.3.0 so perhaps you could also include that. If you need help with that, please let me know.

@ekohl I have fixed your comments now and I had a look at https://github.com/voxpupuli/modulesync_config to see if I could fix  that as well.
I think I need some help with this ..

Hmm, it seems like puppet-logstash is missing in https://github.com/voxpupuli/modulesync_config/blob/master/managed_modules.yml

@ekohl, @bastelfreak Could you please have another look at this?
I think it would be smart to get this merged before the 5.4.0 release of modulesync.

Should README.md have been updated according to the elastic -> voxpupuli transition and logstash version constraints adjusted to supported versions?

@h-haaks yes (in a separate pull request).

The differences between 5.3.0 and 5.4.0 are trivial so I'd include that here.

Is it ok to run msync from the master branch before the 5.4.0 tag is created?

Generally I'm not too happy about making changes in the code itself in a modulesync PR, but if it gets the module moving forward I'm happy to approve.

I do agree. All of this is just parts of transitioning this module into voxpupuli, I think. The modulesync commits are just part of that.
I'll gladly change the title to something like 'Get module to build with voxpupuli'.

Is it ok to run msync from the master branch before the 5.4.0 tag is created?

I think @bastelfreak forgot to push a tag because he did create https://github.com/voxpupuli/modulesync_config/commit/2f1495fadadb102d600a4093e06368ea89684f33 so just go for it.

@ekohl I don't have write access to the repository. Could you please merge this PR?

Thanks for taking this over the finish.


State machine expansion

Merging the last of Håvard's work, which should leave a good baseline for next year's team. Currently has some merge conflicts that need to be resolved, I'll get back to it!

Closing in favor of the new state machine expansion branch


Possible typo in the paper

Thanks for sharing MOTSynth dataset and the corresponding code!
I have one minor comment for the paper.  On paper P7 section 4.4. Multi-object Tracking left-column Results paragraph, the paper says "we obtain 45.0 MOTA and 51.2 IDF1 with our MOTSynth trained model, yielding +3.5 MOTA and +1.6 IDF1 improvement over the COCO trained model (43.5 MOTA and 49.6 IDF1).". Does it seem the improvement on MOTA should be +1.5 MOTA?
Thank you!

Hi, thanks for your interest in our paper!
You're right about the typo, good catch! We will update the text in a future arXiv update.
Thanks again,
Guillem


PyTTI-Tools: FiLM.ipynb - doesn't start

Interpolate!
Results will be saved in a subdirectory of frames_dir named "interpolated_frames"

2022-09-26 11:42:18.966 | INFO     | main::6 - Beginning interpolation...
2022-09-26 11:42:23.017 | DEBUG    | main:_run_pipeline:171 - ['frames']
W0926 11:42:23.081343<PHONE_NUMBER>07488 environments.py:374] Make sure that locally built Python SDK docker image has Python 3.7 interpreter.
I0926 11:42:23.081508<PHONE_NUMBER>07488 environments.py:380] Default Python SDK image for environment is apache/beam_python3.7_sdk:2.34.0
I0926 11:42:23.106427<PHONE_NUMBER>07488 translations.py:678] ==================== <function annotate_downstream_side_inputs at 0x7f7fc35227a0> ====================
I0926 11:42:23.106673<PHONE_NUMBER>07488 translations.py:678] ==================== <function fix_side_input_pcoll_coders at 0x7f7fc35228c0> ====================
I0926 11:42:23.106805<PHONE_NUMBER>07488 translations.py:678] ==================== <function pack_combiners at 0x7f7fc3522dd0> ====================
I0926 11:42:23.107073<PHONE_NUMBER>07488 translations.py:678] ==================== <function lift_combiners at 0x7f7fc3522e60> ====================
I0926 11:42:23.107178<PHONE_NUMBER>07488 translations.py:678] ==================== <function expand_sdf at 0x7f7fc3523050> ====================
I0926 11:42:23.107293<PHONE_NUMBER>07488 translations.py:678] ==================== <function expand_gbk at 0x7f7fc35230e0> ====================
I0926 11:42:23.107396<PHONE_NUMBER>07488 translations.py:678] ==================== <function sink_flattens at 0x7f7fc3523200> ====================
I0926 11:42:23.107529<PHONE_NUMBER>07488 translations.py:678] ==================== <function greedily_fuse at 0x7f7fc3523290> ====================
I0926 11:42:23.107744<PHONE_NUMBER>07488 translations.py:678] ==================== <function read_to_impulse at 0x7f7fc3523320> ====================
I0926 11:42:23.107830<PHONE_NUMBER>07488 translations.py:678] ==================== <function impulse_to_input at 0x7f7fc35233b0> ====================
I0926 11:42:23.107934<PHONE_NUMBER>07488 translations.py:678] ==================== <function sort_stages at 0x7f7fc35235f0> ====================
I0926 11:42:23.108054<PHONE_NUMBER>07488 translations.py:678] ==================== <function setup_timer_mapping at 0x7f7fc3523560> ====================
I0926 11:42:23.108170<PHONE_NUMBER>07488 translations.py:678] ==================== <function populate_data_channel_coders at 0x7f7fc3523680> ====================
I0926 11:42:23.108772<PHONE_NUMBER>07488 statecache.py:172] Creating state cache with size 100
I0926 11:42:23.109313<PHONE_NUMBER>07488 worker_handlers.py:894] Created Worker handler <apache_beam.runners.portability.fn_api_runner.worker_handlers.EmbeddedWorkerHandler object at 0x7f7fc2f0d390> for environment ref_Environment_default_environment_1 (beam:env:embedded_python:v1, b'')
I0926 11:42:23.109435<PHONE_NUMBER>07488 fn_runner.py:607] Running (((ref_AppliedPTransform_Create-directory-names-Impulse_3)+(ref_AppliedPTransform_Create-directory-names-FlatMap-lambda-at-core-py-3222-_4))+(ref_AppliedPTransform_Create-directory-names-Map-decode-_6))+(ref_AppliedPTransform_Process-directories_7)
2022-09-26 11:42:25.948001: W tensorflow/core/common_runtime/gpu/gpu_bfc_allocator.cc:39] Overriding allow_growth setting because the TF_FORCE_GPU_ALLOW_GROWTH environment variable is set. Original config value was 0.
2022-09-26 11:42:29.362 | DEBUG    | main:process:158 - 0 frames detected.
I0926 11:42:29.363154<PHONE_NUMBER>07488 interpolator_cli.py:159] Generating in-between frames for frames.
Traceback (most recent call last):
File "apache_beam/runners/common.py", line 1233, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 572, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/interpolator_cli.py", line 162, in process
input_frames, _TIMES_TO_INTERPOLATE.value, self.interpolator))
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/util.py", line 122, in interpolate_recursively_from_files
yield util.read_image(frames[-1])
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/interpolator_cli.py", line 187, in
app.run(main)
File "/usr/local/lib/python3.7/dist-packages/absl/app.py", line 308, in run
_run_main(main, args)
File "/usr/local/lib/python3.7/dist-packages/absl/app.py", line 254, in _run_main
sys.exit(main(argv))
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/interpolator_cli.py", line 183, in main
_run_pipeline()
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/interpolator_cli.py", line 176, in _run_pipeline
result = pipeline.run()
File "/usr/local/lib/python3.7/dist-packages/apache_beam/pipeline.py", line 573, in run
return self.runner.run_pipeline(self, self._options)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/direct/direct_runner.py", line 131, in run_pipeline
return runner.run_pipeline(pipeline, options)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 196, in run_pipeline
pipeline.to_runner_api(default_environment=self._default_environment))
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 206, in run_via_runner_api
return self.run_stages(stage_context, stages)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 385, in run_stages
runner_execution_context, bundle_context_manager)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 653, in _run_stage
bundle_manager))
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 770, in _run_bundle
data_input, data_output, input_timers, expected_timer_output)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 1080, in process_bundle
result_future = self._worker_handler.control_conn.push(process_bundle_req)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/portability/fn_api_runner/worker_handlers.py", line 378, in push
response = self.worker.do_instruction(request)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/worker/sdk_worker.py", line 598, in do_instruction
getattr(request, request_type), request.instruction_id)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/worker/sdk_worker.py", line 635, in process_bundle
bundle_processor.process_bundle(instruction_id))
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/worker/bundle_processor.py", line 996, in process_bundle
element.data)
File "/usr/local/lib/python3.7/dist-packages/apache_beam/runners/worker/bundle_processor.py", line 221, in process_encoded
self.output(decoded_value)
File "apache_beam/runners/worker/operations.py", line 352, in apache_beam.runners.worker.operations.Operation.output
File "apache_beam/runners/worker/operations.py", line 354, in apache_beam.runners.worker.operations.Operation.output
File "apache_beam/runners/worker/operations.py", line 216, in apache_beam.runners.worker.operations.SingletonConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 713, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 714, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1235, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1300, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1233, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 571, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "apache_beam/runners/common.py", line 1396, in apache_beam.runners.common._OutputProcessor.process_outputs
File "apache_beam/runners/worker/operations.py", line 216, in apache_beam.runners.worker.operations.SingletonConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 713, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 714, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1235, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1300, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1233, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 571, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "apache_beam/runners/common.py", line 1396, in apache_beam.runners.common._OutputProcessor.process_outputs
File "apache_beam/runners/worker/operations.py", line 216, in apache_beam.runners.worker.operations.SingletonConsumerSet.receive
File "apache_beam/runners/worker/operations.py", line 713, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/worker/operations.py", line 714, in apache_beam.runners.worker.operations.DoOperation.process
File "apache_beam/runners/common.py", line 1235, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 1316, in apache_beam.runners.common.DoFnRunner._reraise_augmented
File "apache_beam/runners/common.py", line 1233, in apache_beam.runners.common.DoFnRunner.process
File "apache_beam/runners/common.py", line 572, in apache_beam.runners.common.SimpleInvoker.invoke_process
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/interpolator_cli.py", line 162, in process
input_frames, _TIMES_TO_INTERPOLATE.value, self.interpolator))
File "/usr/local/lib/python3.7/dist-packages/frame_interpolation/eval/util.py", line 122, in interpolate_recursively_from_files
yield util.read_image(frames[-1])
IndexError: list index out of range [while running 'Process directories']
2022-09-26 11:42:30.928 | INFO     | main::14 - Interpolation comlpete.

GPU issue. Solve: Runtime -> Change Runtime type -> GPU

Thanks updating with the fix.


Fix alphabetization in data/moves.js

Moves are listed alphabetically; this pull request corrects some apparent mistakes:

Now it should be ready for review, @scheibo. Hopefully I didn't forget one.
There are 17 isNonstandard moves, only three were listed at the end of the file, therefore I alphabetized those as well.

Thanks!

All isNonstandard moves should be at the end of the file. There should also not be 17 isNonstandard moves...

Oh, the others are LGPE moves. Only custom moves isNonstandard: "Custom" should be at the end of the file. They're placed correctly.


datapath: move policy map value prefix length to flags

Move the prefix length field in the policy map value to the flags (same byte as 'deny') to a previously unused space. This cleans up padding space for future use.
Skip map entries with inconsistent prefix length field in value vs. key so that the entry will be rewritten with the correct prefix length field in the value. This fixes a potential issue in upgrade where a policy map entry may remain with zero valued prefix length in value leading to incorrect policy enforcement.
Fixes: #35150

/test


Invalid Props on div element

When using the component React fires an
Unknown props callback, expiredCallback, locale on <div> tag. Remove these props from the element.
Warning. This is due to the way that the component props are passed down to the actual div element without stripping the purely functional component props.

Thanks for reporting this warning. We could simply omit those two props something like:
const { className, sitekey, callback, expiredCallback, ...otherProps } = this.props;

So that Unknown props will not automatically be passed down to the div through ...otherProps .
I may release a new version with this change tomorrow when I am able to access to internet on my computer. :)

Just saw your comment. I have done it using lodash's omit in order to cover potential other props in the future gracefully without changing the code. Will file a pull request in a bit.


update version on pypi

The version currently available on pypi force-downgrades several packages.  It would be nice to update to the current version on pypi, which has fixed requirements.txt, so this doesn't happen anymore.

Sorry about this. I'll update the release on pypi next week (need help from a coworker because I don't have access). In the meantime you should just install from github instead with pip install git+https://github.com/quantopian/qgrid

This is fixed in release 0.3.2, which is now available on pypi.


Castbox.fm not working

Castbox.fm control is not working... any help?

Works fine for me on Chromium: 73.0.3683.75 (Official Build) (64-bit)

It still doesn't work for me - MacOS Mojave 10.14.3, Chrome 73.0.3683.75 (Official Build) (64-bit)
Castbox.fm isn't even detected by the extension itself...

Maybe it's OS specific? I'm on win 8.1.
Can you post the output from the console?

Sure, the content from the regular developer tools console or is it something else?

Screenshot -> https://jmp.sh/4TPssIl

Thank you. It confirms what you were saying about Keysocket not firing at all. The console should at least have something like keysocket: plugin castbox loaded.
If you right-click on the keysocket icon in Chrome, and select "This can read and change site data >" - what does it say there?

Here it is: https://jmp.sh/BQCAWJ1

That is weird. And it works on other sites - like soundcloud?

Soundcloud and Youtube... no problems at all

Youtube example: https://jmp.sh/BX3HBM7

That is so weird. I don't have a mac to test on, so I can't help unfortunately. If anybody else on mac os could confirm if this os specific, that would be helpful.

I also have this issue. Works fine on google music, doesn't work at all on castbox.


Provide Stack support?

I have experimented with using HMock with Stack, and I get the following error when using GHC 8.6 and 8.8:
/tmp/stack-b8726112c6310f6a/HMock-<IP_ADDRESS>/src/Test/HMock/Internal/State.hs:202:7: error:
    • Couldn't match type ‘MockT m’ with ‘ReaderT (MockState m) m’
        arising from the coercion of the method ‘unliftio-core-<IP_ADDRESS>:Control.Monad.IO.Unlift.askUnliftIO’
          from type ‘ReaderT
                       (MockState m)
                       m
                       (unliftio-core-<IP_ADDRESS>:Control.Monad.IO.Unlift.UnliftIO
                          (ReaderT (MockState m) m))’
            to type ‘MockT
                       m
                       (unliftio-core-<IP_ADDRESS>:Control.Monad.IO.Unlift.UnliftIO (MockT m))’
    • When deriving the instance for (MonadUnliftIO (MockT m))
    |
202 |       MonadUnliftIO
    |       ^^^^^^^^^^^^^

I do not know why I get this error when using Stack but not Cabal, as I use the same version of relevant packages in both cases.  Do you know what might be causing this?
I was able to get around this error by writing the instance for MonadUnliftIO manually instead of deriving it:
instance MonadUnliftIO m => MonadUnliftIO (MockT m) where
  withRunInIO inner = MockT $ withRunInIO $ \run -> inner (run . unMockT)

If you would like to include this change for better Stack support, I am happy to create a pull request.

The following are my Stack configurations for a project that uses HMock.  (For the HMock package itself, the HMock-<IP_ADDRESS> dependency would need to be removed and the doctest dependencies would need to be added.  I can provide these files if wanted.)
GHC 8.6.5:
resolver: lts-14.27

packages:
  - .

extra-deps:
  - binary-<IP_ADDRESS>
  - constraints-0.13
  - containers-<IP_ADDRESS>
  - explainable-predicates-<IP_ADDRESS>
  - extra-1.7.10
  - HMock-<IP_ADDRESS>
  - regex-base-<IP_ADDRESS>
  - regex-tdfa-<IP_ADDRESS>
  - syb-<IP_ADDRESS>
  - text-<IP_ADDRESS>
  - type-equality-1
  - unliftio-0.2.20

GHC 8.8.4:
resolver: lts-16.31

packages:
  - .

extra-deps:
  - constraints-0.13
  - explainable-predicates-<IP_ADDRESS>
  - HMock-<IP_ADDRESS>
  - syb-<IP_ADDRESS>
  - unliftio-0.2.20

GHC 8.10.7:
resolver: lts-18.12

packages:
  - .

extra-deps:
  - explainable-predicates-<IP_ADDRESS>
  - HMock-<IP_ADDRESS>

GHC 9.0.1:
resolver: nightly-2021-10-01

packages:
  - .

(Update: HMock and explainable-predicates are included in nightly-2021-10-01! :+1: )

I don't know what might be causing this, but I'm happy to merge the change.  I'll do that today and put out a point release.

Sounds good.  Thanks!
I created a pull request that includes a comment to make it clear why the instance is defined manually, including version numbers to track when the change can be reverted if/when GHC 8.6 and 8.8 are no longer supported at some point in the future.
I did not include the Stack configuration files.  I use the following files for testing:

stack-8.6.5.yaml
stack-8.8.4.yaml
stack-8.10.7.yaml
stack-9.0.1.yaml
stack.yaml is a symbolic link pointing to the default configuration (stack-8.10.7.yaml)

These files somewhat clutter the project directory.  If you would like to easily test with Stack, however, let me know if you would like me to commit them.

Thanks!  I'd rather not include the stack config files in the directory.  In my experience, it causes HLS to choose stack to build during development, and that makes things a bit clunkier.  Happy to address any future stack issues that come up, though.


Marginal Costs in the NKPC in the One-Asset HANK Example

Hey, I was wondering whether in the example of the one-asset HANK model the marginal costs in the Phillips Curve should be specified as $\frac{w_t}{z}$ rather than only $w_t$? If so, then we would have $mc_t = \frac{w_t}{z}$ and in steady state: $mc_{ss} = \frac{\theta - 1}{\theta}$ and $w_{ss} = mc_{ss}*z$, correct? Changing this had for me only a small effect anyway, but perhaps for some nevertheless important (whenever $z \ne 1$).

Yes, absolutely!
Thanks for pointing this out, should be more relevant for technology shocks.
Are you willing to make a PR?

Yes, will do! Thank you.

Wonderful. Thanks for #10 !


making DefaultHttpDataFactory able to configure basedir and deleteonexit

Motivation: currently (http) disk based attributes or uploads are globally configured in a single directory and can also only globally be deleted on exit or not. it does not fit well multiple cases, in particular the case you have multiple servers in the same JVM.
Modification: make it configurable per attribute/fileupload.
This PR duplicates Disk* constructor to add basedir and deleteonexit parameters and wires it in default http daa factory.

@netty-bot test this please

@netty-bot test this please

@rmannibucau please sign our ICLA and let me know once done:
https://netty.io/s/icla

@normanmaurer done

@rmannibucau thanks!


[RESOLVED] S100-Primario has been restarted (uptime < 10m)

Problem started at 16:43:31 on 2023.06.03
Problem name: S100-Primario has been restarted (uptime < 10m)
Host: S100-Primario
Severity: Warning
Operational data: 00:06:02
Original problem ID: 23233
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23452&eventid=23233

Problem has been resolved in 3m 58s at 16:47:29 on 2023.06.03
Problem name: S100-Primario has been restarted (uptime < 10m)
Host: S100-Primario
Severity: Warning
Original problem ID: 23233


Weight not supported for text indexes

Hey @Joannis,
I noticed weights are not supported for text indexes. I thought I can do a PR to fix this up, but there seems to be a note about it above. Any brief details you want to shoot over before I create one to potentially avoid some incorrect / wasted work?
https://github.com/OpenKitten/MongoKitten/blob/7cece593d3421f103cbb183b15f8091218fd72a2/Sources/MongoKitten/Querying/Index.swift#L139
Thanks

I don't think there's anything special you'd need to know. A PR would be awesome!


Preview for tables in markdown files is incorrect

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T17:15:57.756Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

vscode-docker
Pet
0.0.16

vscode-eslint
dba
1.2.11

tslint
eg2
0.17.0

Go
luk
0.6.63

debugger-for-chrome
msj
3.2.0

java
red
0.8.0

Markdown preview broken for tables.
Steps to Reproduce:

Create a markdown file with following contents.
Note: there are 3 spaces before start of table.

Heading
=======
   |Word |Vowel Count|
   |------|----------|
   |Rhythm|0         |
   |Mingle|2         |

The preview for the file does not show the first column in the table.

If there are no spaces included before the start of table pipe, the preview of table is rendered correctly.
Whereas if there are spaces, the table rendering is broken. The contents of the first column is pushed to second column.

Reproduces without extensions: Yes

We use markdown-it, and the table seems to work fine on the current markdown-it page: https://markdown-it.github.io I suspect we may just need to bump our markdown-it version

Should be fixed in first 1.17 insiders:


Anti-virus reporting infection in evernote-backup portable for Windows x64

I downloaded the ZIP package containing the current portable installer for Evernote-Backup and evernote-backup.exe is immediately quarantined with a report that it is infected with: Beareuws.A!ml
I'm hoping it is a false positive but just providing a heads up.

What AV are you using?
Anyway it is false positive. It's easy to peruse the source for malicious code if you don't trust it.
Maybe it happens because of pyinstaller packaging and the fact that exe is not signed. yt-dlp faced the same issue for example.
Will try to upgrade pyinstaller for next build to reduce the number of false detections.
Current status for 1.9.2:
Virustotal for evernote-backup.exe 1.9.2 x86 7/70
Virustotal for evernote-backup.exe 1.9.2 x64 2/70

The error was from Microsoft Antivirus.
As I said, I anticipated it would be a false positive. Just providing a heads up.


New top level icon.

Ok, I was asked to deliver this icon through a pull request, so if you don't want it I guess we can close this pull request.


chore: release main

:robot: I have created a release beep boop
codegen: 0.6.1
0.6.1 (2023-08-08)
Bug Fixes

generics: change Deserialize<'static> bounds to DeserializeOwned (#259) (8015063)

Dependencies

The following workspace dependencies were updated

dependencies

examples bumped from 0.3.0 to 0.3.1

dev-dependencies

substrate bumped from <=0.6.0 to <=0.6.1
sky130pdk bumped from <=0.6.0 to <=0.6.1
spectre bumped from <=0.6.0 to <=0.6.1

examples: 0.3.1
Dependencies

The following workspace dependencies were updated

dev-dependencies

substrate bumped from <=0.6.0 to <=0.6.1
sky130pdk bumped from <=0.6.0 to <=0.6.1
spectre bumped from <=0.6.0 to <=0.6.1

sky130pdk: 0.6.1
Dependencies

The following workspace dependencies were updated

dependencies

substrate bumped from 0.6.0 to 0.6.1
spectre bumped from 0.6.0 to 0.6.1

spectre: 0.6.1
Dependencies

The following workspace dependencies were updated

dependencies

substrate bumped from 0.6.0 to 0.6.1

substrate: 0.6.1
0.6.1 (2023-08-08)
Bug Fixes

generics: change Deserialize<'static> bounds to DeserializeOwned (#259) (8015063)

Dependencies

The following workspace dependencies were updated

dependencies

examples bumped from 0.3.0 to 0.3.1
codegen bumped from 0.6.0 to 0.6.1

dev-dependencies

sky130pdk bumped from <=0.6.0 to <=0.6.1
spectre bumped from <=0.6.0 to <=0.6.1

tests: 0.0.0
Dependencies

The following workspace dependencies were updated

dependencies

substrate bumped from 0.6.0 to 0.6.1
spectre bumped from 0.6.0 to 0.6.1
sky130pdk bumped from 0.6.0 to 0.6.1

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/codegen-v0.6.1 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/examples-v0.3.1 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/sky130pdk-v0.6.1 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/substrate-v0.6.1 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/spectre-v0.6.1 :sunflower:


evolution-data-server: 3.36.3 -> 3.36.4

Motivation for this change
Version bump for evolution-data-server.
Evolution-Data-Server 3.36.4 2020-07-03
---------------------------------------

Bug Fixes:
	I#215 - Utilize If-None-Match header for WebCal refresh (Milan Crha)
	I#222 - Camel: Match-All condition doesn't show any messages (Milan Crha)
	I#226 - CVE-2020-14928: Response Injection via STARTTLS in SMTP and POP3 (Milan Crha)
	I#228 - Restarting evolution-source-registry re-enables user-disabled CalDAV accounts (Milan Crha)
	evo-I#982 - 'Message contains'-search broken in 3.36.3 (Milan Crha)

Miscellaneous:
	camel-folder-search: Fix a memory leak when searching message body (Milan Crha)
	Rename camel_stream_buffer_truncate() to camel_stream_buffer_discard_cache() (Milan Crha)

Translations:
	Baurzhan Muftakhidinov (kk)

Things done

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

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

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

Thanks.


15.3. Counting majority (Optimal Approach Moors voting algorithm)

My code is clear and well understanding
Please assign it to me

Need to add a description and your approach. Thanks, Closing as of now.


Add unique label on flags

Description
For now we only have one way to find a Flag: the description.
But description are not unique and very volatile and should not be used to find a precise Flag imo.
ID aren't good enough too since they're linked to the database and they change accross Flagr instances (e.g staging/production). An unique label fixes all of these issues.
I'm not good with the Vue frontend don't hesitate to push a commit on this PR to improve it.
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #148 into master will increase coverage by 0.03%.
The diff coverage is 100%.

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

Unique lable or more precisely - unique flag_key has its own pros/cons too.

flag_key should be immutable, which makes it hard to name it right at the beginning. The combination of ID + description fixes it, so we can benefit from ID's immutablibility and description's flexibility.
We have some considerations on the request/response payload size, for example, sending ~1000 flags to the batch evaluation endpoint, the string key size is significant larger than integers. This batch pattern is also used for mobile app's A/B testing, and it loads all the feature flags at the bootstrap time.

The downside of IDs is that they are sequential, which makes it hard to link across multiple environments. Although it's addressable, for example, use a read-replica db for staging, or leverage a prod/staging manifests in code that map the features into flag ids - it's possible that you may already have that configuraiton file (mapping features to flag_ids) in code.

Thanks for the answer! I opened the PR to start the discussions I appreciate the insights.
I agree on all your points except that I still think that another non-db-sequential immutable key is still needed.
we actually don’t really need for it to be a string another integer should do the job without growing the response size too much and that also fix the naming issue.
I’m not sure I understand your last point, for now I’m mapping features to flag descriptions since I can’t know for sure the ID of the flag.
Hope we can find a solution 😊
Anyway thanks for project!

That would be useful!

I’m not sure I understand your last point, for now I’m mapping features to flag descriptions since I can’t know for sure the ID of the flag.

Thanks for the discussion @vayan!
I'm interested in why you don't know the flag ID before implementing the feature. It's possible something I didn't consider before, but for us, it's very common that we just go ahead create the flag first, and then implement the feature and refer the flag ID created before.

why you don't know the flag ID before implementing the feature

It's mostly because I don't know on which database my code will be run against so I have no control over the IDs.
There's also the case of integration testing, I'm creating/deleting lot of flags on the fly which again change the IDs a lot.
If when I create a flag I could set an unique identifier I would not have to care about databases id increments and stuff 😄

@vayan we had the same issue and one of the ideas at the time was to just use the GET findFlags endpoint with the description_like field and the identifier...

@marceloboeira That's what I'm doing right now too 😄 but the description is so easily editable and not unique, it's kind of flaky

Related to https://github.com/checkr/flagr/pull/154
I know it won't address all the cons of not having unique string based IDs, hopefully it will make setting up Flagr in tests or staging easier.
Back to the story of unique labels. If your code doesn't know which database is running, it requires not only CRUD endpoints to support unique lables, but also the evaluation endpoints, right? That requires a change for example,
curl --request POST \
       --url https://try-flagr.herokuapp.com/api/v1/evaluation \
       --header 'content-type: application/json' \
       --data '{
           "entityID": "127",
           "entityType": "user",
           "entityContext": {
             "state": "NY"
           },
           "flagID": 1,
           "flagKey": "some_flag_key",   <-- (or flagLable, and we need to check if the payload has either ID or Key)
           "enableDebug": true
       }'

Also, this applies to not only flags, but also all the modes. May be we can change the base gorm model for all the entities later, for example, adding a unique Key field for every entity.

but also the evaluation endpoints, right?

Right! I didn't want to change everything in the same PR 😄

for example, adding a unique Key field for every entity.

Sure, but adding one to the Flag can be a start, that way we'd be able to evaluate them without the DB ID.

Hi @vayan
Yesterday, I was just about to approve this pr, but figured out there are so many moving parts for this change, thus I created another pr that adds the same thing (including all endpoints affected by flagKey), just the naming will be key not label, since we are already using key for variants.
https://github.com/checkr/flagr/pull/159


Automated cherry pick of #245: fix: always requeue with the latest object

Cherry pick of #245 on release-0.1.
#245: fix: always requeue with the latest object
For details on the cherry pick process, see the cherry pick requests page.

wait... commit the bash script separately :)

wait... commit the bash script separately, into the main branch :)

I'm just trying with the bash. sorry
/hold

/hold cancel


[3/4] - lnwallet/chancloser: add new protofsm based RBF chan closer

Overview
In this PR, we add a new RBF based co-op channel close state machine. This uses the new protofsm package to define the states and transitions for the state machine. The new state machine is then also updated to become a peer.MsgEndpoint which allows us to use the new peer.MsgRouter to handle all message dispatch into the state machine. A series of new wrapper structs (taking care to always accept interfaces to decouple from the concrete types) are created to be able to initialize the environment needed by the new state machine.
This PR doesn't yet include integration within the peer struct. That will come in a follow up PR as we need some additional changes to be able to handle the two possible co-op types that will exist.
The diff might look somewhat large, but over half of it us unit tests, and a large portion of the non-test diff is the new state and event declarations.
State Machine Flow
The new state machine can be modeled with the following diagram:
---
title: Co-Op Close V2
---
stateDiagram-v2
    state CoopCloseV2 {
    [*] --> ChannelActive
    ChannelActive --> ShutdownPending: send_shutdown
    ChannelActive --> ShutdownPending: shutdown_received

	ShutdownPending --> ChannelFlushing: shutdown_received
    ShutdownPending --> ChannelFlushing: shutdown_complete

    ChannelFlushing --> ClosingNegotiation: channel_flushed

    state ClosingNegotiation {
		direction TB
        [*] --> LocalCloseStart
        [*] --> RemoteCloseStart

        LocalCloseStart --> LocalOfferSent: send_offer
        LocalOfferSent --> ClosePending: local_sig_received

        RemoteCloseStart --> ClosePending: offer_received
    }

    ClosingNegotiation --> ShutdownPending: send_shutdown
    ClosingNegotiation --> ShutdownPending: shutdown_received

    ClosingNegotiation --> CloseFin: txn_confirmation
    }

Remaining TODOs

[x] unit tests for the state machine
[ ] commit the above diagram and a msg flow diagram to repo as documentation

Fixes https://github.com/lightningnetwork/lnd/issues/7091

Hi @Roasbeef can you please explain the scenario where you're expecting the state to transition back from ClosingNegotiation to ShutdownPending?
Given the channel flushing has already happened before the state moved to ClosingNegotiation, what would be the scenario where that step would need to be executed again?

@saubyk good question, so I need to update the diagram slightly, but you're right in that at that point the channel is already flushed. With the code that's checked in, there's a special fast path that'll transition from ChannelActive all the way to ClosingNegotiation if we detect that the channel is already flushed. It'll already be flushed if we're doing an RBF iteration, or if we're reconnecting and want to resume the closing process.
Here's the location of one of the fast path transitions:

https://github.com/lightningnetwork/lnd/blob/c273bb4755a43e675d4f538c9fdad1b74f713690/lnwallet/chancloser/rbf_coop_transitions.go#L350-L364

So in that case we sent shutdown, received it, then rather than wait in the ChannelFlushing state, we'll emit an internal event to have us go directly to the ChannelNegotiation phase.
Also just to clarify, the way the protocol works is that when either side wants to do a new RBF iteration (RBF their closing txn), they send the shutdown message again. You effectively can drop all state, then act as if you're closing for the first time. Reading between the lines, I think yuo're right in that you could just send the signatures again, but perhaps one side wants to close to a new address, and that information is contained within teh shutdown message.
I kept things like this rather than introducing some new states to keep the amount of total states to a minimum, and re-use more of the existing transition logic. As an example, if they send a shutdown message to us, we still want to validate that they're using the same upfront shutdown address, etc.

@yyforyongyu: review reminder
@crypt-iq: review reminder
@proofofkeags: review reminder
@morehouse: review reminder

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@crypt-iq: review reminder
@morehouse: review reminder
@roasbeef, remember to re-request review from reviewers when ready

@roasbeef, remember to re-request review from reviewers when ready

Updated to point to master.

@roasbeef, remember to re-request review from reviewers when ready

Haven't looked too much into 4/4 yet, so I'm not sure if these items are addressed there. I do think the following should be addressed though (especially points 2 & 3):

need to validate that OP_RETURN in the scriptPubKey is ok in some cases but not in others
apparently, sometimes the remote closing_complete is allowed to be invalid. See this flow from the BOLT here: https://github.com/lightning/bolts/pull/1205/files#diff-ed04ca2c673fd6aabde69389511fa9ee60cb44d6b2ef6c88b549ffaa753d6afeR1540-R1554
in addition to wire fuzz tests, I think we should have a fuzzer for the actual state machine introduced here where we can feed it random events.

Besides that the PR looks good and can approve once CI passes

apparently, sometimes the remote closing_complete is allowed to be invalid? See this flow from the BOLT here where Alice ignores Bob's closing_complete: https://github.com/lightning/bolts/pull/1205/files#diff-ed04ca2c673fd6aabde69389511fa9ee60cb44d6b2ef6c88b549ffaa753d6afeR1540-R1554

Looks like that's trying to handle a case where Alice has sent a shutdown with one script, but then wants to switch to another. I don't quite get that example though, Alice sent the script using the shutdown so she much send another one (after the round) if she wants to swap her script. Will reply on the spec.


Storybook Integration

I was wondering if you guys could add a new recipe to the ignitecookbook on how to integrate Ignite CLI with Storybook.

Hey @hamad-9
The previous version of ignite used Storybook but we drop the support with 8.x mainly for maintenance reasons.
Here is how you can do it

setup storybook https://storybook.js.org/blog/storybook-for-react-native-6-5/
change the entry point of your app https://dev.to/dannyhw/how-to-swap-between-react-native-storybook-and-your-app-p3o

thanks


upgrade of the trifecta components

What is your feature idea?
ingress-nginx, cert-manager, and external-dns applications need to upgrade to the latest helm charts.
when you provision a new kubefirst management platform (any cloud), the version of these apps will be outdated from latest available. for ease of documentation in this example, we'll assume a github org of kubefunk.net and a mgmt cluster named mgmt-funknet
step 1: the mgmt cluster
the charts for these 3 components on the mgmt stack are defined at:
https://github.com/kubefunk-net/gitops/blob/main/registry/clusters/mgmt-funknet/components/ingress-nginx/application.yaml#L14
https://github.com/kubefunk-net/gitops/blob/main/registry/clusters/mgmt-funknet/components/ingress-nginx/application.yaml#L14
https://github.com/kubefunk-net/gitops/blob/main/registry/clusters/mgmt-funknet/components/cert-manager/application.yaml#L12
upgrading each to their latest chart, and then refreshing their app in argocd, and confirming health is step 1.
step 2: physical and virtual workload clusters
those upgraded components can also be applied to new clusters created by this mgmt stack. to upgrade physical cluster provisioning, you'll need to update:
https://github.com/kubefunk-net/gitops/blob/main/templates/workload-cluster/30-ingress-nginx.yaml#L14
https://github.com/kubefunk-net/gitops/blob/main/templates/workload-cluster/30-cert-manager.yaml#L14
https://github.com/kubefunk-net/gitops/blob/main/templates/workload-cluster/30-external-dns.yaml#L12
once you update these in the templates, you can test how well they orchestrate by going to kubefirst console on this stack, creating a physical cluster, and confirming health on these 3 resources on the new physical cluster in argocd.
repeat these steps for virtual clusters templating:
https://github.com/kubefunk-net/gitops/blob/main/templates/workload-vcluster/30-ingress-nginx.yaml#L14
https://github.com/kubefunk-net/gitops/blob/main/templates/workload-vcluster/30-cert-manager.yaml#L14
https://github.com/kubefunk-net/gitops/blob/main/templates/workload-vcluster/30-external-dns.yaml#L12
test with creation of a virtual cluster and confirming health in argocd.
step 3:
whatever changeset was required to get this stack operational, needs to be promoted up to the gitops-template repository, so that mgmt clusters will begin with the right charts and templates. there will be corresponding files for each of the files listed in steps 1 and 2 in the gitops-template. for example:
kubefunk stack:

https://github.com/kubefunk-net/gitops/blob/main/templates/workload-vcluster/30-ingress-nginx.yaml#L14
gitops-template civo github:
https://github.com/kubefirst/gitops-template/blob/main/civo-github/templates/workload-cluster/30-ingress-nginx.yaml#L14

all of the cloud stacks need these updates in the gitops-template. to test, provision a new stack using your gitops-template branch, and confirm that you can provision a new mgmt cluster, and then confirm that kubefirst instance can create a new physical and virtual cluster that provisions to 100% health in argocd in its registry.
Why is it needed?
cloud native never sleeps
Is this missing feature preventing you from using kubefirst?

[ ] Yes

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for the incredible detail @johndietz !! One question: Could I find the external-dns here: https://github.com/kubefunk-net/gitops/blob/main/registry/clusters/mgmt-funknet/components/external-dns/application.yaml

pull request for step 1: https://github.com/gitops-ing/gitops/pull/1

All green / health confirmed after ugrade 👍 . Proceeding to step 2

pull request for step 2: https://github.com/gitops-ing/gitops/pull/2

pull request for virtual clusters (within step 2): https://github.com/gitops-ing/gitops/pull/3


WslLaunchInteractive  failed with error: 0x80070005 Error: 0x80070005 Access is denied.

Had Ubuntu 16.04-LTS running just fine for months (yea).  After taking an update and rebooting, I can no longer launch wsl.exe.  I've checked the permissions on C:\Windows\System32\wsl.exe and I do have read and execute access.
The service is enabled:
C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-
Subsystem-Linux
Path          :
Online        : True
RestartNeeded : False
PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
FeatureName      : Microsoft-Windows-Subsystem-Linux
DisplayName      : Windows Subsystem for Linux
Description      : Provides services and environments for running native user-mode Linux shells and tools on Windows.
RestartRequired  : Possible
State            : Enabled
CustomProperties :
ServerComponent\Description : Provides services and environments for running native user-mode Linux shells and tools on Windows.
ServerComponent\DisplayName : Windows Subsystem for Linux
ServerComponent\Id : 1033
ServerComponent\Type : Feature
ServerComponent\UniqueName : Microsoft-Windows-Subsystem-Linux
ServerComponent\Deploys\Update\Name : Microsoft-Windows-Subsystem-Linux

Your Windows build number:  (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.17134.167]
Clicking on the Ubuntu icon on my desktop (which always worked before) brings up a window with the following text:
WslLaunchInteractive  failed with error: 0x80070005
Error: 0x80070005 Access is denied.
Press any key to continue...

What's wrong / what should be happening instead:

wsl.exe won't launch / should launch

For WSL launch issues, please collect detailed logs.

Attached in a .zip file
lxcore.zip

Additionally info.
I don't have UMCI enabled:
C:\WINDOWS\system32> Get-CIPolicyInfo
Options HVCIOptions Version PolicyGuid

1073741824           0       0 {0, 0, 0, 0...}

The suggestion to manually set the page file size to 800 didn't help, nor did Settings -> Applications -> Ubuntu -> Advanced Options -> Repair.

@tquiggle - Thanks for sharing the logs. Unfortunately I'm not seeing anything in the logs you shared that would explain the access denied failure. This makes me think that the error is coming from somewhere outside of our components.  Do you see any interesting logs in the system event viewer around where the error takes place?

No, I don't see anything in the system logs.  Out of curiosity, how do you read the lxcore* files?
Just in case I botched the timing on the previous ones, I generated a new set where I'm 100% confident I launched Ubuntu twice from the desktop icon while loggging was enabled.  Both times it failed with 0x80070005 Access is denied.
I appreciate any help!
lxcore-2.zip

@tquiggle - I use WPA to view the logs.  Unfortunately your second set of logs also do not make too much sense.  I see an instance being created but I do not see any access denied errors.

How about including TraceView in WDK and Microsoft/Etw2Json repository?

Microsoft Windows [Version 10.0.18362.145]
Issue: Cannot start WSL.
Console output:
C:\Users\Subhasis>bash
Access is denied.
WSL is installed and running:
PS C:\WINDOWS\system32>  Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Path          :
Online        : True
RestartNeeded : False
PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
FeatureName      : Microsoft-Windows-Subsystem-Linux
DisplayName      : Windows Subsystem for Linux
Description      : Provides services and environments for running native user-mode Linux shells and tools on Windows.
RestartRequired  : Possible
State            : Enabled
CustomProperties :
ServerComponent\Description : Provides services and environments for running native user-mode Linux
shells and tools on Windows.
ServerComponent\DisplayName : Windows Subsystem for Linux
ServerComponent\Id : 1033
ServerComponent\Type : Feature
ServerComponent\UniqueName : Microsoft-Windows-Subsystem-Linux
ServerComponent\Deploys\Update\Name : Microsoft-Windows-Subsystem-Linux
Ubuntu is installed and set as default:
C:\Users\Subhasis>wslconfig /l
Windows Subsystem for Linux Distributions:
Ubuntu-18.04 (Default)
Additional details: I was never able to set even an username. This is how the initialisation went:
Installing, this may take a few minutes...
Access is denied.
Please create a default UNIX user account. The username does not need to match your Windows username.
For more information visit: https://aka.ms/wslusers
Enter new UNIX username: subhasis
Access is denied.
Enter new UNIX username:
Logs in zip file:
bash.zip
ubuntuinstall.zip

I'm having the exact same error with a new WSL install. I installed Ubuntu 18.04 manually (using a browser) as mentioned here: https://docs.microsoft.com/en-us/windows/wsl/install-manual

Same error here. Tried running this manually from the CanonicalGroupLimited error and got a more detailed error:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070005
Error: 0x80070005 Access is denied.

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070005
Error: 0x80070005 Access is denied.

This is when using ubuntu installed from the website:
Logfile_ubuntu.zip
I didn't even have a Windows Store account, but I made one and reinstalled ubuntu through there, but it makes no difference.
This might be related to https://github.com/microsoft/WSL/issues/2577, though the workaround mentioned there (moving the ubuntu installation some place else) doesn't work for me.
I'm running McAfee anti virus, might that be related?

So just wondering did you follow my steps at tinyurl.com/donofrioworkdesk?

I am having the exact same error. I have had working WSL on my previous Dell xps 13 machine. I can't get it to run on the new surface machine. https://github.com/microsoft/WSL/issues/4514

Try to take ownership of the installation folder aka. BasePath before installing it. Command:
takeown /f path\to\folder
icacls path\to\folder /grant Everyone:(OI)(CI)(F)

wsl.exe is in C:\Windows\system32, I was able to run takeown however I am getting error on icacls OI : The term 'OI' is not recognized as the name of a cmdlet

Those commands are for Command Prompt. The path is where WSL distribution will be installed.

Are you having issues starting wsl or rights got messed up my mistake (just trying to get a baring on what is wrong - have you tried my 'no microsoft store available' writeup tinyurl.com/donofrioworkdesk?

i have try every method but still the same eror  WslRegisterDistribution failed with error: 0x80070005
what should i do?

WslRegisterDistribution failed with error: 0x80070005

What about this (if you have WSL installed by "Store" uninstall it...then it should work 'they say?'
https://github.com/microsoft/WSL/issues/6744

'they say?'
#6744
yes it works but now im thinking that whats the different beetwen uninstalling it with installing? there must be some +- feature right?

'they say?'
#6744
yes it works but now im thinking that whats the different beetwen uninstalling it with installing? there must be some +- feature right?
bcs every time im installing the wsl then the ubuntu will get the WslLaunchInteractive failed with error: 0x80070005 Error: 0x80070005 Access is denied.

WslRegisterDistribution failed with error: 0x80070005

What about this (if you have WSL installed by "Store" uninstall it...then it should work 'they say?' #6744

yes i can open it wihtout any eror but are there some different feature or anything?


[WIP] Remove -e , --config and --observe options

Purpose
ballerina run has above additional optional which is not consistent with java jar command. Hence removed.
Config passing, enabling observability and pass config can be done as below.
java -jar main-exectable.jar --b7a.config=/home/waruna/ballerina.conf
--b7a.observability.enabled=true

Same way with ballerina run
ballerina run main-exectable.jar --b7a.config=/home/waruna/ballerina.conf
--b7a.observability.enabled=true

Fixes #18547
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18555 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #18555   +/-   ##
=======================================
  Coverage   15.15%   15.15%
=======================================
  Files          48       48
  Lines        1254     1254
  Branches      197      197
=======================================
  Hits          190      190
  Misses       1050     1050
  Partials       14       14

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 02f0dc1...c43f4f1. Read the comment docs.

Btw, wouldn't the below cause confusion?
--b7a.observability.enabled=true

Shouldn't that be like the follow?
ballerina run --b7a.config=/home/waruna/ballerina.conf
--b7a.observability.enabled=true main-exectable.jar

The configs are params to the run command. Not the user's program

@pubudu91 When we run the jar with java -jar we cannot use above suggestion.
ex. java -jar --b7a.config=something main-exectable.jar
and above change cannot be done in ballerina run as well AFAIK due to implementation issue with the underlying library.

Will send two PRs for doc changes and code changes. Hence closing this. Please refer https://github.com/ballerina-platform/ballerina-lang/pull/18633/files


[DO NOT MERGE] Updated resourceFiles property of TaskAddParameter to denote error.

Updated to include error code RequestEntityTooLarge and documented that error occurs if there are too many files.  Added known workaround of using Application Packages
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ X] The title of the PR is clear and informative.
[ X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ X] If applicable, the PR references the bug/issue that it fixes.
[ X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ X] I have read the contribution guidelines.
[X ] My spec meets the review criteria:

[ X] The spec conforms to the Swagger 2.0 specification.
[ X] The spec follows the guidelines described in the Swagger checklist document.
[ X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-ruby

Automation for azure-libraries-for-java

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go


Error : Please select Age between 18-150

The error popping up when the age is by default 18 , should be solved.

Works fine on browsers for mobile and laptop/desktop devices.

Completed


Remove unnecessary scroll bars

Scroll bars are being displayed for elements that do not need to scroll in Chrome and Firefox.  The scroll bars confuse users and unnecessarily consume screen real estate. This is likely due to combinations of certain values of width, position, display, or overflow. Extra super bonus points if there is a way to write an automated test that prevents these from being introduced in the future.

@neckberg this is probably related to the printing issues

Extra scroll bars on the home page on Chrome in Windows.

Looks like the extra scroll bars show up on all pages. Here are a few more examples.

This SO post suggests a CSS tweak that might https://stackoverflow.com/questions/35484742/hide-useless-scrollbars-that-show-up-on-windows-only

It worked!


Install Script doesn't work any more.

Can we get a new install script for Ubuntu 18.04 or 20? Thank you.

same on #777

Unfortunately #1294 and #1324 are blocking new installations right now

is there any official docker version?

There is an official Dockerfile if you wanted to build your own image.


Don’t use custom hitTest if the cell is hidden

This PR fixes the following edge case:
When a cell is deleted using collectionView.deleteItems, UICollectionView just sets the isHidden flag of the cell to false but the cell view stays "physically" at the same location.
If the actionsContainerView of the cell was visible before the deletion, this cell still accepts touches because of the custom hitTest implementation. This prevents the new cell, which moved to the same location, from accepting its touches.
This PR changes the implementation such that the custom hitTest is used only if the cell is not hidden.

Thanks!