[meshcop] publish Border Router ID in MeshCoP service

A randomly generated 16-bytes BR ID is required for adding Thread network to mobile OS APIs.
This commit generates the ID with OpenThread NonCrypto random API and save the ID in settings.
Example MeshCoP service dump  which includes the id field:
OpenThread BorderRouter #B465._meshcop._udp.local. state changed: ServiceStateChange.Updated
  Host: wgtdkp.local.
  Addresses: ['fe80::21bf:d2a9:a692:4196%0', 'fe80::7a95:56b6:37ca:9a18%0', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '2401:fa00:41:801:456f:3951:5312:e779', '2401:fa00:41:801:abf2:84d:c187:b7fc', '2401:fa00:41:801:b3e6:d67a:b7e5:b337', '2401:fa00:41:801:f6af:37f8:9114:ea78', '2401:fa00:41:801:d5cd:356:54b8:b1b7', '2401:fa00:41:801:d3b:4457:29eb:ef0e', '2401:fa00:41:801:65ea:d70e:7f04:73cf', '2401:fa00:41:801:3ae4:3b3b:dd97:b03', '2401:fa00:41:23:8de3:6871:abc3:c5d7', '2401:fa00:41:23:2d0b:f1b6:ddd0:9827', '2401:fa00:41:23:1ce2:6043:a34f:e022', '2401:fa00:41:23:e4ed:dc8f:14c1:5b00', '2401:fa00:41:23:a9a4:380d:b0e1:6bb', '2401:fa00:41:23:9799:3cd3:bca5:c5d5', '2401:fa00:41:23:12a0:c083:71fd:4034', '2401:fa00:41:23:e21a:db0:6544:1068']
  Port: 49154
  Weight: 0
  Priority: 0
  TXT:
    rv: 1
    id: d6f4da2e14622c38f33ce44dcdc5cbc4
    vn: OpenThread
    mn: BorderRouter
    nn: OpenThread-d9a0
    xp: acc214689bc40bdf
    tv: 1.3.0
    xa: 7a61b152af5bb465
    sb: 000001b1
    at: ffeeddccbbaa0000
    pt: 1a416e35
    sq: 67
    bb: f0bf
    dn: DefaultDomain
    omr: 40fd5e55a6f0cc0001

Depends on https://github.com/openthread/openthread/pull/8971

nit: how about providing a command line argument to switch on/off instead of a compile time feature flag? really want to reduce compile time flags on POSIX platform.

What about also providing a CLI that allows setting the id value?

nit: how about providing a command line argument to switch on/off instead of a compile time feature flag? really want to reduce compile time flags on POSIX platform.

What about also providing a CLI that allows setting the id value?

@wgtdkp would you like me to file a feature request?

nit: how about providing a command line argument to switch on/off instead of a compile time feature flag? really want to reduce compile time flags on POSIX platform.

What about also providing a CLI that allows setting the id value?

@wgtdkp would you like me to file a feature request?

Hey @gabekassel yeah I am aware of this, let me handle this in maybe this week :)

nit: how about providing a command line argument to switch on/off instead of a compile time feature flag? really want to reduce compile time flags on POSIX platform.

What about also providing a CLI that allows setting the id value?

Submitting https://github.com/openthread/openthread/pull/9049 to address this


update dependencies jetty, loopback

Update logback version, jetty version
Documentation

[X] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[X] I thought about adding a changelog entry, and added one if I deemed necessary.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Use hoist-core server-side export with agGrid. #289

Column prop exportFormat to control display in excel files.
Column prop exportValue to transform value prior to export, or to export a different field than the column.
Column prop exportName to use a different column header than the grid.
Add 'exportExcel' and 'exportCsv' context menu tokens.

I've added the option to export using agGrid - see https://github.com/exhi/hoist-react/pull/435/commits/b8b945c2f2eae89eac050b322ca02656ecb896dc.
In the end, I went for a flag you can set on GridModel and types. This allows you to set a grid to export either to server / local without having to use custom context menu items or export buttons, while still allowing to specify one-off exports should you want to.

Looks great and very tight!  Think its the minimal API for everything we want to expose right now.


No controller emoji

As title says, there is no controller emoji when I have it in Polybar. There does exist a controller emoji though when I run the command in my terminal, so this leads me to think that I have to add the font to Polybar - but I do not know what font it is. Could you help me out? This is what fonts are currently used on my Polybar.
font-0 = "JetBrains Mono:size=11;4"
font-1 = "Iosevka Nerd Font:size=11;3"
font-2 = "feather:size=12;3"
font-3 = "FontAwesome:size=10"

It is definitely a font issue, any font with video_game (🎮) emoji will work. I'm currently using JetBrainsMono Nerd.

Alright it took a little while, for some reason JetBrainsMono Nerd didn't work for me, neither did any of the others font I had. I used the following resources to deduce what font to use and then had to scale it down for some reason.

https://github.com/polybar/polybar/wiki/Fonts#find-fonts-for-glyphs
https://github.com/polybar/polybar/issues/905

This is now my Polybar Config.
font-0 = "JetBrains Mono:size=11;4" font-1 = "Iosevka Nerd Font:size=11;3" font-2 = "feather:size=12;3" font-3 = "Noto Color Emoji:scale=8:size=12;3"
Thanks for the help :stuck_out_tongue_closed_eyes:


small clubs update

this small pr fixes a couple of styling issues, which somewhat impact the overall ui/ux. full changelog is below
changes

add research and science fair club
add new logic for navbar dropdown
(kinda) fix styling on [club].jsx for mobile devices

sample images

and yes, this was made with love


How to make hashes for ALL FILES?

So in title how can i make hashes for all files via b3sum?

It's not clear to me what you mean. Could you ask your question again with lots of detail?

I want to hash entire dir via b3sum not one by one files. My OS is Windows 10 x64 LTSC.

There's no one standard way to hash a directory of files. There are a lot of different things you need to think about to define the answer you want:

Are filenames included in the hash? Presumably they have to be.
How are filenames converted into bytes? This is especially tricky, because different operating systems represent names differently, and you usually want the same directory (e.g. the same git repo checkout, or the same tarball) to hash the same across operating systems.
Are file permissions included in the hash? File owners? This is also very OS-specific.
Is everything concatenated into one stream to be hashed, or do you want to use a Merkle tree construction to represent the directory hierarchy?

These are not simple questions. You'll need to decide on your answers to these questions, and then write code yourself to implement your decisions. If you can get away with it, you might want to take a simpler approach like "just create a tarball of the directory, and then hash the tarball." (That works well if you want to keep the tarball around, but it might not work if you need to guarantee that different machines can reproduce the exact same tarball.) Or maybe "just check the directory into git, and then use the git commit hash or the git tree hash."


Mistyped hyerlink

Mistyped Hyperlink
I mistyped the hyperlink so it wouldnt redirect.
Fixed in ths patch
Checklist

[ ] I discussed this pull request with Ultima or another developer before opening.
[x ] I read the contributing guidelines.
[x ] The changes in this pull request are tested.
[ x] The changes in this pull request build(dotnet build -c Release /warnaserror) with no errors.

LGTM


[BUG] SLES 15 SP3 - Deploy control plane - some issues in the "configure_deployer.sh" script

According to my tests using PAYG SLES 15 SP3 based image for the deployer instance, the script "configure_deployer.sh" has some issues and needs to be modified for official SLES 12/15 based Azure images.
Steps to reproduce the behavior:
Deploy control plane - https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/sap/automation-deploy-control-plane?tabs=linux#deploy-the-control-plane-1
Modified Deployer configuration file "MGMT-WEEU-DEP00-INFRASTRUCTURE.tfvars":

# The deployer_image defines the Virtual machine image to use, if source_image_id is specified the deployment will use the custom image provided, in this case os_type must also be specified
deployer_image = {
"os_type"         = "Linux"
"source_image_id" = ""
"publisher"       = "suse"
"offer"           = "sles-15-sp3"
"sku"             = "gen2"
"version"         = "latest"
}

Here the diff for the script "deploy/scripts/configure_deployer.sh"
Issue 1:
Wrong zypper command options used
-        sudo ${pkg_mgr} --gpg-auto-import-keys --quiet upgrade
+        sudo ${pkg_mgr} --gpg-auto-import-keys --non-interactive patch

Issue 2:
The package "sshpass" is available in SUSE Package Hub 15 SP3 repository, this repo is not activated in the SLES 15 SP3 based images available on Azure.
The package "apt-transport-https" is not available in official SLES 15 SP3 repositories.
-        apt-transport-https
+#        apt-transport-https
-        sshpass
+#        sshpass

Issue 3:
Command not needed with SLES 12/15 based deployer image
-    curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash > /dev/null
+# curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash > /dev/null

Issue 4:
Verification if extension "configure_deployer" is installed failed
-    devops_extension_installed=$(az extension list --query [].path | grep azure-devops)
-    if [ -z $devops_extension_installed ]; then
-      az extension add --name azure-devops --output none
+    if  az extension list --query [].path | grep -q "azure-devops";  then
+        echo 'Azure "azure-devops" extension is already installed'
+    else
+        echo 'Azure "azure-devops" extension is missing and has to be installed'
+        az extension add --name azure-devops --output none

NOTE: This is what was used to successfully deploy the control plane, using PAYG SLES 15 SP3 based deployer image.

configure_deployer.sh.tmpl.txt

renamed configure_deployer.sh script example:
configure_deployer.sh.txt

Thanks @amach4  Will add this to release 3.9 (scheduled in the next 2 weeks)


img2img roop

I'm using A6000 on runpod and the roop ext is taking a very very long time, 5 min for 1.  Any ideas?

maybe it's using cpu ?

It can also happen if you are working with a upscaled reference image from my experience..

I think this is the issue.  It stalls out here "Applied providers: ['CPUExecutionProvider'], with options: {'CPUExecutionProvider': {}}"
how do I ensure gpu is being utilized?

try !pip install onnxruntime-gpu

Thanks but I would have no idea where to add that or run lol

