resize function bug

Question describe

Bug position: data_manage.py->resize_omage function

code:
im_arr = imread(image, mode='L')
 r, c = np.shape(im_arr)
 if c > input_width:
     c = input_width
     ratio = float(input_width) / c
     final_arr = imresize(im_arr, (int(32 * ratio), input_width))
 else:
     final_arr = np.zeros((32, input_width))
     ratio = 32.0 / r
     im_arr_resized = imresize(im_arr, (32, int(c * ratio)))
     final_arr[:, 0:np.shape(im_arr_resized)[1]] = im_arr_resized
 return final_arr, c

detail:
if the shape of im_arr is (22,92),the programe will run code in 'else',so the shape of im_arr_resized will be(32,int(c*(32/r))) i.e (32,int(92*(32/22)))=(32,133).
At this code : final_arr[:, 0:np.shape(im_arr_resized)[1]] = im_arr_resized.You just make the fina_arr[ : ,0 : 133]=im_arr_resized,but the max_width of final_arr is 100

Just to clarify, you believe that the resulting array should be (32, 100) or (32, 133)?
Using a slice like in the code pictured should produce a (32, 100) array as expected and desired.

@sevenHsu 我看这里的代码也有这个疑惑，test的时候这里就报错了。我改成如果长度太长，只取前面100列，感觉这样还是有问题的，不能识别后面的文字了。
还有一个问题，我把放入session run之前的batchx图片保存下来，它是被reshape了的，宽和高纬度交换的时候，所以保存出来的看不出字的形状，感觉很奇怪啊

@Belval I can't understand your answer, when i try a picture in  (22,92), will be (32,133) in your code , then will error in next code.
another question, when you prepare training data, from raw_batch_x to batch_x in function "__generate_all_test_batches", you just reshape, i think you should use transpose to change the width and height axis. save the batch_x in this step is not a readable picture anymore.

@xxlxx1 I reproduced the problem. We could simply change the line to final_arr[:, 0:input_width] = im_arr_resized[:, 0:input_width]?
Please tell me if it works on your size. I got this result:
Before:

After:

from utils import resize_image
from scipy.misc import imsave

im = resize_image('test3.png', 100)
print(len(im[0]))
imsave('result.png', im[0])

I'm investigating you other question.

For your second question:
There indeed seems to be a big problem with the reshaping, I changed it to np.swapaxes, which gives the desired result.
I'm currently retraining the whole thing, I'll keep you updated.

Thank you!

Please check my last commit, it should fix both the issues mentionned here.


Provide Dockerfile for a self-contained poll-server

A Dockerfile which creates a docker image containing a running poll-server would have several benefits:

