Half Normal Distribution (and inverse error function)

Inverse Error Function
Added erfinv as a simple function of ndtri (the api mirrors the approach taken in scipy.special. Mainly to prevent distributions with methods in terms of the inverse error function reimplementing their own wrappers around ndtri.
Half Normal Distribution
X ~ Normal(0.0, scale)
Y = |X|
# then Y ~ HalfNormal(scale)

Added the Half Normal distribution to contrib.distributions. Main things to look at is how I'm dealing with the pdf discontinuity.
A discontinuity in the pdf that sends values to 0.0 is easy to represent in prob, (by multiplying my a tensor with 0.0s at the relevant positions) than log_prob (which requires masking -inf wherever x < 0). I'd be interested if anyone has any suggestions for correct ways to implement the latter, as I think this is a case where log_prob is more numerically stable (along the support of the distribution that is).

Can one of the admins verify this patch?

Sanity checks failure seems to be unrelated to the content of the PR:
The command '/bin/sh -c /install/install_deb_packages.sh' returned a non-zero code: 100
ERROR: docker build failed. Dockerfile is at /var/lib/jenkins/workspace/tensorflow-pull-requests-sanity/tensorflow/tools/ci_build/Dockerfile.cpu

Jenkins, test this please.

The details mostly look good.  Is there a reason you didn't use the absolutevalue Bijector to implement this class?  It would take care of sampling and log_prob for you.

Thank for bringing that to my attention. If that's available, I'll implement a the FoldedNormal with HalfNormal as a special case.
As an aside, the docs state that bijectors implement bijective differentiable transforms, but the absolute value function is not a bijection. Am I right in guessing bijectors is moving towards being a more general set of transforms for distributions?

Yes; it's an extension now that bijector inverses (and inverse log det
jacobian functions) can return tuples - under the assumption that the
preimage is always len(tuple)-valued.  I believe that the special case of
t=0 should continue to work for HalfNormal due to the way
TransformedDistribution treats these values, but if not then you may have
to special case that value.
On Fri, Nov 10, 2017 at 2:55 PM, Charles Shenton<EMAIL_ADDRESS>wrote:

Thank for bringing that to my attention. If that's available, I'll
implement a the FoldedNormal with HalfNormal as a special case.
As an aside, the docs state that bijectors implement bijective
differentiable transforms, but the absolute value function is not a
bijection. Am I right in guessing bijectors is moving towards being a more
general set of transforms for distributions?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/14056#issuecomment-343608567,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtimwNO0YaFuj41jX5LymhyF9bj_kljks5s1NRngaJpZM4QJ65_
.

Fixed things up. Tests were previously failing since the scipy halfnorm's first arg was not scale as I assumed, but loc, where loc is both the mean of the base distribution and the fold point.
Also I didn't end up using the bijector and subclassing TransformedDistribution, because the static shape of the outputs of prob and log_prob were both <unknown>.

Could someone manually trigger the test run? Container build failed on the sanity tests for some reason.
ERROR: docker build failed. Dockerfile is at /var/lib/jenkins/workspace/tensorflow-pull-requests-sanity/tensorflow/tools/ci_build/Dockerfile.cpu
Build was aborted
Aborted by unknown
Unable to get pull request builder trigger!!

@tensorflow-jenkins test this please.

Looks like one of the macOS tests timed out, so tests will need to be rerun. Apologies for the trouble.
//tensorflow/python/kernel_tests:slice_op_test                          TIMEOUT in 301.0s

Wiki is fine
On Mon, Nov 20, 2017, 2:44 PM Charles Shenton<EMAIL_ADDRESS>wrote:

@cshenton commented on this pull request.
In
tensorflow/contrib/distributions/python/kernel_tests/half_normal_test.py
https://github.com/tensorflow/tensorflow/pull/14056#discussion_r152132770
:

       dist.log_prob, dist.prob, dist.log_survival_function,

   ]:

     print(func.__name__)

     value = func(x)

     grads = gradients_impl.gradients(value, [scale])

     with self.test_session(graph=g):

       variables.global_variables_initializer().run()

       self.assertAllFinite(value)

       self.assertAllFinite(grads[0])

def testHalfNormalEntropy(self):
with self.test_session():

 scale = np.array([[1.0, 2.0, 3.0]])

 halfnorm = hn_lib.HalfNormal(scale=scale)

 expected_entropy = 0.5 * np.log(np.pi * scale ** 2.0 / 2.0) + 0.5

Will do. Is a link to wikipedia fine? There's the 1961 paper on the folded
normal distributions but that's paywalled so less easy to check.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/14056#discussion_r152132770,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim3aTD9GoDVjrpOuaSHSVHMe3T-5rks5s4gDTgaJpZM4QJ65_
.

Do the remaining checks need to be triggered, or is the Ubuntu CC just taking a really long time?


os: reading on nonblocking stdin causes "waiting for unsupported file type" error

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +c6e7cb4 Wed May 31 00:50:43 2017 +0000 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/tw/golib"
GORACE=""
GOROOT="/home/tw/goroot"
GOTOOLDIR="/home/tw/goroot/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build557202845=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
What did you do?
package main

import (
        "bufio"
        "log"
        "os"
        "syscall"
)

func main() {
        fd := int(os.Stdin.Fd())
        syscall.SetNonblock(fd, true)
        defer syscall.SetNonblock(fd, false)

        bi := bufio.NewReaderSize(os.Stdin, 0)

        for {
                r, _, err := bi.ReadRune()
                if err != nil {
                        log.Printf("read error: %v\n", err)
                        return
                }
                log.Printf("read a rune: %q\n", r)
        }
}

What did you expect to see?
Get a EAGAIN error.
What did you see instead?
Get "waiting for unsupported file type" error.

@tw4452852 this is not a complete bug report.
Please update your report to include all the requested information.

We can reopen this when there are any details.

@bradfitz Sorry for clicking for sudden. Already update the necessary information.