simply create a new cell and run it with the code above


Outlook on iOS minimum supported version number

Hi there,
in this article (https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-office-apps?view=o365-worldwide#sensitivity-label-capabilities-in-outlook), for the "Dynamic markings with variables" under the Outlook on iOS version number , it says "4.7.1+", however just noticed that the latest version in the App Store for Outlook is 4.2128.0, wondering if the "4.7.1" is still valid and is the minimum supported version for this feature to work.
Thanks

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

ID: e0836a95-d3b7-3c43-d56b-5fb4ceeb4765
Version Independent ID: 8a0d366b-5ff7-22de-7aba-6adbe0ea94ea
Content: Manage sensitivity labels in Office apps - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/sensitivity-labels-office-apps.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

Hi @walidelmorsy!  4.7.1 is a very old build of the app (the support for dynamic markings was server-side, not client-side). For easier comparison, read 4.7.1+ (no leading zeros) as 4.0007.1+, (not 4.7000.1). The version you quoted of 4.2128.0 is obviously higher than 4.0007.1, so this latest version supports dynamic markings.

@walidelmorsy - can we close this now?

@cabailey Thank you very much for sharing this explanation. @walidelmorsy Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Thanks very much @cabailey! I think this makes much more sense, the only suggestion I would have is to specify the (0007) bit in the article itself, otherwise we will have more questions about it moving forward :), just my 2 cents :). Thanks once again!

@walidelmorsy Yes, we're monitoring this and so far, only got a couple of inquiries.  We considered updating all references of 4.7.1 to 4.0007.1 but this has other repercussions, and the app wasn't released as 4.0007.1.  If you still had that version installed it would show 4.7.1 (common to drop leading zeros for software versions)  It's such an old version, I'm not even sure Apple would support it any more so what we might do, is increase our minimum supported version that would then make it easier to compare with current versions.  I think this is a problem bigger than this one instance and I'll discuss with the relevant people before making any changes to the docs.


bug: this is not working It also prevents screenshots (a black screen will be captured) [ios]

Plugin version:
@capacitor-community/privacy-screen: "4.1.1"
@capacitor/core: "5.0.5",
Platform(s):
IOS
Current behavior:
when i try take screen shot from ios device is show my app screen instead black screen
Expected behavior:
black screen instead my app screen
Steps to reproduce:

Related code:
const preventScreenshot = async (): void => {
await PrivacyScreen.enable();
};
if (platform !== 'web') preventScreenshot();
insert short code snippets here

Other information:

Capacitor doctor:

insert the output from `npx cap doctor` here

I cannot reproduce the issue using this demo app on my iPhone 13 with iOS 16.5.1.
Please provide a Minimal, Reproducible Example using this template in a public GitHub repository so I can debug the issue.

@robingenz
i created new project and i faced the same issue as well
github :  https://github.com/hashemalkayal/demo-app-capacitor

Just to make sure I didn't misunderstand you: The screenshot shows your app screen but you expect a black screen, right?

@robingenz
Yes, sure.

Yeah, I used your example app.

My iPhone 14 with iOS version 16.2
on app switcher mode my screen is replaced with gray color (correct behvior)
but when i try take screenshot i can see my app screen (incorrect behavior)

I understand that but I can't reproduce the problem and thus can't debug it.
You are welcome to debug it yourself and create a PR with a fix.


make MetricData Id logic more solid

@woodsaj looks good to you?

SetId should always set id.
we can't trust anyone sending metrics, they could
mess with the id field.

most often/always id won't be set yet when SetId() called,
no need to waste cycles branching and calling other functions

when GetId was called repeatedly and id was not set,
it would compute the id over and over again because it didn't save it.

no need for temp var id that just represents m.Id

Furthermore, I would argue that callers of this library should know if
the Id needs to be (re)set and whether or not it should already be set.
(in all places where GetId() is called - currently MT's defcache and
handler - it absolutely should have been set),
so no need for conditional branching.
in fact the old approach would hide bugs where the id wasn't
set yet even though it totally should have been. I rather have it
crash.
So we can just query .Id field instead of function call

This looks good to me. The reason for keeping GetId() was to allow transition to the id being set before the metrics where published to NSQD.

ok thanks


Missing property in sample code

The samles in question are WebVR Lab and WebVr Orange Room. Recently, when launching these from the editor, an error message is displayed:
[web-vr-ui.js?id=6076849&branchId=2377bd1c-2001-4f78-9f0c-62cc0bee56fb:76]: Cannot read property 'isSupported' of null

