Wrong direction given when VLSC is not working.

"Direct customers can submit a request from their Office 365 admin center or contact support."
Office 365 support currently does not have a download link this product nor know what to do when it is missing. Multiple contact resulted in the same. If there is an option this should be communicated to that team so that they can provide the support promised on this page.

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

ID: b8ca0ba7-ad2d-e079-813a-b4e2d622de96
Version Independent ID: 9c5e5594-ebff-f90f-fe73-71b545c3b2e7
Content
Content Source
Service: unspecified

Hi there, thank you very much for your feedback. I've been actively working with our support center contacts to ensure that agents are aware of the download link that they can provide. You should be able to successfully obtain the link from support agents now.
Best,
Lorena | Office Online Server PM

Hi there, I'm closing the issue as per my reply above. Please feel free to reach out if you have further questions.
Thanks,
Lorena | Office Online Server PM

Hi Lorena,
May I know what this download link is?
Thanks!

Hi @isaacgandalf,
I apologize, I am not able to provide the link to customers. Instead, you might follow the instructions on here (https://docs.microsoft.com/en-us/OfficeOnlineServer/office-online-server) to determine how to obtain OOS depending on your license.
Thanks,
Lorena | Office Online Server PM

Thanks for the prompt reply Lorena. I'm actually a support engineer for Office 365 Business myself and have encountered such a question from one of our customers, and I couldn't find anyone who knew of this download link. The ticket was created via the Need Help widget.

Hi @isaacgandalf ,
Are you able to contact me through email so that I can provide the information necessary?
Thanks,
Lorena

Closing issue as it was resolved through communication with Isaac..

Hi @lorenahuangliu and @isaacgandalf,
Would you be able share the solution? If not publicly, then at least with the rest of the Office 365 support team? I followed the advice given above and opened a ticket through my Office 365 Admin Center, and out of 3 replies so far, I've been sent in 3 different directions:
here: https://www.microsoft.com/licensing/servicecenter,
here: https://support.microsoft.com/en-us/assistedsupportproducts#gsproductselector,
and here<EMAIL_ADDRESS>Can someone please either update the internal documentation about handling such requests, or the documentation above with the proper procedures?
Thanks,
Christian

Hi Christian,
I apologize for this inconvenience. Can you give me the open case number and I'll have a look at it, and possibly contact the tech working on it.
Thanks,
Isaac

Thanks for looking into this! The case number is 10907500.
Thanks,
Christian

@cbaerike
Hi Christian,
I have updated the case notes with the relevant information. It will now be up to the case owner to decide how to proceed, depending on policies that may be in place.
However, please review the licensing requirements for Office Online Server to verify eligibility:
https://www.microsoft.com/en-us/microsoft-365/blog/2017/04/18/office-online-server-april-2017-release/
https://www.microsoft.com/en-us/Licensing/product-licensing/products.aspx (download the English version for Product Terms)

Exchange Server 2013  for Office Web Apps Server did support , I think it post it wrongly.
quoted from
https://blogs.technet.microsoft.com/admoore/2015/12/18/wac-oos-oos-and-wac/
Before we move on, take in the following:
Exchange 2013 uses Office Web Apps Server and does not support Office Online Server.
Exchange 2016 uses Offline Online Server and does not support Office Web Apps Server.
Exchange 2013 was an Organization level configuration.

post do remedy the article

@musashiharuno - You may want to post this in a separate feedback thread, as it will likely get overlooked in this one.
On topic: It seems like Office 365 customers are still SOL. Even after @isaacgandalf updated my case as mentioned above, I'm getting the same response (word for word!). Office 365 support is either unwilling or unable to help.
@lorenahuangliu - Can you please update the article and either remove the recommendation to open a ticket through the Office 365 admin center, or provide further details with the magical keywords?
Thanks,
Christian

@cbaerike haha, got your point,
OOS for Vol. License is for OnPrem with SharePoint & Exchange integration.
OOS for Office365, in other words, built-in SharePoint Online & Exchange Online OWA.
frankly speaking, the product introduction/description sometimes is quite vague that not enough to express its real meaning.
personally, I am afraid it can be a separate service for client level since OOS is the server level product. It can't be shipped with Office365 as the standalone licensing.
otherwise, they will clarify the statements in a "plain text".
for the wrong info I raised, I think I might go through the internal process despite of the long process as well.
Thanks

I am having this same exact problem

@msmith91185 Thank you for this feedback.
It looks like your issue has been resolved. If this is not the case please re-open this issue. If there is another issue please open a new issue or contact support.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y

Download it from MSDN https://my.visualstudio.com/downloads?wt.mc_id=o~msft~devcom~resources if you have an account. Much easier than a VLK. Using for DEV

I open a request with office 365 support and it unable to give me the link!!!! Please update how with office365 I can retrieve the iso!!!


TargetGroupPolicy and VpcAssociationPolicy CRD status Update

Currently controller behavior is: if multiple TargetGroupPolicies (tgp), VpcAssociationPolicies(vap) apply to the same k8s obj, only the first policy will take effect and the controller will ignore the rest of policies(will print a error log for it). If that happen, we should use a better way to represent this error by updating policy status: for example, If there are two tgps attached to one svc(serviceExport), one policy is set to accepted status and the other one is set to conflicted status.
(Other policies CRDs or even other controller managed k8s objs may also need proper status update )

Thanks for reporting the issue, we will be investigating it further. Please watch this channel for more updates, and feel free to reach out.

We released EKS controller version v0.0.18 yesterday which contains a revised TG naming strategy to avoid conflicts. Target group names will no longer conflict across clusters for identical specs. Target group names now include a randomized suffix and all identification/deduplication is done through first class fields on the target group and tags.
Marking this issue as resolved. Thank you for you support.


There should be at least one conflict resolver or merger integrated for git hub with Visual Code

VSCode Version:
OS Version:

Steps to Reproduce:

#5770


Added optional zoom in the middle of the image instead of pointer position.

This solves #1422

Looks good, thank you!


Does Training Reward model only support two items comparison in dataset at this time

It looks like the sample datasets only support pair comparison, so I am curious about if we have multiple optional answers ranks from highest to lowest, will it be worked on this architecture

目前还不支持，后续会加入该功能。


Add windows support for downloading recordings

Hello:
This fixes #50 .

The first commit changes the hardcoded /dev/null device to os.devnull which fixes redirection in Windows when saving the file.
The second commit is a workaround for Windows, tempfile.NamedTemporaryFile works weird on Windows, when writing the contents, those are not flushed (even with flush()) so disabling the manually deleting of file and doing it manually works correctly (and should continue to work under other OS) - I also removed the close() call as using with that's unnecessary.

Thank you!


glBindSampler(0, 0) is needed for OpenGL backend

For an app code that uses a separate Sampler scheme instead of texture-sampler bound scheme,
the following code is needed as in ImGui source. Please refer to glBindSampler doc too.

https://docs.gl/gl3/glBindSampler

Hello.
I am quite busy these days so that I will not have time to work this in the next days. In the meantime you can compile the library by yourself and just define what is needed to get this feature.
from imgui_impl_opengl3:
// Desktop GL 3.3+ has glBindSampler()
#if !defined(IMGUI_IMPL_OPENGL_ES2) && !defined(IMGUI_IMPL_OPENGL_ES3) && defined(GL_VERSION_3_3)
#define IMGUI_IMPL_OPENGL_MAY_HAVE_BIND_SAMPLER
#endif

=> You need to define GL_VERSION_3_3 at compilation time.
This will not work on a mac, because of the way openGL is setup on this plaform at the present time.
See src/hello_imgui/internal/backend_impls/opengl_setup_helper/opengl_setup_glfw.cpp
    void OpenGlSetupGlfw::SelectOpenGlVersion()
    {
        #if defined(IMGUI_IMPL_OPENGL_ES3)
        {
            BACKEND_THROW("OpenGlSetupGlfw::SelectOpenGlVersion needs implementation for GLES !");
            //            SDL_GL_SetAttribute(SDL_GL_CONTEXT_EGL, 3);
            //            SDL_GL_SetAttribute(SDL_GL_CONTEXT_PROFILE_MASK,
            //                                SDL_GL_CONTEXT_PROFILE_ES);
            //            SDL_GL_SetAttribute(SDL_GL_CONTEXT_MAJOR_VERSION, 3);
            //            SDL_GL_SetAttribute(SDL_GL_CONTEXT_MINOR_VERSION, 0);
        }
        #elif defined(__APPLE__)
        {
            glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);
            glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 2);
            glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);  // 3.2+ only
            glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);            // Required on Mac
        }
        #else
        {
            // GL 3.2+
            glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);
            glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
            glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);  // 3.2+ only
            glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);            // 3.0+ only
        }
        #endif
    }

Hi,
I did another test today: the portion of code you highlighted is executed, without needing to change anything.
So I guess I do not understand your question.
I will close this issue, please post additional comments if you have and I'll reopen.


#157117709 Fix bugs on Integrations with Circle CI

What does this PR do?
Fix a bugs Circle CI files for continuous integration when linking it with Heroku

Pull Request Test Coverage Report for Build 91

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

Totals

Change from base Build 50:
0.0%

Covered Lines:
1544

Relevant Lines:
1924

💛  - Coveralls

Pull Request Test Coverage Report for Build 91

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

Totals

Change from base Build 50:
0.0%

Covered Lines:
1544

Relevant Lines:
1924

💛  - Coveralls


Update MAMP to 3.3

Updated MAMP to 3.3

