Multinet slower than Alexa

While Wakenet is only trivially slower than Alexa, Multinet is perceptible slower.
I timed a very unscientific video of all three turning on my living room lights and here is what I have found:

Alexa - 1.28 seconds
Wakenet - 1.58 seconds
Multinet - 3.33 seconds

I have confirmed that the command TURN ON LIVING ROOM LIGHTS is in speech_commands/commands_en.txt.
What else do I need to do in order to improve my multinet speeds?
EDIT: removed movies from automatically showing due to bringing browser to a crawl, hoping links above will still work.

Generally when I do speed comparisons between Alexa and Willow I set my Willow wake word to Alexa so variations in speech and in this case start of the timer (finger) don't impact results. There's an additional issue in that we've observed the command time with Home Assistant can vary quite a bit between executions (HA has to receive the command from Willow/Alexa and issue to device). What version of HA are you running? If it's 2023.5 we use websockets and they are substantially faster.
In our testing we consistently see the Willow device confirm before Alexa.
Depending on a variety of factors (your total commands, command lengths, etc) multinet is typically slower. We haven't spent as much time optimizing it but we'll get into it at some point.

We suggest people use "Hi ESP" especially if you already have Alexa devices (like I do) for obvious reasons. I only suggested using Alexa with Willow for your Alexa v Willow bake-off :).
The "Hi Lexin" wake word comes from the English pronunciation of the Chinese name of Espressif, from what I understand. The pronunciation is so strange it's almost useless and I myself am only able to trigger it maybe 20% of the time. We may end up just disabling it.

Ya, was only trying "HI Lexin" as it was one syllable shorter, will stick to "Hi ESP" and hope for a "Willow" wake word in the future ;).
I will look to change the VAD to try and squeeze out a bit more performance.
Going to build with "Alexa"/multinet now to see if there is still same delay.

Until multinet is optimized it sounds like for right now if people want the quickest response they should use wakenet, if they want to keep things local use multinet.

One of the reasons I would love multinet to be faster is I have been trying to make sure all my home automations work when power and even internet go out. So I will have to see if I can live with the multinet lag.

One clarification - you're always using Wakenet. Wakenet is for wake word, multinet is for local speech commands, and server/WIS mode is using a Willow Inference Server.
Speaking of which, we will be releasing WIS tomorrow.  That's not the goal for this project.
For performance with accuracy WIS strongly prefers CUDA. If you have CUDA hardware on your WIS instance a locally hosted WIS is the most private, fastest, and most reliable of all options. WIS has been highly optimized by us for acceleration on Nvidia hardware going back to Pascal. I'll be testing, demoing, and documenting CUDA hardware configurations using $100 used GTX hardware later this week. WIS runs on CPU but the performance isn't any better than other CPU Whisper implementations which is to say it won't be competing with Alexa for speed and accuracy anytime soon.

You might have given me reason to dust of my hardly used/old gaming computer...would just want to see how low I could make the energy consumption.