TypeError: Cannot read property 'isSupported' of null
    at onEnterVrPressedEvent (https://launch.playcanvas.com/api/assets/files/scripts/web-vr-ui.js?id=6076849&branchId=2377bd1c-2001-4f78-9f0c-62cc0bee56fb:76:33)
    at script.WebVrUi.initialize (https://launch.playcanvas.com/api/assets/files/scripts/web-vr-ui.js?id=6076849&branchId=2377bd1c-2001-4f78-9f0c-62cc0bee56fb:102:9)
    at ScriptComponent._scriptMethod (https://code.playcanvas.com/playcanvas-stable.dbg.js:27162:21)
    at ScriptComponent._onInitialize (https://code.playcanvas.com/playcanvas-stable.dbg.js:27180:16)
    at ScriptComponentSystem._callComponentMethod (https://code.playcanvas.com/playcanvas-stable.dbg.js:27580:51)
    at ScriptComponentSystem._onInitialize (https://code.playcanvas.com/playcanvas-stable.dbg.js:27585:10)
    at Function._helper (https://code.playcanvas.com/playcanvas-stable.dbg.js:24278:14)
    at Function.initialize (https://code.playcanvas.com/playcanvas-stable.dbg.js:24281:10)
    at Application.start (https://code.playcanvas.com/playcanvas-stable.dbg.js:23704:24)
    at https://launch.playcanvas.com/editor/scene/js/launch.js:7241:25

Tested in Chrome, Windows 10, no VR hardware connected.

Moved this to forum in light of guidelines.


undefined is not an object (evaluating 'CameraManager.Aspect')

I  have simple react native run from my emulator, and your plugin (component) install successfully, but one function not push on my code.
please find attached file.

Please help me... how to resolved this issue.
I'm waiting your reply.
Thanks
Subhash

Same problem I've got today 😭.

Resolved: react-native link react-native-camera one more time.

Should we close, is the workaround working?

I have the same error

Then I will close. Thanks!

I linked and info.plist doesn't have Camera permissions. Just installed first time today.
"Cannot read property "Aspect" of undefined from example code.

Can you please write steps to solve this in a more elaborated way?

I had same issue
My solution was react-native link react-native-camera put Camera permission on info.plist
And recompile react native run-ios

On Android, uninstalling and reinstalling the apk worked for me.

The key for me on iOS was
rm -rf ./node_modules
npm install
watchman watch-del-all

then I shut down packager, quit simulator, then react-native run-ios

In case anyone's facing this issue on Android, please try the gradle upgrade guide. It worked for me.


Improve the docker login logic

Perform the docker login if the credentials are present and then docker logout after Pongo completes execution of the docker pull. This would allow for increased docker pull rate-limiting using certain docker user accounts.

if given we should log in, if not given we should try without. If it fails, we should retry with the private creds for EE images not publicly available (eg. 036-2 and the likes).

to be taken into account: the docker login should not only wrap pulling the Kong image, but all pulls. eg. when doing "pongo up" it will pull cassandra and postgres. This will minimize the rate-limit errors which we're still encountering.

this has been fixed


Not clear regarding gamma!!

self.gamma = nn.Parameter(tensor([0.]))
o = self.gamma * o + x
or
o = self.gamma * torch.bmm(h, beta) + x
Hi @sdoria ,
I have a problem understanding the code. If we set gamma to 0., then wouldn't that always be zero ?
where is the atention ? As gamma is zero the complete self-attention is zero and the code finally adds input and pass it to linear.
I dont see the self attention here.
May be i did not understand it clearly, would you mind clarifying that?
Thanks!

hey it's been a couple years since I've looked at this code or done anything in machine learning, but I'll try. Possibly gamma is only initiated at 0 and then its value is learned within the model?

Yes, I think so too. Thanks! I referred to original code and it is correct.


SyntaxWarning in aggregate module in Python 3.9.1

aggregate module emits a following SyntaxWarning under Python 3.9.1:
…/lib/python3.9/site-packages/mongomock/aggregate.py:1301: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if (method == 'include') == (include_id is not False and include_id is not 0):

Also emits a warning under Python 3.8.6.

[This was introduced in 3.8](https://bugs.python.org/issue34850]


Questions

I will probably have a lot of questions, so I decided to create this issue and write them here to not get lost somewhere in the chats. Hopefully @MilaNedic or @ttusar can help me with some of them.

I don't think anything is wrong with removing dominated points since our SortedList (perhaps not very smartly named avl_tree - I should change that) works as a binary balanced tree described in the paper (and we only remove dominated points from T since they aren't candidates for cx and cy values). However, as far as I understand, nodes are not removed from Q - the doubly linked list of DLNodes. Preprocessing sets the .ndomr attribute to 1 if the node is dominated and then, when calculating the hypervolume in 3-D using hv3dplus, it is checked if the node is dominated (if yes, the function simply doesn't take it into account).

we only remove dominated points from T since they aren't candidates for cx and cy values
Yeah that makes sense, so removing them shouldn't be a problem.

Also I see now that we are actually removing them from the linked list using remove_from_z function, but only when calculating hypervolume. Not sure if it makes any difference, but will need to keep in mind when implementing other functions.

I know I asked you this before @MilaNedic, but can you explain me the meaning of this attributes of the DLNode again? I am not sure about the difference between self.closest and self.cnext (and which one corresponds to cx/cy in the paper). Also am I right that self.next[i] gives you the point that is the next by the order of i-th coordinate (and the previous one for self.prev)?
class DLNode:
    def __init__(self, x=None, info=None):
        self.x = x if x else [None, None, None, None]
        self.closest = [None, None]  # closest in x coordinate, closest in y coordinate
        self.cnext = [None, None]  # current next
        self.next = [None, None, None, None]
        self.prev = [None, None, None, None]
        self.ndomr = 0  # number of dominators
        self.info = info # information about the point

Hey @MilaNedic, do you maybe remember what one_contribution_3d(head, new) function does? I see it is only used in hv4dplusU function. I probably need something similar to calculate both the contributions of an element not in the archive and contribution of an element that is already in the archive.

The one_contributon_3d(head, new) calculated the contribution of the new point to an already existing "archive". This is then multiplied by height to get the hypervolume in 3-D. I think what may be the problem is the fact that this is a 3-D contribution so for 4-D points, you are missing the height?? But the idea should be very similar to this function.


Marking a LePage as ToC doesn’t work correctly

I just tried making a LePage the table of contents using the button in the inspector. This is the error triggered by the button:

Now, whenever I select a page from that table of contents, this is what I get:

Cheers

Nota bene: Clicking on the button again apparently seems to make it work correctly...

This should work better now.


Mataveid with Octave

I have just tried to execute the RLS example under Octave 5.2.0. I get the following error:

Attribute "sampleTime" is not known in Octave transfer function object. When I code Gd.tsam = sampleTime in rls.m the next error occurs.
To me it seems like the code is not really usable with Octave although the first sentence in the description suggests so...

I have just tried to execute the RLS example under Octave 5.2.0. I get the following error:

Attribute "sampleTime" is not known in Octave transfer function object. When I code Gd.tsam = sampleTime in rls.m the next error occurs.
To me it seems like the code is not really usable with Octave although the first sentence in the description suggests so...

@rstflo
Hi! Can you post your code?

Here is the code I used. It is just one of the examples.
% Load data
X = csvread('.../HangingLoad.csv');
t = X(:, 1); % Time
r = X(:, 2); % Reference
y = X(:, 3); % Output position
u = X(:, 4); % Input signal from P-controller with gain 3
sampleTime = 0.02;
% Do identification of the first data set
l = length(r) + 2000; % This is half data
% Do identification on up and down
sysd_up = rls(r(1:l/2), y(1:l/2), 1, 1, 1, sampleTime);
sysd_down = rls(r(l/2+1:end), y(l/2+1:end), 1, 1, 1, sampleTime);
% Simulate
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));
hold on
lsim(sysd_down, r'(l/2+1:end), t'(l/2+1:end), x(:, end));
hold on
plot(t, y);
legend('Up model', 'Down model', 'Measured');
title('Hanging load - Hydraulic system')
xlabel('Time [s]')
ylabel('Position');

Another problem occurs when I use the OKID example.
Code:
% Load the data
X = csvread('.../MultivariableCylinders.csv');
t = X(:, 1);
r0 = X(:, 2);
r1 = X(:, 3);
y0 = X(:, 4);
y1 = X(:, 5);
sampleTime = 0.1;
% Create the model
inputs = [r0';r1'];
states = [y0';y1'];
derivatives = (states(:, 2:end) - states(:, 1:end-1))/sampleTime;
states = states(:, 1:end-1);
inputs = inputs(:, 1:end-1);
t = t'(1, 1:end-1);
[sysd, K] = okid(inputs, states, derivatives', t, sampleTime);
% Do simulation
[outputs, T, x] = lsim(sysd ,inputs, t);
close
plot(T, outputs(1, :), t, states(1, :))
title('Cylinder 0');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);
figure
plot(T, outputs(2, :), t, states(2, :))
title('Cylinder 1');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);
Error message:

Another problem occurs when I use the OKID example.
Code:
% Load the data
X = csvread('.../MultivariableCylinders.csv');
t = X(:, 1);
r0 = X(:, 2);
r1 = X(:, 3);
y0 = X(:, 4);
y1 = X(:, 5);
sampleTime = 0.1;
% Create the model
inputs = [r0';r1'];
states = [y0';y1'];
derivatives = (states(:, 2:end) - states(:, 1:end-1))/sampleTime;
states = states(:, 1:end-1);
inputs = inputs(:, 1:end-1);
t = t'(1, 1:end-1);
[sysd, K] = okid(inputs, states, derivatives', t, sampleTime);
% Do simulation
[outputs, T, x] = lsim(sysd ,inputs, t);
close
plot(T, outputs(1, :), t, states(1, :))
title('Cylinder 0');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);
figure
plot(T, outputs(2, :), t, states(2, :))
title('Cylinder 1');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);
Error message:

@rstflo
Try writing 'updatemataveid' in gnu octave terminal.
This code example works to 100%. No errors or warnings.

Here is the code I used. It is just one of the examples.
% Load data
X = csvread('.../HangingLoad.csv');
t = X(:, 1); % Time
r = X(:, 2); % Reference
y = X(:, 3); % Output position
u = X(:, 4); % Input signal from P-controller with gain 3
sampleTime = 0.02;
% Do identification of the first data set
l = length(r) + 2000; % This is half data
% Do identification on up and down
sysd_up = rls(r(1:l/2), y(1:l/2), 1, 1, 1, sampleTime);
sysd_down = rls(r(l/2+1:end), y(l/2+1:end), 1, 1, 1, sampleTime);
% Simulate
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));
hold on
lsim(sysd_down, r'(l/2+1:end), t'(l/2+1:end), x(:, end));
hold on
plot(t, y);
legend('Up model', 'Down model', 'Measured');
title('Hanging load - Hydraulic system')
xlabel('Time [s]')
ylabel('Position');

@rstflo
Change
[,,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));

to
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));

Also 'updatemataveid' in Gnu octave terminal, or MATLAB terminal. This code example works to 100%. No errors.

I alread use
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));
During copy/paste the ~ was somehow lost...
Executing 'updatemataveid' in the terminal gives an error:

I alread use
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));
During copy/paste the ~ was somehow lost...
Executing 'updatemataveid' in the terminal gives an error:

@rstflo
Try to write path in your Octave terminal, or MATLAB terminal. Does it looks like this?
>> path

Octave's search path contains the following directories:

.
/home/dell/program/matavecontrol/matavecontrol
/home/dell/program/mataveid/mataveid
.....
.....
more libs

No it does not!
I only have the directories in my search path that come with the downloaded folders.

I think I did not follow the installation guidance properly...
Will check this and come back if there is still a problem.

No it does not!
I only have the directories in my search path that come with the downloaded folders.

I think I did not follow the installation guidance properly...
Will check this and come back if there is still a problem.

@rstflo
That's the issue! :) Try to rename "sourcecode" to "mataveid". And remember! You need "matavecontrol" as well.

Hi Daniel,
just tried what you suggested.
matavecontrol and mataveid are now both in Octave's search path. I successfully updated both via the console using updatemataveid respectively udpatematavecontrol.

Now I get the following error for the OKID example code:

For the RLS example code I get the following error:

Any thoughts?

Post the complete code.

OKID code example:
`% Load the data
X = csvread('.../libs/Mataveid-master/data/MultivariableCylinders.csv');
t = X(:, 1);
r0 = X(:, 2);
r1 = X(:, 3);
y0 = X(:, 4);
y1 = X(:, 5);
sampleTime = 0.1;
% Create the model
inputs = [r0';r1'];
states = [y0';y1'];
derivatives = (states(:, 2:end) - states(:, 1:end-1))/sampleTime;
states = states(:, 1:end-1);
inputs = inputs(:, 1:end-1);
t = t'(1, 1:end-1);
[sysd, K] = okid(inputs, states, derivatives', t, sampleTime);
% Do simulation
[outputs, T, x] = lsim(sysd ,inputs, t);
close
plot(T, outputs(1, :), t, states(1, :))
title('Cylinder 0');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);
figure
plot(T, outputs(2, :), t, states(2, :))
title('Cylinder 1');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);`
RSL code example:
`% Load data
X = csvread('.../libs/Mataveid-master/data/HangingLoad.csv');
t = X(:, 1); % Time
r = X(:, 2); % Reference
y = X(:, 3); % Output position
u = X(:, 4); % Input signal from P-controller with gain 3
sampleTime = 0.02;
% Do identification of the first data set
l = length(r) + 2000; % This is half data
% Do identification on up and down
sysd_up = rls(r(1:l/2), y(1:l/2), 1, 1, 1, sampleTime);
sysd_down = rls(r(l/2+1:end), y(l/2+1:end), 1, 1, 1, sampleTime);
% Simulate
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));
hold on
lsim(sysd_down, r'(l/2+1:end), t'(l/2+1:end), x(:, end));
hold on
plot(t, y);
legend('Up model', 'Down model', 'Measured');
title('Hanging load - Hydraulic system')
xlabel('Time [s]')
ylabel('Position');`

OKID code example:
`% Load the data
X = csvread('.../libs/Mataveid-master/data/MultivariableCylinders.csv');
t = X(:, 1);
r0 = X(:, 2);
r1 = X(:, 3);
y0 = X(:, 4);
y1 = X(:, 5);
sampleTime = 0.1;
% Create the model
inputs = [r0';r1'];
states = [y0';y1'];
derivatives = (states(:, 2:end) - states(:, 1:end-1))/sampleTime;
states = states(:, 1:end-1);
inputs = inputs(:, 1:end-1);
t = t'(1, 1:end-1);
[sysd, K] = okid(inputs, states, derivatives', t, sampleTime);
% Do simulation
[outputs, T, x] = lsim(sysd ,inputs, t);
close
plot(T, outputs(1, :), t, states(1, :))
title('Cylinder 0');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);
figure
plot(T, outputs(2, :), t, states(2, :))
title('Cylinder 1');
xlabel('Time');
ylabel('Position');
grid on
legend('Identified', 'Measured');
ylim([0 12]);`
RSL code example:
`% Load data
X = csvread('.../libs/Mataveid-master/data/HangingLoad.csv');
t = X(:, 1); % Time
r = X(:, 2); % Reference
y = X(:, 3); % Output position
u = X(:, 4); % Input signal from P-controller with gain 3
sampleTime = 0.02;
% Do identification of the first data set
l = length(r) + 2000; % This is half data
% Do identification on up and down
sysd_up = rls(r(1:l/2), y(1:l/2), 1, 1, 1, sampleTime);
sysd_down = rls(r(l/2+1:end), y(l/2+1:end), 1, 1, 1, sampleTime);
% Simulate
[~,~,x] = lsim(sysd_up, r'(1:l/2), t'(1:l/2));
hold on
lsim(sysd_down, r'(l/2+1:end), t'(l/2+1:end), x(:, end));
hold on
plot(t, y);
legend('Up model', 'Down model', 'Measured');
title('Hanging load - Hydraulic system')
xlabel('Time [s]')
ylabel('Position');`