Thank you for the contribution. It was merged directly as 3b996fdb778f2d62690aba3b9cfc91d3994f12ec to keep commit history cleaner. Your contribution is still credited to you.


add Iter method

add Iter method, that iterates over Trie using DFS
fix type in method HasChilds(should be HasChildren)

Thank you!


Back button in browser not taking you back to the book page from the set_assignments page.

Go to
https://isaacphysics.org/physics_skills_14
Click on an accordion and a page within it to "add to my boards".
This then takes you to set assignments :)
The problem is that the back button of the browser does not then take you back to https://isaacphysics.org/physics_skills_14 if you want to assign a different set of questions to a different group.
I.e. to get back to the book index page you have to type the URL again.

This is also true from My Boards.
I also noticed that the back button does work for both Assign a Board and My Boards page when you didn't get to it by pressing Save or Add to my boards.


crypto tls panic when pulling container images

When we try to pull container images in fips enabled environments, we see a crypto tls panic.
panic: tls: HKDF-Extract invocation failed unexpectedly
goroutine 221 [running]:
crypto/tls.(*cipherSuiteTLS13).extract(0x5651729bbfe0, {0x0?, 0x1?, 0x1?}, {0x0, 0x0, 0x0})
	go-go1.22.2/src/crypto/tls/key_schedule.go:100 +0x285
crypto/tls.(*clientHandshakeStateTLS13).establishHandshakeKeys(0xc0003bdbd0)
	go-go1.22.2/src/crypto/tls/handshake_client_tls13.go:388 +0xd3
crypto/tls.(*clientHandshakeStateTLS13).handshake(0xc0003bdbd0)
	go-go1.22.2/src/crypto/tls/handshake_client_tls13.go:90 +0x2bb
crypto/tls.(*Conn).clientHandshake(0xc000634708, {0x5651722c75f8, 0xc000696f00})
	go-go1.22.2/src/crypto/tls/handshake_client.go:265 +0x594
crypto/tls.(*Conn).handshakeContext(0xc000634708, {0x5651722c75c0, 0xc000810db0})
	go-go1.22.2/src/crypto/tls/conn.go:1553 +0x3cb
crypto/tls.(*Conn).HandshakeContext(...)
	go-go1.22.2/src/crypto/tls/conn.go:1493
net/http.(*persistConn).addTLS.func2()
	go-go1.22.2/src/net/http/transport.go:1573 +0x6e
created by net/http.(*persistConn).addTLS in goroutine 217
	go-go1.22.2/src/net/http/transport.go:1569 +0x309

I see the hashToMD function not able to find a match in the hash.Hash type switch here. and returning nil.
I instrumented a debug print statement inside the hashToMD function.
fmt.Printf("actual h type=%T\n", h)

and i see h type=*sha256.digest
But before the img pull command I also see cases of h type=*openssl.sha256Hash which seems to pass the type switch in hashToMD function. Not sure which type is expected or both.
If I skip the type switch and hard code "return cryptoHashToMD(crypto.SHA256)" , the panic disappears.
The code function flow seems to be
ExtractHKDF -> newHKDF -> hashToMD -> h type=*sha256.digest -> no match in type switch.

I have confirmed that exact same panic also occurs with go v1.21.x.