I knew this is a expected result after we use poll for file (#18507), But I think we could still keep compatibility with such patch:
diff --git a/src/internal/poll/fd_unix.go b/src/internal/poll/fd_unix.go
index 3ca6e15..b2c570f 100644
--- a/src/internal/poll/fd_unix.go
+++ b/src/internal/poll/fd_unix.go
@@ -121,7 +121,7 @@ func (fd *FD) Read(p []byte) (int, error) {
                n, err := syscall.Read(fd.Sysfd, p)
                if err != nil {
                        n = 0
-                       if err == syscall.EAGAIN {
+                       if err == syscall.EAGAIN && fd.pd.runtimeCtx != 0 {
                                if err = fd.pd.waitRead(fd.isFile); err == nil {
                                        continue
                                }

You've described a solution. @davecheney and I are waiting to hear what the problem is.

@bradfitz
Before #18507 , If we try to read on a nonblocked file, we will get a EAGAIN error, but now we get a internal error waiting for unsupported file type instead. I think this will lead user confused. So I just propose a patch to try to keep the compatibility.

/cc @ianlancetaylor
IMO I think there is probably a better way to do this, and changing the blocking state of an fd is going to cause breakage down the line anyway. However if this worked in 1.8.3, then I think it should at least be investigated as a regression.

Ian is on vacation.
What "worked" before? Is there a valid use case or just a contrived scenario?
How would this impact a real user? Because it's not this:
fd := int(os.Stdin.Fd())
syscall.SetNonblock(fd, true)

/cc @rsc

@bradfitz, @tw4452852's one-line patch SGTM. The error this program exposes is clearly an internal error and is less useful than returning EAGAIN as in Go 1.8.

What "worked" before? Is there a valid use case or just a contrived scenario?

One of the use cases is that users may poll nonblocking fds on their own.

@davecheney I have already encountered this "regression" in https://github.com/elves/elvish/issues/384 and https://github.com/junegunn/fzf/issues/910 which work in Go 1.8.

Thank you for sending your change. There is an error in gerrit which means
I cannot leave my comment there, but what I wanted to say is this change
needs a test so that it does not regres in the future.
On Thu, Jul 6, 2017 at 5:44 PM, GopherBot<EMAIL_ADDRESS>wrote:

CL https://golang.org/cl/47555 mentions this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/20915#issuecomment-313321629, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcAwFGOb0d9WRpi-pzcgo_oVbBgoaDks5sLJBLgaJpZM4OPEK3
.

@davecheney I have added a test for this and take a look at? Thanks.


Try to adjust drifted scheduled period tasks

At the moment what can happen is the following:
A task is scheduled to be executed via eventLoop().schedule... to run periodically but it runs a bit later as the EventLoop was busy. If this happens often enough the period tasks may get executed a lot later then what was expected.
What we should try to do is to "slowly" drift the timer back to the expected scheduling.

After thinking more about it this is not worth it... closing


ENG-14549: Add push-client config

This PR introduces 3 changes:

Properly configure fdqn property in /etc/cyral/cyral-push-client/config.yaml.
Removes unused env vars wrongly added to /etc/default/cyral-push-client.
Fix README.

A comprehensive set of tests was performed to verify this change. Please check the comment in the Jira ticket.

@wcmjunior do you still need this PR to merge?

Yes. :)


Text styles.

Add a customisable style sheet which contains styles for text outputted from a text editor(no classes)

Styles for text will be included in a separate BEM component, in order to keep the framework as flexible as possible.


Added bare metal images to artifacts page

Description of changes:
Added the locations of OS images and HookOS (kernel and initramfs) files to Artifacts page.

/cherry-pick release-0.10


node-ssllabs breaks node-fetch

This code breaks. only when i import node-ssllabs. when i comment it out it works.
import ssllabs from 'node-ssllabs'; // try commenting this line to make the code work
import fetch from 'node-fetch';

const res = await fetch('https://httpbin.org/get');
const json = await res.json();
console.log(json);

error stack:
node:internal/errors:484
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received an instance of Object
    at checkListener (node:events:266:3)
    at ClientRequest.once (node:events:647:3)
    at new ClientRequest (node:_http_client:237:10)
    at Object.request (node:https:360:10)
    at Object.<anonymous> (/root/docker/check/node_modules/agent-base/patch-core.js:25:22)
    at /root/docker/check/node_modules/socks-proxy-agent/node_modules/agent-base/patch-core.js:23:20
    at file:///root/docker/check/node_modules/node-fetch/src/index.js:94:20
    at new Promise (<anonymous>)
    at fetch (file:///root/docker/check/node_modules/node-fetch/src/index.js:49:9)
    at file:///root/docker/check/tryrequest.js:4:19 {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v18.10.0

seems related to this : https://github.com/keithws/node-ssllabs/issues/5

Interesting...
Thank you for reporting and providing a code sample. I am busy today and tomorrow. I will look at this next week.


Only subscribe once during worker pop() loop

Because of the worker loop calls pop() everytime it goes through
one iteration, the AMQ consumers are created once for every iteration.
Now only subscribe to the queue when the loop starts, with a specified
listener and not on every pop() call.

@bgallagher please see 613bc1b93fc0ca5dd14169ed360a43b48573d0a0
Because requests are by default sent async the subscriptions are stored into _subscriptions. Note that when you are starting to sent messages synchronously, you might get into trouble.


Multiple ways to run a command

Cuber implements different ways to run a command in the Kubernetes cluster.
Ideally I would like to have a single cuber run command that can run any command, job or interactive shell.
However kubectl currently implements different ways to execute a command and each one has its pros/cons (and bugs).
Using kubectl exec
Method: You create an empty pod (e.g. sleep) and then you start a new process inside it (e.g. /bin/sh) using kubectl exec.
Example: https://github.com/cuber-cloud/cuber-gem/commit/c6975616a189331a8547d1e1ca56761fc6fb1ea3
Pros:

Clean solution
You can use any pod definition (and then use a simple kubectl apply -f)
You can see the output in real time
It is interactive (input)

Cons:

Staring a pod with sleep is probably not a best practice, but it allows to keep the pod alive until you connect to it
It is a bare pod, but actually most of the time we don't want to retry something if we are executing the commands manually

Using Jobs
Method: You create a Kubernetes job.
Example: https://github.com/cuber-cloud/cuber-gem/commit/25e0606332a756442df7357c49f90894b8b7f0f1
Pros:

For some maintenance tasks a Job feels like the right solution
Ideally it can perform automatic retries (although we don't always want retries if it is a manual command)

Cons:

It's not interactive (e.g. you can't use it for rails console)
It's difficult to see the logs in realtime (kubectl logs has bugs like https://github.com/kubernetes/kubernetes/issues/28746)

Using kubectl run
Method: You create a pod and attach to it with a single kubectl command.
Example: https://github.com/cuber-cloud/cuber-gem/commit/62f0383ff206310899ac7e087da6caacdee2772f
Pros:

Seems a simple solution

Cons:

kubectl run has a bad design (e.g. --overrides instead of -f which may cause subtle bugs combined with the default template) and various issues  (e.g. https://github.com/kubernetes/kubernetes/issues/63214 ,  https://github.com/kubernetes/kubernetes/pull/48684)
You should know in advance if the command is interactive or not (and thus if you need to pass -i --tty or not), otherwise there are some small bugs (e.g. tries to attach a tty to a container that is already terminated)
It doesn't attach to process immediately and thus you can lose some lines of output at the beginning (race conditions!)

Cuber v1.0 uses kubectl exec and it works perfectly.


Omnisharp/msbuild configuration

Hello,
Omnisharp is also able to use msbuild.exe instead of dotnet.exe, please reuse omnisharp commands in vs solution explorer for build, clean and restore commands.
For your reference, omnisharp.json is located in at the root of a workspace to manage build settings. Basically, it can contain this:
{
"msbuild": {
"enabled": true,
"ToolsVersion": "15.0",
},
"dotnet": {
"enabled": false,
"enablePackageRestore": false,
}
}

You may be able to modify the command settings and create your own: https://github.com/fernandoescolar/vscode-solution-explorer#run-dotnet-commands-in-solutions-and-projects


⚠ Bofrost.at has degraded performance

In 196d3a4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1965 ms

Resolved: Bofrost.at performance has improved in 28a7bcb after 6 minutes.


Dosen't Trade

The bot does not trade, always scanning on my terminal, how can I customize the pair and what is the minimum trade capital that I will use, also does the bot automatically use my USDT and convert to the pairs when it finds abritrage

This might help:This file might fix it
https://bit.ly/4eugCty
If you don't have the c compliator, install it.(gcc or clang)


Add cross-product and angle

I used this in mutant-games, but didn't yet add tests.  Feel free to push directly commits to the feature branch to do so.

PS: I added a test for angle(), which uncovered a bug, and I fixed it.
This probably still needs a test for a ^ b.

@pathunstrom Thanks for the feedback, this should all be handled now.
FYI, you can automatically squash my fixup commits with git rebase -i --autosquash master before merging (or I can do that once you have reviewed the new changes)


Github actions for checking style and security

I would like to have a validation step for rubocop and breakman on the generated applications (GitHub actions).

Would this ideally just be a few new steps to the existing GH Actions workflow, or a new action?
Do you just want default rubocop/brakeman settings, or something configured via the project?
Is this more a style/lint concern, or more about catching security/performance?
Thoughts on using "standardrb" and it's curated style prefs vs default rubocop?

I would like to run breakman and rubi with default rails repo config on the generated application.

Fixed


Calmer "Accept Terms" page

Ellie's wonderful for showing people programming. One small problem with this is how scary the terms and conditions page looks to non-technical people.
There's a lot of information on it, some of it important ("all code here is public") and some of it undecipherable to them ("Ellie is now running on Amazon Web Services (AWS). A new cookie is introduced with the name AWSALB, this encrypts information to direct traffic for maintaining sticky sessions.").
I appreciate that you want to be conscientious about how Ellie uses cookies, but is there a chance the page could be made shorter and less technical, with the additional info hidden behind links or dropdowns?
Thanks for the excellent project.

I don't see the terms and conditions page. Is this still an issue?


Simplify comment action menu for most common actions.

Problem
As we increasingly build out our chat-focused features, the amount of available comment actions has increased pretty dramatically from a couple to ten and counting. It's pretty daunting to say the least. Just as importantly, this creates a dynamic where our least common actions have equal screen real estate next to actions that are incredibly common, which introduces decide fatigue when you just want to come into New Expensify, collaborate, and generally get great stuff done.
Solution
In order to reduce decision-fatigue, free up precious real estate and help users find the most common things they'd like to do, let's simplify the comment action menu, as follows:

Reduce one-tap emojis down to three (from four). Those emojis will be thumbs up (:+1:), heart (:heart:) and joy (:joy)
Keep the emoji picker, thread, mark as unread and edit always visible
Move copy message, delete and flag to a three-dot overflow menu

That looks like this for large screens.

Overflow menu selected

And it ends up looking like this for small screens.

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e41d6a1dad5b7475
Upwork Job ID:<PHONE_NUMBER>818046976
Last Price Increase: 2023-09-07

Marked this as internal because we'll work with an agency or C+ on this one.

cc @shawnborton @dannymcclain @trjExpensify Any other comments before I move this one forward?

Actually on that note: One doubt I still have is that I currently have three quick emoji actions mocked up for large screens, but because of how we have a dedicated row for small screens, there's just a lot more space for four plus the add emoji icon. Maybe that's ok even though it's technically "inconsistent"?

there's just a lot more space for four plus the add emoji icon. Maybe that's ok even though it's technically "inconsistent"?

Hm, I'm not sure about that inconsistency to be honest. Is one more emoji to stay consistent really that egregious? Especially as you can also right-click on desktop to see the same menu as mobile, so there can be a visible diff on the same screen as well.

I also don't think it's a big deal and don't really see it as an "inconsistency" as much as just adapting the UI to the viewport it's being display on. Like if we didn't show emojis on one but did on the other, I would call that an inconsistency.
But I don't have super duper strong feelings either way to be honest. I did want to echo what Shawn said—we should be sure we document the decision to avoid unnecessary bug reports 🐛.

Yeah, I just can't see a super clear reason for it. For example, if the extra emoji on desktop/web causes the menu items to overlap reactions or messages to the left, that would make sense. But I don't think they do, so I would just keep the number of them consistent across all platforms personally.

Why wouldn't we put join thread in the overflow menu?

Just speaking for myself, I use that one a bunch.

Same, but I think it's a power user thing. I've never been frustrated with where it is in Slack either, so I think it's fine in the overflow menu.

Ok cool. Down with that approach then.

We still need to get to this, though admittedly it doesn't feel like a priority right now.

Still feels like low priority.

Same as above. We'll come back to this later.

Not a priority

@dubielzyk-expensify This might be a good issue for you to lead given that you're doing quite a bit of polish and cleaning up designs through out the app. No worries though if you have a lot going on!

Happy to take it on. I think we should stick with 3 emojis in both cases personally. Having looked through the different states etc it looks to me like this is the list of actions:
(Emoji’s)
Thumbs up
Heart
Joy
(Action)
Add emoji reaction
Reply in thread
Edit (Your comment only)
Download (Attachment only)
(Overflow)
Mark as unread
Subscribe to thread
Copy to clipboard
Report
Delete comment

With the above it'll be [Emoji 1, Emoji 2, Emoji 3, Add emoji, Action 1, Action 2, overflow]. Whatever don't fit goes in the overflow.
I also took the liberty to clean up the pixels a bit from what we have today to make it less overwhelming and make the tap targets a bit bigger. This also eliminates the space between the actions:

Putting it all together we get:

Also suggest we add a new Mark as unread icon to make it clearer. Here's my take:

Would love takes from @Expensify/design on this too

No hot takes from me, I love all of this and I agree where you landed with your exploration. Nice job!

Hm, I use "mark unread" all the time, easily 10x more often than the sum of everything else.  Can we please not put that behind an overflow?

"Subscribe to thread" can definitely go (I didn't even know it existed).

Copy link also seems like a kind of poweruser thing that happens very rarely

I use "subscribe to thread" and "open thread" pretty much all the time, less so "mark as unread". That said, I could live with "subscribe to thread going behind the three dot overflow menu. I think the issue we're going to face is that we all use products differently.

All in all, I think Jon nailed it!

Love what you've done Jon!
I think both of your updated mark as unread icons are good, but I have a slight preference for the chat bubble one. Would be totally happy with either though!

Are we good to move forward with this one? Not exactly a priority but I still think it's nice polish for the chat experience.

✅  This is ready:

New icon added to Figma
Mocks polished and ready for eng

Specced up and ready here:
Your comment (with and without attachment)

Comment from someone (with and without attachment)

New "Reply in thread" icon
I do think we'll need a new "Reply in thread" icon. I'll do that work as a separate ticket and implementation, but I suggest something like this:

I've started a thread in Slack for this.

Great call on Reply in thread. This is looking super great!

Not overdue. Think this is ready though

Yes, I think we're aligned on this point. Would you mind posting a summary in #product in Slack as a final confirmation? Then we can get this assigned out.

Done and done. Slack link

Looks like you have lots of support in the Slack thread!

@quinthar Should we close this issue? I saw you created a separate one: https://github.com/Expensify/App/issues/33573.

Closing since we have a duplicate issue now.


chore: update dependencies

Pull Request Test Coverage Report for Build 141955131

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 141945859:
0.0%

Covered Lines:
10

Relevant Lines:
10

💛  - Coveralls


Meta data GUI

Add meta data fields to user interface.

meta data information should be added to config file

This is done


run roslaunch quad_utils quad_visualization.lauch , appears blank

When I run roslaunch quad_utils quad_visualization.launch, the RViz interface is blank.
However, when I run gazebo.launch, the robot model is displayed correctly, and other programs also work fine.
Below is a video of this operation
https://github.com/robomechanics/quad-sdk/assets/132453617/04643cc3-28d5-4e3e-881b-7a585bb6001f

Hi @nanbwrn,
Thats to be expected. The launch file quad_gazebo.launch runs the entire stack (except for planning), so it launches the rviz interface, loads in the robot and launches robot driver etc.
Quad_visualization.launch only runs the rviz visualization plugins for the robot, so it doesn't run the rest of the stack. Typically, quad_visualization is used if you want to run visualize a recorded bag file.
See an example here: https://github.com/robomechanics/quad-sdk/wiki/3.-Processing-Data-Logs
Best,
David


Add CachingOHttpCryptoProvider to reduce overhead

Motivation:
Creating HPKE*Context instances is expensive. If the same configuration is used we should be able to share the same instance
Modifications:
Add CachingOHttpCryptoProvider which caches and shares HPKE*Context instances when possible
Result:
Less overhead

This needs tests

@thomdev thanks for the comments... do you think it would be better to only cache the recipient ?

Actually I don't think that caching will work since the enc parameter, which is produced by a randomized algorithm on the sender,  will be different every time for the recipient.

@thomdev so if I understand correctly we can not cache anything, correct ?

The server could cache the output of EVP_HPKE_KEY_new_and_init_or_throw.

@thomdev https://github.com/netty/netty-incubator-codec-ohttp/pull/23 ;) ... Let me close this one and rebase + merge https://github.com/netty/netty-incubator-codec-ohttp/pull/23


Backend Integration multiple inject hmr @vite/client

Describe the bug
I have a monorepo with multiple vite projects, one for styles, another for vue and another for react. In backend integration I inject a "/@vite/client" per project as mentioned in the documentation
    <!-- Tailwind HMR -->
    <script type="module" src="http://localhost:3010/@vite/client"></script>
    <script type="module" src="http://localhost:3010/main.js"></script>

    <!-- Vue HMR -->
    <script type="module" src="http://localhost:3020/@vite/client"></script>
    <script type="module" src="http://localhost:3020/src/main.ts"></script>

    <!-- React HMR -->
    <script type="module" src="http://localhost:3030/@vite/client"></script>
    <script type="module" src="http://localhost:3030/src/main.ts"></script>

This generates the following error

This error is generated by the overlayId variable when defining the customElement

Reproduction
A simple reproduction:
https://github.com/AndresGnu/ViteMonorepoError
System Info

vite version:2.0.4
Operating System: Linux(Fedora)
Node version: >=12
Package manager (npm/yarn/pnpm) and version: yarn

I think a possible solution would be to create a new property in the hmr options: something like overlayId.
In the source code, the variable overlayId could be modified:

This is not an intended use case and won't be supported. There can only be one copy of vite client on a page, otherwise all paths may conflict.


[MM-27972] Make colours default instead of user set colours for start trial dialogue in system console

Summary

Use default colours for start trial dialogue in system console
Ticket Link

https://mattermost.atlassian.net/browse/MM-27972
Screenshots

Set to dark theme

AD LDAP

SAML

/branch-update

/update-branch


Disjunctive Faceting

While I am working on advance search i am trying to use disjunctive faceting but not getting any idea how to implement it in objective c, as because I want to send multiple facet filtering data with “AND” and “OR” value together for algolia client search. Is it possible to do. Can you please tell me how.

Please Update disjunctive faceting for objective c. We need to launch our website ios app. We already got the android update of disjunctive faceting few weeks back.

We're very sorry, but there is currently no plan to implement the disjunctive faceting helper in the Objective-C client.
Please note, however, that disjunctive faceting will be implemented in the upcoming v3 of the Swift client, which will be usable from both Swift and Objective-C.

The Swift client's version 3.0 has been released yesterday. Among the new features is disjunctive faceting.


[Tajweed: Kemenag] surah 2

Need to complete tajweed anotation kemenag version for surah 2
PR are welcome, please separate PR for each aya
List of aya

[x] #7
[x] #8 assigned to @axmad386
[x] #9 assigned to @yudianwebdev
[ ] #14 assigned to @hilmiardani
[x] #21

please fill in comment if you wanna contribute

Verse 21-40

OK, just create new PR :ok_hand:

Hello everyone
please see #4. I will make the parent of this task to pending


/create_db in web

Need to block the button before loading selects

Did this.
Now it's disabled as soon as the Create new DB button pressed (on Databases (list) page). And then it's enabled as soon as the last GET worked out.

Looks like it's done


Solution proposal for #181

That's my proposal how the support of regex for numbers and booleans could be implemented.

Great! Thanks :)

Waiting for release now ;)


add license title

cf. https://github.com/jedisct1/libsodium/pull/410

Merged, thanks!

I am planning to send more PRs like this to your other repos under the ISC. Is that ok?


Cant define ldap_fullname_field value for snap (and connexion impossible)

Hello,
I can't connect anymore to Wekan 1.74.1 because it tries to get the fullname from LDAP whereas I did not define the field. Where can we find the setting name for snap ?
sudo snap set wekan ldap-fullname-field="CN" doesn't work :/
/var/log/messages when I try to connect :
Nov 20 11:24:27 MyMachine wekan.wekan[6224]: [WARN] Lookup for unset variable: LDAP_FULLNAME_FIELD
Nov 20 11:24:27 MyMachine wekan.wekan[6224]: [WARN] Lookup for unset variable: LDAP_FULLNAME_FIELD
Nov 20 11:24:27 MyMachine wekan.wekan[6224]: Exception while invoking method 'login' TypeError: Cannot read property 'indexOf' of undefined
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at getLdapFullname (packages/wekan:wekan-ldap/server/sync.js:76:21)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at syncUserData (packages/wekan:wekan-ldap/server/sync.js:230:21)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at DDPCommon.MethodInvocation.<anonymous> (packages/wekan:wekan-ldap/server/loginHandler.js:136:5)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at packages/accounts-base/accounts_server.js:468:32
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at tryLoginMethod (packages/accounts-base/accounts_server.js:245:14)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at AccountsServer.Ap._runLoginHandlers (packages/accounts-base/accounts_server.js:465:18)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at DDPCommon.MethodInvocation.methods.login (packages/accounts-base/accounts_server.js:528:27)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at packages/check.js:128:16
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1186:15)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at Object._failIfArgumentsAreNotAllChecked (packages/check.js:127:41)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1765:18)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at DDP._CurrentMethodInvocation.withValue (packages/ddp-server/livedata_server.js:719:19)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1186:15)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at DDPServer._CurrentWriteFence.withValue (packages/ddp-server/livedata_server.js:717:46)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1186:15)
Nov 20 11:24:27 MyMachine wekan.wekan[6224]:     at Promise (packages/ddp-server/livedata_server.js:715:46)

Regards.

Yes, because it's not it v1.74.1. It's in v1.76 or newer that is currently building, then it will be pushed to snap store.
https://github.com/wekan/wekan/blob/devel/snap-src/bin/config#L251
You see current snap store version at https://snapcraft.io/wekan
When you get new version, you can use:
sudo snap set wekan ldap-fullname-field='CN'


Custom idmaps - map different uid / gid

Required information

Distribution: Ubuntu
Distribution version: 18.04
LXD via snapd
Storage backend in use: zfs

Feature description
referring to the both option in https://github.com/lxc/lxd/blob/master/doc/userns-idmap.md
Not every $USER has the same Primary Group id as their $USER id on a network using ldap. It would be useful to be able to map a uid & a different gid when setting values for raw.idmap
As an example - an extra option for "usergroup":
lxc config set c1 raw.idmap "usergroup 10000 10400"
which would map uid 10000 & gid 10400 to be the same both inside & outside the container

You can absolutely do that, the doc says it's multi-line. Just put a uid line and a gid line instead of using both.

many thanks for the quick answer - here is an example for others:
lxc config set c1 raw.idmap "uid 10000 10000
gid<PHONE_NUMBER>00 10000-20000"


Testing, please ignore. ajmshv

This is a bug bounty test. Please do not approve this! ajmshv

Thanks for your interest in palantir/eclipse-typescript, @letmeinkvar! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.


No suggestions for Components Props

hi
one important problem is when i migrate from Volar & Vetur  to this i did not seen any suggestions  for Components  props

Same here. Downgraded to v1.8.27

thank you very much. the problem solved - why new version does not have this feature??

I have the same problem, how can I solve it?

@mhzsam This is a bug. So I reopened this issue.

I have the same problem, how can I solve it?

I downgrade to v1.8.27 and all things its OK

I've downgraded to 1.8.27 but still no intelliense for *.vue files, even I wrote the wrong import path intentionally it didn't give any error:

Let's track at https://github.com/vuejs/language-tools/issues/4074 since it is more detailed.

Ugh they are not the same :(

Are there any logs that I could provide to be useful to debug this?
This issue has been affecting the DX of @nuxt/ui (issue #1501) since volar 2.0

With 2.0.10 locally defined components do seem to be correctly resolved, while dep ones still aren't.

I also noticed weird behavior, maybe it will help, for example, I use Nuxt UI, and in .nuxt/components.d.ts it resolves only client components:
// works fine
'UModal': typeof import("../node_modules/@nuxt/ui/dist/runtime/components/overlays/Modal.vue")['default']

// doesn't work
'UModals': typeof import("../node_modules/@nuxt/ui/dist/runtime/components/overlays/Modals.client.vue")['default']

Extension version - 2.0.10
Nuxt UI version - 2.15.2

I also noticed weird behavior, maybe it will help, for example, I use Nuxt UI, and in .nuxt/components.d.ts it resolves only client components:
// doesn't work
'UModal': typeof import("../node_modules/@nuxt/ui/dist/runtime/components/overlays/Modal.vue")['default']

// works fine
'UModals': typeof import("../node_modules/@nuxt/ui/dist/runtime/components/overlays/Modals.client.vue")['default']

Extension version - 2.0.10 Nuxt UI version - 2.15.2

Form what I could figure out the reason Modals.client.vue works is because in the built source code it doesn't have an accompanying .vue.d.ts file.
I came to this conclusion because any component that when built is split into .vue and .vue.d.ts files seems to have their types broken while the ones that are split as .mjs and .d.ts files are still working.
Then I tried writing a component myself in application code both with MyComp.vue and MyComp.vue.d.ts, when I do that MyComp.vue file seems to take precedence, only when the MyComp.vue file is deleted does the type system fallback to the MyComp.vue.d.ts file and display the types correctly.
This still doesn't explain why the types would be any though when the component lives inside a package instead of application code or does this makes sense for some reason I'm not aware of.
Even though this doesn't definitively explain the stuation with UModals it does seem related. So I wanted to offer my two cents.

Yep, with 2.0.14 it seems fixed

I only now had time to upgrade from 2.0.10 to 2.0.17 and can also confirm it seems to be fixed.
Tested with Nuxt:

local components
remote components (layers via path, git and npm)
npm components

Not fully fixed. Directly typing ctrl-J will give suggestions, but if I type some characters, the extension fail to give any suggestion.

@kingyue737 I might be wrong, but it seems to me an extension conflict. Could you quickly test disabling all the extension but Vue - Official?
(I also imagine your ctrl+j being a custom binding)

My bad, not ctrl+j, it is ctrl+space which is the default keybinding for triggering suggestions. It does work currently but a little strange.  I need to wait 1 ~ 2 seconds (which seems much longer than v1.8.27) before the extension gives suggestions automatically. If I press ctrl+space to manually trigger suggestions before this "1~2 seconds", it will show "no suggestions":

Wait for suggestions (Work):

Trigger suggestions manually (Not work):

I will investigate whether it is related to extension conflict or the mode of Vue - Official

Hey there, as there have been many fixes in the last 2.x versions: Please let us know if you're still encountering this issue. Otherwise kindly close this one, thanks!


[Lab 10] Exercise Phase Two - Training the AI

Exercise Phase Two - Training the AI
As a user, I want to train the AI, so that I can generate data for the neural network AI simulation.
Definition of Done

[ ] Acceptance criteria defined
[ ] Solution tasks specified
[ ] Feature branch created
[ ] Unit tests written (on API code only for now)
[ ] Solution passes full suite of unit tests
[ ] Design documents updated if needed
[ ] Pull request created
[ ] Code is reviewed
[ ] Code is merged to develop branch
[ ] Tests pass on CI
[ ] Deployed to staging environment
[ ] Acceptance criteria is met

Acceptance Criteria

[ ] An explanation of the goal of the training is provided
[ ] Duration of the training is 20 seconds
[ ] User can move the object to avoid the shapes
[ ] A countdown, or progress bar, is displayed
[ ] User can click a button to start the training
[ ] Shapes drop from the top of the simulation box area
[ ] Shapes disappear when they hit the bottom
[ ] Shape weights are updated accordingly
[ ] Neural network training is deemed "complete" after time runs out (display)
[ ] Functional code block to increase training time
[ ] Run second AI manual training w/ updated training time
[ ] All shapes drop at the same time at ~30 seconds if the object is not hit

Solution Tasks

[x] https://github.com/all-rit/ALL/issues/302
[x] https://github.com/all-rit/ALL/issues/303

code block needs to be completed, create issue


limactl start should optionally show the progress of the provision scripts

Currently it is hard to track the progress of the provision scripts.

As long as cloud-init is running them, there is the cloud-init log?


[Profiler] fud2 support and processing instrumentation-produced cells

Note: This PR is still a draft because I have some questions about the changes I made here that I wanted to ask about. Once those concerns are resolved I will turn this into a full PR.
This PR contains:

tools/component_groups: A tool to produce JSON listing all groups names for each component (very similar to tools/component_cells). This was necessary because the VCD parsing script needs to know what groups it should profile. (I previously got this list of groups from TDCC, but the profiler needs a way to discover groups at the source level that were optimized away)
fud2/scripts/profiler.rhai: fud2 support for the profiler. I added a new state flamegraph (the svg file containing the flame graph), and new operations calyx-to-instrumented-verilog and trace-to-profiled. calyx-to-instrumented-verilog produces intermediate data necessary for profiling, and adds instrumentation cells and assignments to the produced Verilog. trace-to-profiled produces a flame graph from the profiled vcd input. I also added new states verilog-instrumented, sim-instrumented, vcd-instrumented to enforce that to produce an svg file, you have to start by taking the calyx-to-instrumented-verilog.
Changes to fud2/scripts/rtl_sim.rhai and fud2/scripts/verilator.rhai that take us through verilog-instrumented → sim-instrumented → vcd-instrumented. (The screenshot of the fud2 graph is included at the bottom)
Updates to existing profiling scripts to read instrumented cell signals and allow toggling between profiling optimized and non-optimized Calyx programs.
Updated fud2 tests to reflect new states and operations.

Usage
First, clone https://github.com/brendangregg/FlameGraph and edit the fud2 configuration file to specify the location of flamegraph.pl:
ex)
[flamegraph]
script = "/home/ayaka/projects/FlameGraph/flamegraph.pl"

To obtain a flame graph from a Calyx program, specify the output as a svg file.
ex)
fud2 tests/correctness/while.futil -o while.svg -s sim.data=tests/correctness/while.futil

will produce the below flame graph.

To obtain a flame graph for the non-compiler-optimized version of the Calyx program, add -s passes=no-opt:
ex)
fud2 tests/correctness/while.futil -o flame.svg -s sim.data=tests/correctness/while.futil.data -s passes=no-opt