easy setup (especially for those who don't know Ruby/gem/rake/MySql etc.)
reproducible setup for different environments
encapsulation of services
avoids 'pollution' of a working system in case you have to uninstall poll

I tried to setup one based on Ubuntu 15.4 but failed to setup database connection. I don't want to install poll together with Ruby and MySql on my desktop system

After 4 years no news...


Data quality issues

Hello, thank you for your impressive work! When I was visualizing the data, I found that some documents had problems such as missing detection boxes and incomplete formula detection boxes. Please help confirm whether there are problems with data quality. Thank you!
The data I downloaded from huggingface, the randomly selected files are:
astro-ph.CO/1804.05921
astro-ph.CO/1005.1278

@huangfw
Thank you for your attention to our work. It should be noted that DocGenome is annotated automatically, so the data quality in the DocGenome dataset is not consistent. We checked the two examples (astro-ph.CO/1804.05921 astro-ph.CO/1005.1278) you mentioned, and indeed the detection boxes for the formulas are inaccurate. This issue is mainly caused by macro definition problems in the LaTeX source code, and we will address these issues in the next version.

@huangfw Besides, we have performed quality grading on all automatically annotated data in DocGemone, assigning it to three quality levels: tier-1, tier-2, and tier-3, as shown in Figure 3 in DocGenome paper. You can choose data with a quality level of tier-1.

@huangfw  Hello,  we have added the information about the different quality levels of the trainset for reference. We will also update the file structure in more detail later.


Add sample_rate configuration

This should mimic the behavior in Java, which we should also add to client-dev spec.

Gonna see if i can add some simple tests around this, though not sure how reasonable it is to mock this.


Set SP and VTOR in Reset vector

I'm opening this PR for discussion after today's meeting, I'm not really sure I want it to be merged but I thought it might be helpful to see what it could look like.
VTOR
The VTOR register offsets the vector table from the default 0x0000_0000 to a user-provided address, which is required if the user's vector table is not at the start of memory (for example, because a bootloader is present).
We occasionally get people asking for help because none of their interrupts are working and it turns out their bootloader does not set VTOR, so interrupts were not taking the right vector. Typically this is on platforms with manufacturer or vendor bootloaders rather than ones the user has installed, so they may not even be aware the bootloader is running.
It's a hard problem to debug and we could resolve it by having cortex-m-rt always write VTOR at startup, since it knows what the vector table address is. On ARMv6-M the VTOR register is optional, but if not present it must be RAZ/WI, which means it's safe to write to it even though it won't have any effect. On ARMv7-M and ARMv8-M VTOR is always implemented. In practice no Cortex-M0 core has VTOR, but many Cortex-M0+ cores do.
However, this write is useless for the vast majority of applications, using up flash space and boot time without any benefit. I think bootloaders should always be responsible for setting VTOR, and for example this document from Arm agrees, but clearly not all bootloader authors read it.
SP
This seems even rarer, but we have also had reports of debuggers resetting the chip by jumping to the reset vector without setting SP (the stack pointer, which is normally set to the first word of the vector table by the CPU at boot). I don't know what else those debuggers aren't setting, but from reports it sounds like setting SP is enough to get some basic functionality. This seems even more cursed (what else should we set, if we can't rely even on this?) but again is pretty easy to include if we wanted to. It's possible some bootloaders also fail to set SP before jumping to user code, although I don't recall hearing about that and it seems even more egregious. It would probably be helpful to have some more specific references to situations where this is necessary (see related issues).
Making this optional
At the moment the reset vector is pre-built and distributed as a binary, so there's no simple way to control this behaviour with feature gates (except for shipping a lot of different binaries, one for each architecture for each set of features). In the future when global_asm! becomes stable, it will probably be easy to feature-gate this functionality, and then it could be pretty easily enabled by users who need it and not others. Since many of the common use cases are for specific platforms which typically have a commonly-used HAL, those HALs could enable the feature for their users, so many users would not need to know about VTOR.
So, one (good?) option is to wait for global_asm! and then revisit this.
Before or after pre_init?
I've put the new instructions before pre_init so that user code calling pre_init could choose to override them. I don't think it's likely any user code would need to run before these instructions: there's only 5 of them, so it's unlikely e.g. a watchdog would fire, and they don't access RAM, so it's unlikely RAM would need enabling, and they only set up the chip to a state it should normally be in after boot (well, VTOR is usually 0, but what we write should be equivalent).
Related issues
These topics have been requested/discussed before:

#283 requesting pretty much exactly this addition, "considered as protective programming", "mimic the HW reset behavior to start off in the same environment when the software is launched from a debugger"
#55 has a bootloader that doesn't set VTOR
#254 STlink debugger not setting SP correctly
#102 SP not being set or seen by a debugger correctly

And besides those issues, it comes up occasionally on the Matrix chat.

One drawback is this will break firmwares using Nordic's nRF softdevices.
The softdevice lives at the start of flash, the application firmware is after it.. The softdevice handles some irqs, then forwards the rest to the application. Setting VTOR will break it, because all irqs go straight to the application so the softdevice won't be able to handle theirs.
I'd be OK with this being optional, opt-in though!


Fix test_webSocket hang

Because the test server sends a close message shortly after sending a pong, the connection might close before our task handles the pong and calls its completion handler. In this case, the pong completion handler is never called, so try await task.sendPing() hangs indefinitely.
This PR cleans up pongCompletionHandlers on error/close and minimally fixes the test to allow the case where the server closes the connection before the pong is handled.

@swift-ci please test


Add rados.py and rbd.py to glance and cinder venvs

This needs to be rebased, and I think we need a set of tasks to do this for package based installs too, which is a different path so maybe need a second set of tasks.


Multiline predicate mangled by DomainReader but handled correctly by plansys2_pddl_parser

Consider the case of a PDDL domain definition with a predicate defined with newlines between the arguments, like this:
(:predicates
    (foo ?foo - foobar)
    (bar
         ?foo - foobar
         ?bar - foobar
         ?baz - foobar
    )
)

This is treated differently be different components of PlanSys2. Running ros2 run plansys2_pddl_parser parser correct groups the arguments and returns a domain like this:
( :predicates
        ( foo ?foo - foobar )
        ( bar ?foo - foobar ?bar - foobar ?baz - foobar )
)

However, when read by the DomainExpert as a model file, DomainReader::get_predicates stores the predicates block (sans comments and newlines) before DomainReader::get_joint_domain reconstructs the predicate block assuming one full predicate per newline which are then passed through a std::set as deduplication with the side-effect of reordering the lines, leading to the following nonsensical block being passed to the POPFPlanSolver::isDomainValid check which syntax errors:
(:predicates
         ?bar - foobar
         ?baz - foobar
         ?foo - foobar
    (bar
    (foo ?foo - foobar)
    )
)

I checked the documentation and could not find a requirement that PDDL predicates not contain newlines and the referenced paper for the PDDL definition has BNF syntax for the language that also doesn't appear to settle this issue.
I'm happy to contribute a PR, but which behavior is correct - should the parser reject the split predicate, or should the DomainReader parsing handle this case?

Let me check if it has a quick fix :thinking:

Hi @Bckempa
This is clearly a bug, and the correct behavior for the DomainReader is to handle this case.
It would be great to have a PR from you. If you prefer, I can try fixing it, but you may want to contribute. Let me know if I can help you :)
Thanks!!!

The easiest way would be to leverage the PDDL parser within the DomainReader


chore(dashboard): cleanup home page

In this PR, I clean up a bunch of old code that was part of the initial Next.js implementation. I also tried to restructure the home page and the workspace overview page to make them more consistent with how we structured other pages.
WHAT

🤖 Generated by Copilot at 93910f2
This pull request adds internationalization and localization support to the Next.js dashboard using the next-translate-plugin module and adds English translations for the common, home, and overview pages. It also updates the dashboard to use the new project terminology and GraphQL schema instead of the old application concept, and fixes some UI and query issues related to the project overview page. Additionally, it adds a changeset file, a metrics test case, and an ESLint ignore pattern.

🤖 Generated by Copilot at 93910f2

Dashboard evolves
Project replaces application
Winter of refactoring

WHY

HOW

🤖 Generated by Copilot at 93910f2

Add a changeset file to document the changes to the @nhost/dashboard package (link)
Rename the application concept to project and use the new GraphQL schema and queries throughout the dashboard application (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
Add a new section for the metrics component in the overview page and adjust the layout and responsiveness of the page (link, link, link, link)
Add the next.config.js file to the dashboard folder and use the next-translate-plugin module to enable internationalization and localization support for the dashboard application (link, link, link, link, link, link)
Add the English translations for the common UI labels and messages used in the dashboard application, such as the menu items, the account settings, and the theme options (link)
Add the English translations for the UI labels and messages used in the home page of the dashboard application, such as the title, the search input, the create project button, and the welcome message (link)
Add the English translations for the UI labels and messages used in the overview page of the dashboard application, such as the metrics labels and tooltips, and the helper text (link)
Add the @nhost/apollo dependency to the dashboard/package.json file, which is a custom Apollo client that integrates with the Nhost authentication and storage services (link)
Remove the OverviewMigration component from the overview page, as it is no longer relevant for the new projects that use RDS by default (link, link)
Remove some unused import statements from the ApplicationErrored.tsx file, such as the pluralize, prettysize, and node-pg-format modules (link)
Delete the ApplicationMigrating.tsx file, as it is no longer needed for the new projects that use RDS by default (link)
Add a skip option to the useGetApplicationStateQuery hook in the ApplicationErrored.tsx file, to avoid making unnecessary queries when the currentProject variable is undefined or null (link)
Add a skip option to the useCurrentWorkspaceAndProject hook in the ChangePlanModal.tsx file, to avoid making unnecessary queries when the currentWorkspace variable is undefined or null (link)
Add a refetchQueries option to the useDeleteApplicationMutation hook in the ApplicationInfo.tsx file, to refetch the GetAllWorkspacesAndProjectsDocument query after deleting a project, to update the cache and the UI (link)
Add a refetchQueries option to the useUnpauseApplicationMutation hook in the ApplicationPaused.tsx file, to refetch the GetAllWorkspacesAndProjectsDocument query after unpausing a project, to update the cache and the UI (link)
Add a refetchQueries option to the useUpdateAppMutation hook in the ChangePlanModal.tsx file, to refetch the GetApplicationPlanDocument query after updating the project plan, to update the cache and the UI (link)
Update the URL for the app_state_history table in the Hasura console in the ApplicationInfo.tsx file, to use the currentProject.id as the filter value instead of the currentApplication.id (link)
Add **/next.config.js to the ignorePatterns array in the .eslintrc.js file, to prevent ESLint from linting the Next.js configuration file, which may contain non-standard syntax or require statements (link)

Codecov Report

Merging #1816 (a15a4db) into main (a8a20cf) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #1816   +/-   ##
=======================================
  Coverage   87.23%   87.23%
=======================================
  Files          83       83
  Lines        9006     9006
  Branches      538      538
=======================================
  Hits         7856     7856
  Misses       1150     1150

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Should be able to use libinput as alternative to evdev

Issue description
Currently libinput is only used for touchpads, but it's capable of handling all input devices.

I need this. Has anyone found a way to hack around the issue?
This isnt my field but it's high on my list; my thinkpad is a pain to use without middle-button scroll...
As it is, enabling libinput doesnt really enable it!

Looking at #19022 I found a fix for my problem from @DamienCassou
{
  services.xserver = {
    libinput.enable = true;
    synaptics.enable = false;

    config = ''
      Section "InputClass"
        Identifier     "Enable libinput for TrackPoint"
        MatchIsPointer "on"
        Driver         "libinput"
      EndSection
    '';
  };
}

I took out
        Option         "ScrollMethod" "button"
        Option         "ScrollButton" "8"

Because libinput takes care of that by itself very well.

I've just hit this myself while trying to make use of the "Disable While Typing" functionality that disables the touchpad for 1 second upon key-press.
At the moment I have:
    xserver = {
      enable = true;
      ...
      libinput = {
          enable = true;
          clickMethod = "clickfinger";
          scrollMethod = "twofinger";
          tapping = true;
          disableWhileTyping = true;
      };
    };

And I can confirm that his option is enabled on the touchpad:
$ xinput list-props 12
Device 'ETPS/2 Elantech Touchpad':
	Device Enabled (142):	1
        ...
	libinput Disable While Typing Enabled (297):	1
        ...

But pressing the keyboard does not disable the touchpad.
This happens because only the touchpad is handled by libinput. The keyboard is handled by evdev.

However, in this case the keyboard doesn't seem to recognise all keys, likely due to interference of some other setting in /etc/X11/xorg.conf.
Looking at the code, evdev is hardcoded at https://github.com/NixOS/nixpkgs/blob/07bc859e9acec3cc6f7a8129e4b05a7584fef209/nixos/modules/services/x11/xserver.nix#L567
There doesn't seem to be an easy way to override this.
Does anyone have any workarounds?

@unode Try https://github.com/NixOS/nixpkgs/pull/31995, the base XkbLayout was causing problems for me.

Hey I have been struggling with this same issue for the last couple of days. I wanted to leave some breadcrumbs for people who might run into this down the line.
I have been trying to enable my touchpad on a dell laptop. I tried the usual options with no luck. (enabling libinput or synaptics in my config). Neither of these seemed to work. But I just made kind of breakthrough that might be helpful to people later.
The short rundown is:
With "libinput" enabled (services.xserver.libinput.enable = true;) rebuilding would create the expected "/etc/X11/40-libinput.conf"
For these changes to take effect I needed to restart X. This can be accomplished by rebooting or forcing it to restart with "systemctl restart display-manager". I had repeatedly been trying to just let it reboot, which was not working.
I discovered that when I would restart X without a reboot cycle, the trackpad would work!
The reason : after a reboot cycle "/etc/X11/40-libinput.conf" is MISSING unless I rebuild the system after booting. Following a rebuild I need to restart X with systemctl.
It seems that during the creation of the /etc directory that occurs during boot, libinput is not built (I have not yet discovered why). I am going to look into why.
In any case I hope this breadcrumb is helpful to someone down the line!


istio proxy access log format config not working

Describe the bug
The latest istio snapshot build: 1.1.0-snapshot.5 allows to customize proxy access log by specifying access log format: https://github.com/istio/istio/blob/1.1.0-snapshot.5/install/kubernetes/helm/istio/templates/configmap.yaml#L25
I tried to set values in the "istio" configmap as following, but it didn't work.
accessLogFormat: '[%START_TIME%] %REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%\n'

Expected behavior
envoy proxy should write log with new format.
Steps to reproduce the bug

change configmap of "istio" with above entry.
restart pilot pod.
create a new istio injected pod, check istio-proxy log. (no access log flowing while firing request)
the new injected istio-proxy container has following config:

             "name": "envoy.file_access_log",
             "config": {
              "format": "[%START_TIME%] %REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL% ",
              "path": "/dev/stdout"
             }
            }
           ] ```

Note; new line "\n" is missing in the runtime config dump of proxy.

And based on https://github.com/envoyproxy/envoy/issues/5193, seems for text formatted log, it needs "\n" in format string. So I guess istio config lost it somewhere between pilot and proxy.

@GregHanson considering you did https://github.com/istio/istio/issues/10056 could you take this one on?

@GregHanson pointed me to https://github.com/istio/istio/pull/11449

resolved by PR #11449


Making a test package

One potential direction to reducing dependency hell.

Moving CSS from BSK to it's own dependency that holds a weak dependency on BSK.
Moving UserScripts from BSK to be owned here.

Also resolved in https://github.com/duckduckgo/content-scope-scripts/pull/65


Refactor some codes, add filter objects, and add support for lable filtering...

refactor&feat&fix&style:
1. Unify parameter types and divide them into two categories: normal parameters kor.Opts and filter parameters filters.Options.
2. includeExcludeLists no longer participates in cmd args binding, and is taken over by filters.Options.
3. The initialization operations of includeNamespace and excludeNamespace are taken over by filters.Options and will only be executed once.
4. Add filters.Framework object to uniformly process filtering logic.
5. All currently supported resources are supported by the kor/used=true tag.
6. Fix the problem that filterOptions.Validate does not take effect
7. Support includeable parameters
The unit tests have passed, but due to the large scope of the changes, more tests are needed.

The original purpose was to abstract the filter framework to facilitate the addition of filter parameters. Other changes are necessary to achieve this goal. #187
now, If we want to add a filter, we only need the following steps：
create filter func
// FilterFunc is a filter that is a function
// If the resource is legal, return true
// example:
// deployment.Spec.Replicas > 0; return true
// meta.GetLabels()["kor/used"] == "true"; return true
type FilterFunc func(object runtime.Object, opts *Options) bool
func TestFilter(object runtime.Object, opts *Options) bool {
	if meta, ok := object.(metav1.Object); ok {
		if meta.GetLabels()["kor/used"] == "true" {
			return true
		}
	}
	return false
}

Set a name
const  TestFilterName = "test"

Add to registry
func NewDefaultRegistry() Registry {
	return Registry{
		LabelFilterName:    LabelFilter,
		AgeFilterName:      AgeFilter,
		KorLabelFilterName: KorLabelFilter,
                TestFilterName: TestFilter,
	}
}


Govee plugin flooding logs with any bluetooth devices it detects

What issue do you have? Please be as thorough and explicit as possible.
My logs are getting flooded with "[Govee] [noble] found device" Logs to the point where I cant really see anything else as It creates around 3-4 logs per minute, meaning everything else gets lost in a flood of new devices logs
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
1 Homebridge UI-x  v4.50.1

Which version of Homebridge/HOOBS do you have?
Hombridge V1.5.0 running Raspbian GNU/Linux Bullseye (11)

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry Pi with Node.js version [v16.13.2]

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
v5.2.0 - It didnt have the issue when I first installed it last October time. I believe it only showed new device logs that identified as govee devices

Which Govee devices do you have that are causing issues? Please include product models if applicable.

Please paste any relevant logs below.

[07/09/2022, 10:10:18] [Govee] [noble] found device [43:6a:92:87:ca:10] [undefined].
[07/09/2022, 10:10:33] [Govee] [noble] found device [07:12:60:0f:61:b0] [undefined].
[07/09/2022, 10:10:34] [Govee] [noble] found device [67:45:ff:0e:01:7f] [undefined].
[07/09/2022, 10:12:50] [Govee] [noble] found device [72:5d:01:ed:21:41] [undefined].
[07/09/2022, 10:14:05] [Govee] [noble] found device [f8:8a:5e:3c:9c:6d] [Oral-B Toothbrush].
[07/09/2022, 10:14:24] [Govee] [noble] found device [38:23:22:bf:f9:c6] [undefined].
[07/09/2022, 10:15:00] [Govee] [noble] found device [fb:d4:be:75:5a:f9] [undefined].
[07/09/2022, 10:15:00] [Govee] [noble] found device [f1:76:86:db:d7:12] [undefined].
[07/09/2022, 10:15:00] [Govee] [noble] found device [f8:95:5b:be:50:9b] [undefined].
[07/09/2022, 10:15:02] [Govee] [noble] found device [e2:fa:da:1d:9b:11] [undefined].
[07/09/2022, 10:15:04] [Govee] [noble] found device [fe:c1:d8:8b:c5:95] [undefined].
[07/09/2022, 10:15:09] [Govee] [noble] found device [ce:65:3a:46:4f:8d] [undefined].
[07/09/2022, 10:15:49] [Ring] Front Door Detected Motion. Loading snapshot before sending event to HomeKit
[07/09/2022, 10:15:55] [Govee] [noble] found device [31:be:02:9c:a0:40] [undefined].
[07/09/2022, 10:15:55] [Govee] [noble] found device [5d:5a:78:a0:98:39] [undefined].
[07/09/2022, 10:15:58] [Govee] [noble] found device [cf:c3:7c:26:02:1e] [undefined].
[07/09/2022, 10:16:06] [Govee] [noble] found device [66:19:17:d0:52:d4] [undefined].
[07/09/2022, 10:16:09] [Govee] [Tv back lights] starting update with params [{"cmd":1,"data":0}].
[07/09/2022, 10:16:09] [Govee] [Tv back lights] starting timer.
[07/09/2022, 10:16:09] [Govee] [Tv back lights] starting scan.
[07/09/2022, 10:16:09] [Govee] Govee Scan Stopped
[07/09/2022, 10:16:09] [Govee] [noble] found device [2c:aa:78:91:7b:54] [undefined].
[07/09/2022, 10:16:09] [Govee] [Tv back lights] scanning started.
[07/09/2022, 10:16:09] [Govee] [Tv back lights] starting loop.
[07/09/2022, 10:16:09] [Govee] [Tv back lights] could not find device [c8:31:30:30:5a:52].
[07/09/2022, 10:16:09] [Govee] Govee Scan Started
[07/09/2022, 10:16:09] [Govee] [noble] found device [66:19:17:d0:52:d4] [undefined].
[07/09/2022, 10:16:09] [Govee] [noble] found device [fb:01:b3:79:ed:45] [Nanoleaf Strip 0W3W].
[07/09/2022, 10:16:09] [Govee] [noble] found device [5d:5a:78:a0:98:39] [undefined].
[07/09/2022, 10:16:09] [Govee] [noble] found device [f8:04:2e:cc:fd:93] [undefined].
[07/09/2022, 10:16:09] [Govee] [noble] found device [d0:03:4b:f0:03:c7] [undefined].
[07/09/2022, 10:16:09] [Govee] [noble] found device [c8:31:30:30:5a:52] [Govee_H6199_5A52].
[07/09/2022, 10:16:09] [Govee] [Tv back lights] has been reported [discoverable] via BLE.
[07/09/2022, 10:16:09] [Govee] [Tv back lights] attempting to connect.
[07/09/2022, 10:16:10] [Govee] Govee Scan Stopped
[07/09/2022, 10:16:10] [Govee] Govee Scan Stopped
[07/09/2022, 10:16:10] [Govee] [Tv back lights] has been reported [connected] via BLE.
[07/09/2022, 10:16:10] [Govee] [Tv back lights] finding device characteristics.
noble: unknown peripheral c83130305a52 connected!
[07/09/2022, 10:16:14] [Govee] Govee discovery stopped while Homebridge is running.
[07/09/2022, 10:16:14] [Govee] Restart Discovery
[07/09/2022, 10:16:14] [Govee] Govee Scan Started
[07/09/2022, 10:16:14] [Govee] [noble] found device [d1:a0:de:3b:ab:9c] [Nanoleaf Strip 0VAK].
[07/09/2022, 10:16:14] [Govee] [noble] found device [e2:fa:da:1d:9b:11] [undefined].
[07/09/2022, 10:16:14] [Govee] [noble] found device [f6:0a:05:36:9b:c8] [Hue white lamp].
[07/09/2022, 10:16:14] [Govee] [noble] found device [64:13:25:a6:45:35] [undefined].
[07/09/2022, 10:16:14] [Govee] [noble] found device [19:e0:8d:8b:69:95] [undefined].
[07/09/2022, 10:16:14] [Govee] [noble] found device [07:12:60:0f:61:b0] [undefined].
[07/09/2022, 10:16:14] [Govee] [noble] found device [31:be:02:9c:a0:40] [undefined].
[07/09/2022, 10:16:15] [Govee] [noble] found device [4d:1c:b5:fe:50:60] [undefined].
[07/09/2022, 10:16:15] [Govee] [noble] found device [c7:33:36:32:3e:1f] [Govee_H6199_3E1F].
[07/09/2022, 10:16:15] [Govee] [noble] found device [a4:c1:38:45:f8:c1] [GVH5075_F8C1].
[07/09/2022, 10:16:15] [Govee] [noble] found device [67:45:ff:0e:01:7f] [undefined].
[07/09/2022, 10:16:15] [Govee] [noble] found device [72:dc:07:d5:b6:6c] [undefined].
[07/09/2022, 10:16:15] [Govee] [noble] found device [41:09:cb:7a:21:28] [undefined].
[07/09/2022, 10:16:15] [Govee] [noble] found device [d7:ae:d7:5f:2a:a4] [Hue Lamp].
[07/09/2022, 10:16:15] [Govee] [noble] found device [d6:8b:c0:e0:70:89] [Hue white lamp].
[07/09/2022, 10:16:15] [Govee] [noble] found device [ce:27:a7:56:ab:61] [Hue Lamp].
[07/09/2022, 10:16:15] [Govee] [noble] found device [ce:65:3a:46:4f:8d] [undefined].
[07/09/2022, 10:16:15] [Govee] [noble] found device [4e:cb:d8:0f:d9:47] [undefined].
[07/09/2022, 10:16:15] [Govee] Govee discovery stopped while Homebridge is running.
[07/09/2022, 10:16:15] [Govee] Restart Discovery
[07/09/2022, 10:16:15] [Govee] Govee Scan Started
[07/09/2022, 10:16:15] [Govee] Govee discovery stopped while Homebridge is running.
[07/09/2022, 10:16:15] [Govee] Restart Discovery
[07/09/2022, 10:16:15] [Govee] Govee Scan Started
[07/09/2022, 10:16:16] [Govee] [noble] found device [c6:b6:ff:2a:a4:c9] [Eve].
[07/09/2022, 10:16:16] [Govee] [noble] found device [fb:d4:be:75:5a:f9] [undefined].
[07/09/2022, 10:16:16] [Govee] [noble] found device [fe:c1:d8:8b:c5:95] [undefined].
[07/09/2022, 10:16:16] [Govee] [noble] found device [f1:76:86:db:d7:12] [undefined].
[07/09/2022, 10:16:17] [Govee] [noble] found device [2b:dc:84:8e:77:14] [undefined].
[07/09/2022, 10:16:17] [Govee] [noble] found device [dc:1f:3b:29:a0:61] [Hue Lamp].
[07/09/2022, 10:16:17] [Govee] [noble] found device [64:a3:e5:b7:30:29] [undefined].
[07/09/2022, 10:16:18] [Govee] [noble] found device [a4:c1:38:ca:c7:86] [GVH5075_C786].
[07/09/2022, 10:16:19] [Govee] [noble] found device [f8:95:5b:be:50:9b] [undefined].
[07/09/2022, 10:16:19] [Govee] [noble] found device [72:5d:01:ed:21:41] [undefined].
[07/09/2022, 10:16:21] [Govee] [Tv back lights] has been reported [disconnected] via BLE [undefined].
noble: unknown peripheral c83130305a52 disconnected!
[07/09/2022, 10:16:24] [Govee] [noble] found device [f5:0a:78:ee:8b:29] [undefined].
[07/09/2022, 10:16:25] [Govee] [noble] found device [f8:8a:5e:3c:9c:6d] [Oral-B Toothbrush].
[07/09/2022, 10:16:26] [Govee] [noble] found device [fc:33:12:be:4d:b5] [undefined].
[07/09/2022, 10:16:58] [Govee] [noble] found device [38:23:22:bf:f9:c6] [undefined].
[07/09/2022, 10:16:58] [Govee] [noble] found device [cf:c3:7c:26:02:1e] [undefined].
[07/09/2022, 10:17:20] [Govee] [noble] found device [57:83:58:46:17:2c] [undefined].
[07/09/2022, 10:17:30] [Govee] [noble] found device [f3:dc:21:b2:16:f8] [undefined].
[07/09/2022, 10:17:31] [Govee] [noble] found device [41:6b:5d:58:8e:ad] [undefined].
[07/09/2022, 10:17:43] [Govee] [noble] found device [34:4c:7c:d0:7d:7c] [undefined].
[07/09/2022, 10:19:08] [Govee] [noble] found device [5f:a4:4c:4b:8a:54] [undefined].
[07/09/2022, 10:19:08] [Govee] [noble] found device [11:81:fa:df:2c:08] [undefined].
[07/09/2022, 10:19:36] [Govee] [noble] found device [1c:1a:c0:5f:1c:1d] [undefined].
[07/09/2022, 10:19:54] [Govee] [noble] found device [6f:42:36:72:ef:f0] [undefined].
[07/09/2022, 10:19:57] [Govee] [noble] found device [3c:4b:61:fe:34:40] [undefined].
[07/09/2022, 10:20:24] [Govee] [noble] found device [30:c8:18:bb:79:d1] [undefined].
[07/09/2022, 10:20:24] [Govee] [noble] found device [7f:d8:37:9c:03:9c] [undefined].
[07/09/2022, 10:23:11] [Govee] [noble] found device [69:7c:a6:7a:8f:58] [undefined].
[07/09/2022, 10:24:21] [Govee] [noble] found device [6b:d9:cb:c5:5d:a8] [undefined].
[07/09/2022, 10:24:37] [Govee] [noble] found device [fd:6f:b2:9d:a0:8e] [undefined].
[07/09/2022, 10:26:00] [Govee] [noble] found device [39:22:76:9e:d7:8e] [undefined].
[07/09/2022, 10:26:06] [Govee] [noble] found device [7b:03:05:2f:29:12] [undefined].
[07/09/2022, 10:26:41] [Govee] [noble] found device [74:91:bd:9a:90:b7] [undefined].
[07/09/2022, 10:26:55] [Govee] [noble] found device [64:6d:59:c3:ab:24] [undefined].
[07/09/2022, 10:27:04] [Govee] [noble] found device [db:28:35:8f:9e:9e] [undefined].
[07/09/2022, 10:27:19] [Govee] [noble] found device [78:dc:cd:85:91:e3] [undefined].
[07/09/2022, 10:27:42] [Govee] [noble] found device [7c:60:b6:8f:d1:e8] [undefined].
[07/09/2022, 10:28:08] [Govee] [noble] found device [1b:31:7a:6f:ff:b1] [undefined].
[07/09/2022, 10:28:08] [Govee] [noble] found device [4f:6e:f6:8d:c9:2d] [undefined].
[07/09/2022, 10:28:41] [Govee] [noble] found device [54:19:4d:2a:9d:91] [undefined].
[07/09/2022, 10:29:04] [Govee] [noble] found device [58:b8:4d:64:a3:61] [undefined].
[07/09/2022, 10:30:00] [Govee] [noble] found device [f1:77:75:e2:ae:a5] [undefined].
[07/09/2022, 10:30:02] [Govee] [noble] found device [d6:30:b1:c8:c1:11] [undefined].
[07/09/2022, 10:30:04] [Govee] [noble] found device [e8:5d:16:13:e4:65] [undefined].
[07/09/2022, 10:30:08] [Govee] [noble] found device [d6:5b:c1:bf:d1:16] [undefined].
[07/09/2022, 10:30:10] [Govee] [noble] found device [e3:0f:eb:23:24:8a] [undefined].
[07/09/2022, 10:30:15] [Govee] [noble] found device [c0:f4:01:a3:1f:c7] [undefined].
[07/09/2022, 10:32:19] [Govee] [noble] found device [e1:e2:c7:e3:e7:e0] [undefined].
[07/09/2022, 10:33:33] [Govee] [noble] found device [62:35:65:1f:c3:00] [undefined].
[07/09/2022, 10:33:33] [Govee] [noble] found device [0b:c4:e9:0d:b4:ab] [undefined].
[07/09/2022, 10:34:14] [Govee] [noble] found device [0e:a3:fe:a1:a9:e4] [undefined].
[07/09/2022, 10:34:14] [Govee] [noble] found device [6a:76:bc:8f:5e:d2] [undefined].
[07/09/2022, 10:34:19] [Govee] [noble] found device [fe:3e:dd:c0:b2:15] [undefined].
[07/09/2022, 10:34:28] [Govee] [noble] found device [df:d8:84:e7:89:e8] [undefined].
[07/09/2022, 10:35:38] [Govee] [noble] found device [4a:1e:0e:71:df:47] [undefined].
[07/09/2022, 10:36:06] [Govee] [noble] found device [6f:bc:a1:29:0d:2b] [undefined].
[07/09/2022, 10:36:26] [Govee] [noble] found device [18:ab:56:79:1e:df] [undefined].
[07/09/2022, 10:36:45] [Govee] [noble] found device [19:ee:aa:7f:9b:65] [undefined].
[07/09/2022, 10:36:47] [Govee] [noble] found device [77:cf:26:af:07:12] [undefined].
[07/09/2022, 10:36:51] [Govee] [noble] found device [f1:90:4c:e2:59:a9] [undefined].
[07/09/2022, 10:36:57] [Govee] [noble] found device [3c:ae:b5:b1:ea:b4] [undefined].
[07/09/2022, 10:37:36] [Govee] [noble] found device [2c:6b:7d:86:9d:24] [Oral-B Toothbrush].
[07/09/2022, 10:39:50] [Govee] [noble] found device [4f:7f:25:b1:2b:61] [undefined].
[07/09/2022, 10:40:35] [Govee] [noble] found device [6a:2f:9e:1c:c7:a9] [undefined].
[07/09/2022, 10:41:44] [Govee] [noble] found device [00:e7:b2:32:ef:2f] [undefined].
[07/09/2022, 10:42:07] [Govee] [noble] found device [f2:22:ec:78:8d:2f] [undefined].
[07/09/2022, 10:42:16] [Govee] [noble] found device [66:be:58:74:3d:fc] [undefined].
[07/09/2022, 10:44:30] [Govee] [noble] found device [7e:ef:bc:cd:53:3c] [undefined].
[07/09/2022, 10:44:31] [Govee] [noble] found device [1c:ac:d3:fd:46:eb] [undefined].
[07/09/2022, 10:44:31] [Govee] [noble] found device [59:e6:68:de:92:89] [undefined].
[07/09/2022, 10:44:55] [Govee] [noble] found device [5c:47:7f:5f:43:eb] [undefined].
[07/09/2022, 10:44:58] [Govee] [noble] found device [1b:1f:2f:76:36:ac] [undefined].
[07/09/2022, 10:45:00] [Govee] [noble] found device [d6:81:17:79:d5:f2] [undefined].
[07/09/2022, 10:45:01] [Govee] [noble] found device [d6:bb:05:8f:9e:04] [undefined].
[07/09/2022, 10:45:03] [Govee] [noble] found device [f5:9a:0a:2d:f0:74] [undefined].
[07/09/2022, 10:45:36] [Govee] [noble] found device [db:47:36:95:17:c3] [undefined].
[07/09/2022, 10:46:06] [Govee] [noble] found device [78:16:0b:03:bb:49] [undefined].
[07/09/2022, 10:47:14] [Govee] [noble] found device [26:80:9c:88:1b:68] [undefined].
[07/09/2022, 10:47:15] [Govee] [noble] found device [4d:06:4d:af:0f:ff] [undefined].
[07/09/2022, 10:47:29] [Govee] [noble] found device [ca:96:3d:b3:e6:26] [undefined].
[07/09/2022, 10:47:51] [Govee] [noble] found device [f0:90:8a:ab:c6:40] [undefined].
[07/09/2022, 10:48:25] [Govee] [noble] found device [79:04:a1:ea:47:bc] [undefined].
[07/09/2022, 10:49:01] [Govee] [noble] found device [1a:2d:56:16:27:85] [undefined].
[07/09/2022, 10:49:12] [Govee] [noble] found device [f6:25:57:04:31:89] [undefined].
[07/09/2022, 10:50:07] [Govee] [noble] found device [d0:51:03:9b:78:32] [undefined].
[07/09/2022, 10:50:33] [Govee] [noble] found device [e6:2e:7c:40:9b:63] [undefined].
[07/09/2022, 10:55:07] [Govee] [noble] found device [55:99:fe:ce:dc:c2] [undefined].
[07/09/2022, 10:55:09] [Govee] [noble] found device [4c:60:7b:be:41:30] [undefined].
[07/09/2022, 10:55:09] [Govee] [noble] found device [2b:aa:42:f6:05:fa] [undefined].
[07/09/2022, 10:55:10] [Govee] [noble] found device [23:eb:0c:d7:d0:dc] [undefined].
[07/09/2022, 10:56:06] [Govee] [noble] found device [79:9d:4e:3a:d3:c2] [undefined].
[07/09/2022, 10:56:07] [Govee] [noble] found device [00:ce:dd:67:38:27] [undefined].
[07/09/2022, 10:57:28] [Govee] [noble] found device [05:e6:2d:3b:40:a2] [undefined].
[07/09/2022, 10:57:53] [Govee] [noble] found device [2d:30:6e:d8:28:ac] [undefined].
[07/09/2022, 10:57:53] [Govee] [noble] found device [55:42:36:06:65:fd] [undefined].
[07/09/2022, 10:58:04] [Govee] [noble] found device [5f:49:d3:76:85:cf] [undefined].
[07/09/2022, 10:58:10] [Govee] [noble] found device [57:38:d7:df:6e:4c] [undefined].
[07/09/2022, 10:58:17] [Govee] [noble] found device [48:be:b0:ee:3a:00] [undefined].
[07/09/2022, 10:58:24] [Govee] [noble] found device [ff:bb:9c:09:de:92] [undefined].
[07/09/2022, 10:59:00] [Govee] [noble] found device [f4:70:0d:2a:28:cf] [undefined].
[07/09/2022, 10:59:01] [Govee] [noble] found device [6d:f3:af:03:d9:80] [undefined].
[07/09/2022, 10:59:13] [Ring] Front Door Detected Motion. Loading snapshot before sending event to HomeKit
[07/09/2022, 10:59:14] [Ring] Front Door Doorbell Pressed
[07/09/2022, 10:59:51] [Govee] [noble] found device [7e:88:fe:00:3c:e3] [undefined].
[07/09/2022, 11:00:00] [Govee] [noble] found device [e9:71:bf:92:c2:dd] [undefined].
[07/09/2022, 11:00:00] [Govee] [noble] found device [c6:2b:54:d9:a4:19] [undefined].
[07/09/2022, 11:00:01] [Govee] [noble] found device [d6:3a:96:4c:1f:c1] [undefined].
[07/09/2022, 11:00:02] [Govee] [noble] found device [cf:28:f6:43:64:dc] [undefined].
[07/09/2022, 11:00:58] [Govee] [noble] found device [df:46:39:ea:62:d5] [undefined].
[07/09/2022, 11:01:01] [Govee] [noble] found device [c5:a4:16:f5:e2:2f] [undefined].
[07/09/2022, 11:01:02] [Govee] [noble] found device [43:22:8a:0e:77:da] [undefined].
[07/09/2022, 11:01:39] [Govee] [noble] found device [ec:5b:f8:1d:b3:b1] [undefined].
[07/09/2022, 11:01:43] [Govee] [noble] found device [6a:4a:d2:6c:1e:a8] [undefined].
[07/09/2022, 11:01:44] [Govee] [noble] found device [da:3c:76:3b:c1:86] [undefined].
[07/09/2022, 11:01:56] [Govee] [noble] found device [f5:03:36:6b:98:e5] [undefined].
[07/09/2022, 11:02:11] [Govee] [noble] found device [55:fd:09:00:0e:19] [undefined].
[07/09/2022, 11:03:28] [Govee] [noble] found device [5e:39:b8:58:7a:1d] [undefined].
[07/09/2022, 11:04:20] [Govee] [noble] found device [60:25:a3:b0:b8:4d] [undefined].
[07/09/2022, 11:04:24] [Govee] [noble] found device [e4:c3:92:b1:af:52] [undefined].
[07/09/2022, 11:04:32] [Govee] [noble] found device [d5:70:96:87:82:25] [undefined].
[07/09/2022, 11:04:35] [Govee] [noble] found device [fc:a4:fe:9f:15:3b] [undefined].
[07/09/2022, 11:05:28] [Govee] [noble] found device [69:0f:4a:2a:bd:7e] [undefined].
[07/09/2022, 11:05:30] [Govee] [noble] found device [22:49:da:0b:3b:e8] [undefined].
[07/09/2022, 11:06:06] [Govee] [noble] found device [68:e6:5b:19:53:0f] [undefined].
[07/09/2022, 11:06:21] [Govee] [noble] found device [28:a2:63:a2:29:d8] [undefined].
[07/09/2022, 11:06:21] [Govee] [noble] found device [72:b8:d2:e0:ec:36] [undefined].
[07/09/2022, 11:08:31] [Govee] [noble] found device [f6:03:64:4d:7d:dc] [undefined].
[07/09/2022, 11:08:31] [Govee] [noble] found device [ea:84:f3:22:a2:05] [undefined].
[07/09/2022, 11:08:37] [Govee] [noble] found device [69:b4:83:a9:8d:3b] [undefined].
[07/09/2022, 11:09:20] [Govee] [noble] found device [6a:67:7b:5b:e9:f1] [undefined].
[07/09/2022, 11:10:11] [Govee] [noble] found device [57:54:5a:59:a0:a2] [undefined].
[07/09/2022, 11:10:50] [Govee] [noble] found device [52:d4:42:da:fa:a7] [undefined].
[07/09/2022, 11:11:18] [Govee] [noble] found device [78:e2:e9:f4:53:77] [undefined].
[07/09/2022, 11:12:58] [Govee] [noble] found device [64:c3:39:7f:d1:7a] [undefined].
[07/09/2022, 11:13:16] [Govee] [noble] found device [5a:c0:48:0c:60:8a] [undefined].
[07/09/2022, 11:15:00] [Govee] [noble] found device [e3:e1:4d:13:53:83] [undefined].
[07/09/2022, 11:15:00] [Govee] [noble] found device [e0:70:5a:10:5a:cf] [undefined].
[07/09/2022, 11:15:01] [Govee] [noble] found device [e2:2f:98:5e:32:f9] [undefined].
[07/09/2022, 11:15:02] [Govee] [noble] found device [e0:6c:cf:67:e1:b4] [undefined].
[07/09/2022, 11:15:03] [Govee] [noble] found device [c6:ae:52:f5:55:b3] [undefined].
[07/09/2022, 11:15:15] [Govee] [noble] found device [db:f4:55:35:37:ed] [undefined].
[07/09/2022, 11:15:28] [Govee] [noble] found device [29:88:ae:b1:30:e9] [undefined].
[07/09/2022, 11:15:28] [Govee] [noble] found device [7e:9c:11:60:c7:f3] [undefined].
[07/09/2022, 11:16:06] [Govee] [noble] found device [6a:25:e7:d7:da:89] [undefined].
[07/09/2022, 11:18:11] [Govee] [noble] found device [c4:bc:26:ad:5c:0d] [undefined].
[07/09/2022, 11:18:54] [Govee] [noble] found device [4a:09:8d:8b:92:73] [undefined].
[07/09/2022, 11:18:54] [Govee] [noble] found device [03:40:d3:49:25:3a] [undefined].
[07/09/2022, 11:19:02] [Govee] [noble] found device [7b:0a:8d:bd:86:13] [undefined].
[07/09/2022, 11:19:02] [Govee] [noble] found device [d8:0b:0d:4a:2a:da] [undefined].
[07/09/2022, 11:19:02] [Govee] [noble] found device [3d:39:bf:a8:2b:b9] [undefined].
[07/09/2022, 11:19:40] [Govee] [noble] found device [31:10:2b:91:c7:fc] [undefined].
[07/09/2022, 11:19:41] [Govee] [noble] found device [14:3f:a6:47:94:1b] [LE_WH-1000XM3].
[07/09/2022, 11:20:01] [Govee] [noble] found device [db:81:f5:b0:ff:81] [undefined].
[07/09/2022, 11:20:12] [Govee] [noble] found device [cc:95:69:d7:0e:f3] [undefined].
[07/09/2022, 11:20:40] [Govee] [noble] found device [fb:22:03:e7:a1:3f] [undefined].
[07/09/2022, 11:20:41] [Govee] [noble] found device [21:11:61:96:90:43] [undefined].
[07/09/2022, 11:20:49] [Govee] [noble] found device [5e:e4:44:9a:a5:50] [undefined].
[07/09/2022, 11:21:33] [Govee] [noble] found device [16:cc:02:97:5c:14] [undefined].
[07/09/2022, 11:21:34] [Govee] [noble] found device [4d:35:cf:bf:4c:a3] [undefined].
[07/09/2022, 11:21:52] [Govee] [noble] found device [69:f4:9f:6c:29:72] [undefined].
[07/09/2022, 11:22:30] [Govee] [noble] found device [5f:2c:3f:0b:03:87] [undefined].
[07/09/2022, 11:22:55] [Govee] [noble] found device [3d:f8:f2:d0:ed:37] [undefined].
[07/09/2022, 11:23:46] [Govee] [noble] found device [55:24:6d:98:9c:6d] [undefined].
[07/09/2022, 11:23:49] [Govee] [noble] found device [c1:0d:5a:28:5a:6e] [undefined].
[07/09/2022, 11:24:16] [Govee] [noble] found device [05:66:b4:fc:7c:e6] [undefined].
[07/09/2022, 11:24:16] [Govee] [noble] found device [3f:cf:bb:8b:5e:35] [undefined].
[07/09/2022, 11:25:44] [Govee] [noble] found device [61:c2:7c:93:e8:07] [undefined].
[07/09/2022, 11:26:06] [Govee] [noble] found device [51:41:12:13:50:32] [undefined].
[07/09/2022, 11:26:25] [Govee] [noble] found device [74:6b:3b:46:4f:85] [undefined].
[07/09/2022, 11:26:45] [Govee] [noble] found device [f1:c5:8f:b8:2e:be] [undefined].
[07/09/2022, 11:26:46] [Govee] [noble] found device [6b:ff:29:8f:08:54] [undefined].
[07/09/2022, 11:27:04] [Govee] [noble] found device [5a:cf:c0:69:1c:b4] [undefined].
[07/09/2022, 11:27:26] [Govee] [noble] found device [6c:9e:86:4e:6a:aa] [undefined].
[07/09/2022, 11:27:36] [Govee] [noble] found device [70:86:c3:e6:e8:42] [undefined].
[07/09/2022, 11:27:42] [Govee] [noble] found device [f6:ac:c3:75:9e:1a] [undefined].
[07/09/2022, 11:28:18] [Govee] [noble] found device [3c:bd:36:f9:6b:9f] [undefined].
[07/09/2022, 11:28:52] [Govee] [noble] found device [45:21:64:72:7a:79] [undefined].
[07/09/2022, 11:30:01] [Govee] [noble] found device [dc:7a:38:d8:9b:98] [undefined].
[07/09/2022, 11:30:01] [Govee] [noble] found device [ed:32:f9:13:24:01] [undefined].
[07/09/2022, 11:30:01] [Govee] [noble] found device [fc:b3:0d:10:98:8f] [undefined].
[07/09/2022, 11:30:02] [Govee] [noble] found device [ea:8d:a5:dd:d8:10] [undefined].
[07/09/2022, 11:30:05] [Govee] [noble] found device [f1:92:3f:70:ed:34] [undefined].
[07/09/2022, 11:30:18] [Govee] [noble] found device [c2:26:2b:06:c5:77] [undefined].
[07/09/2022, 11:30:36] [Govee] [noble] found device [f0:bd:bb:83:94:0b] [undefined].
[07/09/2022, 11:31:05] [Govee] [noble] found device [2c:8b:61:40:b9:6c] [undefined].
[07/09/2022, 11:31:05] [Govee] [noble] found device [6b:ef:d2:46:88:f3] [undefined].
[07/09/2022, 11:31:44] [Govee] [noble] found device [f5:22:0b:27:00:9a] [undefined].
[07/09/2022, 11:32:00] [Govee] [noble] found device [f3:21:0c:79:86:4c] [undefined].
[07/09/2022, 11:32:14] [Govee] [noble] found device [71:68:b8:e6:80:d5] [undefined].

I have the exact same issue. Not sure how to stop these.
My Setup : Homebridge Raspberry pi image
OS : Raspbian GNU/Linux Bullseye (11)
nodejs version : [v16.17.0]

version 6 beta will stop all the logging


Error in POST reques with body

Environment

Operating System: Linux
Node Version:     v20.5.1
Nuxt Version:     3.7.0
CLI Version:      3.8.4
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
I have some routeRules defined in my nuxt.config.ts which aprrently breaks the caching in the API party module.
If you try to render the page without routeRules then it works.
If you try to render the page with routeRules then it breaks.
https://stackblitz.com/edit/github-eequg2?file=app.vue
Describe the bug
server side POST request with body returns undefined and on client it returns an error
Additional context
No response
Logs
No response

Can you please provide a minimal reproducible example?

I'm getting this error in my POST request after updating but I can't for the life of me figure our why it happens.

I tried creating a stackblitz with a repro but it works fine there.

Actually! I found the issue. I have some routeRules defined in nuxt.config:
routeRules: {
'/api/:locale/landingpage/:tag': { swr: 900 },
'/api/:locale/tagged-landingpage/:tag': { swr: 900 },
'/api/:locale/navigation': { swr: 900 },
'/api/:locale/:funnel': { swr: 900 },
'/api/:locale/:funnel/:product': { swr: 900 },
'/api/:locale/:funnel/:product/:area': { swr: 900 },
'/api/:locale/:funnel/:product/:area/:site': { swr: 900 },
},
If I remove those routeRules then my POST request works again.

I have created a reproduction here:
I have some routeRules defined in my nuxt.config.ts which aprrently breaks the caching in the API party module.
If you try to render the page without routeRules then it works.
If you try to render the page with routeRules then it breaks.
https://stackblitz.com/edit/github-eequg2?file=app.vue

The behavior you encounter should happen in every other custom route which uses readBody and is overwritten with custom route rules. Could you please create a reproduction with a custom API route handler and post the issue upstream?
I believe every module using addServerHandler and being overwritten by route rules will face the same issue.
For now, I recommend to not overwrite the module's internal /api/__api_party/:endpointId route, but make your rules more specific instead.
If Nuxt provides a way for modules to detect custom route rules, feel free to open another issue. Thanks in advance!


SVG image support

Microsoft Teams would like to use SVG images in their toasts. We should consider SVG support in the renderers.

Already supported in HTML renderer.

@RebeccaAnne in UWP, would the author have to tell us that it's a SVG? Since we're creating the XAML UI programmatically, I think we have to explicitly create a SvgImageSource rather than the traditional BitmapImage to display a SVG… but the problem is we don't know whether it's a SVG when we're only given a URL (the http url doesn't have to include an extension).
Can you try to confirm that we need additional info (like a property the author specifies to say it's a SVG)?

@andrewleader, yes, looks like that's correct.

We should consider having the author specify a contentType as opposed to something like isSvg.

We do have the mimeType for media. We can do the same for image types that might not be PNG & JPG.

@andrewleader
Is the SVG supported yet in Adaptive cards ?
Please let know.

It's been three long years - this feels like Waiting for Godot.
What is the ETA?


Error: import undefined.AmplitudeReactNativePackage;

After installing Amplitude
npm install @amplitude/analytics-react-native
npm install @react-native-async-storage/async-storage

And building the app I got this error:
File path: com/facebook/react/PackageList.java
app/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java
// @amplitude/react-native
import undefined.AmplitudeReactNativePackage;

      new AmplitudeReactNativePackage(),
          ^
  symbol:   class AmplitudeReactNativePackage
  location: class PackageList

Hi @andrew-skrypnyk thanks for choosing Amplitude.
This repo is for our maintenance RN SDK. The new repo is here:
https://github.com/amplitude/Amplitude-TypeScript/tree/v1.x/packages/analytics-react-native
What version of React Native are you using? Versions of the SDK < 1.4 don't support the latest RN & RN CLI. Can you please updating to the latest version and see if that resolves the issue.
https://www.docs.developers.amplitude.com/data/sdks/typescript-react-native/#compatibility-matrix
Thanks!

error: package undefined does not exist
import undefined.AmplitudeReactNativePackage;
still getting error can you please help me ?
`BUILD FAILED in 1m 11s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
C:\Users\Sameer\Desktop\hookfish\newhookfishapp\android\app\build\generated\rncli\src\main\java\com\facebook\react\PackageList.java:15: error: package undefined does not exist
import undefined.AmplitudeReactNativePackage;
^
C:\Users\Sameer\Desktop\hookfish\newhookfishapp\android\app\build\generated\rncli\src\main\java\com\facebook\react\PackageList.java:143: error: cannot find symbol
new AmplitudeReactNativePackage(),
^
symbol:   class AmplitudeReactNativePackage
location: class PackageList
Note: C:\Users\Sameer\Desktop\hookfish\newhookfishapp\android\app\src\debug\java\com\hookfishforpartners\ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 1m 11s
at makeError (C:\Users\Sameer\Desktop\hookfish\newhookfishapp\node_modules\@react-native-community\cli-platform-android\node_modules\execa\index.js:174:9)
at C:\Users\Sameer\Desktop\hookfish\newhookfishapp\node_modules\@react-native-community\cli-platform-android\node_modules\execa\index.js:278:16
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async runOnAllDevices (C:\Users\Sameer\Desktop\hookfish\newhookfishapp\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:109:5)
at async Command.handleAction (C:\Users\Sameer\Desktop\hookfish\newhookfishapp\node_modules\@react-native-community\cli\build\index.js:192:9)