@rstflo
Hmm...I don't get any errors.
Can you do this:

G = tf(1, [2 4 5]); % Random TF
u = gensig('square', 10, 50, 500); % Square wave, Amplitude = 10, 50 Hz, 500 sample time
t = linspace(0, 500, length(u)); % Time
y = lsim(G, u, t); % Linear simulation
sysd = rls(u, y, 2, 2, 2, t(2)-t(1)); % 2 poles, 2 zeros, 2 zeros for the noise polynomial
lsim(sysd, u, t); % Simulate the estimated model
hold on
lsim(G, u, t); % Simulate the real model and plot it directly on the estimated model

lsim has a problem with this. So I do not come to the point where rsl is used...

lsim has a problem with this. So I do not come to the point where rsl is used...

I am using lsim regularly and I have not had problems so far.

Do you have control-toolbox included in Octave? That will cause problems.

Yes I am using the control toolbox as I use some of the included functions.

Does your code matavecontrol provide all the functions that are included in control toolbox?
I can reinstall Octave and try to figure out if the problems are related to the use of the Octave control toolbox and or remove the control toolbox from the search path first.
Nevertheless I suggest to add the info to the Readme that you need to have matavecontrol to use mataveid and that one should not use the Octave control toolbox at the same time? Or does this work in general and it is only a problem of my installation?

Yes I am using the control toolbox as I use some of the included functions.

Does your code matavecontrol provide all the functions that are included in control toolbox?
I can reinstall Octave and try to figure out if the problems are related to the use of the Octave control toolbox and or remove the control toolbox from the search path first.
Nevertheless I suggest to add the info to the Readme that you need to have matavecontrol to use mataveid and that one should not use the Octave control toolbox at the same time? Or does this work in general and it is only a problem of my installation?

What you could to is to have the previous release of GNU Octave and install that with MataveID och MataveControl. Control-toolbox WILL cause problem for MataveID and MataveControl because they have the same function names.
The difference between MataveID/MataceControl and Control-Toolbox is that mine is 100% Opensource and have no external libraries. It's made for the user to read how the theory goes and be applied in practice :)
I can add that!

When you say previous release - which do you mean? I have the latest release 5.2.0.
So I should install 5.1.0 or an older release?
Has your code been tested/compared/verified against the Octave control toolbox?

When you say previous release - which do you mean? I have the latest release 5.2.0.
So I should install 5.1.0 or an older release?
Has your code been tested/compared/verified against the Octave control toolbox?

Try 5.1.0.
My code has been tested with MATLAB's Control-Toolbox.

Ok this may take some days. I will let you know when tested. Thanks a lot for your support.

I have just tested removing the Octave control toolbox from Octave's search path. Afterwards it was possible to run the OKID as well as the RLS example.
I could also run the following code that you asked me to test.

G = tf(1, [2 4 5]); % Random TF
u = gensig('square', 10, 50, 500); % Square wave, Amplitude = 10, 50 Hz, 500 sample time
t = linspace(0, 500, length(u)); % Time
y = lsim(G, u, t); % Linear simulation
sysd = rls(u, y, 2, 2, 2, t(2)-t(1)); % 2 poles, 2 zeros, 2 zeros for the noise polynomial
lsim(sysd, u, t); % Simulate the estimated model
hold on
lsim(G, u, t); % Simulate the real model and plot it directly on the estimated model

So issue can be closed from my point of view.
If needed I will load the Octave control toolbox directly in my .m files instead of having it in the search path.


Simple signing verification sometimes fails due to transient/network errors

What commit ID of Portieris did you experience the problem with?
v9.5.0
What went wrong?
Portieris blocked deployment of an image with a simple signing policy.
Logs showed:
imagePolicy.go:63] SimpleSigning verification: ImagePullSecret with username <REDACTED> for image <REDACTED> failed, no more secrets in scope (secret 3/3). Failing.
What should have happened differently?
EOFs and connection timeouts can occur for a variety of reasons - both at the registry end and the calling client (Portieris in this case).
Most clients are hardened to retry in these kind of cases, to provide resiliency against transient issues.
I would expect Portieris to have at least one retry here before blocking the deployment.
How can it be reproduced?
There's not a specific reproduce, it will occur occasionally over time.
Any other relevant information
Care is needed to ensure retries are not attempted for all failures. The code in question is inside a loop that can try a variety of different credentials. Obviously a 403 does not need to be retried.

To expand a bit on the last section in the description above..
I believe that ImageReferece.NewImageSource() (in the containers library) will return an error , which is not a useful "typed" error , for both the "invalid creds" case and the "connection error" case.
With the code as currently structured, it is difficult to see how you can harden it against network glitches without also adding an unwanted retry to all attempts that use the wrong/invalid credentials.

If portieris were not installed and the deployment admitted the transient error would be retried and eventually succeeed by the container runtime.
While we can and should look to mitigate a short transient failure ultimately the admission webhook will timeout and the deployment should be rejected, it may be that we can indicate the transient failure on the response but the deployment process would have to retry too.

If portieris were not installed and the deployment admitted the transient error would be retried and eventually succeeed by the container runtime.
While we can and should look to mitigate a short transient failure ultimately the admission webhook will timeout and the deployment should be rejected, it may be that we can indicate the transient failure on the response but the deployment process would have to retry too.

Lets see how the above issue is received and decide whether to PR container/image or to add some string matching (which could be unit tested for safety).

Lets see how the above issue is received and decide whether to PR container/image or to add some string matching (which could be unit tested for safety).

The containers/image library, or at least the parts we rely on here appear to wrap errors extensively. If we also adopt error wrapping properly then we can choose the appropriate place to perform retries and do so if an error in the "stack" of wrapped errors implements net.Error and is .Temporary().

The containers/image library, or at least the parts we rely on here appear to wrap errors extensively. If we also adopt error wrapping properly then we can choose the appropriate place to perform retries and do so if an error in the "stack" of wrapped errors implements net.Error and is .Temporary().

So I think there are four possible avenues here:

Retry all failed admissions n times. This would retry when we hit an EOF as above, but would also retry inappropriately for unauthorized etc. and would also mean we have to deal with how we present errors from multiple attempts to the user.
Retry typed errors as in my previous comment. This would re-try some errors, but not the EOF error that this issue was raised for. We could solve that by retrying any error that implements net.Error regardless of if it is temporary, but this could be too wide as it might catch other errors that unintentionally implement this interface. I don't consider string matching on the errors to be an acceptable approach.
We could make an upstream change tp the containers/image library to allow us to wrap the http.RoundTripper used by github.com/containers/image/docker.dockerClient in a similar way to what is offered by k8s.io/client-go/rest.Config.WrapTransport, this would allow us to re-try on any error that comes back from the actual attempt to perform the request. I'm reaching out to the maintainers to discuss how such an approach could work, but I'm not confident it can be done cleanly.
Not retry. A difference between portieris and the container runtime that would be talking to the registry after admission is that portieris will always have a "user", be that a human calling kubectl apply or helm, or somebody's automation. We always have someone to tell about our errors. Containerd must re-try because it is a daemon, it must retry to serve its base function.

So I think there are four possible avenues here:

Retry all failed admissions n times. This would retry when we hit an EOF as above, but would also retry inappropriately for unauthorized etc. and would also mean we have to deal with how we present errors from multiple attempts to the user.
Retry typed errors as in my previous comment. This would re-try some errors, but not the EOF error that this issue was raised for. We could solve that by retrying any error that implements net.Error regardless of if it is temporary, but this could be too wide as it might catch other errors that unintentionally implement this interface. I don't consider string matching on the errors to be an acceptable approach.
We could make an upstream change tp the containers/image library to allow us to wrap the http.RoundTripper used by github.com/containers/image/docker.dockerClient in a similar way to what is offered by k8s.io/client-go/rest.Config.WrapTransport, this would allow us to re-try on any error that comes back from the actual attempt to perform the request. I'm reaching out to the maintainers to discuss how such an approach could work, but I'm not confident it can be done cleanly.
Not retry. A difference between portieris and the container runtime that would be talking to the registry after admission is that portieris will always have a "user", be that a human calling kubectl apply or helm, or somebody's automation. We always have someone to tell about our errors. Containerd must re-try because it is a daemon, it must retry to serve its base function.

After extensive testing I have been unable to provoke any retry-able errors talking to a registry. I do not believe it is worth the complexity to add a re-try and think this issue should be closed.
While working on this PR I found some related code bugs and have opened #273 to address those.


[ci] Enable parallel execution of unit tests

Unit tests are still running serially on Travis, because we cannot derive a correct coverage report otherwise.

Fixes #134.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1533   +/-   ##
=======================================
  Coverage   87.90%   87.90%
=======================================
  Files          43       43
  Lines        6848     6848
=======================================
  Hits         6020     6020
  Misses        828      828

Continue to review full report at Codecov.

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

I need to pin also the docs requirements.


fix: do not mutate read-only files

Right now, if you attempt to build a project that contains read-only files it will fail with a simple permission error. This makes it impossible for the user
to understand what file is causing issues.
The simple fix used here simply does not mutate the line endings on files which cannot be written.
I'm not sure why the line endings are mutated on files or why the entire project directory is copied. I imagine I'm missing something obvious that could cause other downstream impacts,
so I'm opening this PR as the start of a discussion.
This PR:
fixes https://github.com/railwayapp/nixpacks/issues/1071
related https://github.com/railwayapp/nixpacks/issues/700
TODO