I can't remember exactly what the card is but I think it was a GTX 1080? Maybe a 1040?
Oh yes, I was already planning on making it dual boot headless Linux (if I didn't previously) and then putting Proxmox with a HA image. I would be putting it on a Zigbee power outlet that should be able to tell me energy used.

To my knowledge there is no such thing as a GTX 1040 so between those two options I'd say it's a 1080, which should work quite well with WIS.
We've tested WIS in WSL for users who want to use Windows gaming machines but given the option I wouldn't go that route.

Heh, I will look at it later and figure out what it is!

...you can tell I am not much of a gamer...

So it is a NVIDIA GeForce GTX 1070.

Perfect! I'm actually going to be doing benchmarks with my recently ordered GTX 1070 later this week. For new users it's probably the best bang for the buck right now.

Have Proxmox installed and ready to WIS at it. Will I be needing to do a VM or will you be releasing a container?

It is containerized but setup is a little more involved than docker run - much like willow today it is early.

WIS released - discuss on HN


Unable to use outline with search editor

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

Version: 1.68.1
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630
Date: 2022-06-14T12:52:13.188Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0
Steps to Reproduce:

Search in files, and search something
Click 'Open in editor' to open search editor
When search editor is the current editor, click item in the outline panel
New search editor with name '.' is open, with an error message in the middle of that editor: "The editor could not be opened due to an unexpected error: Unable to resolve resource search-editor:#0.908...."

Hi! I am a first time contributor looking to make my first contribution. I am able to reproduce the bug, and for clarification, have taken photos:

That's the bug, yes

That's the bug, yes. I would take a PR but don't know where to point you on this one off the top of my head.

Hi!! I have been looking through the source code that creates the workbench tree (for the outline pane) and can't seem to find where the event, when the outline is created, is attached to each tree element. Would you happen to know where that is?
(The click event being to move the document to the proper location.)

Sorry, I'm not sure I understand what you're asking for

That's the bug, yes. I would take a PR but don't know where to point you on this one off the top of my head.

Hi!! I have been looking through the source code that creates the workbench tree (for the outline pane) and can't seem to find where the event, when the outline is created, is attached to each tree element. Would you happen to know where that is?
(The click event being to move the document to the proper location.)

Registering the event that gets triggered on click of the tree elements is here:
https://github.com/microsoft/vscode/blob/ab1a31add4608f484d555e3c791f03321a4dda5f/src/vs/workbench/contrib/outline/browser/outlinePane.ts#L306
But you can probably also look at how other things interact with the outline service to properly populate it with custom info. I haven't taken too thorough of a look at the outline code yet, but I'm assuming that that's how it would end up being like

Hi, in 1.77.0-insider this bug still exists, any progress on it?


fix substitution flickering?

i saw this in nvim-cmp which uses redraw in a vim schedule to refresh the completion window in command mode.
i tried it with noice and it seems to remove the flicking from substitution.
redrawing in a command mapping seems fine. which means the schedule method should be safe.
it also hasn't crashed on me in my testing at all.

nvm there is a slowed down infinite recursion in this pr


GUI not showing up

Microsoft PowerToys version
0.68.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
Openning fresh install.
✔ Expected Behavior
GUI to show up.
❌ Actual Behavior
Only a window shows up without GUI.
PowerToysReport_2023-03-23-19-06-28.zip
Other Software
No response

What do you mean?
The GUI of the settings or what exactly isn't working?
/needinfo

I tried reinstalling it from git, same deal. I tried the troubleshooting methods from git forum, nothing worked.
Blank screan. Windows up to date, drivers for the graphic card up to date.
If you need more info i will update happily!

cc: @niels9001

I can't find any relevant information in the logs. Does this also happen in other apps (for example in the Microsoft Store). Does PowerRename work?
/needinfo

I've had the same issue.
Multiple versions have the same issue.
It may be related to the system version of Windows
版本	Windows 10 专业版
版本号	22H2
操作系统内部版本	19045.2673
体验	Windows Feature Experience Pack 120.2212.4190.0


Do I need a cri-containerd with CoreOS?

Hello. Trying to follow your hard way, but stuck with installing cri-containerd on worker nodes.
The problem is that when I try to untar cri-containerd-1.0.0-beta.1.linux-amd64.tar.gz into root /, tar says:

tar: ./usr/local/bin: Cannot utime: Read-only file system

From SO I learned that /usr is read-only by design in CoreOS. Can I skip cri-containerd installation when using CoreOS for worker nodes? If not, how should I install it then?

Can I skip cri-containerd installation when using CoreOS for worker nodes?

Yes, but you will have to modify the kubelet systemd service files to depend on docker instead. This is vaguely what my kubelet systemd service files look like:
[Unit]
Description=Kubernetes Kubelet
Documentation=https://github.com/kubernetes/kubernetes
After=docker.service
Requires=docker.service

[Service]
ExecStart=/home/core/usr/local/bin/kubelet \\
  --allow-privileged=true \\
  --anonymous-auth=false \\
  --authorization-mode=Webhook \\
  --client-ca-file=/var/lib/kubernetes/ca.pem \\
  --cloud-provider= \\
  --cluster-dns=<IP_ADDRESS> \\
  --cluster-domain=cluster.local \\
  --container-runtime=remote \\
  --container-runtime-endpoint=unix:///var/run/docker.sock \\
  --image-pull-progress-deadline=2m \\
  --kubeconfig=/var/lib/kubelet/kubeconfig \\
  --network-plugin=cni \\
  --pod-cidr=${pod_cidr} \\
  --register-node=true \\
  --runtime-request-timeout=15m \\
  --tls-cert-file=/var/lib/kubelet/${instance}.pem \\
  --tls-private-key-file=/var/lib/kubelet/${instance}-key.pem \\
  --v=2
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target

The major difference here are the Before and After settings:
After=docker.service
Requires=docker.service

And the --container-runtime-endpoint setting:
  --container-runtime-endpoint=unix:///var/run/docker.sock \\

With this setup you should of course leave out the cri-containerd and containerd services when using systemctl to start up the kubelet and kube-proxy services.

By the way, in case it's not obvious I'm also using CoreOS instead of Ubuntu and I ran into the same problem you did. Another option if you still want to use cri-containerd is to unarchive the tarball in the /home/core directory using tar -xvf cri-containerd-1.0.0-beta.1.linux-amd64.tar.gz -C /home/core, then modify /home/core/etc/systemd/system/containerd.service and /home/core/etc/systemd/system/cri-containerd.service to point to the correct path for the containerd and cri-containerd binaries then copy them into /etc/systemd/system. There might be more than that to do but around that point in my analysis I figured it would be simpler just to go with docker so that's what I did.

UPDATE: I wrote my original comment prematurely, I still need to work out a couple bugs in my docker CRI setup to get kubelet working.

Hi and thank you for explanation and workarounds. I was wondering if this guide also misses flannel installation. Why? Or it is not required here for some reasons?

This guide is to provide one path for bootstrapping Kubernetes. Docker and flannel are not required my Kubernetes.


SEO problem (Link not crawlable)

First of all, thanks for the helpful library.
Just want to ask here to see if this happens to anyone else too. I had a website that uses react-scroll's Link and Element. Few months ago, the SEO was still 100 until recently when I did another lighthouse test, and the SEO dropped to 90 saying that the links are not crawlable.
Just wondering if there is something that I can do on my side to fix this?

Have you tried adding the href tag?

Do you mean passing another href prop to react-scroll's Link? Currently what I have is a shared component using Link which I created by referring to the usage in the docs.

Hi everyone,
may I know what you have put inside the href? because if I put '#' the plugin no longer works, while if I leave it empty the error in the SEO persists ....
thank you

Hi everyone, may I know what you have put inside the href? because if I put '#' the plugin no longer works, while if I leave it empty the error in the SEO persists .... thank you

For my case, its just a single page website, so I just put '/' in the href. Not sure if that helps.


Default variant can't be installed

Change-Id: I020824c2464d139776ddf5dbbceb3ff03fb52c8a
Please provide a description of this PR:
Recent change to add distroless made it impossible to install default ( it is built as ":latest" - not ":latest-default" ).
We may change the build to produce ":latest-xxx" - but we've been using this pattern since 1.0.
Alternative is to use the same style we use for -revision ( instead of "with" ).

@costinm: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
18fafbc104dd0abbf103cad3d5eb3631d8f9293d
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

You can do this today I think:
$ helm template cni manifests/charts/istio-cni/ --set profile=ambient --set global.variant="" | rg image:
          image: "gcr.io/istio-testing/install-cni:latest"
$ helm template cni manifests/charts/istio-cni/ | rg image:
          image: "gcr.io/istio-testing/install-cni:latest"

cool - was trying "variant=default". Closing.


Ensure that we can properly reset MFA attempts

drive-by fix to ensure git is installed in the docker container

Coverage increased (+0.02%) to 87.32% when pulling 7a755526c0326555e899f23fe44b685f7f38678b on bug/mfa-check into 83da808de4dbc6bfea6674be8e8186a2575608e8 on main.


Check whether Layer 7 protocol docs work before v1.17 release

~Some Layer 7 network policies are beta and require manually building Envoy with Go extensions, but the documentation doesn't make this very clear. For example,~ The Cassandra guide implies that you can just install a standard quick-install version of Cilium to get up and running, but this does not work. Not only this, but there is no validation in the network policy engine to inform the user that the deployed software will not implement their requested policy.
In practice when I ran through the Cassandra guide with a relatively default configuration (via local kind dev environment including external Envoy), I found that (a) it requires 10GB+ of memory (surprise!) and (b) once the policy is applied, all connections to the cassandra server are broken. This makes the guide effectively broken if you just follow the guide and don't know what you're doing to build & deploy custom Envoy extensions for the protocol support.
$ kubectl exec -it $HQ_POD -- cqlsh cassandra-svc
Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>:9042': ConnectionShutdown('Connection to <IP_ADDRESS>:9042 was closed')})
command terminated with exit code 1

To poke around and confirm my suspicions here, I also tried to follow the memcached example. Some of the steps didn't work, but in the end when the network policy was applied I was able to get some protocol-specific access denied messages with v1.17.0-pre.2. Probably for v1.17 final we should try out the various L7 protocol examples and make a call feature by feature whether to fix / update docs / drop the instructions.

Resolved via #36477.


How to realize function like navigator.replace() ?

You would import NavigationActions and call/dispatch NavigationActions.reset.
Docs: https://reactnavigation.org/docs/navigators/navigation-prop#Reset

Yeah，I had tried this last night,and it does well
Thanks!

@rmevans9 @justbettereveryday
https://github.com/react-community/react-navigation/issues/802
I think reset is not what we want.
It sounds like reset will empty your stack instead of replacing one item in your stack.

Meanwhile one could be able to do this by getting the whole state and overwriting the current route with the new one, the problem is that it's also not so easy to get the whole state, since in navation prop it's only the portion of the current route...

@joonhocho reset now accepts a key parameter which allows you to specify what level of state you want to reset to: https://github.com/react-community/react-navigation/pull/789
There's also the option of overriding getStateForAction as shown in this video: Replace a Screen Using React Navigation
However, if reset (with a key) doesn't work as required then I agree that adding replace to the stack api would be much more user friendly than overriding getStateForAction.

Hi! In an effort to get the hundreds of issues on this repo under control I'm closing issues tagged as questions. Please don't take this personally - it's simply something we need to do to get the issues to a manageable point. If you still have a question I encourage you to re-read the docs, ask on StackOverflow, or ask on the #react-navigation Reactiflux channel. Thank you!

@spencercarli Hey Spencer, we ended up using your solution to create a replace method for react-navigation. Works pretty well besides not having an animation, but I still think this is less of a question and more of a feature request.
I think this should be added to the core library because it's such a common situation. And because this is the "standard" navigation library for React Native now, it should cover the most common situations, including replacing the current screen with a new screen and support an animation between those two.

const reset = (navigation, routeName, params = {}) => {
  const resetAction = NavigationActions.reset({
      index: 0,
      actions: [
          NavigationActions.navigate({ routeName, params })
      ],
  });

  navigation.dispatch(resetAction);
};

@sibelius Does that provide an animation?

@joshuapinter no animation and feedback slowly

Any update on this?

this was added recently: https://reactnavigation.org/docs/navigation-prop.html#replace
it doesn't have any animation. it'll take some work on the card stack transitioner to make an animation possible here.

Still a newbie in JS, but this is my hack for replace with animation (not submitting a pull request due to poor code quality)
https://github.com/react-navigation/react-navigation/compare/master...vkedwardli:feature/navigation-action-stack-replace-with-animation
basically you can just call navigation.replaceWithAnimation(routeName, params, action)
What I did: I remove the previous screen from the routes during COMPLETE_TRANSITION (so we can have animation) and then reset the Transitioner's navigation index to the correct values
My environment is a Stack (for those login / splash stuff) -> Tab -> Stack -> Tab, seems to be working on my side, YMMV

cc @ericvicenti ^

Interesting hack, @vkedwardli! I've been thinking about how to get this right for a little while now, and I just had an idea.
Something has been missing in our navigation state that we pass from the stack router to the transitioner, and I think I just realized what it might be. Currently we hold 'isTransitioning' in state, but we don't know what key we were transitioning from. So instead of isTransitioning, what if we had transitioningFromKey, which specified the key we are currently moving away from.
With the following "before" state:
{
  index: 1,
  routes: [ {key: 'a'}, {key: 'b'} ],
  transitioningFromKey: null
}

When the state changes to this, there is no transition.
{
  index: 1,
  routes: [ {key: 'a'}, {key: 'c'} ],
  transitioningFromKey: null
}

When the state changes to this, we do an animated replace to 'c':
{
  index: 1,
  routes: [ {key: 'a'}, {key: 'c'} ],
  transitioningFromKey: 'b'
}

I think this might be the sanest way to model our transitioning state. It would also enable animations for reset.
Thoughts?

@ericvicenti
navigation.replace transitioning animation
Is this problem solved?

use this function to replace the history in react navigation:
this function in your root navigation file App.js
const prevGetStateForActionHomeStack = RootStack.router.getStateForAction;
RootStack.router.getStateForAction = (action, state) => {
if (state && action.type === 'ReplaceCurrentScreen') {
const routes = state.routes.slice(0, state.routes.length - 1);
routes.push(action);
return {
...state,
routes,
index: routes.length - 1,
};
}
return prevGetStateForActionHomeStack(action, state);
};
call this function whenever you want to replace a screen
this.replaceScreen('routename')
replaceScreen = (route) => {
// const { locations, position } = this.props.navigation.state.params;
this.props.navigation.dispatch({
type: 'ReplaceCurrentScreen',
key: ${route},
routeName: ${route},
// params: { locations, position },
});
};

No it will not give you an animation.
On Tue, 21 Aug 2018, 8:23 pm Timur<EMAIL_ADDRESS>wrote:

@tiann https://github.com/tiann will this give me an animation?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-navigation/react-navigation/issues/774#issuecomment-414714130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZc-rTSBfSHko-C7U-_3lo0v_vffCf7eks5uTCX5gaJpZM4Mkywx
.

@ hafizmuhammadshoaib thank you, it works like a charm!!
this is the formatted code:
Add this to your Root Navigator:
const prevGetStateForActionHomeStack = HomeStack.router.getStateForAction;
HomeStack.router.getStateForAction = (action, state) => {
    if (state && action.type === 'ReplaceCurrentScreen') {
      const routes = state.routes.slice(0, state.routes.length - 1);
      routes.push(action);
      return {
        ...state,
        routes,
        index: routes.length - 1,
      };
    }
    return prevGetStateForActionHomeStack(action, state);
  },
};

Use this to replace screen:
  replaceScreen = (screen, params) => {
    this.props.navigation.dispatch({
      key: screen,
      type: "ReplaceCurrentScreen",
      routeName: screen,
      params: params,
    });
  };

你好，使用这个方法之后报了一个异常如下，请教哈怎么处理 多谢

please give me some code from where you are calling this code?? are you using a drawer???

import {StackActions} from 'react-navigation';
import {NavigationActions} from 'react-navigation';

const resetAction = StackActions.reset({
    index: 1,
    actions: [
    	// add other screen if you want
        NavigationActions.navigate({routeName: 'screen2'}),
        NavigationActions.navigate({routeName: 'newScreen'}),
    ],
});


When a dirty node is not in the tree, we should not clear the dirty bit.

Suppose you have two widgets that use global keys, let's call the A and B.
Suppose further that the first time you build the tree, B is a descendant of A.
Not suppose that at some point, the tree is rejiggered such that the following happens:

A, and its descendants including B, are removed from the tree.
A, and its descendants including B, are readded to the tree. This marks A and B dirty.
When A is built, it removes B from the tree, because it now has different children.
B is then processed as well, but it's not in the tree so it's dirty bit is cleared.
Finally, some other node deeper than either A or B puts B back in the tree.

At this point, B will be marked dirty, however, it is already in the dirty list, and this will fire an assertion.

(I have a fix for this, just need to clean up my test.)


How to use it in sveltekit project?

My code
<script>
import { onMount } from 'svelte';
let PdfViewer;
onMount(async () => {
		const module = await import('svelte-pdf');
		PdfViewer = module.default;
	});