info Run CLI with --verbose flag for more details.`
please help !! RN : 0.65


Add insert timestamp for Tag and JobTag tables

It would be helpful to have the insert timestamp for the Tags and the tag Job relation.

This can be implemented using Triggers:
https://www.sqlitetutorial.net/sqlite-trigger/


New data types available in dynamo3

Hi,
I was wondering if the "new" data types of dynamodb were usable in flywheel.
I see them implemented in dynamo3 : https://github.com/stevearc/dynamo3/commit/0b4b21b3dfe1fe2f8a111cdad9540e5a73735f1c
But never mentioned in flywheel documentation nor imported in flywheel.fields module.
Thanks,
Pior

Ok. All types are working just fine.
from flywheel.fields.types import DictType, ListType, BoolType
Field(data_type=DictType)


add authentication, blobstore and FindMeetingQuery(week4)

Do you have accessible url for your site?

https://zhu-sps-summer20.df.r.appspot.com
just complete basic features

updated @akovski

Hi, you seem not update other code with comment inside

sorry, I have checked code in FormHandlerServlet.java and delete unnecessary comment


Fix example project to make it compile again with Xcode 9.2

EDITED @nasli

Fix credentials call issue, updated with new method
Expose sharedRequestWithMethod
Update minimal target version

Thanks for the contribution!!
Checked the operations available in the OCExample app:

Show file list
Download
Upload

All correct.
Approved


TreeView: Now highlights only model text

This PR:

Adds new Style named HighlightModelTextOnly - false by default
Updates Class Explorer Scenario to have a menu for testing new Style
Fixes #2151

See: https://github.com/gui-cs/Terminal.Gui/discussions/2154

@tznind please review!

Looks great, thanks for this and for making it toggleable <3.
Only issue I can see is that the highlight color does not match ListView... seems to be Blue on White instead of Black on White.  Seems to be a regression vs main gui.cs branch.

Also I think we should add the Style setting in here too.  That Scenario has all the toggle able options so should have the new one too.
There is a bit of redundancy in Class Explorer and TreeViewFileSystem.  I think later on we could look to share more code between them or scrap one/merge.


Getting gene name with getfasta

Hi Aaron et al. I'm trying to extract a fasta of precursor mRNA, and this is sooo close to what I need:
bedtools getfasta -name -s -fi genome.fa -bed genes.gtf -fo precursors.fa
with the one issue that the fasta header is always "gene" rather than pulling from the GTF attributes. Not sure if there is an easy workaround, if not then I suppose this is a feature request!

Hi David, bedtools can use the name column (4th col) in a BED file and use that as the name. It is doing the same for your gtf. For now, I suggest to make such a BED file.
We could try to sniff file formats and handle this for gtf, gff, etc, but I think that will create many new bugs.

Thanks. Do you have advice for making that bed file? gtf2bed from bedops doesn't like my Gencode gtf (!) Does bedtools have a way to pull specific attributes from a gtf into the name column?
Closing this since it's not really an "issue".

you can use something like this python script:
import sys

name_attr = 'gene_name'

for line in sys.stdin:
    if line[0] == '#': continue
    toks = line.rstrip().split('\t')
    name = [x.strip() for x in toks[8].split(';') if x.strip().startswith(name_attr)][0]
    name = name.split()[1].strip('"').strip("'")

    print(f'{toks[0]}\t{int(toks[3])-1}\t{int(toks[4])}\t{name}')

then use as:
cat $gtf | python gtf2bed.py > $bed

I tested on this input:
1	transcribed_unprocessed_pseudogene	gene	11869	14409	.	+	.	gene_id "ENSG00000223972"; gene_name "DDX11L1"; gene_source "havana"; gene_biotype "transcribed_unprocessed_pseudogene";
1	processed_transcript	transcript	11869	14409	.	+	.	gene_id "ENSG00000223972"; transcript_id "ENST00000456328"; gene_name "DDX11L1"; gene_sourc e "havana"; gene_biotype "transcribed_unprocessed_pseudogene"; transcript_name "DDX11L1-002"; transcript_source "havana";

and got this output:
1	11868	14409	DDX11L1
1	11868	14409	DDX11L1


Update UsageWithReact.md

amended comments to indicate that with React 0.14 and later version, there is not necessarily to wrap <Provider> child into a function,

We will soon update the docs to match 0.14 anyway, so I'd rather avoid this change for now.
Thanks!


Fine tune on domain dataset and convert it as a chat based model

Hi team,
I would like to fine tune Llama2 model with my domain and eventually convert it as chat model. so, I can ask directly ask questions related to my domain data to and get right response from the model. This is my objective.
I would like to get your advice/guidance on my approach to this problem whether I'm on right direction to my objective or not.
step1. collect domain data -> step2. picture the base Llama model -> step3. fine tune the base Llama model with my domain data -> step4. prepare instruction dataset -> step5. pick the above finetuned model(which is fine tuned with my domain data) now fine tune that model with instruction dataset -> step6. save the model -> step7. load the model -> step8. ask questions related to my domain data and get answer from the finetuned model.
can you please provide your thoughts in this approach? would the above approach help me to achieve my goal?
Also, I have a fews in the above approach

for the above approach should I use the base Llama model or directly use the chat model in the step2? also I have question here, if I pick the chat model, will I be able to fine tune my domain dataset(multi raw text files) because Llama chat model will not have information about my dataset right? or my domain dataset is not included in the training set.
Did you make your instruction dataset(the dataset which you have used to fine the Llama chat model) open source? if so, can you please point me there?
do I need to add special token in my dataset? because I have multiple files in my folder?
is there any input data format for llama2? do I need to combine it together? or does Llama can pick up multiple files from the same folder to fine-tune the model

@HamidShojanazeri @albertodepaola
Note :
domain data file size : each file size is about 1MB
no of file: 1780 files

@IamExperimenting sure, let me share my thoughts on it, it may depend to various factors specially data accessibility and quality but here is how I think.
re:1 as usually making the instruction dataset is harder than your domain raw data, if thats the case in your domain I agree starting with base model, finetuned on domain then instruct fine-tune it might be a better path.
re:2 we haven't open sourced instruction dataset.
re:3 if you are using the base model you wont need special token but if you are using chat model take a look at this preprocessing step that add special tokens.
re:4 here we mostly support HF datasets, so this doc should be helpful to get you started with your custom dataset.

@HamidShojanazeri thanks for your response :) . Let me start fine tuning Llama2 base model with my domain data and get up back to you. I have another question, just wanted to clarify whether my understanding about the domain fine tuning is correct or wrong.
After fine tuning Llama2 base model with my domain data, should I expect the fine tuned model to generate sentence same as my  domain data?
example:
Domain data:
DUKE OF YORK:
No; it is stopp'd with other flattering sounds,
As praises, of whose taste the wise are fond,
Lascivious metres, to whose venom sound
The open ear of youth doth always listen;
Report of fashions in proud Italy,
**Whose manners still our tardy apish nation**
Limps after in base imitation.
Where doth the world thrust forth a vanity--
So it be new, there's no respect how vile--
That is not quickly buzzed into his ears?
Then all too late comes counsel to be heard,
Where will doth mutiny with wit's regard.
Direct not him whose way himself will choose:
'Tis breath thou lack'st, and that breath wilt thou lose.

the prompt i'm sending to the fine tuned model.
prompt = "Whose manners still our tardy apish nation"

output = fine_tuned_llama2_base_model.generate(prompt)

print(output)
Whose manners still our tardy apish nation
Limps after in base imitation.
Where doth the world thrust forth a vanity--
So it be new, there's no respect how vile--
That is not quickly buzzed into his ears?
Then all too late comes counsel to be heard,
Where will doth mutiny with wit's regard.

@HamidShojanazeri one more question, while preparing instructions dataset, should I only prepare questions and answers from my domain dataset or can I also use some open source question answering dataset?
Is there a minimum requirement for instruction dataset?


Initial stack implementation

Summary
Based on the tiny variant: https://github.com/paketo-buildpacks/jammy-tiny-stack/tree/e9a41436b06d3c3fa2960980ea98be36796ab3b6
Changes:

Renamed

search and replace tiny with base
change stack id from io.buildpacks.stacks.jammy.base to io.buildpacks.stacks.jammy as suggested in #1

Updated README
Updated description
Recreated the Dockerfile of the run image based on the build image Dockerfile
Added some packages from bionic base stack
Updated the integration test (use a simple java app instead of go)

Use Cases
See #1
I'm not sure if it fixes the issue completely and if I should add a Closes keyword to the description.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@phil9909 awesome! So quick! Thanks for submitting this.
Before I dig into a review, I've noticed that the find-and-replace didn't work inside the .github directory - the workflows point to actions on the jammy-tiny-stack repository. Could you replace tiny with base inside the .github directory too?

@paketo-buildpacks/stacks-maintainers @ryanmoran I'll hold off merging until you all have a chance to approve.


Tracking Issue for F# 6/.Net 6 support

This issue outlines the current support for F# 6/.Net 6.0 in Ionide
Projects
Most projects that update to .Net 6 will work great! Features that rely solely on library support, like the native task computation expression, will work exactly as you expect.  These features, while requiring compiler changes to actually implement (see the RFC for Resumable Code), appear as 'normal' Computation Expressions to most editor tooling and so typecheck as you'd expect.
There are some features that will not work. Features that rely on changes to the parser or relax type checking in scenarios that previously would not have compiled will still report as errors, since the version of the compiler embedded in Ionide targets F# 5. Examples of such features are dot-less indexing and type-directed conversions.
Scripts
Scripts are currently nonfunctional as soon as you install a 6.0 (even prerelease) SDK onto your system. This is some tech debt around how we locate the set of DLLs to use as the typechecking environment for FSI, and is also being addressed as part of the updates to support F# 6.
Please follow https://github.com/fsharp/FsAutoComplete/pull/846 for progress towards resolving both of these sets of issues.

This is now successfully resolved in Ionide 5.9.0, which released a few moments ago.


feat: set http, ws, auth to localhost on default

setting http, ws and auth to listen to localhost on default, otherwise its open for anyone to connect

updated the test too, forgot that

needs a rebase on main to get lints to pass

will be included via #3299
ty @rya0x


'Permission denied' error when 'postBuild' script create file in '$out/share/bash-completion/completions/'

Describe the bug
I use an overlay to define all my profile packages in one place. Some of my installed packages don't generate bash-completions upon install. So I add a postBuild attribute containing the required script.
All is fine when none of the installed packages generate any completions.
When one of the installed package (tmux) dose generate a  completion, i.e. generates a file in $out/share/bash-completion/completions/, scripts that attempt to create a file in that directory in postBulid fails with a 'Permission denied' error.
To Reproduce
This is my, simplified, overlay:
self: super:
{
  my-nix-env = with self; # self is nixpkgs
    buildEnv {
      name = "my-nix-env";
      paths = [
        #
        # other packages hidden
        #
        tmux # causes rclone completion installment below to fail
        rclone # rclone needs manual completion generation
      ];
      postBuild = ''
        echo "...mkdir -p $out/share/bash-completion/completions/..."
        mkdir -p $out/share/bash-completion/completions/
        echo "...install rclone completions..."
        $out/bin/rclone genautocomplete bash $out/share/bash-completion/completions/rclone
      '';
    };
}

Expected behavior
Manually created completion file is created and nix-env -i ... succeeds. Had 'tmux' been removed, the install would succeed as expected.
Screenshots

Additional context
Nixos running in VirtualBox, probably not relevant.
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.93, NixOS, 19.09.1806.b047b7315d8 (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.2`
 - channels(joe): `"nixpkgs-20.03pre211021.690dd986b23"`
 - channels(root): `"nixos-19.09.1806.b047b7315d8"`
 - channels(gomain): `"nixpkgs-20.03pre197053.d08a7431561"`
 - nixpkgs: `/home/joe/.nix-defexpr/channels/nixpkgs`

