boards: shields: add suport for weact_ministm32h7xx_ov2640

Add support for OV2640 camera sensor to use with WeAct Studio MiniSTM32H7xx boards.
Shield  used with https://github.com/zephyrproject-rtos/zephyr/pull/71463 sample.

I think we should define a binding for the connector (similar to dsi_lcd_qsh_030 display connector for example) since it's apparently used by many vendors (#71463 (comment)) and use that binding to specify the pins in ov2640 node, in a board-independent way.
Also, the I2C, DCMI (except port child node, and board-independent properties like sensor), and DMA nodes should be moved to a board-specific overlay (#77854 does the same for display shield) & then be referenced by generic aliases (like "cam_interface" for DCMI so the sensor can be used with a board that has a cam interface other than DCMI).
BTW, should the shield be renamed to "ov2640_cam_module" for example?

Thanks for your review, @JarmouniA!
Since I'm not familiar with the connector binding approach, I'll take a look at it carefully.

Hi, @JarmouniA.

I think we should define a binding for the connector (similar to dsi_lcd_qsh_030 display connector for example) since it's apparently used by many vendors (#71463 (comment)) and use that binding to specify the pins in ov2640 node, in a board-independent way.

I think it is done! Let me know if I got right your suggestion.

BTW, should the shield be renamed to "ov2640_cam_module" for example?

About the shield name, could it be "weact_ov2640_cam_module"? To make it less generic.

My point was that the connector should't be considered a WeAct one, it's used on a lot of boards from other vendors as well (like ESP32-CAM https://components101.com/sites/default/files/inline-images/ESP32-CAM-Schematics.png), so if we are going to make a compatible for it, it should not have WeAct in its name. Same thing for the camera module (https://components101.com/sites/default/files/components/ESP32-CAM-Camera-Module.jpg).

Good observation, @JarmouniA.
There is one point here to consider: even though the connector is similar, the position of the pins is different from the WeAct schematic https://github.com/WeActStudio/MiniSTM32H7xx/blob/master/HDK/STM32H7xx SchDoc V11.pdf. I believe this is a problem when creating a generic OV2640 shield version. What you think?

I placed the connectors next to each other and noticed that the pins are upside down. Additionally, the ESP32-CAM doesn't connect the PWDN pin, while the WeAct doesn't connect the RESET pin (which is linked to the reset system).

the position of the pins is different from the WeAct schematic

Ah, good catch, didn't pay attention to this.
In this case, would it make sense to have a generic compatible for the connector, then specific ones for each vendor, depending on the pins mapping, that include the common one? Or would it be simpler to just keep the current implementation? The same for the cam module.

I think we would keep it simpler as in the current implementation. Is it ok for you?

Thank you @JarmouniA for your valuable review!

Change the shield name to weact_ov2640_cam_module.

This introduces a new naming for shields.
As noted here, there seems to be a zephyr_ prefix for all shields, which might allow to make a difference between names specific to a SoC/Boad/project and those standardized by Zephyr, facilitating review of all standards:

https://github.com/zephyrproject-rtos/zephyr/pull/77854#discussion_r1740830325

There is a compromise to take in that:

dvp is relatively widespread but roots back to OmniVision
dcmi is a peripheral by ST
camera_interface sounds like the right name but could be mistaken with MIPI-CSI which also "a camera interface".
camif does not seems as broadly as the vendor terms.

If we try to copy-cat zephyr_mipi_dsi, this could be:

zephyr_camif or zephyr_dvp or zephyr_camera_dvp or zephyr_camera_parallel`
zephyr_camera_i2c or zephyr_camif_i2c or zephyr_dvp_i2c or zephyr_camera_parallel_i2c or zephyr_mipi_csi_i2c

Which one sounds the best?

Which one sounds the best?

Hi, @josuah. The zephyr_camera_dvp and zephyr_camera_i2csounds great for me!
Thanks for your suggestion!

Change camera_interface to zephyr_camera_dvp.
Change camera_connector_i2c to zephyr_camera_i2c.

CI complains about samples/drivers/video/capture_to_lvgl/ not existing, which will be introduced by #71463.

@CharlesDias There are some CI issues to be fixed

Hi @erwango.
This PR https://github.com/zephyrproject-rtos/zephyr/pull/71463 has to be merged first. Could you review it? Thank you!

Rebase.

Add new MCO configuration as suggested on https://github.com/zephyrproject-rtos/zephyr/pull/71463#discussion_r1773212375

Rebase.

Update the samples/drivers/video/capture_to_lvgl/sample.yaml file to include this shield.

Hello, everyone.
I am trying to understand why the CI is failing! Do you have any suggestions for me?
Another point: should I update the samples/drivers/video/capture_to_lvgl/sample.yaml to include this shield? If that's the case, should it be like this?
sample:
  name: Video capture to LVGL
tests:
  sample.video.capture_to_lvgl:
    tags:
      - video
      - shield
      - samples
    extra_args:
      - platform:mini_stm32h743:SHIELD=weact_ov2640_cam_module
    harness: console
    harness_config:
      fixture: fixture_camera
      type: multi_line
      ordered: true
      regex:
        - "Device name"
        - "Format"
        - "Capture started"
    platform_allow:
      - mini_stm32h743
    depends_on: video
    integration_platforms:
      - mini_stm32h743

@CharlesDias
extra_args:
      - platform:mini_stm32h743:SHIELD=weact_ov2640_cam_module

this does not look right.
See
https://github.com/zephyrproject-rtos/zephyr/blob/3a15e37b5a9a0d17c111eecb3a1803c2ab20cd5d/samples/drivers/display/sample.yaml#L136

Thanks, @JarmouniA! Do I have to change also from sample.video.capture_to_lvgl: to sample.video.capture_to_lvgl.shield.weact_ov2640_cam_module:?

I used as a model the https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/drivers/video/capture/sample.yaml file.

Not yet, @JarmouniA! There is something more! Twister is mysterious to me! :)

Removed the boards/shields/weact_ov2640_cam_module/Kconfig.defconfig file.

Rebase

Hi, everyone.
What you think about the use of CONFIG_VIDEO_HFLIP=y and CONFIG_VIDEO_VFLIP=ysymbols? In this way, the shield depends on these symbols that are relevant only for sample/drivers/video/capture_to_lvgl code. Does this make sense? Is there another way? Thanks!

Change port label from dcmi_ep_in to zephyr_camera_dvp_in.

What you think about the use of CONFIG_VIDEO_HFLIP=y and CONFIG_VIDEO_VFLIP=y symbols inside of boards/shields/weact_ov2640_cam_module/boards/mini_stm32h743.conf? In this way, the shield depends on these symbols that are relevant only for sample/drivers/video/capture_to_lvgl code. Does this make sense? Is there another way? Thanks!

The FPC can eventually be folded to rotate the camera by 180°, but then that can still be overridden by the user.
This reminds me of LIBV4LCONTROL_FLAGS that permits to rotate a misoriented camera at the very last moment.


Improve docker image to decrease size

Use alpine instead of ubuntu1604-customize to reduce docker image size from 2.8G to 2.41G. Add and modify commands to make everything works in alpine.

Codecov Report

Merging #13827 (fefcf78) into master (0203366) will decrease coverage by 13.02%.
The diff coverage is 61.41%.

@@              Coverage Diff              @@
##             master   #13827       +/-   ##
=============================================
- Coverage     43.86%   30.83%   -13.03%
+ Complexity     8930     5824     -3106
=============================================
  Files          1359     1386       +27
  Lines         78109    80561     +2452
  Branches       9496     9805      +309
=============================================
- Hits          34260    24840     -9420
- Misses        40960    53627    +12667
+ Partials       2889     2094      -795

Impacted Files
Coverage Δ

...o/client/block/policy/DeterministicHashPolicy.java
68.42% <ø> (ø)

...nt/block/policy/LocalFirstAvoidEvictionPolicy.java
94.28% <ø> (ø)

.../alluxio/client/block/policy/LocalFirstPolicy.java
93.93% <ø> (ø)

.../client/block/policy/MostAvailableFirstPolicy.java
91.66% <ø> (ø)

.../alluxio/client/block/policy/RoundRobinPolicy.java
97.91% <ø> (ø)

...lluxio/client/block/policy/SpecificHostPolicy.java
40.00% <ø> (ø)

...xio/client/block/stream/BlockWorkerDataReader.java
0.00% <0.00%> (ø)

...ient/block/stream/BufferCachingGrpcDataReader.java
42.25% <0.00%> (+0.58%)
:arrow_up:

...main/java/alluxio/client/file/FileSystemUtils.java
0.00% <0.00%> (ø)

...va/alluxio/client/meta/MetaMasterConfigClient.java
0.00% <ø> (ø)

... and 662 more

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 7d70714...fefcf78. Read the comment docs.

@ssz1997 @LuQQiu   with alpine, are we still able to run fuse related? e.g., I remember the original reason to move from Alpine to Customized ubuntu is to have libfuse working

@ssz1997 @LuQQiu with alpine, are we still able to run fuse related? e.g., I remember the original reason to move from Alpine to Customized ubuntu is to have libfuse working
also cheyang/fuse2:ubuntu1604-customize has a some optimization in libfuse.

I manually tested the fuse mount/unmount and it worked. I also migrated the optimization here.

@ssz1997 have you tested any file read write path? like write a file into fuse, see if it shows in alluxio namespace/UFS. Read some file from fuse, etc.

@ssz1997 have you tested any file read write path? like write a file into fuse, see if it shows in alluxio namespace/UFS. Read some file from fuse, etc.

I tried creating directory inside the alluxio mounting path - it appears both in alluxio namespace and mount point. Also tried copy a local file to the mounting path, and it can be read both from alluxio namespace and the mount point.

@madanadit  do you have the context when we switch from alpine to ubuntu? I remember it is for libfuse, but it seems @ssz1997  is able to run fuse without using ubuntu

That's what I remember as well; that libfuse wasn't available on alpine. Could have changed since.

thanks @ssz1997  for verifying it works! Good to know.
@LuQQiu , can you work with @ssz1997 to understand if the MAX_IDLE_THREAD macro still works ? That's the customization @cheyang added to the cheyang/fuse2:ubuntu1604-customize

That's what I remember as well; that libfuse wasn't available on alpine. Could have changed since.

double checked the PR, we actually checkedout and installed libfuse on top of Alpine -- that's why it works.

@ssz1997 Thanks for the work you did to decrease the size of docker image. I definitely agree with build a small size image for stable production env. But, before stable, we need a env with jdk tools like jps, jstack, we also need ping, vi, net-tools to helps us to debug unexpected behavior. Base on these, would you please maintain two types dockerfile, one for release, the other for debug. I suggest to use centos as the base image for debug version, it is widely used by lots of company in production env.

Centos docker image is even bigger than the ubuntu one. Should we offer the official testing docker image? If we should, a bigger Alluxio docker image based on either ubuntu or centos is acceptable and can be under alluxio-test/alluxio @apc999 what are your thoughts? @Xenorith what are your thoughts on centos vs ubuntu?

i would propose naming the larger image as alluxio-dev instead of alluxio-test
i do not have a preference between ubuntu vs centos; this might be a better question for @madanadit given he's more familiar with production environments. i personally use centos more often and am less familiar with ubuntu, but that shouldn't affect this decision

maybe still in alluixo/alluxio repo, but with different tag name . e.g, suffixed by -dev to indicate larger image size and more tools inside (based on different image). Let's discuss it tonight.

Redirect this PR to target feature branch ssz-docker.
This PR will target to simplify the docker image based on alpine
Next PR will target to add a profile to support building a docker image based on centos. @maobaolong can you share what changes may be needed to change the alluxio docker image to be on centos? i guess many install package commands are different

@LuQQiu Uninstall some packages after their usage to further decrease the image size. The image can be gotten by docker pull ssz1997/alluxio-alpine:latest. The tarball used is the latest OS master tarball. PTAL, thanks!

@apc999 PTAL, thanks

After some consideration and input from @Xenorith (Thanks Rico!), I feel like it doesn't worth to create a common Dockerfile-common for Dockerfile and Dockerfile-dev for the following reasons:

alpine image needs as few packages as possible, but centOS needs many packages. Also they use different package managements (alpine uses apk, and centOS uses yum), so the commands are quite different. Therefore, any installation involving packages, including installing libfuse, java, all the various tools, can't be put into the common dockerfile.
The commands for creating user are also different because alpine supports less commands.
Even if we put the step that grants some directory permission to user Alluxio in Dockerfile-common, we have to copy them out  to Dockerfile and Dockerfile-dev. Anything in common that's new, we have to copy them out into the two Dockerfiles, which may still involve modify our Dockerfiles.
Other than these 3 steps, the Dockerfile doesn't do much. The ARG and ENV variables are not sharable across different Dockerfiles. So we don't really have much to put into Dockerfile-common.
@LuQQiu @apc999 Please let me know if you have any question.

@ssz1997 @Xenorith Based on our discussion, is it possible to put the common code in a script and then use that script in two dockerfiles?

@LuQQiu 90% of the commands are actually different. The only common ones are grant permissions to Alluxio worker.

The libfuse related commands and grant permissions commands are common, is it possible to put them into a common script and trigger it in Dockerfile, or how hard it is

@LuQQiu It's not hard. Now I think it does make sense to put these commands into a script. I'll work on it.

@LuQQiu I suggest we merge this PR and the centOS one first, and then I'll create the PR for the common script.

alluxio-bot, merge this please


startup bug and question.

On first install, got this error:
   Virtual Garage Door Error       Error in plugin execution startup:

  File "plugin.py", line 396, in startup
type: key loggingLevel not found in dict

   Started plugin "Web Server 2023.1.0"

Line 396 should be:
        level = self.pluginPrefs.get('loggingLevel', 'INFO')

Or similar.
Now the question - is there a reason you're specifying all the different possible relay types in the code, rather than just checking that the Indigo device is of type "relay":
  for dev in indigo.devices.iter("indigo.relay"):
      do something

Hi Joe,
As we both know, the Indigo server initializes the pluginPrefs dictionary using the default values in the PluginConfig.xml file in the plugin bundle.  The question is, when does this happen in the global plugin initialization sequence?  Because pluginPrefs is an instance attribute, we know that it cannot occur until after the Plugin class instance object (self) is created by

Actually, I'm not sure that's exactly right.  If the plugin has been run before, and the preferences file has been created, then it's read during the superclass init.  If it's not, then the config file isn't read until the config dialog is presented.  Which is supposed to happen immediately on first start, but I'm not sure if it's before the startup routine or after.  And I'm not sure that always happens when it's supposed to.  I never depend on it.  So I always use the .get() to make sure I don't get an exception on any dict that I didn't create in my own code.
Matt or Jay would have the definitive answer on this.

Hi Joe, I did some more research/tests and confirmed your analysis.  I was totally wrong! The xml file is only used by the configUi and never sets the pluginPrefs directly. If run previously, a preferences file is read by the superclass init and used to fill self.pluginPrefs. If it is a first time run, self.pluginPrefs will always be empty…even in the startup method.  The server may force the configUi to execute, but it doesn’t seem to happen all the time.  Anyway, you proposed the only workable solution.  Thanks for your help. I will upload a new VGD 1.2.2 with the correct fix later today.
Thanks again,
David

You're welcome.
Now, about that search for the relay type devices....

I made a list of the "indigo.relay" devices in my system.  It included all of my relay devices except the EasyDAQ device.  Unfortunately it also included about 30 on/off switches that are not used as relays. My list of deviceTypeId's also includes many of these as well due to user requests for additional devices.  Anyway, I think that I prefer to explicitly control the supported devices list forth relay and sensor devices.
BTW:  Are you using or do you plan to use VGD?  If so, I hope that it works well for you.  Let me know if you have any suggestions.
David

I'll probably use VGDO when I wire up either the ratgdo or a shelly relay.  Haven't decided which I'll do yet.  I also only have one tilt sensor on each door, so I might need to get a couple more.  Depends on how well it works with just the one.


Typescript definitions?

TypeScript Definition Manager
Would be very helpful if we got Typescript Definition files for the api (not the templating/handlebars).

Did you look at the code? This is js not ts.

Okay, will do it.

What is the best way to add TSD for project?

@elfet I think you can specify your typing definitions in package.json with the line
"typings": "./monkberry.d.ts"

How to test TSD?

This package seems to be purpose built for this: https://www.npmjs.com/package/typescript-definition-tester

You might also consider porting to TypeScript - in my experience, that's usually the better approach, because it guarantees correct typedefs and removes the burden of maintaining them by hand.
In addition, it hardens your codebase against errors and makes the code self-documenting for other contributors.
You're already using ES6, so basically you would just be adding type-annotations for compile-time safety - it won't affect the footprint of the generated code at all.
Inferno is another project that uses this approach.


MAINT move cost-over-time to bokeh, ADD hover tooltips for cost-over-time

Codecov Report

Merging #132 into development will increase coverage by 0.12%.
The diff coverage is 100%.

@@               Coverage Diff               @@
##           development     #132      +/-   ##
===============================================
+ Coverage        72.38%   72.51%   +0.12%
===============================================
  Files               18       18
  Lines             2126     2136      +10
===============================================
+ Hits              1539     1549      +10
  Misses             587      587

Impacted Files
Coverage Δ

cave/plot/plotter.py
94.23% <100%> (+0.39%)
:arrow_up:

cave/analyzer.py
77.54% <100%> (ø)
:arrow_up:

cave/cavefacade.py
68.04% <100%> (ø)
: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 8f1ef09...53b1d11. Read the comment docs.

Could you please change the format of the x-axis labels such that it is more human readable.

Oh I missed the last comment, will do.


Pass server->client command over a separate socket pair

This pull request changes the VFIO-user protocol to optionally use a separate pair of sockets for server->client commands. Doing so simplifies command / reply processing for the case where both server and client send commands concurrently, which has proven problematic per issue #279.
Included are the functional changes, new pytests, as well as protocol specification updates.

Rebased after https://github.com/nutanix/libvfio-user/pull/763 was merged.

Btw. I think it makes sense to break out https://github.com/nutanix/libvfio-user/pull/762/commits/4025f6e6acd6a32500d6dc4e3e9bfe5f8528dff0 into a separate MR so the mechanical s/sock/client/ changes don't clutter this MR up?

As discussed, I have now broken out various bits and pieces into separate merge requests:
https://github.com/nutanix/libvfio-user/pull/772 - Introduce client object in python tests
https://github.com/nutanix/libvfio-user/pull/773 - Replace protocol header flags bit field with mask
https://github.com/nutanix/libvfio-user/pull/774 - Prepare python test helpers for receiving commands
https://github.com/nutanix/libvfio-user/pull/775 - Describe the twin-socket feature in the spec
And there's another one that we haven't discussed yet. This is preparation work for the server version capabilities to include the index of the socket file descriptor in the ancillary data array:
https://github.com/nutanix/libvfio-user/pull/771 - Construct server capabilities using json-c
I think it'll be best if we work through these preparatory MRs first, then I can rebase this one eventually. Or I can alternatively update this one to the final version now - let me know if you have a preference.
I will also go through the comment threads here and resolve what has been addressed already.


Optimize JournalDB More

What is wrong?
My latest mainnet test shows JournalDB being a major contributor to import_block() time:

.commit() taking 13.5% of total time
.__getitem__ taking another >2% of time
.latest and .latest_id ~1.1%
.record() ~0.85%

A few other methods that are in the 0.5-1% range, but add up to another couple of percent. It looks like a major reason for each of them is uuid which is spending 4.3% of total blocktime in __hash__ and another 2.7% in __eq__.
How can it be fixed

Look into uuid alternatives
refactor the data store to always keep the latest data and have the changesets be backwards-facing diffs (since gets get is called 17k times, commit called 43k times, and discard only called 274 times, we should optimize for the "happy path" where everything gets committed).

I think this will wrap up the import_block() performance sprint for now (HexaryTrie is the next major contributor, but that will take some serious new features, and I think it's fast enough to make Beam Sync progress)

UUID is for uniqueness.  We should be able to just use an itertools.count() and use sequential numbers right?

UUID is for uniqueness. We should be able to just use an itertools.count() and use sequential numbers right?

Right, that's my first instinct too. Since the journal itself only exists on one thread/process, and mostly invents its own checkpoints, I expect that to work fine.


feat: flatten at rules conditionally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please tag the 1.9.1 release

Could you please push the git tag for the 1.9.1 release now on PyPI?
I think it should be v1.9.1 referencing 23f21b3c23e4a92464625704b04ae5f00a0e16c2.
Thanks!

Hi sorry for the slow reply, I've been away. Thanks for the reminder, I just tagged it: https://github.com/TomGeorge1234/RatInABox/releases/tag/v1.9.1

Thanks!


out_keep_prob is not used in BiDynamicRNNLayer

out_keep_prob defined in BiDynamicRNNLayer is not used in the followed code sections, unlike the one in DynamicRNNLayer. The following code may be missing in the BiDynamicRNNLayer
        if dropout:
            self.fw_cell = DropoutWrapper_fn(self.fw_cell,
                      input_keep_prob=1.0, output_keep_prob=out_keep_prob)
            self.bw_cell = ...

@lei-li i make a new commit, https://github.com/zsdonghao/tensorlayer/commit/8b2eaa41215fe6e682d8c69e1a6ce75e4b289ba5
please have a try.

@zsdonghao thanks for the quick move!

@zsdonghao thanks for the quick move.


WIP: Add jasmine junit and coverage reporting

Changes Unknown when pulling 08b36810fa12764d6500cda6558fa12a836a183f on reporter-updtes into ** on master**.

Changes Unknown when pulling 5dd5e1c2a3df969d44e4383177e4c30fc3cd96a2 on reporter-updtes into ** on master**.


[RC-1.1.90] Pipeline fixes

Update CD pipeline to follow SovrinHelpers v1.2

Signed-off-by: Wade Barnes<EMAIL_ADDRESS>

Cancelled CI build since the change only effects the CD pipeline.


website SSL

It's a little jarring when one visits https://locust.io/ and gets a security warning.

@heyman do you know if you can update this?

looks like you're using AWS and heroku. Both should be able to terminate SSL with a free certificate from https://letsencrypt.org/

@hutchic What browser gives security warnings for non SSL-sites (without a password input field on).
We're using the free (legacy) Heroku plan, which doesn't support SSL. However, I should be able to enable it easily by proxying it through Cloudflare.

https://locust.io/ should work now!


Rename getBalance to getExternalBalance

It loads an external account and as such this naming reflects it better.

Perhaps getBalanceAtAddress may make more sense upon initial reading?

Good idea, although I'd suggest that a proposal is created which renames all the getExternal<xyz> to a scheme get<xyz>AtAddress

There is a naming convention in RPC that applied here would mix both proposals to getBalanceAt(), but in English it would be better to have getBalanceOf().

@axic would changing the naming scheme make sense if we want to keep it similar to EVM opcode names?

@jakelang I think "similar" is good enough. It should not be a problem for match mentally BALANCE opcode with getExternalBalance or getBalanceOf.


UWS_THREADSAFE for non-Epoll backend

When trying to compile uWS with CFLAGS="-DUWS_THREADSAFE=1" on OS X/Darwin, the following compile error occurs (see below).
Indeed, preCbData and preCb are only defined for the Epoll backend, not for Libuv. Is a Libuv-based build not supposed to define UWS_THREADSAFE, or is it thread-safe by default?
src/Hub.h:52:20: error: no member named 'preCbData' in 'Loop'
        getLoop()->preCbData = nodeData;
        ~~~~~~~~~  ^
src/Hub.h:53:20: error: no member named 'preCb' in 'Loop'
        getLoop()->preCb = [](void *nodeData) {
        ~~~~~~~~~  ^
src/Hub.h:57:20: error: no member named 'postCbData' in 'Loop'
        getLoop()->postCbData = nodeData;
        ~~~~~~~~~  ^
src/Hub.h:58:20: error: no member named 'postCb' in 'Loop'
        getLoop()->postCb = [](void *nodeData) {
        ~~~~~~~~~  ^
4 errors generated.

Yes, kqueue and epoll and similar low level system features are thread safe by design in itself and this will be exploited all the way up to application level but libuv is not really that well designed in terms of threading and it doesn't reflect the underlying system very well so that is harder to implement efficiently.


Possible EventEmitter memory leak on no-unchecked-send

I tried running the no-unchecked-send rule on the zeppelin-solidity project, and it reported:
(node:8223) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 CallExpression listeners added. Use emitter.setMaxListeners() to increase limit

This is not caused by this rule. This message appears when there are many rules in the .soliumrc.json file.


descriptor: size verification should be before digest calculation

Conforming to description 'Before calculating the digest, the size of the content SHOULD be
verified to reduce hash collision space.' at https://github.com/opencontainers/image-spec/blob/master/descriptor.md.
Signed-off-by: Ling FaKe<EMAIL_ADDRESS>

0d2a6069 looks good to me, although with the Copy approach currently
used by validateContent there's not much benefit in either order.  The
spec wording does increase efficiency in cases where you can
calculate the size more cheaply (e.g. if you're reading a file off the
disk and can stat for the size, or if you're recieving a file over
HTTP and can look at Content-Length).

LGTM

LGTM


Unable to use the out-of-the-box support for  jsx syntax

Environment
Nuxt 3.8.0
Reproduction
Just use nuxt 3.8.0 and try using jsx syntax through a layout or some component.
https://codesandbox.io/s/mystifying-haze-zyv2dh?file=/pages/index.vue
Describe the bug
The jsx tags such as div and img are not being compiled into corresponding HTML elements.
I used jsx inside script with setup attribute and lang=“jsx”
Additional context
message: 'React is not defined'
No response
Logs
No response

Reproduction link
https://codesandbox.io/s/mystifying-haze-zyv2dh?file=/pages/index.vue

@mhdSid Hey! I don't find any error or message. I haven't changed any code. : >

https://codesandbox.io/p/sandbox/serene-ioana-47zyhf?welcome=true
It work normally. May be?

Im currently using builder-webpack and it uses default tsx to transpile tsx/jsx code which injects React.createElement.
I solved it by removing Nuxt's default config for jsx/tsx for webpack (the code is not optimal but at least the JSX gets converted into code that uses "h" from vue instead of React.createElement):
import { defineNuxtModule, installModule, extendWebpackConfig } from '@nuxt/kit'

export default defineNuxtModule({
  async setup () {
    extendWebpackConfig(config => {
      console.log(config.module.rules)
      const ruleIndex = 4 // config.module.rules.findIndex(rule => String(rule.test) === String('/\.m?[jt]sx$/'))
      config.module.rules[ruleIndex] = {
        test: /\.m?[jt]sx$/,
        exclude: /node_modules/,
        use: {
          loader: 'babel-loader',
          options: {
            plugins: ['@vue/babel-plugin-jsx'],
            presets: [
              [
                '@babel/preset-env',
                {
                  targets: process.server ? { node: 'current' } : { ie: 11 },
                  corejs: { version: 3 }
                }
              ]
            ]
          }
        }
      }
    })
  }
})

Let me find a time to create a PR for this..

This will be resolved in the next Nuxt release, but for now you can resolve with:
export default defineNuxtConfig({
  builder: 'webpack',
  webpack: {
    loaders: {
      esbuild: {
        jsxFactory: 'h',
        jsxFragment: 'Fragment',
        tsconfigRaw: '{}',
      }
    }
  }
})


New Assets Loading

This feature allows loading assets in a better manner if consider useful can merge.

Yeah..... no.
You can't submit a PR with 207,000 changed lines (mostly reformating 2/3 of our codebase and

Compare changes these changes are done to whole asset loading with different way loading, not trough route and not trough voyager_asset anymore to avoid issues on ngnix or other web server who doesn't use rewrite in general.

#a92b7eddb377b275b99705c19a4bbf16fa2de498


(WIP)(PUP-6374) Minitar verify module tarballs

Previously it was possible, depending on platform, to create a
.tar.gz that won't properly extract with Minitar on puppet versions
prior to 3.8.7 or 4.4.0.  This has particularly caused problems
with the DSC module on Windows.
While the bug was fixed in #4740 /
f888fb09fbef5f7c74ef799b3877ec6f7843a409, these older versions may
still be unable to install modules as a result on platforms that
rely on minitar - namely Windows, AIX and Solaris

Provide some ability to catch these modules as they're packed on
platforms with a native tar.  This should primarly be OSX, where
bsdtar is the norm.  The use of gnu tar typically creates archives
compatible with the old version of Puppet that does not contain
the minitar fix.

CLA signed by all contributors.

This PR has been open for some time and unfortunately it seems like we're not going to be able to pick it up any time soon. I'm going to close it for now, but we can re-open if/when PUP-6374 is prioritized for next steps.


Be much more aggressive about restart and reconnect

This is a preliminary PR for aggressive reconnection.  With these changes, in principle, uProxy should automatically recover from network disconnections (#2662).
I've only tested this on Android.  Note that Android is distinct from desktop in part because the UI can never be closed (without shutting down the whole app).
In my testing, this works well for Cloud connections.  For Quiver, the results are mixed.  During short disconnections, it seems that Quiver drops messages, which is a serious problem.  For long disconnections (long enough for Quiver to detect the failure and log out, which takes several minutes), this logic sometimes works, but often seems to run into WebRTC-related issues (e.g. no UDP candidates, or candidates only on the defunct VPN interface).
I've added extensive comments to explain the logic.  As noted in the comments, there are several codepaths that could likely be removed, pending more testing and discussion.

This change is

After some additional testing I've noticed some more misbehaviors.   It seems like sometimes that app just gets killed, which is bad ... but I'm also beginning to wonder whether this logic actually works while uProxy is in the background.  Maybe the UI environment is actually paused, so this code is not running.  (This might be a new behavior in Android N.)  I've also seen reconnection fail on flaky wifi networks, which is not all that surprising.
Anyway, this is just to say that we'll need to test this change more before claiming that it does what it says it's supposed to do.

Yeah...it's hard to see the extra state being maintained and amount of comments required as an improvement :-) Can you express the problem more concisely, e.g. "social networks should automatically reconnect in the same manner as peerconnections, and both should only do so when the system is online"?

OK, I've attempted to refactor this into independent state machines, and the first one (for peerconnections) is now posted, #2771.


Cannot compile the current build. (valve.bik - Permission Denied)

Version
Commit Id 8881e688ae2d274bfcf39ccd4c557d75903cd883
What is the bug?
Cannot compile the rom, like at all. I'm compiling it on Linux Mint 21.3. I installed everything that's needed, that being snapd (Since mint doesn't come with it) and all of the dependencies as per the "How to build" instructions. After running the make command everything seems to come together just fine until it reaches the valve.bik file (Valve intro) in the /Portal/hl2/media/ folder. As soon as that file is reached, says that "Authorization required, but no authorization protocol specified" and then spews out an "Permission Denied" error, stoping the compile.
I've tried literally anything I could. I even took out the files out of that folder and then the whole folder itself in hopes that it would at least give me a different error that the files are missing or something, but even despite the fact the the files were literally not there, it still gave me the same "Permission Denied" error as if they still existed. I genuinely have no idea if it was me that did something wrong or if there's something wrong with my game files or if it's a problem with the compile itself. I'm just at a loss with this. Any help would be aprecieated.
Steps to reproduce the behavior:
Just try compiling, no idea if it will behave the same for everyone though.
Screenshots
Pic of the whole error message before the compile just stops.

Did you copy your game files to the vpk directory, or use a symlink?
Does it work if you don't run as root? It may be looking for some configuration which doesn't exist for the root user.

Full copy of the game files, no symlink. As for trying to not run it as root, let me check.

That seemed to do the trick! Thanks! Might want to specify that in the build instructions so nobody has the same problem later down the line. Once again, thank you!

Great to hear it's working. As for the docs, I can update it later, but in the mean time PRs are welcome :)

I've updated the readme in ebd7d341f756195b05eddd8f36b9e7f7bfbc01cf.


chore(deps): update quay.io/keycloak/keycloak docker tag to v25

This PR contains the following updates:

Package
Update
Change

quay.io/keycloak/keycloak
major
23.0.7 -> 25.0.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@dependabot rebase


chore: remove eth-phishing-detect

Explanation

After porting PhishingDetector into @metamask/phishing-controller, eth-phishing-detect is now unused and can be removed.
References

Changelog

@metamask/phishing-controller
No consumer changes
Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

can we remove also the directory types/eth-phishing-detect

can we remove also the directory types/eth-phishing-detect

Absolutely yes, good catch! done in 4086987


[FLINK-3443] [runtime] Prevent cancelled jobs from restarting

After JobManager shut down, it was possible that jobs were restarted, because the execution graphs were failed and not cancelled. Although I would have expected the ExecutorService shutdown to handle this, it did not (seen in log files, if you don't immediately shut down the JVM after a test).

We had an offline chat with Stephan about this issue and he pointed out a better solution.


Break on "unhandled" exceptions when a debugger is attached

Currently when there are exceptions in Flutter, they get swallowed by the framework and rendered on the device. This might be better than crashing when not debugging but if a debugger is attached it seems wrong to pass up breaking and letting the user inspect the exception and state. Otherwise the user needs to read the stack, but a breakpoint in the appropriate place and then reproduce the issue (which is what break-on-unhandled-exceptions should avoid us having to do).
There was a little discussion in #2357 about this, and there was some suggestion that users could use "break on all exceptions", however I really don't think that's a good solution. Users often have exceptions being caught, or use third party code that is sloppy with it's exceptions. For all intents and purposes, these exceptions are uncaught.

@DanTup who has the next action on this issue, do you think? I've just been struggling with exactly this.

I think this has been discussed a little (w/ @devoncarew @a-siva) but it sounds like there's no easy/obvious solution. The error isn't "unhandled" anymore because Flutter catches it to render the red screen/error. All the solutions I can come up with are kinda weird (like Flutter just not catching unhandled exceptions, or there being some way for Flutter to signal that this catching of an error should still break the debugger prior to handling it).
It does still bug me a lot too (I've been making lots of crashes lately doing maths in my tiler library 🙈). When an error occurs, I'd much prefer the debugger to break and let me examine variables than give me incomplete information in the Debug Console and then I have to repro it with a breakpoint.

@DanTup I'd love to see this issue fixed, too. I run into it myself. Can you post a small repro that we can use to drive a solution?

I'm not sure how complete a repro you're after, but any code that generates some exception that you might want to examine state for works. For example I did flutter create and added some code that "accidentally" throws a null pointer exception (simulating exercising some path that didn't initialise a variable) after clicking the button a few times (highlighted code here is new):

When this exception occurs and I'm running in debug mode, what I would like is for the debugger to pause on that line (as it would in a Dart CLI application or pub run test) so I can examine variables etc.
What actually happens if we just get info written to the Debug Console (as if we ran without debugging):

When this happens, I currently have to either add a breakpoint to that line or enable break-on-all-exceptions, but both have drawbacks:

Breakpoint will trigger lots of times, not only when the error occurs (conditional breakpoint can be used, though it's more awkward - especially since we don't provide completion/validation for the expression)
Break-on-all-exceptions tends to break in lots of places you don't want, requiring lots of resuming

In addition, I need to be able to reproduce the issue again - and if I don't know what triggered it the first time I hit it, this might take some time.
I understand this might not be the best way to debug some Flutter issues, but it feels like it's been "taken away" when using Flutter (it works for Dart CLI and pub run test), making it harder to use the IDE debug tools.

I convert it , is display like this.

cc @mraleph as we discussed this today. From Slava, one solution might be to mark the Flutter framework exception handling method with a special pragma (I-handle-framework-errors). When we encounter an exception, the VM looks up the stack to see if the exception is handled or not. The framework exception hander means that all exceptions from build methods are technically handled, so we'll never break on uncaught exceptions. The difference w/ this new pragma marked method would be that, for the purposes of the break-on-uncaught-exceptions, the VM would notice the pragma method on the stack, and could then decide to break at the place where the exception was thrown. The user would then be able to inspect local variables and state at the place where the exception occured.
also cc'ing @mkustermann, who's been working on improvements to async stack handling (and may have context in this area)

cc'ing @goderbauer - I'm assuming that there is a good framework method that we'd want to mark w/ this pragma

Could you hook into FlutterError.reportError? https://master-api.flutter.dev/flutter/foundation/FlutterError/reportError.html
That method is called from various places in the framework after we've caught an exception.
Should we also break when the user has set up some custom error-handling, e.g. by providing their own FlutterError.onError implementation? If not, we may just want to hook into Flutter's default error handling, i.e. FlutterError.dumpToConsole maybe?

I believe it would need to be something that was on the stack when the exception was thrown - something that might itself call FlutterError.reportError(). From a very quick perusal of the framework code, that might be something like _debugReportException() from widgets/framework.dart?

Actually, it looks like that method is not on the stack either; something like performRebuild() would need to be marked w/ the pragma (would would then call into the normal uncaught exception error handling code in the framework).

If you just mark performRebuild you'd miss many other places where we catch exceptions in the framework and "swallow" them by printing an error to the console.

@goderbauer I think the only robust solution here is to introduce a special method swallow which is specially marked and does essentially the following:
@pragma('vm:exception-swallower')
void swallow<T>(T Function() code) {
  try {
    return code();
  } catch (e, st) {
    // Report e & st and do nothing.
  }
}

and then rewrite all other code to use this pattern. Other patterns are very hard to support - note that we need to know at the moment when we throw exception that the catch which is going to catch it is a "swallowing" catch. Because you want to stop execution at the moment of throw - not after exception was caught.

also cc'ing @mkustermann, who's been working on improvements to async stack handling (and may have context in this area)

For synchronous exceptions propagated up the stack, it would be not very difficult to make the debugger break on unhandled exceptions (as well as exceptions that would be caught by a function that was marked with a pragma annotation).
Making this also work for async functions is probably quite a bit more challenging and might only work in a subset of situations.

@cskau-g Could you look into the "synchronous" part of this issue?
Some more explanation:
When an exception gets thrown we make a decision whether to notify the debugger or not. We want to notify the debugger about unhandled exceptions, even if they there is a handler if-and-only-if the handler for the exception has such a pragma. The runtime can simply walk the stack, get the function and see if it has a corresponding @pragma() annotation to make this decision.

A CL has landed, adding @pragma('vm:notify-debugger-on-exception') (doc).
This enables the approach mraleph described above.
I believe this addresses everything on the Dart side, so I'll resolve the issue here.

A CL has landed, adding @pragma('vm:notify-debugger-on-exception') (doc).
This enables the approach mraleph described above.
I believe this addresses everything on the Dart side, so I'll resolve the issue here.

Will this still require some changes in Flutter (adding that @pragma somewhere?)

Will this still require some changes in Flutter (adding that @pragma somewhere?)

I have added the pragma to the VM, but I have not otherwise changed anything about the way exceptions are handled in Dart or Flutter. So for the new mechanism to take effect you'll need some function in the path of the exception to be annotated with the pragma.
The question to me is what the most appropriate place is to put it.
If you're just interested in temporarily pausing the debugger on all exceptions as if they were uncaught, you can add the pragma in places like _incrementCounter() in your example above.
But it might also be that this could be used through-out Flutter for more general effect - but I'm definitely not the right person to make such a call.

I have added the pragma to the VM, but I have not otherwise changed anything about the way exceptions are handled in Dart or Flutter. So for the new mechanism to take effect you'll need some function in the path of the exception to be annotated with the pragma.
The question to me is what the most appropriate place is to put it.
If you're just interested in temporarily pausing the debugger on all exceptions as if they were uncaught, you can add the pragma in places like _incrementCounter() in your example above.
But it might also be that this could be used through-out Flutter for more general effect - but I'm definitely not the right person to make such a call.

I think we should probably reopen because somebody needs to go through Flutter framework and annotate places where exceptions are swallowed, e.g. example from https://github.com/flutter/flutter/issues/17007#issuecomment-573746008 needs annotation on GestureRecognizer.invokeCallback.

I think we should probably reopen because somebody needs to go through Flutter framework and annotate places where exceptions are swallowed, e.g. example from https://github.com/flutter/flutter/issues/17007#issuecomment-573746008 needs annotation on GestureRecognizer.invokeCallback.

Unassigning myself since I'm probably not the right person for the Flutter changes.

Unassigning myself since I'm probably not the right person for the Flutter changes.

@cskau-g It appears that the pragma doesn't work on async methods:
void main() {
  foo();
}

@pragma('vm:notify-debugger-on-exception')
Future<void> foo() async {   // <<<< note the async here
  try {
    throw 'Foo';
  } catch (e) {
    print('exception caught');
  }
  return Future.value();
}

Is that a known limitation or a bug that could be addressed?
There's one occurrence in framework where we'd need to apply it to an async method: https://github.com/flutter/flutter/blob/12ec7dc8790feb437566c8b8e6b6e883a110b4d1/packages/flutter/lib/src/services/binding.dart#L275

Yeah, I think I know why it does not work - we missed this in the implementation.
If this is high priority let me know and I will take a look myself, otherwise we wait until @cskau-g is back, he is currently away for a bit.

It's not urgent. I filed a bug over on the dart sdk to keep track of this specific issue: https://github.com/dart-lang/sdk/issues/45673

@mraleph Is there a way to apply the pragma to anonymous closures?
void main() {
  bar('Hello World');
}

@pragma('vm:notify-debugger-on-exception')
void bar(String someObject) {
  foo(() {
    try {
      print(someObject);
      throw 'ERROR';
    } catch (e) { // <-- this catch should notify the debugger
      print('exception caught');
    }
  });
}

void foo(Function function) {
  function();
}

Short of refactoring the code to have the try/catch not be part of the closure, I haven't found a way. For the particular instance in the framework, that kind of refactor would make the code a lot more complicated, I believe.

I ran into another issue with the debugger not breaking on the line that causes the exception, but on a (random?) different line instead. This one appears to be unrelated to the pragma and reproduces even without it. I've filed https://github.com/dart-lang/sdk/issues/45684 with steps to reproduce.

After a good night's sleep I thought the problem described in https://github.com/flutter/flutter/issues/17007#issuecomment-818952818 can be resolved by refactoring the code as follows:
void main() {
  bar('Hello World');
}

void bar(String someObject) {
  @pragma('vm:notify-debugger-on-exception')
  void myFunction() {
    try {
      print(someObject);
      throw 'ERROR'; // <-- attached debugger expected to break here
    } catch (e) {
      print('exception caught');
    }
  }
  foo(myFunction);
}

void foo(Function function) {
  function();
}

Unfortunately, the debugger still doesn't break at all. I've filed https://github.com/dart-lang/sdk/issues/45710 for this issue.


feat: Add module Private Service Access (PSA) for GCP

I believe it would enhance the documentation if you provide an elucidation of the particular service or scenario that necessitates VPC peering within the ArmoniK framework.


Code refactoring

These slight code adjustments aim to enhance Pythonic quality by incorporating python str.join

Hi, thanks for your contribution.
The original code also puts a ";" at the end of the line, while the new code does not. Could you please also add this additional ";" so that the output file does not change.
 csv += ';'.join([str(rnn_output[t, b, c]) for c in range(max_c)]) + ';\n'

looks good, thanks!


2D Raycast

Feature request from forum

You'd want to examine how the HashMap code works -- it implements a spatial partition we use for broad phase collisions.  Any implementation of raycasting would probably use that as a starting point.  You could step through the grid sections in order, checking in each one for collisions.  That would definitely be more efficient than using a collision entity, since you could just stop once you found an intersection, and could use a test for ray intersection instead of SAT.

Update:
I have implemented the algorithm that finds the nearest bounding box or all bounding boxes that are intersected by the ray in the HashMap. Now I have to figure out how to efficiently get the actual intersections, since bounding boxes do not always correspond to the actual entity. The following questions arise:

We support only rectangular entities? - When rectangular entities are rotated, their bounding box is larger than the actual entity
Even if we support only rectangular entities, how will we determine if the ray hits entities that have transparent texture? The entitiy could be completely transparent, thus ray should not intersect with that entity at all

I'll have a more in depth look later, but I'd think the easiest tactic would be for it to only work on entities which implement a hitbox.

Ok, thanks for your input, so

find potential candidates in the HashMap using this._cbr || this._mbr || this as the bounding box
very if ray intersects with potential candidate using this.map as the hitbox

What to do if potential candidate doesn't have hitbox (== the Collision component was never added to the entity):?

Return it as intersection result or
Omit all entities without Collision in raycasting?

IIRC the Collision component will just check for overlap with the MBR if there's no hitbox.
I'd be fine with ignoring non-hitbox entities completely in this case.

Hi, is this issue still open?  I took a shot at my own which can be found here.  http://danielgood.github.io/projects/raycasting/index.html.

@danielGood  That looks pretty nice!  Yes, this issue is still open, and thanks for poking at it.
But, if we implement something like this directly in Crafty, there's some existing functionality we'd want to use:  broad-phase collision testing, and the existing mechanisms for defining hitbox polygons.
I did a bit of research/thinking yesterday.

Looks like we could use the 2D version of this algorithm for traversing the broad-phase spatial grid.
To start with, it'd be better to only check for collision against entities which already have a hitbox polygon
The intersection algorithm Daniel seems to be the standard one, so we'd definitely want to use something pretty similar.  But as always we need to avoid creating temporary objects, which'll probably make it look pretty ugly compared to a lot of the reference implementations I've looked at.

Thanks!  I've been working on this for the past half week on and off.  I don't think it would be to hard to integrate what I've written with hitbox polygons, but I think this may make the program less flexible.  I am not that familiar with how certain shapes match up with certain hitboxes.  My biggest concern is diagonal lines which can simulate arcs.
I'm basing it off of the tutorials  at http://www.redblobgames.com/articles/visibility/ and http://ncase.me/sight-and-light/.
Both these sites contain excellent open-source implementations.
Anyways, I'll continue working on it; it is not where I want it yet.

I paused my work on it, but you can see the current progress in my raycast2 branch. I wrote some tests, implemented iteration in the broad-phase and the intersection algorithm. However, they are not connected yet. I was planning on continuing the development on it during summer, but feel free to do so before :)


IntelliJ Inspector panel crashes when resizing the window

Steps to Reproduce

Start a Flutter app in debug mode on macOS + IntelliJ
Open Inspector
Resize IntelliJ window
observe the Inspector window doesn't update and is rendered incorrectly.
Resize the Inspector panel
observe crash

Video

Logs
none?
[✓] Flutter (Channel master, 1.25.0-5.0.pre.52, on Mac OS X 10.15.7 19H15 darwin-x64, locale en)
    • Flutter version 1.25.0-5.0.pre.52 at /Users/ryjohn/code/github/flutter/flutter
    • Framework revision 9e5c8771d4 (23 minutes ago), 2020-12-03 08:59:31 -0800
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/ryjohn/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 51.0.3
    • Dart plugin version 202.8070

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.15.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 87.0.4280.88

• No issues found!

Thanks, your video is private but I can reproduce after resizing many times
Preview

flutter doctor -v
[✓] Flutter (Channel master, 1.25.0-5.0.pre.64, on macOS 11.0.1 20B29
    darwin-x64, locale en-GB)
    • Flutter version 1.25.0-5.0.pre.64 at /Users/tahatesser/Code/flutter_master
    • Framework revision 4d4d017aa5 (4 hours ago), 2020-12-03 21:38:10 -0800
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS
      14.2
    • macOS (desktop)      • macos                     • darwin-x64     • macOS
      11.0.1 20B29 darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google
      Chrome 87.0.4280.88

• No issues found!

I still see a crash when I resize the window quickly, but now I see a small window without any information:

Related to flutter/devtools#2598

Related to flutter/devtools#2598

cc @helin24 @kenzieschmoll

cc @helin24 @kenzieschmoll

cc @jacob314

cc @jacob314

@johnpryan Hi,
Since the related devtools issue seem to have been fixed already https://github.com/flutter/devtools/issues/2598, can this issue be closed ?

Yes, we can close this 👍


Sync Timing for Contacts

Would it be possible to add a section to this page that clearly articulates how the Contact Sync operation functions on an ongoing basis.  Once established, is the process automated, or does the user need to manually trigger the contact sync?  If it's manual, is there any way to automate the process?
The current documentation is unclear as to how the sync process should occur on an ongoing basis AFTER it's set up.
Thank you.
Chris

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: be2a9cdb-ccff-0083-16af-6eaa309416f4
Version Independent ID: 2897af77-749b-da01-ec4d-54976ed10bcc
Content: Share contacts between Business Central and Outlook - Business Central
Content Source: business-central/admin-synchronize-outlook-contacts.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Hello,
Thank you for your feedback! Our apologies for the very long wait for an answer!
A member of our team has at long last reviewed your feedback. The article has been updated to answer your question.


How to visually indicate matches when consuming grep -nH output?

I have installed via cargo install hgrep under MINGW64 (Windows 10).
Assuming an input file like myfile.c:
/*
 * foo has changed [...] and is now a 2-parameters function
 */
// foo(24)
int myvar = foo(42, 28);

... then if I run hgrep on the file directly (e.g. hgrep foo myfile.c) - then the matches are nicely indicated (in addition to corresponding line numbers):

... however if I try to Eat grep -nH output (e.g. grep -nH foo myfile.c | hgrep) - then the matches are NOT indicated anymore, only the corresponding line numbers are:

Can I somehow get the matched substrings to be indicated, also when consuming grep -nH output?

Highlighting matches is a feature only for built-in ripgrep. So it is not available when using hgrep with grep -nH. This is a limitation of the format of -nH option. It does not include column numbers of the match so it is not possible to know the match positions.

I do not want to reopen the issue, just wanted to say many thanks for the answer, @rhysd - that explains it. And also wanted to comment on this:

It does not include column numbers of the match so it is not possible to know the match positions.

If one uses grep --color=always, then wouldn't it be possible to look for the ANSI color escape codes, and use their positions as match positions? If we do grep --color=always foo myfile.c > out.txt, we can see that e.g. last line match is actually int myvar = foo(42, 28);, where  would be start of (default grep) red color for match, and  for end of match ... Or in other words - if  = 0x1B = ESC = \e = ^[, then ^[[01;31m^[[K would represent the start of match, and ^[[m^[[K the end of match.

yes @sdbbs  is right one could parse the color codes, although non default codes etc cause issue and parsing adds overhead and complexity.   Another option would be to pass the highlight term to hgrep with an optional arg.   I think the best option would probably be just something like --grep-in arg and then you could do something like grep MyKeyword | hgrep --grep-in MyKeyword .   Yes hgrep would be re-searching for the match on the line specified, but this is decently low overhead and only an option to enable.
The reason being to potentially allow say sorting or alternate programs to feed hgrep grep compatible data without losing  the highlighting match hgrep provides.    An alternative I currently do is to exact the matched files and pass them as args to hgrep and have it regrep each completely.  Not pretty (or efficient) but works.


5 of my accounts were permanently suspended within 3 days.

Not sure why this is happening but 5 of my accounts have been suspended within the last 3 days. Please post below if you are also experiencing this. Not sure if MAC address is being tracked or IP.

This happened to all my accounts last month. Whenever I tried to claim a reward, it just said:
''There's an issue with your account or order. Please contact Microsoft Rewards customer support for assistance.''
I later got a new phone number and created a new account, but the same issue occurred when I tried to redeem a reward. The weird thing is that it still lets me do the quiz and earn points. I just assumed I got IP banned, so I gave up. Is the same thing occurring with you?

Same here, got banned like 8 out of 13 accounts, used the same number in more than 5 accounts, so im not sure if thats the problem, but seems like they are taking action.

all 14 of my accounts were banned. I used 4 per phone number and 3 on 2 phone numbers. I used them for about 3 months. Not sure what happened. Maybe there needs to be a longer delay between login for each account. Maybe the entire process needs to be slowed down with longer sleep timers within the functions.

I've been using the same script but faster timers, so i don't think the timers are the problem here. Maybe adding a long timer between accounts and IP/MAC changer?

I have no clue how to do that

chrome got updated , so I updated chromedriver but it says this:
"Traceback (most recent call last):
File "C:\Users\loren\OneDrive\Documenti\GitHub\Microsoft-Rewards-Farmer\ms_rewards_farmer.py", line 1544, in
browser.get(BASE_URL)
AttributeError: 'NoneType' object has no attribute 'get'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\loren\OneDrive\Documenti\GitHub\Microsoft-Rewards-Farmer\ms_rewards_farmer.py", line 1547, in
FA.write('\n[ERROR] Could not Loading https://rewards.bing.com/.')
ValueError: I/O operation on closed file.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\loren\OneDrive\Documenti\GitHub\Microsoft-Rewards-Farmer\ms_rewards_farmer.py", line 1801, in
browser.quit()
AttributeError: 'NoneType' object has no attribute 'quit' "
can sm1 help?

Does everyone who got their account banned was using the software on multiple accounts? I was only using one and I'm still good, but I stopped using the script since a few days until we get more information. Would love to hear more details from other people.
@lollogiaco your question is unrelated to this topic and should have been posted in a different thread. But just update your chrome-driver to match your chrome version. Try pip install --upgrade webdriver-manager

Does everyone who got their account banned was using the software on multiple accounts? I was only using one and I'm still good, but I stopped using the script since a few days until we get more information. Would love to hear more details from other people.
@lollogiaco your question is unrelated to this topic and should have been posted in a different thread. But just update your chrome-driver to match your chrome version. Try pip install --upgrade webdriver-manager

I have been using 5 accounts for years without issue.  A few years back, they did reach out and I told them that they are just different family members using the same computer.

Tell us if you resolve with support

No reply so far.  Not holding my breath.  Feel free to submit support request too and see if you get response...

UPDATE: It seems my accounts were unbanned somehow (I didn't speak to customer service because I heard they ban you forever if you do that), and I was able to claim all rewards.
I was able to sign in and get points manually, though, but it seems the bot will not work now due to the old or new ChromeDriver. Perhaps Microsoft has finally cracked down on automated bots?


https://issues.redhat.com/browse/CWFHEALTH-908

hi @qixiang, the source code is finished but I'm not sure how to Mock a Koji call for testing. I tried to duplicate the unit test for "get_ocp_versions_range" but It seems that even when I pass in a value for an "id" in the unit test it is saying that the id field is missing in the test error. Do you have any suggestions?

hi @qixiang, the source code is finished but I'm not sure how to Mock a Koji call for testing. I tried to duplicate the unit test for "get_ocp_versions_range" but It seems that even when I pass in a value for an "id" in the unit test it is saying that the id field is missing in the test error. Do you have any suggestions?

The test fails happen in tests/handlers/botas/test_botas_shipped_advisory.py, not the new test case you added, the existing test cases need to be adjusted because you changed the implementation.
And I'd prefer using Pyxis instead of koji/brew to get the lables.

hi @qixiang, the source code is finished but I'm not sure how to Mock a Koji call for testing. I tried to duplicate the unit test for "get_ocp_versions_range" but It seems that even when I pass in a value for an "id" in the unit test it is saying that the id field is missing in the test error. Do you have any suggestions?

The test failures happen in tests/handlers/botas/test_botas_shipped_advisory.py, not the new test case you added, the existing test cases need to be adjusted because you changed the implementation.
And I'd prefer using Pyxis instead of koji/brew to get the lables.

Changes were made to use Pyxis instead of Koji. Also, I'm not too familiar with the Mock tests in Freshmaker; what updates in the unit tests should be made to accommodate for these changes? I see the issue is with the assertionNotEqual within test_botas_shipped_advisory.py but I don't know what to add to make this unit test work :open_mouth:

update: Mocked the is_hotfix_image to always return False for existing test cases and added new test cases in test_pyxis.py. Will add more tests tomorrow to test that hotfix_images are really filtered

LGTM, just minor comments. @ronnyhlim btw, do you know whether normal images (operator and operand images) are also impacted?

So I've asked and was told that an operator hotfix will consist of an operator image (containing the hotfix) and an operator bundle image (to allow index delivery and customer deployment). With that as you mentioned, we would need to change the rebuild_images_on_rpm_advisory_change.py. Would we want to update filter_out_not_allowed_builds()?

So I've asked and was told that an operator hotfix will consist of an operator image (containing the hotfix) and an operator bundle image (to allow index delivery and customer deployment). With that as you mentioned, we would need to change the rebuild_images_on_rpm_advisory_change.py. Would we want to update filter_out_not_allowed_builds()?

I filed CWFHEALTH-1132 to track this.
filter_out_not_allowed_builds is used to filter with the configurable rules, which is not suitable for this case, and you will need to get all hotfix images first before processing which is non-operational.
https://github.com/redhat-exd-rebuilds/freshmaker/blob/e23a4ffb8f0317082005ca2ecb3df634a611a025/freshmaker/lightblue.py#L1623 is a good place to filter out these hotfix images.
btw, please avoid pasting internal links to public.

So I've asked and was told that an operator hotfix will consist of an operator image (containing the hotfix) and an operator bundle image (to allow index delivery and customer deployment). With that as you mentioned, we would need to change the rebuild_images_on_rpm_advisory_change.py. Would we want to update filter_out_not_allowed_builds()?

I filed CWFHEALTH-1132 to track this.
filter_out_not_allowed_builds is used to filter with the configurable rules, which is not suitable for this case, and you will need to get all hotfix images first before processing which is non-operational.
https://github.com/redhat-exd-rebuilds/freshmaker/blob/e23a4ffb8f0317082005ca2ecb3df634a611a025/freshmaker/lightblue.py#L1623
is a good place to filter out these hotfix images.
btw, please avoid pasting internal links to public.

gotcha, all changes have been made and internal links have been removed!


Fix #200 clear hostname when you click add or remove

Added the feature to clear the host name when you click add remove

Looks good, one test failed as I was using the same lab but all good !


How to get started on VS Code

The Readme file says to create F# Forms application on VS Code
Could you elaborate this step? Is it possible to use VS Code at the moment?

@prashantvc You can edit in VS Code but you'll have to run/deploy/debug using Visual Studio


Bug: The demo (index.html) throwing error "Uncaught UnsupportedVersion at versionCheck"

Describe the bug
Unable to run the surrealdb.wasm in Chrome browser due to the error above.
Steps to reproduce
I clone the latest source from surrealdb.wasm repo and run the following commands:
pnpm i
make build
pnpm serve

Then, I open http://<IP_ADDRESS>:8000/ in the chrome browser, the demo (index.html) is loaded successfully. But when I tried running await surreal.connect("indxdb://test") in browser console, it is throwing the following error:
Uncaught UnsupportedVersion
    at versionCheck (http://<IP_ADDRESS>:8000/node_modules/surrealdb.js/dist/esm.bundled.js:1:34314)
    at Surreal.connect (http://<IP_ADDRESS>:8000/node_modules/surrealdb.js/dist/esm.bundled.js:1:42891)
    at async <anonymous>:1:1

Expected behaviour
It should connect successfully.
SurrealDB version
surrealdb.wasm v1.0.0-beta.13
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

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

Tested and it works in v1.0.0-beta.14.


KAFKA-4772: [WIP] Use peek to implement print

PROPOSAL/DISCUSSION FOR KIP-132.
Tackles KAFKA-4772 and KAFKA-4830.
The functionaliy of KeyValuePrinter is replaced with a printAction that
is being passed to KStreamPeek. We therefore can get rid of
KeyValuePrinter.
KStream.print was extended to handle KeyValueMapper in order to provide
users the option to change output of K and V. Therefore, constructors of
KeyValuePrinter as well as KeyValuePrinterProcessor have to be adapted. The default case
where no mapper will be passed, is still covered by the previous comma
separated out of K, V.

@backender Please do a single PR per JIRA.

@backender As it seems your are not working on this any longer, would you mind closing this PR? Thx.


Fuzzy check logic implemented using levenshtein distance algorithm.

Notably could be better:
$ tea run +wget
error: not-found in pantry: wget/package.yml (spilt-tea-101)

did you mean `go.dev`?

would ideally suggest gnu.org/wget

Notably could be better:
$ tea run +wget
error: not-found in pantry: wget/package.yml (spilt-tea-101)

did you mean `go.dev`?

would ideally suggest gnu.org/wget

Yeah, this can be achieved. we need to slightly tweek the algorithm. I will do it.


More portable shebang

See this: https://stackoverflow.com/questions/10376206/preferred-bash-shebang

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 22 Dec 2014 at 3:20

Is it possible to configure the shebang? Maybe using the Intellij Code templates feature?
I personally prefer a simple "#! /bin/bash" over the env line.

"/usr/bin/env" might also be a distro / environment specific path, so what the heck
using env bash we lose the opportunity to add options (like -x for debug mode) to the shebang
the script become less stable as env depends on the PATH
who actually compiles and installs custom versions of bash in locations other than /bin/bash and adds them to the PATH ? (maybe on non-Linux Unixes, MacOS, systems where bash is not installed and you are not root?)

Also see the good points made against using env in the answers to these:
http://unix.stackexchange.com/questions/29608/why-is-it-better-to-use-usr-bin-env-name-instead-of-path-to-name-as-my
http://stackoverflow.com/questions/21612980/why-is-usr-bin-env-bash-superior-to-bin-bash

Good point.
I'll try to use the template feature for new Bash files in the next update.

Thanks, Jan. Also wanted to say that the plugin is great. :clap:

I know this item is closed, but did this get into the latest release (1.5.2)? I also prefer the #!/bin/bash shebang and would like to be able to adjust this feature.
If it was, I was just wondering where it is (can't seem to find it), or if not, do you have any idea as to when it will be released?
And I can't echo loudly enough the thanks for this wonderful plugin.

This is in the latest release (and the one before). You can edit the Bash file type template, available in the IntelliJ settings under Editor->File and Code Templates. The Bash file content will be used to create new Bash files.
The documentation is currently outdated, though.
--
<>< Re: deemed!

Am 09.11.2015 um 19:11 schrieb Craig Holden<EMAIL_ADDRESS>I know this item is closed, but did this get into the latest release (1.5.2)? I also prefer the #!/bin/bash shebang and would like to be able to adjust this feature.
If it was, I was just wondering where it is (can't seem to find it), or if not, do you have any idea as to when it will be released?
And I can't echo loudly enough the thanks for this wonderful plugin.
—
Reply to this email directly or view it on GitHub.

And there it is! Thanks again!

I just adjusted the template to my preference "#! /bin/bash", in Intellij
CE 14.1.5.
Then I created a new empty plain file "test.sh".
Clicking on the "Add shebang line" quickfix still puts in "#!/usr/bin/env
bash".

Only afterwards did I notice the File - New - Bash script option, which
uses the configured template.
So this is good, I just had the wrong expectation (i.e. that the template
would somehow also configure the quickfix).
Thank you!
 Thanks again!
—
Reply to this email directly or view it on GitHub
https://github.com/jansorg/BashSupport/issues/167#issuecomment-155166126
.

--
Oliver Doepner
http://oliver.doepner.net/

I just adjusted the template to my preference "#! /bin/bash", in Intellij CE 14.1.5.
Then I created a new empty plain file "test.sh".
Clicking on the "Add shebang line" quick-fix still puts in "#!/usr/bin/env bash".

Only afterwards did I notice the File - New - Bash script option, which uses the configured template.
So this is good, I just had the wrong expectation (i.e. that the template would somehow also configure the quick-fix).
Thank you!


losing colors when converting Obj->Glb/glTF

Hello everyone! Thank you for this converter. I have a question.
Why am I losing colors when converting from obj to gltf/glb (vertexColors). Is there any way I can save them?

Hi @Algorush, that hasn't been implemented yet. See https://github.com/CesiumGS/obj2gltf/issues/102


Kubernetes v1.0-pre

This change set upgrade the Kubernetes package to that latest upstream v1.0 code.
Two remarks regarding the universe structure:

Having a compressed index in Git makes conflicts inevitable. We need a better solution.
There's too much duplication between package versions. We need to find a way to reuse more stuff.

Ref: https://github.com/mesosphere/kubernetes-mesos/issues/371

Is there an easy way to point a DCOS deploy at this PR to test the updated k8s?

@karlkfi: I think @sttts answered that question on Slack. You can checkout the right branch locally and point your ~/.dcos/dcos.toml to it with the file:// prefix. Don't forget to run dcos package update after that.

/cc @jsancio


Refactored PVR section to RecycleView

Fixes #745

Thanks for this, and sorry for the delay.
I still haven't been able to test this thoroughly, but the code looks good, so i'll merge it as is.
Once again thanks.


Proper round-trip RPC between client and server

There are a number of cases --- for example, changing the user's password --- where we really want to suspend the client until we have a positive or negative response from the server. Up till now we've managed to avoid this by making the protocol stateless, but that's no longer adequate. (The password change code is really ugly.)
We really need a way whereby the client can register a handler which gets called when the server replies to that message.

No longer relevant in the shiny new gruntle world.


Maintainers

Companion PR: https://github.com/keboola/connection/pull/679

@pivnicek can you please update this PR with master. I see here the commits which are already merge. thx


Improved error message, when a markdown file is missing …

Describe the PR
Removed pkg/errors dependency from whole project tree.
Finish PR #413
Removed an error handler that was introduced to fix #432 . error is nil all the time , the code works the same without that piece of code.
Relation issue
None
Additional context
None.

Good job.

Why does have more dependencies in go module?

if you speak about "go.mod"

package "github.com/gin-gonic/gin" is used in example/basic/api
package "github.com/satori/go.uuid" is used in example/celler/model/account.go
package "golang.org/x/tools" is used in operation.go

It seems necessary.

@swaggo/swaggo-core-team IMO, I think github.com/gin-gonic/gin and
github.com/satori/go.uuid these packages don't need to add in go.mod because all of these only be used in example.  I think add go.mod in examples code itself is better.

Sound good.
If so, are dependencies ignored for example code?

no I mean github.com/gin-gonic/gin and github.com/satori/go.uuid these should be declare   at their own example go.mod like:
github.com/swaggo/swag/tree/master/example/basic/go.mod
github.com/swaggo/swag/tree/master/example/celler/go.mod

not added in github.com/swaggo/swag/go.mod

OK. I understand.

I create PR.

can not multi go.mod.
package github.com/swaggo/swag/example/celler: unknown import path "github.com/swaggo/swag/example/celler": ambiguous import: found github.com/swaggo/swag/example/celler in multiple modules:


Deployment fails with a media service error in northcentralus

FYI - when I tried to deploy to LOCATION="northcentralus" I got the following error for the media service:
{
    "status": "Failed",
    "error": {
        "code": "BadRequest",
        "message": "Creation of new Media Service accounts are not allowed as the resource has been deprecated.",
        "details": [
            {
                "code": "MediaServiceAccountCreationDisabled",
                "message": "Creation of new Media Service accounts are not allowed as the resource has been deprecated."
            }
        ]
    }
}

Changing to LOCATION="eastus" deployed without errors.

Duplicate of #501

Hello, I have run into this issue with new deployments. It appears the block went into place the end of Jan 2024 for New media Services, noted in the guide posted. Any news on the fix?

This has been addressed with a PR in main - you should not be seeing issues now if you pull latest


Add Countdown Flipclock

[ ] Set the correct time
[x] Figure out why jquery isn't loading
[x] Load countdown.css in countdown.php template

I hereby approve this code.

This now has conflicts, and we might be able to remove a lot of the CSS as I have asked JSDelivr to host it.

We have a date. September 5th. So as soon as we get this sorted it can be put up.

[ ] Can we add a "Days" section or would that be too much work?
[ ] Do we know what timezone this is set to? Is it UTC? We need it to be on the same timezone no matter who's viewing so it ends a the right time for everyone

The countdown on it's own is a little vague for someone who is first visiting the site. We should include some hype text above it so people know what we are counting down to.

hype text

It's intentionally vague. We never include text indicating what it's for

https://github.com/jsdelivr/jsdelivr/pull/13425 being merged will neaten this up.

I'm not sure if we have modified it here at all, but there's now a CDN hosted version of flipclock.css at https://cdn.jsdelivr.net/g/flipclock@0.7.7(flipclock.css)

When we push this to master, we should push translations for #1157 and hopefully get most of the content translated before release.

[ ] Push Loki branch translations


BME680 sensor will not be detected on 0.81.5 anymore works with 0.81.2

**Home Assistant release with the issue:0.81.5

**Last working Home Assistant release (if known):0.81.2
**Operating environment (Hass.io/Docker/Windows/etc.):Hass.io

**Component/platform:https://www.home-assistant.io/components/sensor.bme680/
**Description of problem:Sensor BME680 not detected at 0x77 Works with 0.81.2
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 0
  longitude: 0
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: UTC
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123
http:
  # Secrets are defined in the file secrets.yaml
  api_password: xxxxx
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
# updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Sensors
sensor:
  # Weather prediction
  - platform: yr

# Sensor BME680
sensor 1:
  - platform: bme680

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

Traceback (if applicable):

**Additional information:

Have you tried 0.81.4? I just re-enabled the HA BME680 module as a test and it’s working fine for me at 0x77. (I’ve switched to using a custom Python script that uses the Bosch BSEC library to talk to the sensor and then submits the data to an MQTT broker. It provides much more realistic IAQ values, along with realistic temperature and humidity values. I’ll be uploading it to GitHub soon.)

Sorry, I must have misread your initial post and thought you were on Hassbian. Let me throw Hass.io on a spare Pi and see if I can write up some instructions for installing i2ctools on it. It’s a pretty critical package for debugging I2C issues.


Working WASIX API

Before any consideration for merging, compatibility with @wasmer/wasi is broken, so the package under @wasmer/wasix to prevent accidental breakage. No consideration was made to make it 1-1 compatible.
I tried to stay as close as possible to wasi-web in hopes of being able to just copy/sync in the future.
Added

networking via fetch
threading via workers
TTY (immutable unless handled by JavaScript consumer)
dynamic NodeJS polyfills for crypto, fetch, & Worker
WasiConfig options "concurrency" (1-16) & "tty" (starting TTY State)
console_error_panic_hook, wee_alloc, & tracing features

Changed

IO now using WritableStream/ReadableStream for more interactivity.
wasm-pack wasm artifact is not inlined, node uses node:fs to load instead of fetch
file Read API now more closely resembles WebAPI (Blob/File)
init() arguments and behavior, to avoid problems with Workers using init()
enabled Reference Types, enabled WeakRefs, added -Zbuild-std=panic_abort,std to scripts
Modernized browserlist, will not be as compatible with outdated or LTS browsers
some simplifying naming changes

Todo

[ ] create tests for new API
[x] update examples
[x] update documentation
[x] fix CI for nightly requirement

Having trouble getting tests to work, wasix-libc is importing "wasi" "thread-start" instead of "wasix_32v1" "thread_start". I'll have to wait for someone to get back to me on that before I can make tests with threads.
Is there perhaps a way to use a custom runtime for the integration tests in main repo? I'm not familiar with the wasmer workspace so I'm kind of just shooting in the dark here.

Hey @WanderLanz , this PR is awesome work.
We want to add some of the bits of it back into the Wasmer repo (so it's available for anyone trying to compile Wasmer to the browser), but most of the glue things that you created look great. Really good work on updating everything, including reworking current tests.
We'll probably rebase your PR with the new one once things get merged upstream.

@syrusakbary Awesome! I'm glad it'll be of help. Bundling was half the headache, as usual, so hopefully everything goes smoothly for everyone.

Hey just checking back in, it seems like @`Michael-F-Bryan already got the useful parts in the wasix branch, I'll go ahead and close this. Thank you!


Fix artifact naming issue

Reverts the commit that changed to the Spark 2 naming convention on the master branch. Moves to the ADAM release scripts for future releases, which branch then release.

CC @akmorrow13 @heuermh for review.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/bdg-utils-prb/81/
Test PASSed.

Fixes #79

lol I was just in the middle of doing this. Will abort. LGTM.


UI customize - support custom for @link-color

Open for https://github.com/apache/cloudstack-primate/issues/442
@rhtyd cc @svenvogel I've completed this task. Please review it. Thanks.

@blueorangutan package

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/445 (JID-2089)


Download the leptonica source from github

1.74.2 is no longer available from the leptonica website. But anyway, it seems safer going forward to download it from github. It's https, and it won't disappear as easily. Also, this is the same source used by travis, so there's less chance of shipping something untested.

CC: @DanBloomberg

Just to be clear, the tarballs on leptonica.org are all configure/make ready.  On github, releases 1.73 - 1.74.2 are checkpoints of the github source, so one needs to use autotools to generate configure, etc.  Releases 1.74.3 and going forward are configure/make ready tarballs, generated directly from github source but with the necessary added files.
1.74.3 was flawed, in that I had included several files that should have been removed after testing.

Thanks! Now you can install tesseract from the edge channel:
sudo snap install tesseract --edge

And it will be autoupdated every time master changes. I will do some testing before moving it to stable.