Thank you for looking into it! I tried that with a simple TLS client (compiled with the Go compiler built from the go1.22.2-1-openssl-fips, but it works under under GOLANG_FIPS=1 OPENSSL_FORCE_FIPS_MODE=1:

ExtractHKDF -> newHKDF -> hashToMD -> h type=*sha256.digest -> no match in type switch.

Would it be possible to set a breakpoint in crypto.sha256.New() to see how it ends up with a non-boring hash implementation?

Would it be possible to set a breakpoint in crypto.sha256.New() to see how it ends up with a non-boring hash implementation?

I can definitely try the non-boring path. But first, let me share a script that helps reproduce the error in fips enabled env. see attached.
You would need a linux amd64 machine (fedora/rh/centos shud work). Please let me know if the script doesn't work in ur env and i would be happy to make necessary modifications to it.  Please rm the txt extension, github wont let me attach otherwise.
repro-tls-panic.sh.txt

@sipasing thanks for opening this issue and for the reproducer! As I mentioned over slack (and @ueno mentioned on this thread) somehow a non-FIPS (non-boring) hash is being selected and passed down into the FIPS module. Setting a breakpoint as @ueno mentioned could be helpful for us to understand how we're getting into this situation.

Got it. On it. Do u have any preference on gdb or delve ? Or a simple debug print is sufficient ?

Got it. On it. Do u have any preference on gdb or delve ? Or a simple debug print is sufficient ?

Delve is preferred, a print statement could work as well.

I added these print statement inside src/crypto/sha256/sha256.go ?
 func New() hash.Hash {
+   fmt.Println("crypt.sha256.New")
+     _, file, no, ok := runtime.Caller(1)
+    if ok {
+        fmt.Printf("called from %s#%d\n", file, no)
+    }
        if boring.Enabled() {
+        fmt.Println("boring.Enabled")
                return boring.NewSHA256()
        }
+
+    fmt.Println("new digest")
        d := new(digest)
        d.Reset()

and i get
quay.io/quay/busybox:latest: resolving      |--------------------------------------|
elapsed: 0.3 s               total:   0.0 B (0.0 B/s)
crypt.sha256.New
called from /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/vendor/github.com/golang-fips/openssl-fips/openssl/hmac.go#64
boring.Enabled

right before the panic.
For delve, I would need to attach to the go binary and then execute the ctr img pull command ? . working on it.

To add to previous comment, hmac.go#64 is
func NewHMAC(h func() hash.Hash, key []byte) hash.Hash {
 64     ch := h()
 65     md := hashToMD(ch)

to find the caller of NewHMAC, I further added another printf inside hmac.go#64
 func NewHMAC(h func() hash.Hash, key []byte) hash.Hash {
+   fmt.Println("openssl.NewHMAC")
+     _, file, no, ok := runtime.Caller(1)
+    if ok {
+        fmt.Printf("called from %s#%d\n", file, no)
+    }

and i get
openssl.NewHMAC
called from /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/hmac/hmac.go#131
crypt.sha256.New
called from /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/vendor/github.com/golang-fips/openssl-fips/openssl/hmac.go#70
boring.Enabled

hmac.go#131 is
129 func New(h func() hash.Hash, key []byte) hash.Hash {
130     if boring.Enabled() {
131         hm := boring.NewHMAC(h, key)

Delve output
dlv exec ./ctr -- image pull quay.io/quay/busybox:latest
Type 'help' for list of commands.
(dlv) b myLoopingStuff src/crypto/sha256/sha256.go:153
Breakpoint myLoopingStuff set at 0x55e7df6e8346 for crypto/sha256.New() go-go1.21.7/src/crypto/sha256/sha256.go:153
(dlv) continue
quay.io/quay/busybox:latest: resolving      |--------------------------------------|
elapsed: 0.1 s               total:   0.0 B (0.0 B/s)
quay.io/quay/busybox:latest: resolving      |--------------------------------------|
elapsed: 0.2 s               total:   0.0 B (0.0 B/s)
src/crypto/hmac/hmac.New
called from /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/prf.go#28
boring.Enabled
openssl.NewHMAC
called from go-go1.21.7/src/crypto/hmac/hmac.go#139
> [myLoopingStuff] crypto/sha256.New() go-go1.21.7/src/crypto/sha256/sha256.go:153 (hits goroutine(183):1 total:1) (PC: 0x55e7df6e8346)
   148:	// New returns a new hash.Hash computing the SHA256 checksum. The Hash
   149:	// also implements encoding.BinaryMarshaler and
   150:	// encoding.BinaryUnmarshaler to marshal and unmarshal the internal
   151:	// state of the hash.
   152:	func New() hash.Hash {
=> 153:	   fmt.Println("crypt.sha256.New")
   154:	     _, file, no, ok := runtime.Caller(1)
   155:	    if ok {
   156:	        fmt.Printf("called from %s#%d\n", file, no)
   157:	    }
   158:		if boring.Enabled() {
(dlv) bt
 0  0x000055e7df6e8346 in crypto/sha256.New
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/sha256/sha256.go:153
 1  0x000055e7df5f00a6 in vendor/github.com/golang-fips/openssl-fips/openssl.NewHMAC
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/vendor/github.com/golang-fips/openssl-fips/openssl/hmac.go:70
 2  0x000055e7df72f4e2 in crypto/hmac.New
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/hmac/hmac.go:139
 3  0x000055e7df788278 in crypto/tls.pHash
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/prf.go:28
 4  0x000055e7df788ec9 in crypto/tls.prf12.func1
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/prf.go:73
 5  0x000055e7df789644 in crypto/tls.extMasterFromPreMasterSecret
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/prf.go:123
 6  0x000055e7df767c26 in crypto/tls.(*clientHandshakeState).doFullHandshake
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/handshake_client.go:658
 7  0x000055e7df76642a in crypto/tls.(*clientHandshakeState).handshake
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/handshake_client.go:495
 8  0x000055e7df764006 in crypto/tls.(*Conn).clientHandshake
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/handshake_client.go:276
 9  0x000055e7df797085 in crypto/tls.(*Conn).clientHandshake-fm
    at <autogenerated>:1
10  0x000055e7df760212 in crypto/tls.(*Conn).handshakeContext
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/conn.go:1552
11  0x000055e7df75fb37 in crypto/tls.(*Conn).HandshakeContext
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/crypto/tls/conn.go:1492
12  0x000055e7df893cbd in net/http.(*persistConn).addTLS.func2
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/net/http/transport.go:1555
13  0x000055e7df281661 in runtime.goexit
    at /home/sipasing/ci/cntrd-n/proj/data/deps/go/src/go-go1.21.7/src/runtime/asm_amd64.s:1650

Also right before the panic,  dlv shows hash from github.com/minio/sha256-simd.digest.
(dlv) b go-go1.21.7/src/vendor/github.com/golang-fips/openssl-fips/openssl/hmac.go:23
 18:	)
    19:
    20:	// hashToMD converts a hash.Hash implementation from this package
    21:	// to a BoringCrypto *C.GO_EVP_MD.
    22:	func hashToMD(h hash.Hash) *C.GO_EVP_MD {
=>  23:		switch h.(type) {
    24:		case *sha1Hash:
    25:			return C._goboringcrypto_EVP_sha1()
    26:		case *sha224Hash:
    27:			return C._goboringcrypto_EVP_sha224()
    28:		case *sha256Hash:
(dlv) p h
hash.Hash(*github.com/minio/sha256-simd.digest) *{
	h: [8]uint32 [1779033703,3144134277,1013904242,2773480762,1359893119,2600822924,528734635,1541459225],
	x: [64]uint8 [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],
	nx: 0,
	len: 0,}
(dlv) c

Ah, ok. So given that last comment it seems that the hash is of type *github.com/minio/sha256-simd.digest which is not produced within the bounds of the FIPS module (e.g. not from OpenSSL), so that's why the panic is happening. The error message could be better here, but the behavior is correct.

Overall this is not something we can support.  All crypto, including hashes, must be generated by the OpenSSL FIPS module.  Upstream Go boringcrypto has the same constraints.  I'd suggest to open a bug against the library or application that pulls in minio/sha256-simd and suggest to add Go boringcrypto support via build tags similarly to how it has been implemented in minio-go, for example:
https://github.com/minio/minio-go/issues/1697
https://github.com/minio/sha256-simd/pull/61

Thanks for the pointers. I am still investigating ways in which I can manually replace hashes generated by minio/sha256-simd in containerd (the application) with OpenSSL hashes.
I kept this ticket open because I wanted to improve on the error messages. Currently there is a panic generated , but maybe we can improve it to also say that the hash is not supported or something to that effect ??


Session::channel_open should probably not restrict the message to UTF-8

The message argument for Session::channel_open is currently an Option<&str>, while sometimes it's necessary to pass arbitrary binary data to libssh2_channel_open_ex. For example, inside libssh2 itself, raw u32 values are passed inside the string, which can make it invalid UTF-8:
https://github.com/libssh2/libssh2/blob/d39e9ccc5e08a6441075049f1f79ffcb2bbe5a52/src/channel.c#L406
The parameters should probably be Option<&[u8]>, or a generic involving AsRef<[u8]> but there's probably no way to fix the existing method without making a breaking change, but adding a new method feels clunky too.
I could create a PR if this is something you'd consider fixing.

Making the argument Option<T> where T: AsRef<[u8]> would be a Minor Change and can happen with a minor version bump according to RFC 1105.

Is it a minor change if it minor involves an Option though? fn foo(bar: Option<&str>) can unambiguously be called as foo(None), but fn foo<T: AsRef<[u8]>>(bar: Option<T>) can't, as the type for T is ambiguous (even though it's not actually used).

That's a good point, it would definitely mess with ergonomics in the None case. Probably best to go for the breaking-but-unambious &[u8] option then.

This would be useful in many other parts of the API, in most cases the strings should not be required to be UTF-8.
I encountered this issue while trying to use bytestrings in Channel::setenv. While it's not common, you can set environment variables to arbitrary binary data on Linux systems; there isn't any enforced encoding

@mvirkkunen This seems like a reasonable change and brings us better in line with libssh2. In short, I'm all for it.
@agausmann While it may be possible to pass binary data through setenv, even libssh2 expects this data to be a valid C string as evidenced through debug prints. This doesn't matter if those debug prints are not compiled in, but the expectation stands the same. If you can get the libssh2 developers to change from const char *value to const unsigned char *value, removing the expectation that this parameter is a human-readable string, I'd be fine with this change.

I see, I wasn't aware of any conventions around char* versus unsigned char*
That being said, I found out that I can't use setenv in my case anyway, as the environment variable isn't allowed in the SSH server's configuration. So I did it through the shell instead - FOOENV="$(echo -ne '{escaped binary}')" ...

Oh, what? The public wrapper API has a different data type? I didn't even notice. I wonder if that's just for backward compatibility when they noticed the same problem and didn't want to change the public API.
I guess it's not as straightforward to change this then.


No files to display - missing data

@alvacouch
These two resources used to have files, but today they do not.  Both of these resources had data three weeks ago, and there is no reason to suspect a human has cleared the resource contents.
https://www.hydroshare.org/resource/3a925bd4a5784a38944b1e8b51224de1/
https://www.hydroshare.org/resource/70b977e22af544f8a7e5a803935c329c/

I've given you edit permissions for both.
C

@alvacouch The front end is failing to get the folder structure for these resources through the API call
/hsapi/_internal/data-store-structure/
I've seen this error multiple times in the last few weeks.

Thanks for getting back to me.  I'm mildly distressed because the data and notebooks for one of these if for a paper I am trying to get out by AGU.  This looks like a really bad error.  So the data is there it's just not being displayed?

This is widespread, and needs some prompt action.  Here is another resource where this is a problem. https://www.hydroshare.org/resource/64fb0a478974411caea3335e2d07975c/.  An attempt to download a bag results in the following errors

@dtarb @cbcunc @phuongdm @aphelionz From the bag download error, I can see the following two issues possibly related to deployment oversight:

download bag path points to hydrotest41Zone which is the default iRODS setting in local_settings.py, so it appears local_settings.py did not get restored with production settings on production server.

We can see debug traceback on www, which means debug is set to True, which proved again local_settings.py is wrong, since the local_settings.py on production server should have DEBUG set to False.

Restoring production settings followed by rebuilding Django site could fix this deployment issue.

I agree with @hyi. Also make sure to reset the bag_modified flag to cause regeneration of all bags. This should be set in the deploy script.

@hyi,
You are correct. That's my fault. I'm going to rebuild again with the correct local_settings.py

@ChristinaB, @dtarb, @Maurier, all
I have run rebuild on the www.hydroshare.org. Could you please re-check your resources?
Sorry again,
Phuong

I think it worked, at least partially. The resources posted by @ChristinaB have been restored, but I see at least one other instance still showing the behavior:
https://www.hydroshare.org/resource/7a77f525667b42f69cdc3f8db18e1280/

We should establish the practice of running Tony's check to download all resources script as a test on each release candidate, and as a test on each production deploy.

Thanks for the quick response everyone.  Can I suggest that we recreate this 'No files to display' every April 1 for an April Fools joke?
In other news, it looks like the new release also broke the jupyter hub server.  Should I make a new Github issue for that? I'll email @Castronova first.

@alvacouch
The resource 7a77f525667b42f69cdc3f8db18e1280 has a file: data_48.15625_-121.28125.gz but after run
./hsctl managepy ingest_irods_files 7a77f525667b42f69cdc3f8db18e1280
the file has disappeared. What did I do wrong here?

@dtarb @ChristinaB
Sorry for the late response, but we need to avoid to touch to the production server while users access it. And some of you also have presentations/classes today on HydroShare. So, night work might be the best choice.

@alvacouch may be able to help as he wrote that ingest_irods code (I think).  I did make a copy of the zipped bag of this resource that includes this file on Monday when the problem was reported and @ChristinaB  bagging seems to be working now if you need to recover the files before we are able to fix the problem.

@dtarb @phuongdm The trace above is correct function of the script ingest_irods_files. The error messages always show; they are django messages that happen whenever a command is invoked. The actual output of the script indicates correct operation.

@dtarb @phuongdm @aphelionz This may be a UI problem. My command says there are 25 files available but they aren't showing up. Here's what it prints on www:
LOOKING FOR UNREGISTERED IRODS FILES FOR RESOURCE 7a77f525667b42f69cdc3f8db18e1280
(current files 25)

@alvacouch
The file has gone instead of the behavior of ingest_irods_files is created Django file records.

@dtarb @phuongdm @aphelionz I do not have irods credentials to login to the www repository to check the irods files actually present.

@dtarb @phuongdm @aphelionz
[hydro-service@www hydroshare]$ ./hsctl managepy check_irods_files 7a77f525667b42f69cdc3f8db18e1280
.....
LOOKING FOR FILE ERRORS FOR RESOURCE 7a77f525667b42f69cdc3f8db18e1280
[hydro-service@www hydroshare]$
This passes the correspondence test between django and iRODS.
So there is something very wrong with the ui (or these files have been mis-located outside 7a77f525667b42f69cdc3f8db18e1280/data/contents, which is unlikely)

@aphelionz @phuongdm @dtarb I wrote a custom debugger to list what the system is finding. It is located in www:hydroshare/management/commands/junk.py Its output is as follows:
[hydro-service@www hydroshare]$ ./hsctl managepy junk --verbose 7a77f525667b42f69cdc3f8db18e1280
MANAGEPY:
  - docker exec -u hydro-service -ti hydroshare python manage.py junk --verbose 7a77f525667b42f69cdc3f8db18e1280
...
LOOKING FOR FILE ERRORS FOR RESOURCE 7a77f525667b42f69cdc3f8db18e1280
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/observatory_gridded_hydromet.py
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_forJenLennon062917Jim.ipynb
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_forJenLennon071017Jim.ipynb
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/SaukRiver_Sauk_obs_cfs.dly
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/ThunderBasinSNOTEL.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/month_WRF_CIG_1950_2010.csv
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/month_Livneh1915_2011.csv
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Zdiff.csv
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/12186000.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/12189500.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Precip.daily.WRF.m.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Precip.daily.Liv2013m.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/ChocolateGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/CoolGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/SuiattleGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/ELA_all_6_7.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/VistaGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/DustyGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/HoneycombGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/ErmineGlacier.streamflow.daily.cms.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/gl_cov_glac_6_7.txt
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_WatershedHydroMetDownload.ipynb
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_forJenLennon062917.ipynb
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/data_48.15625_-121.28125.gz
check_irods_files: check Django path 7a77f525667b42f69cdc3f8db18e1280/data/contents/USC00455678.csv
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/12186000.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/12189500.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/ChocolateGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/CoolGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/data_48.15625_-121.28125.gz
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/DustyGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/ELA_all_6_7.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/ErmineGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/gl_cov_glac_6_7.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/HoneycombGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/month_Livneh1915_2011.csv
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/month_WRF_CIG_1950_2010.csv
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/observatory_gridded_hydromet.py
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_forJenLennon062917.ipynb
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_forJenLennon062917Jim.ipynb
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_forJenLennon071017Jim.ipynb
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Observatory_Sauk_WatershedHydroMetDownload.ipynb
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Precip.daily.Liv2013m.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Precip.daily.WRF.m.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/SaukRiver_Sauk_obs_cfs.dly
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/SuiattleGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/ThunderBasinSNOTEL.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/USC00455678.csv
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/VistaGlacier.streamflow.daily.cms.txt
check_irods_files: found iRODS path  7a77f525667b42f69cdc3f8db18e1280/data/contents/Zdiff.csv

It found all files in both Django and iRODS.

It seems that @alvacouch is correct. This may be an UI problem.
@hyi
Could you debug this issue for us? @aphelionz doesn't have access to www.

Some updates, folks:

I do have access to www @dtarb @hydroadmin @alvacouch
I noticed that the UI is throwing an error based on this line https://github.com/hydroshare/hydroshare/blob/develop/hs_core/views/resource_folder_hierarchy.py#L86

That tells me that this is NOT a UI issue and that Django is having an issue finding that logical file. I need more time to figure out whether or not that's in the db or iRODS, or both, or neither.
@phuongdm and I are doing a deployment on beta this evening to test and we will look at it over the weekend, provided we can recreate the issue on beta.
Thank you for your patience.

@aphelionz @alvacouch @phuongdm Given the information above, my hunch is that the ingest_irods_files script, which was written before composite resource was deployed if I remember this correctly, does not handle logical files, hence the logical file does not exist for re-ingested irods files in Django DB. In any case, it looks to me like a Django DB issue for this problematic issue.

@hyi @phuongdm @aphelionz It's worse than this. Look at the following:
hydro-service@beta hydroshare]$ ./hsctl managepy fix_missing_logical_files 7a77f525667b42f69cdc3f8d
b18e1280
...
SETTING GENERIC LOGICAL FILE FOR FILES IN RESOURCE 7a77f525667b42f69cdc3f8db18e1280
Logical file missing for file Observatory_Sauk_forJenLennon071017Jim.ipynb
Logical file missing for file data_48.15625_-121.28125.gz

This persists when repeated. The script to fix logical files isn't fixing them.

@alvacouch That was what I experienced as well... is it possible to manually fix this resource in the DB? just hand jam it for now and then do root cause analysis + fix after AGU?
cc @hyi @phuongdm

@aphelionz @hyi @phuongdm This is a class botch. The fix_missing_logical_files routine is calling the wrong fix routine. It's calling the default fix for BaseResource, which does nothing. Fix is imminent.

aha!

I have a fix for it which I am testing now.

Should I make it a hotfix?

It's a race!

@pkdash @aphelionz I have fixed this resource -- inelegantly --- and it works properly. The problem was that the set_default_logical_files was being called in the base class BaseResource, which does nothing.
If you want to take the ticket and make a hotfix, please do.
The deeper question is why this is happening on a widespread basis for people using jupyter. This seems to be a problem with REST calls that create files.

@alvacouch Yeah that's what I found when trying to debug the management script. Was calling the function on BaseResource class. Have now fixed it and testing locally and seems to work. Will make a hotfix today. Also would try to look into the rest call. Thanks

@pkdash Can you hotfix and also run the script on prod? That would be good considering it's the weekend and usage is low.

@pkdash (cc @aphelionz) I will be online today. Let me know when you have something to review.
Meanwhile I suspect there are code paths where the post-add signals are not being sent. I'll take another look at file creation myself and look for such places. I don't know if they're sent when we copy in from IRODS.

@pkdash @aphelionz Note that I fixed the resource of interest but that there are many others on beta that need the fix, so you can test your hotfix on those.

@pkdash I have reverted my changes on beta, so you can use that for testing. I am moving off beta to my own test servers.

@pkdash @aphelionz @phuongdm FYI: I am checking on the possibility that the exact same thing is happening when we add files that is happening in the management script, i.e., we get an instance of BaseResource rather than CompositeResource.
There is some crazy mezzanine stuff going on in hs_core/models.py that affects the routines that get resource type. I do not trust it.
Many of the REST calls use authorize:
https://github.com/hydroshare/hydroshare/blob/develop/hs_core/views/utils.py#L159
which calls get_resource_by_shortkey:
https://github.com/hydroshare/hydroshare/blob/develop/hs_core/hydroshare/utils.py#L68
which uses a rather funky mezzanine type conversion in models.py here:
https://github.com/hydroshare/hydroshare/blob/develop/hs_core/models.py#L3472
which might not properly account for proxy classes. The type returned by this is passed as the object when sending post_add_files signals.
If this type is incorrect, logical files won't get created.

All the more reason to gut mezzanine. However, the AGU mandate remains - we need to make sure things are functioning as smoothly as possible in the next ~2 weeks before we go in and get surgical on the system. For now we need to live with a working fix_missing_logical_files function that we run periodically. In the meantime, let's continue to catalog code paths that are affected by this to tackle after the conference.
Thank you for your looking into this @alvacouch @phuongdm @pkdash @hyi

@aphelionz I don't agree. If my theory is correct, we can safely patch the responders in the REST API.

@aphelionz @pkdash Theory incorrect. Still looking. Whatever it is seems quite systemic, though.

@alvacouch The only purpose of having this function get_resource_by_shortkey is to get a typed resource instance given a resource id. So I don't think the problem is with this function.

See #2456 that I just filed.  This may (or may not) have a similar root cause, but it is a presently reproducible way to create a resource that has content files that do not show in the display.

@alvacouch Here is the PR https://github.com/hydroshare/hydroshare/pull/2458 for you to review.

I will be online again in couple of hours.

@alvacouch The ingest_irods_files management command seems to have the same bug as the one I fixed for the missing logical file management command.  Have a look at this line: https://github.com/hydroshare/hydroshare/blob/develop/hs_core/management/commands/ingest_irods_files.py#L154

@pkdash Yes. Could you patch. it properly?

@aphelionz This behavior is probably caused by a one-line bug. So if we can find it, we should squash it.

Between @pkdash , @alvacouch , @phuongdm , and a tiny bit of deployment help from me… it looks like this is fixed. Please review at https://beta.hydroshare.org/resource/7a77f525667b42f69cdc3f8db18e1280/

Nice work!! Thanks everyone. HydroShare gets better every day.


#13 Adding a way to tell server callback to skip …

…setting status code or sending content.

Codecov Report

Merging #14 (d8990c1) into main (75d7c2b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #14   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          283       286    +3
  Branches        28        28
=========================================
+ Hits           283       286    +3

Flag
Coverage Δ

server
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

server/src/server.ts
100.00% <100.00%> (ø)


Not getting the reg. email.

Tried making two different accounts with two different emails. But I never recieve the reg. email on either of them. And when i press "Never got the registration email?" nothing happens :(
Please help :)
Best regards,
Adrian from Denmark.

Same problem.

It's not working for me either. I tried multiple emails and also tried resending the registration emails.

@EskiMoses @dcjoker @BokkieDoke your accounts should be activated now


Already read items still appear in search results as unread

Newsbeuter is pretty and very useful for me, but, unfortunately, it suffers from some small bugs. One of this bugs annoys me very much. It can be reproduced very easily:

start a search in an RSS feed
read some articles
quit search
run new search

And voila! You can see your read articles again, marked as unread, among with other articles that are relevant to the search string.
I tried hard to create working UI test that demonstrates this, and after all, here it is. Here I start a search that finds two articles (31), read one of these articles (39), reset a search (45) and start a new one (56). After that I expect that already read item should not be shown (60). But it is.
Here is a test log:
I: On (1,3), found `1 N  Aug 30   212   |RSS 2.0 testbed f|  RSS 2.0 Item 1' as expected.
I: On (1,3), found `1    Aug 30   212   |RSS 2.0 testbed f|  RSS 2.0 Item 1' as expected.
I: On (2,3), found `2 N  Aug 28   170   |RSS 2.0 testbed f|  RSS 2.0 Item 3' as expected.
E: On (1,3), expected `1 N  Aug 28   170   |RSS 2.0 testbed f|  RSS 2.0 Item 3', but found `1 N  Aug 30   212   |RSS 2.0 testbed f|  RSS 2.0 Item 1'

Unfortunately, I'm not able to fix this issue yet, but I hope that working test could help identify root cause of this issue, Therefore, I just provide a test at this time. I hope this issue could be fixed!

@akrennmair Could you please merge this pull request and release a new version of newsbeuter?

Hi. Thought I'd chime in and explain why this hasn't been merged over the last half a year that I've been maintaining the codebase.
The work is incomplete, as the author himself mentioned in his last comment. I focused my attention on issues for now, but I'll look into this one eventually. If you're interested, you can complete the patches—reviewing complete PRs is much less work than fixing bugs, so I'll be able to merge it pretty quickly.
As for the release, I've put 2.10 together a while ago, but @akrennmair hasn't gotten around to releasing it yet. Looking forward to it just as much as you do!

So, first of all I need to check whether this bug appears in new versions. Please give me some time to take a look at code.

My investigation reveals that the first attempt to fix the bug was really crappy. So I've started from the very beginning and found much simpler solution. Please take a look at #339. I think, current pull request should be closed now.
@cambid @Minoru thank you for the ping!


Mp2 driver

MP2 Module
Will implement two functions mp2 and df_mp2 that will compute conventional and density fitted mp2 correlation energies.
Questions:

[ ] Return should be MP2 correlation energy? or full MP2_ energy

TODOs:
Conventional MP2:

[x] Conventional energy function
[x] MO transform amjames/SSS_2017_QuEst/#5
[x] Denominators amjames/SSS_2017_QuEst/#6
[x] Energy function amjames/SSS_2017_QuEst/#7

DF MP2:

[ ] Energy Expression

Interface

[ ] Update wfn and return energy

Misc

[ ] Docs fix docstrings to follow numpy style guides
[ ] Add testing for all module internal functions

[ ] ready to go

AJ please resolve the conflicts and let me know when you have a unit that I can merge in!

@Kee-Wang , It looks like you droped some MP2 code in as a placeholder, but I had already done the same thing on this PR. I'm going to remove it when I resolve.

@dgasmith this is ready to go


OCPBUGS-6357: Rebase to v1.5.0 for OCP 4.13

Diff to upstream v1.5.0:
https://github.com/kubernetes-sigs/aws-efs-csi-driver/compare/v1.5.0...RomanBednar:rebase-v1.5.0
I cherry-picked:

https://github.com/kubernetes-sigs/aws-efs-csi-driver/pull/897 to get golang.org/x/net v0.5.0 which resolves CVE-2022-41717

Notable changes since v1.4.9:

None

Full changelogs:
https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-1.x.md#v150

cc @openshift/storage for review

/lgtm
/approve


add tds configuration information

Tony, are the rabbit-dev and rabbit-htx systems, above this one, still correct?

rabbit-dev can be removed


part of PR 340 adding test_setup_ptmx and test_setup_default_symlinks

as requested by separating #340 into small PRs
this one is the fourth part of adding two test cases:

test_setup_ptmx
test_setup_default_symlinks

please help review 🙇🏻

Codecov Report

Merging #359 (ed5895c) into main (7f91bc6) will increase coverage by 0.39%.
The diff coverage is 61.53%.

@@            Coverage Diff             @@
##             main     #359      +/-   ##
==========================================
+ Coverage   70.18%   70.57%   +0.39%
==========================================
  Files          48       48
  Lines        7409     7420      +11
==========================================
+ Hits         5200     5237      +37
+ Misses       2209     2183      -26


The developer mode renewal script exposes the private ssh key to unintended users for a short time

Describe the bug
When going to the Info > Automatic Developer Mode Renewal > Script section, the code reads as such:
https://github.com/webosbrew/dev-manager-desktop/blob/669387f8f95e6463e2cc66931eb81780a0746076/src/app/info/renew-script/renew-script.sh#L9-L15
Observe that this script first writes the key to the usually world-readable+sticky-permissions /tmp/, and only then chmods the file to 0600 to restrict the access to it.
This is racy and it is quite possible that an external observer would be able to open the file before the permissions to it are changed.
Expected behavior
The script should instead utilize the umask mechanism to set a permissions mask before creating the secret key file, thus making it create the private key file with the correct permissions straight away.
An alternative method would be to create a directory within /tmp, set the 0700 permissions on it and only then create the file within that directory.
Screenshots
N/A
Additional context

OS: N/A

What do you think about ddbc8f2? I'm not really set up to test it. Also, I'm not sure what platforms this script is supposed to run on and if mktemp is available on all of them.

This looks good for me in context of linux at least. mktemp does exist on macs and as far as I know BSDs too. Ultimately if people are grabbing the script and integrating it into their systems, more likely than not they will know how to adjust it to work on their system in absence of mkdir, whereas if it works, but exposes secrets, it might go by unnoticed.

Yet another option would be to create and set up file before writing data to it:
touch file
chmod 0600 file
echo "$key" > file

but I'm partial to the mktemp variant personally.


Discord Module "Connection Failure" On Linux

I'm trying to switch to using Linux, and companion seems to be a good way to control the Stream Deck.
I was able to use "shell path local" to somewhat work around using terminal commands under my main account, and I assume a similar issue might be in place for the discord app. However I'm knew to this and not sure if this is the case.
(NOTE: the shell work around was to use "echo  | su -  -c "". Not secure but was for testing.)
To Reproduce
1.Open discord on your machine
2. Add connection to "Connections" tab in Companion
3. Create discord application and follow the installing steps
4. Open the "Logs" option for the module
5. Turn the module on and off.
6. last error "debug: Login err: {}"

Expected behaviour
Considering I'm still learning this all, my "expected behavior" is to be able to control discord.

Companion Version
I tried Stable Versions v3.2.1 to v3.3.1
Along with Beta Version 3.4.0+706-main-849878c4

Additional context
This is being done on a repetitively clean install of Linux. Specifically PopOS.
I have tried both the Discord version in the PopOS repository and the DEB file from the Official Discord website. (I believe both of these are the "official" version.)

If Companion is running on the same machine as Discord, Discord is from the official Discord website, and you're not doing any sort of sandboxing of apps, then there's not much support I can offer.
I don't use Discord on my Linux machines so can't test myself, but others who have ran in to issues previously on linux have all been due to sandboxing, so I'd recommend you investigate that on your end.

I didn't consider sandboxing might be happening. I will try to look into that over the next few days.
If I find anything I'll be sure to post here. Or if I find the "fix".

I am having the same issue, but discord is sandboxed. Let me know if there's a fix!

The fix is to not sandbox Discord, or configure your sandbox to allow the IPC between Companion and Discord.
There's nothing that can be done on this modules side if a sandbox is being used to explicitly block the connection that's required.

How would I do this with a flatpak? I have flatseal, so I can easily allow requests. Is there a certain interface that I have to allow discord to receive?

I don't use Flatpak so I can't offer much guidance other than to suggest reading through their documentation and seeing how to allow IPC communication, as that's how the Companion module communicates with the Discord client running on the system.

I'm just wondering if there's a certain interface the module communicates on that needs to be allowed by flatpak. Like, for example, localhost:8080

Most likely the Inter-process Communications checkmark on Flatseal, right?

Closing this issue as there have been no further reports, and the issue appears to entirely be related to installing Discord in a sandbox which by design would block connections such as this module unless configured otherwise.


Add "Open Cargo.toml" action

What is it?
This adds an "open cargo.toml" action from the vscode shell, resolves #6462
Test
Ran cargo xtask install --server and cargo xtask install --client, then Developer: Reload Window.

When clicked:

Hey @lnicola, @matklad it looks like I've accidentally merged this PR from my command line--I'm really sorry about this :|. I thought that I would be pushing just to my local branch, and I did not imagine that it would be on the rust-analyzer version od the repo.
The reason why I did this was because I was failing a merge-commit test, and the messaging said:
# Push the changes. We did a rebase, so we need `--force` option.
  # `--force-with-lease` is a more safe (Rusty) version of `--force`.
  $ git push --force-with-lease
```.

At any rate, is there a way I can re-open this?

The changes look good to me, but there's still a bit of a mess in history. Lets try to clean up.
@p3achyjr I think the following steps should help:

run git status to make sure you don't have uncommited files
run git log to make sure that the latest commit has the e1c953c hash (to make sure state you have locally and state we see on github are the same)
run git reset --soft 111cc34c8f181315f4dcfa85c616d54d47eff0b9. This should reset the branch state to the commit on the base branch, from which you started your hacking. The --soft flag however preserves your changes (state of the files on the file system) intact
run git add . && git commit -m 'add open Cargo.toml action' to commit all your changes as a single commit (but make sure there's no .DS_store file)
run git push --force-with-lease to push the changes to github.

Thanks @matklad. I was running into issues where whenever I ran git commit --amend, I could not push my changes because I would have to run git pull first. This was further complicated by how whenever I ran git pull, I would get merge conflicts.
The steps worked though! Will keep this in my back pocket :)

Hm, there's still something wrong with history (.DS_Store file is still there), but I'll fix that up locally!
bors r+
Thanks!


fix sync val error in virtual swapchain Blit

fixes #991

CI gfxreconstruct build queued with queue ID 26712.

CI gfxreconstruct build # 2445 running.

CI gfxreconstruct build # 2445 passed.


Deploy to DO Droplet

Adding a volume to the correct mount point
formatted volume:
# on the attached droplet
sudo mkfs.ext4 /dev/disk/by-id/scsi-0DO_Volume_deliberation-empirica-dotempirica-volume

created .emprica folder at root
cd /
mkdir .empirica

Mount the given volume
mount -o discard,defaults,noatime /dev/disk/by-id/scsi-0DO_Volume_deliberation-empirica-dotempirica-volume /.empirica

Change fstab so the volume will be mounted after a reboot
echo '/dev/disk/by-id/scsi-0DO_Volume_deliberation-empirica-dotempirica-volume /.empirica ext4 defaults,nofail,discard 0 0' | sudo tee -a /etc/fstab

Enabling websockets
Building a GH action to start the server
Needs to:

Install empirica and node dependencies in server/client
bundle the experiment
transfer to server

Log forwarding
Should forward the console logs to sentry, if we can do that? Otherwise saving them to a file.

Websockets is a bear, and caddy isn't making things any easier. I think I'm giving up on this for now.


deps: update auth libraries

@rghetia

@elharo can you please remove the merge commit and resubmit?


Update AppVeyor CI to use librdkafka 1.6.2

librdkafka 1.6.2 is now ready to use for Windows. If all is good, I'll replace 1.5.3 with 1.6.2 for the PECL builds as well.

@cmb69 thank you so much for this, i highly appreciate it. Have an awesome weekend :tada:

For the record: I have deploy librdkafka 1.6.2, so PECL builds will use the new version from now on.

@cmb69 awesome, many thanks again :bow: :pray:


Update example-cqs-mvp-template.json

Adding header re primary/aggregator knowledge sources. @jdr0887 : will this approach work for you?

This PR can be closed, as Jason updated the template using fields within the TRAPI query, rather than the suggested header.


The simulator doesn't seem to use the GPU when training baselines.

Habitat-Lab and Habitat-Sim versions
Habitat-Lab: vx.x.x or master?
master
Habitat-Sim: vx.x.x or master?
master
Habitat is under active development, and we advise users to restrict themselves to stable releases. Are you using the latest release versions of Habitat-Lab and Habitat-Sim? Your question may already be addressed in the latest versions. We may also not be able to help with problems in earlier versions because they sometimes lack the more verbose logging needed for debugging.
Master branch contains 'bleeding edge' code and should be used at your own risk.
Docs and Tutorials
Did you read the docs? https://aihabitat.org/docs/habitat-lab/
yes
Did you check out the tutorials? https://aihabitat.org/tutorial/2020/
yes
Perhaps your question is answered there. If not, carry on!
❓ Questions and Help
I use the following command to train the baseline model.
bash ./habitat_baselines/rl/ddppo/single_node.sh

It seems like only the model (type C) is running on GPU and the simulators are not. I don't why.

@erikwijmans Could you please help me?


Detection Mode in modse 2.9.0

Describe the bug
I've configure the modsec 2.9 to run with an apache server.
The engine is set to Detection only, with a rule to test that behaviour
SecRuleEngine DetectionOnly
SecRule ARGS:testparam "@contains test" "id:'1234', phase:2, t:none, deny, status:403, msg:'Testing de DetectionOnly en WAF'"
For what I understad, that rule should appear in the audit log file, but dont do any disruptive actions in the browser.
Nevertheless, I receive an 403 on the browser.
Should I do a specific notation in every rule?
Thanks in advance!
Logs and dumps
Output of:

DebugLogs (level 9)
AuditLogs
Error logs
If there is a crash, the core dump file.

Notice: Be carefully to not leak any confidential information.
To Reproduce
Steps to reproduce the behavior:
A curl command line that mimics the original request and reproduces the problem. Or a ModSecurity v3 test case.
[e.g: curl "modsec-full/ca/..\..\..\..\..\..\/\etc/\passwd" or issue-394.json]
Expected behavior
A clear and concise description of what you expected to happen.
Server (please complete the following information):

ModSecurity version (and connector): [e.g. ModSecurity v3.0.1 with nginx-connector v1.0.0]
WebServer: [e.g. nginx-1.15.5]
OS (and distro): [e.g. Linux, archlinux]

Rule Set (please complete the following information):

Running any public or commercial rule set? [e.g. SpiderLabs commercial rules]
What is the version number? [e.g. 2018-08-11]

Additional context
Add any other context about the problem here.

Sorry for not deleting the generated text. First time posting here

I found the error. There was an error in the configuration of the virtual host


Highly dynamic data storage

Description
A storage type that does not track changes.
Motivation
We need to have a way to store highly dynamic data without bloating the stronghold file.
Requirements

define type at creation
not bloat the changelog (and explode the size of the stronghold)
be tuned for performance

Open questions (optional)
Datastructure: trie could be nice, but also a minor engineering feat
@bernardoaraujor

From the perspective of IOTA Access, it's important to have a secure storage for Access Policies.
Since IOTA Access Servers run on constrained devices, there needs to be some upper limit to the size of the Strongheld Policies.
At the moment I can't think of any criteria under which Policies would be dumped when limit is reached.
Assume time: when reach storage size limit of Strongheld Policies, erase oldest Policy.
A simple approach for implementation would be:

Strongheld Policies are stored in a circular buffer, which is implemented as an array of pointers to each SP.
For every new store_policy operation, increment head pointer.

That keeps the vault for Strongheld Policies as constant size.

Also related to your comment @bernardoaraujor - #27

@cvarley100 & @laumair - would love to have your feedback on this feature request as well.

perhaps related to this issue: https://ferrous-systems.com/blog/lock-free-ring-buffer/

This will resolve with the new client.


Update centralized-deployment-of-add-ins.md

updated licensing requirements

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/6430

@kwekuako Please merge this PR. Thanks


Add "url" option to ol.source.MapQuest

We already have that option for other tile sources like OSM and Stamen so it makes sense to have it for MapQuest as well.

LGTM


Testify suite support

Hello,
I tried the module with test suite and it retrieves the name of the suite, not the subtest.
Its quite problematic as a suite can contain lots of subtests and it does not provide a way to execute a specific context.
What do you think about adding it ?

Not sure if I understand what you mean by "execute a specific context " but if you want to debug just a specific subtest you can run :lua require('dap-go').debug_test(). It will find the nearest test from the current cursor position and start a debug session just for that.
Is this what you want?

By context I meant the subtest of a testify suite.
I tried it and I think I got an error.
I'll try to add some example here.

How many levels of subtests do you have? I constantly debug testify test with one subtest and it works. I know that there is a limitation if you have more than 2 levels of subtests. I already have a patch to fix this btw. I just need to find time to apply it. Will let you know when I do it.


fix(kslideout): title and content styles

(Branched off of the work for https://github.com/Kong/kongponents/pull/1770 so targeting that PR’s branch for now)
Summary
This PR mainly aims at reducing the need to override some of KSlideout’s default styles by making the layout a bit more consistent and adjusting the spacing between certain elements.
fix(kslideout): overriding KCard padding
Removes the custom padding override of .kong-card so that the content area has the same padding as KCard.
fix(kslideout): title styles
Addresses a number of style issues of the title bar in order to achieve a better default appearance.
Removes the margins added to the title, before title, and after title containers and instead adds a padding to the header making the title bar appear flush with the content.
Reduces the gap size between title, before title, and after title to allow for more flexible usage scenarios.
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>Notes

Markup changes: I’m changing the markup of the component here which might interfere with the development efforts that are on-going for Kongponents v9, but this depends on whether there are plans to change this component much in that process. Let me know, happy to make changes.
Before/after title slot usage: I’d like to hear about current use cases for the before/after title slots as I’m making changes to how those are spaced-out in the header.

The overrides we currently find ourselves using (with Kongponents v8) without these changes:
.k-slideout {
  // Overrides KSlideout’s override so the padding is the same as that of KCard.
  --KCardPaddingX: #{$kui-space-80} !important;
  --KCardPaddingY: #{$kui-space-80} !important;
}

.k-slideout-header-content {
  padding-right: $kui-space-80;
  padding-left: $kui-space-80;
}

Screenshots
Before:

After:

PR Checklist

[x] Conventional Commits all commits follow the conventional commit standards outlined in the main README.
[x] Tests coverage: test coverage was added for new features and bug fixes
[x] Docs: includes a technically accurate README

Closing this as it was superseded by #2012.


WIP Fix 112

Fix a couple of corner cases found when updating metadata in my blog

Argh, branched off the wrong place.


How to set security level?

@ankitpokhrel Thanks for great software.
I would like to set security level. Is it possible to set it using custom fields?
 Should I add it manually? I don't know how to add such type of field.
Any hint will be appreciated.

Hi @klaudiusz223, security field is not a custom field as per your config and setting this field is not directly supported. However, you can try to update the config file manually to see if it works.
- name: Security
  key: security
  schema:
    datatype: array
    items: json

# jira issue create --custom security="Level 1"

Note that you need to provide correct datatype in schema, it should be json array I think.

Hi @ankitpokhrel
Thank You for the answer.
I have not tried to set the security field yet because in my case it can create a ticket with the default secuirty level, which means that I will not be able to access it. Unfortunately, I have no influence on it. I don't have administrator privileges in JIRA. Besides, I read somewhere that setting security level is not possible when creating a ticket, but it can be changed after creation. If this is the case, it means that in my case it will not work for the reasons I wrote above.
But it turned out that I am forced to set different customfield and unfortunately without success.
my setup is
            - name: functional
              key: customfield_11111
              schema:
                datatype: array
              items: json

the correct request has the form (succeeded using curl)
        "customfield_11111": [
            {
                "id": "20009"
            },
            {
                "id": "20010"
            }
        ],

If I run using parameters
--custom functional = {"id": "20009"}, {"id": "20010"}
it is transformed in body to
"customfield_11111": ["{id: 20009}", "{id: 20010}"]
and should be
"customfield_11111": [{"id": "20009"}, {"id": "20010"}]
I tried several ways, quoting \ using ', but with no success.
e.g.
 --custom functional = {id: 20009}, {id: 20010}
--custom functional = {"id": "20009"}, {"id": "20010"}
--custom functional={\"id\":"20009"},{"id":"20010"}
--custom functional='{"id":"20009"},{"id":"20010"}'
--custom functional='{'id':"20009"},{"id":"20010"}'

I'm not sure if this is a bug or I do something wrong

I'm also unable to set custom fields, I am failing to get the example story-points working. I've tried both the name and customfield_ formats as the reference

I also am unable to set story points.
It is present as an available createmeta field:
curl -k --request GET \
  --url "${JIRA_SERVER?}/rest/api/2/issue/createmeta?projectKeys=PE&expand=projects.issuetypes.fields" \
  --user "<user>:${JIRA_API_TOKEN?}"

output contains:
"customfield_10006":{"required":false,"schema":{"type":"number","custom":"com.atlassian.jira.plugin.system.customfieldtypes:float","customId":10006},"name":"Story Points","fieldId":"customfield_10006","hasDefaultValue":false,"operations":["set"]}

I have added the following to my .config/.jira/.config.yml file:
  fields:
    custom:
    - name: Story Points
      key: customfield_10006
      schema:
        datatype: number

However, none of these has an effect on ISSUE-123 (even though visiting ISSUE-123 via Web UI does allow me to edit the custom "Story Points" field):
jira issue edit ISSUE-123 --custom=story-points=1 --no-input
jira issue edit ISSUE-123 --custom story-points=2 --no-input
jira issue edit ISSUE-123 --custom "story points"=3 --no-input
jira issue edit ISSUE-123 --custom "Story Points"=4 --no-input
jira issue edit ISSUE-123 --custom="Story Points"=3 --no-input --debug
jira issue edit ISSUE-123 --custom=customfield_10006=4 --no-input --debug

I can see the following output in the terminal:
✓ Issue updated
JIRA_SERVER/browse/ISSUE-123

However, the story point in ISSUE-123 remain unchanged.

Just checked on Jira v8.22.1 and it seem to be working fine in my installation.
@MattPD your config looks ok to me, could you please mention what version of jira you are using? You can get it with jira serverinfo if you are using the latest version of jira-cli.
@rhysjtevans Any additional details to help debug the issue would be great (eg: is this happening for just story points custom field or others too?).

Interesting--I do have the latest release but it doesn't appear to be recognized:
$ jira serverinfo
Error: unknown command "serverinfo" for "jira"
Run 'jira --help' for usage.
unknown command "serverinfo" for "jira"

$ jira version
(Version="1.1.0", GitCommit="3b93e147eac468ad985bdece27469153b4bb2814", CommitDate="2022-08-14T08:10:40+00:00", GoVersion="go1.18.3", Compiler="gc", Platform="linux/arm64")

I can wait for the next release if this requires the latest commit build--or perhaps there's some way I can check this via Curl?
FWIW, the bottom of my Jira Web UI says "Atlassian Jira Project Management Software (v8.20.5#820005" and visiting the AboutPage.jspa shows
Jira v8.20.5
Copyright © 2002 - 2022 Atlassian Corporation Pty Ltd.

Hi @MattPD, serverinfo command is not yet released, my bad. I checked this on Jira v8.20.5 and the story points is updated successfully in my installation.
It would be helpful if someone can debug this a bit and provide more info.


Add taskList throttling to allow users to limit activities executed per second

Fixes https://github.com/uber/cadence/issues/50

Coverage increased (+0.08%) to 66.321% when pulling 24e626c31190ac55b73559d1263fee9abb72bf16 on tasklist into cadabad906c89c1ac56ec3fbfdcaf1af644820cc on master.

Coverage increased (+0.1%) to 66.351% when pulling e7a1fbdf24198996114f6a8e5f3abc5bc7c78757 on tasklist into cadabad906c89c1ac56ec3fbfdcaf1af644820cc on master.

Coverage increased (+0.1%) to 66.363% when pulling 85fac838af56e73766a6f8adc6db44a984d55e1e on tasklist into cadabad906c89c1ac56ec3fbfdcaf1af644820cc on master.

Coverage increased (+0.2%) to 66.406% when pulling c93e34cd025b5e3cad2df5d0c438e7e6accabad0 on tasklist into cadabad906c89c1ac56ec3fbfdcaf1af644820cc on master.

Coverage increased (+0.3%) to 66.871% when pulling 2dff6f6694070e8f9d2b65a971838c8d9d616670 on tasklist into 26303d59c643c45ab0dcaefd2688cdc413d84398 on master.

Coverage increased (+0.3%) to 66.876% when pulling 2dff6f6694070e8f9d2b65a971838c8d9d616670 on tasklist into 26303d59c643c45ab0dcaefd2688cdc413d84398 on master.

Coverage increased (+0.4%) to 67.059% when pulling 623475c580083c268f2605def55514ad8f57c210 on tasklist into 26303d59c643c45ab0dcaefd2688cdc413d84398 on master.

Coverage increased (+0.4%) to 67.001% when pulling 744025f7255be41bb670a3ef72927137d09d8f83 on tasklist into 26303d59c643c45ab0dcaefd2688cdc413d84398 on master.

Coverage increased (+0.2%) to 66.999% when pulling 46f4c3ee65c2e3974df1081f8333fdcaa30b0346 on tasklist into 36c6f54ed83bc414dfca96a0092ccaff763abdb7 on master.


added some profile changes and a new picture

@johnchase, we actually need to add your office hours in the gregcaporaso/teaching-website-source repo, not here (the html here is built automatically). Can you remove that change from this PR, and I'll add to the other repo? I can show you how I update the teaching website so you can do it in the future (I have a build script that makes it really easy).

@johnchase, note that there is a conflict now that I've updated your office hours using my build script.

@gregcaporaso I changed the file back to what it was originally.

@johnchase, something went wrong with this and you've got all of everyone else's commits included. Can you submit a new pull request with just the updates to your picture and profile? I think that will be easier than trying to fix this one.


2fa update

This PR implements a suggestion from the code review and other small things.

The $type for the TwoFactorAuthEmail action has been changed
We're making sure we only display options that users are allowed to use on the Security page
The policy helper function was fixed

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 79.302%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
1613

Relevant Lines:
2034

💛  - Coveralls

@datamweb I forgot to check it and indeed it doesn't work... we went back to the original type though.
Thanks for double-checking.


Problems encountered when using FLAME GPU

Dear FLAME GPU team,
I tried to use FLAME GPU for agent-based modelling in my research. However, since I am not a skilful programmer and have only written simple programs in Java and C, I have encountered many problems when exploring the FLAME.
The screenshot pictures attached are the interface when I run an example (Boids_BruteForce) in the FLAME SDK. I use VS 2019 and CUDA 11.2. At this point, I have changed the CUDA version in Boids_BruteForce.vcxproj to 11.2. I don't know why there were so many errors and this made me confused. Are there any settings that have not been completed?
Thank you so much for answering my question!
Best regards,
Haoyang

Hi,
I don't think that FLAME GPU 1 is currently compatible with CUDA 11.
If you can, using CUDA 10.2 should work.
CUDA 11 includes an updated version of the Thrust library, which includes a full  copy of Thrust, which conflict with the verison we include (supporting older versions of CUDA).
We've not found a simple solution to support CUDA 10 and CUDA 11 without changing changing the build system or duplicating work.
Visual Studio intellisense also generates a lot of incorrect errors/warnigns with CUDA. If you hide intellisense errors from the  log it will greatly reduce the numbers of errors reported, though CUDA 11.2 will still not work.
This is related to  #284

Thanks so much for your help Ptheywood!
I successfully used CUDA10.2 to build the solution 'Boids_BruteForce' in Visual Studio. I want to run the console mode and visualization mode of the project on Windows with my local GPU. What should I do next?
I tried to call Visual Studio's nmake.exe to run the makefile in the directory, but it gave me such an error message. This was confusing.

How can I get the output XML files and generate a visualization window?
Thanks again for your help!
Haoyang

The Makefile provided is for building under linux, it's not needed in windows.
In Visual Studio 4 build configurations are provided, Release_Console, Debug_Console, Release_Visualisation and Debug_Visualisation. You can either select configuration from the drop down at the top, or use the batch build process to build multiple configurations.
You'll want to build the Release_Console and Release_Visualisation configurations.
Once the builds are complete, the executables will be placed into FLAMEGPU/bin/x64/Release_Console/ and FLAMEGPU/bin/x64/Release_Visualisation. Batch files are provided in the FLAMEGPU/bin/x64 folder for each example to show how they can be used.
The console version will place output .xml files in the same directory as the input xml file (probably FLAMEGPU/examples/Boids_BruteForce/iterations/, with 0.xml used as the input file, and 1.xml, 2.xml, ... as the output file for each iteration. I don't believe the visualisation executables will generate output files.

Hi Ptheywood, thank you so much that with your help, I could now modify the FLAME GPU models to a certain extent according to my wishes.
I am currently interested in an example model PedestrianNavigation. I would like to ask, in the XML document of this model, how are the directions of 256*256 Navmap agents pointing to different exit definitions calculated? Is there an introduction to their calculation methods?
Thanks again for your help!
Haoyang

I believe that the following paper describes the pedestrian navigation model, with some discussion of the force vector fields (FVF).
http://paulrichmond.shef.ac.uk/cv/publications/eguk2010_vectorfields.pdf
In addition the following paper describes teh development of a tool to generate force vector fields using an interactive tool. Section 3.5 and Figure 5 describe how the FVF can be calculated using a flood fill algorithm.
I'm not sure if this tool is publicly available anywhere.
http://diglib.eg.org/bitstream/handle/10.2312/cgvc20161304/105-112.pdf
Section 3.1 of Twin Karmakharms' thesis provides a more detailed description of the vector field generation:
http://etheses.whiterose.ac.uk/20938/


Allow option to configure whether users are auto-created from OIDC-backed logins.

Add a configuration option, default['firezone']['authentication']['auto_create_users'] that determines whether users are created when signing in via OIDC for the first time.
This will allow admins to only create users they wish to allow into the instance (leaving the password empty).

HI,

Related to https://github.com/firezone/firezone/issues/585

@rchekhina #728 will fix this and be available in the next release.


Add postcss to package.json to prevent faulty upgrade

Added postcss version number as the upstream postcss deps have wildcard versioning, causing a failure in cra/react-scripts as per #9655. The fix was originally from #9658 , so I am reopening this pull request.

The fix was released in PostCSS 7.0.34. This PR can be removed.

Issue was fixed with the release of https://github.com/postcss/postcss/releases/tag/7.0.34 , closing pull request. Thank you @ai for the fix.


Made flags multivalue.

This makes it possible to run many different scenarios in a single execution.

Sorry, I know that you've put in a lot of work here, but I just can't see that this is the right way to go.

I'd push ever so slightly to dropping the shell script and encapsulating
the configurations we need as separate driver binaries (much like we have
for the smoke test).
It becomes much easier to take them then and 'drop them into the lab' and
run them locally with a profiler.
On Mon, May 18, 2015 at 9:39 AM Vijay Pai<EMAIL_ADDRESS>wrote:

Sorry, I know that you've put in a lot of work here, but I just can't see
that this is the right way to go.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1634#issuecomment-103121683.

+1 for binaries. However, it seems we have a large number of different
scenarios. At any rate, we should get to a decision, even if it's a
temporary one to be revisited down the road.
On Mon, May 18, 2015 at 9:51 AM, Craig Tiller<EMAIL_ADDRESS>wrote:

I'd push ever so slightly to dropping the shell script and encapsulating
the configurations we need as separate driver binaries (much like we have
for the smoke test).
It becomes much easier to take them then and 'drop them into the lab' and
run them locally with a profiler.
On Mon, May 18, 2015 at 9:39 AM Vijay Pai<EMAIL_ADDRESS>wrote:

Sorry, I know that you've put in a lot of work here, but I just can't see
that this is the right way to go.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1634#issuecomment-103121683.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1634#issuecomment-103127049.

Dropping.


Add Simplified Chinese translation

Description
Since there is no Simplified Chinese language file in 1.12, the translation in this pr is not based on any old version of Ender IO, but has used both the zh_cn.lang in 1.10 and the translation provided by CFPA  for reference.
Checklist:
(is this a code pull request?)

[ ] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you)
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Thanks for the effort, I would like a second person to verify this

I think the review is almost there. Every suggestion has been resolved. In fact, the translation also has been reviewed by some players in this pr https://github.com/CFPAOrg/Minecraft-Mod-Language-Package/pull/2160. @agnor99

Thank you for your work on this, I have uploaded your current translations to crowdin for further collaboration.
https://translate.enderio.com/


Luau-LSP Roblox Plugin Bug

After connecting to Roblox Studio with the Luau-LSP plugin, instance type refinement starts to dysfunction. I do not experience this issue with Roblox Studio's script editor.
workspace.Terrain.ChildAdded:Connect(function(objAdded)
    if objAdded:IsA("BasePart") then
        objAdded.Transparency = 1
    end
end)

This doesn't just affect the plugin instances but also affects instances declared in the sourcemap


[r20.03] pure-ftpd: add patches for CVE-2020-9274, CVE-2020-9365

Motivation for this change
Backport of #95280
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pure-ftpd

Result of nixpkgs-review pr 95456 1

1 package built:
- pure-ftpd

Thanks!


Allow do migrations in environments

What this PR solves / how to test
Allow Durable Object migrations to be overridable in environments. By making the migrations key inheritable, users can provide different migrations for each wrangler.toml environment.
Resolves https://github.com/cloudflare/workers-sdk/issues/729
Author has addressed the following

Tests

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[x] Required / Maybe required
[ ] Not required because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Public documentation

[x] TODO (before merge)
[ ] Cloudflare docs PR(s):
[ ] Not necessary because:

Does this make migrations under environments mandatory, or will it pick up the top one if we don't define it?

To avoid a breaking change it is inheritable so it will be picked up from the top level.


Validation Service: Updated error messages

This PR addresses requested error message changes for the HL7 validation service.
It

successfully updates ORU and MSH error messages to include the field property
successfully updates the bad timestamp message to include format
does not remove field name from some error messages
does not fix error messages or stack traces from external library errors

Test Steps:

Using these files, ensure errors and warnings are successfully updated

Changes
Successfully updates ORU and MSH error messages to include the field property

Successfully updates the bad timestamp message to include format

DOES NOT Change
Field names in error messages were essential for accurate error and warning reporting. Observe the following two images:

In the second one, without the unique field name present in the error string, they were inaccurately consolidated. The change required to fix that is out of scope for this work but can be ticketed and completed, or left as is.
It also does not fix messages and stack traces from external libraries. Notably, the following error message which was requested to change:

Error parsing HL7 message: ca.uhn.hl7v2.validation.ValidationException: Validation failed: Primitive value '08112022' requires to be empty or a HL7 datetime string at PID-29(0)

This, as well as the stack trace presented by the phone number parser library, are great candidates for an MVP implementation of Codified Error Messages (aka, the Error Message Makeover!) (aka ticket #7277)
Checklist
Testing

[X] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[X] (For Changes to /frontend-react/...) Ran npm run lint:write?
[x] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #7128

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

CC: @mauricereeves @BerniXiongA6 re: Date format error string conversation in Teams!

@kevinhaube These screenshots look perfect! Thanks for this great work. I do notice that "requested edit" is not necessarily always the best descriptor of what falls into that column. I'll keep that in mind through the next phase of UX testing (so no change needed at this point). I think we can consider this design reviewed.


cannot run testrpc on mac (wrong line ending?)

I installed testrpc on MacOS and then tried running it and ran into an error:
$ npm install ethereumjs-testrpc -g
$ testrpc
env: node\r: No such file or directory

This used to work well but now shows the above error. The issue is clearly related to this one and hence I managed to fix it by opening /usr/local/bin/testrpc (which seems to link to /usr/local/lib/node_modules/ethereumjs-testrpc/build/cli.node.js), removing the line break in line 1 and adding it again and saving the file.

Hi there. Thanks for the report! The issue has been fixed in v4.1.3. Cheers!


Export CredentialUnavailableError

This error type exists so a credential that can't acquire a token due to some non-fatal reason can signal ChainedTokenCredential to try another credential. For example, ManagedIdentityCredential returns this error type when managed identity isn't available in the runtime environment. Today, because this type isn't exported, ChainedTokenCredential treats all errors from custom credential implementations as fatal and therefore never tries the next credential in the chain. https://github.com/Azure/azure-sdk-for-go/issues/19699#issuecomment-1352295710 describes a scenario blocked by that behavior.
I also updated ChainedTokenCredential to behave the same whether a CredentialUnavailableError is wrapped or not, so custom credentials can propagate other errors more easily.

We need to start with a very super clear definition of what "non-fatal" means exactly.
What I'm worried about is unpredictable behavior where a credential considered something non-fatal and so the chain picks the next one but this non-fatal error is successful in the future and now a different credential is in effect. It is critical that behavior be consistent & predictable all the time once the process starts.
So, I assume a network error is non-fatal because another attempt may succeed? But some EnvironmentCredential always fails if the env var doesn't exist or has a bad value? But then, what if the process adds the env var or changes the value? Then this EnvCred in the chain will now work and be used in a new client?
Let's discuss this at our next scrum meeting.

What I'm worried about is unpredictable behavior where a credential considered something non-fatal and so the chain picks the next one but this non-fatal error is successful in the future and now a different credential is in effect.

I agree that would be bad. Fortunately, the default behavior of a chain is to reuse the first successful credential for all subsequent authentications. If the chain is A -> B and A returns CredentialUnavailableError while B succeeds, the chain won't try A again.

I assume a network error is non-fatal because another attempt may succeed?

No, network errors during authentication are fatal in that they cause credentials to return other error types. CredentialUnavailableError means a credential can't attempt to authenticate because the runtime environment lacks some necessary data or state.

But some EnvironmentCredential always fails if the env var doesn't exist or has a bad value? But then, what if the process adds the env var or changes the value? Then this EnvCred in the chain will now work and be used in a new client?

This doesn't arise because only the constructor reads environment variables, and it returns an error when it doesn't find a complete set. If the configuration is complete but incorrect, the credential will attempt to authenticate--no CredentialUnavailableError--and ultimately return an Azure AD error.


fix: add missing extensions for progress openedge

Changes proposed:
add missing extensions for progress openedge

[x] Fix

@clement-brodu it seems that that extensions are already supported via language id. The icons should be there if you use this other extension. See how it is defined here
Is it not working for you?

I'm closing this unless @clement-brodu confirms this is not working with language id.

Hello,
Even with the extension detecting the correct file type, the icon is not the correct one for *.p files.

That’s strange. Looks like a bug. I’ll try to reproduce it.

I see what's going on. Prolog has P as an extension and both are competing against that. Let me check if we can get rid of that prolog extension.

Let's get rid of the P extension in prolog and leave it to language extensions implementors to decide.