@veprbl Mind to answer?

@gomain This has to do with how buildEnv works. If you add "ls -la $out" you will see that "$out/share" is a symlink to /nix/store/afd141s2x5qq3vi5l2v46wziycxpskzy-tmux-2.7 which is immutable.

@gomain This has to do with how buildEnv works. If you add "ls -la $out" you will see that "$out/share" is a symlink to /nix/store/afd141s2x5qq3vi5l2v46wziycxpskzy-tmux-2.7 which is immutable.

Thanks for pointing this out. 'tmux' indeed created a symlink $out/share/bash-completion pointing to some /nix/store/*-tmux-3.0a\share\bash-completion. That explains why I can't create files there.
Would greatly appreciate if you could point me in the right direction here. I basically want to declare all my programs and env setup in a single place. Something I can take with me and rerun on multiple machines/users.
Anyway, thanks a lot.

A solution I can think of is to move the bash completion generation into its own derivation. Something along the lines of:
runCommand "rclone-bash-completion" { buildInputs = [ rclone ]; } ''
  mkdir -p "$out"/share/bash-completion/completions/
  rclone genautocomplete bash "$out"/share/bash-completion/completions/rclone
''

Or it might be that this really ought to be done in the rclone itself, then you could contribute the completion generation functionality to nixpkgs for all users to use.

Actually, this functionality is being added to rclone right now in #79062


Platform compatibility sheet?

Can you provide any info on platform compatibility?

I do not have a list of compatibility limitations. It has been quite awhile since I created and tested this. I believe when I created this I had tested it on the latest versions of the Samsung Galaxy Android and iOS platforms at that time and ran the Unit tests actually on the devices.


fix: deprecate ropsten and rinkeby

Summary
Deprecate all instances of ropsten and rinkeby.
Changes

Text change to goerli and sepolia to reduce the confusion in future
fix makeAddressURL() to generate polygonscan url too

Issues
https://www.pivotaltracker.com/n/projects/2424361/stories/183587058

Carried over from https://github.com/TradeTrust/tradetrust-website/pull/636.


docs(update): set author information

Description
Setting author information in documentation to for Jack De Winter.

:tada: This PR is included in version 3.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Unit test fails on windows: test_spark_config_precedence_in_transformation_2

Describe the bug
A clear and concise description of what the bug is.
Code and/or configuration snippet that caused the issue
pramen {
}

Expected behavior
A clear and concise description of what you expected to happen.
Context

Pramen/pramen-py version:
Spark version:
Scala/Python version:
Operating system:

I'd be happy if you find the reason of failure. In my case it xpasses when run separately. However when run with other tests it is usually fails


update angular to 2.2.3?

as the title says, can we move to latest version of angular, since it supports meta service which will be very useful in universal.

@kodeine I see the official universal starter repo is only on 2.1.2 and has issues when you try to upgrade it. Soon the core angular team is supposed to be universal into the core testing setup, so hopefully that will help things. As it is currently, just about every other upgrade of Angular breaks with Universal.

it supports meta service

cool but meta is not yet a part of angular :)

Whats "meta service"?

@qdouble
i was actually talking about the following dependencies to be updated.
 "@angular/common": "2.1.0",
    "@angular/compiler": "2.1.0",
    "@angular/compiler-cli": "2.1.0",
    "@angular/core": "2.1.0",
    "@angular/forms": "2.1.0",
    "@angular/http": "2.1.0",
    "@angular/platform-browser": "2.1.0",
    "@angular/platform-browser-dynamic": "2.1.0",
    "@angular/platform-server": "2.1.0",

@kodeine the universal starter repo is only updated to 2.1.2... Universal breaks with the newer angular updates as the angular team doesn't currently include it in their tests, that's why I've been updating the universal branch slower than the other branches

there's news?

@fdambrosio no, seems the universal branches will lag behind until they finish bringing it into and testing it against the angular core repo

with npm install I have this warnings:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed
.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was i
nstalled.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of webpack@1 || ^2.1.0-beta but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of webpack@1 || 2 || ^2.0.0-beta || ^2.1.0-beta but none w
as installed.

I get warnings with yarn as well with absolutely fresh checkout of this project.
Seems all seed projects have issues like this where they're never fully up-to-date.
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning Incorrect peer dependency<EMAIL_ADDRESS>warning Incorrect peer dependency "<EMAIL_ADDRESS>warning Incorrect peer dependency "webpack@1 || ^2.1.0-beta".
warning Unmet peer dependency "jasmine-core@*".
warning Incorrect peer dependency "webpack@1 || 2 ||

How can we fix?

there's a simple way to migrate our material+universal project to bootstrap+universal kit?
We need angular2+webpack+universal+responsive/adaptive layout, please can you tell how can do that?

@fdambrosio the branches are similar, so you could just manually make the changes, or follow instructions here: https://github.com/qdouble/angular-webpack2-starter/wiki/Recommended-Steps-for-Merging-Starter-into-Existing-Project

thanks @qdouble
bootstrap + universal works good?

@fdambrosio in JIT mode, there were no issues the last time I checked

I'm testing a fresh bootstrap+universal starter kit.
with yarn run universal the homepage crash with this error:
ReferenceError: window is not defined
    at _requestIdle (/node_modules/@angularclass/idle-preload/dist/index.js:17:15)
    at eInjector.get (e.ngfactory.js:139:99)
    at eInjector.get (e.ngfactory.js:144:115)
    at eInjector.get (e.ngfactory.js:149:85)
    at eInjector.createInternal (e.ngfactory.js:464:131)
    at eInjector.NgModuleInjector.create (/node_modules/@angular/core/bundles/core.umd.js:6968:80)
    at NgModuleFactory.create (/node_modules/@angular/core/bundles/core.umd.js:6953:22)
    at /node_modules/@angular/core/bundles/core.umd.js:6671:47
    at ZoneDelegate.invoke (/node_modules/zone.js/dist/zone-node.js:232:26)
    at Object.onInvoke (/node_modules/@angular/core/bundles/core.umd.js:6229:41)

@fdambrosio ah, just added that recently, try to do a git checkout to an earlier commit, I'll probably have to roll back some of the updates

Yeah idle-preload will never work with Universal.  I should have used a
switch is the code to activate it only when it is executed by the browser.
On Mon, Jan 9, 2017, 6:45 AM Anthony<EMAIL_ADDRESS>wrote:

@fdambrosio https://github.com/fdambrosio ah, just added that recently,
try to do a git checkout to an earlier commit, I'll probably have to roll
back some of the updates
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/qdouble/angular-webpack2-starter/issues/191#issuecomment-271265538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB7ujG2MSvRQzxxwfAa2FXh33KRa5rhdks5rQh3hgaJpZM4LA6PG
.

You can rollback it until I do the fix
On Mon, Jan 9, 2017, 9:16 AM Fabien Rogeret<EMAIL_ADDRESS>wrote:

Yeah idle-preload will never work with Universal.  I should have used a
switch is the code to activate it only when it is executed by the browser.
On Mon, Jan 9, 2017, 6:45 AM Anthony<EMAIL_ADDRESS>wrote:
@fdambrosio https://github.com/fdambrosio ah, just added that recently,
try to do a git checkout to an earlier commit, I'll probably have to roll
back some of the updates
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/qdouble/angular-webpack2-starter/issues/191#issuecomment-271265538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB7ujG2MSvRQzxxwfAa2FXh33KRa5rhdks5rQh3hgaJpZM4LA6PG
.

thanks, I'm trying 75b1b832157491569b0a1c04c9f1cc0c3d47b05e and it builds and run locally, but it doesn't load style.css  main.css and index.js (404 not found)
on server I have this error:
# node index.js
module.js:472
    throw err;
    ^

Error: Cannot find module 'core-js/es6/reflect'

please update for angular 4.0.0

closing... universal branches will be updated when it's stable in Angular 4


Move the ECC setup and tear down into it's own globar RAII object

The test suite crashes and burns because the ECC library is set up and torn down many time.
This pull request puts the initialization and tear down functions into a global RAII object so it only happens once, even when the test suite is setup and torn down multiple times.
This smells of a bug somewhere else, but this is a neat workaround.

Thanks


issue-3

Your branch confilcting with master. Please, update your master to actual version.
You can do it executing git pull origin master command.


[kube-keepalived-vip] Exited due to segmentation fault (SIGSEGV)

Kubernetes version: v1.7.4
Following the steps in the documentation, I created a single yaml file to reproduce:
apiVersion: v1
kind: ReplicationController
metadata:
  name: echoheaders
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: echoheaders
    spec:
      containers:
      - name: echoheaders
        image: gcr.io/google_containers/echoserver:1.4
        ports:
        - containerPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: echoheaders
  labels:
    app: echoheaders
spec:
  type: NodePort
  ports:
  - port: 80
    nodePort: 30302
    targetPort: 8080
    protocol: TCP
    name: http
  selector:
    app: echoheaders
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kube-keepalived-vip
  namespace: default
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: kube-keepalived-vip
rules:
- apiGroups: [""]
  resources:
  - pods
  - nodes
  - endpoints
  - services
  - configmaps
  verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: kube-keepalived-vip
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kube-keepalived-vip
subjects:
- kind: ServiceAccount
  name: kube-keepalived-vip
  namespace: default
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: vip-configmap
data:
  <IP_ADDRESS>: default/echoheaders
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-keepalived-vip
spec:
  template:
    metadata:
      labels:
        name: kube-keepalived-vip
    spec:
      hostNetwork: true
      serviceAccount: kube-keepalived-vip
      containers:
        - image: gcr.io/google_containers/kube-keepalived-vip:0.9
          name: kube-keepalived-vip
          imagePullPolicy: Always
          securityContext:
            privileged: true
          volumeMounts:
            - mountPath: /lib/modules
              name: modules
              readOnly: true
            - mountPath: /dev
              name: dev
          # use downward API
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
          # to use unicast
          args:
          - --services-configmap=default/vip-configmap
          # unicast uses the ip of the nodes instead of multicast
          # this is useful if running in cloud providers (like AWS)
          #- --use-unicast=true
      volumes:
        - name: modules
          hostPath:
            path: /lib/modules
        - name: dev
          hostPath:
            path: /dev
      nodeSelector:
        type: worker

$ kubectl get po
NAME                        READY     STATUS    RESTARTS   AGE
echoheaders-smfnc           1/1       Running   0          5s
kube-keepalived-vip-dk0vj   1/1       Running   0          5s
$ kubectl logs kube-keepalived-vip-dk0vj
VRRP child process(489) died: Respawning
Starting VRRP child process, pid=491
Registering Kernel netlink reflector
Registering Kernel netlink command channel
Registering gratuitous ARP shared channel
Opening file '/etc/keepalived/keepalived.conf'.
pid 491 exited due to segmentation fault (SIGSEGV).
  Please report a bug at https://github.com/acassen/keepalived/issues
  and include this log from when keepalived started, what happened
  immediately before the crash, and your configuration file.
VRRP child process(491) died: Respawning
Starting VRRP child process, pid=493
Registering Kernel netlink reflector
Registering Kernel netlink command channel
Registering gratuitous ARP shared channel
Opening file '/etc/keepalived/keepalived.conf'.
pid 493 exited due to segmentation fault (SIGSEGV).
  Please report a bug at https://github.com/acassen/keepalived/issues
  and include this log from when keepalived started, what happened
  immediately before the crash, and your configuration file.
[...]

Me, too.
The logs are repeated without interruption.

@arthur0 @moonek please check if the image aledbf/kube-keepalived-vip:0.16 solves the issue

@aledbf Yes, this image solves the issue for me. Grateful.

@aledbf do you have a diff / can point to the changes you did to make it work ?

@primeroz please check https://github.com/aledbf/kube-keepalived-vip/


Check logic of vouching query 1541516

Part of #28

Is this related to a specific epic/milestone that we can tag this with (for better overview in project management tools)?

Addressed with PR #19


Add CSP for localhost and github pages

Currently, iframes are not allowed to show content from SEDOS dashboard.
We want to allow localhost (for local development) and sedos-project.github.io (for documentation).
This can be done via package django-csp read more at: https://www.stackhawk.com/blog/django-content-security-policy-guide-what-it-is-and-how-to-enable-it/

Fixed in latest dev.
Did not use CSP package. Instead I simply removed clickjacking Middleware.


make homebrew for diagnostics collector

it is already here https://github.com/rsvihladremio/homebrew-ddc


remove desmos in favor of recharts

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2502   👈

This comment was auto-generated by Graphite.


Specifies the CRDT used for Gossiping in Consensus

Gossiping is specified in terms of a CRDT.
Pull requests over branch gossip-spec will serve to get early feedback until gossip-spec is ready to be merged into main.

Overall, I believe that specifying the state of a (BFT) SMR protocol as a CRDT is a very interesting approach. From a curiosity point of view, it would be interesting to see if this can be done solely with set of messages. However, maybe it is easier to have also some state with predicates over it. For instance, as suggested in the comments below, a base predicate can be  which returns  if there is a proof that some round  has ended.

Agree that having these predicates will make it easier to specify and read. This is the approach I will be taking on the supersession operator and probably other places as well.

I think the use of CRDTs is well supported by this document, that covers some empty gaps existing in the previous version.
However, I think this document would benefit from having the merge/tombstone operators being used, even as an example, for the actual consensus messages.
Further recommendations:

Avoid changing code, even if correcting misspelled comments in code, in spec PRs
Try breaking long lines into smaller ones for easy reading and better version control
Check the math symbols adopted and make sure they are rendered by GitHub

Wrt 1. reverted.
Wrt 2. I prefer breaking on period ends exactly for better version control, as I won't have to move words around to rebalance lines when some small edit happens.
Wrt 3. Will do in the follow up PR.

@cason Are you ok with me addressing the the remaining comments in the follow up PR?


Comments icon colored with no new comments

It appears that #515 contains a bug: In production I just posted an answer to a user comment on one of my media, and now I have a yellow comment icon in the navbar indicating that there are new comments, while clicking on the icon shows there are none:

There is no way to decolor the yellow icon (only waiting until someone posts a new commmment somewhere and the clearing all commments). This is actually something we wanted to avoid in #515 but for some reason, it does not work.

I can reproduce it in development. Starting scenario: Teacher has no unread comments. Student posts new comment for a medium that does not have a comment yet (I do not know if the latter part  is relevant). Teacher's new_comment icon in the navbar turns yellow. Teacher goes directly to the medium and displays comments under /media/:medium_id/show_comments and replies. Then Teacher clicks on the yellow new_comments icon and finds that it does not show anything.

A quick inspecttion of the code in comments_controller.rb shows that at no point in the workflow described above the unread_comments flag for the Teacher user is set to false.


Update reflectx to allow for optional nested structs

Based on https://github.com/jmoiron/sqlx/pull/847, but fixed an issue that optional pointer fields are not handled correctly.

Nested structs are now only instantiated when one of the database columns in that nested struct is not nil. This allows objects scanned in left/outer joins to keep their natural types (instead of setting everything to NullableX).
Example:
select house.id, owner.*,
from house
left join owner on owner.id = house.owner

Before
type House struct {
 ID      int
 Owner   *Person // if left join gives nulls, Owner is set
}

type Owner struct {
 ID sql.NullInt64 // make nullable columns even tho if table doesn't have those columns nullable
}

After
type House struct {
 ID      int
 Owner   *Person // if left join gives nulls, Owner will be nil
}

type Owner struct {
 ID int    // no need to set this to sql.NullInt
}

Hello, @ardan-bkennedy, and I recently stepped in to help maintain this project.
We are sorting the opened issues and pull requests and would like to know if you still NEED this merged.
Thank you for your contribution.

This would be insanely useful 🙏🏻

Would love for this to be merged. I have been using sqlx with these changes for some time as it is a feature I find really useful.

@dlsniper This issue is precisely what forced me to ditch sqlx many years ago. Now I ran into it again in another project... Hoping to see this merged soon 🤞🏻

I tried this change in my project, and there are definitely breaking changes. The code copies from stdlib convertAssign, but it's not fully compatible with it. For example, without this change scanning an int64 value into string field works fine, but with this change it fails. I'm looking at the code trying to figure out I could address this issue.

@dlsniper @ardan-bkennedy I created another followup PR: https://github.com/jmoiron/sqlx/pull/950. It addresses incompatibility issues, adds tests, and is much shorter. It would be great if you could take a look at it!


ReadyQueue: takes futures and yields their values

Work in progress
ReadyQueue is a structure into which an arbitrary number of futures
can be pushed. ReadyQueue implements Stream, yielding the inner
futures' resolved values as they become ready.
This structure can handle large numbers of futures efficiently.

cc @alexcrichton, this PR isn't ready yet. The tests don't all pass. Currently, dropping ReadyQueue doesn't drop the inner futures. Fixing this will require a somewhat significant restructure.

I updated the PR.
I now use UnsafeNotify because I couldn't get Arc<Inner<T>> to implement Notify and be able to be converted into a NotifyHandle. This is due to the 'static requirement on NotifyHandle. I didn't want ReadyQueue to require 'static because it isn't actually required for safety (the notify implementation never can read T).

@alexcrichton This PR should be ready to merge into the restructuring branch.


Should we really use the name useTry?

Can a function be called a hook just because it's returning an array?
Because of the naming,

eslint will now show irrelevant lint info on it, and not allow it to be called conditionally.
it implies that it's to be used inside functional components, but in reality, it could be used literally anywhere.

That very much seems like an issue with eslint. If it's assuming that any function that starts with the word use is a React Hook, then there's a bigger issue there to deal with.
I'm not sure how the name implies it should be used in functional components, this isn't targeted at React. Like you said, this can be used anywhere.

Then why are we introducing the useTry export instead of noTry? It seems very much inspired by React hooks, which are render-only functions.

Besides, it's not even using any React hook internally, nor does it do any closure storage to get the latest state value like useState and others. So if it's not intended to be a hook, we should refrain from using the use prefix.
Found this to be relevant to our issue:
https://github.com/facebook/react/issues/15227

We are using useTry because under the hood, the function is still using a try-catch. We're just abstracting it away, we are still using try-catch.
A developer coming along to a piece of code containing this library, seeing noTry without prior knowledge of the library, will add cognitive load to understand what the piece of code is actually doing. useTry is much less complex and a lot easier to get a quick understanding of what's happening.
React do not, and cannot, own a prefix for functions. That is simply outrageous. The problem here lies in the eslint-plugin-react-hooks and how they are determining what a React Hook is.
Other non-React libraries may also be using the use prefix, as highlighted by the issue you attached.
If you are having an issue with eslint regarding the usage of this library as a React Hook you have 3 options:

Use the noTry export. It still exists, and you can use it safely.
Use in-line eslint disable // eslint-disable-next-line react-hooks/rules-of-hooks
Configure eslint to not run on the files that you are using useTry with.

fair enough, thanks @Coly010 🙂