PP81 density bug

Hey,
I've been trying to use the pp81 to parameterize internal waves, but I've been getting the maximum viscosity in a lot of places where I shouldn't have, mostly the second layer in my 3d model. After debugging and seeing a lot of places where the density differences between layers shouldn't be inverted. I double checked by calculating the density using temperature and salt from the state variables just to make sure this is a density calculation issue.
I noticed the following lines in the file pp81_ri_number.F:
     CALL FIND_RHO_2D(      I     iMin, iMax, jMin, jMax, K,      I     theta(1-OLx,1-OLy,Km1,bi,bj), salt(1-OLx,1-OLy,Km1,bi,bj),      O     rhoKm1,      I     Km1, bi, bj, myThid )
      CALL FIND_RHO_2D(      I     iMin, iMax, jMin, jMax, K,      I     theta(1-OLx,1-OLy,K,bi,bj), salt(1-OLx,1-OLy,K,bi,bj),      O     rhoK,      I     K, bi, bj, myThid )
Looking at the function FIND_RHO_2D, it says that the last K value (4th variable from the end) is just there for debugging reasons, and the first K (5th variable from the start) is what is used as Kref. Maybe the bug here is to switch the first K to become Km1? I tried this and it has lowered all the viscosity to background levels. I'm not sure yet if good or bad but definitely different. Since pp81 uses FIND_RHO_2D and not FIND_RHO_SCALAR I thought that this problem may be different than the previous opened issue.
Thanks for your hard work and any insights!

I don't think that this is a bug. To evaluate the stratification (N^2) one needs to consider the vertical
derivative of density at constant pressure; this is done by using the same Kref in the 2 calculations of density (the 2 calls to FIND_RHO_2D). Note that this is similar to what is done in do_oceanic_phys.F to compute "sigmaR" (and in fact we could and probably should use "sigmaR" in pp81_ri_number.F to improve the efficiency of pkg/pp81).

I think this issue/question has been answered. Nothing new here since last year so will close this issue.


Ability to disable hitbox change

Make sure you are not opening a duplicate.

[x] I have searched the issue tracker and did not find an issue describing my bug.

Description of your suggestion.
Disclaimer: I am playing a modpack with this mod (Valhelsia:EV). The information on their discord tells me that the change in hitbox of some mobs is because of this mod.
I cannot find any way to disable this, so it would be great if this option could be added.

Sorry, it seems disabling the 'Big Zombie' modifier changes this.


GitLab token expires now

Component
server
Describe the bug
Hello,
You can't opt out from expiring tokens in GitLab on newer versions^1.
Unfortunately, refreshing token seems not be supported in go-gitlab yet^2.
The workaround for me now, is logging out regularly from woodpecker and pushing empty commits to trigger builds.
System Info
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-313e72e5"}

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

Closing this issue due to no response.

upstream issue got closed ...
from woodpecker side we just need to implement the Refresher interface for gitlab
https://github.com/woodpecker-ci/woodpecker/blob/42c745362b11f09d3e397c102b78c4bf0c664f3a/server/remote/remote.go#L96-L101

Back from vacation.
Couldn't get it to work with the latest state of the feature branch.
Getting messages like these in the server logs :
{"level":"error","error":"OAuthError: Refresh: no existing Token",
"caller":"/home/dsanader/code/6543-forks/woodpecker/server/router/middleware/token/token.go:59",
"message":"refresh oauth token of user 'dsanader' failed"}

Doesn't seem to be related to the token issue, but jobs aren't being picked up by the agents and stay in pending state.