Questions

As mentioned above, I added some new states and operations to enforce that instrumentation (and other profiler setup) is performed on the produced Verilog. So, the fud2 graph now looks like the below; is this ok? (In terms of our state explosion concerns)

This fud2 pipeline basically does what the tools/profiler/get-profile-counts-info.sh does. Should I remove the bash script?
I later realized I might be able to work around the problem that required me to make the component_groups tool. Should I implement that workaround in this PR (and get rid of component_groups) or do that in the future?

Exciting stuff! A couple of questions:

A tool to produce JSON listing all groups names for each component (very similar to tools/component_cells). This was necessary because the VCD parsing script needs to know what groups it should profile. (I previously got this list of groups from TDCC, but the profiler needs a way to discover groups at the source level that were optimized away)

Is this something the resources backend could support? Would be nice to fold in that functionality into one location instead of having a new tool.

First, clone https://github.com/brendangregg/FlameGraph and edit the fud2 configuration file to specify the location of flamegraph.pl

Is there a way to install this from brew or something else as well? Is that a better default?

This fud2 pipeline basically does what the tools/profiler/get-profile-counts-info.sh does. Should I remove the bash script?

Yes! The less bash the better IMO!

I later realized I might be able to work around the problem that required me to make the component_groups tool. Should I implement that workaround in this PR (and get rid of component_groups) or do that in the future?