</script>
<svelte:component
	this={PdfViewer}
	url="https://raw.githubusercontent.com/vinodnimbalkar/svelte-pdf/369db2f9edbf5ab8c87184193e1404340729bb3a/public/sample.pdf"/>

it shows this error

Hi @CHETANECINFOSOLUTIONS
<script>
	import PdfViewer from 'svelte-pdf';
</script>

<PdfViewer url='https://raw.githubusercontent.com/vinodnimbalkar/svelte-pdf/369db2f9edbf5ab8c87184193e1404340729bb3a/public/sample.pdf' />

Please check this: https://stackblitz.com/edit/sveltejs-kit-template-default-pjuhkj

Yes, I have tried this way also still returns same error.

Has anyone got this working in sveltekit? as of April 2024?

Has anyone got this working in sveltekit? as of April 2024?

you can try using this library, it works.
https://pdfjs.express/documentation/get-started/svelte

Has anyone got this working in sveltekit? as of April 2024?

I have I working on sveltekit !

Has anyone got this working in sveltekit? as of April 2024?

I have it working on sveltekit !

Have you got a working repo I can take a look at?

Has anyone got this working in sveltekit? as of April 2024?

I have it working on sveltekit !

Have you got a working repo I can take a look at?

Regrettably not, but if you want you can show me your implementation and I can help you with it

Has anyone got this working in sveltekit? as of April 2024?

I have it working on sveltekit !

Have you got a working repo I can take a look at?

Regrettably not, but if you want you can show me your implementation and I can help you with it

Unless I'm missing something there's not much implementation to talk about, so let's assume the implementation at the top (initial post on this issue). Or the one in the docs:
<script>
	import PdfViewer from 'svelte-pdf';
</script>

<PdfViewer url='./sample.pdf' />

I also get the same error:
This document requires a password: Setting up fake worker failed: "Cannot load script at: http://localhost:5173/node_modules/.vite/deps/pdfjs-dist/build/pdf.worker.js".
It seems that it goes in here:
https://github.com/vinodnimbalkar/svelte-pdf/blob/master/src/lib/PdfViewer.svelte#L189
But I guess that this has to do with the installation.
In my project, the pdfjs-dist/ directory is located in the root level of node_modules/ instead of in node_modules/.vite/ directory as the error reports. Additionally, upon npm run build I get this warning:

Using @sveltejs/adapter-vercel
Warning: The following modules failed to locate dependencies that may (or may not) be required for your app to work:
node_modules/pdfjs-dist/build/pdf.mjs
- canvas
✔ done
✓ built in 2.57s


How to deploy easegress as a cluster

Add cookbook chapter about easegress cluster. Depends on https://github.com/megaease/easegress/pull/382

Please remember to update README.md ##User Cases, README.zh-CN.md ## 用户案例  and doc/cookbook/README.md


CMake package support

This PR updates the CMake support in DirectXTex to support find_package(directxtex CONFIG):
find_package(directxtex CONFIG REQUIRED)

target_link_libraries(foo Microsoft::DirectXTex)

Related to this issue: https://github.com/microsoft/DirectXTK/issues/247


Feature add x location with rebase

close #197

see if this works. if not we should just squash and merge the old PR #198


feat: Implement core::hash::Hasher for Hasher

This PR is an attempt to implement core::hash::Hasher for Hasher.
To achieve that, I first needed to transform Hash into a u64 (https://github.com/BLAKE3-team/BLAKE3/commit/bde6e6f8918b1d909ea4e1a006da5f893a279dbf):

This is an attempt to encode an Hash into u64. This transformation
will increase the number of collisions as u64 can represent fewer
values than [u8; OUT_LEN] (at the time of writing, OUT_LEN is set
to 32).
Bytes from Hash are extracted by chunks of 8, and then added to
u64 with a modular addition.

Then, core::hash::Hasher can be implemented (https://github.com/BLAKE3-team/BLAKE3/commit/41baa2f7759c95d1b8469639cfc02c8946a1dfb3):

This is an attempt to implement the standard Hasher API for
blake3, so that implementors can use blake3 when a generic hasher
is expected.

Things that must be discussed:

Do you want Hasher to implement core::hash::Hasher?
Do you find acceptable the strategy to convert Hash into u64?
If OUT_LEN % 8 != 0, bytes will be missed by From<Hash> for u64. Can it be different? Do we have to assert that?

There was a similar proposal here, but we decided against it: https://github.com/BLAKE3-team/BLAKE3/pull/87

Do you want Hasher to implement core::hash::Hasher?

As mentioned above, probably not. But let me know what you think of the discussion at #87.

Do you find acceptable the strategy to convert Hash into u64?

Yes, I think there are three reasonable options:

modular addition, like you're doing here
xor
just truncating the hash to 8 bytes

The third option does seem kind of lazy compared to the first two, but it's what BLAKE3 already does if you request a short output.

If OUT_LEN % 8 != 0, bytes will be missed by From for u64. Can it be different? Do we have to assert that?

OUT_LEN is defined to be 32 bytes in the published spec, and that will never change. It's kind of like the values of the IV constants in that way. So I think it's fine to assume things like this in calling code.

Lot to read in order to formulate a counter point of view. Give me few days :-). Thanks for your feedback!

I should add that I've been thinking a lot about "structured hashing" recently. (That term seems to be overloaded but I don't know what else to call it.) I feel like a widely useful standard could be doable. But at the same time, I don't think it would be a small project. Here's a random part of the question I was thinking about today, provoked by this PR:

How do we hash something like:
struct Foo {
    a: String,
    b: String,
}

Broadly speaking, it seems like there are two options. We either concatenate the bytes of the strings themselves with some kind of delimiter, or we hash them individually and concatenate their hashes. I'll call these approaches hashing together vs hashing separately. (For now I'll ignore mixed options like "hash them separately if they're above a certain length".) The upside of hashing separately is that the resulting structure is "more incremental" with respect to b. For example, say both a and b actually come from long streams of data, and we'd like to compute the final Foo hash incrementally without allocating a ton of memory to buffer either or both of the streams. In the hashing together approach, we'd start by feeding a into our final digest, we'd throw in some sort of counter and/or delimiter, and then after that we'd feed in b. This isn't ideal, because we can't make any progress reading the b stream until the a stream is entirely finished. That could be an issue in some interesting use cases.
If the programmer anticipated that this was going to be an issue, they could work around it by just defining Foo to hold the hashes of a and b rather than the strings themselves. That would effectively convert the hash together approach into the hash separately approach. However, there's a subtle security issue here, very reminiscent of the issues that come up in designing a tree hash. (Foo is kind of like a small tree with two leaves, right? When all I have is a hammer...) If we hash the strings separately, then "generalized length extension" attacks become possible. For example, if only know the hash of a, and not the contents of a, I can still compute the hash of a larger Foo struct that contains a. Again, this might be an issue in some interesting use cases. The defense again this sort of attack is to domain separate the hashes of interior fields from the "root" hash, like we do when we construct secure tree hashes, so that those interior hashes are never published. This isn't hard to do once the problem is clear, but it's something that one-off designs in the wild are likely to get wrong, and it's a way that a new standard might be able to distinguish itself.

Anyway, this is a big design space, and I probably shouldn't clutter up the BLAKE3 issues with too much discussion of it :) But if this is something that you or other folks want to discuss further, we could set something up.


Goto definition doesn't work on a standalone C++ Header (after installing the C++ VSIX)

[Window Title]
Visual Studio Code
[Main Instruction]
Visual Studio Code
[Content]
Version 0.10.11
Commit f291f4ad600767626b24a4b15816b04bee9a3049
Date 2016-03-11T17:10:35.304Z
Shell 0.35.6
Renderer 45.0.2454.85
Node 4.1.1
Steps to Reproduce:

Open standalone header with some classes defined
Find a member variable
Goto definition
It doesn't jump to the member variable

This is an issue with the C++ extension.  If this issue still reproduces, please enter an issue at https://github.com/Microsoft/vscppsamples/issues


Demo of what it would look like for public surface

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core


Bootloop

It gets stuck on the Xiaomi logo after installing the module.
Xiaomi Pad 6
Hyper OS 1.0.4
Android 14
Alpha Magisk (Fork)

Probably HyperOS is not supported. Report this issue to Mods-Center.


Add categories feature for the blogs.

Feature request

Allow the author of the blogs to choose a category (from a dropdown menu of categories) when he is creating a blog post. This will be stored in the DB so some alteration to the schema will be required.
Allow user to search via categories by giving a dropdown menu of categories on the home page.

@Pranav016 please assign this to me

@Pranav016 Please assign this to me

Categories can be seen in #225

@Pranav016 I'll add this feature also once I'm done with frontend using ReactJS

@Pranav016 I'll add this feature also once I'm done with frontend using ReactJS

You can work on this after the other one gets merged. Also if you are done with that, you can make a PR, reviewing takes time.

@Pranav016 yeah sure sure... Im working on all the features and ill try hosting it so that you can have a look at it before merging and sugfest any changes(UI, functioning and a bit of animations) ... Once its meged then we can go ahead with the additional features that are mentioned in issues list

can you please assign this to me?

can you please assign this to me?

You want to work under GSSoC ?

Shall I work on this under GSSoc 2021? I will use EJS templating engine.

/level3/

@A7abhilash  are you still working on this issue?

@A7abhilash are you still working on this issue?

I have already implemented this feature while I was revamping frontend with react... But unfortunately in production, frontend is not able to get the authenticated token back from backend... IDK why so, I am just wandering around that bug....


Support rename of a function’s name started from a parameter or argument label

When starting rename from a function parameter’s label, we should be performing a rename of the function signature. To do that, we need to do some adjustments of th rename positions in order to get the position of the function’s base name and use that for the rename requests sent to sourcekitd.
rdar://119875277

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

@swift-ci Please test Windows

@swift-ci Please test Windows


Adding page number to the pdf

Is your feature request related to a problem? Please describe.
Well this is the great product but with this I got some greedy and I want to have some page number marking at the end of the page or in the header or the footer of the page!
Describe the solution you'd like
Well I came across some python code which you could use which I had developed in the previous project along with that I would suggest a package name "pdfrw", you can install it with pip and then It could solve major of the problem.
Describe alternatives you've considered
The code I am attaching along with idea to use pdfrw