[ ] Tests are added/updated if needed

Friendly reminder regarding this pull request. Please let me know if there are any further updates needed.

Hey sorry about the delay. The line endings mutating was added here, https://github.com/railwayapp/nixpacks/pull/436 to fix issues with Windows.
This PR looks good though. Could you please just fix the lining/tests and we can get it merged :)

Can you help me with the windows build?
I'm a rust beginner and have no idea what the idiomatic way of handling this sort of thing in rust is.,

Of course! You should be able to have a separate is_writable function that is used for windows. Similar to this
https://github.com/railwayapp/nixpacks/blob/2df97bbf824d939081598573a643ae818397b39c/src/nixpacks/app.rs#L154

Friendly reminder that this pull request may be closed soon if there is no further activity. Let me know if you need any assistance.

I've updated the is_writable function to support windows. I'll merge after everything passes.


Teleport Locomotion System

Teleport Locomotion is a fundamental system needed in many different VR Applications. We need such a system also as a Feature_TeleportLocomotion inside the toolkit.
It should be a simple drag-n-drop solution comparable to the Feature_StickLocomotion and provide few parameters to customize. The visual cue for the teleport location and the arc should be rendered in a performant way on the Oculus Quest.
The hit detection is likely going to use a ray-cast based system.

I started implementing a basic teleport system. It is now on the experimental branch:

The teleport system is now on master; it is still very limited and simple but basically works.


TypeScript Typings are off on transformEntriesToType

pretty sure there’s a bug in the typescript typings for migration.transformEntriesToType https://github.com/contentful/contentful-migration/blob/master/index.d.ts#L267
The docs say that it should have sourceContentType and targetContentType fields https://github.com/contentful/contentful-migration#transformentriestotypeconfig
Think this prevents writing typescript migrations

Hey, thanks again @bsgreenb, I added the fix.


Handle Timeline containers

At the beginning of the XML event "text" entry there may be a link to a container in round brackets. This must be taken into account, i.e. it should neither appear in the yWriter scene description nor be overwritten during synchronization.

First idea:
Upon synchronization with yWriter, convert the bracketed numbers into UIDs looking like"ContID:1" and store them as item tags.

My thought for these (waving a magic wand, of course), is that it could be user-dependent how they wanted the containers handled. My first thought is that containers could make great Chapters-- after all, they contain Events (Scenes), but also recognizing that someone else may have a different use in mind for them, like (as you say), having a certain Container result in a specific tag on the Scene), or even the viewpoint character-- that could be useful for someone who really gets into the character and wants to do their writing at a stretch.
I realize the headache it could create. You'd need some type of "pair file" to know how the sync is setup, and also-- messy!

As far as I found out, the containers in Timeline are used to create groups of events with a fixed time reference. If you move a container, the time intervals of the members are preserved. This concept has no counterpart in yWriter, and I would not misuse it.
My issue was really just about making the container information invisible in yWriter so that it wouldn't be touched accidentally. I can also remove it altogether and restore it from the timeline project during synchronization.

The other way round, yWriter scene titles beginning with a bracketed word will cause unreadable timelines, since Timeline's XML parser takes it as an invalid container ID and throws an exception. So for now, be sure not to begin scene titles with brackets.

With v0.8.0, this is implemented:

Containers are invisible in yWriter.
Synchronization does not affect the membership of an event in a container.
Scene titles beginning with an opening bracket '(' or '[') are automatically prefixed with '_' in Timeline. Do not remove this prefix; it will not appear in yWriter after synchronization.


Pressing "Enter" on Mac using the LWJGL3 backend doesn't insert a new line into a TextArea

Issue details
Pressing "Enter" on a Mac using the LWJGL3 backend doesn't insert a new line into a TextArea.
It works perfectly fine using LWJGL2.
Reproduction steps/code
public class LWJGL3TextAreaTest extends GdxTest {
    private Stage stage;
    private Skin skin;

    @Override
    public void create () {
        stage = new Stage();
        Gdx.input.setInputProcessor(stage);
        skin = new Skin(Gdx.files.internal("data/uiskin.json"));
        TextArea textArea = new TextArea(
            "Text Area\nEssentially, a text field\nwith\nmultiple\nlines.\n"
                + "It can even handle very loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong lines.",
            skin);
        textArea.setX(10);
        textArea.setY(10);
        textArea.setWidth(200);
        textArea.setHeight(200);

        TextField textField = new TextField("Text field", skin);
        textField.setX(10);
        textField.setY(220);
        textField.setWidth(200);
        textField.setHeight(30);
        stage.addActor(textArea);
        stage.addActor(textField);
    }

    @Override
    public void render () {
        Gdx.gl.glClearColor(0.2f, 0.2f, 0.2f, 1);
        Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);
        stage.act();
        stage.draw();
    }

    @Override
    public void resize (int width, int height) {
        stage.getViewport().update(width, height, true);
    }

    @Override
    public void dispose () {
        stage.dispose();
        skin.dispose();
    }
}

Version of LibGDX and/or relevant dependencies
Latest Master/ Libgdx 1.9.3-SNAPSHOT
LWJGL3 backend
Issue description/solution
The problem is that LWJGL3 generates '\r' on an enter press, while LWJGL2 generated a '\n' on an enter press. Therefore this line (ENTER_ANDROID is '\r') is executed, which selects the next text field.
How to fix?
I don't know how to fix this issue. We could either generate '\n' key events instead of '\r' events or we could fix the TextField class.
Please select the affected platforms

[ ] Android
[ ] iOS
[ ] HTML/GWT
[ ] Windows
[ ] Linux
[x] MacOS

It's strange and i think it is bug in LWJGL3. Before MacOS X -- apple used '\r'. So it was funny:

Unix uses '\n'
MacOS '\r'
Windows uses both at the same time CR+LF
But with MacOS X, which is Unix based, there should be regular '\n' used. I've checked on my MBP13 -- all applications show that I type '\n' on an "enter" press.

Had this same issue on Windows just now.
Making a version of the TextField class that used '\n' for ENTER_DESKTOP instead of '\r' did seem to resolve it in my case.

Confirmed, wth.

I noticed it too, pressing enter either in a textfield or textarea cycles the focus like tab does.

This issue still exists. The easiest solution would be to remove the behaviour of pressing ENTER_ANDROID to change focus.

This is no longer an issue.


model_name raising error because of the dot

as per title

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


InputState:addActions(actions) does not automatically remove unused Actions

There are three solutions I have thought of so far but I am not too fond of them:

Add InputState:removeActions(actions).
I would like to avoid this so that the user doesn't have to remove the actions manually.

Store the actions in a weak table.
I'm not sure what to think of this yet, is this fine? Should we avoid metatable magic?

Change InputState:update()  to InputState:updateActions(actions).
If the user updates each Actions manually the InputState doesn't need to store them. For this to work we would need some way to reset some of the controls because those have to be reset after all the Actions have been updated.

Fixed in #13.


Update sql-server-backup-to-url-best-practices-and-troubleshooting.md

The BackupToURL exe will only output the log file (using trace flag 3051) and the Windows Event Log if you are using Page Blobs (i.e. the backup T-SQL has WITH CREDENTIAL). If you are using block blobs then the TF is ignored and no output is written to log file or the Windows Event Log.
I'm propsing this update as the doc currently gives you the impression that using the TF will result in the verbose output in all use cases, which is not true.
If there is a better way to convey this situation please update the doc to reflect that.

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

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

#sign-off

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


Feature Request: Ability to specify a rendering template for individual forms

It would be extremely useful to be able to specify what template should be used to render a specific form. The default form template can be overridden, but it still gets used for all forms, which is extremely limiting when some forms need special styling compared to others. I suppose it's possible to do a comparison to the form ID in the template and use a separate setup based on that, but that particular solution seems extremely hacky and un-Django-like.
This feature would add a single option to the admin interface for editing forms that lets the user specify the template to use for that form (probably as a dropdown pulling from a project settings variable, to avoid injection risks from user data). It would then modify the BuiltFormNode.render method to pull the form-specific template, defaulting to the built-in template if none exists or was specified.
I would be willing to do the codework to get this functional and provide a pull request, but I don't want to do so if the feature doesn't align with project goals.

I think this is best implemented via templates as you described.


Exploit failed on iOS 11.4.x

When using Unc0ver v3.0,0-b4 on a iPhone 7+ running iOS 11.4.1 using the Voucher_Swap exploit the device panics and reboots itself every time after pressing jailbreak. This seems like a common issue on all 11.4.x devices, but not everyone seems to be affected by this. For me, the last message in the logs is stashed voucher pointer in thread (which is in voucher_swap.c at line 837). I have tried some instructions someone gave on reddit (no passcode, no siri, airplane mode, 30 seconds wait after opening app) but that didn't change anything. Checking the panic logs mentions something about an unaligned kernel data abort. I'm suspecting pwn already knows this but thought I would mention it. Let me know if there is any information you want from me or if there is anything I can do. Also, thanks pwn and the team for making this possible!
diagnostics.plist: https://cdn.discordapp.com/attachments/340497979670528000/540244231206338561/diagnostics.plist
panic log (one of many, this one is from v3.0.0-b4): https://cdn.discordapp.com/attachments/340497979670528000/540305874481184770/panic-full-2019-01-31-000031.727.ips

i7+ 11.4.1 v3.0.0~b7
I had the same problem of always crashing. My steps to resolve (or just luck?):

Airplane mode
Clear memory
Open unc0ver and press button (all settings default)
After the crash/reboot and instantly after unlocking, open unc0ver and press the button
It worked and went through the motions of initial install

Still panics for me

still reboots for me after stashed voucher pointer in thread on beta 9, iPad Pro 10.5 11.4.1

Can confirm that it works seamlessly on b13.


Vxlan doc

New GA doc under Networking. Replaces existing IPIP and VXLAN doc.