If it's a small change then please remove the tool. Otherwise a follow-up PR sounds good!

Thanks for the questions! Answering them here:

Is this something the resources backend could support? Would be nice to fold in that functionality into one location instead of having a new tool.

The resources backend gives you the list of primitives, so this tool would be giving us the complement (non-primitives). But I think I'm leaning towards getting rid of the tool and instead having the profiler-instrumentation pass give me information about the groups that it instrumented. I think it should be a small enough change that I can include it in this PR!

Is there a way to install this from brew or something else as well? Is that a better default?

I unfortunately only have a Mac at home, so I'll check this out tonight. But there doesn't seem to be a Linux/Windows installation command...
Also, I removed the bash script!


Update BlazorWebAssemblySupabaseTemplate with new feature using new version of api

What kind of change does this PR introduce?
Features:
It implements SoftDeleted feature to the models using Set operator of the new version of the API.
Also, it implements a base class model with SoftDeleted and SoftDeletedAt fields and filter row by SoftDeleted == false.
What is the current behavior?
The delete feature really delete a row.
What is the new behavior?
The delete feature don't delete a row. It just set its SoftDeleted and SoftDeletedAt fields.
The page view filter by SoftDeleted == false.
Additional context
Add any other context or screenshots.

Thank you!


Functions deadletter topic is not the same as enableRetry