Along with that adding that code with Zip file too
pg_no.zip
Additional context
Add any other context or screenshots about the feature request here.

I'm not sure if I get what you're trying to suggest but currently we can write page numbers like this

Ok so reading the code I guess you mean adding page numbers to PDF? That will be a little out of context to what this tool is trying to do.
Usually, when you write an assignment, click a picture, and generate PDF, it will generate a PDF without page number only.
For such edge cases, you can download as an image and generate PDF in any other PDF generator that adds the page numbers.
Let me know if there's something I've misunderstood and I will reopen it.


Add MaskedDeck

This PR:

Defines AbstractDeck and makes Deck a subtype of it
Defines MaskedDeck <: AbstractDeck, which has several type-stable and non-allocating functionalities. For example, pop! does not actually remove elements, but rather tracks how many cards have been popped out of the deck.

bors r+

bors r+


Handlers under roles mistakenly treated as tasks

Issue Type

Bug report

Ansible and Ansible Lint details
ansible <IP_ADDRESS>
ansible-lint 3.4.8

Ansible via Arch Linux, ansible-lint via pip.
Desired Behaviour
Lint should be runnable against roles. In particular, handlers should be
checked like handlers.
Actual Behaviour
If I include a role in a playbook and then run ansible-lint against that playbook, ansible-lint
sees the role's handlers as tasks. As a specific and minimal example, here's a playbook in
main.yml:
- name: foo
  roles:
    - { role: bar }

and here is bar/handlers/main.yml:
---
- name: do anything
  shell: echo merp | cat
  when:
    - something.changed

... then ansible-lint complains like so:
$ ansible-lint main.yml
[ANSIBLE0016] Tasks that run when changed should likely be handlers
/home/vegai/ansible-role-handler-problem/bar/handlers/main.yml:2
Task/Handler: do anything

... and if look at ANSIBLE0016, https://github.com/willthames/ansible-lint/blob/master/lib/ansiblelint/rules/UseHandlerRatherThanWhenChangedRule.py this should only be run for tasks, and handlers/main.yml is clearly a handler.

I forked a branch and fixed this, but the unit test is a bit wonky. https://github.com/vegai/ansible-lint/tree/do-not-run-matchtasks-for-handlers
For some reason, the unit test I added succeeded before this change.

https://github.com/willthames/ansible-lint/pull/253


Webpack upgrade

Fixes
Opening as a draft as I still need to do some deeper testing to ensure there are no quirks. But the basic funcitonality works as expected.
I'd expect any issues to surface at build time as opposed to runtime. But just being a user, I'm not familiar with all the nooks and crannies, so any extra eyes for any potential oddities would be good.
Upgrade webpack and related changes as an incremental step toward implementing typescript, as mentioned here https://github.com/OdyseeTeam/odysee-frontend/issues/1178.
Rolls in https://github.com/OdyseeTeam/odysee-frontend/pull/1901
Other information
Webpack and related updates were made.  Not all of the packages could be brought to current.  Specifically, postcss and cssnano. postcss-rtl is no longer maintained and will not function with the latest major version of postcss.
PR Checklist

Toggle...
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[x] Refactoring (no functional changes)
[ ] Documentation changes
[x] Other - Please describe: build upgrade

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[TODO] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

I've been poking at this over the past couple days, and everything I've seen is working.  Let me know if any of you run into any issues.

Might want to hold off changes to see what Tom thinks -- is the timing right?

Of course. No rush from my end. Take it at your leisure or even use this as a baseline reference down the line if this is something that needs to be done much later.

Of course. No rush from my end. Take it at your leisure or even use this as a baseline reference down the line if this is something that needs to be done much later.

Cool.  I think this is good for the path to typescript, though.  Let's wait for his feedback on timing and testing bandwidth.

The changes regarding the images have been implemented. There is still one hanging issue with NODE_ENV being lost that I still need to resolve. My first guess is that it has something to do with some interaction between the webpack v4 and cross-env, but I'll get that worked out in my next pass (side note/FYI: cross-env is now in maintenance mode).

Inadvertently closed the PR. Reopened.

I wouldn't mind getting this in, but could use some testing on one of our test instances. Let's get it building first?
failing on Travis: https://github.com/OdyseeTeam/odysee-frontend/runs/7623226763?check_suite_focus=true
thanks for the effort @david0178418 !

@tzarebczan Anytime!
Yeah, in the next batch of free time I have, I'll figure out why NODE_ENV isn't propagating in the CI environment. I'd previously set it in the script, but had forgotten that this was the same script ultimately used for dev as well.  I'm guessing it has something to do with some interaction between webpack and cross-env.
Also, it might require some trial and error commits since I can't seem to reproduce the issue locally.  My apologies to you and the team if it spams you all with borked build messages while I feel that out.

@tzarebczan if you give me a heads-up before you plan on putting this on a testing environment, I can do another package update and rebase against master to make it as updated as possible before testing.

I can put it up today, so let me know when it's ready!

@tzarebczan Ok, you should be good to go now.

Got this during build: warning " ><EMAIL_ADDRESS>has incorrect peer dependency "webpack@^1 || ^2 || ^3 || ^4". [webpack-cli] Error: Unknown option '--display' [webpack-cli] Run 'webpack --help' to see available commands and options error Command failed with exit code 2.

That's coming from our build script - maybe just remove? not supported anymore?

Thanks. I'll see about taking a look at it later this evening.

I shipped it on stashu.odysee.com without that. Seems to work properly, no other warnings. We'll give it a whirl over next few days to make sure nothing major creeps up.

Sounds like a plan. Thanks guys.

So far things are looking good on the test site. Any things you can think of that would be problematic or to look out for, or basically since it builds, runs, should be fairly safe?

Yeah, basically that.  Since it's at the build level, failures should be catastrophic and up front.
The main things that I'd look to potentially break would be things like async imported, broken asset references and such. Most of the core functionality seems to touch on these, and they seem to be working as expected.
Aside from any other concerns others may have, the only other thing I'd want to double check on is that workflow yml change.  I see that there's some potential discussion to be had around this since you created a ticket, so I want to be sure that this tweak is good to go for the time being.

@keikari noticed this weird checkbox thing,

Odd.  Good catch.
I took a brief look at the selectors, and I'm seeing this in prod:

vs this in the new build:

It might be a couple of days before I can get to it, but I'll dig into it and see what's resulting in the difference.

It works fine on development build, so I'm thinking the production optimizer or new post-css thing yanked out the needed duplicate line.
But not sure why we needed to re-define the left color for it to work correctly in the first place.

@infinite-persistence Thanks for pointing that out.  Yeah, running the production build locally reproduces it, so this gives me a target to see what's up.
Btw, quick question. Does Odysee currently support right-to-left languages? I'm only asking because postcss-rtl is no longer maintained and is not compatible with the latest version of postcss. Not looking to try and entangle a change on that front with this change, but also a good time to trim any libraries that might happen to be unused and within arms reach.

Yup, we do support those languages.  There is also an open bug for it (just fyi)
https://github.com/OdyseeTeam/odysee-frontend/issues/1229

Just addressed the checkbox issue.  Also, the branch has been freshly rebased against master.  So worth poking at it again.

Thank you! rebuilding on stashu now...

@infinite-persistence , I saw some sentry related changes that conflicted here and got things resolved on this side. All looks good here, but might want to double check to make sure it looks right to you as well.

Thanks for the merge and heads-up.  Tried a full build with sentry auth tokens and all -- seems to be working fine.

On an unrelated note (just thinking out loud):

Seems like the vendor* stuff have been replaced with simple hashes

   -->

But dev:web-server produces them, with weird "node_modules" prefix.  Would be nice if dev/prod differences can be minimized, but probably not a big deal

In dev:web, I wonder where's the generated output now ... used to be in dist like production build, so we can have quick peeks.  All in-memory now?

Sorry for making you rebase/etc. I can try to ship this on Monday if it's all clean.

@tzarebczan No worries at all.  Considering how low level it is, it's a given that this should be gone over with a fine-tooth comb. And as I mentioned to @infinite-persistence in a previous comment, it would have been totally cool for you guys to decline this PR and just use it as a reference for later work. Whatever works for your timeline works for me.

@tzarebczan just wanted to double check here to make sure there are no other todos you'd like on this one.

All good from our end, just wanted to get the creator memberships stuff shipped this week before giving this a final whirl + prod deployment. I can take care of the conflicts then.

Is OpenSSL is now updated on this update? I think there's a critical bug on their system.
https://odysee.com/@AlphaNerd:8/millions-of-devices-are-vulnerable-to-a:4

Thanks again for all the hard work here @david0178418 , we finally were able to get it shipped out.

Glad to see that this was able to help! Thanks @toshokanneko for getting it back up to speed with more recent code.

Glad to see that this was able to help! Thanks @toshokanneko for getting it back up to speed with more recent code.

Thank YOU @david0178418 ! Glad someone already did most of the work xD

congrats for your PR work! 🥳


Error in direction consistency similarity ?

Hello,
Seems there might be an error in the formulation of your clip direction consistency similarity, according to #28 ?
It is written down as (C(e_i) - C(o_i)) * (C(e_i+1) - C(e_i))
Did you mean to write
(C(o_i+1)) - C(o_i)) * (C(e_i+1) - C(e_i))
or maybe
(C(e_i)) - C(o_i)) * (C(e_i+1) - C(o_i+1))
?
In the previous issue you said it is the first one, but I don't know if that is actually correct? I would really appreciate if you could confirm which one of the two is it.
Thanks!

I have the same question regarding the clip direction consistency similarity.

You just have to change the inputs to the function when you call it. So if you are doing the directional score, input consecutive frames, and if you are doing similarity score, input the two frames from the separate videos

Originally posted by @ayaanzhaque in https://github.com/ayaanzhaque/instruct-nerf2nerf/issues/82#issuecomment-1852544207
From this response, the similarity score would be
(C(e_i)) - C(o_i)) * (CT(e_i)) - CT(o_i))
Which is also different


Close POAMs related to Nessus/Zap false positives