Deploy preview for calico ready!
Built with commit af834d3d9b372135acb51d71ece21f1631c7f4bd
https://deploy-preview-2577--calico.netlify.com

Grr, there are some failing tests due to broken links in removing the old docs:
- /_site/master/getting-started/kubernetes/installation/config-options.html
  *  internally linking to /master/networking/vxlan, which does not exist (line 782)
     Calico’s VXLAN encapsulation mode
- /_site/master/networking/node.html
  *  internally linking to /master/networking/ip-in-ip, which does not exist (line 543)
     CrossSubnet IPIP
- /_site/master/reference/calicoctl/resources/ippool.html
  *  internally linking to /master/networking/ip-in-ip, which does not exist (line 1159)
     Configuring IP-in-IP
- /_site/master/reference/public-cloud/aws.html
  *  internally linking to /master/networking/ip-in-ip, which does not exist (line 1071)
     Configuring IP-in-IP guide
- /_site/master/reference/public-cloud/gce.html
  *  internally linking to /master/networking/ip-in-ip, which does not exist (line 1043)
     IP-in-IP encapsulation
- /_site/master/reference/public-cloud/ibm.html
  *  internally linking to /master/networking/ip-in-ip, which does not exist (line 1040)
     IP-in-IP encapsulation

@bmckercher123 could you chase these down and adjust to use the new document?

@caseydavenport @bmckercher123 I will try to finish this off for the release.

Thanks @neiljerram!


feat: GetStarted element

📑 Description
Get started - bottom element at the Home Page

[ ] Not Completed
[x] Completed

✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] I have checked the page with https://validator.unl.edu/
[x] All the tests have passed
[x] My pull request is based on the latest commit (not the npm version).

ℹ Additional Information

The following is nothting to do with this PR.
Shouldn't "View all components" link go to https://flowbite-svelte.com/docs/components/accordion ? It leads to https://flowbite-svelte.com/docs/pages/introduction .

Yes. It should.


Rename plugin class

Hi,
According to Webpack team:

3rd party Plugin names should be foo-webpack-plugin for pkg name and FooWebpackPlugin for class

The package will not be renamed for now but we have to change plugin class.
It should keep compatibility with previous class name.
Task list

[ ] Add class alias
[ ] Change documentation
[ ] Write new test case

If you find another side effect, do not hesitate to correct it
Thank you

I could tackle this one too.

Hi @Phinneas,
Thank you, but I prefer let this issue to a first pr only
iGitScor


fix: Handle Schrodingers Error

Fixes https://github.com/getsentry/raven-js/issues/1260
cc @MaxBittker @zivl

@kamilogorek looks good to me as well!
much kudos for the fast response


Update Juno forum address to 'discourse.julialang.org'

Shuld Juno always use "usage" category in Juila forum? or Juno can use "Development" category as well.

Thanks!


Support exec by --id-label

Right now, --workspace-folder is a mandatory argument to exec. This makes sense if the devcontainer was started from the environment that's running the CLI, from a locally-accessible filesystem. However, if the container was started by way of VS Code's "Clone Repository in Container Volume" feature, it's impossible to provide the workspace folder, since it only existed within the ephemeral bootstrap container.
It seems like --id-label is intended to be an identification mechanism for containers that doesn't require a local copy of their devcontainer.json -- if so, it would make sense to support this mechanism for exec.

This currently requires the devcontainer.json to work. We can revisit this when we add support for "attaching" to an existing dev container without a devcontainer.json.
You could try doing something similar to the Dev Containers extension which uses a temporary container to access the devcontainer.json. The following worked when I tried it with a dev container created from https://github.com/chrmarti/vscode-regex (you would see different labels/names):
Dockerfile for the temporary containers:
FROM mcr.microsoft.com/devcontainers/base:0-alpine-3.16

RUN apk add --no-cache \
	nodejs \
	python3 \
	npm \
	make \
	g++ \
	docker-cli \
	docker-cli-buildx \
	docker-cli-compose \
	;

RUN npm i -g @devcontainers/cli

Build and run temporary container:
docker build -t devcontainer-cli .

docker run -it --rm --mount type=volume,src=vscode-regex-main-29a8aa263ac65c28ae2f5568b6fd157f,dst=/workspaces -v /var/run/docker.sock:/var/run/docker.sock devcontainer-cli /bin/ash

Run devcontainer CLI from within the temporary container:
devcontainer exec --workspace-folder /workspaces/vscode-regex --id-label vsch.local.repository=https://github.com/chrmarti/vscode-regex.git/tree/main --id-label vsch.local.repository.volume=vscode-regex-main-29a8aa263ac65c28ae2f5568b6fd157f --id-label vsch.local.repository.folder=vscode-regex --log-level debug /bin/sh -c "pwd && ls -l"


Add JS modules

@Elchi3 Good suggestion, an initial support variant makes sense here.
This runs into something I've been anticipating: should we use js-modules as the identifier for both the group and the initial feature? I think we probably should, and the consequence is that groups and features will be distinct namespaces and consumers need more than a bare identifier to refer to a group.

To me the "JS module" group acts as an umbrella for all things that have to do with modules on a technical level. And I think for exploring the web platform, these technical groups are interesting.
I can imagine that "JS modules (initial support)" becomes part of other groups and "JS Modules in SVG" doesn't.
For example, https://www.webcomponents.org/introduction mentions that JS modules also belong to set of web platform APIs that make "Web Components".
Group: Web Components

JS modules (initial support) (Consumers can decide to provide the option to zoom in to see the all other features grouped "JS module", in case you really want to do something special.)
Shadow DOM (same)
Custom Elements (same)

I've pushed a change to remove svg.elements.script.type.module from the other feature so that this PR makes sense on its own.
I'll let this sit for a few days (a.k.a. weekend) to collect my thoughts on how best to handle the evolution of this feature.

I brought this up with @Fyrd on a call today and here are some things I learned:
I asked him where he might draw the line on making distinct features for feature evolution, in view of making a feature on caniuse or consuming one from web-features. After a little bit of discussion, I linked to https://github.com/web-platform-dx/web-features/pull/676#pullrequestreview-1925024614 and asked him whether he would group those things together (perhaps with an indicator of "partial implementation" until all of the pieces were satisfied) or split them. His response was, almost word for word: "Why not both?" 😄
When I pressed him a bit on how he'd decide without the help of web-features, he said that he would probably err on the side of a larger feature until (paraphrasing) 'it became a problem'. That is, he'd lump things together unless he had folks asking him for finer detail. He talked a little bit about developers asking about certain details of a given feature's support and not necessarily learning the answer until after the question was raised. Sometimes that leads to changes in what features are covered on caniuse.
But on the "both" line of thinking, I think our snapshots (and probably groups) approach was very much validated: Alexis linked to https://caniuse.com/?search=ecmascript 202, to show that he has implemented some bespoke searches on caniuse that do what is already suggested by snapshots. Heretofore unknown to me, caniuse users sometimes use the site in an exploratory way, to find out what's new in the web platform. Alexis has responded by surfacing categories, instead of trying to track support for large, only-distantly related sets of features.
To editorialize briefly, to me this suggests two things to explore:

A principle of parsimony: unless we have evidence that developers are mentally splitting (features/bundles or groups), we ought to prefer more comprehensive features and groups.
Considering the possibility of composing features (e.g., to show the status of feature A + feature B) for our authorial convenience, but deferring to consumers to decide whether to always, sometimes, or never show the composed or decomposed features.

Thank out @ddbeck and @Fyrd, that sounds great to me. I'm not sure how to implement it in this PR yet, but I like the direction.

For the purposes of this PR, the answer might just be to merge it (unless @Elchi3 thinks the evolutionary bundles are strictly necessary, in addition to the general feature shown here)? We can add more, finer-sliced features later, if they turn out to be distinct/relevant to developers.


I fill confused about the -DALP_BUILD_GENERATED=ON

Hi, I fill confused about the -DALP_BUILD_GENERATED=ON.
My concern is:

If I want to use SIMD which means I need the fastest speed during compress and decompress, do I need to set -DALP_BUILD_GENERATED=ON  in CMakeLists.txt?
if DALP_BUILD_GENERATED=OFF,  No SIMD is applied and the speed is lower,  Am I right?

Thank you very much for your amazing lossless float compression algrithm!

Hi,
Thanks for your questions!
ALP utilizes auto-vectorization to benefit the SIMD capabilities of modern hardware. This means the core library is implemented using scalar-only code, not explicit SIMD instructions. However, it achieves the same performance as implementations based on explicit SIMD.
The -DALP_BUILD_GENERATED flag is only used to benchmark the decompression speed of explicit SIMD implementations versus scalar code. This was done to show that ALP can match the speed of explicit SIMD implementations by only using scalar-code and relying on the compiler's auto-vectorization capabilities.
Your Questions:

No, you do not need to set -DALP_BUILD_GENERATED=ON to use SIMD. However, you do need to compile the ALP library with the appropriate flags. For example, on x86 with the AVX-512 instruction set, you should use the -mavx512 flag.

No, setting -DALP_BUILD_GENERATED=OFF is only for benchmarking the explicit SIMD implementation of ALP. The scalar implementation can achieve the same performance with the right compiler flags.

Conclusion:
To achieve the fastest speed using SIMD during compression and decompression, make sure to compile with the correct flags that match your hardware's capabilities. We will add this feature in the future to auto-detect the right flag within the ALP library.

Please let us know if you have more questions!

Thank you for your reply.
I understand it now.
Sincere thanks!


Center or adapt the content of the tiles?

On a large tile if the space is larger than the content, it is not centered

My initial thought here is that this can then cause a problem if the content is larger than the area.  If centered, it will stay center and you will have content cut off from both the top and the bottom.
I'll leave this open until I have a chance to explore options, but I believe I tried this previously and had that issue so I removed it.


sensu::client_service failure when cookbook > 0.6.0 (opsworks)