Hello,
After a bit of tinkering in server/remote/gitlab/gitlab.go, I found out that the token was indeed empty in the Refresher func. Injecting in the transport seems to improve the situation.
@@ -149,11 +151,14 @@ func (g *Gitlab) Refresh(ctx context.Context, user *model.User) (bool, error) {
        config := g.oauth2Config()
        config.RedirectURL = ""

-       trans := &oauth2.Transport{Config: config, Transport: &http.Transport{
+       trans := &oauth2.Transport{Config: config, Token: &oauth2.Token{AccessToken: user.Token, RefreshToken: user.Secret, Expiry: time.Unix(user.Expiry, 0)}, Transport: &http.Transport{
                TLSClientConfig: &tls.Config{InsecureSkipVerify: g.SkipVerify},
                Proxy:           http.ProxyFromEnvironment,
        }}

added your diff

@dsanader can you verify tag pull_1031 does solve it?

It almost completely fixes the GitLab token validity issues for me.
I had a few glitches in the context of merge requests events.
Git cloning was not authorized when merging to the main repo on the first run. Hitting the restart button was enough to trigger a successful build.
I haven't tracked it down yet, but I guess Refresh might not be called every time in some cases.
Will report back with more detailed info.


Improved Readability in Several Keras Code Files

Now the code files will be more PEP8 compliant and more readable.

These changes include numerous PEP8 violations (for a list, check out the PEP8 test failures on Travis). Please be aware that we do not normally merge PRs that are solely about code style, especially if they represent a regression rather than an improvement.

@fchollet I will be sure to review those changes. It's ironic because those changes were supposed to improve PEP8! Fortunately, since edits from maintainers are allowed, you can make any changes to those changes if you need to (remove any mistakes and leave the good changes). By the way, I am working on PyAutoCode, which will allow Keras users to create and train Keras models using simple sentences. I hope that will be of any help :)


Text field has changeevent parameters reversed

for the text field OnChange function the oldValue and newValue parameters are reversed.
Line 289
var fn = function(t, n, o) {
should be
var fn = function(t,o,n){

Thx. Will fix in  asap.

Fixed in : https://github.com/ahome-it/ahome-touch/commit/775cfd1549eb797d4103f429cfed76db3758b876


feat: Port/data.nat.succ_pred

[x] depends on: #1084

This PR/issue depends on:

leanprover-community/mathlib4#1084
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#1084
By Dependent Issues (🤖). Happy coding!

bors r+


Modify blender script to export files as VRM 1.0

right now it's exporting each armature + mesh as vrm 0.x

duplicate issue, now added in too https://github.com/M3-org/character-assets/blob/main/_utilities/blender_export.py


Fix a typo and done some amendments to the code

Usually while using jupyter notebooks\labs, it is advisable to use '!' before non python code (like pip). I thought we could also follow it here, it is just way to make code clearer and better. It doesn't disturb the functionality of the code. @jlooper is it okay ??? or can just close this PR. Sorry I made a mistake in last commit message :sweat_smile:

Note - check solution ipynb files too


Feature Request: Add options pertaining to snapshot expire schedule as part of config

As discussed in discord, some community members including me have been facing inconsistent timeouts and errors during the snapshot expiry process.
There seems to be some bug with Athena and a case has been raised by me with regards to it. In parallel, to overcome the issue of timeouts, I tried experimenting by changing the schedule and stepfunction timeout to 30m from 1hr and it worked well for me.  Expiry averages to 16 mins of running before failing with ICEBERG_VACUUM_MORE_RUNS_NEEDED and then subsequent query sucesssfully executes with average of 30 seconds for my volume of logs with this new setting!!
It would be helpful, if the schedule and stepfunction timeout is kept as part of config so that the consumer can find the sweet spot where the expiry works as expected depending on the size of the logs they ingest. This will also help in managing the athena related issue until it gets resolved.

@rams3sh  I am also facing same issue, but I didn't get what you are trying to say. Can you please tell me how to avoid the timeout errors while running the vacuum from stepfunction. please post a code snippet how to add timeout variable

@B161851  There is an inherent issue with Athena because of which timeout issues are happening.
As a workaround, I manually updated the event bridge time scheduled to run the VACUUM command as there exists no parameter in matano config to do it from CLI. Decreasing the time of VACUUM ensures that cleanup data does not get accumulated faster. Please note, this is only a temporary fix. Permanent fix can only be provided by Athena team from AWS.
As and when you add more data sources, you may start witnessing the timeout even within the small duration.


Cereal-rebase

@OXPHOS i'm just updating the travis build image so that you have libcereal-dev available :) once it's done i'll let you know

although yeah including cereal in .h is not the best thing :P

@OXPHOS could you fix the clang-format errors? btw do we wanna merge this directly into develop now?

@vigsterkr Thanks! I am trying to rebase the origin feature/cereal branch on develop. But it was kinda tricky so I want to make sure all tests passed first. I'll close this PR w/o merging when they're all green..

@OXPHOS cool still formatting issues :)

but i dont care... so use this to forcepush the feature branch...

Any.h format check failed

@OXPHOS Can you write me an email once this kinda works?

Force pushed to feature/cereal


ENABLE-30 Accessible Context Menu

Completed:

Testing on MacOS Safari, Firefox, and Chrome for the link and area.
Testing on iOS Safari for the link.

Still needs:

Testing on Android and Windows.
Announcement for how to open the context menu—VO+Shift+M on Mac and its equivalent on Windows.

I assume this is still WIP right?  If so, can you put that in the Issue Title please?


Provide ppc64le binary and image

It would be great to have official binary and image for ppc64le.
I have the required change for the build script, it builds fine. Tests (stress) are running OK and I also did some real usage test, with Kata's integration tests that are using Sonobuoy.

In general, I think you can make a good case that we should support all the versions that k8s does. That would mean we may want to consider (ppc64le, s390x, arm [we build arm64]).

I'd love to work on addition of linux/s390x build to sonobuoy.
So far I've executed the stress and integration tests on s390x. In general things look good except failing some integration test, because sonobuoy/systemd-logs:v0.3 image is missing for s390x. I see that for other platforms it was built 2 years ago just 1 time (I guess manually?). Would it be possible to build the sonobuoy/systemd-logs image for s390x and add it to multi-arch version as well?

I didn't think any of the integration tests required the systemd-logs; and even then we can build the binary/image without having explicit integration testing on it. We talked about this in a recent Sonobuoy status meeting and mentioned that for some of the less common arches like ppc64le and s390x we can just edit the README or docs to mention that those are community supported for testing/feedback rather than being tied into our CI at the time.

Yeah, I didn't suggest to extend your CI system to run the tests for new platforms. Just tried to verify from my side, that sonobuoy binary is workable for linux/s390x platform.

I can put it on my list to build/release systemd-logs for those arches; do you have a recommendation for the base image or anything else I need to know about ppc64le or s390x?

I've submitted the PR to add s390x to systemd-logs image build. btw ppc64le was already there :)
I've also tested that systemd-logs build works ok with new architecture and reexecuted the sonobuoy integration tests with newly built systemd-logs image on s390x. Now all tests are passed.


Define severity, rule suppression, rule selection

Closes #177
Closes #132
Closes #133

Remember to check the Linux build, do you need help with that?
Some tests seem to be failing there, like this one:
  Failed SeverityOneOnly [232 ms]
  Error Message:
   Assert.IsTrue failed. Expected failing rule Ids do not match actual failed lines.  Expected: [TA-000003]  Actual: [TA-000003,TA-000005,TA-000015,TA-000017]
  Stack Trace:
     at Analyzer.Types.ConfigurationTests.TestRunner.TestRule(TestConfiguration ruleExpectations) in /home/runner/work/template-analyzer/template-analyzer/src/Analyzer.Types.ConfigurationTests/TestRunner.cs:line 54```

converting to draft - will improve the current tests flow


macos: system.drawing.common not found

On a mac (mojave) I get the error for release 14.1 :
dotnet RoslynPad.dll
Error:
An assembly specified in the application dependencies manifest (RoslynPad.deps.json) was not found:
package: 'System.Drawing.Common', version: '4.5.0'
path: 'runtimes/unix/lib/netcoreapp2.0/System.Drawing.Common.dll'
dotnet --info shows this:
$ dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   2.2.203
Commit:    e5bab63eca
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.14
OS Platform: Darwin
RID:         osx.10.14-x64
Base Path:   /usr/local/share/dotnet/sdk/2.2.203/
Host (useful for support):
Version: 2.2.4
Commit:  f95848e524
.NET Core SDKs installed:
1.1.7 [/usr/local/share/dotnet/sdk]
2.1.4 [/usr/local/share/dotnet/sdk]
2.1.301 [/usr/local/share/dotnet/sdk]
2.1.302 [/usr/local/share/dotnet/sdk]
2.2.100 [/usr/local/share/dotnet/sdk]
2.2.203 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.6 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.4 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
`
Any ideas?

Duplicate of #249


executing "content" at <$paginator.Pages>: error calling Pages: runtime error: invalid memory address or nil pointer dereferenc

[hugo 5/5] RUN hugo:
#17 0.680 Start building sites …
#17 0.681 hugo v0.95.0-9F2E76AF linux/amd64 BuildDate=2022-03-16T14:20:19Z VendorInfo=gohugoio
#17 2.052 Error: Error building site: failed to render pages: render of "page" failed: "/src/themes/hugo-theme-bootstrap/layouts/_default/archive.html:7:28": execute of template failed: template: _default/archive.html:7:28: executing "content" at <$paginator.Pages>: error calling Pages: runtime error: invalid memory address or nil pointer dereference
#17 2.053 Total in 1606 ms

executor failed running [/bin/sh -c hugo]: exit code: 255

0.95版本存在问题，0.85版本正常

@halobug 我没重现出来，有重现步骤吗？

So I translated

translate 0.95版本存在问题，0.85版本正常

and it is

there is a problem with version 0 95 0 version 85 is healthy

hugo server --source=exampleSite --themesDir=../..

Start building sites …
hugo v0.98.0-165d299cde259c8b801abadc6d3405a229e449f6 linux/amd64 BuildDate=2022-04-28T10:23:30Z VendorInfo=gohugoio
Error: Error building site: failed to render pages: render of "page" failed: "/home/********/Hugo/mysite/themes/hugo-theme-bootstrap/layouts/_default/archive.html:7:32": execute of template failed: template: _default/archive.html:7:32: executing "content" at <$paginator.Pages>: error calling Pages: runtime error: invalid memory address or nil pointer dereference
Built in 415 ms

Line 7 of /archive.html is

{{- $count := len $paginator.Pages -}}

I seem to remember that error msg before though. I had to change the number of posts/page ??
BUT, I'm using version 0.67.1

This issue should be fixed by 0ff419c220d48cac168ae8807657069847ed8e6d and 567ab0b5a124b7191fc26c36aac51992d3b28cfb.

@razonyang - thank you, that's fine now.

@jehoshua7 My pleasure.


Feature Request for Text Embeddings Inference

Validations

[ ] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
Hi,
Thank you for your work.
I was wondering if you could add support for https://github.com/huggingface/text-embeddings-inference as an embeddingsProvider (like you did with the TGI).
Would be great.
Kind regards,
Solution
No response

Just adding that TEI also provides an /rerank endpoint, which could also be implemented as one of the rerankers e.g. when used with models such as jinaai/jina-reranker-v2-base-multilingual.
I would also be willing to add this feature if it is wanted 🤔

That would be real nice! I am working on a pilot within my company to see if this could increase development speed and documentation, this would be a real nice feature I can use for the setup.

I am closing this issue since it is already implemented! See: https://docs.continue.dev/walkthroughs/codebase-embeddings, the reranking part is not implemented, I suggest that you make a seperate issue.
Kind regards

@LLukas22 - currently we do not have support for TEI as a reranker (see the available options here).
We'd we welcome a PR to implement it though! Check out https://github.com/continuedev/continue/blob/main/CONTRIBUTING.md to get started and feel free to reach out with any questions in Discord.


[Hub Generated] Review request for Microsoft.ResourceHealth to add version preview/2021-01-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This PR: https://github.com/Azure/azure-rest-api-specs/pull/12803 addresses the potentialOutages singleton question.

hi @liusu-coder, is the change deployed to Prod already? thanks

hi @liusu-coder, is the change deployed to Prod already? thanks

hi @liusu-coder, pls ping me when the backend change deployed to Prod, then I'll merge the PR. thanks

hi @liusu-coder, is the change deployed to Prod already? thanks

hi @liusu-coder, pls ping me when the backend change deployed to Prod, then I'll merge the PR. thanks

Thanks for the message. The code change is relatively extensive and we are going through lots of code reviews and testing. As soon as it's ready, i will let you know, thanks.


Option to turn off array flattering

It would be nice to have an option not to flat an arrays, because it hard to use them in format-data callback. You wouldn't receive a nice array to it, just a null value.
To clearly understand my idea, here is a working example (Sorry, no time for forking...)
Option declaration:

 ...

@fruit: Seems easy enough.
Also, to chime in, it would be nice to have a data-flat-max-level option. I.e
{
    model: {
        field1: "some value",
        field2: "some value",
        noTable: {
            field1: "some value",
            field2: "some value",
        }
    }
}

data-flat-max-level="2" would produce:
{
    "model.field1": "some value",
    "model.field2": "some value",
    "model.noTable.": {
        "field1": "some value",
        "field2": "some value"
    }
}

@jtrumbull: good idea. Additionally, it would be fine to define data-field-flat-max-level on a table's row-level:
Row representation:
{
    "username": "alice81",
    "profile": {
        "first_name": "Alice",
        "last_name": "Smith",
        "address": {
            "street": "Meyrin Road 385, 1217",
            "town": "Meyrin",
            "country": "Switzerland"
        }
    }
}

Table sample:

            User Name
            First Name
            Last Name
            Addresse

function addresseFormatter(value) {
    return value.country + ' ' + value.street;
}

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
 You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @uwaisdev, @daaser, @keywordwei, @Prabhat1308, @jonathannto, @hudson-newey, @rokitgg, @abhisamant, @vmocampos, @blockbee, @LiMeitong, @erikacls, @KristofDcu, @EsDub92, @jweyrich, @youngDuckling, @soequelle, @aparisella, @imesong, @mlgrs, @vahdani, @qqonline, @cocos543, @victorodri, @mtphyscs, @shellyalina, @tdntinh, @Madusha1995, @michel-klein, @SayeedSadauki, @qiohm, @supernovalx, @MateusAndrade, @itmustbejj, @jastroud, @PrasoonPratham, @cesar2120, @onecarpayment, @savelyevresearch, @rogozhka, @AbhishekBiswal, @raharjaliu, @SftJun, @veselinovicst, @Arctic-Panda, @MStumpp, @zjach, @kusiha, @yw79641760, @new-happy


Ubuntu 22.04 image fails at git.sh installation script

Description
Building a linux image using AzureDevOps Packer build task results in an error at git.sh script installation. It fails at the ssh-keyscan step without any proper error message since 28th April . The message we see is below:
"Provisioning step had errors: Running the cleanup provisioner, if present"
We overrode the git.sh file to add some logging as below and we don't see any detailed logs
ssh-keyscan -vvv -t rsa,ecdsa,ed25519 github.com >> /etc/ssh/ssh_known_hosts
logs:
debug2: fd 3 setting O_NONBLOCK
debug3: conalloc: oname github.com kt 2
debug2: fd 4 setting O_NONBLOCK
debug3: conalloc: oname github.com kt 4
debug2: fd 5 setting O_NONBLOCK
debug3: conalloc: oname github.com kt 8
Provisioning step had errors: Running the cleanup provisioner, if present
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
ubuntu22/20230426
Is it regression?
ubuntu22/20230317
Expected behavior
Packer build task should execute successfully
Actual behavior
Packer build task fails on git.sh installation script
Repro steps

Azure DevOps
Pipeline with Packer build task

We are also seeing the same problem, have run the pipeline multiple times to verify it's failing in the same place.

Hello @mortenlerudjordet , @Vinayak014 , we do not observe this issue in our Azure pipelines https://github.visualstudio.com/runner-images/_build/results?buildId=131952&view=logs&j=747417c8-a650-5aed-afed-d9b52dbd7d24.
Please check your configs one more time, and make sure you are using the updated master branch.
We are going to close this issue. If you have any questions feel free to reach us.

I fixed my problem by reverting this commit - bea98d07491839b4ab1963e6a0341e8cab07ae16 which is related to install.sh.

Can confirm that after allowing outbound on 22 for github.com and ssh.dev.azure.com for the packer build VM the pipeline no longer fails on ssh-keyscan part.

Also ran into this issue. Checking if opening port 22 fixes this issue. If it does, consider adding more verbosity. Right now, the pipeline just dies after downloading. It downloads, does not throw any warning or error, then continues onto the VM breakdown.


fix: hide error when writing a log in an undetermined environment

@bcoe just sending this in early for your review. PTAL!

@stephenplusplus I think this should get at the underlying issue:
https://github.com/googleapis/gcp-metadata/pull/239

I think we can probably close

Goodbye, 579. No ticket to Hollywood for you.


fix build in windows

I've accept it for now. But it's more like a hack. More proper msvc compiler is needed. For example older msvc do not support off_t etc.


feat(sidecar): support large staking operations

Some professional node operators rely on custom setups that look quite different from solo stakers. Some of the differences are:

validator clients connected to N EL/CL pairs, non-sticky (i.e. these can rotate as need be, and as servers go down)
rotating validator keys between different validator clients and EL/CL pairs, non-sticky
stateless MEV-boost MUXers used interchangeably depending on availability (or custom criteria like specific validator pubkeys)

Bolt works under the assumption that commitments rely on a single source of truth, which in our case is the bolt-sidecar.
-> It's not possible to run 2 bolt-sidecars with the same validator key as that could lead to safety faults.
This does constrain the flexibility of some of the setups described above, where for instance MUXers are stateless (e.g. get_header and get_payload calls could be made from different machines). This doesn't work for us since we need to be able to ship local blocks to beacon clients in case of locally built fallback blocks.
-> On first analysis, it looks to me like the "stickiness" of the bolt-sidecar<->beacon<->validator_key link is limited to 1 epoch.
Another point is allowing bolt-sidecar to use fallback EL/CL URLs as to have built-in redundancy for these types of setups.
This could be added as an optional flag or env variable.

Thanks for these notes, really interesting!
Along this reasoning, I've noticed that the constraint submission logic + proof verification on MEV-Boost makes it lose it's statelessness property: the get_header call that we proxy into a get_header_with_proofs is stateful, because of the constraints that are stored in local memory and sent by the bolt sidecar.
As you suggested for scaling the bolt sidecar horizontally, a good solution might be saving those constraints in a Redis cluster.


[fix] Parameterize the azure hack script

It contains some fixed values for crcqenvs we need to parameterized it
also add the blob container create cmd  az storage container create -n qenvs-state --account-name

Also added some policy to delete files after X time on the blob container https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-policy-configure?tabs=azure-cli#optionally-enable-access-time-tracking


Custom player styles broken in fullscreen

Like the title says. This is from the 2012 Cosmic Panda layout:

Seems to be a Chrome exclusive issue. Will probably be fixed in the next update.

The player styles are better now, but the slider needs to be made longer (This is from the 2014 style)

Will get to it when I get the chance.


[firebase_ml_vision] multiple app support

Originally was #23049 but I am creating this issue to track non-default Firebase app support in firebase_ml_vision specifically
@bparrishMines

@collinjackson
The issue at https://github.com/flutter/flutter/issues/28149 has been closed and moved here. Future collaboration on this issue will be done here.

611

Given the age and inactivity of this issue I'm going to close this issue in favour of making a feature request over in Discussions.


Documentation: sphinx docs and action for GH Pages

Summary
Documentation: sphinx docs and action for GH Pages
Details and comments
Part of #3 and #4

Documentation screenshots

@Morcu please review :)


Made directory argument optional

It annoyed me to have the directory be a required command-line argument, so I made it optional. I did this a while ago but since you have been updating the program lately I thought it would be good to get it into the master branch.
Now you can just do "python artview.py" and it will bring up the directory menu to choose the file.

Er, never mind looks like this was already done?


{Storage} az storage blob show: Use try catch for GetPageRange after GetBlobProperties in blob show

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage


reset syscc in mp_abort for Viya response

When running mp_abort using the compute api approach the response is not being surfaced to the adapter.
It transpires that the reason is the existence of a non-zero SYSCC value results in state of error for the job, as per the extract below.
In order to handle errors gracefully we should reset the value for SYSCC (the final value is displayed anyway in the response json).
{
	"completedTimeStamp": "2021-06-28T20:43:12Z",
	"creationTimeStamp": "2021-06-28T20:43:11Z",
	"id": "EEE43D54-4F36-5243-A103-13FBFDADBD30",
	"jobConditionCode": 1012,
	"links": [{
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30",
		"method": "GET",
		"rel": "self",
		"type": "application\/vnd.sas.compute.job",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/state",
		"method": "GET",
		"rel": "state",
		"type": "text\/plain",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/state"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/state?value=canceled",
		"method": "PUT",
		"rel": "cancel",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/state?value=canceled"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30",
		"method": "DELETE",
		"rel": "delete",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/log",
		"itemType": "application\/vnd.sas.compute.log.line",
		"method": "GET",
		"rel": "log",
		"type": "application\/vnd.sas.collection",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/log"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/listing",
		"itemType": "application\/vnd.sas.compute.log.line",
		"method": "GET",
		"rel": "listing",
		"type": "application\/vnd.sas.collection",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/listing"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/results",
		"itemType": "application\/vnd.sas.compute.result",
		"method": "GET",
		"rel": "results",
		"type": "application\/vnd.sas.collection",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000\/jobs\/EEE43D54-4F36-5243-A103-13FBFDADBD30\/results"
	}, {
		"href": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000",
		"method": "GET",
		"rel": "up",
		"type": "application\/vnd.sas.compute.session",
		"uri": "\/compute\/sessions\/3e53cb30-276c-4b25-9562-ad5409904956-ses0000"
	}],
	"listingStatistics": {
		"lineCount": 0,
		"modifiedTimeStamp": "2021-06-28T20:43:11Z"
	},
	"logStatistics": {
		"lineCount": 1934,
		"modifiedTimeStamp": "2021-06-28T20:43:12Z"
	},
	"sessionId": "3e53cb30-276c-4b25-9562-ad5409904956-ses0000",
	"state": "error",
	"stateElapsedTime": 0,
	"statistics": {
		"systemCpuTime": 0.05,
		"userCpuTime": 0.21
	},
	"version": 1
}

:tada: This issue has been resolved in version 2.35.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

The correct (handled) response is now shown
{"START_DTTM" : "28JUN21:21:17:05.846"
,"sasjsAbort" : [{
 "MSG":"Problem running MP_ABORT (Physical file does not exist, settings.SAS. Cannot %INCLUDE member settings in the aggregate __DC.)\n\nLog Extract:\n"
 ,"MAC": "/Public/app/viya/services/public/startupservice"}]
,"SYSUSERID" : "allbow"
,"_DEBUG":" "
,"SYS_JES_JOB_URI": " "
,"_PROGRAM" : "/Public/app/viya/services/public/startupservice"
,"SYSCC" : "1012"
,"SYSERRORTEXT" : "Cannot %INCLUDE member settings in the aggregate __DC."
,"SYSJOBID" : "11729"
,"SYSVLONG" : "V.03.05M0P111119"
,"SYSWARNINGTEXT" : "Physical file does not exist, settings.SAS."
,"END_DTTM" : "28JUN21:21:17:05.847"
}


Move cms store to core library

The cms store is wired into the component library. As part of GH-250, we move ngrx store outside the component library and only interact with the facades.

Can start this one when facades refactoring is done


Add a splash screen

It woudl be great to add a splash screen explaining:

default view for the app (https://github.com/PeaceGeeksSociety/services-advisor/issues/88 services whose end date has not expired)

clarifying how the information is collected (i.e. through ActivityInfo database and with the support of UNHCR intersector Coordination Section)

How do people currently get to the services advisor? I remember Renee showing us that it comes from another website from the UNHCR. The splash content would probably be better from that site for a few reasons.

as a user: If I'm coming to this page directly, I already know what I'm looking for. The splash screen would be simple another thing to exit.
as a user: If I don't know what the Services Advisor is, then I will be referred to it from another website. That website should tell me why this web app is right for me.

^ is my understanding. (cc. @PeaceGeeks )
If however we want to keep this information within the Services Advisor, I recommend putting it in a Help or Support section of the app.

@amyngai - yes that is correct - from help.unhcr.jo - tho the plan is to send out an SMS to all refugees when the new app is ready to launch. i am also registering servicesadvisor.org which we will use.

ok. What are your thoughts in the above issue @PeaceGeeks ?
What is and how long will the content be to explain the above concerns. We can put it in a help section, I also had designed a small section here:

to explain the app (which I didn't have content, so it's really just filler at the moment)

@Edouard-Legoupil ?

@Edouard-Legoupil - looking for your input here since this was your suggestion. Does this address the 'splash screen' idea, or were you wanting something more?

Sorry for the late response: -- adding to https://github.com/PeaceGeeksSociety/services-advisor/issues/89 -- the splash screen could actually allow users to select their use case and the default behavior that is related to the use case:
Ideas for the splash screen:  --

Services-Advisor allows to discover and search for humanitarian services through map. The app is also available in Arabic. Please tell us:

I am a refugee and I want to know what services are available to me without referral

I am a humanitarian work and and I need to know about all services I can refer refugees to.

I can see in the UI screenshot -- "UNHCR Services Advisor" -- Reference to UNHCR should be removed. "Services Advisor" is an inter agency tool. It's important to maintain this neutrality for the branding of the tool

what does the ^ screenshot accomplish? Should it change the filters presented once clicked or is it merely for data of who uses the app?


Communicate changes to client developers

This issue documents the upcoming Sigstore staging TUF changes for client developers:

The repository (https://tuf-repo-cdn.sigstage.dev/) will soon be produced by new software running in this git repository
Staging will be a live repository (with changes at a similar frequency as the production TUF repository)
Staging will uses signing keys similar to production TUF repository
Everything Should Just Work: clients should not have disruptions
However, the changed tooling means there are some small metadata changes that could have effects

metadata contains custom fields (that clients do not need to understand, but need include when producing canonical JSON)
metadata may contain empty signatures "sig": "" (for signers that have not signed this metadata)
artifact hashes will be using "sha256" only

The long term plan is for sigstore-conformance to test against staging (sigstore/sigstore-conformance#124)... but that may take a while. In the mean time:

client developers can already make a preliminary test against the development URL if they want  (https://sigstore.github.io/root-signing-staging/ in place of https://tuf-repo-cdn.sigstage.dev/)
The plan is to deploy https://tuf-repo-cdn.sigstage.dev/ as soon as we are all set (#47)
Once new staging is live, I will ping the "clients" slack channel and this issue and ask client devs to file issues in this repository if something isn't working

Once the new staging TUF is live, please test that your client works with it: Production TUF will follow with similar change some time after.

The Sigstore staging TUF at https://tuf-repo-cdn.sigstage.dev/ is now deployed from this repository.
Please test and get in touch if something isn't working.
Future steps:

make sigstore-conformance test staging as well (so clients get notified about upcoming breaking changes in Sigstore TUF, even if they are breaking by accident)
start migrating the production TUF (https://github.com/sigstore/root-signing that publishes to https://tuf-repo-cdn.sigstore.dev/)  to the same setup as well

I think this is now handled


Marketdata for all currency pairs + Trade order creation

Hi @tennantje, thanks for putting this gem together!
Just made a small tweak to the Marketdata methods to make them more dynamic and implemented the trade order creation method.
I've tested the trade order creation method and it works for my account. I've successfully purchased some BTC, ETH and LTC with the new version of this gem.

Thanks for this, I'll push the new gem version shortly.
I'm not really interested in maintaining this any more, as I'm no longer involved in cryptocurrency as I was when I created this. If you (or anyone reading this in the future) would like to maintain it - I'm happy to hand over the repo.


trying different file name

Doesn't Java require that the public class name and the file name match?

Nice catch! Yes, you are right. Though you might want to change everything to HelloWorld instead of Main for the sake of readability and the purpose of the guide.


Cannot connect with wildcard certificate

Issue tracker is ONLY used for reporting bugs. New features and questions should be discussed on our slack channel.

Expected Behavior
I should be able to use a wildcard certificate to connect to Zeebe just like I can with zbctl.
Current Behavior
The client does not connect as reported in https://github.com/camunda/camunda-modeler/issues/3326
Possible Solution

Steps to Reproduce

Check out the linked issue from Camunda Modeler.
Context (Environment)

Detailed Description
grpc log
D 2023-01-24T14:47:48.927Z | channel | (1) dns:test.test.localhost:26500 Channel constructed with options {
  "grpc.enable_retries": 1,
  "grpc.initial_reconnect_backoff_ms": 1000,
  "grpc.max_reconnect_backoff_ms": 10000,
  "grpc.min_reconnect_backoff_ms": 5000,
  "grpc.keepalive_time_ms": 180000,
  "grpc.keepalive_timeout_ms": 120000,
  "grpc.http2.min_time_between_pings_ms": 90000,
  "grpc.http2.min_ping_interval_without_data_ms": 90000,
  "grpc.keepalive_permit_without_calls": 1,
  "grpc.http2.max_pings_without_data": 0
}
D 2023-01-24T14:47:48.928Z | channel | (1) dns:test.test.localhost:26500 createCall [0] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-01-24T14:47:48.929Z | call_stream | [0] Sending metadata
D 2023-01-24T14:47:48.931Z | channel | (1) dns:test.test.localhost:26500 callRefTimer.ref | configSelectionQueue.length=1 pickQueue.length=0
D 2023-01-24T14:47:48.932Z | call_stream | [0] write() called with message of length 0
D 2023-01-24T14:47:48.932Z | call_stream | [0] end() called
D 2023-01-24T14:47:48.932Z | call_stream | [0] deferring writing data chunk of length 5
D 2023-01-24T14:47:48.940Z | subchannel | (2) <IP_ADDRESS>:26500 Subchannel constructed with options {
  "grpc.enable_retries": 1,
  "grpc.initial_reconnect_backoff_ms": 1000,
  "grpc.max_reconnect_backoff_ms": 10000,
  "grpc.min_reconnect_backoff_ms": 5000,
  "grpc.keepalive_time_ms": 180000,
  "grpc.keepalive_timeout_ms": 120000,
  "grpc.http2.min_time_between_pings_ms": 90000,
  "grpc.http2.min_ping_interval_without_data_ms": 90000,
  "grpc.keepalive_permit_without_calls": 1,
  "grpc.http2.max_pings_without_data": 0
}
D 2023-01-24T14:47:48.941Z | channel | (1) dns:test.test.localhost:26500 callRefTimer.unref | configSelectionQueue.length=1 pickQueue.length=0
D 2023-01-24T14:47:48.941Z | subchannel | (2) <IP_ADDRESS>:26500 IDLE -> CONNECTING
D 2023-01-24T14:47:48.942Z | channel | (1) dns:test.test.localhost:26500 Pick result for call [0]: QUEUE subchannel: null status: undefined undefined
D 2023-01-24T14:47:48.942Z | channel | (1) dns:test.test.localhost:26500 callRefTimer.ref | configSelectionQueue.length=0 pickQueue.length=1
D 2023-01-24T14:47:48.942Z | subchannel | (2) <IP_ADDRESS>:26500 creating HTTP/2 session
D 2023-01-24T14:47:48.959Z | subchannel | (2) <IP_ADDRESS>:26500 connection closed with error unable to verify the first certificate
D 2023-01-24T14:47:48.960Z | subchannel | (2) <IP_ADDRESS>:26500 connection closed
D 2023-01-24T14:47:48.960Z | subchannel | (2) <IP_ADDRESS>:26500 CONNECTING -> TRANSIENT_FAILURE
D 2023-01-24T14:47:48.960Z | channel | (1) dns:test.test.localhost:26500 callRefTimer.unref | configSelectionQueue.length=0 pickQueue.length=0
D 2023-01-24T14:47:48.960Z | channel | (1) dns:test.test.localhost:26500 Pick result for call [0]: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-01-24T14:47:48.960Z | call_stream | [0] cancelWithStatus code: 14 details: "No connection established"
D 2023-01-24T14:47:48.960Z | call_stream | [0] ended with status: code=14 details="No connection established"
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://test.test.localhost' }
} Error: 14 UNAVAILABLE: No connection established
    at Object.callErrorFromStatus (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/client.js:195:52)
    at /Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/call-stream.js:111:35
    at Object.onReceiveStatus (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/zeebe-node/dist/lib/GrpcClient.js:135:36)
    at InterceptingListenerImpl.onReceiveStatus (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/call-stream.js:106:23)
    at Object.onReceiveStatus (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
    at Object.onReceiveStatus (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
    at /Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/call-stream.js:188:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/client.js:163:34)
    at ServiceClientImpl.<anonymous> (/Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Users/maciej/workspace/bpmn-io/camunda-modeler/app/node_modules/zeebe-node/dist/lib/GrpcClient.js:305:47
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} }
}
D 2023-01-24T14:47:49.942Z | subchannel | (2) <IP_ADDRESS>:26500 TRANSIENT_FAILURE -> IDLE

Possible Implementation

Potentially related: https://github.com/camunda-community-hub/zeebe-client-node-js/issues/290

Is this an issue with wildcard certificates specifically, or with self-signed certificates in general?

We closed the linked issue in Camunda Modeler as wontfix because we found out that it's not a problem with zeebe-node but rather too lenient behavior of zbctl. Therefore, this issue can be closed too.

To add to https://github.com/camunda-community-hub/zeebe-client-node-js/issues/288#issuecomment-1408213932:
zeebe-node validates the full chain of trust for certificates, zbctl does not. Could be worth adding that to the documentation. We're doing that for the Camunda Modeler here.
See downstream https://github.com/camunda/camunda-modeler/issues/3366#issuecomment-1406818981 for our wontfix rationale.


Use [weak self] instead of [unowned self]

App crashes:

I'm recreating new WebSocket instance in :func webSocketError(error: NSError)or func webSocketClose(code: Int, reason: String, wasClean: Bool).
Looks like, there is no guarantee that WebSocket will exist, when closure will be called.
Version: 2.6.1.
I will let you know if I catch same error on 2.6.3

Thanks for catching this error. I just pushed an update to the master branch.


[BUG][Doc] Doc website search engine is not working

Bug
Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[x] Other (documentation website)

Describe the problem
When using the search engine of the documentation website (on the left side panel) I always get the following error message:

This appears for all text queries, both existing methods/class/objects and random text.
Steps to reproduce

Go on https://docs.delta.io/latest/api/python/spark/index.html
Click on the "Quick Search" field and enter some text
Click on the search icon or press the enter key
See the error message

Observed results

Expected results
I should get a list of results matching the text I searched for. At least not an error message.
Further details
Browser: Chrome version 129.0.6668.101
Environment information
No concerned
Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[x] No. I cannot contribute a bug fix at this time.

Has the similar issue with Java API Doc: https://docs.delta.io/latest/api/java/index.html
404 Not Found
- Code: NoSuchKey
- Message: The specified key does not exist.
- Key: latest/api/java/index.html
- RequestId: 19GEQFYYAY2YZ7RY
- HostId: qugLxmdQ/T5/VhLz6HoCXuS7cHdkdkx5os0RR0t3IiP20UpW/1vHb4ymdUj5+h/m6wUkkFj5pu8=


Update to ngModule (angular RC5)

https://angular.io/docs/ts/latest/guide/ngmodule.html

Hi,
Can you help by sending a pull request for that?
I believe that a good approach would be to still let specific pipes to be individually imported, as well as providing an ngModule which contains all the pipes.

not 100% sure I have got everything correct but it seems to work for me.  Let me know if you want anything changed


Catch LineupOptimizerException

What's the correct way to catch this exception? I can't for the life of me catch it.
Even this doesn't work.
try:
    lineup_generator = optimizer.optimize(10)
except:
    pass

I still get the Runtime Error
pydfs_lineup_optimizer.exceptions.LineupOptimizerException: Can't generate lineups

from pydfs_lineup_optimizer.exceptions import LineupOptimizerException
Then use the LineupOptimizerException in the except block.
Sorry I'm on my phone hope this helps some.

Nope. Still doesn't catch it. I tried that which is why I'm so confused. The blank except should also catch it.
try:
    lineup_generator = optimizer.optimize(10)
except LineupOptimizerException:
    pass

Nope. Still doesn't catch it. I tried that which is why I'm so confused. The blank except should also catch it.
try:
    lineup_generator = optimizer.optimize(10)
except LineupOptimizerException:
    pass


adout conda envs

Hello, I'm very interested in your code, but it's always hard to configur Python environment, so my advice is that you can package the environment required by the code into an anconda environment, just like fast.ai, ,so that different computers with different Configurations can be easily downloaded and quickly configured.

I am sorry but this is not planned in the short term, but you're very welcome to contribute through a Pull Request


Add EST

Adding Ecole Supérieure des Communications Electroniques et de la Poste (ESCEP) to ne domain.
Here's the URL of the official website :  https://supecole-dev.net/
Here's the link on the official website where a long-term (>1 year) IT related course is offered by the university : https://supecole-dev.net/hospitality-management/#
Important : The school name changed from EST to ESCEP which means (Ecole Supérieure des Communications Electroniques et de la Poste) but we are always on the EST domain. The website url isn't on the est domain but on www.escep.edu.ne which is redirected to https://supecole-dev.net/
A PDF of a document from the school where the domain is recognized in the Headletter :
PLANNING  30-07-2023.pdf

@aminou-yerima The first verification stage is complete: the official domain for  Ecole Supérieure des Communications Electroniques et de la Poste is www.auf.org, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.auf.org/afrique-ouest/membres/nos-membres/ecole-superieure-des-telecommunications-est/

Hi @philipto thanks for your response. The official domain for École Supérieure des Communications Electroniques et de la Poste is www.est.edu.ne the www auf.org an university organization that École Supérieure des Communications Electroniques et de la Poste is part of.
Please, kindly check it even on the proof of domain ownership page it's noted.

@aminou-yerima Regrettably, this request has signs of fraud. I have to close it without merging.
It does not mean that something is wrong with the school. The issue is related to a combination of suspicious factors related to the domain and the official website (see screenshot attached).
Please feel free to apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
Thank you for your understanding!


Reword millisecond docs to give example of usage

As per #373, makes millisecond docs simpler to understand

I don't really like the talk of "variable" here (in the new documentation comment). Does the core documentation use language like "variable" elsewhere?
Generally, wouldn't a much easier fix to the problematic aspect of the documentation you point out be to simply replace (500 * milliseconds) by (500 * millisecond)? Why is the rest of the rewording necessary from your perspective?

I've removed the word variable now - I agree it didn't feel right there.
That would be an easier fix, but a less clear fix I feel. I wanted an explicit code example that people could use right away, rather an example just in the brackets, which doesn't seem as obvious that it's meant to be code. Adding halfSecond = 500 * millisecond makes it more explicit and obvious than (500 * millisecond) in the middle of a sentence, basically.

Though I could just change it to remove the s if you think that's clear enough.

I actually think just removing the plural s would be enough.

That it's code, should be clear from type-setting on the docs page.

Okay - changed it so it's now just the 's' removal, and got rid of the previous commits I made too.


Update pre-commit and ci configuration

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

Project coverage is 99.38%. Comparing base (ceea222) to head (74fa014).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #22   +/-   ##
========================================
  Coverage    99.38%   99.38%
========================================
  Files            8        8
  Lines          647      647
  Branches        20       20
========================================
  Hits           643      643
  Misses           4        4

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


NPM publish

@plusacht/owners please npm publish 1.0.3 and 1.0.4 (master) or feel free to add me jason.mitchell.w (at) gmail.com

I will do it in the next 48 hours.
I use the npm semantic-release library to publish this addon, that has shown to be troublesome. I will change that and give you also publish right's if you want @jasonmit .

Ahh, you already answered my question :smile:

@jasonmit you have npm publish rights. Ff you can wait until i remove the semantic-release stuff, and if not just release it. Else I will do it in the next 48 hours.

friendly bump :smiley_cat:

I didn't have rights when I opened the issue, if that changed since then I'll version tonight

done!

Fantastic! Thank you 😬
On Thursday, April 7, 2016, Claudio Romano<EMAIL_ADDRESS>wrote:

done!
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/plusacht/ember-bootstrap-datetimepicker/issues/72#issuecomment-206786462

--
Thanks,
Offir Golan


Error handling

Hi,
I think it would be helpful if the documentation was updated with some details on how errors are reported/handled with Azure CLI, for example exit codes, use of stderr, etc.  There is a brief mention of exit codes https://github.com/Azure/azure-cli#exit-codes but would be useful if this was added to the documentation and expanded upon.
Thanks,
Mark

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

ID: 1c268a98-afcb-d2c2-87c7-880d52900533
Version Independent ID: 4c835da4-38bc-22a8-67b4-dd522adcc0e3
Content: Get started with Azure CLI
Content Source: docs-ref-conceptual/get-started-with-azure-cli.md
Service: azure-cli
GitHub Login: @dbradish-microsoft
Microsoft Alias: dbradish

@bowlerma Thank you for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@bowlerma , I think this is a great idea and have created a work item for a conceptual doc that just talks about error handling in the Azure CLI.  Thank you for taking the time to help make the Azure CLI even better.


Post-processing of Intensity profile

hi the team,
Thanks for this great contribution to the filed. I have one question regarding the post-processing of LiDAR Intensity profile.
From this paper titled "LiDAR Snowfall Simulation for Robust 3D Object Detection" we know that LiDAR raw intensity roughly follows a Lambertian model which has dependence on the range squared and cosine incidence angle (see below). I tried to correct these dependence to obtain surface properties like reflectance but find that: it seems Waymo dataset has already done some post-processing to remove range and incidence angle dependence. My question is: Has the team done some post-processing as I mentioned above? If yes, do we have a reference for these detailed operations?

Thanks and look forward to your reply.
Best,
Shengyu

Hi Shengyu,
Thanks for your question - unfortunately, due to IP reasons, we are unable to provide details on the LiDAR data processing.
Please don't hesitate to reach out if you have any other questions.
Thanks!

hi,
I have another question regarding two returns of the LiDAR sensor data. I am wondering how exactly these two returns are organised. I find for pixels with both returns: 1). the intensity difference could be both negative and positive, so it's not organised as strongest + second strongest;  2). the range difference could also be both negative and positive, though only around 0.1% of pixels having the first return with bigger range than the second return, so they are also not strictly organised as closest peak + second closest peak. I am wondering are there any strict physical properties between the two returns. Thanks for your attention.
Best,
Shengyu

thanks


fix(toggles): move theming rules to component folder

Describe pull-request
Moving theming rules to component folder
Solving issue
Fixes: AB#2224
How to test

Open toggles in Storybook of this branch
Open toggles in Storybook of production
Compare styling- there should not be any difference between those two

The color is off in the disabled state between main-branch and the deployed version. Probably just a simple variable error?

@EmelieLitwin - Please check if you have the latest changes in your local main branch, maybe it is just a commit missing.


Correction for raw affiliation UMR 6226 CNRS – University of Rennes 1

Correction needed for raw affiliation UMR 6226 CNRS – University of Rennes 1
raw_affiliation_name: UMR 6226 CNRS – University of Rennes 1
new_rors: 015m7wh34;02feahw73;00adwkx90
previous_rors: 015m7wh34;02feahw73
works_examples: W4387665734
contact: 23f3bed882c84835e2e14ecee2347cef:b35a7e5b1a34eec7acd65052162a0e5f @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.