Too much time/energy goes into tracking down known false positives, to the detriment of tracking new findings (like SameSite)
Security considerations
Masking real findings as false positives is a real concern. Needs careful vetting, or working with upstream to fix issues.
Implementation sketch
POAMS:
2020-V0043-RA-5

This is not as time sensitive, so it could be closed if it's noise on our board


Tooltip TypeError with web.animations.js

#### Bug:
Material Tooltip with web.animations.js, do not work properly if we trigger a tooltip more than two consecutive times in a short time is thrown this error (only Safari):
'TypeError: e [0] .push is not a function. (In 'and [0] .push (1)', 'and [0] .push' is undefined)  --- web-animations.min.js:16:6248
What is the expected behavior?
No error
What is the current behavior?
This error on mouse enter more times in small piece of time:

'TypeError: e [0] .push is not a function. (In 'and [0] .push (1)', 'and [0] .push' is undefined) '
What are the steps to reproduce?
Plunker template: http://plnkr.co/edit/GqVcNkh0GRxCYUmcj7fv?p=preview
What is the use-case or motivation for changing an existing behavior?
I'm using 2 Material for a big project and I find difficulty with this bug.
Which versions of Angular, Material, OS, browsers are affected?
MAC OSX,material2-builds, and latest, web.animations 2.2.2. Safari on Sierra, not Chrome.
Is there anything else we should know?

This is a duplicate of #3694

Maybe also a duplicate of https://github.com/angular/material2/issues/3384

vHi,I believe is a duplicate of this, can you excuse me, please?
Bye

Il giorno 31 mar 2017, alle ore 08:30, karlhaas<EMAIL_ADDRESS>ha scritto:
Maybe also a duplicate of #3384 https://github.com/angular/material2/issues/3384
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/angular/material2/issues/3846#issuecomment-290628614, or mute the thread https://github.com/notifications/unsubscribe-auth/ATgUNTwahNYcePRyVIBWuwIcPNxDpWYIks5rrJ1sgaJpZM4Muda9.

Seems to be working fine in the latest version.
Be sure to check out the changelog for the latest release in regards to changes w/ animations.

@jelbourn still the same error with material v. 2.0.0-beta.3 in Safari

Same error 2.0.0-beta.5 in Safari

updating "web-animations-js": "2.2.5" should fix


check-a-record fails to parse a host that contains 'http://' or a path