So sometime after the cookbook rev'd past 0.6.0, I started seeing the stack trace below.
I managed to track down the problem to this commit: 720fa2e0114c715cdf1f3389aafb7b4cbf3b6821
Having reverted it, sensu::client_service runs without issue.
[2014-01-26T12:17:12+00:00] DEBUG: Re-raising exception: Chef::Exceptions::ValidationFailed - sensu_service[sensu-client] (sensu::client_service line 20) had an error: Chef::Exceptions::ValidationFailed: Required argument service is missing!
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:113:in `_pv_required'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:69:in `send'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:69:in `validate'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:66:in `each'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:66:in `validate'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:56:in `each'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:56:in `validate'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:88:in `set_or_return'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource/lwrp_base.rb:86:in `_set_or_return_service'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource/lwrp_base.rb:80:in `service'
  /opt/aws/opsworks/releases/20131222191101_216/site-cookbooks/sensu/providers/service.rb:33:in `load_current_resource'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/provider.rb:97:in `run_action'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource.rb:617:in `run_action'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:50:in `run_action'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:82:in `converge'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:82:in `each'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:82:in `converge'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection.rb:94:in `execute_each_resource'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection.rb:92:in `execute_each_resource'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:81:in `converge'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/client.rb:404:in `converge'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/client.rb:469:in `do_run'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/client.rb:200:in `run'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application.rb:190:in `run_chef_client'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application/solo.rb:239:in `run_application'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application/solo.rb:231:in `loop'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application/solo.rb:231:in `run_application'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application.rb:73:in `run'
  /opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/chef-solo:25
  /opt/aws/opsworks/current/bin/chef-solo:16:in `load'
  /opt/aws/opsworks/current/bin/chef-solo:16
[2014-01-26T12:17:12+00:00] ERROR: Running exception handlers
[2014-01-26T12:17:12+00:00] ERROR: Exception handlers complete
[2014-01-26T12:17:12+00:00] FATAL: Stacktrace dumped to /opt/aws/opsworks/releases/20131222191101_216/chef-stacktrace.out
[2014-01-26T12:17:12+00:00] DEBUG: Chef::Exceptions::ValidationFailed: sensu_service[sensu-client] (sensu::client_service line 20) had an error: Chef::Exceptions::ValidationFailed: Required argument service is missing!
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:113:in `_pv_required'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:69:in `send'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:69:in `validate'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:66:in `each'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:66:in `validate'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:56:in `each'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:56:in `validate'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/mixin/params_validate.rb:88:in `set_or_return'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource/lwrp_base.rb:86:in `_set_or_return_service'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource/lwrp_base.rb:80:in `service'
/opt/aws/opsworks/releases/20131222191101_216/site-cookbooks/sensu/providers/service.rb:33:in `load_current_resource'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/provider.rb:97:in `run_action'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource.rb:617:in `run_action'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:50:in `run_action'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:82:in `converge'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:82:in `each'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:82:in `converge'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection.rb:94:in `execute_each_resource'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/resource_collection.rb:92:in `execute_each_resource'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/runner.rb:81:in `converge'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/client.rb:404:in `converge'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/client.rb:469:in `do_run'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/client.rb:200:in `run'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application.rb:190:in `run_chef_client'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application/solo.rb:239:in `run_application'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application/solo.rb:231:in `loop'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application/solo.rb:231:in `run_application'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/../lib/chef/application.rb:73:in `run'
/opt/aws/opsworks/releases/20131222191101_216/vendor/gems/chef-11.4.4/bin/chef-solo:25
/opt/aws/opsworks/current/bin/chef-solo:16:in `load'
/opt/aws/opsworks/current/bin/chef-solo:16
[2014-01-26T12:17:12+00:00] FATAL: Chef::Exceptions::ValidationFailed: sensu_service[sensu-client] (sensu::client_service line 20) had an error: Chef::Exceptions::ValidationFailed: Required argument service is missing!
pid 25125 exited with status 256, exit code: 1 (time=11 sec)
[2014-01-26 12:17:12] ERROR [opsworks-agent (25122)] Chef run failed with exitcode 1

Closing due to age of issue referencing a very old version of Chef. Please open a new issue if this is still an issue.


quick cleanup of appdelegate

@ahmednawar we need a bigger cleanup here, but this is a start

@derrickstaten LGTM 👍


Crash when moving out of frame

@Luxonis-Brandon reported that the reduce_rgb_latency branch crashed when he moved out of the frame on the BW1097 when running python3 test.py.
Host exception:
Traceback (most recent call last):
  File "test.py", line 120, in <module>
    y1 = int(e[0]['top'] * img_h)
ValueError: cannot convert float NaN to integer

My guess is e[0]['top'] is NaN. This didn't happen every time he left the frame.

I was not able to replicate this. Idea:
Wrap the coordinate math inside a try block and and continue on ValueError inside an except block. Print info on the error inside the except block. This will ensure the script doesn't crash if we receive a NaN value.
I'm thinking a try block versus checking if every number is not NaN as most of the time these numbers look fine and doing the check every time adds overhead. Instead, we just handle the few times where things are correct.
/cc @Luxonis-Brandon

Yes, that sounds like an ideal solution to me.  Thanks!

Closing as it might have ran via old code.


Fix edit uri in mkdocs.yaml

Describe the bug
On the mkdocs static site, when clicking on the edit page, a 404 not found is received because it redirects to the master branch that does not exist, the correction is to put it to point to the main branch.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://argocd-vault-plugin.readthedocs.io/en/stable/'
Click on 'edit'
See error

Expected behavior
Page correct in github.com
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Thanks for the contribution @ernelio! The change will only be reflected in the latest version of the docs until we release a new version.


[Bug]: account button

Contact Details
No response
What happened?
When I click on the account link that appears when logged in, or when I click on my profile picture, I encounter an error. Instead of being redirected to the expected page, an error is displayed.(I tried this on various accounts and different networks).

What browsers are you seeing the problem on?
No response
Relevant log output
I expected to be redirected to the relevant account or profile page without encountering any errors

Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct

Hey @youssefjaziri456, thank you for pointing it out.
Please link it with https://digitomize.com/u/dashboard/profile [Profile]

@youssefjaziri456 @pranshugupta54 Youssef I can help you with that

@pranshugupta54 Which page is supposed to be shown when you click on account

Hi @youssefjaziri456,
I was able to reproduce this issue on my end as well, following the steps you provided. This confirms that there is indeed a bug in the account button of the website.
I've attached screenshots below that demonstrate the issue:

Based on my testing, I can confirm that there is a bug when using the account button.