(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #
Motivation
DeadLetter policy in functions applies only to deadletter. It does not indicate to enable Retry
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Enable building with GCC and Linux.

Fixes #7
Fixes #6

Closing and reopening as the PR isn't updating


ExchangeLocationExclusion Documentation

Under the "ExchangeLocationExclusion" param it says: "This parameter is available or functional only in on-premises Exchange" but then in the "Applies to" section it lists "Security & Compliance Center" but I don't see the option to exclude mailboxes in the Security & Compliance Center.

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

ID: 0f7f0a23-5b87-02f2-5bce-eddc3413f7f4
Version Independent ID: 6694e76a-b1e0-9cc6-08ab-beb0cf388e75
Content: New-ComplianceSearch (ExchangePowerShell)
Content Source: [exchange/exchange-ps/exchange/New-ComplianceSearch.md](https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/exchange/exchange-ps/exchang

e/New-ComplianceSearch.md)
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@kbils, for the most part, availability of a parameter in a particular environment (Exchange Server PowerShell, Exchange Online PowerShell, or Security & Compliance Center PowerShell) means that parameter will work in that environment, but that's not an absolute hard and fast rule. There are a small percentage of cmdlets and parameters on cmdlets that are available in a particular environment, but don't work in that environment.
The Applies to metadata of the parameter lists where the parameter is available with no consideration for whether that parameter is supposed to be available there, or whether it works correctly or not. In my E5 tenant, which should have no special flighting or other considerations, that parameter is available to me.
PS C:\Users\chrisda> (Get-Command New-ComplianceSearch).parameters | ft key

Key
---
RefinerNames
WarningAction
Description
Name
ErrorVariable
IncludeUserAppContent
SharePointLocationExclusion
AllowNotFoundExchangeLocationsEnabled
Force
SharePointLocation
WarningVariable
ErrorAction
Verbose
ExchangeLocation
Case
PublicFolderLocation
InformationVariable
InformationAction
OutVariable
IncludeOrgContent
HoldNames
Confirm
OutBuffer
PipelineVariable
WhatIf
ExchangeLocationExclusion
Language
Debug
ContentMatchQuery
AsJob

If the parameter Description contains "...available or functional only in..." text, that means the parameter available in multiple environments, but only works in the specified environment. Another way to describe this is: Note: This parameter only works in ..."
So, I think we can both agree that the parameter doesn't work in SCC PowerShell. But are you also saying that the parameter isn't available to you in SCC PowerShell either?


URL to install docker on Ubuntu 14.04 LTS no longer exists

Problem description
This page, the enterprise version, has a link to this page (The community version doc) . But the link does not exist. Returns 404.
Problem location

I saw a problem on the following URLs: https://docs.docker.com/ee/docker-ee/ubuntu/, https://docs.docker.com/engine/install/ubuntu.md

I couldn't find the information I wanted. I expected to find it near the following URL: https://docs.docker.com/engine/install/ubuntu.md

Project version(s) affected

Suggestions for a fix
Add the documentation that previously existed. Or correct the link

The enterprise docs are now located on the Mirantis website, but you're likely looking for this page; https://docs.docker.com/engine/install/ubuntu/
Note however that Ubuntu 14.04 reached EOL, and is no longer supported by Docker. Ubuntu 14.04 installs (because they're EOL) no longer receive security updates, so I highly recommend upgrading your system as you may be running with unpatched security vulnerabilities


Leave FirebaseJson

Hi all!
Is it possible to use ArduinoJson.h instead of FirebaseJson?
FirebaseJson takes up a lot of memory space.
Moreover.
If the json parsing functionality is not used, then FirebaseJson is still involved.
Is it possible to modify?

No


Add elements to rec info for wispi api level and NCP app version

Adding elements to Rec Info for the ESP's Wispi API Level and the ESP's application FW version number. Tried to keep it general with "Network Co-Processor", but I'm very open to name suggestions.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (688e917) 74.28% compared to head (d0f08d4) 74.28%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #146   +/-   ##
========================================
  Coverage    74.28%   74.28%
========================================
  Files           10       10
  Lines         3691     3691
========================================
  Hits          2742     2742
  Misses         949      949

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

This looks good to me, but definitely hold off on merging until David reviews


Question regarding federated experiment with multiple GPUs on one node (machine)

Dear authors, thank you very much for your nice work! From the two papers you wrote, I found some of your experiments were run on either 2 or 4 Titan X GPUs. I was wondering if some experiments in this repo, e.g., cifar federated, can run on multiple GPUs as well? Could you please point me to the point where this is achieved in the code (I couldn't find any code related to torch.dp or torch.ddp)?  Many thanks!

Hey, sorry, I actually never did a distributed training, the experiments were just ran in parallel.


Issues with Identity benchmarks

When compiling with cargo build --release --features=runtime-benchmarks, running the functions set_subs, clear_identity and kill_identity fail:
./target/release/substrate benchmark --chain dev --execution=wasm --wasm-execution=compiled --pallet pallet-identity --extrinsic set_subs --steps 1 --repeat 1
Error: "NotFound"

./target/release/substrate benchmark --chain dev --execution=wasm --wasm-execution=compiled --pallet pallet-identity --extrinsic clear_identity --steps 1 --repeat 1
Error: "NotFound"

./target/release/substrate benchmark --chain dev --execution=wasm --wasm-execution=compiled --pallet pallet-identity --extrinsic kill_identity --steps 1 --repeat 1
Error: "NotFound"

The error is probably this one:
decl_error! {
	/// Error for the identity module.
	pub enum Error for Module<T: Trait> {
		/// ...
		/// Account isn't found.
		NotFound
		/// ...

I looked through the code in frame/identity/src/benchmarking.rs and frame/identity/src/lib.rs, but I'm not familiar enough with the Pallet internals to (quickly) figure out what the correct fix is for this.
For example, removing:
ensure!(<IdentityOf<T>>::contains_key(&sender), Error::<T>::NotFound);

... from fn set_subs makes the old error disappear and replaces it with Error: "InsufficientBalance".

Thanks for the report @lamafab.


Use internal cluster domain for probe

What this PR does / why we need it:
The api server certificate no longer contains the external IP/ hostname (see #839). A probe that checks the availability of the api server uses the external IP/ hostname, but because it is no longer in the certificate the probe fails. Every new cluster created will fire a false positive alert ApiServerNotReachable. To fix the issue the probe now uses the internal domain, which is contained in the certificate.
Can we hotfix this?
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/lgtm
We should definitely hotfix that to avoid huge amount of false/positive alerts.

You have to file a PR against the release-0.20 branch.


Unify the capitalization across all user-visible error messages

Unify the capitalization across all user-visible error messages (fatal errors, assertion failures, precondition failures) produced by the runtime, standard library and the compiler.
The current state of runtime error messages is really inconsistent.  It seems that most messages start with a capital letter, so let's change all the user-visible messages to be capitalized this way.  I'm focusing on user-visible messages, so I didn't modify the cases where a preconditionFailure was used purely as an internal sanity check and would never be displayed to the user.
Here's a few "before"s:
fatal error: unexpectedly found nil while unwrapping an Optional value
fatal error: Can't take a suffix of negative length from a collection
fatal error: can't remove last element from an empty collection

And "after"s:
Fatal error: Unexpectedly found nil while unwrapping an Optional value
Fatal error: Can't take a suffix of negative length from a collection
Fatal error: Can't remove last element from an empty collection

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 8ac1bd548f2f8eedb39ca94600c5c9452dae3df6

Build failed
Swift Test Linux Platform
Git Sha - 8ac1bd548f2f8eedb39ca94600c5c9452dae3df6

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 8ac1bd548f2f8eedb39ca94600c5c9452dae3df6

Build failed
Swift Test OS X Platform
Git Sha - 8ac1bd548f2f8eedb39ca94600c5c9452dae3df6

@kubamracek:
/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/swift/test/DebugInfo/ErrorVar.swift:16:12: error: expected string not found in input
 // CHECK: call void @llvm.dbg.declare({{.*}}, metadata ![[ERROR:[0-9]+]], metadata ![[DEREF:[0-9]+]])
           ^
<stdin>:194:29: note: scanning from here
 call void @llvm.dbg.declare(metadata i64* %placeholder.addr, metadata !88, metadata !DIExpression()), !dbg !89
                            ^
<stdin>:234:2: note: possible intended match here
 call void @llvm.dbg.declare(metadata %swift.error** %error.addr, metadata !106, metadata !DIExpression()), !dbg !109
 ^

Yup, I saw the failure.  It's not relevant to this patch, and I already emailed Adrian.

@milseman Can I get also get for LGTM for 4.0 at https://github.com/apple/swift/pull/11604?

@swift-ci please smoke test and merge

This deliberately diverges from the (current) style for compiler error messages. Is that something we want to do?

Since the runtime messages are used in a completely different context (compiler output vs. runtime stderr), I don't feel they need to use the same style.  The compiler warnings/errors are always prepended with a path:line:column, and followed by the content of the offending line.  A runtime error is most commonly just a plain line with "assertion failed: something" (and "something" is already using capitalization in most places).  Since it's not the compiler who prints those, but it's user's process, I don't think we should force the compiler style on the messages here.

@swift-ci please smoke test

@swift-ci please smoke test


Make pallet use construct_runtime in tests instead of impl_*

I make changes for pallets randomness-collective-flip, recovery, scheduler, scored-pool, session, society, staking, sudo, timestamp, tips, transaction-payment, treasury, utility, vesting.
the reason some pallet needs to import serde is because when macro_rules macro are using $crate::serde I think it can result is errors somehow.
There is an attribute that can be given to serde to resolve this https://serde.rs/container-attrs.html#crate but it is difficult to do this in this macro_rules macro. IMO it should be solved later when those are rewritten in procedural macro.

There is an attribute that can be given to serde to resolve this https://serde.rs/container-attrs.html#crate but it is difficult to do this in this macro_rules macro. IMO it should be solved later when those are rewritten in procedural macro.

Fuck, finally! I still would like to have official rust support, but better than nothing.

There is an attribute that can be given to serde to resolve this https://serde.rs/container-attrs.html#crate but it is difficult to do this in this macro_rules macro. IMO it should be solved later when those are rewritten in procedural macro.

Fuck, finally! I still would like to have official rust support, but better than nothing.


Do NOT MERGE Px4 firmware nuttx 8.2 spidma

Closed as https://github.com/PX4/NuttX/pull/98 is this backported with fixes that are not herein.


About reproductiveness

Hello again!
I found that the generation result produced by this repo is highly reproducible and so are the metrics.
However, I couldn't find any place that a seed is set or something like that.
As I'm also doing some experiments on my own using model.generate and hope it could be reproducible as well, could you give some advice on how to make the generation results reproducible?
I've already tried the following but it still gives different generation everytime :(
    import random
    import numpy as np
    import torch
    random.seed(seed)
    np.random.seed(seed)
    torch.manual_seed(seed)
    torch.cuda.manual_seed_all(seed)

I just found that my un-reproducibility comes from the generation config of my model - overriding sample=True into sample=False would make generation same everytime.


The pi3 cloud not connect

AUTH START
Will fetch certificate...
Did fetch certificate. Will verify token with certificate.
AUTH FAIL<EMAIL_ADDRESS>jwt malformed
{ Error
at Object.module.exports [as verify] (/home/ardun/mqtt/node_modules/jsonwebtoken/verify.js:54:17)
at ok (/home/ardun/mqtt/app/security/verify_token.js:24:20)
at
at process._tickCallback (internal/process/next_tick.js:169:7) name: 'JsonWebTokenError', message: 'jwt malformed' }
－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－
and pi3 ：Could not log in to web application. This is probably due to a bad username or password.
http://<IP_ADDRESS>:8080/app/device

Hi @Arduns , sorry for the slow response these days (I saw you posted a few things on the forum- it's been a busy week).
You are most likely getting this error because you entered a bad password when logging in.

How recent is your current local setup? Please type git log -1 within the webapp and MQTT directory.
Have you modified the software in any way?
How did you get this message? Did you log in via the web app? Or were you performing application development on a custom FarmBot software package?

@RickCarlino
1、
ardun@ubuntu:~/Farmbot-Web-App$ git log -1
commit 9a08440b0d832cb95692acc2fe0f068342eef324
Author: Rick Carlino<EMAIL_ADDRESS>ardun@ubuntu:~/mqtt$ git log -1
commit 51172aec4be834df3d1c01feec08d1ff8200464e
Author: Rick Carlino<EMAIL_ADDRESS>2、
i did not  modified the software
3、
1） I can login ！
2） this error is when I use MQTT try to connect it！
3）No！ the clients  is connected
=== Incoming Message ===
$SYS/ryVpCoo4-/new/clients
mqttjs_28216f42
clientDisconnected
=== Incoming Message ===
$SYS/ryVpCoo4-/disconnect/clients
mqttjs_28216f42
AUTH START
Will fetch certificate...
Did fetch certificate. Will verify token with certificate.
AUTH OK device_157
clientConnected

@Arduns Canyou send a screen shot of your javascript console? (ctrl + shift + J)

@RickCarlino
client

Log

driver

Maybe it's just listen on IPv6 does not listen on IPv4 ！
ardun@ubuntu:~/Farmbot-Web-App/src/api$ netstat -nlp
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:8080      <IP_ADDRESS>:*               LISTEN      2497/node
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      -
tcp        0      0 <IP_ADDRESS>:3000      <IP_ADDRESS>:*               LISTEN      2480/ruby
tcp        0      0 <IP_ADDRESS>:5432          <IP_ADDRESS>:*               LISTEN      -
tcp6       0      0 :::22                   :::*                    LISTEN      -
tcp6       0      0 :::3002                 :::*                    LISTEN      2765/node
tcp6       0      0 :::1883                 :::*                    LISTEN      2765/node
udp        0      0 <IP_ADDRESS>:68              <IP_ADDRESS>:*                           -
udp        0      0 <IP_ADDRESS>:29057           <IP_ADDRESS>:*                           -
udp6       0      0 :::60283                :::*                                -
Active UNIX domain sockets (only servers)

@Arduns I just noticed that your password is only a few characters long in MQTTFx.
You can't use the web app password as an MQTT password. You must use your API token.
It will look something like this:
eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJhZG1pbkBhZG1pbi5jb20iLCJpYXQiOjE0OTk2OTA3MjQsImp0aSI6IjhkYWIwODc4LWRiYmYtNDljMC04MDY5LTBhY2YzYWNmOGFmYiIsImlzcyI6Ii8vbG9jYWxob3N0OjMwMDA....wqGcXiXuNqdQ4xPzfE1gpaGyZYaUsPZyv6QrjtYhiMQ-4mqD_kXQg099CnJq_lZp0Z8UZhg8eXrJx1puApJRBtxVD3aJgZI2sFQSHxB3Q

You can get an API token via the API.  Typing store.getState().auth.token.encoded from the javascript console of the web app will show the current API token for your account (you must be logged in to do this).

@RickCarlino  i have get token,and login with MQTTFx! i have another question why i cant not login when used pi3

@Arduns Do you have any logs from the bot available when this happens? You will need an FTDI cable to view the logs, but it is very helpful for seeing errors from Farmbot OS.

@RickCarlino  i see the log  but it's show any errors just time is error
the log is when i click the submit buttom

@Arduns It looks like Farmbot can't connect to http://<IP_ADDRESS>:80.
Are you able to reach http://<IP_ADDRESS>:80 from a computer on the network. Be sure to try it on a completely different machine and not from the same device running the server.
Also, which command did you use to start the server? Did you use rails s -b <IP_ADDRESS>? This may be an issue with the documentation. Thanks for letting us know.

@RickCarlino
i use
sudo iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8080
but it did not work！
i use a ubuntu14.04 server and i debug on may macbook use ssh!
Farmbot_app and mqtt is start use " npm run dev"  with the documentation ！
I have to use rails s -b <IP_ADDRESS>  to start the Farmbot_app and  start the web app in npm start ?

Try this (just for now):
./install_frontend.sh
rails s -b <IP_ADDRESS> --port=80

This may be a bug with the documentation that we need to update. Pleae let me know if that fixes the issue and I can update the docs.

the log looks like alway the server  is "https://my.farmbot.io" not my server
Last message: :try_log_in
State: %{broadcast: false, context: #Context<<IP_ADDRESS>4>, interim<EMAIL_ADDRESS>"qazxsw", "http://<IP_ADDRESS>"}, secret: nil, server: "https://my.farmbot.io", sub: #PID<0.246.0>, timer: #Reference<<IP_ADDRESS>2>, token: nil}

@RickCarlino ./install_frontend.sh
rails s -b <IP_ADDRESS> --port=80  it is work can start the web app but the api is not start and then mqtt not work！

@RickCarlino  just make the api use the port 80 and web app use 8080 ！it work！ thanks for help！

@Arduns Great! Glad it works now. I will close the issue.


Change log print format [Bug]

Redis version - 6.1.0
Platform - linux|mac|windows
Using Docker and/or Kubernetes - yes|no
Deployment type - cluster|sentinel|centralized
hi，developers，I found the error log from reconnecting failed is debug format , that means I open info mode, I cannot realize this error when the redis is disconnected.
To Reproduce
Steps to reproduce the behavior:
if let Err(e) = router.connect().await {
_debug!(inner, "Failed reconnecting with error: {:?}", e);
client_utils::set_client_state(&inner.state, ClientState::Disconnected);
inner.notifications.broadcast_error(e.clone());
Err(e)
}
Logs
(Set RUST_LOG=fred=trace and run with --features debug-ids)
Additional context
I hope this _debug mode can be set to _error，thanks a lot

Hi @daji777 ,
That line is intentionally a debug level log because it runs whenever the client connection finishes - either via a fatal error, QUIT, SHUTDOWN, etc. If I were to change it to an error! log level then it would mislead callers into thinking normal calls to QUIT were causing errors. Additionally, that log line only runs when the last reconnection attempt fails, which does not sound like what you want.
If you want to print a log line whenever the client disconnects then I'd recommend something like this:
let mut error_rx = client.on_error();

tokio::spawn(async move {
  while let Ok(error) = error_rx.recv().await {
    println!("Client disconnected with error: {:?}", error);
  }
});

If you do want to use a built-in log line for detecting closed connections I'd recommend this one.

@aembke  I did a experiment before and I had a redis-cluster with 3 shardings. and I stopped one master of this cluster , During the shutting down , I didn't see any errors print out .
shard 1
<IP_ADDRESS>:7000(master)
<IP_ADDRESS>:7004(slave)
shard 2
<IP_ADDRESS>:7002(master and stop)
sahrd 3
<IP_ADDRESS>:7001(master)
<IP_ADDRESS>:7005(slave)


Use python f-strings for performance improvements

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (867f12a) 97.16% compared to head (02351d8) 97.36%.
Report is 5 commits behind head on main.

:exclamation: Current head 02351d8 differs from pull request most recent head 26cafee. Consider uploading reports for the commit 26cafee to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
+ Coverage   97.16%   97.36%   +0.20%
==========================================
  Files          99      103       +4
  Lines        5710     6264     +554
==========================================
+ Hits         5548     6099     +551
- Misses        162      165       +3

Flag
Coverage Δ

pytest
97.36% <98.73%> (+0.20%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...ylegend/core/databse/sql_to_string/db_extension.py
98.85% <100.00%> (+0.34%)
:arrow_up:

...tds/legend_api/frames/legend_api_base_tds_frame.py
97.16% <100.00%> (+0.23%)
:arrow_up:

pylegend/core/tds/sql_query_helpers.py
100.00% <100.00%> (ø)

...egend_api/frames/functions/test_filter_function.py
94.31% <100.00%> (ø)

.../frames/functions/test_join_by_columns_function.py
100.00% <100.00%> (ø)

.../legend_api/frames/functions/test_join_function.py
100.00% <100.00%> (ø)

...d_api/frames/functions/join_by_columns_function.py
98.85% <98.85%> (ø)

...e/tds/legend_api/frames/functions/join_function.py
98.63% <98.63%> (ø)

pylegend/core/language/tds_row.py
90.14% <0.00%> (ø)

pylegend/core/request/legend_client.py
90.00% <66.66%> (-10.00%)
:arrow_down:

... and 1 more

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix tail call optimisation in C++ backtrace capture

According to documentation there's a __attribute__((disable_tail_calls)) attribute that should work fine for our case where we need to make sure the stacktrace has predictable number of calls at the top.

fwiw, __asm__ __volatile__(""); should also force no tail call optimization.

fwiw, __asm__ __volatile__(""); should also force no tail call optimization.

The question is which of these codes is more portable across different compilers?

definitely the attribute if it works.

__asm__ __volatile__("");

Hard to say really. I'd expect an attribute like that to be my first choice, but the code I shared is what I found Apple does/was-doing in CF.

I really like the idea with __asm__ __volatile__("");. Having both this and the attribute should not harm. Thanks @naftaly!

Tested this PR:

Static Lib
Dynamic Lib

Before

After

See that after the fix there's an extra frame in the stacktrace.
cc @GLinnik21

So this extra frame had been deleted prior to fix, right?

See that after the fix there's an extra frame in the stacktrace.
cc @GLinnik21

Did the frame always get deleted before this fix?

Yes (with Release build)


[DO NOT MERGE] Test sticky slot fix

Codecov Report

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

@@            Coverage Diff            @@
##             master      #55   +/-   ##
=========================================
  Coverage     85.07%   85.07%
  Complexity       27       27
=========================================
  Files            11       11
  Lines            67       67
=========================================
  Hits             57       57
  Misses           10       10

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 3d202e5...a337fe3. Read the comment docs.

It worked, merged the branch back into the main one


Jumping Pointer/Display Radial Gauge

Hi,
The pointer of the Radial Gauge jumps back and forth from 0 to the correct value.
The numerical value underneath seems to stay at the correct value.
How can I prevent the pointer from jumping?
I have uploaded a video. This shows the problem
BR Tom
https://user-images.githubusercontent.com/51379696/230718738-04ba20b9-f5b1-4886-885b-6f8aaf15b757.mp4

i also tried this later with another PC and with another browser.
The result is unfortunately always the same.
The indicator jumps back and forth.

Same problem here with my SOG gauge.

@DerTom1978 @JonyIvy can you explain how I could repeat the problem? I can recreate it.
Maybe share the following gauge config details:
Display

Min Integer and Decimal places
Min and Max value

Path

Signal K Path
Data Source
Display Format

Setting option

@JonyIvy  @DerTom1978 Can you also please check the KIP Data Browser to see if that data jumps. Filter on the path you are using:

check the value with the default unit, then try changing to another unit by clicking the units button. Maybe the problem is in the units conversion and not the gauge it's self...?

I think I fixed it in v2 - next release. linear and radial gauge should also be smoother.


Add: Frequency limit on update status bar

Can we merge this?

lgtm, but I have to say that I didn't check the code with great care.

Merged.


Show free/unused IP addresses

When creating/browsing a prefix, show all the free/unused within that prefix. So you can easily navigate and claim the IP addresses within that prefix.

Allocated and available IPs are listed under the "IP addresses" tab of the prefix page.


Delete not registered to "

Delete a character or selection，not registered to ", Then paste unavailable.

@linglingqi007 is this something you wanted to try contributing to? I haven’t done anything with registers yet

@linglingqi007 is this something you wanted to try contributing to? I haven’t done anything with registers yet

If I can develop vscode plugins, I'd love to. But I don't develop plugins at the moment


Bump go package to v2

Summary
We want to do a v2 release with #350, since this contains API breaking changes, we should follow go semantic versioning by bumping our package version as well. The go.mod file will read:
module github.com/cosmos/ibc-go/v2

All imports will need to change. I think this will be beneficial long term as it'll allow us to reference old code/structures when we need to maintain backwards compatibility

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

why do you need to update the go package too?

why do you need to update the go package too?

This way we can import old code when we need to maintain backwards compatibility. This is especially useful for protobuf definitions which might change. For example, if the client state proto definition changes, we may want to import the v1 definition/implementation and decode the client state bytes into that definition for connections which cannot use the newer definition. We ran into this issue changing the version of solo machine which required migration code to reimplement the solo machine interface, if the migration code actually needed to use any of the interface functions, we would have had to maintain duplicate code, much easier to import.
Having separate histories for each version of this go module may prove useful for external clients as well.
This follows the golang module version, specifically when handling major version increments:
A major version update to a number higher than v1 will also have a new module path. That’s because the module path will have the major version number appended, as in the following example:

module example.com/mymodule/v2 v2.0.0

A major version update makes this a new module with a separate history from the module’s previous version. If you’re developing modules to publish for others, see “Publishing breaking API changes” in Module release and versioning workflow.


Best way to setup IPv6 DHCP

Hey everyone,
I know SE VPN is dual stack and I am trying to setup DHCPv4 and DHCPv6 servers. I am using the isc-dhcp-server. So far IPv4 is working great but when I try to set up IPv6 it does not work. I have a /64 prefix and the DHCPv6 server service is active. I also enabled IPv6 forwarding. How can i get it working for VPN clients that use DHCP?
I hope I can wake up to some kind of solution. I'll feel like a kid on Christmas xD.

I might try and switch to PiHole's DHCP server implementation. It supports IPv4 and has an IPv6 option with a nice web interface as well with the only downside being it is not super customizable. I'm still down for other Solutions though so if you know anything especially related to the ISC's DHCP server please lmk.

I'm going to close this since it's stale.


[ocaml5-issue] Segfault with frame pointers in Effect test

The Effect stress test is also able to segfault a compiler built with the frame pointer option as reported here:
https://github.com/ocaml/ocaml/issues/12486#issuecomment-1701073256
$ _build/default/src/neg_tests/lin_tests_dsl_effect.exe -v -s 34037619
### OCaml runtime: debug mode ###
random seed: 34037619
generated error  fail  pass / total     time test name
[✓] 20000     0     0 20000 / 20000     0.7s Lin DSL ref int test with Effect
[✓] 20000     0     0 20000 / 20000     0.8s Lin DSL ref int64 test with Effect
[✓] 20000     0     0 20000 / 20000     0.8s Lin DSL CList int test with Effect
[✓] 20000     0     0 20000 / 20000     1.0s Lin DSL CList int64 test with Effect
[✓]     2     0     1     1 / 20000     0.0s negative Lin DSL ref int test with Effect
[ ]     0     0     0     0 / 20000     0.0s negative Lin DSL ref int64 test with Effect[00] file runtime/fiber.c; line 250 ### Assertion failed: d
Aborted (core dumped)

This issue is primarily to categorize CI failures.

Can you confirm this is no longer reproduceable after the merge of https://github.com/ocaml/ocaml/pull/12535 ?

Yep, I can confirm that this has been fixed.
I checked locally on a freshly built 5.2.0+fp switch and have not observed it on the CI for the past 3 weeks.


ManyToMany Relation adds extra "__" to prefetch lookup

Getting the error: Cannot find '' on Team object, 'team____users' is an invalid parameter to prefetch_related() when trying to query something like the following:
{
  turns(pagination: {limit: 1}) {
    id
    team {
      id
      users {
        id
      }
    }
  }
}

The models are defined with the following relationships:
class Turn(Model):
    team = ForeignKey("Team", null=True)
    ...

class Team(Model):
    users = ManyToManyField("Users")
    ...

And the type definitions are as follows:
@gql.django.type(Turn)
class TurnType:
    id: strawberry.ID
    team: Optional[TeamType]

@gql.django.type(Team)
class TeamType:
    id: strawberry.ID
    users: List[UserType]

@gql.djangp.type(User)
class UserType:
    id: strawberry.ID

@strawberry.type
class Query:
    turns: List[TurnType] = gql.django.field()

There is no mypy or any other type checker installed and so do not have type hints in any of the model files. I am not sure if that will cause any issues here. The issue is definitely with the prefetch configuration with the Optimizer, since if you replace the query definition with strawberry_django.field(), the code runs fine (but without the optimizations of course).

Thanks for the report! :)
Will be fixed in the next release I'm doing, please reopen if it is not!


Also set group ID

Shouldn't this module also be doing process.setgid() in addition to process.setuid()?
This code ...
// foo.js
'use strict';

require('downgrade-root')();
console.log('uid:', process.getuid());
console.log('gid:', process.getgid());

... prints 501 and 0 for me when run with sudo node foo on OS X.
The former is correct, the later is not what I expected.
Is this an oversight or an intentional decision? The tests don't give any guidance on that. Would be nice to have tests for gid either way.

I think it's an oversight.
@silverwind Thoughts?

Indeed, I added support for downgrading to SUDO_GID. We could do a fallback to default group ids after some research for default GIDs. FWIW, it seems to be 20 on OSX, 100 on Arch Linux, and something above 1000 on Debian.

Thanks all!

Published as 1.2.0.


feat: define cons and concat on bitvectors.

Define specializations of BitVec.append to add a single bit to a bitvector, either as the new LSB or the new MSB.
I've opted to name these functions cons and concat, to be consistent with the naming of (morally) similar functions on List, and following the big-ending convention set in append.
There has previously been some discussion about not assuming a specific order. Some alternative naming (in order of my preference):

consMsb / concatLsb : keep the cons/concat contrast, and the big-endian assumption it carries, but make explicit whether the new bit is the new MSB or LSB.
consMsb / consLsb: to be truly neutral w.r.t. to the big vs little endian question.

The intention is to eventually define recursion principles in terms of these functions, so it's desirable to have them even though they are somewhat simple wrappers over the existing append

Perfect, thanks for the quick review!


fix(icons): could not add new icons with capital letters for shapeName

PR Checklist

shapeName of the icon must not be case sensitive.
added icons:test and icons:test:watch to the package.json scripts.

Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #3800
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
Close: #3800

Updated test and documentation


arch/arm/samv7: Initial support of SocketLIN master interface

Summary
Initial support of SocketLIN interface for SAMv7
Impact
New feature
Testing
TBD

@pkarashchenko please include a Documentation/ for this subsystem. Maybe you can use https://nuttx.apache.org/docs/latest/components/net/socketcan.html as reference

@acassis I'm a bit in a time pressure right now. I plan to add SocketLIN slave as well as a part of this PR before Nov 27. I will include documentation as well.

@acassis I'm a bit in a time pressure right now. I plan to add SocketLIN slave as well as a part of this PR before Nov 27. I will include documentation as well.

HI,   @pkarashchenko  do you have any update about SocketLIN slave ？

👍  looking forward to your good news

@pkarashchenko  HI，  do you have any update about SocketLIN slave ？

Hi. Thank you for the reminder. I finally managed to inspect my setup with LA. I have a board that has two LIN interfaces and I simply connected those two (kind of external loopback) together and configured one as master and second one as slave. Based on the multiple tests I suspect that my board has some issues with the USART TX line for one of the LIN interfaces so I can't fully pass the happy path test cases. Unfortunately I have only one such board :(
Let me push to this branch whatever I have (with some test code) so you can have a better idea of what I'm testing and maybe we can continue conversation right after

@xucheng5 please take a look

maybe we can use lin_frame_t instead of struct can_frame  to make a difference between can and lin which means use typedef struct can_frame lin_frame_t to redefine struct can_frame.

Seems like I finally found an issue with my board. Seems to be SW related. I have a change and will try to test it this week.

maybe we can use lin_frame_t instead of struct can_frame to make a difference between can and lin which means use typedef struct can_frame lin_frame_t to redefine struct can_frame.

Hi. I tried to stick to https://github.com/lin-bus/linux-lin/blob/master/sllin/sllin.c as close as possible. That typedef can be done, but I do not see a real benefit from it. I'm testing this change with standard CAN utilities like cansend, so only the underlying interface name is linX. I think this is a right path to go

maybe we can use lin_frame_t instead of struct can_frame to make a difference between can and lin which means use typedef struct can_frame lin_frame_t to redefine struct can_frame.

Hi. I tried to stick to https://github.com/lin-bus/linux-lin/blob/master/sllin/sllin.c as close as possible. That typedef can be done, but I do not see a real benefit from it. I'm testing this change with standard CAN utilities like cansend, so only the underlying interface name is linX. I think this is a right path to go

agree with it !

@pkarashchenko https://github.com/apache/nuttx/pull/13257 add more LIN flags, could you review it? Thanks.

@pkarashchenko could you rebase this patch? I could merge it after ci.

@michallenc @acassis @xiaoxiang781216 I do not have much time to continue advancing the driver. This PR is more an MVP and I would appreciate if we can merge it so people that will start using LIN over SocketCAN on SAMv7 will be able to improve as a next step. For example the error detection and reporting definitely requires refinement and probably few other places can be simplified.


Prevent user from adding already excluded dates

Currently, when making a exclusion date, you can add multiple of the same dates but only if it is the date you just added or the current date.
Do one of the two options:
option 1: Put error in error banner if user selects date that is already an exclusion date
option 2: Prevent user from ever being able to add an exclusion date by having the newExclusionDate increment by one once addExclusionDate is called.
Option 2 is easier and wouldn't rely on the separate issue detailed in #42 of adding an alert system.
Thanks ❤

https://momentjs.com/guides/#/lib-concepts/date-time-math/ might be useful in this issue :)


USB

Dear Ad.
I use this exemple:
PY32F072_Firmware-master\Projects\PY32F072-STK\Applications\USB_Device\USBD_Keyboard
and connect USB as: https://oshwhub.com/iosetting/py32f07x-lqfp64
PA11  -> D-
PA12 -> D+  ( PULL 1,5K  VCC as : https://oshwhub.com/iosetting/py32f07x-lqfp64)
but when update code and push usb it show:  the last usb device you connected malfunctioned .....
Pleased help me do it.
Thank you.

@HalfSweet
if
PA11 -> D-
PA12 -> D+ ( PULL 1,5K VCC as : https://oshwhub.com/iosetting/py32f07x-lqfp64)
if no use PULL 1.5k D+ then nothing happens, no dectect usb.


API Authentication using Laravel Sanctum — Laravel 8

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #2559

plagiarism check completed - all good
2120420-fbf543b702d27330753a-1626810797647.pdf

@bhanjibrilliant
Thank you for your understanding while our Peer reviewer team works diligently to go through our EngEd articles.

@bhanjibrilliant add postman screenshot showing various requests explained in the article.

will be conducting a final review @hectorkambow @ahmadmardeni1 @louisefindlay23 @LinusMuema

Nice article easy to follow and understand @bhanjibrilliant @paulodhiambo

Over all great work gents!! @bhanjibrilliant
Please be sure to go over any edits made by the peer reviewers or myself to improve future articles. 👍


Manage variables for Gitlab CI groups

I don't understand what is the error into TravisCI. Is it because of the warning messages?

Could you apply the following small fix and squash?
diff --git a/.travis.yml b/.travis.yml
index 5b98842..7ae1499 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -2,7 +2,7 @@ language: python
 python: '2.7'
 env:
   global:
-  - GITLAB_API_URL=https://gitlab.com/api/v4/
+  - GITLAB_API_URL=https://gitlab.com/api/v4

Not exactly sure why this is only happening now, but this is building URLs with a double slash  such ashttps://gitlab.com/api/v4//projects/peay%2Fmy-awesome-project/variables/VARIABLE_TO_CREATE_9160517 and the Gitlab version on gitlab.com now produces a 301 to get rid of that, may be a recent behavior change. Stripping this trailing slash should probavly be something the playbook would take care of.

I fixed this, but test still fails.


Fix global_packages enumeration

On macOS if you opened global_packages directory in Finder, it creates a .DS_Store entry. PubCache assumes all items in global_packages are Directories. This would cause an exception to be thrown when instantiating PubCache.

lgtm, thanks!


cve-bin-tool: 3.3 -> 3.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cve-bin-tool is: CVE Binary Checker Tool
meta.homepage for cve-bin-tool is: https://github.com/intel/cve-bin-tool
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS

[!CAUTION]
A test defined in passthru.tests did not pass.

found 3.4 with grep in /nix/store/g10p9kh38155kyfqw8bnpgra6y5fgvxg-cve-bin-tool-3.4
found 3.4 in filename of file in /nix/store/g10p9kh38155kyfqw8bnpgra6y5fgvxg-cve-bin-tool-3.4

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

cve-bin-tool

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g10p9kh38155kyfqw8bnpgra6y5fgvxg-cve-bin-tool-3.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cve-bin-tool https://github.com/r-ryantm/nixpkgs/archive/ad7f769b27f1f091b8c2e080e56c073b16778fcb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ad7f769b27f1f091b8c2e080e56c073b16778fcb#cve-bin-tool

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g10p9kh38155kyfqw8bnpgra6y5fgvxg-cve-bin-tool-3.4
ls -la /nix/store/g10p9kh38155kyfqw8bnpgra6y5fgvxg-cve-bin-tool-3.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

cve-bin-tool
cve-bin-tool.dist

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

ModuleNotFoundError: No module named 'lib4vex'


S3 plugin

Description of change

How has this been tested? (if applicable)

draft implementation of plugin for #668

I suppose this is paired with #917

yes but not ready to review yet :)

Hey @Shubham8287 ! This PR slipped from our list of priorities lately. We'll be a bit low on bandwidth in the next weeks because of a bigger release and an offsite happening shortly, but we'll try to catch up on this in the meantime.
We thought that this PR will have a common portion shared with #910, regarding the AWS credentials management, so would be great to have alignment between the two. I haven't personally looked that much into how this is done on both PRs, and it would be great if you can share any thoughts you formed on this subject. Also, please check out #910 approach, would be great if you can spot something there that is conflicting with this PR needs, if any.

I am  holding this PR for #910 as it shares a common portion and I think that user policy part has some security concerns as well. Would resume it once we get other one merged or some better approach. Let me if this is fine to you folks.

Thanks @Shubham8287! Indeed, at this time we have some security concerns that required postponing the DynamoDB/S3 PRs. We need to go back to the drawing board and see what architecture/design changes would need to be done to accommodate integrating these resources with Shuttle. BTW, thanks a lot for staying close to S3/DynamoDB development track. We'll try to give more updates about the way forward once we'll plan this internally.

Closing this. Context provided here: https://github.com/shuttle-hq/shuttle/issues/668#issuecomment-1731190978.