Given the url http://httpstat.us, I expected this to resolve, but instead it failed:
check-a-record http://httpstat.us
No A records found (lookup http://httpstat.us: invalid domain name)

This also throws a similar error:
check-a-record http://httpstat.us/502
No A records found (lookup http://httpstat.us/502: invalid domain name)

I would expect this to parse the base domain and check that.

cc @jaresty

Please see https://github.com/cloudfoundry-incubator/check-a-record/commit/4226f68599dc66aa6f3f7d9d7ef68afec90c35c1


Confusing tokenization behaviour for incomplete orthography profiles

I'm somewhat confused by the way the missing, _missing and exception keyword arguments of Tokenizer.transform are supposed to work. Locally, I fixed a bug where a callable was passed to _search_graphemes as _missing, but now graphemes missing in the profile are just silently tokenized by default - which I think is wrong. If a profile exists, missing tokens should raise an exception by default, right?

@LinguList I think this behaviour was introduced in your PR https://github.com/bambooforest/segments/commit/ab017b3dee4d20abe35f1d2e0271925faa1893e6
Any ideas?

I think a couple of tests would go a long way towards explaining the intent of the functionality.

me culpa. The behaviour before was: just don't tokenize things if there are unknown things. This is unwanted behaviour, becuase it's extremely difficult to debug. So I introduced a customizable character that would replace missing characters, e.g., a question mark.
Now, I think I messed things up in terms of expliciteness, since -- soooryyy -- I wanted to have a working solution that I could use to create my orthoprofiles.
Looking at it right now, I think one could replace the _missing by "missing", but I think what I ALSO wanted to have as a specific behaviour is what is also criticizable, the possibility to mark the missing graphemes in some user-defined way, like "", for a missing "m". So I intruduced and ugly lambda function in "transform".

I'll have a closer look in the afternoon / after department meeting. To summarize the wanted behavior for the moment:

we need to track characters that don't work, but we need to be flexible here, marking them in a user-defined way
we need to allow to pass the wanted behavior as a formatting rule, like, e.g., , since due to different datasets, no fixed behavior will guarantee that it gets ambiguous at some point

Is that understandable so far? For me, in practice, it helped a lot, and otherwise, I woul've hat huge problems in creating any of teh orthoprofiles I created, as this can be very tedious and time consuming.

Ok. I see the usefulness of this behaviour; just wanted to double-check that the default shouldn't be silently making up invalid tokens. So perhaps missing should always be a callable, defaulting to raising an exception?

Yep, I guess, that is useful.

@LinguList If you could turn your description of the desired behaviour into a couple of tests, that would also be a good way to document it.

allright, will do so!

in the book, page 86, we state in the formal orthography specification:
B9. Leftover characters, i.e. characters that are not matched by the profile, should be reported to the user as errors. Typically, the un- matched character are replaced in the tokenization by a user-specified symbol-string.
honestly, i don't remember what the default behavior of segments was before, but let's let the user specify the symbol moving forward, with default being i guess "?" (because i think it's useful and standard to reserve "#" for word boundaries)

Yes, it was a question mark, I remember, but here is my problem: if it is always a question mark, we may confuse a real question mark with an error-questionmark. Furthermore, we would like to see what went wrong, that is, what character was not captured, and for this reason, I introduced that crappy implementation of the new behaviour that would model something like:
t_hOxt@

both as
t_h O x t <@>

in the graphemes, but also as:
tʰ ɔ x t <@>

in the transformed form. Here, we conveniently see that the word was nicely converted, but that my sampa-profile lacks a specification for "@". Given that the marking of errors can easily be ambiguous, since there may be datasets that HAVE <> for other purposes, we further need to allow the user to change the default marking (for the moment, <> works fine, but normal brackets would be problematic, but something like "?:@" would work as well, etc.).
You see the point? Despite the ugly code, in practice, this greatly facilitated the production of the profiles I wrote so far, as I could immediately see what I had been missing.

I just looked up how python handles encoding/decoding errors. It seems as if this scheme could also handle all of our use cases, and would be the easiest in terms of documentation.
So Tokenizer.__call__ would gain a keyword argument errors which accepts a string, specifying the desired behaviour, defaulting to 'replace'. Following the python practice of using U+FFFD REPLACEMENT CHARACTER to signal replacement also seems a good idea, I think. In any case we can also copy the error handler registration mechanism, to allow even more control (but replacing U+FFFD REPLACEMENT CHARACTER with some custom character after tokenization doesn't seem too much effort either).

@LinguList you <...> replacement scheme could be implemented by registering a custom error handler for replacement mode, e.g.:
t = Tokenizer()
t.register_error('replace', lambda c: '<{0}>'.format(c))
t('t_hOxt@')

excellent. As long as we can have this behavior, all is fine with me.

@LinguList @bambooforest  I'll put together a PR for you to review.

super, thanks in advance, and sorry for the bad code I submitted in 2016: I was under pressure and needed the things to run, but I'll try to improve with these things and (try to) communicate desired behavior discussions before coding them in the future.

https://www.youtube.com/watch?v=8jQlubar9A8

sounds like an excellent solution @xrotwang -- the replacement character even contains a question mark, haha.
http://www.fileformat.info/info/unicode/char/fffd/index.htm
and has some decent Font coverage
http://www.fileformat.info/info/unicode/char/fffd/fontsupport.htm

Just came across one complication: When implementing a test for @LinguList's <...> replacement scheme, I happened to use a character which isn't in test.prf, but is in test.rules, so to my confusion, I got
>>> t('habe')
... '<i> a b <e>'

One could argue that rules shouldn't be applied to results of the replacement error handler. But this would require some knowledge of the implementation of this handler. But since the use case for custom replacement handlers seems to be solely the initial creation of orthography profiles, I'd guess there won't be any rules defined by then. So I'd say custom error handlers and their effects are the sole responsibility of the calling code, not of the tokenizer.

In general, when working on my SEA language orthoprofiles, I tried to avoid rules as long as possible, preferring to customize output by spelling out whole words, which are exceptions, rather than providing a small rule. This increases redundancy, but it is easier to control, since rules are also following specific ordering, while redundant full-word segmentation for erroneous transcriptions does not require any order, as the algorithm starts with the longest chunk anyway. I have made good experience in practice on that, and I'd say that this should be a recommendation for all orthoprofiles: try to avoid the usage of rules.


Vitis support for Tensorflow 2 Separable Convolution layers

Hello,
My team is interested in deploying an EfficientDet model on a ZCU102 board. We are using the AutoML repository to train our EfficientDet TF2 model. We are using Vitis-AI to quantize and compile the model for deployment to the board.
We have ran into several issues with getting the AutoML code to quantize. While most have been solved with workarounds, like turning the subclass keras model into a functional keras model, we have ran into the blocker that Vitis-AI does not support Separable Convolution layers for TF2. We would like to get these layers on the DPU and don't want to revert back to using regular convolution layers as this would make the model too large and slow for our needs.
Is there plan to support Separable Convolution layers in TF2 in the near future?

@renjiangyong thank you! Is the patch just simply a different branch?

We had fixed this issue in the latest Vitis-3.0, please use the latest docker to test, thank you.


Corrected filename for factions datafile

The new factions datafile had the incorrect filename in the manifest.json.

Thanks!


Activation of MFA OnPrem Server IP Requirements

Required IP address for MFA Activate On-prem server is different than listed IP subnet.
What is the exact IP address list for communication of on-prem and azure for existing licence.

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

ID: 6dd28f91-2039-4f0d-7c38-4775f8767bf0
Version Independent ID: c7a81541-2675-0860-be8b-3a44c1b74918
Content: Getting started Azure MFA Server - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfaserver-deploy.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@msozgen Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfaserver-deploy

@msozgen Thanks for the link. We are currently investigating and will update you shortly.

@msozgen Coudl you please provide the IP addresses that you are getting on your side. We tried this and found that it confirms with the details provided in the article ? Ifyou have obtained any other IP  please let us know and we will have this investigated

@msozgen Coudl you please provide the IP addresses that you are getting on your side. We tried this and found that it confirms with the details provided in the article ? Ifyou have obtained any other IP please let us know and we will have this investigated

Hello @shashishailaj,  OnPrem MFA servers does not get online state when we open range given in the link. (which is below)
<IP_ADDRESS>/25 | <IP_ADDRESS> | <IP_ADDRESS> – <IP_ADDRESS>
<IP_ADDRESS>/25 | <IP_ADDRESS> | <IP_ADDRESS> – <IP_ADDRESS>
<IP_ADDRESS>/25 | <IP_ADDRESS> | <IP_ADDRESS> – <IP_ADDRESS>
When we open FW ports with Any to the internet, MFA servers gets in online state, than we see some IP addresses start with 20 and 40-43. Than we tried to solve record those IP addresses and  we see that it is belongs to the Akamai.

@msozgen Thank you for the information , I have requested clarification on this from the product group . If they provide any new information , we will have the article updated. In case they would need more data I will let you know the engagement procedure.
Thank you.

@msozgen We checked this internally and found that the IP address list mentioned is correct. Could you please provide the details of the IPs of range starting from 20 and 40-43 which you had obtained on your firewalls which activation request was going through. As per the PG , whenever you try to activate the MFA server , the request goes to css.phonefactor.net and the IP range  provided in the article is inclusive of those IPs . I would suggest to send us the IP range details that you had found and if possible exact IP addresses from firewall logs. and send us an email on azcommunity[at]microsoft[dot]com .  We will now close this issue however we will take this offline and provide you with alternate support options. Please do send us the requested data and we will continue this offline.
Thank you.


Redirect not working in react-router-dom v6

Hi,
I updated react-router-dom from v5 to v6 and update connected-react-router to v6.9.3 but I found out redirects not working.
import {routerActions} from 'connected-react-router';
dispatch(routerActions.push(url))

Url was changed but page not changed.
My react version is 18.2.
Have somebody similar problem?

https://github.com/supasate/connected-react-router/issues/397
https://github.com/supasate/connected-react-router/issues/590
https://github.com/supasate/connected-react-router/issues/543


Consider replacing runtime-generated cleanups with static ones

component(
  async function () { console.log(”running”, this) },
  async function (isFinal) { console.log(isFinal ? ”destroying” : ”rerunning”, this) }
);

less heap allocation
less memory usage
smaller chance of accidental memory leaks

Most cleanups just use this to delete something from somewhere. Easily taken care of with this new API. But need to look into other use-cases as well.

Still going to add something like this

[ ] setTemporaryStore(this, [something, needed, for, cleanup])
[ ] const [something, needed, for, cleanup] = getTemporaryStore(this)

Actually, maybe it would be better to keep the old system, but call the cleanups with this. Enables both React-style closure cleanups and shared cleanups.


Selection of layers that depend on other layers

Using https://raw.githack.com/walkermatt/ol-layerswitcher/master/examples/select-groups.html as example, given the structure of:

Census

Wards
Districts

Could it be possible to make it such that it becomes something like:

Wards

Districts

so that checking off wards will show wards, and that districts can be toggled on or off regardless of wards, but toggling wards off will also disable districts?
If that isn't possible, then can there be an option to hide just one layer such that a similar effect can be recreated:

Wards

Wards (but hidden from the panel)
Districts

Would it also be possible to set whether or not layers are checked off or not upon creation of the layer switcher? (Not wanting all layers on by default)

Hi,
The initial visible state of the layers can be set for individual layers either by specifying a visible option or by calling setVisible on a layer instance.

Okay, that works for initially setting a layer to be not visible.
Is there a solution for the first issue that I described about a layer's visibility being dependent on another layer?

I don't think you need anything LayerSwitcher specific to solve your first requirement. You can hide the dependent layer from the LayerSwitcher by not giving it a title property and toggle it's visibility within a change:visible listener on the other layer.

That worked out, makes sense.
Thank you.


Update expressroute-routing.md

Please evaluate small addition in text.

@BertWolters : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@charwen, can you review this one too? Same Microsoft Teams as the other PR.

#sign-off

@charwen: I'm sorry - only the author of this article, @cherylmc, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


Active filters block should not show search suggestions

ref. culturefeed_search_ui_search_active_filters_block()
The 'active filters' block not only outputs active filters, but also search suggestions. It should not do that, they are not related to eachother. The search suggestions should be split off to a separate block.

This issue is from August 2013. Is this still relevant?


[reliable payments] router payment state machine

This PR introduces a persistent state machine to the ChannelRouter's payment flow, ensuring we can handle payment results that are received after a restart. It also paves they way for adding cancellation of payments, and resuming payment sessions across restarts.
Problem
lnd currently runs into problems if it is restarted while an HTLC is in flight on the network. The primary reason for this is the way the router hands the HTLC to the switch.  The router persist no information about the payment, so when a result eventually comes back, we risk the information needed to properly populate the OutgoingPayment in the database is lost.
Solution
With the paymentStateMachine introduced in this PR, we store two pieces of key information:

The HTLC paymentID. This is used to query the Switch whether the HTLC is still active. If not active we know that we can safely retry the payment attempt. If active the router will wait for the result to be available, and store the result to the DB.
The HTLC's route.  This is added to the DB  together with the preimage when the payment succeeds.

Note
The Switch does not currently persist the pending payment attempts across restarts. This will be added in a follow-up PR.
Replaces #2475
Builds on

[x] #3065
[x] #3064
[x] #3063

Comments addressed and unit tests added for new ControlTower and router state machine behavior.
PTAL @joostjager @Roasbeef @cfromknecht

Splitting the move of Route to a separate merge would be useful for overview in this one.

Can be rebased now that one of the dependent PRS has been merged.

PTAL @joostjager @Roasbeef

PTAL @cfromknecht

Moved first parts of this PR into Builds #3065, #3064 and #3063

Consider fixing redundant serialization: https://github.com/lightningnetwork/lnd/pull/3064#discussion_r283911175

Comments addressed. PTAL @joostjager @Roasbeef @cfromknecht

Got an error on a node when trying to update to this PR (failed migration):
2019-05-21 20:25:10.990 [INF] CHDB: Applying migration #9
2019-05-21 20:25:10.993 [INF] CHDB: Migrating outgoing payments to new bucket structure
2019-05-21 20:25:10.995 [INF] CHDB: Unable to apply migration #9
2019-05-21 20:25:11.007 [ERR] LTND: unable to open channeldb: bucket already exists

Got an error on a node when trying to update to this PR (failed migration):
2019-05-21 20:25:10.990 [INF] CHDB: Applying migration #9
2019-05-21 20:25:10.993 [INF] CHDB: Migrating outgoing payments to new bucket structure
2019-05-21 20:25:10.995 [INF] CHDB: Unable to apply migration #9
2019-05-21 20:25:11.007 [ERR] LTND: unable to open channeldb: bucket already exists

I think this means that the node has more than one payment to a payment hash: https://github.com/lightningnetwork/lnd/pull/2761/commits/a38c07b0cfee398468b3b4f51b6c9b44ed2b46de#diff-99f3013528876f55a0e46ff7014e8a19R741
Definitely something that needs to be addressed, since I guess this can be common for old nodes...

Confirmed that the latest version allows my existing nodes with duplicate payment hashes to upgrade!

Comments address, and migration+test altered to allow migrating from duplicate payments. PTAL @joostjager @Roasbeef @cfromknecht


fix: do not always set classification to false

hi @sgbaird  👋🏽
Thanks for packaging this up. I think this fix here is needed (perhaps one should also add a simple test that overfits to check that it does what it is supposed to do).
Cheers,
Kevin

Oh wow, great catch! Yeah, that definitely looks like the right fix. I haven't dealt too much with classification and CrabNet, and adding a unit test seems to be in order here. I'll go ahead and merge the request for now.


"Export after every entry" not working as expected

App version
1.7.3
Bug Description
If I enable "Export after every entry", the exact same date range is exported each time, rather than (as expected) e.g. the last seven days.
Steps to Reproduce

Go to Settings
Export / Import
Choose a date range, e.g. 7 days
Export after every entry: Enable
Export format: PDF (not sure if important, but that's what I'm using)
Take some readings over several days
Look at PDFs generated

Observed result:
Other than the filename, the PDFs are identical, all showing data from e.g. 1 Aug to 7 Aug.
Expected result:
The first PDF to have data from 1 Aug to 7 Aug, the second PDF to have data from 2 Aug to 8 Aug, etc.
Details (Screenshots, Debug Info, Configurations)
Attachments

Thanks! The fix will land in 1.8.1.


Support returning an array of styles to be merged from props callbacks

Problem description:
Sometimes I want to do this:
glamorous.div(({big, square}) => {
  const bigStyles = big ? {
    [desktopMediaQuery]: {
      fontSize: 20
    }
  } : {}

  const squareStyles = !square ? {
    [desktopMediaQuery]: {
      borderRadius: '50%',
    }
  } : {}

  return {...bigStyles, ...squareStyles}
})

But that wont work because Object.assign (or object spread in this case) is shallow, so the last desktopMediaQuery object will entirely override the first one. So I have to workaround this limitation myself with more imperative, less expressive code.
Suggested solution:
I think it'd be cool to be able to do this:
  glamorous.div(({big, square}) => {
    const bigStyles = big ? {
      [desktopMediaQuery]: {
        fontSize: 20
      }
    } : {}

    const squareStyles = !square ? {
      [desktopMediaQuery]: {
        borderRadius: '50%',
      }
    } : {}
-   return {...bigStyles, ...squareStyles}
+   return [bigStyles, squareStyles]
  })

And have glamorous forward both of those items to glamor and have glamor merge them as it does everything else so nicely for us.
I'm going to start working on this now... Because I want it now :)

Oh snap... This already works. ❤  glamor! My PR will be to add a test and docs for this then!

I just want to thank @threepointone for being so awesome :clap:

Cool! Luckily very easy to change the Typescript typings to support it. I'll a make PR with the typings change and little typescript test 😉.

🤗


Please make Vector3 overloads for GetNearbyVehicles and GetNearbyPeds

I need overloads for these two methods which take a Vector3 position as origin but not a ped.

There is no native which can do that. Would be nice if there was.

#101 is a hackish solution to that problem, as i said in that thread.

Not sure if this is too "hackish" of a solution to use, maybe we should wait for a better native function? Also, i agree with @crosire on the state of the commit history :-P

Ugh that looks ugly. Thanks for the response though. :)
I don't know how much different the game engine of V is compared to IV and I'm no C++ guy but have you looked at the source of HazardX's .net script hook for GTA IV? Maybe you find something helpful.

I think some functions of Hazard's scripthook are made possible by reading memory, as far as i remember.

http://hazardx.com/files/sourcecode_of_the_gta4_net_scripthook-92

Maybe implemented by #101, not sure yet

That's not really a good solution. It would need some testing if GTAV stores peds and vehicles as continous lists in memory like GTAIV did, in which case one could fetch data from there.

I will close this as a duplicate of #13


Add version() function

To check Presto version one currently has to:
SELECT node_version FROM system.runtime.nodes LIMIT 1

Let's provide a more convenient form:
SELECT version();

Based on the conversation in #4629 , I am removing syntax-needs-review.


Changes to code to make sure that the server.js file runs without error

Changes to code to make sure that the server.js file runs without error

Note this PR includes the changes hanging in PR#: https://github.com/c-phelps/workout-wizardz/pull/54
If that PR is rejected, this PR will be rejected and adjusted.


Calling feature test through C++ Alexa SampleApp

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
Using Alexa SampleApp i tried testing calling number. I received audio that "calling with alexa is not supported on this device". I am using Linux ubuntu 16.04 version to compile the code. Do i need to change something in my code. During compilation of alexa auto sdk, avs sdk is downloaded and compiled. Separately i checked in avs sdk, i found that in PCC.make, Phone call feature is OFF. Do i need to make some changes in auto sdk or in cmake file of auto sdk, enabling the PCC feature for AVS sdk ?
What is the expected behavior?
 It should say if number is not found that " number is not found".This kind of reply i should receive.
What behavior are you observing?
calling with alexa is not supported on this device.
Provide the steps to reproduce the issue, if applicable:

run the c++ sampleapp.
press T, and say "Alexa call faisal"

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <x.y.z>1.17

Tell us what hardware you're using:

[ ] Desktop/Laptop Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux Ubuntu 16.04
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @syedfaisal5
Calling support in the SDK requires an sdk adapter package. Please reach out to your Amazon business contact in order to get more information.
Thanks!

Hi @syedfaisal5
Calling support in the SDK requires an sdk adapter package. Please reach out to your Amazon business contact in order to get more information.
Thanks!
Is this for SampleApp default phonecall feature testing also ? I am trying to check default phone call feature with given contact.json file, but still it is saying : " calling with alexa is not supported on this device". Does something need to enable or make changes in auto sdk.


Limit to Snippet Variables?

Is there a limit to how many variables can be in a single snippet, and if so, what is that limit? I tried to create a boilerplate snippet that had 9 variables, and it only worked for the first 6 of them. But I'm not sure if that was simply due to a mistype or not...

Hi @shadowlightwolf89, can you please move this over to atom/snippets and then share the snippet in question?  Thanks.

This issue was moved to atom/snippets#158


fix very low accuracy metric

The accuracy of multilabel task is ~0.002 no matter how tuned the parameters, comparing to the ~0.91 on the benchmark. The reason for the low accuracy is that input of sklearn_metrics.accuracy_score is not flattened. Given a 200 classes prediction, the accuracy counts right when the 200 is exactly matched the ground truth. If we flatten the predictions and targets before calling sklearn_metrics.accuracy_score, then the accuracy is about the same as the benchmark.
Also, I have added some logging enhancement in this PR.

Looks good to me. Thanks for the PR!


Installing from a local ISO does not seem to work

Hi,
So, since the container was unable to download the Windows 7 iso from the download site, I decided I would instead use a local Windows 7 image.
So, here is what I did, as per the instructions:

I downloaded the iso image into the local bind of the /storage folder, as defined under the docker-compose instruction volumes:
I renamed the image custom.iso

When I execute the docker-compose.yml file:

at first, it finds the image and analyzes it
but then it fails on QEMU not finding any image in the iso.

I tried by downloading your Windows 7 iso image (the one that the container was previously unable to access). I succeeded in downloading it, renamed it as above, but I got the same error.
What am I doing wrong?
S.

@asitemade4u mine is working fine. I tested using locally tiny windows 10 iso. The difference in my opinion is this line:
volumes:
  - /home/user/example.iso:/custom.iso

You've to map the local iso file with the storage iso inside of container. In my case I did this:
version: "3"

services:
  windows:
    image: dockurr/windows:latest
    container_name: tiny-win10
    restart: on-failure
    devices:
      - /dev/kvm
    cap_add:
      - NET_ADMIN
    ports:
      - "8006:8006"
      - "3389:3389/tcp"
      - "3389:3389/udp"
    stop_grace_period: 2m
    environment:
      VERSION: "win10"
      RAM_SIZE: "8G"
      CPU_CORES: "4"
      DISK_SIZE: "64G"
    volumes:
      - /mnt/win/dockur-windows/tiny-windows10.iso:/custom.iso  **# Map the local iso inside of the container**

and here are the logs:
/mnt/win/dockur-windows ❯ docker compose up                                                                                took 1m35s
WARN[0000] /mnt/win/dockur-windows/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 1/0
 ✔ Container windows_container  Recreated                                                                                0.1s
Attaching to windows_container
windows_container  | ❯ Starting Windows for Docker v4.07...
windows_container  | ❯ For support visit https://github.com/dockur/windows
windows_container  | ❯ CPU: Intel Core i5 8350U | RAM: 9/16 GB | DISK: 96 GB (fuseblk) | KERNEL: 6.12.4-arch1-1...
windows_container  |
windows_container  | ❯ Extracting local ISO image...
windows_container  | ❯ Detecting version from ISO image...
windows_container  | ❯ Detected: Windows 10 LTSC
windows_container  | ❯ Adding drivers to image...
windows_container  | ❯ Adding win10x64-ltsc.xml for automatic installation...
windows_container  | ❯ Building Windows 10 image...
windows_container  | ❯ Warning: the filesystem of /storage is FUSE, this extra layer will negatively affect performance!
windows_container  | ❯ Creating a 64G growable disk image in raw format...
windows_container  | open: Operation not permitted
windows_container  | ❯ ERROR: TUN device is missing. Please add the following setting to your container: --device /dev/net/tun
windows_container  | ❯ Warning: falling back to usermode networking! Performance will be bad and port mapping will not work.
windows_container  | ❯ Booting Windows using QEMU v9.2.0...
windows_container  |
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
windows_container  | BdsDxe: loading Boot0001 "UEFI QEMU DVD-ROM QM00013 " from PciRoot(0x0)/Pci(0x5,0x0)/Sata(0x0,0xFFFF,0x0)
windows_container  | BdsDxe: starting Boot0001 "UEFI QEMU DVD-ROM QM00013 " from PciRoot(0x0)/Pci(0x5,0x0)/Sata(0x0,0xFFFF,0x0)
windows_container  |
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
windows_container  |
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,931A70E6-6211-49B2-A236-008FB41276EC,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
windows_container  | BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,931A70E6-6211-49B2-A236-008FB41276EC,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
windows_container  |
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,931A70E6-6211-49B2-A236-008FB41276EC,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
windows_container  | BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,931A70E6-6211-49B2-A236-008FB41276EC,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi


Limit specs to rack-test < 0.7.0 for Ruby 1.8.7 compatibility

What was the end-user problem that led to this PR?
The problem was the specs were broken by the release of rack-test 0.7.0.
What was your diagnosis of the problem?
My diagnosis was rack-test has intentionally dropped 1.8.7 support, though we didn't catch that immediately because they didn't put a required_ruby_version in their gemspec.
What is your fix for the problem, implemented in this PR?
My fix pins us to older versions of the gem.

@bundlerbot r+

@bundlerbot retry


Alexa is me

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

What is the expected behavior?

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <x.y.z>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Closing this issue. @dipalisb please reopen with more information added here.


extention stopped working after recent update

Greetings,
Earlier this week I updated automatic1111 for the first time in about two months, and it seems that this extention stopped working. I removed the extention and added it again, but this didn't solve the issue. I've checked the settings and csv files, and those all seem fine.
Does anyone else have similar problems and/or know how to fix this? Thanks.

This seems to be a common problem after the big Gradio update the webui recently did, but the current version of tag autocomplete already has the necessary fixes. Similarly to #152 and #157, please make sure you use the most recent version of tag autocomplete and make sure to completely restart the webui after updating/reinstalling, the "Restart UI" button isn't enough in some cases. Also try CTRL+F5 to force a cache refresh.
If this doesn't work, or you've already tried it, the next step would be to look if any javascript errors show up in your browsers console.

Hi, thanks for the quick reply.
I never actually saw any errors. It's just that nothing happens anymore when I start typing in my prompt.
I'm not sure how to force it to download the correct version. It shows my current version of the extension as 223abf54 (Wed Apr 5 11:05:44 2023), and neither "check for updates" nor "apply and restart" change that. I manually downloaded the latest version 2.1.0 and replaced the javascript, scripts and tags folders. Afterwards I started A1111 again, but to no avail.

Are you using any other extensions? If so please try deactivating everything other than this one, just to make sure it's not a compatibility problem. Trying on another browser might be a good check to do as well.

I ran into this as well:
2023-04-12 17:17:45.402300+00:00ValueError: File cannot be fetched: /stable-diffusion-webui/extensions/a1111-sd-webui-tagcomplete/javascript/ext_loras.js. All files must contained within the Gradio python app working directory, or be a temp file created by the Gradio python app.

Is dumped out in my log for every file from the extension.

All this time I thought ppl were talking about getting errors in the command window of a1111. Turns out I was indeed getting a lot of errors in the console of the browser. Mybad!
The first image has the errors I get upon starting. Whenever I start typing in the prompt window I get several errors like the one in the second image. Does this mean that there is a different solution? I typed the lines you suggested into the console but it's telling me that tagBasePath and CFG are undefined.

Yeah it seems the script isn't loaded correctly.
In the first error it says "redeclaration", do you maybe have a duplicate version of the extension that is somehow interfering? The rest of the errors most likely come from these global variables missing as well. Also make sure that you don't have the old legacy version of the script installed (before extensions were a thing), where the files would be dropped off in the webui's root Javascript and scripts folders instead of the extensions subdirectory. Or maybe you put them there recently by mistake?

There was indeed an old version (25/10/22) in the main javascript folder. After removing that file everything works again. Thank you very much! :)


Unable to access the UDP port of the virtual machine on the macOS

Describe the bug
I have a CoreDNS service running in Docker, but can't access it in macOS!
To Reproduce
Steps to reproduce the behavior:
docker run -d -p 53:53/udp --name coredns coredns/coredns:latest

dig @<IP_ADDRESS> -p 53 github.com

; <<>> DiG 9.10.6 <<>> @<IP_ADDRESS> -p 53 github.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Expected behavior
I want to be able to access docker UDP port on macOS.
Logs
console | ERRO[04-18 10:17:59] failed to update listeners                    container=docker error="listen udp [::]:53: bind: address already in use"
time="04-18 18:28:35" level=error msg="UDP proxy conn ReadFrom() failed: read udp <IP_ADDRESS>:32939: i/o timeout"
time="04-18 18:29:04" level=error msg="UDP proxy conn ReadFrom() failed: read udp <IP_ADDRESS>:48851: i/o timeout"
time="04-18 18:29:44" level=error msg="UDP proxy conn ReadFrom() failed: read udp <IP_ADDRESS>:52516: i/o timeout"
time="04-18 18:30:35" level=error msg="UDP proxy conn ReadFrom() failed: read udp <IP_ADDRESS>:53799: i/o timeout"
time="04-18 18:30:35" level=error msg="UDP proxy conn ReadFrom() failed: read udp <IP_ADDRESS>:56715: i/o timeout"

Info report

OrbStack info:
  Version: 0.7.0 (70000)
  Commit: bd15b6e5fed45a098f5493cc8d89aa71b3081a51 (v0.7.0)

System info:
  macOS: 13.3.1 (22E261)
  CPU: arm64, 10 cores
  CPU model: Apple M1 Max

---------------- [ cut here ] ----------------

Please copy and paste the above information into your bug report.
Open an issue here: https://github.com/orbstack/orbstack/issues/new/choose

Additional context
And if I do not explicitly specify the bound IP address when I start the service, the following error log will appear:
console | ERRO[04-18 10:17:59] failed to update listeners                    container=docker error="listen udp [::]:53: bind: address already in use"

This looks like a duplicate of #181. Please update to v0.7.1 and share new logs if the issue remains.

@kdrag0n Yes it is working fine but still there is error like below in vmgr.log:
console | INFO[04-19 01:57:33] add forward                                   spec="{<IP_ADDRESS> 53 udp}"
console | WARN[04-19 01:57:33] failed to apply listener changes              notAdded="[{<IP_ADDRESS> 53 udp}]" notRemoved="[]"
console | ERRO[04-19 01:57:33] failed to update listeners                    container=docker error="listen udp <IP_ADDRESS>:53: bind: address already in use"

In addition, I want to know whether it is possible to customize the network of the virtual machine instead of accessing the port of the virtual machine through mapping. For example, I want to build a cluster through multiple virtual machines, but now I can only access the port of one virtual machine at the same time.

Reproduced, will look into this. It looks like the reply packet is being sent to the wrong IP due to a bug in some new networking code in v0.7.0.

Fixed and released in v0.7.2.


Adding movidius_ncs to documentation index for distro

I'd like movidius_ncs to be indexed and documented on ros.org

@mikaelarguedas , could you please help merge this pr?


Fix Travis CI build issues #2128

Checklist

[x] I have read the Contribution & Best practices Guide.
[x] My branch is up-to-date with the Upstream development branch.
[ ] I have added necessary documentation (if appropriate)

Short description of what this resolves:
Before this PR, the travis builds were not working as expected, thus not updating the heroku deployment on each merged PR or commit. Now it works as expected.
Changes proposed in this pull request:

Update deprecated istanbul package to nyc
Add new scripts to package.json
Install g++ before install so serverTest.js works
Temporarily disable npm test which was unncessarily causing errors

Fixes #2128

@mariobehling Please take a look at this. You can view the succeeded build logs https://travis-ci.org/fossasia/open-event-wsgen/builds/635582280.

@mariobehling @aayusharora Please review and merge. Thanks!

travis has been running for more than 13 hours now 😕

Thank you!


Clarification needed on custom theme usage with MantineProvider

Reproduction
I've created a minimal repository that demonstrates this issue: next-app-mantine-tailwind-template-issue
Steps to reproduce:

Clone the repository
Install dependencies (pnpm install)
Check the TypeScript error in src/app/layout.tsx on line 50

Description
There seems to be a disconnect between the documentation for custom theme usage and how it should be implemented with MantineProvider. The current documentation shows how to configure the Tailwind preset with a custom Mantine theme, but it's not clear how this should work with MantineProvider.
Current Behavior
Following the documentation, I created a theme configuration like this:
// theme.ts
import tailwindPresetMantine from "tailwind-preset-mantine";
import { createTheme } from "@mantine/core";

const mantineTheme = createTheme({
  // custom theme options
});

const themeConfig = {
  presets: [
    tailwindPresetMantine({
      mantineColors: mantineTheme.colors,
      mantineBreakpoints: mantineTheme.breakpoints,
    }),
  ],
};

export default themeConfig;

However, when trying to use this configuration with MantineProvider:
<MantineProvider theme={themeConfig}>{children}</MantineProvider>

I get the following TypeScript error:
Type '{ presets: Config[]; }' has no properties in common with type 'PartialObjectDeep<MantineTheme, {}>'.ts(2559)

Expected Behavior
I expect to be able to use my custom theme with MantineProvider without any type issues.
Environment

tailwind-preset-mantine version: [^1.2.1]
@mantine/core version: [^7.13.4]
Next.js version: [^15.0.1]

Hi there! It looks like there might be a little misunderstanding in how to use it.
I've made some updates to the template to include the custom theme code in this commit.
Please take a look, and let me know if you have any questions!

Thank you for clarifications. Yes, not it works as expected with no type issues.

I've also updated the docs to make it more clear for custom themes:
https://github.com/songkeys/tailwind-preset-mantine#custom-mantine-theme


Guard last edited at

As last_edited_at field is rather new from publishing-api, we will
need to do some data migration to populate that field for existing
documents. In the meantime, a nil value will cause an error at
time_ago_in_words so I'm adding a guard clause for a smoother
transition.
Branched off of #804 as we might not need this work-around if we know that the api will never return nil for last_edited_at

Closing as we'd rather have it error if that field is missing. We plan on republishing this content instead.
https://trello.com/c/ZXHlaqzq/167-republish-all-v1-content-to-populate-last-edited-at

I think it would be better to merge this actually.
I'd rather not republish all documents in Specialist Publisher yet as this puts unnecessary load on Publishing API and clutters up the event log. We'll need to do this eventually, but we can probably do this one format at a time rather than everything now.


Failing cloud formation

I am getting this error every time when I ran the SAM cloud formation template
Embedded stack arn:aws:cloudformation:us-west-2:<account_id>:stack/iotfleetprov-IoT-<id>/70920bb0-5ef5-11eb-8668-06d3cec249cb was not successfully created: The following resource(s) failed to create: [CertMonitorFunctionCheckCertExpiryEvent, FleetProvisioningHookPermission, FleetProvisioningCustom, CertRotationHookPermission].
CLI command:
aws cloudformation create-stack --region us-west-2 --stack-name iot-prov-pipeline --template-body file://pipeline.yaml --capabilities CAPABILITY_NAMED_IAM --parameters ParameterKey=CodeRepositoryName,ParameterValue=automated-iot-fleet-provisioning-by-claim ParameterKey=CodeRepositoryBranch,ParameterValue=master ParameterKey=ResourceTag,ParameterValue=iotfleetprov --profile IoT
Note: Running the cloud formation using Admin keys
Please fix this and help me to understand the error
Update: the template worked fine in N Virginia region

The possible reason is the code assumed the regions as default (us-east-1)
From s3 CLI doc
If you send your create bucket request to the s3.amazonaws.com endpoint, the request goes to the us-east-1 Region.
For boto3, we have to use
    	location = {'LocationConstraint': region}
        s3Client.create_bucket(Bucket=model_bucket, CreateBucketConfiguration=location)

Instead of
s3Client.create_bucket(Bucket=model_bucket)


Cleaning up spot outputs

closes #19

LGTM at a read through.
(Lemme know if you want me to dig deep and I'll run it on my own, but I trust it does what you say it does)

This is a perfect review btw, it is super for us to describe exactly how we reviewed.
From this post 👇
Reviewers
Guards the commit history.

Are NOT responsible to test the code.

Should response within a logical time, or ping the reviewee to opt out of the review

The review process
Read the pull request title and body to see that you get the need and value of the pull quickly.

Validate sane git commits.

Validate CI checks are passing.

Always comment on lines in diff view, not in general discussion at the pull request page.

Nitbitting VS Bikeshedding 1/2
Comment on all that gets your attention, including typos, However, Don’t lose sight on what the pull requests actual value.

Ask in a polite way if you need elaboration.

Use Emoji!!1.

Since we don't have tests (yet), and the project is still very new, it is up to the developer to ensure that the code actually works


bugfix: feast-hive was crashing in case of 2 schemas having same-named table

Hi again! I've encountered with a bug: it I have 2 Hive schemas with same-named table, feast-hive is crashing on feast apply on table search and name validation step.
Here's my bugfix for it.
And some code to reproduce the bug could be found here: https://github.com/Felix-neko/feast_sandbox/commit/c8be5ae4550d69830926e029eb3a9b53bd160a27
P.S. I'm a bit overwhelmed with my current work, but It will be extremely cool if you take it to your set of unittest: this place is tricky enough to be unittested.
^_^

Thanks for your contribution, I was on long holiday before, will have a look of this.

Thanks for your improvement and sorry for processing later.