Hey @youssefjaziri456, can you simply rename the account option in dropdown to profile and redirect to /profile`

Hello @pranshugupta54 , I can take up this issue if it hasn't been assigned to anyone yet.

It's a very minor change - u just need to change the path and name

This is a very minor fix, we're re-assign due to in-activity

can you assign me?


Document Threat Vectors/Profiles

Trust Model needs to be advanced first -> Issue #28
This then provides the terminology and concepts to describe various threats and how we seek to address them. Will link to wider documentation if that exists to identify the solution.
We can however start to accumulate a list of threats to describe

Protecting guest memory from host (relates to use of TEE)
Orchestration apis (e.g. kubectl exec) (allow list of kata-agent apis)
Protecting container images requests from host tampering (relates to container pull)
Identifying the guest is as intended before starting workload (attestation combined with delivery of a secret required for access to what needs kept confidential (data or container encryption)
Protecting guest boot/root volume from host
Protecting container bundles from host interference (relates to storage #23)
Protecting persistent storage ( solution relates to storage #23)

Future Topics

Protecting secrets (kubernetes secrets)

@magowan is this issue still relevant or can be closed?
If it's still relevant to what release do you think we should map it to (mid-November, end-December, mid-February etc...)?


Missing links in this page

Description
[Enter feedback here]
The link to the PersistentAuthenticationStateProvider class (reference source)
is going to a missing page
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/server/?view=aspnetcore-8.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/server/index.md
Document ID
8da62490-e36f-8f38-8f06-d5d6bceaafde
Article author
@guardrex

Thanks @romarro ... Yes, they moved the 🧀 on that one. I'll update the link. Thanks for the report!


crosslink between Meltano docs on installation and deployment

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/842
Originally created by @dmor on 2019-07-31 21:25:58

Would be more natural for these pages to be organized near each other, and to also link to one-another

View 3 previous comments from the original issue on GitLab


[SEDONA-458] The docs should have examples for UDF

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-458. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

Add UDF examples in SQL tutorial.

How was this patch tested?
Did this PR include necessary documentation updates?

Yes, I have updated the documentation update.

@furqaankhan Note that you can run pre-commit run --all-files in your local machine to let it automatically fix all lint issues.


Import design tokens from Figma instead of XD

🧹 Tech Debt
Our documented process to get colors and sizes into nimble-tokens is to import them from Adobe XD. However the tooling for that process stopped working and we're moving away from XD towards Figma.
The Figma components spec has token values in it too: we should figure out how to import values from there instead. One option to consider is this design tokens Figma plugin.

[ ] figure out and implement new process
[ ] migrate existing tokens
[ ] document new process

I researched this during innovation days last week. You can see progress in this branch.
Takeaways:

this looks possible using the design tokens Figma plugin described above. I documented the process in a contributing document in that branch.
There are some problems that still need to be solved:

the token hierarchy from Figma isn't currently respected by our Style Dictionary generation process, which results in build errors due to tokens with identical names (e.g. "Fail>>Dark>>Fail 100" and "Fail>>Light>>Fail 100" are both called "Fail 100"). We could fix this by changing our token naming or updating the token generation script. The latter seems preferable but requires some work.
the plugin has some bugs, for example https://github.com/lukasoppermann/design-tokens/issues/197. These aren't showstoppers but if not fixed they may impact our token naming strategy.
the token names have changed between XD and Figma. This will require a one-time manual remapping of all the usages. This seems worth doing rather than going back to the less organized XD naming scheme.

We decided we still want to do this but it might make sense to wait a little while for our Figma usage to stabilize. Right now we're still filling in a lot of missing tokens/components and figuring out the right organization.

Brandon mentioned at team meeting today that he's considering renaming the meaning of tokens in Figma. A lot of the colors like "Black15" aren't actually "black at 15% opacity". It could be good to take this opportunity to make their names match their values. This will be a bigger breaking change but could be worthwhile to do as part of the transition.

It doesn't seem like a high priority to align on naming conventions, token hierarchies, etc between design and dev. It'll also be costly to adopt tooling to export/import tokens. Closing this as low ROI.


ThemeManager planned improvements, feedback wanted

Hi,
I would like to become a main contributor/maintainer for this project.
Contribution Ideas:

Update demo project (maybe add to mublazor docs)
Add more options (upcoming skeleton color for example: https://github.com/MudBlazor/MudBlazor/pull/9815)
Add presets (Default, pastel, neon,...)
Ability to load custom fonts
Exporting/importing themes (See #3)
Improve readme
Performance/stability
Diagnostics (warnings for accessibility and contrast for example)
Add tests
Make things more compact overall (dense/margin) to be able to show as many things as possible on demo page.

Would like to discuss these further here with the community.

I would like to become a main contributor/maintainer for this project. @ScarletKuro @henon

I think @henon would need your discord to discuss this.
As for the features. I think it's more to @Garderoben since he wrote 99% of the code, I'm just life supporting it.
I can only say that the most requested feature was to import/export the theme settings.

Here is a rough idea of having the drawer come up from the bottom instead.

Exporting/Uploading a json file is working, but still have some issues to work out. For exporting I would like to have multiple options.
What exports would you want?

.json file?
Copy/pasteable C# code?
.cs file?
Export just the colors as rgb/hex?

I will be away for 1-2 weeks so no coding progress will be made, but I will be sure to get respond to any feedback.

I would say you only need the json and copy/pastable C# code for the MudTheme for your project. Not sure about other formats

Not sure if you'd like to add another item to the list?  SSR support as it currently only works with CSR.

It would be nice if all the configurable colors, elevations, texts etc would be on a sample page and were manageable by the thememanager. For me the thememanager on the side would be best, since I have a 40" monitor  (wide), but perhaps you can make that configurable as well.


[OpenAI Speak] ... Stopped working a few weeks ago...

Extension
https://www.raycast.com/jian_chao_man/openai-speak
Description
Nothing happens anymore. No voice.
Steps To Reproduce
Select text, Run command, nothing happens anymore (it used to work).
Current Behaviour
Nothing happens
Expected Behaviour
Speaks the selected text

MY BAD! My Open AI credits expired. Refilling solved the issue.


It doesn't train my voice.

I followed the instruction below:
https://youtu.be/gYNCnltAHzY?si=4eAqdlQbezHR0Lpo
However, it doesn't apply to my voice, but generates a completely different voice. I have no clue what wrong is.

Is this for voice cloning/replication?

So assuming it's that - there are limitations. Are you using it for English or something else?
There are several factors - audio length, clarity, speech style - that determine if it will work.

Is this for voice cloning/replication?

Yes, as I mentioned above, I just followed the instruction and it looks like just voice cloning.

So assuming it's that - there are limitations. Are you using it for English or something else? There are several factors - audio length, clarity, speech style - that determine if it will work.

Ah, I see. I'll give it another shot. Thanks!


should raise an error when run with py2

Thanks. I'll implement this. For what it's worth, I removed the pip install instructions from the readme and highly recommend people use the Docker image.


Add LPD support for PAPPL

Is your feature request related to a problem? Please describe.
It looks like it is common for old Windows print servers in enterprise environment to by accessed by CUPS via LPD protocol instead of Samba - some people probably won't be able to upgrade to newer Windows, so it would be great to have a way how to support them within PAPPL, once LPD is removed from CUPS.
Describe the solution you'd like
If the destination is installed with port 515 (queue name might be specified as well), send the data via LPD protocol.

I am really not keen on propagating LPD support in PAPPL. The "legacy" printer applications (that wrap CUPS drivers) already bundle the CUPS LPD backend and so already support LPD that way... That covers all of the PS/PCL office printers you'd be printing to via an old Windows print server...

Ok, then the plan is to move LPD backend into pappl-retrofit. IIUC currently it uses CUPS LPD backend as it is (it uses symlink to /usr/lib/cups, so it sees backends and filters as CUPS 2.x), so once CUPS removes it, it stops working.
But if the plan would be to move them into pappl-retrofit, then we don't need it in PAPPL. @tillkamppeter is my conclusion correct, Till?


Remove unused code from the configuration migration tool

This removes code that would convert public/private keys from file to an inline version for the configuration.
The migration tool only sets the paths that are given, so there is no need to read these files and do the translation.

Codecov Report

Merging #498 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #498      +/-   ##
============================================
- Coverage     99.49%   99.48%   -0.01%
+ Complexity     1204     1195       -9
============================================
  Files           206      206
  Lines          3947     3914      -33
  Branches        204      201       -3
============================================
- Hits           3927     3894      -33
  Partials         20       20

Impacted Files
Coverage Δ
Complexity Δ

...um/tessera/config/migration/TomlConfigFactory.java
100% <100%> (ø)
9 <2> (-9)
:arrow_down:

Continue to review full report at Codecov.

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


FileNotFoundError: [Errno 2] No such file or directory: '/home/robot/catkin_ws/src/point_cloud_segmentation-master/pcs_detection/scripts/example_data/trained_hist.npy'

after catkin build sucess ,
I roslaunch pcs_ros demo.launch
`

`
the teriminal shows
Traceback (most recent call last):
File "/home/robot/catkin_ws/src/point_cloud_segmentation-master/pcs_ros/src/histogram_backprojection_node", line 53, in
server = HistogramBackprojectionServer(filepath)
File "/home/robot/catkin_ws/src/point_cloud_segmentation-master/pcs_ros/src/histogram_backprojection_node", line 23, in init
self.histogram_backprojection = HistogramBackprojection(filepath)
File "/home/robot/catkin_ws/devel/lib/python3/dist-packages/pcs_detection/models/histogram_backprojection.py", line 19, in init
self.histogram = np.load(hist_filepath)
File "/home/robot/.local/lib/python3.8/site-packages/numpy/lib/npyio.py", line 417, in load
fid = stack.enter_context(open(os_fspath(file), "rb"))
FileNotFoundError: [Errno 2] No such file or directory: '/home/robot/catkin_ws/src/point_cloud_segmentation-master/pcs_detection/scripts/example_data/trained_hist.npy'
[histogram_backprojection_node-2] process has died [pid 275489, exit code 1, cmd /home/robot/catkin_ws/src/point_cloud_segmentation-master/pcs_ros/src/histogram_backprojection_node __name:=histogram_backprojection_node __log:=/home/robot/.ros/log/1a756414-37fe-11ed-b265-b1452c6111fe/histogram_backprojection_node-2.log].
log file: /home/robot/.ros/log/1a756414-37fe-11ed-b265-b1452c6111fe/histogram_backprojection_node-2*.log

The python modules are supposed to be getting installed when you catkin build. Did you source your setup.bash after you built?

yes , i did , and it shows  FileNotFoundError: [Errno 2] No such file or directory: '/home/robot/catkin_ws/src/point_cloud_segmentation-master/pcs_detection/scripts/example_data/trained_hist.npy'
but i can't find the  file in the pcs_detection package :

I download the  pkg in the master branch

The python modules are supposed to be getting installed when you catkin build. Did you source your setup.bash after you built?

more details, after I catkin build the workspace , pcs_detection install into /home/robot/ws_tesseract_new/devel/lib/python3/dist-packages

it there has also not trained_hist.npy

Oh I see. It looks like that is the histogram that is "trained" from the dataset and used for histogram backprojection. This repo was set up to either use that or fcn8. It looks like I didn't include any of the trained models here. I'm not immediately seeing the code to generate the histogram, but you can see this example. Basically I think you want the output of roihist = cv.calcHist([hsv],[0, 1], None, [180, 256], [0, 180, 0, 256] ) saved to a pickle.


Marshal SOQL queries with OR operators between different columns

Marshal SOQL queries with OR operators between different columns.  For example, I don't believe this query is currently marshal-able:
SELECT Name,Email,Phone
FROM Contact
WHERE Title = 'Purchasing Manager' OR Department = 'Accounting'

I've been playing with an implementation that I think might work and is in keeping with the current patterns: adding an optional clause tag called joiner for whereClause.  If not set, the marshal function uses AND to join (to maintain current functionality).  If it's set to OR (case insensitive), then it will separate the clauses with OR.
type contact struct {
	Name  string `soql:"selectColumn,fieldName=Name" json:"Name"`
	Email string `soql:"selectColumn,fieldName=Email" json:"Email"`
	Phone string `soql:"selectColumn,fieldName=Phone" json:"Phone"`
}

type orSOQLQuery struct {
	SelectClause contact                `soql:"selectClause,tableName=Contact"`
	WhereClause  positionOrDeptCriteria `soql:"whereClause,joiner=OR"`
}

type positionOrDeptCriteria struct {
	Title      string `soql:"equalsOperator,fieldName=Title"`
	Department string `soql:"equalsOperator,fieldName=Department"`
}

// this would generate the soql query
soql.Marshal(orSOQLQuery{
    WhereClause: positionOrDeptCriteria{
        Title:      "Purchasing Manager",
        Department: "Accounting",
    },
})

Thanks @t-margheim for submitting the issue and corresponding PR. I think this is a great addition to this library.


Account actions should require 2FA if enabled.

[ ] Change Name (?)
[ ] Change E-Mail (also verify, #84)
[ ] Change Password
[ ] Reset Password
[x] Enable 2FA
[ ] Disable 2FA
[ ] Add Device to 2FA

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6841003-account-actions-should-require-2fa-if-enabled?utm_campaign=plugin&utm_content=tracker%2F86903&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F86903&utm_medium=issues&utm_source=github).

Invalidated as Simplet is now deprecated. See simplet.eustasy.org